Results 1 to 4 of 4
  1. #1
    Join Date
    Nov 2003
    Location
    Mars
    Posts
    115

    Unanswered: Warning msg in application log urgent

    Hi all,
    Sql server 7.

    Under event viewer->application log i am getting the below error continously. Pls help

    Regards,Event Type: Warning
    Event Source: SQLServerAgent$abc
    Event Category: Printers
    Event ID: 208
    Date: 2/9/2004
    Time: 9:23:03 PM
    User: N/A
    Computer: abc1
    Description:
    The description for Event ID ( 208 ) in Source ( SQLServerAgent$abc ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: SQL Check, 0xAF04DFE7917DEA489F33D8A38E8A0793, Failed, 2/9/2004 9:23:00 PM, The job failed. The Job was invoked by Schedule 31 (6.x schedule). The last step to run was step 1 (Step 1)..


    Waiting for ur reply
    TIA
    aadil

  2. #2
    Join Date
    Dec 2003
    Posts
    31
    SQL agent tryed to execute job, the problem is in the job or in one of its step. find the job name in the msdb..sysjobs according to the job id (unique identifier)
    select name from msdb..sysjobs where job_id ='xAF04DFE7917DEA489F33D8A38E8A0793'
    and check it steps. the problem seems to be there

  3. #3
    Join Date
    Nov 2003
    Location
    Mars
    Posts
    115
    Hi,

    thanks for ur reply
    We found the job which is causing failing due to which this error msg is being displayed.
    its an web assistant DTS job
    we are getting the below error.

    Unable to perform a SETUSER to the requested username 'dbo' because the username is invalid for database 'catalog'. The step failed.

    waiting for reply
    TIA


    Originally posted by yoavmaimon
    SQL agent tryed to execute job, the problem is in the job or in one of its step. find the job name in the msdb..sysjobs according to the job id (unique identifier)
    select name from msdb..sysjobs where job_id ='xAF04DFE7917DEA489F33D8A38E8A0793'
    and check it steps. the problem seems to be there

  4. #4
    Join Date
    Dec 2003
    Posts
    31
    so try another user member of sysadmin, (sa or another) since the dbo is alias to sa and other sysadmin users

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •