000025441 - How to shut down connections to Progress database when the normal Start and Stop Control Panel applet is not finishing the job

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

Article Content

Article Number000025441
Applies ToMicrosoft Windows
RSA Authentication Manager 6.1
IssueHow to shut down connections to Progress database when the normal Start and Stop Control Panel applet is not finishing the job
 RSA AuthenticationServer will not start and it is NOT possible to delete or rename *.lk (lock) files in the ACEDATA directory
Replica is authenticating users
Microsoft Services show that all RSA Authentication Manager process are stopped
Although RSA Authentication Manager is stopped, it seems as if there are still connections alive to the Progress database
lock files (*.lk) cannot be removed or deleted
Error: "General Error - Broker server log file exists in ACE data directory that could not be removed. Error 32" in Event Viewer / Application Log
Violation error when trying to remove lk files
RSA Authentication Manager will not start properly
RSA Authentication Manager does not start properly after a reboot
RSA Authentication Manager does not start
Rebooting Authentication Manager machine when server start is set to manual still creates lock files in the ACEDATA directory
Using the Progress utility _mprshut in the RSA Authentication Manager\rdbms32\bin directory shows there are still active connections to the database
CauseThere is possibly a fault on a portion of the hard drive area where the RSA Authentication Manager database is stored; hence, it is impossible to remove or delete the lock files or completely stop the connections to the database
Power Outages can cause the database to shutdown unexpectedly and lock (.lk) still exist
Resolution

For example, if your Authentication Manager software is installed at C:\Program Files\RSA Security\RSA Authentication Manager, the command to run to close sdserv database connections is as shown below:

1. Change directory to C:\Program Files\RSA Security\RSA Authentication Manager\rdbms32\bin

2. Run   _mprshut -0 "C:\Program Files\RSA Security\RSA Authentication Manager\data\sdserv"   (this will open a text based menu system)

3. Chose number 8. Shut Down Database

4. Chose number 2. Unconditional Shutdown

Repeat this procedure for the sdlog database:

_mprshut -0 "c:\Program Files\RSA Security\RSA Authentication Manager\data\sdlog"

The lock files (any file with extension .lk) should now be gone. 

If the problem happens again follow the above procedure again and then the step below

To prevent this issue from occurring again, copy the contents of DATA directory into another folder named data_new (c:\ Program Files\RSA Security\RSA Authentication Manager\data_new).

 

Then, rename the DATA (c:\ Program Files\RSA Security\RSA Authentication Manager\data) directory to old_data (c:\ Program Files\RSA Security\RSA Authentication Manager\old_data) and rename the new_data to data (c:Program Files\RSA Security\RSA Authentication Manager\data).

 

Lastly, start the RSA Authentication Manager services from the Control Panel applet. (Start ? Programs ? RSA Security ? RSA Authentication Manager Control Panel)
Notes  
Legacy Article IDa37092

Attachments

    Outcomes