Home

Earlier today the Exchange CXP team released Update Rollup 1 for Exchange Server 2007 SP3 to the Download Center. The release of the rollup via Microsoft Update will happen on September 21st.

This update includes new fixes for the following server roles:

  • Client Access
  • Edge Transport
  • Hub Transport
  • Mailbox
  • Unified Messaging

A fix for the Exchange 2007 SP3 and OWA S/MIME Version Mismatch we blogged about soon after the release of Service Pack 3 is included in this release, and additionally we'd like to call out the following fixes:

  1. KB 980301 The Microsoft Exchange Information Store service stops responding during a Volume Shadow Copy Service backup on an Exchange Server 2007 server
  2. KB 983529 The EdgeTransport.exe process crashes and then restarts on an Exchange Server 2007 server
  3. KB 973637 Exchange Server 2007 creates incorrect Lotus Notes proxy email addresses
  4. KB 982928 The Msftesql.exe process continues using memory on an Exchange Server 2007 server
  5. KB 983296 Exchange ActiveSync crashes on an Exchange Server 2007 server causing the client synchronization to be unavailable

For a full list of the fixes included in this rollup, see KB 2279665 Description of Update Rollup 1 for Exchange Server 2007 Service Pack 3.

Note for Forefront Protection for Exchange users

For those of you running Forefront Protection for Exchange, be sure you perform these important steps from the command line in the Forefront directory before and after installing this rollup. Without these steps, the Information Store and Transport services will not start.

  1. Before installing the rollup, disable ForeFront by using the "fscutility /disable" command
  2. After rollup installation completes, re-enable ForeFront by running the "fscutility /enable" command

Kevin Bellinger

56 Comments
Not applicable
Wow, quite a few changes there.  Also happy about: http://support.microsoft.com/kb/978144/  - finally fixing the erroneous warnings people with CCR geoclusters were seeing with test-replicationhealth  (and made it hard to use this cmdlet in a script)
Not applicable
It's unfortunate that Outlook Web Access Remote Document Access, which Microsoft broke with Service Pack 3, remains unfixed.  When will this be repaired?  

OWA Remote Document Access is a business critical feature for many organizations, mine included.  (At least fifteen posts under "Exchange 2007 SP3 and OWA S/MIME Version Mismatch" relate to this error).  Remote Document Access is the primary reason we upgraded to Exchange 2007.

I reported the error to Microsoft support in early July and was promised a fix in "about a month."  The Exchange Team really needs to pay closer attention to its customers' needs and address this problem ASAP.
Not applicable
I also have the same problem as Greg.
Many users are complaining to me about this.

Not applicable
@JavierS: Thank you for your message.  Good news:  In another thread, Bharat Suneja [MSFT] said: ...A fix for the remote document issue w/Exchange 2007 SP3 will likely be included in the next rollup for SP3 - it's not included in the just-released rollup 1. If you can't wait for rollup 2, an interim update will be available this week from CSS. You will need a bug reference - please look for it in a follow-up comment soon.
September 13, 2010 3:13 AM
Not applicable
I really love reading the information in the message posted above. It will really help me in solving that type of issue that I'll surely encounter or if not is being encountered by my friends. Thanks and keep on posting such an informative as this one above.
Not applicable
Shame RU1 now causes Management Tools on Windows 2008/2008 R2 or Windows 7 to error getting information about Exchange 2007 running on Windows 2003. Seems to change the file %windir%system32inetsrvnativerd.dll and then causes COM errors getting CAS Information.
Not applicable
@Gareth - I've asked our test team to try and repro the condition you've mentioned in your post to identify what the issue you're experiencing is. I'll post back here once we've had a chance to review it and advise next steps if it's something that was introduced inadvertantly with RU1. Thanks for taking the time to report it to us.
Not applicable
After applying this update to my Exchange server, and after starting the EMC, whenever I connect to a CMS or CAS server, I receive the following error:

Retrieving the COM class factory for remote component with CLSID {2B72133B-3F5B-4602-8952-803546CE3344} from machine <cmsservername> failed due to the following error: 800706ba
Not applicable
Ack!  Firewall rules were different in my lab vs. production.  Importing the production policies into the lab resolved the issues.
Not applicable
After install this rollup the command 'New-ReceiveConnector' is failed: 'Error:
Active Directory operation failed on [dc]. This error is not retriable. Additional information: The parameter is incorrect.
Active directory response: 00000057: LdapErr: DSID-0C090B38, comment: Error in attribute conversion operation, data 0, vece
The requested attribute does not exist.'

Production AD Schema is Exchange 2007 SP2.

In test lab AD Schema is Exchange 2010 SP1 and creation of the new receive connectors on Exchange 2007 servers SP3 Rollup 1 does not fail.
Not applicable
@Kevin Bellinger - Thanks for the update. I did a little more digging and it appears that files in %windir%system32inetsrv are being updated which relate to the COM error I get, especially nativerd.dll which on a plain SP3 machine doesn't get the error.
Not applicable
I'M having the same problem on our 2 CCR cluster, after applying Rollup1 to my Exchange server, and after starting the EMC, whenever I connect to a CMS or CAS server, I receive the following error:

Retrieving the COM class factory for remote component with CLSID {2B72133B-3F5B-4602-8952-803546CE3344} from machine <cmsservername> failed due to the following error: 80040154
Not applicable
Today I'm update Enterprise production system (AD) to Exchange 2010 SP1 Scheme. All of the Exchange 2007 SP3+Rollup1 servers work fine: ''New-ReceiveConnector' command doesn't fail.
Please, include this comment for KB2279665: "Before install this update, You must UPGRADE the schema at Active Directory to [...]. (or, fix this behavour with Ex2007 SP3 RL2 :)
Not applicable
Solution - need to add check for this this AD Schema Changes before install Exchange 2007 SP3 Rollups:
"Exchange 2007 SP3 Active Directory Schema Changes
The msExchSMTPExtendedProtectionPolicy class has been added to the ms-Exch-Smtp-Receive-Connector class. The changes are as follows: [...]"
Not applicable
I just applied SP3UR1 to the passive node of our single-copy cluster and rebooted it.  Now, the  Cluster service won't start, complaining about RPC.

Cluster.log has interesting wording:
.......ERR  [INIT] Unable to bind RPC to UDP, status 1721.

We do have custom RPC settings that haven't been touched in a couple of years and appear to be intact, and connectivity seems fine.  Still looking...
Not applicable
Uninstalling UR1 made everything happy again, for the record.
Not applicable
Is upgrade to Exchange 2007 SP3 in single label domain supported, from SP1? I know it's not recommended but looking to migrate mailboxes to 2010 while SP2 or above is required.
Not applicable
I am unable to make a receive connector for an application relay.  No matter which settings I use I get this:
After install this rollup the command 'New-ReceiveConnector' is failed: 'Error:
Active Directory operation failed on [dc]. This error is not retriable. Additional information: The parameter is incorrect. Active directory response: 00000057: LdapErr: DSID-0C090C26.  comment: Error in attribute conversion operation, data 0, v1772

The requested attribut does not exist
Not applicable
I should add, the above error is on a fresh install of SBS 2008.
Not applicable
Our IMAP expert asks:  Do you have any idea why Exchange's IMAP server is now (post-UR1) serving most text/plain parts as text/html instead?

Old messages (ones delivered prior to the rollup installation) are also getting served up as text/html now, when they were previously multipart/alternative messages with both text/plain and text/html subparts.

So, it's not something that's affecting the actual content of the messages; it's something that affecting how Exchange presents message subparts to IMAP clients.
Not applicable
I'm experiencing this problem as well on all our Exchange 2007 HT/CAS servers after applying this update.

When browsing through the EMC to Server Configuration, and then selecting one of the remote servers, this error pops up:

Retrieving the COM class factory for remote component with CLSID {2B72133B-3F5B-4602-8952-803546CE3344} from machine <cmsservername> failed due to the following error: 80040154

Any idea's?
Not applicable
Sorry the actual error I'm getting as mentioned above is this:

Retrieving the COM class factory for remote component with CLSID {2B72133B-3F5B-4602-8952-803546CE3344} from machine xxxx failed due to the following error: 800706a
Not applicable
@ Gareth - I wanted to provide an update now that we have identified the issue. We've assigned this to an upcoming milestone for E14 SP1. Once we have an internal update available I'll post back and provide a KB so customers can obtain relief prior to the official RU release later this year.
Not applicable
@Kevin Bellinger - You assigned Gareth's problem to an upcoming milestone for E14 SP1 (i.e., Exchange 2010 Service Pack 1)???   This thread is about E12 SP3 RU1 (i.e., Exchange 2007 Service Pack 1).  Please provide a fix for us (Gareth included) who are using Exchange 2007.  Thanks.
Not applicable
@ Kibitzer - I meant to write E12 SP3 - apologies for the confusion.
Not applicable
It seems that rollup 1 changed the way text/plain was handled.  To get it to work like it had before I had to either do it for all users or I could modify it for specif users

for imap on a specific user I used powershell, but it can also be done in the GUI

set-casmailbox userid ImapMessagesRetrievalMimeFormat 0
set-casmailbox userid ImapUseProtocolDefaults $false

for POP on a specific account

set-casmailbox userid popMessagesRetrievalMimeFormat 0
set-casmailbox userid popUseProtocolDefaults $false

in the gui i seleceted the account in question, properties, mailbox features, imap or pop , properties - then deselected use defaults, and then selected text
Not applicable
@ Kevin Bellinger - Thanks for the clarification.  The Exchange Team is doing a great job with both E12 and E14 adding features and improving the product, the occassional bug not withstanding.
Not applicable
Which part is most important to get update for this:
"Exchange Server 2007 creates incorrect Lotus Notes proxy email addresses "

I have updated the HUB server where the connectivity suite is sitting, but it still generate incorrect formats.
Not applicable
I am having the same issue as G3steel - also on SBS 2008.  Also fails from Exchange Command line - seems to fail at the Name paramater.

After install this rollup the command 'New-ReceiveConnector' is failed: 'Error:
Active Directory operation failed on [dc]. This error is not retriable. Additional information: The parameter is incorrect. Active directory response: 00000057: LdapErr: DSID-0C090C26.  comment: Error in attribute conversion operation, data 0, v1772

Any ideas?  SP3 intalled with no errors - is this a schema update issue?  I thought it was done as part of the SP3 install - do I need to manually do this?

Thanks.
Not applicable
I had the same problem as jjpb with the SP3UR1 on a SCC cluster with the cluster service not starting. I can confirm that removing SP3UR1 fixed the problem.

Its the exact same issue.

Any updates on what is causing this, any fixes or workarounds?
Not applicable
Just to update - once I iuninstalled Rollup Update 1 for Exchange 2007 SP3 I was able to add the Recieve Connector.  So some change in there seems to cause the problem.
Not applicable
I am having the same issue with the receive connectors. Not a huge deal for now but would like to get it fixed. Msoft?
Not applicable
I have the same problem as swg and jjpb , I have 2 CCR nodes with Exchange 2007 SP3 and Forefront, I have disabled Forefron and applied RU1 and after reboot Cluster Service did start, if I roll back, everything is fine, is this a bug ? Can you please advise?
Not applicable
On two separate servers I tried to apply SP3 with RU1 integrated. One was a 64 bit Windows 2008 SP2 machine with Exchange 2007 SP2 w/ RU4. It has the CAS/HTS/MBX roles installed.
The other was a 32 bit Windows 2003 SP2 machine with Exchange 2007 SP2 with RU4. It just had the Admin console as it was running DPM 2007 SP1.

On both machines the error of "Installing product excahgneserver.msi failed. Fatal Error during installation. Error code is 1603.

On the actual Exchange server, fixing it required removing the RU1 from the Updates folder of SP3, manually copying over the CHM file (since most Exchange files were removed as a part of the upgrade), restarting web services, and re-running SP3. Once SP3 succesfully applied, and I got a change of underwear, I applied RU1 separately.
I did disable Forefront protection before attempting SP3 w/ RU1 as indicated in this post.

The DPM server required copying the CHM file over as it didn't really have IIS integration.

With the one server I was willing to chalk it up to something wacky about the machine. With two separate servers acting the same way w/ 2 different versions (32bit versus 64bit and Windows 2008 versus Windows 2003) I think it's the code not liking applying the RU1 in conjunction with SP3.

Has anyone run into this?
Not applicable
Correction - copying over the CHM file onto the DPM server didn't work, I had to rip out the registry keys for Exchange and completely re-install the admin console from SP3.

And "On both machines the error of "Installing product excahgneserver.msi failed. Fatal Error during installation. Error code is 1603." was supposed to be:

On both machines I got the error of "Installing product excahgneserver.msi failed. Fatal Error during installation. Error code is 1603." when I did Setup /m:upgrade from SP3 with RU1 in the Updates folder.
Not applicable
Is there any official answer for:

Retrieving the COM class factory for remote component with CLSID {2B72133B-3F5B-4602-8952-803546CE3344} from machine <exchange server> failed due to the following error: 80040154

After E2003 SP3 and UR1 were applied. UR1's release notes says nothing about required firewall changes.
Not applicable
Hi Petri

Good question - same issue after Exchange 2007 SP3 Update Rollup 1 with the following error message: "Retrieving the COM class factory for remote component with CLSID {2B72133B-3F5B-4602-8952-803546CE3344} from machine <Servername> failed due to the following error: 800706ba."

We uninstalled Update Rollup 1 and everything is fine... any inputs?

Cheers,
Smiliman
Not applicable
Smiliman,

Seems to have something to do with FW:
http://forums.msexchange.org/m_1800538177/printable.htm

I have also some servers FW disabled and there I do not have issue at all. Strange is that I haven't seen any drops on the FW logs.
Not applicable
Just tested...
By disabling the firewall the remote management was working just fine. So something has changed from the firewall point of view.
Not applicable
Hi Petri

Thanks for your posting. Well, I agree - it's "something" with the firewall... but: We didn't change anything that has to do with the firewall (for example OS patches). We just installed Exchange 2007 Service Pack 3 and the Update Rollup 1. In my point of view it's strange that we have to change something in the firewall configuration after installing Update Rollup 1 for Exchange 2007 Service Pack 3 without any hints in the documentation - it smells like a bug with the Update Rollup 1 for Exchange 2007 Service Pack 3… So, we just waiting for an official statement of Microsoft and maybe for Update Rollup 2 for Exchange 2007 Service Pack 3 ;) Should be released in December 2010...

Cheers,
Smiliman
Not applicable
Has no one else tried to update a 2007 SP2 server with SP3 w/ RU1 integrated via the Updates folder? I can't believe I had 2 separate machine installs die in exactly the same way and be the only one.
Not applicable
The ONLY way I could get this patch to install was to set TEMP to C:TEMP, log out, open a command prompt with admin privileges, THEN launch the update. All other methods failed on my plain-vanilla Exchange 2007 install.
Not applicable
@ Kevin Bellinger - I am seeing the same issue as Gareth since installing SP3 RU1 , and my firewalls  are disabled.  Has the internal update for this been released yet?
Not applicable
We are also experiencing the same issues. We have a mixed environment with a 2003 CAS machine and 2 x 2008 CAS Machines.

Cannot run any CAS related CMDLETS from the 2008 machines but is ok on the Server 2003 machine.

Firewalls have been turned off on all the machines to no avail.
Not applicable
After SP3 Rollup1, I receive the following error on CAS/MBX/HT server:

Exchange 2007 Retrieving the COM Class factory for remote component with CLSID (2B72133B-3F5B-4602-8952-803546CE344) from machine server.domain.com failed due to the following error: 80040154

Firewall is turned off on all 3 Exch2007 servers in the environment.

Any ideas or fixes?
Not applicable
After Rollup1 installation getting same message as Clusterpuppy mentioned and no firewall is configured. Any other solution?
Not applicable
Exchange 2007 Retrieving the COM Class factory for remote component with CLSID (2B72133B-3F5B-4602-8952-803546CE344) from machine server.domain.com failed due to the following error: 80040154

Firewall is turned off on all 3 Exch2007 servers in the environment.

Also problem..... Any solution
Not applicable
Has the 'New-ReceiveConnector' error been fixed yet?
Not applicable
@Kevin Bellinger - Do you have an update for us regarding the KB# with the interim workaround?

@ All - apparently I missed the instructions in the SP3 documentation that said don't put anything in the Updates folder if you are going to upgrade an existing machine to SP3. Why the /m:Upgrade on the Service Pack does make it automatically ignore the Updates folder is beyond me (I.E. Why not build that into the Service Pack Upgrade process so that admins don't have to worry about what's in the Updates folder).
Not applicable
I also have the problem with new receive connector on SBS08.  I lost sending from the SBS after an update.  In an attempt to fix it I have tried running the connect to internet wizard, which failed.  I then researched it's failure and found that it could not find the Default recieve connector (which existed),  I deleted the default and tried to recreate, which failed.  Now I am slammed and must reimage the server from a backup since this is completely broken.