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 Connection to MSDE with SQL JDBC Driver

Connecting to SQL Server with SQL Server Driver for JDBC is OK. Trying to connect to same database, installed under MSDE, i get error "Error establishing socket".
It looks like the JDBC Driver only supports full SQL Server 2000 and not MSDE?D, What JDBC driver are you using?
If the driver you are using supported only TCP connection, make sure that TCP is enabled on the server side for MSDE.

Error connecting new data source to SQL Server Express

In ODBC Data Source Administrator, I add the SQL Server driver, complete a name and select my local SQL Server instance, select Windows NT authentication (the client configuration is set to TCP/IP, dynamically determine port) and on clicking Next, the following errors occur:

Connection failed:
SQLState: '01000'
SQL Server error: 2
[Microsoft][ODBC SQL Server Driver][Shared Memory][ConnectionOpen (Connect()).
Connection failed:
SQLState: '08001'
SQL Server error: 17
[Microsoft][ODBC SQL Server Driver][Shared Memory]SQL Server does not exist or access denied.

I note that in the Help it says: "The SQL Server system administrator must have associated your Microsoft Windows login with a SQL Server login ID".

Is this the problem? If so, where do I make this association?

Thanking you in anticipation.

In a default installation of SQL Express, every user on a computer can at least connect to the server. The fact that you're connection is failing suggests that something else is wrong. Based on the error, the most likely cause is that you've mis-typed the server name. SQL Express installs to a named instance so you need to provide both the machine name and instance name in your connection, be default, the instance name is SQLEXPRESS, so your server name would be <machinename>\SQLEXPRES. For local connection you can replace <machinename> with "(local)" or "." Note that it's a back slash, people commonly use the forward slash which will cause an error.

If that doesn't help, verify which SQL driver you are using, there are two of them. It looks like you're using the Native Client, which is good, but if you're using the old MDAC driver (just says "SQL Server" in the list) then you'll need to enable the TCP protocol for the Server using the SQL Configuration Manager. MDAC ODBC connection go through TCP, even for local connections.

Mike

|||

Hi,

I would suggest to refer http://support.microsoft.com/kb/322336 & http://support.microsoft.com/kb/328306/en-us

Hemantgiri S. Goswami

Error connecting new data source to SQL Server Express

In ODBC Data Source Administrator, I add the SQL Server driver, complete a name and select my local SQL Server instance, select Windows NT authentication (the client configuration is set to TCP/IP, dynamically determine port) and on clicking Next, the following errors occur:

Connection failed:
SQLState: '01000'
SQL Server error: 2
[Microsoft][ODBC SQL Server Driver][Shared Memory][ConnectionOpen (Connect()).
Connection failed:
SQLState: '08001'
SQL Server error: 17
[Microsoft][ODBC SQL Server Driver][Shared Memory]SQL Server does not exist or access denied.

I note that in the Help it says: "The SQL Server system administrator must have associated your Microsoft Windows login with a SQL Server login ID".

Is this the problem? If so, where do I make this association?

Thanking you in anticipation.

In a default installation of SQL Express, every user on a computer can at least connect to the server. The fact that you're connection is failing suggests that something else is wrong. Based on the error, the most likely cause is that you've mis-typed the server name. SQL Express installs to a named instance so you need to provide both the machine name and instance name in your connection, be default, the instance name is SQLEXPRESS, so your server name would be <machinename>\SQLEXPRES. For local connection you can replace <machinename> with "(local)" or "." Note that it's a back slash, people commonly use the forward slash which will cause an error.

If that doesn't help, verify which SQL driver you are using, there are two of them. It looks like you're using the Native Client, which is good, but if you're using the old MDAC driver (just says "SQL Server" in the list) then you'll need to enable the TCP protocol for the Server using the SQL Configuration Manager. MDAC ODBC connection go through TCP, even for local connections.

Mike

|||

Hi,

I would suggest to refer http://support.microsoft.com/kb/322336 & http://support.microsoft.com/kb/328306/en-us

Hemantgiri S. Goswami