Several problems in command line client.

[szwart]

Server version 4.2 with encryption
Client version 4.2 with encryption.

We are using the command line client to retrieve source code over the internet.
We have found the following problems:

1) The command line crashes we the project in VSS is not found.

2) Both client (GUI and CLC) are missing VSS projects.
It seems that both clients are missing some projects that are available
in the VSS database. When the project is retrieve using the command
line client, the client crashes (problem 1).

3) The command line is not reliable over the internet.
When the CLC is used to retrieve a project, it gives the 'Net error during attempt to read headers. (RH2). Error: 0'
errors. See output below.

Command:
soscmd -command GetFileInfo -server wall04:8081 -name xxx -password xxx -alias Picasso_New -project $/common/make -verbose -file include.mak

Result:
SourceOffSite Command Line Client: 128 bit Encryption version 4.2
Connected to server wall04 at port 8081.

Matched alias 'Picasso_New' to database '\\xxxx\srcsafe.ini'

Received Secure Challenge from server
Successfully logged in.
Sending GetFileInfo Command to server.
Downloading project tree from server
Downloading project tree for $/
Net error during attempt to read headers. (RH2). Error: 0
Error: Server response = 0 UnRecognizedCommand
Net error during attempt to read headers. (RH2). Error: 0
Saving Tree status updates to file.
Closed connection to server wall04 at port 8081.

[szwart]

Forgot to meantion, that the test was done over a local network, which results in the same errors !.
So I think the connection is not the problem.

[Beth]

Could I have you give me the exact Automation Component Version? Also, when in the registry check to see what the threading model is that is located in the same area as the path to the ssapi.dll. It should be set to Both instead of Apartment.

What you are experiencing might be all caused by Project Rights. Could you temporarily disable that in VSS, then restart the SOS service, and see how things work for you and let me know?

[szwart]

The version of ssapi.dll is 6.0.81.69. The version of VSS is 6.0d Build 8163.
This seems to be an old version, we will update this.
The threading model is set to both.
Disabling project rights is not a option for us, due to legislation. We cannot
take the risk that released source code is changed.

[Beth]

The automation component version you have has had reports of problems with it. The two automation component versions that I've seen a lot of good luck with are 6.0.98.48 and and 6.0.96.40. The first one can be obtained from service pack 6 of Visual Studio 6. That is different from sp6 for VSS 6 though, so don't mix them up. The other version can be downloaded from here: SOS Concurrency crash in VSS 6.0c and earlier versions. I think you might like the first one I mentioned better, but you can certainly try both. Just make sure you backup the parent folder of the previous ssapi.dll first.

[davidllamas]

Hi.

I would like to test few solutions that are posted here (I'm also having several problems in command line client), but I'm not able to find ssapi.dll version 6.0.98.48 ... I've been searching in service pack 6 of Visual Studio 6, service pack for VSS 6, etc., but ... nothing.

Could somebody give me a hand and let me know where I could find it?.

I would like to know as well if that is the last version of ssapi.dll available ...

Many thanks in advance.

David

[Beth]

How I came up with that particular ssapi.dll was by just installing the service pack 6 for VS 6. The sp 6 for VSS 6 gives an entirely different update to the automation component and is not the one you want.

The last automation component for VSS 6 is not necessarily the best one for SOS 4.2, and I don't recall the full number at the moment, though it will be good for SOS 5.

If you still have problems getting it, you might give the other one I mentioned a try. The zip holds a text file that has the instructions.

[szwart]

We installed service pack 6 of Visual Studio. It seems that most of problems are gone.
Note. we needed to remove the cache's on the clients. These where not updated and therefore
most of the problems remained.

[Beth]

What are your residual problems?

[davidllamas]

How I came up with that particular ssapi.dll was by just installing the service pack 6 for VS 6. The sp 6 for VSS 6 gives an entirely different update to the automation component and is not the one you want.

The last automation component for VSS 6 is not necessarily the best one for SOS 4.2, and I don't recall the full number at the moment, though it will be good for SOS 5.

If you still have problems getting it, you might give the other one I mentioned a try. The zip holds a text file that has the instructions.

Beth,

ssapi.dll version 6.0.98.48 is not in service pack 6 for VS6 ... Check http://msdn.microsoft.com/en-gb/vstudio/aa718364.aspx ... I'm desesperate, because SOS server is taking the cpu to the limit and stays there until I reset the service ... Would be possible for you to send me (david@inchcolm.org) the ssapi.dll version 6.0.98.48?. I don't know what else to try ... I would much appreciate that.

Regards
David

[Beth]

David, give the 6.0.96.40 a try first. I posted a link to it above. Instructions for installing are included in the zip file.

Also, it sounds like you might be having a different problem. Can you provide more details on the issue you are having?

Which automation component do you have now? See this link for instructions to find your current version: Automation Component Version)