Potential causes of the "SQL Server does not exist or access denied" error message

Extended support for SQL Server 2005 ended on April 12, 2016

If you are still running SQL Server 2005, you will no longer receive security updates and technical support. We recommend upgrading to SQL Server 2014 and Azure SQL Database to achieve breakthrough performance, maintain security and compliance, and optimize your data platform infrastructure. Learn more about the options for upgrading from SQL Server 2005 to a supported version here.

"SQL Server does not exist or access denied" is a generic Microsoft Data Access Components (MDAC) message that indicates that the computer that is running Microsoft SQL Server cannot be contacted. This generic message has many potential causes.

Additionally, the following error messages also have similar causes:
SQL Server is unavailable or does not exist.
The specified SQL Server is not found.

Important The "SQL Server does not exist or access denied" message does not indicate the following:
  • The logon process to SQL Server failed.
  • SQL Server does not have the correct permissions to process the query.
  • You cannot use SQL Server authentication because only Windows authentication is permitted.

Potential causes

Server-related causes

If no client computers can connect to the computer that is running SQL Server, there may be a server-side problem.
Potential causeResolution
SQL Server is not installed on the computer that you specify in the connection string.Verify that SQL Server is actually installed on the computer that you specify in your connection string.
SQL Server is not started.SQL Server must be running to accept connections.
SQL Server is not listening on the protocol or port that you are using to connect.The Server Network Utility on the server determines which protocols SQL Server will use and on which TCP/IP ports SQL Server will listen. The Client Network Utility, an MDAC data source name (DSN), or your connection string determines which protocol and port your client uses when it connects. For more information, view PRB: Configuring DSNs with SQL Server net-libraries and SQL Server clients may change protocols when the client computers try to connect to an instance of SQL Server.
When SQL Server started, it could not listen on the specified TCP/IP port and is not accepting TCP/IP connections.View Clients cannot communicate to SQL Server through port 1433 or the port SQL Server is listening on.
The SQL Server name is different from the computer name.View BUG: "Renaming a server" topic in SQL Server Books Online is incomplete for SQL Server 2000.
View Frequently asked questions - SQL Server 7.0 - SQL Setup for SQL Server 7.0.
View How to change a clustered SQL Server network name for SQL Server in a clustered environment
On a multihomed computer that is running SQL Server 2000 Desktop Engine (MSDE), clients may be unable to connect to the server.View FIX: MSDE connection may fail on a multihomed computer.
When you attempt to open a connection to a computer that is running SQL Server 2000 over a virtual private network (VPN) connection, the attempt may fail.View FIX: Dynamic IP addresses cannot connect to SQL Server 2000.
Starting with SQL Server Desktop Engine (also known as MSDE 2000) Service Pack 3 (SP3) or SP3a , only local connectivity is permitted, by default.If you want to permit remote connections to SQL Server Desktop Engine, follow the steps in How to help secure network connectivity for SQL Server 2000 local databases.

Client-related or application-related causes

If some client computers or applications can connect but others cannot, you are probably experiencing a client-side problem.
Potential causeResolution
The computer name does not exist.Double-check the spelling of the computer to which you are trying to connect.
You are trying to access a named instance of SQL Server, but you are not specifying the correct instance name.View How to connect to a SQL Server 2000 named instance with the previous version's client tools.
The Windows-level security that you are using to connect is different from what you expect.For example, Microsoft Internet Information Services (IIS) uses IUSR_computername, not the account with which you log on to Windows or perhaps another account depending on how you configured IIS. Additionally, linked servers use the Windows-level security context of SQL Server Agent in some circumstances. The security context of the account that you are using may not have access to the computer on which SQL Server is installed.
You are not using the correct protocol.Check your Client Network Utility (CNU) to verify the protocols that you are using (for earlier versions of MDAC, you set a default instead of enabling protocols). Additionally, verify whether there are any defined aliases in the CNU that specify a different protocol or port (or both) than you expect. For more information, view SQL Server clients may change protocols when the client computers try to connect to an instance of SQL Server and PRB: Configuring DSNs with SQL Server net-libraries.
You removed the Client for Microsoft Networks networking component from the network properties on the client.View Client for Microsoft Networks functions when unbound from network adapter.
If SQL Server is clustered, the network adapters may be incorrectly named or configured.If any network adapters are named with special characters or with mixed case, rename them. Verify that the network adapters on the computer are configured properly.
You may be experiencing the side effects of an MDAC mismatch.View Component Checker: Diagnose problems and reconfigure MDAC installations.
Check the protocol that is specified in the following registry subkey:
This value typically reflects the settings in the CNU, but sometimes it does not.
If the value is DBNETLIB, it uses one of the protocols in the enabled protocols list of the CNU. If a specific protocol is listed, that protocol is used instead.
You are trying to connect through named pipes, but either the named pipe on which SQL Server is listening has changed from the default, or you are using the incorrect pipe name.For a default instance, use the following pipe in the Server Network Utility:
For a named instance, use:
You have specified a DSN that is not of the correct type (file, user, or system).View How to use system, user, and file data sources.
A standalone computer (without any network protocols installed) fails to connect locally to the Microsoft SQL Server 7.0 Desktop Edition.View BUG: SQL Desktop Edition: Shared memory fails to connect after you install MDAC 2.6.

Network-related or domain-related causes

If you receive this error message only with computers that are in a specific domain, on a certain subnet, or behind a firewall, review the following issues.
Potential causeResolution
A firewall or router is not configured properly or has been configured to block UDP port 1434.If UDP port 1434 is blocked, you may have to specify the port on which SQL Server is listening in your connection string from the client. For more information, view TCP ports needed for communication to SQL Server through a firewall and BUG: Cannot connect to a clustered named instance through a firewall.
The local security policy user rights assignment for your Windows account does not allow access from the network.The "Access this Computer from the Network" policy must be permitted. Additionally, the "Deny access to this computer from the network" right must not be granted.
There is a domain trust problem, or one of the computers is in a workgroup and therefore has no access to the domain.In some cases, to work around this problem, you can create the same local Windows account on both computers with the same password for each account. For more information, view How to configure security for log shipping.
Your name resolution is not working.Check your settings in the name resolution system that you use (such as DNS, WINS, hosts, or lmhosts). For more information, view How to troubleshoot basic TCP/IP problems.
tcp/ip tcpip named pipes shared memory odbc mdac

Article ID: 328306 - Last Review: 03/05/2015 03:24:00 - Revision: 17.0

Microsoft SQL Server 2000 Standard Edition, Microsoft SQL Server 7.0 Standard Edition, Microsoft SQL Server 2005 Standard Edition, Microsoft SQL Server 2005 Express Edition, Microsoft SQL Server 2005 Developer Edition, Microsoft SQL Server 2005 Enterprise Edition, Microsoft SQL Server 2005 Workgroup Edition

  • kbsqlsetup kbinfo KB328306