Sign in
 
Home20122008 R2200820052000LibraryForums
SQL Server >
> 
> 
SQL Job error: error code 0x5. [SQLSTATE 42000] (Error 15404)).

Answered SQL Job error: error code 0x5. [SQLSTATE 42000] (Error 15404)).

  • Monday, May 07, 2012 7:01 PM
     
     
    Sign In to Vote
    0

    I'm currently receiving the following error when I setup a new job and run it.


    Message
    The job failed.  Unable to determine if the owner (DOMAIN\USERB) of job OppInfo has server access (reason: Could not obtain information about Windows NT group/user 'DOMAIN\USERB', error code 0x5. [SQLSTATE 42000] (Error 15404)).


    I would like to use two domain accounts and not use any local accounts. The first account (DOMAIN\USERA) will be used to to run the SQL Server Agent.  The second account (DOMAIN\USERB) will be setup as the owner of the job.


    Currently, UserB is under the local administrator group with dbo permissoins to the master and msdb database.  UserB also has dbo permissions to the database where the job makes the updates.

    What permissions do I need to give UserB in order to overcome the above error?


    • Edited by Luhem181 Monday, May 07, 2012 7:03 PM
    •  
     

All Replies

  • Monday, May 07, 2012 8:07 PM
    Moderator
     
     Answered
    Sign In to Vote
    2

    Hello,

    Error 0x5 means access denied.

    Try to changing the owner of the jobs to the sa account, on the properties of the job.

    If the above does no help, please change the service account for the SQL Server agent service to account with proper permissions. This may be happening because the service account for SQL Server Agent service is a local account. Try starting the service with a domain account.

    http://technet.microsoft.com/en-us/library/ms345578.aspx

    Hope this helps.


    Regards,
     
    Alberto Morillo
    SQLCoffee.com

     
  • Thursday, May 10, 2012 1:29 AM
     
     
    Sign In to Vote
    0
    Change the owner for some user tath has Sysadmin Server rol.

    Carlos Ignacio Aguero. DBA SQL Server. Toda mi respeto al pueblo Peruano por la ayuda prestada en la guerra de Malvinas.

     
  • Thursday, May 10, 2012 8:59 AM
    Moderator
     
     
    Sign In to Vote
    0
    It's something where your service account is not able to validate UserB's credential hence you are getting this error. I hope your service account doesn't have enough permission in AD to query for the user.

    Mark as ANSWER if I helped you today :-) www.sql-articles.com