sql server - SSIS package upgraded by deployment -


In our QA virtual environment, which has multiple SQL Server, I have an SSIS 2012 package (ispac, project deployment) Visual Studio 2010 Made through Destination was SSIS Server 2012, but the client on the workstation was included in SQL Server 2014. Specified to execute the ISPAC package on the workstation and to deploy on SQL Server 2012, the deployment went without error, but when we executed the package on the SSIS server, we would like to

"package name" Receives: Error: The version number in the package is not valid. The version number can not be more than the current version number.

"Package Name": Error: Error loading error: "DTS: Property" from "8" node.

"Package Name": Error: Version 6 error with version 0xC001700A failed "Version number in package is not valid." The version number can not exceed the current version number. "

In all my packages (.dtsx)

  & lt; DTS: Property DTS: name = "Package format version" & gt; 6 & lt; / DTS: Property & gt;  

Also manifest

  & lt; SSIS: Property SSIS: Name = "PackageFormatVersion" & gt; 6 & lt; / SSIS: Property & gt;  

It seems that the SQL 2014 client or workstation has upgraded my package to V8, though my destination server was V6. When I directly deployed SQL Server 2012 (which was not SQL 2014) everything was deployed and ran as expected. Is this the expected result? Or a problem

So whatever you are experiencing is expected of the behavior citation needed . When any SSIS package is opened using API, the package is updated in that API version. This allows the V-1 package to run on a Vcurrent server, changes have been made in formats and items, so a 2014 package may be Maybe does not have reason to run on the 2014 box, but this is the intention The bits on the disc remain unchanged but the in-memory version is updated.

Since the ISDAPPad Wizard was used in 120 Folder (SQL Server 2014) in the deployment, the first time it happened when it looked at the 2012 version of .ispac, it was converted to the 2014 format . Therefore, the in-memory version of this ISPAC will be serialized in SSIDB and those APIs are similar between 2012/2014. The DeployProject / deploy_project method only takes a binary object, which version does not have any recognition of those bits, this is just the right size.

But, you go to execute the package, that happens when the API needs to see the actual bits there and it shows, this is a version I can not understand I am

Some examples that appear on that API


Comments

Popular posts from this blog

python - Overriding the save method in Django ModelForm -

html - CSS autoheight, but fit content to height of div -

qt - How to prevent QAudioInput from automatically boosting the master volume to 100%? -