SourceGear Support

Enabling the Timeout Idle Connections feature of the SOS Server prevents more than one user from connecting at a time. If that feature is enabled, once one user connects, if a second user tries to connect, both get disconnected. To prevent this from happening, start the Server Manager, go to the Gen...

When you enter multiple serial numbers in the SOS 4.0 Server Manager, they will be written to the sossvr.prp file and recognized by the SOS Server, but the next time you open the Server Manager, only one serial number will appear.

Can you both repost your Collab issues to the Collab support forum? That will eliminate any confusion and hopefully trigger some responses.

Did you install SOS 4.0 to the same directory as your 3.5 Client? The SOS 4.0 client was designed to use the same cache file format (for remembering file statuses) as 3.5, but 4.0 will only find those cache files if stored to the same directory as 3.5. If you use the 4.0 GUI Client, I'm guessing all...

Can you email me your sossvr.prp file? We've had a couple of similiar reports of the errors you are seeing with the server and multiple connections, and in both cases, the server machine had multiple network cards. Does your server had 2 NICs? When more than one user connects, do the connections dro...

Yep, that's the only difference. Professional has encryption, Standard doesn't.

That option seems to work fine in the SOS GUI Client, but it does not work in the IDE Client. It will be fixed in our next bug fix release. One word of caution though, if this option was working in the IDE, it would cause the behavior of VB and VS.NET to change when performing operations like file e...

No, there is no limit to the size of the cache file.

See my first note... try exiting VS.NET and perform a Get Latest using the SOS GUI Client and once that finishes correctly and file statuses are no longer Renegade, then close the GUI Client and restart VS.NET

Is this a project you just recently added to source control?

If you perform a Get Latest Version on one of the files, what happens?

You should be able to turn of the SOS Client option "Use read-only flag for files that are not checked out" but we are currently investigating a bug with this option in 4.0 which may be preventing it from working correctly. If it is a bug, we will fix it and release a patch.

Yes, running two instances of VS.NET with integrated SOS 3.5 could cause files in one instance to appear Renegade. The fetch date of files are stored by SOS in cache files called *.sos files. SOS compares the date at which it fetches a file with the current mod date to determine Edited and Renegade ...

If you are positive that you haven't modified any of the files, then the simpliest way to resolve this would be to exit VS.NET and using the SOS GUI Client, perform a Get Latest from the root of the solution. When it prompts you about overwriting, choose Yes to All, as you've been doing within the I...

The SOS 4.0 Server was designed so that it could be installed on the same machine as the 3.5 Server, without the two interfering with each other. Email to me your sossvr.prp file from your SOS 4.0 Server installation directory and also the log.txt file (which should exist if you tried to start the 4...

Hmmm. SourceOffSite should work the same way, and does in our testing here. The keyword expanded file should be updated locally after your Check In. So we still need to determine why this isn't happening for you. What type of source files are you testing with?

Using the SOS GUI Client, what is the status of those files? (select their parent project and look under the Status column of the file list pane)