Microsoft Knowledge Base Email Alertz

KBAlertz.com: An update to a recurring meeting request that is sent from Exchange Server 2003 does not occur on the receiver side

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]

Search KbAlertz

Advanced Search

Webmasters
Put kbAlertz on your website.
[ Click Here for more! ]





ASP.NET 2.0 Web Hosting with SQL 2005: Click Here!
Discount ASP.NET Hosting


Bug Tracking Software
For bug tracking software or defect tracking software or issue tracking software, visit Axosoft.


Community Site



We Send hundreds of thousands of emails using ASP.NET Email



Expert Web Design & Graphic Design
Design44.com




Mentioned In








Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks




An update to a recurring meeting request that is sent from Exchange Server 2003 does not occur on the receiver side

Article ID:913579
Last Review:April 18, 2008
Revision:1.1
On This Page

SYMPTOMS

Consider the following scenario. A recurring meeting request is sent from a Microsoft Exchange Server 2003 user to an external recipient, such as a Lotus Notes user in a different organization. Then, the meeting is packaged in an iCalendar attachment. If an update to that meeting is sent from Exchange Server, Exchange Server sends a new iCalendar attachment that has the RRULE property updated. However, Exchange Server does not increase the SEQUENCE property as required by Request for Comment (RFC) 2445, "iCalendar." In this scenario, the update does not occur on the receiver side.

Back to the top

RESOLUTION

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support (http://support.microsoft.com/contactus/?ws=support)
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

You must have Microsoft Exchange Server 2003 SP2 installed to apply this hotfix.

Restart requirement

You do not have to restart the computer after you apply this software update. However, the Exchange Information Store, Microsoft Search, the IIS Admin Service, and all other dependent services will be restarted to apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other software updates.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
File nameFile versionFile sizeDateTime
Davex.dll6.5.7653.301,132,03205-Mar-200821:27
Exoledb.dll6.5.7653.302,623,48805-Mar-200805:28
Exosal.dll6.5.7653.3070,14405-Mar-200821:18
Mdbmsg.dll6.5.7653.303,381,24805-Mar-200818:00
Store.exe6.5.7653.305,266,43205-Mar-200821:19

Back to the top

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Back to the top

MORE INFORMATION

For more information, click the following article numbers to view the articles in the Microsoft Knowledge Base:
817903 (http://kbalertz.com/Feedback.aspx?kbNumber=817903/) New naming schema for Exchange Server software update packages
824684 (http://kbalertz.com/Feedback.aspx?kbNumber=824684/) Description of the standard terminology that is used to describe Microsoft software updates

Back to the top

REFERENCES

For more information about the iCalendar attachments and about the RRULE and SEQUENCE properties, visit the following Microsoft Web site:
http://www.ietf.org/rfc/rfc2445.txt (http://www.ietf.org/rfc/rfc2445.txt)
Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.

Back to the top


APPLIES TO
Microsoft Exchange Server 2003 Standard Edition
Microsoft Exchange Server 2003 Enterprise Edition

Back to the top

Keywords: 
kbautohotfix kbexpertiseinter kbhotfixserver kbqfe kbfix kbbug kbpubtypekc KB913579

Back to the top

       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate

Be the first to leave feedback, to help others about this knowledge base article.

(Optional) Name

(Optional) Public URL Or Email

Comments
No HTML -- Text Only Please