We are having a problem with vault related to where/how vault is storing its cache. We have roaming profiles in use on our network, and on some machines, some user's profiles end up in different folders than on other machines ("C:\Documents and Settings\JimB" vs "C:\Documents and Settings\JimB.Domain.000" and so on). Since Vault currently seems to be storing the location of it's cache files in the users registry using an absolute path (ex. C:\Documents and Settings\JimB\Application Data\.......) as opposed to using an environment variable and expanding them (ex. %APPDATA%\......) Vault ends up having problems on the machines where the path on disk to the users profile is different. It errors out saying "access denied" (false error message) trying to access a folder that doesn't exist on disk on this machine. Is there a way to have Vault use environment variable expansion in its registry setting for file/cache locations?
Also, I have to say that I think storing these VERY large caches in the AppData folder intead of the LocalSettings folder is a bad idea. As the cache bloats up to hundreds of megs, the roaming profiles become slower and slower to load. However even with it moved to LocalSettings, I would still have the problem that it has a static string in the registry directing it to a cache folder that doesn't exist.
Roaming User Profiles and Vault Cache location
Moderator: SourceGear
I did notice that for some of our more recent users, that only have ever used recent versions of vault, that their cache does point to Local Settings instead of AppData. But some of our users that have been around a while had to go into the options of vault, to reset the cache location so it goes to Local Settings.
But I still do have the problem that on roaming profiles the profile folder may be different on other machines, and Vault errors out when the Cache folder doesn't exist at the path stored in the registry. Again, I would like to see it use an environment variable expansion to use %USERPROFILE% to find the logged on user's profile.
But I still do have the problem that on roaming profiles the profile folder may be different on other machines, and Vault errors out when the Cache folder doesn't exist at the path stored in the registry. Again, I would like to see it use an environment variable expansion to use %USERPROFILE% to find the logged on user's profile.
You didn't specify which version of Vault you are using, but you can change the location in Tools -> Options -> Local Files -> Cache/Backup Locations. You should choose a non-roaming place for this to exist. As you've discovered, the cache folder is not something you want to store within your roaming profile.
In regards to environment variables within the location, I can log a feature request to do just that.
In regards to environment variables within the location, I can log a feature request to do just that.
Jeff Clausius
SourceGear
SourceGear