EventID: 208 Source: SQLSERVERAGENT

  • Hi all,

    Getting the following error when SQL Server 2000 Maintenance Plans tries to backup the database:

     

     

    SQL Server Scheduled Job 'lab_proj backup' (0x05A45FDE1452E24EB5E46DB1FD67B62A) - Status: Failed - Invoked on: 2006-09-15 16:51:00 - Message: The job failed.  Unable to determine if the owner (win\Jim) of job lab_proj backup has server access (reason: Could not obtain information about Windows NT group/user 'win\Jim'. [SQLSTATE 42000] (Error 8198)).

     

     

    Jim has the administrator rights on the Server.

     

    Thanks for any help.

     

    Regards,

     

    Abrahim

     

  • change the owner of the job to 'sa' from win\Jim

  • SQL server is not able to retrieve win\jim info. from domain controller. Try to login to the box using win/jim account.

    thks,

    Sats..

  • Unfortunately Login to the box with jim didn't fix the problem.

    I fund this fix on Microsoft site

    1.Start SQL Server Enterprise Manager.
    2.Expand Microsoft SQL Servers, and then expand SQL Server Group.
    3.Expand your server name.
    4.Expand Management, and then expand SQL Server Agent.
    5.Click Jobs. In the right pane, right-click the job that failed, and then click Properties.
    6.In the Properties dialog box, click Owner on the General tab to display the list of owners.
    7.In the Owner list, click the SQL Server user who you want to use. Alternatively, click sa, and then click OK.
    8.When you are prompted to stop and to restart SQLAgent, click OK.
    9.Restart any instances of SQL Server.

     

    Thanks for all the help.

     

    Abrahim

     

  • did you read my post?:

    <change the owner of the job to 'sa' from win\Jim>

    The 7, 8 ,9 are not True statments :

    due to change the Job owner you do not need restart any sql server service!

    please post link where from you got the info

    7.user who you want to use. Alternatively, click sa, and then click OK.
    8.When you are prompted to stop and to restart SQLAgent, click OK.
    9.Restart any instances of SQL Server.

  • correction:

    step 8 and 9 are not required

  • Eugene,

     

    Sorry, I guess I missed your post 🙁

     

    Abrahim

     

Viewing 7 posts - 1 through 6 (of 6 total)

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