Error Message

The following event is logged after the service startup:

Log Name:      Veritas Enterprise Vault
Source:        Enterprise Vault 
Event ID:      8600
Task Category: Directory Service
Level:         Error
The connection to SQL Server could not be established. 
The connection will be tried repeatedly until the Directory Service is stopped. 
SQL Server : SQLServer

V-437-8600

A Dtrace of the Directory Service will show the following: 

EV:H    {CADOContext::CreateConnection:#682} Failed to create COM object hr: The specified module could not be found.  (0x8007007e)
EV:H    {CADOContext::CreateConnection:#693} Free the COM object. hr: 0x8007007e hr: The specified module could not be found.  (0x8007007e)
EV:L    CADOContext::CreateConnection exit. source:Provider=MSOLEDBSQL;Server=SQLServer;Database=MASTER;Integrated Security=SSPI;DataTypeCompatibility=80; hr=The specified module could not be found.  (0x8007007e)
EV:H    CDirectoryServiceObject::CheckDirectoryEntry - Directory database existence check has failed. The connection to SQL Server could not be established.   The connection will be tried repeatedly until the Directory Service is stopped.   SQL Server : %1      (0xc0042198)
EV~E    Event ID: 8600 The connection to SQL Server could not be established. |The connection will be tried repeatedly until the Directory Service is stopped. |SQL Server : SQLServer |

Error when executing the new-object -comobject adodb.connection PowerShell command:

Retrieving the COM class factory for component with CLSID {00000514-0000-0010-8000-00AA006D2EA4} failed due to the following error: 8007007e The specified module could not be found. (Exception from HRESULT: 0x8007007E).

Enterprise Vault Directory service cannot properly establish a COM.ADODB.Connection; this has been noticed when there are corrupted or missing files in the Windows system directories C:\Program Files\Common Files\System\ado or C:\Program Files (x86)\Common Files\System\ado.

Executing the PS command new-object -comobject adodb.connection using x86 Windows Powershell or Enterprise Vault Shell would mimic the same failure.

The root cause of this issue is not related to any Enterprise Vault components. The following Microsoft utility helps in repairing missing or corrupted files from the aforementioned Windows system folders.

1. Stop all the Enterprise Vault services.

2. Open a command line with admin privileges and execute the command SFC.exe /verifyonly and wait until it completes.

3. Review the CBS.log created in C:\Windows\Logs\CBS\. For example, the following may be listed if the msado15.dll file is missing:

CSI    0000074d [SR] Repairing corrupted file [ml:520{260},l:100{50}]"\??\C:\Program Files (x86)\Common Files\System\ado"\[l:22{11}]"msado15.dll" from store

4. Execute the command SFC.exe /scannow to repair the corrupted or missing files and wait until it is completed.

5. Restart the Enterprise Vault server.

Please refer to Microsoft documentation https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/sfc for additional details.