This project has moved. For the latest updates, please go here.
2
Vote

SSIS PackageFormatVersion in wrong location

description

When generating an SSIS package from my BIML script, the tag <DTS:Property DTS:Name="PackageFormatVersion">6</DTS:Property> is generated towards the end of the file, right before the variables. This prevents the package from being loaded into a SQL Server Agent Job. A generic error about the package being unable to load occurs and doesn't tell you why.

Eventually I found that moving it to the beginning of the file as the first child of the <DTS:Executable> tag solved the problem.

I am unable to find anything that I can do in my script to cause this property to be written in the correct location for the package to be loaded into the SQL Agent.

I can open the package and run it directly in Visual Studio without making the change. It seems to be only affected when scheduling with the SQL Agent.

BIDS Helper 2012 v1.7
Visual Studio 2010
SQL Server (Agent) 2012

comments

DonnOMalley wrote Jul 27, 2016 at 2:59 AM

Turns out. As long as the <DTS:Property DTS:Name="PackageFormatVersion">6</DTS:Property> tag is placed before the precedent constraints and variables tags, the package will load into the SQL Agent Job.

DonnOMalley wrote Jul 27, 2016 at 3:02 AM

I found that as long as the <DTS:Property DTS:Name="PackageFormatVersion">6</DTS:Property> tag is before the <DTS:PrecedenceConstraints> and <DTS:Variables> tags the package would load into the SQL Agent Job.

Configurations, Connections and Executables could all be above the Property and it would load correctly.

fmoeller wrote Jul 28, 2016 at 6:00 PM

Hi,

I have experienced the same, see https://connect.microsoft.com/SQLServer/feedback/details/2621473/ssdt-bi-2015-does-not-open-package-which-works-flawlessly-in-ssdt-bi-2012

You cannot edit the packages of BIDShelper with VS2015 unless you move the PackageFormatVersion...

I have reported this to Varigence right after the bug got closed by Microsoft.

wrote Sep 11 at 12:57 PM

DocCodePlex wrote Sep 11 at 1:01 PM

+1

Couldn't design ETL package in Visual Studio 2015/2017. Loaded fine in Visual studio 2012/2010.

Moved up the PackageFormatVersion tage and it loaded....