SSIS Job - Intermittent Login Timeout Failures

  • I have been running into some weird problem - I have SSIS jobs scheduled to run on a regular basis. Most of the time they run without any problem, but lately I got more and more sporadic job failures like the following message. The failure does not persist for long as the same job will run fine later without any intervention.

    Everything else on the server seems fine. I don't see any info in the sql error log. Any ideas? Thanks!

    ------------

    Microsoft (R) SQL Server Execute Package Utility Version 10.0.2531.0 for 64-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 9:23:26 AM Could not load package "xxxxxxx" because of error 0xC0014062. Description: The LoadFromSQLServer method has encountered OLE DB error code 0x80004005 (Login timeout expired). The SQL statement that was issued has failed. Source: Started: 9:23:26 AM Finished: 9:23:42 AM Elapsed: 15.039 seconds. The package could not be loaded. The step failed.

  • Hi!

    Have you solved the problem? We have the same problem.

    Best regards,

  • I realize this is a few years old, but did anyone ever figure out what was causing this issue? I have an SSIS package running fine 90% of the time, but for a stretches of the day it fails over and over with 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 Native Client" Hresult: 0x80004005 Description: "Login timeout expired".

    An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.".

    An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Named Pipes Provider: Could not open a connection to SQL Server [2]. ".

    End Error

    Error: 2013-06-13 15:13:26.13

    Code: 0xC020801C

    Source: 03) Asset - RDP Link Update RdpFirstLinkCallLogId [14273]

    Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "E2Prod2" failed with error code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method call failed.

    Different task flow, different connection manager failing, different times of the day.

  • Yes, it's been a while ago. I believe it turned out to be an issue with the IT infrastructure. Our storage systems for the sql server were failing. After the infrastructure was upgraded, the problems went away.

  • Thanks for following up, I'll look into that.

  • Check you max server memory configuration. This is probably entirely coincidental but these error messages seems to have gone away for me after I increased my C drive space, it was a little tight.

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply