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.

The Boinc Folder? Which Boinc Folder where you looking in? The Boinc Program Install Folder?,

Or the Boinc Data Folder? Which is where 'stderrdae.txt' would be.

Claggy

OK, glad it is fixed.
Yet any next time that you expect help from us, please do tell everything that you did. We're not looking over your shoulder, we're not holding your hand. We cannot see what you do or did. You will have to tell us.

That includes things such as deleting key files in or complete BOINC directories.

---

I had already said there was nothing there & that I had reinstalled BOINC several times & that I had done a Repair install of the OS already so it stands to reason that there would be either no stderrdae.txt or there would be nothing in it if it can't connect at all. Thanks for the help though anyway ...

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.

The Boinc Folder? Which Boinc Folder where you looking in? The Boinc Program Install Folder?,

Or the Boinc Data Folder? Which is where 'stderrdae.txt' would be.

Claggy

I've been with BOINC long enough to know where to look for Files ...

I had already said there was nothing there & that I had reinstalled BOINC several times & that I had done a Repair install of the OS already so it stands to reason that there would be either no stderrdae.txt or there would be nothing in it if it can't connect at all. Thanks for the help though anyway ...

False inference, I'm sorry to say.

stderrdae.txt, and its close cousin stdoutdae.txt, are written by the core client, boinc.exe

The client can be, and frequently is, running and logging messages into those files, irrespective of whether a BOINC manager or other monitoring tool is connected to display the same messages on screen.

As has been said already in this thread, you need to distinguish between the case where the core client fails to run, or starts and immediately crashes (in which case the log files are your friend), versus the case where the client is running properly, but the manager fails to connect to it (which is where the discussion about firewalls should start).

I'm having the same problem on a different box after switching from ATI Video Cards to NVIDIA Video Cards. ATI Drivers were Uninstalled & then the NVIDIA Drivers were installed but now the BOINC Client won't Connect. It appears the boinc.exe pops in & out of the Task Manager Window. What do you want from the stderrdae.txt ??? and from what part of it, there' no date or time so at the beginning or end of it do you need the info.

NOTE: I installed Client v6.12.1 and the Client Connected ... :) ... What happened to the Messages in this Version, now we get Notices, to cut down on over head ???

The Messages have been moved to another location accessed via the menu.
It was talked about some time ago, but I've forgotten where they went to.

The reason was to cut down on the panic/worry of new users on first seeing some of them and then thinking that there was something wrong.

The new Notices will contain news from projects and other sources that users need to know/should know about.

Your problem with not getting 'the other brand' of card recognized when changing from one to the other has also occurred before, and I thought that Un-install was sufficient.
As it's not, some one else will have to explain about it.

Messages are available via the Event Log in the Advanced menu.

---

The reason was to cut down on the panic/worry of new users on first seeing some of them and then thinking that there was something wrong.

I was Panicky & Worried when I didn't see any Messages lol ... ;)

I already found where they went to in the other menu as Jord said ...

What do you want from the stderrdae.txt ??? and from what part of it, there' no date or time so at the beginning or end of it do you need the info.

That's easy ;-)

Just rename or delete stderrdae.txt before starting BOINC, then all messages in the newly created one will be up to date.

Gruß,
Gundolf

What do you want from the stderrdae.txt ??? and from what part of it, there' no date or time so at the beginning or end of it do you need the info.

That's easy ;-)

Just rename or delete stderrdae.txt before starting BOINC, then all messages in the newly created one will be up to date.

Gruß,
Gundolf

I'll try & remember that if it happens again ...

Had the same thing happen on another Box Messing around switching Video Cards and a Update to the v6.12.1 Client fixed it. Even if I don't know what causes it at Least I have a fix for it if nothing else ... :)

Why 6.12.1 ?? That's a development version and an old one at that. We're already up to 6.12.4, with 6.12.5 coming in the pipeline (I expect it somewhere this week).

---

Ahh.
In regard to your problem with the video cards, there's this procedure which may help.

Why 6.12.1 ?? That's a development version and an old one at that. We're already up to 6.12.4, with 6.12.5 coming in the pipeline (I expect it somewhere this week).

I thought that was the latest one at the Download site when I checked for a dew Version of the Client, but I see now if I would have scrolled down a little further the 6.12.4 was there. I downloaded that one now but as long as 6.12.1 is working I'll just go with that for now. I was still on 6.10.57, I don't update that often & as long as things are working that's good enough for me.

I was still on 6.10.57...

Perhaps you should have tried the latest recommended version (6.10.58) first, before using a development version. :-)

Gruß,
Gundolf

...but as long as 6.12.1 is working I'll just go with that for now.

Perhaps it's wise to use http://boinc.berkeley.edu/download_all.php as the download page and nothing else. 6.12.1 may be working for what you want, but it has loads of bugs which 6.12.4 doesn't have, or in lesser form.

Ok, just make sure you upgrade to the next recommended 6.12 as soon as it's released (which should be soon).

---

I'm in the process of Updating them all to v6.12.4, that should do me until the 6.15.xx comes out ... lol

I'm in the process of Updating them all to v6.12.4, that should do me until the 6.15.xx comes out ... lol

v6.12.5 is out, working, and an improvement on v6.12.4 - until I can find the next bug ;-)

Easy there, kiddo. It's only on the 'not very public dl page'... wait until it's available on the download all page. :)

---