Environment
GroupWise 7.03 through the GWIA to an external Microsoft Exchange system that contains the following:
Microsoft Windows Server 2003 w/SP2 Enterprise Edition
Microsoft Exchange 2003 w/SP2
Microsoft Office Outlook 2003 SP3
Microsoft Exchange 2003 w/SP2
Microsoft Office Outlook 2003 SP3
Situation
Same as KB 347728 except no Exchange Gateway is used.
User sends a recurring appointment to a Microsoft Outlook client. When the appointments arrive they are shown as one appointment and can not be fanned out to show all, and may not be accepted. Appointment can be accepted by some third party email programs like Gmail. Microsoft Outlook WebAccess does not have the problem either. In some cases the problem is caused by a bug that is on the Exchange server. See KB 925873 article.http://support.microsoft.com//kb/925873 . In this case, the patch and steps provided did not fix the issue. Further research on Microsoft's part revealed that the problem is in the Outlook client and even though results should be the same between the Outlook client and Outlook WebAccess, they are designed differently. Microsoft has declared that this is working as designed.
User sends a recurring appointment to a Microsoft Outlook client. When the appointments arrive they are shown as one appointment and can not be fanned out to show all, and may not be accepted. Appointment can be accepted by some third party email programs like Gmail. Microsoft Outlook WebAccess does not have the problem either. In some cases the problem is caused by a bug that is on the Exchange server. See KB 925873 article.http://support.microsoft.com//kb/925873 . In this case, the patch and steps provided did not fix the issue. Further research on Microsoft's part revealed that the problem is in the Outlook client and even though results should be the same between the Outlook client and Outlook WebAccess, they are designed differently. Microsoft has declared that this is working as designed.
Resolution
Update June 6th 2013 - Some enhancements have been made to GroupWise in order to better workaround Microsoft not using the BYYEARDAY field. Some of the changes are available in later GroupWise 8 code, and others available in GroupWise 2012.
The issue exists in the Microsoft Outlook client.
It does not support the use of the BYYEARDAY field.
As of April 2008, Microsoft was tracking the amount of users who were experiencing this issue, but due to few numbers they were not yet ready to pursue a fix for this issue. Until they see a sufficient demand for this feature it is considered to be working as designed and maintain no future plans to fix it.
Novell Development is considering possible enhancements to help the situation.
The RFC rule containing the use of recurrence is 2445, section 4.3.10 and can be found at http://tools.ietf.org/html/rfc2445 or http://www.w3.org/2002/12/cal/rfc2445#sec4.3.10. As the BYYEARDAY field is defined in RFC 2445 and not supported by Microsoft.
The issue exists in the Microsoft Outlook client.
It does not support the use of the BYYEARDAY field.
As of April 2008, Microsoft was tracking the amount of users who were experiencing this issue, but due to few numbers they were not yet ready to pursue a fix for this issue. Until they see a sufficient demand for this feature it is considered to be working as designed and maintain no future plans to fix it.
Novell Development is considering possible enhancements to help the situation.
The RFC rule containing the use of recurrence is 2445, section 4.3.10 and can be found at http://tools.ietf.org/html/rfc2445 or http://www.w3.org/2002/12/cal/rfc2445#sec4.3.10. As the BYYEARDAY field is defined in RFC 2445 and not supported by Microsoft.