Veritas xml error viewing job history

Posted on 2007-10-15
Last Modified: 2013-12-01
Getting this error when trying to look at the job history:   JOB LOG DISPLAY ERROR  Illegal xml character  99: D:\Program Files\Veritas\BackupEx\NT\Data\BEX_ServerName_01068.xml.  I've been getting this error everyday when trying to view the job history for the daily backup for a week.  The W2003 server is up to date on all Windows updates.  Please help...
Question by:tinamerrifield
    LVL 28

    Expert Comment

    It looks like your jobs may not be completing and are not correctly writing closing tags in the xml files for the logs.
    Open D:\Program Files\Veritas\BackupEx\NT\Data\BEX_ServerName_01068.xml with notepad and check if the job reports that is was succesfull.

    If not succesfull, check the event viewer for any of the Backup Exec services terminating unexpectedly, or the server rebooting.
    LVL 23

    Accepted Solution

    Please refer to the following article

    also run live update to update the backup exec software
    LVL 23

    Expert Comment

    the issue can also occur if you have a lot of errors in the job logs and the job log exceeds the limit of the XML parser.

    Also it can appear due to exchange related errors,like trying to backup mailboxes that have been deleted or are marked for deletion

    Author Comment

    Thanks so much iamthecreator for the solution.  It seemed to be registering the xml dll's again and clearing out all the old xml files.  I ran a quick backup job and can now view the job log just fine.

    Expert Comment

    When trying to view the job log for a completed backup, I get the following error:

    "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."

    "LoadXML failed. Reason: A. Error on line 181, position 24 in "f"
    C:\Program Files\VERITAS\Backup Exec\NT\Data\BEX00021.xml

    I have followed the instructions in the Veritas article 254079 but the problem still exists.

    In the article it says to register some DLL files. All except MSXML1.dll are ok. When attempting regsrv32 msxml1.dll an error says: "LoadLibrary("MSXML1.dll") failed - The specified module could not be found."

    Featured Post

    Why You Should Analyze Threat Actor TTPs

    After years of analyzing threat actor behavior, it’s become clear that at any given time there are specific tactics, techniques, and procedures (TTPs) that are particularly prevalent. By analyzing and understanding these TTPs, you can dramatically enhance your security program.

    Join & Write a Comment

    Suggested Solutions

    Create your own, high-performance VM backup appliance by installing NAKIVO Backup & Replication directly onto a Synology NAS!
    The Delta outage: 650 cancelled flights, more than 1200 delayed flights, thousands of frustrated customers, tens of millions of dollars in damages – plus untold reputational damage to one of the world’s most trusted airlines. All due to a catastroph…
    This tutorial will walk an individual through locating and launching the BEUtility application to properly change the service account username and\or password in situation where it may be necessary or where the password has been inadvertently change…
    This tutorial will walk an individual through setting the global and backup job media overwrite and protection periods in Backup Exec 2012. Log onto the Backup Exec Central Administration Server. Examine the services. If all or most of them are stop…

    728 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    18 Experts available now in Live!

    Get 1:1 Help Now