all groups > sql server connect > april 2004 >
You're in the

sql server connect

group:

general network error; no event logged



general network error; no event logged Mike Doyle
4/26/2004 2:10:56 PM
sql server connect: When running a job under SQLAgent we have intermittently
received the following message:

ConnectionCheckForData (CheckforData()). [SQLSTATE 01000]
(Message 10054) General network error. Check your network
documentation. [SQLSTATE 08S01] (Error 11). The step
failed.

The job had been running for two years successfully and
has recently (over the last two weeks) begun failing
intermittently. The job is run from the local SQL
server. The step runs a stored procedure and fails after
about an hour and a half of running.

Re: general network error; no event logged mdoyle NO[at]SPAM exmplar.com
4/27/2004 6:18:57 AM
There are no network issues of which I am aware. I am the
IT support staff. I am working with our SQL staff on this
issue.

I have just been told it operates locally only on the
local SQL server.

We did install Arcserve on this system a little over a
month ago and this problem started occuring 2 weeks ago,
but I can't draw any dots between that and this problem
and the arcserve is functioning without error. There is
no indication of any connectivity issue on this server
other than this odd error not reflected in the event log.

ps. I am passing these along to our SQL people so feel
free to get technical. :)



[quoted text, click to view]
Re: general network error; no event logged Mark Allison
4/27/2004 11:28:28 AM
Mike,

Can you confirm with your network admins that there haven't been any network
glitches recently? This error is usually down to connectivity problems. Does
the stored procedure access anything on other servers?

--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk




[quoted text, click to view]

Re: general network error; no event logged kevmc NO[at]SPAM online.microsoft.com
4/29/2004 7:48:27 PM
The error indicates a Winsock Error 10054 which may occur if a TCP reset
happens on the session. See if changing the server to use Named Pipes
instead of Sockets makes a difference.


Thanks,

Kevin McDonnell
Microsoft Corporation

This posting is provided AS IS with no warranties, and confers no rights.


AddThis Social Bookmark Button