Re: general network error; no event logged
From: Mark Allison (marka_at_no.tinned.meat.mvps.org)
Date: 04/27/04
- Next message: Snehal Tiwari: "URGENT: MSDE TCP Problem"
- Previous message: Marek Powichrowski: "Re: Trusted Connection=Yes"
- In reply to: Mike Doyle: "general network error; no event logged"
- Next in thread: mdoyle_at_exmplar.com: "Re: general network error; no event logged"
- Reply: mdoyle_at_exmplar.com: "Re: general network error; no event logged"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 27 Apr 2004 11:28:28 +0100
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.
- Next message: Snehal Tiwari: "URGENT: MSDE TCP Problem"
- Previous message: Marek Powichrowski: "Re: Trusted Connection=Yes"
- In reply to: Mike Doyle: "general network error; no event logged"
- Next in thread: mdoyle_at_exmplar.com: "Re: general network error; no event logged"
- Reply: mdoyle_at_exmplar.com: "Re: general network error; no event logged"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
