Put the knife down and take a green herb, dude. (c) Ruffin Bailey 2001-2017

Got a meeting request that borked Outlook, so I started a-googlin'. Here's the easily found Microsoft support article:

The "not supported calendar message.ics" attachment is created when the original .ics file cannot be converted to an Outlook or Microsoft Exchange meeting type. The conversion fails if one or more of the following conditions are true:

The meeting contains a recurrence pattern that is available to a third-party email client, such as Lotus Notes. However, this recurrence pattern is not supported by Outlook:

Monthly by Date: Every month on the nth day and the nth day. Outlook only supports one nth day of the month.

Monthly by Day: Every month on the nth day of the week and the nth day of the week. Outlook only supports one nth day of the week in any month.

Custom recurrence: Outlook does not support custom recurrence patterns that are available in some third-party email clients, such as Lotus Notes.

The meeting contains a recurrence pattern that is defined by the RDATE property. However, the meeting does not include a corresponding RRULE property. In this case, Outlook does not open the item, even if the RDATE property specifies a supported recurrence pattern

How do you fix problem 1? Oh, so glad you asked! It's easy!

To work around this issue, have the meeting organizer create a meeting that uses a recurring pattern that Outlook supports.

Or, if it's problem 2., it's even more fun! You can go read an RFC.

For more information about the RDATE and RRULE properties, visit the following page on The Internet Engineering Task Force (IETF) website: http://tools.ietf.org/html/rfc2445

Wow. The worst part of this is the date of the last update to this support article.

Article ID: 2643084 - Last Review: November 9, 2011 - Revision: 2.0

These don't seem like particularly difficult thing to kludge around. How is it that such an easily definable set of edge cases can't be kludged into Outlook 2010 at some point in the last three and a half years? Are there really that many more important issues? Sounds like this could be fixed in a good weekend of work, plus a few hours of QA. Release it as an unsupported script or translation utility, for heaven's sake.

/sigh

Outlook fail.

Update: ExQuilla imported the ics file, no problems.

Labels: outlook fail

title: Put the knife down and take a green herb, dude.	descrip: One feller's views on the state of everyday computer science & its application (and now, OTHER STUFF) who isn't rich enough to shell out for www.myfreakinfirst-andlast-name.com Using 89% of the same design the blog had in 2001.
FOR ENTERTAINMENT PURPOSES ONLY!!! Back-up your data and, when you bike, always wear white.
x MarkUpDown is the best Markdown editor for professionals on Windows 10. It includes two-pane live preview, in-app uploads to imgur for image hosting, and MultiMarkdown table support. Features you won't find anywhere else include... MarkUpDown Multiline Table & Bootstrap Grid support. Beautiful Easy Actions that keep the Markdown flowing. HTML paste to paste HTML source into your documents. You've wasted more than $15 of your time looking for a great Markdown editor. Stop looking. MarkUpDown is the app you're looking for. Learn more or head over to the 'Store now!

Wednesday, May 27, 2015
Outlook support tells me RTFRFC. Thanks. Got a meeting request that borked Outlook, so I started a-googlin'. Here's the easily found Microsoft support article: The "not supported calendar message.ics" attachment is created when the original .ics file cannot be converted to an Outlook or Microsoft Exchange meeting type. The conversion fails if one or more of the following conditions are true: The meeting contains a recurrence pattern that is available to a third-party email client, such as Lotus Notes. However, this recurrence pattern is not supported by Outlook: Monthly by Date: Every month on the nth day and the nth day. Outlook only supports one nth day of the month. Monthly by Day: Every month on the nth day of the week and the nth day of the week. Outlook only supports one nth day of the week in any month. Custom recurrence: Outlook does not support custom recurrence patterns that are available in some third-party email clients, such as Lotus Notes. The meeting contains a recurrence pattern that is defined by the RDATE property. However, the meeting does not include a corresponding RRULE property. In this case, Outlook does not open the item, even if the RDATE property specifies a supported recurrence pattern How do you fix problem 1? Oh, so glad you asked! It's easy! To work around this issue, have the meeting organizer create a meeting that uses a recurring pattern that Outlook supports. Or, if it's problem 2., it's even more fun! You can go read an RFC. For more information about the RDATE and RRULE properties, visit the following page on The Internet Engineering Task Force (IETF) website: http://tools.ietf.org/html/rfc2445 Wow. The worst part of this is the date of the last update to this support article. Article ID: 2643084 - Last Review: November 9, 2011 - Revision: 2.0 These don't seem like particularly difficult thing to kludge around. How is it that such an easily definable set of edge cases can't be kludged into Outlook 2010 at some point in the last three and a half years? Are there really that many more important issues? Sounds like this could be fixed in a good weekend of work, plus a few hours of QA. Release it as an unsupported script or translation utility, for heaven's sake. /sigh Outlook fail. Update: ExQuilla imported the ics file, no problems. Labels: outlook fail posted by ruffin at 5/27/2015 04:23:00 PM
0 comments