SOLUTION

Workaround:

Start the Node Manager from command line instead of running it as a Windows service.

Permanent fix:

If the instance already exists:

1. stop the node manager service

2. uninstall node manager service by running DOMAIN_HOME\bin\uninstallNodeMgrSvc.cmd (if it doesn't work, run sc delete "service name")

3. backup DOMAIN_HOME\bin\installNodeMgrSvc.cmd

4. copy the following 3 lines from DOMAIN_HOME\bin\startNodeManager.cmd

set JAVA_OPTIONS=-Dreports.server.product.home=...
set JAVA_OPTIONS=-Dreports.bridge.product.home=...
set JAVA_OPTIONS=-Dreports.tools.product.home=...

and add them to DOMAIN_HOME\bin\installNodeMgrSvc.cmd after line

set JAVA_OPTIONS=-Dreports.product.home=...

5. run DOMAIN_HOME\bin\installNodeMgrSvc.cmd

 

In the case of a fresh installation (where the domain has not yet been created):

1. Apply Patch 22566394 right after the installation finished.

2. Continue with the configuration script.

NOTE

Please be aware this patch will only fix the issue for domains created *after* applying the patch. For an existing domain this issue can be fixed manually using the actions described in the If the instance already exists section (see above).

BUG:22566394 has been resolved starting in 12.2.1.2 version.