I'm having a problem accessing the Log Viewer on an intranet installation that's been running rock solid for over a year now.  The version of DNN is 3.2.0 with a SQL 2000 database.

I became aware of the issue when users could not pull the page up.  Everyone was getting the following error:

DotNetNuke Upgrade Error

The Assembly Version ([ASSEMBLYVERSION]) does not match the Database Version ([DATABASEVERSION])
ERROR: Could not connect to database.

Timeout expired.  The timeout period elapsed to obtaining a connection from the pool.  This may have occurred because all pooled connections were in use and max pool size was reached.

I was not attempting any upgrades.  Checking the Event Log in Windows did not point to anything. I did an IISReset but I was still getting the same error.  I then rebooted the server and the error continued.   But a few minutes later the issue resolved itself and the page came up.  With the page up I tried to access the DNN Log Viewer but I get the following Error: Log Viewer is currently unavailable.

Since I never made any changes to DNN logs events I'm thinking that the logs are growing too big.  Can anyone tell me which logs I can look at in SQL and the best way to delete them?

Hi Philip,

I've noticed a few times, that if dnn_eventLog becomes too big, SqlDataProvider.PurgeLog( invoked from Application_End event) fails with "Timeout expired". 
The reason is that SQL of [dnn_PurgeEventLog] SP is very slow.
Could anyone from core team to review the SQL for optimisation?   

this would be even faster:

truncate table {objectQualifier}eventlog

You can do that from Host > SQL

DNN Blog | Twitter: @erikvb | LinkedIn: