SystemMailbox{de67fac6-3df7-4c84-ad6b-907ac40cd533}@domain.com. Messages to this recipient will be deferred until the configuration is corrected in Active Directory.

MSExchange Transport
Event ID 9217

Not sure how this happened just started getting this error message. Would like to resolve it before it starts causing issues.
Bull174Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

jrhelgesonCommented:
Whoa - if this just started, then that would mean the configuration used to exist in Active Directory and was deleted, or has gone missing due to AD corruption issues.  Let's hope they were just deleted.

Those objects are created when you prepare the Active Directory environment for the installation of Exchange Server. They can be re-created by rerunning the "setup /prepareAD" option and related options.

The steps required are detailed here:
http://careexchange.in/how-to-recreate-system-mailbox-federatedemail-discoverysearchmailbox-in-exchange-2010/
0
Bull174Author Commented:
I thought so! So will this require a reboot also I do this on my 2 CAS/HUB servers or just one?
0
jrhelgesonCommented:
No, you delete the offending object from Active Directory Users & Computers, it's in the users container.
Prior to doing that, run the following command from any one of your exchange servers PowerShell:
"Get-mailbox -arbitration"

That command may return an error for the offending mailbox.  It did on mine.

Have the Exchange 2010 SP3 setup files downloaded & extracted to the domain controller.

1) Delete the SystemMailbox from AD Users & Computers  / user container, then
2) Open command prompt,  change to the Exchange 2010 SP3 setup files folder and run the "Setup /p" command.  This will re-create the SystemMailbox account that you just deleted.
3) From the Exchange Server PowerShell (doesn't matter which server), run the following command:
     Enable-Mailbox -arbitration "SystemMailbox{de67fac6-3df7-4c84-ad6b-907ac40cd533}"
4) Then run the command again: "Get-mailbox -arbitration" and see the results.
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

Bull174Author Commented:
When I use that command I get 3 mailboxes


[PS] C:\Scritps>Get-mailbox -arbitration

Name                      Alias                ServerName       ProhibitSendQuota
----                      -----                ----------       -----------------
SystemMailbox{1f05a927... SystemMailbox{1f0... 815-mbx-31       unlimited
FederatedEmail.4c1f4d8... FederatedEmail.4c... 815-mbx-31       1 MB (1,048,576 bytes)
SystemMailbox{e0dc1c29... SystemMailbox{e0d... 815-mbx-31       unlimited


I don't see anything that shows these are the same
0
Bull174Author Commented:
I ran this command and found that it has two mailboxes with the same account

get-mailbox "systemmailbox*" -arbitration | fl database,Identity,SAMaccountname

Results
Database       : UDB2
Identity       : domain.com/Users/SystemMailbox{1f05a927-3ae0-4379-b4bf-3507c152ac34}
SamAccountName : SM_c36c2b892fb54c35a

Database       : UDB2
Identity       : domain.com/Users/SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9}
SamAccountName : SM_d8f7b5afc2d3478da
0
jrhelgesonCommented:
Where are you getting/seeing the message that is provided in the title:
SystemMailbox{de67fac6-3df7-4c84-ad6b-907ac40cd533}@domain.com. Messages to this recipient will be deferred until the configuration is corrected in Active Directory.
0
Bull174Author Commented:
only on one of my CAS/HUB servers
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
jrhelgesonCommented:
How did you fix the problem then? Was it by changing the record in Active Directory LDAP?  The article you referenced is not very clear.

Deleting/recreating the mailbox is the preferred method to solved it as it will update all the pointers to that specific SystemMailbox record.
0
Bull174Author Commented:
I deleted the two mailboxes that had the label CNF at the end of them and waiting a hour as the error has been occuring every hour. No error messages.
0
Bull174Author Commented:
This points out where the duplicate is. CNF is the duplicate that is causing the error.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.

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.