-
Title
"IFormContext with key "FormContext_1" not found in SessionCache" error encountered when using Active Roles Web Interface to perform various tasks -
Description
When performing tasks in the Active Roles Web Interface, sometimes an error is displayed.
An error occurred during the last operation.
Error: IFormContext with key "FormContext_1" not found in SessionCache. -
Cause
Cause 1
In IIS, you can allow an application pool to use many worker processes to allow for better performance. In this case, setting the maximum worker processes number higher than 1 will cause this error to occur.
Cause 2
The application pool is recycled after reaching its maximum memory usage.
Cause 3
The application pool is crashing due to an updated garbage collection. Please see the following Microsoft KB article for more information on the changes:
ExecutionEngineException occurs during Garbage CollectionTo confirm this to be the issue, you can see the following information in the Windows Event Log with .NET for the source:
Application: W3WP.exe Framework Version: v4.0.30319
Description: The process was terminated due to an internal error in the .NET Runtime at IP ###############with exit code 80131506.Cause 4
McAfee Antivirus software is installed on the Web Interface host machine.
Cause 5
Resource constraints on the SQL server hosting the ActiveRoles Server database are causing resource deadlocks.
Cause 6
Log Name: Application
Source: ASP.NET 4.0.30319.0
Date: 3/11/2015 10:57:28 AM
Event ID: 1309
Task Category: Web Event
Level: Warning
Keywords: Classic
User: N/A
Computer: hostname
Description:
Event code: 3012
Event message: An error occurred processing a web or script resource request. The resource identifier failed to decrypt. -
Resolution
Workaround 1
Reset the worker processes count to 1 and recycle the application pool.
- In the Internet Information Services (IIS) Manager, expand the server name and select Application Pools.
- In the right pane, right-click the ARServerAppPool application pool and select Advanced Settings.
- Under Process Model, set the value for Maximum Worker Processes to 1 and click Ok.
- Right-click the ARServerAppPool application pool and select Recycle.
Workaround 2
The default private memory limit is 1GB. Any medium to large size organizations commonly hit 1 GB, some very frequently.This private memory limit can be removed by setting the private member limit to 0 as per this resource.Starting with a clean install of the Active Roles Web Interface in Active Roles 7.4.3, this default has been changed is now 0 (no limit). This change is being tracked as Defect ID 141532.Workaround 3
Please see the steps in the following MSDN article to disable concurrent garbage collection:
https://msdn.microsoft.com/en-us/Library/at1stbec(v=vs.100).aspx
Workaround 4
Disable File Checking in IIS, which is known to cause false positives with some antivirus software.
Run the following commands from an elevated command prompt (Run as Administrator).reg add HKLM\SOFTWARE\Microsoft\ASP.NET /v FCNMode /t REG_DWORD /d 1 /fiisresetWorkaround 5
Confirm the issue by checking the Application Event Viewer logs on the machine hosting the Web Interface. If resource deadlocks are being encountered, you may see the following:
Event ID: 2262
C:\Windows\Microsoft.NET\Framework64\v2.0.50727\aspnet_isapi.dll reported itself as unhealthy for the following reason: 'Deadlock detected'.
Address this issue from the SQL side by either increasing available resources on the SQL host, moving the database to a dedicated SQL instance, or other actions as determined by your SQL administrator. Alternatively, you can decrease the load being placed on the SQL server by decreasing the duration of change history which is being tracked by Active Roles Server. Please reference the following resource for instructions:
Workaround 6
Configure an explicit Validation Key as per the following Microsoft KB article:
https://support.microsoft.com/en-us/kb/829743 -
Change Request
TF00141532 -
Attachments
-
Additional Information
With Cause 4, if the Web Interface logging is enabled as per https://support.quest.com/kb/24508 the above error message will occur in the logs approximately every 20 minutes.
