9 พฤษภาคม 2555 9:50
I am getting the below error for few of the user accounts(most of them are diprovisioned user accounts i.e. moved to deprovisioned OU in the AD) while the Export Run of the Quest Management Agent. Couldn't figure out why this error is coming. Any help will be much appreciated. Export run becomes very slow due to this error:
Event Type: Error
Event Source: MIIServer
Event Category: Server
Event ID: 6801
Time: 4:09:32 AM
The extensible extension returned an unsupported error in MIIS.
The stack trace is:
"Microsoft.MetadirectoryServices.ExtensibleExtensionException: Cannot modify object "<GUID=bafdc932-0995-4440-a89f-5b1f90f7e8f8>": Administrative Policy returned an error.
Value cannot be null.
Parameter name: request DN
at QuickConnect.ManagementAgent.ARSFileExport.ModifyEntry(String changedAttributes, CSEntry csentry)
at QuickConnect.ManagementAgent.ARSFileExport.ExportEntry(ModificationType modificationType, String changedAttributes, CSEntry csentry)
Microsoft Identity Integration Server 3.2.1008.0"
25 พฤษภาคม 2555 15:14Hard to tell, this error message is coming from a custom management agent implementation, it the DN attribute or the Request DN attribute available within the connector space, and available to connectors that don't have this error? are they occurring with deleted connectors?
Need realtime FIM synchronization and advanced reporting? check out the new http://www.imsequencer.com that supports FIM 2010, Omada Identity Manager, SQL, File, AD or Powershell real time synchronization!
6 สิงหาคม 2555 13:54
Sorry, I didn't opened the technet portal, as I didn't receive a reply to my post for a long time.
Answer to your questions are as below:
1. Yes the DN value is present in the connector space for the problematic IDs and also for the normal IDs which don't have this error.
2. Yes the error is occuring with the deleted connectors, which means the IDs which are permanently deleted from our corporate AD, the error is particularly coming for those IDs only.
13 สิงหาคม 2555 19:30
Could you switch on logging on the export run profile for your Quest MA? The log file should give you some clues.
Also, could you verify that the object for which are getting your error still exists in the AD?
Paul Loonen (Avanade) | MCM: Directory 2008 | MVP: FIM2010