Long Running Data Import or Content Deletion Jobs Result in Failure in Archer

[KB-Sync1]

Article Number

000029541

Applies To

Product(s): Archer
Version(s): All Versions
Primary Deployment: On Premises/AWS Hosted/AWS SaaS

---

Description

While attempting to import or delete large amount of content, the SQL request may take longer than expected and timeouts can occur causing jobs to fail or discontinue processing.  

For instance, after deleting an application's content using the Delete Application Content button, the process never completes and appears to be hung.
Note: To reset this button, refer to Archer Delete Content Button Status Displays 'Processing ... Step X of Y' and No Longer Deletes.
0EMVM000005rs7S.png

Cause

The Archer Services Account in the Security Parameters page 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 Archer UI, the Save and Save and Close buttons are disabled.
0EMVM000005ry9d.png

Resolution

The only way to change the Session Timeout option is via SQL.

1. Perform a SQL Backup of the Instance database in case a restore is required.
2. 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'

Possible timeout_time_interval values:

1 = Hours
2 = Minutes
3 = Days