Highlighted

Enterprise Vault Cache Unable to reset

Has anybody seen this error before?

Capture.JPG
1 Solution

Accepted Solutions
Highlighted
Accepted Solution!

It doesn't matter whether you

It doesn't matter whether you believe the server is short on memory or not, as each process can only take up a certain amount of memory, for instance you will never see any EV process go over 200mb of memory as that is how much is allocated to each.

Offline Vault in Enterprise Vault 2007 and below was a purely client side application, bringing items in to the cache via download.asp
however Vault Cache is half server side and half client side, so when you do a reset of your Vault Cache, not only will it remove the files from your ev client, but it will then start making requests through the ASPX files on the server which will start preparing the MDC and DB files which get downloaded to the client via BITS


So is restarting the services drastic? not really for the fact that it will only incur 20 seconds at most (in most environments) downtime and will clear mapi profiles and any other memory being consumed by storage and index processes.

Again, the error is memory related, either on the client, but is most likely being reported by the EV server than anything else
https://www.linkedin.com/in/alex-allen-turl-07370146

View solution in original post

5 Replies
Highlighted

Did you get any errors on the

Did you get any errors on the EV server at all?
Not Enough Storage is available typically refers to memory (as opposed to disk space as most people are lead to believe)
though usually that error is also server side, have a look at the memory consumption and try restarting the EV Services and see if that helps
https://www.linkedin.com/in/alex-allen-turl-07370146
Highlighted

Nope.  No errors.  The EV

Nope.  No errors.  The EV servers are not running short on memory.  Restarting the services seems a bit extreme.  Before doing that, any other suggestions?
Highlighted

indicates problem is on client!

Vault Cache is on client. perhaps client tracing reveals something?

Check scanost / scanpst, to see of files perhaps corrupt.

http://office-outlook.com/outlook-forum/index.php/m/191499/#msg_191499

has some hints.

More rigid solutions
create new outlook profile
create new network profile (see link)

Good luck

Regards. Gertjan
Highlighted
Accepted Solution!

It doesn't matter whether you

It doesn't matter whether you believe the server is short on memory or not, as each process can only take up a certain amount of memory, for instance you will never see any EV process go over 200mb of memory as that is how much is allocated to each.

Offline Vault in Enterprise Vault 2007 and below was a purely client side application, bringing items in to the cache via download.asp
however Vault Cache is half server side and half client side, so when you do a reset of your Vault Cache, not only will it remove the files from your ev client, but it will then start making requests through the ASPX files on the server which will start preparing the MDC and DB files which get downloaded to the client via BITS


So is restarting the services drastic? not really for the fact that it will only incur 20 seconds at most (in most environments) downtime and will clear mapi profiles and any other memory being consumed by storage and index processes.

Again, the error is memory related, either on the client, but is most likely being reported by the EV server than anything else
https://www.linkedin.com/in/alex-allen-turl-07370146

View solution in original post

Highlighted

I would be interested to see

I would be interested to see a full client log when this happens.
 
If you want, you can do this in Outlook by using Ctrl + Shift + Any EV toolbar button, set log level to Max tracing, OK out and restart Outlook. Try to reset Vault Cache, then use the Open Log button to get at the latest log and attach it to the original message in this thread. Remember to set log level back to its previous level.
 
As long as you do not have any un-synchronised items (to be archived) in the VC that have been dragged in via Virtual Vault, you may be able to resolve the issue by deleting the MDC file. Don’t delete the MDC if you do have un-synchronised items as they are contained in the MDC.
 
To find the MDC look in the log file for a line like:
    [Offline Config] Working Directory: C:\Users\<myuser>\AppData\Local\KVS\Enterprise Vault\2E1F96DF6F49BC4A3BAA62CDF0DA7402\
 
The usename and hex number at the end will be different.
Exit outlook, go to that directory and delete the file with the .mdc extension. Restart Outlook and try the VC reset again.