SourceGear Support

If they're bound within VS.NET, you should (1) unbind them (2) switch source control providers to SOS (3) rebind them to source control.

The bind/unbind process is done using the Change Source Control dialog within VS.NET.

If you look at your Serial Numbers within the Server Manager, and select one, the number of licenses is shown at the bottom of the dialog.

If you're referring to switching between VSS and SOS from within Visual Studio, the following article may help:

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

After the new projects are added, are the other users performing a "Refresh Project Tree" operation on the parent node of the new projects? This command is found under the View menu of the Client. By default, the SOS Client does not automatically refresh the project tree structure.

Derek,

Can you send me your <<servername>>.sos file, and your C++ project file? Those files may give us some clues and help us try to reproduce what you are seeing.

Hi Derek, Well, I'm not sure about the "ataset" (missing the "D", I don't think we've seen a problem like that before) but the main problem could be due to the local paths you have for the files. This could explain why the SOS GUI works fine, but within the IDE its messed up. Can...

Check out the following post:

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

When you create your crypto key in the Server Manager, you must provide the name of the server machine (either its hostname or IP address). After you import the key in the client and then try to connect to the server, you must use the same hostname or IP address.

In almost all cases when configuring VSS database paths in the SOS Server, you should use UNC paths instead of mapped drives. Give that a try and see if it makes a difference.

You may be having a different problem. Is the server creating a log file (called log.txt and located in the installation folder)? If so, send me the file and I can look to see what might be wrong.

Hi Derek, This has been a problem we have tried to deal with for a long time, but the fault lies in the VSS Automation component which the SOS Server relies on for interacting with the VSS database. Basically, the VSS Automation component does not provide the same history information that you see in...

Sorry, SOS does not support Branch from within project history.

The problem is, within VS.NET, even though you are performing the operation on the project, VS.NET passes that to SOS as a series of file check outs. So each file is handled in its own operation. However, we should able to add a "do not show this dialog again" checkbox which would solve th...

Hi Steve, Sorry for the delay. What exactly do you mean by "it works for a while after restarting the server, and then quits"? If you restart the server, you can connect with your laptop and perform operations as normal? If that's the case, after it quits working, can you have someone send...

Dave,

Do you mean you have mapped the drive to P on the machine where you are using the client?

If so, that doesn't matter. In your soscmd command, you want to use the drive letter that the SOS server users, which would be the D drive as configured.