When you try to connect to a SQL Server database from a client application, under certain circumstances, you might get the below error message:
A connection was successfully established with the server, but then an error occurred during the login process. (provider: Named Pipes Provider, error: 0 – No process is on the other end of the pipe.)
In order to -possibly- overcome this problem you can perform the below two checks:
Ensure that the maximum number of concurrent connections is set to 0 (in SSMS right-click on instance –> connections –> maximum number of concurrent connections), which means unlimited.
Ensure that in your connection string, in the client application, along with the rest of the settings, the database name is correct:
string connString=”Server=[SERVER_NAME]; Database=[DATABASE_NAME]; User ID = [USER_NAME]; Password=[PASSWORD]”;
If you specify a database that does not exist, even though the connection to the SQL Server instance will be established, the provider will not be able to find the database thus resulting to the above error message.
Hope this helps!
Reference: The SQL Server and .NET Hub (http://www.sqlnethub.com)
What are your views on the subject? Have something to share? Feel free to leave your comment!
Rate this article:
Recommended eBooks on SQL Server: