Scheduled reports (DeskI) remain in status "Pending" in SP4(FP 4.3)

[former_member142702]

Hi,

I am facing a weird problem with a BO XI R2 cluster installation (2 Windows Servers, one CMS, 2 DeskI Job servers on one node) after installing SP4 + FP 4.3. The users are allowed to schedule DeskI reports they created themselves. The scheduling works out fine at the beginning but at some point overnight the DeskI servers (although empty) completely ignore the fact that there are available jobs for scheduling. This means that the DeskI reports remain in status "Pending". Changing the "maximum number of jobs" setting at the CMC in the DeskI job servers properties tab seems to work like a wake-up call and the scheduling starts again. After a while though (can take up to a day to get there) the job servers start again to ignore the pending jobs.

Is this a known issue in SP 4? Anyone had similar experiences two?

Any help/ideas & hints will be highly appreciated.

Cheers

Stratos

[Former Member · Accepted solution]

This issue is being investigated by PG and is planned to be fixed in FP4.5.

See the following link:

http://www.businessobjectstips.com/tips/xir2-sp4-bug-schedules-pending/

Regards,

Jeff

[Former Member]

You can see how many jobs are running & pending for the Deski server by pulling up the Instance Manager (Under Manage group) in the CMC. It may be that one of your jobs is set to a high recurrence frequency and it clogging the servers. In any case, in normal circumstances, you should not having pending jobs if your number of running numbers is below your max number of jobs setting.

[former_member142702]

Hi Will,

Quote: "In any case, in normal circumstances, you should not having pending jobs if your number of running numbers is below your max number of jobs setting". Exactly this is what we are expecting but the job server seems to sleep not caring about the actual number of pending jobs und wakes up only if we use a high setting (40) for the maximum number of jobs.

Have found some references about similar problems for both the Web Intelligence and the Crystal Report Job Servers but not a real solution so far. It may be a problem with the CMS but I am not really sure. Restarting the CMS does not help neither.

Cheers

Stratos