So, obviously this happens when SQL Server 2008 is running along with SQL Server 2005 on the same machine. That means, the exe shipped with 2005 is picked up when it is expected to use the one shipped with 2008. Reason for the error: Old version of the DTEXEC is picked up by SQL Server instead of the new one. This occurs when CPackage::LoadFromXML fails.Īha! Could these be the underlying issue(s)? At least I had a different path to look down.Īccording to the blog post the problem is this This message is used as a return value from functions that encounter errors.”. There should be more specific errors preceding this one that explains the details of the errors. The version number cannot be greater than current version number.”.Įrror 3: Error loading CleanStagingTables.dtsx: Error loading value “3” from node “DTS:Property”.Įrror 4: Error loading ‘CleanStagingTables.dtsx’ : The package failed to load due to error 0xC0010014 “One or more error occurred. The version number cannot be greater than current version number.Įrror 2: Error loading CleanStagingTables.dtsx: Package migration from version 3 to version 2 failed with error 0xC001700A “The version number in the package is not valid. That is when I got these errors Įrror 1: Error loading CleanStagingTables.dtsx: The version number in the package is not valid. I was working remotely but that was the only similarity.įor some reason I tried to open the dtsx file in the Deployment folder. So I changed it to DontSaveSensitive just to see if somehow I had changed it in my sleep. I had not changed that, (at least not that I remembered). It was set to the default of EncryptSensutiveWithUserKey. On Tweet mentioned the Security Protection level. I also posted the error in several forums still thinking someone has run into this before. I sent a Tweet to some SSIS people and to the #ssis list. After finding several posts in forums by others dating as far back as 2005 I did not find anything to indicate what was wrong or what else to investigate.
Surely someone had run into this issue before. I then went to Google to see what information was out on the web for this error. So, I reverted the change and tried to deploy again.
My code had not changed except for the minor update I just performed. This occurs when CPackage::LoadFromXML fails. No further detailed error information can be specified for this problem because no Events object was passed where detailed error information can be stored.”. The package failed to load due to error 0xC0011008 “Error loading from XML. When this error popped up after another change and tried to redeploy. I just need to document the information for turnover and wanted to confirm all was still working.
After creating two separate packages, one for the import and one to clean out the tables as I was testing the import successfully I knew I was going to have to update some the components in the package after moving it to the remove development box used by the dev team.Īfter copying the files from my laptop to the remote server, running them, making a few changes here and there and getting them to work like they were designed I reported in our morning standup meeting I was 95% complete. I first developed the packages locally on my laptop using 2008 versions of SQL Server and SSIS. Background: While working on a small SQL Server Integration Service project I ran into this problem.