That happens on the second computer under Window 10 Home on HP Pavilion Notebook. The first computer is Dell where it works perfectly.
Does it fix itself in time? They have instituted a delay in the startup of Boinc now and it can take seemingly forever to start showing that's it's connected and doing anything. Apparently there is so much going on with the pc when it first starts up, and when manually starting Boinc after the pc is running, that a delay was the best way to ensure it was working correctly. Boinc is shifted to a very low priority so other things happen first.
Anything in the boinc log? (C:\ProgramData\BOINC\stdoutdae.txt) Or does any other file in the C:\ProgramData\BOINC folder get updated when the error occurs?
Is the file C:\ProgramData\BOINC\gui_rpc_auth.cfg present?
C:\ProgramData\BOINC is where boinc keeps its data on MY computer. Might be different on yours.
Only thing I can think of now is that the windows firewall is preventing the GUI program (that is what you see on the screen) from connecting to the core program (that runs in the background).
This communication is done over TCP port 31416. Check if your firewall rules somehow disallows the boinc core program from listening to this port. You might also try to add a firewall rule explicitly allowing the core program to listen to this port.
I suppose we ought to check for the obvious precondition first - is the Core Client (boinc.exe) running on that computer? Look in the list of running processes in Windows Task Manager, and check that boinc.exe is there.
(The BOINC Manager tries to start the client at logon, but can only 'connect' to it once it has started running properly)
Sasha_11 wrote:That happens
)
Does it fix itself in time? They have instituted a delay in the startup of Boinc now and it can take seemingly forever to start showing that's it's connected and doing anything. Apparently there is so much going on with the pc when it first starts up, and when manually starting Boinc after the pc is running, that a delay was the best way to ensure it was working correctly. Boinc is shifted to a very low priority so other things happen first.
It's already more than
)
It's already more than week.
...same User Login as by the
)
...same User Login as by the Install of the Manager? Ver.: 7.6.22 32 or 64 Bit!?
Otherwise uninstall the Manager, reboot, install for all Users, not as a Service! You don't loose any WU's. ;-)
BR
Greetings from the North
>...same User Login as by
)
>...same User Login as by the Install of the Manager? Ver.: 7.6.22 32 or 64 Bit!?
Yes - all the same
Anything in the windows event
)
Anything in the windows event log?
Anything in the boinc log? (C:\ProgramData\BOINC\stdoutdae.txt) Or does any other file in the C:\ProgramData\BOINC folder get updated when the error occurs?
Is the file C:\ProgramData\BOINC\gui_rpc_auth.cfg present?
C:\ProgramData\BOINC is where boinc keeps its data on MY computer. Might be different on yours.
Reinstalled Boinc Manager and
)
Reinstalled Boinc Manager and tried again. Got the following:
Unable to connect to the core client,
Message box: Boinc Manager has exited unexpectedly 3 times within the last 3 minutes.
C:\ProgramData\BOINC:
stderrdae.txt, stderrgpudetect.txt, stdoutdae.txt -all have 0 length.
stdoutgpudetect.txt contains:
26-Oct-2016 23:45:15 [---] cc_config.xml not found - using defaults
Haven't found BOINC-related Windows log.
Only thing I can think of now
)
Only thing I can think of now is that the windows firewall is preventing the GUI program (that is what you see on the screen) from connecting to the core program (that runs in the background).
This communication is done over TCP port 31416. Check if your firewall rules somehow disallows the boinc core program from listening to this port. You might also try to add a firewall rule explicitly allowing the core program to listen to this port.
Added BOINC to firewall list
)
Added BOINC to firewall list of permitted apps, then turned firewall off - both didn't help.
Could the wireless router be the problem?
I suppose we ought to check
)
I suppose we ought to check for the obvious precondition first - is the Core Client (boinc.exe) running on that computer? Look in the list of running processes in Windows Task Manager, and check that boinc.exe is there.
(The BOINC Manager tries to start the client at logon, but can only 'connect' to it once it has started running properly)
That's right. There ara no
)
That's right. There ara no Boinc.exe.