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

SQLServer Error: 10054 Communication link failure [SQLSTATE 08S01] Expand / Collapse
Author
Message
Posted Sunday, December 2, 2007 10:39 PM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Thursday, March 31, 2011 7:40 AM
Points: 11, Visits: 90
Hi All,

I'm getting this error in the SQL Server Agent Error Log. What could be the reason for this issue?
Please help me to sort out this issue.

SQL Server 2005 with SP1.

Date,Source,Severity,Message
12/01/2007 01:30:00,,Error,[382] Logon to server failed (ConnUpdateJobActivity_NextScheduledRunDate)
12/01/2007 01:30:00,,Error,[165] ODBC Error: 0 this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. [SQLSTATE 08001]
12/01/2007 01:30:00,,Error,[298] SQLServer Error: 10054 Communication link failure [SQLSTATE 08S01]
12/01/2007 01:30:00,,Error,[298] SQLServer Error: 10054 TCP Provider: An existing connection was forcibly closed by the remote host. [SQLSTATE 08S01]


Regards,
Sravan
Post #428583
Posted Tuesday, December 4, 2007 4:11 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Wednesday, September 24, 2014 8:54 AM
Points: 5,579, Visits: 6,363
We get similar error messages at random during the day. We're currently troubleshooting, but our best guess right now is network error. Also, we've gotten that error when we had a bad HBA card on the SAN.

It's time to involve your network & server teams. Have them put a sniffer on the server to see how packages are going in and out. Also, have them check the NICs, HBAs and cable connections to your box. But you might have to define a time frame for the sniffer, so log what times of the day you're getting this error and what jobs / queries are running when it happens.

Oh, and don't forget to check your SQL Server Surface Area Configuration to make sure you have remote logins enabled.


Brandie Tarvin, MCITP Database Administrator

Webpage: http://www.BrandieTarvin.net
LiveJournal Blog: http://brandietarvin.livejournal.com/
On LinkedIn!, Google+, and Twitter.

Freelance Writer: Shadowrun
Latchkeys: Nevermore, Latchkeys: The Bootleg War, and Latchkeys: Roscoes in the Night are now available on Nook and Kindle.
Post #429177
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse