February 16, 2016 at 5:00 am
Hi All
Having fun with a CmdExec job step.
Trying to run an exe from a network share via a job but constantly receiving
"The process could not be created for step 2 of job 0x3ABDCCFC6D54F54289ACC5F50F74158A (reason: Access is denied). The step failed."
The agent has execute rights to the network share and the application, I have also created a credential and proxy for my domain admin account and mapped that to the job step but still receiving the same error.
I have a feeling its down the UAC, but cant figure out how to get around it.
Any light on getting this resolved would be greatly appreciated.
Thanks
Ant
February 16, 2016 at 8:20 am
What does the step do? If you log in to a console of the server as your proxy and execute the code in the step, what happens? Not the step, re-run the code in some other manner.
February 22, 2016 at 2:08 am
Sorry the reply email went into my Junk folder.
The step is just a simple execute an exe from a network location \\Server\Share\app.exe, running this via CMD as the domain admin proxy account works as needed.
I have tried as a powershell script and eventually got it to work using a SSIS execute process task package instead.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply