• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 9270
  • Last Modified:

Exchange 2010 event log error 2501, 2604, and 2601

I have 4 exchange 2010 servers.  All  exchange 2010 servers are installed on a hyper-v virtual with Server 2008 SP2.  I do not have SP1 for exchange 2010 installed.  For about a month now I have been getting the following errors in my event logs every 15 minutes on all 4 exchange 2010 servers:

EVENT ID - 2501.
Process MSEXCHANGEADTOPOLOGY (PID=1912). 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.

EVENT ID - 2604
Process MSEXCHANGEADTOPOLOGY (PID=1912). When updating security for a remote procedure call (RPC) access for the Microsoft Exchange Active Directory Topology service, Exchange could not retrieve the security descriptor for Exchange server object REGULUS - Error code=8007077f.
 The Microsoft Exchange Active Directory Topology service will continue starting with limited permissions.

EVENT ID - 2601
Process MSEXCHANGEADTOPOLOGY (PID=1912). When initializing a remote procedure call (RPC) to the Microsoft Exchange Active Directory Topology service, Exchange could not retrieve the SID for account <WKGUID=1A9E39D35ABE5747B979FFC0C6E5EA26,CN=Microsoft Exchange,CN=Services,CN=Configuration,...> - Error code=8007077f.
 The Microsoft Exchange Active Directory Topology service will continue starting with limited permissions.

I have had these 4 exchange 2010 servers up and running for about 10 months now, but just recently started getting these errors.  Any ideas on how to fix them?  Thanks.
1
denver218
Asked:
denver218
1 Solution
 
Shreedhar EtteCommented:
Hi,

Refer this article:
http://support.microsoft.com/kb/2025528

Hope this helps,
Shree
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
denver218Author Commented:
Thanks.  That solved the problem.
0
 
abedfarahCommented:
0
 
Senior IT System EngineerIT ProfessionalCommented:
Yes, I've just got to this issue as well.

So what's the permanent fix ?
0

Featured Post

Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now