22 May, 2009
0 Comments
0 categories
Applies to Microsoft SQL Server 2000
If Named Pipes come before TCP/IP in the SQl Server Client Network Utility, you can get the error message "SQL Server does not exist or access denied", when you try to connect remotely to your Microsoft SQL Server 2000 instance. When you connect localy on the server everything seems to work fine.
Solution
Disable all network protocols except TCP/IP in the SQl Server Client Network Utility
Restart the service of your Micorosft SQL Server 2000 instance.
Tags: SQL Server
One Reply to “Named Pipes before TCP/IP causes "SQL Server does not exist or access denied" error message”