March 15, 2018 at 11:23 am
Hi All,
I've been running into a boatload of issues when attempting to run a Master package via dtexecui.exe and also within BIDS. I'm not sure what's causing it, as I haven't made any changes to any versions. It appears to be erroring out on random child packages, so it's difficult to pinpoint what the cause is. The individual child packages run fine themselves, using dtexecui and within BIDS. I've tried reimporting the previous version of the Master package from our source control software and saving it to the solution file, but no good, as the errors persist. I've also tried recreating the file connection managers to the child packages that are erroring out, but that didn't fix it either. Here are the errors that are occurring from our error log table for ssis packages:
Beginning of package execution.
There was an exception migrating the package from version 3 to version 8. Exception information follows. System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.SqlServer.Dts.Runtime.Wrapper.IDTSInfoEvents100.FireInformation(Int32 InformationCode, String SubComponent, String Description, String HelpFile, Int32 HelpContext, Boolean& pbFireAgain)
at Microsoft.SqlServer.Dts.Runtime.PackageFormatUpdate.VersionUpdate.LogUpgradeStepInfo(Int32 code, String msg)
at Microsoft.SqlServer.Dts.Runtime.PackageFormatUpdate.VersionUpdate.VersionUpdate3or4to5()
at Microsoft.SqlServer.Dts.Runtime.PackageFormatUpdate.VersionUpdate.UpdateVersion(Int32 packageVersion, Int32 targetVersion, IDTSInfoEvents100 infoEvents, String& xmlDocument, String packagePassword, DTS_PACKAGE_UPGRADE_OPTIONS packageUpgradeOptions)
There was an exception migrating the package from version 3 to version 8. Exception information follows. System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.SqlServer.Dts.Runtime.Wrapper.IDTSInfoEvents100.FireInformation(Int32 InformationCode, String SubComponent, String Description, String HelpFile, Int32 HelpContext, Boolean& pbFireAgain)
at Microsoft.SqlServer.Dts.Runtime.PackageFormatUpdate.VersionUpdate.LogUpgradeStepInfo(Int32 code, String msg)
at Microsoft.SqlServer.Dts.Runtime.PackageFormatUpdate.VersionUpdate.VersionUpdate3or4to5()
at Microsoft.SqlServer.Dts.Runtime.PackageFormatUpdate.VersionUpdate.UpdateVersion(Int32 packageVersion, Int32 targetVersion, IDTSInfoEvents100 infoEvents, String& xmlDocument, String packagePassword, DTS_PACKAGE_UPGRADE_OPTIONS packageUpgradeOptions)
Package migration module has failed.
Package migration module has failed.
Package migration from version 3 to version 8 failed with error 0x80004003 "Invalid pointer".
Package migration from version 3 to version 8 failed with error 0x80004003 "Invalid pointer".
Error loading value "<DTS: Property xmlns: DTS="http://www.microsoft.com/SqlServer/Dts" DTS:Name="PackageFormatVersion">3</DTS: Property>" from node "DTS: Property".
Error loading value "<DTS: Property xmlns: DTS="http://www.microsoft.com/SqlServer/Dts" DTS:Name="PackageFormatVersion">3</DTS: Property>" from node "DTS: Property".
Error 0x80004003 while loading package file "D:\SFAS\SSIS\SESDatamart\packages\Load_DimProduct.dtsx". Invalid pointer
.
Error 0x80004003 while loading package file "D:\SFAS\SSIS\SESDatamart\packages\Load_DimProduct.dtsx". Invalid pointer
.
End of package execution.
Any assistance with this would be greatly appreciated, as I've been banging my head over this for a while and it's been preventing me to deploy to the higher environments. Thanks in advance!
March 20, 2018 at 10:08 am
Any suggestions are welcome....please?
March 30, 2018 at 11:18 am
Have you recently upgraded SQL Server versions? Also, the error message is suggestive of a package version issue, as if the version of the package file is just too old. What version of SQL Server BIDS was used to create the packages, and what version is being used currently?
Steve (aka sgmunson) 🙂 🙂 🙂
Rent Servers for Income (picks and shovels strategy)
April 10, 2018 at 8:44 am
Thanks for your reply, Steve. We haven't upgraded SQL Server or BIDS versions, which is why the error was so puzzling. It has since then resolved itself somehow...very strange. In any case, thanks for your reply. 🙂
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply