-
Title
Named Pipes Provider, error: 0 - No process is on the other end. -
Description
Customer reports seeing errors in the event log as described below:
An error occurred running a SQL statement. Dumping the SqlCommand.
The Exception message was: [A connection was successfully established with the server, but then an error occurred during the pre-login handshake. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 0 - No process is on the other end of the pipe.)] -
Cause
This issue happens when the Named Pipes Protocol is in the stack, but is disabled in the protocols list in SQL 2005.
-
Resolution
Enable the Named Pipes Protocol in SQL 2005:
- Open SQL 2005 Management Studio
- Go to SQL Server setup
- Change network support
- Select network protocol
- Enable
- Restart the SQL Server Service
- Restart all Archive Manager Services
The error should now be resolved.