Hello everybody
I am not a very advanced user.
I just downloaded boinc ver. 6.10.56 of boinc manager for Win7 x64.
As far as I can tell the boinc manager cannot connect to localhost.
I have created exceptions for all of the boinc executables in windows firewall and still the same.
I also found somewhere that it can help to change the properties of the boinc program folder to deactivate "read only" status. That I could not do. If I change it and look at properties again, it goes back to the way it was before.

In the stderrgfx.txt file it says: TRACE [3812]: RPC_CLIENT::init connect 2: Winsock error '10061'

Sorry if this question has been asked to death, but I could not find anything that would help me in the forums.

I would appreciate any help you can give.

Is boinc.exe running?

The winsock error is google top hitting here:

http://msdn.microsoft.com/en-us/library/ms740668%28VS.85%29.aspx

---

Coelum Non Animum Mutant, Qui Trans Mare Currunt

Thanks for the reply.
Forgot that little detail. Boinc.exe runs for a few seconds, maybe ten, and then stops. I can see it in task manager when I start up boinc, but only runs for a few seconds and then disappear.

About the error. Sounds strange, doesn´t it? that boinc.exe would actively refuse the connection?
Have no idea what it means.

To quote your post:

As far as I can tell the boinc manager cannot connect to localhost.

If boinc.exe is not running then BOINC Manager wont be able to connect to it, to the client known as localhost [on IP 127.0.0.1]. Think you have to review your securities as to why the client service does not persist.

---

Coelum Non Animum Mutant, Qui Trans Mare Currunt

Thanks again for the reply.
Where can I look for the reason for the client shutting down?
As I said, I created exceptions in windows firewall for boinc.exe and boinc manager, and no other firewall or security software running. I wouldn´t know where to start looking.

Don't know what else... no AV at all? Run the installer again and choose repair or uninstall, reinstall might kick. And if you upgraded from 5.x to 6.x then the instructions may not have been followed... to boot.

---

Coelum Non Animum Mutant, Qui Trans Mare Currunt

Firstly, ensure that 127.0.0.1 and 0.0.0.0 and port 31416 are allowed permissions for BOINC.exe, BOINCmgr.exe, BOINCcmd.exe, BOINCscr and c:\Windows\boinc.scr. Ensure that the path to these executables is specified correctly in Win Firewall.

Secondly, for 'WINSOCK ERROR 10061' and/or no project running in task manager and boinc run without calculate any WU:

1. Terminate the 2 BOINC processes: boincmgr & boinctray in Process manager, i.e., <ctrl>+<Shift>+<Esc> (click image name to sort alphabetically)
   
2. Navigate to C:\Program Files\Boinc (or where you've installed BOINC) in Windows Explorer
   
3. right click and select Properties for BOINC Programs folder
   
4. remove Read only and Apply to all subsdirectory.
   
5. Restart boinc and it run again
   

im having this same problem, boinc.exe starts, then 10 secs later it shuts down, with no error messages. besides the one the manager gives when he cant find that process.

tried everything you said, but still the same problem. running the same OS as the op, win 7x64.

the winsock error has little to do with this i guess, the problem is boinc.exe shutting down.

also noticed the memory usage grows very fast on that process before shutdown.

Did you look for error messages in the various stderr/stdout files to be found in the BOINC data directory?

Did you try starting boinc.exe in a cmd shell?

Gruß,
Gundolf

---

Computer sind nicht alles im Leben. (Kleiner Scherz)

People, ever since Windows XP there has been a read-only mark on the 'special Windows directories'. You cannot remove this mark in Windows. Even after trying, it'll return when you next check it. So stop fiddling with it, it's really not what's at fault here. All your files will not be read-only (unless you restored them from a CD/DVD).

@toro & Cmk, is that on a clean installation of Windows and BOINC, or are you using an old (backed-up?) BOINC Data directory?
How did you install BOINC, as a screen-saver installation or as a protected application execution installation? (see this screen shot and this one to decide what you did).

@toro, Winsock 10061 means that the connection was refused, because the application or the service wasn't running. Can you check in Task Manager whether or not boinc.exe actually starts up, and if it does, how many times?

---

Since this is kind of a Frequent Frequent Asked Question, why not have the BM, when authorized, report in layman language understood comment to say that boinc.exe is not running? Who knows what "localhost" is? Who understands the interactions of the BOINC components?... not the crunching for the masses volunteers I'd think!

---

Coelum Non Animum Mutant, Qui Trans Mare Currunt

Because BOINC Manager can't know whether it is that boinc.exe isn't even running, or that it is but just behind a firewall. BOINC Manager isn't reading what's all in memory.

---

At what effort could it? Someone has access to the BM GUI so not seeing any secret in not having it enabled to check if the core client is running... a text such as "The BM is not able to connect to localhost or check that the core client (boinc.exe) is running". That in it self conveys to the user without much guesswork that that is the key element to verify.

---

Coelum Non Animum Mutant, Qui Trans Mare Currunt

thanks for the replys guys.
This was a fresh installation. But I have tried uninstalling and installing again several times.

this is what i get from stderrdae.txt
Unhandled Exception Detected...

- Unhandled Exception Record -
Reason: Access Violation (0xc0000005) at address 0x00000000734DA2FF read attempt to address 0x0000012C

and from stdoutgui.txt:
01:07:02 p.m.: Error: can't open file 'C:\Program Files\BOINC\\RebootPending.txt' (error 2: the system cannot find the file specified.)
[06/27/10 13:07:03] TRACE [1468]: init_asynch() boinc_socket: 708

I tried uninstalling boinc, rebooting, erasing all of boinc directories and installing again. Same thing.

I´m still very much lost. Don´t know what else to try.

Edit: as far as what I did when I installed it, I didn´t change anything, so whatever the default is.
Also, boinc.exe does start. Only one process. Shuts down after ten seconds or so.

Since you see the core client [boinc.exe] start and unload when firing up the BéOINC Manager it begs the question if the service is actually trying to start even before you sign in. I'm presuming you look in the Windows-7-64 bit Task Manager with full admin rights (I'm running that now). If not, there is a button left bottom when the TM is running that allows to see all processes. Plz confirm it is not running!

Then if you launch services.msc in the menu start line, you can see if boinc.exe is installed as a services and also who's got thew rights. You can start the service from there too [right click for pop up menu]. When in expanded view, you even have a small menu on left when clicking the BOINC service line, stop, start, restart... something to that effect. Curious to know if it bombs out too when doing a restart or start.

let us know.

PS the RebootPending.txt file is created during first clean install and then deleted upon boot. Conversely, some reported in past that to pester user to reboot and reboot and reboot... manually deleting the file to end this circle.

---

Coelum Non Animum Mutant, Qui Trans Mare Currunt

PS the RebootPending.txt file is created during first clean install and then deleted upon boot. Conversely, some reported in past that to pester user to reboot and reboot and reboot... manually deleting the file to end this circle.

His RebootPending.txt file is deleted, else there wouldn't be a message about it in stdoutgui.txt that it can't find the file specified.

For some help on what can cause error 0xc5, see this FAQ.

Also check in Event Viewer (Start->Administrative Tools->Event Viewer) if there are any notifications about what BOINC is doing. Do check Windows Logs->Applications for that.

---

Gosh, as if I did not see that... read again, I used the word "conversely"!

---

Coelum Non Animum Mutant, Qui Trans Mare Currunt

Yes, you said conversely, but you didn't make it clear whether or not his RebootPending.txt was deleted or not. Before toro goes on a fruitless search for this mythical file...

No need to feel attacked.

---

Let's see what the error message says:

Error: can't open file 'C:\Program Files\BOINC\\RebootPending.txt' (error 2: the system cannot find the file specified.)

BOINC creates it only in one place and it even spits out a path to go with it. Full marks to the coders to making it clear, to make goose chases superfluous... the nagging part though why it is reported as missing.

---

Coelum Non Animum Mutant, Qui Trans Mare Currunt

Because BOINC Manager can't know whether it is that boinc.exe isn't even running, or that it is but just behind a firewall. BOINC Manager isn't reading what's all in memory.

I think it can, because the client is setting a mutex "Global\\BoincSingleInstance". Normally from preventing it to start twice. Easy to check if it's running.

---

TThrottle The way to control your CPU and GPU temperature.
BoincTasks The best view of BOINC.
My other activities