Соединение не выполнено sqlstate 01000 ошибка sql server 11001

We have an application that uses MSDE as its ‘Back-end’. 
It has been working fine for years.  We have however had to recently re-build the Operating System on our own Server that it was running on. 

Original O/S Environment

We used Windows Server 2008 r2, using
Hyper-V to run Windows Server 2003 so that we can use
MSDE to run our application. 

We do not want to change to later versions of SQL Server Express as they no-longer support Replication.

NEW O/S Environment

When we re-built the Server we went for Windows Server 2008 r2, using
Hyper-V to run Windows 7 Enterprise so that we can use
MSDE to run our application. 

We have used this setup many times before and know that MSDE runs quite happily under Windows 7. 

Servers have been renamed

The real Windows Server 2008 r2 machine used to be called FILESERVER. 
It is now called FILE-SERVER.

The virtual machine running our application was originally called GEMSERVER. 
It is now called GEM-SERVER. 

What’s happening on the Server

The application is running fine.  We can access the underlying MDSE Database with SQL Server 2005 Management Studio Express without problem.
 We can build a test ODBC Data Source and connect to the ‘SQL Server’ Database, again without problems. 

What’s happening on the Client PC

The application does not connect.  I get:

     An error occurred while connecting.
     [DBNETLIB]ConnectionOpen (Connect())SQL Server does not exist
     or access denied.

When I build a ODBC Data Source to test the Connection I get:

Microsoft SQL Server Login

Connection failed:
     SQLState: ‘01000’
     SQL Server Error: 11001
     [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen
     (Connect()).
     Connection failed:
     SQLState: ‘08001’
     SQL Server Error: 6
     [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]Specified SQL
     server not found

I can Ping GEM-SERVER from the Client PC without problems. 

I have disabled Firewalls an Anti-Virus Software on both the GEM-SERVER and the Client PC – to no avail. 

I’ve tried connecting with:

• Named Pipes,
• TCP/IP,
• IP Address of GEM-SERVER – 192.168.16.122,
• Using Specific Port 1433 in connection.

NONE of it worked.  L

ANYBODY any ideas what to try next?

Ошибка Microsoft SQL Server: 53 или ошибка Microsoft SQL Server: 11001 или ошибка SQL Server 53 и 40. Ошибки SQL server 53 и 17

Подробности ошибки:

Не удается подключиться к ошибке SQL Server, которая может быть номером ошибки: 11001 или номером ошибки: 53, серьезностью: 20, состоянием: 0 или ошибкой SQL Server 53 и 40. Ошибки SQL server 53 и 17

(provider: TCP Provider, error: 0 — No such host is known.) (Microsoft SQL Server, Error: 11001)

причины ошибок:

Эта ошибка возникает, когда SQL Server не может быть найден в Сети, что означает либо IP-адрес недоступен, либо номер TCP-порта либо не открыт, либо не является правильным номером порта, либо заблокирован брандмауэром и т. д

Решение:

Приведенные ниже шаги помогут устранить эти проблемы

1.Проверьте, можете ли вы пинговать сервер
2.Проверьте, открыт ли брандмауэр для подключения
3.Проверьте, работает ли служба SQL Server и если именованный экземпляр, то служба браузера
4.Проверьте, включен ли протокол TCP / IP в диспетчере конфигурации SQL Server
5.Проверьте, установлен ли в свойствах SQL Server параметр “Разрешить удаленные подключения” на уровне экземпляра

Дополнительная информация ниже:

Для экземпляра по умолчанию используется порт TCP / IP 1433, но это может быть изменено вручную. Поэтому пожалуйста проверьте TCP IP порт все еще находится на уровне по умолчанию 1433

Щелкните правой кнопкой мыши на TCP / IP и выберите пункт Свойства.
Прокрутите вниз до IPAll.
Убедитесь, что динамические порты TCP пусты.
Убедитесь, что TCP-порт установлен на 1433.

Для именованного экземпляра установки SQL Server должна быть включена и запущена служба браузера, которая определяет номер порта SQL Server. Служба SQL browser работает на порту UDP 1434 и это должно быть разрешено через ваш брандмауэр

Пожалуйста, попробуйте перезагрузить ваш сервер / компьютер, чтобы убедиться, что он будет работать.

SQL server error 11001 occurs when the SQL Server can’t be found on Network.

This happens if the IP address is not reachable or the TCP port number is either not open or is not the correct port number or is blocked by a firewall

Here at Bobcares, we have seen several such SQL related issues as part of our Server Management Services for web hosts and online service providers.

Today we’ll take a look at the cause for this error and how to fix it.

Why does SQL server error 11001 occur

Now let’s look into what causes this error to occur

1. This error mainly occurs when the SQL Server client can’t connect to the server. This may happen when the client cannot resolve the name of the server or the name of the server is incorrect.

2. If we want to access a SQL server beyond a local area network then the connection must pass through one or more routers and at least one Proxy/Firewall. Sometimes, the Firewall and/or Proxy may not allow SQL Server to be accessed from an external location.

For instance, the error appears as below.

How we resolve SQL server error 11001

Here are the steps that our Support Engineers provide to our customers to follow to fix this error.

1. Enter the correct server name on the client such that you can resolve the name of the server from the client. Also, to check the TCP/IP name resolution, we suggest using the ping command in the Windows operating system.

Also, make sure you are using the correct instance name. When connecting to a default instance, machinename is the best representative for the instance name and when connecting to a named instance such as sqlexpress, we suggest specifying the instancename as follows: machinenameinstancename.

Here, enter the SQL Server instance name for instancename.

Also, check that the SQL Server is in the network. Use the command SQLCMD -L to retrieve the list of SQL Servers installed in the network.

NOTE: This will only return SQL Servers if the SQL Server Browser service is running.

2. We suggest running netsvrcn.exe using command prompt as an Administrator on the ‘Server’ running the MSDE Database.

3. Enable TCP/IP and Named Pipes protocol

Check the TCP/IP and Named Pipes protocols and port. First, open SQL Server Configuration Manager and check the SQL Server Network Configuration protocols. Named Pipes and TCP/IP protocol must be enabled.

For the TCP/IP protocol, right-click and select properties and then check the TCP/IP communication port. The default port is 1433. However, this can be changed for security purposes if needed.

4. Restart the SQL Server instance.

5. From the firewall using ‘Windows Firewall Advanced Security’, exclude the ports SQL Server normally listens on, for both inbound and outbound rules:

1433 TCP port
1434 UDP port

6. SQL Server Browser service must be running. You can check the browser service status using either SQL Server Configuration Manager or the SC command as follows.

sc query sqlbrowser

[Need any further assistance in fixing SQL errors? – We’re available 24*7]

Conclusion

In short, this error occurs when the SQL Server can’t be found on Network. Today, we saw the resolution to this SQL error.

var google_conversion_label = «owonCMyG5nEQ0aD71QM»;

We have an application that uses MSDE as its ‘Back-end’. 
It has been working fine for years.  We have however had to recently re-build the Operating System on our own Server that it was running on. 

Original O/S Environment

We used Windows Server 2008 r2, using
Hyper-V to run Windows Server 2003 so that we can use
MSDE to run our application. 

We do not want to change to later versions of SQL Server Express as they no-longer support Replication.

NEW O/S Environment

When we re-built the Server we went for Windows Server 2008 r2, using
Hyper-V to run Windows 7 Enterprise so that we can use
MSDE to run our application. 

We have used this setup many times before and know that MSDE runs quite happily under Windows 7. 

Servers have been renamed

The real Windows Server 2008 r2 machine used to be called FILESERVER. 
It is now called FILE-SERVER.

The virtual machine running our application was originally called GEMSERVER. 
It is now called GEM-SERVER. 

What’s happening on the Server

The application is running fine.  We can access the underlying MDSE Database with SQL Server 2005 Management Studio Express without problem.
 We can build a test ODBC Data Source and connect to the ‘SQL Server’ Database, again without problems. 

What’s happening on the Client PC

The application does not connect.  I get:

     An error occurred while connecting.
     [DBNETLIB]ConnectionOpen (Connect())SQL Server does not exist
     or access denied.

When I build a ODBC Data Source to test the Connection I get:

Microsoft SQL Server Login

Connection failed:
     SQLState: ‘01000’
     SQL Server Error: 11001
     [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen
     (Connect()).
     Connection failed:
     SQLState: ‘08001’
     SQL Server Error: 6
     [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]Specified SQL
     server not found

I can Ping GEM-SERVER from the Client PC without problems. 

I have disabled Firewalls an Anti-Virus Software on both the GEM-SERVER and the Client PC – to no avail. 

I’ve tried connecting with:

• Named Pipes,
• TCP/IP,
• IP Address of GEM-SERVER – 192.168.16.122,
• Using Specific Port 1433 in connection.

NONE of it worked.  L

ANYBODY any ideas what to try next?

We have an application that uses MSDE as its ‘Back-end’. 
It has been working fine for years.  We have however had to recently re-build the Operating System on our own Server that it was running on. 

Original O/S Environment

We used Windows Server 2008 r2, using
Hyper-V to run Windows Server 2003 so that we can use
MSDE to run our application. 

We do not want to change to later versions of SQL Server Express as they no-longer support Replication.

NEW O/S Environment

When we re-built the Server we went for Windows Server 2008 r2, using
Hyper-V to run Windows 7 Enterprise so that we can use
MSDE to run our application. 

We have used this setup many times before and know that MSDE runs quite happily under Windows 7. 

Servers have been renamed

The real Windows Server 2008 r2 machine used to be called FILESERVER. 
It is now called FILE-SERVER.

The virtual machine running our application was originally called GEMSERVER. 
It is now called GEM-SERVER. 

What’s happening on the Server

The application is running fine.  We can access the underlying MDSE Database with SQL Server 2005 Management Studio Express without problem.
 We can build a test ODBC Data Source and connect to the ‘SQL Server’ Database, again without problems. 

What’s happening on the Client PC

The application does not connect.  I get:

     An error occurred while connecting.
     [DBNETLIB]ConnectionOpen (Connect())SQL Server does not exist
     or access denied.

When I build a ODBC Data Source to test the Connection I get:

Microsoft SQL Server Login

Connection failed:
     SQLState: ‘01000’
     SQL Server Error: 11001
     [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen
     (Connect()).
     Connection failed:
     SQLState: ‘08001’
     SQL Server Error: 6
     [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]Specified SQL
     server not found

I can Ping GEM-SERVER from the Client PC without problems. 

I have disabled Firewalls an Anti-Virus Software on both the GEM-SERVER and the Client PC – to no avail. 

I’ve tried connecting with:

• Named Pipes,
• TCP/IP,
• IP Address of GEM-SERVER – 192.168.16.122,
• Using Specific Port 1433 in connection.

NONE of it worked.  L

ANYBODY any ideas what to try next?

Hello,

I’m having some issues connecting to our SQL database over TCP/IP. We have an Access database that we use to run queries on a SQL database hosted on our server. We are using SQL Server 2008 R2.

When setting up the User DSN in ODBC Administrator these are the settings being used:
Name: Name
Description: Description
Server: ServerDatabase
Using SQL Authentication
Client Configuration Settings are set to connect via TCP/IP
Connect to SQL Server to obtain default settings for the additional configuration options is checked.
Login ID: Username
Password: Password

We are using SQL authentication because the user is not connected to the domain. TCP/IP has been enabled from within SQL Server Configuration Manager and the Client Configuration. Firewalls between the computer and server have been disabled during testing with no luck.

I’ve tried searching Google but I have been unable to find a solution that works for us.

I appreciate your help!

Edit: Here is the full error message

Connection failed:
SQLState: ‘01000’
SQL Server Error: 11001
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen
(Connect()).
Connection failed:
SQLState: ‘08001’
SQL Server Error: 6
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]Specified SQL
server not found.

If the server name and credentials are correct, maybe you were using the wrong driver?…

In my case I used the wrong odbcad32.exe to connect to a MySQL server via a 32-bit driver. The confusing thing is, that the 64-bit odbcad32.exe shows other 32-bit MySQL datasources. After I clicked ‘Add’, two SQL driver entries showed up (I have two MySQL driver versions installed) and it took me a minute to realize that these are just preinstalled MS SQL drivers after it returned the error in the question.

If you need a 32-bit ODBC connection, make sure to use C:windowsSysWoW64odbcad32.exe — another everlasting source of confusion, if you don’t know that on a 64-bit Windows the 32-bit binaries are located in SysWoW64 and the 64-bit ones are in System32.

After the ODBC Administration Tool is no longer available from the Computer Management GUI in Windows 10/11, I suspect that this problem might have become more common in recent years, when people fall for the 64-bit version, using Windows key + ‘R’ and just type odbcad32.exe even if they want to establish a 32-bit driver connection for a legacy ODBC-using application.