0
Answered

Offset and length were out of bounds for the array or count is greater than the number of elements from index to the end of the source collection.

Carol Wapshere 1 year ago • updated by anonymous 1 year ago 4

I'm trying to understand what it error means - I'm seeing this error logged a number of times a day in the IdB logs but having trouble pinning it to a specific connector.

Sometimes the line in the log is this:

20170924,02:35:24,UNIFY Identity
Broker,LDAP engine,Error,"Handling of LDAP schema request. Handling of LDAP schema request
from user IdBLDAP on connection 127.0.0.1:58252 for the server schema failed
with error ""Offset and length were out of bounds for the array or
count is greater than the number of elements from index to the end of the
source collection."". Duration: 00:00:06.0373233.",Normal


Sometimes it's this:

20170924,12:14:56,UNIFY Identity
Broker,LDAP Engine,Error,"An error occurred on client from
127.0.0.1:60790. More details:
Internal Server Error #11:
System.ArgumentException: Offset and length were out of bounds for the array or
count is greater than the number of elements from index to the end of the
source collection.
   at
System.Array.Reverse(Array array, Int32 index, Int32 length)
   at System.Collections.Generic.Stack`1.System.Collections.ICollection.CopyTo(Array
array, Int32 arrayIndex)
   at
Unify.Framework.Collections.CallContextScope`1.get_CurrentScope()
   at
Unify.Framework.Auditing.AuditTrailScope.Dispose()
   at
Unify.Product.IdentityBroker.RequestHandlerAuditingDecorator.TryRetrieveHandlerReport(IDictionary`2&
handlerReports)
   at
Unify.Product.IdentityBroker.LDAPConnection.<RespondToMessageAsync>d__35.MoveNext()",Normal


Things seem to be working fine, however these errors are showing up in monitoring so I'd like to either eradicate the error, or filter it out somehow if it's of no concern.



Affected Versions:
Fixed by Version:

Answer

Answer
Answered

Closed due to no author response

Under review

Hi Carol

What version of IdB are you seeing this in? Can you provide your extensibility configuration?

Thanks Beau. Waiting on change control to get it deployed.

Answer
Answered

Closed due to no author response

The patch was installed last week and I haven't seen the error since.