troubleshooting Question

Topology Provider coundn't find the Microsoft Exchange Active Directory Topology

Avatar of Matthias Unterrieder
Matthias UnterriederFlag for Switzerland asked on
ExchangeActive DirectoryMicrosoft
5 Comments1 Solution11 ViewsLast Modified:

Trying to reach the lokal Exchnage Server on an Hybrid Exchange 2019

this behavior is since yesterday, no Microsoft Updates since 4 Days.

Error Message from Broswer:

Topology Provider coundn't find the Microsoft Exchange Active Directory Topology service on end point 'TopologyClientTcpEndpoint (localhost)'.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: Microsoft.Exchange.Data.Directory.ADTopologyEndpointNotFoundException: Topology Provider coundn't find the Microsoft Exchange Active Directory Topology service on end point 'TopologyClientTcpEndpoint (localhost)'.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

The Connection to the online Site O365 works fine.

Error Log on Server: MSExchange ADAccess 4027

Process MSExchangeHMWorker.exe (ExHMWorker) (PID=2548). WCF request (Get Servers for herzelmg.lan) 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.0030027. 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 ---


---------------------------
  • i have all default Subnet Setup in AD Site and Services
  • I'm able to connect to the AD Server and Browse the OU's by [Computer Management / Groups]
  • i set the Exchange Server to the GPO "Audit Security Privilege"
  • nltest /dsgetsite will show the correct "Default Site"
  • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters Value of [DynamicSiteName] i st also Set

  • I'm not able to start the Service [Microsoft Exchange Active Directory Topology] on the Server
  • Computer account is in all necessary AD Groups
  • Tried to solve with or without firewall enabled
  • Network Settings on Server are Correct

any help appreciated
Mat
Join the community to see this answer!
Join our exclusive community to see this answer & millions of others.
Unlock 1 Answer and 5 Comments.
Join the Community
Learn from the best

Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.

Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 1 Answer and 5 Comments.
Try for 7 days

”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.

-Mike Kapnisakis, Warner Bros