If the component cannot be launched by inserting into Office applications or the object cannot be copied onto the clipboard from MarvinSuite or from Marvin Editor component, then it hints an installation/uninstallation problem or a mismatch in the running mode. The first thing we recommend to check is the RunningMode flag in the registry. HKEY_LOCAL_MACHINE\SOFTWARE\ChemAxon\MarvinOLE
is decimal value numbering from 1.
RunningMode key is deleted! - Marvin OLE will be running in .NET mode by default.
Java Mode (1) - Marvin OLE is running in Java mode.
.NET mode (2) - Marvin OLE is running in .NET mode even if Java mode was installed.
Data transfer mode (3) - Marvin OLE is running without GUI. (Not recommended)
If RunningMode is set to Java (1), Marvin OLE will search for the Java infrastructure, the Marvin Beans. To be able to find it, the following registry path should contain the referenced Marvin Beans isntallation folder and its version:
C:/Program Files/ChemAxon/MarvinBeans/lib 18.104.22.168
If it is not there, Marvin OLE cannot be launched in Java mode.
In this case the administrator should either make correction in the referential folder by adding the correct path with '/' slash, or should delete the whole ReferenceFolders regsitry key, and delete(change) the RunningMode key to .NET (2).
This is the common problem, which might occur especially with early version of installers like 5.3.x series.
If Oracle Java environment damaged or no jvm installed locally providing jni bridge it is recommended for the administrator to change the registry accordingly to .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/StandaloneModeOn.reg accordingly.
If the desired mode is standalone editing mode (Marvin OLE is displayed in a separate window end it even runs in-placed) then it is worth running StandaloneModeOff.reg first and StandaloneModeOn.reg afterwards again to clear up the registry.
Adminsitrator wants to set the Standalone Mode globally for all users but on some users machines it is still in in-palce editing mode. In this case it is worth checking if the user has overriden 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 choosen the in-palce mode explicitly. The key either should be deleted or needs to be set to 1 for eliminating the problem.