Due to the following issues, it is recommended that all exceptions be created in the Meeting Maker client rather than on the device.

For BlackBerry Phone or Windows Mobile 5 device users there exists a possibility of an issue involving a recurring appointment that has an exception on either the first or last instance.  There are several variables associated with this issue as well.

1. If, from the device, the first or last instance of the recurring appointment is modified that instance may be deleted from the device.  The event displays correctly, however, in Meeting Maker.  This does not occur consistently, however, as the occurrence of it depends upon the order in which the "add" (for the instance that was modified) and the "update" (for the recurring series) are synchronized.
2. If the change synchronizes and does successfully display on the device it is open to another irregularity.  Should there be a change to either the exception instance of the event or to the series in general, duplicates of the instance or of the entire series will result.

NOTE: This no longer occurs after applying nlpim.exe hotfix v4.3.0.5.

 

This issue is related to the issue noted above.  After applying nlpim.exe hotfix v4.3.0.5, the following issues exist.  These issues also stem from a change made to the first or last instance of a recurring meeting.

If, from a device, the first or last instance of a recurring meeting is edited to create an exception both sides will synchronize correctly, however, this sequence of events is possible:

1. If a middle instance is edited from the device, the first or last instance that was initially changed is duplicated on the server (the exception and original).
2. If the above issue occurs the series is open to a second issue.  If the series is changed from the server, the first or last instance that was initially changed is duplicated on the device (the exception and original).

For BlackBerry phone and Windows Mobile 5 users there is an additional possibility.  If, from a device, the first or last instance of a recurring meeting is edited to create an exception both sides will synchronize correctly.  If the series is changed from the server, however, the exception is deleted from the device.