I've been running for a while. Seems rosetta has such errors on occaision. Just looking at mine, I've got 9 work units right now, and of the 5 that have been completed, two had errors. One after 22 minutes, the other after only 3 minutes of compute time.

Bottom line, don't worry too much about it. BOINC will get more work when it is needed and report back the errors to the project. This should help them figure out if there's a bug, or erroneous data in the work unit, or if it just means it ran in to a protein sequence that can't exist or something.

If you're in it for the credits, then perhaps Rosetta isn't stable enough for you. If you're just new to it all, it does happen on occaision. And, generally, over time new versions make such problems increasingly rare. That's why you don't see the same with SETI, the project has been around much longer.

---

Add this signature to your EMail:
Running Microsoft's "System Idle Process" will never help cure cancer, AIDS nor Alzheimer's. But running Rosetta@home just might!
https://boinc.bakerlab.org/rosetta/