SourceGear Support

The first thing to try would be to enable debug logging on the server, and look for any errors there. See this KB article for details. If nothing looks out of the ordinary on the server, you can enable client-side logging (see this KB article ). When client-side logging is enabled, and the string &q...

Vault currently doesn't have any feature like this, but it will soon (it's scheduled to be included in the next release after 3.0). Vault needs to keep the baseline version of each file in storage, as well as any versions a merge was done from (so the merge can be undone). Deleting all old versions ...

Vault doesn't use isolated storage for any of its settings any more (we had too many problems with it). The file you're looking for is called CacheMember_WorkingFolderAssignments , and its exact location depends on a few things (your Vault username, repository GUID, etc.). Read this KB article for d...

It seems that the fixes that went into 2.0.6 broke some of the things you've reported. The columns were not being saved and loaded correctly, and the focus issue crept in somehow as well. All of these problems have been logged as bugs and will be fixed in the next version of Vault (3.0).

You appear to have a duplicate </appSettings> key near the end of the file.

Could you describe what kinds of files are being missed? We've had problems in the past with documents saved by Microsoft Word being recognized. If it's many types of files, are your working folders on a network share or legacy filesystem?

Vault 3.0 introduces a client-side feature that uses a Cyclic Redundancy Check ( CRC ), a type of one-way hash function, to detect modifications to files in working folders. Because each byte of the potentially modified file is read to compute the CRC value, which is then compared against the CRC va...

This is a known problem with our mutex handling, and will be fixed in a future release of Vault. Does this error happen often with this file? Does the Get Latest Version include other files, or only this one?

When you say "if I commit while out of sync", do you mean that the files are in a Needs Merge state? If so, a dialog will appear offering an interactive merge (which will "sync" the files, also giving you the chance to approve the changes). I may have misunderstood what you meant...

Spaces within the quoted values may affect logging operation, but spaces outside will be parsed according to XML standards (basically all collapsed into a single space). So the indentation of your tags shouldn't matter. The tags in the KB article should be placed inside the <appSettings> tag (which ...

The Unix SOS client should work with the latest GTK libraries. I believe the problem was only with GTK 2.4.0, which was released with bugs related to the tree control. This bug was fixed in GTK 2.4.1 (and all later versions), but many distributions shipped with 2.4.0.

If you can reproduce this bug easily, please turn on the client-side logging for the check out list. See this KB article for detailed instructions. You can enable the logging class "all" (which will create a large log file) until you can reproduce the problem. Then mail me the log file (yo...

If you can reproduce this problem with client-side logging enabled (see this KB article for details) and send me the log file, we can diagnose your problem quicker. In the VaultGUIClient.exe.config file, set the "classesToLog" value to "checkoutlist", then start the client. When ...

You can try deleting your client-side SOS cache files to cause the client to fetch the full structure from the server on the next login. These files are stored at: ~/.sos/servers/<yourservernamehere>/*.sos

Are there any other warnings or errors in the messages pane in the bottom of the main window?