Return-Path: Delivered-To: apmail-directory-users-archive@www.apache.org Received: (qmail 24229 invoked from network); 30 Jul 2007 18:01:33 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 30 Jul 2007 18:01:33 -0000 Received: (qmail 37685 invoked by uid 500); 30 Jul 2007 18:01:33 -0000 Delivered-To: apmail-directory-users-archive@directory.apache.org Received: (qmail 37662 invoked by uid 500); 30 Jul 2007 18:01:32 -0000 Mailing-List: contact users-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@directory.apache.org Delivered-To: mailing list users@directory.apache.org Received: (qmail 37651 invoked by uid 99); 30 Jul 2007 18:01:32 -0000 Received: from Unknown (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 30 Jul 2007 11:01:32 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of the.mail.lister@gmail.com designates 64.233.184.228 as permitted sender) Received: from [64.233.184.228] (HELO wr-out-0506.google.com) (64.233.184.228) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 30 Jul 2007 18:01:25 +0000 Received: by wr-out-0506.google.com with SMTP id 25so677526wry for ; Mon, 30 Jul 2007 11:01:05 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding; b=cz/ah/xt4+3Ce/M3QOmBmH6y/0BmI5fRjl3hCrFUsIiDz/hQ0lZaevX5Hp2TAIl87B/7LUEv68vwAHf+WXiXYZ6Kn3hlpN+BiC8aggon667mROUUdruQQ07GcQ1weez5n4CrTRc9t1y6BkB7fXEvTZ/ZyGtLD/P/PHEjpIMCCUU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding; b=Lhyrh0fGD792SEHQCSY0A8RZq6gb8PEmLQ0/Bqu024ArT2ZEz5rvyqdbdHrFO0ekOOZkWKD36JK6mynbvvzIqLnySAAzdbUskpsnUyZDtnAItUnZjS2WVopKKfB9S57v1NOipE1eT3Fh+1t7tVWsDuyZtFBunwvLIoX/otiygf8= Received: by 10.90.89.5 with SMTP id m5mr2313419agb.1185818465211; Mon, 30 Jul 2007 11:01:05 -0700 (PDT) Received: from ?10.1.129.48? ( [167.156.63.253]) by mx.google.com with ESMTPS id 8sm3110070wra.2007.07.30.11.01.03 (version=SSLv3 cipher=RC4-MD5); Mon, 30 Jul 2007 11:01:03 -0700 (PDT) Message-ID: <46AE275F.9030304@gmail.com> Date: Mon, 30 Jul 2007 14:01:03 -0400 From: Tod User-Agent: Thunderbird 1.5.0.12 (Windows/20070509) MIME-Version: 1.0 To: users@directory.apache.org Subject: Re: Error reading children of base DN References: <46ADF19E.2050805@gmail.com> <46AE158D.90600@labeo.de> In-Reply-To: <46AE158D.90600@labeo.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Stefan Zoerner wrote: > Hi Tod! > >> I'm getting an error reading the children entries against a Lotus >> Domino server. I understand the reason for the error, but I'm having >> trouble finding the offending entry. Is there some debug method I can >> use to track it down? >> > > You might want to give us more information in order to get help. Am I > right that you use Lotus Domino as your LDAP server? What technology do > you use to retrieve the entries (JNDI? Java at all?) etc. What does > "offending entry" mean? If it is not compliant to the schema, why is it > in your directory? You probably mean something else (but what?). There is a Domino server that houses information in its NAB that is important to our customer. I can retrieve data using perl Net::LDAP calls, as well as with C API calls. I haven't tried JNDI but I *suspect* similar results. As I was trying out the LDAP Studio on other LDAP servers, I pointed it to the Domino box to see if it would work. When I tried to expand the baseDn I got the following error "Error while reading entry Empty Attribute is not allowed!". I don't profess the virtues of Domino's (or ADS's) compliance with LDAP schema standards, I am just tasked in dealing with them :) > Please note that this is a mailing list primarily for users of Apache > Directory software (like ApacheDS, Directory Studio ...). If you > questions related to IBM products, this is likely not the right place to > ask. I understand the error above but I need more information to track down the entry(ies) causing that error. It would be helpful if there was a way to get more details from LDAP Studio so that I could discover the problem with the directory and remove it, hence my post. Incidentally, I just tried this on ADS and I get a "Error while reading entry, Unprocessed Continuation Reference(s)" error when trying to expand its baseDn. That's probably better saved for a separate thread... Thanks - Tod