Microsoft KB Archive/937494

= Description of the Outlook 2007 hotfix package: June 12, 2007 =

Article ID: 937494

Article Last Modified on 9/11/2007

-

APPLIES TO


 * Microsoft Office Outlook 2007

-



SUMMARY
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.



Issues that the hotfix package fixes
This 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 event that resembles the following event is logged in the Application log: Event Type: Warning

Event Source: MSExchangeSA

Event Category: RFR Interface

Event ID: 9234

Date:

Time:

User: N/A

Computer:

Description: Referral Interface was not able to find an msExchExchangeServer object with legacyExchangeDN '/o= /ou=Exchange Administrative Group (group)/cn=Configuration/cn=Servers/cn= ' 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 &quot;Sync Issues&quot; folder and to the Conflicts folder. You send a meeting request that contains an attendee to which you cannot 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.</li> 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.</li> You accept an all-day event request. Then, you schedule another all-day event that spans the same times as the all-day event that you accepted. When you switch between events, the event that you scheduled may disappear. When you switch to the accepted event and then switch back to the scheduled event, the scheduled event reappears.</li> 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.</li> 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.</li> You are the organizer of a recurring meeting. When you open the recurring meeting, the meeting opens as a Send Cancellation action.</li> 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.

</li> 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: <ul> If the body of the recurring meeting message is small, the body of the exception message is now large.</li> If the body of the recurring meeting message is large, the body of the exception message is now blank.</li></ul>

Note A large message body for a personal folders (.pst) file is 8 kilobytes (KB) or larger.</li> 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.

</li> 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.</li></ul>

<div class="moreinformation_section">

Hotfix information
The following file is available for download from the Microsoft Download Center:

Download the Outlook 2007 hotfix package now.

Release Date: June 12, 2007

For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:

119591 How to obtain Microsoft support files from online services

Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.

Prerequisites
There are no prerequisites for installing this hotfix.

Restart information
You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information
This hotfix is not replaced by any later hotfix.

Registry information
You do not have to create any registry keys or modify any registry keys to use any hotfixes that this package contains.

File information
This hotfix may not contain all the files that you must have to fully update a product to the latest build. This hotfix contains only the files that you must have to correct the issues that this article lists.

The global version of this hotfix package uses a Microsoft Windows Installer package to install the hotfix package. The dates and the times for these files are listed in Coordinated Universal Time (UTC) in the following table. When you view the file information, the date 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.

Download information

Microsoft Windows Installer .msp file information

After the hotfix is installed, the global version of this hotfix has the file attributes, or a later version of the file attributes, that are listed in the following table:

Additional notes

<ul> For more information about how to install this hotfix, see the Readme.txt file that is included in the hotfix package.</li> For more information about the terminology that Microsoft uses for software that is corrected after it is released, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

</li></ul>

Additional query words: outlook2007 outlook2k7 outlook12 ol2007 ol2k7 ol12

Keywords: kberrmsg kbbug kbfix kbprint kbqfe kbpubtypekc kbhotfixrollup kbcalendar kbexpertiseinter kbhotfixserver kboffice2007postrtmfix KB937494

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.