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 (884012)
The information in this article applies to:
- Microsoft SQL Server 2000 (all editions), when used with:
- the operating system: Microsoft Windows Server 2003
- Microsoft SQL Server 2000 (all editions) SP1, when used with:
- the operating system: Microsoft Windows Server 2003
- Microsoft SQL Server 2000 (all editions) SP2, when used with:
- the operating system: Microsoft Windows Server 2003
SYMPTOMSYou 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. CAUSEBecause 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.RESOLUTIONTo 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.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
Modification Type: | Major | Last Reviewed: | 9/22/2006 |
---|
Keywords: | kbconnectivity kbnetwork kberrmsg kbtshoot kbprb KB884012 kbAudDeveloper |
---|
|