-663 FFFFFD69   DS LOCKED

Source:  eDirectory or NDS

Explanation:  An attempt was made to perform an eDirectory or NDS operation or background process on a server whose eDirectory or NDS database was not open.

The following processes occur when eDirectory or NDS attempts to open an eDirectory or NDS database on a server running NetWare:

• The ds.nlm attempts to open the local database when volume SYS: is mounted or when the ds.nlm is reloaded.
• DSREPAIR requests the ds.nlm to open the local database after a database repair or upon exiting dsrepair.nlm.

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:  If this error occurs during an eDirectory or NDS operation, the eDirectory or NDS database on the server responsible for handling the operation is probably not open.

Action:  Repair the database using DSREPAIR.

Possible Cause:  The unicode.nlm -497 was returned to eDirectory or NDS (ds.nlm).

Action:  See possible causes and actions for error code -497 FFFFFE0F UNI HANDLE MISMATCH.

Possible Cause:  If this error occurs during an eDirectory or NDS background process, the database on the target server is not open.

Action:  Repair the database using DSREPAIR.

Possible Cause:  The target server's eDirectory or NDS tree name is null. A server will return a null eDirectory or NDS tree name if its local database is not open.

Action:  Repair the database using DSREPAIR.

Possible Cause:  The eDirectory or NDS database is locked on the server. This error will be seen in DSTRACE when the source server is trying to synchronize with a target server that has a locked database.

On the server with the locked database, no activity will be in the DSTRACE screen.

This error occurs when one of the following conditions exist:

• DSREPAIR is loaded on the server that is performing an operation that has locked the eDirectory or NDS database.
• The hard drive on the server is starting to fail.
• The server receives an error trying to open eDirectory or NDS when mounting volume SYS:.

Action:  Check to see whether DSREPAIR is loaded by going to the Partition Continuity screen in NDS manager. From the Partition Continuity screen, run Repair Local Database. At this point, if DSREPAIR is loaded, Partition Continuity will ask whether you want to unload DSREPAIR to perform the Repair Local Database option.

• If DSREPAIR is not loaded, load DSREPAIR.

  If DSREPAIR is loaded, run the Repair Local Database option once.

  If the error persists after running DSREPAIR the first time, contact a Novell Support Provider.

  WARNING:  If Repair Local Database is run a second time, the original.OLD database files will be overwritten and it might not be possible to restore their former Directory Information Base (DIB).

• If running Repair Local Database does not fix the problem, try bringing down the server and bringing it back up again. If running Repair Local Database and bringing down the server do not fix this error, the server might need to be removed from the tree.