This project has moved and is read-only. For the latest updates, please go here.

Unexpected range exception when scheduling monthly projects for day of week on XP Pro

Jun 11, 2012 at 10:01 PM
Edited Jun 11, 2012 at 10:02 PM

32-bit Windows XP SP3 or 64-bit Windows XP SP2. This only reproduces on Windows XP.

The Problem:
When a task is scheduled to run monthly on a specific weekday (like the 2nd Monday) of the month,  an exception "Value does not fall within the expected range" is thrown when closing the Edit Trigger dialog. This only happens on Windows XP 32 and 64-bit and does not appear with Vista and Windows 7. Also, it only happens when scheduling monthly for a specific weekday (for example, the second Monday) and the error does not appear if the project is scheduled monthly to run on a particular day of the month (the 11th) as opposed to a specific weekday.

To Reproduce:
On the Triggers tab, select the default trigger and choose "Edit...". Choose Monthly. In the Months group, the Days radio button is selected so choose "On" instead and then choose "Second" and "Tuesday" or any values here and then click OK.  

Exception details:
Value does not fall within the expected range.

Exception type:  System.ArgumentException
Message:         Value does not fall within the expected range.
Source:          Microsoft.Win32.TaskScheduler
Target Site:     SetTrigger

Stack Trace:
Microsoft.Win32.TaskScheduler.V1Interop.ITaskTrigger.SetTrigger(TaskTrigger& Trigger)
   at Microsoft.Win32.TaskScheduler.Trigger.SetV1TriggerData()
   at Microsoft.Win32.TaskScheduler.Trigger.Bind(ITask iTask)
   at Microsoft.Win32.TaskScheduler.TriggerCollection.Add(Trigger unboundTrigger)
   at Microsoft.Win32.TaskScheduler.TriggerCollection.Insert(Int32 index, Trigger trigger)
   at Microsoft.Win32.TaskScheduler.TriggerCollection.set_Item(Int32 index, Trigger value)
   at Microsoft.Win32.TaskScheduler.TaskPropertiesControl.triggerEditButton_Click(Obje
ct sender, EventArgs e)
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button,
Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ButtonBase.WndProc(Message& m)
   at System.Windows.Forms.Button.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr
wparam, IntPtr lparam)


Jun 12, 2012 at 2:58 PM

Looks like this has been corrected in source release 77874. Please disregard post. Thanks.

Jun 12, 2012 at 7:45 PM

Ooopsss....I was just informed by my assigned tester that source release 77874 didn't fix the above-reported issue. Hoping to get a resolution from this thread. Thanks David!

Jun 13, 2012 at 6:06 PM

Fixed in changeset 78634. Thanks for reporting this.

Jun 13, 2012 at 6:50 PM

Awesome! Thanks David!