Error: "No JVM could be found . . ." when you start the Authoring Environment

Article:TECH112981  |  Created: 2006-01-06  |  Updated: 2007-01-21  |  Article URL
Article Type
Technical Solution


When you double-click the Authoring.exe file to start the Authoring Environment for the first time, you see the following error message:

No JVM could be found on your system.
Please define EXE4J_JAVA_HOME
to point to an installed JDR or JRE or download a JRE from


This problem happens when the files for the Authoring Environment are not in the \Program Files\Symantec\Critical System Protection\Console folder.

If you extracted the files to a different folder or to a subfolder that is under the Console folder, move the files to the Console folder. To do so, move the files and the Authhelp folder to the Console folder. Also move the contents of the extracted Conf folder to the Conf folder that is under the Console folder.

Technical Information
Included files

When you expand the file, the process extracts the following files and folders:
Conf (a folder)
Authhelp (a folder)

Move all files, not just the Authoring.exe file
If you move only the Authoring.exe file to the Console folder, you cannot start the Authoring Environment.

In this situation, when you double-click the Authoring.exe file to start the Authoring Environment, you see the error message "Load Error. Unable to load configuration settings. OK." When you click OK, you see the log on window. If you log on, you see the error message "An error has occurred during application startup. OK." When you click OK at this error message, the window closes and the Authoring Environment does not start.

Legacy ID


Article URL

Terms of use for this information are found in Legal Notices