Hi,
When we try to run a report from Cognos Connection in PDF format, its taking long time and giving the error "Unable to execute the request because there was no process available within the configured time limit. The server may be busy". But when running in HTML format or when I click ont he report, its working good.
Thanks,
Jaspire
When you run in html mode, only one page of data is brought back...that's why it's fast. Other output formats require running the report to completion.
Copy the report SQL and run it against your database in its native client, you'll likely find that you have the same problem there. Examine the SQL as a starting point to troubleshooting...difficult to say what your specific problem may be without knowing specifics.
Thanks for your reply,
I ran the SQL in SQL Server database that we have. It ran fast.
I appreciate any more suggestions on why my report is taking long time when ran in PDF?
Thanks
Jaspire
does your report use a master-detail relationship? i had performance issues with that type of report when the query called a stored procedure the stored procedure was re-executing for every page of the master-detail
Thank you.
But there is no Stored procedure in our report. Also the report is running slow in PDF and also in EXcel formats. Only in HTML format, its running good.
I appreciate if you could give more suggestions on why it is taking much time to run. Also there is possibility of divide by Zero condition, but the report gave HTML output even in divide by zero situation.
Jaspire
Can you run the report to completion in HTML (with the "bottom" link)?
If you can, then the only difference should be in the rendering (of Excel and PDF), and that seems unlikely. I'm guessing a full run of HTML will also exhibit the problem. The "no process available" error seems to indicate some sort of resource issue on your server but that could be almost anything - memory, disk, or misconfiguration. Try to find more info on the error in your logs and in the Cognos knowledge base, and/or open a case with Cognos.
Actually the problem is with the Joins in the report. The report used fields from different folder which were not actually joined with other fields when building package.
Thanks
Jaspire