SSIS Package fails in SSMS but runs in Visual Studio

AjitNayak 21 Reputation points
2022-01-10T05:49:19.327+00:00

Package runs fine when I run it via Visual Studio but when calling it from the Jobs under SSMS, I get the following errors

  1. <message>Stream:Error: One or more component failed validation.</message>
  2. <message>Stream:Error: There were errors during task validation.</message>
  3. <message>Stream:Error: "Serialize" failed validation and returned validation status "VS_ISBROKEN".</message>
  4. <message>Stream:Error: The component metadata is out of sync with the compiled script. Recompile the script using the Script Component Editor.</message>

I saw some posts that suggested to change settings for runtime, delayvalidations and validateExternalMetadata and I modified all these settings but I still get the error. Weird part is, my colleague cloned my code and all he had to do was just open the packages in SSIS and save it and then push it to Git. It works like a charm.

Any help would be greatly appreciated, its consumed almost a week of my time.

Regards,
AN

SQL Server Integration Services
SQL Server Integration Services
A Microsoft platform for building enterprise-level data integration and data transformations solutions.
2,702 questions
0 comments No comments
{count} votes

Accepted answer
  1. ZoeHui-MSFT 41,491 Reputation points
    2022-01-10T06:18:26.24+00:00

    Hi @AjitNayak ,

    Please check the version of your SQL Server. You may use select @@version to get the information.

    Make sure in the Visual Studio the target server version is same as your sql server version.

    Right click on the project name, then choose Properties, Expand Configuration Properties, then click on General, and then choose the desired SQL Server Version for the TargetServerVersion property.

    If it does not work, open the package, and then click edit script, rebuild the code and save the package and re-deploy for a try.

    Or you may create a new package and then use the code to see if it could run successfully in SSMS.

    Regards,

    Zoe


    If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


1 additional answer

Sort by: Most helpful
  1. AjitNayak 21 Reputation points
    2022-01-11T20:16:36.81+00:00

    Thanks for your inputs @ZoeHui-MSFT , our sql server version is Microsoft SQL Server 2014 (SP3-CU4-GDR) (KB4583462) - 12.0.6433.1 (X64) Oct 31 2020 02:54:45 Copyright (c) Microsoft Corporation Developer Edition (64-bit) on Windows NT 6.3 <X64> (Build 9600: ) (Hypervisor)

    As for the incompatible project errors, I installed SSDT for 2017 and it fixed the issue. (it was previously installed but might have gotten deleted while I tried to reinstall SSIS 2017)

    Going back to the original issue, I have not tried pushing the changes to Dev from the 2017 SSIS as other tasks got piled up but will update this thread if that resolves my issue.

    Thanks again for your time and patience.

    -Ajit

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.