62.0 SERVER Messages

The following includes messages from SERVER.EXE.

SERVER-X-6: Invalid screen ID passed to screen manager. Module: name. Code offset in module: offset.

Source: SERVER.EXE
Explanation: An NLM (the module named in the message) tried to print to a nonexistent screen.
Possible Cause: The NLM is probably an outdated version or is corrupted.
Action: Replace the NLM with an updated or uncorrupted copy.

SERVER-X-83: Stack overflow detected by kernel.

Source: SERVER.EXE
Possible Cause: This is a problem in the code of an NLM or other file.
Action: Contact the NLM or file vendor.

SERVER-X-93, 95, 96: Api_name was called with work to do already enqueued.

Source: SERVER.EXE
Explanation: There is an internal programming error in the NLM.
Action: Contact the NLM vendor.

SERVER-X-106: Error reading MT safe API list in NLM’s XDC data.

Source: SERVER.EXE
Explanation: There was an error reading part of an NLM. The NLM might be corrupted or there might be a disk problem.
Action: Check disks to make sure they are functioning correctly. If the disk system is functioning, then contact the NLM vendor.

SERVER-X-113: Error reading MT unsafe API list in NLM’s XDC data.

Source: SERVER.EXE
Explanation: There was an error reading part of an NLM. The NLM might be corrupted or there might be a disk problem.
Action: Check disks to make sure they are functioning correctly. If the disk system is functioning, then contact the NLM vendor.

SERVER-X-135: API name is not accessible from address space name.

Source: SERVER.EXE
Possible Cause: An NLM loaded into a protected address space is not designed to run in protected memory.
Action: Run the NLM in the kernel address space.

SERVER-X-137: API name is not accessible from address space name.

Source: SERVER.EXE
Action: See message SERVER-X-135: API name is not accessible from address space name..

SERVER-X-196: name file exists, overriding default locale values.

Source: SERVER.EXE
Explanation: The language specified by the file will be used instead of the default language.
Action: This message is for information only. No action is necessary.

SERVER-X-197: name file exists but is invalid. NOT overriding default values.

Source: SERVER.EXE
Explanation: Each language supported by NetWare has a language configuration file that is loaded into the operating system tables. In this case, the language specified by the file will NOT be used instead of the default language.
Possible Cause: The language configuration file is corrupted.
Action: Delete the corrupted file and copy the original file from the master CD-ROM or diskette.

SERVER-X-202: Detected user thread hogging the CPU.

Source: SERVER.EXE
Explanation: A thread running in a protected address space has not relinquished the CPU, causing the address space to fault.
Action: How the server responds to the fault depends on whether the Memory Protection Fault Cleanup parameter is set to On or Off and whether the address space is restartable. See Memory Parameters in the NW 6.5 SP8: Utilities Reference and Managing Server Memory in the NW 6.5 SP8: Server Memory Administration Guide.

Treat the problem as an abend: review the abend.log file in sys:\system; break into the debugger to find more information (press Shift + Shift + Alt + Esc); if necessary, perform a core dump. For more information, see Resolving Abends in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

SERVER-X-286: Invalid resource tag passed to api_name.

Source: SERVER.EXE
Explanation: There could be a bug in the NLM, or the NLM might be corrupted.
Action: Contact the NLM vendor.

SERVER-X-312: Invalid resource tag passed to api_name.

Source: SERVER.EXE
Explanation: There could be a bug in the NLM, or the NLM might be corrupted.
Action: Contact the NLM vendor.

SERVER-X-276: Invalid screen ID passed to screen manager. Module: name. Code offset in module: offset.

Source: SERVER.EXE
Explanation: See SERVER-X-6: Invalid screen ID passed to screen manager. Module: name. Code offset in module: offset..

SERVER-X-384: This module is using one outdated API call. You should upgrade to a newer module when it becomes available.

Source: SERVER.EXE
Possible Cause: The operating system displays this message whenever an NLM is loaded that is using old API calls. NetWare renamed some of the APIs as additional resources that were tracked. Resource tracking provides statistical information about how many resources are being used. It also protects the file server from loadable modules that try to use more than their share of resources and forces them to relinquish all their resources when unloaded. The old API calls work; however, they are slower than the new API calls.
Action: Contact the vendor of the NLM for an updated version. Continue to use the version until you receive the newer version.

SERVER-X-410: Insufficient memory to autoload modules.

Source: SERVER.EXE
Explanation: An unsuccessful attempt to automatically load specified NLM programs during startup was made.
Possible Cause: The server might not have enough available memory.
Action: Add more memory to the server or remove the instructions to autoload the specified NLM programs from the autoexec.ncf file. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

SERVER-X-466: SetInputToOutputCursorPosition called with invalid screen ID.

Source: SERVER.EXE
Explanation: An invalid screen ID was used.
Possible Cause: This is a problem in the code of an NLM or other file.
Action: Contact the NLM vendor.

SERVER-X-467: SetInputToOutputCursorPosition called when another process is already using the keyboard.

Source: SERVER.EXE
Possible Cause: This is a problem in the code of an NLM or other loaded file.
Action: Contact the NLM or file vendor.

SERVER-X-498: Insufficient memory to allocate initial memory test block.

Source: SERVER.EXE
Explanation: System initialization failed.
Possible Cause: The server does not have enough memory.
Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

SERVER-X-508: Invalid resource tag passed to RegisterHardwareOptions.

Source: SERVER.EXE
Explanation: An NLM was trying to register hardware that it needed to use. The server detected that the resource tag passed as a parameter to the RegisterHardwareOptions routine was not valid. The hardware was not registered, and the server returned an error to the NLM. The NLM will not be able to perform properly. The NLM might have had a problem when it tried to get the resource tag before calling RegisterHardwareOptions.
Possible Cause: If the server is low on memory, the request to create the resource tag might have failed. In this case a preceding error message should indicate the out- of-memory problem.
Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.
Possible Cause: There could also be a bug in the NLM that is calling RegisterHardwareOptions with an invalid resource tag.
Action: If memory is not the problem and the error persists, contact the vendor for an updated version of the NLM.

SERVER-X-510: CheckAndAddHardware could not allocate a resource tag.

Source: SERVER.EXE
Possible Cause: This error could occur for one of the following reasons:

  • The NLM made a call to an API for a previous version of NetWare or IntranetWare.

  • The operating system tried to allocate memory for the resource, but the server does not have enough memory.

In either case, the NLM that called CheckAndAddHardware is not able to register the hardware resources that it needs to use. The NLM will not be able to function properly.

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 error persists, contact a Novell support provider or the NLM vendor.

SERVER-X-518: RemoveHardwareOptions called with invalid pointer.

Source: SERVER.EXE
Explanation: When a LAN or disk driver tried to unload, it called the RemoveHardwareOptions function with an invalid pointer.
Possible Cause: This error probably indicates an outdated driver.
Action: Update the offending LAN or disk driver with a newer version. If the problem persists, contact a Novell support provider.

SERVER-X-585: Process has been created for name (name), with a stack size of size, less than the required stack size of size.

Source: SERVER.EXE
Explanation: The specified stack size was too small, so the process created a stack of the required size.
Possible Cause: This is a problem in the module code.
Action: Contact the module vendor.

SERVER-X-586: Invalid resource tag passed to CreateProcess.

Source: SERVER.EXE
Explanation: While processing a request to create a new process, the server passed an invalid resource tag to the create process routine. The server returned an error to the NLM that was trying to create the new process. The process was not created.
Possible Cause: The NLM might have had a problem when it tried to get the resource tag before calling a create process. If the server is low on memory, a preceding error message should indicate the out-of-memory problem. There also could be a bug in the NLM, or the NLM might be corrupted. In either case, the NLM will not be able to complete the operation for which the process was needed. If the NLM is in the process of loading, it might fail to load.
Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide. If there is no memory problem, try reloading the NLM from the manufacturer’s original media. If the error persists, contact the vendor for an updated version of the NLM.

SERVER-X-587: CreateProcess called with stack size too small.

Source: SERVER.EXE
Explanation: The system tried to load an NLM that allocated an inadequate amount of stack space for itself.
Possible Cause: The NLM is outdated or corrupted.
Action: Try reloading the NLM from its original media and try again. If the problem persists, contact the vendor for an updated version of the NLM.

SERVER-X-588: CreateProcess could not allocate a process control block.

Source: SERVER.EXE
Explanation: If this error occurs while the system is trying to load an NLM, the NLM will not be able to load and run properly.
Possible Cause: The system does not have enough memory to start a new process. The request to create a new process might have been internal to the server or generated by an NLM.
Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

SERVER-X-607: ScheduleWorkToDo passed invalid resource tag.

Source: SERVER.EXE
Explanation: There could be a bug in the NLM, or the NLM might be corrupted.
Action: Contact the NLM vendor.

SERVER-X-610, 611: Api_name was called with work to do already enqueued.

Source: SERVER.EXE
Explanation: There is an internal programming error in the NLM.
Action: Contact the NLM vendor.

SERVER-X-613: Invalid line in command file.

Source: SERVER.EXE
Explanation: A message that was to be displayed on the screen was too long.
Possible Cause: This problem might have occurred when this product was translated.
Action: No further action is required.

SERVER-X-618: Invalid startup command: string.

Source: SERVER.EXE
Explanation: A command other than LOAD or SET was issued from within a startup.ncf file.
Action: Edit the startup.ncf and delete any commands other than LOAD or SET. For more information, see Using Server Batch Files in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

SERVER-X-701: Api_name was called with work to do already enqueued.

Source: SERVER.EXE
Explanation: There is an internal programming error in the NLM.
Action: Contact the NLM vendor.

SERVER-X-703: Module is using number outdated APIs.

Source: SERVER.EXE
Explanation: The operating system displays this message whenever an NLM is loaded that is using old API calls. The NLM will still function.
Action: Contact the vendor of the NLM for an updated version. Continue to use the version until you receive the newer version.

SERVER-X-719: Error reading message file.

Source: SERVER.EXE
Explanation: This error might indicate file system or data corruption.
Action: Run VREPAIR and restart the system.

Warning: If you delete the volume, all data will be destroyed. You will have to restore the data from a backup.

If the problem persists, make sure a volume backup exists. Delete the volume, re-create it using NWCONFIG, and restore the data from the backup.

SERVER-X-720: Error allocating memory for message file.

Source: SERVER.EXE
Possible Cause: The server probably does not have enough memory to load the message file.
Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide. If memory is not the problem, try running VREPAIR; then restart the system.

Warning: If you delete the volume, all data will be destroyed. You will have to restore the data from a backup.

If the problem persists, make sure a volume backup exists. Delete the volume, re-create it using NWCONFIG, and restore the data from the backup.

SERVER-X-721: INVALID FORMAT.

Source: SERVER.EXE
Possible Cause: When setting a server parameter, you did not use the correct format to specify the time zone.
Action: Specify the time zone in the correct format. For help, see the Time Parameters under SET in the NW 6.5 SP8: Utilities Reference.

SERVER-X-746: Server NetWare Copyright Violation! Call SUPERVISOR! Server at address number/node also has my serial number.

Source: SERVER.EXE
Explanation: The copy of NetWare or IntranetWare running on the specified server is illegal because another server on the network has the same serial number. All logged-in users will receive this message.
Action: Bring down the server that is using the illegal copy of NetWare or IntranetWare, and buy a valid copy of it to run on the server.

SERVER-X-816: Invalid resource tag passed to AllocateConnectionNumber.

Source: SERVER.EXE
Explanation: The server was processing a request to create a new connection, but the resource tag that was passed in as a parameter to create a connection call was invalid. The server will not allocate the connection, and it will return an error to the NLM that requested the connection.
Possible Cause: A previous out-of-memory error occurred when the NLM tried to get the connection resource tag.
Action: If the preceding message indicates that the system is out of memory, make more memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.
Possible Cause: An internal program error occurred in the NLM.
Action: If the problem does not appear to be memory related, contact a Novell support provider and provide an accurate account of the circumstances that led to the error so the support provider can re-create the problem and find a solution.

SERVER-X-817: Swap-in failed (error_code, hexadecimal_error_code). This may cause a program to terminate unexpectedly.

Source: SERVER.EXE
Explanation: The server couldn’t read data from the swap file on the disk. There might be a disk problem or a volume containing a swap file might have been dismounted when there was no other swap file to hold the data.
Action: If a volume containing a swap file was dismounted, and there was no other swap file in which to store the data, applications that use virtual memory could fail and be unloaded. Reload the applications. To prevent the problem in the future, make sure that a volume containing a swap file is not dismounted unless there is a swap file on another volume to hold the data.

SERVER-X-820: Average Page In Rate Threshold Exceeded

Source: SERVER.EXE
Explanation: The average number of pages swapped to disk each second has exceeded the value of the Average Page In Alert Threshold parameter.
Action: The server might be running low on memory, causing it to swap data to disk more often.

SERVER-X-830: Short term memory allocator is out of memory. Number attempts to get more memory failed.

Source: SERVER.EXE
Explanation: The request for short-term memory failed.
Possible Cause: The server is out of memory.
Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

SERVER-X-831: Process_name Process did not relinquish control frequently. Module: name. Code offset in module: offset.

Source: SERVER.EXE
Explanation: Normally, NLM programs relinquish control of certain resources when a higher priority request comes in or when a certain process is completed. This message indicates that the NLM is not relinquishing control when it should, preventing higher priority processes from executing.
Possible Cause: The NLM might be corrupted, or the server might have a prerelease version of the NLM.
Action: Unload the NLM. Make sure the server has the most current version of the NLM; then reload it from the original CD-ROM or diskettes. If the problem persists, contact the vendor of the NLM.

SERVER-X-847: ERROR alias keyword too big.

Source: SERVER.EXE
Possible Cause: You created an alias keyword that was greater than 47 characters.
Action: Create an alias keyword of 47 characters or less.

SERVER-X-872: Insufficient memory to set up first load search path entry.

Source: SERVER.EXE
Explanation: When you executed SERVER.EXE, the server did not have enough memory to create the initial search path to the DOS partition or to the Sys: volume on the NetWare partition.
Possible Cause: The server is very low on memory.
Action: Add more memory.

SERVER-X-874: Insufficient memory to set up first load search path entry.

Source: SERVER.EXE
Action: See message SERVER-X-872: Insufficient memory to set up first load search path entry..

SERVER-X-879: Invalid path specified.

Source: SERVER.EXE
Explanation: The specified path length value is less than two characters long.
Action: Check the spelling of the path name; make sure the path begins with a volume name or a DOS drive letter.

SERVER-X-882: Insufficient memory to add search path.

Source: SERVER.EXE
Explanation: The SEARCH ADD command was used, but the server cannot allocate memory to expand the search path mapping.
Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

SERVER-X-884: Insufficient memory to add search path.

Source: SERVER.EXE
Action: See message SERVER-X-882: Insufficient memory to add search path..

SERVER-X-889: Invalid path specified.

Source: SERVER.EXE
Explanation: See message SERVER-X-879: Invalid path specified..

SERVER-X-892: Insufficient memory to add search path.

Source: SERVER.EXE
Explanation: See message SERVER-X-882: Insufficient memory to add search path..

SERVER-X-893: Insufficient memory to add search path.

Source: SERVER.EXE
Explanation: See message SERVER-X-882: Insufficient memory to add search path..

SERVER-X-894: Insufficient memory to add search path.

Source: SERVER.EXE
Explanation: See message SERVER-X-882: Insufficient memory to add search path..

SERVER-X-918: LOADER cannot find public symbol: API_name for module name.

Source: SERVER.EXE
Explanation: The loader could not find the module’s public symbol name in the Public Symbol table.
Action: Complete one of the following:

  • If you are a user, see the documentation for the NLM. Another module must be loaded before this module.

  • If you are a developer, verify the spelling of the symbol. Make sure the module that defined this symbol made it public. Implement auto-loading so that the module that defines the public symbol is automatically loaded before other modules that need access to this symbol.

SERVER-X-960: Page fault, insufficient rights to read from page.

Source: SERVER.EXE
Explanation: A module running in a protected address space tried to read from the kernel.
Possible Cause: This is a problem in the module code.
Action: You can try to run the module in the kernel address space, but remember that modules running in the kernel address space can abend the server. To solve the problem, contact technical support or the module vendor.

SERVER-X-962: Page fault, insufficient rights to write to page.

Source: SERVER.EXE
Explanation: A module running in a protected address space tried to write to the kernel.
Possible Cause: This is a problem in the module code.
Action: You can try to run the module in the kernel address space, but remember that modules running in the kernel address space can abend the server. To solve the problem, contact technical support or the module vendor.

SERVER-X-978: A fault occurred in a registered console command handler.

Source: SERVER.EXE
Possible Cause: An NLM caused a memory protection page fault when the command parser was called. The server might be using an unlicensed or outdated version of the NLM, or a version that is still under development.
Action: Determine which NLM caused the error and unload it.

SERVER-X-982: Insufficient memory for Command Process Resource tags.

Source: SERVER.EXE
Possible Cause: The server is low on contiguous memory.
Action: Add more memory or unload unnecessary NLM programs.

SERVER-X-983: Error allocating semaphores for Command Line Services

Source: SERVER.EXE
Possible Cause: Server is extremely low on memory.
Action: Add more memory.

SERVER-X-992: Command file processor unable to allocate work buffer.

Source: SERVER.EXE
Possible Cause: The server is running out of Alloc Short Term memory and cannot allocate enough of this type of memory to process command files.
Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

SERVER-X-993: Command file processor unable to allocate work buffer.

Source: SERVER.EXE
Action: See message SERVER-X-992: Command file processor unable to allocate work buffer..

SERVER-X-996: Too many input parameters passed to Command File processor.

Source: SERVER.EXE
Explanation: An .ncf file was passed more than 32 parameters.
Action: Reduce the required parameters to 32 or fewer.

SERVER-X-997: Invalid line in command file - line length exceeds number characters.

Source: SERVER.EXE
Possible Cause: A line in an .NCF file is too long.
Action: Make sure no trailing information comes after the commands in .NCF files. Edit the file if necessary. For more information, see Using Server Batch Files in the NW 6.5 SP8: Server Operating SystemAdministration Guide. (The file being processed should be a command (DOS) text file.)

SERVER-X-1002: The preferred language message file for this NLM is out of sync with the NLM; the default language will be used.

Source: SERVER.EXE
Explanation: The language message file contains a different number of messages than the NLM header file specifies.
Possible Cause: The NLM and the message file are probably not the same version; one has probably been updated but the other has not
Action: Use message and NLM files that are the same version.

SERVER-X-1004: ERROR alias text too big.

Source: SERVER.EXE
Possible Cause: The string for which you created an alias was longer than 511 characters.
Action: Make sure the alias string is 511 characters or less.

SERVER-X-1005: ERROR unable to allocate memory for an alias.

Source: SERVER.EXE
Possible Cause: The server is very low on memory.
Action: Add more memory or unload unnecessary NLM programs.

SERVER-X-1073: Unable to unload module name.

Source: SERVER.EXE
Explanation: The module could not be unloaded from an address space, possibly because another module was being unloaded.
Action: Wait and try again. If modules still cannot be unloaded, you will be prompted to shut down the address space.

SERVER-X-1132: Error reading from load file.

Source: SERVER.EXE
Possible Cause: The NLM the server is trying to load is not readable because a disk error occurred or the file is corrupted.
Action: Get a new copy of the NLM from the vendor or replace the disk.

SERVER-X-1134: Invalid load file format.

Source: SERVER.EXE
Explanation: The description text field of an NLM was invalid. This field should contain text (about the NLM) that is greater than zero and less than 128 characters long.
Possible Cause: The NLM in this case did not meet these criteria. This problem is due to manufacturer error, NLM corruption, or disk malfunction.
Action: Reload the NLM from the master CD-ROM or diskette. If the error persists, make sure the disk drive is operating properly. If the drive functions correctly, contact the vendor of the NLM for updates or fixes.

SERVER-X-1136: Invalid load file version.

Source: SERVER.EXE
Explanation: The version number of the file to be loaded is incorrect.
Action: Specify the name of a valid NetWare loadable file (probably an NLM), or find out if the file has been corrupted. If the file is corrupted, get a new copy of the file.

SERVER-X-1143: Unable to unload module name (error number).

Source: SERVER.EXE
Explanation: The NLM could not be unloaded.
Possible Cause: The module might have public symbols that other loaded NLM programs use, or other loaded NLM programs are dependent upon this module to be loaded.
Action: Check the documentation for the NLM. The documentation should specify which module or types of modules would be using it. These modules must be unloaded before the server can unload the module that produced the error message.

SERVER-X-1152: Node number is invalid and was ignored.

Source: SERVER.EXE
Explanation: When you loaded a LAN driver, you specified an invalid node number as a parameter. The server ignored the invalid node number and selected a node number that appeared to be valid.
Action: This message is for information only.

SERVER-X-1155: Node number configuration is NOT supported and was ignored.

Source: SERVER.EXE
Explanation: This is an informational message indicating that you specified a node number for a driver that does not allow you to specify a node number.

SERVER-X-1159: Repeated send retries number ignored.

Source: SERVER.EXE
Explanation: This is an informational message given when a driver is loaded and the number of send retries is repeated. The repeated number was ignored. The number of send retries is the number of times the board will resend a packet.

SERVER-X-1162: Repeated board name setting ignored.

Source: SERVER.EXE
Explanation: This is an informational message that given when a driver is loaded and the board name is repeated. The repeated name was ignored.

SERVER-X-1200: Number of supported frame types too big.

Source: SERVER.EXE
Explanation: The driver passed in a number of supported media types to the operating system that exceeded the system’s internal buffer limit of 32.
Possible Cause: The server might be using an outdated driver.
Action: Make sure the driver is certified for the NetWare server you are running and is functioning properly. If the server has a current and functional driver and the problem persists, contact a Novell support provider.

SERVER-X-1211: Repeated bus name setting ignored.

Source: SERVER.EXE
Explanation: This is an informational message given when a driver is loaded and the bus name is repeated. The repeated name was ignored.

SERVER-X-1214: Bus name configuration is not supported.

Source: SERVER.EXE
Possible Cause: When loading a driver, you specified a bus name that the card can’t support.
Action: Specify a bus name that the card can support.

SERVER-X-1229: Unsupported frame type setting ignored.

Source: SERVER.EXE
Explanation: A specified frame type was ignored when the LAN driver was loaded.
Possible Cause: The LAN driver might not support the frame type or the frame type might already be loaded.
Action: If necessary, replace the driver with one that does support the specified frame type.

SERVER-X-1278: QueueEventReport failed to allocate memory.

Source: SERVER.EXE
Explanation: The server is low on memory.
Action: Unload unnecessary modules or add more memory.

SERVER-X-1301, 1302, 1305, 1306: Error reading filename.

Source: SERVER.EXE
Explanation: The file could be locked or it could be corrupted.
Action: If another user is using the file, wait until the file is unlocked. If the file is not locked, it might be corrupted. Try restoring the file from a backup.

SERVER-X-1307: Invalid packed NLM filename.

Source: SERVER.EXE
Possible Cause: An NLM program that is not a File System Engine NLM is too large to be loaded. Four megabytes is the maximum size allowed.
Action: Do not try to load that NLM program.

SERVER-X-1308: Unable to allocate memory for NLM unpacking.

Source: SERVER.EXE
Explanation: The operating system was unable to allocate memory for unpacking the NLM.
Possible Cause: The operating system is out of memory.
Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

SERVER-X-1310: Filename is not a packed NLM.

Source: SERVER.EXE
Possible Cause: This file might not be an NLM at all.
Action: Make sure that the file the server is loading is really an NLM.
Possible Cause: The user is trying to load a file as an NLM that is not packed as NLM programs should be.
Action: If the server is still having problems, replace the problem NLM with a copy of the original.

SERVER-X-1311: This version of the loader doesn’t support this NLM compression format (version version).

Source: SERVER.EXE
Explanation: The operating system tried to load an NLM that is in an unsupported compression format.
Action: Make sure that any compressed NLM programs to be loaded are at the least in compression format v1.10.

SERVER-X-1312: Filename has an invalid size.

Source: SERVER.EXE
Explanation: This message reports when and how many incomplete packets were received.
Possible Cause: This problem can result from a defective network board, a malfunctioning LAN driver, or a problem with some other LAN hardware component.
Action: See Tips for Resolving General Communication Problems in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

SERVER-X-1316: Unable to allocate memory for data trees.

Source: SERVER.EXE
Explanation: The operating system was unable to allocate memory for data trees.
Possible Cause: The server is out of memory.
Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

SERVER-X-1318: Read past end of read buffer.

Source: SERVER.EXE
Explanation: While an NLM was being loaded, a read error occurred.
Possible Cause: The system did not recognize the end-of-file marker.
Action: Try to reload the original NLM. If the original NLM file is corrupted, contact the vendor of the NLM.

SERVER-X-1319: Error number reading source file.

Source: SERVER.EXE
Severity: Warning
Explanation: The operating system tried to load an NLM, but the process failed.
Possible Cause: This error is caused by internal errors relating to the NLM or to physical disk errors in the loading process. The NLM is corrupted.
Action: Load a new copy of the NLM from the master disk.
Possible Cause: The disk system is faulty.
Action: If the NLM is not at fault, check the disk system (cables, disk drive, and controller) for potential problems. If the server is still unable to load the NLM, call the vendor of the NLM for any fixes or updates.

SERVER-X-1321: Error number reading source file.

Source: SERVER.EXE
Severity: Warning
Action: See message SERVER-X-1319: Error number reading source file..

SERVER-X-1343: FreeObject received an invalid object pointer number.

Source: SERVER.EXE
Explanation: Memory might be corrupted.
Action: Replace memory or contact your support provider.

SERVER-X-1345: FreeObject detected corrupt preceeding redzone for object number.

Source: SERVER.EXE
Explanation: Memory might be corrupted.
Action: Replace memory or contact your support provider.

SERVER-X-1346: FreeObject detected object number is already free.

Source: SERVER.EXE
Explanation: There is probably an internal programming error in the NLM.
Action: Contact the NLM vendor.

SERVER-X-1353: FreeObject detected corrupt trailing redzone for object number, object size size.

Source: SERVER.EXE
Explanation: Memory might be corrupted.
Action: Replace memory or contact your support provider.

SERVER-X-1375: Invalid message file.

Source: SERVER.EXE
Explanation: The message file for an NLM on the console was invalid.
Possible Cause: The server might be using an outdated version of the file.
Action: Determine why the file is invalid and replace it with a valid file.

SERVER-X-1400: Error unloading killed loadable module.

Source: SERVER.EXE
Explanation: An error occurred while an NLM was being unloaded. The NLM is still loaded. A preceding message should explain why the module could not be unloaded.
Possible Cause: The error might have occurred because another module is still referencing public symbols or resources exported by this module. An NLM can be unloaded only when all other NLM programs that use its global variables are unloaded.
Action: Check the preceding message to see why the NLM was not unloaded. If necessary, unload the NLM that is using this module’s public symbols or resources; then unload this NLM.

SERVER-X-1401: Invalid resource tag passed to ParseDriverParameters.

Source: SERVER.EXE
Possible Cause: An NLM tried to register a driver parameter, but the module did not create a resource tag for the process.
Action: Contact the vendor for an updated version of the NLM.

SERVER-X-1512: Invalid load file format.

Source: SERVER.EXE
Explanation: When you tried to load a module, the server did not recognize the module as an NLM.
Possible Cause: The module may be corrupted or it may not be an NLM.
Action: If possible, try loading a different copy of the module or contact the module vendor.

SERVER-X-1514: Invalid procedure offsets within load file.

Source: SERVER.EXE
Explanation: Values within the load file header for a particular NLM were not what the system expected. The items in question include the initialization offset, code image length, exit procedure offset, and check unload procedure offset.
Action: This error indicates a corrupted NLM or a faulty disk system. Reload the NLM from the master CD-ROM or diskette, and check the disk system for potential problems.

SERVER-X-1532: Device_name deactivated for unknown reason.

Source: SERVER.EXE
Possible Cause: A hardware error probably occurred which deactivated the drive.
Action: See Disk Errors in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

SERVER-X-1533: Device name deactivated due to driver unload.

Source: SERVER.EXE
Explanation: This status message indicates that the drive was deactivated because the driver was unloaded.

SERVER-X-1534: Device name deactivated by driver due to device failure.

Source: SERVER.EXE
Explanation: This is a hardware error that usually generates other messages.
Action: Look for other messages for additional information about the problem. See Disk Errors in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

SERVER-X-1535: Device name deactivated due to user request.

Source: SERVER.EXE
Explanation: This informational message indicates that the specified drive was deactivated due to the user’s request.

SERVER-X-1536: Device name deactivated due to media dismount.

Source: SERVER.EXE
Explanation: This informational message indicates that the specified drive was deactivated.

SERVER-X-1537: Device name deactivated due to media eject.

Source: SERVER.EXE
Explanation: This informational message indicates that the specified drive was deactivated.

SERVER-X-1538: Device name deactivated due to server down.

Source: SERVER.EXE
Explanation: This informational message indicates that the specified drive was deactivated because the server was shut down or went down.

SERVER-X-1539: Device name deactivated due to server failure.

Source: SERVER.EXE
Explanation: This informational message indicates that the specified drive was deactivated because of a server failure.

SERVER-X-1540: Device name deactivated due to hotfix failure.

Source: SERVER.EXE
Explanation: The indicated drive was deactivated because of a Hot Fix error.

SERVER-X-1542: Module name is a NIOS only NLM.

Source: SERVER.EXE
Explanation: This NLM cannot be run on a server; it must be run on a client.
Action: Run the NLM on a client workstation; or choose a different NLM to load on the server.

SERVER-X-1543: Could not redirect block number on device number.

Source: SERVER.EXE
Possible Cause: A potential device failure and data loss has been caused by one of the following:

  • An I/O error occurred that could not be corrected by Hot Fix. No redirection blocks are left, or the hard disk is no longer operational.

  • Due to insufficient space, the system was unable to redirect data during a Hot Fix operation.

Action: Use the messages that follow this message to determine why Hot Fix has failed. See Disk Errors in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

SERVER-X-1544: Warning: There are no more redirection blocks on device name.

Source: SERVER.EXE
Explanation: The partition has used all its redirection blocks. Future I/O errors cannot be redirected to Hot Fix.
Action: The disk is in danger of failing. Troubleshoot or replace the disk.

SERVER-X-1545: Insufficient memory to load NLM.

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

SERVER-X-1546: Invalid record in load file.

Source: SERVER.EXE
Possible Cause: The operating system tried to load an NLM that had invalid code or data segments.
Action: Relink the NLM. If the problem persists, contact a Novell support provider or the vendor of the NLM.

SERVER-X-1547: Error reading load file.

Source: SERVER.EXE
Severity: Warning
Explanation: The operating system tried to load an NLM, but the process failed.
Possible Cause: Internal errors relating to the NLM occurred. The NLM is corrupted.
Action: Load a new copy of the NLM from the master diskette.
Possible Cause: Physical disk errors in the loading process occurred. The disk system is faulty.
Action: If the NLM is not at fault, check the disk system (cables, disk drive, and controller) for potential problems. If the server is still unable to load the NLM, call the vendor of the NLM for any fixes or updates.

SERVER-X-918: Load file referenced undefined public variable.

Source: SERVER.EXE
Explanation: The loader could not find the module’s public symbol name in the Public Symbol table.
Action: Complete one of the following:

  • If you are a user, see the documentation for the NLM. Another module must be loaded before this module.

  • If you are a developer, verify the spelling of the symbol. Make sure the module that defined this symbol made it public. Implement auto-loading so that the module that defines the public symbol is automatically loaded before other modules that need access to this symbol.

SERVER-X-1549: Load file contains invalid public variable name.

Source: SERVER.EXE
Possible Cause: The public variable name in the NLM file header had a zero-character length. The name field can store up to 256 characters. This message indicates a corrupted NLM.
Action: Reload the NLM from the master diskette. If this does not correct the problem, contact the vendor of the NLM.

SERVER-X-1550: Load file defines a public variable that has already been defined.

Source: SERVER.EXE
Explanation: While the system was loading an NLM, it found that one or more of the module’s public variables had been defined previously. An NLM cannot use a previously defined public variable, because system integrity could be compromised. This error is not fatal. The NLM will continue to load until all previously defined symbols have been listed to screen. The NLM will then be unloaded and all resources will be returned to the operating system.
Action: Contact the vendor of the NLM about updates or patches.

SERVER-X-1552: Warning: There are only number redirection blocks left on device name.

Source: SERVER.EXE
Explanation: The partition is running out of redirection blocks. If the Hot Fix redirection area is not increased, the disk will not be able to use Hot Fix to correct future I/O errors.
Action: The disk is probably failing. Troubleshoot or replace the disk.

SERVER-X-1553: Module initialization failed.

Source: SERVER.EXE
Explanation: The module could not be initialized. The server will probably receive a message from the module that explains why the initialization failed.
Action: Refer to the module’s message.

SERVER-X-1554: Invalid public record offset in load file.

Source: SERVER.EXE
Explanation: This error indicates a corrupted NLM or a faulty disk system.
Action: Reload the NLM from the master CD-ROM or diskette, and check the disk system for potential problems.

SERVER-X-1555: Address space name is not an unloadable address space.

Source: SERVER.EXE
Explanation: You attempted to unload an address space that was autoloaded by an NLM, such as JAVA, and is required for the NLM to function. Such address spaces cannot be unloaded manually.
Action: Unload the NLM; this will automatically unload the associated address space.

SERVER-X-1574: Needed support modules are not present.

Source: SERVER.EXE
Explanation: The NLM could not be loaded because it depends on other NLM programs that have not been loaded.
Possible Cause: The server is trying to load an NLM before loading a number of support modules that must be loaded previously. The load attempt aborted because these modules were required for the current NLM to operate properly.
Action: Additional messages may appear on the console screen or in the boot$log.err file (in Sys:system) stating what support modules are required. If you do not have the required modules, contact the NLM vendor.

SERVER-X-1587: Error number: getting information for name volume.

Source: SERVER.EXE
Possible Cause: The volume on which the swap file resides might have failed.
Action: Check status of volume and repair as necessary.

SERVER-X-1600: Address space name is not an unloadable address space.

Source: SERVER.EXE
Explanation: See SERVER-X-1555: Address space name is not an unloadable address space..

SERVER-X-1601: Invalid Address Space State (number).

Source: SERVER.EXE
Explanation: You tried to load a module into an address space that had been shut down because it faulted or experienced a cleanup failure. Although the address space was shut down, it was not deleted.
Action: Load the module into a different address space.

SERVER-X-1614: Remirroring process aborted on mirror object number.

Source: SERVER.EXE
Possible Cause: The system found the remirroring process to be out of synchronization due to hardware failure. The designated partition cannot be mirrored. Data integrity might be lost for the volumes that reside on the designated partition. The operating system supports the partition as an unmirrored device. This error might have been caused by a hard disk or channel failure. Another possibility is that the directory was corrupted.
Action: Try to salvage the data on the mirrored disks. Replace failing disks.

SERVER-X-1616: An NLM has been loaded that does not allow low priority threads to be run. Low priority threads are used for file compression, etc. Set `Upgrade Low Priority Threads’ to ON or unload the NLM.

Source: SERVER.EXE
Possible Cause: An NLM has been loaded that does not yield the CPU properly. Some processes, such as file compression, cannot be completed.
Action: Use the SET server utility to set the Upgrade Low Priority Threads parameter to On, or unload the NLM.

If this NLM is from a vendor other than Novell, try loading the NLM using the following command line syntax:


LOAD    NLM (CLIB_OPT)/Y

This syntax causes the NLM to use a different method of yielding CPU calls (using a handicapped queue) that allows priority threads to run.

SERVER-X-1631: Error number: getting information for name volume.

Explanation: See SERVER-X-1587: Error number: getting information for name volume..

SERVER-X-1633: Error number: deleting swap file on volume name.

Source: SERVER.EXE
Explanation: When you delete a swap file, any data in the file must be moved to another swap file. In this case, the data could not be moved.
Possible Cause: There might not be another swap file to move the data to, or other swap files might be full.
Action: Make sure another valid swap file exists with enough room to hold the data from the file you want to delete.

SERVER-X-1635: Error number: reading swap file on volume name page number number error number.

Source: SERVER.EXE
Explanation: There might be a disk problem or a volume containing a swap file might have been dismounted when there was no other swap file to hold the data. Applications that use virtual memory, such as Java applications, might start to fail; if so they will be unloaded.
Action: Reload any virtual-memory applications that have been unloaded. To prevent the problem from happening again, do not dismount a volume containing a swap file unless there is a swap file on another volume to store the data.

SERVER-X-1657: SizeOfObject received an invalid object pointer number.

Source: SERVER.EXE
Explanation: Memory might be corrupted.
Action: Replace memory or contact your support provider.

SERVER-X-1658: SizeOfObject detected corrupt preceeding redzone for object number.

Source: SERVER.EXE
Explanation: Memory might be corrupted.
Action: Replace memory or contact your support provider.

SERVER-X-1666: Expected slot number missing or invalid.

Source: SERVER.EXE
Explanation: You did not specify a slot number when loading a driver.
Possible Cause: The card for which you are loading the drive requires a slot number.
Action: Reload the driver, specifying the slot number for the card.

SERVER-X-1682: I/O port number is NOT supported and was ignored.

Source: SERVER.EXE
Explanation: When loading a driver, you specified a port that was not supported and therefore was not used. Instead, the system used a different port number that appeared to be valid.
Possible Cause: The port you specified is probably invalid.
Action: If the driver loaded successfully, no further action is needed. If the driver didn’t load successfully, determine a correct port number and try reloading the driver with the valid number.

SERVER-X-1683: Memory address is NOT supported and was ignored.

Source: SERVER.EXE
Explanation: A bad parameter was passed to a driver.
Action: Refer to the driver documentation to learn what parameters are required.

SERVER-X-1684: Memory length number is NOT supported and was ignored.

Source: SERVER.EXE
Explanation: A bad parameter was passed to a driver.
Action: Refer to the driver documentation to learn what parameters are required.

SERVER-X-1691: Memory range number to number is ALREADY in use.

Source: SERVER.EXE
Explanation: Another driver has already registered this memory address.
Action: Choose a different memory address or try loading the driver without specifying a memory address, so NetWare can choose the address.

SERVER-X-1692: Memory address is ALREADY in use.

Source: SERVER.EXE
Explanation: Another driver has already registered this memory address.
Action: Choose a different memory address or try loading the driver without specifying a memory address, so NetWare can choose the address.

SERVER-X-1693: Memory range number to number is ALREADY in use.

Source: SERVER.EXE
Explanation: See SERVER-X-1691: Memory range number to number is ALREADY in use..

SERVER-X-1694: Memory address is ALREADY in use.

Source: SERVER.EXE
Explanation: See SERVER-X-1692: Memory address is ALREADY in use..

SERVER-X-1712: SizeOfObject detected object number is not currently in use.

Source: SERVER.EXE
Explanation: There is an internal programming error in the NLM.
Action: Contact the NLM vendor.

SERVER-X-1713: SizeOfObject detected corrupt trailing redzone for object number, object size size.

Source: SERVER.EXE
Explanation: Memory might be corrupted.
Action: Replace memory or contact your support provider.

SERVER-X-1849: ERROR resetting parameter to its default value.

Source: SERVER.EXE
Explanation: When you executed the RESET ENVIRONMENT command, a parameter could not be reset to its default value, probably because it must be set in the startup.ncf file.
Action: Set the parameter in the startup.ncf file.

SERVER-X-1886: Unable to load SYSCALLS.NLM for memory protected execution.

Source: SERVER.EXE
Explanation: The SYSCALLS module could not be loaded. The console probably displays a message providing more information.
Possible Cause: The module might be missing or there might be problems initializing the module.
Action: Refer to the console messages for more information.

SERVER-X-1899: Unable to unload module name (error number).

Explanation: See SERVER-X-1143: Unable to unload module name (error number)..

SERVER-X-1930: Rejected an incomplete NCP packet from Station number (NCP number number).

Source: SERVER.EXE
Possible Cause: An NCP packet received from a client program had an invalid length, which invalidated the packet. The client program might be an outdated version or it might be corrupted.
Action: Replace the offending client program with updated or uncorrupted software.

SERVER-X-1934: Processed an incomplete NCP from Station number (NCP number number).

Source: SERVER.EXE
Explanation: This informational message indicates that the NCP engine processed an NCP packet even though the packet contained one or more fields with an invalid length.

SERVER-X-1935: Rejected an NCP with a bad subfunction length, Station number (NCP number number).

Source: SERVER.EXE
Explanation: An NCP packet received from a client program had an invalid sub-function length, so the sub-function lengths did not add up to a valid IPX length.
Possible Cause: The client program might be an outdated version or it might be corrupted.
Action: Replace the offending client program with updated or uncorrupted software.

SERVER-X-1936: Processed an NCP with a bad subfunction length, Station number (NCP number number).

Source: SERVER.EXE
Explanation: An NCP packet received from a client program had an invalid subfunction length, so the sub-function lengths did not add up to a valid IPX length.
Possible Cause: The client program might be an outdated version or it might be corrupted.
Action: Replace the offending client program with updated or uncorrupted software.

SERVER-X-1948: Unable to find load file filename.

Source: SERVER.EXE
Possible Cause: The specified load file could not be found using the specified path in the command or the search path. Files with the extensions .nlm, .nam, .lan, and .dsk will be checked if no extension was specified. If an extension was specified, only files with that extension will be checked.
Action: Make sure the file exists in the directory. Check the spelling and extension of the file.

SERVER-X-1949: Error reading from load file.

Source: SERVER.EXE
Explanation: See message SERVER-X-1132: Error reading from load file..

SERVER-X-1952: Error reading from load file.

Source: SERVER.EXE
Explanation: See message SERVER-X-1132: Error reading from load file..

SERVER-X-1954: Invalid load file format.

Source: SERVER.EXE
Explanation: See message SERVER-X-1134: Invalid load file format..

SERVER-X-1955: Invalid load file version.

Source: SERVER.EXE
Explanation: See message SERVER-X-1136: Invalid load file version..

SERVER-X-2004: Unable to locate MM.NLM (Media Manager) in the startup area.

Source: SERVER.EXE
Explanation: The Media Manager is not in the server startup (boot) directory.
Action: If the Media Manager has been moved to another location, move it back to the startup directory. Otherwise, copy the Media Manager NLM from the original NetWare CD-ROM.

SERVER-X-2052: Set_parameter action FAILED

Source: SERVER.EXE
Explanation: The parameter could not be set to the specified value. The value might be out of range.
Action: Check the range of values for the parameter. See SET in the NW 6.5 SP8: Utilities Reference.

SERVER-X-2189: Name failed to initialize.

Source: SERVER.EXE
Explanation: An NLM failed to load successfully and returned an error.
Action: Refer to the server console to see if the NLM displayed its own error message. Contact the NLM vendor.

SERVER-X-2190: Insufficient memory to create new address space.

Source: SERVER.EXE
Possible Cause: The server is low on memory.
Action: Add more memory or unload unnecessary NLM programs.

SERVER-X-2191: FreeMovableCacheMemory found an invalid memory list.

Source: SERVER.EXE
Explanation: Memory might be corrupted.
Action: Replace memory or contact your support provider.

SERVER-X-2196: Error: No swap file on volume name.

Source: SERVER.EXE
Explanation: You tried to delete a swap file that does not exist.

SERVER-X-2206: FreeMovableCacheMemory found an invalid memory list.

Source: SERVER.EXE
Explanation: Memory might be corrupted.
Action: Replace memory or contact your support provider.

SERVER-X-2207: Insufficient memory to set up first load search path entry.

Source: SERVER.EXE
Explanation: See message SERVER-X-872: Insufficient memory to set up first load search path entry..

SERVER-X-2212: Unable to create address space with default name.

Source: SERVER.EXE
Explanation: The server could not create the address space.
Possible Cause: There may not be enough memory to create the space.
Action: Determine how much memory is available. If memory is low, unload unnecessary modules or add more memory.

SERVER-X-2214: Unable to create address space name.

Source: SERVER.EXE
Explanation: The server could not create the address space.
Possible Cause: There might not be enough memory to create the space or the address space name might be invalid.
Action: Check the address space name to see if it is too long or uses invalid characters. If the name is valid, determine whether the server is low on memory. If memory is low, unload unnecessary modules or add more memory.

SERVER-X-2213, 2241, 2301: Unable to load USERLIB.NLM for memory protected execution.

Source: SERVER.EXE
Explanation: The USERLIB module could not be loaded. The console probably displays a message providing more information.
Possible Cause: The module might be missing or there might be problems initializing the module.
Action: Refer to the console messages for more information.

SERVER-X-2302, 2303: FreeMovableCacheMemory found an invalid memory list.

Source: SERVER.EXE
Explanation: Memory might be corrupted.
Action: Replace memory or contact your support provider.

SERVER-X-2323: Cache memory allocator exceeded minimum cache buffer limit.

Source: SERVER.EXE
Explanation: The SET server utility’s Minimum File Cache Buffers and Minimum Directory Cache Buffers parameters limit the minimum number of cache buffers for the system.
Possible Cause: This error occurs when other areas of the server try to allocate more memory and only the minimum number of cache buffers is left. System performance might be degraded. The subsystem that requested additional memory will not be able to perform the requested action because the required memory was not available.
Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

SERVER-X-2324: Cache memory allocator out of available memory.

Source: SERVER.EXE
Explanation: All cache memory has been used. System performance is severely degraded.
Possible Cause: This error occurs when the NetWare operating system tries to allocate a cache buffer and the remaining number of buffers is less than the System Cache Limit. The default value is 20 buffers.
Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

SERVER-X-2325: Number of cache buffers is getting too low.

Source: SERVER.EXE
Explanation: The number of cache buffers has dropped below a preset value. However, the requested cache buffer was allocated successfully.
Possible Cause: The server is running out of memory.
Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

SERVER-X-2327: The MM.NLM (Media manager) Failed to Initialize. Press any key to retry loading operation.

Source: SERVER.EXE
Explanation: For some reason the Media Manager could not be started. The server console might display additional messages explaining the source of the problem.
Action: Refer to the server console.

SERVER-X-2347: Unable to allocate memory for displaying commands.

Source: SERVER.EXE
Possible Cause: The server is very low on memory.
Action: See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

SERVER-X-2348: Unable to allocate memory for displaying commands.

Source: SERVER.EXE
Action: See message SERVER-X-2347: Unable to allocate memory for displaying commands..

SERVER-X-2388: Insufficient memory to load module.

Source: SERVER.EXE
Possible Cause: An attempt to load an NLM failed because the server does not have enough memory currently available to load it.
Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

SERVER-X-2491: Unable to clear supervisor account lockout.

Source: SERVER.EXE
Explanation: An ENABLE LOGIN command was issued, but the system was unable to clear the locked-out Supervisor account.
Possible Cause: An error occurred when accessing the bindery files or writing to the disks.
Action: Try the command again. If it fails, bring down the server and then bring it back up. Try the command again.
Possible Cause: The bindery is corrupted.
Action: If the Supervisor’s account is still locked, you might have to run BINDFIX to locate errors and inconsistencies that might be causing problems in the bindery.

SERVER-X-2509: The server name has NOT been set.

Source: SERVER.EXE
Explanation: No file server name was specified for the SET FILE SERVER NAME command.
Action: Re-execute the command and include a valid file server name.

SERVER-X-2513: Protect command has an invalid file name.

Source: SERVER.EXE
Explanation: When you executed the PROTECT command you specified an incorrect file name as a parameter.
Action: Specify the correct file name as a parameter to the PROTECT command. The file must be a .ncf file.

SERVER-X-2527: Invalid station number number.

Source: SERVER.EXE
Possible Cause: The CLEAR STATION command was executed with an invalid station number as a parameter. The station number was out of range.
Action: Check MONITOR for a list of active station numbers and retry the command.

SERVER-X-2529: NLM connections CANNOT be cleared..

Source: SERVER.EXE
Explanation: A resource could not be released for some reason.
Action: Keep trying or try to unload the NLM that’s using the resource.

SERVER-X-2553: Illegal character character in file server name.

Source: SERVER.EXE
Possible Cause: When naming a file server, you included one or more unsupported characters in the server name.
Action: Choose a new name that does not contain illegal characters. Valid characters are: A - Z, 0 - 9, -, _ .

SERVER-X-2586: Missing message to BROADCAST. Broadcast was NOT sent.

Source: SERVER.EXE
Explanation: The BROADCAST command was not executed.
Possible Cause: No message was specified for the BROADCAST command.
Action: Re-execute the command and include a message.

SERVER-X-2587: Broadcast was NOT sent.

Source: SERVER.EXE
Explanation: The BROADCAST message was not sent, possibly because an invalid connection number was specified.
Action: Re-execute the command and specify a valid connection number.

SERVER-X-2588: Invalid station number number.

Source: SERVER.EXE
Possible Cause: The BROADCAST command was executed with an invalid station number as a parameter. The station number was out of range.
Action: Check MONITOR for a list of active station numbers and retry the command.

SERVER-X-2593: Broadcast was NOT sent to any stations.

Source: SERVER.EXE
Explanation: The message could not be sent to any of the designated stations.
Possible Cause: The stations may not have been logged in.
Action: Resend the message when the stations are logged in.

SERVER-X-2598: Unable to allocate memory for hot plug driver.

Source: SERVER.EXE
Explanation: There was not enough memory to load a hot replace disk driver.
Possible Cause: The server is very low on memory.
Action: Remove unnecessary modules or add more memory.

SERVER-X-2600: Unable to read load file header.

Source: SERVER.EXE
Explanation: The server tried to read the NLM header but received an error. The NLM was not loaded.
Possible Cause: The NLM may be corrupted.
Action: Replace the NLM with an uncorrupted version, if possible. Contact the NLM vendor.

SERVER-X-2601: Unable to read version information.

Source: SERVER.EXE
Explanation: The server tried to read the version of the NLM being loaded and could not. The NLM was not loaded.
Possible Cause: The NLM may be corrupted.
Action: Replace the NLM with an uncorrupted version, if possible. Contact the NLM vendor.

SERVER-X-2625: Memory length must be on a paragraph boundary (i.e. number or number).

Source: SERVER.EXE
Explanation: The REGISTER MEMORY command could not be executed because it was given an invalid memory length as a parameter.
Possible Cause: The hexadecimal memory values specified as parameters to the REGISTER MEMORY command were invalid.
Action: For instructions on calculating the correct memory values for the command, see Register Memory in the NW 6.5 SP8: Utilities Reference.

SERVER-X-2628: There is no memory present at the specified address..

Source: SERVER.EXE
Explanation: Invalid parameters were passed to the REGISTER MEMORY command.
Action: Re-execute the command with valid memory addresses. See Register Memory in the NW 6.5 SP8: Utilities Reference to learn how specify the hexadecimal memory addresses required by the command.

SERVER-X-2713: Module did not release 1 resource.

Module: module

Resource: resource

Description: description

Source: SERVER.EXE
Possible Cause: An NLM failed to release an allocated resource when it was unloaded. In many cases, the NLM reclaims the resource. Unreleased resources are not available for system use if the operating system cannot recover them. This can cause memory allocation errors.
Action: Contact the vendor of the NLM to determine whether the NLM should have released the resource. The vendor might have a newer NLM that corrects the problem.

SERVER-X-2715: Module did not release number resources

Module: module

Resource: resource

Description: description

Source: SERVER.EXE
Possible Cause: An NLM failed to release allocated resources when it was unloaded. In many cases, it reclaims the resource. Unreleased resources are not available for system use if the operating system cannot recover them. This can cause memory allocation errors.
Action: Contact the vendor of the NLM to determine whether the NLM should have released the resources. The vendor might have a newer NLM that corrects the problem.

SERVER-X-2973: Warning: extra input ignored (value).

Source: SERVER.EXE
Explanation: Extra input was included when the SET command was executed.
Action: Make sure the SET parameter was executed with the correct values. Re-execute the SET command if necessary.

SERVER-X-2994: Unable to allocate memory for new language name.

Source: SERVER.EXE
Possible Cause: The operating system was unable to allocate memory for a new language name because it is out of memory.
Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

SERVER-X-2995: Unable to allocate memory for new language.

Source: SERVER.EXE
Possible Cause: The operating system was unable to allocate memory for a new language because it is out of memory.
Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

SERVER-X-3044: Unable to find load file filename.

Explanation: See message SERVER-X-1948: Unable to find load file filename..

SERVER-X-3085: Invalid offset from Universal Time Coordinate.

Source: SERVER.EXE
Possible Cause: You did not enter an offset from the Universal Time Coordinate or you specified an offset that is not valid (for example, it might be too big or too small).
Action: Specify a valid offset from the Universal Time Coordinate.

SERVER-X-3332: Removed address space because of memory protection violation.

Address space: name

Reason: reason

Running Thread: thread

EIP: instruction pointer

Source: SERVER.EXE
Explanation: An NLM faulted ina protected address space. The address space was deleted and its resources returned to the system.
Action: A core dump of the protected address space has been written to Sys. Review the core dump to help determine the source of the abend in the protected space.

SERVER-X-3372: Attempt to reinitialize re-entrant module FAILED.

Source: SERVER.EXE
Explanation: For some reason, a module could not be loaded re-entrantly. There might be an internal problem in the NLM.
Action: Contact the NLM vendor.

SERVER-X-3389: Name: SYS$LOG.ERR was deleted, file size = number, threshold = number.

Source: SERVER.EXE
Explanation: The sys$log.err file should be deleted when it reaches its maximum size. The sys$log.err file reached its maximum size and was deleted.
Action: No action is necessary.

SERVER-X-3430: Unable to unload module name (error number).

Explanation: See message SERVER-X-1143: Unable to unload module name (error number)..

SERVER-X-3480: Unable to open file name; NLM not loaded.

Source: SERVER.EXE
Explanation: The NLM could not be opened or could not be found.
Possible Cause: The file might not have been loaded, might have been deleted, or you might be specifying the wrong file or path name.
Action: Make sure the NLM is loaded and that you have specified the path and file name correctly; then try again. If a NetWare module is missing, you can copy the file from the NetWare CD-ROM. Load NWCONFIG, select Copy Files Options, and enter the path to the NetWare CD-ROM; followthe prompts. For assistance, refer to the help messages on the screen or press F1 for additional help.

SERVER-X-3481: Unable to open file filename. Directory support NLM not loaded.

Source: SERVER.EXE
Explanation: The operating system NLM cannot be loaded.
Possible Cause: The SERVER.EXE file is corrupted or an outdated version.
Action: Make sure the NLM is the most current version. If you suspect corruption, reinstall the NLM using a fresh copy from the original media CD-ROM or diskette.

SERVER-X-3488: File filename has an invalid NLM type; NLM not loaded.

Source: SERVER.EXE
Possible Cause: The file has an .NLM as an extension, but it is not a valid NLM.
Action: Verify the NLM against the original CD-ROM or diskette.

SERVER-X-3490: Unable to read file filename; NLM not loaded.

Source: SERVER.EXE
Possible Cause: The NLM is corrupted.
Action: Make sure the NLM is the most current version. If you suspect corruption, reinstall the NLM using a fresh copy from the original media CD-ROM or diskette.
Possible Cause: The server is out of system resources.
Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

SERVER-X-3513: INVALID FORMAT.

Source: SERVER.EXE
Explanation: See message SERVER-X-721: INVALID FORMAT..

SERVER-X-3549: Unable to open the license file (name). string.

Source: SERVER.EXE
Explanation: When an attempt was made to get the license document found in the file indicated, the license file could not be opened for some reason.
Action: Try reinstalling the license file using NWCONFIG. If the problem persists, contact a Novell support provider.

SERVER-X-3552: Unable to remove the invalid Main Server License file (name). string.

Source: SERVER.EXE
Explanation: The Main Server License was found to be invalid for some reason. In order for a valid license to be installed, the invalid one must be removed. It cannot be deleted at this point in the validation process.
Action: Contact a Novell support provider.

SERVER-X-3553: Unable to remove the invalid Upgrade License file (name). string.

Source: SERVER.EXE
Explanation: The Main Server License was found to be invalid for some reason. In order for a valid license to be installed, the invalid one must be removed. It cannot be deleted at this point in the validation process.
Action: Contact a Novell support provider.

SERVER-X-3554: Unable to remove the invalid companion Reseller License file (name). string.

Source: SERVER.EXE
Explanation: The Main Server License was found to be invalid for some reason. In order for a valid license to be installed, the invalid one must be removed. It cannot be deleted at this point in the validation process.
Action: Contact a Novell support provider.

SERVER-X-3555: Unable to get a File Size for the license file (name). string.

Source: SERVER.EXE
Explanation: The license file size cannot be obtained. The validation process has failed and the license will not be loaded. No connections can be granted by the server.
Action: Contact a Novell support provider.

SERVER-X-3557: Unable to read in the license document from the file (name). string.

Source: SERVER.EXE
Explanation: The server was unable to read the file indicated. The validation process has failed for that license file, and it should have been removed.
Action: Try reinstalling the license using NWCONFIG. If the problem persists, contact a Novell support provider.

SERVER-X-3559: A duplicate server license ID has been discovered by this server. Please correct the problem by reinstalling the correct license either on this server or the server at the network address indicated on the console screen. string

Source: SERVER.EXE
Explanation: The license file is invalid for some reason and has been removed by the server.
Action: Reinstall the license using NWCONFIG. If the problem persists, contact a Novell support provider.

SERVER-X-3645: ERROR MPKStubs not inserted for OldInternalPublics due to Alloc Error.

Source: SERVER.EXE
Explanation: The server is low on memory.
Action: Increase server memory or unload unneeded modules.

SERVER-X-3647: ERROR MPKStubs not inserted for Internalpublics due to Alloc Error.

Source: SERVER.EXE
Explanation: The server is low on memory.
Action: Increase server memory or unload unneeded modules.

SERVER-X-3806: Name: failed trying to rename SYS$LOG.ERR, file was deleted instead.

Source: SERVER.EXE
Explanation: When the sys$log.err file reached it’s maximum size, it should have been renamed. The file was deleted instead, and a new sys$log.err file was created.
Possible Cause: Something prevented renaming the file. For example, the file may have been open when the server tried to rename it.
Action: No action is necessary.

SERVER-X-3912: Invalid load file format.

Source: SERVER.EXE
Explanation: See message SERVER-X-1134: Invalid load file format..

SERVER-X-3916: Error reading load file.

Source: SERVER.EXE
Severity: Warning
Explanation: See message SERVER-X-1547: Error reading load file..

SERVER-X-4095: Unable to load the message/help support files.

Source: SERVER.EXE
Explanation: This informational message indicates that an error occurred when the operating system tried to load the message and help files for an NLM it was loading.

SERVER-X-4097: Unable to load module messages in preferred language # number; the default language #number will be used.

Source: SERVER.EXE
Possible Cause: While loading an NLM, the operating system was not able to find the message files for the preferred language. Instead, the operating system is using the default language message files. Enter LANGUAGE LIST at the server console prompt to see a list of languages and their numbers.
Action: If the error persists, change the preferred language.

SERVER-X-4098: Unable to load module messages in preferred language # number; the default language #number will be used.

Source: SERVER.EXE
Possible Cause: While loading an NLM program, the operating system was not able to find the message files for the preferred language. Instead, the operating system is using the default language message files. Enter LANGUAGE LIST at the server console prompt to see a list of languages and their numbers.
Action: If the error persists, change the preferred language.

SERVER-X-4099: Unable to load module help in preferred language #number; the default language #number will be used.

Source: SERVER.EXE
Possible Cause: While loading an NLM, the operating system was not able to find the help files for the preferred language. Instead, the operating system is using the default language help files. Enter LANGUAGE LIST at the server console prompt to see a list of languages and their numbers.
Action: If this error persists, change the preferred language.

SERVER-X-4100: Unable to load module help in preferred language #number; the default language #number will be used.

Source: SERVER.EXE
Possible Cause: While loading an NLM, the operating system was not able to find the help files for the preferred language. Instead, the operating system is using the default language help files. Enter LANGUAGE LIST at the server console prompt to see a list of languages and their numbers.
Action: If this error persists, change the preferred language.

SERVER-X-4101: Error reading help file.

Source: SERVER.EXE
Explanation: This error might indicate file system or data corruption.
Action: Run VREPAIR and restart the system.

Warning: If you delete the volume, all data will be destroyed. You will have to restore the data from a backup.

If the problem persists, make sure a volume backup exists. Delete the volume, re-create it using NWCONFIG, and restore the data from the backup.

SERVER-X-4102: Error allocating memory for help file.

Source: SERVER.EXE
Possible Cause: The server probably does not have enough memory to load the help file.
Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

If memory is not the problem, try running VREPAIR; then restart the system.

Warning: If you delete the volume, all data will be destroyed. You will have to restore the data from a backup.

If the problem persists, make sure a volume backup exists. Delete the volume, re-create it using NWCONFIG, and restore the data from the backup.

SERVER-X-4103: Invalid help file.

Source: SERVER.EXE
Explanation: The help file for an NLM on the console was invalid.
Possible Cause: The server might be using an outdated version of the file.
Action: Determine why the file is invalid and replace it with a valid file.

SERVER-X-4104: Error removing the swap file from volume name. This volume is needed by the Virtual Memory system. Unload everything using virtual memory before dismounting this volume.

Source: SERVER.EXE
Explanation: You tried to dismount a volume that contained a swap file; there was no other swap file to move the data to.
Action: Create a swap file on another volume before deleting this volume; or unload all protected address spaces and all modules that use virtual memory, then dismount the volume.

SERVER-X-4105: Error removing the swap file from volume name. This volume is needed by the Virtual Memory system. Unload everything using virtual memory before dismounting this volume.

Explanation: See message SERVER-X-4104: Error removing the swap file from volume name. This volume is needed by the Virtual Memory system. Unload everything using virtual memory before dismounting this volume..

SERVER-X-4106: Swap-out failed (error_code; hexadecimal_error_code; error_code) This may have been caused by dismounting a volume being used for virtual memory swapping even though there was insufficient memory to hold all of the swap data.

Source: SERVER.EXE
Explanation: This message appears if a volume containing a swap file was dismounted, even though there was no other swap file to store the data and not enough memory to store the data. Applications that use virutal memory, such as Java applications, might start to fail. If so, the applications will be unloaded and the rest of the system should continue to function normally.
Action: Reload any applications that have been unloaded. To prevent the problem from happening again, do not dismount a volume containing a swap file unless there is a swap file on another volume to hold the data.

SERVER-X-4554: Failed to remove name address space.

Source: SERVER.EXE
Explanation: The memory management system could not free the memory assigned to the address after the address space either faulted or was unloaded. The memory resources are quarantined and unavailable for use.
Action: To release the memory resources, restart the server.

SERVER-X-4630: Unable to down File Server

Source: SERVER.EXE
Explanation: The file server cannot be downed after the console hung.
Possible Cause: Whatever module or process locked the console may be preventing the downing of the file server.
Action: Contact technical support.

SERVER-X-4652: Unable to load module help in preferred language; the default language will be used.

Explanation: See message SERVER-X-4099: Unable to load module help in preferred language #number; the default language #number will be used..

SERVER-X-4796: ERROR MPKStubs not inserted for Externalpublics due to NVMAlloc error number.

Source: SERVER.EXE
Explanation: The server is low on memory.
Action: Increase server memory or unload unneeded modules.

SERVER-X-4797: ERROR MPKStubs not inserted for Externalpublics due to Alloc Error.

Source: SERVER.EXE
Explanation: The server is low on memory.
Action: Increase server memory or unload unneeded modules.

SERVER-X-4834: Error: Could not shrink the swap file to meet the new maximum swap size parameter.

Source: SERVER.EXE
Possible Cause: To reduce the size of the file, data must be moved to another swap file. For some reason, the data could not be moved. Another swap file might not exist or the another swap file might not be large enough to accommodate the data.
Action: Make sure there is another swap file large enough to accommodate the data or change the maximum size of the current swap file to a larger value.

SERVER-X-4835: Error: Could not grow the swap file to meet the new minimum swap size parameter.

Source: SERVER.EXE
Possible Cause: You might have specified a minimum swap file size larger than the free space on the volume or larger than the volume itself.
Action: Remove files from the volume to increase free space or create a swap file on another volume that has more space, or reduce the minimum swap file size.

SERVER-X-4837: Error changing swap parameters for volume name.

Source: SERVER.EXE
Explanation: The swap parameters could not be changed, probably because the new values are not valid. For example, this message is displayed if you set the minimum value higher than the maximum value.
Action: Make sure the new parameter values are valid.

SERVER-X-4848: Error: Initializing swap file on volume name.

Source: SERVER.EXE
Possible Cause: The disk where the volume resides is probably running out of space.
Action: Removed unneeded files to free disk space or replace the disk with a larger one.

SERVER-X-4851: Error: Initializing swap file information on Sys: volume.

Source: SERVER.EXE
Possible Cause: The disk where the volume resides is probably running out of space.
Action: Removed unneeded files to free disk space or replace the disk with a larger one.

SERVER-X-5168: The preferred language message file for this NLM is out of sync with the NLM; the default language will be used.

Source: SERVER.EXE
Explanation: See message SERVER-X-1002: The preferred language message file for this NLM is out of sync with the NLM; the default language will be used..

SERVER-X-5169: Unable to load module messages in preferred language; the default language will be used.

Explanation: See message SERVER-X-4097: Unable to load module messages in preferred language # number; the default language #number will be used..

SERVER-X-5178: Unable to unload module name.

Source: SERVER.EXE
Explanation: See message SERVER-X-1073: Unable to unload module name..

SERVER-X-5595: WARNING: number lost interrupt(s) detected on interrupt number. Lost interrupt alerts occur when there are no interrupt request bits set in the corresponding interrupt controller hardware when the processor acknowledges the interrupt.

Source: SERVER.EXE
Possible Cause: A LAN card is probably failing.
Action: Note the interrupt number, then execute the CONFIG command at the server console prompt to see a list of installed LAN cards and their interrupts. The card using the specified interrupt is probably faulty. Replace the card.

SERVER-X-5596: WARNING: number spurious (unclaimed) interrupt(s) detected on interrupt number. Spurious interrupt alerts occur when an interrupt is not claimed by any of the registered handlers for that interrupt.

Source: SERVER.EXE
Possible Cause: A LAN card is probably failing.
Action: Note the interrupt number, then execute the CONFIG command at the server console prompt to see a list of installed LAN cards and their interrupts. The card using the specified interrupt is probably faulty. Replace the card.

SERVER-X-5653: ERROR occurred while modifying ALERT #number.

Source: SERVER.EXE
Explanation: You attempted to enable or disable the display of an alert, but an error occurred. The alert code may not have been written correctly to allow the enabling or disabling of the display.
Action: Contact the vendor of the module or code that displays the alert.

SERVER-X-5655: ALERT #number (name bit) was NOT enabled.

Source: SERVER.EXE
Explanation: You attempted to enable the display of an alert that cannot be displayed.

SERVER-X-5657: ALERT #number (name bit) was NOT disabled.

Source: SERVER.EXE
Explanation: You attempted to disable an alert that cannot be disabled.

SERVER-X-nnnn [nmID1001C]

WARNING! Server name experienced a critical error. The offending process was suspended or recovered. However, services hosted by this server may have been affected.

Source: SERVER.EXE
Explanation: The server console displays this alert if one or more server processes have been suspended. It is common to see this alert after the server abends and the auto abend recovery process has restarted the server. A number in angle brackets appears after the server console prompt to indicate how many times a thread or process has been restarted.
Action: To troubleshoot server abends, see Resolving Abends in the NW 6.5 SP8: Server Operating SystemAdministration Guide.