Can't connect SOS client

If you are having a problem using SourceOffSite, post a message here.

Moderator: SourceGear

Post Reply
CTSstuart

Can't connect SOS client

Post by CTSstuart » Fri Jul 23, 2004 2:41 am

Hi,

Having used your demo, I have now moved to the next stage, and have installed the SOS server onto my VSS machine (new build).

After considerable messing about, moving directories, etc., I eventually got the service started by changing the rights of the VSS directory to allow the machine administrator access rights, and starting the service as .\administrator

I start the SOS client on the local machine, connecting to itself on the default unsecure port 8080, and try to login to the DB, and the login fails. I have copied the section of the log file below:

21/07/2004 16:42:39 - Stopping the service.
21/07/2004 16:42:39 - Exception in Listen(): System.Net.Sockets.SocketException: A blocking operation was interrupted by a call to WSACancelBlockingCall
at System.Net.Sockets.Socket.Accept()
at System.Net.Sockets.TcpListener.AcceptSocket()
at ClassicService.Listener.Listen()
21/07/2004 16:42:39 - Exception in Listen(): System.Net.Sockets.SocketException: A blocking operation was interrupted by a call to WSACancelBlockingCall
at System.Net.Sockets.Socket.Accept()
at System.Net.Sockets.TcpListener.AcceptSocket()
at ClassicService.Listener.Listen()
21/07/2004 16:42:41 - ****************************************************
21/07/2004 16:42:41 - SourceOffSite Server 4.0.2 Professional - With Cryptography

21/07/2004 16:42:41 - CurrentCulture is en-GB.

21/07/2004 16:42:41 - Server Information
21/07/2004 16:42:41 - Operating System: Microsoft(R) Windows(R) Server 2003, Standard Edition
21/07/2004 16:42:41 - Service Pack: 0.0
21/07/2004 16:42:41 - OS Version: 5.2.3790
21/07/2004 16:42:41 - Locale: Ox0809
21/07/2004 16:42:41 - OSLanguage: 1033
21/07/2004 16:42:41 - Total Physical Memory: 255.17 MB
21/07/2004 16:42:41 - Time Zone: (GMT) Greenwich Mean Time : Dublin, Edinburgh, Lisbon, London
21/07/2004 16:42:41 -
21/07/2004 16:42:41 - SSAPI.dll Information:
21/07/2004 16:42:41 - Location: file:///C:/Program Files/SourceOffSite Server/Interop.SourceSafeTypeLib.DLL
21/07/2004 16:42:41 - DisplayName: Interop.SourceSafeTypeLib, Version=5.1.0.0, Culture=neutral, PublicKeyToken=null
21/07/2004 16:42:41 -
21/07/2004 16:42:41 - Started at 21/07/2004 16:42:41

21/07/2004 16:42:41 - General logging level is Verbose. Method logging is Disabled.

21/07/2004 16:42:41 - Number of licenses configured: 10 21/07/2004 16:42:41 - SourceSafe Initialization file(s) located at: 21/07/2004 16:42:41 - C:\VSSDB\srcsafe.ini

21/07/2004 16:42:41 - cts-sourcecode is attempting to listen for connections on secure port 8081 21/07/2004 16:42:41 - cts-sourcecode is attempting to listen for connections on unsecure port 8080

21/07/2004 16:42:41 - Waiting for a connection....secure = True 21/07/2004 16:42:41 - Waiting for a connection....secure = False 21/07/2004 16:42:48 - Connection accepted from 192.9.200.30:4036 on local address 192.9.200.30:8080, session id is 1. 21/07/2004 16:42:48 - 1: Connection from: cts-sourcecode.central.ctsnet.co.uk (192.9.200.30) 21/07/2004 16:42:48 - 1: Preparing to send the list of databases... 21/07/2004 16:42:48 - 1: Sending the challenge to the client. 21/07/2004 16:42:48 - 1: Sending the challenge message body to the client. 21/07/2004 16:42:48 - 1: Waiting for the client's response... 21/07/2004 16:42:51 - 1: Reviewing the client's response... 21/07/2004 16:42:51 - 1: Process the client's non-crypto login request. 21/07/2004 16:42:51 - 1: User 'Cts' requesting to login to database 'C:\VSSDB\srcsafe.ini' 21/07/2004 16:42:51 - 1: Client is speaking protocol version 2.0

21/07/2004 16:42:51 - 1: Exception during Login: Access is denied. 21/07/2004 16:42:51 - 1: User Cts disconnected from cts-sourcecode.central.ctsnet.co.uk.


Do you have any suggestions what I should try to get this working?


Thanks

corey
Posts: 250
Joined: Tue Dec 30, 2003 10:13 am

Post by corey » Fri Jul 23, 2004 2:07 pm

I'm concerned about all of the "moving directories and messing about" that you refer to. What was wrong with your original configuration?

What happens if you just temporarily grant full access to the VSS folder to everyone, can SOS connect correctly then?
Corey Steffen
SourceGear LLC

CTSstuart

Post by CTSstuart » Mon Jul 26, 2004 3:16 am

Ok - so i decided to retrace my steps to give a more detailed reply of what i had done, and it works first time. :x

Post Reply