November 12, 2010 at 7:32 pm
First I almost never use the environment variable as a config location, the main reason is that it is difficult to version control, a little more complex to set and occasionally requires either a reboot of SQL or the server when you set it or change it.. Mileage may vary.
It is not a good idea to run SQL as LocalSystem. It can limit some functionality, it prevents the use of trusted connections to other servers. There are others but thats the first one that comes to mind. Create a user account and have SQL & SQL Agent run as that account. The only upside to LocalSystem is that it can access almost anything on the local machine.
CEWII
November 15, 2010 at 9:06 am
I searched a lot online, and followed the procedures...even though I still get this when I try to schedule a job in agent job:
===================================
The package failed to load due to error 0xC0010014 "One or more error occurred. There should be more specific errors preceding this one that explains the details of the errors. This message is used as a return value from functions that encounter errors.". This occurs when CPackage::LoadFromXML fails.
------------------------------
Program Location:
at Microsoft.SqlServer.Dts.Runtime.Application.LoadPackage(String fileName, IDTSEvents events, Boolean loadNeutral)
at Microsoft.SqlServer.Dts.Runtime.Application.LoadPackage(String fileName, IDTSEvents events)
at Microsoft.DataTransformationServices.Controls.PackageProtectionUtils.<>c__DisplayClass4.<LoadPackageFromFile>b__3(String password, IDTSEvents events)
at Microsoft.DataTransformationServices.Controls.PackageProtectionUtils.LoadPackageWithPassword(PackageLoader loader, IWin32Window dialogParent, String& packagePassword)
at Microsoft.DataTransformationServices.Controls.PackageProtectionUtils.LoadPackageFromFile(String file, IWin32Window dialogParent, String& packagePassword)
at Microsoft.DataTransformationServices.DTSExecUI.Controls.GeneralViewCtrl.GetPackage()
===================================
The package failed to load due to error 0xC0010014 "One or more error occurred. There should be more specific errors preceding this one that explains the details of the errors. This message is used as a return value from functions that encounter errors.". This occurs when CPackage::LoadFromXML fails.
------------------------------
Program Location:
at Microsoft.SqlServer.Dts.Runtime.Wrapper.ApplicationClass.LoadPackage(String FileName, Boolean loadNeutral, IDTSEvents90 pEvents)
at Microsoft.SqlServer.Dts.Runtime.Application.LoadPackage(String fileName, IDTSEvents events, Boolean loadNeutral)
I changed the DBconfig file's pass in SSIS package, changed the creator name to match production server's windows authentication, create the agent proxy, which the principle is production server's windows authentication and point to sa, windows authentication, and modify the windows authentication account to the target database catalogs and make it as sysadmin, edit windows authentication account, SQLagentuser, SQLserveruser to have fully control of SSIS directory, use Don'tSaveSensitivity and load config file.....
Any thoughts?
November 15, 2010 at 11:49 am
I tried everything I could to make sure the permission issue, still got the error message that I couldn't load the package!
Then I tried to use comdexe to execute the package, then I found this:
Description: The version number in the package is not valid. The version number cannot be greater than current version number.
Description: Package migration from version 3 to version 2 failed with error 0xC001700A "The version number in the package is not valid. The version number cannot be greater than current version number.".
Description: Error loading value "<DTS:Property xmlns:DTS="www.microsoft.com/SqlServer/Dts" DTS:Name="PackageFormatVersion">3</DTS:Property>" from node "DTS:Property".
Could not load package "E:\*.dtsx" because of error 0xC0010014.
Description: The package failed to load due to error 0xC0010014 "One or more error occurred. There should be more specific errors preceding this one that explains the details of the errors. This message is used as a return value from functions that encounter errors.". This occurs when CPackage::LoadFromXML fails.
So I searched again, which it might be the case that I developed the SSIS package on BIDS 2008 which by default demands SQLServer 2008? and I did try on local which is SQL2008 and failed on Production server with SQL2005....could this might be the reason SQL Agent job couldn't load the SSIS package?
November 16, 2010 at 11:16 am
princa (11/15/2010)
So I searched again, which it might be the case that I developed the SSIS package on BIDS 2008 which by default demands SQLServer 2008? and I did try on local which is SQL2008 and failed on Production server with SQL2005....could this might be the reason SQL Agent job couldn't load the SSIS package?
You can't run a SQL Server 2008 package through SQL Server 2005 Job Agent.
Viewing 4 posts - 16 through 18 (of 18 total)
You must be logged in to reply to this topic. Login to reply