Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Networkname no longer available message. Expand / Collapse
Author
Message
Posted Saturday, March 8, 2014 11:24 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Thursday, March 13, 2014 8:46 AM
Points: 2, Visits: 5
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.
Post #1548980
Posted Sunday, March 9, 2014 6:45 AM
SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Monday, September 15, 2014 1:13 AM
Points: 1,535, Visits: 2,577
Did you check it from network point of view ?. I think the server had gone out of network, may be.
Post #1549051
Posted Sunday, March 9, 2014 10:52 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Thursday, March 13, 2014 8:46 AM
Points: 2, Visits: 5
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.
Post #1549063
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse