FDM Error – Unable to create Load Balance Manager object Error=cannot create activex componenent

When accessing FDM via the web, the following error message is returned:

Unable to Create Load Balance Manager Object!
When launching the FDM Load Balance Server Configuration and attempting to update with the service account password receive error message:

“Unable to create Load Balance Manager object!
Please verify that the user name, password, and domain are correct
Error=Cannot create ActiveX component.”

The software is unable to create the FDM Load Balance Manager DCOM object and results in the error.

This error message is caused by one of three items:

1) The Account entered in the Load Balance Config has been locked out
2) The Id/Pwd entered into the load balance configuration is invalid
3) There is an invalid id set in the Security Tab of the Load Balance Manager DCOM object.

Any of these items would result in being unable to create the Active X component necessary.

Reset Identity and Security on FDM Load Balance Server DCOM object

Perform the following:

1) Choose Start/Run and type Dcomcnfg
2) Expand Component Services\Computers\My Computer\Dcom Config and locate the object {E652643D-6CC1-48AC-915D-01842B04F292}
3) Right-click on this item and choose “Properties” and click on the “Security” tab
4) Click the “Edit” button and remove all users/groups and click OK, then set the radio button to “Use Default”
5) Click the “Edit” button under Access Permissions and remove all users/groups and click OK, and set the radio button to “Use Default”
6) Click on the “Identity” tab and remove the ID in the “This User” field and set the radio button to “The Launching User” and click “Apply” and “OK”
7) Re-launch the FDM Load Balance Config and reset the service account, application servers, and MSAD Configuration.


Essbase Administration Services (EAS) Crashing While Editing Outline

EssbaseAdminService crashes frequently during outline editing while plenty of JVM memory available and JRE used is jrockit.  The jrocket dump file can be found under:


A dump file has file name such as jrockit.12826.dump.

If you review the jrocket dump, there is no out-of-memory issue but contain following message on a Linux system:

Error Message: Illegal memory access. [54]
Signal info : si_signo=11, si_code=1 si_addr=0x1cd
Version : Oracle JRockit(R) R28.2.5-50-153520-1.6.0_37-20121220-0843-linux-x86_64

The default size of a thread stack in jrockit is 320K for win64 and 1M for Linux64.  Depending on the request, the default may not be large enough.  When the stack overflows, there really is nothing obvious in the core or dump file.

To Fix –

Increase the size of the thread stack by adding/modifying the -Xss setting.


The -Xss setting will need to be added/modified in two locations:

1.  Navigate to <EPM_ORACLE_INSTANCE>\bin\deploymentScripts.

2.  Edit the setCustomParamsEssbaseAdminServices.cmd and add/modify the -Xss1M to the USER_MEM_ARGS setting.  For example:

USER_MEM_ARGS=-Xms128m -XX:PermSize=64m -XX:MaxPermSize=256m -Xmx4096m -Xss1M

3.  Add/Modify the -Xss setting to the Windows Registry.

a. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Hyperion Solutions\EssbaseAdminServices0\HyS9eas_epmsystem1.  If there is a JVMOption for -Xss, increase the value to 1m.  If a JVMOption for -Xss does not exist:

b. Create a new “String Value” entry with following name and value:

Value: Value:-Xss1M
With Y being equal to (current value of JVMOptionCount) + 1

c. Increase the value of the JVMOptionCount parameter by 1.

4.  Restart the EAS server.



1.  Navigate to <EPM_ORACLE_INSTANCE>/bin/deploymentScripts.

2.  Edit the setCustomParamsEssbaseAdminServices.sh.  Add/modify the option -Xss2m to the USER_MEM_ARGS setting.  For example:

USER_MEM_ARGS=-Xms128m -XX:PermSize=64m -XX:MaxPermSize=256m -Xmx4096m -Xss2M

3.  Restart EAS server.