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] >-----Original Message-----
>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 >
>
>
>
>"Mike Doyle" <mdoyle@exmplar.com> wrote in message
>news:486a01c42bd2$f7664de0$a501280a@phx.gbl...
>> 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.
>>
>> Our environment is Windows 2000 SP1, SQL server 7.0 Sp3.
>
>
>.