-663 FFFFFD69 DS LOCKED
Source
eDirectory
Explanation
An attempt was made to perform an eDirectory operation or background process on a server whose eDirectory database was not open.
The following processes occur when eDirectory attempts to open an eDirectory database on a server running NetWare®:
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 operation, the eDirectory 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 (ds.nlm).
Action
See possible causes and actions for error code -497.
Possible Cause
If this error occurs during an eDirectory background process, the database on the target server is not open.
Action
Repair the database using DSREPAIR.
Possible Cause
The target server's eDirectory tree name is null. A server will return a null eDirectory tree name if its local database is not open.
Action
Repair the database using DSREPAIR.
Possible Cause
The eDirectory 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:
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 NetIQ* 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).
A trademark symbol (®, TM, etc.) denotes a NetIQ trademark. An asterisk (*) denotes a third-party trademark. For information on trademarks, see Legal Notices.