Abnormal Jar Packages Detection

This chapter provides solutions for abnormal JAR packages when using the Designer Environment Detection function.

Is the Jar Package Missing？

Problem: JAR package is missing in the classpath of %FR_HOME%\lib\{directory1}, {directory2}

 or %FR_HOME%\webapps\webroot\WEB-INF\lib\{directory1}, {directory2}

Log record: Error code: 11300108, missing jar: { }.jar (For example, designer.jar).

Reason: The Jar package is missing under the corresponding path.

Solution: Contact technical support to obtain the corresponding version of the Jar package, and put the Jar package under the corresponding path.

Is the Version of the Jar Package Consistent with the Server？

Note: The local environment is based on the designer folder. To keep the consistency of local environment and remote environment, versions of jar packages in designer folders need to be consistent with remote environment.

Problem: When the Jar package of the designer is inconsistent with the remote environment, a prompt pops up: Jar package version is inconsistent, { }.jar (For example, designer.jar).

Log record: Error code: 11300109, Jar package version is inconsistent:

Reason: The Jar package versions are inconsistent with the local environment or remote environment.

Solution: Update the Jar package version of the local environment and remote environment to the same version. For details of how to confirm versions, see About Software.

Whether There is a Conflict in Jar Packages？

Problem: There are Abnormal Jar packages in the path of %FR_HOME%\lib{directory1}, {directory2}

 or %FR_HOME%\webapps\webroot\WEB-INF\lib\{directory1}, {directory2}

Log record: Error code: 11300110, abnormal jar: { }.jar (For example, designer.jar).

Reason: There is a conflict in JAR packages.

Solutions:

1. If there is a conflict between the jar packages of the FineReport and the customized jar package, you can contact technical support for help.

2. If there is a conflict between the old and new versions of the Jar packages of the product, you need to confirm the needed version, retain it and delete the other one.

3. If there is a conflict in Jar packages of the third-party introduced in the product, the common problem is that a driver is placed under WEB-INF/lib, while the plugin depends on this different version of driver. For the situation, you can contact technical support for help.