Exchange 2010 event errors 2601, 2604, 2501

In a recent migration from Exchange 2003/2007 to Exchange 2010, I ran into an issue where I had 2601, 2604, and 2501 errors.


Log Name:      Application
Source:        MSExchange ADAccess
Date:          4/8/2013 12:02:20 PM
Event ID:      2601
Task Category: General
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      Exchange10.domain.org
Description:
Process MSEXCHANGEADTOPOLOGY (PID=1268). When initializing a remote procedure call (RPC) to the Microsoft Exchange Active Directory Topology service, Exchange could not retrieve the SID for account - Error code=8007077f. 
 The Microsoft Exchange Active Directory Topology service will continue starting with limited permissions.


and


Log Name:      Application
Source:        MSExchange ADAccess
Date:          4/8/2013 12:02:20 PM
Event ID:      2604
Task Category: General
Level:         Error
Keywords:      Classic
User:          N/A
Computer:     Exchange10.domain.org
Description:
Process MSEXCHANGEADTOPOLOGY (PID=1268). 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 EXCHANGE10 - Error code=8007077f.
 The Microsoft Exchange Active Directory Topology service will continue starting with limited permissions.

and lastly


Log Name:      Application
Source:        MSExchange ADAccess
Date:          4/8/2013 12:02:20 PM
Event ID:      2501
Task Category: General
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Exchange10.domain.org
Description:
Process MSEXCHANGEADTOPOLOGY (PID=1268). 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.





The issue was caused by adding a second IP address to the server so that I didn't have to reconfigure all the mail-enabled devices, hosts and applications.  I retired the 2003 and 2007 servers and gave the two extra IP addresses to the Exchange 2010 server.  The server functioned fine with multiple IP addresses, but it had these errors.

To solve this,



  1. open a command prompt as Administrator and run "IPCONFIG /registerdns"
  2. Open the Services snap-in and restart the Microsoft Exchange Active Directory Topology service.  This will warn you that it will restart about six to ten other Exchange services (depending on your configuration).  Some of theses services may result in a brief service disruption so plan accordingly.



Comments

Post a Comment

Popular posts from this blog

"The following factors also affect the level of access for" user with excess permissions

Image
I have a user that had access to site settings, all content, etc. I double checked her access and it was read only but the permissions check tool showed a panel beneath the site permissions that showed Allow for many categories. She had full control. "The following factors also affect the level of access for" She was added as a Site Collection Administrator. I don't know who would have added her there, but someone had. If you find this type of issue, that should be the first thing you check. You can also check the Web Application User Policy in Central Admin. That's the other area I find people or groups with elevated permissions.
Read more

Robocopy Error 31 A device attached to the system is not functioning

I was migrating Windows file shares to NetApp CIFS shares using Robocopy. I was unable to copy owner information or NTFS Security (/COPY:DATSOU) without getting this Error: ERROR 31 (0x0000001F) Copying NTFS Security to Destination Directory F:\PATH A device attached to the system is not functioning. I thought it may be the zone information on may of these files. I used the Sysintenals Streams utility to remove that information. It did not help. In the end, I was forced to copy without NTFS information (/COPY:DATU) When I viewed the properties of any share, folder, or file, the length of time to enumerate and display the permissions was exceedingly slow. I tried disabling anti-virus, etc. In the end, I had to manually re-create the permissions after the initial data copy. File ownership information was lost. UPDATE: I ran a CHKDSK /F and following a reboot this robocopy functioned fine.
Read more