Connect Error

We have a SQL 2005 clustered server (Microsoft Cluster Services) that is
queried from 4 IIS6 Windows Server 2003 frontends. Each frontend runs both
classic ASP apps connection with SQL Server ODBC and .NET2 apps connecting
with System.Data.SqlClient. Ocassionaly we get a string of errors timeouts
opening a connection running maybe 2 minutes.
One the classic ASP apps we log one of these two errors:
Microsoft OLE DB Provider for ODBC Drivers (0x80004005)
[Microsoft][ODBC SQL Server Driver][DBNETLIB]General network err
or. Check
your network documentation
or
Microsoft OLE DB Provider for ODBC Drivers (0x80004005)
[Microsoft][ODBC SQL Server Driver]Timeout expired
on the ADODB.Connection.Open
On the .NET2 apps we log
Message Timeout expired. The timeout period elapsed prior to completion of
the operation or the server is not responding.
StackTrace at
System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection
owningObject)
at
System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection
owningConnection)
at
System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection
outerConnection, DbConnectionFactory connectionFactory)
at System.Data.SqlClient.SqlConnection.Open()
at
System.Web.SessionState.SqlSessionStateStore.SqlStateConnection..ctor(SqlPar
titionInfo sqlPartitionInfo)
Source .Net SqlClient Data Provider
I've setup an unrelated machine to use ODBCPing on the DSN to the DB and
during the error period I get:
COULD NOT CONNECT TO SQL SERVER
SQLState: S1T00 Native Error: 0
Info. Message: [Microsoft][ODBC SQL Server Driver]Timeout expired
DSN ODBCPING
What could cause a failure to accept connections like that and what else can
I do to find the issue?Have you found a solution for your problem?
Tks.
Rui
"Demi" wrote:

> We have a SQL 2005 clustered server (Microsoft Cluster Services) that is
> queried from 4 IIS6 Windows Server 2003 frontends. Each frontend runs bot
h
> classic ASP apps connection with SQL Server ODBC and .NET2 apps connectin
g
> with System.Data.SqlClient. Ocassionaly we get a string of errors timeout
s
> opening a connection running maybe 2 minutes.
> One the classic ASP apps we log one of these two errors:
> Microsoft OLE DB Provider for ODBC Drivers (0x80004005)
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]General network e
rror. Check
> your network documentation
> or
> Microsoft OLE DB Provider for ODBC Drivers (0x80004005)
> [Microsoft][ODBC SQL Server Driver]Timeout expired
> on the ADODB.Connection.Open
> On the .NET2 apps we log
> Message Timeout expired. The timeout period elapsed prior to completion of
> the operation or the server is not responding.
>
> StackTrace at
> System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection
> owningObject)
> at
> System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection
> owningConnection)
> at
> System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection
> outerConnection, DbConnectionFactory connectionFactory)
> at System.Data.SqlClient.SqlConnection.Open()
> at
> System.Web.SessionState.SqlSessionStateStore.SqlStateConnection..ctor(SqlP
artitionInfo sqlPartitionInfo)
> Source .Net SqlClient Data Provider
> I've setup an unrelated machine to use ODBCPing on the DSN to the DB and
> during the error period I get:
> COULD NOT CONNECT TO SQL SERVER
> SQLState: S1T00 Native Error: 0
> Info. Message: [Microsoft][ODBC SQL Server Driver]Timeout expired
> DSN ODBCPING
> What could cause a failure to accept connections like that and what else c
an
> I do to find the issue?