We recommend that you first make sure that you have the most current version of FusionReactor installed as recent updates include license and activation fixes. You can download the most current version from the FusionReactor download page.
In the following section, we list the most often reported problems with the FusionReactor license and activation process as seen from the user's perspective. The typical causes of these problems are discussed subsequently, along with the steps necessary to solve them.
The runtime user of the server on which FusionReactor is installed requires read/write access to the Java System Preferences Backing Store. Depending on the operating system, the location of this data store is different. On Windows the data is stored in the registry hive HKEY_LOCAL_MACHINESOFTWAREJavaSoftPrefs, the data belonging to FusionReactor is in HKEY_LOCAL_MACHINESOFTWAREJavaSoftPrefscomintergralfusionreactor.
Page 14 of the FusionReactor Installation Guide provides you with instructions how to adjust the permissions of this store.
On Linux and Solaris the data is typically stored in the directory /etc/.java/.systemPrefs as a hierarchy of directories containing XML files. The data belonging to FusionReactor is in the directory /etc/.java/.systemPrefs/com/intergral/fusionreactor. To set the necessary permissions execute the following command as user root:
chmod -R 777 /etc/.java/.systemPrefs
Alternative locations of the System Preferences Backing Store
Some JVMs try to create the System Preferences Backing Store in the directory $JAVA_HOME/.systemPrefs as a fallback solution if the directory /etc/.java/.systemPrefs cannot be created where $JAVA_HOME denotes the directory where the JVM itself is located (e.g. /opt/coldfusionmx/runtime/jre ).
We strongly recommend you to use /etc/.java/.systemPrefs as the one and only location of the System Preferences Backing Store. In case there is already data from other applications in $JAVA_HOME/.systemPrefs you should move it to /etc/.java/.systemPrefs and delete $JAVA_HOME/.systemPrefs afterwards (after you have adjusted the permissions of /etc/.java/.systemPrefs properly).
Clear the System Preferences Backing Store
If you attempt to install a license and you get the error message mentioned before:
Can not upload license: null
or simply
null
then you should stop the application server, clear the content of the Java System Preferences Backingstore and restart the application server.
On a Windows machine run the registry editor (regedit.exe or regedt32.exe) and then delete the key
HKEY_LOCAL_MACHINESOFTWAREJavaSoftPrefscomintergralfusionreactor
On a UNIX machine as user root delete the directory
/etc/.java/.systemPrefs/com/intergral/fusionreactor
If the permissions are configured correctly uploading a license and activating it will work properly afterwards.
On MacOS the System Preferences are stored as a set of *.plist files under the /Library/Preferences folder. Once the application server has stopped delete the file /Library/Preferences/com.intergral.fusionreactor.plist to clear all Preferences belonging to FusionReactor.
This bug has been introduced with version 6 of the Linux and Solaris SUN Java VM and unfortunately has not been fixed even in the recently released version 6.0_05. We have a technote available at https://www.fusion-reactor.com/support/kb/FRS-168.cfm which provides you with detailed instruction how to apply a fix for this bug.
If you upload a license with Firefox and nothing seems to happen (except that you have to login again) check the reactor-0.log file for the typical error message (see also https://www.fusion-reactor.com/support/kb/FRS-45.cfm) shown below
... javax.crypto.IllegalBlockSizeException: Input length must be multiple of 8 when decrypting with padded cipher at com.sun.crypto.provider.SunJCE_h.b(DashoA12275) at com.sun.crypto.provider.SunJCE_h.b(DashoA12275) at com.sun.crypto.provider.SunJCE_ae.b(DashoA12275) at com.sun.crypto.provider.PBEWithMD5AndDESCipher.engineDoFinal(DashoA12275) at javax.crypto.Cipher.doFinal(DashoA12275) ...
If multiple retries of uploading the license file again do not change this try to upload the license from a different browser and/or computer. If this does not help neither manually copy the license file to FusionReactor/license/license.lic and restart the server.
As mentioned in the overview of this document there is a hotfix available that fixes the bug FR1409 in the previous FusionReactor version 3.0.0 where a license can only be activated if the computer has a connection to the Internet. Download: fusionreactor-hotfix1409.zip. It comes as a ZIP file containing a new version of the FusionReactor Java library (fusionreactor.jar) together with instructions how to apply the fix. However, we recommend to upgrade to a newer version, which does not require this hotfix.
Type: | Technote |
---|---|
Issue Number: | FRS-198 |
Components: | License + Activation |
Environment: | |
Resolution: | Fixed |
Last Updated: | 30/Jul/11 12:02 AM |
Affects Version: | 3.0, 3.0.1 |
Fixed Version: | 3.0, 3.0.1, 3.5 |
Server: | ColdFusion 6, ColdFusion 7, ColdFusion 8, ColdFusion 9, Flex Data Services, JBoss, Jetty, JRun 4, LiveCycle Data Services, Railo, ServletExec, Tomcat, WebSphere, WebLogic |
Platform: | Windows XP, Windows 2000, Windows 2003, Linux, MacOS, Solaris, Windows Vista |
Related Issues: |
FRS-45: Why can’t I upload my license file (using Firefox)? FRS-168: FusionReactor trial expires immediately on a Java6 VM running on Linux or Solaris FRS-204: Safari web browser fails to upload license |
Comments are closed.