difficulties connecting in SOS v4

Mark B · Post by **Mark B** » Tue Apr 06, 2004 3:39 pm

Hi,

I am running the v4 client against the v4 server. Every once in a while (perhaps every 6th time I try), when I open a large solution in VS7, the VS IDE hangs while initializing. If I open the SOS client at this time, I find that the client hangs with the message "Logging in..." in the status pane.

The server log file contains quite a few error entries; excerpts follow:
4/6/2004 2:30:29 PM - 18: Exception: Index was outside the bounds of the array.
4/6/2004 2:41:30 PM - Connection accepted from x.x.x.x:xxxx, session id is 20.
4/6/2004 2:43:41 PM - Connection accepted from x.x.x.x:xxxx, session id is 21.
4/6/2004 2:43:56 PM - 21: Exception: Index was outside the bounds of the array.
4/6/2004 2:43:56 PM - Connection accepted from x.x.x.x:xxxx, session id is 22.
4/6/2004 3:41:49 PM - 20: Exception: Index was outside the bounds of the array.
4/6/2004 4:30:29 PM - 16: Exception: Index was outside the bounds of the array.
4/6/2004 4:46:28 PM - Connection accepted from x.x.x.x:xxxx, session id is 23.
4/6/2004 4:46:35 PM - 23: Exception: Index was outside the bounds of the array.
4/6/2004 4:46:35 PM - Connection accepted from x.x.x.x:xxxx, session id is 24.

Anyone have a hint as to whats going on here?

Server is Win2k SP3; clients are XP SP1

Thx,

Mark B

corey · Post by **corey** » Wed Apr 07, 2004 1:49 pm

Mark,

First check out the following note and see if it applies to you:

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

If not, email me your entire log.txt file from your server.

Guest · Post by **Guest** » Thu Apr 08, 2004 7:50 am

Cory,

The "timeout Idle" option is not enabled. Our server log is attached.

Note that we also saw another problem - perhaps unrelated. A user somehow got in the predicament that their cached password was wrong. Ther enabled the "connect automatically" and "remember password" options and successfully logged in (so the correct password should have been stored).

But on a subsequent invocation of Visual Studio 7, they got a series of "invalid password" errors (had to kill the VS7 process). I corrected the issue by having them open SOS v4 client, disable the "make SOS your default SCC", close client, open VS7, deal with its confusion (VSS not installed on their desktop), close VSS, open SOS client, make SOS default SCC, close client, open VS7, all is well.

FYI, this is the second time I replied to your response - the first response I posted apparently disappeared into the ether.

Thanks,

MarkB

corey · Post by **corey** » Thu Apr 08, 2004 2:42 pm

I'm not sure what all of the "Exception: Index was outside the bounds of the array" errors are from. Can you enable debug level logging, restart the server, and then send me the new log file once the error occurs again? Maybe the extra logging will provide more info so we can figure out what's going on. Here's how to enable debug logging:

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

Also, when the IDE or GUI Client hangs, how long do you let it go before you kill the process?

Guest · Post by **Guest** » Mon Apr 19, 2004 7:12 am

The "verbose" log is attached. When the hang occurs, I have waited up to 10 minutes before killing the process. Fortunately, right now it does not seem to be hanging as often as it did (perhaps once every other day now versus several times per day previously).

corey · Post by **corey** » Mon Apr 19, 2004 3:42 pm

With the latest log file you posted, do you know approx when the last hang occurred?

Guest · Post by **Guest** » Mon Apr 19, 2004 7:50 pm

Funny you should ask - SOS hung immediately *after* i sent the log

Also I *just now* had to restart the SOS service. So I have attached another log, and here I can tell you exactly where the problem occured.

Session 38 is a user connecting through VS7; Session 39 is me connecting through the SOS client. They both connect, but do not log in - this is where it hangs.

The last entry in the log before I bounced the service is line 3907 of the file:
4/19/2004 9:27:46 PM - 39: Open the database.

The next line in the log is:
4/19/2004 9:30:13 PM - Stopping the service.

So you can see I waited about 2.5 minutes to log in before bouncing the service.

I hope this helps you track down the problem.

Thanks

corey · Post by **corey** » Tue Apr 20, 2004 3:41 pm

Thanks. We'll look at your latest log and see what we can find out.

corey · Post by **corey** » Mon Apr 26, 2004 7:50 am

Mark,

What version of SourceSafe do you have installed on the SOS Server machine? Can you give me the exact version number of the ssapi.dll file on that machine?

Guest · Post by **Guest** » Mon Apr 26, 2004 8:47 pm

Cory,

The SSAPI.DLL version is "6.0.98.48" (VSS v6.0d)

I have seen the other post about changing the "Threading Model" registry value from "Apartment" to "Both". I did this, restarted the SOS v4 service, and I have not seen a hang since. This may not be a sure cure, as the problem was intermittent.

Also, I have one remote user (gregg) who keeps seeing crashes in VS7 (.NET). He starts typing in a module, VS prompts him to check out the file, he clicks OK, and then VS crashes. I have never experienced the crash, but we were both seeing the hang (perhaps when we simultaneously accessed SOS).

Any thoughts on the crashing?

Mark

corey · Post by **corey** » Tue Apr 27, 2004 7:08 am

Anonymous wrote:Cory,

The SSAPI.DLL version is "6.0.98.48" (VSS v6.0d)

I have seen the other post about changing the "Threading Model" registry value from "Apartment" to "Both". I did this, restarted the SOS v4 service, and I have not seen a hang since. This may not be a sure cure, as the problem was intermittent.

I'm guessing the threading model was the problem. I should have asked you about that at the start. Sorry.

Anonymous wrote: Also, I have one remote user (gregg) who keeps seeing crashes in VS7 (.NET). He starts typing in a module, VS prompts him to check out the file, he clicks OK, and then VS crashes. I have never experienced the crash, but we were both seeing the hang (perhaps when we simultaneously accessed SOS).

Any thoughts on the crashing?

Mark

Is this always happening with one particular file or is he unable to check out any files without having VS.NET crash?

Guest · Post by **Guest** » Thu Apr 29, 2004 2:48 pm

The user says that it does not always occur on every file, nor is it always the same file. I will try to snag a snapshot of the log file the next time I am told it has happened.

Mark · Post by **Mark** » Mon May 10, 2004 2:58 pm

OK, the following log entries aurround a Vsiual Studio crash when attempting to un-checkout a file at 2:19 pm:

5/10/2004 2:12:19 PM - 8: Received message number 106.
5/10/2004 2:12:19 PM - 8: Version information obtained for $/Inform/MethodLib/PlotStack.vb
5/10/2004 2:13:44 PM - 8: Received message number 106.
5/10/2004 2:13:44 PM - 8: Version information obtained for $/Inform/MethodLib/TracePlot.vb
5/10/2004 2:18:26 PM - 8: Received message number 105.
5/10/2004 2:18:26 PM - 8: GetFile() file=PlotStack.vb
5/10/2004 2:18:26 PM - 8: Getting version information: $/Inform/MethodLib/PlotStack.vb
5/10/2004 2:19:02 PM - 8: Received message number 107.
5/10/2004 2:19:22 PM - 8: Exception: An existing connection was forcibly closed by the remote host
5/10/2004 2:19:22 PM - 8: Error processing client request: at System.Net.Sockets.Socket.Receive(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags)
at ClassicService.ProtocolMessage.ParseStream(Socket socket, Crypto crypto)
at ClassicService.Client.GetMessage()
5/10/2004 2:19:22 PM - 8: User gregg disconnected from COLBY.
5/10/2004 2:33:02 PM - Connection accepted from 10.0.1.88:2211, session id is 9.
5/10/2004 2:33:02 PM - 9: Connection from: COLBY (10.0.1.88)
5/10/2004 2:33:02 PM - 9: Preparing to send the list of databases...
5/10/2004 2:33:02 PM - 9: Sending the challenge to the client.
5/10/2004 2:33:02 PM - 9: Sending the challenge message body to the client.

our SOS configuration follows:
5/9/2004 8:22:57 AM - ****************************************************
5/9/2004 8:22:57 AM - SourceOffSite Server 4.0.0 Professional - With Cryptography

5/9/2004 8:22:57 AM - CurrentCulture is en-US.

5/9/2004 8:23:05 AM - Server Information
5/9/2004 8:23:05 AM - Operating System: Microsoft Windows 2000 Server
5/9/2004 8:23:05 AM - Service Pack: 4.0
5/9/2004 8:23:05 AM - OS Version: 5.0.2195
5/9/2004 8:23:05 AM - Locale: Ox0409
5/9/2004 8:23:05 AM - OSLanguage: 1033
5/9/2004 8:23:05 AM - Total Physical Memory: 511.54 MB
5/9/2004 8:23:05 AM - Time Zone: (GMT-05:00) Eastern Time (US & Canada)
5/9/2004 8:23:05 AM -
5/9/2004 8:23:05 AM - SSAPI.dll Information:
5/9/2004 8:23:05 AM - Location: file:///E:/Utils/SourceOffSiteServer/Interop.SourceSafeTypeLib.DLL
5/9/2004 8:23:05 AM - DisplayName: Interop.SourceSafeTypeLib, Version=5.1.0.0, Culture=neutral, PublicKeyToken=null
5/9/2004 8:23:05 AM -
5/9/2004 8:23:05 AM - Started at 5/9/2004 8:23:05 AM

5/9/2004 8:23:06 AM - General logging level is Verbose. Method logging is Disabled.

5/9/2004 8:23:06 AM - Number of licenses configured: 2

BTW, I often see this message in the log:
5/10/2004 2:33:02 PM - 9: Compression is NOT on.

but server manager says that compression IS on - which is it ??

Thanks,

Mark

corey · Post by **corey** » Tue May 11, 2004 12:18 pm

The server log doesn't show any errors, so this appears to be a problem only on the client-side. Did VS.NET crash before the undo checkout finished or not? Had the file been modified before the user attempted the undo checkout?

The compression entry in the log file is a known bug. The log file always shows it turned off even when its on. We'll be fixing this in the next release.

Mark · Post by **Mark** » Tue May 11, 2004 2:44 pm

The user said that they though that the file was successfully un-checked out. The file was modified.

so this does not indicate an error?

5/10/2004 2:19:22 PM - 8: Exception: An existing connection was forcibly closed by the remote host
5/10/2004 2:19:22 PM - 8: Error processing client request: at System.Net.Sockets.Socket.Receive(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags)
at ClassicService.ProtocolMessage.ParseStream(Socket socket, Crypto crypto)
at ClassicService.Client.GetMessage()
5/10/2004 2:19:22 PM - 8: User gregg disconnected from COLBY.

I guess "the client" at this point is the part of SOS client that VS interracts with, referred to as the "remote host" in the log.

That right?