|
Troubleshooting the Microsoft.MetadirectoryServices.MissingParentObjectException 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 second error I hit was Microsoft.MetadirectoryServices.MissingParentObjectException. In my case the stack trace looked like this:
Microsoft.MetadirectoryServices.MissingParentObjectException: Object
"cn=Peter Griffin,ou=users,dc=msresource,dc=net" does not have a parent object in management agent "ad-lds".
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 occurred because the AD-LDS MA hadn’t been staged. To correct this error, create a new run profile for Full Import (Stage Only) and run this run profile. Running this run-profile will stage the existing container objects into the connector space so that future provisioning operations can use these containers as parents. |
