I've exited the client, ended the processes in task manager, and started the client. I've also loaded the "read config file" from the client and I still do not have anything in my stdoutdate.

My config file is indeed in the data_dir. (located in ProgramData\BOINC.. not program files...)

There is no event log view at the start of the client.

I've exited the client, ended the processes in task manager, and started the client. I've also loaded the "read config file" from the client and I still do not have anything in my stdoutdate.

My config file is indeed in the data_dir. (located in ProgramData\BOINC.. not program files...)

There is no event log view at the start of the client.

How did you exit the client? and How did you start the client?

How did you do a 'read config file' from the client?, You can do that from Boinc Manager, you can't do from the boinc client (not directly anyway)

Restart your PC, and when Boinc Manager (the GUI) is up and running, tell us what Boinc programs are running in Task Manager, and what project applications (if any) are running.

Claggy

yes the manager is what I mean...

advanced >> read config file

I restart my PC daily. Ever single time it boots, in the system tray, the BOINC manager has a red circle (more like a dot) that says "Connecting to localhost" and it never, ever, ever changes... ever.

these three are running in task manager

BOINC.exe
BOINCMGR.exe
BOINCTRAY.exe

yes the manager is what I mean...

advanced >> read config file

I restart my PC daily. Ever single time it boots, in the system tray, the BOINC manager has a red circle (more like a dot) that says "Connecting to localhost" and it never, ever, ever changes... ever.

these three are running in task manager

BOINC.exe
BOINCMGR.exe
BOINCTRAY.exe

The manager and client are both running but the red dot and the "Connecting to localhost" means the manager is unable to connect to the client. The client is the thing that reads the config file, not the manager. Clicking advanced >> read config file merely tells the manager to tell the client to read the config but if manager isn't connected to client then the client never receives the command and will thus not read the config file. It will read the config file whenever it starts but that's all.

So the question is why the manager cannot connect to the client. Maybe something to do with permissions is blocking the connection? The two connect and communicate on port 31416. Is that port blocked in your firewall or anti-virus software or anything?

Also, you could kill the client via Task Manager then open a command prompt and run the client that way. Unless it hangs or goes berserk it will then log messages to the screen where you will be able to read them. If I understand correctly that is part of the problem... you can't read the log messages... and I have a hunch the client is hanging before it starts logging and before it opens port 31416 and is able to connect with manager.

So do something like the following in the command prompt/console/terminal:

cd "c:\program files\boinc"
boinc.exe

and then see what you get (or don't get) for messages on the screen.

Another possibility is that BOINC's registry entries are munged. The path to the data dir is stored there. If it's munged then boinc.exe (the client) could be looking at a different data directory or a directory that doesn't exist which could be causing it to hang or simply wait and do nothing so you could also add the parameter to the above command to point to the data dir or check the registry entries to see if the correct path to the data dir is contained therein.

bump

" the BOINC manager has a red circle (more like a dot) that says "Connecting to localhost" and it never, ever, ever changes... ever."

Which is the answer as to why you are not seeing anything in BOINC Manager, but if the right BOINC.exe is running, there would nevertheless be entries in the stdoutdae.txt file.


Open a command window, navigate to where the boinc.exe is installed and do a

boinccmd --read_cc_config

The manual: http://boinc.berkeley.edu/wiki/Boinccmd

If the core client is running you would get a confirmation,

retval 0

which logged in my stdoutdae.txt with the sampled lines I posted before.

Else, your install is borged... maybe there are 2 installations / data_dirs on the system... it's possible.

---

Coelum Non Animum Mutant, Qui Trans Mare Currunt

I get

"can't connect to local host" (in the command prompt)

There are not two data dirs on my system.

bump

bump

Try Boinc 7.0.52, if you can't get that to work eithier, i'd uninstall Boinc, delete the Boinc Data directory, and do a fresh install, and attach to your projects afresh,
you could always revert to your old host id's by following this FAQ:

How to revert to an older HostID number?

Claggy

bump

Try Boinc 7.0.52, if you can't get that to work eithier, i'd uninstall Boinc, delete the Boinc Data directory, and do a fresh install, and attach to your projects afresh,
you could always revert to your old host id's by following this FAQ:

How to revert to an older HostID number?

Claggy

Done. Still did not fix the issue.

bump

Try Boinc 7.0.52, if you can't get that to work eithier, i'd uninstall Boinc, delete the Boinc Data directory, and do a fresh install, and attach to your projects afresh,
you could always revert to your old host id's by following this FAQ:

How to revert to an older HostID number?

Claggy

Done. Still did not fix the issue.

Details please, how much of that did you do?, what client version did you install? x86 or x64? what directories did they install to?

Claggy

bump

Try Boinc 7.0.52, if you can't get that to work eithier, i'd uninstall Boinc, delete the Boinc Data directory, and do a fresh install, and attach to your projects afresh,
you could always revert to your old host id's by following this FAQ:

How to revert to an older HostID number?

Claggy

Done. Still did not fix the issue.

Details please, how much of that did you do?, what client version did you install? x86 or x64? what directories did they install to?

Claggy

I uninstalled, deleted my data dir, installed 7.0.52 x86, it put BOINC in C:\Program Files\BOINC
and my data dir is in
C:\ProgramData\BOINC

bump

Try Boinc 7.0.52, if you can't get that to work eithier, i'd uninstall Boinc, delete the Boinc Data directory, and do a fresh install, and attach to your projects afresh,
you could always revert to your old host id's by following this FAQ:

How to revert to an older HostID number?

Claggy

Done. Still did not fix the issue.

Details please, how much of that did you do?, what client version did you install? x86 or x64? what directories did they install to?

Claggy

I uninstalled, deleted my data dir, installed 7.0.52 x86, it put BOINC in C:\Program Files\BOINC
and my data dir is in
C:\ProgramData\BOINC

The x86 version should be installed to C:\Program Files (x86)\BOINC and not C:\Program Files\BOINC which is for the 64bit version. (on a 64bit OS)

You did say you had a 64bit OS, so you should uninstall the x86 version and install the x64 version:

I doubt my PC specs are the problem here.
Intel/i7 920/OCed at 3.2Ghz, Ati /5900 series/ 12 GB of RAM, Win Vista 64 bit

Claggy

bump

Try Boinc 7.0.52, if you can't get that to work eithier, i'd uninstall Boinc, delete the Boinc Data directory, and do a fresh install, and attach to your projects afresh,
you could always revert to your old host id's by following this FAQ:

How to revert to an older HostID number?

Claggy

Done. Still did not fix the issue.

Details please, how much of that did you do?, what client version did you install? x86 or x64? what directories did they install to?

Claggy

I uninstalled, deleted my data dir, installed 7.0.52 x86, it put BOINC in C:\Program Files\BOINC
and my data dir is in
C:\ProgramData\BOINC

The x86 version should be installed to C:\Program Files (x86)\BOINC and not C:\Program Files\BOINC which is for the 64bit version. (on a 64bit OS)

You did say you had a 64bit OS, so you should uninstall the x86 version and install the x64 version:

I doubt my PC specs are the problem here.
Intel/i7 920/OCed at 3.2Ghz, Ati /5900 series/ 12 GB of RAM, Win Vista 64 bit

Claggy

OK I've now tried both iterations of the 7.0.52 and 7.0.28.

I've been following this thread since its inception and I must state that you are a frustrating person to help. Look, the people who have tried to help you so far, I commend them for it, but as you continue to post non-info back at them, I'm sure you'll find that eventually all help will dry up.

And here's the thing, the guys trying to help you aren't the ones having the problem. You have the problem, so you will have to inform the people trying to help you with all possible details on what you did. Even if that means that you post a step by step course of the things that you tried.

I see the last Claggy posted was advising you to uninstall the 32bit version of BOINC and install the 64bit version. Nothing in your post following his shows which version you tried. Perhaps that it's all clear for you, but here's the thing, we're not in the same room as you when you do things, we don't see what you do. You will have to tell us. If not, expect help to taper off and you being stuck with the problem until luck plays out.

---

OK I've now tried both iterations (32 bit and 64 bit) of the 7.0.52 and 7.0.28.

I currently have the 64 bit version of 7.0.28 installed in C:\Program Files\BOINC. "Connecting to local host" for ∞

What kind of firewall program do you use?
Have you specifically allowed both boincmgr.exe and boinc.exe through the firewall, on the private network?

---

What kind of firewall program do you use?
Have you specifically allowed both boincmgr.exe and boinc.exe through the firewall, on the private network?

I don't use any firewall software (windows firewall is turned off). I have a router though.

Please open a command line window (Start->All Programs->Accessories->Command prompt.)
Next start both BOINC.exe and BOINCMGR.exe
Next open Windows Explorer and check if there's a TMP directory in C:, if there isn't make one. TMP, not TEMP.

Next, in the command line window, type: netstat -an >> C:\tmp\netstat.txt and hit Return.

Next open C:\TMP\netstat.txt and post its contents here without editing anything in it.

---

Active Connections

Proto Local Address Foreign Address State
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
TCP 0.0.0.0:554 0.0.0.0:0 LISTENING
TCP 0.0.0.0:2869 0.0.0.0:0 LISTENING
TCP 0.0.0.0:5357 0.0.0.0:0 LISTENING
TCP 0.0.0.0:10243 0.0.0.0:0 LISTENING
TCP 0.0.0.0:17500 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49152 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49153 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49154 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49157 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49160 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49161 0.0.0.0:0 LISTENING
TCP 0.0.0.0:61472 0.0.0.0:0 LISTENING
TCP 127.0.0.1:19872 127.0.0.1:49180 ESTABLISHED
TCP 127.0.0.1:39123 0.0.0.0:0 LISTENING
TCP 127.0.0.1:49180 127.0.0.1:19872 ESTABLISHED
TCP 127.0.0.1:49816 0.0.0.0:0 LISTENING
TCP 127.0.0.1:49816 127.0.0.1:49825 ESTABLISHED
TCP 127.0.0.1:49817 0.0.0.0:0 LISTENING
TCP 127.0.0.1:49825 127.0.0.1:49816 ESTABLISHED
TCP 127.0.0.1:50699 127.0.0.1:31416 SYN_SENT
TCP 192.168.1.138:139 0.0.0.0:0 LISTENING
TCP 192.168.1.138:2869 192.168.1.108:35841 TIME_WAIT
TCP 192.168.1.138:49175 204.236.136.111:443 CLOSE_WAIT
TCP 192.168.1.138:49192 204.236.136.111:443 CLOSE_WAIT
TCP 192.168.1.138:49219 204.236.140.85:443 CLOSE_WAIT
TCP 192.168.1.138:49221 204.236.140.85:443 ESTABLISHED
TCP 192.168.1.138:49227 173.194.68.125:5222 ESTABLISHED
TCP 192.168.1.138:49262 205.158.153.149:5222 ESTABLISHED
TCP 192.168.1.138:49263 199.47.218.150:80 ESTABLISHED
TCP 192.168.1.138:49272 208.88.178.49:25999 ESTABLISHED
TCP 192.168.1.138:49275 205.158.153.164:5222 ESTABLISHED
TCP 192.168.1.138:49284 205.188.8.207:443 ESTABLISHED
TCP 192.168.1.138:49289 64.12.104.224:443 ESTABLISHED
TCP 192.168.1.138:49290 205.188.13.70:443 ESTABLISHED
TCP 192.168.1.138:49554 23.3.106.155:80 TIME_WAIT
TCP 192.168.1.138:49573 74.125.226.214:443 ESTABLISHED
TCP 192.168.1.138:49574 173.194.75.147:443 ESTABLISHED
TCP 192.168.1.138:49578 173.194.68.125:5222 ESTABLISHED
TCP 192.168.1.138:49592 173.194.43.5:443 ESTABLISHED
TCP 192.168.1.138:49610 173.194.43.38:443 ESTABLISHED
TCP 192.168.1.138:49712 74.125.226.199:80 ESTABLISHED
TCP 192.168.1.138:49818 67.228.168.216:80 ESTABLISHED
TCP 192.168.1.138:49852 173.194.67.120:443 ESTABLISHED
TCP 192.168.1.138:50040 216.52.242.80:80 TIME_WAIT
TCP 192.168.1.138:50055 23.48.113.244:80 TIME_WAIT
TCP 192.168.1.138:50056 23.48.113.244:80 TIME_WAIT
TCP 192.168.1.138:50058 23.48.113.244:80 TIME_WAIT
TCP 192.168.1.138:50059 23.48.113.244:80 TIME_WAIT
TCP 192.168.1.138:50060 23.48.113.244:80 TIME_WAIT
TCP 192.168.1.138:50071 23.48.116.163:80 TIME_WAIT
TCP 192.168.1.138:50100 216.52.242.80:443 TIME_WAIT
TCP 192.168.1.138:50269 217.18.19.155:443 CLOSE_WAIT
TCP 192.168.1.138:50318 74.125.226.229:443 ESTABLISHED
TCP 192.168.1.138:50352 23.3.106.8:443 ESTABLISHED
TCP 192.168.1.138:50376 173.194.43.8:80 ESTABLISHED
TCP 192.168.1.138:50381 74.125.226.207:80 ESTABLISHED
TCP 192.168.1.138:50415 74.125.226.197:80 ESTABLISHED
TCP 192.168.1.138:50430 23.48.222.185:80 ESTABLISHED
TCP 192.168.1.138:50431 74.125.226.230:80 TIME_WAIT
TCP 192.168.1.138:50432 74.125.226.230:80 TIME_WAIT
TCP 192.168.1.138:50436 74.125.226.198:80 ESTABLISHED
TCP 192.168.1.138:50437 74.125.226.198:80 ESTABLISHED
TCP 192.168.1.138:50438 74.125.226.198:80 ESTABLISHED
TCP 192.168.1.138:50447 184.25.109.88:80 ESTABLISHED
TCP 192.168.1.138:50449 207.171.163.131:443 ESTABLISHED
TCP 192.168.1.138:50450 205.251.251.109:80 CLOSE_WAIT
TCP 192.168.1.138:50452 184.25.109.120:80 ESTABLISHED
TCP 192.168.1.138:50453 184.25.109.88:80 ESTABLISHED
TCP 192.168.1.138:50454 184.25.109.88:80 ESTABLISHED
TCP 192.168.1.138:50455 184.25.109.88:80 ESTABLISHED
TCP 192.168.1.138:50456 184.25.109.88:80 ESTABLISHED
TCP 192.168.1.138:50457 184.25.109.88:80 ESTABLISHED
TCP 192.168.1.138:50479 204.93.223.148:80 TIME_WAIT
TCP 192.168.1.138:50480 204.93.223.148:80 TIME_WAIT
TCP 192.168.1.138:50481 205.251.251.29:80 TIME_WAIT
TCP 192.168.1.138:50482 205.251.251.29:80 TIME_WAIT
TCP 192.168.1.138:50483 205.251.251.29:80 TIME_WAIT
TCP 192.168.1.138:50488 205.188.28.118:80 ESTABLISHED
TCP 192.168.1.138:50490 69.194.36.221:80 TIME_WAIT
TCP 192.168.1.138:50491 72.21.81.253:80 TIME_WAIT
TCP 192.168.1.138:50492 72.21.81.253:80 ESTABLISHED
TCP 192.168.1.138:50538 65.55.13.90:80 ESTABLISHED
TCP 192.168.1.138:50539 184.25.108.9:80 ESTABLISHED
TCP 192.168.1.138:50541 157.56.77.156:443 ESTABLISHED
TCP 192.168.1.138:50543 184.25.108.56:80 ESTABLISHED
TCP [::]:135 [::]:0 LISTENING
TCP [::]:445 [::]:0 LISTENING
TCP [::]:554 [::]:0 LISTENING
TCP [::]:2869 [::]:0 LISTENING
TCP [::]:5357 [::]:0 LISTENING
TCP [::]:10243 [::]:0 LISTENING
TCP [::]:49152 [::]:0 LISTENING
TCP [::]:49153 [::]:0 LISTENING
TCP [::]:49154 [::]:0 LISTENING
TCP [::]:49157 [::]:0 LISTENING
TCP [::]:49160 [::]:0 LISTENING
TCP [::]:49161 [::]:0 LISTENING
UDP 0.0.0.0:123 *:*
UDP 0.0.0.0:500 *:*
UDP 0.0.0.0:1900 *:*
UDP 0.0.0.0:3702 *:*
UDP 0.0.0.0:3702 *:*
UDP 0.0.0.0:4500 *:*
UDP 0.0.0.0:5004 *:*
UDP 0.0.0.0:5005 *:*
UDP 0.0.0.0:5355 *:*
UDP 0.0.0.0:17500 *:*
UDP 0.0.0.0:56390 *:*
UDP 0.0.0.0:56391 *:*
UDP 0.0.0.0:56392 *:*
UDP 0.0.0.0:56393 *:*
UDP 0.0.0.0:56394 *:*
UDP 0.0.0.0:56395 *:*
UDP 0.0.0.0:56396 *:*
UDP 0.0.0.0:56397 *:*
UDP 0.0.0.0:56398 *:*
UDP 0.0.0.0:56399 *:*
UDP 0.0.0.0:56400 *:*
UDP 0.0.0.0:56401 *:*
UDP 0.0.0.0:56402 *:*
UDP 0.0.0.0:56403 *:*
UDP 0.0.0.0:56404 *:*
UDP 0.0.0.0:56405 *:*
UDP 0.0.0.0:56406 *:*
UDP 0.0.0.0:56407 *:*
UDP 0.0.0.0:56408 *:*
UDP 0.0.0.0:56409 *:*
UDP 0.0.0.0:57674 *:*
UDP 0.0.0.0:57675 *:*
UDP 0.0.0.0:61451 *:*
UDP 0.0.0.0:64078 *:*
UDP 127.0.0.1:1900 *:*
UDP 127.0.0.1:41242 *:*
UDP 127.0.0.1:44301 *:*
UDP 127.0.0.1:45454 *:*
UDP 127.0.0.1:52327 *:*
UDP 127.0.0.1:53654 *:*
UDP 127.0.0.1:55293 *:*
UDP 127.0.0.1:57984 *:*
UDP 127.0.0.1:57985 *:*
UDP 127.0.0.1:58199 *:*
UDP 127.0.0.1:58200 *:*
UDP 127.0.0.1:58201 *:*
UDP 127.0.0.1:58202 *:*
UDP 127.0.0.1:58232 *:*
UDP 127.0.0.1:58233 *:*
UDP 127.0.0.1:58242 *:*
UDP 127.0.0.1:58243 *:*
UDP 127.0.0.1:61464 *:*
UDP 127.0.0.1:61465 *:*
UDP 127.0.0.1:61489 *:*
UDP 192.168.1.138:137 *:*
UDP 192.168.1.138:138 *:*
UDP 192.168.1.138:1900 *:*
UDP 192.168.1.138:61463 *:*
UDP [::]:123 *:*
UDP [::]:500 *:*
UDP [::]:3702 *:*
UDP [::]:3702 *:*
UDP [::]:5004 *:*
UDP [::]:5005 *:*
UDP [::]:5355 *:*
UDP [::]:61452 *:*
UDP [::1]:1900 *:*
UDP [::1]:61461 *:*
UDP [fe80::100:7f:fffe%12]:1900 *:*
UDP [fe80::100:7f:fffe%12]:61462 *:*
UDP [fe80::a2:3c4f:4b6f:9b14%10]:1900 *:*
UDP [fe80::a2:3c4f:4b6f:9b14%10]:61460 *:*
UDP [fe80::f8ad:4364:3644:ba8b%11]:1900 *:*
UDP [fe80::f8ad:4364:3644:ba8b%11]:61459 *:*