Rick,

1. We can do some analysis of what time the server is thinking the notficications need to go at against what time you think it should go at. Notifications are a real minefield due to issues around DST and Timezone support in DNN (.Net v2). One thing to consider is that you need to check that the time is accurate on your web server and sql server, and that timezones are configured correctly. In any case come back to and we'll try to help. If there is still a significant bug (aside from DST issues), we'll get it fixed.
2. What is the specific are of it not working? Does this relate to point 1?
3. Yes, this should probbaly be added as a feature. Perhaps you would like to raise this on Gemini.

Cheers
Roger

Thank you for responding.

1. This is the primary issue that I am interested in (it's the one that I am focused on) the others seem very unimportant in comparison with this issue.

Before the tests I verified that the time zone on the Windows Vista (Ultimate) clock was set to GMT -5. I also verified the time was correct.

My coworker also mentioned before the testing that I should check the MS SQL Server 2005 database time by using a select statment to view getdate() which returned the correct date and time.

Therefore the time is accurate on the web server and SQL server and the time zone is set correctly on the web server. I couldn't find a time zone on the database, but the getdate() was correct. I am using IIS on my local machine to serve the ASP.NET pages (I couldn't find any time settings there).

Here are my actual tests (tests ran 10/7/08 - 10/8/08) (all time zones GMT -5):

Event time set to:                    5pm
Reminder time set to:              20min
*Time should have been recieved: 4:40pm
Email notification time sent: 9am the next day

Event time set to:                    5:30pm
Reminder time set to:              40min
*Time should have been recieved: 4:50pm
Email notification time sent: 9am the next day

Event time set to:                    5:30pm
Reminder time set to:              30min
*Time should have been recieved: 5pm
Email notification time sent: 9am the next day

Event time set to:                    6pm
Reminder time set to:              35min
*Time should have been recieved: 5:25
Email notification time sent: 9am the next day

Note that even though they were all recieved at the same time, the actual time that they should have been recieved was different in each case.

The day that I set the reminder tests I left the computer on when I went home. When I got back to work the next day at 9am, I recieved all of them with the same sent time. I haven't tried the module with a fresh install on another server at all this may be due to it running on Vista. I am curious if anyone else has the same issue but I will not be able to spend a lot of time looking into the solution.

In the event viewer, I have gotten some exceptions that may be related to this problem.

I have included some of the traces:

---This is from starting the request method for the scheduler
10/9/2008 9:59:59 AM   Scheduler Exception       AssemblyVersion: -1; PortalID: -1; PortalName ... 
AssemblyVersion: -1
PortalID: -1
PortalName:
UserID: -1
UserName:
ActiveTabID: -1
ActiveTabName:
RawURL:
AbsoluteURL:
AbsoluteURLReferrer:
UserAgent:
DefaultDataProvider:
ExceptionGUID:
InnerException: Collection index must be in the range 1 to the size of the collection.
FileName:
FileLineNumber: -1
FileColumnNumber: -1
Method:
StackTrace:
Message: System.IndexOutOfRangeException: Collection index must be in the range 1 to the size of the collection. at Microsoft.VisualBasic.Collection.IndexCheck(Int32 Index) at Microsoft.VisualBasic.Collection.get_Item(Int32 Index) at DotNetNuke.Services.Scheduling.DNNScheduling.Scheduler.CoreScheduler.ScheduleQueueContains(ScheduleItem objScheduleItem) at DotNetNuke.Services.Scheduling.DNNScheduling.Scheduler.CoreScheduler.AddToScheduleQueue(ScheduleHistoryItem objScheduleHistoryItem) at DotNetNuke.Services.Scheduling.DNNScheduling.Scheduler.CoreScheduler.LoadQueueFromTimer() at DotNetNuke.Services.Scheduling.DNNScheduling.Scheduler.CoreScheduler.Start()

---I'm not sure why I'm getting this exception
10/9/2008 10:49:03 AM   General Exception       AssemblyVersion: -1; PortalID: -1; PortalName ... 
AssemblyVersion: -1
PortalID: -1
PortalName:
UserID: -1
UserName:
ActiveTabID: -1
ActiveTabName:
RawURL:
AbsoluteURL:
AbsoluteURLReferrer:
UserAgent:
DefaultDataProvider:
ExceptionGUID:
InnerException: This operation returned because the timeout period expired. (Exception from HRESULT: 0x800705B4)
FileName:
FileLineNumber: -1
FileColumnNumber: -1
Method:
StackTrace:
Message: System.ApplicationException: This operation returned because the timeout period expired. (Exception from HRESULT: 0x800705B4) at System.Threading.ReaderWriterLock.AcquireReaderLockInternal(Int32 millisecondsTimeout) at DotNetNuke.Services.Scheduling.DNNScheduling.Scheduler.CoreScheduler.get_ScheduleInProgress()

---I get this exception too, but I'm not sure why
10/9/2008 1:11:41 PM   Host Alert       EventQueue.ProcessMessage: Message Processing Failed; Proces ... 
EventQueue.ProcessMessage: Message Processing Failed
ProcessorType: DotNetNuke.Entities.Modules.EventMessageProcessor, DotNetNuke
Body:
Sender:
BusinessControllerClass: DotNetNuke.Modules.Media.MediaController, DotNetNuke.Modules.Media
DesktopModuleId: 66
UpgradeVersionsList: 03.02.00,03.02.03
ExceptionMessage: Object reference not set to an instance of an object.
---

2. This separate issue is related, because the expected result is to recieve a reminder notice (just like in #1). From the event detail, I click the link to send the reminder to my email address which is showing up correct. Then I check my email and I recieve nothing. The SMTP settings were tested before hand and the site is able to send emails wiith no problem.

(I'm not sure if there were any errors in the Event Viewer here)

3. I created an account on Gemini, but I couldn't figure out how to post to it.