How to solve the connection problem in SQL Server 2000

SQL Server also rolls forward committed transactions and does not write changes to the hard disk. When the recovery process is completed, SQL Server writes the following information to the SQL Server Error Log File:

Recovery Complete

During the restoration process, the SQL Server may not accept the connection. During this time, clients attempting to connect to SQL Server may receive an error message similar to the following:

Timeout Expired

The SQL Server proxy service may fail to be started because it waits for SQL Server to restore the database. Therefore, when you receive the following information in the SQL Server Error Log File, the connection will no longer fail due to a timeout error:

Recovery Complete

If the recovery process takes a long time, you may need to troubleshoot the fault.

Test different methods for connecting to an SQL Server instance

When you connect to an SQL Server instance, you can use one or more of the following methods to solve the connection problem.

•	Use SQL Server Authentication and Windows authentication to test the connection to the SQL Server instance.
•	Test the connection to an SQL Server instance from other data sources (such as odbc dsn,. udl files, SQL query analyzer, SQL Server Enterprise Manager, isql utility, or osql utility.
•	Use other protocols to test the connection to the SQL Server instance. You can create a new alias for the SQL Server instance that uses this Protocol to specify different protocols. You can also specify the protocol in your connection string by adding tcp:, np:, lpc:, or rpc: at the beginning of the SQL Server instance name. For example, if the TCP/IP connection fails, the pipe connection is successful.
•	Use another Logon account to test the connection. This helps you determine whether the problem is related to a specific Logon account.
•	In the % systemroot % \ system32 \ drivers \ etc \ hosts file, add an entry corresponding to the IP address of the computer on which the SQL Server instance is running.
•	Try to connect to the SQL Server instance from the computer and client running SQL Server.
•	If you are connecting from a computer running SQL Server, you can specify "." or "(local)" (without quotation marks) to replace the Server name and then connect.
•	Try to connect to the SQL Server instance by using the IP address instead of the Server name.
•	Try to specify the specific port on which the SQL Server instance is listening. You can create an alias or add a port number to a connection string (for example, MyServer \ MyInstance, 1433 ).

Capture network monitor traces

If the connection issue cannot be resolved by using the steps mentioned in the "test methods for connecting to an SQL Server 2000 instance" section, use the network monitor utility to capture network traces. For more information about network tracing, click the following article number to view the article in the Microsoft Knowledge Base:

148942 (http://support.microsoft.com/kb/148942/) How to Use Network Monitor to capture network traffic

294818 (http://support.microsoft.com/kb/294818/) FAQs about network monitor

169292 (http://support.microsoft.com/kb/169292/) Basic knowledge of TCP/IP tracking data

102908 (http://support.microsoft.com/kb/102908/) How to exclude TCP/IP connection issues in Windows 2000 or Windows NT

For more details, you need to use the SQL event probe trace. Network diagnostic tools can also be used for non-clustered computers running SQL Server for network tracing. For more information about how to use the network diagnostic tool, click the following article number to view the article in the Microsoft Knowledge Base:

321708 (http://support.microsoft.com/kb/321708/) how to use the network diagnostic tool (Netdiag.exe) in Windows 2000)

Back to Top

Reference

For more information about SQL Server-related connection problems, click the following article number to view the article in the Microsoft Knowledge Base:

812817 (http://support.microsoft.com/kb/812817/) Support Web broadcast: Microsoft SQL Server 2000: Connection troubleshooting 319930 (http://support.microsoft.com/kb/319930/) how to connect to Microsoft Desktop Engine 257434 (http://support.microsoft.com/kb/257434/) INF: the network library in the existing DSN is replaced by the network library in the new DSN connected to the SQL Server with the same name. 306985 (http://support.microsoft.com/kb/306985/) RPC error 313062 (http://support.microsoft.com/kb/313062/) how to connect to a cluster virtual Server in Windows 2000 by Using Active Server Pages to connect to database 313295 (http://support.microsoft.com/kb/313295) how to Use The server name parameter in The Connection string to specify The client network library 320728 (http://support.microsoft.com/kb/320728/) How to exclude The "The Maximum Connection Limit Has Been Reached" error message 328306 (http://support.microsoft.com/kb/328306/) INF: possible cause 247931 (http://support.microsoft.com/kb/247931/) INF: verify in Active Server Page the method for connecting to SQL Server 169377 (http://support.microsoft.com/kb/169377/) how to access SQL Server 328383 (http://support.microsoft.com/kb/328383/) INF in Active Server Page: the SQL Server Client can change Protocol 238949 (http://support.microsoft.com/kb/238949/) on connection how to set the SQL Server network library 270126 (http://support.microsoft.com/kb/270126/) PRB in the ADO connection string: how to manage client connections to two SQL Server 7.0 virtual servers 2000 (http://support.microsoft.com/kb/316779/) PRB after an Active/Active Cluster 316779 upgrade: clients with forced protocol encryption settings may not be able to connect 216643 (http://support.microsoft.com/kb/216643/) INF through an IP Address: ODBC/OLEDB connection option 7.0 (http://support.microsoft.com/kb/265808/) cannot be found when a connection to SQL Server 265808 is tracked) INF: how to connect to SQL Server 2000 named instance 191572 (http://support.microsoft.com/kb/191572/) INFO: Connection Pool 313173 (http://support.microsoft.com/kb/313173/) managed from ADO object called by ASP) example of a JDBC driver for Microsoft SQL Server 2000 connection pool manager 237844 (http://support.microsoft.com/kb/237844/) How to enable ODBC connection pool 259569 (http://support.microsoft.com/kb/259569/) PRB in a Visual Basic ADO application: installing third-party products destroys Windows 2000 MDAC Registry Settings

Back to Top

The information in this article applies:

•	Microsoft SQL Server 2000 Standard Edition

Back to Top

Keywords:

Kberrmsg kbhowto kbtshoot kbregistry kbsqlclient kbdns kbdll kbclientserver kbclient KB827422

Back to Top

Microsoft and/or its suppliers do not declare the applicability of files published on the server and the information contained in the graphics for any purpose. All such documents and related figures are provided "in accordance with the sample" without warranty of any nature. Microsoft and/or its suppliers