License Not Found Errors
Normally, the JasperReports Server installer includes an evaluation license file that you replace with a commercial license file, as described in Installing a New License File. If JasperReports Server returns an error after you replace the license file, the most likely causes are:
|•||You didn't clear your application server’s work directory, as explained in “Installing a New License File”. Delete the work directory, restart the application server, and try logging into JasperReports Server again.|
|•||The Djs.license.directory property in your application server startup environment is incorrectly set:|
For example, in Windows the correct setting looks like this:
In Linux, the correct setting looks like this:
The specified directory must contain the license file, named jasperserver.license. The property is set in JAVA_OPTS in the standalone.conf file. It must contain the location of your license file, which is usually the <js-install> directory:
<tomcat>/bin/setclasspath.bat/.sh or bin/setenv.bat/.sh
<jboss>\bin\standalone.conf.bat or <jboss>/bin/standalone.conf
Failure to Unlock TIBCO JDBC Driver Error
When you use one of the TIBCO JDBC drivers, the server checks for a valid JasperReports Server license in the correct location. If no license is found, you'll see an error like this:
|Failed to unlock TIBCO JDBC driver. Please check the license file.|
This is essentially a "License not found" error. Make sure the jar file for the TIBCO JDBC driver jar is located in JasperReports Server's jasperserver-pro/web-inf/lib directory, for example, <tomcat_home>/tomcat/jasperserver-pro/web-inf/lib. Do not place the driver jar outside the jasperserver-pro directory, for example, in the <tomcat_home>/lib directory. The TIBCO driver jar files are Jaspersoft-specific and will not work with other applications.
If moving the jar file doesn't resolve this error, use the methods in License Not Found Errors.
License Not Found or License Corrupt Error with Tomcat as a Service
If you have Tomcat running as a service in Windows, the installer attempts to make the proper updates so the server license file is found at when you start the application server. If the installer is unsuccessful, make sure you took the steps described in License File for Existing Tomcat as Windows Service.