I just ran into this same problem. There is a knowledge base article about this on the MSDN site, but it calls for reverting to a known good backup of the db:
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.