Exchange Server 2010 Troubleshooting Issues – Part III

First of all a HUGE THANKS to Yuval Sinay for putting this information together.

The following article will provide a summary on common issues in Exchange 2010 deployment in the Enterprise. The information in this article consists of my own experience and official Microsoft knowledgebase articles. Due to the fact that your Exchange environment may vary, please read the information carefully and test the suggestions from this article - in a lab that can demonstrate the current Exchange infrastructure.

The article is divided to the following chapters:

1. General issues in Exchange 2010 deployment.

2. Best practices in Exchange 2010 deployment.

3. Common issues in Exchange 2007 migration to Exchange 2010.

4. Common issues in Exchange 2003 migration to Exchange 2010.

Common issues in Exchange 2007 migration to Exchange 2010

• Strange errors may appear during OWA/Outlook Anywhere, Offline Address book management (e.g. Event ID 9519 "Error 0x80004005" in Application event log, etc.).
  • Event ID 9519 "Error 0x80004005" is logged in the Application log when you try to mount a database in Exchange Server 2010 or in Exchange Server 2007
  • In rare situations, you may need to apply the solution from the link above, to “Exchange Enterprise Servers” group (e.g. Give the group the user right to”Manage auditing and security log” in the domain controllers GPO) – I saw this issue when the Exchange 2007 server was installed in the past on domain controller.
• After creating a new Exchange 2010 database, the new database wouldn’t mount and the following error may appear: “Active Directory operation failed on <<DOMAIN CONTROLLER NAME>>. This error is not retrievable. Additional information: The name reference is invalid. This may be caused by replication latency between Active Directory domain controllers. Active directory response: 000020B5: AtrErr: DSID-03152392, #1: 0: 000020B5: DSID-03152392, problem 1005 (CONSTRAINT_ATT_TYPE), data 0, Att 200f4 (homeMDB)”
  • You cannot create a new Exchange Server 2010 Mailbox database in a multiple domain environment
  • Due the fact that the issue appear in customer with a single domain, I recommended to review the steps bellow.
    • Use the following method to create a new Exchange 2010 database:
      • Create a new Exchange 2010 database without mount it.
      • Use the power shell command to force the Exchange 2010 to use a preferred domain controller: "Set-ADServerSettings –PreferredServer mydomaincontrollername.domainname.local"
      • Mount the database by using the following power shell command: "Mount-Database -Identity "Second Mailbox Store" -DomainController mydomaincontrollername.domainname.local"