Exchange AD Topology is not starting - event id 7000 & 7009

Question

Dear All,

I have a problem with our Exchange 2019. This was migrated a few months before from an SBS 2008 server in two steps, to a temporary E2016 server and finally to 2019. The old SBS was the only DC, all the migration process has been done successfully with dcpromo, they are not using it for months. The old DC name was "SERVER", the new is "SRV-DC". Now after I had cleared it's old server's DNS entry from DNS the Exchange services had stopped and I cannot start them. I have found the old DC server under Active directory sites, and deleted it, and also found some entries in DNS, and cleared them too. Now, I can't find anything about the old DC server, everything looks fine, all diagnostics show me that the only DC is SRV-DC, but Exchange services still couldn't start, first of all, the AD topology service. I got no explained error messages just event id 7000 and 7009, which tells me that the service is not starting due to a timeout.
Please help me!
Exchange powershell is not working too. Only diagnostics, health manager, health manager recovery and search host controller service is running, nothing else! IPv6 is enabled, and I have already uninstalled the AV from the computer, restarted a few times but there's no solution.

Answer 1

Thanks guys. Problem has been solved. The original problem was that, according to another forum I had modified the AD topology service's config file (Microsoft.Exchange.Directory.TopologyService.exe.config) and set MinPercentageOfHealthyDC = "50" and added this line: MinSuitableServer = "1"
I don't know which was the problem with this, but when I was restored the previous version of the file from shadow copy the service and other Exchange services were started successfully. So the problem was created by myself while I was working on the original problem and when I was corrected the DNS entries and AD sites configuration the other problem had prevented the service to start. That was simple to fix but hard to investigate. :) Thank you for your suggestions again!

Answer 2

Hello @Zoltán Berente

I would like to suggest you to increase Service Time out from Registry, please take backup before change.

1. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control
2. In the right pane, locate the ServicesPipeTimeout entry.

If the ServicesPipeTimeout entry does not exist, you must create it. To do this, follow these steps:

1. On the Edit menu, point to New, and then click DWORD Value.
2. Type ServicesPipeTimeout , and then press Enter.
3. Right-click ServicesPipeTimeout, and then click Modify.
4. Click Decimal, type 60000, and then click OK. This value represents the time in milliseconds before a service times out.
5. Reboot the Server.

If the reply was helpful, please don’t forget to upvote or accept as answer.

Answer 3

@Zoltán Berente

Remove record from ADSI isn't suggested and supported. About this issue, here are my suggestion:

Fist, make sure all the topology is supported in your organization: Exchange Server supportability matrix

Then, try to prepare AD/Domain/Schema on this Exchange server. After preparing, try to restart Exchange server and check again.

If you cannot complete the prepare operation, I would suggest you try to deploy an another Exchange, then move database using database portability.

---

If the response 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.

Answer 4

Is this issue resolved? whats was the solution?