Error Message

1. The following entries are normal entries as seen after a restart of the EV server or a restart of the EV Services:

Log Name:      Veritas Enterprise Vault
Source:        Enterprise Vault
Event ID:      4110
Task Category: Admin Service
Level:         Information
Keywords:      Classic
Description:
The Admin Service has successfully completed its preliminary checks and has started  (...)

V-437-4110

Log Name:      Veritas Enterprise Vault
Source:        Enterprise Vault
Event ID:      41299
Task Category: Index Admin Service
Level:         Information
Keywords:      Classic
Description:
The Indexing Service is pending initialization.
Requesting additional time for initialization routines....

V-437-41299

Log Name:      Veritas Enterprise Vault
Source:        Enterprise Vault
Event ID:      41297
Task Category: Index Admin Service
Level:         Information
Keywords:      Classic
Description:
The Indexing Service has started (...).

V-437-41297

Log Name:      Veritas Enterprise Vault
Source:        Enterprise Vault
Event ID:      41302
Task Category: Index Admin Service
Level:         Information
Keywords:      Classic
Description:
The Indexing Service has completed its initialization. The service is now functioning fully.

V-437-41302

2. The following entries indicate the start of the issue and may be seen multiple times:

Log Name:      Veritas Enterprise Vault
Source:        Enterprise Vault
Event ID:      41303
Task Category: Index Admin Service
Level:         Information
Keywords:      Classic
Description:
The Indexing Service has been started, but must complete additional work before it can respond to external requests.

V-437-41303

Log Name:      Veritas Enterprise Vault
Source:        Enterprise Vault
Event ID:      13397
Task Category: Storage Server
Level:         Warning
Keywords:      Classic
Description:
The connection 'Provider=MSOLEDBSQL;Server=;Database=;Integrated Security=SSPI;DataTypeCompatibility=X;' was lost and the system is waiting to reconnect (Thread Id: X)

V-437-13397

Log Name:      Veritas Enterprise Vault
Source:        Enterprise Vault
Event ID:      13397
Task Category: Admin Service
Level:         Warning
Keywords:      Classic
Description:
The connection 'Provider=MSOLEDBSQL;Server=;Database=;Trusted_Connection=yes;DataTypeCompatibility=X;' was lost and the system is waiting to reconnect (Thread Id: X)

V-437-13397

Log Name:      Veritas Enterprise Vault
Source:        Enterprise Vault
Event ID:      41619
Task Category: Index Admin Service
Level:         Information
Keywords:      Classic
Description:
A transient error is preventing the execution of a SQL command. Enterprise Vault will try to run the command again.
Command: 'EVSqlConnection: DB: Data Source=;Initial Catalog=;Integrated Security=True;Connect Timeout=120'
Attempt: X of 40.
Last Error: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

V-437-41619

Log Name:      Veritas Enterprise Vault
Source:        Enterprise Vault
Event ID:      41320
Task Category: Index Admin Service
Level:         Error
Keywords:      Classic
Description:
A periodic Index Admin check could not determine the status of one or more Index Volumes that are managed by this server. (Error: Could not connect to [] at [])

V-437-41320

 

The issue is caused by the EV servers not connecting to the SQL server(s) housing the various databases used by EV. These databases commonly include the Vault Store databases and Vault Store Group databases (also known as the fingerprint databases), and can also include the Monitoring database and Auditing database as listed in the Event Logs. If the Enterprise Vault Admin Service and Enterprise Vault Directory Service start without any errors, it is unlikely that EV cannot connect to the EnterpriseVaultDirectory database.

The cause is usually attributed to moving the databases referenced in the Event Logs to different SQL servers where the SQL server change was not properly logged in EV or there are orphaned entries for the previous SQL servers in the EV servers' Registry.

 

See this article for more details on how to move the EV databases to a different SQL server.

To determine if the EV servers' Registry contains orphaned entries for the previous SQL servers:

1. Edit the following PowerShell script to replace with the SQL server name and/or instance and/or port as applicable. Then edit \

.txt

to a path on the EV server and a name of the text file that will contain the output (e.g.: C:\RegistrySQLInfo01.txt).

Get-ChildItem -Recurse -Force -Path 'HKLM:\SOFTWARE\Wow6432Node\' | Get-ItemProperty | Where {$_ -Match ''} >> \

.txt

If there are multiple SQL servers listed in the Event Logs, use and edit the following script. Note, the script is configured to search for 2 SQL servers - add/edit as many -OR $_ -Match ' entries as needed.

Get-ChildItem -Recurse -Force -Path 'HKLM:\SOFTWARE\Wow6432Node\' | Get-ItemProperty | Where {$_ -Match '' -OR $_ -Match ''} >> \

.txt

2. Run the script on each EV server using PowerShell or the PowerShell ISE.

3. Review the output file for any Registry locations that contain references to the previous SQL servers.

A simple workaround that should allow Accelerator Searches to work would be to edit the HOSTS file on each EV server to point the previous SQL servers to the IP addresses of the new SQL servers.

For a longer-term solution, any Registry entries on the EV servers that point to the previous SQL servers may need to be edited to the new SQL servers. Please consult with your Windows Administration team to make the changes.

**************************************************
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.
**************************************************

 

After submitting Enterprise Vault (EV) Compliance Accelerator (CA) or Discovery Accelerator (DA) Searches, the Searches do not progress. Looking at the Searches tab in the CA Department or DA Case, the Search does not show an entry for the Run Date. Looking at the Search Details for the Search, all Index Volumes are listed in either the '2000 not started archive indexes' dropdown or the '2000 queued archive indexes' dropdown. There may not be any relevant entries in the EV Event Logs on the Accelerator Server. However, a review of the EV Event Logs on the EV server(s) may show one or multiple entries for the events as listed below.