Environment is an ASP-based application which renders reports from CE10 via managed reporting. Datasources for the reports are xml files accessed through ODBC connection defined on the CE10 server.
When the application hands off report rendering to the CE server, it times out after 10 minutes with the error: "Request timed out because there has been no reply from the server in 600000 ms. The error number was -2147217385. Error occurred in the following component: webReporting.dll"
We've narrowed down where the 10 minutes is being spent, and it's a 10-minute period following the generation of the xml data files.
Troubleshooting to date has involved fixing the order of NIC's in the application's webserver (see We have also attempted to modify every registry setting on the CE server in the HKLM\Software hive for Crystal Decisions to change the 10 minute (600000ms) timeout to 30 minutes, and have rebooted the server after changes. Reports still timing out with the same error.
We have some reports which generate roughly the same size of xml files and/or number of pages in the report (verified through CR10 design preview)--these reports render without error off the server.
Any ideas for us to look at here?
TIA,
mossd
When the application hands off report rendering to the CE server, it times out after 10 minutes with the error: "Request timed out because there has been no reply from the server in 600000 ms. The error number was -2147217385. Error occurred in the following component: webReporting.dll"
We've narrowed down where the 10 minutes is being spent, and it's a 10-minute period following the generation of the xml data files.
Troubleshooting to date has involved fixing the order of NIC's in the application's webserver (see We have also attempted to modify every registry setting on the CE server in the HKLM\Software hive for Crystal Decisions to change the 10 minute (600000ms) timeout to 30 minutes, and have rebooted the server after changes. Reports still timing out with the same error.
We have some reports which generate roughly the same size of xml files and/or number of pages in the report (verified through CR10 design preview)--these reports render without error off the server.
Any ideas for us to look at here?
TIA,
mossd
