The following error was generated when “$error.Clear();
install-ExsetDataAtom -AtomName OrgLevelCt -DomainController $RoleDomainController -Organization $RoleOrganizationName

” was run: “System.Management.Automation.ParameterBindingValidationException: Cannot bind argument to parameter ‘DomainController’ because it is null.
at System.Management.Automation.ParameterBinderBase.ValidateNullOrEmptyArgument(CommandParameterInternal parameter, CompiledCommandParameter parameterMetadata, Type argumentType, Object parameterValue, Boolean recurseIntoCollections)

Any ideas ?

Yep, still works perfectly on Exchange 2016. I didn’t even bother checking the registry. Thanks for this tip!

I am dealing with the above issue (Exchange 2016 uninstall failed after it could not stop all the services in time) and now it says that “an incomplete installation was detected”.
I cannot re-install because I have installed an Exchange 2019 to our domain. I even tried, but of course got the message that a newer server exists.

Any ideas?

Thank you,
Roubi (an IT gal)

WHEN I RUN SETUP OF EXCHANGE 2016 I GET THIS ERROR BELOW

Directory C:\Program Files\Microsoft\Exchange Server\V15\bin\Setup\ServerRoles\Common not found.

I thought i’d be all cool and specify the DB and LOG file paths parameters in my setup command but i failed to create the folders first and furthermore i failed to specify the .edb extension of the DB and LOG files i wanted to create.

therefore the setup program got stymied and failed at the MB role install phase.

I found and pulled the watermark then reran the command to install the mb role.

I’m really hoping that works.

Thanks for sharing this fantastic write-up. I’ve just exited a 3 day wrestling match with a failed Exchange 2016 server install (I’m an amateur) and the information you shared here and a couple other of your posts were key to me finding my way through the maze to resolution. VERY much appreciated.

Regards,
Stuart Rowe

I’d like to try the solution from Aleksey, but I don’t have CU10 anymore and it’s not available from MS anymore.

What I’m trying to do is uninstall 2013 after a 2016 migration, but it’s failing at step 6 – unified messaging service. It’s lookin for the UMLanguagePack msi and can’t locate it. I’ve tried to uninstall from th command from the /bin drive of the exchange installation location, but still fails.

I believe if I had CU10 I’d be able to get this sorted, but I’m stuck right now. Ha k for any help!

This worked for me too, just remove both registry values & run setup /m:uninstall from admin command prompt.

Exchange 2013 SP1 CU18, removing one exchange mailbox server.

This answer did it for me. There’s was no Action or Watermark entry in my registry, and this was much easier than having to reinstall first. Excellent!