EV8 SP5: Monitor was not run because it requires the Enterprise Vault Storage service to be running.

[Matthew_Kimler]

I have this error now in EV8 SP5 with the new status item in the admin console.

Monitor was not run because it requires the Enterprise Vault Storage service to be running.

Check that the Storage Service is running.

It's definitely running on all servers and even rebooting or restarting the services keeps it at warning levels. Is there a way to clean this up or fix this?

[JesusWept3 · Accepted solution]

dtrace the source of the event, so for instance if you have a warning saying "Archive Task" then dtrace archive task, in this instance it may be the monitoring middle tier?

Anywho, usually when you see weird things like that its because the DNS isn't resolvable, and that in my experience is because the Site Alias isn't resolvable.

If you find any kind of EV ID, whether its an archiveID, FolderID, Storage Service ID etc you will see the following type of format

14EC93DB75559B2458ECDC585AF3C72FD1610000myEVSite

The Alias here is "myEVSite" and in an install myEVSite should resolve to an EV server, doesn't matter which but its usually for the main installed server, or the first install or what not.

So what i would do is this

1. Open outlook and go to Help -> About Enterprise Vault -> Tech Info (button)

2. Scroll down to the "Testing Connection" section

3. Make a note of the Default Filter id, look at the Site Alias at the end

4. Now go to the EV Server reporting the error

5. Open a command prompt and just try a simple "ping <siteAlias>"

6. If it doesn't resolve, try adding to the hosts file as a quick test
If it then works, you will need to ask your DNS team to sort it out

7. If it does resolve, in a command prompt type
sc \\<siteAlias> query

This should then list out the services, if this comes back with an error then you need to make sure that the user you're running this under has proper permissions to check service status and what not.

It could also be that the site alias is resolvable but to the wrong address

Failing all of that, run the dtrace, repro the problem and find the name or ip address that monitoring is trying to connect to in order to determine whether its running