Could you please check your internal CPID in client state XML (between <cross_project_id> and </cross_project_id>, when the "wrong" cpid shows up at the projects? I had this problem also, and my internal CPID looked like HASH("*****" ), which is not correct, it should be a 32 digit hexadecimal string. If this is the case, try upgrading to the newest BOINC version, perhaps it is resolved now. If not try mailing boinc_dev@ssl.berkeley.edu, to ask for progress on this bug. I got rid of it by completely uninstalling BOINC from both my computers and reinstalling it again, but perhaps this is not necessary.
Thanks a lot, for your response,
I have wait the time that CPID problem re appear. It is now, in daytime (more easy to try to understand), and first time i could look at the Client state xml with wrong cpid.
But the new cpid seems to be normally formed, a 32 digit hexadecimal, but it is different from usually and different from the cross_project_id i could read on my projects accounts website.
If i understand the <cross_project_id > but i am not sure
- it will be the same on all my project,
- i could read in clear on all the project website on my accounts
- it could be sometime different but only when i add a new project, and a synchronization occurs in few hours after
- if i have fews projects on the same unit, all projects stay synchronized and it will come back to precedent value.
Is it right ? Is somebody have an idea more ?
Philippe