SSIS .dtsx package error - Failed to start project - ssis

All, I'm using visual studio community 2019 - please see error message below. This error occurs when I try to run/execute a .dtsx package. I've registered regsvr32 dts.dll successfully, but to no avail:
Thanks for any help.

Related

SSIS editing a script task and saving it doesn't work

Note: I am not an SSIS developer and have a very limited knowledge on it, so may be missing on very small details, please read carefully.
I have an existing SSIS package which has script task in one of the steps.
I had to update one single value in script task, so I opened it in notepad++ and updated the value and saved it. Now when the scheduled SSIS job runs, it still picks up the old value and not the updated one.
I realized script task is a VB file, so probably would need to re-compile it for the binaries. I read about it and found out, if you open it through VS and save it, VS automatically compiles it and you don't have to do anything further. I can be wrong here.
I can't do project deployment on the server, so I would just need the updated package file to replace it on the server.(I am taking this updated package file from the Visual studio project that I created to edit the SSIS package. I am not sure, if there is another way to get the package or even if this is a right package.
Now the problem is,
when I updated the old package using notepad++, it didn't throw any error when it was running through scheduled job, but it took the old value
Now when I am putting the new package that I edited using Visual studio, it throws below error
Executed as user: sampleUser(nameupdated). Microsoft (R) SQL Server Execute Package Utility Version 13.0.5026.0 for 32-bit Copyright (C) 2016 Microsoft. All rights reserved. Started: 5:08:09 PM Error: 2021-11-02 17:08:10.83 Code: 0xC0016016 Source: OraclePackage Description: Failed to decrypt protected XML node "DTS:Password" with error 0x8009000B "Key not valid for use in specified state.". You may not be authorized to access this information. This error occurs when there is a cryptographic error. Verify that the correct key is available. End Error Error: 2021-11-02 17:08:11.26 Code: 0x00000005 Source: Rename files in archive folder to _yyyymmddhhmm Rename files in archive folder to _yyyymmddhhmm Description: Failed to migrate scripts contained in the package to the VSTA 14.0 format. Move the scripts to a new Script task. End Error Error: 2021-11-02 17:08:14.19 Code: 0x00000005 Source: Script Task Script Task Description: Failed to migrate scripts contained in the package to the VSTA 14.0 format. Move the scripts to a new Script task. End Error Error: 2021-11-02 17:08:17.17 Code: 0x00000001 Source: Script Task Description: Exception has been thrown by the target of an invocation. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 5:08:09 PM Finished: 5:08:17 PM Elapsed: 7.25 seconds. The package execution failed. The step failed.
I read about this error and found that package's security level can cause this issue, so update the protection level of the package from "EncryptSensitiveWithUserKey" to "DontSaveSensitive"
Now when I am running the project I get below error
Executed as user: sampleuser(nameUpdated). Microsoft (R) SQL Server Execute Package Utility Version 13.0.5026.0 for 32-bit Copyright (C) 2016 Microsoft. All rights reserved. Started: 5:31:44 PM Error: 2021-11-02 17:31:53.93 Code: 0x00000001 Source: Script Task Description: Exception has been thrown by the target of an invocation. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 5:31:44 PM Finished: 5:31:53 PM Elapsed: 9.047 seconds. The package execution failed. The step failed.
Please let me know if there is another way to edit the script task directly and compile it in place so that it takes the updated values else, if there is something else I can do.
Thanks in advance.
I found a solution(more of an error or less knowledge from my side actually)
Updating the security from "EncryptSensitiveWithUserKey" to "DontSaveSensitive"
When you open an existing SSIS package in Visual studio, the read and write variables are wiped out from script task for some reason. Reassigning them resolved the problem.
How did I find out if that was the problem, I put some exception handling in the script task to notify me of further issues.
Hope this helps to someone in the similar problem.

SSDT SSIS Extension installation failed with VS 2019 Enterprise

I have been struggling to install SSIS extension on Visual Studio 2019 Enterprise.
Error Details:
[0BBC:47D8][2021-10-29T20:18:09]i000: MainViewModel.OnPackageActionProgress: Percent completed: 50, Overall progress: 11
[5288:4B60][2021-10-29T20:18:12]e000: Error 0xc0000005: Process returned error: 0xc0000005
[5288:4B60][2021-10-29T20:18:12]e000: Error 0xc0000005: Failed to execute EXE package.
[0BBC:47D8][2021-10-29T20:18:12]e000: Error 0xc0000005: Failed to configure per-machine EXE package.
It seems there are issues with my computer. Below is the screenshot that the tool is not able to repair the .NET Framework. Truly I believe this is a good starting point.
Try to install .NET Framework manually from the following URL:
https://support.microsoft.com/en-us/kb/3102436
If that does not work, try to run the following tool:
https://www.microsoft.com/en-us/download/details.aspx?id=30135&wa=wsignin1.0

Execute package task in errorhandling gives error

In my OnError eventhandler I try to execute a (child) package but I get this error:
Error: Error 0x80040154. Failed to create an instance of empty child package. The Distributed Component Object Model (DCOM) configuration or the installation of SQL Server Integration Services, may be corrupted on your machine.
followed by Class not registered
This happens even if it is an empty package I call.
Is it not possible to execute an package in an EventHandler?
What else could lead to this error?
Packages are set as ExecuteOutOfProcess
Using Visual Studio 2019 with microsoft integration services installed.
Edit:
Setting ExecuteOutOfProcess to FALSE made the empty package run.
Another package with 3rdparty-components however failed.
But that is cleaclry caused by that 3party component. Investigating
Reinstalling the Integration Sevrices Add-on solved the problem

Cannot Add Script Component to Data Flow Task

Cannot add a Script Component to Data Flow Task for an SSIS Package that I am working on.
I am running Visual Studio 2017 and creating an SSIS Package that is targeted for SQL Server 2012
I am trying to drag the Script Component Task from the SSIS Toolbox to the Data Flow Task, I get the error as shown below
TITLE: Microsoft Visual Studio
The component could not be added to the Data Flow task. Could not
initialize the component. There is a potential problem in the
ProvideComponentProperties method.
ADDITIONAL INFORMATION:
Error at Replace Delimiter in File [SSIS.Pipeline]: Failed to create
COM Component Categories Manager due to error 0x80070002 "The system
cannot find the file specified.".
Error at Replace Delimiter in File [ [52]]: The component is missing,
not registered, not upgradeable, or missing required interfaces. The
contact information for this component is "".
Exception from HRESULT: 0xC0048021
(Microsoft.SqlServer.DTSPipelineWrap)
BUTTONS:
OK
The Script Component should be added to the Data Flow Task
Thanks for your suggestions - but I ended up upgrading my license to visual studio 2019 and it worked like a charm
I guess because with this version the SSDT is integrated better
Not really entirely sure what the issue was with Visual Studio 2017 - it could be my install but because VS 2019 didn't work I did not bother with it.

Custom SSIS component created for SQL Server 2014 not working in SQL Server 2016

We got a couple of custom SSIS components which were created targeting SSIS for SQL Server 2014.
We are now migrating our dtsx packages to SSIS for SQL Server 2016.
I have modified the custom SSIS components such that assembly references to DTS assemblies have been given the property SpecificVersion=False.
I'm using the DTS.Runtime.Application.Upgrade method to upgrade my packages in a console app. However the packages which have these custom components are throwing the below error.
What else should I be doing?
Error in DFT (SSIS.Pipeline) The "" failed to cache the component metadata object and returned error code 0x80131600.
Error in DFT (SSIS.Pipeline) Component , clsid {4F885D04-B578-47B7-94A0-DE9C7DA25EE2} failed to initialize due to error 0xC0047067 "The "%1" failed to cache the component metadata object and returned error code 0x%2!8.8X!.".
Error in DFT ( [2]) The component is missing, not registered, not upgradeable, or missing required interfaces. The contact information for this component is "".
Error in DFT (SSIS.Pipeline) The component metadata for "" could not be upgraded to the newer version of the component. The PerformUpgrade method failed.
Error in Package.dtsx The loading of the package has failed.
You get to rebuild the component against the 2016 SSIS binaries, redeploy it to the GAC and probably change the references in your packages to use the new components (unless the 2014->2016 migration process is entirely different than 2005->2008 and 2008->2012 which is when I stopped building custom components).
The reason for this is that the DLLs for SSIS are strongly signed/versioned and that signature changes between editions of the project so the 2014 component you built is against the 130 version of TxPipeline dll and it now needs to reference 140 to be successful.