Source: eDirectory or NDS
Explanation: The specified eDirectory or NDS schema class definition does not exist on the eDirectory or NDS server that is replying to the request.
The request might be
WARNING: Applying all solutions mentioned in this topic could make the problem worse if the actual cause of the problem is not known. Before following a course of action, make sure that you understand the cause of the error and the consequences for the actions suggested.
Possible Cause: The timestamp on the attribute of an object is in the future by two days or more.
Action: Contact a Novell Support Provider.
Possible Cause: An attempt was made to add a class to the containment list of another eDirectory or NDS schema class definition. In this case, the class to be added does not exist on the eDirectory or NDS server that is replying to the request.
Action: Contact a Novell Support Provider.
Possible Cause: An attempt was made to create an eDirectory or NDS object using an eDirectory or NDS schema class definition that does not exist.
Action: Contact a Novell Support Provider.
Possible Cause: An attempt was made to change an object to an eDirectory or NDS object with an eDirectory or NDS schema class definition that does not exist.
Action: Contact a Novell Support Provider.
Possible Cause: The ndssch.exe file in sys:\public is not synchronized with the *.sch files in sys:\system\schema.
Action: Find the server that has the files with the .sch extension and set DSTRACE= *ssd *ssa or *ss to force schema synchronization. Add a replica of the root to this server. Import the schema from another tree extended with the same information.
Possible Cause: Third-party schema is not synchronized.
Action: Remove and reinstall the third-party schema and re-create the extension.
Possible Cause: If this error occurs when grafting trees, the name of the tree might be greater than 22 characters.
Action: Change the tree name to a name with 22 characters or less using the following steps:
Load dsmerge on the server that contains the master replica.
Use the Rename this tree option.
Log in to the tree using the fully distinguished name of user Admin, along with the password.
Enter the new tree name. Press F10 to perform the rename.
Upon exiting dsmerge, you can run the Limber process to expedite synchronizing the tree's name change.
To start the Limber process, type the following commands at the console prompt:
Clean out any orphans or external references to the old tree by running DSREPAIR.
Edit any login scripts that refer to the old tree name.