SQL Server外文文献及翻译 第6页
3. Try to connect to the instance of SQL Server by using different protocols. For example, the connections that use the TCP/IP protocol with Windows authentication may not be successful, but connections that use the named pipes protocol with Windows authentication may be successful.
If you are using certificates, you may receive a Secure Sockets Layer (SSL) security error message when you try to connect to the instance of SQL Server.
Troubleshoot stress on TCP/IP sockets
When you use the SQL Server ODBC driver, the Microsoft OLE DB Provider for SQL Server, or the System.Data.SqlClient managed provider, you can disable connection pooling by using the appropriate application programming interfaces (APIs). When you disable connection pooling and your application frequently opens and closes connections, the stress on the underlying SQL Server network library may increase. Sometimes, the Web servers and the JDBC drivers may also try to connect to the instance of SQL Server. Therefore, the increase in connection requests to SQL Server may be more than SQL Server can handle. This may stress the TCP/IP sockets, and you may receive the following error message in the SQL Server error log file:
2003-08-07 20:46:21.11 server Error: 17832, Severity: 20, State: 6
2003-08-07 20:46:21.11 server Connection opened but invalid login packet(s) sent. Connection closed.
For additional information, click the following article numbers to view the articles in the Microsoft Knowledge Base:
154628 INF: SQL logs 17832 with multiple TCP\IP connection requests
328476 TCP/IP settings for SQL Server drivers when pooling is disabled
Note You may not notice the stress on TCP/IP sockets if you are running SQL Server 2000 SP3 or SQL Server 2000 SP3a because a limit on the number of login packets was added. The 17832 error occurs when you use third-party drivers to connect to the instance of SQL Server. To resolve this problem, contact the third-party vendor and obtain drivers that have been tested to work with SQL Server 2000 SP3 and SQL Server 2000 SP3a.
See if the instance of SQL Server is started in single-user mode
If the instance of SQL Server that you are trying to connect to is started in single-user mode, only one connection can be established with SQL Server. If you have software running on your computer that automatically connects to SQL Server, the software can easily use the only connection. For example, the following software can automatically connect to the instance of SQL Server:
• SQL Server Agent
• Third-party backup software
• Third-party monitoring software
• Third-party virus software
• Microsoft Internet Information Services (IIS)
• SQL Server Enterprise Manager
The client application that is trying to connect to the instance of SQL Server receives the following error message:
SQL Server does not exist or Access Denied
This error generally occurs during SQL Cluster Setup and service pack setup when the setup process starts the instance of SQL Server in single-user mode. The specified applications may automatically connect to the instance of SQL Server using the only available connection, and setup is not successful.
To determine if the instance of SQL Server has been started in single-user mode, check to see if the SQL Server error log file has an entry that is similar to following:
2003-07-31 11:26:43.79 spid3 Warning ******************
2003-07-31 11:26:43.80 spid3 SQL Server started in single user mode. Updates allowed to system catalogs.
Verify named pipes connectivity to SQL Server
If you cannot connect to the instance of SQL Server by using named pipes, make sure that the instance of SQL Server is configured to accept named pipes connections.
Troubleshoot connections that time out during the recovery process
Every time that you start an instance of SQL Server, SQL Server recovers each database. During this recovery process, SQL Server rolls back the transactions that are not committed. SQL Server also rolls forward the transactions that are committed and the changes that were not written to the hard disk when the instance of SQL Server was stopped. When the recovery process is complete, SQL Server logs the following message in the SQL Server error log file:
Recovery Complete
During the recovery process, SQL Server may not accept connections. Clients that try to connect to the instance of SQL Server during that time may receive an error message that is similar to the following:
Timeout Expired
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 优,文-论'文.网
http://www.youerw.com , 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] [6]
SQL Server外文文献及翻译 第6页下载如图片无法显示或论文不完整，请联系qq752018766
