A connection was successfully established with the server, but then an error occurred during the login process. (provider: Shared Memory Provider, error: 0 – No process is on the other end of the pipe.) (.Net SqlClient Data Provider)

We faced this issue on one of our servers which was due for a restart.

Many blogs suggested that the Named Pipes be enabled, and that the order of the named Pipes vis-a-vis TCP/Ip be changed.

When i checked the errorlog, it showed :

SQL Server is terminating because of a system shutdown. This is an informational message only. No user action is required.

Service Broker manager has shut down.

SQL Trace was stopped due to server shutdown. Trace ID = ‘1’. This is an informational message only; no user action is required.

The SQL Server Network Interface library could not deregister the Service Principal Name (SPN) for the SQL Server service. Error: 0x45b, state: 4. Administrator should deregister this SPN manually to avoid client authentication errors.

Some more Googling led to a possible issue with an incorrect shutdown of the services. The “SPN” is related to Active Directory, and in some cases with Kerberos.

The server was restarted and the issue was solved in this case. Note: the other methods like Named Pipes enabling did not help here.

Some useful references :





This entry was posted in Uncategorized. Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s