September 13, 2018 at 3:11 pm
Hello, I have an odd event that happened, and I've seen it once before recently.
I have a package, I own it, my ID is on it, and I deployed it. I also have a model that it loads, I own it too, I deployed it as well. I created a job, also under my ID, and set it all up. This job runs the package and loads the cube weekly without fanfare.
Today, after the job ETL'd out data, and began to load the model, and it failed at due to permissions denial, does not have permissions to that database (cube). I look, and it was another users ID. I go through the job, package and model and it is my ID that shows as owner. Yet if I start the job, singed in and being on my own ID, it will show this other ID as the owner when that job is running.
I contacted that user and asked what he's been doing, running a job that is his, has nothing to do with my mode, package or job a all.
I think somehow when he logs on the server to manually run his job, while its running, it somehow gets its wires crossed with my job. Yet, I can go to SSISDB and manually execute just the package, and its my ID as owner when it's running.
Has anyone else seen, heard or experienced this oddity themselves, and what was the fix?
Thanks
September 14, 2018 at 6:54 am
Do you maybe have a Proxy SSIS Execution Account set up?
September 14, 2018 at 8:29 am
DinoRS - Friday, September 14, 2018 6:54 AMDo you maybe have a Proxy SSIS Execution Account set up?
I found the issue, I had one package that had the wrong proxy set to it, and that was the cause of the problem
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply