000033339 - Singular Application slow performance and 'request timed out' log errors when attempting to edit/save a record and/or navigate between tabs in RSA Archer

Document created by RSA Customer Support Employee on Jan 11, 2017Last modified by RSA Customer Support on Apr 24, 2019
Version 3Show Document
  • View in full screen mode

Article Content

Article Number000033339
Applies ToRSA Product Set: Archer
RSA Version/Condition: 5.x, 6.x

The following snippet is from the w3wp log file:

<E2ETraceEvent xmlns="http://schemas.microsoft.com/2004/06/E2ETraceEvent">
        <TraceRecord Severity="Error" xmlns="http://schemas.microsoft.com/2004/10/E2ETraceEvent/TraceRecord">
        <Description>Request timed out.</Description>
          <Module>ModuleId: 195, ModuleName: XXXXX, ModuleStatus: ActiveInProduction, ModuleType: Application</Module>
          <ExceptionType>System.Web.HttpException, System.Web, Version=, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a</ExceptionType>
          <Message>Request timed out.</Message>
          <Source />
          <StackTrace />

Some display fields that are populated with a large amount of values are known to cause performance impacts, and even Timeout errors when attempting to edit, save, or navigate a record. For example, if there is a Record Permission field that is set to populate a Dropdown with a significant amount of users, this can cause slowness due to the number of users being loaded during the Edit process.
ResolutionBelow are some fields that are known to cause these issues, and their recommended changes:
  1. Record Permission Field
    • Change Display Control to Values Popup
  2. User/Group List Field
    • Change Display Control to Values Popup
  3. History Log Field
    • Change Display Control to Link