We applied KB952580 on Exchange 2007 Service Pack 1 on windows 2003 enterprise Service Pack 2 X64bit, after we applied this patch, when we go to do a backup we are getting the following errors: Event ID: 305 Description: The operation failed with error code -1811 (0xfffff8ed). EVENT ID: 401 Description: Instance 1: The physical consistency check has completed, but one or more errors were detected. The consistency check has terminated with error code of -106 (0xffffff96). But the transcation logs are being cleared out by BackupExec 12 D. So I really don't understand what these errors mean.

Although we have not had the problem so far, also have applied the rollup 4 for Exchange 2007 SP1 last night since it's available through Windows Update. However, we can't find any article nor description of the rollup 4 anywhere. Can't even find KB952580 on MS. Please provide any information about it if anybody knows about it. Thank you.

It also seemed like it was pulled. I did MSBA around 2 PM EST but when I went to work on the system around 7 PM EST, windows update did not have this patch listed. It would be nice to see that documentation.

Hi there, it seems Microsoft accidentally published "Update Rollup 4 for Exchange Server 2007 Service Pack 1 (KB952580)" for a short time. I saw the update on our WSUS server too, but it seemed curious that non information could be found - so I didn't install the update. After the next WSUS synchronisation, the update rollup was marked as expired and could not be applied. Greetings, MR

You're luck it's not on Windows 2008, it bricked one of my "just about to go live" Hub Transport servers (Services wouldn't start, can't uninstall). Spent today building another one. Cheers MS.Serves me right for not disabling the recommended auto-update autoinstall.

I guess you're not the only one with this issue. I installed the rollup yesterday. It wasn't expired in my WSUS server when I deployed it. I'm running Server 08 and the rollup completed successfully. I've performed a reboot on the server since the rollup and everything appears to be functioning as normal. UNTIL --- This morning I received an error report from the backup. The error was:Consistency check for component '2f0b2d1e-3028-44e3-b122-7457343d9c1b'\'Microsoft Exchange Server\Microsoft Information Store\MAIL-SERVER' failed. Application 'Exchange' will not be avaliable in the backup done at time '9/9/2008 03:00:06 AM'I just got time to look at it this afternoon and can't find a solution as to yet. I hope I don't have to perform a restore because it doesn't sound like uninstalling the rollup will work. I'm going to spend the majority of the day tomorrow working on it!Good luck to all!

Did anyone open up any calls with Microsoft Support on this? ON my CAS servers I am seeing nothing in terms of services not starting or services that cannot start so I guess I am lucky. Just on my mailboxes cluster servers, during the backup I am getting two errors. I am waiting on further instructions by Microsoft on what I can or should do at this point. I will keep everyone posted. Makes me not that confident in applying further patches. The tech told me that if it does not have a tech net article associated with it then don't install it. But the security ones sometimes don't have technet articles associated with them at the time of release. I just assumed that if MSBA picked it up it was okay to install and since I was able to download it from Microsoft it was okay.

We also applied update rollup 4 KB952580 after it came down via windows update auto-magically and started to get suspicious when we noticed lots of calendar sync issues from our Blackberry server as follows;Event Type: WarningEvent Source: BlackBerry Messaging Agent xx Agent 1Event Category: NoneEvent ID: 20216Date: 8/09/2008Time: 12:11:23 PMUser: N/AComputer: xxDescription:{xx@xx.com.au} Synchronize() failed: ERR_FAIL, Tag=6794Anyway after wasting hours troubleshooting the BES to no avail, permissions, changing the service account, upgrading software, etc. I did a search and found this thread and discovered KB52580 got pulled. So an uninstallation of rollup 4 went ok and didn't appear to cause any more issues BUT hasn't fixed the calendar sync issue it introduced. Doh!Luckily email still works so I guess we wait for update 4 to be reposted and hope it actually fixes things next time.

We are also running a Blackberry Enterprise Server and didn't notice anything on that end after the update. I was here until 1:00 AM restoring the entire server. Unfortunately I had to do a complete restore going back 2 days! It took forever to isolate the changed data and reload the entire server. I attempted to uninstall the rollup and that was pointless. That only created 10(x) the problems. After I performed a restore of the PC (now back to rollup 3) I immediately performed a chack for update via the WSUS server and the rollup 4 package was expired and no longer available. Imagine that! Microsoft ... your killing me! Everything appears to be back to normal!

Well i've now set up a 2nd HT server and done a DR rebuild of the one that died. Fun Fun Fun.

Finally there is an official statement from MS regarding the release of KB952580 http://msexchangeteam.com/archive/2008/09/11/449787.aspx Greetings, MR

Hi all, Yes,it is an incorrect version. If you encounter any problem,then please just uninstall it. We will keep update it. http://msexchangeteam.com/archive/2008/09/11/449787.aspx Thanks for your cooperation. Xiu

Xiu Zhang,I really appreciate your enthusiasm but just try to uninstall this update and see what it causes. It's not that easy for everyone. Some have uninstalled it without a hitch. Others like myself had to perform full system recoveries. I attempted to perform a recovery just for the exchange application and that failed. This update has really caused some of us a big headache. Yeah, maybe it was partially our fault for installing the update and putting too much trust into MS. I have over 20 hours already into a system restore thanks to this little update!

It is unfortunate that the update was accidentally released. Mistakes happen. Isn't this the reason why we have best practices and documents that always say out loud how important it is to test any change (not just updates *any* change) in non-production environment as much as possible? I am by no means saying this update hasn't caused problems but I am stressing the importance of testing changes and updates before applying them in production environments. Please don't be harsh on the developers who are spending countless days and nights testing fixes that will make the product better and resolve known issues.

Bhargav,Since I'm sure you directed this at me I'll respond. I'm not trying to be harsh towards anyone. I do understand that mistakes happen. I make them just as everyone else does, if not more. However, please understand that not every company that runs exchange has millions of dollars to pour into non-production machines and/or technicians to monitor them. Some of us only have our production machines. Most of my clients only have production machines. Your statement as to "spending countless days and nights" fixing things for us. Not to be harsh, but that's what they get paid to do! For all of the moderators and MVP's who volunteer time and help us with problems, I applaud them for their devotion. You must understand however that this has caused some of us a lot of grief and time. My apologies to anyone who feels offended.

Sorry if you feel my response was directed to you. I posted the information that we always stress upon for every reader. I do understand not every compnay has financial support or infrastructure (list goes on) to support that extra test machine. That is where Microsoft tries to help as well. The virtualization products like Virtual PC, Virtual Server, even Huper-V Server 2008 which will be available at no cost can help you test without purchasing extra servers. You can even download prebuilt VHDs that saves you time and allows you to spend that valuable time in testing and other tasks your job demand. I understand your comment about developersdoing their job but I work within the company and I know how much effort goes in testing before release to deliver best quality possible.We at Microsoft have recognizedthe grief it hascaused and it has been reflectedin posting by the exchange team. http://msexchangeteam.com/archive/2008/09/11/449787.aspx Sorry for any confusion.

Hi sabo_e, Problem you have encountered has been reported to our product team, and below is the newest update for your issue. You may try to follow the steps to solve the problem. 1. Uninstall the rollup from View Installed Updates in Windows Server 2008 or Add/Remove programs in Windows Server 2003. 2. If the server also has the CAS role, open the web.config file located at <Exchange Install folder>\Client Access\exchweb\ews using an editor like Notepad.exe. 3. Replace all instances of %ExchangeInstallDir% with the actual path of the Exchange installation folder. E.g. If you have installed Exchange in D:\Program Files\Microsoft\Exchange Server replace %ExchangeInstallDir% with D:\Program Files\Microsoft\Exchange Server\. Here is a line in the web.config file. Before <codeBase version="0.0.0.0" href="file:///%ExchangeInstallDir%bin\Microsoft.Exchange.Common.IL.dll"/> After <codeBase version="0.0.0.0" href="file:///D:\Program Files\Microsoft\Exchange Server\bin\Microsoft.Exchange.Common.IL.dll"/> 4. Restart W3SVC service Notelease backup your web.config file and then do the changes. Hope it helps. Xiu

I have a support call opened with Microsoft at this point and I am waiting on their directions. It seems I am not the only one that this affected. Can you confirm when the new offical release comes out if I install over top of the pre-release will it correct itself?

For anyone who has applied the update and have questoin about if new update can be applied over this update, the answer is yes. You can apply the update over the old one and it will install and replace files as necessary.

thanks for the information. Do you have any knowledge of a timeline of release for the offical update? will it be soon?

Rollup 4 for Exchange Server 2007 with sp1 has been released.