Visual Studio 2022 - SSIS - Faulting application name: DtsDebugHost.exe, and Faulting module name: KERNELBASE.dll

Nitin Patil 0 Reputation points
2023-12-11T14:28:36.6666667+00:00

I downloaded and installed Visual Studio 2022, with extensions including SQL Server Integration Services Project 2022.
We used Visual Studio 2019 before.
One of the tasks from an existing SSIS package is to read the data from Oracle and write it to a CSV file.
The SSIS package execution completes when the task is still reading the data from Oracle. It never writes to the CSV file.
I’ll provide the information from the Debug log and also from the Event viewer.

The Debug log is as follows -
SSIS package “C:\JetTeamFoundationServer\JasperInfinity\Infinity.InitialDataLoads\Infinity.InitialDataLoads.SSIS\RandomSSISFunctionTests.dtsx” starting.
Information: 0x4004300A at Query Oracle and save to csv, SSIS.Pipeline: Validation phase is beginning.
Warning: 0x80049304 at Query Oracle and save to csv, SSIS.Pipeline: Warning: Could not open global shared memory to communicate with performance DLL; data flow performance counters are not available. To resolve, run this package as an administrator, or on the system’s console.
Information: 0x40043006 at Query Oracle and save to csv, SSIS.Pipeline: Prepare for Execute phase is beginning.
Information: 0x40043007 at Query Oracle and save to csv, SSIS.Pipeline: Pre-Execute phase is beginning.
Information: 0x402090DC at Query Oracle and save to csv, Flat File Destination [2]: The processing of file “C:\SSISOutputs\RandomSSISFunctionTests.csv” has started.
Information: 0x4004300C at Query Oracle and save to csv, SSIS.Pipeline: Execute phase is beginning.
SSIS package “C:\JetTeamFoundationServer\JasperInfinity\Infinity.InitialDataLoads\Infinity.InitialDataLoads.SSIS\RandomSSISFunctionTests.dtsx” finished: Canceled.
The program ‘[17548] DtsDebugHost.exe: DTS’ has exited with code 0 (0x0).

The event viewer ( Windows- Application) Reports -

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

Problem signature:
P1: DtsDebugHost.exe
P2: 2019.150.2000.281
P3: 6417d84c
P4: KERNELBASE.dll
P5: 10.0.19041.3570
P6: da674bb7
P7: c0000005
P8: 000000000002cf19
P9:
P10:

Attached files:
?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5DAA.tmp.mdmp
?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5F13.tmp.WERInternalMetadata.xml
?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5F33.tmp.xml
?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5F41.tmp.csv
?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5F61.tmp.txt

These files may be available here:
?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_DtsDebugHost.exe_de27d2d2d6a3aa8e5c33b0416b41945e9a7b8c38_5857d2a0_8b157804-fc98-4151-b123-6432c0929bd6

Analysis symbol:
Rechecking for solution: 0
Report Id: 38764628-b45a-474f-9159-6ca854697e47
Report Status: 268435456
Hashed bucket: 16c3510a12905583eebe04add5e0900e
Cab Guid: 0

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

2 answers

Sort by: Most helpful
  1. ZoeHui-MSFT 33,296 Reputation points
    2023-12-13T06:55:35.3666667+00:00

    Hi @Nitin Patil

    Could not open global shared memory to communicate with performance DLL; data flow performance counters are not available. To resolve, run this package as an administrator, or on the system’s console.

    Could you please try to run Visual Studio as administrator?

    In addition, you may set run64bitRuntime to true.

    Here is a same thread you may take a reference to.

    Regards,

    Zoe Hui


    If the answer is helpful, please click "Accept Answer" and upvote it.


  2. Nitin Patil 0 Reputation points
    2023-12-13T15:10:55.8966667+00:00

    Thanks, @ZoeHui!

    I had already tried running the Visual Studio 2022 as an administrator.

    The 64bitRuntime had always been True. It did not help.

    The SSIS package executes from the server and writes the data to the CSV file. It needs to run from the local workstation. (All observations mentioned from the issue are while running the package from the local workstation.)

    0 comments No comments