Fix for Event ID 2937 MSExchange ADAccess in Exchange 2010 SP1

Sunday, September 26, 2010
I have noticed the following event on Exchange 2010 servers after upgrading Exchange 2010 RTM to Exchange 2010 Service Pack 1:


Log Name:      Application
Source:        MSExchange ADAccess
Date:          9/26/2010 9:12:29 AM
Event ID:      2937
Task Category: Validation
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      EX1.companyabc.com
Description:
Process w3wp.exe () (PID=1960). Object [CN=Jeff Guillet,CN=Users,DC=companyabc,DC=com]. Property [HomeMTA] is set to value [companyabc.com/Configuration/Deleted Objects/Microsoft MTA
DEL:0a05fe00-f8ce-4016-bba8-dce98cfe6b93], it is pointing to the Deleted Objects container in Active Directory. This property should be fixed as soon as possible.

The process in the event varies, but I've seen:
  • EdgeTransport.exe
  • ExSetupUI.exe (when installing Exchange)
  • Microsoft.Exchange.RpcClientAccess.Service.exe
  • Microsoft.Exchange.ServiceHost.exe
  • MSExchangeMailboxAssistants.exe (when moving a mailbox)
  • powershell.exe (when a user launches the Exchange 2010 management tools)
  • w3wp.exe (when the user accesses OWA)
The event in the example above is most commonly seen, and is caused when the user's homeMTA attribute is pointing to a deleted object in AD.  To fix this for a specific user, run the following command from the Exchange Management Shell (EMS) on the server:
Get-Mailbox jeff | Update-Recipient
Or for all user mailboxes use:
Get-Mailbox | Update-Recipient
To correct the arbitration mailboxes use:
Get-Mailbox -Arbitration | Update-Recipient
These commands will update the user's homeMTA value to the correct value.

I've also seen this warning for the Edge Transport routing group property, as shown below.

Log Name:      Application
Source:        MSExchange ADAccess
Date:          7/12/2010 8:52:23 AM
Event ID:      2937
Task Category: Validation
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      EX1.companyabc.com
Description:
Process edgetransport.exe () (PID=3500). Object [Exchange Routing Group (DWBGZMFD01QNBJR)]. Property [RoutingMasterDN] is set to value [mailgate
DEL:b2bbdba9-71e4-46ff-a50b-fbea9a6c4534], it is pointing to the Deleted Objects container in Active Directory. This property should be fixed as soon as possible
.
To correct this error:
  • Open ADSIEdit and navigate to CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=companyabc,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=companyabc,DC=com.
  • Right-click the Edge Transport server and copy the distinguishedName value.
  • Navigate to CN=Exchange Routing Group (DWBGZMFD01QNBJR),CN=Routing Groups,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=companyabc,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=companyabc,DC=com and open its properties
  • Paste the copied DN value to the msExchangeRoutingMasterDN attribute

5 comments:

  1. Jeff, thanks for the post. I had the RoutingMasterDN warning as well, and was wondering what value I needed to replace it with.

    ReplyDelete
  2. This didn't work for me it wasn't there this is how I fixed it
    http://www.petenetlive.com/KB/Article/0000448.htm

    ReplyDelete
  3. Hello Jeff,

    Thanks this works for me.

    Werner

    ReplyDelete
  4. Hello Jeff,

    I am receiving this same error but it's for my Offline Address Lists as shown below. I have replaced my domain name, etc with x's for privacy. The solutions provide above are not working. Can you help?

    Process w3wp.exe () (PID=6996). Object [CN=Default Offline Address List,CN=Offline Address Lists,CN=Address Lists Container,CN=xxxx,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=xxxx,DC=org]. Property [PublicFolderDatabase] is set to value [xxxx.org/Configuration/Deleted Objects/Public Folder Store (EXCHANGE)
    DEL:fd81f0f7-91e5-4940-8970-ab159a70d70b], it is pointing to the Deleted Objects container in Active Directory. This property should be fixed as soon as possible.

    ReplyDelete
    Replies
    1. Run the Exchange Best Practices Analyzer in EMC Tools. Follow the link in results to the solution.

      Delete

Thank you for your comment! It is my hope that you find the information here useful. Let others know if this post helped you out, or if you have a comment or further information.