$813 serverless mode not working Help please

Graham Stevens graham.stevens at gmail.com
Tue Jan 2 04:11:20 EST 2018

Hi Jay,

The third error, "The Java Virtual Machine failed to load", would 
indicate that you haven't set the path correctly to your JVM, without 
which Omnis is crippled.

In your   AppData\Omnis Software\YourOmnisExecutableDirectory\studio 
directory there is a config.json file in which you have to enter the 
path to your jvm.dll.  For example, on the Windows 10 machine here in 
the office, the "java" object looks like this:

  "java": {
         "resetClassCacheOnStartup": true,
         "jvm": "C:\\Program Files\\Java\\jre-9\\bin\\server\\jvm.dll"

HTH and a Happy New Year to you,

On 31/12/2017 18:46, Omnis Newbie wrote:
> Oh, you might be on to something, the following 4
> errors appeared in the trace log upon launching
> Omnis before even opening a Library.
> The first two look like db dams, the 3rd might
> have something to do with it I'm guessing but I'm
> very new to all of this stuff.  I do know that I have
> Java jdk 8 update 152 installed.  I'm using an old win7 machine btw.
> could the .NET error have anything to do with this?
> External Library File 'C:\Program Files\Omnis
> Software\OS8.1.3\xcomp\damdb2.dll' failed to load.
> OS Error: The specified module could not be found.
> External Library File 'C:\Program Files\Omnis
> Software\OS8.1.3\xcomp\damora8.dll' failed to
> load. OS Error: The specified module could not be found.
> The Java Virtual Machine failed to load
> Failed to load .NET layer, ensure Microsoft.NET
> is installed and OMDOTNET.DLL is registered
> upon opening up the library and testing the
> remote form no additional errors were added to the trace log.
> does this give you any additional ideas as to what is wrong?
> your help is much appreciated.

More information about the omnisdev-en mailing list