Technote

Under UNIX/Linux the reason for this could be different user:group settings of FusionReactor and ColdFusion MX. Please make sure that the user and group of FusionReactor (usually installed in /opt/fusionreactor) is the same as of the ColdFusion MX server. If not become root and do the following

chown -R : /opt/fusionreactor

where you have to replace and with the actual values of your ColdFusion MX installation (e.g. cfusion:other or jrun:bin). Adjust the path to FusionReactor according to your environment.

If FusionReactor runs with the privileges of the ColdFusion MX server it presumably cannot write to /opt/fusionreactor where it has to store its configuration and log files.

The same behaviour can be noticed on Windows if the ColdFusion MX service has been changed to run under a dedicated user account (with restricted permissions).

This user account needs enough rights to write to the FusionReactor directory and (at least once) to the registry hive HKEY_LOCAL_MACHINE.