InetSoft Reporting Software - Report Configuration Troubleshooting

The following is provides information regarding report configuration troubleshooting for InetSoft's reporting software. View the information below to learn more about the Style Intelligence solution.

Appendix A: Troubleshooting

None of my settings have taken effect.

If your configuration files are in a folder other than the classes folder of the web application, a sree.home initialization parameter must be set for both the administrator and the repository servlets.

I cannot see my reports after I deploy them.

This could be a problem with the location of the registry directory or the CLASSPATH in the application server.

This problem could also occur if you have security set up for your environment. If you have set up security and have created users and roles, then the Report Server will require a username and password ticket to generate the replets. The users must have permission to view the replets.

I can see my reports in the repository tree but when I try to view them I get a “replet not found” error.

All report files (.srt) and class files are loaded from the classpath of the application server. Make sure that these files are located in a folder which is in the CLASSPATH (or any of its sub-folders). If the replets are deployed from a packaged jar file, make sure that the replet.auto.reload property is set to false.

I deployed a template but I cannot see it.

Templates are loaded as resources. When a template is registered it must be prefixed with a '/', for example '/template1.xml'. Also, be sure to select 'template' as the type on the registration page.

I can see the body of my report, but the fields are not populated with data.

Check the location of the data source and query registry files in the Enterprise Manager. Make sure that valid datasource.xml and query.xml registry files are being referred to.

My Charts seem to have jagged edges, especially pie charts.

Try changing the image type to PNG rather than JPEG, using the 'Presentation' > 'General' node in the Enterprise Manager.

The Repository does not bind to the RMIREGISTRY.

Make sure the classpath is set before running the rmiregistry. Alternatively, make sure that the port is not in use, and it matches the parameter value.

The RMI node will not start.

Make sure that the rmiregistry and the Activator are running on the node.

The repository does not bind to the name service.

Make sure that the same port is being used.

Is it possible to run a task continuously (i.e. Have a task that executes every few minutes)?

It is possible to do this by writing a user defined ScheduleAction which extends DefaultUserAction. A scheduled task consists of one or more actions and one or more conditions. The conditions are checked to see when and whether a task will be started. When all conditions are met, the task actions are executed in order. If a task is a repeated task, it will be rescheduled to run at the next cycle. Multiple time conditions typically should not be added for the same scheduled tasks (this can result in retry time conflicts); instead, another task should be created.

This software will not run in WebSphere.

WebSphere has an XML parser (WebSphere\AppServer\lib\xml4j.jar) which uses DOM level 1 interfaces. Even if you put the Xerces 1.1.2 (or later) xerces.jar in your classpath, the wrong interfaces are found by any Java code running in WebSphere, because WebSphere puts the user's classpath at the end. Therefore, you must edit the WebSphere\AppServer\bin\admin.config file and put xerces.jar at the beginning of the com.ibm.ejs.sm.adminserver.classpath variable. This software uses the newer xerces.jar parser – therefore, it is necessary to edit this property so the servlet can be deployed without error.

CVS Archive will not work with Sun One application server.

The Sun One application server is unable to use the cvs executable on a remote drive. Move the executable file to a local drive.


Evaluate InetSoft's Business Intelligence Software for your reporting software needs.