I was updating a .bat file to pause and resume the client on my notebook, when I noticed the following:
running

C:\Users\Robi>"C:\Program Files\BOINC"\boinccmd --get_cc_status
network connection status: don't need connection
CPU status
    not suspended
    current mode: always
    perm mode: always
    perm becomes current in 0 sec
GPU status
    not suspended
    current mode: according to prefs
    perm mode: according to prefs
    perm becomes current in 0 sec
Network status
    not suspended
    current mode: always
    perm mode: always
    perm becomes current in 0 sec
Operation failed: Error 2

^^^^^^^^^^^^^^^^^^^^^^^^^ why Error 2? 

I can send the stderr to nul to hide it, but that doesn't answer the question on what's happening and why the Error 2.

C:\Users\Robi>"C:\Program Files\BOINC"\boinccmd --get_cc_status 2>nul
network connection status: don't need connection
CPU status
    not suspended
    current mode: always
    perm mode: always
    perm becomes current in 0 sec
GPU status
    not suspended
    current mode: according to prefs
    perm mode: according to prefs
    perm becomes current in 0 sec
Network status
    not suspended
    current mode: always
    perm mode: always
    perm becomes current in 0 sec

no Error 2, sent to nul

client is

C:\Users\Robi>"C:\Program Files\BOINC"\boinccmd --client_version
Client version: 7.6.22

boinccmd:

C:\Users\Robi>"C:\Program Files\BOINC"\boinccmd -V
boinccmd,  built from BOINC 7.6.22

windows:

OS Name	Microsoft Windows 7 Home Premium
Version	6.1.7601 Service Pack 1 Build 7601
OS Manufacturer	Microsoft Corporation
System Manufacturer	ASUSTeK Computer Inc.
System Model	U52F
System Type	x64-based PC
Processor	Intel(R) Core(TM) i5 CPU       M 460  @ 2.53GHz, 2534 Mhz, 2 Core(s), 4 Logical Processor(s)
BIOS Version/Date	American Megatrends Inc. U52F.208, 07/21/2010
SMBIOS Version	2.6
Installed Physical Memory (RAM)	4.00 GB
Total Physical Memory	3.79 GB
Available Physical Memory	857 MB
Total Virtual Memory	8.19 GB
Available Virtual Memory	2.09 GB
Page File Space	4.40 GB

So, the question is:
why does boinccmd --get_cc_status return "Operation failed: Error 2"?
Anyone? Did I find a bug?

Thanks for any info.

Robi

I don't think the error you get is one from BOINC or boinccmd, but one from Windows. It's not an error that's anywhere in the BOINC (client) source code.

Here's mine:

P:\BOINCProgram>boinccmd --get_cc_status
network connection status: don't need connection
CPU status
    not suspended
    current mode: always
    perm mode: always
    perm becomes current in 0 sec
GPU status
    not suspended
    current mode: according to prefs
    perm mode: according to prefs
    perm becomes current in 0 sec
Network status
    not suspended
    current mode: always
    perm mode: always
    perm becomes current in 0 sec

P:\BOINCProgram>

But perhaps I don't see it because I have my BOINC programs directory outside the Windows protected Program Files/Program Files (x86) directories. Maybe that Windows doesn't like this command to be done on an executable in this protected directory.

---

Ran it on W7-64 in admin terminal window. The only difference I see is that the first line reports 'online' instead of 'don't need connection', no error.

---

Coelum Non Animum Mutant, Qui Trans Mare Currunt

I'm on BOINC v7.6.22, Windows 7 Pro/64, and my BOINC programs aren't in a protected area.

But I'm getting 'Error 2' every which way I try it.

D:\BOINC>boinccmd.exe --get_cc_status
network connection status: don't need connection
CPU status
    not suspended
    current mode: always
    perm mode: always
    perm becomes current in 0 sec
GPU status
    not suspended
    current mode: always
    perm mode: always
    perm becomes current in 0 sec
Network status
    not suspended
    current mode: always
    perm mode: always
    perm becomes current in 0 sec
Operation failed: Error 2

I have a faint recollection that something in that general direction was fixed somewhat recently. I don't think it's a real error anyway.

The error seems to be on the network section.
So could be a network specific error 2, or TCP/IP error 2. Until we know what's throwing the error 2, it's difficult to figure out.

Checking further around, error 2 seems to have to do with the tool not being able to communicate via RPC to the client on the correct port(s). Has any of you made absolutely sure you added your present BOINC programs in your firewall, all with the correct path ways?

Edit (after reading Juha's answer): But then I am using BOINC 7.6.32, so it could also be that if it's something that was fixed, that it's already in this version.

---

For that matter, tested on 7.6.29 and BOINC client is in it's prescribed spot... C:\Program Files\BOINC

---

Coelum Non Animum Mutant, Qui Trans Mare Currunt

I have a faint recollection that something in that general direction was fixed somewhat recently. I don't think it's a real error anyway.

https://github.com/BOINC/boinc/commit/0921a0e7c433f321801b0714f870b8ebf71cf51a

Edit - tested with the private build I made to test yesterday's bugfix - no error. It's gone.

Thanks to all for the replies, and the checking!
I liked the "spurious error msg" part in github :)

I'll just wait for the update then, and, since it's not a serious error (for me), it's bearable :) specially when followed by a 2>nul ;)


Thanks again, Robi

I liked the "spurious error msg" part in github :)

If you liked that, you'll like the prequel:

https://github.com/BOINC/boinc/commit/bb2f9339b48df2b170583741a3323616dc119484