If you are experiecing the following error message when executing reports then you should investigate the impact of increasing the queue time limit that is set in Cognos Connection.
"DPR-ERR-2002 Unable to execute the request because there was no process available within the configured time limit. The server may be busy."
In the server administration pages, the following parameters determine the maximum number of BIBusTKServMain.exe processes which can be handled by Cognos:
Maximum number of interactive report service processes (interactive reports)
Maximum number of batch report service processes (scheduled report)
Each BIBusTKServMain.exe process can handle a number of requests determined by the following parameters:
Number of high affinity connections for the batch report service
Number of low affinity connections for the batch report service
Number of high affinity connections for the interactive report service
Number of low affinity connections for the interactive report service
Remember that you can also refer to the documentation that was provided with your Cognos install, more specifically the "Administration and security guide" (ug_cra.pdf).
When the 'number of connections' (which equates to the number of report executions a BIBusTKServMain.exe process can handle) is reached for all the processes (BIBusTKServMain.exe), the request is queued. Queue time limit of report service in seconds is the queue timeout. If no report execution is finished before the timeout value, the error message is returned to the user.
The solution is to increase the Queue time limit of the report service in seconds parameter to allow requests to stay in queue longer.
You can also consider investigating increasing the number of processes or the the number of connections. These parameters have to take in account the machine (number of CPUs and quantity of RAM available) being used by CRN/Cognos 8, as well as the number of concurrent users.
The FrameWork modelization impacts the generated SQL for your reports. If the SQL generated by CRN/Cognos 8 is not optimized, the requests may take longer to execute. The connection will not be released, and there is a chance that requests will be queued - therefore modeling optimization may also help avoid this error message.
Here are the steps to make this modification:
1. Login to Cognos Connetion with an Administrator account.
2. Go to Tools > Server Administration > Configure Tab.
3. Go to the Dispatcher Properties > Settings Tab.
4. Look for the Queue time limit of report service in seconds parameter and increase it.
