I am getting the following error on one of my MAs. Can you please give me advice on how to correct? Microsoft.MetadirectoryServices.UnexpectedDataException: Unhandled object type in DetermineMVDeletion called with csentry CS GAL_AKLC msExchDynamicDistributionList distinguishedName and mventry MV group 84a92dcc-c693-41cc-8e69-1f4feec6509b at Microsoft.MetadirectoryServices.GALSync.MVSynchronizer.DetermineMVDeletion(CSEntry csentry, MVEntry mventry) Thanks Peter Thompson

Perhaps your issue can be solved with http://support.microsoft.com/kb/2028634/ Fixed issues in Sync Engine ... Issue 8 GALSync cannot recognize the new Exchange Dynamic Distribution List type.http://setspn.blogspot.com

Thanks for that. It was indeed a Dynamic Distribution List that caused the problem originally. I will install the update as suggested. Unfortunately I do not think that this will fix this issue as I have removed the DLs from syncing and am still getting the above. Peter

Thanks for that. It was indeed a Dynamic Distribution List that caused the problem originally. I will install the update as suggested. Unfortunately I do not think that this will fix this issue as I have removed the DLs from syncing and am still getting the above. Peter

How did you removed them from syncing? If you alter the scope of the MA, or move the DL's out of the scope of the MA, you'll probably need a full import and sync to confirm this.http://setspn.blogspot.com

How did you removed them from syncing? If you alter the scope of the MA, or move the DL's out of the scope of the MA, you'll probably need a full import and sync to confirm this.http://setspn.blogspot.com

They were just hidden from the address book. I have run w Full import without joy.

They were just hidden from the address book. I have run w Full import without joy.

You might wanna double check in the filter definitions on the GAL MA whether this object type is filtered when hidefromaddresslist==true. Or whether this is determined in the code (rules extension). Besides that, I don't think because you hide the list from the addressbook that FIM will immediately ignore this object. It might have gotten stuck in some situation from the initial runs...http://setspn.blogspot.com

You might wanna double check in the filter definitions on the GAL MA whether this object type is filtered when hidefromaddresslist==true. Or whether this is determined in the code (rules extension). Besides that, I don't think because you hide the list from the addressbook that FIM will immediately ignore this object. It might have gotten stuck in some situation from the initial runs...http://setspn.blogspot.com

Hide from addressbook definitely filters. Unfortunately the sync had started before I hid. I think the only option is to remove this from the metaverse but am unsure how to do this.

Hide from addressbook definitely filters. Unfortunately the sync had started before I hid. I think the only option is to remove this from the metaverse but am unsure how to do this.

It seems that if you leave this long enough it is finally purged. The problem has finally gone away all by itself :)

It seems that if you leave this long enough it is finally purged. The problem has finally gone away all by itself :)

It seems that if you leave this long enough it is finally purged. The problem has finally gone away all by itself :)