Every 2-3 days, my Windows Server 2003 R2 Enterprise box which is hosting a .NET web app will start having an issue. The .NET app stops being able to connect to the SQL server with this error:
An error has occurred while
establishing a connection to the
server.(provider: Named Pipes Provider,
error: 40 – Could not open a
connection to SQL Server) (Microsoft
SQL Server, Error: 5)An error has occurred while
establishing a connection to the
server. 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: 40 – Could not
open a connection to SQL Server)
(Microsoft SQL Server, Error: 1326)
After a reboot of the server, everything works fine. I checked RAM, open connections on SQL server, etc, and nothing seems out of wack.
Any ideas?
Strangely I am seeing events like this mixed in the mass of SQL Connection error events that I posted above:
This instance of SQL Server has been
using a process id of 44552 since
7/6/2010 12:07:27 PM (local) 7/6/2010
4:07:27 PM (UTC).
But there is no SQL Server installed on this server?? Also after reboot there are many messages about SQL Server starting back up and stuff.
I take that back, there are processes running like MSSQLSERVER… but why? It's not installed.. don't see any way of removing it either.
Best Answer
That error is generic, and just means you can't connect to SQL. Is there anything else in the server event logs?
Just a stab in the dark, but if a reboot fixes the issue, then are your TEMPDBs filling the hard drive?