start job

Last Post 04 Mar 2012 05:50 PM by russellb. 6 Replies.
AddThis - Bookmarking and Sharing Button Printer Friendly
  •  
  •  
  •  
  •  
  •  
Sort:
PrevPrev NextNext
You are not authorized to post a reply.
Author Messages
dbandee
New Member
New Member

--
28 Feb 2012 11:54 AM
ok, i have been pulling my hair for last two days we have this setup all over our domain every night one of the backup jobs doe bak, copy to test box and starts restore job on test server. have dozens of these jobs, have been working fine for very long time untill now; all of a sudden i started gettign "permissions denied on sp_start_job" for one account; as far as i know nothing changed, the acct is sys admin on both prod and dev server, same acct owns both jobs; So this works from ServerA to ServerB using same acct, but fails from ServerC to ServerB. any thoughts. thanks
rm
New Member
New Member

--
28 Feb 2012 01:23 PM
Change job owner to sa then try again. If works, that's job owner permission issue.
dbandee
New Member
New Member

--
01 Mar 2012 05:51 AM
i did try that and it failed with the same error.
it is calling the job on serverB using sql agent account of serverA
so the problem is on serverB, i think, because serverA job fails saying the login can not start the job on serverB because it does not have permissions to sp_start_job
and it is sysadmin. it almost seems like login's sid got corrupted or something
it is sysadmin but it is not being seen as sysadmin
PaulMcKibben
New Member
New Member

--
01 Mar 2012 02:16 PM
Is it possible that the server policy has been changed?

rm
New Member
New Member

--
02 Mar 2012 06:00 AM
>> it is sysadmin but it is not being seen as sysadmin

Maybe it was sysadmin but not anymore.
johnlynn
New Member
New Member

--
02 Mar 2012 07:51 PM
I think in order to figure this out we need to see the whole permission denied message - it should be something like "permissions denied on sp_start_job - database xxxx" <- it's this xxxx (the database where the permission denied is coming from) that's important.
russellb
New Member
New Member

--
04 Mar 2012 05:50 PM
No. sp_start_job only exists in msdb. Doesn't matter what db you call it from.

dbandee, tried creating a new account to run the jobs?

if sa can't run it either, it's not likely a problem with the account, but I would test a new account anyway.
You are not authorized to post a reply.

Acceptable Use Policy