Thursday, March 29, 2012

General network error.

Receiving error:
"General network error. Check your network documentation. [SQLSTATE 08S01]
(Error 11)".
Running on SQLServer 2000 EE, SP3, Windows 2000 Adv.
This started after we rebuild the server. We have tens of jobs that run at
night. This error is happening only randomly as some days nothing happens
and same job runs fine but other day it blows up. It is not happening with
same job either. Then we restart the job and it runs fine.This error message is generated from ODBC, and not really
from SQL Server. It is generated when a connection
something the ODBC fails ie DB2 (see Microsoft) so
although SQL Server is reporting it, it is not the cause.
I would sugest that you go through the Event View on your
NT, or put in a trace to see exactly where it fails.
J
>--Original Message--
>Receiving error:
>"General network error. Check your network documentation.
[SQLSTATE 08S01]
>(Error 11)".
>Running on SQLServer 2000 EE, SP3, Windows 2000 Adv.
>This started after we rebuild the server. We have tens
of jobs that run at
>night. This error is happening only randomly as some
days nothing happens
>and same job runs fine but other day it blows up. It is
not happening with
>same job either. Then we restart the job and it runs
fine.
>
>.
>|||Nothing in the event log or SQLServer log accept that error message.
"Julie" <anonymous@.discussions.microsoft.com> wrote in message
news:1302301c4433d$9f6096f0$a101280a@.phx.gbl...
> This error message is generated from ODBC, and not really
> from SQL Server. It is generated when a connection
> something the ODBC fails ie DB2 (see Microsoft) so
> although SQL Server is reporting it, it is not the cause.
> I would sugest that you go through the Event View on your
> NT, or put in a trace to see exactly where it fails.
> J
>
> >--Original Message--
> >Receiving error:
> >"General network error. Check your network documentation.
> [SQLSTATE 08S01]
> >(Error 11)".
> >
> >Running on SQLServer 2000 EE, SP3, Windows 2000 Adv.
> >
> >This started after we rebuild the server. We have tens
> of jobs that run at
> >night. This error is happening only randomly as some
> days nothing happens
> >and same job runs fine but other day it blows up. It is
> not happening with
> >same job either. Then we restart the job and it runs
> fine.
> >
> >
> >
> >.
> >|||Hi ilovesql,
We are expiriencing the same issue - I was woundering if you had this resolved.
I also wanted to ask you - when you rebuild the server did it have the same configuration as before or you installed SP3 for SQL Server?
We went from Win2000 server SQL server 2000 SP2 to WIN2003 server SP3 and we started to have this problem from that day on. Microsoft is working on it but this is the second day and they haven't came up with the solution.
I think it is SP3 - something is not right with it.
Thanks,
Anna
"ilovesql" wrote:
> Nothing in the event log or SQLServer log accept that error message.
>
> "Julie" <anonymous@.discussions.microsoft.com> wrote in message
> news:1302301c4433d$9f6096f0$a101280a@.phx.gbl...
> > This error message is generated from ODBC, and not really
> > from SQL Server. It is generated when a connection
> > something the ODBC fails ie DB2 (see Microsoft) so
> > although SQL Server is reporting it, it is not the cause.
> > I would sugest that you go through the Event View on your
> > NT, or put in a trace to see exactly where it fails.
> >
> > J
> >
> >
> > >--Original Message--
> > >Receiving error:
> > >"General network error. Check your network documentation.
> > [SQLSTATE 08S01]
> > >(Error 11)".
> > >
> > >Running on SQLServer 2000 EE, SP3, Windows 2000 Adv.
> > >
> > >This started after we rebuild the server. We have tens
> > of jobs that run at
> > >night. This error is happening only randomly as some
> > days nothing happens
> > >and same job runs fine but other day it blows up. It is
> > not happening with
> > >same job either. Then we restart the job and it runs
> > fine.
> > >
> > >
> > >
> > >.
> > >
>
>

No comments:

Post a Comment