Salesforce

OpenEdge Ubroker java processes fail to start after Windows 10 Creators Update is installed

« Go Back

Information

 
TitleOpenEdge Ubroker java processes fail to start after Windows 10 Creators Update is installed
URL Nameubroker-java-processes-fail-to-start-after-windows-10-creators-update-is-installed
Article Number000183154
EnvironmentProduct: OpenEdge
Version: 10.x, 11.x
OS: Windows 10
Other: Windows 10 Creators Update Version 1703 (OS Build 15063.0)
Question/Problem Description
Ubroker java processes fail to start after Windows 10 Creators Update is installed.
Nameserver, AppServer, and WebSpeed components fail to start with error 8297.
The AdminServer shows the jvmstart command for the UBroker processes but there are no logs files created
Advanced logging (Article How to increase the logging level for the OpenEdge AdminServer?) shows the java processes are started but immediately shutdown
Ubroker java processes only fail to start when the AdminServer is started as a Windows Service
Steps to Reproduce
Clarifying Information
WIN+R: winver shows Windows 10 Version 1703 (OS Build 15063.0) or later
Error MessageUnable to start <service name> (8297)
Defect NumberEnhancement PSC00356583
Enhancement Number
Cause
The Windows 10 Creators Feature update introduced new features which prevent jvmStart from starting java.exe (UBroker processes)
 
Resolution
Upgrade to 11.6.4 (if currently running 11.6.x) or to 11.7.1 or later (if running 11.7).

For older versions of OpenEdge, namely, 10.2B 08, 11.4 and 11.5.1, contact Progress Technical Support for the latest hotfix for your platform for your version.
The earliest Hotfixes for 10.2B, 11.4, 11.5.1 and 11.6.3 where the issues are addressed as follows:
  • 10.2B0874 
  • 11.4.0.055
  • 11.5.1.048
  • 11.6.3.023
Going forward, Progress is treating Windows 10 Feature updates as a new Certification which we aim to align with the Current Branch for Business (CBB) timelines. For further information refer to Article  Certification for Windows 10, the Creators Update, and future Feature Updates  

For Development and Production environments, investigate subscribing to the CBB roll-outs by deferring feature and quality updates. These environments should only be on the early adopter CB Service Branch if they are Test or QA environments that need the Microsoft update verified to ensure that there will be no impact when it's rolled out later through the CBB branch.
Workaround
Workaround 1:

Rollback the Windows Creators Update.

Workaround 2:

Start the AdminServer from the command line with proadsv

Workaround 3: 

Copy the jvmstart command from the AdminServer log file  and execute it from the proenv command line

Workaround 4:

In Virtual Machine, drop the number of CPU to 1 
In Physical machine, set CPU cores to 1 and disable Hyper-Threading.
Notes
Keyword Phrase
Last Modified Date11/20/2020 7:09 AM

Powered by