SourceGear Support

Note that if the purpose of doing this is to be able to retrieve files at a given state (and they won't be edited after that), you could always use labels to mark the folder version, and then get the tree as of the label at any time in the future.

The command line client source code has an example of these calls in the ProcessCommandGetLabel() command in VaultCmdLineClient.cs. The CLC source is included with the API installer. So, I would suggest looking there first for usuage, and you might even want to run the CLC in the debugger to see exa...

Turn on IDE logging and then try it again. See http://support.sourcegear.com/viewtopic.php?t=2898 for directions on logging, then either post the log file here or email it me.

So before the Vault login comes up, the error happens? That indicates a configuration problem on the 2nd machine.

This may be a dumb question, but is Vault installed on the other machine and set to be the default source control provider?

Vault fully supports VS 2005.

When you tried it on a different machine, did you first do an Open From Source Control to open the project?

When you installed the admin tool previously, did you use the separate Admin Tool installer, and are now try to install it with the server installer? This would likely cause problems, although I'm not sure whether it would show up in the errors you are seeing.

This is probably something to do with the .Net Framework. Try the following: 1. Completely uninstall the Vault client 2. Manually delete HKEY_LOCAL_MACHINE\SOFTWARE\SourceGear\Vault Client. 3. Manually delete your local cache at C:\Documents and Settings\[username]\Local Settings\Application Data\So...

This is set up via IIS on the server. You can specify the Vault Service to use non standard ports there.

For the client side, the server name in the Connect dialog can have the port number appended to it, such as "vaultserver.domain.com:XX"

The string isn't meant to conform to the windows standard. We print the machine name first because it is usually the unique part of the string, so it takes less space to determine differences.

The Vault server log outputs login and logout info. It is at %windir%\temp\sgvault by default.

OK, go to the server log (usually in %windir%/temp/sgvault) and see whether there are error messages related to a delete attempt.

Microsoft's MSDE and SQL Server are the only two databases supported by Vault. MSDE is free, but has a 2 GB limit on the size of the DB>

We need to determine whether this is a client or server issue. If you try the delete from a different machine or a different user on the same machine, do you get the same error?

Thanks for your understanding

3.5 will be released either this month or next month...

The imported labels will not appear differently in 3.5 - the dates and versions have to be adjusted in order to recreate the labels accurately in Vault. The contents of the labels are correct, at the expense of their versions numbers and therefore dates. One other (pedantic) note about 3.5 : The lab...