Custom Class

[Wolfgang Kais]

Hello all.
In a windows 2000 Active Directory schema, I have created a new class, and I
have appended the class name to the possSuperiors attribute of the
organizationalUnit class. Then I wrote an ldif script that created a new
instance of my new class and a new OU below it. All works fine, and the new
subtree even is displayed in Active Directory Users and Computers. When I
right-click the new OU (logged on as an administrator), I see the submenu
"New". But when I click "User" to create a new user, I get an error message
("Severe Error, contact the administrator"). When I create the new user
through a script, everything works fine. Is that a problem of the console
(dsa.msc)? How can a avoid that problem?

 

[John]

Hello Wolfgang,

Are you seeing any events in the DS event log? If not try turning up DS
logging -
http://support.microsoft.com/default.aspx?scid=kb;en-us;314980&Product=win2000

Specifically for the following entries. (start the level at 1 to start
with)
Internal Configuration
Directory Access
Internal Processing

If possible, could you export the schema extension that you recently
implemented and post it. Please use ldifde to export, include the -m switch
in the commands syntax.

ldifde -f schemaExt.ldf -d <dn of schema object> -m

 

[Wolfgang Kais]

Hello John.
Thanks for your reply.

Hello Wolfgang,

Are you seeing any events in the DS event log?
If not try turning up DS logging -
http://support.microsoft.com/default.aspx?scid=kb;en-us;314980&Product=win20
00

Specifically for the following entries. (start the level at 1 to start
with)
Internal Configuration
Directory Access
Internal Processing

I have now tried that, no error, just a warning about a diconnection and an
information (translated from german):
04.12.2003 11:06:55 NTDS LDAP Informations LDAP-Interface 1535
DOMAIN\administrator LONDON "The following error was returned from the
LDAP-Server:
0000208D: NameErr: DSID-031001C9, problem 2001 (NO_OBJECT), data 0, best
match of:
'CN=407,CN=DisplaySpecifiers,CN=Configuration,DC=domain,DC=tst'
"
But the container exists!
The problem only occurs when I try to add a new "user", not if I try to add
an object of another class. Adding users through a script works fine.

If possible, could you export the schema extension that you
recently implemented and post it. Please use ldifde to export,
include the -m switch in the commands syntax.

ldifde -f schemaExt.ldf -d <dn of schema object> -m

Thanks for the hint with the -m switch. I even found out what it means. I
have no problem with modifying the schema using the ldif script which I
created (I exported the attributes and classes without the -m switch an then
deleted attributes until the import worked).
Am I allowed to send you the file via email?
[/QUOTE]

 

[John]

Check this article out:
http://support.microsoft.com/default.aspx?scid=kb;en-us;290999&Product=win2000

You can send the ldif file to me, offline please. Keep this thread open for
dialog so that others may benefit from it hopefully. Send the ldif file to
my hotmail account (e-mail address removed) if it is not too large.

Also, if you can export
'CN=407,CN=DisplaySpecifiers,CN=Configuration,DC=domain,DC=tst' as well
using CSVDE rather than LDIFDE. The following syntax should collect the
data I am most interested in .

csvde -f dispSpec.ldf -d
CN=407,CN=DisplaySpecifiers,CN=Configuration,DC=domain,DC=tst -p onelevel -l
cn

Thanks,
John

 

[Wolfgang Kais]

Hello John.

I did not create displaySpecifiers for the new classes, and I don't think
that this is the problem, because "user-Display" exists, and the
creationWizard/createWizardExt entries were not changed (not by me, but by
Exchange 2000). When the CreateUser-wizard is invoked, does he need the
displaySpecifier of the object two levels up in the hierarchy? I rather
guess that this specific wizard can't handle a DN that consists of other
attributes than "cn", "ou" or "dc". The other wizards can.
The Wizard works fine in other OUs that are not created below my new
classes. Even without DisplaySpecifiers, the 3 OUs (that were created
direcly below an object of a new class whose rDNAttID differs from the
ordinary ones) are displayed like containers (even though they aren't).
I tried to send you the files (including a screenshot, zipped, 28k), but
your mailbox seems to be full. I'll try again later.