java.lang.IllegalArgumentException: Executable name has embedded quote when Running Batch Engine Using Seeded 'RunEngine' Workflow 12.2.4.1 (Doc ID 1969804.1)

Last updated on MAY 15, 2015

Applies to:

Oracle Demantra Demand Management - Version 12.2.4.1 to 12.2.4.1 [Release 12.2]
Information in this document applies to any platform.

Symptoms

On : 12.2.4.1 version, Engine

ACTUAL BEHAVIOR
---------------
Cannot run Batch Engine using seeded 'RunEngine' workflow. Fails on 'RunWindowsForecast'

When starting the seeded 'RunEngine' Workflow it fails on the step 'RunWindowsForecast'.

Tried using the seeded command line for 'RunWindowsForecast' which was "#application_root#\..\..\Demand Planner\Analytical Engines\bin\EngineManager.exe" 1 1.

I have also tried changing this command line to: "D:\Demantra\Demantra_12.2.3\Demand Planner\Analytical Engines\bin\EngineManager.exe" 1 1 however this also failed at the same step.




ERROR
-----------------------
2015-01-07 12:51:27,233 GMT [ExeStepExecutionThread] FATAL workflow.general: Executable name has embedded quote, split the arguments
java.lang.IllegalArgumentException: Executable name has embedded quote, split the arguments
    at java.lang.ProcessImpl.isQuoted(ProcessImpl.java:52)
    at java.lang.ProcessImpl.getExecutablePath(ProcessImpl.java:85)
    at java.lang.ProcessImpl.<init>(ProcessImpl.java:127)
    at java.lang.ProcessImpl.start(ProcessImpl.java:28)
    at java.lang.ProcessBuilder.start(ProcessBuilder.java:452)
    at java.lang.Runtime.exec(Runtime.java:593)
    at java.lang.Runtime.exec(Runtime.java:431)
    at java.lang.Runtime.exec(Runtime.java:328)
    at com.demantra.workflow.step.ExeStep.run(ExeStep.java:338)
    at java.lang.Thread.run(Thread.java:662)

2015-01-07 12:51:27,233 GMT [WFProcess_30] ERROR dpweb.general: Process ID:  782956
Schema ID:   1313
Schema name: 'Run Engine'
Step ID:     'Step2'
Step name:   'RunWindowsForecast'

Error description 'Program internal error:'



STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Started Workflow Manager, then started 'Run Engine' workflow.
2. Workflow fails straightaway on the seeded workflow step 'RunWindowsForecast'.



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