Occurrence of error messages are the common phenomenon that you experiences while working on SQL server. There may be database related errors, network related problems or application failure. Whatever are the error messages and the cause behind the errors but it frustrates you completely. Sometimes it happens that you are unable to connect the instance of SQL server and experience SQL server not exists error. It generally appears on system having Windows XP service pack2 when you fail to connect to its SQL Server. You receive following error message while trying to do so.

Unable to connect to server

Server: Msg 17, Level 16, State 1 [Microsoft][ODBC SQL Server Driver][Named Pipes]SQL Server does not exist or access denied.

Causes behind the error

• When you try to connect to such an instance of SQL server that is configured only on Named Pipes server network library
• Failure of logon process
• Incorrect permissions for query
• When you try to connect to the instance using TCP/IP sockets
• When SQL server is installed on a cluster

All above mentioned reasons are responsible for the occurrence of SQL server not exists error. The error usually appears during discovery phase of connection.

Resolution

• The problem can be resolved if you hardcode TCP port or Named Pipe of SQL server named instance
• Change network connection settings to enable TCP Port 445
• You can also enable TCP port 445 by enabling file and printer sharing

By using above mentioned steps you will be able to fix the SQL server not exists error and smoothly connect to SQL Server. But in between connection failure sometimes it happens that your database becomes damaged or corrupted due to some internal or human errors. It also occurs due to corrupt network or virus attack. So, after resolving the error you should restore your database with recent backup. In case, if backup is not available then use MS SQL Database Repair Software. It fixes common issues of SQL Server database and also restores the lost objects.