SourceGear Support

When you move a Vault database to another SQL server installation, you need to drop and then recreate the login and db user used by Vault.

See this link for more info:

http://support.sourcegear.com/viewtopic.php?t=24

By default, SourceOffSite looks for WinDiff and tries to launch it for viewing differences. Did you browse for the WinDiff utility in the External Programs tab or are you just using the default WinDiff setting? In some instances, it is necessary to browse for WinDiff in order to get it to work. This...

Error: "Access denied attempting to launch a DCOM Server" when trying to start the SOS Server service. The SOS Server is not a DCOM Server ... nor does it use DCOM. Is the SOS Server on the same machine as the VSS database? If so, I would suggest you try changing the account running the Se...

Check out this KB article and see if it fits your situation.

http://support.sourcegear.com/viewtopic ... ht=chunked

Do you have a Vault Server on another machine? If so you could connect with the Vault Admin tool and deactivate your license on that machine and copy it to a text file. Then install Vault Server on this machine, connect with the admin tool and paste in the license. The Vault admin account doesn't ne...

Do you have a Vault Server on another machine? If so you could connect with the Vault Admin tool and deactivate your license on that machine and copy it to a text file. Then install Vault Server on this machine, connect with the admin tool and paste in the license. The Vault admin account doesn't ne...

If you are upgrading from Vault 1.1 or later, you can install Vault 2.0 over your existing installation. If you have a Vault 1.0.3 or earlier, uninstall the Vault Server (when prompted, choose to keep your database), then install Vault 2.0. Your database will be upgraded as part of the installation....

The SourceOffSite Server returned service specific error 2147... This error message points to a problem with the Java Virtual Machine on the server machine hosting the SourceOffSite Server. The SourceOffSite Server was written in Java and works best with Version 5.00.3240 or later versions of the Mi...

Error 1067 occurs when there is a configuration problem with the SourceOffSite Server. The log file in the SourceOffSite folder on the server machine will help identify the cause of the error. Typically, Error 1067 happens for one of three reasons: The serial number configured in the Server Manager ...

Clicking on a project to which you do not have access rights will cause the File List window to grey out and the SOS Client appear to hang. The message in the Status window is "unrecognized message 421."

Clicking the "Stop" button returns the Linux Client to normal operating mode.

Operation failed - $//(<project>) appears in client status window If this error occurs for any project: Please verify that the option in SourceSafe called "Remove local copy after Add or Check In" is not enabled in your VSS installation on the SOS Server machine. This can be verified via T...

This error occurs when an Export Edition Client tries to connect to an SOS Classic Version 3.5.3 Server that is configured to only allow 128-bit connections. If the SourceOffSite Client is using a 56-bit encryption key, the Server should be configured to accept 56-bit connections. The Server can be ...

The Client was unable to locate key file 'C:\Program Files\SourceOffSite\servername.key' This error message occurs when a secure connection is not possible because a key has not yet been imported into the Client. In order for a secure connection to work, a User Key must be created in the Server Mana...

This error occurs when a secure connection is not possible because an incompatible key exists in the SourceOffSite Client folder. User keys are created with two variables -- a server name and a user name. These may be read in the import key file (.iky). The server name and user name used to create a...

This error message means the user is not configured in the SourceSafe Admin utility for the SourceSafe database to which they are trying to connect. This can be verified by trying to log in as the same user to the same database using SourceSafe Explorer. SourceOffSite uses SourceSafe user names and ...