NDS error: insufficient buffer (-649) during LDIF import

(Last modified: 27Oct2003)

This document (10088140) is provided subject to the disclaimer at the end of this document.

fact

Novell LDAP v3

eDirectory 8.7x

eDirectory 8.6.x

symptom

NDS error: insufficient buffer (-649)

Console One ICE and command line ICE returns -649 error: insufficient buffer

Error received when LDAP filters are put on in DSTrace:

Searching "": NDS error:insufficient buffer (-649) returned
LDAPSearchToCB failed, err = insufficient buffer (-649) 
Sending operation result 80:"":"NDS error: insufficient buffer (-649)" to connection 0xca41f400 
DoUnbind on connection 0xca41f400
Connection 0xca41f400 closed

cause

eDirectory is architected around certain buffer limitations that are common to all versions.
One such limitation is the 64K limit on elements of an entire search request.
About 80 bytes are reserved for various control elements, and much of the rest is available for the optional attribute and filter lists.
Thus, both lists of attributes and filters, as well as some other packet formatting, compete for the remaining space in the 64K limit.
Because of other variables in NCP packet formatting, eDir engineering generally rounds this available buffer size to about 63K when noting the limitation.

fix

 At this point, the only work around is to reduce the amount of data that is put in the filter.

note

Example of an LDAP application using a large filter causing the error (The same error can be received if this info was put in an LDIF file and inported using ICE):

DoSearch on connection 0xca479d00
Search request:
 base: ""
 scope:2  dereference:3  sizelimit:0  timelimit:1  attrsonly:0
 filter: "(&(SnvCompanyDescr=Coastal Bank of Georgia)(SnvServiceDt=08*))"
 attribute: "FullName"
 attribute: "SnvCompanyDescr"
 attribute: "SnvServiceDt"
 attribute: "SnvOrgHireDt"
 attribute: "objectClass"
 attribute: "javaSerializedData"
 attribute: "javaClassName"
 attribute: "javaFactory"
 attribute: "javaCodeBase"
 attribute: "javaReferenceAddress"
 attribute: "javaClassNames"
 attribute: "javaRemoteLocation"
Search request:
 base: "ou=EMP,o=family"
 scope:2  dereference:3  sizelimit:0  timelimit:0  attrsonly:0
 filter: "(&(objectclass=inetOrgPerson)(|(cn=11002)(cn=11012)(cn=11020)(cn=11045)(cn=11046)(cn=11049)(cn=11054)(cn=11064)(cn=11072)(cn=11089)(cn=11096)(cn=11098)(cn=11099)(cn=11122)(cn=11128)(cn=11131)(cn=11164)(cn=11189)(cn=11197)(cn=11221)(cn=11237)(cn=11242)(cn=11275)(cn=11346)(cn=11362)(cn=11369)(cn=11388)(cn=11416)(cn=11476)(cn=11517)(cn=11522)(cn=11548)(cn=11565)(cn=11599)(cn=11604)(cn=11609)(cn=11613)(cn=11635)(cn=11636)(cn=11644)(cn=11656)(cn=11657)(cn=11661)(cn=11689)(cn=11732)(cn=11756)(cn=11771)(cn=11775)(cn=11791)(cn=11821)(cn=11822)(cn=11838)(cn=11849)(cn=11852)(cn=11873)(cn=11897)(cn=11928)(cn=11945)(cn=12001)(cn=12007)(cn=12017)(cn=12020)(cn=12025)(cn=12029)(cn=12044)(cn=12047)(cn=12072)(cn=12100)(cn=12103)(cn=12114)(cn=12157)(cn=12181)(cn=12182)(cn=12192)(cn=12244)(cn=12249)(cn=12255)(cn=12268)(cn=12277)(cn=12289)(cn=12292)(cn=12300)(cn=12302)(cn=12308)(cn=12313)(cn=12325)(cn=12335)(cn=12339)(cn=12343)(cn=12390)(cn=12469)(cn=12483)(cn=12509)(cn=12515)(cn=12516)(cn=12517)(cn=12523)(cn=12530)(cn=12532)(cn="
 attribute: (All User)
Searching "": NDS error:insufficient buffer (-649) returned
LDAPSearchToCB failed, err = insufficient buffer (-649)
Sending operation result 80:"":"NDS error: insufficient buffer (-649)" to connection 0xca479dc0
New cleartext connection 0xca479a00 from 192.168.0.26:2603, monitor = 0x2cf, index = 5
DoUnbind on connection 0xca479dc0
Connection 0xca479dc0 closed

document

Document Title: NDS error: insufficient buffer (-649) during LDIF import
Document ID: 10088140
Solution ID: NOVL93530
Creation Date: 23Oct2003
Modified Date: 27Oct2003
Novell Product Class:Novell eDirectory

disclaimer

The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.