Message boards : Questions and problems : Boinc will not connect to Client-Local Host
Message board moderation
Previous · 1 · 2
Author | Message |
---|---|
Send message Joined: 20 Dec 07 Posts: 1069 |
I have installed the following application: That's still the wrong place to be installed. You'll either have to set the destination directory manually in the installer or have to delete anything concerning BOINC from the registry before installing. Gruß, Gundolf |
Send message Joined: 10 Dec 11 Posts: 12 |
removed all entries in register. removed all components from computer. tried to reinstall, got a message that the file was corrupt. deleted that file, downloaded installer again. got message that the installer was corrupt. downloaded the 32 bit version. boinc.6.12.34_windows_intelx86.exe Installing this file to c:\program files (x86)\BOINC\ Data directory C:\ProgramData\BOINC Get a popup during installation: Error 1714: The older version of BOINC cannot be removed. Contact your technical support group. Installation cancelled. I'm about ready to give up. there is now no version of BOINC on my computer, other than the installer |
Send message Joined: 29 Aug 05 Posts: 15554 |
|
Send message Joined: 29 Aug 05 Posts: 15554 |
Now I finally have a clear head. The 64bit version of BOINC when installed in the 32bit Program Files directory will then not start up, and give exactly these problems. That's the boinc_*.*.*_windows_x86_64.exe version, when installed to C:\Program Files (x86)\BOINC\ will it give exactly these symptoms. The 32bit version can be installed to and run from the 32bit and the 64bit Program Files directories without problems. |
Send message Joined: 10 Dec 11 Posts: 12 |
Sigh... followed the link you sent. Followed all the instructions. downloaded the installer cleaner and found no errors. checked windows event viewer, no errors. ran the boinc cleaner, rebooted. downloaded the 32 bit version, tried to install... received the same error 1714 older version cannot be removed. |
Send message Joined: 29 Aug 05 Posts: 15554 |
I suspect it's a corrupt Windows registry entry. You did clean out all the old BOINC.msi files? You may have to clean out the registry on mention of any of that as well, so open regedit, select Computer (at the total top), then press CTRL + F, type in BOINC.msi and click Find Next. Delete all entries that it comes up with. You can continue searching by pressing F3. Just to make sure, prior to starting the installation, you did delete the registry entries at: HKEY_CURRENT_USER\Software\Space Sciences Laboratory, U.C. Berkeley ? HKEY_LOCAL_MACHINE\SOFTWARE\Space Sciences Laboratory, U.C. Berkeley ? |
Send message Joined: 10 Dec 11 Posts: 12 |
I cleaned out the registry before the last install... checked it again to be sure this time, no entries of boinc at all. Went through each step again, with same results. |
Send message Joined: 10 Dec 11 Posts: 12 |
no new suggestions? |
Send message Joined: 28 May 10 Posts: 52 |
Hi, I had the same problem on my mainsys. I reinstalled windows two weeks ago, using a SSD as main drive. Since my system showed these symptoms after the new installation, I assumed some problems with the installation, not with BM. I followed the steps described here. I could close all tasks using the task manager, then I started the BOINC installer with the repair option, afterwards it worked - until I restarted my system. What I found was, that my system had no entry in the windows firewall. I made this manually, restarting the pc then. This time it worked, but I will have an eye on that. There is also a thread in the MW forum http://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=2639 if someone is interested in. If it happens again I can offer full acces to my system for one of the forum mods. I keep you informed. Alexander |
Send message Joined: 28 May 10 Posts: 52 |
This morning everthing started well. Looks like there are sometimes problems with the entries in the firewall. |
Send message Joined: 15 Nov 12 Posts: 2 |
Hi i am trying to get boinc going on my sons computer and he has child locks on his log in.Does any one know if i can get around this? I have set the fire wall to let it go and it is not showing up on the restricted list. Thank you for any help John |
Send message Joined: 8 Mar 07 Posts: 115 |
Hey there, -- Not sure if this will solve the child lock, but... Here is how I got it to run under x64 vista I created a link on my desktop to the BoincMGR. Then, I right click on the icon and choose: Run as administrator. Then it started Boinc client and Manager. Jay |
Send message Joined: 15 Nov 12 Posts: 2 |
thank you for your reaply. I tried your sugestion and olso gave exseptions to the 4 exe programs that i found and had it going. Then the next time he started his computer i am back to square 1. He also has his own login which is not helping i dont think. I will have another go tonight. any other sugestions anybody ta. Thank you John |
Send message Joined: 3 Dec 12 Posts: 15 |
I had a very similar experience in Linux. If you are sure its not a port/firewall issue check to be sure the boinc-client is running. In my case the problem had to do with gui_rpc_auth.cfg file that gets installed with BOINC. In my case I had two files installed. Both contained an alpha-numeric string. This string is your BOINC password. In the Linux version go into the BOINC manager -> Advanced tab > Select Computer (should be same for Win I think). This will bring up a short menu wanting a user and passwd. Use "localhost" for user and the long alpha-numeric string in the gui_rpc_auth.cfg file. If that does not work and you have other files with this name try the string in each one of these files. One should work. You can look at my write up at http://www.usefulramblings.org/?page_id=3082 if you wish. It written for Linux but might give some insight. Hope this helps, Ron www.usefulramblings.org |
Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License,
Version 1.2 or any later version published by the Free Software Foundation.