SourceOffSite crashes after Share Into operation

[seannerd]

I have SoS v5.0.3, Windows 7 64bit 8GB ram.

Using the SoS client, frequently, but not always, when I use "share into", it does the share operation, then crashes. This happened in 5.0.2 as well.

The error is: Unhandled exception at 0x012c603c in sos.exe: 0xC0000005: Access violation reading location 0x00000040.

Any thoughts?

[lbauer]

We haven't had other reports of this with SOS 5.x.

Which version of the VSS Automation Component is the SOS Server using?

To determine the SourceSafe Automation Component (ssapi.dll) version used by SOS Server, look at the System Info tab in the SOS Server Manager.

The SOS Server Manager is in the SOS Server directory on the SOS Server machine, usually, C:\Program Files\SourceGear\SourceOffSite 5 Server.

Also, are there any errors in the SOS Server log that correspond to the failure? The SOS Server log is called log.txt and is in the SOS Server directory on the SOS Server machine.

[seannerd]

Thanks, Linda -

SSAPI.DLL = version 6.0.81.69

In the log I can only spot two different errors around the time I was doing this work:

2010-11-05 15:27:34,550 - 626: ProtocolMessage.ParseStream() - Socket error reading protocol message number (Read 0 of 1 bytes). Exception: Socket Exception: An existing connection was forcibly closed by the remote host (WSA Error: 10054. Exception: An existing connection was forcibly closed by the remote host

and:

2010-11-05 06:49:29,523 - 596: ProtocolMessage.ParseStream() - Socket error reading protocol message number (Read 0 of 1 bytes). Exception: Exception: CONNECTION CLOSED
2010-11-05 06:49:29,523 - 596: ProtocolMessage.ParseStream() Get ProtocolMessage ID Exception: CONNECTION CLOSED BytesRead 0 of 10 (allowed).
2010-11-05 06:49:29,523 - 596: Connection Closed: CONNECTION CLOSED
2010-11-05 06:49:29,555 - 596: VSS database closed for the session id 596.


Thanks again, Linda.

- Sean

[lbauer]

You've got a fairly old version of VSS 6. It's one that doesn't work very well with SOS.

SOS 5.0 requires either 6.0d (build 98.48) or VSS 2005 Update version.
http://www.sourcegear.com/sos/documentation/sysreq.html

Note that only the VSS client on the SOS Server machine needs to be this version. SOS Server communicates with the SourceSafe database through the automation component provided by the client on the server machine.

[seannerd]

OK, Linda - we updated and the problem remains. : (

SSAPI.DLL is now Version: 8.0.50727.1551

The same type of errors are in the log as before. I think the problem is actually worse now. Before, it would make it through all the files in my "Share Into" operation and crash at the end. Now, it crashes before completion, and it takes several tries to make it through all the files in a particular directory.

We even use the VSS Analyze function with repair inconsistencies and restarted the service - still no change.

Do you have any other ideas?

Thanks.

- Sean

[lbauer]

Does this crash happen every time, or only on certain "share into" operations?

How many projects/files are you sharing -- does it make a difference if it's a lot or just a few?

We'd like to see a copy of your SOS log.

The SOS Server log is called log.txt and is in the SOS Server directory on the SOS Server machine.

Send the log zipped up to support at sourcegear.com, Attn: Linda. Please include a link to this forum post.

[seannerd]

It turns out that there was something up with my directory structure (my local working folder). I renamed my working folder, and did a "get latest" of the whole tree for all projects. After that, I was able to perform all operations consistently and without error.

Weird - I wonder what it was about the local files I had.

Anyway - thank you for your time, Linda, and sorry I wasted it with the thought of other possibilities.

- Sean

[lbauer]

No problem; glad things are working for you now.