July 25, 2013 at 3:47 am
Hi to everyone,
I have the issue below: I have an ssis package built in VS 2008, which is being called from SSMS 2008 through an sql job. The job runs with an sql proxy account and is being executed normally.
On another server with SQL 2012, the same ssis package has been upgraded with VS 2010 to 2012, the job has been generated from 2008 and has been setup to be called through SQL 2012 with the new parameters and, even though the ssis package is executed normally in VS 2010, when I call it through the job it won't be executed, and I get the following error: "Exception has been thrown by the target of an invocation." This seems to be a security issue.
The package is also executed successfully through command line (C:\Windows\system32>dtexec /FILE "\"E:\Package.dtsx\"" /CHECKPOINTING OFF /REPORTING EW).
Let me inform you that the sql proxy account has been configured to the new server and the job runs with this account.
I would appreciate any help and directions.
Thanks a lot.
July 25, 2013 at 4:43 am
How are you trying to execute the package in SQL Server 2012?
Is the package using the project deployment model or the package deployment model?
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
July 25, 2013 at 7:06 am
I assume it's the package deployment model.
July 25, 2013 at 7:43 am
You can't use the new parameters in the package deployment model.
How did you configure the job?
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
July 25, 2013 at 8:09 am
The way it was configured as well in SQL 2008 R2.
The job actually does not overwrite any parameters within the ssis package, all parameters are being configured within the ssis, the job just calls ths *.dtsx file.
July 25, 2013 at 1:36 pm
jochr23 (7/25/2013)
The way it was configured as well in SQL 2008 R2.The job actually does not overwrite any parameters within the ssis package, all parameters are being configured within the ssis, the job just calls ths *.dtsx file.
If the package contains parameters, it is using the new project deployment model.
Did you deploy the package to the SSIS catalog or to the MSDB database?
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply