Could not open a connection to SQL server when launching SmartView internal

Published: Mar 28, 2017
Post Author Written by David Youngquist

When launching SmartView internal, receiving an error that says “A network-related or instance-specific error occurred while establishing a connection to the 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)”.

This typically means that the SQL server name does not match what is found in SQL.  This could happen if you restore one SQL server on top of another SQL server or if you rename the machine after SQL has been previously installed.  

To determine if this is the issue, go back into SQL management studio and look at the name of the SQL server in the “Object Explorer” window.  Then create a new query and type the following command and run the query.


If the name returned is different than the name displayed in the Object Explorer, that is what is causing the connection issue. If this is the case you need to rename the server.  For information on renaming your SQL server use this article from Microsoft.  Rename a Computer that Hosts a Stand-Alone Instance of SQL Server

Feeling stuck? Get the support and guidance you need to help you power through any data challenge

We're on your integration team. Connect with our people and let us know how we can help you.