Home
%3CLINGO-SUB%20id%3D%22lingo-sub-593388%22%20slang%3D%22en-US%22%3EHow%20does%20Exchange%202007%20setup%20know%20to%20resume%20a%20failed%20setup%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-593388%22%20slang%3D%22en-US%22%3E%3CP%3E%3C%2FP%3E%3CP%3EIn%20case%20that%20you%20have%20a%20failed%20Exchange%202007%20setup%20for%20some%20reason%2C%20you%20might%20notice%20that%20setup%20now%20resumes%20the%20previously%20failed%20setup%20rather%20than%20start%20completely%20over.%20How%20does%20that%20work%3F%20Through%20registry%20values%20called%20%22watermarks%22.%3C%2FP%3E%3CP%3EWatermarks%20are%20used%20to%20mark%20points%20of%20installation.%20Setup%20sets%20the%20mark%20of%20what%20server%20roles%20are%20installed%20halfway%20through%20setup%20as%20opposed%20to%20at%20the%20end.%20This%20is%20important%20because%20Exchange%202007%20setup%20can%20be%20resumed.%20If%20there%20is%20a%20setup%20failure%2C%20the%20setup%20environment%20can%20be%20changed%20and%20then%20setup%20can%20be%20restarted%20from%20the%20watermark%20indicator%20as%20opposed%20to%20starting%20setup%20from%20the%20beginning.%3C%2FP%3E%3CP%3EIn%20addition%20to%20the%20setup%20log%20files%20located%20in%20C%3A%5CExchangeSetupLogs%2C%20there%20will%20be%20several%20additional%20useful%20files%20that%20are%20based%20on%20the%20component%20definition%20files%20mentioned%20in%20the%20preceding%20section.%20These%20files%20have%20the%20following%20form%3A%3C%2FP%3E%3CBLOCKQUOTE%3E%20%3CP%3E%3CB%3E%3CINSTALL_TYPE%3E-%3CSERVERROLE_OR_COMPONENT%3E-Date-TimeStamp.ps1%3C%2FSERVERROLE_OR_COMPONENT%3E%3C%2FINSTALL_TYPE%3E%3C%2FB%3E%3C%2FP%3E%3C%2FBLOCKQUOTE%3E%20%3CUL%3E%20%3CLI%3EThese%20files%20will%20be%20retained%20and%20each%20install%20produces%20a%20new%20set%20depending%20on%20the%20tasks%20involved.%3C%2FLI%3E%20%3CLI%3EThey%20can%20also%20be%20used%20to%20troubleshoot%20setup%20failures.%20If%20a%20server%20role%20for%20example%20the%20Hub%20Transport%20Role%20failed%2C%20look%20in%20the%20Install-HubTransportRole-yyyymmdd-xxxxxxxxx.ps1.%3C%2FLI%3E%3C%2FUL%3E%20%3CP%3EWhen%20you%20open%20those%2C%20you%20will%20see%20that%20some%20lines%20start%20with%20something%20similar%20to%20this%3A%3C%2FP%3E%3CBLOCKQUOTE%3E%20%3CP%3E%3CB%3E%23%20%5BID%20%3D%20fdfe6b1a%2C%20Wt%20%3D%201%2C%20isFatal%20%3D%20False%5D%3C%2FB%3E%3C%2FP%3E%3C%2FBLOCKQUOTE%3E%20%3CP%3EExplaining%20what%20that%20means%3A%3C%2FP%3E%3CP%3E%3CB%3EID%3C%2FB%3E%3CB%3E%20%3C%2FB%3Eis%20the%20ID%20of%20the%20task%20being%20run.%20This%20ID%20can%20be%20tied%20back%20into%20the%20registry%20watermark%20such%20that%20if%20setup%20were%20to%20fail%2C%20thus%20leaving%20behind%20a%20watermark%2C%20you%20can%20do%20a%20search%20of%20the%20.PS1%20file%20to%20determine%20what%20task%20setup%20failed%20on.%20While%20it%20is%20straightforward%20to%20see%20what%20task%20setup%20failed%20on%20in%20the%20ExchangeSetup.log%20this%20will%20give%20you%20a%20definite%20idea.%3C%2FP%3E%3CP%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Flegacyfs%2Fonline%2Fmedia%2Fthemes%2Fexchange%2Fimages%2F439527_ResumeSetup1.jpg%22%20original-url%3D%22%2Fthemes%2Fexchange%2Fimages%2F439527_ResumeSetup1.jpg%22%20%2F%3E%3C%2FP%3E%3CP%3EIn%20situations%20where%20a%20server%20role%20is%20%22partially%22%20installed%20or%20an%20install%20has%20failed%2C%20comparisons%20are%20made%20in%20the%20registry%20under%20HKLM%5CSoftware%5CMicrosoft%5CExchange%5Cv8.0%5C%3CNAME%20of%3D%22%22%20role%3D%22%22%3E.%20In%20this%20location%20is%20a%20set%20of%20registry%20values%20that%20give%20us%20a%20range%20of%20values%20describing%20the%20role%20state%3A%3C%2FNAME%3E%3C%2FP%3E%3CBLOCKQUOTE%3E%20%3CP%3E%3F%20%3CB%3ENot%20installed%3C%2FB%3E%20%E2%80%93%20there%20will%20be%20no%20sub%20container%20for%20the%20role.%3C%2FP%3E%3CP%3E%3F%20%3CB%3EUnpacked%20%3C%2FB%3E%E2%80%93%20The%20%3CI%3EUnpackedVersion%3C%2FI%3E%20value%20indicates%20the%20versions%20of%20the%20files%20that%20have%20been%20copied%20during%20the%20file%20copy%20phase%20of%20setup%2C%20but%20no%20components%20have%20been%20configured.%3C%2FP%3E%3CP%3E%3CB%3ENote%3A%3C%2FB%3E%20The%20%3CI%3E%22AdminRole%22%3C%2FI%3E%20does%20not%20have%20a%20%3CI%3EConfiguredVersion%20%3C%2FI%3Ereg%20value%20since%20it%20doesn't%20have%20configuration.%3C%2FP%3E%3CP%3E%3F%20%3CB%3EPartially%20configured%3C%2FB%3E%20-%20Configuration%20is%20currently%20in%20progress%20or%20failed%20partway%20though.%20Typically%20the%20presence%20of%20a%20%3CB%3EWatermark%3C%2FB%3E%20would%20indicate%20a%20partially%20configured%20role.%20The%20value%20for%20a%20watermark%20can%20be%20used%20mapped%20to%20an%20install%20task%20in%20a%20*.PS1%20file%20located%20under%20C%3A%5CExchangeSetupLogs.%3C%2FP%3E%3CP%3E%3F%20%3CB%3EFully%20installed%20(Configured)%3C%2FB%3E%20%E2%80%93%20The%20presence%20of%20the%20%3CI%3EConfiguredVersion%3C%2FI%3E%20and%20%3CI%3EUnpackedVersion%20%3C%2FI%3Evalue%20indicates%20a%20successful%20install.%20The%20value%20of%20%3CI%3EConfiguredVersion%3C%2FI%3E%20indicates%20the%20version%20of%20the%20product%20that%20has%20been%20configured.%3C%2FP%3E%3CP%3E%3CB%3ENote%3C%2FB%3E%3A%20%3CI%3EUnpackedVersion%20%3C%2FI%3Eand%20%3CI%3EConfiguredVersion%20%3C%2FI%3Evalues%20must%20match%20otherwise%20Setup%20will%20complain.%3C%2FP%3E%3C%2FBLOCKQUOTE%3E%20%3CP%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Flegacyfs%2Fonline%2Fmedia%2Fthemes%2Fexchange%2Fimages%2F439528_ResumeSetup2.jpg%22%20original-url%3D%22%2Fthemes%2Fexchange%2Fimages%2F439528_ResumeSetup2.jpg%22%20%2F%3E%3C%2FP%3E%3CP%3E-%20%3CA%20href%3D%22http%3A%2F%2Fmsexchangeteam.com%2Farchive%2F2007%2F04%2F23%2F438148.aspx%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3EJon%20Bradley%3C%2FA%3E%2C%20%3CA%20href%3D%22http%3A%2F%2Fmsexchangeteam.com%2Farchive%2F2006%2F02%2F21%2F420125.aspx%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3ENagesh%20Mahadev%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E

In case that you have a failed Exchange 2007 setup for some reason, you might notice that setup now resumes the previously failed setup rather than start completely over. How does that work? Through registry values called "watermarks".

Watermarks are used to mark points of installation. Setup sets the mark of what server roles are installed halfway through setup as opposed to at the end. This is important because Exchange 2007 setup can be resumed. If there is a setup failure, the setup environment can be changed and then setup can be restarted from the watermark indicator as opposed to starting setup from the beginning.

In addition to the setup log files located in C:\ExchangeSetupLogs, there will be several additional useful files that are based on the component definition files mentioned in the preceding section. These files have the following form:

<Install_Type>-<ServerRole_Or_Component>-Date-TimeStamp.ps1

  • These files will be retained and each install produces a new set depending on the tasks involved.
  • They can also be used to troubleshoot setup failures. If a server role for example the Hub Transport Role failed, look in the Install-HubTransportRole-yyyymmdd-xxxxxxxxx.ps1.

When you open those, you will see that some lines start with something similar to this:

# [ID = fdfe6b1a, Wt = 1, isFatal = False]

Explaining what that means:

ID is the ID of the task being run. This ID can be tied back into the registry watermark such that if setup were to fail, thus leaving behind a watermark, you can do a search of the .PS1 file to determine what task setup failed on. While it is straightforward to see what task setup failed on in the ExchangeSetup.log this will give you a definite idea.

In situations where a server role is "partially" installed or an install has failed, comparisons are made in the registry under HKLM\Software\Microsoft\Exchange\v8.0\<name of role>. In this location is a set of registry values that give us a range of values describing the role state:

? Not installed – there will be no sub container for the role.

? Unpacked – The UnpackedVersion value indicates the versions of the files that have been copied during the file copy phase of setup, but no components have been configured.

Note: The "AdminRole" does not have a ConfiguredVersion reg value since it doesn't have configuration.

? Partially configured - Configuration is currently in progress or failed partway though. Typically the presence of a Watermark would indicate a partially configured role. The value for a watermark can be used mapped to an install task in a *.PS1 file located under C:\ExchangeSetupLogs.

? Fully installed (Configured) – The presence of the ConfiguredVersion and UnpackedVersion value indicates a successful install. The value of ConfiguredVersion indicates the version of the product that has been configured.

Note: UnpackedVersion and ConfiguredVersion values must match otherwise Setup will complain.

- Jon Bradley, Nagesh Mahadev

10 Comments
Not applicable
Do you think I could use this to either uninstall SP1 beta or to trick the real SP1 when it comes out to installing over SP1 beta?
Not applicable
I was trying to add the ClientAccess role to Exchange 2007. However, got the following error. Anyone knows how to change the mode of IIS from 32-bit to 64 bit?

Thanks


D:Exchange2007>Setup.com /role:ClientAccess /Mode:install

Welcome to Microsoft Exchange Server 2007 Unattended Setup

Preparing Exchange Setup

The following server roles will be installed
  Client Access Role

Performing Microsoft Exchange Server Prerequisite Check

  Client Access Role Checks        ......................... FAILED
   The Microsoft Internet Information Service is in 32-bit mode and this is a
64-bit computer. The mode must be changed before Setup can continue.


The Exchange Server setup operation did not complete. Visit http://support.micro
soft.com and enter the Error ID to find more information.

Exchange Server setup encountered an error.
Not applicable
How do you restart a partial install?  My setup errored at the last step of setting up the Active node in CCR.  Typo in my dns record.  It tells me to retry the install, however when I open the setup.exe all the roles are grayed out.  What do I do to resume?
Not applicable
Nathan,

Go to Add/Remove and look for Exchange 2007 there. There are two buttons there.

If the Modify action shows that the Mailbox role is installed (grayed out) - then go to the Remove action and uncheck the Mailbox role, remove it and then again run Setup to install Mailbox again. Depending on exactly in which stage Setup failed, you might have to remove the role to install it again as it shows installed already.
Not applicable
How do you remove an installation if the Add/Remove Programs applet won't do it?  I am trying to remove an Edge Transport Role (after I have renamed the host computer and its workgroup), and the "Remove" feature within Add/Remove Programs ultimately tells me that I can only do this on a Hub or Edge Transport Server... but I can't reinstall the Edge Transport Server because setup tells me that it's already installed.  Can't reinstall it, can't remove it.  What happens if I just delete the EdgeTransportRole collection under HKLMSoftwareMicrosoftExchangev8.0 ?
Not applicable
I would format the box myself. if you do not want to do that for some reason. you could try an untested unsupported method of deleting keys from the registry but first save off any Edge data you might need
remove the following registry keys:
Under HKEY_LOCAL_MachineSystemCurrentControlSet delete the following:
All MSExchange* keys
msftesql-Exchange
msftesqlFD-Exchange
msftesqlIDX-Exchange
Delete the HKEY_LOCAL_MachineSoftwareMicrosoftExchange Key

Delete All Exchange Binaries, by default the binaries are installed here:
C:Program FilesMicrosoftExchange Server

Reboot reinstall Edge
Not applicable
As a followup, thanks Jon, this worked like a charm.  After this I was at least able to install and uninstall the product; after a few sessions, with each consecutive install and uninstall getting further along in the process, I successfully installed the Edge Server, and it's now happily servicing our domain.
Not applicable
Has anyone encountered and resolved this error

Mailbox Role Checks              ......................... FAILED
Setup cannot continue with upgrade because 'D:Program FilesMicrosoftExch
ange ServerbinExchHelp.chm' is open. Close the file and restart setup.

My SP1 setup failed, everytime I try and upgrade the server it fails with the above message
Not applicable
RESOLVED

Setup.com /mode:upgrade

Mailbox Role Checks              ......................... FAILED

Setup cannot continue with upgrade because 'D:Program FilesMicrosoftExch
ange ServerbinExchHelp.chm' is open. Close the file and re-run Setup.com /mode:upgrade

Copy file ExchHelp.chm into your bin directory and re-run Setup.com /mode:upgrade

_____________________________

cheers
B
Not applicable
patelbg2001,

Was the CHM not there already or did you take the SP1 CHM and overwrote the RTM CHM and then setup went through?