The job associated with the object is unresponsive

[dhawkins9101]

We run BusinessObject XI on a Windows 2K3 server with 4Gb of RAM and a quad-core processor of 3.00 GHz.

We run just shy of 35 scheduled reports per day and the max processing time on one of our biggest jobs is 2 minutes.

We had a corrupt LUN on our Storage area network and had to run a chkdsk on the volume. That volume was where several of the job servers had their temp space. Since running that, we have not been able to successfully run any jobs on the Business Objects server.

The message: The schedule result provided by the Job Server for the object identified by 82950 is invalid.

shows up in the event log and the report eventually times out and fails due to an unresponsive job server child process.

We are going to attempt a reboot after we clean up yet another corrupt LUN on our SAN, but if that doesn't resolve the issue, do you have any suggestions?

Dan

 

[hilfy]

The reboot should clear up the issue. However, if it doesn't you may want to try rescheduling one of the reports that's failing - don't right-click on the recurring instance and reschedule, do the new schedule from scratch. If this resolves the issue, then that's what you'll have to do for all of the schedules.

Are your input and output file repositories also on the SAN? If so, it could be the LUN where they reside is bad. In which case, it means that the report templates might be corrupted. When you schedule a report, the recurring schedule has its own copy of the report template, so that's one opportunity for file corruption and is why you want create a new schedule rather than rescheduling. However, if the master template for the report is corrupt, you'll have to open a back up copy of the .rpt file (hopefully you have them!) and re-publish it to BOE.

-Dell

A computer only does what you actually told it to do - not what you thought you told it to do.