This is a known bug, the result code should have been 0. It is fixed in Netscape Directory 6.11. The workaround is to ignore the resultcode value when result entries are returned or to ignore the result codes with values greater than 80 (assume the value is 0 in such a case).

Miodrag

G. Smith wrote:

I am perfoming a query which makes use of a vlvindex on iplanet's
directory server 5.1 and I am getting the following responses. Although the sort appears to be working, I am getting a non zero
result code.


vlvResponse.getContentCount() :21445
vlvResponse.getContext() :null
vlvResponse.getFirstPosition() :874
vlvResponse.getResultCode() :4141200
vlvResponse.getResultCode() :{VirtListResponseCtrl: isCritical=true
firstPositi
on=874 contentCount=21445 resultCode=4141200}
rControls.length: 2
Server Succeeded!


Does anyone have any ideas where this value might orignate from or
know of the valid result code ranges?

Thanks,
Jerry




Reply via email to