GetProject ERROR:"soscmd.exe encountered a problem and.

tgcrook · Post by **tgcrook** » Fri Oct 15, 2004 4:55 pm

Using soscmd.exe of SOS Classic Version 4.0.2 GetProject works for many folders but on certain ones it throws an error. I can get latest with no problems using the GUI client.

When I issue the following command:
soscmd.exe -command GetProject -server theServer:18081 -name xxxxx -password xxx -database D:\TeamSpecificFolders\TheApp\VssDatabases\TheAppDEVSrcCode\srcsafe.ini -project $/TheApp/Release_2.1/src/com/company/theapp/test -soshome C:\Progra~1\SourceOffSite -workdir src\com\company\theapp\test -verbose

...I get the attached errors. The first error is what pops up ("soscmd.exe encountered a problem and needs to be closed"), the next two are what I get when I select that error's
option to get the details of the error.

While the same command on a different project (different folder within the same database) works just fine...
soscmd.exe -command GetProject -server theServer:18081 -name xxxxx -password xxx -database D:\TeamSpecificFolders\TheApp\VssDatabases\TheAppDEVSrcCode\srcsafe.ini -project $/TheApp/Release_2.1/src/com/company/theapp/db -soshome C:\Progra~1\SourceOffSite -workdir src\com\company\theapp\db -verbose

Here are the updates to the log in different cases. Two when getProject works & two when it fails. Thinking a conflict
may be happening I ran the commands both with the GUI VSS client running and with it closed....

This is with VSS connected to same DB& getProject results in an error message
10/15/2004 3:54:04 PM - Connection accepted from 10.31.4.159:2214 on local address 10.64.70.11:18081, session id is 51.
10/15/2004 3:54:09 PM - 51: Unable to get hostname from address: 10.31.4.159
10/15/2004 3:54:14 PM - 51: Exception: An existing connection was forcibly closed by the remote host

This is with VSS disconnected to same DB & getProject results in an error message (same result as above)
10/15/2004 4:02:18 PM - Connection accepted from 10.31.4.159:2224 on local address 10.64.70.11:18081, session id is 54.
10/15/2004 4:02:22 PM - 54: Unable to get hostname from address: 10.31.4.159
10/15/2004 4:02:28 PM - 54: Exception: An existing connection was forcibly closed by the remote host

This is with VSS connected to same DB& getProject results in successful retrieval of files from a different project (different folder within same vss database)
10/15/2004 3:57:08 PM - Connection accepted from 10.31.4.159:2216 on local address 10.64.70.11:18081, session id is 52.
10/15/2004 3:57:12 PM - 52: Unable to get hostname from address: 10.31.4.159

This is with VSS disconnected to same DB& getProject results in successful retrieval of files from a different project (different folder within same vss database)
10/15/2004 3:59:54 PM - Connection accepted from 10.31.4.159:2222 on local address 10.64.70.11:18081, session id is 53.
10/15/2004 3:59:58 PM - 53: Unable to get hostname from address: 10.31.4.159

Looks to me like the log doesn't provide much. In the error states it only shows that the connection was forcibly closed,
which is likely just me clicking OK on the error message & ending the connection.

This functionality is instrumental to running our automated builds. I'm surprised not to see more posts for this error. PLEASE let me know if this is a known bug and if it is something that will not be remedied until the next SOS release. If there is a known workaround it would be extremely helpful.

Thanks,
Tim

lbauer · Post by **lbauer** » Sat Oct 16, 2004 7:02 pm

What's different about the folders where the Get doesn't work? Are they large, with many subprojects and files? Does the size of the get make a difference?

Another possibility, if SOS can Get one project but not another, is minor database corruption. You might try running analyze on the VSS database.

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

Randy Haben · Post by **Randy Haben** » Mon Nov 15, 2004 6:35 pm

I have the same probelm trying to do automated builds. Even small subprojects fail. I can use the GetProjectTree command on the same project with all of the same parameters with no problem at all.

lbauer · Post by **lbauer** » Thu Nov 18, 2004 12:09 pm

Could you email a copy of your command to linda at SourceGear.com?

Randy Haben · Post by **Randy Haben** » Fri Dec 03, 2004 6:50 pm

Well, I am not gettiing the error dialogs anymore (have no idea why). And after turing on -verbose I can see that I am getting most files, but I keep gettting errors "No such file or project" when SOS seems to attempt get files with numbers or dates for names. We don't have any files like that so it is obviously misinterpreting seomthing in the database as a file.

Guest · Post by **Guest** » Fri Dec 03, 2004 6:51 pm

Oops! Spoke too soon. When the process completes, I get the Dr. Watson dialog that pops up when an AV occurs.

Guest · Post by **Guest** » Thu Dec 09, 2004 10:21 am

We've seen this strange file name issue before with the Command Line Client.

I can send you a preview of SOS 4.1 to see if the new CLC performs better.

Email linda at SourceGear.com for more information.