Thanks for that.

---

Coelum Non Animum Mutant, Qui Trans Mare Currunt

Hello all...

im experiencing the same foult u guys do... i read the posts here but i cant find anythig wrong... its just stands idle or trying to "connecting to localhost".

i checked Boinc.exe its running, i tried shutting down antivirus & firewalls & started boinc again.. same result.

Before that i even put all programs under "trusted applications" in comodo internet security.

i tried regressing in earlier versions... that i know have worked... same shit :P

only get this in the stdrrdae.txt file


Unhandled Exception Detected...

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

Engaging BOINC Windows Runtime Debugger...

********************

and that other stdoutgui.txt file

13:13:17: Error: can't open file 'C:\Program\BOINC\\RebootPending.txt' (error 2: det går inte att hitta filen.)
[06/30/10 13:13:17] TRACE [4616]: init_asynch() boinc_socket: 776

[06/30/10 13:13:17] TRACE [4616]: init_asynch() connect: -1

[06/30/10 13:13:20] TRACE [4616]: init_poll(): sock = 776

strangely... couldnt find a stderrgfx.txt u mention in ur posts.

and heres some info from stdoutdae.txt

30-Jun-2010 13:13:17 [---] Starting BOINC client version 6.10.43 for windows_intelx86
30-Jun-2010 13:13:17 [---] log flags: file_xfer, sched_ops, task
30-Jun-2010 13:13:17 [---] Libraries: libcurl/7.19.7 OpenSSL/0.9.8l zlib/1.2.3
30-Jun-2010 13:13:17 [---] Data directory: C:\Documents and Settings\***** ******\Application Data\BOINC
30-Jun-2010 13:13:17 [---] Running under account ***** ******
30-Jun-2010 13:13:17 [---] Processor: 2 AuthenticAMD AMD Athlon(tm) 64 X2 Dual Core Processor 6000+ [Family 15 Model 67 Stepping 3]
30-Jun-2010 13:13:17 [---] Processor: 1.00 MB cache
30-Jun-2010 13:13:17 [---] Processor features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 htt pni cx16 syscall nx lm svm rdtscp 3dnowext 3dnow
30-Jun-2010 13:13:17 [---] OS: Microsoft Windows XP: Professional x86 Edition, Service Pack 3, (05.01.2600.00)
30-Jun-2010 13:13:17 [---] Memory: 2.00 GB physical, 35.72 GB virtual
30-Jun-2010 13:13:17 [---] Disk: 232.88 GB total, 220.36 GB free


also checked if boinc is running service - its not

dont know what to do... boinc has run problem free 90% of the time ive run it... and every time theres been a problem ive just regressed to the previous version and waited for the next one up n line to get released.

and trying out ur fixes hasnt worked :-(

Thanks!

i tried shutting down antivirus & firewalls & started boinc again.. same result.

Before that i even put all programs under "trusted applications" in comodo internet security.

Have you tried running without Comodo Internet Security, by means of uninstalling it and then seeing what BOINC does then?

I know, that can be a pain... but if things work out correctly with Comodo gone, then it isn't a BOINC problem, or some problem the developers here have to fix. Then it's Comodo who have to fix their program to work with this common software.

---

If you're running Comodo, ensure that BOINC is not being sandboxed. The sandbox is a virtual environment and BOINC will never work there.

The easiest way to bypass Comodo is to set the security level for anti-virus, firewall, Defense+ and sandbox each to 'disabled'; right click the Comodo icon in the system tray and navigate the context menu displayed.

I'm running Comodo and if you establish the correct internet and computer security rules it'll work fine; see the 'firewall' thread for suggestions on how to set it up.

Furthermore, anything that Comodo may be inderdicting with respect to BOINC will be evident in the Defense+ Events and in the Firewall Events logs. The former with respect to specific apps and the specific action attempted, the latter with respect to attempts to initiate network communication. The logs are extremely specific with regards to what exactly is being attempted and useful for diagnostic purposes.

Clearly the various components of BOINC need permission to perform the actions on the host, and secondly all the appropriate BOINC modules require network access to the internet (and internally), as necessary, for BOINC functionality.

For example, if a BOINC wants to connect to a project an essential function will be DNS lookup (resolving IP address from host name), it requires DNS Client Service access rights. Deny that and the firewall will never complain about BOINC attempting to establish UDP outbound to the DNS server destination port 53; the process will be blocked from even initiating a DNS internet connection. However, before it even gets to that point, BOINC needs to be able to talk amongst itself. This is essentially a networking issue pertaining to localhost, i.e., 0.0.0.0 to 127.0.0.1

Sounds like you and Comodo have to get to know each other better.

I'll chime is as another frustrated non-technical user with this problem.

I'm running:

- Windows XP Pro
- SAV 10.1 Corporate

I have local admin rights on the machine (a Dell Latitude D830).

When I start Boincmgr, Boinc.exe fires up for about 10 seconds and then dies. It does the same if I try to "attach to project or account manager". Strangely (to me), I'm no longer getting any messages from Boincmgr about localhost, but I had been getting those earlier in this battle.

The version of Boinc I'm running (or trying to run) is 6.10.56. I was running an earlier version when this problem started but that was a few weeks ago and I'm sorry, I don't remember what version it was. I also tried 6.10.57 and got the same problem. I've tried uninstalling and re-installing several times (and have rebooted). I removed BOINC using Windows (add/remove programs) rather than the Boinc install process, all to no avail.

I don't see anything interesting in the event viewer, but when I check the services running BOINC is missing.

I have no clue what to try next.

but when I check the services running BOINC is missing.

Did you even install BOINC as a service? (That's 3rd screen in the installer, Advanced button, checking the "Protected application execution" option)

If you never checked that, chances are high BOINC isn't installed as a service, so won't show up in the service applet.

Any error messages in stderrdae.txt or stderrgui.txt?

---

but when I check the services running BOINC is missing.

Did you even install BOINC as a service? (That's 3rd screen in the installer, Advanced button, checking the "Protected application execution" option)

If you never checked that, chances are high BOINC isn't installed as a service, so won't show up in the service applet.

Any error messages in stderrdae.txt or stderrgui.txt?

Hi Jord, sorry for the belated reply. When I subscribed to the thread I though it would send me an email so I didn't check back until today.

Re installing it as a service, you're right. I guess I didn't. There was a time when it took a fair amount of fiddling to get BOINC to run properly as a service, then one day a new release came out and it happened automatically. I assumed that was still the case. I don't necessarily care if it runs as a service, but in days of yore I think that was the only way to get it to run when I'm not logged in.

As far as stderrdae and stderrgui go, strangely enough they do not seem to exist on this machine. stderrgfx is there, but not the other two.

I must be doing something incredibly stupid, but I have no clue at all as to what it might be.

This site, as with all project sites, will only send you an email when a subscribed thread is updated, if you have enabled that option (to be notified) in your account on the (this) site.

This site, as with all project sites, will only send you an email when a subscribed thread is updated, if you have enabled that option (to be notified) in your account on the (this) site.

Got it. Thank's Les.

I ran the 6.10.58 install again and removed BOINC, then reinstalled. Boinc.exe keeps trying to start, I see it in Task Manager but it quickly disappears.

The only pertinent log entry through all of this are in the application log where it says twice that BOINC configuration completed successfully and then than BOINC installation completed successfully. All those are obviously during the install.

See Message 33534 in this same thread: ;-)

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?

namely stdoutdae.txt

Gruß,
Gundolf

I did a Windows search on drive C (my only drive) for anything named std*.txt. The only one found was the stdgrf.txt.

Meanwhile I removed again and installed 5.8.16. I picked the service option and it's running like a champ. I will do some more testing.

Oh, one more thing, all the std*.txt files are magically back.

I'm not making this up. :-)

OK. Getting somewhere.

I installed 6.6.38 and it worked fine.

I installed 6.10.58 and I'm back to the problem.

Did you reboot in between?

Is your windows explorer set to show hidden files/directories?

Gruß,
Gundolf

Did you reboot in between?

Is your windows explorer set to show hidden files/directories?

Gruß,
Gundolf

No and yes ... although I'll double check the latter when I get home tonight. Was a change made to hide them in more recent versions?

Also, I wasn't able to reproduce the earlier success in dropping back and making it work. I'll try to play with it more tonight and throw in some reboots here and there, but the whole process is so time consuming ... life always eventually interferes.

No and yes ... although I'll double check the latter when I get home tonight. Was a change made to hide them in more recent versions?

Windows does hide them, not BOINC.

Also, I wasn't able to reproduce the earlier success in dropping back and making it work. I'll try to play with it more tonight and throw in some reboots here and there, but the whole process is so time consuming ... life always eventually interferes.

That might be your problem. The newer BOINC versions create new users, which have to be enabled by a reboot. The BOINC user might not have the needed access rights to the BOINC directories.

Gruß,
Gundolf