soscmd getProject command fails

If you are having a problem using SourceOffSite, post a message here.

Moderator: SourceGear

Post Reply
Chris Rowland
Posts: 5
Joined: Thu Jun 17, 2010 3:13 am

soscmd getProject command fails

Post by Chris Rowland » Mon Jul 05, 2010 5:35 am

Hi,

I'm trying to get the soscmd Getproject command to work and I'm getting Error 400 Operation failed.

the command line is:
C:\Program Files\SourceGear\SOS4_2\soscmd.exe -soshome "C:\Documents and Settings\crowland\Application Data\SourceGear\SOS" -command GetProject -server SOSserver:8080 -name user -password "password" -alias "Issue18x" -project "$\i4dev\Test\testproj" -workdir "C:\Inca18x\i4dev\Test\testproj"

It's version 4.2 of soscmd, AIUI that's the latest one.

The server log shows:

Code: Select all

2010-07-01 18:05:22,772 - ****************************************************
2010-07-01 18:05:22,772 - SourceOffSite Server 5.0.3.324 Professional - With Cryptography
2010-07-01 18:05:22,772 - 
2010-07-01 18:05:22,772 - CurrentCulture is en-GB.
2010-07-01 18:05:22,772 - 
2010-07-01 18:05:23,053 - Server Information
2010-07-01 18:05:23,053 -     Operating System: Microsoft Windows XP Professional
2010-07-01 18:05:23,053 -     Service Pack: 3.0
2010-07-01 18:05:23,053 -     OS Version: 5.1.2600
2010-07-01 18:05:23,053 -     Locale: Ox0809
2010-07-01 18:05:23,053 -     OSLanguage: 1033
2010-07-01 18:05:23,053 -     Total Physical Memory: 503.35 MB
2010-07-01 18:05:23,053 -     Time Zone: (GMT) Greenwich Mean Time : Dublin, Edinburgh, Lisbon, London
2010-07-01 18:05:23,053 - 
2010-07-01 18:05:23,053 - SSAPI.dll Information:
2010-07-01 18:05:23,053 -     Version: C:\Program Files\Microsoft Visual Studio\Common\VSS\win32\SSAPI.DLL (06.00.31222)
2010-07-01 18:05:23,053 -     Threading Model: Both
2010-07-01 18:05:23,053 - 
2010-07-01 18:05:23,053 - Logging at level Error
2010-07-01 18:05:23,053 - 
2010-07-01 18:05:23,053 - 
2010-07-01 18:05:23,069 - Number of licenses configured: 10
2010-07-01 18:05:23,069 - 
2010-07-01 18:05:23,084 - SourceSafe Initialization file(s) located at:
2010-07-01 18:05:23,084 - \\ukoiak3s02\data\Masters\Software\Issue18xIncaVSS\srcsafe.ini
2010-07-01 18:05:23,084 - SourceOffSite Server will be using the Visual SourceSafe 6 (non-enumeration optimized) Interface.
2010-07-01 18:05:23,084 - Started at 07/01/2010 18:05:23
2010-07-01 18:05:23,084 - ****************************************************
...
2010-07-05 12:03:45,603 - Connection accepted from 172.17.8.55:1595 on local address 172.17.9.174:8080, session id is 18.
2010-07-05 12:03:46,181 - 07/05/2010 12:03:46 - Server Exception (400): [C:\Program Files\SourceGear\SourceOffSite 5 Server\temp\crowlande851d5a5-5798-4685-bdf4-c5b3c28e238f634139282257438212\testproj] - OPERATION_FAILED
2010-07-05 12:03:46,181 - 18: Server Error: 400
2010-07-05 12:03:46,228 - 18: VSS database closed for the session id 18.
If I use the SoS client version 5.0.3 then I see that one file status is marked Renegade.
I clear this and try the command line again and it fails in the same way and after that the file is again marked Renegade in the SoS client. The file is a text file but is empty.

In SoS Client Checkout reports that the filewhich may have been modified and it attempts to merge, I let it and do an undo checkout, this also shows the Modified File dialog, I let it overwrite.

Do you have any suggestions about how to resolve this? It's one of a number of problems that's preventing me convert a source management system from VSS to SoS but I get the impression that they all have a similar root cause.

If I can get this going I'll have a stronger case to upgrade SoS...

Thanks,

Chris

lbauer
Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear

Re: soscmd getProject command fails

Post by lbauer » Mon Jul 05, 2010 9:27 am

Can you do the same get with the SOS GUI Client?

Can you do the get to a non-working folder, not using -SOShome?

Note: I've edited out some of the sensitive command info, since you may not want them on a public forum.
Linda Bauer
SourceGear
Technical Support Manager

Chris Rowland
Posts: 5
Joined: Thu Jun 17, 2010 3:13 am

Re: soscmd getProject command fails

Post by Chris Rowland » Tue Jul 06, 2010 8:54 am

Thanks Linda,

If I don't set the soshome parameter GetProject works, so do most other commands.

GetProject Tree takes a very long time then fails, but if I add the soshome parameter it works.

Most of my other problems seem to be caused by my confusion.
Thanks again,

Chris

lbauer
Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear

Re: soscmd getProject command fails

Post by lbauer » Tue Jul 06, 2010 9:21 am

Thanks for the info, though I'm not clear on whether you are still getting the 400 error when running your script.
Linda Bauer
SourceGear
Technical Support Manager

Chris Rowland
Posts: 5
Joined: Thu Jun 17, 2010 3:13 am

Re: soscmd getProject command fails

Post by Chris Rowland » Wed Jul 07, 2010 9:13 am

The command:

Code: Select all

C:\Program Files\SourceGear\SOS4_2\soscmd.exe -soshome "C:\Documents and Settings\crowland\Application Data\SourceGear\SOS" -command GetProject -server cnshfws3003:8080 -name crowland -password "" -database "\\ukoiak3s02\data\Masters\Software\Issue18xIncaVSS\srcsafe.ini" -project "$\i4dev\Test\testproj" -workdir "C:\Inca18x\i4dev\Test\testproj"
gives error 400, but the command:

Code: Select all

C:\Program Files\SourceGear\SOS4_2\soscmd.exe -command GetProject -server cnshfws3003:8080 -name crowland -password "" -database "\\ukoiak3s02\data\Masters\Software\Issue18xIncaVSS\srcsafe.ini" -project "$\i4dev\Test\testproj" -workdir "C:\Inca18x\i4dev\Test\testproj"
gives error 0 and appears to be working.
It looks as if specifying the -soshome folder makes the difference.

Is this the correct soshome path? From what I can see I've got sos databases in
C:\Documents and Settings\crowland\Application Data\SourceGear\SOS
and in
C:\Documents and Settings\crowland\Local Settings\Application Data\SourceGear\SourceOffSite

My guess is that the first is for SoS 4.x and the second for 5.x.
I am using soscmd 4.2 version because there isn't a 5.x soscmd.

Chris

lbauer
Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear

Re: soscmd getProject command fails

Post by lbauer » Mon Jul 12, 2010 4:05 pm

C:\Documents and Settings\crowland\Local Settings\Application Data\SourceGear\SourceOffSite

Yes, this is the cache (SOSHome) location for the SOS 5 client.

If you're using the SOS 4 client/command line client, the cache is

C:\Documents and Settings\crowland\Application Data\SourceGear\SOS
Linda Bauer
SourceGear
Technical Support Manager

Chris Rowland
Posts: 5
Joined: Thu Jun 17, 2010 3:13 am

Re: soscmd getProject command fails

Post by Chris Rowland » Wed Jul 14, 2010 6:34 am

I'm using SoS client 5 BUT soscmd.exe is 4.2 - because that's the latest soscmd there is.

Should soscmd V4.2 use the V5 soshome or the V4 soshome? The data format is totally different.

Chris

lbauer
Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear

Re: soscmd getProject command fails

Post by lbauer » Wed Jul 14, 2010 6:51 am

Sorry for the confusion. Use the SOS 4 client's -soshome. As you pointed out, there is no 5.0 Command Line Client, but the 4.2 Command Line Client can connect to the SOS 5.x server.
Linda Bauer
SourceGear
Technical Support Manager

Post Reply