Event ID 2601, 2604, 2501
We are running Exchange 2010 Service Pack 1 on our CAS servers and we are getting the following event ID: Event ID 2601 - Warning Event ID 2604 - Error Event ID 2501 - Error All these events are related to source of MSExchange ADAccess Does anyone have any suggestions on how to correct this? Or what to look for, as I saw a couple of other posting and those steps did not help.
March 23rd, 2011 1:29pm

Few of us have memorized all event ID numbers and few of us are inclined to look up the numbers you've posted, so please post the entire event log entry. You are welcome to use the handy-dandy "copy to clipboard" button in the event log detail window to assist you with this.Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
Free Windows Admin Tool Kit Click here and download it now
March 23rd, 2011 1:55pm

Ed, Sorry - I was in a hurry this afternoon. What does the MSExchange ADAccess need? Log Name: Application Source: MSExchange ADAccess Date: 3/23/2011 5:54:35 PM Event ID: 2601 Task Category: General Level: Warning Keywords: Classic User: N/A Computer: XXXXXXXXXXXXXX Description: Process MSEXCHANGEADTOPOLOGY (PID=1888). When initializing a remote procedure call (RPC) to the Microsoft Exchange Active Directory Topology service, Exchange could not retrieve the SID for account <WKGUID=XXXXXXXXXXX,CN=Microsoft Exchange,CN=Services,CN=Configuration,...> - Error code=8007077f. The Microsoft Exchange Active Directory Topology service will continue starting with limited permissions. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="MSExchange ADAccess" /> <EventID Qualifiers="32772">2601</EventID> <Level>3</Level> <Task>1</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2011-03-23T21:54:35.000000000Z" /> <EventRecordID>370003</EventRecordID> <Channel>Application</Channel> <Computer>XXXXXXXXXXXX</Computer> <Security /> </System> <EventData> <Data>MSEXCHANGEADTOPOLOGY</Data> <Data>1888</Data> <Data>&lt;WKGUID=XXXXXXX,CN=Microsoft Exchange,CN=Services,CN=Configuration,...&gt;</Data> <Data>8007077f</Data> </EventData> </Event> Log Name: Application Source: MSExchange ADAccess Date: 3/23/2011 5:54:35 PM Event ID: 2604 Task Category: General Level: Error Keywords: Classic User: N/A Computer: XXXXXXX Description: Process MSEXCHANGEADTOPOLOGY (PID=1888). 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 XXXXXXX - Error code=8007077f. The Microsoft Exchange Active Directory Topology service will continue starting with limited permissions. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="MSExchange ADAccess" /> <EventID Qualifiers="49156">2604</EventID> <Level>2</Level> <Task>1</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2011-03-23T21:54:35.000000000Z" /> <EventRecordID>370004</EventRecordID> <Channel>Application</Channel> <Computer>XXXXXXX</Computer> <Security /> </System> <EventData> <Data>MSEXCHANGEADTOPOLOGY</Data> <Data>1888</Data> <Data>XXXXXX</Data> <Data>8007077f</Data> </EventData> </Event> Log Name: Application Source: MSExchange ADAccess Date: 3/23/2011 5:54:35 PM Event ID: 2501 Task Category: General Level: Error Keywords: Classic User: N/A Computer: XXXXXXXXX Description: Process MSEXCHANGEADTOPOLOGY (PID=1888). 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 Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="MSExchange ADAccess" /> <EventID Qualifiers="49156">2501</EventID> <Level>2</Level> <Task>1</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2011-03-23T21:54:35.000000000Z" /> <EventRecordID>370005</EventRecordID> <Channel>Application</Channel> <Computer>XXXXXXXX</Computer> <Security /> </System> <EventData> <Data>MSEXCHANGEADTOPOLOGY</Data> <Data>1888</Data> <Data>DsctxGetContext</Data> <Data>8007077f</Data> </EventData> </Event>
March 23rd, 2011 6:27pm

Hi sabo_e, During restart of the server, the operating system queries Active Directory to get its AD Site information. On a Windows 2008 R2 server, this will sometimes fail. As the Exchange Services are starting, it also will do a query for its AD site and that too will fail. You can get more information from this KB: MSExchange ADAccess Event ID's 2601, 2604, 2501 http://support.microsoft.com/kb/2025528 I also suggest you use Exbpa to do a health check for your Exchange Server, if you get any related information, please paste in your next post. Thanks, Evan Liu TechNet Subscriber Support in forum If you have any feedback on our support, please contact tngfb@microsoft.com Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Free Windows Admin Tool Kit Click here and download it now
March 24th, 2011 1:26am

Evan, Are you aware if a hotfix has been released for this issue? I noticed the KB article is a year old, hoping it was been resolved in a update somewhere. If not is there any way to prevent this behavior, ie. delay the exchange startup or do we simply need to live with restarting to the Topology service after a reboot? Thanks, Chris
May 10th, 2011 1:13pm

No hotfix, but this is a known issue, MS did fix by hard coding the sitename into the netlogon registry key.
Free Windows Admin Tool Kit Click here and download it now
May 10th, 2011 1:53pm

Hi, Please let me know which registry key they hard coded. MNYash
June 14th, 2011 12:49am

HKLM\System\CurrentControlSet\Services\Netlogon\Parameters New -> String Value (REG_SZ) and name the REG_SZ value: “SiteName” without the quotes We also set Microsoft Exchange Forms-Based Authentication Service to a delayed startup type Let me know if this helps or not.
Free Windows Admin Tool Kit Click here and download it now
June 15th, 2011 7:59am

This seems to have helped the issue, but i still see the evenid in the log. is that wah tyou see also?
June 15th, 2011 3:53pm

This seems to have helped the issue, but i still see the evenid in the log. is that wah tyou see also?
Free Windows Admin Tool Kit Click here and download it now
June 15th, 2011 10:48pm

This seems to have helped the issue, but i still see the evenid in the log. is that wah tyou see also?
June 15th, 2011 10:48pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics