Send Knowledge Base Article
The article has been sent to your inbox successfully.
We never share your data
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
KB1488 | Last review: Sep 27, 2017 | Netwrix Auditor for SQL Server | All versions
|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:
|Resolution||SQL servers must be specified in Netwirx Auditor as “Server_name\Instance_name”.
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
And TCP is enabled for the server.
Was this information helpful?