EV Admin Service does not start after failing over on a Microsoft Cluster

book

Article ID: 100014066

calendar_today

Updated On:

Description

Error Message

Event ID: 4143 Insufficient Diskspace is available on drives [All Mapped Drives] for the Enterprise Vault to run.

Enterprise Vault will now be shut down; to correct this problem, delete any unwanted files and restart Enterprise Vault
V-437-4143

The following is shown in a Dtrace of the AdminService process: 

CPerfMonitor::Is Valid: [YES]|
CWMIPerfQuery::GetCounter(B) (Entry)|
CWMIPerfQuery::GetFormattedValue - (Entry)|
CWMIPerfQuery::GetFormattedValue - [Win32_PerfFormattedData_PerfDisk_LogicalDisk] Value [0.000000]|
CPerfMonitor::CheckCounters I: value[5] 0|
CPerfMonitor::CheckCounters critical level (99) breached|

 

Cause

This can occur when the EV Admin Service resource starts up before the storage resource(s) have initialized.

 

Resolution

The EV Admin Service resource should be configured to list all storage resources as dependencies. This will ensure that the storage resources are initialized prior to the Admin Service's checking them for free disk space.

The Enterprise Vault Configuration wizard sets up the proper dependencies for the Enterprise Vault components. However, any storage resources subsequently added must be configured with the proper dependencies. It is these subsequently added storage resources that are most likely to cause the issue described above if they are not configured properly.

Issue/Introduction

During a failover of an active passive Microsoft Cluster, the Enterprise Vault (EV) Admin Service will not start, citing insufficient disk space. The disks are the same as on the Active node and have plenty of space. The drive letters that are cited as lacking sufficient space are not consistent across multiple failovers.