Exchange 2013 Database Is Mandatory on Usermailbox
- Home
- Collaboration
- Microsoft Exchange
I had to make an emergency migration from one exchange server to another. Both are exchange 2016. I thought everything was working just fine. Mail flows in both directions. No errors. Until I tried adding a new account. That's when I get this stupid error. Every single mailbox gives this error. When I select edit on a mailbox, I get that error. When I run " Get-Mailbox -Arbitration | ft Name, ServerName, Database -Auto", I don't get the info the Microsoft docs say I shoulWhat is going on?
- ROM
- CPU
- RAM
- GPU
49 Replies
Try the following:
Get-MailboxDatabase
Get-Mailbox -Database "Database name here" -Arbitration | ft Name,ServerName,Database -Auto
Sounds like a corrupt or missing attribute on the 'homeMDB' attribute.
Open the system mailboxes attributes in ADSIEdit and review the 'homeMDB' attribute.
-Jay
You won't find it in Exchange, you would find it in ADSIEdit.msc or in Active Directory under "users" with a name of 'systemmailbox.....'
Make sure advanced features is turned on in AD, then open the system mailbox properties in AD, go to the attribute editor tab, scroll down to the homeMDB attribute and see if it is populated.
-Jay
I have six and they look disabled.
Only one of them is missing that information. Should I copy the string from one of the others? Should I enable them?
Will I need to reboot or restart any services?
Shouldn't need to, but if that doesn't fix the issue, then the system mailboxes will need to be rebuilt from the Exchange installation media.
-Jay
Jay6111 wrote:
Shouldn't need to, but if that doesn't fix the issue, then the system mailboxes will need to be rebuilt from the Exchange installation media.
-Jay
That sucks. Will I lose any data? Is it a complete reinstall or is there an option to just rebuild the system mailboxes?
The data lost in those mailboxes is insignificant as they are corrupt right now anyway. Basically you delete the system mailboxes from AD and the federation, migration mailboxes as well. Should all be in the same location. Then open an elevated command prompt, change directories to the location where the Exchange media is located and then run the following.
Setup . exe / PrepareAD / IAcceptExchangeServerLicenseTerms
That will recreate the system mailboxes.
-Jay
I am getting the error on every single mailbox I select in the ECP. So will I lose every single mailbox and all the mail there?
Are you deleting their mailboxes? Then no.
It's a common thing, so much so, there is a TechNet on it.
https://technet.microsoft.com/en-us/library/gg588318(v=exchg.150).aspx
-Jay
Jay6111 wrote:
Are you deleting their mailboxes? Then no.
It's a common thing, so much so, there is a TechNet on it.
https://technet.microsoft.com/en-us/library/gg588318(v=exchg.150).aspx
-Jay
Ok. Just making sure. There would be a lot of unhappy people...
Jay6111 wrote:
The data lost in those mailboxes is insignificant as they are corrupt right now anyway. Basically you delete the system mailboxes from AD and the federation, migration mailboxes as well. Should all be in the same location. Then open an elevated command prompt, change directories to the location where the Exchange media is located and then run the following.
Setup . exe / PrepareAD / IAcceptExchangeServerLicenseTermsThat will recreate the system mailboxes.
-Jay
So I did that and now none of the system mailboxes have anything in homemdb.
You're not done yet.
Now open the Exchange management shell and run the following,
Get-User | Where { $_ . Name – like "SystemMailbox*" } | Enable-Mailbox -Arbitration Get-User | Where { $_ . Name – like "FederatedEmail*" } | Enable-Mailbox – Arbitration
Then change the name of the system mailbox to 'Microsoft Exchange' by running the following.
Get-Mailbox – Identity "SystemMailbox{e0dc1c29*" – Arbitration | Set-Mailbox – Arbitration – DisplayName "Microsoft Exchange"
Then set the quota limit on the federation mailbox by running the following,
Get-Mailbox – Arbitration – Identity "FederatedEmail*" } | Set-Mailbox – Arbitration – ProhibitSendQuota 1MB
Then test by running the get-mailbox -arbitration and see if they show up now.
-Jay
When I get to Get-Mailbox –Identity "SystemMailbox{e0dc1c29*" –Arbitration | Set-Mailbox –Arbitration –DisplayName "Microsoft Exchange" I get
The repair did not work then.
Open the properties of the system mailboxes in AD again, goto the attribute editor tab, scroll down to the homemdb attribute and open it.
This should have an attribute similar to
CN=<Database-Name>,CN=Databases,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrive Groups,CN=<YOUR DOMAIN>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<YOUR DOMAIN NAME>,DC=COM
-Jay
Jay6111 wrote:
The repair did not work then.
Open the properties of the system mailboxes in AD again, goto the attribute editor tab, scroll down to the homemdb attribute and open it.
This should have an attribute similar to
CN=<Database-Name>,CN=Databases,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrive Groups,CN=<YOUR DOMAIN>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<YOUR DOMAIN NAME>,DC=COM
-Jay
That is present in all the mailboxes now. Still getting that same error though.
The steps I gave you are basically following this TechNet.
https://technet.microsoft.com/en-us/library/gg588318(v=exchg.141).aspx
Beyond that, populating the homemdb attribute manually may fix it but if it doesn't then I suspect you have more issues in the environment.
-Jay
Try restarting the servers then. Not ideal, but about the only thing left I can think of.
-Jay
This topic has been locked by an administrator and is no longer open for commenting.
To continue this discussion, please ask a new question.
Exchange 2013 Database Is Mandatory on Usermailbox
Source: https://community.spiceworks.com/topic/2057005-database-is-mandatory-on-usermailbox-exchange-2016
0 Response to "Exchange 2013 Database Is Mandatory on Usermailbox"
Post a Comment