Exchange 2010 Install Error: Database is Mandatory on UserMailbox

Installing new Exchange 2010 on Server 2008r2 in Server 2003 domain with an existing Exchange 2003 Server.

Getting this error (see attached screen shot).

I ran this command:

adfind -default -f "&(objectcategory=person)(objectclass=user)" samaccountname displayname homemdb -nodn -csv > c:\users.csv

And didn't find any users whose homemdb is NOT in the existing mail server.

I did have one aborted install of Exchange2010 on this domain and did create one test mailbox and then ended up deleting everything... I thought.  But I think that test mailbox might be my problem.

But it's not in Active Directory Users and Computers and it's not in the above users.csv generated by the adfind statement.

Thanks for any ideas on how to find my bad object.

Who is Participating?
GilesmpConnect With a Mentor Commented:
Hmm, well the order of installation should be CA, HT, MB.  If you're saying the mailbox role is already installed  you may want to uninstall the mailbox role, reinstall hub then mailbox separately.

Although first, in adsiedit, can you check in "DC=domain, CN=users", find the "CN=FederatedEmail....", right click, Properties and see if the "homeMDB" is set for that and see where the "homeMTA" is pointing.

If the "homeMDB" is missing and/or the "homeMTA" is pointing at an incorrect location this can trigger the error you have received.  You can recreate the Federated Account by following this article
Are you able to see a trace of the test account anywhere using adsiedit.msc?
gateguardAuthor Commented:
I don't see it under the Users OU in Domain.  Is there another place to look?

Is there a search function in adsiedit?
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

Are you installing the Exchange roles separately or together?
gateguardAuthor Commented:
I did them together, then got a failure on the Hub Transport for an orphaned connector, which I resolved and then re-ran the installer choosing the first 3 roles (mailbox, client access, hub transport) and it went immediately to the Hub Transport installer since the other 2 were already installed.

gateguardAuthor Commented:
I used this article,
and tried to follow  these steps:

1. Remove the FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042 e-mail account by using the ADSIEDIT tool. To do this, follow these steps:
a. Click Start, click Run, type adsiedit.msc, and then click OK.
b. Locate the Default Naming Context node, and then locate to the CN=Users container.
c. Locate and then right-click the CN=FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042 container. Then, click Delete.
2. Rerun the Exchange Server 2010 Mailbox role setup application.
3. Create a new federated e-mail account by using the following command:
New-Mailbox -Arbitration -Name FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042 -UserPrincipalName FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042@<Default_Accepted_Domain>

But step #2 is now failing:

Mailbox Role

The following error was generated when "$error.Clear();
          if ($RoleCreatePublicFolderDatabase)
            $publicDB = get-PublicFolderDatabase -Server:$RoleFqdnOrName -ErrorAction SilentlyContinue;
            $DB = get-MailboxDatabase -Server:$RoleFqdnOrName -ErrorAction SilentlyContinue;
            if ($publicDB -and $DB)
                set-mailboxdatabase `
                  -Identity:$DB.Identity `
                  -publicFolderDatabase:$publicDB.Identity `
                  -DomainController $RoleDomainController
        " was run: "Cannot bind argument to parameter 'Identity' because it is null.".

Cannot bind argument to parameter 'Identity' because it is null.

gateguardAuthor Commented:
I tried that solution and now I'm really hosed.  I can't move forward because I have errors and I can't move back because I can't uninstall anything.  If I try to uninstall the failed mailbox role it says my public folder has replicas and they have to be removed first, with no indication how to do that.

I would really like to just wipe this server but before I do that I want to know:

Is there a SURE way to "remove a failed exchange2010 server" from my (probably now corrupted) domain?
I'm not aware of a step by step guide for removing a failed uninstall of Exchange 2010.

I'm afraid all I can suggest at the moment is try to address the error you are receiving first and then retry the uninstall.

What I believe the error is asking you to do is to move all public folder replicas back to the 2003 server and delete the instances on the 2010 box.  You should be able to use MoveAllReplicas.ps1 to do move them back to the 2003 server ... more info here
gateguardAuthor Commented:
I ended up wiping the server and then rebuilding it with the same name, ip and joined to the domain I ran: /m:recoverserver

But thanks for all your help on this question.  I learned a lot.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.