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
Related
I tried to import my db from SQL Azure, but I am getting the next error in SQL Server Management Studio from each version that I specified:
SQL Server Management Studio v17.9.1:
Could not load schema model from package. (Microsoft.SqlServer.Dac)
ADDITIONAL INFORMATION:
Internal Error. The database platform service with type Microsoft.Data.Tools.Schema.Sql.Sql150DatabaseSchemaProvider is not valid.
You must make sure the service is loaded, or you must provide the full type name of a valid database platform service.
(Microsoft.Data.Tools.Schema.Sql)
SQL Server Management Studio v18.0 Preview 5:
Failed to retrieve data for this request. (Microsoft.SqlServer.Management.Sdk.Sfc)
ADDITIONAL INFORMATION:
There is already an open DataReader associated with this Command which must be closed first. (System.Data)
The version when I am trying to import SQL Server is
Uninstall SQL Server Management Studio 2018, then install SSMS v17.9.1. Re-import the Bacpac and you will have better results.
For this import error, you can try this way :
Install Microsoft SQL Server Data-Tier Application Framework (February 2015) ( Both the x64 and x86 versions).
Here is the link may be useful for you:
Unable to import SQL Azure V12 BACPAC: "type Microsoft.Data.Tools.Schema.Sql.SqlAzureV12DatabaseSchemaProvider is not valid"
I've actually been having a very similar problem.
Although I had a slightly different error message for MSSMSv17 (in regards to the additional information).
But the same error for MSSMSv18 (Preview 6).
So after trying many different things until I had irreversible damaged my SQL server installations to the point where I had to reinstall Windows, the first thing I installed was SQL Server 2017 & MSSMSv18. Which produced the same error as before. But MSSMSv17 worked, soo... yay?
Hi I'm looking for some guidance.
I've developed an SSIS project with a couple of script tasks and script components using visual studio 2015 for targeted version 2016.
I have two environment server A and server B both have SSIS 2016 SP1 installed on it.
I have done a project deployed of the packages to Sever A and tested the packages everything executed perfectly.
However when I deployed the packages in SSIS_DB from Server A to Server B I get these errors in my execution report.
The component metadata for "script component, clsid { }" could not be upgraded to the newer version of the component. The PerformUpgrade method failed
2
There was an exception while loading Script Task from XML: System.Exception: The Script Task "" uses version 15.0 script that is not supported in this release of Integration Services. To run the package, use the Script Task to create a new VSTA script. In most cases, scripts are converted automatically to use a supported version, when you open a SQL Server Integration Services package in %SQL_PRODUCT_SHORT_NAME% Integration Services.
at Microsoft.SqlServer.Dts.Tasks.ScriptTask.ScriptTask.LoadFromXML(XmlElement elemProj, IDTSInfoEvents events)
The interesting part is if I deploy my packages directly from visual studio to Server B the packages executes correctly with no issue.
So there seems to be inconsistencies between server A and Server B.
A small background to this is that when both servers were built Server A had Microsoft SQL Server 2016 (SP1-GDR) and Server Microsoft SQL Server 2016 (RTM)
but they both now have Microsoft SQL Server 2016 (SP1-GDR) after Server B was updated.
I'm not sure how the upgrade was done by my suspicion is that the SSIS on server are different but I can't seem to prove it.
when I check the version they both seem to return same or similar meta data
The right answer is here: https://andyleonard.blog/2017/09/ssis-version-15-0-script-error/
In my case the problem was the setting at the project level “TargetServerLevel” set to “SQL Server 2017”. The correct value must be “SQL Server 2016”. Once the value is changed and the project redeployed errors desappear.
I believe one of developers in my team used VS 2017 when added the project. All other tasks and components, excep script, were fine even with incorrect server version and the problem appeared only when I had to use script tasks and components.
To fix the problem open project parameters => Configuration Properties => TargetServerVersion
Select “SQL Server 2016”, then deploy to the server.
This was caused by SSMS. I don’t know what’s going on under the hood but During the deployment I was using SSMS 2017 which seems to be upgrading script components in my packages. I changed to use SSMS 2016 and this issue disappeared
Just summarizing some things because there are some reasons for facing this problem:
Your are deploying a package with Target Version Definition for another SQL Server
You are deploying a package which contains a script task with not same SSMS version as SQL Server Version
If your package doesn't contain a script task for example, then any version of SSMS can deploy the package to any version of SQL Server via SSISDB catalog. Not sure why is this happening. Seems that you can deploy and execute packages while making sure that the package target version is supported from SQL Version, but also if you have a ScriptTask inside you need to be super careful and make sure also that the integration services version of SSMS is the same with SQL Server version.
I will open a question to Microsoft just to be sure why the script task has this treatment. Maybe is because the script task is Framework dependent.
Something similar to my problem has been posted before but not quite like this. I have Visual Studio 2015 Version 14.0.25431.01 Update 3. I develop packages with this and deploy the project to SQL Server 12.0.4100.01. The packages run fine. Then I try to deploy from the ispac and I get the error:
There was an exception while loading Script Task from XML: System.Exception:
The Script Task redacted uses version 14.0 script that is not supported
in this release of Integration Services. To run the package, use the Script
Task to create a new VSTA script. In most cases, scripts are converted
automatically to use a supported version, when you open a SQL Server
Integration Services package in %SQL_PRODUCT_SHORT_NAME% Integration
Services.
at Microsoft.SqlServer.Dts.Tasks.ScriptTask.ScriptTask.LoadFromXML
(XmlElement elemProj, IDTSInfoEvents events)
I checked the xml in Visual Studio and unpacked the ispac to compare the code in each and all the versioning code is the same. Apparently there is an upgrade/downgrade operation happening when deploying from Visual Studio but doesn't happen when deploying from the ispac. Is there a way to create an ispac that is version compatible?
You can change the project property TargetServerVersion : SQL Server 2012/2014/2016
The script language will be changed automatically to Microsoft Visual c# 2010/2012/2015.
Note: First copy code from the script task and save it.
I have developed a project in Visual Studio 2015 and initially TargetDeploymentVersion was set to 2014.
Later we realized this project also needs to be deployed on SQL Server 2012.
So, we changed TargetDeploymentVersion to 2012, build the project, and deployed .ispac on SQL Server Integration Services 2012. The deployment went well.
Please note, we kept Run64bitRunTime=False.
But during validation I started receiving these component metadata could not be upgraded messages.
Following is a printout of the error:
Please, someone, help with this issue.
Cause:
This is a Component Mismatch Exception.
The reason for this error is that the component was developed with a higher version of SQL Server Integration Services.
The server or workstation on which you are running or opening the SQL Server Integration Services Package contains an older version installed.
Since the downgrade of the component is not allowed, the Upgrade Process is triggered.
Unfortunately, the Upgrade Process was unsuccessful in reaching the goal.
Solution:
To fix this error, it is necessary to change the TargetServerVersion parameter to SQL Server 2012 in the SQL Server Integration Services 2012 project.
Right-click the project in the Solution Explorer and select Properties.
To display the TargetServerVersion option, go to Configuration properties and then General.
Deploy the entire project again, and this error will be resolved.
I hope this solution helps others who have this same error.
I have Visual Studio 2013 installed on machine in addition to MS SQL Server 2012. I used to use all the Business Intelligence projects in MS VS 2013 in a very normal way. However, recently when I created a new SSIS project and then clicked on the SSIS packages in order to create a new SSIS package, I got the following error:
Error creating package
------------------------------
ADDITIONAL INFORMATION:
Retrieving the COM class factory for component with CLSID {B5F5B1CF-7950-436C-B3BD-E193B1F5E5A5} failed due to the following error: 8007007e The specified module could not be found. (Exception from HRESULT: 0x8007007E). (Microsoft.SqlServer.ManagedDTS)
I hope the that the information I have provided are sufficient to explain my problem clearly.
I simply reinstalled the SSDT (SQL Server Data Tools), repaired my installed packages and the problem was solved.