Search status does not update in a timely manner in the Enterprise Vault (EV) Compliance Accelerator (CA) or Discovery Accelerator (DA) client.
Article ID: 100000649
Updated On:
Cause
Enterprise Vault (EV) Compliance Accelerator (CA) and Discovery Accelerator (DA) 8.x and greater use a CA or DA Client on a user's workstation to access searches, items for review and export and all other content within the selected Customer. When a search is running, it's status can be monitored in the Searches tab of the Case in which the search is running. In some instances, the search status does not update in a timely manner. The index volumes section below the search status pane can show all index volumes as having finished, but the search status remains as not started or in progress.
The refresh of the search status is provided through updates to the CA or DA Customer database using a SQL view or stored procedure. The SQL updates are provided in a timely manner. The update of the status information in the DA Client is provided through the Internet Information Service (IIS) using Active Server Page (ASP) calls between the DA and SQL servers. These ASP calls cache information so provide faster updates for information that has not changed. When this issue occurs, the ASP cache is not updated properly, thereby showing the incorrect status. The cache will update eventually, but can take several hours.
Workaround:
A simple workaround exists to force a refresh of the ASP cache is to
The refresh of the search status is provided through updates to the CA or DA Customer database using a SQL view or stored procedure. The SQL updates are provided in a timely manner. The update of the status information in the DA Client is provided through the Internet Information Service (IIS) using Active Server Page (ASP) calls between the DA and SQL servers. These ASP calls cache information so provide faster updates for information that has not changed. When this issue occurs, the ASP cache is not updated properly, thereby showing the incorrect status. The cache will update eventually, but can take several hours.
Workaround:
A simple workaround exists to force a refresh of the ASP cache is to
- Hold the Ctrl key
- Left click on the Symantec or Veritas logo in the bottom right corner of the CA or DA Client
- Release the Ctrl key.
Resolution
The first solution to apply is to simply restart the IIS services on the DA server. Do do this,
- Open a Command Prompt on the DA server while logged on with a local administrative account such as the Vault Service Account (VSA)
- Enter and execute
iisreset - Monitor the reset execution to completion, then close the Command Prompt window
- Restart the Enterprise Vault Accelerator Manager Service (EVAMS)
- Close and relaunch the DA Client
If the delay returns after restarting IIS, a registry entry may need to be added to the CA or DA server. This registry entry is DisableLazyContentPropagation. The IIS Help contains information about this registry setting in the Global Registry Entries section.
Warning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. It is recommended that a complete backup of the registry be made prior to making any registry changes.
Note: This option has the potential to slow IIS processing as every page update must write a new page to be displayed / accessed. This option should be tested to ensure its effects are understood.
A) On the DA server, open a registry editor (regedit.exe) while logged on with an account that has local administrator privileges.
B) Browse to the following location:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ASP. C) Right click on the ASP key, select the New, then the Key options.
D) Enter Parameters for the key name.
E) Right click on the new Parameters key and select the New, then DWORD value options.
F Enter DisableLazyContentPropagation as the name of the new DWORD (you may have to rename the value).
G) Right click on the new DisableLazyContentPropagation value, then click Modify.
H) Enter 1 into the Value Data field to disable the behavior.
I) Select Decimal for the Base options.
J) Click OK to save the change.
When completed, the registry entry should look similar to the following:
HKEY_LOCAL_MACHINE
SYSTEM
CurrentControlSet
Services
ASP
Parameters
DisableLazyContentPropagation REG_DWORD 0x00000001 (1)
K) Close the registry editor.
L) Reset IIS, restart EVAMS and relaunch the DA Client as in Steps 1 - 5 above.
To change the behavior back to the default, change the value to 0, then restart per Step L.
L) Reset IIS, restart EVAMS and relaunch the DA Client as in Steps 1 - 5 above.
To change the behavior back to the default, change the value to 0, then restart per Step L.
Issue/Introduction
Search status does not update in a timely manner in the Enterprise Vault (EV) Compliance Accelerator (CA) or Discovery Accelerator (DA) client.
Was this article helpful?
Yes
No
Powered by
