The SQL Server Agent service may not start because it waits for SQL Server to recover the databases. Therefore, when you receive the following message in the SQL Server error log file, the connections will no longer fail with a timeout error:
Recovery Complete
If the recovery process takes a long time, you may have to additionally troubleshoot the recovery process.
Test different ways to connect to the instance of SQL Server
If you experience connectivity problems when you connect to the instance of SQL Server, you can use one or more of the following methods to work around the connectivity problem.
• Test the connectivity to the instance of SQL Server by using both SQL Server Authentication and Windows authentication.
• Test the connectivity to the instance of SQL Server from other data sources, such as an ODBC DSN, a .udl file, SQL Query Analyzer, SQL Server Enterprise Manager, the isql utility, or the osql utility.
• Test the connectivity to the instance of SQL Server by using different protocols. You can specify different protocols by creating a new alias for the instance of SQL Server using that protocol. You can also specify the protocol in your connection string by adding tcp:, np:, lpc:, or rpc: to the beginning of the name of the instance of SQL Server. For example, if TCP/IP connections are not successful, named pipes connections succeed.
• Test the connectivity by using a different login account to help you determine if the problem is associated with a particular login account.
• Try to add an entry that corresponds to the IP address of the computer that is running the instance of SQL Server to the %systemroot%\system32\drivers\etc\hosts file.
• Try to connect to the instance of SQL Server from the computer that is running SQL Server and from the client.
• If you are connecting from the computer that is running SQL Server, you can specify "." or "(local)" (without the quotation marks) instead of the server name and then connect.
• Try to connect to the instance of SQL Server by using the IP address instead of the server name.
• Try to specify the specific port that the instance of SQL Server is listening on, either by creating an alias or by adding a port number to the connection string (MyServer\MyInstance, 1433, for example).
Capture network monitor traces
If the connectivity problem is not resolved by the steps that are mentioned in "Test different ways to connect to the instance of SQL Server 2000" section, use the Network Monitor utility to capture network traces.
To obtain more detailed information, you may have to use SQL Profiler traces. You can also use the Network Diagnostics Tool for non-clustered computers that are running SQL Server for network tracing.
上一页 [1] [2] [3] [4] [5] 下一页
SQL Server英文文献和翻译 第4页下载如图片无法显示或论文不完整，请联系qq752018766
