SourceGear Support

I too am finding this behavior very annoying...several times a day. Using version 5.0.2 (18753). My setup is same as ohbillie: - Recursive, Lock onto this folder, and Background updates are checked. - Search by: Any Status I frequently have Vault Client on my second monitor. After making changes in ...

Windows Installer caches a copy of the installation file used so that you can do reinstalls, repairs, and uninstalls without having to have the original file. If you somehow deleted this cached copy of the preview installer then you would get this error. Changing the GUID like you did is one way to ...

If you change the ports that one of the servers listens on you can run both the 3.5.x and the 4.0 servers at the same time (if you really need to).

The SOS Server does not push the tree changes to the client unless it is requested. Getting the project tree is an expensive operation so you have to do the refresh manually. However, you should only have to hit refresh once. Refreshing from the root of the tree will refresh the entire tree. It will...

SOSCMD is NOT sending the username where the server expects the database path. It is a known bug in the VSS Automation Component.

Sorry I can't help with the actual problem.

Right click on the file and choose properties. One of the tabs on the dialog that appears will tell you what you're looking for. I think it is called "Links" (I don't have SOS at this location).

You need to setup some SourceSafe databases. These lines give a clue: 24/03/2004 16:10:26 - Invalid SourceSafe Initialization file 24/03/2004 16:10:26 - Invalid or no databases to support. Run the Server Manager to configure databases OR You should be able to copy the server and alias values from yo...

Are you sure the users exist in SourceSafe?

The list you refer to just reserves a SOS license for those users.

The SOS client just opens a standard TCP/IP connection to the server and sends packets across that connection.

Most likely it is the D-Link hardware that is causing the trouble, as you observed when you switched routers. Why you only see it with SOS is a mystery for SG.

I believe this is a VSS 6.0d issue. The automation component often has trouble getting history under certain conditions with 6.0d.

Make sure you have all hotfixes and other patches available. Alternatively, 6.0c should work also.

Make sure you turn off checksums now that your status is updated. Leaving it on may affect performance.

When I do a history on a file, I can not do a diff on the version I have on my local machine and with an older version. I also can not do a diff between versions in the history. Also I can not get an older version out of VSS, however I can do all of these things when I use the VSS Client. What happ...

I have followed the instructions in the KB regarding this error and it did not resovle it. I did not find any of the indicated keys in the registry. I then installed the client version and still same error. I searched for the SSAPI.DLL file on the server and it was not found. This was a move from a...

I don't know if your case is the same, but most multi-NIC users reported that their problems went away when they removed one NIC (not possible on the DL-320, right?). Have you tried the latest preview of SOS 4? The server is written in C# and SourceGear doesn't think the multi-NIC card problem exist...

blackbaud wrote:forgot to login to the forum before posting the issue...

Does this server have more than one NIC in it?