Yet Another Local Failure Notice

[fsiegel]

I would still like to know how you created this appointment, but I do know why Outlook 2003 complains, and it looks like it is because of a bug in the way Outlook 2003 processes these .ics files.

The "period" in this .ics is 1, which makes sense -- it occurs every day. The interval is 1 in the .ics file. Whereas Outlook 2007 treats this as a weekly occurrence, occurring every week on Monday thru Friday, Outlook 2003 treats this as a daily occurrence, occurring every weekday. But for daily occurrences, the period is supposed to be stored in minutes (i.e. 1440), but in this case, the period is stored in days (1), so our code does its calculations, and determines that this is a bad appointment.

Not sure I can code around this. Depends on what I find out about how you created this appointment.

[fsiegel]

You probably created a daily appointment in Outlook 2003 that occurs every weekday. Correct? We now have a bug for this -- 42426.

[vader]

hi,

we have the same problem here with ol 2007/win7/zimbra 6.0.0 but with appointments occurring every year (bithdays). is there an estimation if that bug will be fixed in 6.0.3?

[fsiegel]

This is bug 42426, and I am going to look at it today. I have only been able to reproduce with weekday appointment. It would help me a lot if you could give me an exact scenario of how you create your "birthday" appointment. When I create a yearly appt in Outlook 2007, it works fine.

Please list the exact steps that you do.

Thanks

[vader]

the user just told me that, that he created the appointment by importing them from a google calendar by gSyncit. it looks like the dates are corruped because they do not show in the calendar but open a reminder window.

[fsiegel]

Well -- if I had some .ics I could take a look, but this isn't as interesting as if they had created the appointment in Outlook. It's tough to support all these flaky addins.