Delta Imports from IDB on LDAP Groups Consistently Fail with Sequence contains more than one element error.

Richard Green 9 years ago updated by anonymous 9 years ago 2

Hi Gents,

Interesting one - we're consistently seeing the below error while running delta imports from IDB into FIM, on the LDAP Groups partition.

 "System.InvalidOperationException: Sequence contains more than one element
   at System.Linq.Enumerable.Single[TSource](IEnumerable`1 source)
   at Unify.Product.IdentityBroker.ImportProxy.ChangesToAttributeChange(ObjectModificationType modType, IGrouping`2 changes, AttributeType desiredType)
   at System.Linq.Enumerable.WhereSelectArrayIterator`2.MoveNext()
   at Unify.Product.IdentityBroker.ExtensionMethods.Visit[TSource](IEnumerable`1 source, Action`1 visitor)
   at Unify.Product.IdentityBroker.ImportProxy.EntryToDeltas(SearchResultEntry searchEntry)
   at System.Linq.Enumerable.<SelectManyIterator>d__14`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__0`1.MoveNext()
   at Unify.Product.IdentityBroker.ImportProxy.Import(GetImportEntriesRunStep importRunStep)
Forefront Identity Manager 4.1.3646.0"

Note this is the same error noted in UNINWCSTL-1, however this is not a DN issue.

Nothing is noted in the IDB logs around this, although I have attached a Diagnostic log taken while this occurred.

In investigating, i noted that initially the delta's seemed to be working fine, and then started failing from a specific point - notably 2nd Oct, 2:05 am.

I looked at the IDB ChangeLog table for changes on this adapter around this time, abd found some interesting entries:

ChangeLogKey, AdapterId, ChangeType, ChangeTimestamp, TargetDistinguishedName, NewDistinguishedName, Changes
1868584, 65F663DB-076A-4630-92C2-6FE82BD5FE95, 2, 2015-10-01 16:14:14.1352367, UID=e5453054-7ba4-460b-8222-a0cc83dc0cca,OU=LDAPGroups,DC=IdentityBroker, NULL, LDAPGroupObjectClass:-;LDAPGroupCn:-;LDAPGroupGidNumber:-;LDAPGroupObjectDN:-;LDAPGroupDescription:-
1868610, 65F663DB-076A-4630-92C2-6FE82BD5FE95, 3, 2015-10-02 01:20:09.8420583, UID=b3ac6d1e-025c-46cb-ab31-56d3169af7dc,OU=LDAPGroups,DC=IdentityBroker, NULL, memberUid:+ c1234580
1868611, 65F663DB-076A-4630-92C2-6FE82BD5FE95, 3, 2015-10-02 01:20:09.8420583, UID=243a5553-04c1-4eec-92f6-dab5b2f7a9d5,OU=LDAPGroups,DC=IdentityBroker, NULL, memberUid:+ c1234580
1888631, 65F663DB-076A-4630-92C2-6FE82BD5FE95, 2, 2015-10-02 16:14:45.9843075, UID=e8fbc6c2-3b28-42e7-8943-a148a8351af2,OU=LDAPGroups,DC=IdentityBroker, NULL, LDAPGroupObjectClass:-;LDAPGroupCn:-;LDAPGroupGidNumber:-;LDAPGroupObjectDN:-;LDAPGroupDescription:-

I sampled around either side, but if you note the 2 entries in the middle are both just before the delta's started failing, and are adding a value to a multivalue field. This seems consistent with the error text aswell.

I've attached full config aswell, let me know if more is provided.


Hi Richard Green,

I wasn't able to reproduce this so I have attached Unify.IdentityBroker.FIMAgent.dll which will generate a different error message to help diagnose the issue. Please add the file to %FIM Install Directory%\2010\Synchronization Service\Extensions and try rerunning the import, and let me know what the message comes up as.

As per our discussion, the fix for this issue was included in Identity Broker for FIM v5.0.2, but the DLL in the FIM installation directory was still on v5.0.1.