Not Able to Externalize Users from Essbase Server to Shared Services Using Essbase Admin Console

When Essbase is run in background the following Error message is displayed:

"Can not load JVM from location in essbase.cfg
JVM load failed, info [jvm.dll], Single Sign-on Initialization failed! "



When trying to externalize from EAS console the following message appears:

"error: 1051549 Can not convert Analytic Services to Shared Services mode when Analytic Services is not configured with Shared Services or the initialization process has failed."

Cause
The path is wrong in the JVMMODULELOCATION in Essbase.cfg.



Solution
To resolve this issue take the following steps:
1. Stop Hyperion S9 BI+ Analytic Services 9.3.1 .

2. Stop Shared Services, Essbase Administration Services, Hyperion Open LDAP services.

3. Correct the path of JVMMODULELOCATION in the Essbase.cfg file.
4. Save the file.
5. Start Shared Services, Essbase Administration Services, Hyperion Open LDAP services.

6. Start Essbase Server in foreground on your 64 bit Server.
7. Check whether you are still getting error "Can not load JVM from location in essbase.cfg " if not stop Essbase, and start it normally. Please proceed to externalize the user in EAS console.

To set the JVMMODULELOCATION parameters, you must specify the full path and file name
of the Java Virtual Machine (JVM) library in Essbase.cfg. The location and name of the library varies, depending on the JRE version and the operating system that you are using.
Following are some of the entries:

32-bit Windows:
JRE ----HYPERION_HOME\common\jre\sun\1.5.0

JVM.DLL ----HYPERION_HOME\common\jre\sun\1.5.0\bin\server\jvm.dll


64-bit Windows:
JRE -----HYPERION_HOME\common\JRE-IA64\Sun\1.4.2
JVM.DLL---HYPERION_HOME\common\JRE-IA64\Sun\1.4.2\bin\server\jvm.dll



64-bit Windows on AMD Opteron and Intel Xeon:
JRE---HYPERION_HOME\common\JRE-AMD64\Sun\1.5.0
JVM.DLL-----HYPERION_HOME\common\JRE-AMD64\Sun\1.5.0\bin\server\jvm