Error encountered when executing SSIS package

I am encountering the following error when executing an SSIS package:

Retrieving the COM class factory for component with CLSID {4555B0A5-E8D7-49BD-B299-3140C34D3769} failed due to the following error: e06d7363 
Exception from HRESULT: 0xE06D7363.;
at Microsoft.SqlServer.Dts.Runtime.Package..ctor()
at Microsoft.SqlServer.Dts.Runtime.PackageItem.Load(IDTSEvents events)
at Microsoft.SqlServer.Dts.Runtime.PackageItem.LoadPackage(IDTSEvents events)
at Microsoft.SqlServer.IntegrationServices.Server.ISServerExec.ISServerExecutionEvents.LoadPackage(PackageItem item)
at Microsoft.SqlServer.IntegrationServices.Server.ISServerExec.ProjectOperator.StartPackage()
at Microsoft.SqlServer.IntegrationServices.Server.ISServerExec.ProjectOperator.PerformOperation()

This is what I have done:

• Built the package in Visual Studio
• Import the package into the Integrated Services Catalog in SQL Server Management Studio
• Deployed the package to the Integrated Services Catalog
• Executed the package (and got the error).

I checked online, and found that 0xE06D7363 means that a C++ exception has been thrown, which doesn't really help.

I also found that 4555B0A5-E8D7-49BD-B299-3140C34D3769 refers to a object named SSIS.Package.3 in the registry, but that also doesn't help.

Has anyone encountered this, and more importantly, does anyone know of a way of resolving it?

If Creating ssis package from an .net application

The problem is that that the application had been compiled with a reference to an SQL version ManagedDTS.dll and was being deployed to a SQL 2014 environment. Check the references and confirm that your reference to the ManagedDTS.DLL is using the version of the DLL that matches your production environment.

If you are creating an Integration Services Packages using Visual Studio:

In the property pages for an Integration Services project, on the General tab of Configuration Properties, select the TargetServerVersion property and choose SQL Server 2016, SQL Server 2014, or SQL Server 2012.

Read this MSDN article for more informations

This Article contains more details