Important Update: Archer Community Scheduled Maintenance on November 23–24 - New Community Launching Soon! Learn More..
000039774
After upgrading to Archer 6.9 or newer (Including SP1 and SP2) from previous versions, performance of the web tier is degraded. Also, review of SQL Traces taken via KB 000035802 - How to Run a SQL Server Profiler Trace to Troubleshoot Archer Performance Issues shows no long running stored procedures in the SQL Database. Archer application logs will show no errors as well.
This issue is most noticeable when saving records or switching tabs in a record, as response times are significantly degraded from previous versions where you may notice a very large increase in your Waiting (TTFB) when comparing performance via a Network trace in the web browser.
This issue is caused by some new settings missing in the web.config file. Starting newer versions of Archer, some additional settings have been added.
If the settings do not exist in your web.config file, perhaps something failed when the installer tried to update it or an old file was copied in place after the upgrade.
In order to confirm you are experiencing this issue look for the section below in your Archer web.config file:
<cachingConfiguration> <namedCaches> <add name="ConfigurationCache" pollingInterval="00:01:00" physicalMemoryLimitPercentage="0" cacheMemoryLimitMegabytes="0" /> </namedCaches> </cachingConfiguration>
If you are on Archer 6.9 or newer, this section has been/should be removed and replaced with the below:
Make sure to take a backup of the web.config file before proceeding or applying any changes to it.
<system.runtime.caching> <memoryCache> <namedCaches> <add name="ConfigurationCache" pollingInterval="00:01:00" physicalMemoryLimitPercentage="0" cacheMemoryLimitMegabytes="0" /> </namedCaches> </memoryCache> </system.runtime.caching>
Once the web.config file modifications are complete, save the changes and perform an IIS reset.
Note: This change must be applied to all Web servers.
Alternatively, you can run the Archer installer with the correct permissions on the account running the install (run as a different user if needed; and ensure Full Control over the file/folder for that account).