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.