Hello, I tried installing SP1 for Exchange 2007 on my Exchange box, but I received the following error: Code Block Setup previously failed while performing the action "Install". You cannot resume setup by performing the action "BuildToBuildUpgrade". This error appears right from the start, when I click Next in the Introduction screen. Anybody has an idea here? Thanks!

I have exactly the same problem on a CCR cluster I followed exatcly theese instructions: http://technet.microsoft.com/en-us/library/bb676320.aspx but when i launch this command: Setup /upgradecms i have the error reported above Any help would be greately appreciated. Regards Maurizio

And you are not alone in the dark.. We have exactly the same behavior on our CCR, and we have contacted MS Support ifwe have a solution we will tell you my friends.. Esso / Sweden

Guys we probably have solved it, we deleted the Watermark key from HubTransportRole in the registry: http://msexchangeteam.com/archive/2007/05/21/439529.aspx Now everything seems fine... I hope this can solve even to you. Bye Maurizio

Thanks Maurizio, I was having the same issue when trying to run the setup /upgradecms on my SCC during the SP1 upgrade process. After deleting the watermark registry key I was able to finish the upgrade. -Brian

Hello Folks! As i sade we have the same problemwith our Exchange-cluster, but we have a CCR not a SCC.. I am going to try this solution, in the next "servicewindow" [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\v8.0\ClusteredMailboxServer]"Action"="Install""Watermark"=dword:eefe939a No answer from Microsoft yet, but i suspect that they came wit the same solution.. Esso / Sweden

Hi Esso, i can confirm you we have a CCR Cluster and that this workaround worked fine (remove the watermark key from the hubtransport section of the registry). I'm very interested in what MS will say about this solution (and if this is really THE solution) Please keep us informed with the problem on your cluster. Bye Maurizio

I did not have the Watermark key in the HubTransportRole branch, but in the ClientAccessRole branch. Removing only the Watermark key did not solve the problem, but removing the Action key (value: Install) as well, did the trick!

Hello Folks! I have been in contact witt MS Support, and they are going to look at this (5th dec) afternoon. I tould them about your solution and they seem to now about it. And i am sure it is the way to go.. Iam coming back and tell you how itworks out. (excuse my english) Esso / Sweden

It looks like SP1 will fail if any of the server roles under HKLM\SOFTWARE\Microsoft\Exchange\v8.0 has either a Watermark registry value or Action:Install value present. Removing these from the server roles allows the service pack to install.

Maurizio, and others... THANKS. This post was a lifesaver. The watermark registry entry in my case was in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\v8.0\ClusteredMailboxServer Deleting it allowed me to complete the setup /upgradecms and bring everything back to life. Andre.

Hey I have another problem. I dont have a "ClusteredMailboxServer" key inregistry key on the Hub Server.I see other roles like HUB and CAS. Watermark Key did exist under ClientAccess key. This was removed but upgrade still failed. Please Note: When installing Active mailbox cluster role on mailbox server, setup failed to complete and failed reason: Server is not a clustered mailbox server. This was ignored because when we ran the Get-ClustredMailboxServerStatus the corect information was shown and bother servers were seen as operational and node A was online. Please give your thoughts on why this might be occuring. Thanks.

trythis : i've delete : HKLM : key=> Watermark and i renamed : HKLM : key => Action "RecoveryDisaster" by "BuildToBuildUpgrade" I've relaunch "setup.com /mode:upgrade" and it's OK, Install and checked are OK regards

Having the same problem with /upgradecms (on original passive node). We have no "Watermark" inthe registryunder Exchange (v 8) , as this is on a Mailbox role only cluster member. Don't have the "ClusterMailboxServer" listed in the registry either, although get-clusteredmailboxservers displays information as expected. The Stop and Move commands executed without error, until setup /upgradecms Clustered Mailbox Role Checks ......................... FAILED The local computer is not a possible owner of the clustered mailbox server you are attempting to upgrade. Restart setup on a possible owner. Possible owner (s): (servername of nonupgraded server)

I had to use ADSIEDIT.msc to modify the msExchServerRedundantMachines attribute of the cluster box name, to list both cluster mailbox hostnames. Also, this didn't seem to work until all names were capitalized.

The watermark trick fixed this for me in a CCR. Thanks a million guys. The Action key was already set as 'Uninstall', which I left in place and it worked fine. There is also a very good article covering the entire sp1 upgrade procedure for CCR, which includes the Remote Streaming Backup key required for seeding etc, which is turned off by default after sp1. Check this out here: http://telnetport25.wordpress.com/2007/11/30/upgrading-a-two-node-exchange-2007-ccr-cluster-to-service-pack-1/ Cheers

Please stop deleting watermark keys in the registry to work around these issues. These watermark keys are there for a reason and the actual underlying problem needs to be resolved before continuing setup by using Add/Remove programs. You have to look at the Exchange setup logs to determine what failed by referencing the watermark key in the registry with what is in the setup logs. Deletinga watermark key will leave your server in an incomplete Exchange configuration and YOU WILL HAVE PROBLEMS with your server. You may think that things are installed properly, but somewhere down the road, more problems may occur. There are special considerations for upgrading a CMS for SP1 in which this fails and how to work around it, but for regular non-CMS roles, this is not the way to go. If you cannot figure this out, then you need to call Microsoft support for further assistance. Mike Lagase Microsoft Exchange Escalation Services

Here's the KB article from Microsoft: http://support.microsoft.com/kb/947281. We did have an error when installing a mailbox server which stated "The Exchange server address list service failed to respond." We found out that this was due to a leap year bug, and the fix was just to restart the server after installation. That KB article allowed us to install SP1. Steve

Action key was the trick. It was in Admin Tools for me.

hi ,first check if ur perviouse version was RTM or not , beacuse if it was RTM u will not be able to do soo if yours is not RTM so delete the water mark as the others said then try again..

Just a heads up for future issues with Exchange 2010 - you may get this same error; however it is (or was in my case) found under HKLM > SOFTWARE >Microsoft > ExchangeServer > v14 > AdminTools Uder this key there was the infamous Action and Watermark entries. Delete these and you'll be good to go.Karl

I had the same problem and " I did not have the Watermark key in the HubTransportRole branch, but in the ClientAccessRole branch. Removing only the Watermark key did not solve the problem, but removing the Action key (value: Install) as well, did the trick!" works !!

You have to remove the Action key, http://www.vincenzosciarra.tk/2011/02/28/exchange-2007-setup-error-setup-previously-failed-while-performing-the-action-%E2%80%9Cuninstall%E2%80%9D-you-cannot-resume-setup-by-performing-the-action-%E2%80%9Cdisasterrecovery%E2%80%9D/--- Vincenzo Sciarra http://www.vincenzosciarra.tk

not just that, you need to look for the following reg keys under MailboxRole: ConfiguredVersion UnpackedVersion my ConfiguredVersion was missing, corrected this and ran setup.com /mode:install /role:mailbox and all ran through successfully, also watch out if you are using SCOM to monitor, the service gives you grief, must change it from Disabled to Auto Start, rerun the command line option and all will be fine. Simon Craner