I have may SSI packages running on multiple sources and recently we have been experiencing this Login timeout expired problem. This is not consistent it happens very randomly. The error message is . Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80004005 Description: "Login timeout expired". 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 login response". An OLE DB record is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80004005 Description: "TCP Provider: Timeout error [258]. ". End Error Error: 2011-02-16 02:35:55.83 Code: 0xC020801C Source: Data Flow Task OLE DB Source [319] Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "JDE" failed with error code 0xC0202009. is it something to to do with multiple open connections that are not closed after the package executions complete? if yes is there a property or any work around to close the connection as and when all the package tasks are complete. Thanks

My packages donot have multiple dataflows in the same package. But I am running multiple packages at the same time connecting to same source and target database.

Any chance of sequencing them? How many are we talking about? I kind of doubt this is the issue. SQL should be able to handle hundreds or thousands of connections, unless you have it limited somewhere? By License Agreement?Todd C - MSCTS SQL Server 2005 - Please mark posts as answered where appropriate.

We have configuration files for all the connections. At any point there are not more than 20 packages running parallely. we never had any problem like this till recently (this packages are running like for around a year). Just today and once last week we had this issue of timeing out and package failing. When contacted DBA's they said everythng at the source end was fine nothing went wrong when this packages failed and there was just some issue with slow WAN links thats all. I googled for the issue and found sugestion 1. to increase the timeout in connection manager(need to try) 2. to check if there are multiple open connections and close all connections when the package tasks are completed (do not know how to) 3. use ip address insted of the server name just to avoid DNS issue (didnot help)

Hi Devlssis! Did you have found the answer to your problem? Im experiencing the same problem, but I am receiving this error message when connecting from any kind of source (DLL, services, Reporting services) to my SQL 2008 server. This error drops randomly a lot of times everyday, and any kind of advice will be helpful. Tks