Description of Update Rollup 2 for Exchange Server 2007 Service Pack 2
Microsoft Exchange Server 2007 will reach end of support on April 11, 2017. To stay supported, you will need to upgrade. For more information, see Resources to help you upgrade your Office 2007 servers and clients.
Applies to: Exchange Server 2007 SP2
Microsoft has released Update Rollup 2 for Exchange Server 2007 Service Pack 2. This topic describes the following:
The issues that the update rollup fixes
How to obtain the update rollup
For More Information
Issues That the Update Rollup Fixes
Update Rollup 2 for Exchange Server 2007 Service Pack 2 fixes the issues that are described in the following Microsoft Knowledge Base articles.
Exchange Server 2003 may generate duplicate journal reports in a mixed Exchange Server 2003 and Exchange Server 2007 environment |
|
The "age limits" function of a public folder do not work as expected in an Exchange Server 2007 environment |
|
A Computer that is running Microsoft Exchange Server 2007 that has the Client Access Server (CAS) role installed becomes slow when a user tries to open a folder that contains many items |
|
An appointment is displayed incorrectly as an all-day event if you use a mobile device to synchronize the calendar in Outlook |
|
The Auto Attendant 'Business Hours' schedule is not updated in Exchange Server 2007 when the DST setting is changed |
|
Exchange Server 2007 users intermittently cannot access an Exchange Server 2003 user's Free/Busy information in Office Outlook 2007 |
|
When Unified Messaging-enabled users call Outlook Voice Access on Exchange Server 2007 to play voice mails messages, there is a delay before the voice mail message is played |
|
The Microsoft Exchange Server 2007 log or database experiences abnormal growth |
|
When a user sends e-mail messages to a remote domain, some e-mail messages are queued on an Exchange Server 2007 Hub Transport server or Edge server |
|
A return address is split into two separate and incomplete addresses when a recipient replies to a specific message in Exchange 2007 |
|
Some message parts are not readable when Exchange Server 2007 must convert the message part encoding from binary or from 8 bit to 7 bit. |
|
Incorrect exceptions are generated for a recurring iCalendar message when an Exchange Server 2007 server processes an SMTP message that contains the iCalendar message part. |
|
OWA does not highlight misspelled words in an Exchange Server 2007 CAS proxy environment. |
|
Some attendees cannot receive a meeting cancellation notification when the appointment recurrence pattern is changed by using EWS in Exchange Server 2007 |
|
Unread messages are marked as "read" when Exchange Server 2007 processes the EXAMINE command |
|
You still receive an error message when you run the Test-OwaConnectivity command after you apply hotfix KB957485 in Exchange Server 2007 |
|
Store sessions are not released when you run the Add-PublicFolderClientPermission cmdlet or the Remove-PublicFolderClientPermission cmdlet in public folders on a computer that is running Exchange Server 2007 |
|
A new accepted domain that is added does not work in an Exchange Server 2007 organization |
|
The folders returned during an IMAP4 LSUB command are incorrect on an Exchange Server 2007 mailbox |
|
The EdgeTransport.exe process crashes intermittently on an Exchange Server 2007 server |
|
Exchange Server 2007 performance counter "Messages queued for submission" performance counter displays an incorrect value |
|
You receive an NDR you try to send messages through your Microsoft Exchange Server 2007 account |
|
Exchange Server 2007 OWA users receive an error message when the users change the display line for the search results on the address books |
|
The "Task Owner" field is not set when you create a task in Outlook Web Access |
|
A call transfer fails by using key mapping in a mixed Exchange Server 2007 UM server and OCS 2007 environment |
|
EWS proxying requests fail after you run Availability Service requests in a CAS to CAS proxying scenario in Exchange Server 2007 |
|
You cannot log on to your mailbox and you receive an error in an Exchange server 2003 and Exchange Server 2007 coexist environment |
|
Event 2104 and event 2147 are continuously logged in an Exchange Server 2007 Cluster Continuous Replication (CCR) environment |
|
An attachment of a meeting request cannot be opened when you use a CDO application to accept a meeting request in Exchange Server 2007 |
|
The misspelled word of a message loses its custom format when an Exchange Server 2007 user writes the message in OWA |
|
The RemoveDelegate operation of EWS fails, and then a "500 internal server" error response and event ID 4999 are logged in an Exchange Server 2007 server |
|
The custom form of a meeting request is removed in the recipients' calendar in an Exchange Server 2007 environment |
|
When an IMAP4 client sends a FETCH (bodystructure) request to a server that is running the Exchange Server 2007 IMAP4 service, a corrupted response is sent as a reply |
|
Messages that have duplicate message IDs are deleted when they are archived to an Exchange 2007 mailbox |
|
The free/busy information of an Exchange Server 2007 user is not displayed |
|
Microsoft Exchange Transport services crashes and a "StackOverflowException" error is logged when Message Journaling is enabled on Exchange Server 2007 |
|
Warning message when you run the Update-AddressList cmdlet in Exchange Management Shell on Exchange Server 2007: "Failed to update recipient" |
|
Exchange Server 2007 Unified Messaging incorrectly plays a nonbusiness hours greeting when someone call during holiday |
|
You cannot edit a transport rule if one or more of the recipient addresses are disabled or removed in an Exchange Server 2007 server |
|
The Calendar Month View displays a numeric date and not an abbreviated month name when you set the Regional Settings to Japanese or to Korean in Outlook Web Access for Exchange Server 2007 |
|
When you edit an e-mail message in OWA, the font changes to the default Internet Explorer font |
|
The message delivery time is incorrect when you send e-mail messages by using an IMAP4 client together with the APPEND command in Exchange Server 2007 |
|
An incorrect value for DumpsterMessagesDeleted is reported in an Exchange Server 2007 environment |
|
The time for an updated meeting request is incorrectly shown in an exception instance of a recurring meeting request on an Exchange Server 2007 environment |
|
The EXOLEDB component is not initialized successfully when you start Exchange Information Store Service on an Exchange Server 2007 server |
|
A move operation on a folder fails when the "ptagProvisionedFid" attribute is invalid in an Exchange Server 2007 environment |
|
One or more errors occur when you set the Message Access logging level to "Expert" in an Exchange Server 2007 SP2 server |
|
Non-ASCII characters in a display name of a forwarded message are shown with "?" when the display name of a contact is in East Asia characters in an Exchange Server 2007 environment |
|
Error message when a client that uses the WebDAV protocol to connect to an Exchange Server 2007 server: "Error 1000" |
|
The "Proxy server name" field is shown incorrectly in Outlook Web Access in an Exchange Server 2007 CAS-to-CAS proxy environment |
|
Windows Server 2008 VSS backup plug-in fails to back up Exchange 2007 Service Pack 2 databases that reside on a volume mount point |
Pre-Installation Tasks
If you are using public folders in your Exchange Server 2007 organization, and if you have set the retention period on the public folder database to a value that is greater than 123 days, you must follow the following steps before you install Update Rollup 2 for Exchange Server 2007 SP2.
Click Start, in the Start Search box, type adsiedit.msc, and then press Enter.
In the ADSIEdit MMC, click Action, and then click Connect to.
In the Well-known naming context list, click Configuration.
Expand the following list item and subitems in order:
CN=Configuration,DC=Domain,DC=com
CN=Services
CN=Microsoft Exchange
CN=OrgName
CN=Administrative Groups
CN=Servers
CN=ServerName
CN=Information Store
CN=Second Storage Group
Double-click CN=Public Folder Database.
Double-click msExchOverallAgeLimit.
Change the existing value from seconds to days by dividing the existing value by 86,400.
Note
You must repeat these steps on all public folder databases in the Exchange 2007 environment.
If you install Update Rollup 2 for Exchange Server 2007 SP2 without performing these steps, and if you then try to access the public folder settings by using the Exchange Management console, you receive the following error message:
TimeSpan overflowed because the duration is too long
Also, when you try to access Exchange by using Outlook Web Access, you receive the following error message:
Exception
Exception type: Microsoft.Exchange.Clients.Owa.Core.OwaInvalidConfigurationException
Exception message: TimeSpan overflowed because the duration is too long.If you are using public folders, and if you have set the retention period on the public folder database to a value that is less than or equal to 123 days, you receive a warning message. However, Exchange Server 2007 will continue to function correctly. In this case, you can use the following steps to fix the issue:
Click Start, in the Start Search box, type adsiedit.msc, and then press Enter.
In the ADSIEdit snap-in, click Action, and then click Connect to.
In the Well-known naming context list, click Configuration.
In the ADSIEdit snap-in, expand the following item and sub-items in order:
CN=Configuration,DC=Domain,DC=com
CN=Services
CN=Microsoft Exchange
CN=OrgName
CN=Administrative Groups
CN=Servers
CN=ServerName
CN=Information Store
CN= Second Storage Group
Double-click CN=Public Folder Database.
Double-click msExchOverallAgeLimit.
Change the existing value from seconds to days by dividing the existing value by 86,400.
You must repeat these steps on all public folder databases in the Exchange 2007 environment.
Important
These changes take effect after all Exchange Server 2007 servers in the organization that host Public Folder databases are upgraded to Update Rollup 2 for Exchange Server 2007 Service Pack 2.
Update Rollup Information
Update Rollup 1 for Exchange Server 2007 SP2 was released on January 22, 2010. To obtain this update rollup from the Microsoft Download Center, see Update Rollup 2 for Exchange Server 2007 Service Pack 2.
Important
Before you install an update rollup or a service pack, see How to Install the Latest Service Pack or Update Rollup for Exchange 2007 for prerequisites, installation instructions, and known issues. Before you apply an update rollup to clustered Mailbox servers, see Applying Exchange 2007 Update Rollups to Clustered Mailbox Servers.
For more information about the Exchange 2007 servicing model, see Exchange 2007 Servicing.
For a list of update rollups that apply to Exchange Server 2007 SP2, see the "Update rollups for Exchange Server 2007 Service Pack 2" section in How to Obtain the Latest Service Pack or Update Rollup for Exchange 2007.
This update rollup does not apply to Exchange Server 2007 release to manufacturing (RTM) version or to Exchange 2007 Service Pack 1 (SP1). The series of update rollup packages for Exchange Server 2007 SP2 is independent of the corresponding series of update rollups for Exchange Server 2007 RTM or for Exchange 2007 SP1.