Ok, there is some good and bad news.

Lots of other people seem to have this problem. I don't really understand LDAP myself, but from what I'm reading the MS LDAP provider caches the LDAP structure locally and uses this to interrogate the server.

Here is a posting I found on a Novell site to fix a similar problem, it is a work-around (highlight in bold are mine):
Quote:

Hi,

Microsoft's ADSI libraries have an incompatibility with the eDirectory
schema
(to which they have been made aware by Novell).

For standard schema entries, your get method will work ok. But for any schema definitions outside the standard set, you will have to tell ADSI what type it is, and read it with the GetInfoEx Arry etc.

For more information on this please go to developer.novell.com/support
and
search on ADSI. For your script, I've pasted a quick sample below.
The types
are enumerated at
http://msdn.microsoft.com/library/en-us/netdir/adsi/adstypeenum.asp?frame=true

Code:

set UserObj=GetObject( "LDAP://myserver/o=novell/cn=admin" )
UserObj.GetInfoEx Array("fullname"), 3
Set entry = UserObj.GetPropertyItem( "fullname", 3 ) 'ci string type
For Each v In entry.Values 'if multivalued attribute
 Set propVal = v
 descString = propVal.GetObjectProperty(3) 'ci string type
 wscript.stdout.writeline descString
Next


Let me know if you have problems with this. It works for me, but I'm
not a
winscript expert by any means.

Thank you
Susan Perrin




Here is a link to a KB article about accessing third-party LDAP servers using ADSI:
http://support.microsoft.com/kb/q251195/

I found these by GOOGLEing using the original error message that you had.