Home Dashboard Directory Help
Search

"Unable to complete login process due to delay in opening server connection" by RAJB1234


Status: 

Closed
 as External Help for as External


7
0
Sign in
to vote
Type: Bug
ID: 496639
Opened: 10/8/2009 8:00:01 AM
Access Restriction: Public
0
Workaround(s)
view
0
User(s) can reproduce this bug

Description


Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80004005 Description: "Unspecified error". An OLE DB record is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80004005 Description: "Unable to complete login process due to delay in opening server connection". End Error Error: 2009-10-08 02:33:10.77     Code: 0xC0202009     Source: XXXX XXX[201]     Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80004005 Description: "Unspecified error". An OLE DB record is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80004005 Description: "Unable to complete login process due to delay in opening server connection".

This error is coming up when the SSIS packages are executing during the nightly process, when we kick off the packages again it works fine. As we kick off the packages in the morning i am not sure what should have caused this error.

Let me know if its the connection issue , how to increase the connection time-out.

Thanks in Advance,
Rajesh
Details
Sign in to post a comment.
Posted by Crakdkorn on 7/19/2011 at 9:06 AM
Other half of the similar error is "Coannot initialize the data source object of OLE DB Provider "SQLNCLI10" for linked server. Then it says OLE DB provider "SQLNCLI10" for lined server returned message "Unable to complete login process due to delay in opening server connect".
Posted by Microsoft on 11/19/2010 at 3:44 PM
Resolving this issue as this looks like a connection problem and there has been no feedback in the past three months. If this is still an issue, please reopen this bug.
Posted by Microsoft on 8/12/2010 at 1:39 PM
There are three things to check.
First is the capacity of the server, for sql server, in ssms, right click on server node => Connections tab, and check the Remote query timeout is big enough.

2nd is the connection timeout, this can be changed through connection string, by adding somehting like ";connect timeout=50". Notice that this setting is provider-specific.

3rd is the Command timeout, most of the ssis adaptors has a CommandTimeout property that can be found in advanced editor. 0 means infinite.

Check and modify the three settings to avoid timeout.

Posted by Microsoft on 8/12/2010 at 1:37 PM
There are three things to check out, first is the capacity of the server, for sql server, in ssms, right click on server node => Connections tab, and check the Remote query timeout is big enough.

2nd is the connection timeout, this can be changed through connection string, by adding somehting like ";connect timeout=50". Notice that this setting is provider-specific.

3rd is the Command timeout, most of the ssis adaptors has a CommandTimeout property that can be found in advanced editor. 0 means infinite.

Check and modify the three settings to avoid timeout.

Posted by bwdavis59 on 3/9/2010 at 6:53 AM
Don't know if this is relevant, look for a command timeout value, it is different than the connection timeout.
I don't know if you can specify that in SSIS or not. We had to increase it in some .NET code we were using to execute backup commands against a SQL Server 2008 instance.

Posted by acorr1 on 1/13/2010 at 1:21 PM
Same prob also. SQL Server 2008 on Windows Server 2008 x64 using SSIS. We have about a dozen nightly jobs. This error will occur on one job every 3rd or 4th night. Usually one of the bigger jobs (taking between 10 minutes to 3 hours to process). Timeout is set to 1000. Yes it tells you which component fails. Solution appears to be to re execute the SSIS package. Has been happening for about a year. Agree really frustrating.
Posted by luminary_designs on 12/4/2009 at 10:31 AM
Same problem. Intermittent. SQL2005, 64, SSIS.

Really frustrating.
Posted by Microsoft on 10/26/2009 at 5:51 PM
Hello,
Is there any error message telling which component or task is encoutering the error? Usually there will be another error message starting with the source of the error message.
Also, to increase the timeout of a connection, you could append a provider-specific string such as ";connect timeout=50" to the connection string.
Please provide more details about what component/task is throwing the error message and the data provider you are using.

Thanks
Sign in to post a workaround.