Nodemanager Error " Unable to connect to the Node Manager. It may not be running or communications may be blocked by a firewall" (Doc ID 1565049.1)

Last updated on DECEMBER 13, 2016

Applies to:

Primavera P6 Enterprise Project Portfolio Management - Version 8.3 and later
Information in this document applies to any platform.
***Checked for relevance on 04-Dec-2014***

Symptoms

When running the automatic configuration wizard or while manually running EPPMCONFIG, an error occurs attempting to start the weblogic domain.

Evaluation of configuration log file (located in c:\p6eppm_1 folder) with a name similar to config_mm_dd_yy_hhmm.log (Example:  config_06_26_2013_0815.log) shows error:

OUTPUT>PRM-Starting Primavera Admin Server, Managed Servers, and Deployments
OUTPUT>PRM-Connecting to Node Manager...
OUTPUT>Connecting to Node Manager ...
OUTPUT><Jun 17, 2013 10:56:16 AM PDT> <Info> <Security> <BEA-090905> <Disabling CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true>
OUTPUT><Jun 17, 2013 10:56:16 AM PDT> <Info> <Security> <BEA-090906> <Changing the default Random Number Generator in RSA CryptoJ from ECDRBG to FIPS186PRNG. To disable this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true>
OUTPUT>PRM-Node Manager does not appear to be running. Attempting to start and reconnect...
OUTPUT>Connecting to Node Manager ...
OUTPUT>PRM-Unable to connect to the Node Manager. It may not be running,
OUTPUT>PRM-or communications may be blocked by a firewall.
OUTPUT>PRM-Completed. Returned error level: 1




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