Re: ldap DirectoryServices.DirectoryEntry System.NotImplementedException: Handling of this ADSVALUE type is not yet implemented (type = 0xb).

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: m96 (m96_at_gmx.li)
Date: 02/13/05


Date: Sun, 13 Feb 2005 17:38:44 +0100
To: "Lionel LASKE" <llaske@c2s.fr>

hi,

> My guess is that your LDAP Server is in LDAP v2 (MMS ?).

the problem also occurs on ldap v3 servers like the free novell ldap
server at www.nldap.com port 80 for informations and port 389 for the ldap
server. you can also create an account for authorized access. and even
then it won't work....

for example this is what i get from the server above for a search
(cn=admin):

objectclass := inetOrgPerson
objectclass := organizationalPerson
objectclass := person
objectclass := top
objectclass := ndsLoginProperties
passwordrequired := False
messageserver := cn=DEVNET-PUBLIC_SYS,o=NOVELL
logintime := 2/4/2005 2:13:37 AM
networkaddress := System.NotImplementedException: Handling of this ADSVALUE type is not yet implemented (type = 0xb).
nrdregistryindex := System.Byte[]
language := System.NotImplementedException: Handling of this ADSVALUE type is not yet implemented (type = 0xb).
passwordallowchange := True
adspath := LDAP://www.nldap.com:389/cn=admin,o=NOVELL
equivalenttome := cn=bfjeldst,o=NOVELL
equivalenttome := cn=jcox,o=NOVELL
equivalenttome := cn=cseamons,o=NOVELL
equivalenttome := cn=AClark,o=NOVELL
equivalenttome := cn=FZhao,o=NOVELL
sn := admin
cn := admin
acl := System.NotImplementedException: Handling of this ADSVALUE type is not yet implemented (type = 0xb).
acl := System.NotImplementedException: Handling of this ADSVALUE type is not yet implemented (type = 0xb).
acl := System.NotImplementedException: Handling of this ADSVALUE type is not yet implemented (type = 0xb).
acl := System.NotImplementedException: Handling of this ADSVALUE type is not yet implemented (type = 0xb).
nrdregistrydata := System.Byte[]

> When you call a LDAP v2 Server with ADSI or with DirectoryServices, you
> can't use custom attribute.
> The reason is that ADSI/Directory Services need the schema to expose
> attributes as object properties. Unfortunatly, LDAP schema is only published
> in LDAP v3. So, when ADSI find a custom attribute, it can't determine its
> type and raise an exception.
>
> On a LDAP v2 server you must use only standard LDAP attribute with
> ADSI/Directory Services . If you really need using custom attributes, you
> must call the native C/LDAP API (and it's not fun !).

so that means you can not add handler for user specific types... that's a
shame...

thank you very much for your help...



Relevant Pages

  • Re: Does samba 3.0.14Aa on OS 5.0.6 work with ldapsam backend on another LDAP server?
    ... used 3.0.9 on SCO 5.0.6 for quite some time after suffering problems I ... a RedHat4 box running samba 3.0.10 and OpenLDAP 2.2.13. ... and no LDAP server (although there were the ... share on the SCO server without any smbpasswd on that server! ...
    (comp.unix.sco.misc)
  • LDAP/SSL authentication in FC2
    ... My LDAP server is a FC1 box with OpenLDAP/TLS (stock standard from the ... objectClass: inetLocalMailRecipient ... objectClass: shadowAccount ...
    (Fedora)
  • RE: LDAP & Find People not working
    ... need to refer to the KB article below to know how to use LDAP: ... | Yes, the scanner is on the local area network, so as you indicated below, ... | So I wonder why the scanner does not see the LDAP server. ...
    (microsoft.public.windows.server.sbs)
  • slapd - slow starting
    ... contact LDAP server ... then slapd started fine but I without ldap in nsswitch.conf I cant ... # The user ID attribute (defaults to uid) ... # SSL enabled. ...
    (freebsd-stable)
  • Re: Configuring LDAP on Entourage 2004 OS X
    ... On the SBS server box, open Server Management console, navigate to ... by companies that are independent of Microsoft. ... Configuring LDAP on Entourage 2004 OS X ...
    (microsoft.public.windows.server.sbs)