Not so sure we are making such great progress.  Both times I've implemented your fixes I deleted *event* from the bin directory.  That is, I specifically deleted the three DLLs you reference above.

I had a thought though... is it possible that if I had partially implemented your zip file the first time around (say, deleted *event* from bin and replaced it with your DLL, but not yet modified the web.config, or maybe even deleted DotNetNuke.Events.* but not DotNetNuke.Modules.Events.*), then hit the site, would I have caused an irreversible error?  Pure speculation here, but I may very well have done something like that the first time around.  Is it possible that this may have written DB entries (or tried and failed) or something else which is causing my problems?

To be honest, I'm pretty sure I did hit the site part way through implementing your zip file, but I'm not sure at what stage in the implementation I was.  It was late and I should have been sleeping .  If there's even a slim possibility that this could cause an irreversible problem, I'll gladly scrub the site and start over from the beginning.  However, out of curiosity, if this is a likelihood is there some sort of SQL query I can run or something else I can check to validate this suspicion?  I generally like to find resolutions to issues before sweeping them under the rug .

Ok, got it!

This is what is happening.  It is actually the DotNetNuke SearchEngineScheduler and PurgeScheduleHistory that are causing the errors - but its because of we're using the new App_Code compilation (which I'm sure is why this bug made it into the golive version of 4.3.5). 

I'm guessing your Dr.Watson is seeing the null exception and shutting down the threads before they go anywhere else.  This is why my system didn't show the error.  Because of the security/anti-virus system you have, its locking down the system before it has a chance to crash and continue (whcih is what happens with me here).  I had to recompile dotnetnuke.dll in order to make this go away.  I was trying to not do too much to the core to keep the mods simple, if they don't adopt into the core.  But looks like we've got to.  I put this new dll on our dev server and it no longer logs the exceptions when the app starts, so I think we've got this fixed for now.  I update the .zip file I have posted, so you can just re-download, and copy over/replace your existing dotnetnuke.dll with the one I now have packaged.

Let me know if that works for you, I'm pretty sure that was the issue - but theres only one way to know for sure.  Install it and let me know.

I just wanted to give this thread a bit of a bump.  Steve and I have been working to resolve the issues I'm having with his code, and I give him tons of credit as he's gone above and beyond the call of duty (especially since he's not part of the DNN team).  Having said that, is anyone from the DNN core team or the Events Module team reading this?  I ask because the fact that Enrollment and Notifications are both broken in the current version (3.2) of the Events Module is a huge oversight.  Steve's code definitely has Enrollment email working, but at the cost of replacing some of the core DLLs in DNN, including DotNetNuke.dll.  Even if we do get this working perfectly, the next minor upgrade to DNN will probably break it, or at the very least require a recompile on his part.

So, DNN team, if you're listening... Please Help!