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:

Hyperion Essbase - Version 11.1.2.1.000 and later
Microsoft Windows x64 (64-bit) - Version: 2008 R2
***Checked for relevance on 19-May-2014***

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

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms