I am having a problem with my event notifcations being sent at the incorrect time using Events Module 3.2.0 and DNN 3.3.4. The notifications are usually sent out 12+ hours late so after much debuging here is what I have found (I have tried this on 2 seperate DNN installations on 2 seperate servers with the same result).

I set my super user and portal time zone settings to Eastern Time (-5:00 UTC) I also verified that all my events are the same time zone. I then added some code into the events module to dump data into the scheduler log so I could see what times where being evalutated. I noticed the NotifyTime parameter in class EventNotifcation (which is calculated by using the EventTimeBegin value and subtracting out the appropriate reminder time) was always much farther ahead then it should be. What appeared to be happening was the EventTimeBegin was being converted to UTC 0 twice, after more reading through the code I found this is what was happening. In the EventInfoHelper::AddRecurringEvent() the EventTimeBegin is converted to the users time zone but the parameter UserTimeZone was being set to 0 not to -300 as would be expected. So the EventTimeBegin was converted to UTC 0 here and then converted again in EventNotification::SendEventNotifications() (which, to the best of my understanding, is the only place it should be converted to UTC 0 during the notifcation process).

Since these functions are being called as part of a scheduled event and not by user interaction is it correct that UserTimeZone would be equal to 0? And if so wont this always cause the NotifyEvent time to be incorrect? Or am I completely off :O)

Also how does the date calculation handle Day Light Savings time? Since right now EST should be 4 hours behind UTC, not 5.

Thanks