July 8, 2013 at 6:10 am
Hi
We use a Central Management Server to target multiple servers with various jobs. I have created a multi server job, and selected the required target servers from the 'target servers' section.
The job has only been 'picked up' and listed in one server out of 20 ie when i look in the sql server agents\jobs folder.
I remember we had a similar issue a while back whereby disabling a job on the CMS didnt disable the job on the target server and we had to defect/re-enlist it.
Can anybody advise on why the jobs are not appearing on the target servers and do i have to do the 'defect - renlist' method again. Is there anything else i need to check to stop this happening ?
July 8, 2013 at 3:07 pm
Hello.
I have managed to fix the problem. If anybody has got a problem with Multi server jobs using a CMS where the status says blocked then read on....
In the end this was a simple fix - I didn't need to go down the path of defecting and then re-enlisting target servers. I simply removed the recent multi server job that i had added and then the 'blocked' status disappeared without me having to do anything else.
It turns out the job i created didn't have the required privileges and hence the blocked status
Hopefully this post will save somebody some valuable time !:-)
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply