Reports Timing Out

[#1]

Users have been experiencing an intermittent issue when they try to run reports on-demand through the InfoView application. The usual error message is:

Your request could not be completed because a failure occurred while the report was being processed. Please contact your system administrator.

It seems that the problem is most common during a week when a large number of users run reports.

On a given day, the reports will time out then work again after a time period of about a half hour. Usually another time period later, reports won't run. Many times, the cycle will repeat itself during the day.

One other peculiarity is that I would run a report through scheduler. The report ran fine. When I tried to view latest instance, that then timed out as well.

I suspect there is some setting. Is anyone familiar with this issue or its resolution? Thanks!!

[Former Member]

we are having a similar problem when we try to run the queries, i realized that after you install SP4 in XI R2 began the problem, it would be some bug? does anyone know about something about?

atten

[Former Member]

Edward,

Your request could not be completed because a failure occurred while the report was being processed. Please contact your system administrator.

Does the timeout occur at approximately the two minute point? If so, I too suffer from that in my deployment. The reason why the report subsequently works is due to caching. If the report is in the BOE server cache, then it doesn't send it to the database server, but fetches it from cache and voila, you get it with no further problems. However, the default out-of-the-box expiry for cache is four hours, so if someone exceeds the four-hour period, then your back in the vicious cycle again. I don't know how to overcome the two-minute timeout (we call it the two-minute drill), and this timeout doesn't affect scheduled reports, so a scheduled report can exceed the two-minute limit (but after 20 minutes our schedule reports will bomb out). However, when you send a report to scheduling, ensure that it is not saved with the "refresh on open" option set, otherwise, when you go to pick it up from the "History" you will run into the same vicious cycle again. Good luck.

John