Error when adding SSIS package to SQL Agent job in SQL Server 2008R2
Hi,
I have built an SSIS package in VS2017 which runs fine in Debugger mode.
I am trying to call the package from a SQL Server Agent job that sits on a SQL Server 2008R2.
Using SSMS on the 2008R2 Server I am trying to load the Package from the File System into the job but when I try to add the Package , I get the following error
I have built an SSIS package in VS2017 which runs fine in Debugger mode.
I am trying to call the package from a SQL Server Agent job that sits on a SQL Server 2008R2.
Using SSMS on the 2008R2 Server I am trying to load the Package from the File System into the job but when I try to add the Package , I get the following error
TITLE: SSIS Execution PropertiesAny guidance appreciated
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.
ASKER
Hi Nakul,
thank you for your comment,
am not using 3rd party components.
I'm wondering if the issue is somehow related to the package being developed in VS2017 and deployed on SQL Server 2008R2?
thank you for your comment,
am not using 3rd party components.
I'm wondering if the issue is somehow related to the package being developed in VS2017 and deployed on SQL Server 2008R2?
That may be. If you check the properties of your SSIS project, you should see the option to target the packages to a specific minimum SQL Server version.
However, if this were the case, I would have expected an error after the package was loaded. This particular error that you are encountering indicates that the package itself failed to load. Hence, the first thoughts go to some missing dependency on the server.
However, if this were the case, I would have expected an error after the package was loaded. This particular error that you are encountering indicates that the package itself failed to load. Hence, the first thoughts go to some missing dependency on the server.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Thank-you for the update. It will be helpful to others as well who land up on this question.
The solution indicates that it was indeed the target SQL version of the project that was causing the issue.
The solution indicates that it was indeed the target SQL version of the project that was causing the issue.
Typically, this indicates that SQL encountered a reference in the SSIS package (which is ultimately an XML) but was unable to resolve it because the 3rd party component is not installed on the server where the package is running.