Link to home
Start Free TrialLog in
Avatar of MarcoLynn
MarcoLynn

asked on

Backup Exec log conversion errors

I am still getting this error.  I am running BE 11d rev7170 sp4 on a Windows 2003 server and am getting an error in trying to display the job logs.  The Job History window comes up fine in xml but the job log does not.  There have been no recent updates and the ones available by Symantec do not relate to xml errors.  I tried a reboot of the server again to see if it would correct the issue and did not.  I get the same error.  When I try to search for the error, I get a lot of proramming hits, which I have no experience with.  I tried the repair on the xml version which is 4.0 sp2, but no success.  I appreciate all the help I can get, because I have no idea why this keeps occurring!  The error is below:
One or more errors were encountered converting the job log into web page for display.  The job log will be displayed in text format.
The name in the end tag of the element must match the element type in the start tag.
28789: C:\Program Files\Symantec\Backup Exec\Data\BEX_CHEDDAR_01053.xml
ASKER CERTIFIED SOLUTION
Avatar of Syed Mutahir Ali
Syed Mutahir Ali
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of MarcoLynn
MarcoLynn

ASKER

I have Summary information and directories processed.  The strange thing is that not all of the logs that are over 50mb are having the issue.  Some of them, for the very same job, open just fine.  I did delete some from the directory:  C:\Program Files\Symantec\Backup Exec\Data and they have been displaying fine since.  But I still don not have a solid resolution.  Total job is 280 to 290g.  Thanks for your input and I will check the secure symantec site.
No more help from anyone??  Well, since I deleted a large portion of the logs, I have not had an issue wiht them displaying in html.  I do find it odd that Symantec has not found a real fix for this issue yet.  Thanks for your advise and support, Mutahir.  I will accept yours as a solution but really do not have one yet. Thanks!