Would setting the log file (under host settings in DNN)  to use the file system rather than the database resolve this issue?  I have a couple sites crashing with the same error.  I am using Cyber Siouxland (www.cybersiouxland.com) shared hosting, which is the same as GoDaddy.

Unhandled Error

The transaction log for database 'db_name' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases 

You know jd I'm a rookie at this so I don't know. If anyone could answer this it would be great!

I have kept a close eye on my database since they truncated the transaction log. My database reported 24 mb after they did this but has grown by about 5 mb a day.

I'll post godaddys reply and see if anyone agrees:

Unfortunately if the database size continues to grow in such a manner you will need to explore re-organizing the database structure to prevent future issues. Normally issues with excessive transaction log and database growth with DotNetNuke is related to poor, improperly installed or corrupted modules that are generating constant errors that fill the event log and database transaction logs as well as database. You may want to review your sites event log to see if you can find any details on any potential issues in this area.

Yet my event log only has 7 things in it since the 15th. I wouldn't think that would grow at 5 mb a day. On another note there is one message that is 6 of the 7 messages. Is it safe to publicly post it here to see if anyone can tell me what it is?

Thanks,

Mike