Problems connecting to server

Chris Austin · Post by **Chris Austin** » Tue Oct 12, 2004 4:43 am

I have a 1 user license installed on the server (4.0.2) and it very frequently I get the problem of the client not being able to connect. Restarting the service always fixes this, but it is happening several times a day. Here is the relevent extract from the log:

12/10/2004 11:40:03 - Connection accepted from 217.42.141.150:3899 on local address 192.168.0.2:4445, session id is 6.
12/10/2004 11:40:03 - 6: Enter Authorized()
12/10/2004 11:40:03 - 6: Connection from: host217-42-141-150.range217-42.btcentralplus.com (217.42.141.150)
12/10/2004 11:40:03 - 6: Preparing to send the list of databases...
12/10/2004 11:40:03 - 6: Sending the challenge to the client.
12/10/2004 11:40:03 - 6: Sending the challenge message body to the client.
12/10/2004 11:40:03 - 6: Waiting for the client's response...
12/10/2004 11:40:07 - 6: Reviewing the client's response...
12/10/2004 11:40:07 - 6: Process the client's non-crypto login request.
12/10/2004 11:40:07 - 6: Enter Login()
12/10/2004 11:40:07 - 6: User 'Gerhard' requesting to login to database 'C:\Documents and Settings\Chris\My Documents\Capgen\VSS\srcsafe.ini'
12/10/2004 11:40:07 - 6: Client is speaking protocol version 2.0

12/10/2004 11:40:07 - 6: Exception during Login: The handle is invalid.
12/10/2004 11:40:07 - 6: The handle is invalid.
12/10/2004 11:40:07 - 6: Exit Login()
12/10/2004 11:40:07 - 6: Enter KillConnection()
12/10/2004 11:40:07 - 6: User Gerhard disconnected from host217-42-141-150.range217-42.btcentralplus.com.
12/10/2004 11:40:07 - 6 - Exit KillConnection()

lbauer · Post by **lbauer** » Wed Oct 13, 2004 3:01 pm

It sounds like there's a problem with the SOS Server.

Check this KB article and see if you have VSS 6.0d on the SOS Server machine. This version of VSS does not work very well with SOS because of the change in the threading model.

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

Chris Austin · Post by **Chris Austin** » Fri Oct 15, 2004 2:44 am

Thank you for your help. I have made the change suggested by this post and will see whether this helps,

Chris

Andriy · Post by **Andriy** » Sun Nov 14, 2004 6:16 am

I have the same random problems with login (the same work environment with 1 user), made suggested changes (http://support.sourcegear.com/viewtopic.php?t=10) and now server consumes 100% of CPU after user connected. It does not depend on actions performed by user, SosService.exe consumes all the CPU even after user disconnected, only server restart helps. When threading model not changed, service consumes very small amount of CPU time. VSS databases are analyzed and fixed, or empty - does not matter. Antivirus software does not check VSS database folders and SOS temporary folder. I think antivirus is not a reason at all because of TaskManager points to SosService.exe. Any suggestions?

Thanks,
Andriy

lbauer · Post by **lbauer** » Sun Nov 14, 2004 1:10 pm

Put SOS Server logging into Verbose mode:

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

Do an operation that reproduces the 100% CPU usage.

Then I'd like you to undo the registry change -- put threading back to Apartment, and repeat the operation.

Then send me a copy of the log.txt file from the SOS Server directory.

Email it to linda at SourceGear.com. Please reference this forum post in your email.

targetboy · Post by **targetboy** » Thu Nov 18, 2004 7:38 am

hi there,

i just installed SourceSafe c version on my host machine and the source server and client.
i installed the sosservice and its running. on my second machine i just installed sourcesafe c -> netsetup and the source client. when i know try to connect to the server per dyndns.org or direct ip it hangs in first line "connecting to....." no more action

i am totaly new to this source safe stuff and i would be very happy if someone can help me setting up that thing.
i have a router but i opened the port 8080 tcp/udp......

thx very much for ur help!!!

Marcel

targetboy · Post by **targetboy** » Thu Nov 18, 2004 7:47 am

sorry forgot: after a while i get a message : "server closed connection"
attached the logfile!

.....Marcel

lbauer · Post by **lbauer** » Thu Nov 18, 2004 12:17 pm

The log file shows no connection attempts, so the SOS Server isn't even seeing anything from the client. Something is blocking the connection.

Try the telnet test with this command:

telnet marcel.<yourdomain.com> 8080

Is the connection made? If not, the SOS Client can't connect, either.