With the release of SSDT 2016 (GA), I've loaded SQL Server 2016 GA Developer Edition, the new SSMS 2016 stand-alone build, and even Visual Studio 2015 Update 2 (Professional edition) and Visual Studio still crashes anytime I attempt to open an SSIS package or create a new solution using the SSIS template (including the import wizard). I've reinstalled using the suggested order (SQL Server 2016, SSMS, SSDT) as well as just Visual Studio 2015 followed by SSDT. Both result in the same crash. I'm able to create and open all other solution types (SSRS, SSAS, SQLCLR) so it seems to be an issue specific to SSIS. The Connect bug report can be found (along with the attachments and everything MSFT has asked for) here: https://connect.microsoft.com/SQLServer/feedback/details/2781125/ssis-projects-crash-visual-studio
The error in Visual Studio is as follows:
Problem signature:
Problem Event Name: APPCRASH
Application Name: devenv.exe
Application Version: 14.0.25420.1
Application Timestamp: 57685d85
Fault Module Name: KERNELBASE.dll
Fault Module Version: 6.3.9600.18340
Fault Module Timestamp: 5736541b
Exception Code: c06d007e
Exception Offset: 00014878
OS Version: 6.3.9600.2.0.0.272.7
Locale ID: 1033
Additional Information 1: d3a5
Additional Information 2: d3a5b2a34c74c92cf7c3ff2061a46015
Additional Information 3: 86f5
Additional Information 4: 86f5db7ad561caf63ca32f7aba7c4416
This project may be used for building high performance data integration and workflow solutions, including extraction, transformation, and loading (ETL) operations for data warehousing. Currently the supported target server version starts from SQL Server 2012 up to 2022.
SSDT is no longer needed. VS 2022 supports SQL as part of the built in workload.
Reasons that the package may have failed are as follows: The user account that is used to run the package under SQL Server Agent differs from the original package author. The user account does not have the required permissions to make connections or to access resources outside the SSIS package.
SSDT is backwards compatible, so you can always use the newest SSDT to design and deploy databases, models, reports, and packages that run on older versions of SQL Server.
Exception code c06d007e is "Delay-load module not found", so you are missing a DLL.
To debug it you can track DLL loading attempts using Process Monitor: https://technet.microsoft.com/en-us/sysinternals/bb896645.aspx
or older FileMon: http://technet.microsoft.com/en-us/sysinternals/bb896642.aspx
After you find which dll is missing you can try to extract it manually from distribution or install all the components on clear system and copy needed DLL from there.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With