Posted Wed, 15 Jul 2020 17:10:52 GMT by
Can you please advise the cause and resolution of the below compiler error:
    
(BimlCompilerBuild target) ->
MSBUILD : error : Error:: Metadata file 'Microsoft.SqlServer.DTSPipelineWrap, Version=14.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91, processorArchitecture=MSIL' could not be found 
[C:\Users\xxx\Documents\xxx\output\xxx.mst.ProjectView.bimlproj]
MSBUILD : error : Error:: Metadata file 'Microsoft.SqlServer.DTSRuntimeWrap, Version=14.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91, processorArchitecture=AMD64' could not be found 
[C:\Users\xxx\Documents\xxx\output\xxx.mst.ProjectView.bimlproj]
MSBUILD : error : Error:: Metadata file 'Microsoft.SqlServer.PipelineHost, Version=14.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91, processorArchitecture=MSIL' could not be found 
[C:\Users\xxx\Documents\xxx\output\xxx.mst.ProjectView.bimlproj]
MSBUILD : error : Error:: Metadata file 'Microsoft.SqlServer.TxScript, Version=14.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91, processorArchitecture=MSIL' could not be found 
[C:\Users\xxx\Documents\xxx\output\xxx.mst.ProjectView.bimlproj]
MSBUILD : error : Fatal:: Internal Compiler Error: Workflow EmitSsis contains fatal errors. Phase execution halted. For assistance, please send Biml Compiler error messages to support@varigence.com. See other errors for more information. 
[C:\Users\xxx\Documents\xxx\output\xxx.mst.ProjectView.bimlproj]
    0 Warning(s)
    5 Error(s)
 
Posted Fri, 17 Jul 2020 00:02:00 GMT by
This error occurs when using scrip components and script tasks. 
        
What is actually going on, is that there is a mismatch between the version of SSIS installed on your machine and the version of SSIS that is compatible with the version of SQL Server that your project is targeting.

The most common example of this would be someone that is using Visual Studio 2017 (VS2017), and has the appropriate SSIS installed for VS2017 but is targeting SQL Server 2014 with his project in BimlStudio.

There are two easy solutions to fix this problem:
    
The first is to change the target version of SQL Server to a compatible version.

In the case described above, that would mean changing the target version from SQL Server 2014 to SQL Server 2016 or SQL Server 2017. 
This is because the versions of SSIS that work for VS2017 are compatible with those versions of SQL Server.
    
The second solution is to download the appropriate version of SSIS. So for the example above, you would need to install the version of SSIS designed for the version of Visual Studio that is compatible with the target server version. 

This link https://sqlstudies.com/2015/04/27/what-sql-version-is-my-ssis-package/ has a great chart that shows which versions of Visual Studio match with which versions of SQL Server.

You must be signed in to post in this forum.