-
Title
NI: Reasons specified in customized calendar rejection notifications -
Description
NI: Reasons specified in customized calendar rejection notifications -
Resolution
Notes Integration can be configured to provide a “REASON” in the notification returned to a user when a calendar message is not supported or an error is detected. The document provides a list of each reason and what caused it.
Calendar items originating in Outlook
Rejection notifications for calendar items originating in Outlook can be broken in two categories:
1) Unsupported invitation features resulting from the way in which the Outlook user specified the meeting (user errors)
2) Issues resulting from the creation of the ICS file by Exchange (Exchange errors)
In the first case, the Outlook user should cancel the meeting and reschedule it using a supported recurrence pattern. In the second case, the file needs to be looked at to determine how the error occurred.
User Errors
Attempting to convert single meeting into recurring meeting
Explanation: The Outlook user scheduled a single occurrence meeting and is now trying to convert it to a recurring meeting.
Corrective Action: Cancel the original meeting and reschedule it.
Attempting to reschedule meeting with Domino Resource
Explanation: The Outlook user is attempting to reschedule a meeting that contains a Domino Room or Resource.
Corrective Action: Cancel the original meeting and reschedule it.
Cannot cancel series if single occurrence already canceled
Explanation: The Outlook user is attempting to cancel the series but has previously canceled a single occurrence of the series.
Corrective Action: Cancel each meeting occurrence individually.
Invalid RRULE (%s) – BYMONTHDAY = 0
Explanation: The Outlook User scheduled a recurring meeting to occur on the zero day of each month.
Corrective Action: Cancel the original meeting and reschedule it specifying a valid day of the month.
Invalid RRULE (%s) – BYMONTHDAY 28
Explanation: The Outlook User scheduled a recurring meeting to occur on either the 29th, 30th or 31st day of each month. This is not supported by Notes.
Corrective Action: Cancel the original meeting and reschedule it specifying a day value between 1 and 28.
Invalid RRULE (%s) – BYMONTHDAY
Explanation: The Outlook User scheduled a recurring meeting to occur on either the 29th, 30th or 31st day of each month. This is not supported by Notes.
Corrective Action: Cancel the original meeting and reschedule it specifying a day value between 1 and 28.
Invalid RRULE (%s) - does not contain Count= or Until=
Explanation: The Outlook user scheduled a recurring meeting with no end date.
Corrective Action: Cancel the original meeting and reschedule it specifying either and ending date or a specific number of occurrences.
Meeting cannot go past Year 2037
Explanation: The Outlook user is trying to schedule a recurring meeting that will go past Year 2037.
Corrective Action: Cancel the original meeting and reschedule it so it ends before 2037.
Meeting Exceeded Recurrence Limit
Explanation: The Outlook user specified a recurring meeting that contains too many dates. By default, CMT for Coexistence will only support 1200 meetings for a recurring meeting. This is configurable via the BTRecurrenceLimit parameter. If the expanded list of individual meetings exceeds this limit, this error will be returned.
Corrective Action: Cancel the original meeting and reschedule it with less meeting occurrences.
Rescheduling of entire series after rescheduling individual occurrence not supported
Explanation: The Outlook user rescheduled a single occurrence of a recurring meeting, and is now trying to reschedule the entire series.
Corrective Action: Cancel the original meeting and reschedule it.
Too many dates for RDATE buffer
Explanation: The Outlook user specified a recurring meeting that contains too many dates. For recurring meetings, the RRULE from the ICS file is expanded into a list of individual date/times for the meeting. These are stored in a 32K buffer. If there are too many dates and we will overflow this buffer, this error will be returned.
Corrective Action: Cancel the original meeting and reschedule it with less meeting occurrences.
Until time
Explanation: The Outlook user specified an “UNTIL” date/time that preceded the first date/time of the meeting.
Corrective Action: Cancel the original meeting and reschedule it with a valid UNTIL date.
Exchange Errors
Invalid cancel received
Explanation: There was an error processing the Cancel message received from Exchange.
Corrective Action: Retry to cancel the original meeting and reschedule it.
Invalid ICS file. First character is a ' '
Explanation: The first character of a line in the ICS file cannot be a space.
Corrective Action: Cancel the original meeting and reschedule it.
Invalid parameters for ICAL_ConvertRRULEtoRDATE
Explanation: CMT for Coexistence expands the RRULE for a recurring meeting into a series of RDATES, with each RDATE representing a single instance of the recurring meeting. While trying to do this, one of the parameters taken from the ICS file is invalid.
Corrective Action: Cancel the original meeting and reschedule it.
Invalid RRULE (%s) - contains space
Explanation: The RRULE contained in the ICS file contains a space, which is invalid.
Corrective Action: Cancel the original meeting and reschedule it.
RRULE Changed
Explanation: The RRULE in the ICS file is different from the RRULE contained in the original meeting invitation.
Corrective Action: Cancel the original meeting and reschedule it.
Unsupported ICS file: EXDATE found
Explanation: The EXDATE keyword was found in the ICS file for a meeting request.
Corrective Action: Cancel the meeting and reschedule it using a simpler repeat pattern.
Unsupported ICS file: Multiple VEVENTS found
Explanation: In the ICS file, a VEVENT is used to define a calendar event. CMT for Coexistence does not support more than one VEVENT in a single ICS file.
Corrective Action: Cancel the original meeting and reschedule it.
Unsupported ICS file: Quoted Printable Text found
Explanation: The ICS file is encoded in MIME as Quoted Printable Text. This is not a supported type.
Corrective Action: Cancel the original meeting and reschedule it.
Calendar items originating in Notes
Rejection notifications for calendar items originating in Notes can be broken in two categories:
1) Unsupported invitation features resulting from the way in which the Notes user specified the meeting (user errors)
2) Issues resulting from the processing of the item by CMT for Coexistence (BTCal errors)
In the first case, the Notes user should cancel the meeting and reschedule it using a supported recurrence pattern. In the second case, the file needs to be looked at to determine how the error occurred.
User Errors
Can only move weekend occurrences for Daily repeating meetings
Explanation: The Notes user specified to move the meeting if it occurs on weekend for a non-Daily recurring meeting. The Notes user can only choose “Don’t move”.
Corrective Action: Cancel the meeting and reschedule it specifying “Don’t move” for weekend occurrences.
Cannot add invitees to a Notes meeting
Explanation: The Notes user attempted to add users to an already scheduled meeting and it was not successfully processed.
Corrective Action: Cancel the meeting and reschedule it.
Cannot repeat more than one day using Monthly by Date
Explanation: The Notes user specified more than one day when choosing the Monthly by Date option. The Notes user can only choose one day.
Corrective Action: Cancel the meeting and reschedule it specifying only one day.
Cannot repeat more than one day using Monthly by Day
Explanation: The Notes user specified more than one day when choosing the Monthly by Day option. The Notes user can only choose one day.
Corrective Action: Cancel the meeting and reschedule it specifying only one day.
Cannot reschedule after another already scheduled occurrence
Explanation: The Notes user is trying to reschedule an instance of a recurring meeting after another scheduled occurrence.
Corrective Action: Cancel the rescheduled meeting and reschedule it specifying a supported pattern.
Cannot reschedule before another already scheduled occurrence
Explanation: The Notes user is trying to reschedule an instance of a recurring meeting before another scheduled occurrence.
Corrective Action: Cancel the rescheduled meeting and reschedule it specifying a supported pattern.
Cannot support Exchange Resource "
Explanation: The Notes user is trying to schedule a meeting and specified an Exchange resource in the Resource field. Exchange resources must be added in the To: field.
Corrective Action: Cancel the meeting and reschedule it specifying the Resource in the To: field.
Cannot support Exchange Room "
Explanation: The Notes user is trying to schedule a meeting and specified an Exchange Room in the Room field. Exchange Room must be added in the To: field.
Corrective Action: Cancel the meeting and reschedule it specifying the Room in the To: field.
Cannot update Current and All Previous or Current and All Future
Explanation: The Notes user specified either “This instance and all previous instances” or “This instance and all future instances” when rescheduling a meeting. This is not supported. The Notes user can only reschedule the entire series or just a single occurrence.
Corrective Action: Cancel the meeting and reschedule it specifying a supported pattern.
Custom meeting dates not supported
Explanation: The Notes user specified a recurring meeting using custom dates.
Corrective Action: Cancel the meeting and reschedule it using a supported pattern.
Domain %s not configured for CMTc
Explanation: The Notes user attempted send a mail item to a Foreign Domain that is not configured for BTExchangeDomain or BTAltExchangeDomains.
Corrective Action: Send the mail item to a valid Foreign Domain.
Meeting event has Exceptions
Explanation: The Notes user rescheduled one or more individual occurrences of a recurring meeting, and is now trying to reschedule the entire series.
Corrective Action: Cancel the meeting and reschedule it using a supported pattern.
Month by Day reschedule not supported
Explanation: The Notes user is attempting to reschedule a meeting using the Month by Day option.
Corrective Action: Cancel the meeting and reschedule it using a supported pattern.
The maximum number of invitation exceptions has been exceeded. Rejecting…
Explanation: The Notes user attempted to add Exchange users to an existing meeting and but the number of exceptions exceeds BTAddUserExceptionsMax.
Corrective Action: Cancel the meeting and reschedule it.
The maximum time to process Add User requests has been exceeded. Rejecting…
Explanation: The Notes user attempted to add Exchange users to an existing meeting and BTCal could not get the original invitation information before BTAddUserDelayMax has expired.
Corrective Action: Cancel the meeting and reschedule it.
There are %u exceptions and you cannot add an Exchange user if there exceptions. Rejecting…
Explanation: The Notes user attempted to add Exchange users to an existing meeting that had exceptions and exceptions are not allowed.
Corrective Action: Cancel the meeting and reschedule it, or add the Exchange user to individidual occurrences.
BTCal Errors
Cannot find meeting in BTCache database
Explanation: The Notes user is attempting to reschedule a meeting, and BTCal cannot find the meeting in the cache database.
Corrective Action: Cancel the meeting and reschedule it.
Cannot open note in BTCache database
Explanation: The Notes user is attempting to reschedule a meeting, and BTCal cannot open the associated document in the cache database.
Corrective Action: Cancel the meeting and reschedule it.
Meeting not found in BTCache database
Explanation: The Notes user is attempting to reschedule a meeting, and BTCal cannot find the meeting in the cache database.
Corrective Action: Cancel the meeting and reschedule it.