SQL Server Error : 11001, Severity: 16. Non-NULL value successfully returned.

SQL Server Error : 11001 Details

SQL Server Error: 11001
Severity: 16
Event Logged or not: No
Description:
Non-NULL value successfully returned.
Severity 16 Description:
Indicates general errors that can be corrected by the user.

When the SQL Server cannot be discovered on the network, error 11001 occurs.

This occurs when the IP address is not reachable, or when the TCP port number is either not open or incorrect, or is blocked by a firewall.

What causes SQL server error 11001?

Let’s have a look at what’s causing this problem.

1. When the SQL Server client is unable to connect to the server, this error occurs. This can happen if the client is unable to resolve the server’s name or if the server’s name is wrong.

2. If we want to connect to a SQL server from outside of our local area network, we must need one or more routers and at least one proxy/firewall. The Firewall and/or Proxy may prevent SQL Server from being accessed from a remote location.

 

Solution:

On the client, enter the correct server name so that you may resolve the server name from the client. We also recommend using the ping programme in the Windows operating system to examine TCP/IP name resolution.

Also, double-check that you’re using the right instance name. When connecting to a default instance, server-name is the most accurate representation of the instance name; however, when connecting to a named instance, such as sqlexpress, we recommend using the instance name as server or domain-name/instance-name.

In the instance-name field, type the name of the SQL Server instance.

Also, make sure the SQL Server is connected to the network. To get a list of SQL Servers installed on your computer, type SQLCMD -L.

On the ‘Server’ executing the MSDE Database, we recommend running netsvrcn.exe as an Administrator from the command prompt.

TCP/IP and Named Pipes protocols must be enabled.

Examine the protocols and ports for TCP/IP and Named Pipes. To begin, go to SQL Server Configuration Manager and look at the SQL Server Network Configuration protocols. The TCP/IP protocol and named pipes must both be enabled.

Right-click and select properties for the TCP/IP protocol, then check the TCP/IP communication port. 1433 is the default port. If necessary, this can be altered for security reasons.

Lastly try Restart the instance of SQL Server.

Alternate Solutions if above does not work:

Check if not Excluded the ports SQL Server normally listens on from the firewall using ‘Windows Firewall Advanced Security’ for both inbound and outbound rules:

UDP port 1434 for sql browser

TCP port 1433 for sql service

The SQL Server Browser service has to be active and running. You may verify the status of the browser service using SQL Server Configuration Manager or the services

 

SQL Server Error Code and solution summary

SQL Server Error: 11001
Severity: 16
Event Logged or not: No
Description:
Non-NULL value successfully returned.

Solutions would be

• Enable TCP and NAMED PIPES protocol
• Restart SQL Server instance
• Exclude the ports SQL Server normally listens on, from the firewall using ‘Windows Firewall Advanced Security’ for both in-bound and out-bound rules:
  • 1433 TCP port
  • 1434 UDP port

Test the ODBC connection from a client machine.