Solving the Event ID 2937 MSExchange ADAccess error on the server side

Share this:

In this Tutorial we are going over the process to fix the error 2937 on an Exchange Server 2010/2013 when the issue happens on an object different than an user.

Solution


This error may occur at the object level (Mailbox or Arbitration Mailbox) and it can be solved by running the following cmdlet:

Get-Mailbox <Mailbox> | Update-Recipient

The solution can be found on this Microsoft document http://technet.microsoft.com/en-ca/library/d00ed0ed-d9b5-48df-9ff7-32f1a9cc592b.aspx however it does not address when the issue is with specific services, such as w3wp.exe as shown in the figure below.

image

In the issue above the issue is that the information that we have on the msExchRoutingMasterDN has an invalid entry, and that may happen when an old server is removed (specially when your environment is coming from several transitons Exchange 2003 –> 2007/2010 and so forth).

The solution is simple, first we need to find an existent server that has the Hub Transport role installed, and these are the steps that we can use logged as administrator on any Domain Controller.

1. Open Adsiedit.msc

2. Expand Configuration (or open it)

3. Expand CN=Configuration

4. Expand CN=Services

5. Expand CN=Microsoft Exchange

6. Expand CN=<Organization Name>

7. Expand Administrative Groups

8. Expand CN=Exchange Administrative Group (FYDIBOHF23SPDLT)

9. Expand Servers

10. Right click on the chosen server and click Properties

11. Double click on distinguishedName and copy the content, it will be something like this:

CN=TOREXCH01,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=OrganizationName,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domain,DC=local

image

Time to go back on the tree and get properties of the Exchange Routing Group (DWBGZMFD01QNBJR) and we can use these following steps:

1. Open Adsiedit.msc

2. Expand Configuration (or open it)

3. Expand CN=Configuration

4. Expand CN=Services

5. Expand CN=Microsoft Exchange

6. Expand CN=<Organization Name>

7. Expand Administrative Groups

8. Expand CN=Exchange Administrative Group (FYDIBOHF23SPDLT)

9. Expand CN=Routing Groups

10. Right-click on Exchange Routing Group (DWBGZMFD01QNBJR) and then Properties

11. Double click on msExchRoutingMasterDN and remove the current value and add the new value that we copied from the previous steps.

image

After that we can restart the MSExchange Transport and at this time we won’t see the issue.

Conclusion


In this Tutorial we went over the process to fix the event ID 2937 for MSExchange ADAccess.

Written by Anderson Patricio

Anderson Patricio

Anderson Patricio is a Canadian MVP in Cloud and Datacenter Management, and Office Server and Services, besides the Microsoft Award he also holds a Solutions Master (MCSM) in Exchange and several other certifications. Anderson has been contributing to the Microsoft Community with articles, tutorials, blog posts, twitter, forums and book reviews. He is a regular contributor here at ITPROCentral.com, MSExchange.org, Techgenix.com and Anderson Patricio.org (Portuguese).