Think innovative

RSA Authentification Manager 7.1 Database Server not starting

By on Oct 14, 2013 in RSA | 8 comments

You are receiving this error from your RSA Server:


com.rsa.common.UnexpectedDataStoreException: System was modified beyond the allowed threshold, cannot decrypt.

or that one:
Log Name:      System
Source:        Service Control Manager
Date:          14.10.2013 09:37:58
Event ID:      7034
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
The RSA Authentication Manager Database Instance service terminated unexpectedly.  It has done this 8 time(s).



Start RSA Util with the following parameters. This will reset the encrypted file store

C:\Program Files\RSA Security\RSA Authentication Manager\utils>rsautil manage-secrets -a recover -m yoursuperadminpasswordhere
Machine fingerprint restored successfully.


RSA Version: RSA Authentification Manager 7.1 SP4

Please leave a comment, if this saved you some time 🙂


  1. Hello.This article was really interesting, especially since I was investigating for thoughts on this matter last Thursday.


    October 17, 2013

  2. Thanks this helped me solve a problem with an RSA Server I had virtualised, an unhelpful RSA Technical support person whom I spoke to on the phone did not even suggest this fix!

    William Third

    October 24, 2013

    • Hi William,

      Thank you for your comment 🙂

      Cool, that it worked for you 😉

      I recently upgraded our RSA Authentification Manager to Version 8. The migration was easy and well documented. Version 8 comes in a virtual Linux appliance packed as OVF-template. Very nice to handle with VMware ESX.

      There is no Windows version anymore. The service is stabler, no more problems with the oracle database.

      I can really recommend upgrading to version 8 if your company has the extra money.

      Best regards,
      Joey Kappe

      Joey Kappe

      October 24, 2013

  3. Time definitely saved – thanks!


    May 29, 2014

  4. After Windows Automatic Updates today,the database instance failed to start, your suggestion fixed it. Thank you so much.

    Edgar Morillo

    December 14, 2016

  5. Hi,

    I got this error when I start the RSA VM on different HW than it was installed. Very annoying issue if you have automatic Failover with flexibel CPU Features.

    My solution is to move the VM to the installation host and everything is fine. As soon, as there is another CPU Generation runnng, you’re f****d…
    This solution took a few hours of my life. Hopefully RSA will improve their license checks for virtual Environments.



    December 18, 2016

    • Hi Fabian,
      Thank you for your contribution to that solution.

      Do I understand you correctly?
      You deployed the virtual RSA VM.
      Then you changed the hardware of your old ESX host.

      Did you just change your hardware or also upgraded your ESX/ESXi Host?

      Which version of ESX/ESXi are you running?
      Did you use vMotion?

      Best regards,

      Joey Kappe

      December 18, 2016

Post a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.