SYMPTOM:
When running a large Report Services document, the execution fails in Strategy Web 9.x and 'Error in Result' and 'System call error. Error communicating with connection process. Process hung' errors are found in the DSSErrors.log, as shown below:
2007-08-02 12:36:32.859-05:00 Unknown failed. Unable to connect. Error type: System call error. Error communicating with connection process. Process hung..
CAUSE:
The report execution time has been reached, as shown below:
When the report execution time limit meets, the following errors could be found in DSSErrors.log, which cause the 'System call error':
- Job# 303 has timed out.
2007-08-02 12:35:32.265-05:00 MsiJobTimeOutTask::Run: Job 303 has timed out.
- Job# 303 is canceled.
2007-08-02 12:35:32.296-05:00 MSIPU::Kill: Job is created at 2007-08-02 10:54:32.125.
- Replacing thread.
2007-08-02 12:35:37.328-05:00 MSIPU::Kill: PU:QueryExecution: Thread found busy after cleanup, replacing thread, job:303, step:4, thread:2420.
- Since job# 303 has already been timed out and canceled, the process hangs with the new thread.
2007-08-02 12:36:32.859-05:00 Unknown failed. Unable to connect. Error type: System call error. Error communicating with connection process. Process hung..
ACTION:
Increase the report execution time. Refer to TN16361 - What are the settings that directly regulate report execution times in the MicroStrategy 8.x Product Suite? for further information.
