Enterprise Vault (EV) services fail to start with the error: "The Enterprise Vault Archiving Service for EXCH1 service on Local Computer started and then stopped."
Problem
Enterprise Vault (EV) services fail to start with the error: "The Enterprise Vault Archiving Service for EXCH1 service on Local Computer started and then stopped".
Error Message
Event Type: Error
Event Source: Enterprise Vault
Event Category: Admin Service
Event ID: 4141
Date: 4/1/2010
Time: 2:50:46 AM
Computer: EVSERVER1
Description:
Insufficient diskspace is available on drive C: 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-4141
v-437-4145
v-437-4143
Cause
Enterprise Vault services can stop due to many reasons. The Windows Event logs should be reviewed as a first step to troubleshoot such issues. In this particular case, the services were stopped due to insufficient disk space on a local drive which was revealed in the Windows Event log entry.
Note: Enterprise Vault will shut down when 95% of Virtual Memory is used or if a local drive is 99% full.
Solution
The following methods can be used to resolve or alleviate the problem:
- Free up the space on local drive(s) and reboot the server. Verify the services are able to start and verify the Windows Event Viewer log is no longer reporting Event 4141.
- The start up parameters of the Enterprise Vault Admin Service can be modified to specify which local disks to monitor and which to exclude. For details on this, see the Administrators Guide Chapter: Day-to-day administration
Section: About monitoring disks
- The NoMonitor registry key can be set up to disable/enable monitoring of memory and all local disk space resources.
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\KVS\EnterpriseVault\AdminService
Content: DWORD: NoMonitor
0 - Monitor resources
1 - Do not monitor resources
Description: The Admin Service automatically monitors memory and disk space resources, logging warnings in the Application Log if necessary and, in extreme cases, shutting down Enterprise Vault services. You can use NoMonitor to force the Admin Service not to monitor resources. You can also control the monitoring by editing the Admin Service's startup parameters.