SOS 5.0.1 hangs on "Cancel current operation"

[guillaume]

Hi,

In SOS 5 client, if I click on a folder, it starts to refresh the list content. If I click on "Cancel current operation", the client seems to cancel the operation, but for a reason I don't know, it then also tries to reconnect to the server.
It then stays hanging for ever on displaying "Logging in...". the cursor shows timeglass as if the client was working normally, waiting for an answer from the server that never comes.

Then, attempt to stop SOS 5 server service from service panel does not work (it does not stop nor answer), and it must be killed in task manager.

If I take care never using "Cancel current operation", it works well.

The server log is as follows:

2009-11-26 11:39:47,919 - Loading SourceOffSite Server configuration from C:\Program Files\SourceGear\SourceOffSite 5 Server\sossvr.prp
2009-11-26 11:39:47,934 -
2009-11-26 11:39:47,934 - ****************************************************
2009-11-26 11:39:47,934 - ****************************************************
2009-11-26 11:39:47,934 - SourceOffSite Server 5.0.1.242 Professional - With Cryptography
2009-11-26 11:39:47,934 -
2009-11-26 11:39:47,934 - CurrentCulture is nb-NO.
2009-11-26 11:39:47,934 -
2009-11-26 11:39:48,044 - Server Information
2009-11-26 11:39:48,044 - Operating System: Microsoft(R) Windows(R) Server 2003, Enterprise Edition
2009-11-26 11:39:48,044 - Service Pack: 2.0
2009-11-26 11:39:48,044 - OS Version: 5.2.3790
2009-11-26 11:39:48,044 - Locale: Ox0414
2009-11-26 11:39:48,044 - OSLanguage: 1033
2009-11-26 11:39:48,044 - Total Physical Memory: 7,99 GB
2009-11-26 11:39:48,044 - Time Zone: (GMT+01:00) Brussels, Copenhagen, Madrid, Paris
2009-11-26 11:39:48,044 -
2009-11-26 11:39:48,044 - SSAPI.dll Information:
2009-11-26 11:39:48,044 - Version: C:\program files\Vss\win32\SSAPI.DLL (06.00.9848)
2009-11-26 11:39:48,044 - Threading Model: Apartment
2009-11-26 11:39:48,044 -
2009-11-26 11:39:48,044 - Logging at level Error
2009-11-26 11:39:48,044 -
2009-11-26 11:39:48,044 -
2009-11-26 11:39:48,059 - Number of licenses configured: 10
2009-11-26 11:39:48,059 -
2009-11-26 11:39:48,059 - SourceSafe Initialization file(s) located at:
2009-11-26 11:39:48,059 - D:\Utvikling\VSS\srcsafe.ini
2009-11-26 11:39:48,059 - D:\Utvikling\VisualSourceSafe\srcsafe.ini
2009-11-26 11:39:48,059 - SourceOffSite Server will be using the Visual SourceSafe 6 (non-enumeration optimized) Interface.
2009-11-26 11:39:48,059 - Started at 11/26/2009 11:39:48
2009-11-26 11:39:48,059 - ****************************************************
2009-11-26 11:39:48,059 - ****************************************************
2009-11-26 11:39:48,059 -
2009-11-26 11:39:48,059 - FILSERVER01 is attempting to listen for connections on secure port 8081
2009-11-26 11:39:48,059 - FILSERVER01 is attempting to listen for connections on unsecure port 8080
2009-11-26 11:39:48,075 - Waiting for a connection....secure = False
2009-11-26 11:39:48,075 - Waiting for a connection....secure = True
2009-11-26 11:39:56,028 - Connection accepted from xx.xxx.xx.xx:50967 on local address 192.168.91.20:8080, session id is 1.
2009-11-26 11:39:58,809 - Connection accepted from xx.xxx.xx.xx:50968 on local address 192.168.91.20:8080, session id is 2.
2009-11-26 11:39:59,949 - 1: ProtocolMessage.ParseStream() - Socket error reading protocol message number (Read 0 of 1 bytes). Exception: Exception: CONNECTION CLOSED
2009-11-26 11:39:59,949 - 1: ProtocolMessage.ParseStream() Get ProtocolMessage ID Exception: CONNECTION CLOSED BytesRead 0 of 10 (allowed).
2009-11-26 11:39:59,949 - 1: Connection Closed: CONNECTION CLOSED
2009-11-26 11:39:59,949 - 1: VSS database closed for the session id 1.
2009-11-26 11:40:09,371 - Connection accepted from xx.xxx.xx.xx:50969 on local address 192.168.91.20:8080, session id is 3.

Best Regards,
Guillaume

[jclausius]

When cancel operation is invoked, the SOS client will kill the network connection and reattempt to establish communications. It appears from your log, you are using VSS 6.0d on the sever, but the threading model is incorrect which might explain why the client could not reconnect to the server.

The VSS 6.0d threading model should be set to "Both", and not "Apartment." See http://support.sourcegear.com/viewtopic ... 14&t=12691 and see if that resolves the issue.

[guillaume]

Yes, it worked

Thank you.

Regards,
Guillaume