The access control entry defines the ObjectType {9b026da6-0d3c-465c-8bee-5199d7165cba} that can’t be resolved tab mailbox delegation on Exchange 2016

Question

_{Friday, December 15, 2017 9:30 AM}

Dear MS Support
I have a Mail Exchange 2016 CU3 on Windows server 2012R2 running on an Active Directory Domain 2008 environment.
December 13, 2017 I have build more Active directory Windows Server 2016.
After when build DC 2016, access to Exchange Admin click on the mailbox tab mailbox delegation object error

  Warning
The object abc.local / JSC / 01.Head Office / IT / Users / Phuong, Nguyen Van has been corrupt or is not compatible with Microsoft support requirements, and it's in an inconsistent state. The following validation errors occurred:
The access control entry defines the ObjectType '9b026da6-0d3c-465c-8bee-5199d7165cba' that can not be resolved ..

Please help me method to resole this error handling
This is a bug or just a warning from Exchange 2016
Thanks

All replies (5)

_{Monday, December 18, 2017 5:51 AM ✅Answered | 2 votes}

Hi,

Based on your description, I know that you will get the error above if you click on mailbox delegation tab after building another DC 2016.

Any misunderstandings, be free to post back!

Per my experience, if we expand AD schema from 2012 R2 to 2016, we may get this issue, and the solution is to run IISRESET.

Hope it helps.

Regards,

Manu Meng

Please remember to mark the replies as answers if they helped.
If you have feedback for TechNet Subscriber Support, contact [email protected].

_{Saturday, December 23, 2017 1:04 PM}

Dear Manu Meng,

Althought  expand AD schema from 2012 R2 to 2016. 

Currently, the forest level function is 2008 and Domain level function 2008.
I only build one Active Directory Additional 2016 and after day I demote DC 2008 and migration 2008 to 2016

Afer I reboot my Exchange 2016 my error is resolve.

After I check again AD 2016 DC tab

At the properties tab security of the domain of the DC server => There are several User Unknown SID-1-5-21-104 xx

My question is the SID account-unknown-- what effect does it have with my Server Exchange 2016.

Please for me advise

Thanks

_{Saturday, March 9, 2019 10:02 PM}

I am getting this same error after introducing our first 2016 Domain Controller at one of our sites. Now when I try to edit a Distribution Group within that site, I get the error. I've rebooted my Exchange servers. Message still persists. How do I fix this? Very annoying.

Thanks, Jeremy

_{Monday, March 25, 2019 9:29 AM | 5 votes}

Thanks alot, we had the same issue after Schema Update from 2008R2 to 2016 with out Exchange 2013 DAG.

Recycling the "MSExchangeECPAppPool" worked as well. I just want to let you know, so you dont have to kill all your client sessions by resetting iis. maybe this works for somebody else.

thanks again

_{Wednesday, May 29, 2019 11:42 PM}

Had the same issue after schema update also. Recycling the app pool worked perfectly.