Scheduled report do not progress past stage PENDING

[eo]

Hi

Newly deployed CE10 (every version seems to get worse than the one before???).

I came in to work this morning, and with Instance Manager checked the state of scheduled reports. Multiple reports, that was supposed to start run at 6am, was still not complete (at 9am), I deleted them all off, and scheduled a new report. This is now 0.5 hours later, and the schedukled report has not yet progressed to the Running stage? I have restarted all the services, this did not help.

Please help, staff are losing confidence in CE as a BI tool (quite understandably)!



EO
Hertfordshire, England

 

[Turkbear]

Hi,
( Side note : we have been running CE since V8.5 and have had few, if any, problems with scheduled reports. )
Instead of using Instance manager, do this in the CMC:
Click on the 'pending' tag and see what it says about when it is going to run..It may also say why is has not so far.


Have you checked the date and time on the CE server?





To Paraphrase:"The Help you get is proportional to the Help you give.."

 

[eo]

It had to do with many JobServerChild processes 'stuck' in the process. I had to clear them all down, and restart the services.

Thanks,

EO
Hertfordshire, England

 

[srinivasanbs]

Hi,

We too experience the same kind of problem here. We are using CE 10 Solaris version and multiple reports are deployed. We see the reports are getting struck in pending mode frequently. Not much details when we click on 'pending' tag. It just gives the creation time, 'next run time' etc. the thing is, it never returns to running mode on that 'next run time'. Restarting the servers solves the issue temporarily. But soon in a day or two again the reports gets stuck in pending mode.

Because of this, we have to keep restarting the servers whenever problem ocurs. Is there anyway we can solve this problem completely?

Note: Crystal Support did not help on this.

Thanks.

 

[eo]

Ours was a combination of issues.

Large reports got stuck in front of daily reports (which as a consequence did not run due to waiting in the qeue). The only way to solve this was to clear the JobServerChild processes on the server, and to relook at why the large reports failed to run (which was an issue outside of CE). Not sure if this will be of benefit, but it selved our issue.



EO
Hertfordshire, England