0
Answered

LDAP bulk update request postponed

Eddie Kirkman 6 years ago updated 6 years ago 4

In a customer DEV environment I am exporting some users from MIM and get an 

ma-extension-error

0x80230703

unexpected-error reported for all of them by MIM

The eventvwr error is

The management agent controller encountered an unexpected error.
 
 "BAIL: MMS(9724): extensionmanager.cpp(620): 0x80230703 (unable to get error text)
BAIL: MMS(9724): extensionmanager.cpp(2648): 0x80230703 (unable to get error text)
BAIL: MMS(9724): export.cpp(2150): 0x80230703 (unable to get error text)
BAIL: MMS(9724): export.cpp(521): 0x80230703 (unable to get error text)
BAIL: MMS(9724): ..\cntrler.cpp(9848): 0x80230703 (unable to get error text)
BAIL: MMS(9724): ..\cntrler.cpp(8569): 0x80230703 (unable to get error text)
Forefront Identity Manager 4.3.2124.0"

and IdB shows this in the log


05/Nov/2018 16:35:00
  • Information
LDAP EngineA client has connected to the LDAP endpoint from address: 127.0.0.1:59560.
05/Nov/2018 16:35:00
  • Information
LDAP engineHandling of LDAP bind request.
Handling of LDAP bind request received on connection 127.0.0.1:59560 to connect as user admin completed successfully. The bind was successful. Duration: 00:00:00.0937243.
05/Nov/2018 16:35:02
  • Information
LDAP engineHandling of LDAP Bulk Start request.
Handling of LDAP Bulk Start request received from user admin on connection 127.0.0.1:59560 completed successfully. Duration 00:00:00.0010018.
05/Nov/2018 16:35:03
  • Information
LDAP engineHandling of LDAP Bulk Update request.
Handling of LDAP Bulk Update request received from user admin on connection 127.0.0.1:59560 was postponed as it was not the next expected bulk request. This request will be handled as part of a future request. Duration 00:00:00.5950385.
05/Nov/2018 16:36:22
  • Information
LDAP engineHandling of LDAP unbind request.
Handling of LDAP unbind request received on connection 127.0.0.1:59560 to connect as user admin completed successfully. Duration: 00:00:00.


None of these error messages really tell me what is going on.  Any idea what the "postponed as it was not the next expected bulk request." thing is all about?

Answer

Answer
Answered

As you use the UniqueIdentifier field in the DN template, which is a required field on the connector, that field needs to be included in the export (which I can see in the trace was not included).

GOOD, I'M SATISFIED

thanks for the pointers

Satisfaction mark by Eddie Kirkman 6 years ago
Under review

Thanks for the information Eddie.

The "postponed as it was not the next expected bulk request" message means that a bulk page was received with an out of order id (they should count up from 1). It shouldn't really come up though.

Is the failure happening consistently? Are you able to get a rawcap of the failure?

Thanks.

yes.

IdB log:

12/Nov/2018 13:57:06
  • Information
LDAP EngineA client has connected to the LDAP endpoint from address: 127.0.0.1:50130.
12/Nov/2018 13:57:06
  • Information
LDAP engineHandling of LDAP bind request.
Handling of LDAP bind request received on connection 127.0.0.1:50130 to connect as user admin completed successfully. The bind was successful. Duration: 00:00:00.1093515.
12/Nov/2018 13:57:08
  • Information
LDAP engineHandling of LDAP Bulk Start request.
Handling of LDAP Bulk Start request received from user admin on connection 127.0.0.1:50130 completed successfully. Duration 00:00:00.
12/Nov/2018 13:57:09
  • Information
LDAP engineHandling of LDAP Bulk Update request.
Handling of LDAP Bulk Update request received from user admin on connection 127.0.0.1:50130 was postponed as it was not the next expected bulk request. This request will be handled as part of a future request. Duration 00:00:00.2499774.
12/Nov/2018 13:58:28
  • Information
LDAP engineHandling of LDAP unbind request.
Handling of LDAP unbind request received on connection 127.0.0.1:50130 to connect as user admin completed successfully. Duration: 00:00:00.

error 6801 in eventvwr:

The extensible extension returned an unsupported error.
 The stack trace is:
 
 "Unify.Product.IdentityBroker.LdapOperationException: Error during processing of BulkUpdateRequest targetting : Operation timed out.
   at Unify.Product.IdentityBroker.LdapConnection.SendRequest(ILdapRequest request)
   at Unify.Product.IdentityBroker.ExportProxy.GetBulkRequestResult(BulkUpdateRequest request)
   at Unify.Product.IdentityBroker.ExportProxy.BulkExportEntries(IList`1 csentries)
   at Unify.Product.IdentityBroker.ExportProxy.Export(IList`1 csentries)
   at Unify.Product.IdentityBroker.UnifyLdapConnector.PutExportEntries(IList`1 csentries)
Forefront Identity Manager 4.3.2124.0"

followed by 6401

The management agent controller encountered an unexpected error.
 
 "BAIL: MMS(6056): extensionmanager.cpp(620): 0x80230703 (unable to get error text)
BAIL: MMS(6056): extensionmanager.cpp(2648): 0x80230703 (unable to get error text)
BAIL: MMS(6056): export.cpp(2150): 0x80230703 (unable to get error text)
BAIL: MMS(6056): export.cpp(521): 0x80230703 (unable to get error text)
BAIL: MMS(6056): ..\cntrler.cpp(9848): 0x80230703 (unable to get error text)
BAIL: MMS(6056): ..\cntrler.cpp(8569): 0x80230703 (unable to get error text)
Forefront Identity Manager 4.3.2124.0"

MIM error: Capture.JPG

Answer
Answered

As you use the UniqueIdentifier field in the DN template, which is a required field on the connector, that field needs to be included in the export (which I can see in the trace was not included).

Thanks - it turns out that the DEV environment is completely different to PROD and is missing a number of attributes in the flow, which is a little disappointing but not a complete surprise