Windows 10: Unable to work with SSIS packages in Visual Studio 2017

Unable to work with SSIS package in Visual Studio 2017, seeing the following in event viewer:Error 1:Application: devenv.exeFramework Version: v4.0.30319Description: The process was terminated due to an internal error in the .NET Runtime at IP 5FE61A33 5FE40000 with exit code 80131506.Error 2: Faulting application name: devenv.exe, version: 15.9.28307.1622, time stamp: 0x6101da21Faulting module name: clr.dll, version: 4.8.4250.0, time stamp: 0x5f2a0630Exception code: 0xc0000005Fault offset: 0x00021a33Faulting process id: 0x158cFaulting application start time: 0x01d798f9413afaecFaulting appli

:)

 

Visual Studio (.NET Framework)

Do you still have the Visual Studio Installer or Visual Studio Manager still installed?

If you have it still installed and it opens up correctly, you could try removing all additional packages that are installed, and try reinstalling them again. It could have been a corruption issue relating to package extensions that you may have installed
into Visual Studio 2017 Community Edition. If that does not work, go to apps in settings, and select Visual Studio 2017 Community Edition and select repair. If that does not work, you could try going to TechNet, and asking there for help. It could be a
bug with the current version of the .NET Framework 48 or with the recent version of Visual Studio 2017 Community Edition.

If you can not find Visual Studio Installer or Visual Studio Manager, unfortunately in this situation the only thing I can think of is if you still have the installation file that you downloaded from the Visual Studio website. If you can't find that, then
I suggest that you download Visual Studio 2019 Community Edition, since the 2017 Community edition is not given for free anymore unless you have some sort of subscription. However, I suggest that you still check with TechNet before taking this step.

 

Visual Studio IDE Crashing

I have a setup of Visual Studio Professional 2017 15.7.6 with SSIS installed. I have a few packages which, when I try to run with the debugger active, cause devenv.exe to crash.

The issue started randomly about 2-3 weeks ago and I have yet to figure out the origin, it may have been a windows server update.

These packages work with the debugger turned off and simple packages work.

The packages themselves work occasionally and at times will work continuously.

The packages consist of a flat file connection (connected to a CSV) which executes a SQL stored procedure then loops through the file and reads all rows. The rows then get counted and their data types checked, once checked they are pushed into a SQL database
and another stored procedure is run.

Sometimes removing the error handling on check data types fixes it, sometimes not. Sometimes removing row counting helps. Sometimes removing things results in the package working once and then not working again after that.

I have tried any listed suggestions I could find including devenv resets, visual studio repairs, visual studio downgrades, running code on the dstDebugger and more. The issue prevails and is stumping me on what causes it.

The setup is on a Hyper-V virtual machine with 30x2.4GHz cores and >38GB RAM.

Any help would be appreciated,

Thanks.

 

visual studio 2017

Hi,

Thank you for writing to Microsoft Community Forums.

Usually, the packages installation fails if there is an issue with the installation file or the installed program. You can try to download a new setup file and then try to install Visual Studio from https://docs.microsoft.com/en-us/visualstudio/productinfo/vs2017-system-requirements-vs

I would also suggest you to check this article on Troubleshoot
Visual Studio installation and upgrade issues which should be helpful based on the Visual Studio installation issue that you are facing.

However, let me point you in the right direction where you will be able to get the support for the issue that you are facing. I would suggest you to post your query in the
TechNet,
where you will be able to find support from professionals and members for issues related to Visual Studio 2017.

Thanks,

Suman.B

Microsoft Community - Moderator