March 8, 2014 at 11:24 am
We have been receiving many of these lately. Sql Server 2008.
(provider: TCP Provider, error: 0 - The specified network name is no longer available.)
When it happens we have used sp_who to see if there were any connections from the web server and are not seeing more than a couple. I have saw that one of the possible causes can be connections not closed. We are not seeing any large numbers of connections. We have also run sql against sysprocesses.
SELECT
DB_NAME(dbid) as DBName,
COUNT(dbid) as NumberOfConnections,
loginame as LoginName
FROM
sys.sysprocesses
WHERE
dbid > 0
GROUP BY
dbid, loginame
There is a close connection in every finally statement.
Same thing not seeing more than a few connections (less than 8). When the error happens every sql command fails. We have tried code to run through the connection pool and close all the connections that doesn't seem to work either. If I close the application pool in IIS for a period of time it will clear up. If we just restart IIS or the pool the error persists. Any ideas on where else we can look to try to resolve this?
Our setup for Sql Server is defaults mostly.
March 9, 2014 at 6:45 am
Did you check it from network point of view ?. I think the server had gone out of network, may be.
March 9, 2014 at 10:52 am
When this happens we can ping the DB server from the same box getting the errors through IIS. We can execute a DB call external to IIS. We just can't make db calls within IIS. We put a call to SqlConnection.ClearAllPools() in based on some reading we have done but that does not seem to have an affect on the error.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply