Forum Discussion

Suporte_GP's avatar
Suporte_GP
Level 4
12 years ago

End tag 'machine' does not match the start tag 'sql_dbcc_group'.

It started one week ago. All my backups (incremental and full) are presenting this error when I try to open the job history.

"One or more errors were encountered converting the job log into a web page for display. The job log will be displayed in text format."

End tag 'machine' does not match the start tag 'sql_dbcc_group'.

Attached is the print screen of the error.

That doesn't happen for unlocks, restores, inventory and catalogs.

 

Any ideas?

  • It happened with one server only.
    Apparently got back to normal.

    This thread can be closed.

  • Hi,


    Check the TN below out:

    http://www.symantec.com/business/support/index?page=content&id=TECH23776

    Thanks!

  • Hi Craig,

    I've done that already.

    Besides, it was working until Apr 23th.

  • Are these jobs (the ones where the job log doesn't open) succesful or failed ?

    And did any BE service crash recently ?

    Lastly, is the XML file actually present in the Data directory ?

     

  • 1.) They've failed because of a SQL resource.

    2.) No, nothing that I've noticed.

    3.) Yes, it is. I can actually open using a browser.

     

  • Hello there,

         Is the Job log large in size? Have you enabled detail logging?

    Refer to the following technote

    http://www.symantec.com/docs/TECH73728 : A Job Log gives the error of "One or more errors were encountered converting this log into a web page for display" if it is very large in size.

     

    Thanks,

    -Sush...

  • Hi Sush, thanks for you reply.

    No, the XML and the HTML have around 150kb each. I'm assuming that's a regular size, right?

    I haven't enabled the detail logging.

    I have one XML file from another job that has the status of completed with exceptions, from Apr 16th, which has 157 kb.

  • Have you tried to create a new job and run. And then the new job is complete try to open the Job log and see if that errors out in the same manner.

     

    Thanks,

    -Sush...

  • It happened with one server only.
    Apparently got back to normal.

    This thread can be closed.