Solved

Exchange 2010 Install Error: Database is Mandatory on UserMailbox

Posted on 2011-09-02
10
1,307 Views
Last Modified: 2012-05-12
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.

   ErrorInstallingHubTransportRole.pdf
0
Comment
Question by:gateguard
  • 5
  • 5
10 Comments
 
LVL 3

Expert Comment

by:Gilesmp
ID: 36473337
Are you able to see a trace of the test account anywhere using adsiedit.msc?
0
 

Author Comment

by:gateguard
ID: 36473460
I don't see it under the Users OU in Domain.  Is there another place to look?

Is there a search function in adsiedit?
0
 
LVL 3

Expert Comment

by:Gilesmp
ID: 36473774
Are you installing the Exchange roles separately or together?
0
 

Author Comment

by:gateguard
ID: 36474491
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.

0
 
LVL 3

Accepted Solution

by:
Gilesmp earned 500 total points
ID: 36474690
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 http://support.microsoft.com/kb/978776
0
Shouldn't all users have the same email signature?

You wouldn't let your users design their own business cards, would you? So, why do you let them design their own email signatures? Think of the damage they could be doing to your brand reputation! Choose the easy way to manage set up and add email signatures for all users.

 

Author Comment

by:gateguard
ID: 36478164
I used this article, http://support.microsoft.com/kb/978776
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
Failed

Error:
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.


0
 
LVL 3

Expert Comment

by:Gilesmp
ID: 36480160
0
 

Author Comment

by:gateguard
ID: 36485957
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?
0
 
LVL 3

Expert Comment

by:Gilesmp
ID: 36487550
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 http://technet.microsoft.com/en-us/library/bb331970.aspx
0
 

Author Closing Comment

by:gateguard
ID: 36526101
I ended up wiping the server and then rebuilding it with the same name, ip and joined to the domain I ran:

setup.com /m:recoverserver

But thanks for all your help on this question.  I learned a lot.
0

Featured Post

How to run any project with ease

Manage projects of all sizes how you want. Great for personal to-do lists, project milestones, team priorities and launch plans.
- Combine task lists, docs, spreadsheets, and chat in one
- View and edit from mobile/offline
- Cut down on emails

Join & Write a Comment

"Migrate" an SMTP relay receive connector to a new server using info from an old server.
Disabling the Directory Sync Service Account in Office 365 will stop directory synchronization from working.
In this video we show how to create a Shared Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >> Sha…
To add imagery to an HTML email signature, you have two options available to you. You can either add a logo/image by embedding it directly into the signature or hosting it externally and linking to it. The vast majority of email clients display l…

747 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

12 Experts available now in Live!

Get 1:1 Help Now