client hangs on login

blehenbauer · Post by **blehenbauer** » Thu Sep 23, 2004 12:19 pm

Hi -

It's me again from

Server Hangs - http://support.sourcegear.com/viewtopic.php?t=1526

After watching the discussions for a while I'm fairly certain the issue we are seeing has been described by others in the following topics:

SOS Hangs - http://support.sourcegear.com/viewtopic.php?t=1851
Cannot connect due to the endless logging in - http://support.sourcegear.com/viewtopic.php?t=1610

In effect, I had thought the server was hanging, but I am becoming more convinced that it is a client hang.

I have verbose logging enabled on the server, but my log file always looks like this when this occurs:

9/23/2004 1:24:27 PM - Connection accepted from 192.168.139.10:29917 on local address 192.168.139.19:8080, session id is 7.
9/23/2004 1:24:27 PM - 7: Enter Authorized()
9/23/2004 1:24:31 PM - 7: Unable to get hostname from address: 192.168.139.10
9/23/2004 1:24:31 PM - The requested name is valid, but no data of the requested type was found
9/23/2004 1:24:31 PM - 7: Connection from: 192.168.139.10 (192.168.139.10)
9/23/2004 1:24:31 PM - 7: Preparing to send the list of databases...
9/23/2004 1:24:31 PM - 7: Sending the challenge to the client.
9/23/2004 1:24:31 PM - 7: Sending the challenge message body to the client.
9/23/2004 1:24:31 PM - 7: Waiting for the client's response...
9/23/2004 1:24:31 PM - 7: Reviewing the client's response...
9/23/2004 1:24:31 PM - 7: Process the client's non-crypto login request.
9/23/2004 1:24:31 PM - 7: Enter Login()
9/23/2004 1:24:31 PM - 7: User 'lehenbauer' requesting to login to database 'E:\VSS\Development\srcsafe.ini'
9/23/2004 1:24:31 PM - 7: Client is speaking protocol version 2.0

More illuminating might be what we see on the client. I'm attaching a screenshot. In effect, the bottom window never reports a successful login while the other windows stay blank and do not show a project view or file list. The critical part of this is that once this occurs for one user no other SOS users can login successfully after that point.

I'm wondering if this is some kind of client error and not a server error. Is there any kind of logging I can enable on the client that might help to troubleshoot the issue?

- Bonnie

lbauer · Post by **lbauer** » Fri Sep 24, 2004 10:34 am

There is no client side logging in SOS Classic.

Yes, this is a client hang, but most likely it's because the client isn't getting information back from the SOS Server. On the server side, the login to the database never completes, so everything comes to a standstill.

This seems to point to some sort of problem communicating with VSS. I know you run Analyze on a regular basis, based on previous emails from you.

Perhaps this is a network or VSS automation component problem.

How many users do you have? How big is your VSS database? What type of hardware and system resources are available to the SOS Server?

What version of VSS is currently on the SOS Server machine?

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

On the SOS Server machine, do a search for ssapi.dll and let me know if you find multiple copies.

blehenbauer · Post by **blehenbauer** » Fri Sep 24, 2004 10:57 am

We have 6 users for this sourcesafe database

Our SS database size is 2.25 GB. We run analyze on a weekly basis with the -d, -f, -c flags.

The SS database and SOS server are on the same machine. It has four 2.4 Ghz processors and 1 GB of RAM.

I have two SSAPI DLL version 6.0.98.48 on the server, one in the VSS\Client\win32 directory and one in the VSS\Client\netsetup.x86\VSS\win32 directory.

Any red flags here?

blehenbauer · Post by **blehenbauer** » Mon Sep 27, 2004 11:50 am

Any other ideas? We're having a particularly frustrating time today and have had to restart the SOS service six times already.

If this is an issue logging in to sourcesafe, why would we be able to log into sourcesafe while this lockout is occurring?

lbauer · Post by **lbauer** » Mon Sep 27, 2004 2:50 pm

SOS communicates with the VSS database via the SourceSafe automation component. That's why Automation Component problems do not affect accessing VSS directly with a VSS client.

I think we've done this before, but check this KB article and verify that you have the correct registry setting on the SOS Server machine:

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

We've had reports of poor performance on dual processor machines.

Is it possible to install the SOS Server on a different, single processor machine? You can point the SOS Server to your database on the other machine.

This will help determine if there's a server configuration issue.

blehenbauer · Post by **blehenbauer** » Tue Sep 28, 2004 4:31 pm

I think we have it working now.

When I checked

HKEY_CLASSES_ROOT\CLSID\{783CD4E4-9D54-11CF-B8EE-00608CC9A71F}\InprocServer32\ThreadingModel

Just like the other dozen times I checked it, it was set correctly. On a lark I decided to see what the other settings in the registry were for that class ID, and I found:

HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{783CD4E4-9D54-11CF-B8EE-00608CC9A71F}\InprocServer32

... which I don't think we talked about before, but which WAS set to have the wrong threading model. So I updated that to not use apartment threading and restarted SOS, and we've been stable for a day.

Thanks for your patience working through this with me. It seems my HKLM settings were overriding the HKCR settings, and I didn't think to look at them.

Hopefully this will be able to help someone else with this same problem who hasn't checked the HKLM settings.

- Bonnie

lbauer · Post by **lbauer** » Wed Sep 29, 2004 4:09 pm

Interesting. We'll look into this. We've had a couple of reports of what appeared to be 6.0d concurrency crashes when threading mode appeared to be set correctly. Maybe this was the problem.