Note that this FIM installation does not have the portal available, so everything needs to be handled via code and/or the synchronization manager
I am in the process of developing and setting up a new MA for provisioning users to an external system. I wish to use a local SQL database for storing the connector space data, and I've set it up so that the schema is determined from the structure of the database tables and their columns. I have defined one column "recordId" to serve as anchor and configured it as such in the MA configuration in the synchronization manager.
We have set up an extension for handling provisioning etc within the metaverse, and I have added my MA there. However, when I try to do synchronization, I get error messages about:
System.InvalidOperationException: The DN must be set before calling CSEntry.CommitNewConnector.
at Microsoft.MetadirectoryServices.Impl.ConnectorImpl.Commit()
at Mms_Metaverse.MVExtensionObject.Microsoft.MetadirectoryServices.IMVSynchronization.Provision(MVEntry mventry) in c:\FIM\Solutions\MVExtension\MVExtension.cs:line 344
If I try to set the DN explicitly with CSEntry.DN before calling CSEntry.CommitNewConnector(), I get error messages about:
"Object <DN-value> doesn't have a parent object in management agent <MA>"
This makes me wonder if I need to do some kind of initialization of the connector space or something special when I start using this new MA for the first time in this FIM implementation, or perhaps there is something else entirely. And and all advice on how to get this sorted out is welcome!