This is as I suspected, although the error is coming from an appointment created in Outlook, and trying to sync to the server, not the other way around as I had originally figured. We are having trouble processing a recurrence stream of a recurring appointment you are creating.
This may or may not be a bug in our code (probably is), so I need to ask some questions about the offending appointment. Hopefully you will know which one it is -- it looks like you are sending 2 appointments. The first one is one you are creating, which is giving the error. The second is one that already exists, and has the Zimbra id 1311.
So for the one you are creating, how are you creating it? What is the recurrence pattern? Daily, weekly? Unfortunately, the logging code is not really distinguishing very well right now, and I can use this information to figure out the issue and creating better logging.
And now, for the "TMI" portion. :-)
It seems that there is a problem with the way this appointment is being created. It may be that the bug is just that we are not reporting it correctly. We are putting out the error because we think this appointment is violating the Microsoft Appointment and Meeting Object and Protocol Specification in some way, specifically the "Period" field. The spec says:
"This field is the interval at which the meeting pattern specified in PatternTypeSpecific field repeats. The Period value MUST be between 0 and the MaximumRecurrenceInterval, which is 999 days for daily recurrences, 99 weeks for weekly recurrences and 99 months for monthly recurrences."
So are you specifying an appointment that violates this?
If possible, can you save the offending appointment as either an .ics or an .msg or both, and post it? That will allow me to reproduce this in house.
Thanks  |