Symantec Backup Exec 12.5 [job monitor] (not responding)

Helena Duggan's picture

Running Backup Exec 12.5 on Windows 2008 Server, have a weekly backup jobs of about 526gb, however when try to open the job history it hangs with (not responding).  Works fine on all other jobs which are of similiar size, my only problem is that there are errors mentioned within this job ( E000954C ) but I cannot see what the error is as I cannot open the job log.  Have tried opening through the Alerts window but get the (not responding).  Is there any way of seeing this log?

Matt Alexander's picture

Job Monitor Hanging

I can't find anything in the KB or in Connect concerning this. I'm going to escalate the thread and see if a TSE can help out.

If a post answered your question, please "Mark As Solution".

Connect Forum Moderator
Backup & Archiving and Endpoint Management & Virtualization Communities

pkh's picture

I have this exact same

I have this exact same problem when one of my jobs generated a job log which is about 100MB.  BE does not seem to be able to handle big job logs.  The tech support guy is also unable to read the job log until I provided him with the solution below

Go to C:\Program Files\Symantec\Backup Exec\Data and you will find a lot of .xml files.  These are the job logs.  Find the one that was created at the time of your job and that is probably the job log.  To 'read" it, you can open it using Notepad if it is less than 32MB in size or Metapad if it is greater than 32MB.

__________________

If this answers your question, please mark this as the solution.

Helena Duggan's picture

Just looked at the file

Just looked at the file within C:\Program Files\Symantec\Backup Exec\Data  as suggest the file size is 839,136kb while all others are around 22kb,  I had the same issue last week with this job as it is a weekly where the file size was also similiar, but another job of which backs up the same amount of information has a log file of only 23kb.

pkh's picture

Are you able to read the big

Are you able to read the big job log?  You should determine what is generating the excessive amount of logging and correct that error.