license issue

User 204415f4a4

03-12-2008 12:58:19

Dear Szilard,





We have just installed ChemAxon components for PP 7.0.1. The license file that we have been using in the past for JChem 3.2.6 was placed in the PP server as stated in your installation document, but did not work for any Calculator plugin. When we replace it with the new 5.1.3 license file, the BCUT descriptors can be calculated but not HBA, HBD, logP… descriptors even though we have a license file for these plugins. The same thing for standardizer module.





Thank you in advance for your help.





Cheers,





ISI

ChemAxon 9c0afc9aaf

03-12-2008 18:57:27

Hi,





Old license files may not work with the latest version, above JChem 5.0 I recommend using the new version.





Above JChem/Marvin 5.0.5 the recommended way is to use an environment variable to point to the license file (opposed to copying it into a "chemaxon" directory under the home directory).





This method eliminating the possibility of dealing with different user homes and the potential confusion.


This is also the only way to install the license if your Pipeline Pilot server runs in impersonation mode.





The relevant part of the instructions from README.txt:
Quote:



If using JChem / Marvin 5.0.5 or better, the recommended way


to set the license is to create an environment variable CHEMAXON_LICENSE_URL,


It should point to the license file obtained from chemaxon on the file


system of the PP server.


Please remember to restart the PP server after setting / modifying this


environment variable.


NOTE: This is the only way to install licenses on a PP server running in


impersonation mode.
Tips:


- the variable should include the name of the license file, not just the enclosing directory, use absolute path please


- make sure the variable points to the correct license file (you can easily check its contents via a text editor)


- make sure you have restarted the Pipeline Pilot server after setting or changing this variable


- if you are getting a LicenseException the path to the license file should be included in the stack trace (press "Details" in the error dialog)





If this does not help you may send me the stack trace and the license file for analysis in e-mail (dorant at chemaxon dot com).





Best regards,





Szilard