Share via

Visual Studio Professional 2019 keeps crashing when I try to open an SSIS project (new or old)

bhrj4 6 Reputation points
2022-05-26T13:23:26.177+00:00

Hi,

I had been using Visual Studio Professional 2019 for a a few years now to create/modify SSIS packages with no issue...but in the past few months my Visual Studio has started crashing any time I try to create (or open an existing) SSIS project.

Visual Studio 2019 Version 16.11.15
SSIS extension version 3.16

I've been looking at the Event Viewer and these are 2 errors I get when Visual Studio crashes:

First:
Application: devenv.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an internal error in the .NET Runtime at IP 72311A33 (722F0000) with exit code 80131506.

Second:
Faulting application name: devenv.exe, version: 16.11.32510.428, time stamp: 0x627b1042
Faulting module name: clr.dll, version: 4.8.4341.0, time stamp: 0x6023024f
Exception code: 0xc0000005
Fault offset: 0x00021a33
Faulting process id: 0x4a4c
Faulting application start time: 0x01d87044f9bb1b44
Faulting application path: C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\Common7\IDE\devenv.exe
Faulting module path: C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll

Things I've tried:

  • I've checked memory - and no issues with that.
  • Uninstalling and reinstalling Visual Studio 2019
  • Uninstalling and reinstalling SSMS (worth a shot right?)
  • Tried to use Visual Studio 2017 - but same issue

Any suggestions to fix this issue is appreciated!

Thank you

SQL Server Integration Services
SQL Server Integration Services
A Microsoft platform for building enterprise-level data integration and data transformations solutions.
2,705 questions

3 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Steve Denning 6 Reputation points
    2022-05-30T14:57:41.047+00:00

    I'm running the same VS and SSIS versions as stated in the original post and have just started to experience the same issue. SSIS projects will load, but can take a good 20-30 minutes to do so. It seems like this could be due to a change in the latest VS update.

    Rolling back VS to the previous version seems the most obvious thing to try, but according to the following post it seems that rollback isn't currently supported:
    https://learn.microsoft.com/en-us/answers/questions/411941/rolling-back-a-vs2019-update.html

    Has anyone else been able to identify a solution to this issues?

    1 person found this answer helpful.
  2. Yitzhak Khabinsky 26,586 Reputation points
    2022-05-26T21:31:30.08+00:00

    Hi @bhrj4 ,

    Pease try repairing your .Net Framework with this:

    https://www.microsoft.com/en-us/download/details.aspx?id=30135

  3. ZoeHui-MSFT 41,496 Reputation points
    2022-05-27T01:46:45.307+00:00

    Hi @bhrj4 ，

    Please try to repair Visual Studio.

    VS Installer-->More-->Repair.

    If this do not work, you may roll back the VS to a lower release to see if it could resolve your issue.

    VS-history

    If the two methods all fail, please report the issue here, the product team will help to deal with it.

    Zoe

    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.

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.