August 13, 2015 at 1:11 am
I have a package deployed in SSIS 2012 catalog. It is working fine when called from agent job but when it fails when called directly from catalog.
The package is failing on script task which is trying to create a directory.
other info:
1) I am using same account for executing the package from job and directly.
2) The account has all the necessary permission on the folder
3) I tried running the package in 32 bit mode
4) I tried redeploying the package
But none of the above worked for me.Any help would be much appreciated.
Pramod
SQL Server DBA | MCSE SQL Server 2012/2014
in.linkedin.com/in/pramodsingla/
http://pramodsingla.wordpress.com/
August 13, 2015 at 10:30 pm
following is the link of the discussion that I had with Arthur on MSDN forum
Pramod
SQL Server DBA | MCSE SQL Server 2012/2014
in.linkedin.com/in/pramodsingla/
http://pramodsingla.wordpress.com/
August 13, 2015 at 11:17 pm
If you are running an Integration Services package from within Management Studio, it's going to run under the account you connect to the server with via SMSS, but when you run the SQL Server Agent job from Management Studio, it will run under the SQL Server Agent account.
The scenario you described was almost the same as the one I found only two days after starting a new job. Make sure the account you are using to connect to the server has the appropriate permissions in the parent folder, and then run the SSIS package again.
August 14, 2015 at 1:10 am
i am using proxy account in the job and its the one which i am using to connect to the catalog.
Pramod
SQL Server DBA | MCSE SQL Server 2012/2014
in.linkedin.com/in/pramodsingla/
http://pramodsingla.wordpress.com/
August 14, 2015 at 4:56 am
psingla (8/13/2015)
following is the link of the discussion that I had with Arthur on MSDN forum
It appears from the above thread that this may not be solveable without MS's intervention. But...
Can you post the exact text of the error message when calling it from the system catalog?
August 14, 2015 at 5:41 am
Brandie Tarvin (8/14/2015)
psingla (8/13/2015)
following is the link of the discussion that I had with Arthur on MSDN forumIt appears from the above thread that this may not be solveable without MS's intervention. But...
Can you post the exact text of the error message when calling it from the system catalog?
Thanks Brandie for looking into this.Following is the exact problem that others are also facing.Perhaps I should open a ticket with MS.
Pramod
SQL Server DBA | MCSE SQL Server 2012/2014
in.linkedin.com/in/pramodsingla/
http://pramodsingla.wordpress.com/
August 14, 2015 at 5:49 am
psingla (8/14/2015)
Brandie Tarvin (8/14/2015)
psingla (8/13/2015)
following is the link of the discussion that I had with Arthur on MSDN forumIt appears from the above thread that this may not be solveable without MS's intervention. But...
Can you post the exact text of the error message when calling it from the system catalog?
Thanks Brandie for looking into this.Following is the exact problem that others are also facing.Perhaps I should open a ticket with MS.
Sorry, but I don't have time to go hunting all over the internet. If you can post your error here instead of redirecting me to other places, I will try to help.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply