Error Starting Essbase After Applying Microsoft Patches "Failed to initialize EPM Shared Services Security instance." (Doc ID 1377201.1)

Last updated on AUGUST 08, 2017

Applies to:

Symptoms

When attempting to start Essbase in the foreground and Shared Services after MS Security Patches were applied, the following error occurs:

Failed to initialize EPM Shared Services Security instance. Oracle Instance is not defined.It needs to be defined either as an environment variable or as a system argument.. Verify EPM System Registry configuration.

Warning: Invalid or Obsolete Configuration Setting - essbase.cfg(15): "InstanceName Essbase1"

Exception in thread "main" EPMCSS-00002: Failed to initialize EPM Shared Services Security instance. Oracle Instance is not defined. It needs to be defined either as an environment variable or as a system argument.. Verify EPM System Registry configuration.

Changes

Microsoft patches were applied.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.