Workstation repository caching not functioning

kiwirob · Post by **kiwirob** » Sun Aug 13, 2006 10:43 pm

Vault version 3.1.8.3771

I have been successfully using this version of vault for many months but recently had to rebuild my PC due to a disk failure. The source code for the repositories are on a disk that was not replaced so the existing in folder caches remain.

Since installing vault every time I connect to a repository on the vault server it downloads the full repository tree. The server is 19,000 km away in a different time zone and downloading 25MB everytime takes over 7 minutes and makes it virtually unuseable.

Even a simple connect, quit, connect downloads the entire tree once again.

The CacheMember_Repository file is being created as expected but just doesn't appear to be used on next connect. It is 59MB in size.

We have checked log files on both the client and server and they do not differ significantly from those of a collegue using the same client in the UK. He has also connected using my login n the UK and it is using the cache correctly so it is specific to my workstation not my vault user settings.

As I said I have previously had this version installed and working ok so its not a specific problem with the version, but something different about the installation.

I have tried reinstalling but no difference. I only have .NET 2.0 installed at this stage, do i need .NET 1.1 as well?

I think I have some log files available if required.

Any ideas?

lbauer · Post by **lbauer** » Mon Aug 14, 2006 7:47 am

When you connect, do you wait until the entire tree is downloaded, or quit the connection before then? If you close the connection before the entire cache/tree is downloaded, it won't save anything and will just start over the next time.

Could there be permissions or diskspace issues writing to the location of the cache files? You can change the location in the Vault GUI under Tools->Options->Local Files->Cache/Backup locations to see if that makes a difference.

kiwirob · Post by **kiwirob** » Mon Aug 14, 2006 2:57 pm

Hi Linda

I'm aware of the entire tree issue and always wait for the first tree download before reconnecting. Its a slow process testing, changing settings, downloading twice etc.

No issues with disk space ~200GB free, and i'm an administrator.

It doesn't matter which vault user I connect as from my workstation the same thing happens.

I have attached both a client log and server log, unfortunately they aren't for the same login but they both exhibit the same problem.

lbauer · Post by **lbauer** » Mon Aug 14, 2006 3:45 pm

I looked into this further and it is a known issue when you have a Vault Client using the .NET Framework 2.0 and the Vault server is in a different timezone. Microsoft changed the way time values are sent with the .NET 2.0 Framework. Because of this, the cache doesn't get updated properly.

This was fixed in Vault 3.5.

The solution for earlier versions is to make sure Vault client and server are using the same .NET version

kiwirob · Post by **kiwirob** » Mon Aug 14, 2006 4:38 pm

Thanks Linda.

Installed 1.1 and its now working fine, should have tried it earlier

.