The most common problems are errors in the database configuration. These are typically errors in the database configuration files or in the application server configuration files. For information about resolving these errors, refer to troubleshooting section Troubleshooting.
If you have trouble running reports in your new JasperReports Server instance, refer to troubleshooting section Error Running a Report. If you're having trouble running the MDX example Topic or SugarCRM OLAP view, you need to update the port for XML/A connections. See Updating XML/A Connection Definitions (Optional).
The following error could be caused by an incorrect ampersand setting on your data source configuration:
Error 500: Filter [characterEncodingProxyFilter]: cold not be initialized
The data source line needs to have & and not & to be evaluated correctly. That is, the URL you enter in the procedure to define the JDBC data source and expose it through JNDI should look like this:
If you encounter errors when creating resources with internationalized names, and you have an Oracle database, configure your Oracle JDBC driver. Set the Oracle-specific option listed in the tables of Setting JVM Options.
In earlier releases of JasperReports Server it was possible to find the following error in the WebSphere log:
SRVE0068E: Uncaught exception thrown in one of the service methods of the servlet: jasperserver. Exception thrown: org.springframework.web.util.NestedServletException: javax.xml.validation.SchemaFactoryFinder$ConfigurationError: Provider org.apache.xerces.jaxp.validation.XMLSchemaFactory could not be instantiated: org.apache.xerces.impl.dv.DVFactoryException: DTD factory class org.apache.xerces.impl.dv.dtd.DTDDVFactoryImpl does not extend from DTDDVFactory.
Since around release 4.0, the xercesImpl jar used is version 2.7.1 and more recently 2.10.0.
The error shown above is caused by a conflict between the IBM JDK used by WebSphere and the xercesImpl-2.6.2 library bundled with older versions of JasperReports Server. There are two solutions:
|•||Remove the xercesImpl library from the following location:|
|•||Update the xercesImpl library to a new version (if it's an old version).|
The following error may occur because AspectJ needs class loaders to be tried out in a specific order:
Change the default class loader policy:
|1.||In the WebSphere Administrative Console, navigate to Applications > (app-name) > Manage Modules > JasperServer UI application.|
|2.||Change the following setting:|
Class loader order
Class loaded with local class loader first (parent last)
|4.||Save the master configuration.|
|5.||Restart the WebSphere server.|