Troubleshooting of SQL Server nonexistent or access denied

SQL Server does not exist or access failure troubleshooting. This article provides a solution process and ideas. 1. I raised the question of a CS-mode invoicing system that an enterprise normally uses. When a new client connects to the database server (installing SQLServer2000), a fault message is displayed-"[DBNETLIB] [ConnectionOpen (

SQL Server does not exist or access denied troubleshooting. This article provides a solution process and ideas. 1. I raised the question of a set of C/S Mode invoicing systems normally used by an enterprise. A Newly Added client is connecting to the database Server (installing SQL Server 2000) when a fault occurs, the system prompts "[DBNETLIB] [ConnectionOpen (

SQL Server does notExistOrRejectAccessFaultOfExcludeThis article provides a solution process and ideas.

1. Question proposal

An enterprise uses a C/S-mode invoicing system. A new client appears when it connects to the database Server (installing SQL Server 2000 ).FaultPrompt-"[DBNETLIB] [ConnectionOpen (connect ().] SQL Server does notExistOrRejectAccess", The system cannot log on, and other clients work normally.

2. Solution Process and ideas

For suchFaultNote:FaultThe solution is to check the firewall and port 1433 settings on the client. AppearsFaultThe client is installed with the Kaspersky 6.0 Internet security package. After adding port 1433 to Kaspersky's "Network Settings ",FaultThe prompt is changed to "general network error (recv ()", resulting in the followingFaultThere are many reasons for prompt information, which is difficult to determine. For this reason, clients andFaultIn the SQL SERVER Client settings of the client, it is found that the working client uses the "Named pipes" protocol as the priority, and uses the SERVER name to connect to the database SERVER.FaultThe client uses "TCP/IP" as the priority-enabled protocol and uses the ip address of the server to connect to the database server. The default port is 1433.Fault"Named pipes" is set as the priority-enabled protocol on the client. If you use the server name to connect to the database server, the connection is normal and can run normally. Determined accordinglyFaultThis is related to the TCP/IP protocol. Run netstat on the SERVER (Windows 2000 Server SP4 + SQL SERVER 2000, with the IP address 10.140.90.249? Command, the result is as follows:

Active Connections

Proto Local Address Foreign Address State

......

TCP 10.140.90.249: 80 10.140.90.52: 2519 TIME_WAIT

TCP 10.140.90.249: 80 10.140.90.52: 2523 TIME_WAIT

TCP 10.140.90.249: 80 10.140.90.52: 2525 TIME_WAIT

TCP 10.140.90.249: 80 10.140.90.52: 2527 TIME_WAIT

TCP 10.140.9 0.249: 80 10.140.90.52: 2529 ESTABLISHED

TCP 10.140.9 0.249: 80 10.140.90.52: 2531 ESTABLISHED

TCP 10.140.90.249: 139 0.0.0.0: 0 LISTENING

TCP 10.140.90.249: 1051 10.140.90.249: 2161 ESTABLISHED

TCP 10.140.90.249: 2161 10.140.90.249: 1051 ESTABLISHED

......

From the above content, we can see that the TCP/IP protocol on the Server does not enable listening to port 1433. Search for information about SQL Server and port 1433 on the Internet, it is found that port 7.0 is enabled by default for SQL Server 1433, and port 2000 is disabled by default before SP4. Ask the Administrator to install the SP4 patch for SQL Server 1433 on the Server, because the SQL Server 2000 version is not displayed in "about", go to "query analyzer" and check the SQL Server 2000 version. In "query analyzer", run:

SELECT @ VERSION

The returned value is "8.00.194 RTM", which is the original version of SQL Server 2000. Ask the Administrator further and learn that the SQL Server service on the Server was not stopped when SP4 was installed, SQL Server 2000 SP4 explicitly requires that the SQL Server service and all client programs on the Server be stopped before installation. Therefore, it is determined that SQL Server 2000 SP4 on the Server is not successfully installed. The relationship between SQL Server 2000 and version can be found online.

After you reinstall SQL Server 2000 SP4 on the Server, the following message is displayed: "A suspended file has been created during the previous installation of the program. You must restart the computer before running the program ." This indicates that the previous SP4 was not successfully installed and the server was restarted. The prompt continues. Start the Registry Editor and go to the HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Control \ Session Manager branch to delete the PendingFileRenameOperations project, then, SQL Server 2000 SP4 is successfully re-installed. Then execute netstat on the server? An command, port 1433 is in the column and is in the "LISTENING" status.FaultThe client is set to the TCP/IP connection mode, the program is started, the connection is successfully completed, and the error message is no longer displayed.

3 conclusion

Nowadays, software systems are becoming more and more complex, and more systems are involved,ExcludeFaultCannot beFaultConfused by the surface of the phenomenon, we need to analyze it step by stepExcludeGo to forums and official websites on software systems to learn about related products, especially patch information.ExcludeFaultYou can get twice the result with less detours.

ThisFaultIt also appears in the standalone status. Generally, the SQL server Client sets TCP/IP as the priority-enabled protocol and uses the IP address to connect to SQL SERVER, when there is a problem with the physical connection of the network cable or the IP address settings.