Not sure if you are still having this issue. I recently ran into the same error & it appears to be related to DB maintenance job that was happening...