SOS Server 4.0 locking up

rstrong · Post by **rstrong** » Thu Mar 11, 2004 8:29 pm

Just installed the release version of SOS 4.0. Having problems with the server regularly locking up when a long duration operation is running (typically "get latest version" to a large project within vs.net) and a new connection is attempted by the same or a different user. Often all that is necessary is that an attempt be made to open a new instance of SOS Explorer to get service to lock up.

Would occasionally have this sort of issue under 3.5.3. Went away completely by checking the Automation Component Synchronization checkbox under Debug in the Server Manager. Option not available in this verions (is it available via app config file?).

Using the 4.0 client as well as 4.0 server. Both client and server operating systems are Windows Server 2003.

corey · Post by **corey** » Thu Mar 11, 2004 8:54 pm

Which version of SourceSafe do you have installed on the SOS Server machine? If its 6.0d, see the following KB article:

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

Archie · Post by **Archie** » Fri Mar 12, 2004 12:35 am

Found same problem.
When one user is getting last version, another user attempts to connect, both users' connection will drop.
SOS Sever 4.0, Win2K with SP4. VSS6.0c
"ThreadingModel" is "Both"

corey · Post by **corey** » Fri Mar 12, 2004 8:04 am

rstong: are you also using VSS 6.0c?

Can both of you give tell me the exact version of the VSS automation component? On the machine where the SOS Server is running, go to your VSS installation folder, and check the version number of ssapi.dll (right click on the file, choose properties, then the version tab of the properties dialog, and the file version will be listed at the top).

rstrong · Post by **rstrong** » Fri Mar 12, 2004 11:17 am

Was using VSS 6.0d

Changing threading model of automation component to "Both" took care of the problem.

Thanks for the help.

corey · Post by **corey** » Fri Mar 12, 2004 11:24 am

Archie: If your connections are being dropped, instead of hanging the server, then perhaps you're dealing with a different problem. Can you email me your server's log file?