A user has faced an issue related to parametrized actuate report and calculated filed in parameter applet.

I have assisted 4 siebel application for the actuate report issues. I am listing down the common Reports error and their Solutions which i faced during these assignments.

“Report generation has failed on the  Report Server”
“External library not found”
“Use of a null instance handle”
“The page cannot be displayed”

If you implement actuate reports within Siebel you would know that when you create a new user you have to synchronize the user with the Actuate server so that they can generate Actuate reports.

Troubleshooting Steps
All the above factors can contribute to the poor performance of reports. If you are encountering report performance issues, the following checks should be made to isolate the problem. Please refer to the previous sections as appropriate.
1. Are all the reports perform badly or is it only specific reports that are performing badly?
2. If all reports are performing badly, check the following:

Network
The network is the infrastructure that allows the Client Web Browser, Actuate e.Reporting Server, and Siebel Object Manager to communicate, assuming that they are all on separate machines. When the report is requested, the Siebel Object Manager passes the request to Actuate over the network.

Reports Server
Physical Machine and Factories
The Reports Server has a finite capacity that depends on the specification of the physical machine. It is able to run multiple factory processes that allow reports to be processed concurrently, increasing the overall throughput of reports per minute. The number of factories dictates the number of reports that can be run concurrently.

Aggregate Functions
The use of aggregation functions impacts the performance of a report to some extent. This behavior is expected because aggregation involves the summarizing of the records in some form. Therefore, the amount of aggregate information required adds to the overhead of the report performance.
Look ahead aggregates, for example, cause the report to retrieve all records before it is able to calculate the expression that is using the look ahead aggregate. Whenever possible, it is preferable to use running aggregates, which are calculated as data is being retrieved. For more …

Search Specification in the Report Design
If it is not practical to set the search specification on the business component or to set the search specification in the report object definition, an alternative is to configure the report to apply a search specification to the business component. This causes the report to re-query the business component with the search specification. The search specification of the report object in Siebel Tools is static and overrides any queries performed in the UI just before the report submission. Therefore, setting the search specification in …

Dedicated to Rachana Agarwal , who irritated me a lot to write this Actuate page..
 
Performance issues for Actuate Reports can occur due to a variety of factors. This technical note discusses these factors and concludes with some general trouble shooting steps to isolate which of these factors may be affecting your report performance.
The following topics are detailed in this technical note.
 
• Report Design
• Reports Server
• Network
• Siebel Object Manager
• Volume of Data
• Troubleshooting Steps
Report Design
The report design can have a large impact on the performance of a report. Consider the following points to assess impact on …