You may not be able to connect to an instance of SQL Server 2000 Service Pack 2 or earlier that is installed on a Windows Server 2003 computer through the TCP/IP port

Article translations Article translations
Article ID: 884012 - View products that this article applies to.
Expand all | Collapse all

SYMPTOMS

You may not be able to connect to an instance of Microsoft SQL Server 2000 Service Pack 2 (SP2) or to an earlier version of Microsoft SQL Server 2000 through a TCP/IP port. This problem occurs when the following conditions are true:
  • You try to connect to an instance of SQL Server 2000 that is installed on a computer that is running Microsoft Windows Server 2003.
  • You try to connect to an instance of SQL Server 2000 from a remote computer on your network.


Additionally, you may receive one of the following error messages:

Error message 1

[TCP/IP Sockets]SQL Server does not exist or access denied.
[TCP/IP Sockets]ConnectionOpen (Connect()).

Error message 2

Unable to connect to server <SQL Server Instance Name>:
Server: Msg 17, Level 16, State 1
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]SQL Server does not exist or access denied.

Error message 3

Connection failed:
SQLState: '01000'
SQL Server Error: 10061
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen (Connect()).

Connection failed:
SQLState: '08001'
SQL Server Error: 11
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]General network error. Check your network documentation.




Note You may also notice this behavior when you try to connect to an instance of Microsoft SQL Server 2000 Service Pack 3 (SP3) or to a later version of SQL Server 2000 that is installed on a computer that is running Window Server 2003, if the instance of SQL Server 2000 SP2 or the earlier version of SQL Server 2000 is installed on the same computer.

CAUSE

Because the Windows Server 2003 family does not support SQL Server 2000 SP2 or earlier versions of SQL Server 2000, Windows Server 2003 blocks both the TCP/IP network ports and the UDP network ports that are required to connect to an instance of SQL Server 2000. Therefore, you cannot connect to an instance of SQL Server from a remote computer on your network by using the TCP/IP protocol.

RESOLUTION

To resolve this problem, upgrade all the instances of SQL Server 2000 that are running on a Windows Server 2003-based computer to SQL Server 2000 Service Pack 3 (SP3) or to a later version of SQL Server 2000.

For additional information about how to obtain latest service pack for SQL Server 2000, click the following article number to view the article in the Microsoft Knowledge Base:
290211 How to obtain the latest SQL Server 2000 service pack


Note You cannot work around this problem. You must upgrade all the instances of SQL Server 2000 to SQL Server 2000 SP3 or to a later version of SQL Server 2000.

STATUS

This behavior is by design.

MORE INFORMATION

When you install an instance of SQL Server 2000 SP2 or an earlier version of SQL Server 2000 on a computer that is running Windows Server 2003, Windows Server 2003 logs an Information event that is similar to the following in the application log. The message states that the instance of SQL Server is vulnerable to virus attacks.

Type: Information
Source: MSSQLSERVER/MSDE
Category: None
Event ID: 1
Date: 5/6/2004
Time: 5:29:24 AM
User: N/A
Computer: <Computer Name>

Description:

You are running a version of Microsoft SQL Server 2000 or Microsoft SQL Server 2000 Desktop Engine (also called MSDE) that has known security vulnerabilities when used in conjunction with the Microsoft Windows Server 2003 family. To reduce your computer's vulnerability to certain virus attacks, the TCP/IP and UDP network ports of Microsoft SQL Server 2000, MSDE, or both have been disabled. To enable these ports, you must install a patch, or the most recent service pack for Microsoft SQL Server 2000 or MSDE from http://technet.microsoft.com/en-us/sqlserver/bb331754.aspx

For more information, see Help and Support Center at http://support.microsoft.com.

REFERENCES

For additional information, click the following article numbers to view the articles in the Microsoft Knowledge Base:
841375 A message stating that an instance of SQL Server is vulnerable to virus attacks is logged in the application event log when you install SQL Server 2000 or MSDE 2000 on a computer that is running Windows XP Service Pack 2

815431 Installation of a named instance of SQL Server 2000 virtual server on a Windows 2003-based cluster fails

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

329329 Windows Server 2003 support for SQL Server 2000


Properties

Article ID: 884012 - Last Review: November 16, 2007 - Revision: 3.6
APPLIES TO
  • Microsoft SQL Server 2000 Standard Edition, when used with:
    • Microsoft Windows Server 2003, Standard Edition (32-bit x86)
  • Microsoft SQL Server 2000 Service Pack 1, when used with:
    • Microsoft Windows Server 2003, Standard Edition (32-bit x86)
  • Microsoft SQL Server 2000 Service Pack 2, when used with:
    • Microsoft Windows Server 2003, Standard Edition (32-bit x86)
Keywords: 
kbconnectivity kbnetwork kberrmsg kbtshoot kbprb KB884012

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com