Skip to main content

RFC Extract Not Working in Data Source Registry

Mary Tanzy
  • Updated

Overview

When a user runs an RFC Extract job for an SAP Application Server source type on Common's Data Source Registry page's Vertical View, the job times out and the RFC Functions list does not populate as expected. The issue is best resolved by extending the timeout setting.

Issue

This issue results in an HTTP Request Timeout on a foreground event,  with one of the following outcomes on the Data Source Registry page:

  • The job fails without returning an error message.
  • A popup message displays: "Thread was being aborted."
  • The Application Event Log displays: "Request timed out."
  • The Debug Log displays: "Invalid operation. The connection is closed."

Resolution

To increase the HTTP Request timeout for the DSP application, update the executionTimeout code in the Web.Config file located in the %DSP Install Path%\BOA\DSP\Web folder on the DSP application server. 

WARNING:  Saving a change to the Web.Config file, or any file used by the IIS application (that runs DSP), may restart the IIS application.  DSP users will be logged out and any foreground jobs will be aborted. All background jobs will continue to run (like Collect extracts).

To update the executionTimeout code to resolve the issue:

  1. Navigate to the %DSP Install Path%\BOA\DSP\Web folder on the DSP application server.

NOTE:  The default value of %DSP Install Path% is C:\Program Files (x86).

2. In the Web.Config file, update this line:

<httpRuntime maxRequestLength="20000" targetFramework="4.6" />

To match this:

<httpRuntime maxRequestLength="20000" executionTimeout="1200" targetFramework="4.6" />

NOTE :  Your <httpRuntime /> line may not match the example if it has already been modified from its
default value.  In that case, take note of the original value and make a backup of it.

Adding the executionTimeout="1200​" piece extends the HTTP Request timeout from the default of 110 seconds to 20 minutes.

Related articles