Greetings,
I am attempting to use the soscmd.exe to "get latest". Part way through an error occurs that ends the application. The error is unhandled and I am prompted to "Send Error Report" to Microsoft. The screen is attached.
"Get Latest" works fine from the SOS client (version 4.0.2.151).
The command-line I use is:
soscmd.exe -soshome "C:\Documents and Settings\xxxx\Application Data\SourceGear\SOS" -server "hsi-dev:8888" -database "D:\Source\iTDS v1.0\srcsafe.ini" -name "xxxx" -password "xxxx" -command GetProject -project "$\iTDS v1.0" -recursive -workdir "C:\SOURCE\ITDS V1.0"
The error in Event Viewer is:
Event Type: Error
Event Source: Application Error
Event Category: None
Event ID: 1000
Date: 6/7/2006
Time: 9:21:56 AM
User: N/A
Computer: HSI-HANSENM
Description:
Faulting application soscmd.exe, version 0.0.0.0, faulting module ntdll.dll, version 5.1.2600.2180, fault address 0x00011e58.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 73 6f 73 ure sos
0018: 63 6d 64 2e 65 78 65 20 cmd.exe
0020: 30 2e 30 2e 30 2e 30 20 0.0.0.0
0028: 69 6e 20 6e 74 64 6c 6c in ntdll
0030: 2e 64 6c 6c 20 35 2e 31 .dll 5.1
0038: 2e 32 36 30 30 2e 32 31 .2600.21
0040: 38 30 20 61 74 20 6f 66 80 at of
0048: 66 73 65 74 20 30 30 30 fset 000
0050: 31 31 65 35 38 0d 0a 11e58..
Any ideas?
Thanks,
Matt Hansen
soscmd.exe "faulting" ntdll.dll
Moderator: SourceGear
soscmd.exe "faulting" ntdll.dll
- Attachments
-
- soscmd error.png (12.38 KiB) Viewed 4284 times
Problem gone...
The command did not work previously. Have not had other issues.
Thanks for the help. I tried your suggestion and it worked, but I call that command-line 2 other times; from an automated build process. I didn't change those and they work now. ???
I suspect it was failing because I had a file checked out, or not checked out, but writable, or something. I'm not sure if that makes sense based on your product, but it's just a hunch.
Thanks,
Matt
Thanks for the help. I tried your suggestion and it worked, but I call that command-line 2 other times; from an automated build process. I didn't change those and they work now. ???
I suspect it was failing because I had a file checked out, or not checked out, but writable, or something. I'm not sure if that makes sense based on your product, but it's just a hunch.
Thanks,
Matt