| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: BOINC Agent Support
Thread: Bionic won't connect! |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 13
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Good news. I followed all of Ageless's tips and I can now connect as the localhost. Now I just need to get connected to my projects. Here is the error I get in event viewer. I made sure that boinic.exe & boinicmgr.exe were closed before opening a new one, but it looks like it's saying an existing boinic is open???
The description for Event ID ( 1 ) in Source ( BOINC ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: BOINC error: 183, Another instance of BOINC is running. |
||
|
|
Jord
Advanced Cruncher Joined: Dec 30, 2005 Post Count: 148 Status: Offline Project Badges: 
|
Oh nice, that one. Well, double, triple check that boinc.exe isn't running. That BOINC Manager starts up multiple times isn't a problem. BOINC, the client can only start once.
----------------------------------------If you have BOINC installed as a service, exit it by stopping the service, either through services.msc or a command line command of net stop boinc Else try the simplest thing in the book: reboot the computer. That usually clears up whatever is stuck.
Tears in my eyes
How they fall like rain to the floor |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Oh nice, that one. Well, double, triple check that boinc.exe isn't running. That BOINC Manager starts up multiple times isn't a problem. BOINC, the client can only start once. If you have BOINC installed as a service, exit it by stopping the service, either through services.msc or a command line command of net stop boinc Else try the simplest thing in the book: reboot the computer. That usually clears up whatever is stuck. So I tried that with no luck. HOWEVER, I FIXED IT! Before I tried an uninstall, reboot and reinstall and still got the connection errors. This time I uninstalled, wiped my entire Program Files/Boinic folder, rebooted, and reinstalled. When I pulled up the WCG after the fresh install everything connected! Who knows what got corrupted in those files that were left over after the uninstalls before. Anyways thanks for all you help guys. Onto more crunching for science! |
||
|
|
|