[Microsoft] [odbc SQL Server Driver] [dbnetlib] SQL server does not exist or access is denied)

[Microsoft] [odbc SQL Server Driver] [dbnetlib] SQL server does not exist or access is denied. Baidu After several hours of continuous search and analysis with sogou, I finally realized the cause.

Connect to the SQL database,
Ip_connstr = "driver = {SQL Server}; server = 127.0.0.1; database = database name; uid = sa; Pwd = password"

This is correct. Generally, no errors will occur.

"[Microsoft] [odbc SQL Server Driver] [dbnetlib] SQL server does not exist or access is denied"

The reason is that it can be searched from Baidu. Note the following:

In fact, it is very simple to put the server = 127.0.0.1 127.0.0.1
Change

Open your IIS and expand Internet Information Service
** (Local Computer)
** This is what you need. For example, if you are using webnet
Then you can change

Ip_connstr = "driver = {SQL Server}; server = webnet; database = database name; uid = sa; Pwd = password"

In this way, you can

In fact, I also found a solution in Baidu, which is just a lazy test,

As follows:
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

References: http://www.it-school.cn/html/Windows-SDK-API/200611/121149.html
Generally, the above address can solve the problem.

To prevent this, the page cannot be opened later: Copy

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) --> 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

After sharing my experience, it took a long time not only three or four hours, but finally solved the problem ......