exchange 2016 services stuck in starting

ramin sa 261 Reputation points
2023-02-21T06:45:40.3766667+00:00

Hi dear Expert

our exchange services stuck in starting and we get below event

"Process Microsoft.Exchange.Directory.TopologyService.exe (PID=4744) Forest xxx.xx Topology discovery failed, error details

No Suitable Directory Servers Found in Forest xxx.xx Site Default-First-Site-Name and connected Sites.."

Please give me hand to fix my issue

Exchange | Exchange Server | Other
Exchange | Exchange Server | Management
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Yuki Sun-MSFT 41,376 Reputation points Moderator
    2023-02-21T08:17:05.75+00:00

    Hi @ramin sa

    Any changes were made in the environment right prior to the occurrence of this issue?
    Are there any other potentially relevant event logs recorded together with this one in the event viewer?
    What's the basic topology of your Exchange environment?

    Please try adding the MinSuitableServer value and see if it can help.
    Reference: Event ID 2142 when Exchange services don't start

    1. Locate Microsoft.Exchange.Directory.TopologyService.exe.config File , By Default It Should Be Under "C:\Program Files\Microsoft\Exchange Server\V15\Bin"
    2. Open NotePad As Administrator & Then Open Microsoft.Exchange.Directory.TopologyService.exe.config File
    3. Locate "Topology MinimumPrefixMatch"
    4. Add MinSuitableServer = "1"
    5. Save The File & Restart Microsoft Exchange Active Directory Topology Services.  

    If the above doesn't work, please try enabling IPV6 on the primary server and check the result.


    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

    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.


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.