VS 2019 crash when executing SSIS package

Question

Hello guys,

I have VS 2019 Community installed on Windows Server 2019.
When I start a package from VS, VS hangs , crash and restart.

2 DtsDebugHost.exe processes keep running in background, and I have to kill it with TaskManager to release the .ispac file of the solution.

In the event viewer, I can find this :
Nom de l’application défaillante devenv.exe, version : 16.11.32228.343, horodatage : 0x621d5771
Nom du module défaillant : ucrtbase.dll, version : 10.0.17763.1, horodatage : 0xc3ae1887
Code d’exception : 0xc0000409
Décalage d’erreur : 0x000a5d0b
ID du processus défaillant : 0x24d8
Heure de début de l’application défaillante : 0x01d842acea8516cd
Chemin d’accès de l’application défaillante : C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\IDE\devenv.exe
Chemin d’accès du module défaillant: C:\Windows\System32\ucrtbase.dll
ID de rapport : 261f5211-00cd-4a99-98be-03f9ee0e8a28
Nom complet du package défaillant :
ID de l’application relative au package défaillant :

Here are the VS versions :

Microsoft Visual Studio Community 2019
Version 16.11.11
VisualStudio.16.Release/16.11.11+32228.343
Microsoft .NET Framework
Version 4.8.03761

Version installée : Community

Microsoft Visual Studio Tools for Applications 2019 00435-00000-00000-AA059
Microsoft Visual Studio Tools for Applications 2019

Common Azure Tools 1.10
Fournit des services courants utilisables par Microsoft Azure Mobile Services et Microsoft Azure Tools.

Gestionnaire de package NuGet 5.11.0
Gestionnaire de package NuGet dans Visual Studio. Pour plus d'informations sur NuGet, visitez https://docs.nuget.org/

Outils Azure App Service v3.0.0 16.11.106.23128
Outils Azure App Service v3.0.0

Outils C# 3.11.0-4.22108.8+d9bef045c4362fbcab27ef35daec4e95c8ff47e1
Composants C# utilisés dans l'IDE. Selon votre type de projet et vos paramètres, une version différente du compilateur peut être utilisée.

Outils Visual Basic 3.11.0-4.22108.8+d9bef045c4362fbcab27ef35daec4e95c8ff47e1
Composants Visual Basic utilisés dans l'IDE. Selon votre type de projet et vos paramètres, une version différente du compilateur peut être utilisée.

Package hôte de l'adaptateur de débogage de Visual Studio Code 1.0
Couche d'interopérabilité pour l'hébergement d'adaptateurs de débogage Visual Studio Code dans Visual Studio

ProjectServicesPackage Extension 1.0
ProjectServicesPackage Visual Studio Extension Detailed Info

SQL Server Data Tools 16.0.62201.17150
Microsoft SQL Server Data Tools

SQL Server Integration Services 15.0.2000.180
Concepteur Microsoft SQL Server Integration Services
Version 15.0.2000.180

Can you please help as I can't debug any package...

Franck

Answer 1

Hopefully you aren't trying to debug this on a production server. When you build and debug your SSIS package in VS it is running in the local DTS host and not against your SQL Server instance (other than perhaps data sources that query data). So there is no real reason to install Visual Studio on a server. This would be a huge security hole to me along with potential performance degradation. So my first question is can you debug this package locally and it works?

In rare cases a package may work locally but not on an SSIS instance. In that case install SSMS on the server and try running it from there to debug what is going on. Note that in order to run an SSIS package you have to deploy it to the server and to do that you may need to run VS as an admin.

Finally, if VS is crashing consistently at the same spot then try adjusting your SSIS package until you can narrow down where it is failing. It is possible it is relying on a component that isn't installed or is out of date although I would expect the package to fail validation.

Answer 2

Thanks @Michael Taylor

No, I am not debugging on a production server :)
This a VM on a private cloud and the database can only be accessed from there. So I can not test it locally.
I'll check with infra team if they can open requiered ports for a test.

The SSIS Catalog is on the same server. When I deploy the package to the catalog and run it from the catalog, it works fine.

In the package, I have 3 simple data flows, that reads data from an oracle database and load it in SQL Server tables.
Sometimes, the crach happens during the second, somtimes during the third.
The only "difference" I can notice for the 3 data flows is the number of rows :
around

1. 000 lines for the first
2. 000 lines for the second
3. 000 lines for the third.

I have checked and there is no disk space or memory issue.

Franck

Answer 3

When I disable the 64b runtime, VS crashes during the 3rd data flow, using around 1.2 Gb. The 2 remaining dtdebughost.exe are using 8 and 88 Mo of ram.
When I enable the 64b runtime, VS crashes during the 2nd data flow, using around 450 Mb. The 2 remaining dtdebughost.exe are using 8 and 72 Mo of ram.

This is a brand new installation for my new job, and the first package I'm trying to developp. Before, in my previous job, I was used to run data flows in debug mode extracting several millions of rows...

Answer 4

I have changed the targetServerVersion from SQL Server 2019 to SQL Server 2017... and the package runs fine in VS...
Changing back to 2019 makes VS crashing...

So, waiting for a update of VS2019 and/or SSIS extension, I'll stay in 2017... Deploying to a 2019 SSIS seems to work...

Thanks for your support @Michael Taylor