My Oracle Support Banner

Essbase: Essbase Server Fails To Start After Upgrading Java Development Kit (JDK) to JDK1.7.0_291 (Doc ID 2758842.1)

Last updated on MAY 18, 2022

Applies to:

Hyperion Essbase - Version 11.1.2.4.042 and later
Information in this document applies to any platform.

Symptoms

After Upgrading Java Development Kit (JDK) to JDK1.7.0_291 following the Doc ID 2351499.1  Essbase fails to start with below error:


Essbase.log

<Log_TimeStamp>/Info(1051224)
Can not load JVM from location in essbase.cfg [X:\Oracle\Middleware\jdk160_35\jre\bin\server\jvm.dll], OS status [The specified module could not be found.]. Will try to load from library path

<Log_TimeStamp>/Error(1051225)
JVM load failed [jvm.dll], OS status [The specified module could not be found.]. Single Sign-On Initialization Failed !

<Log_TimeStamp>/Info(1056815)
Essbase 64-bit - Release 11.1.2 (ESB11.1.2.4.042B066)

<Log_TimeStamp>/Info(1051232)
Using English_UnitedStates.Latin1@Binary as the Essbase Locale

<Log_TimeStamp>/Info(1051739)
Create essbase_sec.validating during Essbase start up

<Log_TimeStamp>/Error(1051527)
In Shared Services Security mode it is not possible to start Essbase when single sign on initialization fails.

Changes

 Java is upgraded to JDK1.7.0_291

Cause

To view full details, sign in with your My Oracle Support account.

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


In this Document
Symptoms
Changes
Cause
Solution
References


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