PM'ed you a screenshot Astro.
And Thanks a million credits for your help.

EDIT In advance that is! lol

---

DONATE TO SETI

Well this might be the problem. boincmgr.exe is 2972 however there is no listing for boinc.exe in the task manager. PID 2972 does not appear in the dos box.

Bring up a DOS box, change to the BOINC directory, and run this:
boinc.exe -daemon -allow_remote_gui_rpc

Look for any error messages and post them.
The command:
netstat -a -n

...should show an entry with port 31416 LISTENING. If not, then Windows is blocking BOINC from listening on that port.

If no error, then try to startup the manager and connect to localhost.

Where's this stand now, Pawly?

---

Capitalize on this good fortune, one word can bring you round ... changes.

He sent me a screenshot of the dos box and taskmanager. I didn't see boincmgr, or boinc listed in netstats, but did see JUST boincmgr listed in the taskmanager. NO process was using 31416. He claims it starts up fine, then boinc closes (for some reason). I went to bed when he was running virus, spybot, adware, malware checks, etc. He's using CA e-Trust antivirus and Sygate firewall. Claims CA won't update properly after computer malfunction (atleast that's what I inferred he meant).

He did the add/remove program uninstall and reinstall. sygate only asked for permission for boincmgr. I suspect sygate is stopping boinc, but can't confirm that. I could see how it might stop boinc from accessing a port, but not how it would shut boinc down entirely.

so, as far as I know, he's still got issues.

The only thing I can add at this point is that BOINC doesn't shut down entirely, just detaches BOINC Manager from "localhost". The Program itself continues to try to attach to localhost.

CA antivirus has been having trouble Updating but this is a problem that Computer Associates knows about and is trying to fix on their end (effecting many people).

SO yeah, I still have issues.

---

DONATE TO SETI

You haven't said whether or not virii, etc were found. You need to figure out why boinc.exe is shutting down, and boincmgr can't get a port assigned. The biggest culprit would be your firewall. What have you tried with regard to that? Have you shut it down, then uninstalled/reinstalled boinc, to see if it works without a firewall? I assume you're installing boinc as "single user" when you install it, but perhaps it's installed as a service?

AdAware and SpyBot found nothing out of the ordinary. I uninstalled BOINC, dropped the firewall and reinstalled with the same result. Starts and then disconnects from localhost after a few seconds.

The only thing I updated before the troubles began was MSN Live Messenger. But I do not have it running currently.

EDIT - Single user installation.

EDIT II - Unfortunately I will have to head off to work soon and then will be camping for a few days after that. I guess I'll just have to let the RAC drop like a rock until I return. Thanks to everyone for trying to help. Keep those thinking caps turned on and maybe I'll return to a solution!

Paul

---

DONATE TO SETI

AdAware and SpyBot found nothing out of the ordinary. I uninstalled BOINC, dropped the firewall and reinstalled with the same result. Starts and then disconnects from localhost after a few seconds.

The only thing I updated before the troubles began was MSN Live Messenger. But I do not have it running currently.

EDIT - Single user installation.

EDIT II - Unfortunately I will have to head off to work soon and then will be camping for a few days after that. I guess I'll just have to let the RAC drop like a rock until I return. Thanks to everyone for trying to help. Keep those thinking caps turned on and maybe I'll return to a solution!

Paul

This may be very simplistic, but what do you get if you ping localhost from a CMD box?

C:\\>ping localhost

Pinging desktop [127.0.0.1] with 32 bytes of data:

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Ping statistics for 127.0.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms


F.

AdAware and SpyBot found nothing out of the ordinary. I uninstalled BOINC, dropped the firewall and reinstalled with the same result. Starts and then disconnects from localhost after a few seconds.

The only thing I updated before the troubles began was MSN Live Messenger. But I do not have it running currently.

EDIT - Single user installation.

EDIT II - Unfortunately I will have to head off to work soon and then will be camping for a few days after that. I guess I'll just have to let the RAC drop like a rock until I return. Thanks to everyone for trying to help. Keep those thinking caps turned on and maybe I'll return to a solution!

Paul

This may be very simplistic, but what do you get if you ping localhost from a CMD box?

C:\\>ping localhost

Pinging desktop [127.0.0.1] with 32 bytes of data:

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Ping statistics for 127.0.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms


F.

Identical to what you have posted.

---

DONATE TO SETI

Maybe stderrdae.txt and/or stdoutdae.txt in BOINC directory have some clues why BOINC shuts down.

-Juha

---

If there is no line for BOINC.exe, then it is not running for some reason, and therefore the manager cannot attach to it. We need to figure out why BOINC.exe is shutting down.

Looking in stderrdae.txt is a good first step.

---

BOINC WIKI

I'm now having the same problem with one of my computers.

I don't use a firewall on the computer, I have one on my router and all other computers are connecting fine.

I use a service install of BOINC.

I just noticed a window open with seti beta screensaver running. Could this be part of the problem. I know Pawly runs the same project on his machine?

---

Check out the forum for Canada the #1 Canadian team.

you have exactly the same problem???? No boinc.exe in taskmanager (Boinc.exe closes by itself, leaving the manager empty but displayed)?

Yes the same problem.

---

Check out the forum for Canada the #1 Canadian team.

If you're seeing the Setibeta screensaver running, I wonder how that's possible without the daemon (boinc.exe) running. I've seen some apps written as a wrapper running without boinc, but not one without a wrapper. I have some thinking to do.

A window opened up its running in the window, and like I said I did a service install the screensaver shouldn't run at all.

---

Check out the forum for Canada the #1 Canadian team.

here's a wild thought. At some point two instances of boinc were installed. When both try to start they're each seeing the other and shutting down. It's a stretch, but that's what I'm left with. could you do a search for *boinc* and see if it exists in other folders (other than C:\\programfiles\\boinc or whereever you installed it to.

Search showed no other installs. I uninstall before I install a new version.

---

Check out the forum for Canada the #1 Canadian team.

A window opened up its running in the window, and like I said I did a service install the screensaver shouldn't run at all.

So the application is just running in its standalone mode. That could happen if BOINC died immediately after launching it, the app decides to run standalone if it cannot establish the shared memory interface with BOINC.

                                                               Joe

I now have uninstalled BOINC and installed to a new directory, there is no problem connecting. So I'm going to assume that one of the projects is causing the problem.

Is there anyway to transfer the work over from the previous install, I want to do one project at a time to see if I can get it to disconnect?

---

Check out the forum for Canada the #1 Canadian team.