locked
SSIS Error : Unable to complete login process due to delay in opening server connection RRS feed

  • Question

  • Hi Gurus,

    One of my packages which is called from a windows scheduled task is intermittently throwing the following error:

    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 11.0"  Hresult: 0x80004005  Description: "Unable to complete login process due to delay in opening server connection".
    End Error

    This happens once or twice a week, rest of the days the job runs fine. Since the source server is not owned by our team, can't change investigate much on their side however we tried moving our job execution time to an earlier hour but the problem stays.

    Here is what I am planning to implement as a work around:

             -Trap the error if occurs

             -Then wait for 15 minutes and try executing the package again (repeat up to four times)

             -Fail and notify about the error

    Does this approach look good and is this doable/feasible? Is there a better way to fix this issue? Your valuable inputs are highly appreciated.


    HTH,
    Cheers!!
    Ashish
    Please mark it as Answered if it answered your question or mark it as Helpful if it helped you solve your problem.


    Thursday, December 27, 2018 4:42 PM

All replies

  • Hi Ashish, 

    I think it's a nice workaround. 

    Please check the discussion in this link: SSIS Package Failure - Intermittent TCP / Login Error

    It might be caused by the busy communication on the source server, so you can also try to move the job execution time to several more hours earlier/later... just to reduce the possibility of failure. 


    MSDN Community Support Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com

    Friday, December 28, 2018 7:13 AM