SourceGear Support

Vault 2.0 Windows 2003 Server XP Pro SP1 clients We've tenatively started moving to non-exclusive check out mode of operation, but have found that often checking out a group of files will end up with them all checked out exclusively. What appears to be happening is that if I check out only mergeable...

Vault 2.0 Windows 2003 Server XP Pro SP1 clients We use the default setting where checking in an unchanged file instead performs an undocheckout. Common behavior when someone owns a project is to have all or almost all files checked out, and periodically check in all and then continue working on the...

If you are just working with a small group of developers and externally verifiable security is not your major concern, your simplest route would be a self-signed certificate. Search for IIS6 Resource Kit (it works on IIS5.1 in XP as well) and the utility 'makecert'. You can have SSL up at no cost in...

I'm posting back here since I discovered how to deal with this one. The underlying VSS message was always something like: Unable to get $/Documents/PartsLists/WidgetPartList.xls from the VSS Database. SourceSafe was unable to finish writing a file. Check your available disk space, and ask the admini...

The VSS importer issues a warning about checked out files, valuable since it does not attempt to import the checked out status. This warning appears to correctly only list checked out files, however it incorrectly attributes who has the files checked out. If there are m developers with n total files...

Most of the time when developers in my company add files to source control these files are still being worked on so they must immediately be checked back out. VSS had an option on the add files dialog called 'check out immediately' which accomplished this. Vault appears not to have this, but seems l...