000011649 - Node Manager Service fails to start

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000011649
Applies ToWindows 2008 R2
Authentication Manager 7.1 SP4
IssueNode Manager Service fails to start with 1067 dependency error
C:\program file\RSA Security\RSA Authentication Manager\appserver\weblogic\common\nodemanager\logs\nodemanager_server.log.n has

<Debug> <server> <mcc-rsa-2_server> < Lock file C:\Program Files\RSA Security\RSA Authentication Manager\server\servers\mcc-rsa-2_server\data\nodemanager\mcc-rsa-2_server.lck exists:false>
<Debug> <server> <META-INF> < Lock file C:\Program Files\RSA Security\RSA Authentication Manager\server\servers\META-INF\data\nodemanager\META-INF.lck exists:false>
<Debug> <server> <rsa-help> < Lock file C:\Program Files\RSA Security\RSA Authentication Manager\server\servers\rsa-help\data\nodemanager\rsa-help.lck exists:false>
<Debug> <server> <tmp> < Lock file C:\Program Files\RSA Security\RSA Authentication Manager\server\servers\tmp\data\nodemanager\tmp.lck exists:false>
<Debug> <server> <upload> < Lock file C:\Program Files\RSA Security\RSA Authentication Manager\server\servers\upload\data\nodemanager\upload.lck exists:false>

<SEVERE> <Fatal error in node manager server>
java.lang.InternalError: Could not instantiate SSLContextWrapper
503 error on Security console
ResolutionAfter verifying Name resolution, and that Fully Qualified Doman Name (FQDN) and IP had not been changed, customer restarted services, but still could not start Node Manager.  They then rebooted Windows, and all services started.
Legacy Article IDa63686

Attachments

    Outcomes