by Manz » Sat Jan 21, 2012 11:54 pm
The error has seemed to fix itself. So no outstanding errors at the moment.
If anyone else comes across this bug: turn sysadmin on and off and ownership on and off and restart the whole server. It seems to fix itself.