0
Answered

Extended Database Connector has "stopped-extension-dll-expection" occur till full import is run

Tom Parker 2 years ago • updated by anonymous 2 years ago 11

Occasionally delta import to MIM will fail with the “stopped-extension-dll-expection” error. When the error occurs, it will continue over and over until a full import is run.

Event viewer logs:

The extensible extension returned an unsupported error.
 The stack trace is:
 
 "Unify.Product.IdentityBroker.LdapOperationException: Error during processing of SearchRequest targetting cn=changelog: Operation timed out while waiting for message queue with id of 10. ---> System.OperationCanceledException: Operation timed out while waiting for message queue with id of 10.
   at Unify.Product.IdentityBroker.LdapConnection.GetMessage(Int32 messageId)
   at Unify.Product.IdentityBroker.SearchRequest.Send(Func`2 send, Func`2 recv)
   at Unify.Product.IdentityBroker.LdapConnection.SendRequest(ILdapRequest request)
   --- End of inner exception stack trace ---
   at Unify.Product.IdentityBroker.LdapConnection.SendRequest(ILdapRequest request)
   at Unify.Product.IdentityBroker.LdapConnectionProxy.<SearchRequestPaged>d__8.MoveNext()
   at Unify.Product.IdentityBroker.ImportProxy.<GetChangedEntriesPaged>d__30.MoveNext()
   at System.Linq.Enumerable.<SelectManyIterator>d__14`2.MoveNext()
   at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext()
   at System.Linq.Enumerable.<SelectManyIterator>d__14`2.MoveNext()
   at Unify.Product.IdentityBroker.ExtensionMethods.Take[TSource](IEnumerator`1 source, Int32 count, IList`1& items)
   at Unify.Product.IdentityBroker.ExtensionMethods.<Page>d__3`1.MoveNext()
   at Unify.Product.IdentityBroker.ImportProxy.Import(GetImportEntriesRunStep importRunStep)


Environment:

  • Identity Broker v5.1.0 Revision #0
  • MIM 4.3.2266.0


Affected Versions:
Fixed by Version:

Note: the usual run time of a delta import on this MA is a few seconds, when erroring in this way it takes around 30 minutes to complete with no changes.

When the full import runs, what is the volume of changes that it usually brings in?

Has the full import ever failed with the same error?

Does the MA import the entryUUID field?

Can you please also provide the Operation Timeout configuration from the relevant Run Step.

Timeout (seconds): 120

Operation timeout (s): 600

  1. The full import for this one brought in 49 adds and 136 updates which is pretty standard. There's a scheduled full import every morning after the target data source has it's own full import data refresh.
  2. The full import always succeeds.
  3. Yes it does import the entryUUID field.

Thanks. Are there any additional DLL patches? Is the entryUUID used as part of any mapping or provisioning logic - if not would it be possible to remove it from the imported attribute list and see if the issue persists?

I'll try to get some load testing going in a non-prod environment. If we can get the issue to consistently appear there we'll remove the entryUUID and see if that fixes anything.

Under review

Hi Tom,

Could you please state the Identity Broker and Identity Broker for Microsoft Identity Manager version numbers?

  • Identity Broker v5.1.0 Revision #0
  • MIM 4.3.2266.0
I'll try to get some load testing going in a non-prod environment. If we can get the issue to consistently appear there we'll remove the entryUUID and see if that fixes anything.

Hi Tom, is there an update? Thanks.