I run many projects for a few months but today i had to completely new install my computer. I installed the 5.2.13 Boinc Client which was running fine for a few days and also was running fine after the new install. But now there is always an error message "Boinc Manager couln´t connect to a Boinc Client!" I tried to reinstall Boinc, but it won´t work... Could anybody help me please?!? Sorry for the poor english! ;-)

EDIT - Now i´ve got Boinc to work... But i must start the Boinc client by double-clicking on the boinc icon in C:\\Programme\\Boinc\\ ,and then i must start the Boinc Manager by double clicking the boincmgr icon in C:\\Programme\\Boinc\\ ... What can i do to start Boinc normal???
Please help me! I´m a Boinc junkie... ;-)

Keep on crunching!

---

Stefan,

Manually telling Boinc to "run" when you want it to run and to "stop" when you want it to stop is "normal". Isn't that what you do with other programs?

Regards,

Michael

---

"The arc of history is long, but it bends toward Justice"

Manually telling Boinc to "run" when you want it to run and to "stop" when you want it to stop is "normal". Isn't that what you do with other programs?

Michael, if I understood him correctly, it's not a matter of "he has to run BOINC Manager" - it's that he has to _first_ launch the boinc daemon manually, before the Manager will work. Short of waiting for 5.2.14 or whatever is released with that fix, I don't know what to advise.

---

Yes Bill, you are right. Normaly the Boinc Manager starts at Windows startup and beginns to crunch... But i had to start it manual. But after comletly shuting down (not after a reboot) Boinc began to work normal. Now it starts normaly at the Windows startup. I have no idea what was wrong this night...
Thanks for your answers!

Greetz Stefan

BOINC@Austria

---

I had the same problem, and could only get the manager to connect to the client after removing the shortcut to the manager from my "startup" folder and rebooting. Rebooting and allowing Windows to try to start the manager from my "startup" folder was not successful. One data point however that was not mentioned here: When I was unable to connect to the client (client was running) from the manager, I _was_ able to connect to that client from another PC on my network. Go figure. I hope someone is able to fix this. It feels like once the manager launches the client at startup time, if it fails to connect to it, it will never connect to it. Note, the manager that can't connect to it's own client on localhost, can still connect to clients on other PCs.

---

My understanding is that 5.2.14 _did_ solve this issue, but had to be pulled because of an unrelated problem. There should be a new version out (in alpha test anyway) next week. Hopefully it will pass testing quickly, and become the 'recommended' version.

---