We upgraded from 3.5 to 4.2 and are running both SOS services on our Windows 2003 server. I am doing some testing with the 4.2 server and client before we move all our people up to 4.2.
The 3.5 version worked great.
The 4.2 version is running terrible. It seems that if you get hooked up you might be able to get to subdirectories, but if you ever try to refresh the tree, SOS client just gives an hour glass forever.
After that happens, you cannot connect to the SOS server unless you restart the service on the Windows 2003 server.
What could we change in the configuration to get rid of this problem?
I changed the logging to verbose, and the server has these lines the bottom of the log file:
10/23/2006 5:14:54 PM - 2: Received message number 101.
10/23/2006 5:14:54 PM - 2: GetProjectTree project: $/
10/23/2006 5:18:17 PM - 2: Exception: An existing connection was forcibly closed by the remote host
10/23/2006 5:18:17 PM - 2: Error processing client request: at System.Net.Sockets.Socket.Receive(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags)
at ClassicService.ProtocolMessage.ParseStream(Socket socket, Crypto crypto)
at ClassicService.Client.GetMessage()
10/23/2006 5:18:17 PM - 2: User Alan disconnected from s154-5-79-215.bc.hsia.telus.net.
and then the SOS client just sits at the hour glass.
Darcy
SOS Client hangs
Moderator: SourceGear
What Automatin Component Version are you using?
You are testing with the client and server and VSS all on the same machine? Are you using a local or public IP?
Could you increase the level of logging, more information here: http://support.sourcegear.com/viewtopic.php?t=463, recreate the scenario and send a server log? SourceOffSite log file (log.txt) is located on the machine where the SOS server resides. You can send that to support at sourcegear.com and just reference this post or send it to me using the private function here.
You are testing with the client and server and VSS all on the same machine? Are you using a local or public IP?
Could you increase the level of logging, more information here: http://support.sourcegear.com/viewtopic.php?t=463, recreate the scenario and send a server log? SourceOffSite log file (log.txt) is located on the machine where the SOS server resides. You can send that to support at sourcegear.com and just reference this post or send it to me using the private function here.
Have you applied the fix mentioned here: http://support.sourcegear.com/viewtopic.php?t=10
I have looked over the log. I would go back to saying to apply the fix I posted in my last message.
If the issue continues after the fix, and only after the fix, then it looks like something else is attempting to use the same port as SOS, and either the other application or SOS needs to be configured to use an unused port.
If the issue continues after the fix, and only after the fix, then it looks like something else is attempting to use the same port as SOS, and either the other application or SOS needs to be configured to use an unused port.