Video Screencast Help

Jobs disappeared from in BE 2012 Console and a warning is noticed towards the bottom left hand corner in the console "The query for Job View failed"

Created: 11 Apr 2012 • Updated: 19 Jul 2012 | 14 comments
Gurvinder Rait's picture
32
Votes
Login to vote
Me Too!I have the same issue
Product(s): Backup Exec - 2012, Backup Exec
Severity: Non-data threatening / major functionality
Status: Public fix available
Tech Note: More Information

Jobs disappeared from in BE 2012 Console and a warning is noticed towards the bottom left hand corner in the console "The query for Job View failed"

The above is caused by a Job which might show up as Invalid schedule when the schedule ID for that got deleted. This is being Investigate but for the time being all such cases are to be reported and escalated. Support can edit the backup exec database so that the Jobs can be again viewed.

A fix will be developed for the  Issue that led to this situation but for the end user who have run into this Issue we will have to manually edit the bedb (backup exec database)

This issue has been addressed by a Hotfix

Comments 14 CommentsJump to latest comment

MrKristoff's picture

I am having the same problem.  I simply deleted a couple jobs from a Server and closed BE.  When I reopenend, jobs on all servers are gone and getting the JobView query failed error.  I ran live update and installed service pack 4 and all the available hotfixes thereafter and the error and missing jobs persist.  What can I try next?  I saw in another post where someone had deleted jobs from the Jobs Table in the BEDB database in SQL.  Don't want to do that until I know it is safe to do so.

0
Login to vote
Desmond Gooi's picture

I am using SP2 already. But I still have the same problem as job dissapear + "the query for job view failed".

I think I will log call to technical support. Any proved solution for this issue?

-5
Login to vote
Gurvinder Rait's picture

Hi Desmond, If the jobs were created before SP1a, then you might run into this Issue. The fix was in SP1a, if BE was Installed after SP1a was installed then this Issue should not occur again.

-6
Login to vote
Cwooddell's picture

This issue happened to me again with a brand new BE install on a fresh OS install on a dedicated server at a brand new location. Before any BE configuration was done, all updates on offer from Liveupdate were applied. That consists of:

Service Pack 1a

Hotfix 189571

Hotfix 170964

Hotfix 194470

Hotfix 199866

Hotfix 200433

Hotfix 201596

Hotfix 205111

Service Pack 1a was supposed to resolve this issue, but apparently the same type of symptom (though maybe for different causes) still persists.

-5
Login to vote
Gurvinder Rait's picture

I hope the jobs were created post SP1a was applied. If thats the case then please open a case with technical support to get this reviewed.

-6
Login to vote
Cwooddell's picture

Yes, they were. It was a green field implementation with all service packs and hotfixes available via Liveupdate deployed prior to any jobs being created.

I have already opened a case with Support and it's been escalated to "Tier 2" at the moment. I was posting here to inform you that there are still issues (maybe different ones) causing the same symptom.

Hopefully SP2 will resolve this permanently. :)

-8
Login to vote
nasirmahmood430's picture

Jobs are vacant in many fields including technical support

<a href="http://www.search50.net">jobs search engine

-1
Login to vote
David Palmerston's picture

We still have open cases because the hotfix only partially fixes this problem as released on 5/4/2012.  The original hotfix does seem to fix the 'orphaned rows' problem in BEDB with the Policy, TaskDefinition, Jobs, and BEJobs tables, but there must be at least one more table that depends upon having a valid scheduleID that was not 'fixed' in the hotfix.  If that is the case, the likely suspects are probably the  JobViewRemote and Scripts_Schedule tables.

In any case, after installing the hotfix when we get the Query for JobView failed error, we have been able to run the database maintenance by resetting the time and it seems to make the problem go away until the next time we perform whatever process is causing the problem to occur.

-9
Login to vote
remicsto's picture

Technical Support deleted bad jobs and bad schedules from backupexec database (bedb).
The issue was solved (warning disappeared from left hand corner ),
but I have lost all my configured backup policies.
 

-3
Login to vote
Alessandro Caponi's picture

 

For testing i make a new lab with one server and I have prepared the Server with Windows Small Business 2011.

I have installed a full BAckup Exec 2012 in testing mode (60gg) with all patches (also 180962, using liveupdate).

 

I then made a new full backup on a remote NFS storage (NAS).

 

After, for my lab testing i disrupt the disk of the server and then i start with BE2012 SRD disk for a full recovery (supported in this new version, as older backup exec system recovery)..

I restored the full backup correctly and the server restart without error.

 

Opening the BE2012 console i saw the same error "the query for job view failed"; the job is not more present, the destination storage on nas also.

I can recreate the same destination storage (and make a inventory/catalog) , but i cannot reconnect the server.

 

-6
Login to vote
remicsto's picture

I have the same issue on my lab,

A fix (180962) as been released on 05/04/2012

But he was useless on my server, because jobs already disappeared.

So, a case was opened.

 

http://www.symantec.com/business/support/index?pag...

-7
Login to vote
Gurvinder Rait's picture

The fix will prevent you from getting into that situation in future. let me know if the Issue was fixed after you contacted technical support

Thanks

-4
Login to vote