Post reply

YV Alert: Jobs started to Fail for owners with group membership permissions

  • December 8, 2006 at 10:44 am

    #62141

    Hello,

    We discovered a recent problem that affects servers with different jobs. Some jobs on at least 2 servers stopped running 2 days ago after the site server reboot  for the job owners who did not have explicit login in SQL Server but rather were sysadmins through their membership in Administrators and Builtin\Administrators. These jobs ran successfully for months and the servers were rebooted before on a regular basis.

    Error message in the Job History on the job startup: "The job failed.  The owner () of job DB Backup 'MyDB maintainance Plan' does not have server access."

    The fix is to reset the job owner to somebody else, to SA or other SQL Server explicitly defined login.

    We do know that prior to the server reboot a couple of days ago we did have some recent Windows patches installed and the reboot completed the patch installation process. After that jobs with owners who did not have explicit login started to fail.

    I did find several posts on Microsoft forums with similar problem, but I did not find any support article on this. The jobs that fail for us are not just Maint. Plan jobs, other jobs as well. In effect, the job does not go as far as to execute the first step.

    Regards,Yelena Varsha

  • December 11, 2006 at 8:00 am

    This was removed by the editor as SPAM

  • December 11, 2006 at 8:47 am

    #677228

    Yelena,

    I've run into this as well with no solution. Rather than burn the call to PSS, I've just reset them to sa everytime I edit them. That's usually where the owner switches and then on reboot it stops working.

  • December 11, 2006 at 9:14 am

    #677239

    Steve,

    Thanks for confirming that it is the issue. 

    What happened to the concept of the group / role based access?

    I do agree with you about setting the job owner to SA or other Standard login even if for no other reason than domain controller or domain not being available to validate the Windows login. But many developers probably don't even know that when they schedule a package for example, the job owner is themselves and the job is created and managed in the Jobs.

    Regards,Yelena Varsha

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply