Environment
Novell Sentinel 6.1 Report
Crystal XIR2 SP4
Situation
Request Timeout Error
Running a report from the CMS Web Interface returns 0 results eventually returning a Request Timeout error. The web interface can also hang on running and no result sets are ever returned. If a query is done directly against the database using SQLPlus or other utility, it returns results.
Running a report from the CMS Web Interface returns 0 results eventually returning a Request Timeout error. The web interface can also hang on running and no result sets are ever returned. If a query is done directly against the database using SQLPlus or other utility, it returns results.
Resolution
Like most web applications, Crystal XIR2 has a default a timeout of
15 minutes for returning results. In the case of more complicated
reports that require more time to run, it is very possible that
this timeout period can be exceeded thus resulting in the Request
Timeout Error in the web application. You can increase this value
by following these steps:
1. On the Crystal reports server, create a folder call "Reports" in the C:\inetpub\wwwroot directory.
2. Using notepad, create a document called web.config and save it to the C:\inetpub\wwwroot\Reports directory
3. Copy and paste the following lines into the web.config file you just created:
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<system.web>
<httpRuntime executionTimeout="2400"/>
</system.web>
</configuration>
4. Save this file and restart CMS on the server.
This value, 2400, is equivalent to 40 minutes thus ensuring you should no longer timeout processing the results.
1. On the Crystal reports server, create a folder call "Reports" in the C:\inetpub\wwwroot directory.
2. Using notepad, create a document called web.config and save it to the C:\inetpub\wwwroot\Reports directory
3. Copy and paste the following lines into the web.config file you just created:
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<system.web>
<httpRuntime executionTimeout="2400"/>
</system.web>
</configuration>
4. Save this file and restart CMS on the server.
This value, 2400, is equivalent to 40 minutes thus ensuring you should no longer timeout processing the results.