SQLserver2000 [Microsoft] [odbc SQL Server Driver] [DBNETLIB] SQL Server does not exist or access is denied

Source: Internet
Author: User
Tags sql server driver odbc sql server driver

Sqlserver2000, error when opening service manager: [Microsoft] [odbc SQL Server Driver] [dbnetlib] SQL server does not exist or access is denied"

 

 

[I]

(A machine acts as a server and a client, and the software connection appears:
[Dbnetlib] [connectionopen (connect ().] SQL server does not exist or access is denied.
There are several solutions to the problem from the Internet:
(A) 1: If you access the Internet independently, open port 21. enable port 1433 on the LAN.
2. Disable the firewall!
(B) Change sqllocalname = "(local)" of the database connection to an IP address. You can change (local) to 127.0.0.1 or an Internet IP address.
(C) Open the service, stop full-text retrieval and SQL Server services, enable SQL Server, and then enable full-text retrieval.
(D) Right-click SQL Server properties ==> the "ownership link:" allow cross-database ownership link "option must be checked (this operation requires restarting SQL Server ).

[II]

1. Ping is guaranteed first.

2. No error will be reported when telnet ip 1433 is written in dos

3. Use an ip address to connect to the Enterprise Manager:
Enterprise Manager --> right-click SQlserver group --> Create sqlserver registration --> next --> Write Remote Instance name (IP address, machine name) --> next --> select Sqlserver login --> next --> write login name and password (sa, pass) --> next --> complete

4. If not:
Sqlserver server --> Start Menu --> SQLserver --> server network utility --> enable WinSock Proxy --> proxy address: (sqlserver Server IP address) --> proxy port --> 1433 --> OK

5. If not:
Sqlserver client --> Start Menu --> SQLserver --> client network utility --> alias --> Add --> write alias such as "" --> "network library" select TCP/IP --> The server name is written to the remote ip address or Instance name --> OK

[III]

Select Microsoft SQL Servers> tool> Options> advanced> query timeout> change to 0.

Others tell me to add the hosts file under c: \ winnt \ system32 \ driver \ etc \
Ip computername is enough, and I can do it again. I have no idea how to change it,
Why? Why not sqlserver7.0? Why?
Yes.

The effect is equivalent to the following operations:

Sqlserver client --> Start Menu --> SQLserver --> client network utility --> alias --> Add --> write alias such as "" --> "network library" select TCP/IP --> The server name is written to the remote ip address or Instance name --> OK

[IV]

Abstract: This article focuses on how to open port 1433 after installing SQL Sever2000 in Win2003.

It has been used for several years for Windows2003 and SQL Server2000, but this problem is the first time. I recently encountered a problem when debugging a JSP + SQL2000WEB program. I installed SQL Server2000 ON THE Win2003 Simplified Chinese server version. It is installed by default. Everything works normally, but Tomcat runs normally after the installation is complete, the JSP program cannot connect to the SQL2000 database. Check the port. port 1433 is not open, not to mention remote connection.

The general analysis is as follows:

1. the SQL server service is not started;

Check the Service Startup and restart the service.

2. modified the port number;

Open the network utility and check that the enabled Protocol has the TCP/IP protocol. Check that the port number is 1433.

3. The client utility has been changed;

Open the client utility, check that the protocol port is normal, and re-create an alias.

4. Installation Problems;

It is suspected that there is a problem with the installation steps. Uninstall and reinstall the instance. All items are default and the fault persists.

5. Installation version issues;

Check the installation disc, which has been tested for a long time and should not cause any problems.

6. System Problems;

I can't see any other problems. Is it a system problem? However, reinstalling the system is too troublesome. You should first try other methods to see if the problem can be found. Checking System logs should be a good habit. After carefully reviewing the reinstallation logs, you can find the following content: the Microsoft SQL Server 2000 or Microsoft SQL Server 2000 Desktop Engine (also known as MSDE) that you run and
Microsoft Windows Server 2003 has known security vulnerabilities. To reduce computer attacks by some viruses, Microsoft SQL Server 2000, MSDE or both of the TCP/IP and UDP network ports are disabled. To enable these ports, you must start from the latest service package of the slave, or Microsoft SQL Server 2000 or MSDE.

For more information, see help and support in go.microsoft.com/fwlink/events.asp
Finally, I found the problem. It turned out to be a small security consideration for Windows. So why have we never met anyone before? The person who used to be safe,
After installing SQL, You must fix the vulnerability before using it. Therefore, you have never paid attention to this issue. It seems that what kind of habits will have some drawbacks!
Now that you find the problem is simple, immediately to the Microsoft Website: http://www.microsoft.com/downloads/details.aspx? Displaylang = zh-cn & FamilyID = 8e2dfc8d-c20e-4446-99a9-b7f0109f8bc5

Download "database components (download file: SQL2000-KB884525-SP4-x86.EXE)" for SP4 )"
After installing SQL Server SP4, check the address bar of the browser to test that www.ITstudy.cn is normal.

Appendix:
Remote connection to SQL Server 2000 Server Solution

Solution steps:
Check whether the IP address of the ping server can be pinged.
This is to see whether the physical connection to the remote SQL Server 2000 Server exists. If not, check the network and view the configuration. Of course
Make sure that the IP address of the Remote SQL Server 2000 Server is correctly spelled.
2. Enter the IP port of the Telnet server in DOS or command line to check whether the port can be connected.
For example, Telnet 202.114.100.100 1433
The port value is usually 1433, because 1433 is the default listening port of SQL Server 2000 for TCP/IP. If you have any questions, this step will usually be asked.
Question. The common prompt is "... Unable to open the connection, connection failed ".
If there is a problem with this step, check the following options.
1. Check whether the remote server has started the SQL Server 2000 Service. If not, start.
2. Check whether the TCP/IP protocol is enabled on the server. This Protocol is required for remote connection (over the Internet. The check method is: on the server
Choose Start> program> Microsoft SQL Server> server network utility to check whether the enabled Protocol has the TCP/IP protocol. If
No, enable it.
3. Check whether the server's TCP/IP Port is configured as port 1433. View the TCP/IP in the enabled protocol in the server network utility
Ensure that the default port is 1433, and the check box of the hidden server is not checked.
In fact, it is okay if the default port is modified, but when the client performs a telnet test, the server port number must be configured with the server
The port number must be the same. If the "Hide server" check box is selected, the client cannot view the server by enumerating the server,
But does not affect the connection, but the default port of TCP/IP protocol is implicitly changed to 2433.
Changes.
4 if the server operating system has been patched with sp2, you must configure windows Firewall to open port 1433 to it.
You can directly turn off the windows Firewall (Other firewalls are also the best ).
5. Check whether the server listens on port 1433. If the server does not listen on port 1433 of the tcp connection, it cannot be connected. The check method is in
Enter netstat-a-n or netstat-an in the dos or command line of the server to check whether tcp 127.0.0.1 is similar
1433 listening. If not, you usually need to patch SQL server 2000 with at least sp3. In fact, start the query on the server side
Analyzer, enter select @ version to execute and you will see the version number. All Versions earlier than 8.0.2039 must be patched.
If there is no problem above, then you can perform the telnet server IP 1433 test. The screen will flash and the cursor will not stop flashing in the upper left corner. Gong
Hi, you can now connect to the Enterprise Manager or query analyzer.

3. Check client settings
Program> Microsoft SQL Server> client network tools. Make sure that the client TCP/IP protocol is the same as in the server network utility.
Enabled, and the default port is 1433 (or other ports, consistent with the server side ).

4. Test the connection in the Enterprise Manager or query Analyzer
Enterprise Manager-> right-click sqlserver group-> Create sqlserver registration-> next-> Write Remote IP-> next-> select sqlserver login-> next
Step-> write the login name and password (SA, password)-> next-> complete
Query analyzer-> file-> connection-> Write Remote IP-> write login name and password (SA, password)-> OK
It is usually recommended to do this in the query analyzer, because by default, the timeout setting for registering another SQL server through the Enterprise Manager is 4 seconds, and the query
The analyzer is 15 seconds.
Modify the default connection timeout method:
Enterprise Manager-> Tools-> options-> In the displayed "SQL Server Enterprise Manager properties" window, click the "advanced" tab-> connection settings-> log on
Enter a large number in the box after the recording timeout (seconds)
Query analyzer-> tool-> Option-> connection-> enter a large number in the box after logon timeout (seconds)
Generally, you can connect to IOT platform. If an error is prompted, proceed to the next step.
Five errors are usually caused by SQL Server's "Windows only" authentication method, so you cannot use SQL Server's
Log on to the Account (such as SA) to connect. The solution is as follows:
1. Use the enterprise manager on the server side and select "use Windows Authentication" to connect to SQL Server.
2. Expand "SQL Server group", right-click the name of the SQL Server server, select "properties", and then select the "Security" tab.
3. Under "authentication", select "SQL Server and Windows ".
4. Restart the SQL Server service. (In DoS or command line, net stop MSSQLServer to stop the service, Net start
MSSQLServer is also a quick way to start the service ).

Note: When connecting to the local server, the named pipe protocol is usually used (you can see in the server network utility that the enabled protocol has this)
The default port is 445. Therefore, local connectivity cannot be explained. connecting to a remote server is a completely different protocol ).

 

Related Article

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.