Compliance Checker Getting Help and Support

If you have any questions concerning Compliance Checker, please contact compliance-checker-support@chemaxon.

KNOWN ISSUES

Missing backslash and backslash1..6 in JSON reports
Japanese fonts in reports
Browser incompatibility issues
Mac and Windows upgrade
Single check
File check
Report generation
Startup

Missing backslash and backslash1..6 in JSON reports

• If the input contains backslash or backslash followed by number 1..6 in the input field then these characters will be missing from the JSON report

As a workaround \ can be replaced by \\ or in the case when \ is followed by a character which is used as a regular expression then \\ (4 backslashes) can be used.

Use please check-with-id endpoint so that there is no need for adding the input structure as property.

Japanese fonts in reports

• The 'What is controlled' field contains Japanese characters for the JP hits

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 font set to the /usr/lib/jvm/.../jre/lib/fonts/ folder and adding the report.font.name= to the application.properties.

(E.g. the kochi-gothic-subst.ttf font set, that can be downloaded from https://osdn.net/projects/efont/releases/ - but you need to clarify it's licensing with the issuer.)

This will be fixed after licensing issues of an appropriate font set will be cleared.

Browser incompatibility issues

• In version 19.10 some browser incompatibility issues were found with Edge and IE11.

We suggest using the Chrome browser but Firefox is working as well.

These incompatibility issues with Microsoft's browsers are investigated and will be fixed ASAP.

Mac and Windows upgrade

• The Mac and Windows installer overwrites the application.properties file in its default location

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.

After the upgrade the application.properties file (in the default ../cc-config/config folder) should be replaced with the saved config file.

Single check

• 2D-Clean issue

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.

File check

• Cannot read molecule file

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.

If the first 6 lines of the file do not contain invalid structure records then this file import error does not occur!

Report generation

• Finished status

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.

After a Page refresh , the Download button and the Generated file name is displayed correctly.

Startup

• Slow startup on Fedora-based systems

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 safe SecureRandom seed.