000033753 - RSA Archer 5.x, 6.x users unable to login due to Instance database transaction log is full

Document created by RSA Customer Support Employee on Aug 12, 2016Last modified by RSA Customer Support on Oct 11, 2019
Version 4Show Document
  • View in full screen mode

Article Content

Article Number000033753
Applies ToRSA Product Set: Archer
RSA Version/Condition: 5.x
Platform: Windows
IssueUsers experiencing an issue with login into RSA Archer instance, due to instance database transaction log is full.
The error shown on the login page shows a generic message rather than the actual fault - e.g. "Warning: The system is unable to validate the user account. Please review your login credentials and try again."
User-added image

The actual error is observed in RSA Archer log file -e.g. Archer.w3wp.YYYYMMDD.xml log:

<E2ETraceEvent xmlns="http://schemas.microsoft.com/2004/06/E2ETraceEvent">
                <TraceRecord Severity="Error" xmlns="http://schemas.microsoft.com/2004/10/E2ETraceEvent/TraceRecord">
                    <Description>The transaction log for database 'INSTANCEDB' is full due to 'LOG_BACKUP'.
SQL statement: usp_update_user_login @userToken = 'LOGIN_SESSION', @userId = 2, @acctStatusId = 1, @graceLogins = 0, @lastAttempt = 'M/DD/YYYY h:mm:ss PM', @updateDate = 'M/DD/YYYY h:mm:ss PM', @failedAttempts = 1, @lastLoginAttempt = 'M/DD/YYYY h:mm:ss PM'</Description>
                        <ExceptionType>ArcherTech.Kernel.Utility.Data.ArcherDbException, ArcherTech.Kernel, Version=5.5.10200.1011, Culture=neutral, PublicKeyToken=null</ExceptionType>
                        <Message>The transaction log for database 'INSTANCEDB' is full due to 'LOG_BACKUP'.
SQL statement: usp_update_user_login @userToken = 'LOGIN_SESSION', @userId = 2, @acctStatusId = 1, @graceLogins = 0, @lastAttempt = 'M/DD/YYYY h:mm:ss PM', @updateDate = 'M/DD/YYYY h:mm:ss PM', @failedAttempts = 1, @lastLoginAttempt = 'M/DD/YYYY h:mm:ss PM'</Message>
   at ArcherTech.Kernel.Utility.Data.ArcherSqlDatabase.WrapDatabaseCall(DbCommand command, Action methodToWrap)
   at ArcherTech.Kernel.Utility.Data.ArcherSqlDatabase.ExecuteNonQuery(DbCommand command)
   at ArcherTech.Kernel.DataSource.Db.AuthenticationDataSource.UpdateUserLogin(UserLogin userLogin)
   at ArcherTech.Kernel.Utility.UserLoginUpdateHelper.UpdateLoginForFailure(InternalSessionContext sessionContext, UserLogin userLogin, SecurityEventType onErrorEventType)
   at ArcherTech.Kernel.Brokers.AuthenticationBroker.HandleInvalidCredentials(AuthenticationPluginResult validateCredentialsResult, UserLogin userLogin, InternalSessionContext sessionContext)
   at ArcherTech.Kernel.Brokers.AuthenticationBroker.Login(AuthenticationRequest request)</StackTrace>

CauseThe Transaction Logs for Archer Instance database is filled up.
This commonly occurs if the SQL Transaction Logs in the database are not maintained when the Recovery Model is set to Full.
  1. Transaction Log Maintenance - Manage the Transaction Log for instance Database

To shrink a data file

  1. In Microsoft SQL Server Management Studio's Object Explorer, connect to an instance of the SQL Server Database Engine and then expand that instance.
  2. Expand Databases and then right-click the database that you want to shrink.
  3. Point to Tasks, point to Shrink, and then click Files.
  4. Select the file type and file name.
  5. Select the Release unused space check box.

Note: Selecting this option causes any unused space in the file to be released to the operating system and shrinks the file to the last allocated extent. This reduces the file size without moving any data.

  1. Click OK.

  1. Optionally - configure the Recovery Model and ensure it is set to Simple

To view or change the recovery model

  1. In Microsoft SQL Server Management Studio's Object Explorer, click the server name to expand the server tree.
  2. Expand Databases
  3. Right-click the Archer Instance database, and then click Properties, which opens the Database Properties dialog box.
  4. In the Select a page pane, click Options.
  5. To change the recovery model select a different model list and select Simple.
  6. Click OK.
For full details on Database Best Practices for RSA Archer, this can be found in RSA Archer Sizing and Performance Guide - https://community.rsa.com/docs/DOC-29240
Alternatively - Implement regular processes to manage the transaction log properly if the Recovery Model for the GRC Platform Instance database is not set to Simple.