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.
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.
The application pool is recycling after reaching it's maximum memory usage.
The application pool is crashing due to an update garbage collection. Please see the following Microsoft KB article for more information on the changes:
ExecutionEngineException occurs during Garbage Collection
To 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.
McAfee Antivirus software is installed on the Web Interface host machine.
Resource constraints on the SQL server hosting the ActiveRoles Server database are causing resource deadlocks.
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
Event code: 3012
Event message: An error occurred processing a web or script resource request. The resource identifier failed to decrypt.
Reset the worker processes count to 1 and recycle the application pool.
Please see the steps in the following MSDN article to disable concurrent garbage collection:
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).
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:
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 ActiveRoles Server. Please reference the following resource for instructions:
Configure an explicit validationKey as per the following Microsoft KB article: