Post reply

Intermittent Error on SQL Server Agent:[SQLSTATE 42000] (Error 8198))

  • February 16, 2004 at 8:58 am

    #107268

    Recently, I have begun receiving the below error:

    The job failed. Unable to determine if the owner (wtsinf\sqlservice) of job CDIN_Audit has server access

    (reason: Could not obtain information about Windows NT group/user 'wtsinf\sqlservice'. [SQLSTATE 42000] (Error 8198)).

    This is just one example. I had 6 jobs fail this weekend(all with the same error), and our SQL DBA has no clue why.

    Thoughts or suggestions?

     

  • February 17, 2004 at 12:22 am

    #494308

    there is an issue with using windows-accounts as job-owner.

    I don't know the kb-no by heart. I'll add it if I find it back.

    If I'm correct it was http://support.microsoft.com/?kbid=233161

    Johan

    Learn to play, play to learn !

    Dont drive faster than your guardian angel can fly ...
    but keeping both feet on the ground wont get you anywhere :w00t:

    - How to post Performance Problems
    - How to post data/code to get the best help[/url]

    - How to prevent a sore throat after hours of presenting ppt

    press F1 for solution, press shift+F1 for urgent solution 😀

    Need a bit of Powershell? How about this

    Who am I ? Sometimes this is me but most of the time this is me

  • February 17, 2004 at 12:37 am

    #494310

    Being lazy, I usually just edit such jobs and change the owner to sa.


    Cheers,
    - Mark

  • February 17, 2004 at 12:54 am

    #494312

    isn't that (Being lazy) one of the top prerequisite to become a sysadm/dba

    Johan

    Learn to play, play to learn !

    Dont drive faster than your guardian angel can fly ...
    but keeping both feet on the ground wont get you anywhere :w00t:

    - How to post Performance Problems
    - How to post data/code to get the best help[/url]

    - How to prevent a sore throat after hours of presenting ppt

    press F1 for solution, press shift+F1 for urgent solution 😀

    Need a bit of Powershell? How about this

    Who am I ? Sometimes this is me but most of the time this is me

  • February 17, 2004 at 1:21 am

    #494313

    I encounter similar problem. In a domain have WIN2K server as PCB server and BDC server. after shutting down the BDC server. the job was working fine.

  • February 17, 2004 at 2:45 pm

    #494440

    Give this a try: Change the job owner to a standard SQL Server user or system administrator (sa).

     


    - Rob

  • February 17, 2004 at 10:51 pm

    #494460

    try this KB article http://support.microsoft.com/?kbid=834124

  • December 6, 2007 at 8:35 pm

    #757931

    http://support.microsoft.com/kb/241643/

    I've been using this link but still cant get my jobs to work. I've changed the job owner to sa and it still fails.. have also restarted the instance,

    -set sql agent to startup as an admin user (my domain user)

    But the job is using a linked server to query a table on a remote server, dump it into a temp table locally then move of into a local table.

    That linked server is configured to use my domain user which has admin rights.

    Any thoughts please? I perhaps dont have the right mix.

    When I change the owner from something other than my account I get this error

    Executed as user: job. Remote access not allowed for Windows NT user activated by SETUSER. [SQLSTATE 42000] (Error 7410). The step failed.

    Which I presume is because it doesnt have privs on the linked server??

    Cheers,

  • December 6, 2007 at 10:08 pm

    #757940

    Have you tried to reboot the server itself. I have hit this when the connection between the domain and the server has failed. (can happen for so many reasons). Rebooting should reset the connections.

  • December 9, 2007 at 2:57 pm

    #758412

    Tried a reboot but no joy.

    My issue is if I change the job owner the if fails to connect to the server using the database link and I get the SETUSER error.

    The linked server is configured as "using the login's current context"

    So is the issue really with the security context?

    Cheers,

  • March 3, 2008 at 11:06 am

    #784558

    Checked the properties of the account that is running SQL Services, I ran into this same problem and the domain account running SQL Services was locked out and once I unlocked the account, I restarted the job manually and it started successfully. Hope this helps.

  • March 17, 2008 at 11:47 am

    #790472

    I had same problem but it fixed itself.

    Same jobs worked the night before AND the night after, but on the one night in the middle, NO JOY.

    Did nothing to fix and made no changes to break.

    Any ideas on what could make this Intermittent?

  • March 24, 2008 at 7:52 pm

    #793296

    you should try to enable some trace flags and see what you find at the point of failure. If that does not work you may need to run psdiag and dump the stack to see what happened.

  • March 26, 2008 at 8:43 am

    #794085

    thx

    will do

  • May 9, 2008 at 3:45 am

    #812900

    Hi

    I had the same issue. And got fixed after a lengthy search on many forums.

    Here is the solution:

    http://support.microsoft.com/kb/811031

    Do the workaround step by step and i am sure that will fix.

    regards

    sudharshan

Viewing 15 posts - 1 through 15 (of 16 total)

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