SourceGear Support

I'd still suggest trying the registry fix to see if it helps. If it doesn't, you can always revert back. Has this problem been occurring for a long time or has it just recently started? For how long have you been running SOS on that server machine? If the registry change doesn't help, I may need to ...

With SOS 4.0, you should be able to run both clients simultaneously without any problems, but you should also be able to perform most operations from within VS.NET if you prefer.

If you attempt a Get Latest on several files at once and automatic merge fails for several of them, SOS will show you a list of all of the files that require a manual merge. You have probably not seen the "Needs Merge" status because your file lists were not refreshed before you performed ...

If the changes user A is making conflict with those made by user B, then the SOS Client will not be able to automatically merge the two files, and user A will need to do the merge manually. In this case, from the SOS menu, choose "Show Merge", and the configured merge utility will show the...

SourceOffSite 4.1 and 4.2 integrate with Dragnet, SourceGear's new bug tracking product, allowing users to view their open bugs from within the SOS Client and marking bugs as fixed or updated when checking in files. To configure SOS integration with Dragnet, follow the steps below. 1. First, if you'...

SourceOffSite 4.1 is now available and can be downloaded from: http://www.sourcegear.com/sos/downloads.asp SOS 4.1 is a free upgrade for 4.0 users. A list of new features and bug fixes can be found at: http://support.sourcegear.com/viewtopic.php?t=2582 Additional instructions for those upgrading fro...

SourceOffSite 4.1 is now available and can be downloaded from: http://www.sourcegear.com/sos/downloads.asp SOS 4.1 is a free upgrade for 4.0 users. A list of new features and bug fixes can be found at: http://support.sourcegear.com/viewtopic.php?t=2582 Additional instructions for those upgrading fro...

SourceOffSite 4.1 is now available and can be downloaded from: http://www.sourcegear.com/sos/downloads.asp SOS 4.1 is a free upgrade for 4.0 users. A list of new features and bug fixes can be found at: http://support.sourcegear.com/viewtopic.php?t=6815 Additional instructions for those upgrading fro...

I did find one thing that seems to work - if I open the solution on my second machine (the remote machine) using integrated VSS first, close, and then switch to SOS again, I'm able to get it loaded. But if I open the solution on the 1st machine again using integrated VSS, I have to do this procedur...

In that case, as a test, let's try this: 1. Take one of your existing .vbproj or .sln files and make a copy of it and give the copy a .txt extension. Then add the file using the SOS GUI Client and see if you can check it out. 2. Then create a new text file that simply has the characters "hello&...

Let's try to narrow it down by sticking to just using the SOS GUI Client for now, instead of working within VS.NET (since VS.NET adds its own complexities on top of everything). It would even be best for now if you could exit VS.NET when attempting to use the GUI Client just to make sure that VS.NET...

Yea, the log file shows that the exception is occurring during the database open, so it appears to be a problem with your SourceSafe installation on the SOS Server machine. Reinstalling SOS will not correct the problem. What were the other two products you installed? I'm wondering if one of them cau...

The "beginning this morning" part is what caught my eye. Does that mean that everything was working fine before today? Have there been any known changes in the SOS Server and/or Client environments? Are there are error messages listed in the server's log file? Also, what do you mean by &qu...

If you turn off the keep-alive option, does the message never appear?

If it still appears, it may be because of the "automatically refresh file list" option. Do you have that enabled?

Do you know why your connection is being closed? Is that normal for the network you're on?

What were the other 2 products you installed? It appears as if something may have happened to your SourceSafe Automation component (which the SOS Server uses). Enable verbose logging and then email me the log file after you try to login again. To enable verbose logging, follow these instructions: ht...