I have recently reinstalled boinc and now it wont connect to the server and thus is just sitting there doing nothing. Also it doesn't start up with windows but that might be because asus thought it would be a good idea to play hide and seek with the boot files.



I have recently faced the boinc.msi problem on multiple computers, wouldn't it be easier to just put the core function of the fix into the installer.

now it wont connect to the server

Which server is THE server please?

It may also help to have a copy of the actual error message, as there are many it could be.

I have recently reinstalled boinc and now it wont connect to the server and thus is just sitting there doing nothing. Also it doesn't start up with windows but that might be because asus thought it would be a good idea to play hide and seek with the boot files.

Which Windows OS?
Which project(s) are you try to attach to?

I have recently faced the boinc.msi problem on multiple computers, wouldn't it be easier to just put the core function of the fix into the installer.

.msi problem are usually caused by Windows and the installer usually can't clean up the mess Windows makes. Therefore it is suggested to follow the procedures outlined in the Boinc FAQ Service.

---

Boinc V 7.4.36
Win7 i5 3.33G 4GB NVidia 470

This isn't any paticualar server I'm trying to access (that I know the name of) it's just boinc trying to access localhost. I can't get far enough to connect it to any project.

Also I'm running windows 7 64 bit and boinc 6.10.58 64 bit.

Also I already cleaned up that "mess windows caused", what I'm saying is if the problem is going to be happening in a predictable way in an amount of cases then why don't you save us the trouble of going and sorting out the problem because I assure you that many people are coming up to that error and not bothering trying to fix it.

If it's "local host", then your computer ISN'T trying to access a server - it's trying to access itself.

BOINC is in two parts:
1) The 'core client', or 'local host', or 'the worker part'. This isn't visible.
2) The 'Manager', which is the gui that appears on your screen.

The purpose of the manager is to display to the user some of the things that the client is doing. If the 2 can't connect, then you can't see what is happening.
The 2 parts communicate via port "PI" - 31416.
And if something takes over this port (e.g. Windows), or blocks it (e.g. your anti virus program), then you get the message that you see.

So, first off, allow your AV through that port, or give all parts of BOINC trusted status, or what ever is the option in your AV.

Having the same problem with 1 Box of mine, all it does is sit there saying "connecting to localhost" whatever it means by that, it's self I assume. I've un-installed and installed BOINC several times but the same thing happens, it won't connect for some reason. I was working up until this morning but I've shut the Box off for now because it won't connect. I can get on the internet with the Box so it's not the net connection ???

Read Les' post just before yours. It'll explain what is what.

And then just allow BOINC to pass through your firewall.
Boinc.exe, boincmgr.exe need to be allowed through on TCP and UDP ports 31416.
Boinc.exe needs separate access to the internet on TCP ports 80 and 443.

---

I read his post already but I don't run a Firewall or AV, it was running up until this morning & I didn't make any changes. Worse comes to worse I'll try a re-install of the OS ...

Which OS is that?

---

Which OS is that?

Win XP Pro 64-Bit, just reinstalled the OS the other day because I put a new MBoard & CPU in it, been running BOINC okay until this morning though ...

You do know that Windows XP has a firewall? That even when you disable this firewall, that it isn't really disabled?

So try to add BOINC as an exception in Windows Firewall. See about 1/3rd down the page at http://www.microsoft.com/windowsxp/using/networking/security/winfirewall.mspx.

---

Did that already, also Disabled the Firewaill through the services.msc, it's something I do as soon as I install a fresh OS or re-install a OS

Just checked again & still nothing, the boincmgr.exc & boinc manager have been added to the exceptions list but whether the firewall is off or on the client still can't connect to the localhost ...

Please check in Windows Task Manager if boinc.exe is still running when you get the message. Did you use the 64bit or 32bit version of BOINC?
Which directory did you install BOINC its program files into?

---

The boinc.exc shows in the Task Manager but then goes away. 64-Bit Version of BOINC ... D:\Program Files\BOINC

From what I can find out there is no localhost entry in the Advanced section of the Windows Firewall Window. There's a Wireless Network Connection 2 but no localhost entry like my other Wireless Box's have.

I did a Repair install of the OS but still no localhost entry. .

The boinc.exc shows in the Task Manager but then goes away.

How shall the manager connect to the localhost if the localhost (boinc.exe) isn't running?

Gruß,
Gundolf

---

Computer sind nicht alles im Leben. (Kleiner Scherz)

BOINC consists of separate parts that all make up the one program. The client (boinc.exe) and the Manager (graphical user interface, boincmgr.exe) are the two most important. Although, Boinc can easily run without Boinc manager. However, it can't run without the client.

So something is stopping the client from running. It can be that it crashes. it can be that one of the science applications of any of the projects you're attached to is causing havoc.

Please navigate to your BOINC Data directory and open stderrdae.txt, then check what the last error was. Post it here, if necessary.

---

There's nothing there & I'm not attached to any Projects with the Box. I figured it might be a Project as I've had it happen before & by getting rid of a few Projects I could connect.

I still say the whole problem is that there is no localhost entry in the Advanced Window of the Firewall ... I'm installing a fresh copy of Win XP Pro now after formatting the Partition. I wasted the whole day and could have had that done already but thought I could straighten it out, that's what I get for thinking ... lol ... hopefully that will fix it, something was messed up because I even lost the Internet Connection on the Box even though I was showing a connection in my Network Connections ...

You're confusing 2 things:
1) getting a program to run, and keep running,
and
2) allowing this program through whatever firewall may or may not exist.

Concentrate on fixing 1).

stderrdae.txt as mentioned by Ageless is where there should be error messages about things going wrong with the client.
Have you looked at this file?

You're confusing 2 things:
1) getting a program to run, and keep running,
and
2) allowing this program through whatever firewall may or may not exist.

Concentrate on fixing 1).

stderrdae.txt as mentioned by Ageless is where there should be error messages about things going wrong with the client.
Have you looked at this file?

It's fixed, I formated the partition & reinstalled the OS & BOINC is connecting again on that Box. Again, there was no "stderrdae.txt as mentioned by Ageless" to look at as I deleted\uninstalled & got rid of all the files in the BOINC Folder this morning when I couldn't connect.