I had the same error and the suggestions posted by Allen Cui worked - putting the database into emergency mode, then rebuilding the log, etc.

Cheers

Jeff