Resposta Proposta ERROR SQLSTATE 42000 Error 15404

  • sexta-feira, 11 de dezembro de 2009 14:27
     
     
    Out of the blue I started getting this error trying to run a SQL Agent job:

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

    The SQL Agent service IS running as a domain user, which IS a member of Domain Users.  This job has run fine dozens of times and no domain changes have been made (other than retiring an old DC).  If I change the owner to SA, the job runs fine.  There appears to be a very serious bug in the wal SQL Server 2008 tries to verify domain accounts.

Todas as Respostas

  • terça-feira, 15 de dezembro de 2009 11:37
    Moderador
     
     
    Hi,

    From Raul Garcia in the other thread: http://social.msdn.microsoft.com/Forums/en-IE/sqlsecurity/thread/9dddf08e-929c-43b4-bc10-ac8f36cbb023
    -----------------------
    Most likely the machine account doesn’t have permission to query the AD. I would recommend requesting access to the AD administrator or change SQL Server and run the service as a low-privileged domain account that has proper permissions on the AD.
    ChunSong Feng
    Microsoft Online Community Support

    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    Welcome to the All-In-One Code Framework! If you have any feedback, please tell us.
  • terça-feira, 15 de dezembro de 2009 22:29
     
     
    Already checked this out, SQL Agent is already running as a domain account per my post
  • quarta-feira, 16 de dezembro de 2009 21:07
     
     
    I believe that ChunSong Feng was talking about the SQL Server service account, not SQL Agent, running as a domain account,. 

    RLF
  • sexta-feira, 18 de dezembro de 2009 07:01
     
     
    Hello,

    Better you configure your SQl server and SQL Server Agent with two separate account.

    Thanks

    Thanks

    Regards,
    RM Thirunavukkarasu MCP, MCITP
    http://www.thiruna.blog.com
  • sexta-feira, 2 de março de 2012 17:56
     
     Resposta Proposta

    In this case, you can create a job with the SQL agent service account as job owner and JOb steps can use AD account to run the job steps. This will resolve the problem.



    Thanks Ayyappan Thangaraj, http://SQLServerRider.wordpress.com