SourceGear Support

Usually the name you login as is in the SCC_Aux_Path variable, but yours seems to be missing. That login name would be different for each user. If you are starting with a fresh copy of a project, you need to do an Open From Source Control (the first time only) to create the MSSCCPRJ.SCC file based o...

You should delete your client cache files, which you can find the location of via Tools->Options->Local Files->Cache/Backup locations.

note that this will delete the state of all files and removing all working folders, so you'll need to re-get all the files.

Hmm - that definitely isn't normal :) The RAM on your IIS box looks low, but that is very unlikely to be the problem, just something to note for the future. Put the server in debug logging mode (change via the Admin Tool, Server Options), which may give some indication where the slowdown is. Also, t...

Try this one, which was compiled with our set of sources, and may work better. Unfortunately, our DiffMerge tool wasn't designed to support Chinese characters, and we haven't tested it with other kinds of .so files other than the ones we ship with. If this doesn't work out, I would suggest obtaining...

Renegade means Vault thinks the file is edited, but it is not checked out. If all your files are renegade, it is likely that the files merely have a different datetime stamp than the client thinks they should. You should verify that the file contents are the same as those in the repository, then sim...

There is definitely some other issue going on, since VS determines which files to check out, not Vault. Normally adding a file to a project will only checkout the project file in Vault. You might check the status of the files in the Vault GUI client at the time you add the files. If they are anythin...

Just do a Get Latest and add those files to TFS. I don't believe there is a way to import your history, unless someone has come up with a export/import tool for TFS.

Sorry - I jumped ahead to what you need, which is two clients running on the same machine. The installer is setup to upgrade an existing installation of the client, which means the existing installation always gets replaced by the current version of the client, regardless of where you install it. Th...

You will probably need to do an Open From Source Control from within VS, followed by a Get Latest from the Vault GUI client if Open From Source Control does not retrieve every file that is in the Vault tree. I would still not recommend storing the MSSCCPRJ.SCC file under source control, since doing ...

This page is created on install and not changed by Vault afterward, so as a workaround you can update the HTML to point to the right name for the server

Yes, it is our feature/bug DB, but we don't have a date for its release. We'll add your vote, which will bump it up in priority.

Yes, this ends up being a limitation of VS2003. They only display information there for SourceSafe, and for all other SCC providers they display <Unable to Display>.

We have a KB article on how to have two clients running at the same time: http://support.sourcegear.com/viewtopic.php?t=4010

There are a few limitations to running two clients with different versions, so be sure to read all the article.

Don't include "vault" or the connection info in the batch file itself. So, your CLC call should be: vault -host host -name name -password pw -repository rep batch batch.txt And the commands in the batch file (one per line, no extra lines) should be: add -commit $/repfolder c:/temp/file add...

These files are created by Visual Studio anytime someone binds/unbinds a project to source control. The can safely be deleted and obliterated, as VS never uses them again.