SOS Server 4.0 pro error trap

[KuroK]

if I connect to server and try to list folder with no permission for me
SOS server hunged up

------begin log.txt
3/17/2004 5:47:19 PM - Waiting for a connection....secure = True
3/17/2004 5:47:19 PM - Waiting for a connection....secure = False
3/17/2004 5:47:27 PM - Connection accepted from 10.1.1.46:1139, session id is 1.
3/17/2004 5:47:36 PM - 3/17/2004 5:47:36 PM - Server Exception (421): [$/DatabaseDesigner] - BAD_PERMISSIONS
3/17/2004 5:47:36 PM - 1: Server Error: 421
3/17/2004 5:47:48 PM - Killing disconnected or idle client IS~MIKE - (10.1.1.46)
3/17/2004 5:47:48 PM - 1: Exception: A blocking operation was interrupted by a call to WSACancelBlockingCall
3/17/2004 5:47:48 PM - Killing disconnected or idle client - ()
3/17/2004 5:47:48 PM - 2: Failed to start the client instance: Object reference not set to an instance of an object.
3/17/2004 5:47:48 PM - Exception in Listen(): System.ObjectDisposedException: Cannot access a disposed object named "System.Ne
t.Sockets.Socket".
Object name: "System.Net.Sockets.Socket".
at System.Net.Sockets.Socket.get_RemoteEndPoint()
at ClassicService.Listener.Listen()
3/17/2004 5:50:20 PM - Stopping the service.
3/17/2004 5:50:20 PM - Exception in Listen(): System.Net.Sockets.SocketException: A blocking operation was interrupted by a ca
ll to WSACancelBlockingCall
at System.Net.Sockets.Socket.Accept()
at System.Net.Sockets.TcpListener.AcceptSocket()
at ClassicService.Listener.Listen()

------end log.txt

[lbauer]

What version of the SOS Client are you using?

We saw this problem when SOS users connected to SOS 3.5.3 servers with clients that were 3.5.1 or earlier. The problem was that the SOS Server honored VSS project rights, but this didn't work with the older clients. If you're using an older client, this could be a similar problem with SOS 4.0

If you are using an SOS 4.0 client, let me know and we'll check into this as a possible bug. Also, it would be helpful to see how your user's projects rights are set up in the VSS Admin Tool. If you could post or email me a screenshot, it could help us reproduce the problem.

[KuroK]

I try to use only SOS 4.0 client with sos server on other port

[KuroK]

3/22/2004 11:04:44 AM - rose (10.1.1.50) is attempting to listen for connections on secure port 9890
3/22/2004 11:04:44 AM - rose (10.1.1.50) is attempting to listen for connections on unsecure port 9888


3/22/2004 11:04:44 AM - Waiting for a connection....secure = False
3/22/2004 11:04:44 AM - Waiting for a connection....secure = True
3/22/2004 11:12:20 AM - Connection accepted from 10.1.1.27:4956, session id is 1.
3/22/2004 11:12:42 AM - Connection accepted from 10.1.1.27:4957, session id is 2.
3/22/2004 12:07:07 PM - Killing disconnected or idle client tank27.unisquad.com - (10.1.1.27)
3/22/2004 12:07:07 PM - Connection accepted from 10.1.1.46:1106, session id is 3.
3/22/2004 12:07:07 PM - 2: Exception: A blocking operation was interrupted by a call to WSACancelBlockingCall
3/22/2004 12:07:07 PM - Killing disconnected or idle client IS~MIKE - (10.1.1.46)
3/22/2004 12:07:07 PM - 3: Failed to start the client instance: A blocking operation was interrupted by a call to WSACancelBlo
ckingCall
3/22/2004 12:07:23 PM - Connection accepted from 10.1.1.46:1107, session id is 4.
3/22/2004 12:09:24 PM - Connection accepted from 10.1.1.46:1110, session id is 5.
3/22/2004 12:18:44 PM - Killing disconnected or idle client IS~MIKE - (10.1.1.46)
3/22/2004 12:18:44 PM - 5: Exception: A blocking operation was interrupted by a call to WSACancelBlockingCall
3/22/2004 12:18:44 PM - Killing disconnected or idle client - ()
3/22/2004 12:18:44 PM - 6: Failed to start the client instance: Object reference not set to an instance of an object.
3/22/2004 12:18:44 PM - Exception in Listen(): System.ObjectDisposedException: Cannot access a disposed object named "System.N
et.Sockets.Socket".
Object name: "System.Net.Sockets.Socket".
at System.Net.Sockets.Socket.get_RemoteEndPoint()
at ClassicService.Listener.Listen()
3/22/2004 12:31:49 PM - Stopping the service.
3/22/2004 12:31:49 PM - Exception in Listen(): System.Net.Sockets.SocketException: A blocking operation was interrupted by a c
all to WSACancelBlockingCall
at System.Net.Sockets.Socket.Accept()
at System.Net.Sockets.TcpListener.AcceptSocket()
at ClassicService.Listener.Listen()

[lbauer]

I set permissions on my VSS project tree so that I had RCA access to one project but no access to the rest. I was able to click on the projects where I had no access, but SOS did not crash. There were appropriate "bad permissions" errors in the log.

So if SOS is crashing, your configuration must be different than mine. Could you send me a screen shot of your projects rights as set in VSS?

Does SOS work properly for those folders where you do have rights?

Do other users have the same problem with SOS crashing when they try to log in?

[KuroK]

Permissions for first log is attached.

SOS server started from system account that have full permissions on VSS DB folder.

Yes,
I tested this with other user and other WS - and have same problem.

PS
I very impressed that your company rewrite SOS server on C language
because old SOS server work very slovly