SQL 2016 ISServerExec issue


  • Hi,

        I have an SSIS package that I've cut down to indicate my problem. It has a data flow task as follows, which contains a single Excel source task which points to an Excel file and a Row Count task. This is all that's in the package. The Excel source file has about 750,000 rows.

    If I run this package in debug in Visual Studio, it completed successfully.

    If I Deploy it to the SSIS Catalog and run it from there by right-clicking on the package and clicking Execute, it fails with an unexpected termination.

    After running for a while, I get a message that the ISServerExec process terminated unexpectedly and we get this in the system Event log:

    Faulting application name: ISServerExec.exe, version: 13.0.1601.5, time stamp: 0x57244dca
    Faulting module name: MSVCR100.dll, version: 10.0.40219.325, time stamp: 0x4df2be1e
    Exception code: 0x40000015
    Fault offset: 0x0008d6fd
    Faulting process ID: 0x2280
    Faulting application start time: 0x01d311ebed6d10f5
    Faulting application path: D:\Apps (x86)\Microsoft SQL Server\130\DTS\Binn\ISServerExec.exe
    Faulting module path: C:\Windows\SYSTEM32\MSVCR100.dll
    Report ID: 73a3413e-7ddf-11e7-80cd-00505625073d
    Faulting package full name:
    Faulting package-relative application ID:

    We are using:

    Windows Server 2012 R2 Standard

    SQL Server 2016

    Visual Studio Enterprise 2015 Version 14.0.25431.01 Update 3

    If I reduce the number of rows in the source file, it works sometimes, I.e. I ran it with a file containing 50,000 rows and it worked. I've also run it with a file containing 100,000 rows, 200,000 rows etc., which also worked

    With 300,000 rows, it sometimes works and sometimes fails, i.e. terminates unexpectedly.

    Could anyone please give me an idea about how to debug this?



    pátek 11. srpna 2017 9:45

Všechny reakce

  • Hi Kevin,

    It looks like a bug, add logging to the package itself to see what else gets reported, but engaging Microsoft pro services is advisable, and it looks like a resource, namely memory issue.

    But I'd split the file 1st and process it in chunks to allow to accomplishing the mission.




    pátek 11. srpna 2017 14:59
  • Hi,

         Thanks for your reply. Please could you elaborate on 'add logging to the package'. Despite working with SSIS for a number of years, I've never needed to do that before.

         Splitting the file would seem to be the way to proceed, but the file is delivered 2 -3 times a month to a file location, then it's automatically picked up by our package with no manual intervention. I don't think we can even get the package to process, say 200,000 rows at a time because I think we'll just have the same problem. I'll give it a try though.

        Also the file gets bigger every month, so knowing where to stop processing chunks of 200,000 rows wouldn't be easy,

       Thanks for your help,


    pátek 11. srpna 2017 15:19
  • Watch this how to enable logging in SSIS:




    pátek 11. srpna 2017 18:35
  • Hi,

    Even I'm facing the similar issue. The package is failing even while running in debug mode in visual studio.

    The package fails with unexpected termination and below is the error in event viewer.

    My sql server version is 2016 SP2 on windows server 2012 R2 standard version.


    Faulting application name: ISServerExec.exe, version: 13.0.5026.0, time stamp: 0x5aae8fd7
    Faulting module name: MSVCR120.dll, version: 12.0.40660.0, time stamp: 0x577e0f1e
    Exception code: 0xc0000409
    Fault offset: 0x000a7646
    Faulting process id: 0x2308
    Faulting application start time: 0x01d3ee7526cbfa9d
    Faulting application path: e:\Program Files (x86)\Microsoft SQL Server\130\DTS\Binn\ISServerExec.exe
    Faulting module path: C:\Windows\SYSTEM32\MSVCR120.dll
    Report Id: 6adcbbe7-5a68-11e8-80f0-0050568e702c
    Faulting package full name: 
    Faulting package-relative application ID:



    pátek 18. května 2018 7:25