Warning : Could not connect to the server.

SQL server connection issues A network-related or instance-specific error occurred while establishing a connection to SQL Server. provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server
Email It to Me Print this Page
Symptoms The Change Summary report from Netwirx Auditor contains the following warning:
“Could not connect to the <servername> server. A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)”
 
Cause There are several common causes of this issue:
  1. The wrong SQL server name is specified in the Managed Items of the corresponding Managed Object of Netwrix Auditor
  2. The SQL server is not configured to accept remote connections.
  3. TCP protocol is disabled in the SQL server configuration
Resolution SQL servers must be specified in Netwirx Auditor  as “Server_name\Instance_name”.
Example:
SQLMachine\SQLExpress

Default instance name is MSSQLSERVER and if SQL Server was configured as “default instance” while installing, there is no need to specify instance name, just server hostname.

A further tip is to specify the SQL Instance name exactly as it appears when making a connection with SQL Management Studio. If you do not know target instance name please ask your DB admin.

Note: Replace ‘Server_name’ with the SQL server machine name.
Replace ‘Instance_name’ with the SQL server instance name.

Also, make sure that remote connections are enabled
  1. Start SQL Management Studio
  2. Connect to the Database engine of the corresponding instance
  3. Right click the server and select Properties
  4. Go to Connections node and make sure the Allow remote connection to this server checkbox is enabled
 
And TCP is enabled for the server.
  1. Launch SQL Server Configuration
  2. Go to SQL Server Network Configuration > Protocols for the corresponding Instance
  3. Make sure TCP/IP is enabled. Enable if needed
 
Was this information helpful?