SourceGear Support

No errors found in the Vault server log (which makes sense as this is a client connection issue). The error itself can and does happen at virtually any time. However, it seems to happen more frequently if the build server is under load and/or currently making Vault client calls in concurrent build p...

Hello -- We are using the latest version of Vault (4.1.4) and our build process makes use of the Vault command-line client. Once or twice a day, however, we run into the following error when the build process attempts to pull files from Vault: "C:\Program Files\SourceGear\Vault Client\vault.exe...

While you-all are looking into this, you might want to take a close look at inclusionFilters as well. I was having a problem with that too but worked around it by updating my <folder> specification to start at the desired root. As a result, I do not specify any inclusionFilters . On behalf of Cruise...

For whatever it's worth, branches used to take us about 10 minutes. But after the upgrade to Vault 4.1.4, that same branch operation now takes about a minute. Kudos to the development team for speeding that up so significantly!

--Dave Novak

Hello -- I am using the latest version of Vault (4.1.4) and the most recent Vault Plug-in for CruiseControl.NET (also 4.1.4). I have yet to get my exclusionFilters to work properly using the plug-in. They are blissfully being ignored. Here's an example: <project name="MyProject 9.0.0 Client&quo...

Yes, that would be great. This functionality actually is VERY close to working from the Show History results, if you request history since a label or date and specify only the actions Checkin and Add . The only problem is that when you select more than one item from the History Explorer window, you ...

Is there any way to ask Vault to get files since a given date or label? Using Show Labels , I can easily get all files associated with a label, but I cannot get just the files that have changed. I can even Diff a label and see the files that changed, but cannot do a get from the Show Differences dia...

I have just upgraded to Vault 4.1.2 from Vault 3.5.2. One of the subtle differences between 3.5.2 and 4.1.2 is shadow folder behavior when setting up a New Shadow Folder and the specified shadow folder target directory does not already exist. Under the new version of Vault, I get the following error...

I think I got this worked out. For all users with "Access", I simply clicked the Delete this assignment hyperlink to remove access. Access is now as intended. What I don't understand is how these users got access in the first place. According to the Repository Access screen (prior to click...

That indeed is the problem, except I don't understand how they have repository access since by default users are supposed to have no access.

Is there some easy way for me to set access for all users except those in the Xaviant group to No Access?

I am running Vault 4.1.2. No other group rights give them access to this repository. A screen shot is included below:

The Hide users without repository access option on the Folder Security page in the admin does not appear to be working. On one of our repositories, only a handful of our 50 users have any type of access to the repository whatsoever. However, even with Hide users without repository access checked and...

It's working! After giving ownership of all files in that folder to Administrators and then replacing permission entries on all child objects from the parent folder (which already had full permissions for Administrators), then rebooting, all is fine now. Permissions on these files is now the same on...

I agree that this likely has something to do with permissions on that folder or files contained therein. The folder itself has full permissions for Administrators, but the files do NOT have such permissions. Those seem to have permissions for only NETWORK SERVICE and ASP.NET Machine Account. I'm hes...

I have a lead now into what the problem could be. Running under the Vault-configured application pool (VaultAppPool), Shadow Folders does indeed work. The identity used by VaultAppPool is NETWORK SERVICE. I had the Vault Shadow Folder service running under my own application pool, which is configure...