Long running jobs fail for Data Import or Delete Content in Archer
Product Set: Archer Version/Condition: 5.x and 6.x
When importing or deleting large amount of content, a SQL request may take longer than expected and timeout causing jobs to fail or get stuck.
After attempting to delete Application Content using the Delete Content button, the process never completes and appears hung. To reset button, see KB 000029797. The Status displays a message and no longer updates: Processing.. Step X of Y. Image description
The Archer Services Account times out before the Data Import or Delete Content is completed. When a job makes a SQL call, it includes the session token. If the request takes longer than the default 30 minutes, a new session token may get created. When the original SQL call is completed and tries to update the job status, the session token no longer matches and the job fails with invalid session token.
Although the Security Parameter setting for Session Timeout for the Archer Services Parameter can be modified via the Web UI, the Save and Apply buttons are disabled.
The only way to change the Session Timeout option is via SQL.
Perform a SQL Backup of the Instance database in case a restore is required.
Increase the Archer Services Parameter Session Timeout from 30 minutes (default) to something large such as 6 hours by running the following SQL command against the Instance database.
UPDATE tblSecurityParameters SET sec_prm_timeout=6, timeout_time_interval_id=1 WHERE sec_prm_name='Archer Services Parameter'