SourceGear Support

I guess I have to ask the obvious question: is IIS 5.0 installed on this machine?

What is the output of "ldd /Applications/SourceOffSite/sos"? This should list the dynamic libraries that sos depends on. On most Unix platforms, the libraries are only referenced by their major version in the binary, so the dynamic linker will follow the symlink to the correct minor versio...

What version of Vault are you using? Older versions of Vault had problems with the .NET Framework 1.1 SP 1, but this problem isn't present in 3.0.7 (and a few versions before, I think).

The only solution that comes to mind is to bind two different IPs to this server, and let Apache use port 80 on one IP, and SOS use port 80 on the other IP. I can't think of any solutions that would let the two processes both bind to port 80 (or otherwise share access to it).

Yesterday, after a test on a small solution. After switching back and forth between repositories hooking to the same working folder. I saw 'Unknown' file status and have experienced a merge error in one of the local file. I didn't push the test further but there was definitely something to be caref...

The first thing I should say is that SourceGear did not design Vault to work in this way. Bad things may happen that we don't know about, because we haven't tested Vault in this configuration. Files written to the _sgbak folder are never read again by Vault, and are given names that include time str...

I'm not sure if your question is primarily about authentication of users performing get/checkout/commit operations, or about the visibility of data as it's transfered. I'll answer both. Vault authenticates connections from clients using user information stored on the server (a valid username and mat...

We haven't made any packages for the Unix platforms primarily because it simply wasn't easy to integrate into our build system (which is, currently, entirely Windows-based). On the other hand, it should be pretty simple to package. The files you would need to copy to your Unix host would be a bunch ...

I'm trying to reproduce this kind of problem in a development environment, and I haven't been able to edit a file so that Vault doesn't make a pending change set item for it. Are there specific editors that seem to cause this problem more than others? Are there any other special circumstances when t...

The Vault client doesn't use iconv, but the SourceGear DiffMerge tool included with it does.

The error message the client is printing could be more helpful. The actual problem is the part at the very end (wait for the mutex was abandoned). Vault 2 had problems with its use of Windows sytem mutexes. Sometimes they were not disposed of properly before the garbage collection process occured, a...

I've logged a feature request for this option. This sounds like a good optimization for most Vault users. File statuses would be incorrect in the (confessedly rare) case where the file dates remain the same but the contents have changed. We have had a few customers with build systems like this (a fi...

If the server is hosted by a third party (not inside your corporate network), the IP you use to contact it should remain the same. Have you checked for the presence of a proxy while connected through the VPN? It's common that companies require the use of a proxy on their internal networks, and a VPN...

When your VPN is enabled, Windows may automatically set an automatic proxy for IE. It turns out that .NET applications (including Vault) aren't allowed to detect automatic proxy settings, and would continue to try to directly connect to the server (which may not be allowed by your network configurat...

Vault connects to its server using the HTTP or HTTPS protocol. If you regularly specify a special port during login in the Vault client, that is the only port the client uses. The default HTTP port is 80, HTTPS is 443. If you can visit the Vault server with a web browser (http://vaultserver.domain.c...