Bun Bun,

If you had a backup, and restored that prior to re-installation of BOINC [doing this with internet unplugged, to include confirming BOINC had found old data], AND nothing else changed on that system, host network ID same etc, but the HD maybe. WCG would have recognized the return of an old known friend. I've got a laptop, which went from XP OEM, to clean Vista, to clean W7 and it's still going strong [when I let it run].

95711 work 12/27/2006 18:29:04

To top this, I'm using network ID suppress, so WCG only gets the BOINC ID 95711 transmitted, not what the host in network ID is known as.

Doubt, scratching the install, clean registry too, and redoing with aforementioned tips, will make it work, but you could try. Else, it's a lost cause. No reconnect/merge.... on the wish list, but not on the To Do [AFAIK].

--//--

snip:
The RPC is not important in this case [if the servers had auto-recognized the device from the record). It is in respect to data syncing. If the 2 are out, because you put an old backup in place, the server scrubs what's on the client and sends a fresh result set. Done this, and witnessed the erasure. Key is the off-line restoring and only when you are happy that BOINC is running proper [off the old backup], then the old=new works. Mind you, my router is set up to always assign the same internal IP to the same device [automatically]... think that is the weakest link in the matter. Anyway, the prerequisites are described in this Wiki http://boinc.berkeley.edu/wiki/Host_identification_and_merging (I wrote that bit ;>)

Want personal assistance: write to support@worldcommunitygrid.org or find the "contact us" link on WCG home page.

--//--

Just curious here, but is your computer "named" the same as it was previously?

Also, why not just reinstall and reattach to said project here? If the computer has the identical name as it was previously, and you reinstall boinc and reattach, I don't see why it would not work. I did this with a brand new hdd and redownloaded/reinstalled boinc, reattached to wcg, and all worked just fine. I just let the few WU's I was working on go to other crunchers (when my hdd crashed). No problems here by using this method. Considering how much time has passed since you first posted, I'd have thought by now you'd have tried this simple method. :)

As I said before. Nothing else changed. Only my raid array which the BOINC folder resided on crashed. My OS drive remained intact. I have copied my BOINC data folder from format to format on the same hardware but I have always stopped it before and started it after with the same data. Never before has this happened.

I didn't even reinstall boinc initially. My raid arrary crashed (though the OS still saw it nothing was actually written to disc) and BOINC kept running like this for a few days. When I rebuilt the array after restarting the computer BOINC went and grabbed a new hostID. Now nothing I do can bring it back to that original hostID. I have tried reinstalling BOINC and copying over the BOINC data folder from a backup but it either grabs another new hostID or uses one of the ones it made in the past week.

I emailed that support e-mail above but have not received a response.

From that same wiki

"If the scheduling server receives an RPC with a sequence number less than the expected sequence number (usually indicating that the user has copied the client_state.xml file between computers) it creates a new database record and returns a new ID. "

But I am not copying between computers I am restoring a backup. And now since it already created a new hostID I am SOL.

Why does WCG insist on doing things against the grain with BOINC?