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 error. 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.GetConne ction(DbConnection
owningObject)
at
System.Data.ProviderBase.DbConnectionFactory.GetCo nnection(DbConnection
owningConnection)
at
System.Data.ProviderBase.DbConnectionClosed.OpenCo nnection(DbConnection
outerConnection, DbConnectionFactory connectionFactory)
at System.Data.SqlClient.SqlConnection.Open()
at
System.Web.SessionState.SqlSessionStateStore.SqlSt ateConnection..ctor(SqlPartitionInfo 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 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 error. 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.GetConne ction(DbConnection
> owningObject)
> at
> System.Data.ProviderBase.DbConnectionFactory.GetCo nnection(DbConnection
> owningConnection)
> at
> System.Data.ProviderBase.DbConnectionClosed.OpenCo nnection(DbConnection
> outerConnection, DbConnectionFactory connectionFactory)
> at System.Data.SqlClient.SqlConnection.Open()
> at
> System.Web.SessionState.SqlSessionStateStore.SqlSt ateConnection..ctor(SqlPartitionInfo 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?

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?

Configuring SSIS package to read a value before executin

Hi,

Is it possible in any ways to Configure a SSIS package in such a way that based on the User Input the package runs. For e.g if there is a table which has say 10 distinct groups. Normal SSIS package would ideally pick all the data from the source to the Destination

I want to know how to configure in Such a way that I should be able to say Group X as the input and data related to GroupX alone should be copied.

Select * from SomeTable where GroupName = @.CongigVar.

how to achieve something like this?

thanks

Hello,

What kind of input are you intrested in getting?

If you have the group name that you want to get information from in a table, you can, in control flow, make a query to a table, and put it on a variable, then on the data flow you can use the variable as a parameter.

To use it on a parameter your query should be

"Select * from SomeTable where GroupName = ?"

Then in the parameter button on the left you choose the variable that will pass tha value to the question mark.

Is that good for you?

Regards,

|||

Hello,

I think that might just be what I need, but when I tried creating one, its failing with the error, 'Parameter Name Unrecognized'. I think am doing it wrongly. Can you post some links that explains how to put a value from a table onto a variable, and then use it as i/p to a Data flow?

thanks

|||

Nfrf wrote:

Hello,

What kind of input are you intrested in getting?

If you have the group name that you want to get information from in a table, you can, in control flow, make a query to a table, and put it on a variable, then on the data flow you can use the variable as a parameter.

To use it on a parameter your query should be

"Select * from SomeTable where GroupName = ?"

Then in the parameter button on the left you choose the variable that will pass tha value to the question mark.

Is that good for you?

Regards,

There's no need to store values in a table. You can parameterize your package by passing it values when you call it. Explore the /SET option of dtexec. All the information you require is in Books Online.

-Jamie

|||

Yes it is true. I just gave him a way.

The thing that i thnik he wanted to know was the parameter on the query.

Even so thanks