1 Report not logging in causing all to hang

[eyeswideclosed]

We've got about 300 reports in a CE10 managed system, if just 1 report does not log on to the db correctly, missing password or something, then no reports can run after that, just get the grey screen in the viewer timing out, I have to restart the servers or reboot to clear it. Is this normal?

 

[synapsevampire]

No.

Perhaps you are basing the reports on other reports completing (events)?

Or you may have a configuration issue, you might consider applying the service pack:

http://support.businessobjects.com/downloads/updates/service_packs/enterprise.asp

-k

 

[eyeswideclosed]

Thanks. Well it looks like it hangs the page server it happens to use, we have 2, the other 1 still works for other reports but the one that is trying to service the report with the missing logon information will not respond to any report until it is cleared, so about 1/2 of the report requests time out until this happens. Yes we have all the latest packs and hotfixes. Weird.

 

[synapsevampire]

I used to have similar problems with CE 8.5, but my last CE 10 install worked fine.

Also check the restart configuration for that service, and if all else fails, nuke it and create a new one.

-k

 

[eyeswideclosed]

Thanks. Yes I confirmed the page server problem, whichever one the report in question uses hangs up and will not respond to any more requests and will not restart either, I have to reboot the machine to clear it. I recreated all the servers but no change. Well we'll just have to make sure every report has all the logon info I guess, but it's troubling that a missing password on 1 report would crash a page server like that, oh well.

 

[Turkbear]

Hi,
The underlying problem to solve is why that report hangs the page server ( any other fix is just symptomatic)..

Check the event viewer for any error messages related to the page server.

Does that report run in CR Designer( from the CE machine)?

How are you running that report( Scheduled, OnDemand from Eportfolio, custom code..?).

Even a scheduled report with bad login info for the database should just fail not hang..





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

 

[eyeswideclosed]

Any report with a missing password will hang it, not just that one, they are all on-demand. They run fine from anywhere as long as you provide the user and pwd, they all use the same odbc dsn connection. Ok I will check the logs, thanks.