000033720 - Performing a Lookup in RSA Archer 5.x from Cross-Reference field causes a Log Reference ID and the w3wp log file shows: Request timed out

Document created by RSA Customer Support Employee on Aug 10, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 3Show Document
  • View in full screen mode

Article Content

Article Number000033720
Applies ToRSA Product Set: Archer
RSA Version/Condition: 5.x
IssueRequest timed out logged in w3wp log after the User Interface pops up a Log Reference ID. 
Performing a Lookup from a Cross-Reference field that searches through hundreds of thousands of records and takes longer then the default 3 min execution timeout as configured in the web.config. 
A sample w3wp error follows:
      <TraceRecord Severity="Error" xmlns="http://schemas.microsoft.com/2004/10/E2ETraceEvent/TraceRecord">
        <Description>Request timed out.</Description>
          <Module>ModuleId: 471, ModuleName: XXXXXXXXXX, ModuleStatus: ActiveInProduction, ModuleType: Application</Module>
          <ExceptionType>System.Web.HttpException, System.Web, Version=, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a</ExceptionType>
          <Message>Request timed out.</Message>
          <Source />
          <StackTrace />

  1. Log into the web server for this environment.
  2. Open IIS Manager.
  3. Select the Archer site. 
  4. Open the Configuration Editor at the bottom. 
Image 1

  1. In the Section drop down list, select system.web/httpRuntime
Image 2

  1. For executionTimeout, change the value from 00:03:00 (3 minutes) to 00:20:00 (20 minutes).
Image 3

  1. Click Apply to commit the change.
User-added image

  1. Open a command prompt (cmd.exe) by right-clicking and selecting the "Run as Administrator" option.
  2. Issue the command: IISRESET.