Danni juhl

My feedback

  1. 7 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Azure Backup » SQL in IaaS VM  ·  Flag idea as inappropriate…  ·  Admin →
    Danni juhl supported this idea  · 
  2. 463 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  94 comments  ·  SQL Server » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    Danni juhl supported this idea  · 
  3. 12 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  SQL Server » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Danni juhl commented  · 

    Based on the description above, I'll assume the issue I'm experiencing is caused by the same rootcause.
    If a seperate post is required, I'll happily do so.

    OS: Windows 2016
    SQL: 2016 Developer
    SSDT: 17.4
    Project Target Server Level: 2016

    I'm experiencing issues with Package Deployment on any packages that contains a script component.
    By rightclicking -> Deploy in VS, the deployment completes succesfully, however the package fails on execution with error message:

    Microsoft.SqlServer.Dts.Pipeline.ComponentVersionMismatchException: The version of Script Component 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. This package was probably created on a new version of DTS or the component than is installed on the current PC.]]
    at Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostCheckAndPerformUpgrade(IDTSManagedComponentWrapper100 wrapper, Int32 lPipelineVersion)The component metadata for "Script Component" could not be upgraded to the newer version of the component. The PerformUpgrade method failed.
    The component metadata for "Script Component" could not be upgraded to the newer version of the component. The PerformUpgrade method failed.
    The component is missing, not registered, not upgradeable, or missing required interfaces. The contact information for this component is "Includes and runs custom script code. For example, apply a business rule that limits the range of valid values in an "income" column or add values in two columns and calculate the average of the sum.;Microsoft Corporation; Microsoft SQL Server; Microsoft Corporation; All Rights Reserved; http://www.microsoft.com/sql/support;8".
    Script Component - {Task inside Component} failed validation and returned error code 0xC0048021.
    One or more component failed validation.
    There were errors during task validation.
    Package failed validation from the ExecutePackage task. The package cannot run.
    Error 0xC0012050 while executing package from project reference package "{PACKAGENAMEREVOKED}". Package failed validation from the ExecutePackage task. The package cannot run.

    Upon further investigation, I've found that SSDT 17.4 uses a selfpackaged version of ISDeploymentWizard found at "C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\Extensions\Microsoft\SSIS\140\Binn\ISDeploymentWizard.exe", which is the version shipped with SSMS 17.0+.
    SSDT 16.5 however, uses the wizard found at "C:\Program Files(x86)\Microsoft SQL Server\130\DTS\binn\ISDeploymentWizard.exe".

    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.

    Workaround:
    There's two ways:
    1.)Uninstall SSDT 17+, and install SSDT 16.5 instead. The issue no longer persists when using this version.
    2.)Continue using SSDT 17+, and deploy only projects. Only individual package deployment fails.

    Danni juhl supported this idea  · 

Feedback and Knowledge Base