After some network maintenance over the weekend, we had some problems with our development server, which led us to restart it. During the reboot, some updates were installed, which may or may not be a factor. Since then, we have been unable to connect to SQL Server 2005, even locally through Management Studio. Depending on the protocol used to attempt the connection, we get one of the following two errors:
- When you try to connect to an instance using the named pipes protocol or the shared memory protocol, the following error message appears:
There is no process at the other end of the pipe.
- When you try to connect to an instance using TCP / IP, the following error message appears:
An existing connection was forcibly closed by the remote host.
All of the above protocols are enabled, and all SQL services are running successfully (except for the SQL Server agent, which also cannot connect to SQL Server). We also checked the Surface Configuration tool to make sure it accepts connections.
This is not a certificate issue (as shown online) since we do not use encrypted connections.
Any suggestions? Otherwise, we will probably resort to a complete reinstall.
** UPDATE **
Further hints:
- We can connect to Integration Services, but nothing else
- We can connect to an instance of SQL Server Embedded Edition running on the same server
dev