cancel
Showing results for 
Search instead for 
Did you mean: 

XML Error

Lenny_Westberry
Level 3
When I try to open the "Job Log" tab on a completed job, I get this error..."Load XML failed. Reason: A. Error on line 11131, position 110 in "f".
C:\Program Files\VERITAS\Backup Exec\NT\Data\BEX03359.xml".

Any ideas?
4 REPLIES 4

CBT_Help_Desk
Level 4
I am interesting in the answer to this question as I am receiving the same error as well. But it is only happening on one of my many Backup Jobs.

Vidyaj__Patneka
Level 6
Hi,


1. This error may occur if the Database Maintenance task is configured to remove job logs automatically after x amount of days (where x is the number of days).
To resolve the issue kindly refer the following technote,



http://seer.support.veritas.com/docs/258814.htm


=====================

2. This problem may also occur if the Msxml.msi is corrupt.

So please download and install it using following link.

http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=0CDD34BF-50EA-4238-846B-243C58FF224A

Note : Please copy the entire link given below


=============================

--Stop all the Backup EXec services and re-start them .

-- Create a fresh scheduled backup job and then observe the result.

--Update to the latest Internet Explorer if the problem persists.


===========================

Also apply Service Pack 1 of Backup Exec v9.1 as mentioned in the technote given below

Title:- VERITAS Backup Exec (tm) 9.1 for Windows Servers revision 4691 - Service Pack 1

http://seer.support.veritas.com/docs/267180.htm

Hope this helps.

Sagar_Kamat_2
Level 6
We hope that you have upgraded to MSXML 4.0 Service Pack 2. If not, please refer the following link:

http://www.microsoft.com/downloads/details.aspx?FamilyID=3144b72b-b4f2-46da-b4b6-c5d7485f2b42&DisplayLang=en

Note: Please copy/paste the above URL into the browser.

Also, please upgrade to latest Internet explorer and service pack.

We hope this helps.

188507307
Not applicable
I am also getting this type of an error, but only on certain jobs. When I am backing up our document management folders, which have filenames with special characters in them, such as 6%#_01!.tif, the xml log generator cna't interpret these filenames, and generates a filename that is not correct. Then, the log is incorrect and corrupted.
Is there any way to change the log structure that is generated, and have it as straight text initially, as it was in previous versions?