"BOINC ownership or permissions are not set properly; please reinstall BOINC (Error code -1202)"

I have gotten this error a few times in the past on various clients and didn't think it a big deal, but on this particular client it is now happening every 1-3 times on startup. It will run fine for a startup or two after I reinstall BOINC as asked, but I don't want to make a habit of reinstalling every time I turn the thing on. I can't find this error code in the BOINC wiki, although I did find one forum post attributing it to an optimized application (I think it was for Einstein?). I'm running all stock apps and client; the only thing I could attribute it to, is that the frequent errors started at about the same time I attached to Enigma@Home. I will make a post in their forum as well, just to see if anyone else has run into this error--I'm having a problem with that project on another Mac, that fails all of its WUs.

It would be nice if I could track this error to something other than the project (perhaps new client version will help?), but if I have to detach this host from the project I guess it won't be a total loss... It seems like a cool project, but they don't seem to have the same level of support that other projects do. There are always other projects.

Host details: MacBook Pro C2D 2.4 Penryn, 2GB RAM, 160GB HD, OS X 10.5.6, BOINC 6.2.18
Attached Projects: BURP, climateprediction.net (on Delayed Detach), LHC@Home, Spinhenge@Home, Enigma@Home, World Community Grid.

I would appreciate it if anyone could shed some light on the situation; if they know of a fix, or if anyone has run across this error before.

I have the same problem, except it happens on every re-boot. Running the installer fixes the problem for that one time, but next boot, error -1202 again. OS 10.5.6, intel Macbook. There is a foreign character (AE ligature) in the boot drive name, FWIW.

If there's no quick fix then I'm just going to uninstall for now. Maybe in six months or so try again after there's time to work all the bugs out.

The BOINC app should be coded so that even w/o special permissions, it doesn't allow its project engines to access anything outside their directory. Should be a limit in the API calls or something.

Then again, why OSX keeps mucking around and changing the permissions is beyond me, as well.

I forwarded the question to the BOINC Mac developer.

TJM and the BOINC developers are busy fixing this problem. They're trying to get it fixed without a new BOINC version, as the problem does appear to lie in the way the Enigma application or wrapper copies files to the slot directory.

It isn't fixed yet, but things are looking up.

Cool! I guess it's all about who you know! Thanks for passing this on to the right people.