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 connecting to database

I get the following error:

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

How do I correct it?

check this linkhttp://support.microsoft.com/kb/914277/en-us

hope it was helpful

|||

There was a big long thread on this over here.

http://codingforums.com/archive/index.php/index.php?t-124900.html