I cleaned out the transaction log, the event log and the schedule history and site log. The Events module still throws the runtime error.
I restored the site and database, then cleaned the logs, upgraded DNN to 4.09.04 and then upgraded the Events module. Still, it throws the runtime error.
I must clarify that it is the instance of the module that already had data and was in use on the site that is throwing the error. When I create a second instance of the Events module, it appears to work fine. Which means all my events are not accessable and must be re-entered.
Looking at the data in the Events table, I notice that my recurring events have records one-a-week from now until year 2050. That's a lot of records for each recurring event. I started to clean out all the records from 2012 until 2050, but my delete query failed after a long time (2 hours). Instead, I changed the module ID in some of the records from the old instance of the Events module to my new one. That event shows up fine on the new calendar - however if I try to edit that event using the Events module, I get another error.
I'm now starting to manually re-enter the events into the new Events module. I'd like to be able to copy the events from the old module to the new. But I need to know the process for that. The events table seems to be all I need. Is that true? Is there another post in here somewhere that has instructions for doing this?
Thanks.