If a component cannot be launched by inserting it to an Office application or the object cannot be copied to the clipboard from MarvinSuite or the Marvin editor component, then the problem is related to installation/uninstallation or a mismatch in the running mode. The first thing we recommend is to check the
RunningMode flag in the registry.
This registry key is accessible only for administrators.
RunningMode is set to Java (1), Marvin OLE searches for the Java infrastructure, the Marvin Beans. To be able to find it, the following registry path must contain the referenced Marvin Beans installation folder and its version:
If it is not there, Marvin OLE cannot be launched in Java mode.
In this case, the administrator must either make corrections in the referential folder by adding the correct path with or must delete the whole
ReferenceFolders registry key, and delete(change) the
RunningMode key to .
If the Java environment is damaged or no JVM is installed locally providing the JNI bridge, it is recommended for the administrator to change the registry according to the .NET version or to repair the Java environment.
In this case either the user should find a JNI invocation error in the Marvin OLE log, and check running mode (see above) or the EMF generator component has a problem and then its log file contains hints of the origin of the problem.
For simple troubleshooting please run the
StandaloneModeOff.reg or the
StandaloneModeOn.reg according to the problem.
If the desired mode is standalone editing mode then it is worth running
StandaloneModeOff.reg first and
StandaloneModeOn.reg afterward again to clear up the registry.
The administrator wants to set the Standalone Mode globally for all users but on some users' machines, it is still in in-place editing mode. In this case, it is worth checking if the user has overridden any global settings by a local one here:
HKEY_CURRENT_USER\Software\Chemaxon\MarvinOLE\Settings\StandaloneMode. If this key contains 0 value, it means that the user has chosen the in-place mode explicitly. The key either should be deleted or needs to be set to 1 for eliminating the problem.