Exchange 2019 Installation stuck on Step 7

Motubatse 1

Error:
The following error was generated when "$error.Clear();
if (get-service MSExchangeServiceHost* | where {$_.name -eq "MSExchangeServiceHost"})
{
if ($RoleDatacenterIsTestEnv)
{
Stop-Process -Name "Microsoft.Exchange.ServiceHost" -Force
Sleep -Seconds 15
}
else
{
Stop-service MSExchangeServiceHost
}

          Start-service MSExchangeServiceHost  
      }  
    " was run: "Microsoft.PowerShell.Commands.ServiceCommandException: Failed to start service 'Microsoft Exchange Service Host (MSExchangeServiceHost)'.".

Jame Xu-MSFT 4,176 Reputation points

2022-09-13T02:50:04.027+00:00
Hi @Motubatse ,
First check your server system version and whether the prerequisites are installed correctly:
https://learn.microsoft.com/en-us/Exchange/plan-and-deploy/system-requirements?view=exchserver-2019
https://learn.microsoft.com/en-us/Exchange/plan-and-deploy/prerequisites?view=exchserver-2019
Among the prerequisites, do you have Unified Communications Managed API 4.0 installed? If you have 5.0 installed, uninstall and install 4.0, which may cause you to experience error reporting issues.
You could refer to the relevant case:
https://social.technet.microsoft.com/Forums/en-US/97c83882-b3d5-42ab-83e7-d5d646e877ff/exchange-2016-cu14-installation-failed-in-step-10-of-17?forum=Exch2016SD

In addition, the error message is that the service is not started, you could try:

while (1 -le 2) { sleep 1 ; Get-Service | where{$_.DisplayName -Like 'Microsoft Exchange*'} | Set-Service –StartupType ‘Automatic’ }

Related Reference: https://learn.microsoft.com/zh-cn/archive/blogs/karthikm/unable-to-upgrade-cu-the-installation-source-for-this-product-is-not-available-verify-that-the-source-exists-and-that-you-can-access-it-error-code-is-1612

If an Answer is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Jame Xu-MSFT 4,176 Reputation points

2022-09-16T07:13:50.497+00:00

Hi, I'm here to confirm with you if your issue has been resolved. If the problem is successfully solved, you can share your solution and mark them or the helpful reply as answer, this will make answer searching in the forum easier and be beneficial to other community members as well.
Motubatse 1 Reputation point

2022-09-16T12:57:49.837+00:00

My issue is not yet resolved. All the answers I got here is what I already went thought many times
Motubatse 1 Reputation point

2022-09-16T13:00:53.043+00:00

Hi, All prerequisites are installed, and the Unified Communications Managed API 4.0 installed and it's still not helping. Service: Microsoft Exchange Service Hosting stuck on Starting and this happens everytime I reboot and restart the installation
Motubatse 1 Reputation point

2022-09-16T13:17:50.48+00:00

Errors in Windows Event:

Watson report about to be sent for process id: 4288, with parameters: E12IIS, c-RTL-AMD64, 15.02.0922.007, M.Exchange.ServiceHost, unknown, unknown, M.E.Common.ExServiceBase+ServiceStartTimeoutException, 0-dumptidset, unknown.
ErrorReportingEnabled: True

Process ExSetupUI.exe (PID=7072). WCF request (Get Servers for *********) to the Microsoft Exchange Active Directory Topology service on server (TopologyClientTcpEndpoint (localhost)) failed. Make sure that the service is running. In addition, make sure that the network ports that are used by Microsoft Exchange Active Directory Topology service are not blocked by a firewall. The WCF call was retried 3 time(s). Error Details
System.ServiceModel.EndpointNotFoundException: Could not connect to net.tcp://localhost:890/Microsoft.Exchange.Directory.TopologyService. The connection attempt lasted for a time span of 00:00:02.0231796. TCP error code 10061: No connection could be made because the target machine actively refused it 127.0.0.1:890. ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 127.0.0.1:890
at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.Sockets.Socket.Connect(EndPoint remoteEP)
at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
--- End of inner exception stack trace ---
Motubatse 1 Reputation point

2022-09-16T20:01:53.94+00:00

No mailbox database created
Jame Xu-MSFT 4,176 Reputation points

2022-09-19T09:43:24.697+00:00

Hi @Motubatse ,
Do you use a firewall? The error message is that you cannot connect to the network, and if you use a firewall, you need to disable it.
Motubatse 1 Reputation point

2022-09-19T11:00:26.44+00:00

I cannot be the firewall because it was disabled
Jame Xu-MSFT 4,176 Reputation points

2022-09-21T08:36:05.423+00:00

Hi @Motubatse ,
Did you CU upgrade or install a brand new Exchange and what steps did you follow to install it?
Motubatse 1 Reputation point

2022-09-21T20:23:55.67+00:00

Hi @Jame Xu-MSFT , we decommissioned an old Exchange 2010 and installed Exchange 2019 on a brand-new Windows server. So, we started installing all the prerequisites before continuing with the installation
Jame Xu-MSFT 4,176 Reputation points

2022-09-23T08:17:22.87+00:00

Hi @Motubatse ,
You could use the SetupAssist to check if the relevant components are missing.

1 answer

Amit Singh 4,896 Reputation points

2022-09-14T03:11:10.28+00:00

Please have a check and verify all the system requirements and prerequisites to install Exchange 2019 have been met. And if the server you are trying to install Exchange on is a domain controller, it’s recommended to install on a member server instead, see Installing Exchange on a domain controller is not recommended.

For anyone else with this sort of problem, these article seems to resolve it -
https://exchangeshare.wordpress.com/2014/05/16/exchange-2013-sp1-install-error-database-is-mandatory-on-arbitration-mailboxes/
https://www.stellarinfo.com/article/setup-new-exchange-server-2019.php
Please sign in to rate this answer.
Motubatse 1 Reputation point

2022-09-16T13:01:28.657+00:00

All System requirements are met and the Exchange is not being installed on the AD Server
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Exchange 2019 Installation stuck on Step 7

1 answer

Your answer