I came across an Exchange 2007 server with CAS, Hub Transport and Exchange UM roles installed that consistently had event ID: 2501, 2604, 2601 from source MSExchange ADAccess logged every 14 to 16 minutes. The events are as follows:
Error: Event ID 2501
Process MSEXCHANGEADTOPOLOGY (PID=1424). The site monitor API was unable to verify the site name for this Exchange computer – Call=DsctxGetContext Error code=8007077f. Make sure that Exchange server is correctly registered on the DNS server.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Error: Event ID 2604
Process MSEXCHANGEADTOPOLOGY (PID=1424). When updating security for a remote procedure call (RPC) access for the Exchange Active Directory Topology service, Exchange could not retrieve the security descriptor for Exchange server object serverName – Error code=8007077f.
The Exchange Active Directory Topology service will continue with limited permissions.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Warning: Event ID 2601
Process MSEXCHANGEADTOPOLOGY (PID=1424). When initializing a remote procedure call (RPC) to the Microsoft Exchange Active Directory Topology service, Exchange could not retrieve the SID for account <WKGUID=DC1301662F547445B9C490A52961F8FC,CN=Microsoft Exchange,CN=Services,CN=Configuration,…> – Error code=8007077f.
The Microsoft Exchange Active Directory Topology service will continue starting with limited permissions.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Solution
So what fixed it? The error went away after I restarted the server: Microsoft Exchange Active Directory Topology Service in the services console. Note that the following services rely on this:
Microsoft Exchange Unified Messaging
Microsoft Exchange Transport Log Search
Microsoft Exchange Transport
Microsoft Exchange File Distribution
Microsoft Exchange EdgeSync
Microsoft Exchange Anti-spam Update
This essentially means that all your services will briefly go down so be aware of this before you restart it.
I just checked back after 5 hours and haven’t seen those errors and warnings appear since the service was restarted.
One Response
The same happened to my Servers. I restrated them, the error went away..
BUT..it started appearing again.
….
My Solution:
….
To address this issue, modify the network adapter binding list to configure the active network adapter as the first entry in the binding list.
AND,
restart the Microsoft Exchange Active Directory Topology service (it will also resrt all the dependent services as well).