Description of Update Rollup 3-v2 for Exchange Server 2007 Service Pack 3
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.
Microsoft has released Update Rollup 3 for Microsoft Exchange Server 2007 Service Pack 3 (SP3). This article describes the following information about the update rollup:
The issues that the update rollup resolves
How to obtain the update rollup
Issues that the update rollup resolves
Update Rollup 3 for Exchange 2007 SP3 resolves the issues that are described in the following Microsoft Knowledge Base articles:
"Insufficient system resources exist to complete the requested service" error message when you try to extend database files in an Exchange Server 2007 environment |
|
A meeting request may not open correctly after you disable the "Display sender's name on messages" option in the EMC of Exchange Server 2007 SP2 or SP3 |
|
Event ID 1160 is logged and the Microsoft Exchange Information Store service randomly stops responding on an Exchange Server 2007 server |
|
A meeting response status from an external attendee may be incorrect if you send the meeting request from an Exchange Server 2007 environment |
|
A calendar synchronization times out when you use ActiveSync to synchronize with an Exchange Server 2007 mailbox on a mobile device |
|
An item is removed unexpectedly from a public folder in an Exchange Server 2007 environment |
|
The "Require SSL" setting is unexpectedly unselected on the RPC virtual directory on an Exchange Server 2007 server |
|
The "ScheduleOnlyDuringWorkHours" property of a resource mailbox may not function as expected in an Exchange Server 2007 environment |
|
DTMF inputs are not accepted by a UM auto attendant while the greeting message is playing in an Exchange Server 2007 environment [] |
|
The "Test-Replicationhealth" cmdlet fails on a stretched cluster in an Exchange Server 2007 SP3 CCR environment |
|
The Microsoft.Exchange.Search.ExSearch.exe process consumes 100% CPU after you apply Update Rollup 1 or Update Rollup 2 for Exchange Server 2007 SP3 on the passive node of a SCC |
|
"554 5.6.0" NDR message when you send an email message to an Exchange Server 2007 mailbox from a Macintosh computer |
|
"Object <transport rule name> has been corrupted and it is in an inconsistent state" warning message when you view a transport rule on an Exchange Server 2007 SP3 server |
|
The W3WP.exe process may crash when a WebDAV client connects to an Exchange Server 2007 server |
|
The MsExchangeTransport service stops when the Hub server occasionally stops handling the mail flow in an Exchange Server 2007 environment |
|
The EdgeTransport.exe process crashes if the pipeline tracing feature is enabled together with a redirect transport rule in an Exchange Server 2007 environment |
|
"Computer account for 'SMTPSVC/<FQDN of Hub/Transport-Server>' not found in Active Directory" error message in an Exchange Server 2007 environment |
|
The returned URL is incorrect when you use the WebDAV "X-MS-ENUMATTS" method to enumerate an attachment in an Exchange Server 2007 environment |
|
Duplicate read receipts are sent when using a POP3 client or an IMAP4 client in an Exchange Server 2007 environment |
|
Some body parts of a message are displayed as attachments when an Exchange Server 2007 user sends the message by using a third-party mail client |
|
VSS backup fails on a passive node of an Exchange Server 2007 CCR cluster and Event ID 2034 is logged |
|
The values of total items that are returned by running the "Export-ActiveSyncLog" cmdlet on an Exchange Server 2007 server are incorrect |
|
Fax communication sessions are dropped by an Exchange Server 2007 Unified Messaging server |
|
A meeting request is stamped as Busy instead of Tentative when it is sent from an external user to an Exchange Server 2007 user |
Pre-Installation Tasks
Forefront Security for Exchange Server
If you are using Microsoft Forefront Security for Exchange Server, you must disable Forefront Security for Exchange Server before you install Update Rollup 3-v2 for Exchange 2007 SP3. After you install the update rollup package, you must re-enable Forefront Security for Exchange Server. To do this, follow these steps:
To disable Forefront Security for Exchange Server, run the fscutility /disable command.
To enable Forefront Security for Exchange Server, run the fscutility /enable command.
Note
If you do not disable Forefront Security for Exchange Server before you install the update rollup, the Information Store service and the Transport service do not start.
Public Folders
If you are using public folders in your Exchange 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 steps in the following procedure before you install Update Rollup 3-v2 for Exchange 2007 SP3.
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 2007 continues to function correctly. In this case, you can follow these steps to fix the issue.
Click Start, type adsiedit.msc in the Start Search box, and then press Enter.
In the ADSIEdit MMC window, click Action, and then click Connect to.
In the Well-known naming context list, click Configuration.
Expand the following list items and subitems in this order:
CN=Configuration,DC=Contoso,DC=com
CN=Services
CN=Microsoft Exchange
CN=<OrganizationName>
CN=Administrative Groups
CN=Servers
CN=<ServerName>
CN=Information Store
CN=Second Storage Group
Note
In this list, <OrganizationName> and <ServerName> represent the actual names of the organization and server.
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.
Important
These changes take effect after all Exchange 2007 servers in the organization that host public folder databases are upgraded to Update Rollup 3-v2 for Exchange 2007 SP3.
If you install Update Rollup 3-v2 for Exchange Server 2007 SP3 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 |
Update Rollup Information
Update Rollup 3-v2 for Exchange Server 2007 SP3 was released on March 30, 2011. To obtain this update rollup from the Microsoft Download Center, see Update Rollup 3-v2 for Exchange Server 2007 Service Pack 3 (KB2530488).
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 SP3, see the "Update rollups for Exchange Server 2007 Service Pack 3" 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, to Exchange 2007 Service Pack 1 (SP1), or to Exchange 2007 Service Pack 2 (SP2). The series of update rollup packages for Exchange Server 2007 SP3 is independent of the corresponding series of update rollups for Exchange Server 2007 RTM, for Exchange 2007 SP1, or for Exchange 2007 SP2.