Support for Office 2003 ends April 8, 2014
Microsoft will end support for Office 2003 on April 8, 2014. This change will affect your software updates and security options. Article ID: 899704 - View products that this article applies to. On This PageThis article describes issues that may occur with meeting information if you use Microsoft Outlook or Microsoft Outlook Web Access in an organization that is using Microsoft Exchange Server. This article describes the following scenarios in which Calendar items may be removed from the Calendar:
This article also describes the following scenarios in which the Calendar items may become out of date:
Finally, this article recommends the following best practices for working with meeting information:
INTRODUCTIONThis article describes common scenarios in which Calendar information may be removed from the Calendar or may become out of date. This article describes a workaround for the issue that is described in each scenario. This article also describes best practices to create recurring meetings, to add new attendees to meetings, and to share your Calendar with delegates. For more information about Calendar best practices, see the following white paper: Best practices when using the Outlook Calendar
(http://office.microsoft.com/en-us/outlook-help/best-practices-when-using-the-outlook-calendar-HA104004449.aspx)
More informationScenarios in which items may be removed from the CalendarMultiple users receive meeting requests for a mailbox ownerSymptomsThis scenario involves a meeting organizer, a recipient who is the manager, and a delegate who has Editor rights to the manager's Calendar folder and to the manager's Tasks folder. The delegate receives copies of all the manager's meeting requests, but the manager has also elected to see the meeting requests. Therefore, both the manager and the delegate receive every meeting request that is sent to the manager.Consider the following scenario:
If the manager opens the meeting request after the delegate accepts the meeting request, the response status of the meeting request is "Accepted". Therefore, when the meeting request is deleted, the corresponding meeting item is also deleted from the Calendar. ResolutionTo resolve this problem, obtain and install Office 2003 Service Pack 2. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 906451
(http://support.microsoft.com/kb/906451/
)
Issues that are fixed in Outlook 2003 by Office 2003 Service Pack 2
StatusMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.WorkaroundTo work around this issue, use one of the following methods:
You delete a meeting request on one computer after you accept the same meeting request on another computerSymptomsThis scenario involves two computers that connect to the same Exchange Server mailbox. For example, this scenario may include a desktop computer that is using Online mode and a portable computer that is using Cached Exchange Mode.Consider the following scenario:
ResolutionTo resolve this problem, obtain and install Office 2003 Service Pack 2. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 906451
(http://support.microsoft.com/kb/906451/
)
Issues that are fixed in Outlook 2003 by Office 2003 Service Pack 2
Note The solution may require more that just an update to your Microsoft Office Outlook 2003 client installation. For example, if you are using a BlackBerry device as one of the clients in the above scenarios, you will require an update to the CDO.DLL version on the BlackBerry Enterprise Server to which the BlackBerry device wirelessly connects, as well as an update to the BlackBerry Enterprise Server. Additionally, if you use Outlook Web Access as one of the clients in the above scenario, you will need to obtain the latest service pack for Exchange Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 836993
(http://support.microsoft.com/kb/836993/
)
How to obtain the latest service packs for Exchange Server 2003
StatusThis behavior is by design.WorkaroundWe recommend that you process meeting requests on only one computer.You cancel or delete a meeting without sending an updateIf you cancel or delete a meeting, but you do not send the update, the meeting is only removed from your calendar. If you are the organizer, no one is notified that you are canceling the meeting. If you are an attendee, no one is notified that you are not attending.WorkaroundTo work around this issue, send a cancellation notice. To correctly cancel a meeting that you organized or that you do not want to attend, follow these steps.
You frequently change recurring meetingsA frequently updated meeting can create confusion for attendees. For example, if you make frequent changes to the recurrence pattern of the meeting, many updates are sent to the attendees. The recipients may be confused and may incorrectly remove the meeting from the Calendar.Additional updates may be sent in the following scenario. The attendees list has two instances of the same person's name. You delete one of the names. If you click Send updates only to added or deleted attendees when you send the update, the person whose name you deleted receives a cancellation notice. Similarly, if you click Send update to all attendees when you send the meeting update, the person whose name you deleted receives both a cancellation notice and an update. In this scenario, the recipients may be confused and may incorrectly remove the meeting from the Calendar. WorkaroundIf you must make any changes that will potentially cause confusion for any attendees, we recommend that you cancel the meeting for all attendees. After the meeting is removed from the attendees' Calendars, you can send a new meeting request that includes all the changes that you want to make.If you have to schedule a weekly meeting that you must change each week, you may want to send a single instance of the meeting request each week. Scenarios in which Calendar items may become inaccurateForwarded meetings lead to inaccurate information in the calendarThe meeting organizer should not forward meeting requests. Consider the following scenario:
You forward a meeting request as a meeting attendeeWhen you forward a meeting (recurring or single-instance) to a new attendee, the new attendee is not added to the original meeting unless the attendee sends a meeting response. All updates to the meeting are not sent to the attendee, resulting in out-of-date information in that attendee's calendar. When you use Microsoft Outlook to accept a recurring meeting request that was forwarded to you by an organizer of attendee, you may not be added to the meeting attendee list. When the organizer of the attendee views the list in Outlook or Outlook Web Access, your name does not appear in the list. You use Outlook Web Access to accept a meetingIf you use Outlook Web Access to accept a meeting request, data loss may occur if the meeting has been modified in Outlook. Consider the following scenario:
WorkaroundTo work around this issue, accept the meeting request in the Inbox in Outlook before you change the meeting item in the Calendar.You do not click Send Update when you change a meeting that you organizeWhen you change a meeting that you organize, you must click Send Update to make sure that the changes are sent to everyone that you invited to the meeting. For example, you modify the date or the time of a meeting. If you do not send an update, invitees will not be informed of the new meeting time. To send an update, follow these steps:
You do not process a meeting request in the InboxWe recommend that you always accept or decline a meeting request from the Inbox. If you accept or decline a meeting by using the meeting item in the Calendar in Outlook, the meeting request remains in the Inbox. If you do not process the meeting request in the Inbox, the following issues may occur:
Your personal notes are lost after a meeting update is receivedWe recommend that you do not take personal notes in the body of a meeting item in the calendar. If you are an attendee of this meeting, your notes will be lost if a meeting update is received. If you are the organizer, your personal notes will be sent to everyone on the attendee list. Consider the following scenario:
StatusThis behavior is by design.WorkaroundMicrosoft recommends taking personal notes using the Notes feature in Outlook or another product, such as Microsoft Office Work or Microsoft Office OneNote.Best practices for working with meeting informationConvert an existing appointment to a meeting requestSometimes you may have to convert an existing appointment in your Outlook Calendar to a meeting request. Follow these steps to correctly convert the appointment to a meeting request:
Limit the number of delegates who have access to your CalendarOutlook does not have a defined limit for the number of delegates that you can add to your mailbox. Even though Outlook does not have a defined limit for delegates, other resource limitations will eventually limit the number of delegates you can add to your mailbox. For example, if you add many delegates to your mailbox, the 32-KB limit for rules data prevents you from saving delegate rules to the mailbox. This 32-KB limit is imposed by the server. When you reach this limit, you receive the following error message when you try to add a new delegate:Unable to forward meeting-related messages. There may be too many rules on the server. On the Tools menu, click Rules and Alerts, remove some rules, and then try again. Unable to modify folder rule.
When we developed and tested Outlook, we tested a maximum of four delegates. To prevent incorrect or missing meeting information, we recommend that you use only one delegate with Editor permissions. Make sure to decide whether the delegate or the mailbox owner will process all the meeting requests. See the "Multiple users receive meeting requests for a mailbox owner" section for more information. If more than one user must have access to your mailbox, carefully consider whether these users have to be delegates. You may want to give the user Review permissions to your folder instead. To give another user Reviewer permissions, follow these steps:
241325
(http://support.microsoft.com/kb/241325/
)
"There is not enough space on the Microsoft Exchange Server to store all of your rules" error message when you create or import a rule in Outlook
Schedule end dates on recurring meetingsWe recommend that add a definite end date when you schedule a recurring meeting. When you add a definite end date, you may prevent issues that may occur if you have to update the meeting several times. If you schedule an end date on meetings, you can create a new meeting if you realize that the meeting has to be frequently modified.Turn on Calendar logging for executives and for other frequent usersYou can turn on Outlook 2003 Calendar logging for executives and for other frequent users. Calendar logging has a minimal effect on the performance of most computers. When you use Calendar logging, a log file is created. You can use this log file to help troubleshoot meeting issues if one of these users reports a problem.For more information about the Calendar logging feature in Outlook 2003 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base: 841615
(http://support.microsoft.com/kb/841615/
)
Description of the Calendar logging feature in Outlook 2003 Service Pack 1
References817954
(http://support.microsoft.com/kb/817954/
)
You receive no warnings when a meeting is overwritten in your Outlook 2003 Calendar
824097
(http://support.microsoft.com/kb/824097/
)
A meeting is canceled after you receive both a meeting update and a meeting cancellation in Outlook 2003
890436
(http://support.microsoft.com/kb/890436/
)
How to troubleshoot missing and duplicate appointments in Outlook
886688
(http://support.microsoft.com/kb/886688/
)
Recurring appointment that is associated with a meeting request may be removed from a recipient's calendar
830003
(http://support.microsoft.com/kb/830003/
)
Description of the Outlook 2003 hotfix package: December 17, 2003
837019
(http://support.microsoft.com/kb/837019/
)
Description of the Outlook 2003 hotfix package: March 17, 2004
222388
(http://support.microsoft.com/kb/222388/
)
Meeting cancellation and update messages sent to wrong attendees in Outlook
821695
(http://support.microsoft.com/kb/821695/
)
Invitations are not sent to attendees who are added through Meeting Workspace in Outlook 2003
822586
(http://support.microsoft.com/kb/822586/
)
Users are not added to the attendee list of a recurring meeting in Outlook
924470
(http://support.microsoft.com/kb/924470/
)
Outlook delegate feature in mixed versions of Microsoft Outlook and Entourage
309185
(http://support.microsoft.com/kb/309185/
)
Meetings that are placed in an owner's calendar by a delegate do not display free/busy information for additional meeting attendees in Outlook
312433
(http://support.microsoft.com/kb/312433/
)
Accepting or denying a meeting request causes a "5.1.1" non-delivery report in Exchange Server
883915
(http://support.microsoft.com/kb/883915/
)
Description of the Outlook 2003 post-Service Pack 1 hotfix package: September 9, 2004
899919
(http://support.microsoft.com/kb/899919/
)
Developer information about the calendar changes in Outlook 2003 Service Pack 2, Exchange Server 2003 Service Pack 2 and later versions
246480
(http://support.microsoft.com/kb/246480/
)
Outlook doesn't process meeting requests with rules active
829235
(http://support.microsoft.com/kb/829235/
)
Outlook 2003 may stop responding when you accept a meeting request
894470
(http://support.microsoft.com/kb/894470/
)
A meeting is removed from your Outlook Calendar after you accept the meeting and then delete the accepted meeting request
887616
(http://support.microsoft.com/kb/887616/
)
Description of Office 2003 Service Pack 2
906671
(http://support.microsoft.com/kb/906671/
)
Microsoft Exchange Server 2003 Service Pack 2 release notes
PropertiesArticle ID: 899704 - Last Review: February 24, 2014 - Revision: 5.1 Applies to
|

Back to the top











