SSIS2019 Unexpected termination

Divyesh Patel 21 Reputation points
2021-12-16T17:03:13.257+00:00

We upgraded to SQL Server 2019 and upgraded all SSIS project to target server 2019 . When we run SSIS package it runs for some time and then it crashes with Unexpected Termination. Below is reported in event viewer and there is no error in execution log. I am not able to find any detail on how to resolve it. Package is connecting to Oracle and exporting data to text file.

Event viewer:

Faulting application name: ISServerExec.exe, version: 15.0.4178.1, time stamp: 0x614d1427
Faulting module name: ntdll.dll, version: 10.0.14393.4704, time stamp: 0x615bdef9
Exception code: 0xc0000374
Fault offset: 0x00000000000f7143
Faulting process id: 0x2634
Faulting application start time: 0x01d7f29b5a496c79
Faulting application path: D:\Program Files\Microsoft SQL Server\150\DTS\Binn\ISServerExec.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 89994dd1-849b-49e0-9d33-bd880af06df0
Faulting package full name:
Faulting package-relative application ID:

SQL Server Integration Services
SQL Server Integration Services
A Microsoft platform for building enterprise-level data integration and data transformations solutions.
2,592 questions
0 comments No comments
{count} votes

7 answers

Sort by: Most helpful
  1. Yitzhak Khabinsky 25,956 Reputation points
    2021-12-16T19:43:37.527+00:00

    Hi @Divyesh Patel ,

    (1) What is your SSIS run-time SQL Server version?
    Please issue the following statement and add it to your question:

    SELECT @@VERSION;  
    

    (2) Also, how do you execute a SSIS package:

    • From the SSISDB Catalog.?
    • From the SQL Server Agent Job?

    (3) Try to change the runtime execution mode between 32-bit and 64-bit.

    UPDATE
    If you have SQL Server 2019 with SSIS, Enterprise edition, it is much better to use Microsoft Connector for Oracle. Here is the link: Microsoft Connector for Oracle

    It is pretty good, and even doesn't require Oracle Client installation.


  2. AmeliaGu-MSFT 13,986 Reputation points Microsoft Vendor
    2021-12-17T06:29:52.13+00:00

    Hi DivyeshPatel-3985,

    Welcome to Microsoft Q&A.
    In addition, does only this one package crash? Do other packages have the same issue?
    Could you please try to rebuild and redeploy the package?
    Please also try to recreate SSISDB catalog.

    Best Regards,
    Amelia


    If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


  3. Divyesh Patel 21 Reputation points
    2021-12-20T15:50:33.277+00:00

    I have narrowed it down to Oracle connection . We are using 64bit Oracle Client and we are getting this error. When changed to 32bit I get following error.
    Do i need to install anything to make 64bit oracle client work with SQL Server 2019 . Same setup works fine with 2016.

    Package1:Error: There was an error trying to establish an Open Database Connectivity (ODBC) connection with the database server.

    159051-image.png


  4. Divyesh Patel 21 Reputation points
    2021-12-23T00:15:52.41+00:00

    Update on this issue.
    When I build SSIS Package I have to use 32bit oracle client (We use ODBC DSN to connect to Oracle ) drivers as visual studio does not allow 64bit Oracle client. Later when I deploy the package to SQL server we have 64bit Oracle Client installed and package crash with unexpected termination error. If i run the package with 32bit runtime it works but I need this to run using 64bit as that is how we had it configured in SQLServer 2016 and it worked before. Any help will by much apricated.

    0 comments No comments

  5. Divyesh Patel 21 Reputation points
    2021-12-23T17:12:05.57+00:00

    160107-report.txt

    i was able to get attached report for the issue.

    Fault bucket 1304561738599059535, type 4
    Event Name: APPCRASH
    Response: Not available
    Cab Id: 0

    Problem signature:
    P1: ISServerExec.exe
    P2: 15.0.4188.2
    P3: 618345c6
    P4: StackHash_6b84
    P5: 10.0.14393.4704
    P6: 615bdef9
    P7: c0000374
    P8: PCH_81_FROM_ntdll+0x00000000000A67D4
    P9:
    P10:

    Attached files:
    \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER84F4.tmp.WERInternalMetadata.xml

    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_ISServerExec.exe_1767b67241bcba2e835e5f368b8e1789728855f0_adc4b74c_1f578784

    Analysis symbol:
    Rechecking for solution: 0
    Report Id: dd931579-91b5-4b27-8b36-26fee277362d
    Report Status: 0

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.