Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


SQLServer Error: 10054 Communication link failure [SQLSTATE 08S01]


SQLServer Error: 10054 Communication link failure [SQLSTATE 08S01]

Author
Message
sravan2020
sravan2020
Grasshopper
Grasshopper (11 reputation)Grasshopper (11 reputation)Grasshopper (11 reputation)Grasshopper (11 reputation)Grasshopper (11 reputation)Grasshopper (11 reputation)Grasshopper (11 reputation)Grasshopper (11 reputation)

Group: General Forum Members
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
Brandie Tarvin
Brandie Tarvin
SSCertifiable
SSCertifiable (7.7K reputation)SSCertifiable (7.7K reputation)SSCertifiable (7.7K reputation)SSCertifiable (7.7K reputation)SSCertifiable (7.7K reputation)SSCertifiable (7.7K reputation)SSCertifiable (7.7K reputation)SSCertifiable (7.7K reputation)

Group: General Forum Members
Points: 7739 Visits: 8717
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 AdministratorLiveJournal Blog: http://brandietarvin.livejournal.com/On LinkedIn!, Google+, and Twitter.Freelance Writer: ShadowrunLatchkeys: Nevermore, Latchkeys: The Bootleg War, and Latchkeys: Roscoes in the Night are now available on Nook and Kindle.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search