Post reply

Job failure due to connectivity issues

  • December 26, 2015 at 9:55 pm

    #323677

    Hi All,

    Need your help in how to go about troubleshooting below issue. We have some ETL jobs in our environment and failing with communication link failures. Basically, we define a job, inside the job there are sequence of steps and in one of the step

    we are calling an SSIS package which in turn has its own source & destination connection defined inside it.

    So, when that step runs, SSIS pkg runs, it connects to the source system,reads data and loads data into destination system.

    For doing this, we have data flow task inside SSIS package. The job runs fine without any issues. However, sometimes job gets failed intermittently with communication link failures. Whenever this happens, we usually restart the job step.

    The problem, the job step runs for 5-8 hours. so, if a failure occurs at 4 or 5th hour, we have again restart the job step and wait for 5 hours for the job to get completed. This is pain! so, we want to troubleshoot the issue and fix it.

    We have already network team to see any packet drops. But I don't see any help from them.

    We have shared the job history to network team, they say there see no issues from there end at network layer.

    Is there a way from SQL Server side, we can track information to find the reason for communication link failures?

    Error Description: "Communication link failure". An OLE DB record is available. Source: "Microsoft SQL Server Native Client 11.0" Hresult: 0x80004005 Description: "TCP Provider: An existing connection was forcibly closed by the remote host.

    Any thoughts of how to troubleshoot and fix the issue?

    SQL Server versions being used in our env is :Microsoft SQL Server 2012 (SP1)

    Thanks,

    Sam

  • December 27, 2015 at 4:21 pm

    #1848194

    Was SQL Server raising an exception, assertion, or high severity error to its errorlog at the time?

  • December 28, 2015 at 8:25 pm

    #1848383

    All I see from SQL Agent Job history is,

    Error Description: "Communication link failure". An OLE DB record is available. Source: "Microsoft SQL Server Native Client 11.0" Hresult: 0x80004005 Description: "TCP Provider: An existing connection was forcibly closed by the remote host.

  • December 28, 2015 at 8:29 pm

    #1848384

    That's the client. Check the server :).

Viewing 4 posts - 1 through 3 (of 3 total)

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