Microsoft this week re-released Exchange 2007 Service Pack 3 Update Rollup 3 to correct a potentially critical...
flaw that was introduced in the first release of the product just a week ago.
On March 29 Microsoft said it had discovered an "issue" with the first release that could lead to database corruption. The issue, created by Update Rollup 3, had to do with a change in how the database is grown during transaction log replays, as well as when a database is not cleanly shut down and recovery occurs, according to the company.
But this week’s re-release of RU3, called version 08.03.159.002, reportedly fixes the problem. Microsoft officials "strongly advise" Exchange administrators to install the new version and delete any previous version of the product.
Microsoft said only "a small number of users" have been affected by the problem, adding they have had no reports of customers losing data. The company however, said the risk to be great enough to suggest Exchange administrators uninstall RU3 on all.
Still, some administrators and consultants were annoyed.
"I repeat myself: quality control. This isn't doing the product image any good, guys," said Michael de Rooij, a consultant who specializes in Microsoft infrastructure including Exchange, in a post on Microsoft's Team Blog site.
Others thought Microsoft could have reacted faster to the issue.
"I'm surprised it took this long for this recommendation to come out,” wrote John McNamee, an Exchange administrator. “I worked with Microsoft for two days on March 23 and 24 regarding this issue. I had to uninstall the patch and then reseed 26 databases. Aren't patches tested anymore?"
Let us know what you think about this story; email Ed Scannell at firstname.lastname@example.org.