Sort Response Error

[Jeff M. <jef...@pr...>]

When using a server side sort for group owners, I'm getting mixed sort
control errors.

Issue 1 for Net::LDAP:
The result returned by LDAP_CONTROL might not be consistent with the
command line in this case
I query the LDAP for some groups, server side sorted by owner.
($resp->result); doesn't contain anything, but the groups are not sorted
by owner.

From the command line, ldapsearch -b
ou=leiden,ou=groups,ou=peopl,o=probes -h mole -x -S "owner cn"
(&(objectclass=groupofuniquenames)(objectclass=mailgroup))" owner cn

I get the same list of groups and attributes, also not sorted by owner.
Looks more like ldif order - groups listed in the order they were set
up. After the list is finished, it's followed by an error:
Server reported sorting error 53: unable to sort

LDAP log shows no sign of the error (neither does the error log), and
what looks like a good sort:
[05/Oct/2000:15:37:50 -0700] conn=1946 fd=60 slot=60 connection from
10.1.8.10 to 10.1.2.5
[05/Oct/2000:15:37:50 -0700] conn=1946 op=0 SRCH
base="ou=leiden,ou=groups,ou=people,o=probes" scope=2
filter="(&(objectclass=groupofuniquenames)(objectclass=mailgroup))"
[05/Oct/2000:15:37:50 -0700] conn=1946 op=0 SORT owner cn (4)
[05/Oct/2000:15:37:50 -0700] conn=1946 op=0 RESULT err=0 tag=101
nentries=4 etime=0
[05/Oct/2000:15:37:50 -0700] conn=1946 op=1 UNBIND
[05/Oct/2000:15:37:50 -0700] conn=1946 op=1 fd=60 closed - U1

Why might the $mesg->control( LDAP_CONTROL_SORTRESULT ); not show the
error if the command line tool does?

Issue 2 for the LDAP server:
Why wouldn't the server sort my request by owner. I've sorted by all
kinds of other attributes, indexed and non indexed. This is an
iPlanet/Netscape Directory server 4.11. Has anyone else seen this
behavior sorting groups by owner?

Thanks,

Jeff