48.0 NWCONFIG Messages

The following includes messages from NWCONFIG.NLM.

NWCONFIG-X-1: An attempt to access NWCONFIG messages failed. It is likely that the message or help files (NWCONFIG.MSG or NWCONFIG.HLP) are out-of-date, missing, or corrupted.

Source: NWCONFIG.NLM
Explanation: NWCONFIG.NLM cannot read its message file.
Action: Make sure that the server language is set to 4 (English) for the built-in messages, or to a different number to correspond to both of the following:
  • The NWCONFIG.MSG file and NWCONFIG.HLP are in the boot directory (where server.exe is found)

  • The corresponding SYS:SYSTEM\NLS\X directory on the server

NWCONFIG-X-2: An attempt to add an option to a menu failed.

Source: NWCONFIG.NLM
Explanation: NWCONFIG was unable to build a menu on the screen. The server might not have enough available memory.
Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

NWCONFIG-X-3: Fatal error: The installation cannot complete successfully. An attempt to allocate memory failed. You must add (or reconfigure) memory and restart the installation.

Source: NWCONFIG.NLM
Explanation: Memory is insufficient for NWCONFIG to run.
Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

NWCONFIG-X-4: The disk partition table could not be read.

Source: NWCONFIG.NLM
Explanation: NWCONFIG was unable to read the disk partition information from the hard disk.
Action: Make sure the disk is visible from DOS. If it is visible, try to read the partition table with FDISK. If FDISK cannot see the disk, then the disk might be faulty. If FDISK can see the disk but this error still appears, contact a Novell support provider.

NWCONFIG-X-5: No information about device number could be obtained.

Source: NWCONFIG.NLM
Explanation: NWCONFIG was unable to read or write the disk partition table on device number.

NWCONFIG-X-6: No disk partitions are defined on this drive.

Source: NWCONFIG.NLM
Explanation: This informational message indicates that the designated disk drive does not contain a partition table. The server is probably using a new disk that has never been formatted or partitioned before NWCONFIG will create a partition table.

NWCONFIG-X-7: An attempt to write out partition information failed. Error code: code.

Source: NWCONFIG.NLM
Explanation: While writing the partition information to the disk drive, the operating system reported an error to NWCONFIG.

NWCONFIG-X-8: An attempt to add a field to a form failed.

Source: NWCONFIG.NLM
Explanation: NWCONFIG was unable to complete an operation to build a screen presentation.
Possible Cause: Memory is insufficient at the server.
Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

NWCONFIG-X-9: An attempt to write out partition table information failed. Error code: code.

Source: NWCONFIG.NLM
Explanation: While writing the partition information to the disk drive, the operating system reported an error from NWCONFIG.
Action: See Disk Errors in the NW 6.5 SP8: Server Operating SystemAdministration Guide For information on the specific error code, search the Error Codes online documentation.

NWCONFIG-X-10: The block allocation size does not match that of another volume with the same name.

Source: NWCONFIG.NLM
Explanation: NWCONFIG found two volume segments with the same name, but the block sizes of the two do not match. Two volumes on the same server cannot have the same name.
Action: Bring the disks that contain these volumes online one at a time, rather than at the same time. If one of the volumes is old and no longer needed, delete it to avoid the problem in the future.

NWCONFIG-X-11: The number of segments in the volume does not match the number in another volume with the same name.

Source: NWCONFIG.NLM
Explanation: NWCONFIG found two volumes with the same name, but the number of segments in the two do not match. Two volumes on the same server cannot have the same name.
Action: Bring the disks that contain these volumes online one at a time, rather than at the same time. If one of the volumes is old and no longer needed, delete it to avoid the problem in the future.

NWCONFIG-X-12: The volume flags do not match those of another volume with the same name.

Source: NWCONFIG.NLM
Explanation: NWCONFIG found two volume segments with the same name, but the volume flags of the two do not match.
Action: Bring the disks that contain these volumes online one at a time, rather than at the same time. If one of the volumes is old and no longer needed, delete it to avoid the problem in the future. Two volumes on the same server cannot have the same name.

NWCONFIG-X-13: The total volume size does not match that of another volume with the same name.

Source: NWCONFIG.NLM
Explanation: NWCONFIG found two volume segments with the same name, but the volume sizes of the two do not match.
Action: Bring the disks that contain these volumes online one at a time, rather than at the same time. If one of the volumes is old and no longer needed, delete it to avoid the problem in the future. Two volumes on the same server cannot have the same name.

NWCONFIG-X-14: The first block of FAT table 0 of the volume does not match that of another volume with the same name.

Source: NWCONFIG.NLM
Explanation: NWCONFIG found two volumes with the same name, but the FAT tables of the two do not match.
Action: Bring the disks that contain these volumes online one at a time, rather than at the same time. If one of the volumes is old and no longer needed, delete it to avoid the problem in the future. Two volumes on the same server cannot have the same name.

NWCONFIG-X-15: The first block of FAT table 1 of the volume does not match that of another volume with the same name.

Source: NWCONFIG.NLM
Explanation: NWCONFIG found two volumes with the same name, but the FAT tables of the two do not match.
Action: Bring the disks that contain these volumes online one at a time, rather than at the same time. If one of the volumes is old and no longer needed, delete it to avoid the problem in the future. Two volumes on the same server cannot have the same name.

NWCONFIG-X-16: The first block of Directory table 0 does not match that of another volume with the same name.

Source: NWCONFIG.NLM
Explanation: NWCONFIG found two volumes with the same name, but the Directory tables of the two do not match.
Action: Bring the disks that contain these volumes online one at a time, rather than at the same time. If one of the volumes is old and no longer needed, delete it to avoid the problem in the future. Two volumes on the same server cannot have the same name.

NWCONFIG-X-17: The first block of Directory table 1 does not match that of another volume with the same name.

Source: NWCONFIG.NLM
Explanation: NWCONFIG found two volumes with the same name, but the Directory tables of the two do not match.
Action: Bring the disks that contain these volumes online one at a time, rather than at the same time. If one of the volumes is old and no longer needed, delete it to avoid the problem in the future. Two volumes on the same server cannot have the same name.

NWCONFIG-X-18: A volume was found whose name could not be determined.

Source: NWCONFIG.NLM
Explanation: An invalid volume has been found. This volume has become corrupted.
Action: Delete the volume and, if necessary, restore it from backups. If the problem persists, contact a Novell support provider.

NWCONFIG-X-19: Volume name name must be at least two characters long.

Source: NWCONFIG.NLM
Explanation: A volume name was entered which was shorter than two characters.
Action: Enter a name at least two characters long.

NWCONFIG-X-20: A volume was found with an invalid volume block size of number KB.

Source: NWCONFIG.NLM
Explanation: An invalid volume has been found. This volume has become corrupted.
Action: Delete the volume. If the data is required, restore it from backups. If the problem persists, contact a Novell support provider.

NWCONFIG-X-21: A volume was found with an invalid number of volume segments (number). Check to be sure all disk drivers are configured properly.

Source: NWCONFIG.NLM
Explanation: An invalid volume has been found. This volume has become corrupted.
Action: Delete the volume. If the data is required, restore it from backups. If the problem persists, contact a Novell support provider.

NWCONFIG-X-22: A volume was found with an invalid volume segment position number of number segments. Check to be sure all disk drivers are configured properly.

Source: NWCONFIG.NLM
Explanation: An invalid volume has been found. This volume has become corrupted.
Action: Delete the volume. If the data is required, restore it from backups. If the problem persists, contact a Novell support provider.

NWCONFIG-X-23: A volume was found with an invalid starting sector offset of number on a drive of size number sectors. Check to be sure all disk drivers are configured properly.

Source: NWCONFIG.NLM
Explanation: An invalid volume has been found. This volume has become corrupted.
Action: Delete the volume. If the data is required, restore it from backups. If the problem persists, contact a Novell support provider.

NWCONFIG-X-24: A volume was found with an invalid starting sector offset of number. Check to be sure all disk drivers are configured properly.

Source: NWCONFIG.NLM
Explanation: An invalid volume has been found. This volume has become corrupted.
Action: Delete the volume. If the data is required, restore it from backups. If the problem persists, contact a Novell support provider.

NWCONFIG-X-25: A volume was found with an invalid segment length of number starting at number on a drive of size number. Check to be sure all disk drivers are configured properly.

Source: NWCONFIG.NLM
Explanation: An invalid volume has been found. This volume has become corrupted.
Action: Delete the volume. If the data is required, restore it from backups. If the problem persists, contact a Novell support provider.

NWCONFIG-X-26: A volume was found with an invalid FAT table 0, with a starting block of number out of number total blocks. Check to be sure all disk drivers are configured properly.

Source: NWCONFIG.NLM
Explanation: An invalid volume has been found. This volume has become corrupted.
Action: Make sure disk drivers are configured correctly. Run VREPAIR. If these efforts fail, delete the volume. If the data is required, restore it from backups.

NWCONFIG-X-27: A volume was found with an invalid FAT table 1 starting block of number on a volume of number blocks. Check to be sure all disk drivers are configured properly.

Source: NWCONFIG.NLM
Explanation: An invalid Traditional volume has been found. This volume has become corrupted.
Action: Make sure disk drivers are configured correctly. Run VREPAIR. If these efforts fail, delete the volume. If the data is required, restore it from backups.

NWCONFIG-X-28: A volume was found with an invalid directory table 0 starting block of number on a volume of number blocks. Check to be sure all disk drivers are configured properly.

Source: NWCONFIG.NLM
Explanation: An invalid volume has been found. This volume has become corrupted.
Action: Make sure disk drivers are configured correctly. Run VREPAIR. If these efforts fail, delete the volume. If the data is required, restore it from backups.

NWCONFIG-X-29: A volume was found with an invalid directory table 1 starting block of number on a volume of number blocks. Check to be sure all disk drivers are configured properly.

Source: NWCONFIG.NLM
Explanation: An invalid volume has been found. This volume has become corrupted.
Action: Make sure disk drivers are configured correctly. Run VREPAIR. If these efforts fail, delete the volume. If the data is required, restore it from backups.

NWCONFIG-X-30: A volume definition was found with a reserved area that is not filled with zero data. Check to be sure all disk drivers are configured properly.

Source: NWCONFIG.NLM
Explanation: An invalid volume has been found. This volume has become corrupted.
Action: Make sure disk drivers are configured correctly. Run VREPAIR. If these efforts fail, delete the volume. If the data is required, restore it from backups.

NWCONFIG-X-31: Due to a memory allocation problem, the volume definitions were not updated on the disk.

Source: NWCONFIG.NLM
Explanation: There is insufficient memory to accomplish the desired update.
Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide. Then try the operation again.

NWCONFIG-X-32: Volume information could not be written because NWCONFIG was unable to lock disk label.

Source: NWCONFIG.NLM
Explanation: The disk is probably being used by another process. A mounted volume might be using it.
Action: Wait to see if the process releases the device, then retry the action. If there is a disk device error, unload NLM programs (except device drivers) that might be using the disk. Then dismount volumes from the disk. If these efforts fail, try loading MONITOR, deleting all user connections, and disabling logins.

NWCONFIG-X-33: An error occurred (error code: code) while writing to disk label sector number.

Source: NWCONFIG.NLM
Explanation: The disk could not be written to. The driver or disk might not be configured correctly, or a hardware failure might have occurred.
Action: See Disk Errors in the NW 6.5 SP8: Server Operating SystemAdministration Guide. For information about a specific error code, search the Error Codes online documentation.

NWCONFIG-X-34: An attempt to expand the mounted volume tables failed. Error code: code.

Source: NWCONFIG.NLM
Explanation: NWCONFIG could not write to the disk or allocate memory to expand the volume FAT and directory tables.
Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide. For information about a specific error code, search the Error Codes online documentation.

NWCONFIG-X-35: The program could not allocate memory for the volume FAT table.

Source: NWCONFIG.NLM
Explanation: There is insufficient memory to accomplish the desired operation.
Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

NWCONFIG-X-36: The program could not find a free block during FAT block allocation.

Source: NWCONFIG.NLM
Explanation: An internal system error has occurred.
Action: Try again. If the problem persists, contact a Novell support provider.

NWCONFIG-X-37: Function FreeFATTable() was called when no FAT table was allocated.

Source: NWCONFIG.NLM
Explanation: An internal system error has probably occurred.
Action: Try again. If the problem persists, contact a Novell support provider.

NWCONFIG-X-38: The program could not lock disk label in order to read volume information.

Source: NWCONFIG.NLM
Explanation: The disk probably is being used by another process.
Action: Wait to see if the process releases the device, then retry the action. If there is a disk device error, unload NLM programs (except device drivers) that might be using the disk. Then dismount volumes from the disk. If these efforts fail, try loading MONITOR, deleting all user connections, and disabling logins.

NWCONFIG-X-39: An error occurred (error code: code) while reading from disk label, NetWare disk partition sector number. Error information: description

Source: NWCONFIG.NLM
Explanation: NWCONFIG could not read from the disk.
Action: See Disk Errors in the NW 6.5 SP8: Server Operating SystemAdministration Guide. For information about a specific error code, search the Error Codes online documentation.

NWCONFIG-X-40: The program could not read the primary FAT entry from a volume.

Source: NWCONFIG.NLM
Explanation: NWCONFIG could not read from the volume.

NWCONFIG-X-41: The program could not read the mirror FAT entry from a volume.

Source: NWCONFIG.NLM
Explanation: NWCONFIG could not read from the volume.

NWCONFIG-X-42: An error occurred while writing name FAT block sequence number.

Source: NWCONFIG.NLM
Explanation: NWCONFIG could not write to the volume.

NWCONFIG-X-43: The program could not find a free block to which to redirect the FAT block.

Source: NWCONFIG.NLM
Explanation: The volume might be full or the drive parameters might not be set up correctly. This message could also indicate a bug in the program.
Action: If possible, try specifying a larger volume size. Also check the drive parameters. If the problem persists, contact a Novell support provider.

44: End of file was encountered unexpectedly in the FAT file, FAT chain, sequence number number.

Source: NWCONFIG.NLM
Explanation: An internal system error has occurred.
Action: Try again. If the problem persists, contact a Novell support provider.

45: The program could not find a free block during file system directory block allocation.

Source: NWCONFIG.NLM
Explanation: The volume might be full or the drive parameters might not be set up correctly. This message could also indicate a bug in the program.
Action: If possible, try specifying a larger volume size. Also check the drive parameters. If the problem persists, contact a Novell support provider.

NWCONFIG-X-46: The program could not allocate memory for the file system directory table.

Source: NWCONFIG.NLM
Explanation: There is insufficient memory to accomplish the desired operation.

NWCONFIG-X-47: An error occurred while writing name file system directory block sequence number.

Source: NWCONFIG.NLM
Explanation: NWCONFIG could not write to the volume. This could indicate an internal system error.

NWCONFIG-X-48: The program could not find a free block to redirect the file system directory block to.

Source: NWCONFIG.NLM
Explanation: The volume might be full or the drive parameters might not be set up correctly. This message could also indicate a bug in the program.
Action: If possible, try specifying a larger volume size. Also check the drive parameters. If the problem persists, contact a Novell support provider.

NWCONFIG-X-49: End of file was encountered unexpectedly in the system directory file, FAT chain at sequence number.

Source: NWCONFIG.NLM
Explanation: An internal system error has occurred.
Action: Try again. If the problem persists, contact a Novell support provider.

NWCONFIG-X-50: An attempt to read a primary file system directory entry failed.

Source: NWCONFIG.NLM
Explanation: An error occurred when the program attempted to read a volume.

NWCONFIG-X-51: An attempt to read a mirror file system directory entry failed.

Source: NWCONFIG.NLM
Explanation: An error occurred when the program attempted to read a volume.

NWCONFIG-X-52: A file creation error occurred.

Source: NWCONFIG.NLM
Explanation: NWCONFIG could not write to a DOS or NetWare disk. If it is a diskette, it might be bad, write protected, or not inserted correctly. If it is a hard disk, the proper disk driver might not be loaded, the cabling might not be correct, or the drive parameters might be set incorrectly.
Action: Make sure that there is a writable disk. Then check for the possible explanations listed above. See Resolving Volume I/O Errors in the NW6.5 SP8: Traditional File System Administration Guide. If the problem persists, contact a Novell support provider.

NWCONFIG-X-53: An invalid NetWare file path was found in a configuration file record for the PRODUCTS.DAT file.

Source: NWCONFIG.NLM
Explanation: The SYS:SYSTEM\PRODUCTS.DAT file is corrupted.
Action: Run VREPAIR. If this does not work, delete the corrupted file and reinstall PRODUCTS.DAT. If the problem persists, contact a Novell support provider.

NWCONFIG-X-54: An attempt to read a file failed.

Source: NWCONFIG.NLM
Explanation: NWCONFIG could not read from a DOS or NetWare disk. If it is a diskette, it might be bad, might not be inserted correctly, or might not contain the desired file. If it is a hard disk, the proper disk driver might not be loaded, the cabling might not be correct, or the drive parameters might be set incorrectly.
Action: Make sure that there is a readable disk. Then check for the possible explanations listed above. See Resolving Volume I/O Errors in the NW6.5 SP8: Traditional File System Administration Guide. If the problem persists, contact a Novell support provider.

NWCONFIG-X-55: An attempt to write out the file failed.

Source: NWCONFIG.NLM
Explanation: NWCONFIG could not write to a DOS or NetWare disk. If it is a diskette, it might be bad, write protected, or not inserted correctly. If it is a hard disk, the proper disk driver might not be loaded, the cabling might not be correct, or the drive parameters might be set incorrectly.
Action: Make sure that there is a writable disk. Then check for the possible explanations listed above. See Resolving Volume I/O Errors in the NW6.5 SP8: Traditional File System Administration Guide. If the problem persists, contact a Novell support provider.

NWCONFIG-X-56: Fixed-point number representation number is incorrect. The number must be a single integer or two integers separated by a decimal point.

Source: NWCONFIG.NLM
Explanation: The number entered was not a valid number.
Action: Enter a number of the format 1.2, 3.0, and so forth.

NWCONFIG-X-57: Multiple system volumes exist.

Source: NWCONFIG.NLM
Explanation: NWCONFIG found multiple instances of the system volume (SYS:). This is probably caused by two physical disks, each containing a SYS: volume.
Action: Because a given server might have only one SYS: volume, take one of the physical disks offline.

NWCONFIG-X-58: An unclaimed disk segment exists on logical partition number, starting sector number, size number sectors, name name, type type, flags flags.

Source: NWCONFIG.NLM
Explanation: An internal system error has occurred.
Action: Try again. If the problem persists, contact a Novell support provider.

NWCONFIG-X-59: A system volume could not be created.

Source: NWCONFIG.NLM
Explanation: NWCONFIG could not write to the disk. The proper disk driver might not be loaded, the cabling might be not correct, or the drive parameters might be set incorrectly.

NWCONFIG-X-60: Volume name was not found in volume list.

Source: NWCONFIG.NLM
Explanation: NWCONFIG could not read the disk. The proper disk driver might not be loaded, the cabling might be not correct, or the drive parameters might be set incorrectly.

NWCONFIG-X-61: An invalid pointer to a segment of existing volume name was encountered.

Source: NWCONFIG.NLM
Explanation: An internal system error has occurred.
Action: Try again. If the problem persists, contact a Novell support provider.

NWCONFIG-X-62: The program could not create a new menu or form.

Source: NWCONFIG.NLM
Explanation: This error is probably caused by insufficient memory.
Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

NWCONFIG-X-64: An attempt to display information failed; error code: code. Either memory could not be allocated or the text does not fit on the screen.

Source: NWCONFIG.NLM
Explanation: An internal system error has occurred. Either the server does not have enough memory, or the text does not fit on the screen.
Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide. For information about a specific error code, search the Error Codes online documentation.

NWCONFIG-X-66: An attempt to find a non-conflicting volume name for free space failed.

Source: NWCONFIG.NLM
Explanation: An internal system error has occurred.
Action: Try again. If the problem persists, contact a Novell support provider.

NWCONFIG-X-67: The program was unable to read partition information for logical partition number.

Source: NWCONFIG.NLM
Explanation: The disk is either offline or it is damaged so that the data has been corrupted.
Action: See Disk Errors in the NW 6.5 SP8: Server Operating SystemAdministration Guide. Restore the data from backup after rebuilding the disk partitions.

NWCONFIG-X-70: Logical partition number, segment number, is not contiguous; there is an overlap of number sectors.

Source: NWCONFIG.NLM
Explanation: An internal system error has occurred.
Action: Try again. If the problem persists, contact a Novell support provider.

NWCONFIG-X-71: A new segment does not align correctly with free space. Logical partition number, new segment offset number, size number (sectors), old segment type number, offset number, size number.

Source: NWCONFIG.NLM
Explanation: An internal system error has occurred.
Action: Try again. If the problem persists, contact a Novell support provider.

NWCONFIG-X-73: Two segments with volume name name were found having different block shift factors (number and number).

Source: NWCONFIG.NLM
Explanation: Two volumes with the same name exist, but their block sizes differ.
Action: Bring the disks that contain these volumes online one at a time, rather than at the same time. If one of the volumes is old and no longer needed, delete it to avoid the problem in the future. Two volumes on the same server cannot have the same name.

NWCONFIG-X-74: A resource tag could not be allocated.

Source: NWCONFIG.NLM
Explanation: This error is probably caused by insufficient memory.
Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

NWCONFIG-X-75: Error number was returned by the AppendMultiEditText() function.

Source: NWCONFIG.NLM
Explanation: An internal system error has occurred.
Action: Try again. If the problem persists, contact a Novell support provider.

NWCONFIG-X-76: Error number was returned by the MultiEditText function.

Source: NWCONFIG.NLM
Explanation: An internal system error has occurred.
Action: Try again. If the problem persists, contact a Novell support provider.

NWCONFIG-X-77: An invalid parameter was passed to a function at address address.

Source: NWCONFIG.NLM
Explanation: An internal system error has occurred.
Action: Try again. If the problem persists, contact a Novell support provider.

NWCONFIG-X-78: An attempt to access DOS on this computer was unsuccessful.

Source: NWCONFIG.NLM
Explanation: DOS probably has been removed from this server.
Action: Try bringing up the server without removing DOS. If the problem persists, contact a Novell support provider.

NWCONFIG-X-79: File Name contains an incomprehensible version number (number). The version number should be number.

Source: NWCONFIG.NLM
Explanation: The file is corrupted.
Action: Obtain a new copy of the file.

NWCONFIG-X-80: The program cannot get information about the number of devices available.

Source: NWCONFIG.NLM
Explanation: The proper disk driver might not be loaded, the cabling might not be correct, or the drive parameters might be set incorrectly.

NWCONFIG-X-81: The program’s attempt to evaluate the driver dependency tree failed because of an internal error.

Source: NWCONFIG.NLM
Explanation: An internal system error has occurred.
Action: Get an updated driver or description file. If the problem persists, contact a Novell support provider.

NWCONFIG-X-82: The program cannot read the root directory entry.

Source: NWCONFIG.NLM
Explanation: NWCONFIG could not read from the disk. The proper disk driver might not be loaded, the cabling might not be correct, or the drive parameters might be set incorrectly.

NWCONFIG-X-83: The program cannot make a new NUT client.

Source: NWCONFIG.NLM
Explanation: This error message is probably the result of insufficient memory.

NWCONFIG-X-84: Volume name has multiple segments with different optimization flags (number and number).

Source: NWCONFIG.NLM
Explanation: Two volumes with the same name exist, but their optimization flags are different.
Action: Bring the disks that contain these volumes online one at a time, rather than at the same time. If one of the volumes is old and no longer needed, delete it to avoid the problem in the future. Two volumes on the same server cannot have the same name.

NWCONFIG-X-85: Volume name has multiple segments with different Novell eDirectory object ID’s (number and number).

Source: NWCONFIG.NLM
Explanation: Two volumes with the same name exist, but their object IDs are different.
Action: Bring the disks that contain these volumes online one at a time, rather than at the same time. If one of the volumes is old and no longer needed, delete it to avoid the problem in the future. Two volumes on the same server cannot have the same name.

NWCONFIG-X-86: The program cannot get conflict information. Error code: code

Source: NWCONFIG.NLM
Explanation: An internal system error has occurred.
Action: Try again. If the problem persists, contact a Novell support provider. For information on the specific error code, search the Error Codes online documentation.

NWCONFIG-X-87: Warning: The disk cannot be locked because it is currently being used by another process. A mounted volume may be using it. The partition table cannot be modified at this time.

Source: NWCONFIG.NLM
Explanation: The disk cannot be locked because it is currently being used by another process. A mounted volume might be using it.
Action: Wait to see if the process releases the device, then retry the action. If there is a disk device error, unload NLM programs (except device drivers) that might be using the disk. Then dismount volumes from the disk. If these efforts fail, try loading MONITOR, deleting all user connections, and disabling logins.

NWCONFIG-X-94: Overlapping disk segments were detected while free segments were being added.

Source: NWCONFIG.NLM
Explanation: An internal system error has occurred.
Action: Try again. If the problem persists, contact a Novell support provider.

NWCONFIG-X-95: Abend: The GetVolumeNumber function was called with an unmounted volume.

Source: NWCONFIG.NLM
Explanation: An internal system error has occurred. The installation process has terminated prematurely, and NWCONFIG will be unloaded.
Action: Try again. If the problem persists, contact a Novell support provider.

NWCONFIG-X-96: Abend: The program attempted to access FAT entry number, but the highest FAT entry is number.

Source: NWCONFIG.NLM
Explanation: An internal system error has occurred. The installation process has terminated prematurely, and NWCONFIG will be unloaded.
Action: Try again. If the problem persists, contact a Novell support provider.

NWCONFIG-X-97: Abend: File block sequence number was not found in the FAT chain starting at entry number.

Source: NWCONFIG.NLM
Explanation: An internal system error has occurred. The installation process has terminated prematurely, and NWCONFIG will be unloaded.
Action: Try again. If the problem persists, contact a Novell support provider.

NWCONFIG-X-98: Abend: Block number number is invalid for volume name.

Source: NWCONFIG.NLM
Explanation: An internal system error has occurred. The installation process has terminated prematurely, and NWCONFIG will be unloaded.
Action: Try again. If the problem persists, contact a Novell support provider.

NWCONFIG-X-99: Abend: An incorrect sequence number was encountered in the FAT block while a bad block was being redirected.

Source: NWCONFIG.NLM
Explanation: An internal system error has occurred. The installation process has terminated prematurely, and NWCONFIG will be unloaded.
Action: Try again. If the problem persists, contact a Novell support provider.

NWCONFIG-X-100: Abend: The program attempted to assign a FAT block to an unreachable block.

Source: NWCONFIG.NLM
Explanation: An internal system error has occurred. The installation process has terminated prematurely, and NWCONFIG will be unloaded.
Action: Try again. If the problem persists, contact a Novell support provider.

NWCONFIG-X-101: Abend: An error occurred in the FAT entry sequence of the last primary FAT block.

Source: NWCONFIG.NLM
Explanation: An internal system error has occurred. The installation process has terminated prematurely, and NWCONFIG will be unloaded.
Action: Try again. If the problem persists, contact a Novell support provider.

NWCONFIG-X-102: Abend: An error occurred in the in FAT entry sequence of last mirror FAT block.

Source: NWCONFIG.NLM
Explanation: An internal system error has occurred. The installation process has terminated prematurely, and NWCONFIG will be unloaded.
Action: Try again. If the problem persists, contact a Novell support provider.

NWCONFIG-X-103: Abend: The previous volume segment could not be found.

Source: NWCONFIG.NLM
Explanation: NWCONFIG could not read from the disk. The proper disk driver might not be loaded, the cabling might not be correct, or the drive parameters might be set incorrectly.

NWCONFIG-X-104: Abend: An invalid volume segment was found in the disk segment list.

Source: NWCONFIG.NLM
Explanation: Either part of a volume is missing, or the volume segment is corrupted. The remainder of the volume might be offline.

NWCONFIG-X-106: The operation aborted because CLIB.NLM could not be loaded.

Source: NWCONFIG.NLM
Explanation: CLIB.NLM could not be loaded. This could be caused by insufficient memory or conflicts with exported functions.
Action: The system console screen should indicate the cause of CLIB not being loaded. Examine this screen to determine the necessary steps for resolving the conflict. If the problem is due to insufficient memory, increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide. If the problem persists, contact a Novell support provider.

NWCONFIG-X-107: The operation aborted because BTRIEVE.NLM could not be loaded.

Source: NWCONFIG.NLM
Explanation: BTRIEVE.NLM could not be loaded. This could be caused by insufficient memory or conflicts with exported functions.
Action: The system console screen should indicate the cause of Btrieve not being loaded. Examine this screen to determine the necessary steps for resolving the conflict. If the problem is due to insufficient memory, increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide. If the problem persists, contact a Novell support provider.

NWCONFIG-X-108: The operation aborted because the SYS:SYSTEM\PRODUCTS.DAT file could not be accessed.

Source: NWCONFIG.NLM
Explanation: To install products, the above file must be accessible.
Action: Make sure volume SYS: is mounted. (Switch to the console screen and enter volumes.) If it is, restore the PRODUCTS.DAT file from backup or from some other source; then retry the action. If the problem persists, contact a Novell support provider.

NWCONFIG-X-109: BTRIEVE error number occurred while function number was being executed.

Source: NWCONFIG.NLM
Explanation: NWCONFIG received an error from Btrieve.
Action: Look up the error in a Btrieve manual and take appropriate action, or contact a Novell support provider.

NWCONFIG-X-110: This product has no configuration options.

Source: NWCONFIG.NLM
Explanation: There are no options for configuration.
Action: Pressing Enter is not a supported action for this product. Try reinstalling the product and configure it differently. If the problem persists, contact a Novell support provider.

NWCONFIG-X-111: This product cannot be removed.

Source: NWCONFIG.NLM
Explanation: The nature of the product prevents it from being removed.
Action: Do not try to remove this product.

NWCONFIG-X-113: File name cannot be written to. One of the following problems may exist: (1) The target disk is full. (2) The disk is write-protected.

Source: NWCONFIG.NLM
Action: Insert a disk with more free space on it. If the disk is write-protected, remove the write protection.

NWCONFIG-X-114: File name cannot be created. One of the following problems may exist: (1) The disk is full. (2) The disk is write-protected. (3) The path specification is invalid.

Source: NWCONFIG.NLM
Action: Insert a disk with more free space on it. If the disk is write-protected, remove the write protection, or specify a different path.

NWCONFIG-X-115: The operation aborted because BTRIEVE.NLM could not be accessed.

Source: NWCONFIG.NLM
Explanation: Although BTRIEVE.NLM is loaded, Btrieve could not be accessed. The installation process has terminated prematurely, and NWCONFIG will be unloaded.
Action: Make sure that the version of BTRIEVE.NLM is compatible with the NetWare version of NWCONFIG. Unload and reload BTRIEVE.NLM to see if the problem persists. If the problem persists, contact a Novell support provider.

NWCONFIG-X-116: Warning: The volume will be deleted and all its contents lost if you indicate Yes in the Confirm box that follows this message.

Source: NWCONFIG.NLM
Explanation: As indicated, this is a warning message.
Action: Select Yes only to delete the volume.

NWCONFIG-X-117: A memory corruption problem has occurred. Program operation cannot continue.

Source: NWCONFIG.NLM
Explanation: An internal system error has occurred. The installation process has terminated prematurely, and NWCONFIG will be unloaded.
Action: Try again. If the problem persists, contact a Novell support provider.

NWCONFIG-X-118: An attempt to free unallocated memory has failed. Program operation cannot continue.

Source: NWCONFIG.NLM
Explanation: An internal system error has occurred. The installation process has terminated prematurely, and NWCONFIG will be unloaded.
Action: Try again. If the problem persists, contact a Novell support provider.

NWCONFIG-X-121: The Wait message is too large to be displayed.

Source: NWCONFIG.NLM
Explanation: An internal system error has occurred.
Action: Try again. If the problem persists, contact a Novell support provider.

NWCONFIG-X-124: Warning: The disk partition cannot be locked because it is currently being used by another process. A mounted volume may be using it. The partition cannot be modified at this time.

Source: NWCONFIG.NLM
Action: Wait to see if the process releases the device, then retry the action. If there is a disk device error, unload NLM programs (except device drivers) that might be using the disk. Then dismount volumes from the disk. If these efforts fail, try loading MONITOR, deleting all user connections, and disabling logins.

NWCONFIG-X-126: The option failed.

Source: NWCONFIG.NLM
Explanation: This is an internal error probably caused by insufficient memory.
Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

NWCONFIG-X-127: The NetWare Loadable Module name could not be loaded.

Source: NWCONFIG.NLM
Explanation: The reason the NLM could not be loaded will be displayed on the system console screen.
Action: Take action depending upon the message displayed on the system console screen. If memory could not be allocated, increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

NWCONFIG-X-128: The program cannot get a process resource tag.

Source: NWCONFIG.NLM
Explanation: This error probably is caused by insufficient memory.
Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

NWCONFIG-X-129: The program cannot get a non-movable memory resource tag.

Source: NWCONFIG.NLM
Explanation: This error probably is caused by insufficient memory.
Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

NWCONFIG-X-130: The program cannot get an Alloc resource tag.

Source: NWCONFIG.NLM
Explanation: This error probably is caused by insufficient memory.
Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

NWCONFIG-X-131: The program cannot get resource tags.

Source: NWCONFIG.NLM
Explanation: This error probably is caused by insufficient memory.
Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

NWCONFIG-X-132: The program cannot get a screen resource tag.

Source: NWCONFIG.NLM
Explanation: This error probably is caused by insufficient memory.
Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

NWCONFIG-X-133: The program cannot get a timer resource tag.

Source: NWCONFIG.NLM
Explanation: This error probably is caused by insufficient memory.
Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

NWCONFIG-X-134: The program cannot get an AES resource tag.

Source: NWCONFIG.NLM
Explanation: This error probably is caused by insufficient memory.
Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

NWCONFIG-X-135: The program cannot get an IPX Socket resource tag.

Source: NWCONFIG.NLM
Explanation: This error probably is caused by insufficient memory.
Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

NWCONFIG-X-136: The program cannot get memory for the installation stack.

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

NWCONFIG-X-137: The program cannot get an event resource tag.

Source: NWCONFIG.NLM
Explanation: This error probably is caused by insufficient memory.
Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

NWCONFIG-X-138: The program cannot open a screen.

Source: NWCONFIG.NLM
Explanation: This error probably is caused by insufficient memory.
Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

NWCONFIG-X-139: A partition table does not exist on this drive. If you continue and create a disk partition, the table will be created for you.

Source: NWCONFIG.NLM
Explanation: The installation program does not see a partition table on the drive.
Action: If this is a new drive, or if there is no disk partition on the drive, continue with the installation. If there is a disk partition and you want to preserve the data on the drive, indicate No in the box that follows.

NWCONFIG-X-140: This device is not writable.

Source: NWCONFIG.NLM
Explanation: The partition table on a read-only device cannot be created nor deleted. The information on the device cannot be changed.
Action: No action is necessary, unless you want to create or delete the partition table on a device that is writable.

NWCONFIG-X-141: No partitions can be viewed on a tape device.

Source: NWCONFIG.NLM
Explanation: Tape devices do not have a partition table.
Action: No action is possible.

NWCONFIG-X-142: No NetWare partitions are on this CD-ROM device.

Source: NWCONFIG.NLM
Explanation: A CD-ROM device does not have a NetWare disk partition.
Action: The installation program will not show the disk partition table of a CD-ROM device which has no NetWare partition. Select a different device.

NWCONFIG-X-144: File name cannot be unpacked. Error: description.

Source: NWCONFIG.NLM
Explanation: This error could result from inadequate disk space, from I/O errors, or from file corruption.
Action: Do one or both of the following:

If the problem persists, contact a Novell support provider.

NWCONFIG-X-145: Four disk partitions are already on this drive.

Source: NWCONFIG.NLM
Explanation: A partition table was designed to have only four entries. You are trying to define a fifth entry in the partition table.
Action: Determine which three disk partitions are the most important and delete all others. Retry the action.

NWCONFIG-X-146: No NetWare disk partitions (post-NetWare 286 partitions) are on this drive. Create one before continuing.

Source: NWCONFIG.NLM
Explanation: The user is trying to edit a partition table that does not contain a NetWare 3.x or NetWare 4.x disk partition.
Action: Use ConsoleOne to create a partition.

NWCONFIG-X-147: A NetWare disk partition already exists on this drive.

Source: NWCONFIG.NLM
Explanation: A physical disk drive can only have one NetWare partition. This message appears when attempting to create a NetWare disk partition on a disk that already has one.
Action: If a new NetWare disk partition must be created, delete the existing NetWare disk partition. This destroys the data on the current NetWare disk partition.

NWCONFIG-X-148: No free space is available on this drive for a NetWare disk partition.

Source: NWCONFIG.NLM
Explanation: Either there are no free areas on the disk, or the free areas are too small to be of any benefit.
Action: Get another disk, or delete one of the existing partitions.

NWCONFIG-X-149: The NetWare disk partition could not be located. The selected action cannot be completed.

Source: NWCONFIG.NLM
Explanation: The NetWare disk partition was not created correctly.

NWCONFIG-X-150: Warning: No valid entries for volume name were found on disk.

Source: NWCONFIG.NLM
Explanation: Volume name was not found.
Action: Make sure the volume exists and is mounted. Make sure the disk is functioning correctly; see Disk Errors in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

NWCONFIG-X-151: Warning: More than one sync entry exists for volume name.

Source: NWCONFIG.NLM
Explanation: Multiple disk devices are online that contain volumes with the same name.
Action: Bring the disks that contain these volumes online one at a time, rather than at the same time. If one of the volumes is old and no longer needed, delete it to avoid the problem in the future. Two volumes on the same server cannot have the same name.

154: No accessible drives have NetWare partitions. Proceeding to locate NSS volumes.

Source: NWCONFIG.NLM
Explanation: The installation program cannot find a NetWare disk partition.
Action: If no disk partitions have been created, make one.

156: Volume name already exists. Try another name.

Source: NWCONFIG.NLM
Explanation: A volume name was entered that is already defined on the server.
Action: Use a unique volume name.

NWCONFIG-X-157: Volume name cannot be created.

Source: NWCONFIG.NLM
Explanation: An error probably occurred while allocating memory, or an error occurred while accessing the disk.
Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

NWCONFIG-X-158: The segment link cannot be located.

Source: NWCONFIG.NLM
Explanation: An internal system error has occurred.
Action: Contact a Novell support provider.

NWCONFIG-X-159: Warning: Volume name has multiple sync entries. It cannot be deleted at this time.

Source: NWCONFIG.NLM
Explanation: Multiple disk devices are online that contain volumes with the name shown in the message.
Action: Bring the disks that contain these volumes online one at a time, rather than at the same time. If one of the volumes is old and no longer needed, delete it to avoid the problem in the future. Two volumes on the same server cannot have the same name.

NWCONFIG-X-160: Warning: Adjacent disk segments do not line up.

Source: NWCONFIG.NLM
Explanation: An internal system error has occurred.
Action: Try again. If the problem persists, contact a Novell support provider.

NWCONFIG-X-161: Volume name is currently mounted and cannot be deleted.

Source: NWCONFIG.NLM
Explanation: A volume must be unmounted before it can be deleted.
Action: Dismount the volume; then delete the volume.

NWCONFIG-X-163: A volume must be dismounted before its name can be changed.

Source: NWCONFIG.NLM
Action: Dismount the volume; then rename it.

NWCONFIG-X-164: No available NetWare disk partitions are compatible with the selected drive.

Source: NWCONFIG.NLM
Explanation: No disk partitions were found of suitable size to be mirrored with the selected disk partition (drive).
Action: Mirroring requires at least two disks that contain disk partitions of the same size. You might have to install an additional disk to mirror. If this is not the problem, there might be a disk problem. See Disk Errors in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

NWCONFIG-X-165: Warning: The selected NetWare partition contains NetWare volume information. To complete the selected operation, delete the volume information.

Source: NWCONFIG.NLM
Action: Delete all volumes on the NetWare disk partition before deleting the disk partition.

NWCONFIG-X-166: THIS NETWARE DISK PARTITION IS CURRENTLY MIRRORED with other NetWare partitions. You may now choose to remove this partition; however it is recommended that you first unmirror this partition.

Source: NWCONFIG.NLM
Action: Unmirror the NetWare disk partition.

NWCONFIG-X-168: The maximum number of NetWare disk partitions (8) has already been assigned to this mirrored partition group.

Source: NWCONFIG.NLM
Action: Do not try to mirror more than eight disks.

NWCONFIG-X-169: The mirror group contains an unavailable disk partition which must be removed from the group before any other partitions can be removed.

Source: NWCONFIG.NLM
Explanation: A disk partition in the mirrored group cannot be accessed because it is not synchronized.
Action: To resynchronize the unsynchronized disk partition, press F3. You might have to delete the unreachable, unsynchronized drive from the mirror set.

NWCONFIG-X-170: Out-of-sync disk partitions in the group must be removed before you can proceed.

Source: NWCONFIG.NLM
Explanation: One or more disk partitions are not synchronized. Installation cannot proceed.
Action: Remove the unsynchronized disk partitions.

NWCONFIG-X-171: Volume SYS: must be mounted before you can proceed.

Source: NWCONFIG.NLM
Explanation: Installation cannot be performed until volume SYS: is mounted.
Action: Mount the SYS: volume.

NWCONFIG-X-172: The selected disk cannot be tested at this time. Insufficient memory is available to begin another test.

Source: NWCONFIG.NLM
Explanation: Either a previous test is being conducted on the disk, or the server does not have enough memory.
Action: Wait until a previous test is completed. If necessary, increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

NWCONFIG-X-174: The drive is not currently being tested.

Source: NWCONFIG.NLM
Explanation: You tried to stop a test that was not being conducted.
Action: Make sure that the correct drive is selected.

NWCONFIG-X-175: Disk surface testing is currently being done. If you leave NWCONFIG, the testing will be terminated.

Source: NWCONFIG.NLM
Explanation: You tried to leave NWCONFIG during a surface test.
Action: Wait until surface testing is completed.

NWCONFIG-X-176: Hot Fix is not currently installed on the selected disk. Hot Fix needs to be installed for this function.

Source: NWCONFIG.NLM
Explanation: There is no Hot Fix redirection area on the NetWare partition, or there might be no NetWare partition at all.
Action: If there is no NetWare partition, create a NetWare partition from free space. Be sure to specify a Hot Fix redirection area when you create the partition. If there is a NetWare partition, but no Hot Fix redirection area, you can add a Hot Fix redirection area, but you must delete the volumes on the partition. Back up volume data to another device, delete the volumes, create the Hot Fix redirection area, then re-create the volumes and restore the data.

NWCONFIG-X-178: Two volume segments with the same sync value have mismatched data. message

Source: NWCONFIG.NLM
Explanation: NWCONFIG found multiple instances of the same volume. This probably occurred because two physical disks each contain a volume with the same name.
Action: Because each volume on a given server must have a unique name, take one of the physical disks offline. You might have to delete one of the volumes and then bring the disks online simultaneously.

NWCONFIG-X-179: Volume segment entry number on disk_description is invalid: reason Check to be sure all disk drivers are loaded and configured properly.

Source: NWCONFIG.NLM
Explanation: A segment of a volume is corrupted.
Action: See Disk Errors in the NW 6.5 SP8: Server Operating SystemAdministration Guide. You might have to re-create the volume.

NWCONFIG-X-180: Warning: An overlapping segment entry was found starting at sector number on name for volume name segment number. Check to be sure all disk drivers are configured properly, and that multiple volumes do not have the same name.

Source: NWCONFIG.NLM
Explanation: Disk data might be corrupted, or an internal error might have occurred.
Action: See Disk Errors in the NW 6.5 SP8: Server Operating SystemAdministration Guide. If the problem persists, contact a Novell support provider.

NWCONFIG-X-181: A mirror mismatch was detected for FAT block sequence number.

Source: NWCONFIG.NLM
Explanation: Errors have occurred in the volume structure.

NWCONFIG-X-182: A FAT table length error has occurred on volume name. There should be number FAT blocks, but the FAT table length is number blocks.

Source: NWCONFIG.NLM
Explanation: Errors have occurred in the volume structure.

NWCONFIG-X-183: The volume cannot be locked at this time because another process is using it. Perhaps a surface test is being performed. The selected action cannot be completed.

Source: NWCONFIG.NLM
Action: Wait to see if the process releases the device, then retry the action. If there is a disk device error, unload NLM programs (except device drivers) that might be using the disk. Then dismount volumes from the disk. If these efforts fail, try loading MONITOR, deleting all user connections, and disabling logins.

NWCONFIG-X-184: A mirror mismatch was detected for file system directory block sequence number.

Source: NWCONFIG.NLM
Explanation: Errors have occurred in the file system.

NWCONFIG-X-185: Volume definition tables on disk_description are out of sync.

Source: NWCONFIG.NLM
Explanation: A disk corruption error has occurred.

NWCONFIG-X-186: Drive name is unusable.

Source: NWCONFIG.NLM
Explanation: Four attempts were made to read information on the drive and all failed.

NWCONFIG-X-187: Warning: The name of volume old_name was changed to both new_name and second_new_name.

Source: NWCONFIG.NLM
Explanation: An internal system error has occurred.
Action: Contact a Novell support provider.

NWCONFIG-X-188: Warning: The name of volume old_name was changed to new_name and the name of volume old_name was changed to new_name.

Source: NWCONFIG.NLM
Explanation: An internal system error has occurred.
Action: Try again. If the problem persists, contact a Novell support provider.

NWCONFIG-X-189: Warning: Volume name has multiple sync definitions. (Multiple volumes have the same name.) All definitions except number have been discarded.

Source: NWCONFIG.NLM
Explanation: More than one volume was found with the same name. All definitions but one were removed from memory. The volumes are still intact on disk.
Action: Because each volume on a given server must have a unique name, take one of the physical disks offline. You might have to delete one of the volumes and then bring the disks online simultaneously.

NWCONFIG-X-190: Volume name has invalid segment number. This may be due to multiple volumes having the same name, or one or more drivers not being loaded and configured properly.

Source: NWCONFIG.NLM
Explanation: A volume segment was discovered that is either corrupted or is only a part of a complete volume.
Action: Make sure that all segments of the volume are online and drivers are configured correctly. If this does not solve the problem, see Disk Errors in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

NWCONFIG-X-191: Two or more volume were found which have the same name. (Volume name has multiple definitions for segment number.) This could be due to formerly mirrored volumes being synchronized separately, then brought online together. If this is the case, unload the drivers or take the server down, and then bring the separate disks online one at a time. Rename the redundant volumes as they are brought online, so that there is not a name conflict.

Source: NWCONFIG.NLM
Explanation: More than one volume was found with the same name.
Action: Because each volume on a given server must have a unique name, take one of the physical disks offline. You might have to delete one of the volumes and then bring the disks online simultaneously.

NWCONFIG-X-192: Warning: Volume name is missing segment number. Check to be sure all disk drivers are loaded and configured properly.

Source: NWCONFIG.NLM
Explanation: An incomplete volume has been discovered. A segment is missing.
Action: Make sure that all segments of the volume are online. Make sure disk drivers are configured correctly. Troubleshoot the disk. See Disk Errors in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

NWCONFIG-X-193: A volume segment mismatch has occurred. Volume name segment number ends at block number, and segment number starts at block number. Check to be sure all disk drivers are loaded and configured properly, and that multiple volumes do not have the same name.

Source: NWCONFIG.NLM
Explanation: Volume segments were discovered that are inconsistent or corrupted.
Action: Make sure that all segments of the volume are online, volume names are unique, and all disk drivers are configured correctly. See Disk Errors in the NW 6.5 SP8: Server Operating SystemAdministration Guide. You might have to delete and re-create all volumes.

NWCONFIG-X-194: The first segment of volume name, segment number, does not start at block 0. Check to be sure all disk drivers are loaded and configured properly, and that multiple volumes do not have the same name.

Source: NWCONFIG.NLM
Explanation: An incomplete volume was discovered. One or more segments is missing.
Action: Make sure that all segments of the volume are online, all volume names are unique, and all sure disk drivers are configured correctly. See Disk Errors in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

NWCONFIG-X-195: The last segment of volume name, segment number, ends at block number instead of number. Check to be sure all disk drivers are loaded and configured properly, and that multiple volumes do not have the same name.

Source: NWCONFIG.NLM
Explanation: A volume segment was discovered that is inconsistent or corrupted.
Action: Make sure that all segments of the volume are online, all volume names are unique, and all sure disk drivers are configured correctly. See Disk Errors in the NW 6.5 SP8: Server Operating SystemAdministration Guide. You might have to delete and re-create all volumes.

NWCONFIG-X-196: The definition for volume name is invalid. Check to be sure all disk drivers are loaded and configured properly, and that multiple volumes do not have the same name.

Source: NWCONFIG.NLM
Explanation: A corrupted or incomplete volume was found.
Action: Make sure that all segments of the volume are online, all volume names are unique, and all sure disk drivers are configured correctly. See Disk Errors in the NW 6.5 SP8: Server Operating SystemAdministration Guide. You might have to delete and re-create the volume.

NWCONFIG-X-197: Volume name was not found in the list of existing volumes.

Source: NWCONFIG.NLM
Explanation: An internal system error has occurred.
Action: Try again. If the problem persists, contact a Novell support provider.

NWCONFIG-X-198: The definition for sync (or instance) number of volume name was removed.

Source: NWCONFIG.NLM
Explanation: Multiple volumes with the same name were found. One of them was discarded from memory. The data is still intact on disk.
Action: Because each volume on a given server must have a unique name, take one of the physical disks offline. You might have to delete one of the volumes and then bring the disks online simultaneously.

NWCONFIG-X-199: Volume name sync (or instance) number was not found in the volume’s sync list.

Source: NWCONFIG.NLM
Explanation: An internal system error has occurred.
Action: Contact a Novell support provider.

NWCONFIG-X-200: Name change update for volume old_name to new_name is being completed.

Source: NWCONFIG.NLM
Explanation: The volume name has been changed.
Action: None. This message is for information only.

NWCONFIG-X-207: The name name is reserved and cannot be used for a volume.

Source: NWCONFIG.NLM
Explanation: A volume name was entered that is reserved and cannot be used. The names currently reserved are PIPE and CON.
Action: Choose a different name.

NWCONFIG-X-208: The volume definition table on name has invalid entries. Check to be sure all disk drivers are loaded and configured properly.

Source: NWCONFIG.NLM
Explanation: The data on the disk is corrupted or unreadable.
Action: A confirmation question will follow this message. Choosing to fix the volume definition table will destroy the invalid entries. If you think that valid data exists on the volumes in question, do not fix the table. See Disk Errors in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

NWCONFIG-X-209: The selected disk is no longer valid.

Source: NWCONFIG.NLM
Explanation: The installation program can no longer access the disk drive.

NWCONFIG-X-210: This volume is not currently mounted.

Source: NWCONFIG.NLM
Explanation: The program tried to access a volume that was not mounted.
Action: Mount the volume and try again. You might have to mount the volume by entering mount volume_name at the system console.

NWCONFIG-X-211: Volume name could not be mounted. Refer to the system console screen for an error report.

Source: NWCONFIG.NLM
Explanation: NWCONFIG made a request to the operating system to mount the volume, but the request failed for some reason.
Action: See the console screen error message.

NWCONFIG-X-212: The volume is already mounted.

Source: NWCONFIG.NLM
Explanation: The user tried to mount a volume that is already mounted.
Action: None. This message is for information only.

NWCONFIG-X-213: HotFix could not be installed on the drive. Error code: code.

Source: NWCONFIG.NLM
Explanation: NWCONFIG made a request to the operating system to create Hot Fix on the drive, but the request failed.
Action: For information on the specific error code, search the Error Codes online documentation.

NWCONFIG-X-214: Drive information could not be read.

Source: NWCONFIG.NLM
Explanation: An error occurred when the program attempted to read information from a disk drive.
Explanation: Make sure that the drive can be accessed. See Disk Errors in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

NWCONFIG-X-214: Hot Fix for the boot partition could not be installed on the drive. Error code: code.

Source: NWCONFIG.NLM
Explanation: While writing out the Hot Fix information on the boot partition, the operating system reported an error to NWCONFIG.

NWCONFIG-X-215: The drive could not be set up for mirroring.

Source: NWCONFIG.NLM
Explanation: An error occurred when the program attempted to write mirroring information to a disk drive.
Action: Make sure that the drive can be accessed, and that a NetWare disk partition exists on it. See Disk Errors in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

NWCONFIG-X-216: You must unmirror the drive before it can be tested.

Source: NWCONFIG.NLM
Action: Unmirror the drive.

NWCONFIG-X-218: Warning: The selected disk partition may contain valuable data; all data on the partition will be lost.

Source: NWCONFIG.NLM
Explanation: You made a request to delete a non-NetWare disk partition. This is simply a warning message.
Action: Make sure that you want to delete the disk partition before proceeding. The data is lost if the partition is deleted.

NWCONFIG-X-220: The partition table on drive number appears to be invalid. It is possible that you have not chosen the correct driver. If valid data does exist on this drive, and you do not want it destroyed, indicate No in the Confirm box that follows this message.

Warning: If you indicate Yes to recreating the partition table, all existing partitions (DOS partitions, NetWare partitions, etc.) will be deleted and all existing disk data will be lost.

Source: NWCONFIG.NLM
Explanation: The operating system has determined that the partition table is invalid and cannot be recovered.
Action: Follow the directions in the warning message. Answering Yes to the confirmation question will create a new disk partition and destroy all data on the old partition.

NWCONFIG-X-221: This disk partition is out of date with respect to other mirror groups and must be resynchronized before it can be used.

Source: NWCONFIG.NLM
Explanation: The disk partition cannot be accessed because it is not synchronized.
Action: Resynchronize the disk partition by using F3 in the mirror list.

NWCONFIG-X-225: This segment exists on disk. Its size cannot be modified unless you delete and reassign it.

Source: NWCONFIG.NLM
Explanation: You are in the Volume Disk Segment List and are trying to edit the size or name of a segment that is already assigned.
Action: To rename a segment, go to the volume list and edit the volume parameters, changing the volume name.

NWCONFIG-X-226: The system volume (SYS:) does not exist. Installation cannot be completed without it.

Source: NWCONFIG.NLM
Explanation: System volume SYS: must be mounted before NWCONFIG.NLM can be used.
Action: Mount the SYS: volume.

NWCONFIG-X-228: File name is out of date. (Its version numbers are number and number, the expected values are number and number, respectively.) If you are installing from diskette, insert a diskette containing an updated file; otherwise, update the file and reinstall).

Source: NWCONFIG.NLM
Explanation: The specified installation script file is out of date.
Action: Get a current version of the script file.

NWCONFIG-X-230: File copying was cancelled.

Source: NWCONFIG.NLM
Explanation: Copying from a diskette has been cancelled.
Action: None. This message is for information only.

NWCONFIG-X-231: Free space cannot be deleted. Move the cursor to a valid volume entry and then press Del.

Source: NWCONFIG.NLM
Explanation: The user attempted to delete space that is not assigned to an existing volume. Only volume space can be deleted.
Action: Follow the suggestions in the message.

NWCONFIG-X-232: An error occurred while parsing file name, line number, at or near word or symbol word_or_character. Error description: description

Source: NWCONFIG.NLM
Explanation: A syntax error occurred in a script or description file.
Action: If you are writing the script or description file, see the documentation. If not, try again. If the problem persists, contact a Novell support provider.

NWCONFIG-X-233: File name was not found.

Source: NWCONFIG.NLM
Explanation: The specified file was not found during the copy phase.
Action: Try again. If the problem persists, contact a Novell support provider.

NWCONFIG-X-234: The name volume_name already exists in the segments list.

Source: NWCONFIG.NLM
Explanation: The volume name that the segment is being assigned to already exists.
Action: Choose a new name.

NWCONFIG-X-235: File name cannot be opened. Error: description.

Source: NWCONFIG.NLM
Explanation: This error could result from inadequate disk space on a NetWare volume or from a corrupted diskette.
Action: See Resolving Volume I/O Errors in the NW6.5 SP8: Traditional File System Administration Guide. If the error occurred while accessing a diskette, make sure all files can be read from a workstation. If the problem persists, contact a Novell support provider.

NWCONFIG-X-236: The maximum number of segments on this disk has been reached. If you want to add a new segment, first delete another segment.

Source: NWCONFIG.NLM
Explanation: Only one NetWare disk partition can exist on a given disk, and only eight segments can exist on a given disk partition. The disk already has eight segments on it.
Action: Delete a segment before creating a new one.

NWCONFIG-X-239: The disk (logical partition number) is locked and cannot be accessed because another process is using it.

Source: NWCONFIG.NLM
Explanation: Another process or NLM is using the disk partition.
Action: Wait to see if the process releases the device then retry the action. If there is a disk device error, unload NLM programs (except device drivers) that might be using the disk and dismount volumes from the disk. If these efforts fail, try loading MONITOR, deleting all user connections, and disabling logins.

NWCONFIG-X-240: Volume name cannot be locked because another process is using it. Volume configuration cannot proceed.

Source: NWCONFIG.NLM
Explanation: Another process or NLM is using the volume.
Action: Wait to see if the process releases the device then retry the action. If there is a disk device error, unload NLM programs (except device drivers) that might be using the disk and dismount volumes from the disk. If these efforts fail, try loading MONITOR, deleting all user connections, and disabling logins.

NWCONFIG-X-242: File name cannot be read. Error: description.

Source: NWCONFIG.NLM
Explanation: This error could result from inadequate disk space or from other I/O errors.
Action: See Resolving Volume I/O Errors in the NW6.5 SP8: Traditional File System Administration Guide. If the error occurred while accessing a diskette, make sure all files can be read from a workstation. If not, contact a Novell support provider.

NWCONFIG-X-243: The system volume is too small (number MB, number sectors). It should be at least number MB (number sectors).

Source: NWCONFIG.NLM
Explanation: The SYS: volume created is less than 25 MB. It should be at least 25 MB.
Action: If possible, make SYS: at least 25 MB. If this cannot be done, continue with the installation.

NWCONFIG-X-244: The path you specified corresponds to a remote server and is not supported.

Source: NWCONFIG.NLM
Explanation: You entered a remote server path. Remote paths are not supported.
Action: Enter a local path.

NWCONFIG-X-245: An error occurred during parsing of file name on disk disk_description, line number, at or near word or symbol name. Error description: description

Source: NWCONFIG.NLM
Explanation: A syntax error was encountered while reading the above file.
Action: If you are writing the script or description file, follow the specifications for creating the file. If you are not creating the file, contact a Novell support provider.

NWCONFIG-X-246: File name cannot be erased. Error: description.

Source: NWCONFIG.NLM
Explanation: This error could result from file I/O errors or from a diskette being write-protected.
Action: If a diskette is being accessed, make sure it is writable. See Resolving Volume I/O Errors in the NW6.5 SP8: Traditional File System Administration Guide.

NWCONFIG-X-247: NLM_name did not finish loading in the time allowed (number seconds). Control will be switched to the system console screen, where you may either see it finish or enter information to finish loading it.

Source: NWCONFIG.NLM
Explanation: The specified NLM did not load in the time allotted. The NLM might be working properly and perhaps no error occurred.
Action: To view the system console screen and determine whether an error occurred, or to enter information, press Enter. If no error has occurred, proceed normally.

NWCONFIG-X-248: NLM_name did not load. Control will be switched to the system console screen, where you may see the error.

Source: NWCONFIG.NLM
Explanation: The specified NLM failed to load.
Action: To view the system console screen and determine what error has occurred, press Enter.

NWCONFIG-X-249: NLM_name did not finish unloading in the time allowed (number seconds). Control will be switched to the system console screen, where you may either see it finish or enter information to finish loading it.

Source: NWCONFIG.NLM
Explanation: The specified NLM did not unload in the time allotted. You might have to enter information to complete the unload process.
Action: To view the system console screen and see if an error occurred, or to enter information, press Enter. If no error has occurred, proceed normally.

NWCONFIG-X-250: NLM_name did not unload. Control will be switched to the system console screen, where you may see the error.

Source: NWCONFIG.NLM
Explanation: The specified NLM failed to unload.
Action: To view the system console screen and determine what error has occurred, press Enter.

NWCONFIG-X-252: Directory directory_name cannot be created. Error: description.

Source: NWCONFIG.NLM
Explanation: The specified directory could not be created.

NWCONFIG-X-254: Directory name cannot be removed. Error: description.

Source: NWCONFIG.NLM
Explanation: The directory is in use or is not empty.
Action: Make sure that the directory is empty before trying to remove it.

NWCONFIG-X-256: NetWare path path is invalid. Specify a fixed or diskette drive path.

Source: NWCONFIG.NLM
Explanation: NetWare paths cannot be used for this operation.
Action: Specify a drive path for a diskette or fixed disk.

NWCONFIG-X-257: The volume label on this diskette (description) matches the volume label of one of the installation diskettes. Change the volume label on the diskette.

Source: NWCONFIG.NLM
Explanation: The volume label on your diskette is the same as a volume label on one of the NetWare installation diskettes.
Action: Change the volume label on your diskette.

NWCONFIG-X-258: This diskette cannot be written to.

Source: NWCONFIG.NLM
Explanation: The diskette is write-protected or defective.
Action: Make the diskette writable or obtain a new diskette.

NWCONFIG-X-259: A file copy error occurred. Error: description.

Source: NWCONFIG.NLM
Explanation: This error could result from inadequate disk space or from other I/O errors.

NWCONFIG-X-260: A write error occurred on file name. Error: description.

Source: NWCONFIG.NLM
Explanation: This error could result from inadequate disk space or from other I/O errors.

NWCONFIG-X-261: An attempt to combine files into target file filename failed. Error: description.

Source: NWCONFIG.NLM
Explanation: This error could result from inadequate disk space or from other I/O errors.

NWCONFIG-X-262: No installation file (*.IPS or PINSTALL.NLM) could be found at path path.

Source: NWCONFIG.NLM
Explanation: The necessary product installation files are not locatable in the specified path.
Action: Specify a new path that points to the directory containing PINSTALL.NLM or a file with the extension IPS. If you are loading the file from a diskette, insert the installation diskette containing this file.

NWCONFIG-X-263: Installation for the selected item has been aborted.

Source: NWCONFIG.NLM
Explanation: This alert is for information only.
Action: None, unless you wish to begin product installation again.

NWCONFIG-X-264: Item name installation has been aborted.

Source: NWCONFIG.NLM
Explanation: This alert is for information only.
Action: None, unless you wish to begin product installation again.

NWCONFIG-X-265: Directory path path is invalid.

Source: NWCONFIG.NLM
Explanation: The path either does not exist or contains invalid characters.
Action: Make sure that the path points to a valid directory and contains no invalid characters.

NWCONFIG-X-266: Directory path path either is invalid or does not contain the desired file (name). Press F3 (or F4 if applicable) and enter a different path.

Source: NWCONFIG.NLM
Explanation: The specified path does not exist, or does not contain the file, or contains invalid characters.
Action: Enter a valid path.

NWCONFIG-X-267: Directory path path either is invalid or does not contain the desired file (name).

Source: NWCONFIG.NLM
Explanation: The specified path does not exist, does not contain the file, or contains invalid characters.
Action: Enter a valid path.

NWCONFIG-X-268: The specified directory path is invalid. Press F3 (or F4 if applicable) and enter a new path.

Source: NWCONFIG.NLM
Explanation: The specified path either does not exist or contains invalid characters.
Action: Enter a valid path.

NWCONFIG-X-269: The system volume (SYS:) either is not mounted or does not exist.

Source: NWCONFIG.NLM
Explanation: The SYS: volume is either not mounted or not visible to NWCONFIG.
Action: Make sure that the volume is mounted, that all the necessary disk drivers are loaded, and that the disk is powered on. See Resolving Volume I/O Errors in the NW6.5 SP8: Traditional File System Administration Guide.

NWCONFIG-X-270: The system volume (name:) is not mounted.

Source: NWCONFIG.NLM
Explanation: You cannot use NWCONFIG.NLM until you have mounted the system volume.
Action: Mount the volume. Do this at the system console by entering MOUNT volume_name.

NWCONFIG-X-271: The limit (number) for the number of volumes that may be mounted at one time has been reached on this server. Dismount another volume before you mount this one.

Source: NWCONFIG.NLM
Action: Follow the suggestions in the message.

NWCONFIG-X-272: One or more partitions on drive number are inconsistent with the driver geometries (number heads, number sectors, and number cylinders) that NetWare is using. You may continue and edit the partitions anyway, although this inconsistency could create problems later on.

Source: NWCONFIG.NLM
Explanation: The size of the partition is not an even multiple of the number of heads, sectors, and cylinders on the drive.
Action: Although it is possible to continue with the editing, it would be better to re-create the offending partition consistent with the driver geometry that NetWare is using.

NWCONFIG-X-273: Volume name name already exists. Choose a different name.

Source: NWCONFIG.NLM
Explanation: The volume name displayed in the message already exists.
Action: Choose a different volume name.

NWCONFIG-X-274: Some disk partitions already exist. NWCONFIG will delete them (including the files, user data, etc.) and create new ones if you confirm Yes in the box that follows this message. Active (bootable) partitions, such as the DOS boot partition, will not be deleted, even if you confirm Yes. WARNING: To preserve the data in non-active partitions, confirm No.

Source: NWCONFIG.NLM
Explanation: Unless you specify otherwise, NWCONFIG will delete all nonbootable DOS partitions and use the largest area of free space to create a NetWare disk partition.
Action: If you want the partitions deleted, confirm with Yes; otherwise respond No.

NWCONFIG-X-275: No ending signature (`DRIVER DESCRIPTION END’) was found in file name. The file was ignored.

Source: NWCONFIG.NLM
Explanation: The file is probably corrupted or out of date.
Action: If you need this file, replace it with a version that is current and not corrupted.

NWCONFIG-X-277: Driver name is loaded multiple times (re-entrantly). All instances of the driver will be unloaded if you confirm Yes in the menu following this message.

Source: NWCONFIG.NLM
Explanation: Unloading this driver might affect multiple devices that the driver controls. For instance, a LAN driver might control multiple network boards, or a disk driver might control multiple disks. If you unload the driver, all the devices this driver controls will be unavailable to you.
Action: Choose the appropriate action.

NWCONFIG-X-278: No disk driver files (*.DSK, *.HAM, *.CDM) were found.

Source: NWCONFIG.NLM
Explanation: NWCONFIG was unable to access a disk because no disk driver was found.
Action: Copy the needed driver to the boot directory.

NWCONFIG-X-279: No LAN driver files (*.LAN) can be found. Volume SYS: may be unmounted, or directory SYS:SYSTEM may not contain any driver files.

Source: NWCONFIG.NLM
Explanation: NWCONFIG was unable to find a LAN driver. If volume SYS: is mounted, it contains no driver files.
Action: If volume SYS: is not mounted, mount the volume and repeat the operation. You might have to press Insert and install from a diskette.

NWCONFIG-X-280: The driver file (name) could not be found.

Source: NWCONFIG.NLM
Explanation: Either the driver is not present, or the driver name is not spelled correctly.
Action: Specify a correct path to the driver, or specify the correct name of the driver.

NWCONFIG-X-282: Logical name name already exists.

Source: NWCONFIG.NLM
Explanation: The name already exists.
Action: Specify a different name.

NWCONFIG-X-283: The command line string for driver name was too long and could not be generated.

Source: NWCONFIG.NLM
Explanation: NWCONFIG has a limited buffer for generating a command line to use when loading driver files. The parameters you desire require a command line longer than NWCONFIG can generate.
Action: Load the driver from the system console, providing the parameters by hand.

NWCONFIG-X-284: A value must be entered for parameter name. Enter a value before you load the driver.

Source: NWCONFIG.NLM
Explanation: The specified parameter requires a value as in the example below:

NET=01240000 

Action: Specify the proper value for the parameter.

NWCONFIG-X-285: Value value cannot be interpreted.

Source: NWCONFIG.NLM
Explanation: The specified value has no meaning to NWCONFIG.
Action: Supply a valid value as indicated in the documentation for the indicated product.

NWCONFIG-X-286: Value value is already in use. Choose another one.

Source: NWCONFIG.NLM
Explanation: The value specified is already in use.
Action: Choose another value (for example, a different interrupt number).

NWCONFIG-X-287: Recoverable parameter dependency errors occurred with parameter value. You may continue anyway.

Source: NWCONFIG.NLM
Explanation: The value you supplied for a parameter required another parameter that was not supplied.
Action: None. This message is for information only. NWCONFIG was able to recover from the error.

NWCONFIG-X-288: A recoverable initialization problem occurred with parameter value. You may continue anyway.

Source: NWCONFIG.NLM
Explanation: The value supplied for a parameter caused a problem, but NWCONFIG was able to recover from the error.
Action: None. This message is for information only. NWCONFIG was able to recover from the error.

NWCONFIG-X-289: Value value is not in the list of acceptable values.

Source: NWCONFIG.NLM
Explanation: An invalid value was entered.
Action: Enter an acceptable value.

NWCONFIG-X-290: Value value is not within the range specified for this parameter.

Source: NWCONFIG.NLM
Explanation: An invalid value was entered.
Action: Enter an acceptable value.

NWCONFIG-X-293: Driver name did not unload correctly. Control will be switched to the system console screen where you may see the error.

Source: NWCONFIG.NLM
Explanation: NWCONFIG was unable to determine the cause of the failure to unload.
Action: Switch to the system console screen, where a message will be displayed by the NetWare server indicating the reason the driver did not unload. Correct the problem indicated by the server, and retry the operation.

NWCONFIG-X-297: Driver name was successfully unloaded. Press Enter to continue.

Source: NWCONFIG.NLM
Explanation: This alert is for information only.
Action: None. This message is for information only.

NWCONFIG-X-298: Driver name on line number has no FRAME=<frame name> parameter. All new Ethernet drivers that have no frame specified will now default to Ethernet 802.2 frame type, whereas they previously used 802.3. Specify a frame parameter for this driver.

Source: NWCONFIG.NLM
Action: If you want a frame type different from the default, you will need to specify it later.

NWCONFIG-X-300: The network number you entered is the IPX internal network number of this server; it cannot be used to bind to IPX. Enter a different (unique) number.

Source: NWCONFIG.NLM
Explanation: The network address and the internal network number cannot be the same number.
Action: If they are the same, change the internal network number of your server; otherwise, enter the correct network address for this server.

NWCONFIG-X-301: No LAN drivers are loaded. LAN drivers must be loaded and bound in order for NWCONFIG to communicate with other v4.x servers and install Novell eDirectory as part of an existing eDirectory tree.

Source: NWCONFIG.NLM
Explanation: NWCONFIG could not communicate with any other servers because no LAN drivers have been loaded.
Action: If you want NWCONFIG to see other servers on your network, load and bind an appropriate LAN driver; then retry the operation.

NWCONFIG-X-302: No volumes were found.

Source: NWCONFIG.NLM
Explanation: There are no known volumes on this server.
Action: If you know that volumes exist on this server, make sure the correct disk driver is loaded and all necessary disks are powered on and connected properly.

NWCONFIG-X-304: A physical device or partition in the set you selected is no longer valid.

Source: NWCONFIG.NLM
Explanation: The device might have been powered off or in some other way made invisible to NWCONFIG.
Action: Correct the problem and retry the operation.

NWCONFIG-X-305: Driver name was successfully loaded but not bound to any protocol stacks. Press Enter to continue.

Source: NWCONFIG.NLM
Action: To bind the driver to a protocol stack, switch to the system console screen and use the BIND command.

NWCONFIG-X-306: Driver name could not be loaded because command file name could not be created. Load this driver manually from the system console.

Source: NWCONFIG.NLM
Explanation: Normally, the program automatically creates this file with the command parameters in it, and command parameters are read from this file. However, the LOAD command you entered was too long (over 200 characters), so you will have to enter the command manually.
Action: Type LOAD driver_name parameters at the system console screen.

NWCONFIG-X-307: Driver name could not be loaded because command file name could not be written. Load this driver manually from the system console.

Source: NWCONFIG.NLM
Explanation: Normally, the program automatically creates this file with the command parameters in it, and command parameters are read from this file. However, the LOAD command you entered was too long (over 200 characters), so you will have to enter the command manually.
Action: Enter LOAD driver_name parameters at the system console screen.

NWCONFIG-X-308: No disk driver files (*.DSK, *.HAM, *.CDM) were found at this path.

Source: NWCONFIG.NLM
Explanation: The indicated files were not found at this location.
Action: If the path points to a diskette drive, make sure that you are using the correct diskette and that you have inserted it properly into the diskette drive. Otherwise, specify the correct path to locate these files.

NWCONFIG-X-309: No LAN driver files (*.LAN) were found at this path.

Source: NWCONFIG.NLM
Explanation: The indicated files were not found at this location.
Action: If the path points to a diskette drive, make sure that you are using the correct diskette and that you have inserted it properly into the diskette drive. Otherwise, specify the correct path to locate these files.

NWCONFIG-X-310: File name could not be saved to name.

Source: NWCONFIG.NLM
Explanation: NWCONFIG was unable to rename the current version of the file to the save name. A file of that name already exists in the destination, and it cannot be replaced.
Action: Delete the file you tried to replace; then save the file you want to move or rename.

NWCONFIG-X-311: File name could not be copied (error: description). Either the driver file is not in the path specified or the destination path path is invalid.

Source: NWCONFIG.NLM
Action: Make sure that the path contains valid characters, points to a valid directory, and contains the proper files.

NWCONFIG-X-312: Driver name is currently not loaded.

Source: NWCONFIG.NLM
Action: Either load the driver or select another one, as appropriate.

NWCONFIG-X-313: No other volumes exist.

Source: NWCONFIG.NLM
Explanation: No other volumes were found.
Action: If you know other volumes exist, make sure that the disk containing these volumes is powered on and that the appropriate disk driver is loaded and visible to the server.

NWCONFIG-X-314: The limit for maximum number of segments per volume (name) has been reached for all volumes. This segment cannot be added to any of them.

Source: NWCONFIG.NLM
Explanation: You might create a new volume using this segment, but you might not add it to any existing volume.
Action: Proceed as appropriate for your situation.

NWCONFIG-X-315: Volume name may contain valuable data that will be lost if you confirm Yes in the box that follows this message and you save volume changes when you exit from the volumes list.

Source: NWCONFIG.NLM
Explanation: The volume will be deleted if you select Yes.
Action: Proceed as appropriate for your situation.

NWCONFIG-X-316: Existing data on ALL existing segments of volume name will be destroyed if you indicate Yes in the Confirm box that follows this message and you save volume changes when you exit from the (previous) volumes list.

Source: NWCONFIG.NLM
Explanation: The volume will be deleted if you select Yes.
Action: Proceed as appropriate for your situation.

NWCONFIG-X-317: Novell eDirectory tree name is not locatable. It may take a couple of minutes for the tree to appear in this server’s router tables. Wait and try again, or select a different eDirectory tree.

Source: NWCONFIG.NLM
Explanation: To locate existing Novell eDirectory trees, NWCONFIG must query the network. It cannot currently locate the specified tree. This information is normally updated every minute.
Action: Wait and try again, or select a new tree.

NWCONFIG-X-318: Warning: Some volumes are not mounted and will not be upgraded to Novell eDirectory. You may mount and upgrade them later if you wish.

Source: NWCONFIG.NLM
Explanation: This warning simply indicates that unmounted volumes are not upgraded.
Action: Upgrade volumes as appropriate to your situation.

NWCONFIG-X-319: NWCONFIG cannot get the root directory entry for volume name.

Source: NWCONFIG.NLM
Explanation: The root directory (/) was not readable.

NWCONFIG-X-320: The bindery upgrade failed. Some of the bindery objects will have to be created and/or trustee rights changed manually later using Novell eDirectory workstation utilities.

Source: NWCONFIG.NLM
Explanation: NWCONFIG was unable to convert all of the bindery objects to Novell eDirectory objects.
Action: You will have to manually create any missing objects after the installation is complete.

NWCONFIG-X-321: The Directory ID cannot be stamped on volume name.

Source: NWCONFIG.NLM
Explanation: An internal system error has occurred.
Action: Try again. If the problem persists, contact a Novell support provider.

NWCONFIG-X-322: Driver name on line number of the AUTOEXEC.NCF file has no `FRAME=<frame name>’ parameter. All new Ethernet drivers that have no frame type specified will now default to Ethernet 802.2 frame type, whereas they previously used 802.3. Write down the line number. You will be shown the AUTOEXEC.NCF file after NWCONFIG is finished checking it, and you may then add a frame parameter for this driver if it is an Ethernet driver.

Source: NWCONFIG.NLM
Explanation: This error can occur only when a manual installation is being attempted from the command line. Both frame types are loaded automatically when loading a driver with the NWCONFIG program.
Action: Proceed as appropriate for your situation.

NWCONFIG-X-323: This option invoked NLM name, which cannot be loaded remotely. Install this product from the server console.

Source: NWCONFIG.NLM
Explanation: The product installation script for this product has tried to load an NLM. However, NLM programs cannot be loaded remotely.‘
Action: The existing product installation script will not work remotely. You will have to install this product at the server console.

NWCONFIG-X-324: The context you specified is incomplete. Make sure you have entered at least a company/organization name, or if you have entered the context manually, make sure the leftmost context specification is O=<name> or OU=<name>.

Source: NWCONFIG.NLM
Explanation: A full directory context is required.
Action: Enter the directory context again.

NWCONFIG-X-325: A password has not been entered for administrator object name. You must enter a valid password to continue.

Source: NWCONFIG.NLM
Explanation: Other users can accidentally make significant changes to your Novell eDirectory configuration if this user name is not assigned a password.
Action: Enter an Administrator password.

NWCONFIG-X-326: Administrator name could not be authenticated. Verify that the administrator name and context are entered completely and correctly and that you have entered the correct password.

Source: NWCONFIG.NLM
Explanation: The most likely cause of this error is that the name and context have not been entered correctly.
Action: Examine the name and context entered. Make changes where appropriate.

NWCONFIG-X-327: Context name could not be created. Verify that the context path is entered correctly and that object name has supervisor rights on the parent of the new context in eDirectory. Also, if you entered the context name manually, make sure it follows all the proper containment and syntax rules for a valid full context specification.

Source: NWCONFIG.NLM
Explanation: NWCONFIG could not determine the reason that the context could not be created.
Action: Make sure that the context name follows all syntax rules as indicated in documentation for Novell eDirectory.

NWCONFIG-X-328: Another object with name name already exists at context context. This server cannot be installed at that context. Either (1) specify a different context for this server or (2) from a workstation, delete or rename the conflicting object.

Source: NWCONFIG.NLM
Action: Follow the instructions on the screen.

NWCONFIG-X-331: The password was retyped incorrectly. Re-enter the password.

Source: NWCONFIG.NLM
Action: Retype the new password correctly to confirm it.

NWCONFIG-X-332: User object name could not be authenticated. Verify that the complete name is entered correctly and that you have the correct password.

Source: NWCONFIG.NLM
Explanation: An invalid object name or password was entered.
Action: Enter the complete name correctly. If the problem persists, contact a Novell support provider.

NWCONFIG-X-333: Warning: An attempt to log in to Novell eDirectory failed, because the server context is not known. eDirectory may be uninitialized, removed, or corrupted.

Source: NWCONFIG.NLM
Explanation: NWCONFIG was unable to determine the server context.
Action: Execute DSREPAIR; then install or reinstall Novell eDirectory.

NWCONFIG-X-334: Enter a new name for object name.

Source: NWCONFIG.NLM
Explanation: You entered an invalid Novell eDirectory object name.
Action: Enter a valid object name.

NWCONFIG-X-335: An object with name name already exists. Choose a different name.

Source: NWCONFIG.NLM
Explanation: You attempted to assign an object name that already has been assigned to a Novell eDirectory object.
Action: Choose a new object name.

NWCONFIG-X-336: Driver name could not be loaded because the command line is too long. Load this driver manually from the system console.

Source: NWCONFIG.NLM
Explanation: The command line exceeded NWCONFIG’s internal buffer length for command lines.
Action: Switch to the system console and load the driver manually, supplying the necessary parameters.

NWCONFIG-X-337: Warning: Typically, an organization with one or more servers should have only one tree. Different trees do not share Novell eDirectory information (servers, print servers, users, etc.). If there are additional trees you will have to go through an additional login to communicate with other trees (via bindery services).

Make sure you have read the documentation and understand the complexities of managing a multi-tree internetwork. If you decide that you do want another tree, confirm Yes in the box that follows this message.

Source: NWCONFIG.NLM
Action: Proceed as appropriate for your situation.

NWCONFIG-X-339: You must upgrade the bindery before volumes may be installed in Novell eDirectory.

Source: NWCONFIG.NLM
Action: Upgrade the bindery before trying to install the volumes in Novell eDirectory.

NWCONFIG-X-340: There are users logged into this server. Remove all user connections and try to install Novell eDirectory again.

Source: NWCONFIG.NLM
Explanation: You cannot install Novell eDirectory while users are logged in to the server.
Action: Clear the users' connections and retry the operation.

NWCONFIG-X-341: A console command (command) did not finish executing in the time allowed (number seconds). Control will be switched to the system console screen, where you must finish it manually.

Source: NWCONFIG.NLM
Explanation: The reason the command did not completely execute will be shown on the system console screen.
Action: After correcting the problem, finish the command on the system console screen; then return to NWCONFIG.

NWCONFIG-X-342: To see a list of existing objects in Novell eDirectory (countries, organizations, divisions, etc.) when you press Enter, you must first authenticate to eDirectory. To authenticate, you must (1) enter the administrator name, and (2) enter the correct password. (Note that if you type the country and company or organization name, a default administrator name will be created for you.)

Source: NWCONFIG.NLM
Action: To see the list, follow the instructions in the message.

NWCONFIG-X-343: NWCONFIG cannot lock the root directory entry for volume name. Some other process is modifying it.

Source: NWCONFIG.NLM
Explanation: Only one process at a time can modify the root directory entry.
Action: Wait until the other process finishes. If it takes more than a couple of hours, contact a Novell support provider.

NWCONFIG-X-345: The program was unable to initialize NWSNUT.NLM.

Source: NWCONFIG.NLM
Explanation: The support NLM, NWSNUT, returned an error from the initialization process. This could be an internal error, or it could be caused by insufficient memory.
Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.If the server has at least 500 KB of free memory, contact a Novell support provider.

NWCONFIG-X-346: A tree or server with the same name (name) already exists. Choose a different name.

Source: NWCONFIG.NLM
Explanation: Another Novell eDirectory tree exists on the network with the same name.
Action: Choose a different name for the eDirectory tree.

NWCONFIG-X-347: The tree name must have at least 1 character.

Source: NWCONFIG.NLM
Action: Enter a name for the tree, containing at least 1 character.

NWCONFIG-X-348: The total space required by files that will be copied (number MB; number bytes) is larger than the size of the system volume (number MB; number bytes). You must either select fewer file groups (if applicable), or expand the size of system volume SYS: (by recreating it or adding an additional volume segment).

Source: NWCONFIG.NLM
Action: Proceed as appropriate for the situation.

NWCONFIG-X-349: The context name must have at least 3 characters (O=name).

Source: NWCONFIG.NLM
Action: Enter a name for the context having at least 3 characters.

NWCONFIG-X-350: The total space required by files that will be copied (number MB; number bytes) is larger than the free space available on the system volume (number MB; number bytes). Because some files may be overwritten and replaced, you may have sufficient space, but that cannot be determined at this point.

You may want to do one or more of the following: Select fewer file groups (if applicable), delete files, purge deleted files, or expand the size of system volume SYS: (by recreating it or adding an additional volume segment).

Source: NWCONFIG.NLM
Explanation: If you are replacing files with this copy operation (that is, if the files you are copying already exist on the server), then you might have enough space.
Action: If sufficient space is available, continue with the operation; otherwise, follow the instructions in the message.

NWCONFIG-X-351: Warning: TIMESYNC.NLM is not currently loaded. You should load it (from the system console screen) before continuing. Novell eDirectory may have trouble synchronizing properly if the local time differs from the network time.

Source: NWCONFIG.NLM
Explanation: Novell eDirectory requires that TIMESYNC.NLM be loaded.
Action: Load the TIMESYNC NLM.

NWCONFIG-X-352: Warning: Device number contains volume information for segment number of volume name. If you want to save this device’s volume data, confirm Yes in the box that follows this message. If you indicate No, the volume data (on this device only) will be destroyed.

Source: NWCONFIG.NLM
Explanation: NWCONFIG will delete the volume segment from this device if you select Yes.
Action: Proceed as appropriate for your situation.

NWCONFIG-X-354: An attempt to create a record for product name in the product database failed. Error: code.

Source: NWCONFIG.NLM
Explanation: The disk space might be full or limited in some fashion so as to prohibit writing to this file. The file also might be flagged read-only or otherwise made inaccessible.
Action: See Resolving Volume I/O Errors in the NW6.5 SP8: Traditional File System Administration Guide. For information on the specific error code, search the Error Codes online documentation.

NWCONFIG-X-355: The network number must be non-zero. Enter a different number.

Source: NWCONFIG.NLM
Explanation: You entered a zero for the network address.
Action: Enter a nonzero number.

NWCONFIG-X-356: The administrator name has too few characters. It should typically be of the form CN=<name>. [OU=<suborganization>...]. O=<organization> [.C=<country>].

Source: NWCONFIG.NLM
Explanation: The syntax for the administrator name is incorrect.
Action: Make sure that the name conforms to the specification listed.

NWCONFIG-X-358: This server already contains Novell eDirectory information. If you want to modify the eDirectory tree structure, use ConsoleOne. Do not try to reinstall eDirectory unless it is absolutely necessary. However, if you must reinstall, unload any screen saver that could lock the console, remove eDirectory with volumes mounted, then repeat this step. After you complete the installation, load DSREPAIR to delete unclaimed trustees from the volumes, then reinstall all servers that contain subordinate partitions.

Source: NWCONFIG.NLM
Explanation: Normally, you should not reinstall Novell eDirectory after it has been installed.
Action: Read the information in the message carefully; then proceed accordingly.

NWCONFIG-X-359: Novell eDirectory has previously been installed on this server. Do NOT reinstall unless absolutely necessary. eDirectory is a database of information distributed across multiple servers. If you reinstall, and if this server contains the only replica of a partition that has links to other subordinate partitions, all subordinate partition information on OTHER servers will become invalid. Reinstallation may invalidate some or all trustee access rights and mail directories (but not file contents) on THIS server.

To skip reinstalling eDirectory, confirm No in the box that follows this message. If you confirm Yes in the box that follows, you must login to eDirectory to delete the server object and downgrade volume IDs before reinstallation. If you have volumes that are not currently mounted, you should switch to the system console (Ctrl+Esc) and mount them now. After installing the server, load and execute DSREPAIR to delete unclaimed trustee IDs. Then reinstall all servers that contain subordinate partitions.

Source: NWCONFIG.NLM
Explanation: Normally, you should not reinstall Novell eDirectory after it is been installed.
Action: Read the information in the message carefully; then proceed accordingly.

NWCONFIG-X-360: Warning: do not change the time server type from the default unless you have carefully read the time services information and understand the consequences. NetWare 4.x servers may fail to update correctly if time services is configured improperly.

Source: NWCONFIG.NLM
Explanation: The default time synchronization setup should be modified only if you are thoroughly familiar with how this product feature works.
Action: Before attempting to change the time server type from the default, review the documentation on Time Synchronization.

NWCONFIG-X-361: Volume name is out of disk space. File name cannot be copied.

Source: NWCONFIG.NLM
Explanation: There is not enough disk space to complete the installation.

NWCONFIG-X-365: The Directory ID cannot be removed from volume name.

Source: NWCONFIG.NLM
Explanation: An internal error occurred which prevented clearing of an ID field on the volume. Perhaps the volume is read-only.
Action: Contact a Novell support provider.

NWCONFIG-X-366: A virtual device does not have a mirror set that can be displayed or modified.

Source: NWCONFIG.NLM
Explanation: An attempt was made to view the set of mirrored devices corresponding to a virtual device. A virtual device is a device that does not use standard NetWare device partitioning, mirroring, and Hot Fix. The device is registered with NetWare as a logical partition only.
Action: Do not attempt to view the mirrored set, etc. corresponding to this device.

NWCONFIG-X-389: An NCP Server object (or an unknown object) with name name already exists at context context.

Source: NWCONFIG.NLM
Explanation: All objects of the same type must have unique names within a directory tree context. There is an existing Server object with the same name and in the same context as one that is being added.
Action: Change the context or name of the new or existing Server object.

NWCONFIG-X-392: The program cannot allocate a semaphore.

Source: NWCONFIG.NLM
Explanation: This error is probably caused by insufficient memory.
Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

NWCONFIG-X-393: The attempt to log in to server name by user username failed. Error: number

Source: NWCONFIG.NLM
Action: Check the conditions listed in the message and verify that all are correct. To review information for the error code number, see Error Codes in the online documentation.

NWCONFIG-X-394: No LAN drivers are currently loaded. Installation from a remote server requires access to the network. A LAN driver must be loaded and bound to a protocol stack on this server.

Source: NWCONFIG.NLM
Explanation: A network connection is required to install from a remote server. Without a LAN driver being loaded and bound to a protocol, a network connection cannot be created.
Action: Load a LAN driver and bind it to a protocol.

NWCONFIG-X-401: Error executing file name. The file cannot be loaded remotely.

Source: NWCONFIG.NLM
Explanation: This error could result from I/O errors, file corruption, or a bad network connection, or the error could occur because this file must be loaded on the console.
Action: Verify that this file can be loaded remotely. See Resolving Volume I/O Errors in the NW6.5 SP8: Traditional File System Administration Guide.

NWCONFIG-X-402: An attempt to establish a server-to-server session failed. A server-to-server session must exist in order to access the remote server specified in the installation source path: path.

Source: NWCONFIG.NLM
Explanation: The attempt to establish a server-to-server connection failed. Possible reasons follow: wrong password for the specified user, this server is unable to see the other server (router problems, or the other server is down), or this server is not connected to the same network with the same protocols as the other server.
Action: Make sure that the other server is up and that this server can see it. Make sure that the user name and password are correct and that both servers can understand one another.

NWCONFIG-X-403: ISSLIB.NLM (Install Server To Server I/O Library NLM) must be loaded in order to access the remote server specified in the installation source path: path.

Source: NWCONFIG.NLM
Explanation: The attempted operation requires that the file ISSLIB.NLM be loaded. Verify that this file exists, is executable, and is in the server’s search path.
Action: Check for the possible problems listed above. See Resolving Volume I/O Errors in the NW6.5 SP8: Traditional File System Administration Guide.

NWCONFIG-X-405: No disk drivers were found by this program; it could not complete auto mirroring.

Source: NWCONFIG.NLM
Explanation: The disk driver has been unloaded, or a major internal error has occurred.
Action: Backup and reload disk drivers. If the problem persists, contact a Novell support provider.

NWCONFIG-X-406: This program could not find the other IO engine; it could not complete auto mirroring.

Source: NWCONFIG.NLM
Explanation: Communication between the two IO engines has stopped. This could be caused by faulty network boards connecting the two computers, a break in the communication cable, or the other computer being down.
Action: Check the items listed above, then reboot and reinstall. If the problem persists, contact a Novell support provider.

NWCONFIG-X-407: An attempt by this program to allocate memory failed; auto mirroring could not be completed.

Source: NWCONFIG.NLM
Explanation: This program could not allocate required memory to complete auto mirroring.
Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

NWCONFIG-X-408: This program was unable to get disk driver information; it could not complete auto mirroring.

Source: NWCONFIG.NLM
Explanation: The disk driver has been unloaded or there is a major internal error.
Action: Back up and reload disk drivers. If the problem persists, contact a Novell support provider.

NWCONFIG-X-409: This program was unable to get partition information; it could not complete auto mirroring.

Source: NWCONFIG.NLM
Explanation: This program is no longer able to see the hard disk.
Action: Verify that the correct disk driver is loaded. Try installing again. If the problem persists, contact a Novell support provider.

NWCONFIG-X-410: This program was unable to get redirection information; it could not complete auto mirroring.

Source: NWCONFIG.NLM
Explanation: This program is no longer able to see the hard disk.
Action: Verify that the correct disk driver is loaded. Try installing again. If the problem persists, contact a Novell support provider.

NWCONFIG-X-411: This program was unable to create mirror information; it could not complete auto mirroring.

Source: NWCONFIG.NLM
Explanation: This program is no longer able to see the hard disk.
Action: Verify that the correct disk driver is loaded. Try installing again. If the problem persists, contact a Novell support provider.

NWCONFIG-X-412: This program was unable to get mirror information; it could not complete auto mirroring.

Source: NWCONFIG.NLM
Explanation: This program is no longer able to see the hard disk.
Action: Verify that the correct disk driver is loaded. Try installing again. If the problem persists, contact a Novell support provider.

NWCONFIG-X-413: This program could not find any NetWare partitions on the original computer; it did not complete auto mirroring.

Source: NWCONFIG.NLM
Explanation: This program is no longer able to see the hard disk.
Action: Verify that the correct disk driver is loaded. Try installing again. If the problem persists, contact a Novell support provider.

NWCONFIG-X-414: This program could not find any NetWare partitions on the new computer; it did not complete auto mirroring.

Source: NWCONFIG.NLM
Explanation: This program is no longer able to see the hard disk.
Action: Verify that the correct disk driver is loaded. Try installing again. If the problem persists, contact a Novell support provider.

NWCONFIG-X-415: Both computers do not have the same number of NetWare partitions. This program did not complete auto mirroring.

Source: NWCONFIG.NLM
Explanation: Auto mirroring cannot take place if both computers do not have the same number of NetWare partitions.
Action: Manually mirror these partitions. Select the Manual option instead of the Automatic option.

NWCONFIG-X-416: The new server computer’s NetWare partition is orphaned, cloned or non-operational. This program did not complete auto mirroring.

Source: NWCONFIG.NLM
Explanation: There is a problem reading the new server’s NetWare partition.
Action: Verify that the correct disk driver is loaded. Select the Manual partition option and resynchronize the mirrored group.

NWCONFIG-X-417: The new server computer’s NetWare partition is already mirrored. This program did not complete auto mirroring.

Source: NWCONFIG.NLM
Explanation: The program thinks that the new server’s NetWare partition is already mirrored.
Action: The mirror group should be deleted, re-created and mirrored.

NWCONFIG-X-418: The new server’s NetWare partition contains a volume. This program did not complete auto mirroring.

Source: NWCONFIG.NLM
Explanation: A partition with a volume cannot be mirrored.
Action: Verify that you are doing what you want done. Back up any needed data from the new server’s NetWare volume; then go to the Create Partition screen and delete and re-create the offending partition.

NWCONFIG-X-419: The original server’s NetWare partition is orphaned, cloned or non-operational. This program did not complete auto mirroring.

Source: NWCONFIG.NLM
Explanation: There is a problem reading the original server’s NetWare partition.
Action: Make sure that the correct disk driver is loaded. Select the Manual partition option and resynchronize the mirrored group.

NWCONFIG-X-420: The original server’s NetWare partition is already mirrored. This program did not complete auto mirroring.

Source: NWCONFIG.NLM
Explanation: The program thinks that the original server’s NetWare partition is already mirrored.
Action: The mirror group should be deleted, re-created and mirrored.

NWCONFIG-X-421: This program could not add a partition to a mirror group; it could not complete auto mirroring.

Source: NWCONFIG.NLM
Explanation: An internal processing error exists.
Action: Make sure that the correct disk driver is loaded. Retry the operation. If the problem persists, contact a Novell support provider.

NWCONFIG-X-422: This program could not set partition HotFix; it could not complete auto mirroring.

Source: NWCONFIG.NLM
Explanation: There is an internal processing error.
Action: Make sure that the correct disk driver is loaded. Retry the operation. If the problem persists, contact a Novell support provider.

NWCONFIG-X-423: The original server computer’s NetWare partition is larger than the new computer’s partition; it did not complete auto mirroring.

Source: NWCONFIG.NLM
Explanation: The original server’s NetWare partition is larger than the allowed maximum difference for mirroring.
Action: You can either shrink the original server’s partition or increase the new computer’s partition.

NWCONFIG-X-425: Warning: You do not have a disk driver loaded. You need to load the proper disk driver to complete the installation.

Source: NWCONFIG.NLM
Explanation: The server communicates with the hard disk through a disk driver. If no disk driver is loaded, installation cannot proceed because it will not have access to the hard disk.
Action: Load the correct disk driver.

NWCONFIG-X-426: Warning: You do not have a LAN driver loaded. You need to load the proper LAN driver to complete the installation.

Source: NWCONFIG.NLM
Explanation: The server communicates with the network card through a LAN driver. Installation could continue, but communication with other servers will not exist until a LAN driver is loaded.
Action: Load the correct LAN driver.

NWCONFIG-X-427: Warning: You do not have disk drivers loaded on both server computers. You need to load the proper disk drivers to complete the installation.

Source: NWCONFIG.NLM
Explanation: The server communicates with the hard disk through a disk driver. If no disk driver is loaded, installation cannot proceed because it will not have access to the hard disk.
Action: Load the correct disk driver on both computers.

NWCONFIG-X-428: Warning: You do not have LAN drivers loaded on both server computers. You need to load the proper LAN drivers to complete the installation.

Source: NWCONFIG.NLM
Explanation: The server communicates with the network card through a LAN driver. Installation could continue, but communication with other servers will not exist until a LAN driver is loaded.
Action: Load the correct LAN driver on both computers.

NWCONFIG-X-429: You cannot edit/modify the parameters of a currently loaded driver. If you must modify the parameters, unload the driver and reload it.

Source: NWCONFIG.NLM
Action: If the parameters need to be changed, unload the driver and reload it, changing the parameters as needed.

NWCONFIG-X-432: Warning: For NetWare for OS/2, you need at least one LAN driver and also a shared LAN driver (TOKENSHR, etc). You need the LAN driver to complete the installation, and the shared driver to see the network from OS/2.

Source: NWCONFIG.NLM
Explanation: If you are sharing a network board between the server and the client, you will need to load at least two LAN drivers. One LAN driver will be a sharing driver which will allow the client to have access to the network. The other LAN driver will be the driver for the installed network board. You might have multiple real LAN drivers, one for each network board, but only one sharing driver.
Action: If you are sharing a network board with the client, load the preselected sharing driver (TOKENSHR, TOKENLNK, or LANSHARE) and the LAN drivers corresponding to the installed network boards. If you are not sharing a network board, load only the LAN drivers corresponding to the installed network boards.

NWCONFIG-X-433: Warning: You do not have a shared LAN driver loaded. You need to choose the proper shared driver for OS/2 to see the network.

Source: NWCONFIG.NLM
Explanation: If you are sharing a network board between the server and the client, you will need to load both a real and a sharing LAN driver. The real LAN driver allows the server to see the network, and the shared LAN driver allows the client to see the network.
Action: Load the correct sharing LAN driver. There is a line in the CONFIG.SYS file that loads the corresponding sharing driver on the client (TOKENSHR, TOKENLNK, or LANSHARE).

NWCONFIG-X-434: Some NetWare disk partitions already exist. NWCONFIG will delete them (including the files, user data, etc.) and create new ones if you confirm Yes in the box that follows this message. Only NetWare (not DOS or other) partitions will be deleted if you confirm Yes.

WARNING: To preserve the data on existing NetWare partitions, confirm No.

Source: NWCONFIG.NLM
Action: Make sure no data will be lost if you confirm Yes to this box. When a disk partition is deleted all data on that partition is lost. If you wish to delete the partition, answer Yes. Otherwise, answer No.

NWCONFIG-X-435: Warning: You had TCP/IP configured on the original server. You will need to load INETCFG.NLM after the installation is completed, and then re-install TCP/IP support.

Source: NWCONFIG.NLM
Explanation: The TCP/IP installation and configuration has been changed in this version of NetWare.
Action: Follow the instructions in the message.

NWCONFIG-X-436: Warning: You had APPLETALK configured on the original server. You will need to load INETCFG.NLM after the install is completed, and then re-install APPLETALK support.

Source: NWCONFIG.NLM
Explanation: The APPLETALK installation and configuration has been changed in this version of NetWare.
Action: Follow the instructions in the message.

NWCONFIG-X-438: Some NetWare disk partitions already exist on the new server computer. NWCONFIG will delete them (including the files, user data, etc.) and create new ones if you confirm Yes in the box that follows this message. Only NetWare (not DOS or other) partitions on the new computer will be deleted if you confirm Yes.

WARNING: To preserve the data on existing NetWare partitions on the new computer, confirm No.

Source: NWCONFIG.NLM
Explanation: Make sure no data will be lost if you confirm Yes to this box. When a disk partition is deleted, all data on that partition is lost.
Action: If you wish to delete the partition, answer Yes. Otherwise, answer No.

NWCONFIG-X-442: A user name is required to log in to the remote server.

Source: NWCONFIG.NLM
Explanation: Both a user name and a password are required to log in to a server.
Action: Enter the appropriate user name.

NWCONFIG-X-446: Warning: The system volume (SYS:) is not mounted, and driver load and bind commands cannot be added to the system configuration files (and therefore will not take effect after rebooting).

Source: NWCONFIG.NLM
Action: to make sure the driver load and bind commands are added, mount the system volume and create the .NCF files.

NWCONFIG-X-450: Warning: A file that is being installed would overwrite existing file name. It probably should not be overwritten.

However, in the confirm box that follows, you may continue and overwrite this file anyway, if you wish to.

Source: NWCONFIG.NLM
Explanation: An existing file on the server is about to be overwritten.
Action: Check the dates on both the existing file and new file. Determine whether the file should be overwritten, and then answer the confirmation box accordingly.

NWCONFIG-X-451: Warning: A file that is being installed would downgrade existing file name to an older version. Currently installed software that uses this file may not work correctly if you allow it to be overwritten. It probably should not be overwritten.

However, in the confirm box that follows, you may continue and overwrite this file anyway, if you wish to.

Source: NWCONFIG.NLM
Explanation: An existing file on the server is about to be overwritten. The date on the existing file is newer than the file that will overwrite it.
Action: It is recommended that the file not be overwritten unless it has been backed up. The file being installed might not work with currently installed software.

NWCONFIG-X-453: The attempt to log in to the tree name by user username failed. Error: number.

Source: NWCONFIG.NLM
Explanation: Authentication to the Novell eDirectory tree failed during installation of eDirectory.
Action: Make sure your password and context are correct. Press Alt + Esc to toggle to the server console, then enter DISPLAY SERVERS to see if the LAN is working. Try to log in again.

NWCONFIG-X-455: The attempt to log in to server name by user username failed.

You have already reached your limit on the maximum number of times that you may log in to server name.

Source: NWCONFIG.NLM
Explanation: It is possible to configure a NetWare server so that a user has only a specific number of concurrent logins.
Action: If you have other user logins to the designated server, log out of these other connections and try again. If you cannot find other logins, contact the system administrator of the server and increase the number of concurrent connections for this user.

NWCONFIG-X-456: A complete Novell eDirectory user distinguished name is required for an eDirectory login. Expanding names with trailing periods is not allowed here because there is no previous name context established before the eDirectory login.

Source: NWCONFIG.NLM
Explanation: Expanding names with trailing periods can only been done within an established context. If no context has been defined, the full distinguished name must be entered.
Action: Enter the full Novell eDirectory user name. For example,

 CN=USER_NAME.OU=ORGANIZATION.O=COMPANY 

NWCONFIG-X-457: An attempt to get partition replica information on this server failed.

Source: NWCONFIG.NLM
Explanation: This is an internal processing error.
Action: Try again. If the problem persists, contact a Novell support provider.

NWCONFIG-X-459: Warning: Some partitions have master replicas that reside on this server. Before removing Novell eDirectory on this server, the master replicas must be moved to a different server.

You may have NWCONFIG do this for you (see the box that follows), or may designate a server for each master yourself.

Source: NWCONFIG.NLM
Explanation: Master replicas should not be deleted. Instead they should be moved to a server that contains Novell eDirectory.
Action: Follow the suggestions in the message.

NWCONFIG-X-460: Warning: Replica and object synchronization operations are in progress. You should wait until they are complete before attempting to remove Novell eDirectory from this server.

Source: NWCONFIG.NLM
Explanation: Attempting to remove Novell eDirectory before the objects are synchronized could result in a corrupted data base.
Action: Wait for synchronization to complete before removing Novell eDirectory.

NWCONFIG-X-461: Warning: This server cannot currently contact other servers that must be notified before removing Novell eDirectory from this server. You should make sure all servers in this eDirectory tree are up and visible from the network.

Source: NWCONFIG.NLM
Explanation: When you remove Novell eDirectory, all the servers containing replica information need to be informed of the change. If these others servers are not informed, their databases could be corrupted.
Action: Wait until all other servers are available before removing Novell eDirectory.

NWCONFIG-X-462: An attempt to remove Novell eDirectory failed, probably due to a failure to allocate memory.

Source: NWCONFIG.NLM
Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

NWCONFIG-X-463: An attempt to remove Novell eDirectory failed. Error code: code

Source: NWCONFIG.NLM
Explanation: This in an internal processing error.
Action: Try again. If the problem persists, contact a Novell support provider.

NWCONFIG-X-464: An attempt to change the master replica of partition name failed. Error code: code.

Source: NWCONFIG.NLM
Explanation: This in an internal processing error.
Action: Try again. If the problem persists, contact a Novell support provider.

NWCONFIG-X-465: Warning: The root (main) partition for Novell eDirectory tree name exists only on this server.

If you continue, all objects in this eDirectory tree will be destroyed; all servers in this tree must be reinstalled, and all current user accounts, print queues, etc. will be deleted.

Do NOT confirm yes in the box that follows unless this is what you want.

Source: NWCONFIG.NLM
Explanation: The root partition for a Novell eDirectory tree contains information on all objects in that tree. If the root partition is deleted, all information concerning this tree will be lost.
Action: If you are sure you want to delete the tree and all object information select Yes, otherwise select No.

NWCONFIG-X-467: Administrator name could not be authenticated due to an internal Novell eDirectory error (code code).

The eDirectory installation has completed successfully, but no Volume objects were created for mounted volumes. You may load NWCONFIG.NLM after the entire installation completes, and then create the Volume objects. If this is a NetWare 3.x upgrade, you will also need to upgrade bindery information later.

Source: NWCONFIG.NLM
Explanation: Due to an internal error, the administrator could not be authenticated. Therefore, no Novell eDirectory objects could be created.
Action: Follow the suggestions in the message. If the problem persists, contact a Novell support provider.

NWCONFIG-X-468: An organization with the same name (name) already exists. Choose a different name.

Source: NWCONFIG.NLM
Action: Follow the suggestions in the message.

NWCONFIG-X-469: The organization name must have at least 1 character.

Source: NWCONFIG.NLM
Explanation: This message is for information only.

NWCONFIG-X-471: User Admin for organization name could not be authenticated. Verify that you have the correct password.

Source: NWCONFIG.NLM
Explanation: The correct password for the Admin user in the given organization is required for authentication.
Action: Enter the correct password for the Admin user.

NWCONFIG-X-477: Warning: An attempt to open configuration file STARTUP.NCF failed. Error code: code

You may still configure drivers, but later you will have to manually add the LOAD commands to the configuration file if you want the driver LOAD operations to remain after the server reboots.

Source: NWCONFIG.NLM
Explanation: Due to an internal error, the load commands will not be automatically inserted into the STARTUP.NCF file.
Action: See Resolving Volume I/O Errors in the NW6.5 SP8: Traditional File System Administration Guide. You can also do as the message states and manually edit the STARTUP.NCFfile by loading NWCONFIG and selecting NCF File Options > Edit STARTUP.NCF File.

NWCONFIG-X-478: Warning: An attempt to open configuration files IOSTART.NCF and MSSTART.NCF failed. Error code: code.

You may still configure drivers, but later you will have to manually add the LOAD commands to the configuration file if you want the driver LOAD operations to remain after the server reboots.

Source: NWCONFIG.NLM

NWCONFIG-X-479: Warning: An attempt to open configuration file AUTOEXEC.NCF failed. This may be due to volume SYS: being dismounted or inaccessible.

You may still configure drivers, but later you will have to manually add the LOAD commands to the configuration file if you want the driver LOAD operations to remain after the server reboots.

Source: NWCONFIG.NLM
Explanation: Due to an internal error, the load commands will not be automatically inserted into the AUTOEXEC.NCF file.
Action: See Resolving Volume I/O Errors in the NW6.5 SP8: Traditional File System Administration Guide. You can also do as the message states and manually edit the AUTOEXEC.NCF file by loading NWCONFIG and selecting NCF File Options > Edit AUTOEXEC.NCF File.

NWCONFIG-X-480: Warning: An attempt to open configuration files IOAUTO.NCF and MSAUTO.NCF failed. Error code: code

You may still configure drivers, but later you will have to manually add the LOAD commands to the configuration file if you want the driver LOAD operations to remain after the server reboots.

Source: NWCONFIG.NLM
Action: See Resolving Volume I/O Errors in the NW6.5 SP8: Traditional File System Administration Guide. You can also do as the message states and manually edit the IOAUTO.NCF and MSAUTO.NCF files by loading NWCONFIG and selecting Maintenance/Selective Install.

NWCONFIG-X-481: The NetWare/IP product environment could not be set up. The reason could be that CLIB.NLM or BTRIEVE.NLM did not load. Refer to the NetWare system console for the actual reason.

Source: NWCONFIG.NLM
Action: Refer to the NetWare system console screen for the reason the NetWare/IP environment could not be set up, and take the appropriate action. If an NLM could not be loaded, make sure that it is the proper version and see Resolving Volume I/O Errors in the NW6.5 SP8: Traditional File System Administration Guide.

NWCONFIG-X-482: This server is a single reference time source. If there is another directory-enabled server in this eDirectory tree, before you continue to remove eDirectory you should:

1) Press Alt+Esc and enter Set Timesync Type = Secondary at the console prompt.

2) Go to another directory-enabled server in this eDirectory tree, a server that has the time set correctly, and enter Set Timesync Type = Single at the console prompt.

After eDirectory has been removed, update the AUTOEXEC.NCF files on both servers by changing the line set Default Time Server Type = from Single to Secondary in the one case and from Secondary to Single in the other case.

If a TIMESYNC.NLM configuration file (TIMESYNC.CFG) exists on either or both servers, be sure to update it also (via MONITOR.NLM). These steps are necessary to ensure that if the server is taken down and restarted, the time server type will be correct.

Source: NWCONFIG.NLM
Explanation: In the single reference time synchronization method, there must be ONE single reference time server on the network at all times. If the server that Novell eDirectory is being removed from is that single reference server, that role should be assigned to a different server BEFORE removing Novell eDirectory.
Action: Follow the steps in the message.

NWCONFIG-X-483: The ISSLIB.NLM just loaded will not work with the CLIB.NLM currently loaded. For ISSLIB.NLM to work, a version of the CLIB.NLM either having revision number 4.01e or later is required. Unload the currently loaded CLIB.NLM and reload the correct version of CLIB.NLM.

Source: NWCONFIG.NLM
Explanation: ISSLIB only works with the more current versions of CLIB.
Action: Follow the suggestions in the message.

NWCONFIG-X-484: Warning: NWCONFIG has detected that no disk mirroring has been configured. This is allowable, but not recommended, because disk mirroring is an important part of full mirrored-server fault tolerance.

Source: NWCONFIG.NLM
Explanation: Disk mirroring is an important part of full mirrored-server fault tolerance.
Action: Before continuing with NWCONFIG, establish disk mirroring.

NWCONFIG-X-485: Warning: Some problems still exist with disk mirroring. Mirror status description: description. These problems must be resolved before completing the installation.

Source: NWCONFIG.NLM
Explanation: Some problems still exist with disk mirroring.
Action: Make sure the correct disk driver is loaded. Retry creating disk mirroring. If the problem persists, contact a Novell support provider.

NWCONFIG-X-486: NWCONFIG.NLM tried to load the NLM_name to enable serve- to-server communication but failed to do so for some unknown reason. It is not possible now to copy files from a NetWare server.

Source: NWCONFIG.NLM
Explanation: Server-to-server communication, necessary for file copy, is not possible unless the NLM indicated in the message is loaded.
Action: Try to determine from the console screen why the indicated NLM did not load. If possible, fix the problem. Otherwise, contact a Novell support provider.

NWCONFIG-X-488: For the installation to continue, the current version of ICMD.NLM is required to be loaded. NWCONFIG.NLM could not find a copy of the ICMD.NLM in any of the NetWare boot partitions created, or the copies of the ICMD.NLM found in the NetWare boot partitions were corrupted and hence not loadable. Installation cannot continue.

Source: NWCONFIG.NLM
Explanation: The ICMD NLM must be loaded to continue the installation.
Action: Contact a Novell support provider.

NWCONFIG-X-490: NWCONFIG.NLM could not move the old pre-4.1 NDS container audit file name to the root of the SYS: volume. Old audit information will not be available for the corresponding container.

Source: NWCONFIG.NLM
Action: If old audit information is necessary, contact a Novell support provider.

NWCONFIG-X-491: A NetWare boot partition should be created on at least one of the devices so that NWCONFIG.NLM can copy NetWare server boot files to that NetWare boot partition. This will let NetWare boot from that device.

Source: NWCONFIG.NLM
Explanation: A NetWare boot partition is required to boot NetWare.
Action: Create at least one NetWare boot partition on one of the devices so that NWCONFIG.NLM can copy NetWare server boot files to that NetWare boot partition. This will allow NetWare to boot from that device.

NWCONFIG-X-496: NWCONFIG.NLM could not detect any NetWare bOOT partitions. There must be at least one NetWare BOOT partition that can be identified as a destination drive.

Source: NWCONFIG.NLM
Action: NWCONFIG searched for a NetWare boot partition but failed to find one.
Action: Make sure the correct disk driver is loaded. If a NetWare boot partition was not created, create a NetWare boot partition on a device. Retry the operation. If the problem persists, contact a Novell support provider.

NWCONFIG-X-501: The installation NLM could not create the language configuration file LCONFIG.SYS due to some system error. Because of this, the NetWare server is likely to assume code page 437 during reboot.

Source: NWCONFIG.NLM
Action: If a code page other than 437 is needed, contact a Novell support provider.

NWCONFIG-X-502: The installation NLM failed to set the appropriate OS language in the language configuration file LCONFIG.SYS due to some system error. The NetWare server may not reboot in the user-preferred language.

Source: NWCONFIG.NLM
Action: If a language other than English is needed, contact a Novell support provider.

NWCONFIG-X-503: The installation NLM failed to set the correct creation date and time of the language configuration file LCONFIG.SYS.

Source: NWCONFIG.NLM
Action: None. This message is for information only.

NWCONFIG-X-504: Bindery files have been upgraded previously on this server. In the screen that follows, you may elect to re-upgrade if you desire.

Upgrading the bindery again is not advisable (although occasionally it may be necessary) because an additional upgrade might invalidate trustee rights on files for this server’s volumes.

Source: NWCONFIG.NLM
Action: Follow the suggestions in the message.

NWCONFIG-X-516: The first octet of the IP address determines the type of network. In Class A networks, the first octet can only contain numbers in the range range. In Class B networks, the first octet contains the numbers in the range range. In Class C networks, the first octet contains the numbers in the range range.

Source: NWCONFIG.NLM
Explanation: The subnet mask was not set or was not set correctly.
Action: Set the subnet mask using the appropriate values for the network class.

NWCONFIG-X-518: The IP address field should first be initialized before initializing the mask field.

Source: NWCONFIG.NLM
Explanation: You tried to set the mask before specifying the IP address.
Action: Specify the IP address first, then the mask.

NWCONFIG-X-523: NWCONFIG.NLM could not load name.NLM, possibly because the NLM was not located in the search directory.

Source: NWCONFIG.NLM
Explanation: The NLM could not be found.
Action: Make sure the NLM is installed and a search path points to the NLM’s location.

NWCONFIG-X-524: NWCONFIG.NLM could not import from NWPA certain functions that are required for device scanning. Autodiscovery of CDMs is not possible. Choose a CDM by selecting the Select Additional or Modify Selected Disk/LAN drivers option.

Source: NWCONFIG.NLM
Explanation: When you tried to load device drivers, NetWare could discover the adapter, but could not discover CDMs.
Action: Try unloading the HAM and then executing the automatic discovery driver process again, or try loading the CDM manually. If these steps don’t work, make sure the devices are installed and functioning properly.

NWCONFIG-X-525: NWCONFIG.NLM could not register with NWPA.NLM an inquiry function that is required for device scanning. Autodiscovery of CDMs is not possible. Choose a CDM by selecting the Select Additional or Modify Selected Disk/LAN Drivers option.

Source: NWCONFIG.NLM
Explanation: For some reason, NWCONFIG was unable to search for hardware and load drivers automatically.
Action: Try unloading and reloading NWCONFIG. If the problem still occurs, contact Novell Technical Support.

NWCONFIG-X-526: NWCONFIG.NLM could not import from NWPA.NLM certain functions that are required for device scanning. Autodiscovery of CDMs is not possible. Choose a CDM by selecting the Load an Additional Driver option.

Source: NWCONFIG.NLM
Explanation: For some reason, NWCONFIG was unable to search for hardware and load drivers automatically.
Action: Try unloading and reloading NWCONFIG. If the problem still occurs, contact Novell Technical Support.

NWCONFIG-X-527: NWCONFIG.NLM could not register with NWPA.NLM an inquiry function that is required for device scanning. Autodiscovery of CDMs is not possible. Choose a CDM by selecting the Load an Additional Driver option.

Source: NWCONFIG.NLM
Explanation: For some reason, NWCONFIG was unable to search for hardware and load drivers automatically.
Action: Try unloading and reloading NWCONFIG. If the problem still occurs, contact Novell Technical Support.

NWCONFIG-X-537: This program was unable to restore Novell eDirectory due to an internal error.

Source: NWCONFIG.NLM
Explanation: Something prevented restoration of Novell eDirectory from a backup.
Action: Dismount and remount the SYS: volume, run DSREPAIR, then try to restore the directory again.

NWCONFIG-X-538: Warning: The object corresponding to the server you are restoring is not found in Novell eDirectory. If you continue, this object will be restored. The restoration cannot proceed until this object is visible.

Source: NWCONFIG.NLM
Explanation: When you tried to restore Novell eDirectory, the Server object could not be found.
Action: Run DSREPAIR and try the restore process again.

NWCONFIG-X-539: This program was unable to verify the existence of the previous Server object due to in-progress synchronization. Wait for a while, and then try again. Error code: number.

Source: NWCONFIG.NLM
Explanation: During an attempt to restore a server, the Server object could not be verified.
Action: Some kind of synchronization process is happening; for example, external references are being updated. Wait for awhile and try again.

NWCONFIG-X-540: The file server name, internal IPX net number, or key pair of the Server object you wish to restore is different from one that previously existed. The restoration cannot proceed.

Source: NWCONFIG.NLM
Explanation: The Server object to be restored must be identical to one that existed before.
Action: Make sure that the file server name, internal IPX net number, and key pair are the same as those of the previous server object.

NWCONFIG-X-543: The restoration of Novell eDirectory failed, error code number.

Source: NWCONFIG.NLM
Explanation: The device from which you are restoring Novell eDirectory might be off line or not operating correctly.
Action: Make sure the device you are restoring from is online and operating correctly.

NWCONFIG-X-544: Warning: Some volumes remain without objects created for them in Novell eDirectory. Installation should continue normally. After installation completes, you will need to load NWCONFIG.NLM and upgrade mounted volumes into eDirectory.

Source: NWCONFIG.NLM
Explanation: If volumes are created before Novell eDirectory is installed, they are sometimes not upgraded into the eDirectory when eDirectory is installed.
Action: To add the Volume objects to eDirectory, load NWCONFIG and select Directory Options > Upgrade Mounted Volumes into the Directory.

NWCONFIG-X-545: The backup of Novell eDirectory failed, error code number.

Source: NWCONFIG.NLM
Explanation: The backup failed for an unknown reason.
Action: Try running DSREPAIR, then try the backup again. Make sure all devices are online and functioning correctly.

NWCONFIG-X-546: The attempt to redirect server references failed, error code number.

Source: NWCONFIG.NLM
Explanation: The attempt to move a master replica failed.
Action: Run DSREPAIR on the server you tried to move the replica to. Delete and reinstall Novell eDirectory.

NWCONFIG-X-547: The attempt to restore server references failed, error code number.

Source: NWCONFIG.NLM
Explanation: When you reinstalled Novell eDirectory, NetWare couldn’t reference the eDirectory place holders you created when eDirectory was deleted. This might be because you created a new context hierarchy.
Action: Run DSREPAIR.

NWCONFIG-X-548: Warning: An attempt to open configuration file STARTUP.NCF failed. Error code: number.

You may still configure PSMs, but later you will have to manually add the LOAD commands to the configuration file if you want the driver LOAD operations to remain after the server reboots.

Source: NWCONFIG.NLM
Explanation: The STARTUP.NCF file could not be opened. It might be corrupted or it might have been accidentally deleted.
Action: To view the STARTUP.NCF file (or to create a new one if necessary) load NWCONFIG and select NCF File Options > Edit STARTUP.NCF File.

NWCONFIG-X-549: Warning: An attempt to open configuration file AUTOEXEC.NCF failed. Error code: number.

You may still configure PSMs, but later you will have to manually add the LOAD commands to the configuration file if you want the driver LOAD operations to remain after the server reboots.

Source: NWCONFIG.NLM
Explanation: The AUTOEXEC.NCF file could not be opened. It might be corrupted or it might have been accidentally deleted.
Action: To view the AUTOEXEC.NCF file (or to create a new one if necessary) load NWCONFIG and select NCF File Options > Edit AUTOEXEC.NCF File.

NWCONFIG-X-550: No Platform Support Module files (*.PSM) can be found.

Source: NWCONFIG.NLM
Explanation: Platform support modules required for multiprocessing could not be found in the Drivers subdirectory of the NetWare boot directory.
Action: If the files are located somewhere else, move them to the Drivers subdirectory under the NetWare boot directory. If the files cannot be found, copy them from the NetWare CD.

NWCONFIG-X-551: No PSM driver files (*.PSM) were found at this path.

Source: NWCONFIG.NLM
Explanation: The path you specified does not contain .PSM files.
Action: PSM files are usually stored in the Drivers subdirectory of the NetWare boot directory. If you cannot find them, copy them from the NetWare CD.

NWCONFIG-X-553: Abend: ScanTrusteeRights reported too many trustees.

Source: NWCONFIG.NLM
Explanation: A request was made to the NetWare operating system for a certain amount of information, but more information was returned than was requested. This indicates that the system is not stable.
Action: Contact a Novell support provider.

NWCONFIG-X-555: Index for saveData out of range in Mirror DeleteAction().

Source: NWCONFIG.NLM
Explanation: If you tried to delete a partition from a mirrored group, one of the disks in the group is offline.
Action: You can still delete the partition from the mirrored group.

NWCONFIG-X-557: This volume is not a legitimate SYS: volume. If you are renaming a volume back to SYS:, make certain that you name the correct volume back to SYS:.

Source: NWCONFIG.NLM
Explanation: You might be trying to rename a volume as SYS: that was not originally a SYS: volume. You can only rename a volume as SYS:, if it was created as a SYS: volume by NetWare.
Action: If you do not have a SYS: volume, re-create the partition and let NetWare create the SYS: volume on it.

NWCONFIG-X-558: The Novell eDirectory database was not updated with this latest change. Please attempt to remedy this by manually changing the name through ConsoleOne or NetWare Administrator.

Source: NWCONFIG.NLM
Explanation: When you used NWCONFIG to rename a volume, something prevented Novell eDirectory from renaming the corresponding Volume object in the eDirectory database. The database might have been resynchronizing or otherwise unavailable for updates.
Action: Use ConsoleOne to rename the Volume object manually.

NWCONFIG-X-560 - 579: API failed with code number.

Source: NWCONFIG.NLM
Explanation: A Media Manager call failed. There might be a hardware or driver problem, or there might be an inconsistency between the partition table and the disk geometry.
Action: Make sure drives are online and drivers loaded. Look for disk or driver problems. Try setting the server parameter Ignore Disk Geometry to On. (Load MONITOR.NLM and select Server Parameters > Disk > Ignore Disk Geometry.)

NWCONFIG-X-580: Internal Error: No IPX/SPX symbols available.

Source: NWCONFIG.NLM
Explanation: The IPXSPX NLM is not in SYS:SYSTEM. It was probably not loaded.
Action: Try loading IPXSPX.NLM manually into SYS:SYSTEM. If the file has been deleted, copy it from the NetWare installation CD.

NWCONFIG-X-581: The installation program was unable to modify Novell eDirectory information. The error code returned was number.

Source: NWCONFIG.NLM
Explanation: NWCONFIG could not update an object into Novell eDirectory.
Action: Use ConsoleOne to determine what objects were not updated into the directory.

NWCONFIG-X-583: NWCONFIG.NLM failed to register with the media manager as a valid application. This means that you will not be able to perform any of the partition or volume options within NWCONFIG.NLM.

Source: NWCONFIG.NLM
Explanation: For some reason, NWCONFIG could not register with the Media Manager. Therefore, the functions relating to Legacy (or Traditional) Disk Options cannot be used. You can still use NWCONFIG’s other functions.
Action: Try reloading NWCONFIG. If the problem still occurs, NWCONFIG could be corrupted, Media Manager might not be loaded, or a virus could be causing the problem.

NWCONFIG-X-584: This partition is not a NetWare partition and cannot be edited through NWCONFIG.NLM.

Source: NWCONFIG.NLM
Explanation: NWCONFIG can only be used to edit NetWare partitions.
Action: To edit the nonNetWare partitions, use a utility that came with your computer operating system.

NWCONFIG-X-586: Failed to initialize NWI.NLM.

Source: NWCONFIG.NLM
Explanation: NWI NLM drives modules used to preinstall servers with NetWare. The NWI module could not be started, possibly due to low memory.
Action: Provide more memory. Contact the server vendor if problem continues.

NWCONFIG-X-587: Failed to load SLP.NLM, probably because it is not in the search path.

Source: NWCONFIG.NLM
Explanation: A search path might have been deleted or the file might have been moved to a location not in a search path.
Action: Find the file and make sure there is a search path pointing to its location.

NWCONFIG-X-588: Failed to load NCFUPD.NLM, probably because it is not in the search path.

Source: NWCONFIG.NLM
Explanation: A search path might have been deleted or the file might have been moved to a location not in a search path.
Action: Find the file and make sure there is a search path pointing to its location.

NWCONFIG-X-589: Failed to load SCMD.NLM, probably because it is not in the search path.

Source: NWCONFIG.NLM
Explanation: A search path might have been deleted, or the file might have been moved to a location not in a search path.
Action: Find the file and make sure there is a search path pointing to its location.

NWCONFIG-X-593: Failed to upgrade the Novell eDirectory database.

Source: NWCONFIG.NLM
Explanation: You might have tried to install the Novell eDirectory database on a NetWare 6 server that already has an eDirectory database. Or something prevented NWCONFIG from upgrading an earlier version of eDirectory to the NetWare 6 version.
Action: If your NetWare 6 server already has an eDirectory database, no action is necessary. If NWCONFIG could not upgrade an earlier version of the eDirectory database, try running DSREPAIR on the existing database, then try upgrading the database again. If this fails to solve the problem, contact Novell Technical Services.

NWCONFIG-X-594: No device was found with at least number free which is the minimum required for the SYS: volume.

Source: NWCONFIG.NLM
Explanation: To create a SYS: volume, the disk must have at least the amount of free space specified in the message.
Action: Create a bigger partition; use a bigger disk, if necessary.

NWCONFIG-X-595: This device does not have at least number free which is the minimum required for the SYS: volume.

Source: NWCONFIG.NLM
Explanation: To create a SYS: volume, the server must have at least the specified amount of free space in a NetWare partition.
Action: If there is sufficient free space on the disk, re-create the NetWare partition to make it the required size. Use a larger disk if necessary.

NWCONFIG-X-596: No hard drive or MO was found.

Source: NWCONFIG.NLM
Explanation: The hard drive or magneto optical device might not be on line, or the magneto optical device might not have a cartridge seated properly.
Action: Make sure disks and magneto optical devices are online and that cartridges in magneto optical devices are seated correctly.

NWCONFIG-X-600: The search for Novell eDirectory trees failed. name returned number.

Source: NWCONFIG.NLM
Explanation: During installation, a list of Novell eDirectory trees could not be found. There is probably a problem with the LAN.
Action: Check all LAN segments, cabling, connection, etc. Use a network analyzer if necessary.

NWCONFIG-X-601, 602: API failed with code number.

Source: NWCONFIG.NLM
Explanation: A Media Manager call failed. There might be a hardware or driver problem, or there might be an inconsistency between the partition table and the disk geometry.
Action: Make sure drives are on line and drivers loaded. Look for disk or driver problems. Try setting the server parameter Ignore Disk Geometry to On. (Load MONITOR.NLM and select Server Parameters > Disk > Ignore Disk Geometry.)

NWCONFIG-X-603: The attempt to set the preferred DS tree to name failed. The tree could not be found.

Source: NWCONFIG.NLM
Explanation: An incorrect address or a LAN problem might be preventing the server from seeing the tree.
Action: Make sure server and network addresses are correct. Troubleshoot the LAN.

NWCONFIG-X-606: The user name could not be found in the name tree.

Source: NWCONFIG.NLM
Explanation: The user object does not exist in the specified tree.
Action: The user’s grace logins have probably expired. Reset the user’s password.

NWCONFIG-X-607: The attempt to authenticate to server name by user name failed. The most likely reason is that the server name is not in the name tree.

Source: NWCONFIG.NLM
Explanation: The specified server might not be in the tree, the user might not have used the correct password, or a LAN problem could prevent authentication.
Action: Make sure the server is in the tree and the password is correct. To troubleshoot server communication problems, see Unable to Communicate with Server, -625 Errors in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

NWCONFIG-X-608: The attempt to authenticate to server name by user name failed. Error: number

Source: NWCONFIG.NLM
Explanation: The specified server might not be in the tree, the user might not have used the correct password, or a LAN problem could prevent authentication.
Action: Make sure the server is in the tree and the password is correct. To troubleshoot server communication problems, see Unable to Communicate with Server, -625 Errors in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

NWCONFIG-X-610: The attempt to log in to server name by user name failed. The user does not exist.

Source: NWCONFIG.NLM
Explanation: The user object might not exist, or the user might have specified the wrong context.
Action: Make sure the user object exists and that the user enters the correct context when logging in.

NWCONFIG-X-611: The attempt to log in to server name by user name failed. Either the user does not exist or the password is not correct.

Source: NWCONFIG.NLM
Explanation: The user is using the wrong password, the user object might not exist, or the user might have specified the wrong context.
Action: Make sure the user object exists and that the user is specifying the correct context. Reset the users password if necessary.

Error getting drive information.

Source: NWCONFIG.NLM
Explanation: NWCONFIG tried to get drive information, but received an error. There might be a drive or controller problem.
Action: Troubleshoot the drive.

Error getting partition information.

Source: NWCONFIG.NLM
Explanation: NWCONFIG tried to get partition information, but received an error. There might be a drive or controller problem.
Action: Troubleshoot the drive and controller.

Error occurred while retrieving partition table.

Source: NWCONFIG.NLM
Explanation: Media Manager was queried for partition information and returned an error. There might be a problem with the drive or controller. The message might also be generated if there is no partition table. However, in this case you receive additional error messages about the missing partition table, and NetWare tries to create the table for you.
Action: Troubleshoot the drive or controller.

Error moving file name to SYS volume root.

Source: NWCONFIG.NLM
Explanation: Something prevented bindery objects from being upgraded into Novell eDirectory.
Action: Run DSREPAIR and try upgrading bindery objects again.

An error has occurred. Failed to delete this volume after unsuccessful DS object creation.

Source: NWCONFIG.NLM
Explanation: When a volume was created, something prevented the creation of the corresponding Volume object in Novell eDirectory. NetWare then attempted but failed to delete the physical volume, to maintain consistency with eDirectory.
Action: Upgrade the mounted volume into the eDirectory. Using ConsoleOne, select Tools > Disk Management.

Error file name: original size number, new size number.

Source: NWCONFIG.NLM
Explanation: An error occurred when the system tried to copy NetWare files over existing NetWare files.
Action: Try to copy the files again.

Error file name, offset number: original number, new number.

Source: NWCONFIG.NLM
Explanation: An error occurred when the system tried to copy NetWare files over existing NetWare files.
Action: Try to copy the files again.