zimbra upgrade 4.5.9 to 5.0.1 SOAP CHANGES???

[phingers]

Our appointments used to sync over to zimbra perfectly, we upgraded this weekend, and are now experiencing the infamous INVITE_OUT_OF_DATE error again.

Any clues as to what has changed?

<ModifyAppointmentRequest id="325-324" comp="0" xmlns="urn:zimbraMail">
                        <m d="1201400281">
                                 <inv method="REQUEST" type="event" fb="B" transp="O" status="CONF" allDay="0" name="my title" loc="123 Main Street">
                                         <s tz="(GMT-05.00) Eastern Time (US &amp; Canada)" d="20080129T153000"/>
                                         <e tz="(GMT-05.00) Eastern Time (US &amp; Canada)" d="20080129T173000"/>
                                         <or a="myuser@zimbraaccount.com" role="CH" />
                                        </inv>

                                 <mp ct="multipart/alternative">
                                         <mp ct="text/plain">
                                         <content>
my cool content here
                                        </content>
                                        </mp>
                                        <mp ct="text/html">
                                         <content>
             my cool content here.
                                         </content>
                                        </mp>
                                </mp>
                                 <su>test</su>
                         </m>
                 </ModifyAppointmentRequest>

leading to this:

<Error xmlns="urn:zimbra"><Code>mail.INVITE_OUT_OF_DATE</Code><Trace>com.zimbra.cs.mailbox.MailServiceException: The specified Invite is out of date (has been updated): c49bc9d1-94aa-4126-982d-8dcf01270061:325-324
Code:mail.INVITE_OUT_OF_DATE
        at com.zimbra.cs.mailbox.MailServiceException.INVITE_OUT_OF_DATE(MailServiceException.java:398)
        at com.zimbra.cs.service.mail.ModifyCalendarItem.handle(ModifyCalendarItem.java:107)

ETC...

[jhahm]

Can you describe the scenario in more detail? Are you getting the error in web client? This error is returned when the appointment had been updated on the server and therefore the last get response the client got is stale. Client must refresh the local data and resubmit Modify request.

There is no API issue here, it's simply that the appointment you're trying to update has already been modified. It could have been modified when the organizer sent out an update invitation, or the modification could be made by another client on the same mailbox. What are the client apps/devices running on this mailbox?