SSIS :- Exception – Microsoft.SqlServer.Dts.Pipeline.ComponentVersionMismatchException

Background

Deployed a new SSIS package.

It is time to test it out.

But, really having problems.

Error

Error Text


OriginalReference Transformation:Error: The component metadata for "OriginalReference Error Dump Generator"
could not be upgraded to the newer version of the component. The PerformUpgrade method failed.

OriginalReference Transformation:Error:
Microsoft.SqlServer.Dts.Pipeline.ComponentVersionMismatchException: The version of OriginalReference Error
Dump Generator is not compatible with this version of the DataFlow. [[The version or pipeline version or both for the
specified component is higher than the current version.

Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostCheckAndPerformUpgrade
(IDTSManagedComponentWrapper100 wrapper, Int32 lPipelineVersion)<span id="mce_SELREST_start" style="overflow:hidden;line-height:0;"></span>

Error Image

dataOrPipelineVersionIsGreater.01.20190823.0656AM.png

Troubleshooting

Googled for help.

Landed @

Title :- Deploying single SSIS package to SQL 2016 from SSDT 17.0-17.4
Description :- Deploying a single SSIS package with VB script task, targeted for SQL 2016 from SSDT 17.0-17.4 causes the script tasks to not execute but the package deploys and executes reporting success. .
Link :- Link

Contributor

Danni juhl

Danni juhl commented · January 19, 2018

I’ve previously seen issues with installations where both SQL 2016 SSMS and 17+ SSMS are installed, where doubleclicking an *.ispac opens it by default with the 140 Deployment Wizard, and thus failing on script components.

Based on this, I believe the issue being in the DeploymentWizard shipped with 17+, which isn’t backwards compatible with SQL 2016.

Remediation

My issue is that I have a few versions of SQL Server Management Studio ( SSMS ) installed on the machine.

The SQL Server instance I targeted version’s number is 2014.

But, the client I am using is running 2017.

To remediate :-

  1. Launch SQL Server Management Studio ( SSMS ) that matches your server version
    • In our case our server is v2014, launched SSMS v2014
  2. Overwrite previously deployed package with same one
    • The only difference is that we are using matching version number

 

Dedicated

Dedicating to my tokayo, Danni Juhl.

 

Community

No doubt, I was down on myself on this one.

But, then the community came through.

Here is to the Microsoft Community.

I only write for one thing.  The community.

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s