none
SQL Server Agent Scheduled Job Error 0x6ba

    Question

  • Hi,

    Does anyone know what caused the error, and more importantly what can I do to prevent the error from occuring again?

    Date  10/02/2010 18:30:00
    Log  Job History (DataQualityHist)

    Step ID  0
    Server  myServer
    Job Name  DataQualityHist
    Step Name  (Job outcome)
    Duration  00:00:11
    Sql Severity  0
    Sql Message ID  0
    Operator Emailed  
    Operator Net sent  
    Operator Paged  
    Retries Attempted  0

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

    Thanks,

    Kieran.


    If you have found any of my posts helpful then please vote them as helpful. Kieran Wood PGD SoftDev (Open), MBCS http://uk.linkedin.com/in/bileeds
    Thursday, February 11, 2010 2:21 PM

Answers

  • This error sometime happens when your SQL server is not able to connect / interact with AD and get the domain username / password validated. This might be due to various networking reasons and this can happen intermittently as well (like 2 sec once in everyday) , I have seen this error years back where my company’s network was poor and we then decided to change owner to SQL server logins like sa.

     

    If you are still keen to retain the owner as domain user, then talk to your network admins and troubleshoot the intermittent connectivity issue with the exact time your job has failed.


    Thanks, Leks
    Thursday, February 11, 2010 8:55 PM
    Answerer

All replies

  • http://support.microsoft.com/kb/834124
    Blog: http://dineshasanka.spaces.live.com
    Thursday, February 11, 2010 2:30 PM
  • What version of SQL you are using..?



    a) Owner of that SQL Server Agent Job does not have enough permission to run that job.

    b) Or Account under which SQL Agent service is running does not have enough permission to run that job

    Can you try to run that job as 'sa'?

    • Edited by Chirag Shah Thursday, February 11, 2010 2:38 PM content
    Thursday, February 11, 2010 2:35 PM
  • Thanks Dinesh.

    I look into this.
    If you have found any of my posts helpful then please vote them as helpful. Kieran Wood PGD SoftDev (Open), MBCS http://uk.linkedin.com/in/bileeds
    Thursday, February 11, 2010 2:48 PM
  • What version of SQL you are using..?


    Sorry should have said this in my initial post; -

    SELECT @@VERSION 

    returns; -
    Microsoft SQL Server 2005 - 9.00.4035.00 (Intel X86)   Nov 24 2008 13:01:59   Copyright (c) 1988-2005 Microsoft Corporation  Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 2)


    a) Owner of that SQL Server Agent Job does not have enough permission to run that job.

    b) Or Account under which SQL Agent service is running does not have enough permission to run that job



    This is an intermittant fault. The job ran fine on Tuesday with no errors, on Wednesday it failed without changing the job, so I am not sure about the route cause being security.

    Can you try to run that job as 'sa'?
    I don't have access to the sa password for this server.



    If you have found any of my posts helpful then please vote them as helpful. Kieran Wood PGD SoftDev (Open), MBCS http://uk.linkedin.com/in/bileeds
    Thursday, February 11, 2010 2:56 PM
  • Thanks Dinesh,

    However this article refers to error 42000 which is a security based error. I know this is the error which was reported in the job. However I am struggling to see how the route cause of the error could be security since the job fails intermittently.

    Any other thoughts?


    If you have found any of my posts helpful then please vote them as helpful. Kieran Wood PGD SoftDev (Open), MBCS http://uk.linkedin.com/in/bileeds
    Thursday, February 11, 2010 3:11 PM
  • This error sometime happens when your SQL server is not able to connect / interact with AD and get the domain username / password validated. This might be due to various networking reasons and this can happen intermittently as well (like 2 sec once in everyday) , I have seen this error years back where my company’s network was poor and we then decided to change owner to SQL server logins like sa.

     

    If you are still keen to retain the owner as domain user, then talk to your network admins and troubleshoot the intermittent connectivity issue with the exact time your job has failed.


    Thanks, Leks
    Thursday, February 11, 2010 8:55 PM
    Answerer
  • Thanks Lekss,

    OK I guess there is no hard and fast answer I'll open a dialog with a network administrator. I am marking your reply as an answer because I think you are pointing me in the right direction and I think it may take sometime to gain a specific answer my current issue.


    Thanks again,

    Kieran.
    If you have found any of my posts helpful then please vote them as helpful. Kieran Wood PGD SoftDev (Open), MBCS http://uk.linkedin.com/in/bileeds
    Friday, February 12, 2010 10:42 AM