|
Troubleshooting the Microsoft.MetadirectoryServices.NoCompatiblePartitionFoundException Error |
|
|
I’ve been re-acquainting myself with ILM of late and hit a couple of errors that had me stumped from anywhere between a couple of minutes and four hours! So, I thought I’d provide some brief information on the error and the reason I encountered it. I’ll post each error as a separate blog post to keep the entry concise and for search-engine reasons. The first error I hit was Microsoft.MetadirectoryServices.NoCompatiblePartitionFoundException. In my case, the stack trace looked like this:
Microsoft.MetadirectoryServices.NoCompatiblePartitionFoundException: The partition filter criteria for management
agent "ad-lds" do not include an object with DN "cn=Burt Reynolds,dc=msresource,dc=net" and object classes user.
at Microsoft.MetadirectoryServices.Impl.CSEntryImpl.CommitNewConnector()
at Mms_Metaverse.MVExtensionObject.Provision(MVEntry mventry) in C:\Documents and Settings\MIIS
Rules Extensions\paulw-mv-extension.dll\paulw-mv-extension.dll.vb:line 34
This error was because I was trying to provision a user into the AD-LDS connector space but the AD-LDS MA wasn’t configured to use the user class as a valid object type (MA | Properties | Object Types). Changing the code to create an inetOrgPerson object instead (as we wanted to create inetOrgPerson objects as opposed to user objects) resolved this as the MA was configured, as per design, to use inetOrgPerson objects.
Troubleshooting this error indicates that other possible causes are: invalid DN or parent container that isn’t within scope of the MA (MA | Properties | Configure Directory Partitions). |
