Description of the Outlook 2007 hotfix package: June 12, 2007
Symptoms
This article describes the Microsoft Office Outlook 2007 issues that are fixed in the Outlook 2007 hotfix package that is dated June 12, 2007.
This article describes the following items about the hotfix package:The issues that the hotfix package fixes.The prerequisites for installing the hotfix package.Whether you must restart your computer after you install the hotfix package.Whether the hotfix package is replaced by any other hotfix package.Whether you must make any registry changes. The files that the hotfix package contains.
Resolution
Issues that the hotfix package fixesThis hotfix package fixes the following issues that were not previously documented in a Microsoft Knowledge Base article:You try to open a user’s shared calendar in Outlook 2007. If the user’s mailbox is in a different administrative group, the shared mailbox cannot be synchronized correctly. Additionally, an eventthat resembles the following event is logged in the Application log:
Event Type:Warning
Event Source:MSExchangeSA
Event Category:RFR Interface
Event ID:9234
Date:date
Time:time
User:N/A
Computer:server_name
Description: Referral Interface was not able to find an msExchExchangeServer object with legacyExchangeDN ‘/o=Organization_Name/ou=Exchange Administrative Group (group)/cn=Configuration/cn=Servers/cn=server_name’ in the Active Directory.You use a custom solution in a trusted simple MAPI environment to send e-mail messages in Outlook 2007. If an e-mail message contains more than five recipients, the e-mail aliases are not resolved. Additionally, the Outlook security dialog box unexpectedly appears. You have multiple appointments scheduled for a day in the calendar in Outlook 2007. When you print the calendar in Monthly style, only two appointments are printed for the day.
This issue may occur even though there is sufficient room for all the appointments to print for that day. A delegate for your mailbox accepts a meeting request on your behalf. Then,the meeting is updated. When you view the updated meeting request, the No response required button is not displayed. As meeting requests and meeting updates are processed in Outlook, the tracking status and the attendee changes for the meeting requests may cause new style conflicts.
When this issue occurs, the tracking status and the attendee changes are not updated automatically. Therefore,many items may be added to the “Sync Issues” folder and to the Conflicts folder. You send a meeting request that contains anattendee to which youcannot send requests, such as a meeting room. When you reopen the meeting request, the free/busy time for this attendee is not displayed. You send a recurring meeting request to attendees. Then, you update the meeting time for the recurring meeting and then send the update. When you reopen the recurring meeting, the meeting time reverts to the original meeting time. You open a second instance of a recurring meeting. Then, you update the recurring meeting and then send the update. When you do this, the meeting update is sent as expected. However, the changes to the meeting are not saved. You accept an all-day event request. Then, youschedule another all-day event that spans the same times as theall-day event that you accepted. When you switch between events, theevent that you scheduled may disappear. When you switch to the accepted event and then switch back to the scheduled event, the scheduled event reappears.You delete attendees from a recurring meeting and then send the meeting update. When you do this, the update is sent to all attendees. This includes the deleted attendees. You create a meeting exception for a recurring meeting. Then, you restart Outlook and then open the meeting exception. When you do this, the body of the exception message is blank. You are the organizer of a recurring meeting. When you open the recurring meeting, the meeting opens as a Send Cancellation action. You accept a meeting request in Cached Exchange Mode. When you do this, the meeting request is deleted and the meeting acceptance is not sent. Additionally, you may receive the following error message:
Cannot save free/busy information.You create a meeting exception for a recurring meeting. Then,you reopen the meeting exception. When you do this,one of the following symptoms may occur: If the body of the recurring meeting message is small, the body of theexception message is now large.If the body of the recurring meeting message is large, the body of the exception message is now blank.Note A large message body for a personal folders (.pst) file is 8 kilobytes (KB) or larger.When you try to propose a new time for a meeting request, you receive the following error message:
The end date you entered occurs before the start date.You change an existing meeting request. When you click Save and Send Update, the changes to the meeting request are sent as expected. However, the meeting request closes unexpectedly.