33/4/2006 8:16:34 AM|SETI@home|Reason: To fetch work
3/4/2006 8:16:34 AM|SETI@home|Requesting 86400 seconds of new work
3/4/2006 8:16:39 AM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
3/4/2006 8:16:39 AM|SETI@home|General preferences have been updated
3/4/2006 8:16:39 AM||General prefs: from SETI@home (last modified 2006-03-04 07:58:28)
3/4/2006 8:16:39 AM||General prefs: using separate prefs for home
3/4/2006 8:16:39 AM|SETI@home|No work from project

Hi, I, too, have not been unable to download any new work since the outage the week of 27 February. I'm running a Dell with WinXP Pro, SP2 and current for all Windows auto updates. My older IBM laptop which runs WinXP Home, SP2 and current for all Windows auto updates is running Boinc 5.2.13 and is working just fine.

As a lot of hosts were without any WU's anymore or are asking for new WU’s, the splitters are very probably not able to respond to the demand. Things should come to normal in some 1 day or so. Just be patient and leave Boinc Manager handle the way it is doing. The problem will resolve by itself.

---

Read the News at the homepage
Have a look at the Technical News
Look if your question is not answered at the Boinc Wiki

Best greetings, Thierry

If you don't have a "boinc manager is unable to connect to boinc client"
Please do not post here as this Problem has to do with Boinc/Windows XP not Seti as I'm able to retrive units from other Projects useing the same Client under 2000
Something all Bionc'rs should do share your proccessing or Sit back and wait for berkeley to sort out the lab

connection problems are down to "the cleanup"

---

I'm Haveing this Problem too and I've been running Boinc Since Beta

Ive Actualy had it Twice the First Time I totaly Scrubbed Boinc from the Folder and Registry. I seem to think the prblem Lies in the Registry of XP

I think you're right.
I reinstalled BOINC just in case, and it didn't make any difference. The only way to get it to run seems to be : start the client manually, then run boincmgr.

Funnily enough, I'm having no problems (touch wood) with Windows Server 2003, which is basically a souped-up XP after all.

---

Try File, Select Computer, leave the options blank, and hit OK.

Ok here is the problem in simple terms. I try to connect to the BOINC Client and get (Boinc Manager - Connection Failed "boinc manager is unable to connect to boinc client" Would you like to try to connect again ?). I have tried the "File" "Select computer" and leaving the fields blank (trick) several times and NOTHING. I still get (Boinc Manager - Connection Failed "boinc manager is unable to connect to boinc client" Would you like to try to connect again ?) I have also tried entering my computers name and entering my password and still get (Boinc Manager - Connection Failed "boinc manager is unable to connect to boinc client" Would you like to try to connect again ?), I have opened the program with a text editor (and dont know how to read ASCII by the way) and done a search for the file "gui_rpc_auth.cfg" and only found 1 referance to it and there was NO password attached. I am completely at a loss here and cant figure out how to get the damn thing to just CONNECT.
I am using Windows XP - Home edition SP-2 (not XP Pro) with an Intel P-4 3.01GHz with 1GB Ram Using Version 5.2.13 of the BOINC Client

---

Try File, Select Computer, leave the options blank, and hit OK.

Ok here is the problem in simple terms. I try to connect to the BOINC Client and get (Boinc Manager - Connection Failed "boinc manager is unable to connect to boinc client" Would you like to try to connect again ?). I have tried the "File" "Select computer" and leaving the fields blank (trick) several times and NOTHING. I still get (Boinc Manager - Connection Failed "boinc manager is unable to connect to boinc client" Would you like to try to connect again ?) I have also tried entering my computers name and entering my password and still get (Boinc Manager - Connection Failed "boinc manager is unable to connect to boinc client" Would you like to try to connect again ?), I have opened the program with a text editor (and dont know how to read ASCII by the way) and done a search for the file "gui_rpc_auth.cfg" and only found 1 referance to it and there was NO password attached. I am completely at a loss here and cant figure out how to get the damn thing to just CONNECT.
I am using Windows XP - Home edition SP-2 (not XP Pro) with an Intel P-4 3.01GHz with 1GB Ram Using Version 5.2.13 of the BOINC Client

Have you tried this yet. Use windows explorer and look in the "boinc" directory for a file named "gui_rpc.cfg". Right click on it and open it in notepad. Highlight the line of characters in the file and copy it to the clipboard. Exit out of everything (and don't save the gui_rpc.cfg file!) and open boinc. Go to the "select computer screen and type "localhost" for the computer and paste the line you just copied into the password field.
Now it should connect. If you do not have a file named gui_rpc.cfg in your boinc directory simply open the computer select field and type "localhost" in the computer field and just click the mouse in the password field and hit "enter". This should connect and create the "gui_rpc.cfg" file. (This file actually contains your password for connecting to the client.)
If you have the "gui_rpc.cfg" file and follow the first step above and it doesn't connect, use windows explorer again and delete the existing gui_rpc.cfg file and use the second way above to connect and recreate the file with a good password in it.

---

Jim

Some people plan their life out and look back at the wealth they've had.
Others live life day by day and look back at the wealth of experiences and enjoyment they've had.

Have you tried this yet. Use windows explorer and look in the "boinc" directory for a file named "gui_rpc.cfg". Right click on it and open it in notepad. Highlight the line of characters in the file and copy it to the clipboard. Exit out of everything (and don't save the gui_rpc.cfg file!) and open boinc. Go to the "select computer screen and type "localhost" for the computer and paste the line you just copied into the password field.
Now it should connect. If you do not have a file named gui_rpc.cfg in your boinc directory simply open the computer select field and type "localhost" in the computer field and just click the mouse in the password field and hit "enter". This should connect and create the "gui_rpc.cfg" file. (This file actually contains your password for connecting to the client.)
If you have the "gui_rpc.cfg" file and follow the first step above and it doesn't connect, use windows explorer again and delete the existing gui_rpc.cfg file and use the second way above to connect and recreate the file with a good password in it.

Ok that doesnt work. I have checked the entire system including the regestry and can no existance of this file anywhere. Not sure what to do next.

---

Have you tried this yet. Use windows explorer and look in the "boinc" directory for a file named "gui_rpc.cfg". Right click on it and open it in notepad. Highlight the line of characters in the file and copy it to the clipboard. Exit out of everything (and don't save the gui_rpc.cfg file!) and open boinc. Go to the "select computer screen and type "localhost" for the computer and paste the line you just copied into the password field.
Now it should connect. If you do not have a file named gui_rpc.cfg in your boinc directory simply open the computer select field and type "localhost" in the computer field and just click the mouse in the password field and hit "enter". This should connect and create the "gui_rpc.cfg" file. (This file actually contains your password for connecting to the client.)
If you have the "gui_rpc.cfg" file and follow the first step above and it doesn't connect, use windows explorer again and delete the existing gui_rpc.cfg file and use the second way above to connect and recreate the file with a good password in it.

Ok that doesnt work. I have checked the entire system including the regestry and can no existance of this file anywhere. Not sure what to do next.

Ok, if that file does not exist then it has not been created yet. Open the process manager and see if the client is actually running. I'm on Linux but I believe the name in windows is boinccli.exe or something similar. If it's not running then start it up by hand. Then you should be able to start the boinc manager with the "localhost" in the computer field and "enter" in the password field. When it connects it will create the "gui_rpc.cfg" file with your password in it. Then you won't have to enter the information again. However if this program does not start for some reason or another no matter what you do you won't be able to connect.

---

Jim

Some people plan their life out and look back at the wealth they've had.
Others live life day by day and look back at the wealth of experiences and enjoyment they've had.

"gui_rpc.cfg" file

it's gui_rpc_auth.cfg

At all times close down BOINC completely before changing the gui_rpc_auth.cfg file. Make sure you quit BOINC when you run as a service. Closing Boinc Manager will not stop BOINC!

When saving the file through Notepad use the option to save all files, so it doesn't add .txt at the end. In case the file has .txt now, change it through Windows so it shows just .cfg

The file can either work with the 32 character hexadecimal (0 - 9 and a - f characters) password, or with a password you made yourself, or without any password.

For the without any password, try either:
- Delete the 32char password and save the file.
- Delete the 32char password, hit Enter and save the file.

The restart BOINC.

---

"gui_rpc.cfg" file

it's gui_rpc_auth.cfg

I knew that! It just seems I left my brain behind when I was typing it! Matter of fact, I ran into this same problem myself just yesterday. Thanks Ageless!

---

Jim

Some people plan their life out and look back at the wealth they've had.
Others live life day by day and look back at the wealth of experiences and enjoyment they've had.

"gui_rpc.cfg" file

it's gui_rpc_auth.cfg

I knew that! It just seems I left my brain behind when I was typing it! Matter of fact, I ran into this same problem myself just yesterday. Thanks Ageless!

well I finally got it to connect but I have to run and leave running the dos file boinc.exe in order to get the gui version to run and if I close the dos file I get disconnected and it wont reconnect until I restart the dos file =\\ .
seems a bit redundent to run it that way but its working so i guess I cant complain too much.

---

"gui_rpc.cfg" file

it's gui_rpc_auth.cfg

I knew that! It just seems I left my brain behind when I was typing it! Matter of fact, I ran into this same problem myself just yesterday. Thanks Ageless!

well I finally got it to connect but I have to run and leave running the dos file boinc.exe in order to get the gui version to run and if I close the dos file I get disconnected and it wont reconnect until I restart the dos file =\\ .
seems a bit redundent to run it that way but its working so i guess I cant complain too much.

Actually there is only one version of the "program". However it is in two parts. The "dos version" you are speaking of is actually the heart of boinc. It is the one that actually does the scheduling uploading downloading and other odds and ends, in other words *everything* about running the actual crunching programs. The "gui" version is just the "visible front end" control program for it. What you see on the screen only controls the other half. That's why that prograam must be running before the other will work.
You should set it up so that the "dos version" as you call it runs whenever you want it to. Either put it in your "start" menu if you only want it to run when you are logged on, or set it up to run as a service if you want it to run all the time your computer is on. If you want to start it manually, just create a shortcut to it on your desktop. Then you can start it by just clicking on the icon.
/edit/ BTW, it's a puzzle why the gui doesn't start the client. It should start the client when you start the gui! Oh well, put it in your start menu or service list and it will run whether the gui is active or not.

---

Jim

Some people plan their life out and look back at the wealth they've had.
Others live life day by day and look back at the wealth of experiences and enjoyment they've had.

/edit/ BTW, it's a puzzle why the gui doesn't start the client. It should start the client when you start the gui! Oh well, put it in your start menu or service list and it will run whether the gui is active or not.

It does start the daemon (boinc.exe) but later than the GUI starts. That's how come they don't communicate. For some (timing) reason, the GUI starts earlier than the daemon does, and then you have the problem!!

---

"gui_rpc.cfg" file

it's gui_rpc_auth.cfg

I knew that! It just seems I left my brain behind when I was typing it! Matter of fact, I ran into this same problem myself just yesterday. Thanks Ageless!

well I finally got it to connect but I have to run and leave running the dos file boinc.exe in order to get the gui version to run and if I close the dos file I get disconnected and it wont reconnect until I restart the dos file =\\ .
seems a bit redundent to run it that way but its working so i guess I cant complain too much.

Actually there is only one version of the "program". However it is in two parts. The "dos version" you are speaking of is actually the heart of boinc. It is the one that actually does the scheduling uploading downloading and other odds and ends, in other words *everything* about running the actual crunching programs. The "gui" version is just the "visible front end" control program for it. What you see on the screen only controls the other half. That's why that prograam must be running before the other will work.
You should set it up so that the "dos version" as you call it runs whenever you want it to. Either put it in your "start" menu if you only want it to run when you are logged on, or set it up to run as a service if you want it to run all the time your computer is on. If you want to start it manually, just create a shortcut to it on your desktop. Then you can start it by just clicking on the icon.
/edit/ BTW, it's a puzzle why the gui doesn't start the client. It should start the client when you start the gui! Oh well, put it in your start menu or service list and it will run whether the gui is active or not.

I too have found that I have to leave the DOS window active in order for the BOINC manager to stay connected. I can I make it so the DOS window can be closed and still stay connected? How do I make a shortcut to the DOS on the desktop, if I have to? I'm new at this so please don't spare any details.

---

I had this same problem, but it turned out to be ZoneAlarm that was causing the problem. I had to go in and manually set boinc.exe and boincmgr.exe to full internet and trusted zone access. After doing that, it worked fine.

---

Opps I just saw that this is a Windows forum.

---

I suddenly started getting error "boinc manager is unable to connect to boinc client".

I looked at the file edit listed above, but it didn't help.

I looked in Computer Management, Services and Applications, Services and saw that the BOINC service (client) was not started.

I tried to start it, but it would not start - logon failure.

I had set up the service with a specific local user. However, our IT department recently enforced strong passwords, and the BOINC user password was no longer adequate.

I reset the BOINC users password to something acceptable, and amended the BOINC service properties with the new password.

I was then able to start the BOINC service, and connect the BOINC manager to localhost.

All now working ok!

I suddenly started getting error "boinc manager is unable to connect to boinc client".

I looked at the file edit listed above, but it didn't help.

I looked in Computer Management, Services and Applications, Services and saw that the BOINC service (client) was not started.

I tried to start it, but it would not start - logon failure.

I had set up the service with a specific local user. However, our IT department recently enforced strong passwords, and the BOINC user password was no longer adequate.

I reset the BOINC users password to something acceptable, and amended the BOINC service properties with the new password.

I was then able to start the BOINC service, and connect the BOINC manager to localhost.

All now working ok!

The other solution would have been to set it to use the Local System account.

---

BOINC WIKI