The case of disappearing Update Rollup 4
For a brief period of time on 9/9 (Tuesday), a pre-release version of Update Rollup 4 for Exchange Server 2007 Service Pack 1 (KB952580) was inadvertently made available to Microsoft Update, the Microsoft Update Catalog, and WSUS servers for download. While we quickly identified and removed the update from Microsoft Update within a short period of time, some servers using these distribution methods might have detected, downloaded and/or installed this version of the update.
An issue exists with this pre-release version of the Rollup 4 with regard to the Exchange Web Service (EWS) that creates the potential for a continuous crashing cycle. The final version of this update will be released shortly and we recommend customers who have not already installed the update to wait to do so. For those who have already installed the update, we recommend uninstalling this version. Once a new the final version is made available, all Exchange 2007 SP1 Installations with pre-release version of Rollup 4 installed will be offered the final version which will install over the pre-release.
We apologize for any inconvenience and are working to make sure this does not happen again. While at this time we are not aware of many customers being affected by this, we wanted to let you know in case you are currently testing what you downloaded 2 days ago.
Identification of Rollup version via Add/Remove Programs:
To identify the version of the Rollup that you have installed, press the ‘Click here for support information’ link on the rollup, under your Add or Remove Programs applet in Control Panel:
Identification of the rollup version via the Registry:
To identify if the rollup is installed via the registry, the ‘DisplayVersion’ value shown below will be 1. The newer version of the rollup to be released will consist of a 2 or higher.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\KB952954 Name: DisplayVersion Type: REG_SZ Data: 1
Identification of crashes caused by this problem:
If you are experiencing crashes caused by this problem, you will see the following event being logged on your server:
Log Name: Application Source: MSExchange Common Event ID: 4999 Task Category: General Level: Error Keywords: Classic Description: Watson report about to be sent to dw20.exe for process id: 9364, with parameters: E12IIS, RTL-AMD64, 08.01.0240.006, WS, M.E.Services, M.E.S.C.PerfCounterReader.GetCPUPercent, System.InvalidOperationException, d177, 08.01.0311.001. ErrorReportingEnabled: True
Event Xml: <Event xmlns=’http://schemas.microsoft.com/win/2004/08/events/event’> <System> <Provider Name=’MSExchange Common’ /> <EventID Qualifiers=’16388′>4999</EventID> <Level>2</Level> <Task>1</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime=’2008-09-11T00:49:11.000Z’ /> <EventRecordID>1262</EventRecordID> <Channel>Application</Channel> <Computer>test.contoso.com</Computer> <Security /> </System> <EventData> <Data>9364</Data> <Data>E12IIS</Data> <Data>RTL-AMD64</Data> <Data>08.01.0240.006</Data> <Data>WS</Data> <Data>M.E.Services</Data> <Data>M.E.S.C.PerfCounterReader.GetCPUPercent</Data> <Data>System.InvalidOperationException</Data> <Data>d177</Data> <Data>08.01.0311.001</Data> <Data>True</Data> </EventData> </Event>
|Share this post :|
Oh Microsoft. Go you! 🙂