SourceOffSite client hangs when logging in

GeeeTeee · Post by **GeeeTeee** » Thu Jul 06, 2006 10:26 am

Hi,

I am suffering from frequent hangs whenever I attempt a second connection from the same PC.

I primarily use VS2005. This logs in to SourceSafe / SourceOffSite without any problem. If I then try to run Visual Studio 6, it hangs on "Initializing Source Code Control Project", or if I try the SourceOffSite Client, it hangs on "Logging In".

The server is running on Microsoft Windows Server 2003, SSAPI.DLL on the Server is version 8.0.50727.42, and in the registry, threading model is set to Both.

Any ideas please? When I say the client hangs, I've left it over a weekend on some occasions, an this time it's had 4 days, so its more than a slow response!!

Thanks.

Post by **Tonya** » Thu Jul 06, 2006 2:54 pm

Hello,

It is possible that you may be experiencing a known problem in regards to a concurrency crash issue with the VSS API.

See this KB article regarding server hangs and possible fixes:

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

Thanks,

Tonya Nunn
SourceGear

GeeeTeee · Post by **GeeeTeee** » Fri Jul 07, 2006 2:26 am

Hi Tonya,

Thanks for that, but I've already checked through these 3 options:

1) SSAPI.DLL
We have SourceSafe Version 2005 installed (Not 6.0d as in my previous post), and the SSAPI.DLL is version 8.0.50727.42. The registry entry has been applied though, so it is currently set to 'Both'.

2) Only applies on versions prior to the 6.0c hotfix

3) Only applies to SOS Server 3.5.x - we're using 4.1.2

One thing I have noticed - today I have 3 sessions in to the server from my 1 PC - One through VS .NET 2005, one through VS6, one through SourceOffSite Client, and everything is fine. This is using a remote PC over Checkpoint firewall.

Yesterday I was suffering problems trying to get a second connection from SourceOffSite client when I already had a session extablished from VS2005. This PC was on the same network as the server.

Does this help?

Thanks,

George.

Post by **Tonya** » Fri Jul 07, 2006 8:04 am

Hi George,

Thanks for the details. So SOS appears to be working correctly for you today from a different pc that's also on the same network as the one that you were having problems with? Would you mind to send me your SOS log.txt file that's located on the SOS Server machine? You can e-mail it to me at tonya@sourcegear.com.

Hopefully the log file will indicate any problems that the server is experiencing when it hangs.

Thanks,

Tonya

GeeeTeee · Post by **GeeeTeee** » Fri Jul 07, 2006 8:16 am

I've sent you the log file as requested.

The two PCs are actually on separate networks. The PC I'm using successfully today connects to the server network using Checkpoint VPN over ADSL, whereas the PC I was using yesterday is actually on the same network as the server.

The log file is also shown below for anyone who might have a similar problem:

06/07/2006 09:48:54 - Connection accepted from 198.198.198.163:1131 on local address 198.198.198.247:8080, session id is 169.
06/07/2006 16:06:54 - Connection accepted from 198.198.198.163:1976 on local address 198.198.198.247:8080, session id is 170.
06/07/2006 16:43:13 - 170: Exception: An existing connection was forcibly closed by the remote host
06/07/2006 17:01:55 - Connection accepted from 198.198.198.163:2258 on local address 198.198.198.247:8080, session id is 171.
06/07/2006 17:03:59 - Stopping the service.
06/07/2006 17:03:59 - 5: Exception: A blocking operation was interrupted by a call to WSACancelBlockingCall
06/07/2006 17:03:59 - 8: Exception: A blocking operation was interrupted by a call to WSACancelBlockingCall
06/07/2006 17:03:59 - 9: Exception: A blocking operation was interrupted by a call to WSACancelBlockingCall
06/07/2006 17:03:59 - 12: Exception: A blocking operation was interrupted by a call to WSACancelBlockingCall
06/07/2006 17:04:00 - 14: Exception: A blocking operation was interrupted by a call to WSACancelBlockingCall
06/07/2006 17:04:00 - 15: Exception: A blocking operation was interrupted by a call to WSACancelBlockingCall
06/07/2006 17:04:00 - 17: Exception: A blocking operation was interrupted by a call to WSACancelBlockingCall
06/07/2006 17:04:00 - Exception in Receive(): A blocking operation was interrupted by a call to WSACancelBlockingCall
06/07/2006 17:04:00 - 06/07/2006 17:04:00 - Server Exception (400): OPERATION_FAILED
06/07/2006 17:04:00 - 18: Server Error: 400
06/07/2006 17:04:00 - 18: Error removing user temp folder 'C:\Program Files\SourceOffSite Server\temp\George.Thackray632774269970389923'.
06/07/2006 17:04:00 - The process cannot access the file "SQLDefs.txt.gz" because it is being used by another process.
06/07/2006 17:04:00 - 19: Error removing user temp folder 'C:\Program Files\SourceOffSite Server\temp\George.Thackray632774291095107331'.
06/07/2006 17:04:00 - The process cannot access the file "SQLDefs.txt.gz" because it is being used by another process.
06/07/2006 17:04:00 - Exception in Receive(): A blocking operation was interrupted by a call to WSACancelBlockingCall
06/07/2006 17:04:00 - 06/07/2006 17:04:00 - Server Exception (400): OPERATION_FAILED
06/07/2006 17:04:00 - 19: Server Error: 400
06/07/2006 17:04:00 - Exception in Receive(): A blocking operation was interrupted by a call to WSACancelBlockingCall
06/07/2006 17:04:00 - 06/07/2006 17:04:00 - Server Exception (400): OPERATION_FAILED
06/07/2006 17:04:00 - 20: Server Error: 400
06/07/2006 17:04:00 - 20: Error removing user temp folder 'C:\Program Files\SourceOffSite Server\temp\George.Thackray632774292474222787'.
06/07/2006 17:04:00 - The process cannot access the file "SQLDefs.txt.gz" because it is being used by another process.
06/07/2006 17:04:00 - 28: Exception: A blocking operation was interrupted by a call to WSACancelBlockingCall
06/07/2006 17:04:00 - 30: Exception: A blocking operation was interrupted by a call to WSACancelBlockingCall
06/07/2006 17:04:00 - 39: Exception: A blocking operation was interrupted by a call to WSACancelBlockingCall
06/07/2006 17:04:00 - 42: Exception: A blocking operation was interrupted by a call to WSACancelBlockingCall
06/07/2006 17:04:00 - 44: Exception: A blocking operation was interrupted by a call to WSACancelBlockingCall
06/07/2006 17:04:00 - 50: Exception: A blocking operation was interrupted by a call to WSACancelBlockingCall
06/07/2006 17:04:00 - 47: Exception: A blocking operation was interrupted by a call to WSACancelBlockingCall
06/07/2006 17:04:00 - 52: Exception: A blocking operation was interrupted by a call to WSACancelBlockingCall
06/07/2006 17:04:00 - 53: Exception: A blocking operation was interrupted by a call to WSACancelBlockingCall
06/07/2006 17:04:00 - 77: Exception: A blocking operation was interrupted by a call to WSACancelBlockingCall
06/07/2006 17:04:00 - 54: Exception: A blocking operation was interrupted by a call to WSACancelBlockingCall
06/07/2006 17:04:00 - 91: Exception: A blocking operation was interrupted by a call to WSACancelBlockingCall
06/07/2006 17:04:00 - 92: Exception: A blocking operation was interrupted by a call to WSACancelBlockingCall
06/07/2006 17:04:00 - 101: Exception: A blocking operation was interrupted by a call to WSACancelBlockingCall
06/07/2006 17:04:00 - 102: Exception: A blocking operation was interrupted by a call to WSACancelBlockingCall
06/07/2006 17:04:00 - 131: Exception: A blocking operation was interrupted by a call to WSACancelBlockingCall
06/07/2006 17:04:00 - 133: Exception: A blocking operation was interrupted by a call to WSACancelBlockingCall
06/07/2006 17:04:00 - 132: Exception: A blocking operation was interrupted by a call to WSACancelBlockingCall
06/07/2006 17:04:00 - 136: Exception: A blocking operation was interrupted by a call to WSACancelBlockingCall
06/07/2006 17:04:00 - 137: Exception: A blocking operation was interrupted by a call to WSACancelBlockingCall
06/07/2006 17:04:00 - 138: Exception: A blocking operation was interrupted by a call to WSACancelBlockingCall
06/07/2006 17:04:00 - 139: Exception: A blocking operation was interrupted by a call to WSACancelBlockingCall
06/07/2006 17:04:00 - 146: Exception: A blocking operation was interrupted by a call to WSACancelBlockingCall
06/07/2006 17:04:00 - 147: Exception: A blocking operation was interrupted by a call to WSACancelBlockingCall
06/07/2006 17:04:00 - 145: Exception: A blocking operation was interrupted by a call to WSACancelBlockingCall
06/07/2006 17:04:00 - 155: Exception: A blocking operation was interrupted by a call to WSACancelBlockingCall
06/07/2006 17:04:01 - 160: Exception: A blocking operation was interrupted by a call to WSACancelBlockingCall
06/07/2006 17:04:01 - 169: Exception: A blocking operation was interrupted by a call to WSACancelBlockingCall
06/07/2006 17:04:01 - 161: Exception: A blocking operation was interrupted by a call to WSACancelBlockingCall
06/07/2006 17:04:01 - 171: Exception: A blocking operation was interrupted by a call to WSACancelBlockingCall
06/07/2006 17:04:01 - 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()
06/07/2006 17:04:05 - ****************************************************
06/07/2006 17:04:05 - SourceOffSite Server 4.1.2 Professional - With Cryptography

06/07/2006 17:04:05 - CurrentCulture is en-GB.

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

06/07/2006 17:04:06 - General logging level is Error. Method logging is Disabled.

06/07/2006 17:04:06 - Number of licenses configured: 1
06/07/2006 17:04:06 - SourceSafe Initialization file(s) located at:
06/07/2006 17:04:06 - C:\Program Files\Microsoft Visual SourceSafe\Source Code Database\srcsafe.ini

06/07/2006 17:04:06 - pslfp is attempting to listen for connections on secure port 8081
06/07/2006 17:04:06 - pslfp is attempting to listen for connections on unsecure port 8080

06/07/2006 17:04:06 - Waiting for a connection....secure = True
06/07/2006 17:04:06 - Waiting for a connection....secure = False
06/07/2006 17:04:21 - Connection accepted from 198.198.198.163:2266 on local address 198.198.198.247:8080, session id is 1.
06/07/2006 17:08:37 - 1: Exception: An existing connection was forcibly closed by the remote host
06/07/2006 17:22:42 - Connection accepted from 198.198.198.163:2448 on local address 198.198.198.247:8080, session id is 2.
07/07/2006 09:05:50 - Connection accepted from 192.168.72.5:1150 on local address 198.198.198.247:8080, session id is 3.
07/07/2006 09:05:55 - 3: Unable to get hostname from address: 192.168.72.5
07/07/2006 09:07:23 - Connection accepted from 192.168.72.5:1153 on local address 198.198.198.247:8080, session id is 4.
07/07/2006 09:07:28 - 4: Unable to get hostname from address: 192.168.72.5
07/07/2006 09:10:10 - Connection accepted from 192.168.72.5:1157 on local address 198.198.198.247:8080, session id is 5.
07/07/2006 09:10:15 - 5: Unable to get hostname from address: 192.168.72.5

Post by **Tonya** » Fri Jul 07, 2006 8:39 am

Can you change your logging level from 1 to 4 and enable Method logging?

Directions to apply these changes can be found here:

http://support.sourcegear.com/viewtopic ... ing+enable

Thanks,

Tonya

GeeeTeee · Post by **GeeeTeee** » Fri Jul 07, 2006 9:57 am

Hi. OK, I've attached the latest log.

I changed the logging level to 4, enabled Method Logging, and restarted SOS Server.

At the moment, Visual Studio 6 is successfully logged in. Visual Studio 2005 logged in OK, but is now hung. SourceOffSite Client has 3 lines in the bottom window:

Connecting to pslfp:8080
Logging in...
Login Successful

It's been hung at that for the last 70 minutes - the egg timer mouse cursor is showing.

Thanks.

GeeeTeee · Post by **GeeeTeee** » Fri Jul 07, 2006 3:27 pm

Hi,

A bit more information.

As the SourceOffSite client has now been hung for 6 hours, I closed down Visual Studio 6 (The only one of the three apps to successfuly attach).

As soon as I did this, the SourceOffSite client gave an error message (See Error1.jpg), then a few seconds after clicking OK, a second error appeared (See Error2.jpg).

After clicking OK again, I reconnected to the server, and SourceOffSite client was OK, then Visual Studio 2005 unfroze.

Hope that helps!

George.

Post by **Tonya** » Fri Jul 07, 2006 3:46 pm

Thanks for the additional information. I have a test scenario for you to try if you don't mind. The next time that any of your clients hang, could you go to a different machine and log into the SOS Server? If you can successfully log in, perform any kind of operation to confirm that the SOS Server is still running.

Thanks,

Tonya

GeeeTeee · Post by **GeeeTeee** » Mon Jul 10, 2006 9:12 am

Tonya wrote:Thanks for the additional information. I have a test scenario for you to try if you don't mind. The next time that any of your clients hang, could you go to a different machine and log into the SOS Server? If you can successfully log in, perform any kind of operation to confirm that the SOS Server is still running.

No problem, I'll do that next time it occurs.

GeeeTeee · Post by **GeeeTeee** » Tue Aug 07, 2007 2:11 am

Tonya wrote:Thanks for the additional information. I have a test scenario for you to try if you don't mind. The next time that any of your clients hang, could you go to a different machine and log into the SOS Server? If you can successfully log in, perform any kind of operation to confirm that the SOS Server is still running.

Thanks,

Tonya

I know it's been a long time since I wrote on this thread, but I've been on a project for the last year which didn't use SourceGear. I'm back now, and the problem still persists. Today, on one machine, I have Visual Studio 6 running. It is working perfectly well. I then tried using SourceOffSite client, and that just hangs. I forced it to close, retried, and it still hangs. I then went back to Visual Studio 6, tried to check in a file, and got the message 'The connection to the server is closed, do you want to reconnect'. I answered 'Yes', and Visual Studio 6 reconnected OK, and the file checked in OK. SourceOffSite client is still hanging. This would seem to prove that the server is still running. Any ideas what might be wrong? I am communicating with our server via Checkpoint VPN.

Terence · Post by **Terence** » Tue Aug 07, 2007 7:53 am

I think the changes made in the 4.2 release will address this issue. If upgrading to 4.2 is an option for you, can you try that and let us know?

GeeeTeee · Post by **GeeeTeee** » Thu Aug 09, 2007 9:27 am

I've installed V4.2 of both the client and the server, and on first impressions, it certainly seems to have made a difference. I'll keep an eye on things.

Thanks.

Terence · Post by **Terence** » Thu Aug 09, 2007 10:06 am

You're welcome.

jonshin · Post by **jonshin** » Sun May 18, 2008 9:14 am

This problem is occurring for me after it had been working for a while. The SOS client freezes at "Logging in..." and VS2005 just hangs. After a while I get the same "Server closed connection" server error dialog as above.

Vista, SOS 4.1.2, VSS local version: 8.0.50727.42

Why would it all of sudden stop working?

As suggested in another thread I tried to connect to your test server, sos.sourceoffsite.com:8888, daffy, duck without any problems.

SourceGear Support

SourceOffSite client hangs when logging in

SourceOffSite client hangs when logging in

Hanging when logging in