Yet Another Local Failure Notice

[jcha]

We are using Office 2003 SP3
Connector Version: ZimbraOlkConnector-6.0.1_GA_1816_6.0.5691.1.msi

Client Version: 6.0.1_GA_1816.RHEL5_64
Client Release: 20090911162124
Build Date: 20090911-1637

I got 5 users that keep receiving the following:

Local Failures were detected.  No action is required.
This e-mail was generated for technical support purposes.

Sync Type: Delta Sync

Store: Zimbra - (User Name)

Computer Name: (Workstation Name)

Version: 6.0.5691.1

Error ID:
-2147221233

Error Code: -2147221240
Error Message: Unknown error 0x80040108

Yes, I searched and yes, it is related to appointments.
How do I fix this? Is there a way to properly set appointments so that they don't get these error message?

Are older versions of the Zimbra Connector suppressing these errors for the other users? Why is it that only these newer users receive these errors.

Any help or suggestions would be greatly appreciated.

[fsiegel]

We do have a new (better!) calendar converter in version 6, and it seems to think you have invalid mapi objects (0x80040108). Did the local failure message have .xml files attached to it (like the mime, the requests/replies)? If not, the zco log should have more information as to why you get these errors. A lot of times it happens with migrated appointments that have recurrence streams that we can't process. But this other info should help us tell. If you have it (.xml files and/or zco logs), please post it.

[jcha]

I've attached the logs for 2 of my users.
Please let me know if you need more info.

Thanks for your help.

[fsiegel]

Can you please do the logs again, but this time, only turn on logging and http logging. Turn off verbose logging, and especially Calendar tracking. There is too much worthless junk to go through to see what is going on.

Thanks

[jcha]

Am I to wait for the event to happen then attach the log?
If so, then I'm not sure the event has happened this afternoon.
Most of the users are in a meeting, so there isn't a lot of activity.

Attached is about 30 mins worth of HTTP logs.

Again, thanks for the help.

[fsiegel]

Yes -- I need a log that was going when a local failure occurred. The ones you just sent had no local failure. As long as all that other junk is turned off, it shouldn't be that hard to find the reason for the local failure. Ideally, the logging would only be going for a little while before the failure happens, but if that is not possible, just leave logging on, and then when the error happens, shut down Outlook and send the log.

You might then want to turn logging off, as it can slow down performance.

[jcha]

Ok, back again.
The user indicates the Local Failure happened at 2:01pm PST.

[fsiegel]

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

[jcha]

I've attached some appointments from a user that keeps receiving failure notices.

Here is some background information on us:
We use shared calendars keep track of availability.
All employees use appointments to block off time eg. Lunch and Break.

Like I mentioned before this is only happening to the newer employees with the most recent version of the Zimbra Connector v6.0. No complaints from veteran employees which is most likely using versions 4.5 or 5.0.

[fsiegel]

Thanks. I can reproduce this on Outlook 2003, but not Outlook 2007. I'm not sure why Outlook 2003 complains and Outlook 2007 does not, but I may be able to hack this some way.

But the next question is how did you create it? When I imported your .ics into Outlook 2003, and then tried to sync to Zimbra, I got the error. But when I created it in the UI (a daily recurring with no end date), it synced fine.

I noticed some EXDATE clauses in the .ics. So I'm wondering, how were these appointment created in Outlook?

I suppose to get around this, if you created daily appts with an end date of less than 999 days out, that would work. You might try that and let me know.

Once I get some info from you, I can file a bug.