Article ID: 818510 - View products that this article applies to.
This article has been archived. It is offered "as is" and will no longer be updated.
When you try to connect to a Microsoft SQL Server named instance by using a Canonical Name (CNAME), the client receives the following error message, and the connection fails:
This behavior also occurs when you try to connect to a SQL server named instance by using the Hosts (A records).
SQL Server does not exist or access denied
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft Data Access Components (MDAC) service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
Note The installer for this fix is named Q818510_MDAC27_x86.exe.
Date Time Version Size File Name -------------------------------------------------------- 26-Jun-2003 18:39 2000.81.9031.49 61,440 Dbnetlib.dll
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
A CNAME or canonical name is an alias for a particular TCP/IP address that is defined in DNS (Domain Name System). For example, if the TCP/IP address is 10.10.10.10 and if the real computer name is Server1, you can define a CNAME in DNS that is named Server2 that also resolves to the 10.10.10.10 TCP/IP address. Therefore, with a CNAME, you can have two names that point to the same TCP/IP address.
Contact us for more help
Connect with Answer Desk for expert help.