I try to do a rpc connection to the core client.

retval = m_rpc.init("localhost", port);

When I do

pcOp = "suspend"
m_rpc.project_op(*m_pProjects->projects[iProjectNr],pcOp);

I get ERR_AUTHENTICATOR

When I do the same with a remote client everything works just fine.

The strange thing is when I do.
retval = m_rpc.init("localhost", port);
retval = m_rpc.authorize(passwd); With the valid password in gui_rpc_auth.cfg.
I get ERR_AUTHENTICATOR

Just guessing, but is your remote_hosts.cfg up to date?

Gruß,
Gundolf

Just guessing, but is your remote_hosts.cfg up to date?

Gruß,
Gundolf

Yes, I did copy the password from that file, did a reboot...
And it works fine when I do the same with a remote computer, but not for the localhost.

Just guessing, but is your remote_hosts.cfg up to date?

Gruß,
Gundolf

Yes, I did copy the password from that file, did a reboot...
And it works fine when I do the same with a remote computer, but not for the localhost.

Yes, I did copy the password from that file, did a reboot...
And it works fine when I do the same with a remote computer, but not for the localhost.

The password is in gui_rpc_auth.cfg. I asked about remote_hosts.cfg. Is the local host name/IP address in that file?

Gruß,
Gundolf

Yes, I did copy the password from that file, did a reboot...
And it works fine when I do the same with a remote computer, but not for the localhost.

The password is in gui_rpc_auth.cfg. I asked about remote_hosts.cfg. Is the local host name/IP address in that file?

Gruß,
Gundolf

the Ip address of the local machine,not the name of the localhost.

That sounds okay. Well, it was just a thought.

Gruß,
Gundolf
[edit]Another thought: You could try starting boinc.exe with the
--allow_remote_gui_rpc parameter (just to check it out).[/edit]

When I delete gui_rpc_auth.cfg. Reboot, the gui_rpc_auth.cfg is not made.
According to the documentation it should be.

Do you only start the client afterwards or also BOINC Manager?
Which version of BOINC? On what OS? Does the account that starts up have write access to the BOINC Data directory?

---

Do you only start the client afterwards or also BOINC Manager?
Which version of BOINC? On what OS? Does the account that starts up have write access to the BOINC Data directory?

As always you have the answer.
It was the access. Maybe that also solves the other problems lets see.
But just curious what happens, what is password? if there is none. It is not a blank (empty) one.

But just curious what happens, what is password? if there is none. It is not a blank (empty) one.

The password that is generated is a random 32 character (hexadecimal) key.
So it would be best to change it again to something you can remember much easier, like your phone number. ;-)

---

But just curious what happens, what is password? if there is none. It is not a blank (empty) one.

The password that is generated is a random 32 character (hexadecimal) key.
So it would be best to change it again to something you can remember much easier, like your phone number. ;-)

I will do a read of the password in the data directory, from the file, that should always be the right one.

And guess what it was?
I run the compiler/debugger as admin and the BOINC core client runs as local user.
For some reason this makes it impossible the authenticate.
Running my application as local user and everything works ok.
One problem solved up to the next...