kmfkdreams.blogg.se

warning MSB3270: There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference " ,.Solution: Compile the extension with a platform target of ‘Any CPU’ and ignore the compiler warning (see below, I reached out to our Microsoft Premier Support rep, and after working with a Microsoft engineer, I was able to solve the problem. Error: The component metadata for ", clsid " could not be upgraded to the newer version of the component. In an SSIS package that targets SQL Server 2014 and is running in a Windows Server 2012 R2 environment? Is this possible? So, how do I program the custom component to work

Unfortunately, we do no have SQL Server 2016 installed. Note: I can also run other SSIS packages that target SQL Server 2014 WITHOUT the custom component just fine on the Windows Server 2012 R2 environment. When I upgrade the SSIS package's SQL Server Target Version to SQL Server 2016 then the However, when I deploy the same SSIS package and component to a Windows Server 2012 R2 environment, then I receive a PerformUpgrade error ( see error below). I deployed the SSIS package containing the custom component to both my local PC (Winidows 7 Pro) and a development server (Windows Server 2008 R2). I have added this custom component to an SSIS package that targets SQL Server 2014. This component converts specific string values to NULL. Using Visual Studio 2017, SSDT 15.3.0 Preview, I have created a simple Custom Component of the PipelineComponent variety. WHAT IS THE REQUIREMENT TO TARGET SSIS PACKAGES TO SPECIFIC WINDOWS VERSIONS?