000034425 - In RSA Archer, navigating to the Manage Data Feeds page fails to load. The tblAsyncinstrumentation and tblWFInstanceState database tables are extremely large too.

Document created by RSA Customer Support Employee on Dec 8, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000034425
Applies ToRSA Product Set: Archer
RSA Version/Condition:
IssueThe Manage Data Feeds page fails to load.
Additionally, the tblAsyncInstrumentation and tblWFInstanceState tables are extremely large and growing in size.
CauseThe username and password fields on the Transport tab of the Data Feed, in newer versions of Archer, is encrypted by the Archer environment that the Data Feed is saved in.
In a situation where the Archer instance is not able to decrypt the username/password, this results in an invalid username/password that is extremely large (several hundred megabytes) long.
When the Data Feed is scheduled to run, it's configuration is copied into tblAsyncInstrumentation and in this situation, results in jobs that will fail due to the bad configuration and are also extremely large in due to the invalid data in the username and password fields.
As the Data Feed job gets processed and then fails,  it will pass through tblWFInstanceState and this table will also grow significantly in size due to also containing a copy of the Data Feed's invalid configuration.

  1. Edit the Data Feed and correct the username and password on the Transport tab.

  2. For all Data Feeds where option 1 is not possible due to not having the credentials, set the Data Feeds to Inactive so that the Data Feeds do not try to run on a schedule with an invalid configuration.

  3. If you are unable to complete options 1 or 2 above due to a web server timeout caused by the invalid Data Feed configuration being extremely large, then delete the Data Feed from the "Manage Data Feeds" page and import the Data Feed from another instance.

  4. If the "Manage Data Feeds" page fails to load due to a very large number of Data Feeds that are impacted by this issue, then you will need to increase the web server execution timeout (see KB# 000029143).