Knowledgebase: Kerio
Invalid start dates on a recurring event create different instances on server and device
Posted by Matt Kuebler on 09 November 2009 11:07 AM

Kerio:

This issue involves invalid start dates on a recurring event.  An invalid start date is defined as a start date that is not an instance of the series. The following are examples of invalid start dates:
   For a yearly recurring event:  1st Monday every August, starting August 22
   For a monthly recurring event:  25th of each month, starting November 11
   For a weekly recurring event:  Every Friday, starting Monday, September 17

When invalid start dates are specified on a recurring event, the instances of the event are created differently on the server than they are on the device.
On the server (Kerio web client):  The first instance of the event is the start date and there are x-1 number of instances after that, occurring when they should.
On the device:  There is no event on the start date and there are x number of instances after that, occurring when they should.