17.0 DSREPAIR Messages

The following includes messages from the DSREPAIR.NLM.

DSREPAIR-x-001: Unknown switch pointer.

Source: DSREPAIR.NLM
Possible Cause: An unknown command line switch was entered.
Action: Try the task again using a valid switch.

DSREPAIR-x-002: USAGE: (–L LogFileName) (–U) unattended mode.

Source: DSREPAIR.NLM
Possible Cause: The user has entered the DSREPAIR command with incorrect syntax.
Action: Try the command again with the indicated syntax. Note: –L and –U are optional parameters.

DSREPAIR-x-003: Unable to allocate resource tag: name.

Source: DSREPAIR.NLM
Possible Cause: An error occurred while DSREPAIR was trying to register for the operating system resources.
Action: Try running DSREPAIR again, or reboot the server.

DSREPAIR-x-004: Unable to register for volume dismount event.

Source: DSREPAIR.NLM
Possible Cause: An error occurred while DSREPAIR was trying to register for OS resources.
Action: Try running DSREPAIR again, or reboot the server.

DSREPAIR-x-005: Unable to allocate memory for DSREPAIR process stack.

Source: DSREPAIR.NLM
Possible Cause: The server does not have enough available memory.
Action: Increase the available memory to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

DSREPAIR-x-007: Unable to open DSREPAIR status screen.

Source: DSREPAIR.NLM
Possible Cause: An error occurred while DSREPAIR was trying to register for OS resources.
Action: Try running DSREPAIR again, or reboot the server.

DSREPAIR-x-008: Directory Services is loading the local database.

Source: DSREPAIR.NLM
Explanation: When DSREPAIR exits and tries to reload the eDirectory™ database, the process might be delayed.
Action: No further action is required.

DSREPAIR-x-009: Directory Services remains locked, error code.

Source: DSREPAIR.NLM
Explanation: When DSREPAIR.NLM unloaded and tried to reload the eDirectory database, the attempt to load the eDirectory failed.
Action: Try running DSREPAIR again. If your attempt is not successful, reinstall eDirectory on the server.

DSREPAIR-x-010: Process completed.

Source: DSREPAIR.NLM
Explanation: This informational message indicates that DSREPAIR has completed its operation and is unloading from the server.
Action: No further action is required.

DSREPAIR-x-011: Stack overflow, frame size = hex number, ESP = hex number.

Source: DSREPAIR.NLM
Possible Cause: An internal error occurred.
Action: Try running DSREPAIR again, or reboot the server, then run DSREPAIR again.

DSREPAIR-x-013: Could not open all of the Directory Services files.

Source: DSREPAIR.NLM
Explanation: Four Directory database files are stored in a secure area of the NetWare® server's volume SYS. These files were found, but DSREPAIR could not access them.
Action: Try rebuilding the volume using REBUILD (NSS Logical volume) or VREPAIR (Traditional volume. If this does not solve the problem, reinstall eDirectory and restore the objects to the Directory if necessary.

DSREPAIR-x-014: Could not establish basic access to record manager.

Source: DSREPAIR.NLM
Explanation: A request made to the record manager of the DS.NLM program to gain control of the database failed.
Action: Unload then reload eDirectory. If this does not work, reboot the server and try again.

DSREPAIR-x-015: Could not establish full access to record manager.

Source: DSREPAIR.NLM
Explanation: A request made to the record manager of the DS.NLM program to gain control of the database failed.
Action: Unload then reload eDirectory. If this does not work, reboot the server and try again.

DSREPAIR-x-016: Volume SYS is not mounted, cannot access Directory Services files.

Source: DSREPAIR.NLM
Explanation: The volume SYS: must be mounted to use eDirectory because it contains the eDirectory database files.
Action: Make sure the volume SYS: is mounted.

DSREPAIR-x-017: Cannot initialize directory path to Directory Services files.

Source: DSREPAIR.NLM
Possible Cause: DSREPAIR could not find the directory that contains the eDirectory database files in volume SYS:.
Action: Make sure volume SYS: is mounted, or run reinstall the server.

DSREPAIR-x-018: Could not rename file: old_filename.

Source: DSREPAIR.NLM
Possible Cause: A file of the same name might already exist.
Action: Run DSREPAIR again.
Action: If necessary, rebuild the volume using REBUILD (NSS Logical volume) or VREPAIR (Traditional volume), and then running DSREPAIR again.
Action: Then try unloading and reloading eDirectory.
Action: If these actions do not work, reboot the server and try again.
Action: Your final option is to reinstall the server. If the problem persists, contact a Novell® support provider.

DSREPAIR-x-019: Could not read from file: filename, offset: offset.

Source: DSREPAIR.NLM
Explanation: DSREPAIR could not read a record from the eDirectory database.
Action: Try rebuilding the volume using REBUILD (NSS Logical volume) or VREPAIR (Traditional volume) then running DSREPAIR again. Then try unloading and reloading eDirectory.
Action: If these actions do not work, reboot the server and try again.
Action: A final option is to reinstall the server. If the problem persists, contact a Novell support provider.

DSREPAIR-x-020: Could not read entry of name: local_name.

Source: DSREPAIR.NLM
Explanation: DSREPAIR could not read a record from the eDirectory database.
Action: Try rebuilding the volume using REBUILD (NSS Logical volume) or VREPAIR (Traditional volume and run DSREPAIR again. Then unload and reload eDirectory.
Action: If these actions do not work, reboot the server and try again.
Action: A final option is to reinstall the server. If the problem persists, contact a Novell support provider.

DSREPAIR-x-021: Could not write to file: filename, offset offset

Source: DSREPAIR.NLM
Explanation: DSREPAIR could not write a record to the eDirectory database.
Possible Cause: The volume might be full,
Possible Cause: The database might be corrupted.
Action: Try rebuilding the volume using REBUILD (NSS Logical volume) or VREPAIR (Traditional volume then run DSREPAIR again. Then unload and reload eDirectory.
Action: If these actions do not work, reboot the server and try again.
Action: A final option is to reinstall the server. If the problem persists, contact a Novell support provider.

DSREPAIR-x-022: Could not insert record for file: filename, offset offset

Source: DSREPAIR.NLM
Explanation: DSREPAIR could not write a record to the eDirectory database.
Possible Cause: The volume might be full.
Possible Cause: The database might be corrupted.
Action: Try rebuilding the volume using REBUILD (NSS Logical volume) or VREPAIR (Traditional volume then running DSREPAIR again. Then try unloading and reloading eDirectory.
Action: If these actions do not work, reboot the server and try again.
Action: A final option is to reinstall the server. If the problem persists, contact a Novell support provider.

DSREPAIR-x-023: Could not read the file size for file: filename

Source: DSREPAIR.NLM
Explanation: DSREPAIR could not read a record from the eDirectory database.
Action: Try rebuilding the volume using REBUILD (NSS Logical volume) or VREPAIR (Traditional volume then running DSREPAIR again. Then try unloading and reloading eDirectory.
Action: If these actions do not work, reboot the server and try again.
Action: A final option is to reinstall the server. If the problem persists, contact a Novell support provider.

DSREPAIR-x-024: Could not update whole value for file: filename, offset offset

Source: DSREPAIR.NLM
Explanation: DSREPAIR could not write a record to the eDirectory database.
Possible Cause: The volume might be full
Possible Cause: The database might be corrupted.
Action: Try rebuilding the volume using REBUILD (NSS Logical volume) or VREPAIR (Traditional volume then running DSREPAIR again. Then try unloading and reloading eDirectory.
Action: If these actions do not work, reboot the server and try again.
Action: A final option is to reinstall the server. If the problem persists, contact a Novell support provider.

DSREPAIR-x-025: Could not read whole value for file: filename, offset offset

Source: DSREPAIR.NLM
Explanation: DSREPAIR could not read a record from the eDirectory database.
Action: Try rebuilding the volume using REBUILD (NSS Logical volume) or VREPAIR (Traditional volume then running DSREPAIR again. Then try unloading and reloading eDirectory.
Action: If these actions do not work, reboot the server and try again.
Action: A final option is to reinstall the server. If the problem persists, contact a Novell support provider.

DSREPAIR-x-026: Could not purge record in file filename, offset offset

Source: DSREPAIR.NLM
Explanation: DSREPAIR could not purge a record from the eDirectory database.
Possible Cause: The database could be corrupted.
Action: Try rebuilding the volume using REBUILD (NSS Logical volume) or VREPAIR (Traditional volume and running DSREPAIR again. Then try unloading and reloading eDirectory.
Action: If these actions do not work, reboot the server and try again.
Action: A final option is to reinstall the server. If the problem persists, contact a Novell support provider.

DSREPAIR-x-027: Could not allocate number bytes of memory.

Source: DSREPAIR.NLM
Explanation: The server does not have enough available memory.
Action: Increase the available memory to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

DSREPAIR-x-028: Error encountered in schema cache DS_NLM_error_number.

Source: DSREPAIR.NLM
Explanation: An internal error occurred in the DSREPAIR NLM program.
Action: Try again. If the problem persists, contact a Novell support provider.

DSREPAIR-x-029: Could not insert record for file: filename

Source: DSREPAIR.NLM
Explanation: DSREPAIR could not write a record to the eDirectory database.
Possible Cause: The volume could be full.
Possible Cause: The database could be corrupted.
Action: Try rebuilding the volume using REBUILD (NSS Logical volume) or VREPAIR (Traditional volume, then try again. If the problem persists, contact a Novell support provider.

DSREPAIR-x-030: Error reading attribute attribute from entry entry.

Source: DSREPAIR.NLM
Explanation: DSREPAIR could not read a record from the eDirectory database.
Action: Try rebuilding the volume using REBUILD (NSS Logical volume) or VREPAIR (Traditional volume, then try again. If the problem persists, contact a Novell support provider.

DSREPAIR-x-031: Could not truncate the file: filename

Source: DSREPAIR.NLM
Explanation: DSREPAIR could not write a record to the eDirectory database.
Possible Cause: The volume could be full.
Possible Cause: The database could be corrupted.
Action: Try rebuilding the volume using REBUILD (NSS Logical volume) or VREPAIR (Traditional volume, then try again. If the problem persists, contact a Novell support provider.

DSREPAIR-x-032: Internal API version mismatch, DSREPAIR is version number and DS is version number.

Source: DSREPAIR.NLM
Explanation: The same release of DS and DSREPAIR is needed to run DSREPAIR.
Action: Check the versions of each utility. To do this, do the following:

  • To check the version numbers of utilities and NDIR, type the VER.

  • To check the version of the DSREPAIR.NLM, type NDIR DSREPAIR.NLM /VER.

  • To check the DS.NLM version, type MODULES at the server console.

Load a newer version of one or both files. If you are not sure about the current version, contact a Novell support provider.

DSREPAIR-x-033: Could not create or open file: name.

Source: DSREPAIR.NLM
Explanation: DSREPAIR could not create and open a file.
Possible Cause: The volume might be full.
Action: Try rebuilding the volume using REBUILD (NSS Logical volume) or VREPAIR (Traditional volume then running DSREPAIR again.
Possible Cause: No more directory entries are available on the volume.
Action: Use FILER to make sure you have available directory entries.

DSREPAIR-x-034: Could not write to file: filename at location address.

Source: DSREPAIR.NLM
Explanation: DSREPAIR could not write a record to the eDirectory database.
Possible Cause: The volume might be full.
Possible Cause: The database might be corrupted.
Action: Try rebuilding the volume using REBUILD (NSS Logical volume) or VREPAIR (Traditional volume then running DSREPAIR again. If the problem persists, contact a Novell support provider.

DSREPAIR-x-035: Internal versions do not match: DSREPAIR.NLM = version, DS.NLM = version, database files = number

Source: DSREPAIR.NLM
Explanation: The same internal version of DS.NLM and DSREPAIR.NLM and the eDirectory database is needed to run DSREPAIR.
Action: If the versions of the NLM™ programs do not match, load the correct versions of the programs. If the database does not match, then use DSREPAIR.NLM to upgrade it to the most current version. This is done automatically if the DS.NLM and DSREPAIR.NLM programs are the same version and the eDirectory database is one version earlier.

DSREPAIR-x-036: Could not gain access to Directory Services DS.NLM is not loaded.

Source: DSREPAIR.NLM
Explanation: The eDirectory database is not accessible.
Possible Cause: The DS.NLM is not loaded.
Action: Load the DS.NLM, and then try accessing the database again.

DSREPAIR-x-037: Directory Services API interface versions do not match

DSREPAIR internal interface version is version

DSREPAIR API interface version is: version

Directory Services API interface version is: version

Source: DSREPAIR.NLM
Explanation: The version of DSREPAIR does not match with the version DS.NLM.
Action: Get the correct version and try again.

Note: The version’s displayed in the message might all have the same value and still be the wrong version. These versions do not indicate the correct version. To get the correct version, contact a Novell support provider.

DSREPAIR-x-039: Internal Error, number number.

Source: DSREPAIR.NLM
Explanation: An internal failure occurred in the NLM program.
Action: Reboot the server and try again. If the problem persists, contact a Novell support provider or the NLM program vendor.

DSREPAIR-x-040: Error writing to log file, log file closed.

Source: DSREPAIR.NLM
Explanation: An error occurred while DSREPAIR was writing to the log file target device, or the device has no more room. The repair will continue without logging any more errors to the log file.
Action: No further action is required.

DSREPAIR-x-041: This NLM requires a newer version of NWSNUT.

Source: DSREPAIR.NLM
Explanation: While loading, DSREPAIR.NLM determined that the version of the NWSNUT.NLM does not support the functionally required by the DSREPAIR.NLM.
Action: Update the version of NWSNUT.NLM on the server.

DSREPAIR-x-042: This NLM was unable to initialize NWSNUT.

Source: DSREPAIR.NLM
Explanation: The support NLM program, NWSNUT, returned an error from the initialization process.
Possible Cause: An internal error occurred.
Action: Try the operation again. If the error persists, contact a Novell support provider.
Possible Cause: The server has insufficient memory.
Action: Increase the available memory to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide. Try the operation again. If the server has at least 500 KB of free memory, contact a Novell support provider.

DSREPAIR-x-043: Unable to create an NWSNUT portal.

Source: DSREPAIR.NLM
Explanation: The server might be out of memory.
Action: Increase the available memory to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide. Try the operation again.

DSREPAIR-x-044: Could not read from file: name, offset number. Record will be padded with 0’s.

Source: DSREPAIR.NLM
Explanation: DSREPAIR could not read a record from the eDirectory database; however, rather than aborting the repair, the record is filled with 0’s and the repair operation will continue.
Action: No further action is required.

DSREPAIR-x-045: Could not gain access to Directory Services. Another NLM has already registered with DS. This could be one of DSI.NLM, DSMERGE.NLM or DSREPAIR.NLM.

Source: DSREPAIR.NLM
Explanation: Only one of the three described NLM programs can be loaded at a time.
Action: Check to see if one of these NLM programs are loaded and unload it. If that does not resolve the problem, bring down the server and bring it back up. Then retry the operation.

DSREPAIR-x-046: The Schema Tree is corrupt, no repair strategy is available. Remove the server from the Directory Services Tree and then re-install it.

Source: DSREPAIR.NLM
Explanation: The schema cannot be repaired, and the eDirectory database on this server cannot operate without it.
Action: Deinstall the server from the tree and reinstall it.

DSREPAIR-x-047: Could not locate one or more Directory Services files.

Source: DSREPAIR.NLM
Action: If database files are missing, you must deinstall the server from the tree, and then reinstall the server.