6.6.38 problems

Message boards : Questions and problems : 6.6.38 problems
Message board moderation

To post messages, you must log in.

Previous · 1 · 2

AuthorMessage
Profile Ageless
Volunteer moderator
Project administrator
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 29 Aug 05
Posts: 12104
Netherlands
Message 28022 - Posted: 15 Oct 2009, 8:57:14 UTC - in response to Message 28018.  
Last modified: 15 Oct 2009, 8:59:33 UTC

I am not sure what is going on but my boinc acount keeps being lost. I will create one then the next time I try to login it says that there is no account.

Where is this? In a browser on a project web site? Here on the BOINC Dev forums? Or in BOINC Manager->Attach to wizard?

Always check cookies, are they allowed for the web site?
Check script blockers in the browser, are the web sites allowed through?
Check the status of your CAPS LOCK. The email address is the unique factor, yet on many projects Alex@Home.xxx is not the same as alex@home.xxx

My new computer however keeps trying to connect but can't.

What, if any, error messages do you get?
Is BOINC (boinc.exe) allowed through the firewall on that computer? Boinc.exe needs access to the internet on TCP ports 80 and 443. For Windows Vista and above, Boinc.exe needs to be able to act as a server.

Boincmgr.exe, boinc.exe, boinctray.exe, boinccmd.exe and boinc.scr all need access through the local firewall as well, namely on TCP port 31416. This port is used to send RCPs to the various parts of BOINC, it's its way of communicating with its different parts.

Are you seeing the problems when you switch user accounts in Windows? Are those other accounts able to control BOINC through BOINC Manager (a setting in the installer).
Jord
Please do not private message me for tech support. Use the forums for that. Tech PMs will be ignored.
ID: 28022 · Report as offensive
Profile Ageless
Volunteer moderator
Project administrator
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 29 Aug 05
Posts: 12104
Netherlands
Message 28171 - Posted: 20 Oct 2009, 21:30:59 UTC
Last modified: 20 Oct 2009, 22:51:34 UTC

There is a 6.6.41 out which should have a fix for the zero bytes problem as well.


6.6.41 for Windows 32bit
6.6.41 for Windows 64bit
6.6.41 for Linux 32bit
6.6.41 for Linux 64bit
Jord
Please do not private message me for tech support. Use the forums for that. Tech PMs will be ignored.
ID: 28171 · Report as offensive
Dan Engholm

Send message
Joined: 23 Oct 09
Posts: 1
United States
Message 28273 - Posted: 23 Oct 2009, 15:23:23 UTC - in response to Message 28022.  
Last modified: 23 Oct 2009, 15:30:43 UTC

I am seeing behavior that fits the description of "can't connect," etc., using 6.6.38 on Windows XP. The problem is with the manager connecting to the client. It appears that the client (installed as a service) is crashing at startup.

- Unhandled Exception Record -
Reason: Access Violation (0xc0000005) at address 0x004350ED read attempt to address 0x00001CF0

--Dan


Followup: I just upgraded to 6.6.41 and the client has been running now for a few minutes. Before the upgrade, it died seconds after starting.
ID: 28273 · Report as offensive
Profile Ageless
Volunteer moderator
Project administrator
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 29 Aug 05
Posts: 12104
Netherlands
Message 28276 - Posted: 23 Oct 2009, 15:48:35 UTC - in response to Message 28273.  

Followup: I just upgraded to 6.6.41 and the client has been running now for a few minutes. Before the upgrade, it died seconds after starting.

Good, as the fix for that is in 6.6.41

The fix was first incorporated in the 6.10 range of BOINC, but it isn't ready for the grand public yet. So I asked Rom if he could release a newer 6.6 with this fix in it. Got my wish granted. :-)
Jord
Please do not private message me for tech support. Use the forums for that. Tech PMs will be ignored.
ID: 28276 · Report as offensive
Previous · 1 · 2

Message boards : Questions and problems : 6.6.38 problems

Copyright © 2017 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.