000012776 - DPM Server initialization fails when using a Safenet HSM

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 Number000012776
Applies ToRSA Data Protection Manager Appliance 3.5.x
Safenet Luna SA5
Issue
25 Feb 2014 17:51:06,153 1393368666072 INFO http-bio-8443-exec-1 - Client : Internal, Initialized secure random, algorithm: HMACDRBG128, provider: JsafeJCE

25 Feb 2014 17:51:06,180 1393368666072 INFO http-bio-8443-exec-1 - Client : Internal, generateKey() - About to get key

25 Feb 2014 17:51:06,589 1393368666072 ERROR http-bio-8443-exec-1 - Client : Internal, Unable to generate a master key.

25 Feb 2014 17:51:06,590 1393368666072 ERROR http-bio-8443-exec-1 - Client : Internal, Installation has failed.  The install process may need to be reset before continuing.

DPM Server initialization fails when using a Safenet HSM
CauseSafenet HA slot is configured
ResolutionOn the first appliance to be initialized with a Safenet HSM, if the deployment must use the Safenet HA slot, make sure to disable and completely turn off High Availability when running the Quick Setup. If it is already turned on, turn it off, bounce Tomcat, and run the Quick Setup.
Legacy Article IDa64476

Attachments

    Outcomes