LiveCycle Help Content Team

After running the standalone (non-Turnkey) JBoss LiveCycle ES Installer, you select the “Start LiveCycle Configuration Manager” option, but nothing happens. You then try to browse to the directory where you installed LiveCycle ES (e.g. D:\Adobe\LiveCycle8.2\configurationManager\bin), double-click the ConfigurationManager.bat file, and a Command Prompt window appears and closes in seconds. The LiveCycle Configuration Manager does not start. You check the log file (ConfigurationManager.000), but there are no log messages indicating the error.

Not sure what to do? Neither did I when I first encountered this situation. But, here is what you do:1. Open a Command Prompt window and navigate to the LiveCycle Installation directory. For example, here is what I typed: cd D:\Adobe\LiveCycle8.2\configurationManager\bin2. Next, type: ConfigurationManager.batYou now see the error message that flashed in front of you before. It turned out that in my case I did not properly define the JAVA_HOME and PATH environment variables. For instructions on setting these variables, refer to the Installing LiveCycle ES documentation.The reason the ConfigurationManager.000 log file is empty is because the LiveCycle Configuration Manager needs the JAVA_HOME variable defined before it will even start. If it cannot start, it cannot write to the log file.