A connection was successfully established with the server, but then an error occurred during the login process.

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.)

A connection was successfully established with the server, but then an error occurred during the login process. - Article on SQLNetHub

If you get this error message, don’t worry. It is quite descriptive and even more, the solution to this issue is quite simple.

Read on, in order to learn how you can resolve the issue.

 

How to Resolve the Issue

There are 2 things you can try in order to overcome this problem. Therefore, there are two checks you need to perform, in order to take corrective actions.

 


Learn more tips like this! Get the Online Course!

Check our online course titled “Essential SQL Server Administration Tips” (special limited-time discount included in link).

Learn essential hands-on SQL Server Administration tips on SQL Server maintenance, security, performance, integration, error handling and more. Many live demonstrations and downloadable resources included!

Essential SQL Server Administration Tips - Online Course with Live Demonstrations and Hands-on Guides
Lifetime Access / Downloadable Resources and more!

Enroll Now with Discount!


First Check:

The first check involves ensuring that the maximum number of concurrent connections is set to 0. In order to check this, in SQL Server Management Studio (SSMS), right-click on instance, connections and check the value for the maximum number of concurrent connections option. If it is set to 0, it means unlimited.

 

Second Check:

The second check, involves ensuring 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]";

For example, in the case where you specified 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.

I hope you found this tip useful and you managed to resolve the issue.

 

Featured Online Courses:

 

Check our other related Data Access-related articles.

Check out our latest software releases!

Subscribe to our newsletter and stay up to date!

Check out Artemakis’s eBooks!

 

Rate this article: 1 Star2 Stars3 Stars4 Stars5 Stars (2 votes, average: 5.00 out of 5)

Loading...

Reference: SQLNetHub.com (https://www.sqlnethub.com)

© SQLNetHub

 

Troubleshooting: A connection was successfully established with the server, but then an error occurred during the login process. Click to Tweet