SSIS Version Error - Not the 2005 to 2008 one
My desktop machine is running Sql 2008 SP2. The test and prod servers are on SP1, could that cause the semi-infamous "The version number in the package is not valid" error? In all my searches, the only problems are related to trying (or accidentally) running a 2008 package on 2005. Does anyone know? We can recreate the package on an SP1 machine, but I would think it would be compatible within the same major version. Any help is appreciated! I program in C#... but I can't bring myself to retire the 10 year old vbSlinger moniker...
April 20th, 2011 12:02pm

You are trying to execute this package using the 2005 version of DTExecArthur My Blog
Free Windows Admin Tool Kit Click here and download it now
April 20th, 2011 1:20pm

The ssis package on SQL SP2 is not compatible with SP1 becasue SP2 is considered to be a higher version than SP1 and SSIS does not have forward compatibility. The version number for SP2 is 10.00.4000.00 and for SP1 is 10.00.2531.00. Keerthi Kiran Senior Consultant
April 20th, 2011 1:20pm

Thanks Arthur, but we do not believe that is the case. The SQL Agent is using an explicit path.I program in C#... but I can't bring myself to retire the 10 year old vbSlinger moniker...
Free Windows Admin Tool Kit Click here and download it now
April 20th, 2011 1:37pm

We figured as much, but honestly were a little surprised. Guess we'll redo it, thanks.I program in C#... but I can't bring myself to retire the 10 year old vbSlinger moniker...
April 20th, 2011 1:38pm

I just checked that even though the version of the SQL Server engine is carrying a new (higher) number after applying the SP2 the SSIS version does not change between these service packs, it remains at 10.0.1600.22. I have also created a package on the SP2 machine and successfully deployed to SP1 one, no problem. There is a little controversy about reflecting the SSIS version number after the SPs were applied and a MSDN article to determine the version is missing for SQL Server 2008 SSIS: http://support.microsoft.com/kb/942177 Btw, I used the method #2 to check for versions using MsDtsSrvr.exe in the DTS/Binn folder. Arthur My Blog
Free Windows Admin Tool Kit Click here and download it now
April 20th, 2011 2:38pm

As a note, this was in fact the 2005 error. It really was a comedy of errors. This is one good case for not running 12 instances of SQL spread among multiple instances on one box.I program in C#... but I can't bring myself to retire the 10 year old vbSlinger moniker...
April 21st, 2011 3:59pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics