Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

"The query for Job View failed" from Backup Exec 2012 Service Pack 3 + Hotfix 213186

Created: 20 Mar 2014 | 4 comments

Hi,

This error persists even in the newest versions. 

I have Backup Exec 2012 Service Pack 3  + Hotfix 213186 and I still without acess to view my backup jobs.

All that I find about this issue it's the article TECH185878 "http://www.symantec.com/business/support/index?page=content&id=TECH185878"

Could the Symantec sent me a any solution about this issue?

I'm trying to contact  technical support but it's taking so much to answer me.

Operating Systems:

Comments 4 CommentsJump to latest comment

Ananya Bhattacharya's picture

Install SP4 for BE 2012 from http://www.symantec.com/docs/TECH212772 and reboot the server if prompted and check

Regards,

Ananya Bhattacharya
Technical Support Engineer (Advanced Team)

Ananya Bhattacharya's picture

Did you get a chance to install SP4? Did it help?

Regards,

Ananya Bhattacharya
Technical Support Engineer (Advanced Team)

g.rudorff's picture

The problem persistet on my system after upgrading to SP4. I have upgraded the remote agents (2 remote system running win 2008r2 and win 2003). my media server is a win 2008 box.

on opening up each system and tape media, the Job view is empty and yellow traingle "Job view failed" is flashing on the left bottom corner. The job schedules seem to be running, however is throwing "unknown" errors and finishing "with exclusion" very quickly. I doubt to have a valid backup of the selected ressources.

do you have any recommondations? If I need to provide further information, please let me know.

VJware's picture

Are there any errors/warnings under the event viewer ? Have you tried a repair of the Backup Exec DB using this KB - http://www.symantec.com/business/support/index?pag... and then a repair of Backup Exec from Programs & features applet ?

If the repair doesn't help and there aren't any relevant errors, would recommend to log a formal support case as per TECH185878 "this hotfix will prevent the issue only from happening in the future, however, will not fix the existing issue."