Hi,
This post is a followup to an older thread that I had about flowing an empty value and then deleting an attribute in a target LDAP that I posted awhile ago (https://social.technet.microsoft.com/Forums/en-US/868caa9d-aabd-45f2-b63f-a83c5b724e0c/solved-kind-of-can-the-openldap-ma-deleteempty-an-attribute-from-an-existing-user-in-the-ldap?forum=ilm2#9fb06dfb-b291-4469-8005-ed717e51646c).
To sum up that old thread, we had a problem with a scenario where we were trying to flow an empty value coming from a flatfile MA into, eventually, a target LDAP. In that thread, I *THOUGHT* that I had found how to get that working, but per that
thread, I had been testing in my test environment with an AD MA going into an AD LDAP.
However, in our actual/production environment, the LDAP is an Oracle OUD LDAP instance, and we use the OpenLDAP MA as the connector, and, it looks like, while I was able to figure out how to delete the attribute in my test environment (which, again, uses
AD as the LDAP and the FIM AD connector), that same approach doesn't seem to work when the target LDAP is an Oracle OUD and the OpenLDAP MA is used :(!!
With the OUD and OpenLDAP MA, everything during the processing SEEMS to work in FIM, to the point that the attribute-to-be-deleted is appearing in the FIM connector space as being marked as "Deleted", HOWEVER, when we run the final run profile
to do the EXPORT, it is failing to write to the OUD.
If I use a profile with only an EXPORT step, I am getting an "unexpected-error" and in the Event Viewer, I am seeing:
The management agent controller encountered an unexpected error.
Log Name: Application
Source: FIMSynchronizationService
Date: 9/13/2019 6:08:56 AM
Event ID: 6401
Task Category: Server
Level: Error
Keywords: Classic
User: N/A
Computer: FIM01.gxaws.com
Description:
The management agent controller encountered an unexpected error.
"BAIL: MMS(4688): d:\bt\800\private\source\miis\cntrler\cntrler.cpp(12278): 0x80004001 (Not implemented)
BAIL: MMS(4688): d:\bt\800\private\source\miis\cntrler\cntrler.cpp(9315): 0x80004001 (Not implemented)
BAIL: MMS(4688): d:\bt\800\private\source\miis\cntrler\cntrler.cpp(8091): 0x80004001 (Not implemented)
Forefront Identity Manager 4.1.3419.0"
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="FIMSynchronizationService" />
<EventID Qualifiers="49152">6401</EventID>
<Level>2</Level>
<Task>3</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2019-09-13T06:08:56.000000000Z" />
<EventRecordID>75205</EventRecordID>
<Channel>Application</Channel>
<Computer>FIM01.gxaws.com</Computer>
<Security />
</System>
<EventData>
<Data>BAIL: MMS(4688): d:\bt\800\private\source\miis\cntrler\cntrler.cpp(12278): 0x80004001 (Not implemented)
BAIL: MMS(4688): d:\bt\800\private\source\miis\cntrler\cntrler.cpp(9315): 0x80004001 (Not implemented)
BAIL: MMS(4688): d:\bt\800\private\source\miis\cntrler\cntrler.cpp(8091): 0x80004001 (Not implemented)
Forefront Identity Manager 4.1.3419.0</Data>
</EventData>
</Event>
I've re-tested the same flows in my test environment (which again, uses AD
and AD connector) and it works fine, so it appears that the problem is with the OpenLDAP connector or with OUD LDAP.
Has any
one seen this problem and know how to fix/work around this problem?
Thanks!
Jim