SSIS running through SQL Server agent Job Fails --SQL Server 2012 RRS feed

  • Question

  • Hi All,

    I am getting the below error.

    Executed as user: sak\thiru. ...ion 11.0.2100.60 for 64-bit  Copyright (C) Microsoft Corporation. All rights reserved.    Started:  3:31:17 PM  Error: 2014-03-07 15:32:22.46     Code: 0xC0202009     Source: CommonDataSource Connection manager "TESTDB"     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: "Login timeout expired".  An OLE DB record is available.  Source: "Microsoft SQL Server Native Client 11.0"  Hresult: 0x80004005  Description: "A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.".  An OLE DB record is available.  Source: "Microsoft SQL Server Native Client 11.0"  Hresult: 0x80004005  Description: "Named Pipes Provider: Could not open a connection to SQL Server [53]. ".  End Error  Error: 2014-03-07 15:32:43.58  

     The package execution fa...  The step failed.

    I checked namedpipes, ports,services, SqlBrowser all are running fine.

    share your views.




    Saturday, March 8, 2014 12:45 AM


  • Hi Thiru,

    The error messages are rather general and the issue may occur due to various causes. You can check the “Connect Time” setting of the Connection Manager "TESTDB", and increase its timeout value.

    If the issue persists, maybe it occurs because the Windows Firewall or certain anti-virus software blocks the RPC dynamic range of TCP Ports between SQL Server and Domain Controllers. In this case, temporarily disable third party anti-virus software, or configure RPC dynamic port allocation to work with firewalls referring to the following KB article http://support.microsoft.com/kb/154596.

    In addition, the issue may be related to the SQL Server that the OLE DB Source adapter connects to. You can check the SQL Server log to see if any error occurs at that time.

    Hope this helps.


    Mike Yin
    TechNet Community Support

    • Marked as answer by Mike Yin Monday, March 31, 2014 1:51 AM
    Monday, March 17, 2014 2:56 PM

All replies