【導(dǎo)讀】然而,當(dāng)客戶端申請和SQLServer的例證在不同的計算機(jī)，網(wǎng)。SQLSever2021使用網(wǎng)絡(luò)控件庫與一個特別的網(wǎng)絡(luò)記錄溝通。使用的網(wǎng)絡(luò)記錄。舉例來說，如果你想要使一個客戶申請能夠與通過TCP/IP的。在這一個情節(jié)中,TCP/IP協(xié)議。期間，服務(wù)器的網(wǎng)絡(luò)庫也被同時安裝了。如此，SQLServer2021啟用并偵聽TCP/IP、命名管道和共享內(nèi)存。的問題或Windows身份認(rèn)證的問題引起，或者兩者共同組合引起。MSSQLServer服務(wù)已在運(yùn)行SQLServer的計算機(jī)上啟動。域名系統(tǒng)的名稱解析過程被用于解決IP對SQLServer實例名稱。的%systemroot%\system32\drivers\etc\hosts文件中為服務(wù)器添加一個條目。應(yīng)用程序中使用的其他協(xié)議，請打開當(dāng)前的SQLServer錯誤紀(jì)錄文件。在默認(rèn)情況下，一個SQLServer實例默。關(guān)于使用服務(wù)器網(wǎng)絡(luò)實用程序的更多信息，請參見SQLServer在線。參考書中的“SQLServer網(wǎng)絡(luò)實用程序”專題。地址進(jìn)行連接，就可能會出現(xiàn)此問題。

　　

【正文】 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 2021 SP3 or SQL Server 2021 SP3a because a limit on the number of login packets was added. The 17832 error occurs when you use thirdparty drivers to connect to the instance of SQL Server. To resolve 20 this problem, contact the thirdparty vendor and obtain drivers that have been tested to work with SQL Server 2021 SP3 and SQL Server 2021 SP3a. See if the instance of SQL Server is started in singleuser mode If the instance of SQL Server that you are trying to connect to is started in singleuser mode, only one connection can be established with SQL Server. If you have software running on your puter 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 ? Thirdparty backup software ? Thirdparty monitoring software ? Thirdparty virus software ? Microsoft Inter 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 singleuser 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 singleuser mode, check to see if the SQL Server error log file has an entry that is similar to following: 20210731 11:26: spid3 Warning ****************** 20210731 11:26: 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 mitted. SQL Server also rolls forward the transactions that are mitted and the changes that were not written to the hard disk when the instance of SQL Server was stopped. When the recovery process is plete, 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 21 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 puter 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 puter that is running SQL Server and from the client. ? If you are connecting from the puter 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 work 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 2021 section, use the Network Monitor utility to capture work traces. To obtain more detailed information, you may have to use SQL Profiler traces. You can also use the Network Diagnostics Tool for nonclustered puters that are running SQL Server for work tracing.