[SOLVED] Calendar Issues

[augike1]

I am having some calendar issues with Outlook users. This is what happens.
Mr A. schedules a meeting with Mr B. Mr B. receives the appointment and accepts it. After this,
Mr A. does not get any email confirming that Mr B. accepted his invite and neither Mr A. or Mr B. has this schedule in their Calendar items. Has any one run into this problem before? I will like to know what the root cause is so I can fix this.
I have confirmed that the users have the latest service pack for Office.

[phoenix]

Please update your forum profile with the output of the following command (do not post it in this thread):

zmcontrol -v

You haven't given details of the exact problem your users are experiencing. ZImbra version & release? Is this with the Zimbra Outlook Connector or an IMAP account? If it's the Connector, what's the exact version you're using? If it is the Connector then you've posted this in the wrong forum.

[augike1]

Release 6.0.3_GA_1915.UBUNTU8 UBUNTU8 NETWORK edition.

[phoenix]

Originally Posted by augike1

Release 6.0.3_GA_1915.UBUNTU8 UBUNTU8 NETWORK edition.

I asked you to put that in your forum profile (so we don't have to keep asking you which version is installed), please do that.

It would help if you could you also answer the rest of the questions I've asked?

[augike1]

Sorry for my delay on this. I had to research and test more. This is what I observed. The Calender issues were from Windows users running Microsoft Outlook. I also observed that Outlook users with out of date service packs and old ZCO "Zimbra Connector for Outlook"
My Fix was to Upgrade all Service Packs for MS Office 2003 to SP3 and then upgrade the ZCO to 6.0.6. I also had to schedule down time and upgrade the server too. I now have "Release 6.0.6_GA_2324.UBUNTU8 UBUNTU8 NETWORK edition" Running.
It's almost one month running and I have not heard any complaints.

[augike1]

After my upgrade, this is what I have
MS Office SP3
ZCO 6.0.5902.6
Server: 6.0.6_GA_234.UBUNTU8
NOTE: I am not certain as to what the problem was but after so much troubleshooting and googling, we all came to the same conclusion that this was a bug in the software.