SourceGear Support

Hi Jeff,

I turned on "Require Check Out before Check In" and performance and response times have improved dramatically. We do not have deep folder structures and only a few of them have more than 30 or 40 files in them (the average is closer to 5 or 6 per folder).

Jon

Sounds good. Logging into Vault on my PC as another user with differnet working folders fixes the problem, but obviously I would prefer to use my original ID and working folders... Any thoughts on a possible work around? Are there local files or settings I can remove or modify? Anything in the Vault...

It takes at least 40 seconds for a "Get Latest Version" dialog box to pop up. This is quite frustrating...

Hi Jeff, I'm running 3.5.0 Win client and am experiencing the same problem. Concurrent development style and using modification times instead of CRCs to detect differences. I have been up and running on this version for a year or so now and noticed about a few months ago that it was getting very slo...

With the help of the support call center, I found it. Simply removing the "C:\Documents and Settings\<user>\Local Settings\Application Data\SourceGear\Vault_1" directory cleared everything up.

Jon

Hi, We're having an issue with one of our Vault Client installations... It seems that when a particular developer logs into a particular machine, the client won't report the correct Remote Version number. For example, if the remote version is now 10, the client reports 3. Showing the history for tha...

Yes, again because I handled all of the file-owner mess that applies to UNIX/Linux file systems but not Microsoft's.

Jon

Yes, although I changed the existing shadow files' owners to the appropriate ID after the 10:39 test. Here's the rest of the log file.

Jon

[quote="jclausius"][quote="JonEdwards"]The log from previous failed attempts seems to indicate that at some point the shadow encountered the error above and simply stopped? [/quote]What were the log entries for that period of time?[/quote] Here's everything that was logged by the...

Update: The shadow folder is a location on a LINUX machine shared through SAMBA. I went through LINUX and changed the owner of all files in that folder tree to be the user account that the Shadow Service uses. Not sure how another user became the owner of a few of the files, but at some point owners...

We're using 3.1.5 (3546). I tried a sample check-in and this error showed up in the log: 4/17/2006 10:39:36 AM <generic>: [<No Name>:6124] Vault's Shadow Folders encountered an exception attempting to get the files for Lanier. The Shadow Folders for the repository may not be syncrhonized with the Va...

We're using Vault's shadow ability to save off a large part of our source code into a shared folder on the network. At some point this featured stopped working and we're not sure why (or when, for that matter). I've checked the system event log on the machine that hosts the Vault server (and the sha...

Hi Dan, So, our only option (short of trying to get everyone to remember to always hit the toggle box) seems to be to create two Vault users per developer. One user has access to the project folders that should be automatically removed on check-in and has his/her check-in properties set appropriatel...

Ouch. I guess VSS does this too?

This is a stretch, but is this user setting stored in an ini or config file (vs the DB)?

Jon

Hi all, Is it possible to set the Vault client to remove local copies on check-in for one repository but not another? Or even better, can this be set by folder within a single repository? I ask because we develop in two different technologies, one lends itself to keeping only WIP code local and all ...