Comment 1 for bug 1002814

I'm not sure that changing the exception that is raised is really the fix, but I think there is probably some state cleanup that needs to be done after the loopingcall if it fails.

Targeting for folsom-rc1 since this is a state corruption bug that has the potential to block normal users, requiring them to manually poke their database.