1. UNIFYBroker Forum
  2. Bugs
0
Fixed

Sequence contains more than one element

Hayden Gray 5 years ago • updated by Beau Harrison (Senior Product Software Engineer) 5 years ago • 4

Hi Guys,

Getting this error when trying to do DIDS operations in FIM. Issue started last night and all DI operaions appear to be failing now. I'm doing Full imports now as a work around for now.

Reading through a similar ticket I stumbled across this one Richard had raise quite a while ago:
https://voice.unifysolutions.net/communities/6/topics/474-delta-imports-from-idb-on-ldap-groups-consistently-fail-with-sequence-contains-more-than-one

The comments on this ticket say that this was resolved in v5.0.2 however the version in this environment is v5.0.4. For some additional imformation the version of FIM is 4.1.3646.0.

The extensible extension returned an unsupported error.
The stack trace is:
"Unify.Product.IdentityBroker.LdapOperationException: Internal Server Error #11: System.InvalidOperationException: Sequence contains more than one element
at System.Data.Linq.SqlClient.SqlProvider.Execute(Expression query, QueryInfo queryInfo, IObjectReaderFactory factory, Object[] parentArgs, Object[] userArgs, ICompiledSubQuery[] subQueries, Object lastResult)
at System.Data.Linq.SqlClient.SqlProvider.ExecuteAll(Expression query, QueryInfo[] queryInfos, IObjectReaderFactory factory, Object[] userArguments, ICompiledSubQuery[] subQueries)
at System.Data.Linq.SqlClient.SqlProvider.System.Data.Linq.Provider.IProvider.Execute(Expression query)
at System.Data.Linq.Table`1.System.Linq.IQueryProvider.Execute[TResult](Expression expression)
at Unify.Framework.Data.LinqQueryConversionProvider`5.ExecuteMethodCallExpression[TResult](MethodCallExpression methodCallExpression)
at Unify.Framework.Data.LinqQueryConversionProvider`5.Execute[TResult](Expression expression)
at System.Linq.Queryable.SingleOrDefault[TSource](IQueryable`1 source, Expression`1 predicate)
at Unify.Product.IdentityBroker.ChangeLogToLDAPEntryConverter.EntryUuidAttributeValue(IChangeLogItem sourceValue, IDictionary`2 partialAttributes)
at Unify.Product.IdentityBroker.ChangeLogToLDAPEntryConverter.Transform(IChangeLogItem sourceValue)
at Unify.Product.IdentityBroker.SearchRequestHandlerBase.d__13.MoveNext()
at Unify.Framework.Visitor.Visit[T](IEnumerable`1 visitCollection, Action`2 visitor)
at Unify.Product.IdentityBroker.LDAPConnection.d__33.MoveNext()
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)
at Unify.Product.IdentityBroker.LdapConnectionProxy.PartitionDeltaRequestPaged(String partitionDN, Int64 lastChangeNumber, Int32 pageSize)
at System.Linq.Enumerable.d__14`2.MoveNext()
at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext()
at System.Linq.Enumerable.d__14`2.MoveNext()
at Unify.Product.IdentityBroker.ExtensionMethods.Take[TSource](IEnumerator`1 source, Int32 count, IList`1& items)
at Unify.Product.IdentityBroker.ExtensionMethods.d__0`1.MoveNext()
at Unify.Product.IdentityBroker.ImportProxy.Import(GetImportEntriesRunStep importRunStep)
Forefront Identity Manager 4.1.3646.0"

This is current a high priority ticket so any help is greatly appreciated.

Thanks,

Hayden

Under review
Beau Harrison (Senior Product Software Engineer) 5 years ago

Hi Hayden,

To confirm, you are using v5.0.4 of Identity Broker for FIM not Broker itself? Check the dll in the FIM installation, not just the "installed" version as reported by Windows.

Can you check the ChangeLog table for any entries similar to what Richard found in his?

Hayden Gray 5 years ago

Hi Beau,

Is this the file you are referring to?


No worries I'll hit Richard up to see how he troubleshooted the change log, I'll update you further with what I find.

Thanks,

hayden

Beau Harrison (Senior Product Software Engineer) 5 years ago

Can you check the entities in the adapter the failure occurs on for duplicate DNs?

Fixed
Beau Harrison (Senior Product Software Engineer) 5 years ago

Caused by multiple adapter entities with the same DN existing. Improved handling for situations that result in duplicate DNs in adapter space are available from v5.3 onwards.

Customer support service by UserEcho