"Cannot expand the folder. The set of folders cannot be opened" happening on machine rebuild
Hello
We're rebuilding quite a lot of machines at the moment.
The mahcine are being rebuilt with the same name, the same OS version (Windows 7) and the same version of Outlook (Outlook 2010)
In almost all cases that I've seen so far, when the users login and launch outlook, they see a their virtual vault, but when they click on it, they get a message like the one below:
"Cannot expand the folder. The set of folders cannot be opened. The file C:\users\username\AppData\Local\KVS\Enterprise Vault\<number>\<numer>p-in-arc-01.mdc cannot be found"
NOTE: when checked, .mdc file is present in the location listed.
In some cases it just "started working" later on.
In some cases it never starts working again.
We have tried doing a manual "Reset" and this seems to provide a "workaround".
Questions:
- What is the expected behaviour if a machine is rebuilt with the same name?
IMHO it should "just work" i.e. there should be no need to manual intervension / workarounds being applied.
- How can we "fix" this? (it's not really a feasable option to have to select "reset" for each individual users after logon !!!)
- We're rebuilding quite a lot more machines and need a "resolution" rather than the workarounds currently being used.
We're using the latest vault client (released in February this year)
Thanks
-AL
Well if the machines are being rebuilt, then the Vault Cache shouldn't exist and the Vault Client should be rebuilding the Vault Cache itself. Are you perhaps exporting and then re-importing the registry keys and what not from the previous machine?
The machine name isn't really what controls the Vault Cache, its the user that logs on and the Store ID in the users mailbox (Explained in the last post the Store ID is gathered from the PR_STORE_RECORD_KEY in the users mailbox)
If you are rebuilding a machine, would just suggest not trying to re-inforce the Vault Cache by copying the items or the registry hives across from the old machine and just let Enterprise Vault start building the vault cache from scratch