I always appreciate reviewing and googling the DotNetNuke forums and blogs for chances to learn from other's experiences, so here is my recent DNN experience.
A few weeks ago my System Administrator let me know that the DNN SQL Database was getting quite large. We're a voluntary group, and he was going away for a week and we didn't have much time to look at it right then, so we moved the SQL Database to a larger hard disk. (We did a full backup of the database and web server before we did this. My System Administrator also does scheduled periodic (I believe it's daily) system backups as normal maintenance.)
Last night he figured out the Event Log was getting a large number of general exceptions and we had not cleared the Event log since our initial install in July! He cleared the eventlog, truncating it from SQL, as it was too large to look at from within DNN's Administrator's Event Log viewer. He let me know about the situation and I found this thread that might well apply:
The bottom line answer was:
There is an issue with DNN where sometimes modules will get a bad value recorded for their supported features (like Searchable, Portable, etc). This can cause the Search provider to try to create a the module's business class when it doesn't exist. The easiest fix is to look in the database for bad values. You'll want to look for a -1 in the SupportedFeatures column in the DesktopModules table, change it to a 0. Run this from the Host SQL menu.
UPDATE {databaseOwner}{objectQualifier}DesktopModules SET SupportedFeatures = 0 WHERE SupportedFeatures = -1
I turned off logging of the General Exception errors for the Event Log from DotNetNuke in production, (in our case the this is admittably a band-aid approach, but the threat of being affected by the logging event rows is more of a threat than the problem it is reporting) so we shouldn’t see these any more (we can turn it back on if we want to see them). In my opinion, Event logging monitoring should mainly be for the test system.
The update SQL command listed needs to be run. I also made sure that the site log was being cleaned up through the scheduler. Checked this morning and there was just one event log from my login. Cheers.