If you have any questions concerning Compliance Checker, please contact email@example.com.
Contents of Japanese hits' (Category#: 7261-7268) What is controlled field cannot be correctly saved in PDF and SDF reports without installing an appropriate Japanese fontset to the /usr/lib/jvm/.../jre/lib/fonts/ folder and adding the report.font.name=<fontname> to the application.properties.
(E.g. the kochi-gothic-subst.ttf fontset, that can be downloaded from https://osdn.net/projects/efont/releases/ - but you need to clarify it's licensing with the issuer.)
We suggest to use the Chrome browser but Firefox is working as well.
The previously customized application.properties file should be saved to a backup before upgrading with the Mac and Windows installers, because these overwrite this configuration file in its default location.
Sometimes when NAME or SMILES is entered into the input box - and the 2D-Clean is slow - then the displayed structure is not 2D-Cleaned. This distorted structure image will appear even in the reports.
Clicking into the structure image the Marvin JS popup will already display the structure 2D-Cleaned. Or you can 2D-Clean it in Marvin JS by clicking the 2D-Clean button, or make any changes. When the structure image is acceptable for you then click OK in Marvin JS and Check on the Single check page.
If the file contains an invalid structure record in the first 6 lines of the file then the File check fails with the following error:
In this case the file - that contains single-line format structures - still can be checked with the Extended search function, and the invalid structure will probably get passed - as a "Not found" text.
A more correct workaround can be to rename the file to CSV extension and still use the File check function. This will send the invalid structure to Error.
Sometimes the web interface does not show the real status, but usually this can be solved by a Page refresh or reloading the page with Ctrl+F5.
A new report was generated from an earlier batch check and Finished was displayed in the Generated reports section of the batch check Summary dropdown when the report generation was finished.
On Fedora based systems (Fedora / RedHat / CentOS / etc) Java uses
/dev/random to generate the seed of
SecureRandom that is used to generate Session IDs. This causes a very slow first session generation on Compliance Checker services. You can change this value according to Oracle's documentation to have a faster but less safer SecureRandom seed.