Syncronizing local copy with Vault server

If you are having a problem using Vault, post a message here.

Moderator: SourceGear

Post Reply
scaiferw
Posts: 83
Joined: Thu Mar 22, 2012 8:22 am

Syncronizing local copy with Vault server

Post by scaiferw » Mon Jul 29, 2013 9:17 am

When I click "Reset Repository Cache...", I'm warned "Resetting the repository cache should only be invoked when the local repository is not synchronized with the Vault server"

How can I tell if that is the case? I can't see any option to tell me whether the local repository is synched with the server.
Vault Standard Version 5.1.1.19215 -- Windows Server 2008 R2 -- SQL Server 2008 R2

Beth
Posts: 8550
Joined: Wed Jun 21, 2006 8:24 pm
Location: SourceGear
Contact:

Re: Syncronizing local copy with Vault server

Post by Beth » Mon Jul 29, 2013 9:48 am

If the cache is not sync'd you would have errors or some issues that point to the cache as the root cause.

Do you have any problems going on with Vault right now?
Beth Kieler
SourceGear Technical Support

scaiferw
Posts: 83
Joined: Thu Mar 22, 2012 8:22 am

Re: Syncronizing local copy with Vault server

Post by scaiferw » Mon Jul 29, 2013 12:17 pm

Yes, one of my users is getting "The remote server returned an error: (413) Request Entity" when trying to upload large files. I just started another thread about that.

I came across that option when trying to troubleshoot the issue.

From your response, it sounds like the synchronization should always be set? But in that case I wouldn't expect the option to be available. Under what circumstances would it not be synchronized? How can I check? I'd like to understand the process so I'd know how and whether to use that butting.

Rob
Vault Standard Version 5.1.1.19215 -- Windows Server 2008 R2 -- SQL Server 2008 R2

Beth
Posts: 8550
Joined: Wed Jun 21, 2006 8:24 pm
Location: SourceGear
Contact:

Re: Syncronizing local copy with Vault server

Post by Beth » Wed Jul 31, 2013 4:00 pm

Vault will try to keep the cache up to date on its own. There are cases where the cache is missing information, such as a network connection failing during an update. When that happens, Vault might not be able to update its cache fully, because it's not aware that something prevented the full update. It's cases like this where resetting the repository cache or sometimes even clearing the cache and allowing to to be rebuilt is useful.

Uploading large files and receiving errors usually isn't related to a cache issue.
Beth Kieler
SourceGear Technical Support

Post Reply