My computer encountered "connection failed" when I run boinc manager in the last several days. There was nothing wrong with the firewall. The problem remained even after restart or reinstallation.

Finally, I found that only "boincmgr.exe" was running when I run boinc manager and "boinc.exe" wasn't is the process list of task manager. Then I tried to run the "boinc.exe", and then the problem disappeared and boinc manager began to work.

If you have encountered the same problem, you can try to run "boinc.exe" first. Good luck!

Okay, that worked for me, but isn't really a fix (more of a workaround).
How do I get back to BOINC starting properly? without having to run Boinc.exe from a command prompt?

---

Sorry, I have no idea about that, either. The window of boinc.exe is really boring.

Okay, that worked for me, but isn't really a fix (more of a workaround).
How do I get back to BOINC starting properly? without having to run Boinc.exe from a command prompt?

Sorry, I have no idea about that, either. The window of boinc.exe is really boring.

Okay, that worked for me, but isn't really a fix (more of a workaround).
How do I get back to BOINC starting properly? without having to run Boinc.exe from a command prompt?

Errhm, by default, boinc.exe is started automatically, when the BOINC Manager does not find an instance of boinc.exe in the process list. Check out the files stdoutdae.txt and stderrdae.txt if there's something that can tell you the reason for boinc.exe's failure.

---

since 29-Jun-2004:

these are the closest files to what you mentioned:
stdoutgui.txt=
send: -1
send: -1
send: -1

stderrgui.txt=empty

---

By the way, this is more wide spread than you might think and is Recent!
search Q&A for "disconnected"

---

By the way, this is more wide spread than you might think and is Recent!
search Q&A for "disconnected"

In most cases the "disconnected" has to do with the silent activation of Windows Firewall when Windows Update installed Service Pack 2. The user then has to disable the firewall or add two rules for boinc.exe and boingmgr.exe to work properly again.

Hm, I also have that send: -1 but rather rare - unfortunately these messages were logged without a timestamp. How does your BOINC Manager start? During windows startup? Does boinc.exe start if you restart BOINC Manager (I mean restart, not hide and unhide!)?

---

since 29-Jun-2004:

I use Zone Alarm firewall, and Boinc client, Boinc manager for Windows, Boinc Screensaver, and boinc_gui are all fully allowed.
Boinc manager starts at windows startup.
I tried exiting and restarting, repair reinstall, uninstalling and reinstalling, uninstalling fully deleating everything in the Boinc folder and reinstalling. None of those attempts fixed the problem.

---

Okay, that worked for me, but isn't really a fix (more of a workaround).
How do I get back to BOINC starting properly? without having to run Boinc.exe from a command prompt?

Hmmm, I'm suddenly having this same problem on one of my windows 2000 machines.. I've been using BOINC Manager 4.45 for some time now..

YES. the work around get's it going.. but next time I reboot the machine (not too often on this machine).. this work around will have to be done..

I do have another machine that I shut down twice a day during the woek week.. (a laptop that travels to work) .. it would be real annoying if this problem shows up there.. (not yet!)

---

Expanding the edge of Science.

[quote
Hmmm, I'm suddenly having this same problem on one of my windows 2000 machines.. I've been using BOINC Manager 4.45 for some time now..
[/quote]

Interestingly enough, two subsequent reboots of this machine have successfully started the BOINC Manager without problems or need to utilize the "work around".

// Brian

Sometimes the manager tries to talk before the daemon is ready to listen. In that case, File - select computer - localhost or 127.0.0.1 or (blank) works to get the connection going.

---

BOINC WIKI

[quote]Sometimes the manager tries to talk before the daemon is ready to listen. In that case, File - select computer - localhost or 127.0.0.1 or (blank) works to get the connection going
i've tried that and no luck i've also tried the work around and I've add all boic executibles to my exception list. so I gave up on 4.45
and decided to keep running 4.19

---