Adding a Mailbox Server Role to Exchange 2010: “Database is mandatory on UserMailbox”
I came across an interesting error while adding a Mailbox Server to my Exchange Server 2010 environment the other day. The error was pretty clear-cut, and the solution was also pretty simple, but very non-intuitive, so I thought I’d explain how to fix it here. To give full credit, I got my answer from this dialog on the Microsoft TechNET forums, and the fellow with the username Nair.SS helped my solve the problem. It turns out another individual was having exactly the same problem, and he got his issue solved as well. Many thanks to Nair.SS.
The Error
The error message is pictured in this screenshot, and I’ve included the text in the caption:
Here’s the text from that error dialog box.
The following error was generated when “$error.Clear(); if ( ($server -eq $null) -and ($RoleIsDatacenter -ne $true) ) { Update-RmsSharedIdentity -ServerName $RoleNetBIOSName }” was run: “Database is mandatory on UserMailbox. Property Name: Database”.
Database is mandatory on UserMailbox. Property Name: Database
One important detail to include here is that I had two mailbox servers installed in this environment and I was unable to gracefully uninstall them. Thus I had to delete them out of Active Directory using ADSI Edit. I’m pretty sure this is what caused the problem.
The Fix
One of the mailboxes had incorrect settings in Active Directory, so I used ADSI Edit to edit that user.
I connected to the Domain well known Naming Context in my root domain and found the user named CN=FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042. I’m not sure if all those numbers will be the same for everyone, but you can just find the FederatedEmail user. The homeMDB property was blank, so I inserted the CN value of an existing database into the value field, formatted as such:
CN=db1,CN=Databases,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=GTRI,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=gtri,DC=test
I went to install the additional mailbox role, and it installed without any problems. There was one other blog post found here that noted the particular error posted above, but the solution offered was different than mine. This error might have multiple solutions, but that post’s proposed solution did not work for me.
If you have anything to add, please leave it in the comments. Hope this helps!








Hi. I found that Federated EMail User, but in my root domain is no exchange, so that user have not those attributes to edit like homeMDB. And now?
I had the same issue with the same apparent cause (manual removal of Exchange), and this fix worked for me. Thank you!
That worked for me. Thanks!
Thanks very much. Same problem when upgrading Exchange 2010 to SP1-beta. I had the empty homeMDB on three of the special guid-labelled mailboxes. All working now.
cheers
Thank you very much you saved me alot of agony and pain. After i did your solution it installed like a sham.
thanks for that. that helped me out while moving the arbitration mailboxes to another database.
I was running into a similar problem as a previous admin had messed up an exchange sp1 install.
In my case it wasn’t the federated mailbox but the discovery mailbox. A quick check of the setup log will show you exactly which mailbox your failing on.
[WARNING] The object domain.local/Users/DiscoverySearchMailbox {D919BA05-46A6-415f-80AD-7E09334BB852} has been corrupted, and it’s in an inconsistent state. The following validation errors happened:
[11/29/2010 15:02:07.0855] [2] [WARNING] Database is mandatory on UserMailbox.
[11/29/2010 15:02:07.0855] [2] [WARNING] The property value you specified, “16″, isn’t defined in the Enum type “Nullable`1″.
[11/29/2010 15:02:07.0855] [2] [WARNING] Database is mandatory on UserMailbox.
Thank you very much for this, it saved our bacon when Hub transport refused to install.
Thank you
Rob
Yes thank you very much for this. For us it was also the DiscoverySearchMailbox that caused the problem. Updated the homeMDB attribute and ran the SP1 installer again and it worked!
MOST EXCELLENT!