I found this one a little perplexing. On further investigation I found that the transaction logging for the SQL server supporting this was massive. Around 980 meg when I would expect it to run around 15 meg.

Initially I tried killing all processes with active connections to the database, but that did not have the desired result. (We all know what a pain that can be in SQL). So I set the database to “Simple”, and tried to Detach the re-attach.

Still no joy!

All of this round and round ended up with an IIS server and SQL server reboot. All came good and the net result is that I cannot explain the fail or fix it.

Hope this helps someone make the reboot decision faster than I did. That’s another 2 hours of my like I will never get back!