Error The transaction log for database “domain.com” is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases

While accessing a DotNetNuke website today, I was getting this error all the time.

Error   The transaction log for database “domain.com” is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases

Event ID 3001

  • Event code: 3001
    Event message: The request has been aborted.
    Event time: 2/11/2010 12:28:32 PM
    Event time (UTC): 2/11/2010 1:28:32 AM
    Event ID: cc9168019d0b42cabde5ab8fa741927d
    Event sequence: 13
    Event occurrence: 12
    Event detail code: 0

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!

One thought on “Error The transaction log for database “domain.com” is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases

Leave a Reply