Ldap Result Codes - Netscape DIRECTORY SERVER 6.01 Configuration Manual

B1=Corrupt BER tag encountered.
If BER tags, which encapsulate data being sent over the wire, are corrupt when
they are received, a
corrupted due to physical layer network problems or bad LDAP client operations,
such as an LDAP client aborting before receiving all request results.
B2=BER tag is longer than the
information about this configuration attribute see "nsslapd-maxbersize (Maximum
Message Size)," on page 58.
B3=Corrupt BER tag encountered
B4=Server failed to flush data response back to client
P2=Closed or corrupt connection has been detected.
T1=Client does not receive a result within the specified idletimeout period
T2=Server closed connection after ioblocktimeout period was exceeded
U1= Connection closed by server after client sends an UNBIND request. The server
will always close the connection when it sees an UNBIND request.

LDAP Result Codes

LDAP has a set of result codes that it is useful to be familiar with.
Table 5-2
Result Code
0
1
2
3
4
5
6
7
8
9
connection code is logged to the access log. BER tags can be
B1
nsslapd-maxbersize
LDAP Result Codes
Defined Value
SUCCESS
OPERATION_ERROR
PROTOCOL_ERROR
TIME_LIMIT_EXCEEDED
SIZE_LIMIT_EXCEEDED
COMPARE_FALSE
COMPARE_TRUE
AUTH_METHOD_NOT_SUPPORTED
STRONG_AUTH_REQUIRED
LDAP_PARTIAL_RESULTS
attribute value. For further
Chapter 5 Access Log and Connection Code Reference
LDAP Result Codes
187