Engine On Slave Machine Was Created, But Could Not Be Initialized (Doc ID 853027.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Demantra Real-Time Sales and Operations Planning - Version: 2.5.9 and later   [Release: 2 and later ]

Symptoms

-- Problem Statement:
On Demantra 7.2.0 Build 30 in Production:
When running the Demantra batch engine from the Engine Administrator,
the following error occurs:

ERROR
 Engine on machine xxx18612.yyy.com was created, but could not be
initialized. HRESULT=0x80004005 - Unspecified error
ERROR Engine on machine xxx18613.yyy.com was created, but could not be
initialized. HRESULT=0x80004005 - Unspecified error

-- Steps To Reproduce:
The issue can be reproduced at will with the following steps:
a. Login to XXX18611 remote machine (Production Application Server)
b. Navigate to D:\Oracle Demantra Spectrum\Demand Planner\Analytical
Engines\bin\EngineAdministrator.exe
c. Go to Settings > Configure
d. Hit Register
e. Go to File > Run Engine
d. Login using username 'ZZZDEMANTRA' connecting to service: XXX18614.yyyy.com
e. Select Run Mode: Batch and click on Run Engine
f. Monitor engine logs under D:\engine2k\xxx18614.yyyy.com_ZZZDEMANTRA

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