計算機專業(yè)外文翻譯--如何解決 sql server 2000 中的連接問題

1、<p>　　How to troubleshoot connectivity issues in SQL Server 2000</p><p>　　Chris Tull, Microsoft Help and Support</p><p>　　This article can help you to resolve connectivity problems with Mic

2、rosoft SQL Server 2000. This article contains descriptions of common connectivity problems and the steps that you can take to help resolve your connectivity problems. </p><p>　　SQL Server 2000 supports sever

3、al methods of communication between the instance of SQL Server and the client applications. If your client application and the instance of SQL Server reside on the same computer, Microsoft Windows interprocess communicat

4、ion (IPC) components, such as local named pipes or the Shared Memory protocol, are used to communicate. However, when the client application and the instance of SQL Server reside on different computers, a network IPC, su

5、ch as TCP/IP or named pipes, i</p><p>　　?Communication Components</p><p>　　?Client and Server Net-Libraries</p><p>　　?Managing Clients</p><p>　　Troubleshoot connecti

6、vity issues</p><p>　　Most of the connectivity issues that you may notice in SQL Server 2000 occur because of problems with TCP/IP, Windows authentication, or a combination of TCP/IP and Windows authenticatio

7、n. Important Before you start to troubleshoot connectivity issues in SQL Server 2000, make sure that the MSSQLServer service is started on the computer that is running SQL Server.</p><p>　　Verify your DNS

8、settings</p><p>　　The name resolution process in Domain Name System (DNS) is used to resolve the IP address to the name of the instance of SQL Server. If the name resolution process does not work correctly,

9、the instance of SQL Server is not reachable, and you may receive one or more of the following error messages: </p><p>　　SQL Server does not exist or access denied</p><p>　　General Network Error&

10、lt;/p><p>　　Cannot Generate SSPI Context</p><p>　　To verify that the name resolution process is resolving the correct server, you can ping the server by using the server name and the IP address of

11、the server. To do so, follow these steps: </p><p>　　1.Click Start, and then click Run.</p><p>　　2.In the Run dialog box, type cmd in the Open box, and then click OK.</p><p>　　3.A

12、t the command prompt, run the following command:</p><p>　　ping <Server Name></p><p>　　Note the IP address that is returned.</p><p>　　4.At the command prompt, run the followin

13、g command (where IP address is the IP address that you noted in step 3):</p><p>　　ping –a <IP address></p><p>　　Verify that the command resolves to the correct server name. If either of th

14、e specified commands are not successful, time out, or do not return the correct values, the DNS lookup is not working correctly or the problem occurs because of other networking or routing issues. To see your current DNS

15、 settings, run the following command at a command prompt:</p><p>　　ipconfig /allTo work around this problem, add an entry for the server to the %systemroot%\system32\drivers\etc\hosts file on the client com

16、puter. You can also work around the problem by connecting to the server by using the Named Pipes Net-library.</p><p>　　Verify the enabled protocols and aliases</p><p>　　Connectivity problems may

17、 occur if the alias on the client computer is set incorrectly. You can view the aliases by using Client Network Utility. To do so, follow these steps: </p><p>　　1.Start Client Network Utility. If the SQL Se

18、rver client tools are installed on the computer that is running the client application, follow these steps to start Client Network Utility: </p><p>　　a. Click Start, and then point to Programs.</p>&

19、lt;p>　　b. Point to Microsoft SQL Server, and then click Client Network Utility.</p><p>　　If the SQL Server client tools are not installed on the client computer, follow these steps to start Client Networ

20、k Utility: </p><p>　　a. Click Start, and then click Run.</p><p>　　b. In the Run dialog box, type cliconfg in the Open box, and then click OK.</p><p>　　2.In the SQL Server Client

21、Network Utility window, click the General tab, and then enable all the protocols that you want to use.</p><p>　　Note You must at least enable the TCP/IP protocol and the named pipes protocol.</p><

22、p>　　3.Click the Alias tab, and then verify the aliases that are configured for the instance of SQL Server. </p><p>　　4.Verify the properties of the aliases to make sure that the server name or IP addres

23、s and the protocol are configured correctly.</p><p>　　You can create a new alias to test the connectivity by using the server name, the IP address, or even by using a different protocol.Note Earlier version

24、s of Microsoft Data Access Components (MDAC) have a different user interface for Client Network Utility. Therefore, if you do not see the options that are listed in this article, install a later version of MDAC on the co

25、mputer that is running the client application.</p><p>　　Verify that the instance of SQL Server is listening correctly</p><p>　　To verify that the instance of SQL Server is listening on named pip

26、es, TCP/IP, or another protocol that you are using at the client application, open the current SQL Server error log file. The SQL Server error log file may contain entries that are similar to the following:</p>&l

27、t;p>　　2003-11-06 09:49:36.17 server SQL server listening on TCP, Shared Memory, Named Pipes. 2003-11-06 09:49:36.17 server SQL server listening on 192.168.1.5:1433, 127.0.0.1:1433.If you analyze the entries in the SQ

28、L Server error log file, you can verify that the instance of SQL Server is listening on the correct IP address and on the correct port. By default, a default instance of SQL Server listens on the port 1433. You can also

29、use Server Network Utility to verify the protocol settings for SQL Se</p><p>　　2001-11-14 15:49:14.12 server SuperSocket Info: Bind failed on TCP port 1433.If you cannot connect to the instance of SQL Serve

30、r by using a TCP/IP connection, try to use the named pipes protocol or the Shared Memory protocol. Run the following command at a command prompt to obtain information about the ports that are in use:</p><p>

31、　　NETSTAT –an</p><p>　　You can also use the Portqry command-line utility to obtain more information about the ports that are in use.Note For named instances of SQL Server, SQL Server dynamically determines

32、the port and listens on the determined port. Therefore, when you start the named instance of SQL Server, SQL Server tries to listen on the port that was previously being used. If SQL Server cannot bind to that port, the

33、named instance may dynamically bind to a different port. In that situation, make sure that the c</p><p>　　Troubleshoot MDAC Issues</p><p>　　Connectivity problems may also occur because of proble

34、ms with MDAC. For example, a software installation may overwrite some of the MDAC files or change the permissions that you must have to access the MDAC files. You can run the MDAC Component Checker to verify the MDAC ins

35、tallation on your computer.Note If you are connecting to a named instance of SQL Server, make sure that you are running MDAC 2.6 or later on your computer. Earlier versions of MDAC do not recognize named instances of SQ

36、L Serv</p><p>　　Troubleshoot firewall issues</p><p>　　If firewall exists between the client computer and the computer that is running SQL Server, make sure that the ports that are required to co

37、mmunicate through the firewall are open.If you use the TCP/IP protocol to connect to the instance of SQL Server, make sure that you can use the Telnet program to connect to the port where SQL Server is listening. To use

38、 the Telnet program, run the following command at a command prompt: </p><p>　　Telnet <IP Address> <Port Number></p><p>　　If the Telnet program is not successful and you receive an er

39、ror message, resolve the error and then try to connect again.Note Because of issues that were caused by the Slammer virus, the User Datagram Protocol (UDP) port 1434 may be blocked on your firewall.</p><p>

40、　　Troubleshoot authentication and security issues</p><p>　　Connections to SQL Server may not be successful because of authentication failures. If the authentication fails, you may receive one of the followin

41、g error messages:</p><p>　　Login failed for user '<username>'</p><p>　　Login failed for user 'NTAUTHORITY\ANONYMOUS LOGON'</p><p>　　Login failed for user '

42、null'</p><p>　　If you receive an error message because of an authentication failure and the error message does not mention a specific SQL Server login name, troubleshoot the problem with Windows authenti

43、cation. You may receive the following error message because of problems with Windows authentication: </p><p>　　Cannot generate SSPI Context</p><p>　　The following problems may cause authenticati

44、on and security issues: </p><p>　　?Problems occur with NTLM authentication or with Kerberos authentication.</p><p>　　?The domain controller cannot be contacted because of connectivity issues.&

45、lt;/p><p>　　?Problems occur with trust relationships across domains.</p><p>　　For more information about possible causes, see the event logs on the computer. To work around connectivity problems w

46、ith Windows authentication, you can use SQL Server Authentication to connect to the instance of SQL Server. </p><p>　　If the connection is not successful when you use SQL Server Authentication, you receive t

47、he following error message: </p><p>　　Login failed for user '<username>' . Not associated with a trusted connectionTo troubleshoot this problem, follow these steps. Warning If you use Registr

48、y Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use

49、 Registry Editor at your own risk. </p><p>　　1.Make sure that the instance of SQL Server is configured to use Windows authentication and SQL Server Authentication. To do so, make sure that the following reg

50、istry keys are on the computer that is running SQL Server. For the default instance of SQL Server: </p><p>　　HKEY_LOCAL_MACHINE\Software\Microsoft\MSSQLServer\MSSQLServer\LoginMode</p><p>　　For

51、the named instance of SQL Server: </p><p>　　HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server\<Instance Name>\MSSQLServer\LoginMode</p><p>　　Make sure that the following registry

52、key values are set:</p><p>　　Authentication typeValue</p><p>　　Windows authentication only1</p><p>　　Mixed mode (SQL Server Authentication and Windows authentication)2</p>

53、<p>　　Note If you make any changes to the registry, you must stop and then restart the instance of SQL Server for the changes to take effect.</p><p>　　2.Try to connect to the instance of SQL Server by

54、 using different Windows accounts or SQL Server login accounts. This can help determine if the connection is not successful because of problems with a particular login account. For example, the password of the login acco

55、unt may have been changed.</p><p>　　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

56、 be successful, but connections that use the named pipes protocol with Windows authentication may be successful.</p><p>　　If you are using certificates, you may receive a Secure Sockets Layer (SSL) security

57、error message when you try to connect to the instance of SQL Server. Troubleshoot stress on TCP/IP sockets</p><p>　　When you use the SQL Server ODBC driver, the Microsoft OLE DB Provider for SQL Server, or

58、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

59、 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 </p><p>　　2003-08

60、-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 nu

61、mbers to view the articles in the Microsoft Knowledge Base: </p><p>　　154628 (http://support.microsoft.com/kb/154628/) INF: SQL logs 17832 with multiple TCP\IP connection requests </p><p>　　3284

62、76 (http://support.microsoft.com/kb/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

63、 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 an

64、d obtain drivers that have been tested to work with SQL </p><p>　　See if the instance of SQL Server is started in single-user mode</p><p>　　If the instance of SQL Server that you are trying to c

65、onnect 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 o

66、nly connection. For example, the following software can automatically connect to the instance of SQL Server: </p><p>　　?SQL Server Agent</p><p>　　?Third-party backup software</p><p&

67、gt;　　?Third-party monitoring software</p><p>　　?Third-party virus software</p><p>　　?Microsoft Internet Information Services (IIS)</p><p>　　?SQL Server Enterprise Manager </p

68、><p>　　The client application that is trying to connect to the instance of SQL Server receives the following error message: </p><p>　　SQL Server does not exist or Access Denied</p><p>

69、　　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 inst

70、ance 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 e

71、ntry that is similar to following: </p><p>　　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.&

72、lt;/p><p>　　Verify named pipes connectivity to SQL Server</p><p>　　If you cannot connect to the instance of SQL Server by using named pipes, make sure that the instance of SQL Server is configured

73、to accept named pipes connections. </p><p>　　Troubleshoot connections that time out during the recovery process</p><p>　　Every time that you start an instance of SQL Server, SQL Server recovers

74、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 h

75、ard 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: </p><p>　　Recovery Complete</p><

76、;p>　　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: </p

77、><p>　　Timeout Expired</p><p>　　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 Ser

78、ver error log file, the connections will no longer fail with a timeout error: </p><p>　　Recovery Complete</p><p>　　If the recovery process takes a long time, you may have to additionally trouble

79、shoot the recovery process.</p><p>　　Test different ways to connect to the instance of SQL Server</p><p>　　If you experience connectivity problems when you connect to the instance of SQL Server,

80、 you can use one or more of the following methods to work around the connectivity problem. </p><p>　　?Test the connectivity to the instance of SQL Server by using both SQL Server Authentication and Windows

81、authentication.</p><p>　　?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,

82、or the osql utility.</p><p>　　?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 us

83、ing 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 suc

84、cessful, named pipes connections succeed.</p><p>　　?Test the connectivity by using a different login account to help you determine if the problem is associated with a particular login account.</p>&l

85、t;p>　　?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.</p><p>　　?Try to connect to

86、the instance of SQL Server from the computer that is running SQL Server and from the client.</p><p>　　?If you are connecting from the computer that is running SQL Server, you can specify "." or &q

87、uot;(local)" (without the quotation marks) instead of the server name and then connect.</p><p>　　?Try to connect to the instance of SQL Server by using the IP address instead of the server name.</p&

88、gt;<p>　　?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)

89、.</p><p>　　Capture network monitor traces</p><p>　　If the connectivity problem is not resolved by the steps that are mentioned in "Test different ways to connect to the instance of SQL Serv

90、er 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-clust

91、ered computers that are running SQL Server for network tracing. </p><p><b>　　B2 中文譯文</b></p><p>　　如何解決 SQL Server 2000 中的連接問題</p><p>　　Chris Tull, Microsoft Help and Su

92、pport</p><p>　　這一篇文章能幫助你解決微軟 SQL 伺候器 2000 的連接性問題。這一篇文章包含你能拿幫助解決你的連接性問題的通常連接性問題和步驟的描述。</p><p>　　SQL Server的例證和客戶端申請之間的溝通的 SQL Server 2000 支持一些方法。如果你的客戶申請和SQL Server的例證在相同的計算機上住, Microsoft Windows

93、 處理之間的溝通 (IPC) 成份（像是當?shù)氐拿芑蛘弑环窒淼挠洃浻涗洠┯脕頊贤ā?然而, 當客戶端申請和SQL Server的例證在不同的計算機，網(wǎng)絡IPC（像是TCP/IP上住的時候或者命名管道）用來溝通。</p><p>　　SQL Sever 2000 使用網(wǎng)絡控件庫（一個DLL）與一個特別的網(wǎng)絡記錄溝通。 一雙相配網(wǎng)絡控件庫一定在客戶計算機和服務器計算機上是活躍的支援你想要使用的網(wǎng)絡記錄。 舉例來說，

94、如果你想要使一個客戶申請能夠與通過TCP/IP的一個 SQL Server的特定例證溝通, 客戶TCP/IP套接字網(wǎng)絡控件庫 (Dbnetlib.dll) 一定配置成在客戶計算機上對伺候器連接。 同樣地, 服務器TCP/IP套接字網(wǎng)絡控件庫 (Ssnetlib.dll) 一定在伺候器計算機上聽。 在這一個情節(jié)中, TCP/IP協(xié)議堆棧一定是裝置在客戶計算機和服務器計算機。</p><p>　　在你安裝SQL Se

95、rver 2000 之后，你能配置客戶端網(wǎng)絡的特性使用客戶端網(wǎng)絡公用程序的網(wǎng)絡庫屬性。你能配置服務器網(wǎng)絡的特性使用服務器網(wǎng)絡公用程序(Svrnetcn.exe)的網(wǎng)絡控件庫屬性。在安裝 SQL Server 安裝程序中的服務器工具期間，服務器的網(wǎng)絡庫也被同時安裝了。然而，一些服務器的網(wǎng)絡庫可能不是激活的。如此，SQL Server 2000 啟用并偵聽 TCP/IP、命名管道和共享內(nèi)存。因此，讓一個客戶端對一部服務器計算機連接，客戶端一

96、定使用一個客戶端網(wǎng)絡庫，該網(wǎng)絡庫匹配與SQL Server實例正在使用的服務器網(wǎng)絡庫之一。</p><p>　　對于關于SQL Server通訊部件和網(wǎng)絡庫的其它信息，請參見“SQL Server 在線參考書”中的下列主題： </p><p><b>　　?通信部件</b></p><p>　　?客戶端和服務器網(wǎng)絡庫</p>

97、<p><b>　　?管理客戶端</b></p><p><b>　　解決連接問題</b></p><p>　　在 SQL Server 2000 中大多數(shù)連接問題你可能會注意到的都是由 TCP/IP 的問題或 Windows 身份認證的問題引起，或者兩者共同組合引起。</p><p>　　重要說明：你開始解決

98、 SQL Server 2000 的連接問題之前，確定MSSQLServer 服務已在運行 SQL Server 的計算機上啟動。</p><p><b>　　驗證 DNS 設置</b></p><p>　　域名系統(tǒng) (DNS)的名稱解析過程被用于解決IP對SQL Server實例名稱。如果名稱解析程序不正確地工作，SQL服務器的實例不是可到達的，你可能接受到一條或多

99、條下列錯誤信息：</p><p>　　SQL Server does not exist or access denied</p><p>　　General Network Error</p><p>　　Cannot Generate SSPI Context</p><p>　　為了要確認名稱解析程序是解析正確的服務器，你能使用服務器的

100、服務器名字和IP地址ping服務器。為此，請遵從如下步驟操作：</p><p>　　1.單擊“開始”，然后單擊“運行”。</p><p>　　2.在“運行”對話框中，在“打開”框中鍵入 cmd，然后單擊“確定”。</p><p>　　3.在命令提示符下，運行下列命令：</p><p>　　ping <Server Name>

101、</p><p>　　記錄返回的 IP 地址。</p><p>　　4.在命令提示符下，運行下列命令（此處的 IP address 就是你在步驟 3 中記錄的 IP 地址）：</p><p>　　ping –a <IP address></p><p>　　確認指令跟正確的服務器名字解決。如果任一指定指令不成功、超時或者沒有返回

102、正確的數(shù)值在兩個指定的命令，那么DNS查找未能正常工作，或者因為其它的網(wǎng)絡問題引發(fā)問題。要查看當前DNS設定，在命令提示符下運行下列命令：</p><p>　　ipconfig /all</p><p>　　要解決此問題，可以在客戶端計算機上的 %systemroot%\system32\drivers\etc\hosts 文件中為服務器添加一個條目。要解決此問題，還可以使用命名管道網(wǎng)絡庫