000016621 - Transaction Log on Archer Configuration Database is Full

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

Article Content

Article Number000016621
Applies To5.0
5.1
5.1.1
5.1.2
IssueTransaction Log on Archer Configuration Database is Full
[A company] called in reporting that the job engine would not start, SSO wasn't working and they were getting prompted for credentials when accessing the Archer Control Panel.
 
Resolution

We looked in the logs and found that the transaction log file on the Archer Config database was full.  We decided to shrink the files on both the Config and Archer Instance databases to free up space.
1. Access MS SQL Server Management Studio
2. Right click the Config database and go to Tasks --> Shrink -->Files
3. In the File Type box, select Log
4. Make sure "Release Unused Space" is selected and click OK


You can do the same for the Instance database as well.  As always, make sure their Recovery Model is set to simple instead of full to keep the logs from filling up so quickly.

Legacy Article IDa58418

Attachments

    Outcomes