SoS 3.5.3 crashes on XP SP2 on client side

Martijn · Post by **Martijn** » Thu Mar 30, 2006 12:20 pm

Since I upgraded the client to XP SP2 I keep having this crash in the SoS client. Typical extract from the log file on the server:

Wed Mar 01 19:16:47 GMT+01:00 2006 - 192.168.18.1 (192.168.18.1) - Socket read failed
Wed Mar 01 19:16:47 GMT+01:00 2006 - 192.168.18.1 (192.168.18.1) - Connection reset by peer
Wed Mar 01 19:16:48 GMT+01:00 2006 - 192.168.18.1 (192.168.18.1) - User "Martijn" disconnected

This happens with almost all actions: get, checkin, checkout, undo-checkout. Which make SoS practically useless.
Get succeeds when files are not already present. Actually, the actions succeed on one file before the crash. After restarting in find my file got/checked-in/etc.

I read all similar items here, but none of the descriptions matched my problem. None of the solutions solved it.

lbauer · Post by **lbauer** » Thu Mar 30, 2006 3:19 pm

Wed Mar 01 19:16:47 GMT+01:00 2006 - 192.168.18.1 (192.168.18.1) - Socket read failed

This generally indicates some type of network error.
What version of SOS Client and Server are you using?

Check your firewall settings and anti-virus settings to see if anything might be blocking the connection between client and server or closing the connection prematurely.

Martijn · Post by **Martijn** » Fri Mar 31, 2006 4:20 am

Version is 3.5.3. The network has not been altered, XP firewall is off. Prior to my SP2 upgrade I've never had any problems. Maybe the error information of the crash is useful to you:

lbauer · Post by **lbauer** » Fri Mar 31, 2006 2:17 pm

Are there any contents in the b297_appcompat.txt file? When I downloaded it, it was empty.

When exactly does the client crash? Which command(s)/button(s) results in the crash? What steps reproduce the crash?

Does it appear that any communication with the server results in the crash?

Try deleting the client-side cache file(s), which are located at C:\Documents and Settings\user\Application Data\SourceGear\SOS\servers\server\databaseX.sos.

There may be additonal information in the server log. Enable verbose logging in the SOS Server Manager (on the server machine)->Debug tab, reproduce the error and email a copy of the log to Linda at SourceGear.com.

Martijn · Post by **Martijn** » Mon Apr 10, 2006 11:48 am

Hi Linda,

it took a while before I could try your suggestions. As it happens I'm at the office, so I could try SoS from within the company network. No network problems now. I used to do this before upgrading, because I prefer the SoS GUI to VSS's. But, alas, the same thing happens here. A multiple get generates this log.txt. Beforehand, I delete the local cache as you suggested.

The local files were already present. When I delete the local files before getting them with SoS, everything works fine.

lbauer · Post by **lbauer** » Mon Apr 10, 2006 12:51 pm

Mon Apr 10 19:17:09 GMT+02:00 2006 - 192.168.67.135 (192.168.67.135) -
Connection reset by peer

Not much in the log. This message just indicates that the client closed the connection (since it crashed).

I have not been able to reproduce a client crash of SOS 3.5.3 on Windows XP SP2. We haven't had other reports of this, so it appears specific to your machine. Unfortunately, this makes it difficult to resolve.

You said the get succeeds when files are already present. What is the status of those files? Blank? Renegade, Edited?

Is there anything in the Windows Event Viewer that corresponds to the crash?

Martijn · Post by **Martijn** » Tue Apr 11, 2006 9:30 am

The get succeeds when the files are not present.

The status does not affect the crash. Blank files need "Force file transfer". Renegade and Edited files need confirmation in a "lose changes?" dialog. The crash occurs after the get of a single file. This file then has the "Current" date/time, regardless of the settings for date/time.

In the Event Viewer there's an entry that corresponds to the crash, but nothing more. Is the fault address of any help?

lbauer · Post by **lbauer** » Fri Apr 14, 2006 8:40 am

We haven't had other reports of this, so it's hard to say why this is happening. It appears the crash happens when SOS tries to overwrite files in the working directory. Is there anything unusual about your working directories? Are they on the C:\ drive of your client machine? Is there enough disk space?