Take for example, SQL Server 2017 Developer's edition. It is the latest release version. When you install it you can only access using 'localhost' as shown.
Enter localhost
SQLServrConfig0
Click Connect and you are connected as shown.
The error message indicated that it was due to Named Pipe provider error.
Let us enable Named Pipes protocol in SQL Server Configuration Manager as shown.
SQLServrConfig2
Make a note that when you change (enable/disable), you need to stop and start the server. You can do this in SQL Server Configuration Manager.
Now attempt to connect using IPAddress as before.
SQLServrConfig4
Click Connect and you are connected as shown.
SQLServrConfig3
That is all there is to it.
Enter localhost
Click Connect and you are connected as shown.
SQLServrConfig00
Now instead of localhost, try the IPAddress as shown.
SQLServrConfig4
Trying to Connect you get the following message.
The reason for this is that the Protocols for MSSQLSERVER (the instance we are considering) has only Shared Memory enabled as in the SQL Server Configuration Manager.
SQLServrConfig1
The error message indicated that it was due to Named Pipe provider error.
Let us enable Named Pipes protocol in SQL Server Configuration Manager as shown.
Make a note that when you change (enable/disable), you need to stop and start the server. You can do this in SQL Server Configuration Manager.
Now attempt to connect using IPAddress as before.
Click Connect and you are connected as shown.
SQLServrConfig3
That is all there is to it.
No comments:
Post a Comment