Stale data in the ASP.NET Cache on the CA or DA Server or in the CA or DA Client cache on the local workstation or Citrix server can cause a failure to quickly update the cache used to store certain information, which can allow Principal ID values from previous users to be sent to the search creation and update processes, thereby reflecting the wrong user as the search submitter or modifier.

To workaround this issue, implement any of the following workarounds individually or in any combination.

Workaround 1: Manually refresh the CA or DA Client cache

Refer to Technical Article 100025601, "Client Graphic User Interface (GUI) is displaying abnormal content", in the Related Articles section below for instructions to refresh the DA Client cache.

Workaround 2: Create the DisableLazyContentPropagation registry value to force the ASP.NET cache to update with every request

Refer to Technical Article 100000649, "Search status does not update in a timely manner yin the Enterprise Vault (EV) Compliance Accelerator (CA) or Discovery Accelerator (DA) client", in the Related Articles section below.

Workaround 3: Disable the Permissions Cache 

Note: This option may cause a slower than normal response when performing any activity in the CA or DA Client.

1. Open the CA or DA Client with an account that has sufficient Application level permissions to change settings, such as the Vault Service Account.
2. Click on the Configuration tab.
3. Click on the Settings sub-tab.
4. Hold the Ctrl key and click on the banner where it has Configuration Settings to show the hidden configuration settings options.
5. Expand the Security folder.
6. Locate the hidden setting of 'Permission Cache Option'.
7. Change the value for this setting from the default of 2 (Cache used only if no permissions updates are outstanding) to 0 (Do not use the Cache).
8. Click anywhere else on the page to move off of that option and enable the Save button.
9. Click the Save button to save this change.
10. Click the OK button to acknowledge the pop-up dialog box indicating that a restart of Customer Background Tasks is required.
11. Close the CA or DA Client.
12. Log onto the CA or DA server as the Vault Service Account.
13. Open the Services management console.
14. Stop the Enterprise Vault Accelerator Manager Service (EVAMS), leaving the Services management console open.
15. Open a Command Prompt.
16. Reset IIS by running iisreset to clear the IIS and ASP.NET cache.
17. Start EVAMS in the services management console.
18. Close both the Services management console and the Command Prompt.
19. Launch the CA or DA Client and proceed with the expected work.

There are currently no plans to address this issue by way of a hotfix or cumulative hotfix in the current or previous versions of the software at the present time. This issue may be resolved in a future major revision of the software at a later time. However, this particular issue is not currently scheduled for any release.  If you feel this issue has a direct business impact for you and your continued use of the product, please contact your Veritas Sales representative or the Veritas Sales group to discuss these concerns.  For information on how to contact Veritas Sales, please see https://www.veritas.com