Error establishing socket

Our applications (day-end jobs) sporadically get the following errors
(usually between midnight and 1 AM):
[Microsoft][SQLServer 2000 Driver for JDBC]Error establishing socket.
[Microsoft][SQLServer 2000 Driver for JDBC]Address in use: connect
If the job is restarted, it then works without error. Any ideas what may be
causing the error?
Thanks in advance for any assistance you can offer,
-Chris
Chris:
It's suspicious that these errors appear time-related, esp. during a
*mainentance* time of day when servers may be getting backed up or traffic
on the network may spike w/ data replication, etc. Have you done a good
check for possible environment issues?
-shelby
Shelby Goerlitz
Microsoft SQL Server
"Chris Rowan" <ChrisRowan@.discussions.microsoft.com> wrote in message
news:770F1B8E-5740-4DA5-8053-8B88DA922C2A@.microsoft.com...
> Our applications (day-end jobs) sporadically get the following errors
> (usually between midnight and 1 AM):
> [Microsoft][SQLServer 2000 Driver for JDBC]Error establishing socket.
> [Microsoft][SQLServer 2000 Driver for JDBC]Address in use: connect
> If the job is restarted, it then works without error. Any ideas what may
be
> causing the error?
> Thanks in advance for any assistance you can offer,
> -Chris
sql

Error During Job

We have getting an intermitant error when running
some of our Jobs.
ConnectionCheckForData (checkfordata)
[sqlstate 01000][message 10054]
General Network Error. Check Network Documentation
[sqlstat 08s01][error 11]
We can put retries on this step, and sometimes it
works after a couple of retries.. Other times
the job dies. If we restart the job, it will
usually complete.
We don't know why this is happening. The only thing
that step is doing is some inserts and deletes to a
couple of tables.
The connection problem seems to get worse as time goes
by... If we refresh the indexes, and do some other
database cleanup... it gets better.
Can anyone help us in preventing this problem
answered above - sometimes these newsgroups take a few minutes for posts to
appear...
Regards,
Greg Linwood
SQL Server MVP
"scot" <sstyer@.alltel.net> wrote in message
news:481001c42bcd$eff4bba0$a001280a@.phx.gbl...
> We have getting an intermitant error when running
> some of our Jobs.
> ConnectionCheckForData (checkfordata)
> [sqlstate 01000][message 10054]
> General Network Error. Check Network Documentation
> [sqlstat 08s01][error 11]
> We can put retries on this step, and sometimes it
> works after a couple of retries.. Other times
> the job dies. If we restart the job, it will
> usually complete.
> We don't know why this is happening. The only thing
> that step is doing is some inserts and deletes to a
> couple of tables.
> The connection problem seems to get worse as time goes
> by... If we refresh the indexes, and do some other
> database cleanup... it gets better.
> Can anyone help us in preventing this problem
>

Error During Job

We have getting an intermitant error when running
some of our Jobs.
ConnectionCheckForData (checkfordata)
[sqlstate 01000][message 10054]
General Network Error. Check Network Documentation
[sqlstat 08s01][error 11]
We can put retries on this step, and sometimes it
works after a couple of retries.. Other times
the job dies. If we restart the job, it will
usually complete.
We don't know why this is happening. The only thing
that step is doing is some inserts and deletes to a
couple of tables.
The connection problem seems to get worse as time goes
by... If we refresh the indexes, and do some other
database cleanup... it gets better.
Can anyone help us in preventing this problemanswered above - sometimes these newsgroups take a few minutes for posts to
appear...
Regards,
Greg Linwood
SQL Server MVP
"scot" <sstyer@.alltel.net> wrote in message
news:481001c42bcd$eff4bba0$a001280a@.phx.gbl...
> We have getting an intermitant error when running
> some of our Jobs.
> ConnectionCheckForData (checkfordata)
> [sqlstate 01000][message 10054]
> General Network Error. Check Network Documentation
> [sqlstat 08s01][error 11]
> We can put retries on this step, and sometimes it
> works after a couple of retries.. Other times
> the job dies. If we restart the job, it will
> usually complete.
> We don't know why this is happening. The only thing
> that step is doing is some inserts and deletes to a
> couple of tables.
> The connection problem seems to get worse as time goes
> by... If we refresh the indexes, and do some other
> database cleanup... it gets better.
> Can anyone help us in preventing this problem
>

Error During Job

We have getting an intermitant error when running
some of our Jobs.
ConnectionCheckForData (checkfordata)
[sqlstate 01000][message 10054]
General Network Error. Check Network Documentation
[sqlstat 08s01][error 11]
We can put retries on this step, and sometimes it
works after a couple of retries.. Other times
the job dies. If we restart the job, it will
usually complete.
We don't know why this is happening. The only thing
that step is doing is some inserts and deletes to a
couple of tables.
The connection problem seems to get worse as time goes
by... If we refresh the indexes, and do some other
database cleanup... it gets better.
Can anyone help us in preventing this problemanswered above - sometimes these newsgroups take a few minutes for posts to
appear...
Regards,
Greg Linwood
SQL Server MVP
"scot" <sstyer@.alltel.net> wrote in message
news:481001c42bcd$eff4bba0$a001280a@.phx.gbl...
> We have getting an intermitant error when running
> some of our Jobs.
> ConnectionCheckForData (checkfordata)
> [sqlstate 01000][message 10054]
> General Network Error. Check Network Documentation
> [sqlstat 08s01][error 11]
> We can put retries on this step, and sometimes it
> works after a couple of retries.. Other times
> the job dies. If we restart the job, it will
> usually complete.
> We don't know why this is happening. The only thing
> that step is doing is some inserts and deletes to a
> couple of tables.
> The connection problem seems to get worse as time goes
> by... If we refresh the indexes, and do some other
> database cleanup... it gets better.
> Can anyone help us in preventing this problem
>