#EDIR DATA#
DOCTYPE='BOOK' PUBLICID='' SYSTEMID='/dtd/docbook.dtd'System MessagesSystem MessagesNovell, Inc.DisclaimerNovell, Inc. makes no representations or warranties with
respect to the contents or use of this manual, and specifically
disclaims any express or implied warranties of merchantability or
fitness for any particular purpose. Further, Novell, Inc. reserves the
right to revise this publication and to make changes to its content,
at any time, without obligation to notify any person or entity of such
revisions or changes.Further, Novell, Inc. makes no representations or warranties
with respect to any NetWare software, and specifically disclaims any
express or implied warranties of merchantability or fitness for any
particular purpose. Further, Novell, Inc. reserves the right to make
changes to any and all parts of NetWare software, at any time, without
any obligation to notify any person or entity of such changes.TrademarksThe following are registered trademarks of Novell, Inc.: DR DOS, Fastpath, LAN WorkPlace, LANalyzer, NetWare, NetWare Name Service, Novell Press, UnixWare, WordPerfect.UNIX is a registered trademark of Novell, Inc. in the United States and other countries, licensed exclusively through X/Open Company, Ltd.The following are trademarks of Novell, Inc.: Advanced NetWare, Enterprise Certified NetWare Engineer, ECNE, EXOS, FirstMail, Global MHS, HSM, Hardware Specific Module, Hot Fix, IPX, IPX/SPX, IPXWAN, Internetwork Packet Exchange, LSL, Link Support Layer, MLI, MLID, MSL, MSM, MacIPX, MacNCP, MacNDS, Media Support Module, Mirrored Server Link, Multiple Link Interface, Multiple Link Interface Driver, NCP, NDR, NDS, NE/2, NE/2-32, NE1000, NE1500T, NE2000, NE2100, NE3200, NE32HUB, NLM, NLSP, NMS, NSE Pro, NTR2000, NVT, NetSync, NetWare 3, NetWare 4, NetWare 4.01, NetWare 4.1, NetWare Application Notes, NetWare Care, NetWare Client, NetWare Core Protocol, NetWare DOS Requester, NetWare Directory Services, NetWare Express, NetWare IPX Router, NetWare Link Services Protocol, NetWare Link/Frame Relay, NetWare Link/PPP, NetWare Link/X.25, NetWare Loadable Module, NetWare Logotype (teeth logo), NetWare MHS, NetWare Management Agent, NetWare Management System, NetWare Message Handling Service, NetWare MultiProtocol Router, NetWare Navigator, NetWare Peripheral Architecture, NetWare Ready, NetWare Requester, NetWare Runtime, NetWare SFT, NetWare SFT III, NetWare Tools, NetWare UAM, NetWare/IP, Netware Notify, Network Support Encyclopedia Professional Volume, Novell Labs, Novell Research Reports, Novell Virtual Terminal, ODI, Open Data-Link Interface, Packet Burst, Personal NetWare, RX-Net, RXNet/2, Red Box, SFT, SFT III, SMS, SPX, Sequenced Packet Exchange, Storage Management Services, Streams, TSM, Topology Specific Module, Transaction Tracking System, TTS, VLM, Virtual Loadable Module, "Yes, It Runs With NetWare Logo", and the "Yes, NetWare Tested and Approved Logo".The following are registered service marks of Novell, Inc.: Novell Technology Institute, NetWire.The following are service marks of Novell, Inc.: Novell Registry, Certified NetWare Administrator, CNA, Certified NetWare Engineer, CNE, Certified NetWare Instructor, CNI, Novell Authorized Service Center, NASC, Novell Technical Support.The following are collective marks of Novell, Inc.: Novell Authorized Reseller, Technical Support Alliance, TSA.3Com, 3+Share, and TokenLink are registered trademarks of 3Com Corporation.4.3BSD is a trademark of the Regents of University of California, Berkeley.ARCnet is a registered trademark of Datapoint Corporation.AT is a registered trademark of International Business Machines Corporation.AT&T is a registered trademark of American Telephone & Telegraph.Adobe and PostScript are registered trademarks of Adobe Systems Incorporated.Apple, AppleShare, AppleTalk, EtherTalk, ImageWriter, LaserWriter, LocalTalk, Macintosh, and MultiFinder are registered trademarks, and Finder and Mac are trademarks, of Apple Computer, Inc.Btrieve is a registered trademark of Btrieve Technologies, Inc.Canon is a registered trademark of Canon, Inc.COMPAQ is a registered trademark of COMPAQ Computer Corporation.Cisco Systems is a trademark of Cisco Systems, Inc.Citizen is a registered trademark of Tokei Kabushiki Kaisha.Claris is a trademark and MacWrite is a registered trademark of Claris Corporation.CompuServe is a registered trademark of CompuServe, Inc.DEC, DECnet, and Digital are trademarks of Digital Equipment Corporation.DeskJet, DeskWriter, LaserJet, PaintJet, PaintWriter, and PCL are registered trademarks of Hewlett-Packard Company.Diablo is a registered trademark of Xerox Corporation.DynaText is a registered trademark of Electronic Book Technologies, Inc.Epson is a registered trademark of Seiko Epson Corporation.EtherPrint is a trademark of 3Com Corporation.TokenPrint is a registered trademark of Dayna Communications.EtherFlex is a registered trademark of Extended Systems International.GatorBox is a registered trademark of Cayman Systems.Hewlett Packard, HP, HP-GL, LaserJet, and PCL are registered trademarks of Hewlett-Packard Company.Hayes is a registered trademark of Hayes Microcomputer Products, Inc.IBM, OS/2, Micro Channel, ProPrinter, and PS/2 are registered trademarks and AFP, Presentation Manager, and SAA are trademarks of International Business Machines Corporation.Intel is a registered trademark and Pentium is a trademark of Intel Corporation.LaserBridge is a registered trademark of Sonic Systems.Lotus is a registered trademark of Lotus Development Corporation.MS-DOS and Microsoft are registered trademarks and LAN Manager is a trademark of Microsoft Corporation.MacPlot is a registered trademark of Microspot.NEC, Spinwriter, and Pinwriter are registered trademarks of NEC Corporation.NFS is a registered trademark of Sun Microsystems, Inc.Okidata and MicroLine are registered trademarks of Oki Electric Industry Co., Ltd.PageMaker is a registered trademark of Aldus Corporation.Panasonic is a registered trademark of Panasonic Office Automation.PowerPrint is a trademark of GDT Softworks, Inc.SQL Server is a trademark of Sybase, Inc.SprintTalk is a registered trademark of Digital Products.Ultra is a trademark of Hayes Microcomputer Products, Inc.Unicode is a registered trademark of Transoft Ltd.Word is a registered trademark of Microsoft Corporation.XT is a trademark of International Business Machines Corporation.Xerox is a registered trademark and XNS is a trademark of Xerox Corporation.cc:Mail is a trademark of cc:Mail, a Division of Lotus.All other trademarks, service marks, certification marks, and
collective marks --- registered or not --- are the property of their
respective owners.Copyright Notices© Copyright 1983-1994 Novell, Inc. All rights reserved. No
part of this publication may be reproduced, photocopied, stored on a
retrieval system, or transmitted without the express written consent
of the publisher.TYPE="VERT"Novell, Inc.122 East 1700 SouthProvo, UT 84606U.S.A.User Comment FormNovell encourages and welcomes your feedback and suggestions on ways we can improve our manuals. You can help us by sharing your comments and suggestions about how our manuals could be made more useful to you, and about any inaccuracies or information gaps they contain.Submit your comments by printing this User Comment form (click on the icon to display the form, then select "Print" from the "File" menu), filling it in, then faxing or mailing it to us.LABEL="0" FLOAT="0"User Comment FormFILEREF="ucomment.tif"PAGENUM=7 ID="BP1"How to Use this ManualSystem Messages includes error and informational messages generated by the NetWare® 4.1 networking software that need additional explanation to resolve an error condition. This manual does not include self-explanatory messages.This manual is not a comprehensive list of all error or informational messages generated by NetWare 4.1 networking software.Use this manual to get an explanation for a message and, if necessary, a course of action to correct the error condition when a NetWare message is displayed at a workstation screen or a NetWare server console.RENDERAS="SECT1"Arrangement of the ManualThis manual documents messages generated by approximately 200 NetWare 4.1 modules. The modules are arranged alphabetically. They are followed by three appendices:MARK=BULLETIDREF="FM61529""Error Codes" in Appendix A lists numerical error codes that are displayed with many of the messages.IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B list in alphabetical order the MHS error reason, an explanation for the MHS error, and an action to resolve the error.IDREF="FM74346""Workstation Error Messages" in Appendix C provides general troubleshooting suggestions for your workstation.PAGENUM=8 ID="BP2"RENDERAS="SECT1"Message SyntaxA unique identifying code precedes most error messages. Usually, this code consists of the following components:MARK=BULLETThe module name (for example, LOGIN or SERVER)The product version or platformThe message numberFor example, a typical message for LOGIN would appear as follows:FORMAT="LINESPECIFIC"MOREINFO="NONE"LOGIN-4.10-100: Access has been denied. Some variation occurs in the format of certain groups of messages. LAN drivers, for example, include a platform designation instead of a version number:FORMAT="LINESPECIFIC"MOREINFO="NONE"NE2000-DOS-001: The LSL is not loaded. Modules originating from sources related to OS/2 have yet another format: FORMAT="LINESPECIFIC"MOREINFO="NONE"REQ0205: The LAN support module could not be installed. Some messages do not have a unique identifying code, so they are listed alphabetically in the module that originated the message.The module version is not included in this document because it is updated each time a revision or a software patch is made to the module.RENDERAS="SECT1"Recommended Search MethodWhen you are searching for a specific message in this online document, one of the quickest methods is to follow these steps:PERFORMANCE="REQUIRED"Narrow the search to the System Messages book by double-clicking the "System Messages" icon in the DynaText* "Collection" window.PAGENUM=9 ID="BP3"PERFORMANCE="REQUIRED"Choose the search form:PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"From the menu bar, choose the "Book" option.PERFORMANCE="REQUIRED"From the "Book" menu, choose the "Search Forms..." option.The "Search History" dialog will appear.PERFORMANCE="REQUIRED"Click the down arrow to the right of the "Search Form:" box.A drop-down list box will appear.PERFORMANCE="REQUIRED"Select the "Messages by Module" option.PERFORMANCE="REQUIRED"Specify the text to be found:PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Type the message number or part of the message text string in the "In system message" box.PERFORMANCE="REQUIRED"Type the module name in the "From source module" box.PERFORMANCE="REQUIRED"To start the search, click the Find button.The text found will appear highlighted on the screen.RENDERAS="SECT1"Explanations and ActionsAn explanation and suggested actions usually follow each message in this manual. Some actions refer to related information in other manuals. RENDERAS="SECT1"Error CodesMany messages include an error code that is generated by the NetWare software. A comprehensive table of NetWare error codes is found in IDREF="FM61529""Error Codes" in Appendix A.RENDERAS="SECT1"Other Resources for HelpYou may also want to use the following resources to help resolve an error:PAGENUM=10 ID="BP4"MARK=BULLETContext-sensitive help. If you are using a NetWare menu utility or graphical utility, and you want more information about how to complete a task, press MOREINFO="NONE"<F1> for help.If you are unsure about how to use a command line utility, type the utility name with the /? option at the command line. For example, to get help on the RIGHTS utility, type the following command:FORMAT="LINESPECIFIC"MOREINFO="NONE"MOREINFO="NONE"RIGHTS /?  MOREINFO="NONE"<Enter> Hardware manuals. Many network problems occur because of malfunctioning hardware. If you can isolate a problem to a certain computer component or cable segment, check the manuals that came with the hardware involved.Novell® Network Management System (NMS). This product helps you manage the cabling system, computers, software, and other components of the network. Call your Novell Authorized ResellerTM representative for more information about using NMS on your network.NetWare Application Notes and Research Reports. These documents cover technical aspects of NetWare system design, implementation, and management. Novell Application Notes is a collection of technical articles published monthly.The Novell Research ReportsTM are published by Novell as the research becomes available.You may purchase subscriptions and back issues of these publications in the United States or Canada by calling the Novell Research Order Desk at 1-800-UPDATE1. In all other locations, call 1-801-429-5380.Third-party books and periodicals. A number of books on NetWare, including books published by Novell Press®, are available at most bookstores. In addition, numerous networking periodicals give advice on configuring, managing, and troubleshooting your network.PAGENUM=11 ID="BP5"NetWire® on CompuServe*. An inexpensive way to get up-to-date advice and patches is through NetWire on the CompuServe bulletin board. To open a CompuServe account, call one of the following numbers:MARK=BULLETFrom the United States or Canada, call 1-800-524-3388.From the United Kingdom, call 0800-289-378.From Germany, call 0130-37-32.From the rest of Europe, call 44-272-255-111.In all other locations, use the appropriate country code for the U.S. to call 1-614-457-0802.Ask for "Representative 200." This key phrase simply lets the membership representative know that you are a Novell customer.Network Support Encyclopedia Professional VolumeSM (NSE Pro). The NSE ProSM is an electronic information base that contains technical information needed to install, maintain, and troubleshoot a network. The NSE Pro is a comprehensive, single-source compilation of technical information that is updated regularly. The NSE Pro includes technical information documents such as Novell Labs TM hardware and software test bulletins, product documentation, and Novell AppNotes, and Novell Professional Developer Bullets. The NSE Pro also includes downloadable NetWare patches, fixes, and drivers.The NSE Pro is distributed in a CD-ROM format on a subscription basis. Updates are sent to subscribers throughout the year.In addition to the CD-ROM version of the NSE Pro, most of the same information and files are available from NetWire on CompuServe or from the Internet; however, the information is updated daily in these sources.For more information on the NSE Pro, contact a Novell Authorized Reseller.Troubleshooting hardware and software. Specialized hardware and software packages, such as Novell's LANalyzer®, are available to help you isolate network problems.PAGENUM=12 ID="BP6"NetWare training. Many Novell courses are available to help you learn more about NetWare. You can pursue a Certified NetWare EngineerSM, Enterprise Certified NetWare EngineerSM, Certified NetWare AdministratorSM, or Certified NetWare InstructorSM title by taking classes and passing tests. For more information, contact Novell Education at 1-800-223-EDUC in the United States or Canada. In all other locations, call 1-801-429-5508, or contact the nearest Novell Authorized Education Center, located world-wide.Customer service. Call your NetWare Authorized Reseller or Novell Authorized Service CenterSM (NASC) for technical assistance. Most Novell Authorized Resellers and NASCSM locations have Certified NetWare Engineers on staff to assist users with networking problems.PAGENUM=13 ID="BP7"PAGENUM=14 ID="BP8"2XUPGRDEThe In-Place upgrade error (2XUPGDE) messages use the following numbering structure:MARK=BULLETAll 1xx messages are critical and cause the upgrade to abort.All 2xx messages are noncritical.The second digit in each error message indicates the phase that generated the message. For example:x0x---NLM initializationx1x---Phase 1: System Analysisx2x---Phase 2: Disk Analysisx3x---Phase 3: Disk Modificationx4x---Phase 4: Binderyx5x---All phasesx6x---Phase 4: Bindery (overflow)x9x---Restart MessagesNote: All references to NetWare 2.1x imply NetWare 2.2 also.101: An invalid command line parameter was encountered. The In-Place Upgrade process is now being aborted.2XUPGRDEExplanation: An unrecognized command line parameter was entered.Action: For a list of valid command line parameters, type: MOREINFO="NONE"LOAD 2XUPGRDE /? <MOREINFO="NONE"Enter>Allowable syntax for specifying parameters includes three options: parameters can be preceded by a forward slash (/), a minus sign (-), or can be separated by spaces. Parameters are not case sensitive.Press the UP-arrow key to retrieve the previous command, then check for typographical errors and try again.PAGENUM=15 ID="BP9"102: The operating system is unable to get the required resource_ name resource tag. The In-Place Upgrade process is now being aborted.2XUPGRDEExplanation: All NLMs require resource tags to track and maintain system resources to be used. These resources are: process, screen, and memory. Without these resources, the NLM cannot initialize.Action: Add more memory to the server and restart the upgrade.103: The new screen for the In-Place Upgrade cannot be opened. The In-Place Upgrade process is now being aborted.2XUPGRDEExplanation: The resources needed to open a new screen for the upgrade process are not available.Action: Unload all unnecessary NLMs from memory so the required resources can be freed up.104: Unable to allocate memory for the stack. The In-Place Upgrade process is now being aborted.2XUPGRDEExplanation:  Allocating memory for the stack is the first instance where memory is requested for the NLM's use. Without this memory (12 KB), the NLM will not run.Action:  To review memory pools, load the NetWare 3.1x MONITOR.NLM file and select the "Resource Utilization" screen. More memory may needed for the server.105: An invalid password was entered from the command line. Passwords must be between 5 and 127 characters long. The In-Place Upgrade process is now being aborted.2XUPGRDEExplanation:  An invalid password was specified when using the "/PASSWORD=" command line option. Valid NetWare passwords must be between 5 characters and 127 characters long, and cannot contain any control characters. If no text is entered after the "=" character, no passwords will be assigned.Action:  Reload the In-Place Upgrade NLM. Specify a valid, fixed password using the "/PASSWORD=" option or when prompted during the bindery upgrade phase.111: No disks can be found to upgrade. Ensure that the correct disk drivers have been loaded. The In-Place Upgrade process is now being aborted.2XUPGRDEExplanation: The upgrade process cannot find any disks that need upgrading. This situation occurs when disk drivers are not loaded, or when all of the disks have already been upgraded to NetWare 3.1x, or when the disks do not have any NetWare partitions.Action: Load the appropriate disk drivers and restart the upgrade process.PAGENUM=16 ID="BP10"112: No NetWare 2.1x or 2.2 volumes can be found on any of the disks. Check for disk drivers that are loaded without any disks attached. The In-Place Upgrade process is now being aborted.2XUPGRDEExplanation: Either no volumes were found, or the volumes found were already labeled as NetWare 3.1x volumes. This situation occurs when incorrect disk drivers are loaded or when hard disks have been accidently disconnected from their drivers.Action: Make sure that the correct disk drivers are loaded and that the disks have not already been upgraded. Also check for loose cables to the hard disks.113: This hard disk contains more than 8 volumes. NetWare 3.1x allows a maximum of only 8 volumes per hard disk. The In-Place Upgrade process is now being aborted.2XUPGRDEExplanation: NetWare 2.1x allows for a maximum of 16 volumes per hard disk, while NetWare 3.1x is limited to a maximum of 8 volumes per hard disk.Action: Use an upgrade method other than this In-Place process.114: Macintosh files were found, but the Macintosh name space module was not loaded. Load MAC.NAM then restart the upgrade process. The In-Place Upgrade process is now being aborted.2XUPGRDEExplanation: During the System Analysis phase, Macintosh files and folders where found on the disks. The Macintosh name space module, MAC.NAM, was not loaded before starting the upgrade. Without this module loaded, the volumes with the Macintosh files do not mount. If the SYS: volume has any Macintosh files, then the SYS: volume does not mount during the Bindery phase and the bindery does not get upgraded.Action: Exit the In-Place upgrade, load MAC.NAM, then restart the upgrade. MAC.NAM is usually found on the System 1 or System 2 diskette.115: The number of megabytes requested for a DOS partition (number) is too large. Space for a DOS partition is taken from the unused blocks on the SYS: volume. Either free space on the SYS: volume or restart the upgrade and request no more than number megabytes for a DOS partition. The In-Place Upgrade process is now being aborted.2XUPGRDEExplanation: Another way to free disk blocks is to run the NetWare 2.x PURGE utility if it was not run before running the upgrade. The "request no more than number megabytes" is an estimate and may need to be even less than estimated. Valid sizes are from 0  to 32.Action: Move data from the SYS: volume to another volume. Be sure to run the PURGE utility afterwards.PAGENUM=17 ID="BP11"116: Device #number has a hidden partition which overlaps with the NetWare 2.1x partition. NetWare 3.1x cannot access the disk blocks that NetWare 2.1x may have written into the hidden partition. This disk cannot be upgraded.2XUPGRDEExplanation:  This message is displayed when the disk size detected by NetWare 2.x is larger than detected by NetWare 3.x. Some computer vendors place a hidden partition onto their disks to store diagnostic and set-up information. These partitions are small, typically about 2 MB. They can be found on IBM PS/2 models 55, 56, and 95. NetWare 2.x is not very partition-aware. When NetWare 2.x is installed, its default is to claim the entire disk, including the hidden partition. The Hot Fix Redirection Area would overlap this hidden partition. NetWare 3.x is partition-aware. It recognizes the hidden partition, but does not allow it to be accessed. This disk cannot be upgraded since not all of the NetWare 2.x disk blocks can be accessed.Action:  Choose another upgrade method. To avoid this problem with new 2.x installations, choose a smaller End cylinder for the NetWare partition.121: The Directory Entry Table cannot be read due to a bad disk block. The In-Place Upgrade process is now being aborted.2XUPGRDEExplanation: The NetWare 2.1x Directory Entry Table (DET) could not be read from the disk. The disk has a bad block. Without the DET, files and directories will be lost or corrupted.Action: Reboot the server and run the NetWare 2.1x VREPAIR utility. (You may need to run VREPAIR several times until the problem is fixed.)122: The file "DIRSTAMP.SYS" cannot be found. The Directory Entry Table is either corrupted or it is from a version of NetWare not supported by this upgrade program. The In-Place Upgrade process is now being aborted.2XUPGRDEExplanation: The file DIRSTAMP.SYS is used to store information about directories and Macintosh files. This file could not be found when a portion of the NetWare 2.1x Directory Entry Table (DET) was accessed. Without this file, the directories cannot be read.Action: If the DET is corrupted, reboot the server and run the NetWare 2.1x VREPAIR utility to repair it. Make sure that you are upgrading from NetWare 2.1x or 2.2 only. (You may need to run VREPAIR several times until the problem is fixed.)123: The file "DIRSTAMP.SYS" cannot be read. Volume name:'s FAT Table may be corrupted.2XUPGRDEExplanation: DIRSTAMP.SYS is the first file on every NetWare 2.1x volume. If the File Allocation Table (FAT) is corrupted, this file will not be read properly. This error message aborts the upgrade, preventing the paddle wheel from spinning endlessly while in the Disk Analysis phase. If the FAT is corrupted, a symptom may be that only the first 4 KB disk block of each file can be read, causing utilities to "hang" abnormally after being loaded.Action: Your server may have some serious hardware problems. Bring up your NetWare 2.x server and get it into a working state before retrying the In-Place Upgrade.PAGENUM=18 ID="BP12"124: The file server shows symptoms of being downed too quickly. Reboot your NetWare 2.1x server, down it, then wait two or three minutes to be sure that all file transactions are complete before turning the power off.2XUPGRDEExplanation:  The proper way to down a NetWare 2.1x server is to type "DOWN" at the system console prompt, then wait a few minutes before turning the power off. Even after the server responds that it is down, background disk activity can still occur. Common activity may include disk remirroring and Transaction Tracking System file manipulation. Downing the server by simply turning off the power switch may also cause this message to appear.Action: Do the following:1. Reboot the server as a NetWare 2.1x server.2. Type "DOWN" at the console prompt to down the server.3. Wait for up to two or three minutes to be sure there is no more disk activity.4. Reload the NetWare 3.1x operating system and restart the In-Place Upgrade NLM.131: The disk's Partition Table cannot be written to (status = status_number). The Disk Modification Phase cannot be completed without first modifying the Partition Table to recognize NetWare 3.1x partitions. The In-Place Upgrade process is now being aborted.2XUPGRDEExplanation: This error occurs after the disk is first written to at the start of Phase 3. The status indicates the cause of the failure. If the status is equal to 2 or 3, no data has been lost. Otherwise, all data on this disk may be lost. Only the partition table on sector 0 of the disk has been written to.Action: If you have lost your volumes, restore the disk from your backups, then upgrade using another upgrade method.132: The disk which contains the SYS: volume cannot be written to. The In-Place Upgrade process is now being aborted.2XUPGRDEExplanation: The first disk (disk #0), which contains the SYS: volume, cannot be written to. The upgrade is aborted. This message is always preceded by message 231.Action: See 2XUPGRDE error messageIDREF="FM85941" "231: The new NetWare 3.1x partition number cannot be found after writing it to the disk's Partition Table. This disk cannot be upgraded. The disk has been restored to its original state BEFORE the upgrade so no data has been lost. This error may have been produced by faulty hardware." .PAGENUM=19 ID="BP13"133: The Hot Fix Redirection Area in the NetWare 3.1x disk partition cannot be created. The In-Place Upgrade process is now being aborted.2XUPGRDEExplanation: A call to the operating system which creates the Hot Fix Redirection Area, has failed. Your hard disk may be faulty.Action: Make sure that your hard disk is still working.134: The Logical Partition on this disk cannot be opened (status = status_number). The In-Place Upgrade process is now being aborted.2XUPGRDEExplanation: The disk's Logical Partition, which stores the system tables and volume segments, cannot be opened. The status indicates the underlying cause of the error. If the status is equal to 1, a resource could not be obtained; if the status is equal to 14, the logical partition could not be locked.Action: Make sure that your hard disk is still working.135: The Mirror Information Table in the NetWare 3.x disk partition cannot be created. The In-Place Upgrade process is now being aborted.2XUPGRDEExplanation: The table containing disk mirroring information, located inside the Hot Fix Redirection Area, cannot be created. Your hard disk may be faulty. Version 1.00 of the In-Place Upgrade NLM did not create the Mirror Information Table. The NetWare 3.1x INSTALL.NLM file automatically creates this table, if it does not already exist, after you select "Disk Options" and then "Mirroring."Action: Consider replacing your hard disk or performing a low level format to mark any bad disk blocks.141: The NetWare 2.1x or 2.2 bindery files cannot be opened. User accounts, including passwords, will not be upgraded. Bindery files are created when the 2.1x server is first booted after an installation. The In-Place Upgrade process is now being aborted.2XUPGRDEExplanation: The NetWare 2.1x bindery consists of two files located in the SYS:SYSTEM directory: NET$BIND.SYS (for objects and properties) and NET$BVAL.SYS (for property data sets). These bindery files contain the names of users, their rights, their passwords, etc. One or both of these files could not be found or opened. This message is also displayed when a new NetWare 2.1x server has been installed but not booted yet. When a server is booted for the first time, the bindery is created.Action: At this point, the file system has been upgraded to NetWare 3.1x. To finish the upgrade, do the following:MARK=BULLETGet the uncorrupted NetWare 2.1xPAGENUM=20 ID="BP14" bindery files from your backups. They are named NET$BIND.SYS and NET$BVAL.SYS and were located in the SYS:SYSTEM directory. If they cannot be found, use NET$BIND.OLD and NET$BVAL.OLD after renaming them with the .SYS extension.Mount the newly upgraded SYS: volume on the NetWare 3.1x server using the "MOUNT SYS" command.Load a LAN driver and bind IPX to it.Log in from a workstation and copy the NetWare 2.1x bindery files into the SYS:SYSTEM directory.Restart the upgrade with the "/BINDERY" option.The bindery will be upgraded; however, the new user IDs in the bindery will not be associated with the files, directories, and trustees, except for users SUPERVISOR and GUEST. Use the NetWare 3.1x GRANT utility or the NetWare 4.x RIGHTS utility to create new trustees after completing the upgrade.151: This NetWare server has insufficient memory to complete the upgrade. The In-Place Upgrade process is now being aborted.2XUPGRDEExplanation: Your server does not have enough free memory to run the upgrade. Servers using large hard disks or having many directories may need additional memory when upgrading. (The upgrade process uses approximately 8 KB of additional memory for each directory and 4 KB for each megabyte of your hard disk.) A server may require more memory to do the In-Place upgrade than is needed to operate the server on a day-to-day basis. This is because the upgrade caches the entire directory table for a given disk, whereas the server normally only caches a portion of the directory tables.Action: Install more memory in your server.152: The hard disk containing the volume_name: volume has insufficient free space to complete the upgrade. Each volume should have at least 10% free space. The In-Place Upgrade process is now being aborted.2XUPGRDEExplanation: Your server does not have enough free hard disk space to run the upgrade. You will need about 10% of free disk space per volume to accommodate the NetWare 3.1x file system. The SYS: volume may need more than 10% free disk space to accommodate the optional DOS partition. NetWare 3.1x directory tables and the FAT table use more disk space than the NetWare 2.1x tables. Even more disk space is needed for a DOS partition; NetWare 4.x requires a minimum of 5 MB.Action: Bring the NetWare 2.1x server up and run the PURGE utility to free up disk space. Remove all files except for system files until approximately 10% of each volume on the disk is free, or specify a smaller DOS partition size during the upgrade. You can use the VOLINFO utility to display the disk space availability of each volume.PAGENUM=21 ID="BP15"153: The In-Place Upgrade process has been aborted by the user. The In-Place Upgrade process is now being aborted.2XUPGRDEExplanation: During the upgrade process, the user is given the option to abort the upgrade. This option is not given in Phases #3 and #4. The In-Place Upgrade NLM is unloaded, and the user is returned to the console prompt ( : ).Action: None. This message is for information only.191: The previously saved restart data cannot be read from the disk. This partially upgraded disk cannot be upgraded. The In-Place Upgrade process is now being aborted.2XUPGRDEExplanation:  A call to read from the disk failed. This message is given only after an upgrade fails and restart data needs to be retrieved to finish the upgrade. The hard disk may have gone bad, specifically sectors 26 through 31 and the blocks pointed to by the 4-byte values stored in sectors 27 through 29. The hard disk may have failed. Restart cannot function if the drive has a hardware problems, such as a head crash or new bad blocks. Action:  Unload then reload the disk drivers and retry the upgrade process. 192: The file system does not have the same number of hard disks as were available with the initial upgrade session. Ensure that all of the device drivers are loaded just as they were before. The In-Place Upgrade process is now being aborted.2XUPGRDEExplanation:  The number of devices, which includes hard disks, tape drives, etc., is not the same as it was when the upgrade failed. A device driver that was loaded before was probably not loaded with the restart upgrade session. This number includes devices registered with NetWare since NetWare was loaded, of which some or all may have been deleted or deactivated.Action:  Load all of the device drivers that were loaded with the initial upgrade attempt and restart the upgrade.193: The device number stored onto the disk during the initial upgrade session (device #number) does not match the device number that is currently set for this disk (device #number). Ensure that all of the device drivers are loaded just as they were before. The order in which the device drivers are loaded must also be the same as before. The In-Place Upgrade process is now being aborted.2XUPGRDEPAGENUM=22 ID="BP16"Explanation: When a device driver is loaded, each device, or hard disk, registers a unique number with NetWare. This number is not the same as it was with the initial upgrade attempt. Device drivers must be loaded in the same order as they were with the initial upgrade session. This message simply ensures that the file system is the same as it was during the first In-Place upgrade session.Action:  Unload all of the device drivers and reload them in the same order as the initial upgrade session.194: Multiple partially upgraded disks have been found.2XUPGRDEExplanation:  Restart data on each disk indicates the phase in which the upgrade failed. When two disks are found to have failed during the Disk Modification phase, this message is given. It indicates that disks may have been substituted in an attempt to finish multiple failed upgrades. This message should be seen rarely.Action:  Restore the file system to its original configuration and restart the upgrade.201: The number of megabytes specified on the command line for a DOS partition is too large. 32 megabytes are being reserved for a DOS partition.2XUPGRDEExplanation: You used the /P parameter on the command line with an invalid number for the size of the DOS partition. Valid numbers include 0 through 32 only, with no fractions. Because the number entered was greater than the maximum of 32 MB, the maximum was assigned instead.Action: If you do not want a 32 MB DOS partition, unload the upgrade process and start over. Do this by pressing the MOREINFO="NONE"<Alt>+<Esc> keys to return to the console prompt; then type the following command:MOREINFO="NONE"UNLOAD 2XUPGRDE202: WARNING: File ownership and trustee assignments are not upgraded when using the /BINDERY option. New trustee rights may need to be granted after the bindery is upgraded.2XUPGRDEExplanation: The /BINDERY option can be used to upgrade the NetWare 2.1x bindery if the upgrade failed after modifying a disk but before the bindery phase was completed. In some rare instances, the server has enough memory to complete the file system upgrade but not enough to mount the SYS: volume afterwards. The /BINDERY option is provided for this situation; however, trustee rights are lost for all users except SUPERVISOR and GUEST.Action: Use the NetWare 3.1x GRANT utility or the NetWare 4.x NETADMIN or RIGHTS utility to create new trustees after completing the upgrade.PAGENUM=23 ID="BP17"211: The maximum number of upgradable disks (32) has been exceeded. This disk (disk #disk_number) will not be upgraded.2XUPGRDEExplanation: The In-Place utility will upgrade a maximum of 32 disks. NetWare 2.1x and 2.2 support only 32 disks per server, while NetWare 3.x supports up to 2,048 disks.Action: After completing the In-Place upgrade for the first 32 disks, unload the disk drivers for the disks that have been upgraded; then run the upgrade again.212: The SYS: volume cannot be found. Without this volume, NetWare 3.1x will not operate.2XUPGRDEExplanation: The SYS: volume was not present on any of the disks. Both NetWare 2.1x and 3.1x require a volume named SYS: in which to store system files. The upgrade process is not automatically aborted, because some users may want to upgrade disks that were not connected to the server after the initial upgrade.Action: After pressing any key to continue, type "Y" to continue with the upgrade without the SYS: volume, or type "N" to exit the upgrade. Grant trustee rights on the upgraded volumes afterwards.213: The DOS partition will be placed on the same external hard disk as the SYS: volume. Very few computer systems can use a DOS partition on an external hard disk.2XUPGRDEExplanation: The SYS: volume is on an external hard disk such as one connected through a Novell Disk Coprocessor Board (DCB), an ADIC, or a Procomp USA disk subsystem. The DOS partition is placed on the same disk as the SYS: volume. The requested DOS partition will still be created; however, DOS currently does not support external hard disks. A DOS partition makes booting a NetWare 3.1x server considerably faster; however, it is not necessary for NetWare 3.1x. A DOS partition of at least 5 MB is required by NetWare 4.x.Action: Do one of the following:MARK=BULLETIf you have a Novell 386 AE server with a DCB controller, do nothing. It is one of the few computers that can boot from a DOS partition on an external disk.Complete the upgrade; then add a new internal hard disk for the SYS: volume and the DOS partition. Ignore 2XUPGRDE error message 141, which will be issued at the start of the Bindery phase since the bindery is stored on the SYS: volume.Reconfigure the server before performing the upgrade, placing the SYS: volume on an internal hard disk. This option is especially useful if you plan to upgrade later to NetWare 4.x.PAGENUM=24 ID="BP18"214: Volume SYS: has less than 10% free disk space after accounting for the number MB DOS partition. You should either free space on this volume or request a smaller DOS partition size.2XUPGRDEExplanation:  During the System Analysis phase, the free disk space estimate calculated that less than 10% of the disk is would be free after making room for the DOS partition. This is a noncritical error, since it is only an estimate.Action:  Do one or more of the following:MARK=BULLETContinue with the upgrade and see if enough free disk space is really available, as determined during each disk's Disk Analysis phase.Free up space on the SYS: volume by moving or deleting files and running the NetWare 2.x PURGE utility afterwards.Request a smaller DOS partition size.215: Volume name: has less than 10% free disk space. You may need to free some space on this volume since the Directory Entry Tables and File Allocation Tables are larger in NetWare 3.x.2XUPGRDEExplanation:  Explanation: During the System Analysis phase, the free disk space estimate calculated that less than 10% of the disk is would be free.  This is a noncritical error because it is only an estimate.Action: Do one or more of the following:MARK=BULLETContinue with the upgrade and see if enough free disk space is really available, as determined during each disk's Disk Analysis phase.Free up space on the volume by moving or deleting files and running the NetWare 2.x PURGE utility afterwards.221: A directory entry with no parent exists in the Directory Entry Table. The Directory Entry Table translation process should proceed normally.2XUPGRDEExplanation: A directory was found without a complete path to it. The directory and its files cannot be accessed.Action: Do one of the following:MARK=BULLETComplete the upgrade and run the NetWare 3.1x VREPAIR utility afterwards. (This is the recommended method.)PAGENUM=25 ID="BP19"Reboot the server and run the NetWare 2.1x VREPAIR utility; then restart the upgrade. (You may need to run VREPAIR several times until the problem is fixed.)222: Disk #number cannot be opened. Ensure that its disk driver is properly loaded.2XUPGRDEExplanation: The disk cannot be opened for reads and writes.Action: Make sure that the correct disk drivers have been loaded properly.223: The partition table on the disk containing the SYS: volume has no free entries available to write DOS partition information.2XUPGRDEExplanation:  DOS compatible hard disks can have up to four partitions each. The table describing the physical drive parameters of each partition is stored on sector 0. In order to use the disk space being made available for a DOS partition, DOS's FDISK utility needs at least one free entry in the partition table.Action:  Either restart the upgrade and specify 0 MB for the optional DOS partition, or use FDISK after the upgrade to combine or delete the existing disk partitions.224: WARNING: Directory name "old_directory_name" will be renamed to "new_directory_name".2XUPGRDEExplanation: An illegal directory name was found. NetWare 2.1x allowed for directory names up to 14 characters long. NetWare 3.x shortened the length to 11 characters to conform to DOS's eight-character name, three-character extension format. With the "8 dot 3" (8.3) format, directories can have up to eight characters before the period (.) and up to three characters after the period. If a name conflict occurs, the directory will be given a numbered extension starting with ".001."Action: Make note of the new directory name.225: WARNING: Filename "old_filename" will be renamed to "new_filename".2XUPGRDEExplanation: An illegal filename was found. NetWare 2.1x allowed for filenames up to 14 characters long. NetWare 3.x shortened the length to 11 characters to conform to DOS's eight-character name, three-character extension format. With the "8 dot 3" (8.3) format, files can have up to eight characters before the period (.) and up to three characters after the period. If a name conflict occurs, the file will be given a numbered extension starting with ".001".Action: Make note of the new filename.ID="FM85941"231: The new NetWare 3.1x PAGENUM=26 ID="BP20"partition number cannot be found after writing it to the disk's Partition Table. This disk cannot be upgraded. The disk has been restored to its original state BEFORE the upgrade so no data has been lost. This error may have been produced by faulty hardware.2XUPGRDEExplanation: This error occurs after the disk is first written to at the start of the Disk Modification Phase. It has been known to occur on certain faulty PS/2 Model 80 system boards that handle 32-bit addressing incorrectly (ECA 048). The following PS/2 system boards may produce this message:COLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="5*"COLNAME=3 COLWIDTH="10*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Model#COLNAME=2 ROTATE="0" MOREROWS="0"Serial#COLNAME=3 ROTATE="0" MOREROWS="0"RangeCOLNAME=1 ROTATE="0" MOREROWS="0"8580COLNAME=2 ROTATE="0" MOREROWS="0"111COLNAME=3 ROTATE="0" MOREROWS="0"600 - 6101499COLNAME=1 ROTATE="0" MOREROWS="0"8580COLNAME=2 ROTATE="0" MOREROWS="0"121COLNAME=3 ROTATE="0" MOREROWS="0"45000 - 49999COLNAME=1 ROTATE="0" MOREROWS="0"8580COLNAME=2 ROTATE="0" MOREROWS="0"121COLNAME=3 ROTATE="0" MOREROWS="0"9000 - 9014999COLNAME=1 ROTATE="0" MOREROWS="0"8580COLNAME=2 ROTATE="0" MOREROWS="0"311COLNAME=3 ROTATE="0" MOREROWS="0"65000 - 6553499COLNAME=1 ROTATE="0" MOREROWS="0"8580COLNAME=2 ROTATE="0" MOREROWS="0"321COLNAME=3 ROTATE="0" MOREROWS="0"92000 - 9215499This error has also been known to occur on PS/2 Model 56 and Model 95, both of which contain a hidden disk partition for storing microchannel reference information.Action: Check your PS/2 Model 80 system board's serial number. Replace your system board if it has one of the above serial numbers. After your hardware is working correctly, retry the upgrade.240: The user mail directories in SYS:MAIL cannot be renamed to match each user's new User ID.2XUPGRDEExplanation:  The MAIL directory on the SYS: volume contains user mail directories. They are named with the user's bindery ID number. Since users are given new bindery object IDs when the bindery is upgraded, these directories are renamed. These directories contain login scripts and print job configurations under NetWare 3.1x. They are currently not being used by NetWare 4.x.Action:  Use the NetWare 3.1x SYSCON utility to determine each user's NetWare 3.1x bindery ID, then rename their previous mail directories to their new number.241: The Logical Partition on disk #number cannot be opened. Trustee rights and file owner information on this disk will be lost.2XUPGRDEExplanation: The disk's logical partition, which stores the system tables and volume segments, cannot be opened. The bindery has been upgraded successfully at this point; however, the trustees and the file ownership information cannot be recorded.Action: Reassign file ownership and trustee rights by using the FILER and GRANT commands, or by using SYSCON.PAGENUM=27 ID="BP21"242: The Directory Entry Table for volume name: cannot be read as needed to update new User IDs. Trustee rights and file owner information may be lost.2XUPGRDEExplanation: The directory cannot be read into memory. Information such as file ownership and trustee rights are lost.Action: Reassign file ownership and trustee rights by using the FILER and GRANT commands, or by using SYSCON.243: The Directory Entry Table for volume name: cannot be written as needed to update new User IDs. Trustee rights and file owner information may be lost.2XUPGRDEExplanation: The directory cannot be written to. Information such as file ownership and trustee rights are lost.Action: Reassign file ownership and trustee rights by using the FILER and GRANT commands, or by using SYSCON.ID="FM91939"244: The bindery property at offset number cannot be read.2XUPGRDEExplanation: A bindery property could not be read from the file NET$BIND.SYS. The NetWare 2.1x bindery may have been corrupted, or the NET$BIND.SYS file failed to open.Action: At this point, the file system has been upgraded to NetWare 3.1x. To finish the upgrade, do the following:MARK=BULLETGet the uncorrupted NetWare 2.1x bindery files from your backups. They are named NET$BIND.SYS and NET$BVAL.SYS and were located in the SYS:SYSTEM directory. If they cannot be found, use NET$BIND.OLD and NET$BVAL.OLD after renaming them with the .SYS extension.Mount the newly upgraded SYS: volume on the NetWare 3.1x server using the "MOUNT SYS" command.Load a LAN driver and bind IPX to it.Log in from a workstation and copy the NetWare 2.1x bindery files into the SYS:SYSTEM directory.Restart the upgrade with the "/BINDERY" option.The bindery will be upgraded; however, the new user IDs in the bindery will not be associated with the files, directories, and trustees, except for users SUPERVISOR and GUEST. Use the NetWare 3.1x GRANT utility or the NetWare 4.x RIGHTS utility to create new trustees after completing the upgrade.PAGENUM=28 ID="BP22"245: A particular NetWare 2.1x or 2.2 bindery value cannot be written to the NetWare 3.1x bindery.2XUPGRDEExplanation: A bindery value read from NetWare 2.1x's NET$BVAL.SYS could not be written to NetWare 3.1x's NET$VAL.SYS file. The NetWare 2.1x bindery may have been corrupted.Action: See 2XUPGRDE message IDREF="FM91939" "244: The bindery property at offset number cannot be read." .246: The random passwords file named "NEW.PWD" cannot be created. No passwords will be assigned to the users.2XUPGRDEExplanation: User passwords cannot be transferred from NetWare 2.1x's bindery to NetWare 3.1x's bindery. The In-Place Upgrade utility could not create a file named NEW.PWD in the SYS:SYSTEM directory. Users are given no passwords because passwords cannot be recorded.Action: Manually assign users new passwords after the upgrade is completed, using the SYSCON utility from a workstation.247: A random password cannot be assigned to user username.2XUPGRDEExplanation: User passwords cannot be transferred from NetWare 2.1x's bindery to NetWare 3.1x's bindery. An attempt to assign a newly generated password to the user failed. No new password is given to this user.Action: Manually assign users new passwords after the upgrade is completed using the SYSCON utility from a workstation.248: The File Server bindery object has been renamed from "old_server_name" to "new_server_name" to correspond with the server's new name.2XUPGRDEExplanation: The name of the server is stored inside the bindery. When the NetWare 3.1x server operating system was loaded, the server was given a different name than that of the NetWare 2.1x server. The File Server bindery object was renamed to reflect the newly given name. This prevents the SLIST utility from erroneously seeing the old server name, which is no longer available.Action: If you do not like the server's new name, bring down the server and bring it back up again, giving it another name. Change the "file server name" line inside the AUTOEXEC.NCF file in the SYS:SYSTEM directory (for example, "file server name FILESERVER"). Note: This line is required and is usually the first line in the AUTOEXEC.NCF file.PAGENUM=29 ID="BP23"249: WARNING: The file NEW.PWD in the SYS:SYSTEM directory already exists. It has been renamed to "new_name". Random passwords for this upgrade session will still be written to NEW.PWD.2XUPGRDEExplanation: The filename used to store user's random passwords already exists. Other NetWare utilities that create NEW.PWD are NetWare Name Service (NNS) and the Across-The-Wire Migration utility. The old NEW.PWD file will be renamed to NEWPWD.xxx where xxx is a numbered extension (starting with ".001").Action: Take note of the name change so the old file can be deleted if it is no longer needed.251: The NetWare operating system produced an internal error while attempting to release the disk device.2XUPGRDEExplanation: The upgrade process is unable to give the hard disk resource back to the operating system.Action: This may be a symptom of an operating system failure. Reboot the system and start the upgrade process again.252: The disk device lock has been revoked by the operating system. This hard disk may have just failed.2XUPGRDEExplanation: The disk device information was temporarily lost by the operating system. This may have been caused by a hard disk failure.Action: Make sure that your hard disk is still working. Use an updated disk driver if one is available. If you used ISADISK.DSK, try using IDE.DSK.261: The disk with the SYS: volume cannot be found. Trustee rights and file owner information on each volume cannot be updated.2XUPGRDEExplanation:  The SYS: volume contains the bindery. The bindery contains user and group IDs, which are used to identify trustee rights and file ownership. Without these new IDs, the obsolete NetWare 2.1x IDs in the directory tables will not be updated. The SUPERVISOR and GUEST user IDs are the same in both NetWare 2.1x and 3.1x and will not be affected.Action:  Reassign file ownership and trustee rights by using the FILER and GRANT utilities, or by using SYSCON.291: Insufficient free disk space is available for saving all of the restart data. The upgrade will continue, still saving most of the restart data. The unsaved data will only be needed in the unlikely event of a failure during the block movement segment of the Disk Modification phase for this disk only.2XUPGRDEExplanation:  The majority of the restart data is saved into six unused 3 KB sectors of the NetWare 2.1xPAGENUM=30 ID="BP24" system area on track 0.  Large internal tables, such as the Block Move Table used when moving disk blocks during the Disk Modification phase, are saved to free 4 KB disk blocks on the disk. Not enough free disk blocks were available to save these internal tables.Action:  Continue with the upgrade. Unless the power fails during the disk's Disk Modification phase, nothing will be lost in the event of a loss of power. The "/NORESTART" command line option can also be used to perform an upgrade without saving any restart data.PAGENUM=31 ID="BP25"Abend: SERVERAbend: SERVER-4.10-message_number message_stringAbend: SERVERExplanation: Abend (abnormal ending) messages are usually caused by consistency check errors, but they can be caused by insufficient memory, DMA (direct memory access) conflicts, or hardware and software interrupts.If the following abend message appeared, Abend: SERVER-4.10-2: Error returned by object mapping routine.The software module is "Abend: SERVER", the version is "4.10", the message number is "2", and the message string is "Error returned by object mapping routine." Action: For information on all abend messages, see "BOOK="superenu" COLLECTION="nw41"Resolving Abends" in Supervising the Network.PAGENUM=32 ID="BP26"ADSP17: This version of ADSP is incompatible with the version of APPLETLK loaded.ADSPExplanation: The version of the APPLETLK.NLM did not match the one expected by ADSP.Action: Record the version numbers of the APPLETLK.NLM and ADSP.NLM files and contact your Novell Authorized Reseller.25: AppleTalk Data Stream Protocol services are currently in use.ADSPExplanation: Some applications still have streams open to ADSP and AppleTalk. The server could abend if the ADSP.NLM continues to be unloaded.Action: Abort the UNLOAD command to preserve server integrity. Unload the NLM files that are using ADSP to allow them to exit gracefully. Then unload ADSP.NLM. For information on UNLOAD, see "BOOK="utlrfenu" COLLECTION="nw41"UNLOAD" in Utilities Reference.90: It is not advisable to unload ADSP. ADSPExplanation: Some applications are still using ADSP. The server could abend if the ADSP.NLM continues to be unloaded.Action: Abort the UNLOAD command to preserve server integrity. Unload the NLM files that are using ADSP to allow them to exit gracefully. Then unload the ADSP.NLM. For information on UNLOAD, see "BOOK="utlrfenu" COLLECTION="nw41"UNLOAD" in Utilities Reference.314: A memory allocation has failed.ADSPExplanation: Unable to acquire necessary memory. The server may not have enough available memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.408: A small memory allocation has failed.ADSPExplanation: The allocation or duplication of a streams message block failed.Action: If the problem persists, see "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.502: AppleTalk Data Stream Protocol did not start up correctly.ADSPExplanation: ADSP did not load due to an initialization error. This message usually follows another message that indicates the nature of the error.Action: Correct the problem indicated by the error message and reload ADSP. PAGENUM=33 ID="BP27"503: The AppleTalk Data Stream Protocol cannot use STREAMS.ADSPExplanation: ADSP cannot use STREAMS and did not load. The server may not have enough available memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.504: The AppleTalk Data Stream Protocol cannot use APPLETLK.ADSPExplanation: ADSP cannot open an AppleTalk DDP socket. The server may not have enough available memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.505: AppleTalk Data Stream Protocol services are not available through STREAMS.ADSPExplanation: A stream could not be opened for the ADSP protocol. ADSP did not load. The server may not have enough available memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.506: APPLETLK services are not available to the AppleTalk Data Stream Protocol.ADSPExplanation: The ADSP and APPLETLK streams cannot be linked. The APPLETLK.NLM has not completed its initialization.Action: Reload ADSP. If the problem persists, load INETCFG and review the AppleTalk protocol configuration and AppleTalk BIND commands to make sure the stack has been homed. If the configuration is correct, record the versions of the ADSP.NLM, APPLETLK.NLM, and STREAMS.NLM, and contact your Novell Authorized Reseller. For information on INETCFG, see "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference.507: The AppleTalk Data Stream Protocol might not have been able to stop using APPLETLK.ADSPExplanation: A problem unlinking ADSP from the AppleTalk stream when unloading ADSP. ADSP probably failed to load.Action: Correct any problems loading ADSP. If the problem persists, contact your Novell Authorized Reseller.508: The AppleTalk Data Stream Protocol might not have been able to clean up.ADSPExplanation: A problem occurred while trying to close the ADSP control stream. ADSP probably failed to load.Action: Correct any problems loading ADSP. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=34 ID="BP28"509: The AppleTalk Data Stream Protocol was not able to stop using STREAMS. Either ADSP was not using STREAMS, or other services are still using ADSP.ADSPExplanation: ADSP could not deregister from STREAMS; however, it did unload. Applications using ADSP may not be informed that ADSP is no longer available.Action: If ADSP did not load, correct any problems and reload ADSP. If ADSP loaded successfully, don't unload ADSP while applications are using it. 617: A memory allocation of number bytes has failed.ADSPExplanation: ADSP cannot allocate memory for a required resource. The server may not have enough available memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.6000: Cannot resolve external symbol name.ADSPExplanation: ADSP could not find a required public symbol. The symbol should be provided by the NetWare 4 operating system. Action: Record the version of NetWare and the ADSP.NLM in use. Contact your Novell Authorized Reseller.PAGENUM=35 ID="BP29"AFP1: Desktop allocation error on volume name.AFPExplanation: The server does not have enough available memory to run AFP.NLM. Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.5: Desktop reset error on volume name.AFPExplanation: AFP could not close and delete the desktop database files on the specified volume. Action: Make sure no other applications, including backup and restore programs, have the desktop database files open on the volume.6: Desktop has been reset on volume name.AFPExplanation: The network supervisor used AFPCON to rebuild the desktop for the specified volume.Action: None. This message is for information only.9: Insufficient memory to enable Reply Cache.AFPExplanation: The server does not have enough available memory to make using the Finder Accelerator worthwhile. Under these conditions, the memory would be better used in the server's file cache buffers.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.12: An invalid user access method was entered. Access method was not updated.AFPExplanation: The AFP configuration file contained invalid data concerning available login methods. AFP will restore the default values for this item.Action: To enable a login method that is not enabled by default, use AFPCON. For information, see "BOOK="utlrfenu" COLLECTION="nw41"ATCON" in Utilities Reference.13: Btrieve record manager inactive---unable to access desktop database on volume name.AFPExplanation: The state of BTRIEVE.NLM prevents AFP.NLM from using Btrieve.Action: Check the server's the AUTOEXEC.NCF file loads the error log for messages from BTRIEVE.NLM about this problem.PAGENUM=36 ID="BP30"14: Unable to write to desktop database on volume name.AFPExplanation: AFP could not write to the disk, probably because the disk was full or the volume is corrupted.Action: Increase the available disk space on the volume. Make sure the volume is not corrupted. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Disk Space Problems" in Supervising the Network.17: An invalid value for maximum number of AFP connections was entered. Value will not be updated.AFPExplanation: The AFP configuration file contained invalid data concerning the maximum number of AFP connections allowed. AFP will restore the default value for this item.Action: Use ATCON to specify a setting different from the default. For information on ATCON, see "BOOK="utlrfenu" COLLECTION="nw41"ATCON" in Utilities Reference.19: Unable to write configuration data to file (filename).AFPExplanation: AFP could not write the file to the disk, probably because the disk is full or the volume is corrupted.Action: Increase the available disk space on the volume. Make sure the volume is not corrupted. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Disk Space Problems" in Supervising the Network.28: AFP Server unregistered with NBP because the NetWare Directory is inaccessible.AFPExplanation: The Directory database on this server is no longer accessible. This problem may be caused by improper installation, by a faulty backup, or by a faulty DSREPAIR operation. Because users cannot log in while NetWare Directory Services is unavailable, the server will not appear in the Chooser.Action: Reinitialize NetWare Directory Services. NetWare for Macintosh will complete the NBP registration.56: Unable to create directory name on volume name: error number.AFPExplanation: AFP could not create the specified directory to hold the desktop database files on the NetWare specified volume because of a disk error or corrupted volume.Action: Use VREPAIR to remedy the problem. For information on VREPAIR, see "BOOK="utlrfenu" COLLECTION="nw41"VREPAIR" in Utilities Reference. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A.PAGENUM=37 ID="BP31"74: NetWare for Macintosh License violation detected: Server name in zone name has a duplicate serial number!AFPExplanation: AFP.NLM detected a license violation. More that one server is using the same NetWare for Macintosh license. A different license is required for each server using the AFP.NLM.Action: Use a licensed version of NetWare for Macintosh bundled with the NetWare operating system, or install a different NetWare for Macintosh license on each server using the AFP.NLM.80: NOTICE: This copy of AFP.NLM has an invalid serial number.AFPExplanation: This copy of AFP.NLM is corrupted. Action: Reinstall the file from the original floppy diskette or CD-ROM. 90: Incompatible version of Appletalk (APPLETLK.NLM).AFPExplanation: AFP.NLM is incompatible with this version of APPLETLK.NLM. Action: Make sure the version of APPLETLK.NLM that the AUTOEXEC.NCF file loads was the APPLETLK.NLM shipped with the latest version of NetWare for Macintosh.99: Failure registering AFP server name in Zone name: that name already exists.AFPExplanation: There are two servers with the same name in the zone listed. Each server must have a unique name. This problem may have been caused by copying an AUTOEXEC.NCF file from one server to another. Action: Make sure the server name is correct in the AUTOEXEC.NCF file and in AFPCON's General Server Information window.101: AFP Server not registered because the NetWare Directory is inaccessible.AFPExplanation: The Directory database on this server is no longer accessible. This problem may be caused by improper installation, by a faulty backup, or by a faulty DSREPAIR operation. Because users cannot log in while NetWare Directory Services is unavailable, the server will not appear in the Chooser.Action: Reinitialize NetWare Directory Services. NetWare for Macintosh will complete the NBP registration.103: Memory allocation failure during AFP initialization.AFPExplanation: The server does not have enough available memory to load and initialize AFP.NLM. Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.PAGENUM=38 ID="BP32"125: Memory allocation failure during AFP initialization.AFPExplanation: The server does not have enough available memory to load and initialize AFP.NLM. Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.126: Volume name is unavailable to AFP clients due to a memory allocation problem.AFPExplanation: Macintosh clients could not access the specified volume because the server does not have enough available memory to load and run AFP.NLM. Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.127: Volume name is unavailable. Maximum number of pseudo volumes has been allocated.AFPExplanation: The specified volume is unavailable because the maximum number of CD-ROM discs (63) are in the NetWare home volume. Action: Move some CD-ROMs to other volumes. 133: Desktop Rebuild started on volume name.AFPExplanation: The desktop database on the specified volume is being rebuilt by AFPCON's "Start Desktop Database Rebuild" option. The rebuild runs as a low priority operation then produces a completion message.Action: None. This message is for information only.134: Desktop rebuild halted on volume name: Found number application(s) and number icon(s).AFPExplanation: The desktop database rebuild on the specified volume has been cancelled by AFPCON's "Cancel Desktop Rebuild" option. The operation is halted immediately, and partial status information is displayed. The first number represents the number of applications found. The second number represents the number of icons found.Action: None. This message is for information only.136: Desktop rebuilt on volume name: Found number application(s) and number icon(s).AFPExplanation: A desktop database rebuild on the specified volume finished without interruption. The first number represents the number of applications found. The second number represents the number of icons found.Action: None. This message is for information only.PAGENUM=39 ID="BP33"138: This file has no resource fork. Bundle bit cleared. AFPExplanation: The Bundle flag is set, but no icon exists. This minor irregularity has been corrected. Many Macintosh files are distributed with a Bundle flag; this flag indicates that a file contains icons that the desktop database rebuilder should collect.Action: None. This message is for information only.139: This file has a damaged resource fork. It should be removed.AFPExplanation: The desktop database rebuilder found a file with a corrupted resource fork that it can't fix. The problem is usually caused by faulty Macintosh software, and it cannot be fixed by VREPAIR. Action: Delete the file, or recopy the file from the original Macintosh floppy disk. The file is probably corrupted.140: Unable to open file due to error code: filenameAFPExplanation: The desktop database rebuilder could not process the specified file probably due to the internal error. Action: Contact your Novell Authorized Reseller. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A.141: This file has no Bundle resource. Bundle bit cleared. AFPExplanation: The Bundle flag is set, but no icon exists. This minor irregularity has been corrected. Many Macintosh files are distributed with a Bundle flag; this flag indicates that a file contains icons that the desktop database rebuilder should collect.Action: None. This message is for information only.152: Memory Allocation error during operation: refused new session.AFPExplanation: The server does not contain enough available memory to support another user connection. If the problem occurs after the server is operative for a long time, it is most likely caused by a "memory leak" in another NLM. Action: Use the Memory Utilization menu in the MONITOR utility to determine which NLM is leaking memory; then unload that NLM.153: No users are connected; shutting down immediately.AFPExplanation: If all users have logged out of the server and the shutdown time set in AFPCON is less than five minutes, the shutdown operation will complete immediately. You can then safely unload AFP.NLM.Action: None. This message is for information only.PAGENUM=40 ID="BP34"154: No new logins will be accepted. Cancelling NBP registration.AFPExplanation: When the shutdown time set in AFPCON reaches five minutes or less, no new users are allowed to log in to the server. The server will not appear in the Macintosh Chooser.Action: None. This message is for information only.155: AFP Shutdown complete.AFPExplanation: The AFP shutdown operation has completed. All users have been disconnected, and the server no longer appears in the Macintosh Chooser. When the AFP shutdown is complete, the AFP.NLM can be safely unloaded.Action: To unload the AFP.NLM, unload it. 164: Connection number died because the AppleTalk Stack was unbound.AFPExplanation: Changing the configuration of the AppleTalk stack terminated the specified connection. Action: The user must log in again.167: Error code creating Network Trash Folder on volume name.AFPExplanation: The initialization of the specified volume could not be completed probably because of a disk error.Action: Use VREPAIR to fix the problem. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A.168: Error code creating Trash Can Usage Map file on volume name.AFPExplanation: The initialization of the specified volume could not be completed, probably because of a disk error.Action: Use VREPAIR to fix the problem. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A.174: Memory allocation failure during AFP initialization.AFPExplanation: The server does not have enough available memory to load and run AFP.NLM. Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. PAGENUM=41 ID="BP35"175: Volume name is unavailable to AFP clients due to a memory allocation problem.AFPExplanation: Macintosh clients could not access the specified volume because the server does not have enough available memory to load and run AFP.NLM. Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.176: Volume name is unavailable to AFP clients due to a memory allocation problem.AFPExplanation: Macintosh clients could not access the specified volume because the server does not have enough available memory to load and run AFP.NLM. Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.177: Desktop on volume name is unavailable to AFP clients.AFPExplanation: The specified volume is not available to NetWare for Macintosh clients because of an initialization problem. The volume will not appear in the Macintosh Chooser and cannot be mounted by Macintosh users. Action: See the previous messages in the server's error log to determine the exact nature of the problem.PAGENUM=42 ID="BP36"APPLETLK1007: RTMP packet shows range network_range, which is in the startup range. Ignoring RTMP packet.APPLETLKExplanation: A remote network is configured with a network range within the startup range. The network numbers 65280 through 65534 are reserved as a default startup range for nodes that boot up on the network when no router is available.Action: Use ATCON to locate the misconfigured network. Bring down the misconfigured router, correct the router's network range, and bring up the router with its new configuration. For information on ATCON, see "BOOK="utlrfenu" COLLECTION="nw41"ATCON" in Utilities Reference.1009: Datalink initialization failed (error_code). An error occurred while binding AppleTalk to the LAN driver.APPLETLKExplanation: AppleTalk does not support the network media. This message may be due to a failure to obtain a node ID on the network.Action: Verify that the LAN driver is certified and that the server or router has enough available memory. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A.1013: Mismatched range numbers: local=network_range; network reported on port port_numberAPPLETLKAction: An inconsistency in the network range is found among routers connected to the network segment associated with the specified port.Explanation: Check the router configurations in all routers connected to the network segment. Bring down the inconsistent router, correct the configuration, and bring up the router with its new configuration.1014: Mismatched net numbers: local=network; network reported on port port_numberAPPLETLKExplanation: An inconsistency in the network number is found among routers connected to the cable associated with the specified port. Action: Check the router configurations in all routers connected to the cable indicated by the port number. Bring down the inconsistent router, correct the configuration, and bring up the router with its new configuration. PAGENUM=43 ID="BP37"1019: No memory when entering range network_range.APPLETLKExplanation: The router could not create an entry for the specified network range in its routing (RTMP) table. If the problem persists, the router will not be able to forward packets to nodes on the indicated networks.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.1020: Unable to allocate ECB to send periodic RTMP updates.APPLETLKExplanation: AppleTalk was unable to send periodic routing information. If this situation persists for more than 30 seconds, routes will start to age out and the AppleTalk internetwork can become disjointed. Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.1021: Range network_range found, but there are Phase 1 routers present.APPLETLKExplanation: Transition routing is on and Phase 1 routers are on the internetwork. Transition routing limits all extended networks to be configured with a network range of 1. If a network is configured with a range greater than 1, Phase 1 routers will not be able to reach that network.Action: To ensure full connectivity on the AppleTalk internetwork, configure all networks with a range of 1.1022: Unable to allocate ECB to send RTMP request to verify seed information.APPLETLKExplanation: AppleTalk will continue to load, but configuration will not be verified with the actual information running on the network.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.1023: Configured net for port port_number conflicts with router at address node_address.APPLETLKExplanation: This router is a seed router for this network, and the configured network number conflicts with information advertised by a router on the same network.Action: Configure all seed routers attached to this cable with the same network number.1030: No memory when entering an alternate route for range network_range.APPLETLKExplanation: AppleTalk could not allocate the memory necessary to add a route to the specified network range. AppleTalk already has a route for the network range, but the alternate route will not be available.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.PAGENUM=44 ID="BP38"1071: Error opening zone file `filename', error error_code.APPLETLKExplanation: AppleTalk could not read in the zone information. This usually occurs because the zone file is opened by a text editor.Action: Exit the editor and reinitialize the server or router. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A.1072: Not enough memory to read zone file entries.APPLETLKExplanation: AppleTalk could not read in all the zone configuration due to lack of memory. The AppleTalk LOAD command failed.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.1073: Failed to close zone file.APPLETLKExplanation: AppleTalk could not close the zone file after reading in all the zone configuration. The AppleTalk LOAD command failed.Action: Reinitialize the server or router to reload AppleTalk. If the situation persists, load INETCFG and reconfigure all zone lists in the AppleTalk protocol and bind configuration. For information on INETCFG, see "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference.1077: `*' is not allowed as a valid zone name.APPLETLKExplanation: The asterisk (*) is a wildcard character; therefore, it cannot be used as a zone name.Action: Load INETCFG and modify the zone name in the protocol or bind configuration. INETCFG will prevent you from configuring an invalid zone name. For information on INETCFG, see "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference.1083: Cannot detect any AppleTalk router on local net. Last known AppleTalk router was at address node_address.APPLETLKExplanation: There are no known routers on the network at this time. The address of the last know router is displayed.Action: If this situation persists, make sure the router is functioning properly. If the router is functioning properly, there may be a hardware problem in receiving packets from the router.1103: Insufficient memory. Unable to create AARP process.APPLETLKExplanation: The server or router is out of memory, so the AppleTalk Address Resolution Protocol process could not be created.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.PAGENUM=45 ID="BP39"1104: Insufficient system resource. Unable to create AARP process.APPLETLKExplanation: The AppleTalk Address Resolution Protocol process could not be created, due to a lack of system resources (memory).Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.1107: Duplicate Hardware Address:  hardware_address.APPLETLKExplanation: A duplicate hardware address is detected by the AppleTalk Address Resolution Protocol. The second through the sixth bytes of the address are displayed in hexadecimal format. The first byte of the address is not displayed. AppleTalk communication will not be reliable if two nodes on the same network have the same hardware address.Action: Modify the hardware address in one of the nodes. 1121: NBP registration failed for service_name because the name is too long.APPLETLKExplanation: The indicated service will not be accessible.Action: Shorten the name of the indicated service.1122: Unable to allocate ECB for sending NBP reply.APPLETLKExplanation: AppleTalk could not respond to an NBP request. If the problem persists, local services may become inaccessible to clients on the network.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.1123: Unable to allocate ECB for sending NBP Forward Requests generated by a NBP Broadcast Request.APPLETLKExplanation: AppleTalk is unable to forward an NBP request. If the problem persists, services may become inaccessible on the network.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.1132: Error binding APPLETALK to board board_number (error_code).APPLETLKExplanation: The BIND command failed.Action: Make sure that the board is firmly seated in its slot, that the connectors are secure, and that the board is certified to work with NetWare. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A.PAGENUM=46 ID="BP40"1133: Unbind of APPLETALK from board board_number failed (error_code).APPLETLKExplanation: AppleTalk could not unbind from the indicated board. An internal error occurred when you attempted to unbind AppleTalk from a board or unloaded the AppleTalk module. (Unloading the AppleTalk module automatically unbinds the module.)Action: For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A.1134: Unbind of AARP from board board_number failed (error_code).APPLETLKExplanation: AppleTalk was unable to unbind AARP from the indicated board. The error code is an operating system error code.Action: For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A.1135: Error binding APPLETALK to board board_number due to lack of multicast support. LAN Driver multicast support is required for APPLETALK extended networks.APPLETLKExplanation: The driver for the indicated board does not provide multicasting. AppleTalk requires multicast support on LANs. The bind failed.Action: Verify that the LAN driver is certified and that the correct frame type is loaded.1153: Datalink initialization failed (error_code) for port port_number.APPLETLKExplanation: An error occurred while binding AppleTalk to the LAN driver. AppleTalk does not support the network media. This message may be due to a failure to obtain a node ID on the network.Action: Verify that the LAN driver is certified and that the server or router has enough available memory. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A.1154: Failed to configure stack. Error [error_code].APPLETLKExplanation: AppleTalk could not initialize the stack. AppleTalk routing will continue to function if routing is enabled. AppleTalk services such as AppleTalk File Services [using AppleTalk Filing Protocol (AFP)] and AppleTalk Print Service will not function.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A.PAGENUM=47 ID="BP41"1159: Conflicting information: local range=network_range; network_range reported on port port_number.APPLETLKExplanation: All routers directly connected to a network must have consistent network and zone information. An inconsistency in the network range has been found among the routers connected to the network segment associated with the specified port number.Action: Review the configuration of all seed routers on the network segment. Modify the network range on the misconfigured router and reboot the router with its new configuration.1160: Conflicting information: local net=network_number; network_number reported on port port_number.APPLETLKExplanation: All routers directly connected to a network must have consistent network and zone information. An inconsistent network number has been found among the routers connected to the network segment associated with the port number.Action: Review the configuration of all seed routers on the network segment. Modify the network number on the misconfigured router and bring up the router with its new configuration.1161: Conflicting information: local default zone = zone_name; zone_name reported on port port_number.APPLETLKExplanation: All routers connected to a network must have consistent network and zone information. An inconsistent default zone exists among the routers connected to the network segment associated with the port number.Action: Review the configuration of all seed routers on the network segment. Modify the network number on the misconfigured router and bring up the router with its new configuration.1162: Transition-router option is ON, and there is more than one zone name for net network_number.APPLETLKExplanation: AppleTalk is configured for transition routing. To allow AppleTalk Phase 2 routers to operate with AppleTalk Phase 1 routers, transition routing imposes limits extended networks to be in a single zone. More than one zone is detected on the extended network.Action: Check the RTMP table in ATCON to locate the misconfigured network. Bring down the router advertising the wrong or multiple zone names, correct the configuration, and bring up the router. For information on ATCON, see "BOOK="utlrfenu" COLLECTION="nw41"ATCON" in Utilities Reference.PAGENUM=48 ID="BP42"1164: ZIP bringup found invalid character in zone name.APPLETLKExplanation: Another router has sent a ZIP packet with an illegal character in the zone name.Action: Review the configuration of the routers on the network. Modify the zone name on the misconfigured router and reboot the router with the corrected configuration.1166: Configured net range for port port_number conflicts with router at address node_address.APPLETLKExplanation: The BIND command failed. The configured network range conflicts with information advertised by the router. Action: Review the configuration of both routers. Modify the network range in the misconfigured router and reinitialize that router.1167: Configured default zone for port port_number conflicts with router at address node_address.APPLETLKExplanation: The zone specified by the MYZONE parameter on the BIND command line is not a valid zone for the network that the AppleTalk stack is attempting to home on. The default zone for this network will be used as the home zone.Action: None is required. However, you should load INETCFG and correct the zone specified in the AppleTalk bind configuration for this network. If INETCFG is not used to configure the server or router, correct the MYZONE parameter in the BIND command. For information on INETCFG, see "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference.1168: Transition routing option is ON, but the port port_number net network_range has more than one zone.APPLETLKExplanation: AppleTalk is configured for transition routing. To allow AppleTalk Phase 2 routers to operate with AppleTalk Phase 1 routers, transition routing imposes limits configuring extended networks to a single zone. More than one zone is detected on the extended network.Action: Check the router configurations in all routers connected to the network. Bring down the router advertising the incorrect zone, correct the configuration, and bring up the router.1181: Memory allocation failed. SNMP support disabled.APPLETLKExplanation: No AppleTalk MIB support through SNMP will be provided.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.PAGENUM=49 ID="BP43"1182: Failed to register with agent. SNMP support disabled.APPLETLKExplanation: Registration with SNMP failed, and AppleTalk network management information is not available through SNMP. AppleTalk will still be initialized if there are no further errors. This is most likely caused by a memory shortage or a version mismatch. Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.1186: AppleTalk did not start up correctly.APPLETLKExplanation: APPLETLK.NLM could not load. This message normally follows another message indicating a specific error.Action: Correct the problem indicated in the accompanying message and reinitialize the server or router.1187: Insufficient memory. Unable to initialize Router process.APPLETLKExplanation: The server or router does not have enough available memory for AppleTalk to initialize. APPLETLK.NLM did not load.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.1188: Insufficient system resource. Unable to create AppleTalk process.APPLETLKExplanation: The server or router does not have enough available memory for AppleTalk to initialize. APPLETLK.NLM did not load.Action:  See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.1189: Option internal_net is no longer supported and is replaced by the new option internal_net_mode.APPLETLKExplanation: An obsolete keyword has been used on the command line to load APPLETLK.NLM.Action: Use INETCFG to configure the server or router. For information on INETCFG, see "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference. If INETCFG is not used, update the LOAD APPLETLK command line used to load AppleTalk.1190: Cannot resolve external symbol `symbol'.APPLETLKPAGENUM=50 ID="BP44"Explanation: AppleTalk could not find the specified symbol in the NetWare® 4.1 SFT IIITM operating system, and AppleTalk could not load. AppleTalk should only try to access this symbol when loading on an SFT III server. The symbol should then be available to it. The version of the operating system is probably incompatible with the version of AppleTalk that you are loading.Action: Record the version numbers of the NetWare® 4.1 SFT IIITM operating system and the APPLETLK.NLM that you are trying to load, and contact your Novell Authorized Reseller.1192: AppleTalk does not allow for routing enabled in SFT3 MSEngine.APPLETLKExplanation: AppleTalk could not load in the NetWare® 4.1 SFT IIITM MSEngine with routing enabled. In SFT III, AppleTalk is loaded in the MSEngine as well as the IOEngines of both the primary and secondary servers. AppleTalk must be configured as an end node in the MSEngine, and as a router in the IOEngines.Action: Use INETCFG to configure the SFT III system. INETCFG should always cause AppleTalk to be loaded with routing disabled in the MSEngine. (The load line should not contain the parameter "routing=yes".) For information on INETCFG, see "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference.1202: Cannot bind to more than one board when routing is disabled.APPLETLKExplanation: AppleTalk can be bound to only one network interface when it is configured as an end-node, that is, when Packet Forwarding is disabled in INETCFG. The Packet Forwarding option in the AppleTalk protocol configuration determines whether AppleTalk will act as a router or as an end-node. Action: Use INETCFG to configure AppleTalk and bind it to the required board. INETCFG permits only one bind when Packet Forwarding is disabled. Packet Forwarding must be enabled to bind AppleTalk to more than one board. For information on INETCFG, see "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference.1203: AppleTalk already bound to board number board_number.APPLETLKExplanation: AppleTalk has already been bound to the board specified in the BIND command.Action: Use INETCFG to configure the server or router. INETCFG will not allow redundant BIND commands. For information on INETCFG, see "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference. If INETCFG is not used, remove the redundancy by modifying the AppleTalk BIND commands (usually in the SYS:\SYSTEM\AUTOEXEC.NCF file).1204: Memory allocation failed. Unable to initialize board board_number interface.APPLETLKExplanation: AppleTalk was not able to bind to the indicated board.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.PAGENUM=51 ID="BP45"1205: Too many zones (number) supplied with ZONE parameter.APPLETLKExplanation: More than one zone was specified for a nonextended network, or more than 255 for an extended network.Action: If INETCFG is used to configure the server or router, load INETCFG, remove the excess zones, and reinitialize the server or router. For information on INETCFG, see "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference. If INETCFG is not used to configure the server or router, remove the excess zones by modifying the AppleTalk load and bind lines to remove; then bring down the server and bring it back up.1207: Cannot specify more than one zone as home zone.APPLETLKExplanation: More than one zone name is specified for the MYZONE parameter on the bind line. Only one zone name is allowed for the MYZONE parameter.Action: Remove the excess zones using INETCFG. INETCFG will not allow you to specify more than one home zone. For information on INETCFG, see "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference. If INETCFG is not used, remove the excess zones by modifying the AppleTalk bind lines; then bring down the server and bring it back up.1208: No entry found in zone file for net range network_range.APPLETLKExplanation: AppleTalk was instructed to look up zone lists for the specified network or network range; however, no entries were in the ATZONES.CFG file.Action: If the load failed, add zones to the Zone list in the AppleTalk protocol configuration using INETCFG. If the bind failed, add zones to the AppleTalk bind configuration using INETCFG. For information on INETCFG, see "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference. If INETCFG is not used, include the necessary zones by modifying the ATZONES.CFG file; then bring down the server and bring it back up.1210: Too many zones (number_of_zones) found in entry in zone file.APPLETLKExplanation: The zone file entry for an interface exceeds the maximum value of 255 allowed on an extended network or the maximum value of 1 allowed on a nonextended network.Action: Remove the excess zones from the zone list in the AppleTalk bind configuration using INETCFG. For information on INETCFG, see "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference. If INETCFG is not used to configure the server or router, remove the excess zones by modifying the ATZONES.CFG file.PAGENUM=52 ID="BP46"1211: NET or ZONE parameters are not allowed when routing is disabled.APPLETLKExplanation: AppleTalk is configured as an end-node. End-nodes get the network and zone information from routers on the directly attached network and cannot be configured with the zone or network information.Action: Load INETCFG and review the AppleTalk bind configuration. INETCFG will identify the location of the error. For information on INETCFG, see "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference. If INETCFG is not used to configure the server or router, remove the NET and ZONE parameters from the BIND command. 1212: Cannot provide zone list if net number of 0 is given.APPLETLKExplanation: The AppleTalk BIND command failed. A network number of 0 was set on the bind line, indicating the router is not the seed router for this network. The zone list can only be specified for the seed router.Action: Load INETCFG and review the AppleTalk bind configuration. INETCFG will identify the location of the error. For information on INETCFG, see "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference. If INETCFG is not used to configure the server or router, remove the ZONE parameter from the BIND command.1214: Chosen zone "name" invalid, changing to "name".APPLETLKExplanation: The zone specified by the MYZONE parameter on the BIND command line is not a valid zone for the network the AppleTalk stack is attempting to home on. The default zone for this network will be used as the home zone.Action: None is required. However, you should load INETCFG and correct the zone specified in the AppleTalk bind configuration for this network. For information on INETCFG, see "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference. If INETCFG is not used to configure the server or router, correct the MYZONE parameter in the BIND command.1216: Unable to bind stack to port port_name.APPLETLKExplanation: The AppleTalk BIND command failed. This message normally follows another message indicating a specific error.Action: Correct the problem indicated in the accompanying message and reinitialize the server or router.1217: Datalink initialization failed (error_code).APPLETLKExplanation: AppleTalk does not support the network media. This message may be due to a failure to obtain a node ID on the network.Action: Verify that the LAN driver is certified and that the server or router has enough memory. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A.PAGENUM=53 ID="BP47"1218: Memory allocation failed. Unable to initialize port port_number.APPLETLKExplanation: The AppleTalk BIND command failed. The server or router did not have enough available memory to complete the bind processing.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.1220: Datalink initialization failed (error_code).APPLETLKExplanation: AppleTalk may not support the network media. This message may indicate a failure to obtain a node ID on the network.Action: Verify that the LAN driver is certified and that the server or router has enough available memory. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A.1221: Not enough buffers for port port_number RTMP entry!APPLETLKExplanation: AppleTalk could not allocate the memory required to build a routing table entry for this network. The BIND command failed.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.1223: Error unbinding from datalink error_code.APPLETLKExplanation: The UNBIND command failed. This error usually indicates that AppleTalk was not bound to the board.Action: Load ATCON or use the CONFIG command to review the AppleTalk bindings. Correct the name of the board used in the UNBIND command. If the error persists, reboot the server. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. For information on ATCON, see "BOOK="utlrfenu" COLLECTION="nw41"ATCON" in Utilities Reference. For information on CONFIG, see "BOOK="utlrfenu" COLLECTION="nw41"CONFIG" in Utilities Reference.1224: Net number network_number configured for board board_number is in the startup range.APPLETLKExplanation: The AppleTalk LOAD or BIND command failed. AppleTalk Phase 2 reserves the network numbers 65280 through 65534 as a default startup range for nodes that boot up on the network when no router is available. The network number specified by the NET parameter in the LOAD or BIND command is within this startup range. Valid network numbers for the NET parameter range from 1 to 65279.Action: Use INETCFG to configure the server or router. INETCFG it will not allow network numbers within the startup range to be configured. For information on INETCFG, see "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference. If INETCFG is not used to configure the server or router, correct the network number specified by the NET parameter in the LOAD APPLETLK or BIND APPLETLK command line, usually found in SYS:SYSTEM\AUTOEXEC.NCF. PAGENUM=54 ID="BP48"1225: Datalink initialization failed (error_code).APPLETLKExplanation: AppleTalk does not support the network media. This message may indicate a failure to obtain a node ID on the network.Action: Verify that the LAN driver is certified and that the server or router has enough available memory. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A.1227: Net range (network_range) configured for board board_number is in the startup range. The AppleTalk load or BIND command failed.APPLETLKExplanation: AppleTalk Phase 2 reserves the network numbers 65280 through 65534 as a default startup range for nodes that boot up on the network when no router is available. The network range specified by the NET parameter in the LOAD or BIND command is within this startup range. Valid network ranges for the NET parameter range from 1 to 65279.Action: Use INETCFG to configure the server or router. INETCFG will not configure network ranges that are within the startup range. For information on INETCFG, see "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference. If INETCFG is not used to configure the server or router, correct the network number specified by the NET parameter in the LOAD APPLETLK or BIND APPLETLK command line, usually found in SYS:SYSTEM\AUTOEXEC.NCF.1228: Range start is greater than range end (network_range).APPLETLKExplanation: The network range specified by the NET parameter in the BIND command has a range start greater than the range end. The range start must be less than or equal to the range end.Action: Load INETCFG and modify the AppleTalk bind configuration for this board. For information on INETCFG, see "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference. If INETCFG is not used to configure the server or router, correct the network range specified by the NET parameter on the BIND command line.1229: Transition routing option is ON, but the range is more than one (network_range).APPLETLKExplanation: AppleTalk is configured for transition routing. To allow AppleTalk Phase 2 routers to operate with AppleTalk Phase 1 routers, transition routing imposes limits on extended networks to have a range of 1. The AppleTalk bind failed because a range greater than 1 was specified.Action: Load INETCFG and modify the AppleTalk bind configuration for this board to use a network range of 1. For information on INETCFG, see "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference. If INETCFG is not used to configure the server or router, correct the network range specified by the NET parameter on the BIND command line.PAGENUM=55 ID="BP49"1230: Transition routing option is ON, but there is more than one zone name.APPLETLKExplanation: AppleTalk is configured for transition routing. To allow AppleTalk Phase 2 routers to operate with AppleTalk Phase 1 routers, transition routing imposes limits on extended networks to have a single zone. The AppleTalk bind failed because more than one zone was specified.Action: Load INETCFG and modify the AppleTalk bind configuration for this board to use a single zone. For information on INETCFG, see "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference. If INETCFG is not used to configure the server or router, correct the ZONE parameter on the BIND command line to specify only one zone.1234: Memory allocation failed. Unable to initialize zone list.APPLETLKExplanation: AppleTalk could not allocate the required memory to complete the initialization of the zone list for this network interface. The bind failed.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.1235: Zone names are limited to a maximum of number characters.APPLETLKExplanation: The zone name supplied for the ZONE parameter on the AppleTalk load or bind line exceeds the maximum zone name length of 32 characters.Action: Use INETCFG to configure the server or router. INETCFG will not configure invalid zone names. For information on INETCFG, see "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference. If INETCFG is not used to configure the server or router, modify the zone name by using the ZONE parameter on the failing command line. 1236: Zone names must have at least one character. APPLETLKExplanation: A null zone name was supplied for the ZONE or MYZONE parameter on the AppleTalk load or bind line.Action: Use INETCFG to configure the server or router. INETCFG prevents invalid zones names from being configured. For information on INETCFG, see "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference. If INETCFG is not used to configure the server or router, modify the zone name specified on the failing command line. 1237: Net network_number conflicts with previously configured net network_rangeAPPLETLKExplanation: The network number specified for this bind conflicts with a network number already in use or falls within the range of a network range already in use. Action: Load ATCON to see the network numbers in use. Load INETCFG to review the AppleTalk bind configuration and correct the conflicting network number; then reinitialize the server or router. For information on INETCFG, see "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference. If INETCFG is not used to configure the server or router, correct the NET parameter on the BIND command line. For information on ATCON, see "BOOK="utlrfenu" COLLECTION="nw41"ATCON" in Utilities Reference.PAGENUM=56 ID="BP50"1238: Net range network_range conflicts with previously configured net network_range.APPLETLKExplanation: The network range specified for this bind duplicates or overlaps a network range already in use. Action: Load ATCON to view the network ranges in use. For information on ATCON, see "BOOK="utlrfenu" COLLECTION="nw41"ATCON" in Utilities Reference. Load INETCFG to review the AppleTalk bind configuration and correct the conflicting network number and reinitialize the server or router. For information on INETCFG, see "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference. If INETCFG is not used to configure the server or router, correct the NET parameter on the BIND command line.1244: Instruction to home the stack on more than one interface ignored.APPLETLKExplanation: The HOME_HERE parameter was set to "Yes" on more than one BIND command. AppleTalk may have a home stack on only one network interface.Action: Load INETCFG and modify the AppleTalk bind configuration to specify homing on only one bind. For information on INETCFG, see "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference. If INETCFG is not used to configure the server or router, remove the HOME_HERE parameter from one of the BIND commands.1251: Inconsistent zone name. AppleTalk will use the same zone name for the SFT3 network as configured on the SFT3 primary machine.APPLETLKExplanation: AppleTalk was configured with different zone names for the NetWare® 4.1 SFT IIITM network in the two SFT III IOEngines. AppleTalk should be configured with the same SFT III network number and zone in both IOEngines. AppleTalk will ignore the zone name configured in the secondary IOEngine. It will use the SFT III network zone name configured in the primary IOEngine.Action: If the NetWare® 4.1 SFT IIITM network zone name configured in the primary IOEngine is correct, no action is required. Otherwise, use INETCFG to reconfigure the zone name, then reinitialize the server or router in both IOEngines. For information on INETCFG, see "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference. Even if no current action is required, you should use INETCFG to reconfigure the two IOEngines.1252: Inconsistent network number. AppleTalk will use the same network number for the SFT3 network as configured on the SFT3 primary machine.APPLETLKExplanation: AppleTalk was configured with different network numbers for the NetWare® 4.1 SFT IIITM network in the two SFT III IOEngines. AppleTalk should be configured with the same SFT III network number and zone name in both IOEngines. AppleTalk will ignore the network number configured in the secondary IOEngine. It will use the SFT III network number configured in the primary IOEngine.PAGENUM=57 ID="BP51"Action: If the NetWare® 4.1 SFT IIITM network number configured in the primary IOEngine is correct, no action is required. Otherwise use INETCFG to reconfigure the SFT III network number, then reinitialize the server or router in both IOEngines. For information on INETCFG, see "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference. Even if no current action is required, you should use INETCFG to reconfigure the two IOEngines.1253: Zone list verification failed.APPLETLKExplanation: The list of configured zones for this network interface conflicts with the zones learned from other routers on the network.Action: Load INETCFG to correct the zone information in the AppleTalk bind configuration. For information on INETCFG, see "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference. If INETCFG is not used to configure the server or router, correct the zone list in the failing BIND command.1255: Configured zone list for port port_number conflicts with router at address node_address.APPLETLKExplanation: The configured zone list for this network interface conflicts with the zone information learned from the router at the displayed address.Action: Determine the correct zone list for the network and update the zone information in the misconfigured router. 1256: `*' is not allowed as a configured zone name.APPLETLKExplanation: An invalid zone name was configured.Action: Load INETCFG and correct the misconfigured zone name in the AppleTalk protocol or bind configuration. For information on INETCFG, see "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference. If INETCFG is not used to correct the misconfigured zone name, update the ZONE or MYZONE parameter in the failing command. 1257: Zone verification failed.APPLETLKExplanation: AppleTalk could not allocate an ECB to send a ZIP query to verify the configured zone information.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.1258: Zone verification failed.APPLETLKExplanation: AppleTalk could not allocate the necessary memory to verify the configured zone information.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.PAGENUM=58 ID="BP52"1259: Configured zone for port port_number conflicts with router at address node_address.APPLETLKExplanation: The configured zone for this network interface conflicts with the zone information learned from the router at the displayed address.Action: Determine the correct zone for the network and update the zone information in the misconfigured router. 1260: Net range is expected.APPLETLKExplanation: The attempt to bind AppleTalk to an extended network failed. An extended network requires a network range, but only a single network number was specified.Action: Load INETCFG and review the AppleTalk bind configuration for this board. INETCFG makes sure that a network range is configured for an extended network. For information on INETCFG, see "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference. If INETCFG is not used, correct the NET parameter on the BIND command line to specify a network range. A network range of 1 is valid (for example, 5 to 5).1262: Net range of 1 is sufficient for the internal or SFT3 virtual net, net range is set to network_range.APPLETLKExplanation: AppleTalk was bound to the internal or virtual NetWare® 4.1 SFT IIITM network with a net range greater than 1. This is not necessary for the SFT III network, and only the range start number was used.Action: If the network number range that AppleTalk has set for the NetWare® 4.1 SFT IIITM network is correct, no action is required. Otherwise use INETCFG to correctly configure the SFT III network number; then reinitialize the server or router in both IOEngines. For information on INETCFG, see "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference. Even if no current action is required, you should use INETCFG to configure the NetWare SFT III network number correctly.1263: Incomplete network range or invalid network number.APPLETLKExplanation: The value specified for the network number on a nonextended network or the network range on an extended network is invalid.Action: Load INETCFG and review the AppleTalk bind configuration. INETCFG makes sure that valid entries are supplied for the network number or range. For information on INETCFG, see "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference. If INETCFG is not used, correct the error in the NET parameter of the BIND command line.PAGENUM=59 ID="BP53"1265: Net range is not allowed for Non extended net, network is set to the first number in the range.APPLETLKExplanation: AppleTalk is being bound to a nonextended network, but a network range was specified. A nonextended network can only accept a single network number.Action: None is required. AppleTalk will use the start of the network range as the network number. Even though no action is required, you should use INETCFG to correct the error in the AppleTalk bind configuration.1400: AppleTalk supports a maximum of maximum_interface external interfaces. (not including the internal net)APPLETLKExplanation: The AppleTalk bind failed. AppleTalk is already bound to the maximum number of network interfaces that it supports.Action: Load INETCFG and remove unneeded AppleTalk binds. 1404: Unknown frame type.APPLETLKExplanation: The AppleTalk BIND command failed. AppleTalk does not support the frame type loaded for this board.Action: Load INETCFG and review the AppleTalk bind configuration. INETCFG makes sure that AppleTalk is bound to the board with the appropriate frame type loaded.1407: RTMP Update Timer can only be used when binding AppleTalk to a WAN port.APPLETLKExplanation: The RTMP Update Timer parameter is not valid when binding AppleTalk to a network board. The BIND command failed.Action: Use INETCFG to configure the server or router. INETCFG makes sure that the LOAD and BIND command lines are valid for the server or router.1407: The keyword Negotiation only be used when binding AppleTalk to a WAN port.APPLETLKExplanation: The Negotiation keyword is not valid when binding AppleTalk to a network board. The BIND command failed.Action: Use INETCFG to configure the server or router. INETCFG makes sure that LOAD and BIND command lines are valid for the server or router.PAGENUM=60 ID="BP54"1407: WAN Call Destination can only be used when binding AppleTalk to a WAN port.APPLETLKExplanation: The WAN Call Destination parameter is not valid when binding AppleTalk to a network board. The BIND command failed.Action: Use INETCFG to configure the server or router. INETCFG make sure that LOAD and BIND command lines are valid for the server or router. For information on INETCFG, see "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference.1409: Invalid keyword used when unbinding AppleTalk from LAN boards. Keyword can only be used when unbinding AppleTalk from WAN boards.APPLETLKExplanation: Keywords are not supported on UNBIND command lines that unbind AppleTalk from network boards. The UNBIND command failed.Action: Remove the keyword from the command line and reenter the UNBIND command.1410: Unknown keyword parameter. Unbind failed.APPLETLKExplanation: An invalid keyword was specified on the command line. The AppleTalk command line failed.Action: Use INETCFG to configure the server or router. INETCFG makes sure that LOAD and BIND command lines are valid for the server or router. For information on INETCFG, see "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference.1412: CSL Major version mismatch---verify version number. CSL Version: version was expected.APPLETLKExplanation: APPLETLK.NLM and CSLSTUB.NLM or CSL.NLM do not have consistent versions.Action: Contact your Novell Authorized Reseller.1415: WAN mode can only be used when binding AppleTalk to a WAN port.APPLETLKExplanation: The WAN mode parameter is not valid when binding AppleTalk to a network board. The BIND command failed.Action: Use INETCFG to configure the server or router. INETCFG makes sure that LOAD and BIND command lines are valid for the server or router. For information on INETCFG, see "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference.PAGENUM=61 ID="BP55"1465: AppleTalk clients open while stack is unbound.APPLETLKExplanation: The AppleTalk stack has not bound any network interfaces to a client (such as AFP) that is being loaded.Action: None is required, but AppleTalk must be bound to an interface before the client will be able to use the AppleTalk network.1701: Invalid SFT3 configuration, partner's net network_number is number hops away, which exceeds the max hops number allowed.APPLETLKExplanation: The number of hops across the network backbone between the two NetWare® 4.1 SFT IIITM computers is too large.Action: Examine the network backbone configuration, and reconfigure the network or move one of the SFT III computers to make sure the distance between the directly connected networks is within the maximum number of hops allowed.1703: Cannot allocate memory to store SFT3 partner's network information.APPLETLKExplanation: The server could not allocate enough memory for NetWare® 4.1 SFT IIITM system processing. If the current SFT III primary server fails, AppleTalk in the secondary server may not function correctly as the secondary server attempts to become the primary server.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.1705: Cannot allocate memory for SFT3 MSL receive buffer.APPLETLKExplanation: The server could not allocate enough memory for AppleTalk initialization. AppleTalk will not load.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.1706: Cannot allocate memory for SFT3 MSL send buffer.APPLETLKExplanation: The server could not allocate enough memory for AppleTalk initialization. AppleTalk will not load.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.1707: Cannot resolve NetWare symbol `internal_symbol'.APPLETLKPAGENUM=62 ID="BP56"Explanation: AppleTalk could not find the specified symbol in the NetWare® 4.1 SFT IIITM operating system, and AppleTalk could not load. AppleTalk should only try to access the symbol when loading in a SFT III server, and the symbol should then be available to it. The version of the operating system that you are using is probably incompatible with the version of AppleTalk that you are loading.Action: Record the version numbers of the SFT III operating system and the APPLETLK NLM that you are trying to load, and contact your Novell Authorized Reseller.1708: Insufficient memory to schedule the bind to the SFT3 virtual board.APPLETLKExplanation: The server could not allocate enough memory for AppleTalk to bind to the VIRTUAL_BOARD of the NetWare® 4.1 SFT IIITM virtual network. AppleTalk will not be able to route packets to the MSEngine.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.2000: Insufficient memory to allocate structures for service filter. Filter not added.APPLETLKExplanation: The server or router does not have enough available memory to add a service filter to the AppleTalk filter list. The accessibility of services in the network will not correspond to the configuration.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.2001: Insufficient memory for [constructing] route filter. Filter not added.APPLETLKExplanation: The server or router does not have enough available memory to add a service filter to the AppleTalk filter list. The propagation of routing information through the network will not correspond to the configuration.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.2002: Insufficient memory for processing service filter. Filter not added.APPLETLKExplanation: The server or router does not have enough available memory to add a service filter to the AppleTalk filter list. The accessibility of services in the network will not correspond to the configuration.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.2004: Insufficient memory for processing route filter. Filter not added.APPLETLKExplanation: The server or router does not have enough available memory to add a route filter to the AppleTalk filter list. The propagation of routing information through the network will not correspond to the configuration.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.PAGENUM=63 ID="BP57"2005: AppleTalk Filtering is not supported when configured as an end-node. AppleTalk will continue to function as an end-node with no filtering.APPLETLKExplanation: AppleTalk filtering is only supported when the server is configured as an AppleTalk router. The server is configured as an end node and AppleTalk filtering was enabled during configuration or ATFLT.NLM was loaded at the command line.Action: None is required. The server will continue to function as an AppleTalk end node. Use INETCFG to disable AppleTalk filtering or to make the server an AppleTalk router. For information on INETCFG, see "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference.PAGENUM=64 ID="BP58"ATCON2: Loading of ATCON failed due to failure in allocating resource tag.ATCONExplanation: The ATCON.NLM file could not be loaded because a resource tag could not be allocated from the NetWare operating system. This usually means that the server is low on memory. Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.19: Loading of ATCON failed due to failure in initializing with SNMP.ATCONExplanation: ATCON could not establish communication with SNMP. This error usually occurs when the server is low on memory or the SNMP version isn't compatible with the ATCON version.Action: Use NetWare Administrator or MONITOR to determine if the server is low on memory. For information, see "BOOK="utlrfenu" COLLECTION="nw41"NetWare Administrator" in Utilities Reference or "BOOK="utlrfenu" COLLECTION="nw41"MONITOR" in Utilities Reference.MARK=BULLETIf the server is low on memory, see "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.If the server is not low on memory, SNMP and ATCON are probably not compatible versions. Record the version numbers of SNMP.NLM and ATCON.NLM and contact your Novell Authorized Reseller. 20: Loading of ATCON failed due to failure in initializing with TUI. ATCONExplanation: ATCON could not establish communication with the TUI library. This error usually occurs when the server is low on memory or the TUI version isn't compatible with the ATCON version. TUI prints out an additional message explaining the reason for the failure.Action: Use NetWare Administrator or MONITOR to determine if the server is low on memory. For information, see "BOOK="utlrfenu" COLLECTION="nw41"NetWare Administrator" in Utilities Reference or "BOOK="utlrfenu" COLLECTION="nw41"MONITOR" in Utilities Reference.MARK=BULLETIf the server is low on memory, see "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.If the server is not low on memory, TUI and ATCON are probably not compatible versions. Record the version numbers of TUI.NLM and ATCON.NLM and contact your Novell Authorized Reseller.PAGENUM=65 ID="BP59"ATOTAL005: A record cannot be read from the log file.ATOTALExplanation: This file I/O error could be caused by a variety of reasons.Action: See ATOTAL message IDREF="FM23091" "010: The Accounting data file is corrupted." .ID="FM23091"010: The Accounting data file is corrupted.ATOTALExplanation: The length specified in the header for the NET$ACCT.DAT file does not match the length of the file itself (must be in range of 4 to 200 bytes). This file I/O error could have a variety of causes:MARK=BULLETA hardware problem may have occurred.The workstation may be out of memory.The File Allocation Table (FAT) may be corrupted.The NET$ACCT.DAT file may have been overwritten or otherwise corrupted.Action: Try the following:MARK=BULLETCheck the disk drive, CPU, cabling, and other hardware. See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.If the workstation is out of memory, increase the available memory. See "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network.Restart the program without rebooting. If the error recurs, reboot the workstation then restart the program.If the error recurs, turn off accounting and delete the corrupted NET$ACCT.DAT file; then turn accounting back on. For information on accounting, see "BOOK="superenu" COLLECTION="nw41"Maintaining the NetWare Server" in Supervising the Network.If the problem persists, contact your Novell Authorized Reseller.903: The command line syntax is invalid.ATOTALAction: See message IDREF="FM18860""903: The command line syntax is invalid." in Appendix C.PAGENUM=66 ID="BP60"905: This utility was unable to initialize the country information.ATOTALAction: See message IDREF="FM55337""905: This utility was unable to initialize the country information." in Appendix C.912: The specified file cannot be found.ATOTALAction: See message IDREF="FM74299""912: The specified file cannot be found." in Appendix C.917: This utility was unable to set the context.ATOTALAction: See message IDREF="FM32126""917: This utility was unable to set the context." in Appendix C.920: This utility was unable to allocate <number> bytes of memory.ATOTALAction: See message IDREF="FM30331""920: This utility was unable to allocate number bytes of memory." in Appendix C.925: This utility is not supported on Personal NetWare. Use the Personal NetWare utilities.ATOTALAction: Use the equivalent Personal NetWare utility.970: The attempt to open the Unicode table files failed.ATOTALAction: See message IDREF="FM15675""970: The attempt to open the Unicode table files failed." in Appendix C.971: The workstation does not have enough memory to load the Unicode table files.ATOTALAction: See message IDREF="FM55341""971: The workstation does not have enough memory to load the Unicode table files." in Appendix C.972: Access to the Unicode table files was denied.ATOTALAction: See message IDREF="FM90152""972: Access to the Unicode table files was denied." in Appendix C.973: The Unicode table files cannot be found in the NLS directory or in the search path. Code page: <number>  Country:  <number>ATOTALAction: See message IDREF="FM62778""973: The Unicode table files cannot be found in the NLS directory or in the search path. Code page: number Country: number" in Appendix C.974: The Unicode table files are corrupt.ATOTALAction: See message IDREF="FM63405""974: The Unicode table files are corrupt." in Appendix C.PAGENUM=67 ID="BP61"975: The Unicode table files cannot be opened because there are already too many open files. Close some files or modify your CONFIG.SYS file.ATOTALAction: See message IDREF="FM49793""975: The Unicode table files cannot be opened because there are already too many open files. Close some files or modify your CONFIG.SYS file." in Appendix C.PAGENUM=68 ID="BP62"ATPSID="FM20711"18: No files that match filename were found.ATPSExplanation: ATPS could not locate the configuration file in the appropriate directory. The filename includes the name and path of the configuration file. This warning message may indicate that the spoolers or printer servers are not configured.Action: Configure the appropriate ATPS components. For information, see "
BOOK="nwmfpenu" COLLECTION="nw41"NetWare for Macintosh File and Print Services."19: Can't create spooler specified in configuration file filename.ATPSExplanation: ATPS could not use a spooler configuration. This error may be a memory problem or file syntax error. The filename is the name of the configuration file.Action: Increase the available memory. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. If the server does not have enough available memory, disable and reenable the spooler.23: No files that match filename were found.ATPSAction: For an Action and Explanation, see the messageIDREF="FM20711" "18: No files that match filename were found." in this section.24: Can't create printer server specified in configuration file filename.ATPSExplanation: ATPS could not use the current printer server configuration. This error may stem from a memory problem or file syntax error. The filename is the name of the configuration file.Action: Increase the available memory. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. If the server does not have enough available memory, delete the queue and re-create it.30: Legal parameters include these: -v, -s, -n, -b, -d.ATPSExplanation: You specified invalid command-line parameters. The message lists valid parameters.Action: Specify valid parameters when loading ATPS. For information, see 
BOOK="nwmfpenu" COLLECTION="nw41"NetWare for Macintosh File and Print Services.PAGENUM=69 ID="BP63"42: Restore the hidden printers? (0=None, 1=All, 2=Some)ATPSExplanation: This message enables previously hidden printers to be restored.Action: Restore printers that Macintosh users should have access to. Specify 0 for no printers, 1 to restore all printers, or 2 to restore some printers. If 2 is specified, a prompt for each hidden printer will be displayed.44: Connection with printer was lost.ATPSExplanation: The hidden printer could not be restored at unload time because of connection problems.Action: Turn the printer off and on to restore it.45: Printer was busy or offline.ATPSExplanation: The hidden printer could not be restored at unload time because it is in use or offline.Action: Turn the printer off and on to restore it.53: Couldn't send ProcSet query file filename.ATPSExplanation: ATPS could not send the contents of the ProcSet file to the printer. The file may be in use or missing.Action: If the file does not exist, print to the queue again using the appropriate Laser Prep file. If the file exists, use the "File Open/Lock Activity" option in the MONITOR utility to determine if the file is being used. For information on MONITOR, see "BOOK="utlrfenu" COLLECTION="nw41"MONITOR" in Utilities Reference.54: Spooling is currently in progress! Jobs currently being received will be lost.ATPSExplanation: The ATPS spooler is currently receiving jobs from AppleTalk clients while you are trying to unload ATPS.Action: If unloading ATPS and interrupt printing is not desired, respond with "No." Try unloading ATPS later, perhaps after disabling spoolers and printer servers to stop processing of new jobs.110: Couldn't log message.ATPSExplanation: ATPS could not write an entry to the printer log. Action: Make sure the log is not currently being viewed from ATPSCON. For information on ATPSCON, see 
BOOK="nwmfpenu" COLLECTION="nw41"NetWare for Macintosh File and Print Services. Make sure the volume has enough free disk space to handle updates to the printer log. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Disk Space Problems" in Supervising the NetworkPAGENUM=70 ID="BP64". If there is enough space, use the "File Open/Lock Activity" option in the MONITOR utility to determine if the file is being used. For information on MONITOR, see "BOOK="utlrfenu" COLLECTION="nw41"MONITOR" in Utilities Reference.112: Could not initialize queue name.ATPSExplanation: ATPS could not initialize the queue specified. Action: Reselect the queue in ATPSCON. For information on ATPSCON, see "
BOOK="nwmfpenu" COLLECTION="nw41"NetWare for Macintosh File and Print Services.114: Unable to charge user name.ATPSExplanation: ATPS could not charge the user for printing the job. The owner's User object may have been deleted, or the User object may reside in a portion of the Directory tree currently unavailable to ATPS. Action: Make sure the User object exists. If it does, increase the available disk space on the volume. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Disk Space Problems" in Supervising the Network. Make sure the resource file exists. See the appropriate documentation to resolve the problem that may be causing parts of the Directory tree to be inaccessible.116: Object_name cannot read username's account balance.ATPSExplanation: ATPS experienced an error while trying to read the user's accounting properties. The object name is the name of the object ATPS is using to obtain rights in NetWare Directory Services. ATPS probably does not have sufficient rights to the User object's accounting properties.Action: Use the NETADMIN utility to grant read and write trusteeship to the server over the accounting properties of the users to be charged.121: Can't open printer configuration filename.ATPSExplanation: ATPS could not open and read the specified configuration file specified.Action: Use the "File Open/Lock Activity" option in the MONITOR utility to determine if the file is being used. For information on MONITOR, see "BOOK="utlrfenu" COLLECTION="nw41"MONITOR" in Utilities Reference.122: Can't open spooler configuration filename.ATPSExplanation: ATPS could not open and read the specified configuration file.Action: Use the "File Open/Lock Activity" option in the MONITOR utility to determine if the file is being used. For information on MONITOR, see "BOOK="utlrfenu" COLLECTION="nw41"MONITOR" in Utilities Reference.PAGENUM=71 ID="BP65"128: Can't service halted queue.ATPSExplanation: The queue status is set so that ATPS cannot access jobs stored in it.Action: Change the queue's status using PCONSOLE.134: Aborted job number.ATPSExplanation: ATPS could not print the job specified. The job was returned to the queue.Action: Examine additional error messages for indications as to how to proceed.142: Problem writing end-of-file to queue.ATPSExplanation: The ATPS spooler could not write a terminating Control-D character at the end of a PostScript job entry.Action: Make sure there is space on the indicated volume. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Disk Space Problems" in Supervising the Network.147: Unable to identify job owner for accounting purposes.ATPSExplanation: ATPS could not identify the print job owner, and it could not charge the owner for printing the job. Action: The owner's User object may have been deleted, or the User object may reside in a portion of the Directory tree currently unavailable to ATPS. Make sure the User object exists. If it does, see "BOOK="superenu" COLLECTION="nw41"Managing NetWare Directory Services Objects" in Supervising the Network for information for resolving the NetWare Directory Services problem that may be causing parts of the Directory tree to be inaccessible.149: Printer connection invalidated.ATPSExplanation: The server's connection with the printer is closed because of a problem with the connection.Action: For information, see the other messages that appear with this message.162: No queue Directory Services context specified in file filename.ATPSExplanation: The configuration file does not contain the NetWare Directory Services context in which the Queue object resides. The configuration was probably created under a version of NetWare for Macintosh prior to 4.1. Action: Use ATPSCON to select the queue for the configuration. For information on ATPSCON, see 
BOOK="nwmfpenu" COLLECTION="nw41"NetWare for Macintosh File and Print Services.PAGENUM=72 ID="BP66"169: Unable to verify that printer name was hidden.ATPSExplanation: After hiding the printer, ATPS could not locate it on the network to confirm its status.Action: Make sure the printer is online. If it is, check the connection between the printer and the network.177: Unable to verify that printer name was restored.ATPSExplanation: After restoring the printer, ATPS could not locate it on the network to confirm its status.Action: Make sure the printer is online. If it is, check the connection between the printer and the network.186: Couldn't create file filename to hold the spooler's font list.ATPSExplanation: ATPS could not open the internal font list file. The file may be in use or missing.Action: If the file exists, use the "File Open/Lock Activity" option in the MONITOR utility to determine if the file is being used. For information on MONITOR, see "BOOK="utlrfenu" COLLECTION="nw41"MONITOR" in Utilities Reference.187: Error using PPD file for the spooler.ATPSExplanation: ATPS could not read PostScript information from the designated PPD file. The file may be in use or missing.Action: For more information, see the messages that preceded this message.190: Requested spooler zone name is no longer valid.ATPSExplanation: The AppleTalk stack has reported that the AppleTalk zone configured to advertise the spooler is no longer valid. The spooler will be registered in the server's default AppleTalk zone.Action: Use ATPSCON to reselect the spooler zone. For information on ATPSCON, see "
BOOK="nwmfpenu" COLLECTION="nw41"NetWare for Macintosh File and Print Services.193: Unable to read information for form name.ATPSExplanation: ATPS experienced an error while reading information for the form from the PRINTDEF database.Action: Make sure the specified form still exists.PAGENUM=73 ID="BP67"196: Unable to read information for header mode device: mode.ATPSExplanation: ATPS encountered an error while reading header mode data from the PRINTDEF.DAT database. The device is the PRINTDEF device name. The mode is the PRINTDEF mode name.Action: Use ATPSCON to reselect the mode. For information on ATPSCON, see 
BOOK="nwmfpenu" COLLECTION="nw41"NetWare for Macintosh File and Print Services.199: Unable to read information for trailer mode device: mode.ATPSExplanation: ATPS encountered an error while reading trailer mode data from the PRINTDEF.DAT database. The device is the PRINTDEF device name. The mode is the PRINTDEF mode name.Action: Use ATPSCON to reselect the mode. For information on ATPSCON, see 
BOOK="nwmfpenu" COLLECTION="nw41"NetWare for Macintosh File and Print Services.201: Problem writing print job's header information to queue.ATPSExplanation: ATPS could not write PRINTDEF header information to the queue containing the print job. There may not be enough disk space.Action: Increase the available disk space on the volume. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.203: Problem writing print job's trailer information to queue.ATPSExplanation: ATPS could not write PRINTDEF trailer information to the queue containing the print job. There may not be enough disk space.Action: Increase the available disk space on the volume. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Disk Space Problems" in Supervising the Network.204: Unknown problem restoring hidden printer.ATPSExplanation: ATPS could not restore the specified hidden printer for undetermined reasons.Action: Turn the printer off and on to restore it.212: Problem writing dictionary file filename to the queue.ATPSExplanation: ATPS could not write the internal PostScript ProcSet resource file to the queue. There may not be enough disk space.Action: Increase the available disk space on the volume. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Disk Space Problems" in Supervising the Network.PAGENUM=74 ID="BP68"213: Problem writing font file filename to the queue.ATPSExplanation: ATPS could not write the internal PostScript font resource file to the queue.Action: Increase the available disk space on the volume. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Disk Space Problems" in Supervising the Network. Make sure the resource file is available.216: Couldn't create file filename to hold the spooler`s font list.ATPSExplanation: ATPS could not create the internal font list file. The file may be in use or missing. There may not be enough disk space.Action: If the file exists, use the "File Open/Lock Activity" option in the MONITOR utility to determine whether the file is being used. For information on MONITOR, see "BOOK="utlrfenu" COLLECTION="nw41"MONITOR" in Utilities Reference. Make sure the volume has enough disk space. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Disk Space Problems" in Supervising the Network.221: No font list source available for this spooler.ATPSExplanation: ATPS could not locate a font list source for the spooler. The spooler will use a null font list.Action: Use ATPSCON to select a PPD file, custom font list file, or printer as the spooler's query source. For information on ATPSCON, see "
BOOK="nwmfpenu" COLLECTION="nw41"NetWare for Macintosh File and Print Services.224, 227, and 231: Serious spooling error for spooler_name.ATPSExplanation: The spooler encountered an internal AppleTalk problem. The spooler name includes the spooler name, type, and zone.Action: Make sure the queue associated with the spooler still exists. If it does, increase the available memory. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.234: Fatal spooler error for spooler_name.ATPSExplanation: The spooler encountered an internal AppleTalk problem and is shutting down. The spooler name includes the spooler name, type, and zone.Action: Increase the available memory. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.236: Total pages: number PostScript Errors: number.ATPSExplanation: The total page number includes copies, but excludes banners. The PostScript Errors number displays the numbers of print errors detected.Action: If there are PostScript errors, check the printer mode.PAGENUM=75 ID="BP69"237: Couldn't store AppleTalk job in queue.ATPSExplanation: ATPS could not store a Macintosh user's job in the queue. The job will be lost.Action: See the preceding message for more specific information on how to proceed.238: Hidden printers do not appear in the Macintosh Chooser for direct printing.ATPSExplanation: Macintosh users cannot see hidden printers in the Chooser and cannot print directly to hidden printers.Action: None. This message is for information only.241: Printer name hardware error: explanation.ATPSExplanation: The specified printer has reported a hardware error. The printer name includes the name, type, and zone of the printer.Action: Check the printer and correct the physical problem.247: Replaced number control characters with spaces.ATPSExplanation: ATPS replaced the indicated number of control characters with spaces.Action: Use ATPSCON to set Accept Binary Data to Yes which turns off the filter. For information on ATPSCON, see 
BOOK="nwmfpenu" COLLECTION="nw41"NetWare for Macintosh File and Print Services. Configure the Macintosh application to omit ASCII PostScript data.249: AppleTalk print client not logged in to server, connection refused.ATPSExplanation: ATPS rejected a print job because the user submitting the job was not logged in to the server and ATPS security is enabled.Action: Make sure the user logs in to the server containing the print queue.251: Couldn't open custom font list file filename.ATPSExplanation: ATPS could not open the custom font list file filename. The file may be in use or missing.Action: Make sure the file is located in the SYS:SYSTEM\NW-MAC\FONTS directory. If the file exists in the proper location, use the "File Open/Lock Activity" option in the MONITOR utility to determine if the file is being used. For information on MONITOR, see "BOOK="utlrfenu" COLLECTION="nw41"MONITOR" in Utilities Reference.PAGENUM=76 ID="BP70"261: Closing AppleTalk connection with printer due to communications error.ATPSExplanation: A network error or a printer problem occurred.Action: Make sure the printer is online. If it is, check the connection between the printer and the network.262: Couldn't create file filename to hold the spooler's font list.ATPSExplanation: ATPS could not create the specified internal font list file. The file may be in use.Action: If the file exists, use the "File Open/Lock Activity" option in the MONITOR utility to determine if the file is being used. For information on MONITOR, see "BOOK="utlrfenu" COLLECTION="nw41"MONITOR" in Utilities Reference. Make sure the volume has enough disk space. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Disk Space Problems" in Supervising the Network.272: Couldn't open PPD file filename.ATPSExplanation: ATPS could not open the specified PostScript Printer Definition (PPD) file.Action: Make sure the file is located in the SYS:SYSTEM\NW-MAC\PPDS directory. If the file exists in the proper location, use the "File Open/Lock Activity" option in the MONITOR utility to determine if the file is being used. For information on MONITOR, see "BOOK="utlrfenu" COLLECTION="nw41"MONITOR" in Utilities Reference.274: Attempt to attach to queue name failed.ATPSExplanation: The ATPS spooler could not initialize the queue. Action: Use ATPSCON to reselect the queue. For information on ATPSCON, see 
BOOK="nwmfpenu" COLLECTION="nw41"NetWare for Macintosh File and Print Services.287: Can't find printer name; still trying.ATPSExplanation: ATPS is still trying to locate the designated printer on the AppleTalk network. The printer name includes the name, type, and zone of the printer.Action: Use ATCON to locate the printer. For information on ATCON, see "BOOK="utlrfenu" COLLECTION="nw41"ATCON" in Utilities Reference. If the printer could not be located, check the cabling connecting the printer to the network. If the connection is secure, make sure the AppleTalk module is configured correctly.300: Error using custom font list file.ATPSExplanation: ATPS could not read the fonts from the custom font list file specified in ATPSCON. The file may be in use or missing.PAGENUM=77 ID="BP71"Action: Make sure the file is located in the SYS:SYSTEM\NW-MAC\FONTS directory. If the file exists in the proper location, use the "File Open/Lock Activity" option in the MONITOR utility to determine if the file is being used. For information on MONITOR, see "BOOK="utlrfenu" COLLECTION="nw41"MONITOR" in Utilities Reference.301: Connection to AppleTalk client timed out.ATPSExplanation: The AppleTalk connection to a print client timed out; ATPS will discard the incomplete job.Action: Check the connection between the network and the Macintosh workstation.309: Couldn't open the ATPS screen.ATPSExplanation: The ATPS console screen could not be activated because of an internal error.Action: Contact your Novell Authorized Reseller.314: Dictionary file filename not present.ATPSExplanation: ATPS could not locate the specified LaserPrep file filename.Action: None. This message is for information only.320: Unable to initialize spooler name.ATPSExplanation: ATPS could not initialize the specified spooler because of an internal AppleTalk error or a system error. Action: See preceding messages for more information.323: Couldn't create file filename to hold the server's font list.ATPSExplanation: ATPS could not open the specified internal font list file. The file may be in use or missing.Action: Make sure the file is located in the SYS:SYSTEM\NW-MAC\FONTS directory. If the file exists in the proper location, use the "File Open/Lock Activity" option in the MONITOR utility to determine if the file is being used. For information on MONITOR, see "BOOK="utlrfenu" COLLECTION="nw41"MONITOR" in Utilities Reference.324: Charging user name number point(s).ATPSExplanation: ATPS charged the user the specified number of points for printing a job.Action: None. This message is for information only.PAGENUM=78 ID="BP72"326: You need number account point(s) to print job_number.ATPSExplanation: The client lacks sufficient accounting points to print the job. The number parameter is the number of accounting points necessary to print the job.Action: Increase the user's accounting points.341: User not a queue user; won't own job.ATPSExplanation: The Macintosh user who submitted the job is logged in to the server but is not a designated Queue User of the queue. The user could not manipulate the job in the queue or receive notification of job completion.Action: Give the user Queue User status.343: Can't find printer name; retrying.ATPSExplanation: ATPS could not locate the configured printer on the AppleTalk network. The printer name includes the printer name, type, and zone.Action: Use ATCON to locate the printer. For information on ATCON, see "BOOK="utlrfenu" COLLECTION="nw41"ATCON" in Utilities Reference. If the printer could not be located, check the cabling connecting the printer to the network. If the connection is secure, make sure the AppleTalk module is configured correctly.350: Insufficient memory for configuration filename.ATPSExplanation: The server does not have enough available memory for ATPS to create the specified configuration file.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.352: No queue specified in file filename.ATPSExplanation: The specified configuration file does not include a valid NetWare print queue name. Action: Use ATPSCON to create the configuration. For information on ATPSCON, see 
BOOK="nwmfpenu" COLLECTION="nw41"NetWare for Macintosh File and Print Services.353: No printer name specified in file filename.ATPSExplanation: The specified configuration file does not contain a valid AppleTalk printer name.Action: Use ATPSCON to create the configuration file. For information on ATPSCON, see 
BOOK="nwmfpenu" COLLECTION="nw41"NetWare for Macintosh File and Print Services.PAGENUM=79 ID="BP73"361: No queue specified in file filename.ATPSExplanation: The specified configuration file does not include a valid NetWare print queue name. Action: Use ATPSCON to create the configuration file. For information on ATPSCON, see 
BOOK="nwmfpenu" COLLECTION="nw41"NetWare for Macintosh File and Print Services.363: Unable to connect to printer; returning job to queue.ATPSExplanation: The current job is being returned to the queue because the workstation could not establish a connection with the printer.Action: Make sure the printer is online and connected to the network.365: Unable to create dictionary file filename.ATPSExplanation: ATPS could not create the specified internal file because of a NetWare file error.Action: Make sure the volume has enough free disk space to create the file. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Disk Space Problems" in Supervising the Network. If there is enough space, use the "File Open/Lock Activity" option in the MONITOR utility to determine if the file is being used. For information on MONITOR, see "BOOK="utlrfenu" COLLECTION="nw41"MONITOR" in Utilities Reference.372: Can't find printer name; retrying.ATPSExplanation: ATPS could not locate the configured printer on the AppleTalk network. The printer name includes the printer name, type, and zone.Action: Use ATCON to locate the printer. For information on ATCON, see "BOOK="utlrfenu" COLLECTION="nw41"ATCON" in Utilities Reference. If the printer could not be located, check the cabling connecting the printer to the network. If the connection is secure, make sure the AppleTalk module is configured correctly.373: Error querying printer; using defaults.ATPSExplanation: The ATPS spooler encountered a problem retrieving PostScript information from a printer. ATPS will report default values to Macintosh clients.Action: Make sure the printer is online and operational.376: Could not attach to queue name.ATPSExplanation: ATPS is unable to service the specified queue. The queue may have been deleted.Action: Make sure the queue still exists. If it is deleted, re-create it.PAGENUM=80 ID="BP74"379: No queue Directory Services context specified in file filename.ATPSExplanation: The configuration file does not contain the NetWare Directory Services context in which the Queue object resides. This error probably occurred because the configuration was created under a version of NetWare for Macintosh prior to 4.1. Action: Re-create the configuration file using NetWare for Macintosh 4.1.383: Printing is currently in progress! Jobs currently being printed will be interrupted but will remain in the queue.ATPSExplanation: ATPS was directing jobs to an AppleTalk printer when you tried to unload ATPS.Action: If unloading ATPS and interrupt printing is not desired, respond with "No." Unload ATPS later, perhaps after disabling spoolers and printer servers to stop processing of new jobs.385: Printer name busy---reason.ATPSExplanation: The specified printer is not accepting connections because it is currently processing another job or is in an error state. The printer name includes the name, type, and zone of the printer.Action: This message is informational. If the problem persists, make sure the printer is operational.386: Can't find printer name; retrying.ATPSExplanation: ATPS could not locate the configured printer on the AppleTalk network. The printer name includes the printer name, type, and zone.Action: Use ATCON to locate the printer. For information on ATCON, see "BOOK="utlrfenu" COLLECTION="nw41"ATCON" in Utilities Reference. If the printer could not be located, check the cabling connecting the printer to the network. Make sure the AppleTalk module is configured correctly.387: Printer name is configured with an illegal AppleTalk name.ATPSExplanation: The printer name values are not valid. The printer name includes the name, type, and zone of the printer.Action: Give the printer a valid AppleTalk name.PAGENUM=81 ID="BP75"389: Couldn't access font file filename while building server font list.ATPSExplanation: ATPS could not open the specified internal font list file. The file may be in use or missing.Action: Make sure the file is located in the SYS:SYSTEM\NW-MAC\FONTS directory. If the file exists in the proper location, use the "File Open/Lock Activity" option in the MONITOR utility to determine if the file is being used. For information on MONITOR, see "BOOK="utlrfenu" COLLECTION="nw41"MONITOR" in Utilities Reference.396: The ATPS screen could not be closed.ATPSExplanation: The ATPS console screen could not be closed because of an internal error.Action: Contact your Novell Authorized Reseller.397: Unreachable.ATPSExplanation: ATPS could not locate the printer.Action: Make sure the printer is advertised in the Macintosh Chooser and in ATCON. If the printer is advertised, make sure that it is turned on and that it is not in an error condition. For information on ATCON, see "BOOK="utlrfenu" COLLECTION="nw41"ATCON" in Utilities Reference. 400: Connection with printer name was lost.ATPSExplanation: The AppleTalk connection was interrupted while trying to hide the current printer. A network problem or a bad printer connection occurred. The printer name includes the name, type, and zone of the printer.Action: Check the connection between the network and the printer.401: Problem connecting to printer name; retrying.ATPSExplanation: ATPS could not open an AppleTalk connection to the specified printer. This message may indicate a printer or network problem. The printer name includes the name, type, and zone of the printer.Action: Use ATCON to locate the printer. For information on ATCON, see "BOOK="utlrfenu" COLLECTION="nw41"ATCON" in Utilities Reference. If the printer could not be located, check the printer's connection to the network. Make sure the AppleTalk module is configured correctly.PAGENUM=82 ID="BP76"402: Couldn't connect to printer name; retrying.ATPSExplanation: ATPS could not open an AppleTalk connection to the specified printer. This message may indicate a printer or network problem. The printer name includes the name, type, and zone of the printer.Action: Use ATCON to locate the printer. For information on ATCON, see "BOOK="utlrfenu" COLLECTION="nw41"ATCON" in Utilities Reference. If the printer could not located, check the printer's connection to the network. Make sure the AppleTalk module is configured correctly.404: Could not change hidden state of printer name; unknown error.ATPSExplanation: An attempt to change the AppleTalk type of the printer failed for unknown reasons. The printer name includes the name, type, and zone of the printer.Action: Make sure the printer supports being hidden.406: Can't verify that correct dictionary is resident in printer; job may fail.ATPSExplanation: ATPS could not communicate with the printer to ensure that the correct version of the LaserPrep file needed to print the current job is available at the printer.Action: Make sure the printer supports being hidden.408: Can't verify that PatchPrep dictionary is resident in printer; job may fail.ATPSExplanation: ATPS is unable to communicate with the printer to ensure that the version of the LaserPrep file needed to print the current job is available at the printer.Action: Make sure the printer is advertised in the Macintosh Chooser and in ATCON. If the printer is advertised, make sure that it is turned on and that it is not in an error condition. For information on ATCON, see "BOOK="utlrfenu" COLLECTION="nw41"ATCON" in Utilities Reference. 433: Unable to open include file filename.ATPSExplanation: ATPS could not open the specified file for inclusion in the print job. The file may be in use or missing.Action: Disable and reenable the spooler.435: Unable to open dictionary file filename.ATPSExplanation: ATPS could not open the specified internal PostScript ProcSet resource file. The file may be in use or missing.Action: Try the operation again later.PAGENUM=83 ID="BP77"437: Unable to open dictionary file filename.ATPSExplanation: ATPS could not open the specified internal PostScript ProcSet resource file. Action: Try the operation again later.438: Requested font name is unavailable on the server.ATPSExplanation: The current PostScript job uses a font that is not available at the printer or at the server. The printer will probably substitute Courier for the font.Action: Install the font either at the Macintosh or at the printer.440: You must log into server name.ATPSExplanation: ATPS could not print the job because the job owner is not logged in to the server containing the queue and was trying to access a spooler that enforces queue security.Action: The job owner must log in to the appropriate server.448: Unable to open font file Path.ATPSExplanation: ATPS could not open the specified font list file. The file may be in use or missing. The path is the full path name of the font list file.Action: If the file exists, use the "File Open/Lock Activity" option in the MONITOR utility to determine if the file is being used. For information on MONITOR, see "BOOK="utlrfenu" COLLECTION="nw41"MONITOR" in Utilities Reference. If the file is not in use, disable and reenable the affected spooler.469: The current job contains no data.ATPSExplanation: ATPS could not detect data for the job currently being directed to the printer.Action: Make sure the printing configuration is set up correctly in the application that generated the print job.482: Font file filename has invalid syntax.ATPSExplanation: The captured font list file has incorrect syntax. Action: Delete the file.483: Printer name is unable to service queue nameATPSExplanation: The print server is shutting down because it could not send jobs from the queue to the printer. Action: Make sure the queue exists. Then, reselect it in ATPSCON. For information on ATPSCON, see 
BOOK="nwmfpenu" COLLECTION="nw41"NetWare for Macintosh File and Print Services.PAGENUM=84 ID="BP78"489: Server_name has no rights to charge username's account balance.ATPSExplanation: ATPS is unable to charge the user for printing a job. The server on which ATPS is running does not have rights to charge users. Action: Use the NetWare Administrator or NETADMIN utility to grant read and write trusteeship to the server over the accounting properties of the users to be charged. For information, see "BOOK="utlrfenu" COLLECTION="nw41"NetWare Administrator" in Utilities Reference or "BOOK="utlrfenu" COLLECTION="nw41"NETADMIN" in Utilities Reference.506: Printer connection timed out.ATPSExplanation: The AppleTalk session with the printer was lost due to a timeout error.Action: Make sure the printer is online and securely connected to the network. Check the printer log for signs of network communication errors.510: Restore hidden printer name?ATPSExplanation: This message enables previously hidden printers to be restored. The printer name includes the name, type, and zone of the printer.Action: Respond by entering a "Y" for each printer you want to make available to Macintosh users.516: Temporarily unable to query the printer; using old information.ATPSExplanation: The ATPS spooler encountered a problem retrieving PostScript information from a printer. ATPS will retry the operation later.Action: Check the printer.522: Send connection number message: user message buffer full.ATPSExplanation: ATPS could not send a message to the user on the connection number because the user already has too many unread messages.Action: The user must read and clear messages to free up additional buffer space.558: The spooler is not available on the network; check AppleTalk configuration.ATPSExplanation: AppleTalk reports that the stack is not bound to an interface.Action: Reconfigure the stack appropriately. For information, see the BOOK="atrefenu" COLLECTION="nw41"NetWare AppleTalk Reference guide.PAGENUM=85 ID="BP79"568: Unable to create dictionary file filename.ATPSExplanation: ATPS could not create the internal file because of a NetWare file error.Action: Make sure the volume has enough free disk space to create the file. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Disk Space Problems" in Supervising the Network. If there is enough space, use the MONITOR utility to make sure the file is not being used.578: Unable to open font list file path.ATPSExplanation: ATPS could not open the specified font list file. The file may be in use or missing. The path is the full path name of the font list file.Action: If the file exists, use the "File Open/Lock Activity" option in the MONITOR utility to determine if the file is being used. For information on MONITOR, see "BOOK="utlrfenu" COLLECTION="nw41"MONITOR" in Utilities Reference. If the file is not in use, disable and reenable the affected spooler.580: Unable to open font list file path.ATPSExplanation: ATPS could not open the specified font list file. The file may be in use or missing. The path is the full path name of the font list file.Action: Make sure the file is in the SYS:SYSTEM\NW-MAC\FONTS directory. If the file exists, use the "File Open/Lock Activity" option in the MONITOR utility to determine if the file is being used. For information on MONITOR, see "BOOK="utlrfenu" COLLECTION="nw41"MONITOR" in Utilities Reference.597: Can't advertise because named object already appears in zone; will retry.ATPSExplanation: The spooler could not register itself as an AppleTalk entity because its name is already in use by another node.Action: Give the spooler a unique name.615: Insufficient balance: user needs number point(s), has number points.ATPSExplanation: ATPS rejected the specified user's job because of an insufficient accounting point balance. The user is the name of the job owner. The first number is the number of additional points needed to complete the job. The second number is the number of points currently remaining to the user.Action: Increase the user's account balance.617: user has no rights to queue name.ATPSExplanation: The user is not a designated queue user of the queue. The user's job will be refused.Action: Give the user rights to place jobs in the queue.PAGENUM=86 ID="BP80"621: Couldn't print accounting bannerATPSExplanation: ATPS could not print an account summary banner after charging a user for a print job.Action: See the preceding messages for advice as to how to proceed.622: Total pages: number PostScript Errors: numberATPSExplanation: The total page number includes copies, but excludes banners. The PostScript Errors number displays the numbers of print errors detected.Action: If there are PostScript errors, check the printer mode.656: Problem charging for job.ATPSExplanation: ATPS could not charge a user's account for a print job.Action: Make sure the user's account has the necessary balance.660: Unable to open file path containing font list.ATPSExplanation: ATPS could not open the specified font list file. The file may be in use or missing. The path is the full path name of the font list file.Action: Make sure the file is in the SYS:SYSTEM\NW-MAC\FONTS directory. use the "File Open/Lock Activity" option in the MONITOR utility to determine if the file is being used. For information on MONITOR, see "BOOK="utlrfenu" COLLECTION="nw41"MONITOR" in Utilities Reference.666: Unable to open font list file path.ATPSExplanation: ATPS could not open the specified font list file. The file may be in use or missing. The path is the full path name of the font list file.Action: Make sure the file is in the SYS:SYSTEM\NW-MAC\FONTS directory. If the file is in the directory, use the "File Open/Lock Activity" option in the MONITOR utility to determine if the file is being used. For information on MONITOR, see "BOOK="utlrfenu" COLLECTION="nw41"MONITOR" in Utilities Reference.687: Printer name hardware error: explanation.ATPSExplanation: The specified printer reported a hardware error. The printer name includes the name, type, and zone of the printer. The explanation explains the nature of the error.Action: Check the printer and correct the physical problem.PAGENUM=87 ID="BP81"688: Printer name hardware error: explanation.ATPSExplanation: The specified printer reported a hardware error. The printer name includes the name, type, and zone of the printer. The explanation explains the nature of the error.Action: Check the printer and correct the physical problem.692: Can't find printer.ATPSExplanation: ATPS could not locate the specified hidden or restored printer.Action: Make sure the printer is online and properly connected.693: Couldn't create dictionary file filename.ATPSExplanation: ATPS could not create the internal file because of a NetWare file error.Action: Make sure the volume has enough free disk space to create the file. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Disk Space Problems" in Supervising the Network. If there is enough space, use the "File Open/Lock Activity" option in the MONITOR utility to determine if the file is being used. For information on MONITOR, see "BOOK="utlrfenu" COLLECTION="nw41"MONITOR" in Utilities Reference.694: Insufficient memory for configuration filename.ATPSExplanation: The server does not have enough available memory for ATPS to create a configuration.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.695: No spooler name specified in file filename.ATPSExplanation: The configuration file needs an AppleTalk spooler name.Action: Use ATPSCON to create the configuration file. For information on ATPSCON, see 
BOOK="nwmfpenu" COLLECTION="nw41"NetWare for Macintosh File and Print Services.698: Couldn't restore the hidden printer name.ATPSExplanation: ATPS could not restore the specified printer during unload time. The printer name includes the name, type, and zone of the printer.Action: Turn the printer off and on to restore it. PAGENUM=88 ID="BP82"702: Unable to open file path containing font list.ATPSExplanation: ATPS could not open the specified font list file. The file may be in use or missing. The path is the full path name of the font list file.Action: Make sure the file is in the SYS:SYSTEM\NW-MAC\FONTS directory. Use the "File Open/Lock Activity" option in the MONITOR utility to determine if the file is being used. For information on MONITOR, see "BOOK="utlrfenu" COLLECTION="nw41"MONITOR" in Utilities Reference.705: Can't place job in queue: reason.ATPSExplanation: ATPS could not place the job in a queue for the reason shown.MARK=BULLETReason: The user has no queue rights.Explanation: The queue security is on and the user is not logged in to the server or is not a valid queue user.Action: Make sure the user is logged in and is a valid queue user that has the appropriate rights to the queue.Reason: No space is left on the device.Explanation: The volume is probably out of disk space.Action: Increase the available disk space on the volume. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Disk Space Problems" in Supervising the Network.707: Can't place job in queue: reason.ATPSExplanation: ATPS could not place the job in a queue for the reason shown.MARK=BULLETReason: The user has no queue rights.Explanation: The queue security is on and the user is not logged in to the server or is not a valid queue user.Action: Make sure the user is logged in and is a valid queue user that has the appropriate rights to the queue.Reason: No space is left on the device.Explanation: The volume is probably out of disk space.Action: Increase the available disk space on the volume. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Disk Space Problems" in Supervising the Network.PAGENUM=89 ID="BP83"714: Couldn't open file filename.ATPSExplanation: ATPS could not open the file. The file may be open or missing.Action: Make sure the file is located in the proper location. Then, use the "File Open/Lock Activity" option in the MONITOR utility to determine if the file is being used. For information on MONITOR, see "BOOK="utlrfenu" COLLECTION="nw41"MONITOR" in Utilities Reference.717: Named object already appears in zone.ATPSExplanation: The spooler could not advertise itself because another entity in the zone is using the same AppleTalk name.Action: Give the spooler a unique name.719: Serious spooling error for spooler_name.ATPSExplanation: The spooler encountered an internal AppleTalk problem. The spooler name includes the spooler name, type, and zone.Action: Make sure the queue associated with the spooler still exists. If it does, increase the available memory. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.724: Problem writing end-of-file to queue.ATPSExplanation: The ATPS spooler could not write a terminating Control-D character at the end of a PostScript job entry.Action: Increase the available disk space on the volume. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Disk Space Problems" in Supervising the Network.727: Lost contact with printer.ATPSExplanation: ATPS lost an AppleTalk connection during printing.Action: Check the printer connection.728: Problem reading job from queue.ATPSExplanation: ATPS could not read print job data. The job may have been deleted from the queue.Action: Make sure the server has enough disk space to hold the print job. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Disk Space Problems" in Supervising the Network.PAGENUM=90 ID="BP84"752: Can't find spooler configuration filename to disable it; it may have previously suffered a fatal error.ATPSExplanation: ATPS is unable to disable the spooler configuration contained in filename, probably because it is already disabled.Action: Make sure the configuration is not currently disabled.760: Queue name not found on server.ATPSExplanation: The specified queue exists on another server; therefore, ATPS could not access it.Action: Use ATPSCON to specify a queue that resides on the server running ATPS. For information on ATPSCON, see 
BOOK="nwmfpenu" COLLECTION="nw41"NetWare for Macintosh File and Print Services.764: Job number (number bytes) was not received successfully and thus was aborted.ATPSExplanation: ATPS did not detect valid data while receiving the job. The job is being discarded. The job contained the number of bytes specified in the parentheses.Action: See the preceding messages for advice as to how to proceed.765: Job number contained no data and thus was aborted.ATPSExplanation: ATPS did not detect valid data while receiving the job. The job is being discarded.Action: See the full message for advice on to how to proceed.788: Printer returned null dictionary status.ATPSExplanation: The printer returned an unexpected response to a PostScript query.Action: None. This message is for information only.789: Couldn't allocate memory to manage print connection; rejecting print request.ATPSExplanation: ATPS is dropping a client connection because of an error allocating enough available memory to handle the connection. Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.801: Couldn't rebuild the server's font list.ATPSExplanation: ATPS could not create the file SERVER.FNT to hold the server-wide font list.Action: Make sure there is space available in the ATPS directory. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Disk Space Problems" in Supervising the Network.PAGENUM=91 ID="BP85"804: Unable to send printer setup file.ATPSExplanation: ATPS could not send the user-designated setup file to the printer because of a possible communication problem.Action: See the full message for more information.823: Can't identify job owner for accounting purposes.ATPSExplanation: ATPS could not identify the print job owner; therefore, it could not charge the owner for printing the job. Action: The owner's User object may have been deleted, or the User object may reside in a portion of the Directory tree currently unavailable to ATPS. Make sure the User object exists. If it does, see the appropriate documentation to resolve the NetWare Directory Services problem that may be causing parts of the Directory tree to be inaccessible.827: Problem writing include file filename to queue.ATPSExplanation: ATPS could not write the internal PostScript resource file to the queue.Action: Increase the available disk space on the volume. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Disk Space Problems" in Supervising the Network. Make sure the resource file exists.832: user has no rights to queue name.ATPSExplanation: The user is not a designated Queue User of the queue. The user's job will be refused.Action: Give the user rights to place jobs in the queue, and make sure the user is logged in to the server containing the queue.898: Job owner not found in directory.ATPSExplanation: ATPS could not identify the print job owner, therefore it could not charge the owner for printing the job. Action: The owner's User object may have been deleted, or the User object may reside in a portion of the Directory tree currently unavailable to ATPS. Make sure the User object exists. If it does, see the appropriate documentation to resolve the NetWare Directory Services problem that may be causing parts of the Directory tree to be inaccessible.926: Could not get all accounting information for username.ATPSExplanation: ATPS experienced an error while trying to read the user's NetWare Directory Services accounting properties. This is most likely because ATPS does not have rights to the User object's accounting properties.Action: Use the NETADMIN utility to grant read and write trusteeship to the server over the accounting properties of the users to be charged.PAGENUM=92 ID="BP86"942: Queue name was deleted.ATPSExplanation: ATPS was spooling a job to the queue when the queue was deleted.Action: Re-create the queue and reselect it in ATPSCON. For information on ATPSCON, see 
BOOK="nwmfpenu" COLLECTION="nw41"NetWare for Macintosh File and Print Services.943: Queue name was deleted.ATPSExplanation: ATPS was spooling a job to the queue when the queue was deleted.Action: Re-create the queue.PAGENUM=93 ID="BP87"ATXRP4: Printer name illegal AppleTalk name.ATXRPExplanation: ATXRP could not print the job because the AppleTalk information specified for the printer is invalid. The printer name includes the AppleTalk name, type, and zone of the printer.Action: Make sure the AppleTalk printer information specified in PCONSOLE does not use illegal characters such as the equal sign (=) and approximately equal sign.5: Couldn't read configuration information for printer number.ATXRPExplanation: The system could not initialize the driver for the printer. The number is the number of the printer as known to PSERVER.Action: Unload and reload ATXRP.7: Registered printer name as XRP number.ATXRPExplanation: ATXRP successfully registered itself as the driver for the printer. The number is the number of the printer as known to PSERVER.Action: None. This message is for information only.8: Couldn't register printer number.ATXRPExplanation: ATXRP could not register itself as the driver for the printer. The number is the number of the printer as known to PSERVER.Action: Unload and reload ATXRP.34: Reconfiguring printer number.ATXRPExplanation: ATXRP received a command to change the configuration of the printer. The number is the number of the printer as known to PSERVER.Action: None. This message is for information only.35: Couldn't reconfigure printer number.ATXRPExplanation: ATXRP experienced an error reconfiguring the printer. The number is the number of the printer as known to PSERVER.Action: Unload and reload ATXRP.PAGENUM=94 ID="BP88"47: Control-D characters in the current job will be sent as AppleTalk EOFs.ATXRPExplanation: The current job is being filtered for Control-D characters. Action: None. This message is for information only.49: Printer name not responding; retrying.ATXRPExplanation: ATXRP is trying to establish an AppleTalk connection with the printer, but the printer is not responding to the connection requests. ATXRP will retry the connection request.Action: If the condition persists, make sure the printer is online and is connected to the network. Check the system log for signs of network communication errors. If the error occurs intermittently, the printer may be responding slowly.53: Printer name unexpectedly not hidden.ATXRPExplanation: ATXRP expected the printer to be hidden. The printer name includes the name, type, and zone of the printer.Action: None. This message is for information only.54: Printer name unexpectedly hidden.ATXRPExplanation: ATXRP did not expect the printer to be hidden. The printer name includes the name, type, and zone of the printer.Action: None. This message is for information only.96: Printer name unexpectedly not hidden.ATXRPExplanation: ATXRP expected the printer to be hidden. The printer name includes the name, type, and zone of the printer.Action: None. This message is for information only.97: Printer name unexpectedly hidden.ATXRPExplanation: ATXRP did not expect the printer to be hidden. The printer name includes the name, type, and zone of the printer.Action: None. This message is for information only.103: Detected a Control-D character; signaling End of Job.ATXRPExplanation: ATXRP has detected a Control-D character in the current PostScript print job. It is sending an AppleTalk EOF marker to the printer in place of the Control-D character.Action: None. This message is for information only.PAGENUM=95 ID="BP89"104: Can't find printer name; retrying.ATXRPExplanation: ATXRP could not locate the configured printer on the AppleTalk network. The printer name includes the printer name, type, and zone.Action: Make sure the printer's AppleTalk name, type, and zone in ATCON match the printer's AppleTalk name, type, and zone in PCONSOLE. If the printer could not be located in ATCON, check the cabling connecting the printer to the network. If the connection is secure, make sure the AppleTalk module is configured correctly. For information on ATCON, see "BOOK="utlrfenu" COLLECTION="nw41"ATCON" in Utilities Reference. For information on PCONSOLE, see "BOOK="utlrfenu" COLLECTION="nw41"PCONSOLE" in Utilities Reference. 105: Printer name busy; retrying.ATXRPExplanation: The specified printer is not accepting connections because it is currently processing another job or is in an error state. The printer name includes the name, type, and zone of the printer. ATXRP will try to connect to the printer again.Action: None. This message is for information only. If the problem persists, check the printer.106: Can't find printer name; retrying.ATXRPExplanation: ATXRP could not locate the configured printer on the AppleTalk network. The printer name includes the printer name, type, and zone.Action: Make sure the printer's AppleTalk name, type, and zone in ACTON match the printer's AppleTalk name, type, and zone in PCONSOLE. If the printer could not be located in ATCON, check the cabling connecting the printer to the network. If the connection is secure, make sure the AppleTalk module is configured correctly. For information on ATCON, see "BOOK="utlrfenu" COLLECTION="nw41"ATCON" in Utilities Reference. For information on PCONSOLE, see "BOOK="utlrfenu" COLLECTION="nw41"PCONSOLE" in Utilities Reference.107: Connection with printer name was lost.ATXRPExplanation: The AppleTalk session with the printer was lost due to a timeout error. The printer name represents the AppleTalk name, type, and zone of the printer.Action: Make sure the printer is online and securely connected to the network. Check the system log for signs of network communication errors.108: Couldn't change hidden state of printer name, unknown error.ATXRPExplanation: ATXRP could not hide or restore the printer. The printer name represents the AppleTalk name, type, and zone of the printer.Action: The printer model may not support hiding. If the printer does support hiding, unload and reload ATXRP to try hiding the printer again.PAGENUM=96 ID="BP90"109: Printer name was hidden.ATXRPExplanation: You specified that ATXRP hide the specified printer. The printer name includes the name, type, and zone of the printer.Action: None. This message is for information only.110: Printer name was restored.ATXRPExplanation: ATXRP has made the specified printer available to Macintosh users for direct printing. The printer name includes the name, type, and zone of the printer.Action: None. This message is for information only.111: Hiding Printer.ATXRPExplanation: ATXRP will make the printer unavailable for direct printing by Macintosh workstations. Action: None. This message is for information only.112: Restoring Printer.ATXRPExplanation: ATXRP is unhiding the printer, making it available for direct printing.Action: None. This message is for information only.115: Printer name is a type that can't be hidden.ATXRPExplanation: ATXRP does not support hiding of the specified printer model.Action: None. This message is for information only.119: Successfully printed job number.ATXRPExplanation: The print job printed successfully.Action: None. This message is for information only.125: Illegal AppleTalk printer name.ATXRPExplanation: ATXRP could not print the job because the AppleTalk information specified for the printer is invalid.Action: Make sure no illegal characters, such as the equal sign (=) or approximately equal sign, in the AppleTalk printer information are specified in PCONSOLE.PAGENUM=97 ID="BP91"130: Can't find printer name; still trying.ATXRPExplanation: ATXRP is still trying to locate the designated printer on the AppleTalk network. The printer name includes the name, type, and zone of the printer.Action: Make sure the printer's AppleTalk name, type, and zone in ACTON match the printer's AppleTalk name, type, and zone in PCONSOLE. If the printer could not be located in ATCON, check the cabling connecting the printer to the network. If the connection is secure, make sure the AppleTalk module is configured correctly. For information on ATCON, see "BOOK="utlrfenu" COLLECTION="nw41"ATCON" in Utilities Reference. For information on PCONSOLE, see "BOOK="utlrfenu" COLLECTION="nw41"PCONSOLE" in Utilities Reference. 134: Unable to connect to printer; can't print job number.ATXRPExplanation: The print job could not be printed because the workstation could not establish a connection with the printer. ATXRP will try to print the job again.Action: See earlier messages appearing in the log or on the screen for information on how to proceed.138: Aborted job number due to user command.ATXRPExplanation: ATXRP did not print the job because the administrator aborted it during printing. Action: None. This message is for information only.139: Problem connecting to printer name; retrying.ATXRPExplanation: ATXRP could not open an AppleTalk connection to the specified printer. This message may indicate a printer or network problem. The printer name includes the name, type, and zone of the printer.Action: Make sure the printer is connected to the network, and check the system log for network communication errors.149: Servicing job number, printing one copy.ATXRPExplanation: ATXRP has begun to service the job and will print one copy.Action: None. This message is for information only.150: Unknown problem restoring hidden printer.ATXRPExplanation: ATPS could not restore the hidden printer for undetermined reasons.Action: Turn the printer off and on to restore it.PAGENUM=98 ID="BP92"152: Unable to print job number due to error reading job.ATXRPExplanation: ATXRP could not print the job because it experienced an error receiving the print job from PSERVER. ATXRP will try printing the job again.Action: Make sure the server has enough available disk space to hold the print job. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Disk Space Problems" in Supervising the Network.180: Printer connection timed out.ATXRPExplanation: The AppleTalk session with the printer was lost due to a timeout error.Action: Make sure the printer is online and securely connected to the network. Check the system log for signs of network communication errors.185: Printer name busy; retrying.ATXRPExplanation: The specified printer is not accepting connections because it is currently processing another job or is in an error state. The printer name includes the name, type, and zone of the printer. ATXRP will try to connect to the printer again.Action: None. This message is for information only. If the problem persists, check the printer.191: Printer connection closed by printer.ATXRPExplanation: The printer closed the AppleTalk session with the client, because the print job was aborted at the printer or the printer timed out while printing the job.Action: Make sure the print job contained valid data and was not cancelled at the printer.192: Couldn't start printer number.ATXRPExplanation: ATXRP is unable to service the printer. The server may not have enough available memory. Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. Then, unload and reload ATXRP.193: Printer connection timed out.ATXRPExplanation: The AppleTalk session with the printer was lost due to a timeout error.Action: Make sure the printer is online and is connected to the network. Check the system log for signs of network communication errors.PAGENUM=99 ID="BP93"194: Servicing job number, printing number copies.ATXRPExplanation: ATXRP has begun to service the job. ATXRP will print the number of copies.Action: None. This message is for information only.195: Fatal error for printer number.ATXRPExplanation: ATXRP is unable to service the printer.Action: See earlier messages appearing in the log or on the screen for information on how to proceed.196: Couldn't initialize printer number; insufficient memory.ATXRPExplanation: ATXRP is unable to service the printer. The server may not have enough available memory.Action: Increase the available memory. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. Then, unload and reload ATXRP.203: Printer connection closed by printer.ATXRPExplanation: The printer closed the AppleTalk session with the client because the print job was aborted at the printer or the printer timed out while printing the job.Action: Make sure the print job contained valid data and was not cancelled at the printer.205: Closing AppleTalk connection with printer due to communications error.ATXRPExplanation: The AppleTalk session with the printer was lost due to a communications error.Action: See earlier messages appearing in the system log or on the screen for information on how to proceed.210: Sending banner data to printer.ATXRPExplanation: ATXRP is printing a banner page.Action: None. This message is for information only.223: Printer connection closed by printer.ATXRPExplanation: The printer closed the AppleTalk session with the client because the print job was aborted at the printer or the printer timed out while printing the job.Action: Make sure the print job contained valid data and was not cancelled at the printer.PAGENUM=100 ID="BP94"226: Deregistered printer number.ATXRPExplanation: ATXRP is no longer acting as a driver for the printer. The number is the number of the printer as known to PSERVER. This message usually appears when ATXRP is unloaded.Action: None. This message is for information only.228: Sending job data to printer.ATXRPExplanation: ATXRP is sending a job to the printer.Action: None. This message is for information only.229: Hiding printer name.ATXRPExplanation: ATXRP will make the specified printer unavailable for direct printing by Macintosh workstations. The printer name includes the name, type, and zone of the printer.Action: None. This message is for information only.230: Restoring printer name.ATXRPExplanation: ATXRP is unhiding the printer, making it available for direct printing.Action: None. This message is for information only.236: Received down command.ATXRPExplanation: PSERVER is going down and has instructed ATXRP to unload.Action: None. This message is for information only.267: Unable to print job job_number due to error communicating with printer.ATXRPExplanation: ATXRP could not print the job because of a communications error. This message indicates a network error or a printer problem.Action: See earlier messages appearing in the system log or on the screen for information on how to proceed.PAGENUM=101 ID="BP95"AUDITCON005: This utility was unable to write the audit configuration header.AUDITCONExplanation: An internal error has occurred. AUDITCON could not write to the audit configuration header.Action: Restart AUDITCON. If that doesn't work, bring down and reboot the server. If the problem persists, contact your Novell Authorized Reseller.010: This utility was unable to access the audit property via NCP.AUDITCONExplanation: The server returned an error code when the utility tried to access the audit property through the NetWare Core Protocol (NCP).Action: Restart AUDITCON. If that doesn't work, bring down and reboot the server. If the problem persists, contact your Novell Authorized Reseller.015: The auditing system cannot be accessed.AUDITCONExplanation: The server returned an error code when trying to access the auditing system. Action: Restart AUDITCON. If that doesn't work, bring down and reboot the server. If the problem persists, contact your Novell Authorized Reseller.020: An invalid auditor's password was specified.AUDITCONExplanation: The wrong auditing password was specified for the volume.Action: Make sure you have selected the correct volume; then retype the password. (The current volume name is at the top of the screen.) 025: Another auditor is already logged in.AUDITCONExplanation: The auditing system was configured to allow only one auditor login. Action: Wait for the other auditor to exit. If more than one auditor needs access, change the "Allow Concurrent Logins" setting to Yes. 030: This utility was unable to read the bit map.AUDITCONExplanation: The bit map could not be read.Action: Restart AUDITCON. If that doesn't work, bring down and reboot the server. If the error persists, disable volume auditing. Ask the network supervisor, or someone with equivalent rights, to delete NET$AUDT files; then enable volume auditing again.PAGENUM=102 ID="BP96"035: This utility was unable to write the bit map.AUDITCONExplanation: The bit map could not be written to.Action: Restart AUDITCON. If that doesn't work, bring down and reboot the server. If the problem persists, contact your Novell Authorized Reseller.040: This utility was unable to close the old audit file.AUDITCONExplanation: The server returned an error when trying to close the old audit file. Action: Restart AUDITCON. If that doesn't work, bring down and reboot the server. If the problem persists, the file system could be corrupted. Contact your Novell Authorized Reseller.045: This utility cannot create the file.AUDITCONExplanation: The server returned an error when trying to create a file. Action: Restart AUDITCON. If that doesn't work, bring down and reboot the server. If the problem persists, the file system could be corrupted. Contact your Novell Authorized Reseller.050: This utility cannot delete the old audit file. Possibly the file has already been deleted.AUDITCONExplanation: The server returned an error when trying to delete the old audit file.Action: Restart AUDITCON. If that doesn't work, bring down and reboot the server. If the problem persists, the file system could be corrupted. Contact your Novell Authorized Reseller.055: This utility cannot set the attribute for directory entry name.AUDITCONExplanation: The server returned an error when setting a directory attribute.Action: Restart AUDITCON. If that doesn't work, bring down and reboot the server. If the problem persists, contact your Novell Authorized Reseller.060: This utility cannot disable volume auditing.AUDITCONExplanation: Volume auditing could not be disabled.Action: Restart AUDITCON. If that doesn't work, bring down and reboot the server. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=103 ID="BP97"065: Container auditing was not enabled. You must have administrative rights.AUDITCONExplanation: The user does not have rights to enable auditing for a container. The user needs Supervisor (or equivalent) rights to enable auditing for a container.Action: Have the network supervisor or someone with equivalent rights enable auditing.070: Container auditing was not enabled.AUDITCONExplanation: The server failed when trying to enable container auditing.Action: Make sure the user has Supervisor (or equivalent) rights to enable auditing on a container. Restart AUDITCON. If that doesn't work, bring down and reboot the server.075: Volume auditing cannot be enabled. You must have Supervisor equivalent rights.AUDITCONExplanation: The user does not have rights to enable auditing for a volume.Action: Have the network supervisor or someone with equivalent rights enable volume auditing.080: This volume cannot be enabled.AUDITCONExplanation: The server returned an unrecoverable error when trying to enable the volume.Action: Restart AUDITCON. If that doesn't work, bring down and reboot the server. If the problem persists, contact your Novell Authorized Reseller.085: This utility cannot read the filter.AUDITCONExplanation: The server returned an error when trying to read a filter. Action: Restart AUDITCON. If that doesn't work, bring down and reboot the server. If the problem persists, the file system or the server could be corrupted. Contact your Novell Authorized Reseller.090: You are using the wrong filter file version.AUDITCONExplanation: The filter file is an old version or is corrupted. Action: Delete the old or corrupted .ARF file.095: This utility cannot write the filter.AUDITCONExplanation: The file system returned an error when trying to write the filter. The edited filter could not be saved. Action: Restart AUDITCON. If that doesn't work, bring down and reboot the server. If the problem persists, the file system or the server could be corrupted. Contact your Novell Authorized Reseller.PAGENUM=104 ID="BP98"105: Null audit passwords are not allowed.AUDITCONExplanation:  MOREINFO="NONE"<Enter> was pressed without a password being entered.Action: Type a valid password; then press MOREINFO="NONE"<Enter>.110: This utility cannot change the audit password.AUDITCONExplanation: The server returned an error code when the audit password was changed. Action: Have the network supervisor or someone with equivalent rights create a new password.115: An invalid password was entered.AUDITCONExplanation: The password entered either has invalid characters or is too long or too short.Action: Enter a valid password. If this message persists, have the network supervisor create a new password.120: This utility cannot reset the audit file.AUDITCONExplanation: The server returned an error code when trying to reset the audit file. Action: Restart AUDITCON. If that doesn't work, bring down and reboot the server. If the problem persists, the file system or the server could be corrupted. Contact your Novell Authorized Reseller.125: This utility cannot reset the audit history file.AUDITCONExplanation: The server returned an error code when trying to reset the audit history file. Action: Restart AUDITCON. If that doesn't work, bring down and reboot the server. If the problem persists, the file system or the server could be corrupted. Contact your Novell Authorized Reseller.130: This utility cannot write to the file.AUDITCONExplanation: The server returned an error when trying to write to the file.Action: Restart AUDITCON. If that doesn't work, bring down and reboot the server. If the error persists, contact your Novell Authorized Reseller.140: The current server does not support auditing.AUDITCONExplanation: The server you have selected does not support auditing.Action: Have the network supervisor enable auditing on the current server. Make sure you have selected the correct server. The current server is shown at the top of the screen.PAGENUM=105 ID="BP99"145: Auditing versions for the server and AUDITCON do not match.AUDITCONExplanation: Auditing for the server and AUDITCON must utilize compatible versions. Action: Update either the AUDITCON or server version, as appropriate.150: The SplitPath function returned error code.AUDITCONExplanation: The server routine to split path names returned an error. Action: Contact your Novell Authorized Reseller.155: The Unicode tables cannot be initialized.AUDITCONExplanation: The Unicode files could not be found in the current search paths.Action: The Unicode files should be installed in SYS:PUBLIC. Make sure the workstation has a drive mapped to SYS:PUBLIC. If the workstation has a drive mapped to SYS:PUBLIC and the Unicode files still could not be found, contact your Novell Authorized Reseller.160: This utility cannot create a Directory Services context.AUDITCONExplanation: NetWare Directory Services returned an error. Action: Restart AUDITCON. If that doesn't work, bring down and reboot the server. If the error persists, contact your Novell Authorized Reseller.165: This utility cannot get the Directory Services context.AUDITCONExplanation: NetWare Directory Services returned an error. Possibly the VLM shell was not loaded, or the proper login was not used. Action: Make sure that the workstation is using valid VLM shell versions, and that the user is using the proper login utility. (The NetWare 4 LOGIN utility must be used to run NetWare Directory Services.)170: This utility cannot set the Directory Services context.AUDITCONExplanation: NetWare Directory Services returned an error.Action: Restart AUDITCON. If that doesn't work, bring down and reboot the server. If the error persists, contact your Novell Authorized Reseller.175: This utility cannot read the Directory Services object.AUDITCONExplanation: NetWare Directory Services returned an error. Possibly the VLM shell was not loaded, or the proper login utility was not used. PAGENUM=106 ID="BP100"Action: Make sure the workstation is using valid VLM shell versions. Make sure you are using the proper login utility. (The NetWare 4 LOGIN utility must be used or you cannot run NetWare Directory Services.) Make sure you have BROWSE rights to the container object.180: This utility cannot allocate a Directory Services buffer.AUDITCONExplanation: NetWare Directory Services returned an error. Action: Restart AUDITCON or the client workstation.185: This utility cannot get the Directory Services list.AUDITCONExplanation: NetWare Directory Services returned an error. Action: Restart AUDITCON or the server.190: This utility cannot get the Directory Services object name.AUDITCONExplanation: NetWare Directory Services returned an error. Possibly the VLM shell was not loaded, or the proper login utility was not used. Action: Make sure the workstation is using valid VLM shell versions. Make sure you are using the proper login utility. (The NetWare 4 LOGIN utility must be used to run NetWare Directory Services.) Make sure you are using the proper login utility. 195: The Read Audit File function returned error number.AUDITCONExplanation: Possibly the audit file is corrupted. Action: If the file is corrupted, reset it through the Auditing options menu, or delete the file at the DOS prompt; then restart AUDITCON.200: The start Date/Time is after the end Date/Time.AUDITCONExplanation: The specified start Date/Time is later than the specified end Date/Time.Action: Specify a start Date/Time that is chronologically earlier than the end Date/Time.205: This utility cannot read the temporary work file.AUDITCONExplanation: Possible the temporary work file became corrupted while being written.Action: Retry the command.210: This utility cannot write the temporary work file.AUDITCONPAGENUM=107 ID="BP101"Explanation: The utility could not write the temporary work file. The utility looks for a default temporary directory in which to write the temporary work file. If a default directory is not specified, the utility tries to write the temporary file in the current directory. This message is returned if the user does not have Write access to either the default or the current directory.Action: Do one of the following:MARK=BULLETSpecify a default temporary directory using the SET command. Any existing directory on the network can be designated as the default temporary directory. In the example below, the \TMP directory on drive C: is designated as the default temporary directory.FORMAT="LINESPECIFIC"MOREINFO="NONE"MOREINFO="NONE"SET TMP=C:\TMP  MOREINFO="NONE"<Enter> Be sure the user has Write access to the specified directory; then retry the command. Change to a directory where the user has Write access; then retry the command.215: This utility cannot create the temporary work file.AUDITCONExplanation: The utility could not create the temporary work file. The utility looks for a default temporary directory in which to create the temporary work file. If a default directory is not specified, the utility tries to create the temporary file in the current directory. This message is returned if the user does not have Create rights for the default or current directory, or if there is not enough disk space on the volume to create the temporary work file.Action: Do one of the following:MARK=BULLETSpecify a default temporary directory using the SET command. Any existing directory on the network can be designated as the default temporary directory. In the example below, the \TMP directory on drive C: is designated as the default temporary directory.FORMAT="LINESPECIFIC"MOREINFO="NONE"MOREINFO="NONE"SET TMP=C:\TMP  MOREINFO="NONE"<Enter> Make sure that the user has Create rights for the specified directory, and that the target volume has enough disk space to allow for the creation of the temporary work file (see "BOOK="superenu" COLLECTION="nw41"Resolving Server Disk Space Problems" in Supervising the Network). Then retry the command. Change to a directory where the user has Create rights; then retry the command.Remove unnecessary files from the disk to make room for the creation of the temporary work file; then retry the command. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Disk Space Problems" in Supervising the Network.Change to a volume that has enough disk space to allow for the creation of the temporary work file; then retry the command.PAGENUM=108 ID="BP102"220: This utility failed on file open.AUDITCONExplanation: The utility failed to open the specified audit file.Action: Make sure the audit file you want to view exists. Make sure you spell the filename correctly. Make sure the path to the audit file you want is correct.225: This utility cannot read the file.AUDITCONExplanation: The audit file currently open cannot be read because of file corruption.Action: This audit file is unusable. Delete the file.300: This utility cannot read the audit file configuration header.AUDITCONExplanation: The audit file being read is corrupted, and the configuration header cannot be read.Action: This audit file is unusable. Delete the file.310: The current audit file has been reset which canceled this view. To continue viewing this file, press escape and choose `View Old Audit File'.AUDITCONAction: You can continue to view the reset audit file, or view the now older audit file.970: The attempt to open the Unicode table files failed.AUDITCONAction: See IDREF="FM15675""970: The attempt to open the Unicode table files failed." in Appendix C.971: The workstation does not have enough memory to load the Unicode table files.AUDITCONAction: See IDREF="FM55341""971: The workstation does not have enough memory to load the Unicode table files." in Appendix C.972: Access to the Unicode table files was denied.AUDITCONAction: See IDREF="FM90152""972: Access to the Unicode table files was denied." in Appendix C.973: The Unicode table files cannot be found in the NLS directory or in the search path. Code page: <number>  Country:  <number>AUDITCONAction: See IDREF="FM62778""973: The Unicode table files cannot be found in the NLS directory or in the search path. Code page: number Country: number" in Appendix C.974: The Unicode table files are corrupt.AUDITCONAction: See IDREF="FM63405""974: The Unicode table files are corrupt." in Appendix C.PAGENUM=109 ID="BP103"975: The Unicode table files cannot be opened because there are already too many open files. Close some files or modify your CONFIG.SYS file.AUDITCONAction: See IDREF="FM49793""975: The Unicode table files cannot be opened because there are already too many open files. Close some files or modify your CONFIG.SYS file." in Appendix C.999: The message file for this utility cannot be found.AUDITCONAction: See IDREF="FM69424""999: The message file for this utility cannot be found." in Appendix C.PAGENUM=110 ID="BP104"AURP2313: Failed to send Routing Information request.AURPExplanation: AURP uses the Routing Information request to obtain a peer's entire routing table at the start of an AURP connection. If AURP is unable to send the request, the peer's routes are not learned. Action: If another message is displayed that indicates the nature of the error, follow the action directed for that error. Then, unload and reload AURP. This reestablishes the AURP connection.2314: Failed to send Routing Information Response.AURPExplanation: AURP sends Routing Information Responses to inform the AURP peer about all known routes available through this router. This information is not retransmitted. Action: If another message is displayed that indicates the nature of the error, follow the action directed for that error. Then unload and reload AURP. This reestablishes the AURP connection. 2324: No memory when entering range network_range. AURPExplanation: AURP could not allocate memory to save the route for the indicated network range. The route is discarded. Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.2330: Received Open Response with error code IP_address. Connection rejected.AURPExplanation: The peer AURP router, identified by the IP address, rejected the open connection request. No routing or zone information is exchanged with the peer. Action: Verify that the peer's AURP configuration includes this router in the Remote Peers List, or that it accepts unconfigured peers. 2331: Retransmission Handler (rtx_handler) is unable to allocate ECB.AURPExplanation: The router could not acquire sufficient packet receive buffers, also called Event Control Blocks (ECBs). AURP was trying to retransmit a packet when the ECB allocation error occurred. This could be a temporary condition, or it could indicate that the number of ECBs available is not sufficient to support the server load. Action: If the computer consistently get ECB allocation errors, see "BOOK="superenu" COLLECTION="nw41"Resolving Event Control Block Allocation Errors" in Supervising the Network.PAGENUM=111 ID="BP105"2333: Error opening AURP configuration file filename, error code.AURPExplanation: AURP could not open its configuration file and could not load. The configuration file is either not present or in use by another program. Action: Configure AURP using INETCFG. For information on INETCFG, see "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference. Exit the AURP and AppleTalk configuration screens before loading AURP.2334: Parsing failure in filename. Missing keyword: [AURP_TUNNEL].AURPExplanation: AURP encountered an error in the configuration file. This file is created by INETCFG and should not be edited. Action: Use INETCFG to reconfigure AURP. For information on INETCFG, see "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference.2335: Failed to allocate memory for tunnel.AURPExplanation: AURP could not allocate enough available memory to operate and could not load. Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.2337: Failed to allocate memory for an AURP peer.AURPExplanation: AURP could not allocate enough available memory to support a peer configured with INETCFG in the AURP Remote Peer list. Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.2340: Failure occurred while parsing [AURP_TUNNEL] parameter filename.AURPExplanation: AURP encountered an error in the configuration file. This file is created by INETCFG and should not be edited. Action: Use INETCFG to reconfigure AURP. For information on INETCFG, see "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference.2342: Failed to allocate memory for tunnel structure.AURPExplanation: AURP could not get memory to create necessary data structures. Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.2344: Failed to allocate memory for AURP peers.AURPExplanation: AURP could not allocate enough available memory to support a peer configured with INETCFG in the AURP Remote Peer list. Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.PAGENUM=112 ID="BP106"2345: Failure occurred while parsing [AURP_PEER] parameter name.AURPExplanation: AURP encountered an error in the configuration file. This file is created by INETCFG and should not be edited. Action: Use INETCFG to reconfigure AURP. For information on INETCFG, see "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference.2348: Received and discarded a packet from an unsupported version number of AURP implementation.AURPExplanation: AURP received a packet with a version other than the one supported. AURP didn't understand the version, so it discarded the packet. Action: If the peer could not be reconfigured to use a different version number, use INETCFG to remove the peer from the AURP Remote Peers List. For information on INETCFG, see "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference.2349: Received and discarded a DDP packet from an AURP router in which no connection has been established.AURPExplanation: AURP received a normal AppleTalk packet (not an AURP routing protocol packet) through the tunnel from a router that doesn't have a current connection. Action: Use INETCFG to verify that all desired AURP peers have been added to AURP's Remote Peers List. For information on INETCFG, see "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference.2350: Received and discarded an AURP packet with an unknown destination.AURPExplanation: AURP received a packet with an unrecognized IP destination address. Action: Use INETCFG to verify that the local IP address configured for AURP matches one of the IP addresses in the peer's AURP Remote Peers List. For information on INETCFG, see "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference.2351: Received and discarded a packet from an unknown AURP router at IP_address.AURPExplanation: The AURP router at the indicated address does not have a connection to the router at the source IP address in the received packet. Action: To have AURP establish a connection with the peer, use INETCFG to add the peer's IP address to AURP's Remote Peers List. For information on INETCFG, see "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference.PAGENUM=113 ID="BP107"2352: Unrecognized tunnel packet type packet_type.AURPExplanation: AURP received an unknown packet type through the tunnel and the packet was discarded. This usually indicates that AURP is misconfigured.Action: Use INETCFG to reconfigure AURP. For information on INETCFG, see "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference.2357: Failed to initialize tunnel media.AURPExplanation: AURP could not initialize IP to support AURP. Action: Verify that IP is bound to a network interface using the IP address specified as AURP's local IP address. 2358: Insufficient memory to allocate a router interface structure for the tunnel.AURPExplanation: AURP could not allocate enough available memory to add itself to the local AppleTalk router's list of interfaces. AppleTalk cannot use the AURP tunnel.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.2359: Failed to allocate connection control block.AURPExplanation: AURP could not allocate enough available memory for the internal structure necessary to maintain a connection with an AURP peer. Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.2367: No memory to initialize UDP client.AURPExplanation: AURP could not allocate enough available memory to form a data structure used to register with UDP. AURP could not load. Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.2368: Failed to register as a client with UDP. Error code returned by UDP.AURPExplanation: AURP tried unsuccessfully to register with UDP to send and receive packets on the IP internetwork. This error is probably caused by insufficient memory resources. If the server has enough available memory, this problem may be caused by a conflict with another application using the AURP UDP port 387. Action: Increase the available memory. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. If the server has available memory, determine which application is using the AURP UDP port 387 and unload the application.PAGENUM=114 ID="BP108"2369: UDP failed to send AURP packet because error_description.AURPExplanation: UDP could not send an AURP packet. This error can occur if TCP/IP is not bound to a network interface using the source IP address supplied by AURP, if TCP/IP does not have a route to the destination of the packet, or if the server does not have enough available memory to send the packet. Action: Use INETCFG to verify that the local IP address configured for AURP matches an IP address specified for a TCP/IP bind. If not, select a new local address. Verify that the IP addresses in the AURP Remote Peers List are correct. TCP/IP must be directly attached to the networks specified in these IP addresses or have routes to the networks. For information on INETCFG, see "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference. Increase the available memory. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.2370: No memory for zone process!AURPExplanation: AURP could not allocate enough available memory to create the process it uses to maintain zone information. AURP could not load. Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.2372: AURP cannot operate correctly when AppleTalk is configured as an end node and not a router. AURP failed to initialize.AURPExplanation: AURP depends on AppleTalk, and it can only function if AppleTalk is configured as a router. Action: Use INETCFG to configure the APPLETLK.NLM file to enable packet forwarding. For information on INETCFG, see "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference. 2376: The hopcount count in alternate route network_range is too large. Discard alternate route.AURPExplanation: The number of hops separating this router and the destination is larger than the maximum of 15. The route must be discarded. Action: If the network has connectivity problems, reconfigure the network to decrease the number of routers between end nodes.2378: UDP returned error code when AURP attempted to send packet.AURPExplanation: UDP could not send the AURP packet. The error code was returned by UDP. This is usually a temporary condition. Action: If the problem persists, contact your Novell Authorized Reseller.PAGENUM=115 ID="BP109"2381: AURP initialization failed.AURPExplanation: AURP did not load. This message follows an AURP message describing the error AURP encountered. Action: Follow the action for the specified AURP error. 2383: Unable to allocate ECB for retransmitting Open Requests.AURPExplanation: The router could not acquire sufficient packet receive buffers, also called event control blocks (ECBs). This may be a temporary condition, or it may indicate that the number of ECBs available is not sufficient to support the server load. AURP was trying to send an Open Request when the ECB allocation error occurred. AURP pauses and then tries to send the Open Request again. Action: This may be a temporary condition, or it may indicate that the number of ECBs available is not sufficient to support the server load. See "BOOK="superenu" COLLECTION="nw41"Resolving Event Control Block Allocation Errors" in Supervising the Network for information to correct this condition.2385: No memory when entering an alternate route for range network_range.AURPExplanation: AURP could not allocate enough available memory to store an alternate route for the destination network specified. This route is lost.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.PAGENUM=116 ID="BP110"AUTO1: The message file name is invalid. The program cannot be loaded.AUTOExplanation: The .MSG file is invalid. This problem could be the result of a corrupted file, a bad translation, or an outdated file version.Action: Either update the .MSG file with a valid copy or delete the file. The DOS Requester will use the default messages that are bound to the binary files.5: Module1.VLM is not loaded. The module2.VLM file cannot be loaded before module1.VLM. Load the module1.VLM file first then try to load the module2.VLM file.AUTOExplanation: The module2.VLM requires that the module1.VLM be loaded first. Either the current configuration has module1.VLM and module2.VLM loading out of order, or module1.VLM did not load successfully.Action: Make sure the module1.VLM is configured to load before module2.VLM. To do this, change the load order of the "VLM=" parameter in the NET.CFG file. For information on the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.7: In order to load the module3.VLM, one of the following VLMs must be loaded: module1.VLM, module2.VLM.AUTOExplanation: The module3.VLM requires that module1.VLM or module2.VLM be loaded first. Either the current configuration has module3.VLM loading before the modules in the module1.VLM or module2.VLM list, or module1.VLM or module2.VLM did not load successfully.Action: Make sure the module1.VLM or module2.VLM load successfully before module3.VLM. 42: There is a missing or invalid value for `parameter' on line number of the configuration file. This entry will be ignored. Correct the line specified in the configuration file before continuing.AUTOExplanation: The configuration file contains a configuration keyword that has an invalid parameter or that does not specify a parameter. This invalid line will be ignored by the configuration process.Action: None. This message is for information only. The line will be ignored. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message.PAGENUM=117 ID="BP111"43: There is a missing or invalid ON/OFF value for `parameter' on line number of the configuration file. This entry will be ignored. Correct the line specified in the configuration file before continuing.AUTOExplanation: The configuration file contains a configuration keyword that is defined to use either an "ON" or "OFF" parameter, but a different parameter or no parameter is specified. This invalid line will be ignored by the configuration process.Action: None. This message is for information only. The line will be ignored. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the message.45: The parameter specified for the following option was out of range and has been adjusted.AUTOExplanation: A configurable parameter is configured too high or too low to be valid. The parameter is specified on the line following the message.Action: Correct the parameter specified in the NET.CFG file. For information on the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.PAGENUM=118 ID="BP112"BIND1: The message file name is invalid. The program cannot be loaded.BINDExplanation: The .MSG file is invalid. This problem could be the result of a corrupted file, a bad translation or an outdated file version.Action: Update the .MSG file with a valid copy, or delete the file. The DOS Requester will use the default messages that are bound to the binary files.5: Module1.VLM is not loaded. The module2.VLM file cannot be loaded before module1.VLM. Load the module1.VLM file first then try to load the module2.VLM file.BINDExplanation: The module2.VLM requires that the module1.VLM be loaded first. Either the current configuration has module1.VLM and module2.VLM loading out of order, or module1.VLM did not load successfully.Action: Make sure that module1.VLM is configured to load before module2.VLM. To do this, change the load order of the "VLM=" parameter in the NET.CFG file. For information on the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.7: In order to load the module3.VLM, one of the following VLMs must be loaded: module1.VLM, module2.VLM.BINDExplanation: The module3.VLM requires that module1.VLM or module2.VLM be loaded first. Either the current configuration has module3.VLM loading before the modules in the module1.VLM or module2.VLM list, or module1.VLM or module2.VLM did not load successfully.Action: Make sure that module1.VLM or module2.VLM load successfully before module3.VLM.42: There is a missing or invalid value for `parameter' on line number of the configuration file. This entry will be ignored. Correct the line specified in the configuration file before continuing.BINDExplanation: The configuration file contains a configuration keyword that has an invalid parameter or that does not specify a parameter. This invalid line will be ignored by the configuration process.Action: Because this line will be ignored, no action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the message.PAGENUM=119 ID="BP113"43: There is a missing or invalid ON/OFF value for `parameter' on line number of the configuration file. This entry will be ignored. Correct the line specified in the configuration file before continuing.BINDExplanation: The configuration file contains a configuration keyword that is defined to use an "ON" or "OFF" parameter, but a different parameter or no parameter has been specified. This invalid line will be ignored by the configuration process.Action: Because this line will be ignored, no action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the message.45: The parameter specified for the following option was out of range and has been adjusted.BINDExplanation: A configurable parameter has been configured too high or too low to be valid. The parameter is specified on the line following the message.Action: Correct the parameter specified in the NET.CFG file. For information on the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.PAGENUM=120 ID="BP114"BOOTPFWD1: Failed: BootP request dropped. The hop count number exceeded the maximum allowed number. BOOTPFWDExplanation: The BootP request could not be forwarded any further on this internetwork. The maximum hop count was exceeded.Action: Install a BootP server on this network or on a network closer to the BootP client making the request.2: Failed: Attempt to forward BootP packet failed. Error code: code. BOOTPFWDExplanation: The BootP forwarder could not forward the packet. The "send to" call to BSD sockets failed. The error code indicates the error return from the "send to" call. Action: This is usually a temporary condition. If the problem persists, contact your Novell Authorized Reseller.5: Warning: ARP cache update failed.BOOTPFWDExplanation: The BootP forwarder tried to store the address in its ARP cache. It was unable to do so. The server may not have enough available memory. BootP continues to operate.Action:  If possible, release memory to the forwarder so it can maintain the ARP cache. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. 6: Received packet contained an unrecognized BOOTP operation code: code.BOOTPFWDExplanation: The BootP forwarder received an unknown packet. Some other BootP is sending bad packets. Action: Determine where the bad packet originated from and correct that BootP forwarder.7: Insufficient memory to add server. BOOTPFWDExplanation: The BootP forwarder was unable to allocate memory to add the server to its list of BootP servers. The server may not have enough available memory.Action:  Release some memory to allow the forwarder to operate with a full list of servers. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.PAGENUM=121 ID="BP115"8: Unable to resolve server name: name. BOOTPFWDExplanation: The destination server name in the BootP packet could not be resolved to an IP address. The forwarder must know the address of the BootP server to forward requests. Action: Make sure you use the correct server name. If necessary, use INETCFG to input a new server name. For information on INETCFG, see "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference.9: Load command ignored. The `Server' parameter must be specified. BOOTPFWDExplanation: The BootP forwarder must know the name of a BootP server that can handle BootP requests. The forwarder does not load without a valid server. Action: Use INETCFG to create a list of BootP servers available to the BOOTPFWD.NLM file. For information on INETCFG, see "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference.10: Unable to open file: filename. Error description: code. BOOTPFWDExplanation: The BootP forwarder was unable to open the indicated log file. The error is the return code from the "open" call. Action: If you want BOOTPFWD to log its messages, determine the reason for the failure and correct it.11: Activity will be logged to screen.BOOTPFWDExplanation: This is an informational message indicating that the BootP forwarder logs its activity to the screen. Action: None. This message is for information only. If you do not want this level of logging, use INETCFG to turn off logging, or unload BOOTPFWD and reload it without the -log parameter. For information on INETCFG, see "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference.12: Could not create screen. Error description: code.BOOTPFWDExplanation: The BootP forwarder could not open a screen to log its messages. The server may not have enough available memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. 14: Unable to register BOOTP port. Error code: code. BOOTPFWDExplanation: The BootP forwarder could not open the port required to run. The error code is the return code for an internal routine. Action: Contact your Novell Authorized Reseller. PAGENUM=122 ID="BP116"15: Unrecognized BOOTP parameter: `name'. BOOTPFWDExplanation: The BootP forwarder did not recognize the indicated parameter on the load line. The forwarder only accepts the following parameters: Log, File, and Server.Action:  Use INETCFG to build the BOOTPFWD load line. For information on INETCFG, see "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference.16: BOOTPFWD accepts the following parameters: Log, File, and Server.BOOTPFWDExplanation: The BootP forwarder detected some invalid parameters on the command line and is indicating its set of valid parameters. Action: Use INETCFG to set the BOOTPFWD parameters. For information on INETCFG, see "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference.20: Load command ignored. The maximum number of servers number has already been added. BOOTPFWDExplanation: The BootP forwarder can be loaded multiple times to specify additional BootP servers. The current BootP forwarder has reached its maximum. Action: Use INETCFG to build the table of servers. For information on INETCFG, see "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference.21: Unable to allocate ECB.BOOTPFWDExplanation: The BootP forwarder could not allocate an ECB to forward the request. This indicates that the server is low on ECBs or out of memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Event Control Block Allocation Errors" in Supervising the Network. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.PAGENUM=123 ID="BP117"BTRIEVESee "BOOK="btrv_enu" COLLECTION="nw41"Status Codes and Messages" in Btrieve Installation and Operation.PAGENUM=124 ID="BP118"CAPTURE101, 103, 121, 122, 130, 132, and 133: Message.CAPTUREAction: Follow the actions specified in the message. If the problem persists, contact your Novell Authorized Reseller.134: Your station is not approved to attach to NetWare server name using this user account. The supervisor has limited the stations that are allowed to attach to this server.CAPTUREAction: None. This message is for information only.135: NetWare server name does not allow you to attach during an unauthorized time period. The supervisor has limited the times that this account can be accessed.CAPTUREAction: None. This message is for information only.136, 137,139, 140, 142, 153, 157, and 162: Message.CAPTUREAction: Follow the actions specified in the message. If the problem persists, contact your Novell Authorized Reseller.163: This workstation does not have enough memory to run CAPTURE.CAPTUREExplanation: This workstation does not have enough available memory. This utility requires a minimum of from 235 KB to 275 KB of memory. Note: Execution time increases if limited memory is available.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network.200, 201, 210, 211, 219, 220, and 221: Message.CAPTUREAction: Conform to the specifications in the message.222: The form name, name, could not be found. Default values were used.CAPTUREAction: None. This message is for information only.224: The form supplied was not in the forms database. Default values were used.CAPTUREAction: None. This message is for information only.225, 226, 227, and 228: Message.CAPTUREAction: Conform to the specifications in the message.PAGENUM=125 ID="BP119"229: The job configuration contains a form that does not exist.CAPTUREExplanation: The form specified in the print job configuration may have been deleted.Action: Modify the print job configuration to specify a form that exists. Or, specify the form on the command line using the Form= command. For more information on specifying forms in print job configurations, see "BOOK="printenu" COLLECTION="nw41"Setting Up and Servicing Print Servers" in Print Services.230 and 231: Message.CAPTUREAction: Follow the actions specified in the message. If the problem persists, contact your Novell Authorized Reseller.232: A printer name is required with the printer option.CAPTUREAction: Conform to the specifications in the message.233 and 234: Message.CAPTUREAction: Follow the actions specified in the message. If the problem persists, contact your Novell Authorized Reseller.240, 241, and 242: Message.CAPTUREAction: Conform to the specifications in the message.251, 252, 254, 255, 256, and 298: Message.CAPTUREAction: Follow the actions specified in the message. If the problem persists, contact your Novell Authorized Reseller.400: Your password on NetWare server name has been changed.CAPTUREAction: None. This message is for information only.401, 402, 403, 404, 405, 450, 451,453, 454, 455, 500, 501, 503, 504, 505, 506, 507, 600, 601, 602, 603, 604, 605, 606, 607, 608, 609, 611, 612, 614, 615, 616, and 700: Message.CAPTUREAction: Follow the actions specified in the message. If the problem persists, contact your Novell Authorized Reseller.906: The Unicode files cannot be found.CAPTUREAction: See message IDREF="FM78951""906: The Unicode files cannot be found." in Appendix C.PAGENUM=126 ID="BP120"917: This utility was unable to set the context.CAPTUREAction: See message IDREF="FM32126""917: This utility was unable to set the context." in Appendix C.918: This utility is trying to access an invalid context.CAPTUREExplanation: This error occurs while performing CAPTURE S=server J=job.Action: Omit S=server or J=job from the command line.921: Either the supervisor has locked the bindery or volume SYS: is not mounted on server name.CAPTUREAction: See message IDREF="FM49837""921: Either the supervisor has locked the bindery or volume SYS: is not mounted." in Appendix C.922: Intruder detection lockout has disabled this account.CAPTUREAction: See message IDREF="FM41618""922: Intruder detection lockout has disabled this account." in Appendix C.923: An unexpected error has occurred. codeCAPTUREAction: See message IDREF="FM30182""923: An unexpected error has occurred. Error code: code." in Appendix C.PAGENUM=127 ID="BP121"CLIB001: Assertion failed: assertion, file name, line number. An internal system error has occurred. The NLM's author has requested that this notification be generated based on a specific condition.CLIBExplanation: This is an internal error.Action: Contact this NLM program's vendor or contact your Novell Authorized Reseller.009: This version of CLIB.NLM will run only on NetWare version 4.x or later. Please obtain the correct version before attempting to load CLIB.NLM.CLIBExplanation: This copy of CLIB is incompatible with the currently running version of NetWare.Action: Make sure that you are using the latest version of CLIB. If the problem persists, contact your Novell Authorized Reseller.010: CLIB was unable to set up the coprocessor emulator. An internal system error has occurred. The floating point coprocessor (hardware) may not have been installed.CLIBExplanation: CLIB attempted to set up math coprocessor emulation based on existing hardware, including a floating-point coprocessor, installed in the computer. Since this coprocessor could not be found, CLIB (the math library MATHLIB.NLM or MATHLIBC.NLM) cannot perform floating-point calculations for its clients.Action: Contact this NLM program's vendor or contact your Novell Authorized Reseller.011: CLIB failed to allocate an internal memory resource tag. There may not be enough server memory, or server memory may be corrupted.CLIBExplanation: A call to AllocateResourceTag() failed. CLIB cannot load at this time due to memory constraints.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.012: CLIB failed to allocate its local semaphore timer resource tag. There may not be enough server memory, or server memory may be corrupted.CLIBExplanation: A call to AllocateResourceTag() failed. CLIB cannot load at this time due to memory constraints.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.PAGENUM=128 ID="BP122"013: RegisterTrackedResource for Service Advertising failed, (rc=number). An internal system error has occurred. There may not be enough server memory, or server memory may be corrupted.CLIBExplanation: A call to RegisterTrackedResource() failed. CLIB cannot load at this time due to memory constraints.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.014: RegisterTrackedResource function for BSD Sockets failed (rc=number). An internal system error has occurred. There may not be enough server memory, or server memory may be corrupted.CLIBExplanation: A call to RegisterTrackedResource() failed. CLIB cannot load at this time due to memory constraints.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.015: RegisterTrackedResource function for Remote Server Sessions failed (rc=number). An internal system error has occurred. There may not be enough server memory, or server memory may be corrupted.CLIBExplanation: A call to RegisterTrackedResource() failed. CLIB cannot load at this time due to memory constraints.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.016: The NLM header cannot be read. An internal system error has occurred. This error may indicate an incorrectly linked copy of CLIB.NLM.CLIBExplanation: The CLIB's header format is incorrect and cannot be loaded.Action: Make sure that you are using the latest version of CLIB. If the problem persists, contact your Novell Authorized Reseller.017: CLIB was unable to register this NLM with Network Management. There may be no NetWare management agent NLM present.CLIBExplanation: The Network Management agent (an NLM running on the server) responsible for gathering statistics on a software module was not available or did not respond to CLIB's attempt to register. CLIB will continue to perform correctly, although Network Management will be unable to gather statistics on CLIB.Action: Contact this NLM program's vendor or contact your Novell Authorized Reseller.PAGENUM=129 ID="BP123"018: CLIB is unable to set up its branch table. There may not be enough server memory, or server memory may be corrupted.CLIBExplanation: CLIB failed to set up its OS branch tables. CLIB cannot load at this time due to memory constraints.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.019: CLIB failed to allocate a branch table resource tag. There may not be enough server memory, or server memory may be corrupted.CLIBExplanation: A call to AllocateResourceTag() failed. CLIB cannot load at this time due to memory constraints.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.020: An internal Semaphore Timer error has occurred. CLIB's internal Semaphore data structures have been corrupted.CLIBExplanation: Internal data files are corrupted.Action: Contact this NLM program's vendor, or contact your Novell Authorized Reseller.022: An error occurred loading the NLM with the /P or /V option. There was insufficient server memory available.CLIBExplanation: A call to Alloc() failed. CLIB cannot load at this time due to memory constraints.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.023: An invalid namespace was specified using the /N option. Only the namespace strings "DOS," "MAC," "NFS," "FTAM" and "OS2" are valid.CLIBExplanation: You specified an invalid namespace with the /N option.Action: Try again, using valid name space syntax. If the problem persists, contact this NLM program's vendor or contact your Novell Authorized Reseller.024: Login using the /S option loading CLIB failed: rc = number. An incorrect username or password may have been used in the login process.CLIBExplanation: This message may have appeared because an incorrect username or password was used. This error also may be due to a hardware, cabling, or insufficient memory problem.PAGENUM=130 ID="BP124"Action: Try the login again, making sure the username and password are valid. Check the hardware and cabling. If the error occurs due to a memory problem on the server, see "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. If the problem persists, contact this NLM program's vendor or contact your Novell Authorized Reseller.026: An internal system error has occurred. This is a special version of CLIB with stack checking. The system stack has overflowed during a call to a CLIB function.CLIBExplanation: This NLM uses a thread whose stack is too small. A different version of this NLM must be used.Action: Contact this NLM program's vendor or contact your Novell Authorized Reseller.027: This NLM requires that MATHLIB.NLM or MATHLIBC.NLM be loaded. Please load one of the two NLMs listed.CLIBExplanation: The NLM requiring math functionality did not cause either MATHLIB.NLM or MATHLIBC.NLM to autoload when it was loaded.Action: Load one of the two NLMs noted. If the problem persists, contact this NLM program's vendor or contact your Novell Authorized Reseller.028: An error has occurred in CLIB: CLIBExplanation: This NLM made an invalid call. A different version of this NLM must be used.Action: Contact this NLM program's vendor or contact your Novell Authorized Reseller.029: Abort has been called by a non-CLIB NLM, PCB=value.CLIBExplanation: This NLM made an invalid call. A different version of this NLM must be used.Action: Contact this NLM program's vendor or contact your Novell Authorized Reseller.030: Abort has been called by a non-CLIB NLM.CLIBExplanation: This NLM made an invalid call. A different version of this NLM must be used.Action: Contact this NLM program's vendor or contact your Novell Authorized Reseller.031: ABNORMAL NLM TERMINATION in: NLM name. An internal system error has occurred. It will be necessary to reload this NLM.CLIBExplanation: This is an internal error.Action: Reload the NLM. If the error persists, contact this NLM program's vendor or contact your Novell Authorized Reseller.PAGENUM=131 ID="BP125"032: An invalid thread (thread = value, NLMID = value) has been passed to _DestroyThread.CLIBExplanation: This NLM made an invalid call. A different version of this NLM must be used.Action: Contact this NLM program's vendor or contact your Novell Authorized Reseller.033: An invalid thread (value, not linked to thread group value) has been passed to _DestroyThread.CLIBExplanation: This NLM made an invalid call. A different version of this NLM must be used.Action: Contact this NLM program's vendor or contact your Novell Authorized Reseller.034: A thread's screen was not found as it was being destroyed (value, NLMID=value).CLIBExplanation: This NLM made an invalid call. A different version of this NLM must be used.Action: Contact this NLM program's vendor or contact your Novell Authorized Reseller.035: An error occurred as the stream was being terminated (number, thread=value, handle=value).CLIBExplanation: This is an internal system error.Action: Contact this NLM program's vendor or contact your Novell Authorized Reseller.036: An error occurred as the BSD thread was being terminated (number, thread=value, handle=value).CLIBExplanation: This is an internal system error.Action: Contact this NLM program's vendor or contact your Novell Authorized Reseller.037: The thread was blocked for an unknown reason (block number) during an attempt to destroy the thread (thread value).CLIBExplanation: This is an internal system error.Action: Contact this NLM program's vendor or contact your Novell Authorized Reseller.038: Invalid thread (value, thread group value, NLMID value) passed to _DestroyThreadGroup.CLIBExplanation: This NLM file has an invalid format. A different version of this NLM must be used.Action: Contact this NLM program's vendor or contact your Novell Authorized Reseller.PAGENUM=132 ID="BP126"039: A non-CLIB NLM (PCB value) called exit().CLIBExplanation: This NLM file has an invalid format. A different version of this NLM must be used.Action: Contact this NLM program's vendor or contact your Novell Authorized Reseller.040: A non-CLIB NLM (PCB value) called _exit().CLIBExplanation: This NLM file has an invalid format. A different version of this NLM must be used.Action: Contact this NLM program's vendor or contact your Novell Authorized Reseller.041: ExitThread() was called with old style parameters (number, number). Program name must be recompiled.CLIBExplanation: This NLM file has an invalid format. A different version of this NLM must be used.Action: Contact this NLM program's vendor or contact your Novell Authorized Reseller.042: A non-CLIB NLM (PCB value) called ExitThread().CLIBExplanation: This NLM file has an invalid format. A different version of this NLM must be used.Action: Contact this NLM program's vendor or contact your Novell Authorized Reseller.043: An invalid call was made to ExitThread(). No threads exist (PCB value, TGCS value).CLIBExplanation: This NLM file has an invalid format. A different version of this NLM must be used.Action: Contact this NLM program's vendor or contact your Novell Authorized Reseller.044: A bad parameter (action_code number) was passed to ExitThread() (PCB=value).CLIBExplanation: This NLM file has an invalid format. A different version of this NLM must be used.Action: Contact this NLM program's vendor or contact your Novell Authorized Reseller.046: The NLM header cannot be read. An internal system error has occurred.CLIBExplanation: This NLM file has an invalid format. A different version of this NLM must be used.Action: Contact this NLM program's vendor or contact your Novell Authorized Reseller.PAGENUM=133 ID="BP127"047: An invalid description length was encountered in the NLM header. The description length is too long.CLIBExplanation: This NLM file has an invalid format. A different version of this NLM must be used.Action: Contact this NLM program's vendor or contact your Novell Authorized Reseller.048: The NLM header cannot be read. An internal system error has occurred.CLIBExplanation: This NLM file has an invalid format. A different version of this NLM must be used.Action: Contact this NLM program's vendor or contact your Novell Authorized Reseller.049: An invalid screen name length was encountered in the NLM header. An internal system error has occurred.CLIBExplanation: This NLM file has an invalid format. A different version of this NLM must be used.Action: Contact this NLM program's vendor or contact your Novell Authorized Reseller.050: CLIB failed to allocate a small memory allocations resource tag. An internal system error has occurred.CLIBExplanation: A call to AllocResourceTag() failed. This NLM cannot be loaded at this time due to memory constraints.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.051: CLIB failed to allocate the NLM Control structure memory. An internal system error has occurred.CLIBExplanation: A call to Alloc() failed. This NLM cannot be loaded at this time due to memory constraints.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.052: CLIB failed to allocate the Command Line memory. An internal system error has occurred.CLIBExplanation: A call to Alloc() failed. This NLM cannot be loaded at this time due to memory constraints.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.PAGENUM=134 ID="BP128"053: CLIB failed to allocate the AES resource tag. An internal system error has occurred.CLIBExplanation: A call to AllocResourceTag() failed. This NLM cannot be loaded at this time due to memory constraints.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.054: CLIB failed to allocate the Connection resource tag. An internal system error has occurred.CLIBExplanation: A call to AllocResourceTag() failed. This NLM cannot be loaded at this time due to memory constraints.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.055: CLIB failed to allocate the NonMovableCache memory resource tag. An internal system error has occurred.CLIBExplanation: A call to AllocResourceTag() failed. This NLM cannot be loaded at this time due to memory constraints.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.056: CLIB failed to allocate the SemiPerm memory resource tag. An internal system error has occurred.CLIBExplanation: A call to AllocResourceTag() failed. This NLM cannot be loaded at this time due to memory constraints.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.057: CLIB failed to allocate the Process resource tag. An internal system error has occurred.CLIBExplanation: A call to AllocResourceTag() failed. This NLM cannot be loaded at this time due to memory constraints.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.058: CLIB failed to allocate the Semaphore resource tag. An internal system error has occurred.CLIBExplanation: A call to AllocResourceTag() failed. This NLM cannot be loaded at this time due to memory constraints.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.PAGENUM=135 ID="BP129"059: CLIB failed to allocate the Streams resource tag. An internal system error has occurred.CLIBExplanation: A call to AllocResourceTag() failed. This NLM cannot be loaded at this time due to memory constraints.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.060: CLIB failed to allocate the Task resource tag. An internal system error has occurred.CLIBExplanation: A call to AllocResourceTag() failed. This NLM cannot be loaded at this time due to memory constraints.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.061: CLIB failed to allocate the Timer resource tag. An internal system error has occurred.CLIBExplanation: A call to AllocResourceTag() failed. This NLM cannot be loaded at this time due to memory constraints.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.062: CLIB failed to allocate the Screen resource tag. An internal system error has occurred.CLIBExplanation: A call to AllocResourceTag() failed. This NLM cannot be loaded at this time due to memory constraints.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.063: An invalid thread name was encountered in the NLM header. Thread name too long.CLIBExplanation: This NLM file has an invalid format. A different version of this NLM must be used.Action: Contact this NLM program's vendor or contact your Novell Authorized Reseller.064: CLIB failed to allocate the argv memory. An internal system error has occurred.CLIBExplanation: A call to Alloc() failed. This NLM cannot be loaded at this time due to memory constraints.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.065: CLIB failed to create the NLM's screen. An internal system error has occurred.CLIBExplanation: CLIB failed to create an operating system screen for this NLM. This NLM cannot be loaded at this time due to memory constraints.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.PAGENUM=136 ID="BP130"066: CLIB failed to allocate screen memory. An internal system error has occurred.CLIBExplanation: A call to Alloc() failed. This NLM cannot be loaded at this time due to memory constraints.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.067: CLIB failed to allocate the connection Tasks. An internal system error has occurred.CLIBExplanation: A call to AllocateConnectionTasks() failed. This NLM cannot be loaded at this time due to memory constraints.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.068: CLIB failed to create the NLM's thread group. An internal system error has occurred.CLIBExplanation: A call to CreateTGCS() failed. This NLM cannot be loaded at this time due to memory constraints.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.069: CLIB failed to start the NLM in BeginThread(). An internal system error has occurred.CLIBExplanation: A call to BeginThread() failed. This NLM cannot be loaded at this time due to memory constraints.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.070: CLIB failed to allocate the Screen resource tag. An internal system error has occurred.CLIBExplanation: A call to AllocateResourceTag() failed. This NLM cannot be loaded at this time due to memory constraints.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.PAGENUM=137 ID="BP131"COLORPAL010: An error occurred while reading or writing the overlay file.COLORPALExplanation: This error indicates a hardware or an operating system error.Action: Try running the program again. If the error recurs, something is wrong with the operating system or the workstation's disk drive; contact your Novell Authorized Reseller.020: You do not have sufficient rights to save changes to the overlay file.COLORPALExplanation: The overlay file is in an area where you have only Scan and Read rights, or the overlay file has the Read Only attribute set.Action: Check your rights in the area where the overlay file resides. Also check the Read Write attribute of the overlay file itself. If you do not have rights, have them changed, or place the overlay file in a search path (locally or on the network). The search algorithm is as follows: (1) search the current working directory, (2) search the directories listed in the path environment variable, and (3) search the directory from where the utility started.030: The overlay file is the wrong version and must be updated.COLORPALExplanation: COLORPAL checks the overlay file for 10 monochrome and 10 color palettes. If the number of palettes is more or less than 10, COLORPAL will fail. Old overlays had only one monochrome palette by default, but users could extend the number of palettes beyond 10. They cannot do so with the current version.Action: Use the most recent overlay file.577: The message file found (utility_name.MSG) is an incorrect version. The correct version is number. See your network supervisor for assistance.COLORPALAction: See message IDREF="FM91957""998: The message file found (utility_name.MSG) is an incorrect version. The correct version is number. See your network supervisor for assistance." in Appendix C.999: This utility cannot find the message file (COLORPAL.MSG).COLORPALAction: See message IDREF="FM69424""999: The message file for this utility cannot be found." in Appendix C.PAGENUM=138 ID="BP132"CONLOG1: name is not recognized as either affirmative or negative. Please use `Yes' or `No' as the argument to the name parameter.CONLOGExplanation: The indicated parameter requires a "Yes" or "No" argument.Action:  Reload CONLOG with a valid parameter value. See "BOOK="utlrfenu" COLLECTION="nw41"CONLOG" in Utilities Reference.2: Ignoring the ambiguous parameter name.CONLOGExplanation: Two parameters on the load line are ambiguous. Each parameter name must include enough characters to be unique.Action: Reload CONLOG with the parameters spelled out enough to be unique. See "BOOK="utlrfenu" COLLECTION="nw41"CONLOG" in Utilities Reference.3: Ignoring the unrecognized parameter name.CONLOGExplanation: The indicated parameter is not a valid CONLOG parameter. CONLOG accepts the following parameters: HELP, FILE, SAVE, ENTIRE, and MAXIMUM.Action: Reload CONLOG with a valid command line. See "BOOK="utlrfenu" COLLECTION="nw41"CONLOG" in Utilities Reference.4: `name' is a duplicate parameter. Overriding previous name parameter.CONLOGExplanation: The indicated parameter appears twice on the load line. CONLOG uses the second setting.Action: If the second parameter value is correct, no action is required. 5: Cannot register for screen events.CONLOGExplanation: CONLOG could not get messages from the screen. This usually indicates that the server is low on memory or heavily loaded.Action: Use NetWare Administrator or MONITOR to determine what memory might be freed. For information, see "BOOK="utlrfenu" COLLECTION="nw41"NetWare Administrator" in Utilities Reference or "BOOK="utlrfenu" COLLECTION="nw41"MONITOR" in Utilities Reference. Free the memory. For information, see "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. Reload CONLOG. For information, see "BOOK="utlrfenu" COLLECTION="nw41"CONLOG" in Utilities Reference.6: Cannot get memory for screen logging.CONLOGExplanation: CONLOG cannot get enough memory to get the messages from the screen.Action: Use NetWare Administrator or MONITOR to determine what memory might be freed. See "BOOK="utlrfenu" COLLECTION="nw41"NetWare Administrator" or "BOOK="utlrfenu" COLLECTION="nw41"MONITOR" in Utilities ReferencePAGENUM=139 ID="BP133". Free the memory. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. Reload CONLOG. See "BOOK="utlrfenu" COLLECTION="nw41"CONLOG" in Utilities Reference.7: Cannot open filename: error text.CONLOGExplanation: CONLOG could not write the console messages to the log file, so CONLOG exited. The error text provides an explanation of why the write failed. Action: Determine and correct the reason for failure. If necessary, reboot the server. Reload CONLOG.8: Write to system console log failed: error text.CONLOGExplanation: CONLOG could not write the console messages to the log file, so CONLOG exited. The error text provides an explanation of why the write failed. Action: Determine and correct the reason for failure. If necessary, reboot the server. Reload CONLOG. See "BOOK="utlrfenu" COLLECTION="nw41"CONLOG" in Utilities Reference.12: Cannot get semaphore for screen logging.CONLOGExplanation: CONLOG could not get a semaphore required to capture messages from the console. This usually means the server is very low on resources.Action: Increase the available memory. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. Reload CONLOG. See "BOOK="utlrfenu" COLLECTION="nw41"CONLOG" in Utilities Reference.13: Cannot save filename to backup filename. Overwriting.CONLOGExplanation: CONLOG could not create a backup copy of its log file. It is overwriting the existing log file.Action: None. This message is for information only. If you want the backup copy, make sure there is disk space available on the volume. For information, see "BOOK="superenu" COLLECTION="nw41"Resolving Server Disk Space Problems" in Supervising the Network.21: Could not parse number for name parameter. Character number token unrecognized in `name'.CONLOGExplanation: CONLOG expects a number as a value for the indicated parameter. The given value was not a number.Action: Reload CONLOG with the corrected value. See "BOOK="utlrfenu" COLLECTION="nw41"CONLOG" in Utilities Reference.PAGENUM=140 ID="BP134"23: Filename exceeded number kilobyte limit. Restarting log.CONLOGExplanation: The log file exceeded the maximum size. CONLOG is restarting the log file as if you had reloaded CONLOG.Action: None. This message is for information only.24: Could not get messages. Using English.CONLOGExplanation: CONLOG could not find the correct message file (CONLOG.MSG) for the current language. English messages are used as the default.Action: Place the language version of the CONLOG.MSG file in the SYS:SYSTEM/NLS/language_designator directory.PAGENUM=141 ID="BP135"CONN1: The message file name is invalid. The program cannot be loaded.CONNExplanation: The .MSG file is invalid. This problem could be the result of a corrupted file, a bad translation, or an outdated file version.Action: Either update the .MSG file with a valid copy or delete the file. The DOS Requester will use the default messages that are bound to the binary files.5: Module1.VLM is not loaded. The module2.VLM file cannot be loaded before module1.VLM. Load the module1.VLM file first, then try to load the module2.VLM file.CONNExplanation: The module2.VLM requires that the module1.VLM be loaded first. Either the current configuration has module1.VLM and module2.VLM loading out of order, or module1.VLM did not load successfully.Action: Make sure that module1.VLM is configured to load before module2.VLM. To do this, change the load order of the "VLM=" parameter in the NET.CFG file. For information on the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.7: In order to load the module3.VLM, one of the following VLMs must be loaded: module1.VLM, module2.VLM.CONNExplanation: The module3.VLM requires that module1.VLM or module2.VLM be loaded first. Either the current configuration has module3.VLM loading before the modules in the module1.VLM or module2.VLM list, or module1.VLM or module2.VLM did not load successfully.Action: Make sure that module1.VLM or module2.VLM loads successfully before module3.VLM.42: There is a missing or invalid value for `parameter' on line number of the configuration file. This entry will be ignored. Correct the line specified in the configuration file before continuing.CONNExplanation: The configuration file contains a configuration keyword that has an invalid parameter or that does not specify a parameter. This invalid line will be ignored by the configuration process.Action: Because this line will be ignored, no action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the message.PAGENUM=142 ID="BP136"43: There is a missing or invalid ON/OFF value for `parameter' on line number of the configuration file. This entry will be ignored. Correct the line specified in the configuration file before continuing.CONNExplanation: The configuration file contains a configuration keyword that is defined to use either an "On" or "Off" parameter, but a different parameter or no parameter has been specified. This invalid line will be ignored by the configuration process.Action: Because this line will be ignored, no action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message.45: The parameter specified for the following option was out of range and has been adjusted.CONNExplanation: A configurable parameter has been configured too high or too low to be valid. The parameter is specified on the line following the message.Action: Correct the parameter specified in the NET.CFG file. For information on the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.50: DOS version is not 3.1 or later. The NetWare Requester for DOS cannot be loaded. Reboot your computer with DOS 3.1 or later; then load the NetWare Requester for DOS files.CONNExplanation: The DOS Requester requires DOS version 3.1 or later to operate. The current DOS version is not 3.1 or later, so the DOS Requester cannot be loaded.Action: Upgrade the DOS version on your machine to 3.1 or later.51: An older version of the shell is loaded. The NetWare Requester for DOS cannot be loaded. Unload the shell; then load the NetWare Requester for DOS files.CONNExplanation: The DOS Requester cannot be loaded with the NetWare shell. The NetWare shell has been loaded in your machine. Action: Type NETX /U to unload the NetWare shell. For NetWare shell compatibility, use NETX.VLM rather than loading the NetWare shell. You can load NETX.VLM automatically by including it in the NET.CFG file under the NetWare DOS Requester section heading. If the version of the NetWare shell in use does not support the /U parameter, reboot the machine without loading the NetWare shell. For information about the NetWare shell and NET.CFG, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.PAGENUM=143 ID="BP137"52: The NetWare DOS Named Pipes Extender is currently loaded. The NetWare Requester for DOS cannot be loaded. Unload the NetWare DOS Named Pipes Extender; then load the NetWare Requester for DOS files.CONNExplanation: The DOS Requester cannot be loaded after the NetWare DOS Named Pipes Extender. The NetWare DOS Pipes Extender has been loaded in this machine. To use both the DOS Requester and NetWare DOS Named Pipes Extender, load the DOS Requester before the DOS Named Pipes Extender.Action: Type "DOSNP /U" to unload the DOS Named Pipes Extender; then load the DOS Requester before reloading the DOS Named Pipes Extender. For information on the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.PAGENUM=144 ID="BP138"CX120: Control characters are not allowed in the command line.CXExplanation: Control character input is not allowed as a CX parameter. (Note: MOREINFO="NONE"<Ctrl>+<C> and MOREINFO="NONE"<Ctrl>+<Break> abort the CX command.)Action: Retry the command without using control characters in parameters. See "BOOK="utlrfenu" COLLECTION="nw41"CX" in Utilities Reference.215: The context you are trying to change to is invalid. Your current context will be left unchanged.CXExplanation: After getting a context handle, CX encountered an error when it tried to set the desired context. CX has terminated.Action: Make sure that you are using a valid context; then try again. See "BOOK="utlrfenu" COLLECTION="nw41"CX" in Utilities Reference.220: An error occurred during CX's attempt to create the context.CXExplanation: CX could not create a context handle. The library call NWCreateContext () failed because of insufficient memory; CX has terminated.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network, then try again. If the problem persists, contact your Novell Authorized Reseller.230: An error occurred during CX's attempt to get the object name.CXExplanation: For some reason, CX could not get general information about a directory object. CX has terminated.Action: Try again, making sure that you are specifying a valid object. If the problem persists, contact your Novell Authorized Reseller.240: The context you want to change to does not exist. You tried to change to: name. Your context will be left unchanged as: name.CXExplanation: The context you specified must exist in the NetWare Directory Services database before a user can use it. The context does not exist, so CX has terminated.Action: Make sure that you are specifying a valid context. For information, see "BOOK="utlrfenu" COLLECTION="nw41"CX" in Utilities Reference.PAGENUM=145 ID="BP139"242: The specified context does not exist.CXExplanation: The context you specified must exist in the NetWare Directory Services database before a user can use it. The context does not exist, so CX has terminated.Action: Make sure that you are specifying a valid context. For information, see "BOOK="utlrfenu" COLLECTION="nw41"CX" in Utilities Reference.244: The current context is invalid: context name. CXExplanation: NetWare Directory Services allows you to set a default context in the NET.CFG file (NAME CONTEXT=). This message probably indicates that the context specified during login does not match the context specified in NET.CFG. Another possibility is that the context was once valid, but it has since been removed from the Directory tree.Action: Type "CX /T" to determine if the context is still in the Directory tree and if it is valid. Then specify a valid context by typing "CX /R", or by typing "CX..." with the number of periods needed to remove all containers in your current context. For example, if CX showed your context to be ou=test.o=abc, then you would type "CX...", which removes all containers and leaves you at the root. For information, see "BOOK="utlrfenu" COLLECTION="nw41"CX" in Utilities Reference.246: An error occurred in CX's attempt to list the subordinate objects. Error code: code.CXExplanation: An unexpected error has occurred.Action: Try the operation again. Also be sure that no associated problems have occurred (such as the network going down, a connection being lost, or previous errors having occurred and been ignored). If the problem persists, contact your Novell Authorized Reseller. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 260: An internal system error occurred during CX's attempt to canonicalize the context: (context name).CXExplanation: CX attempted to change the context of a given object, but either it was unable to find the object in the given context, or it was unable to create the path in the Directory tree. This error can also occur if an error has occurred in the program. CX has terminated.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.300: An error occurred during CX's attempt to get the VLM shell context.CXExplanation: The VLM shell contains the workstation's default context designation. For some reason, CX could not get this context and has terminated.Action: Make sure that you have a valid context designated in the workstation's NET.CFG file.PAGENUM=146 ID="BP140"810: This utility cannot allocate sufficient memory for the Directory Services buffer.CXAction: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.826: The VLMs are not loaded.CXExplanation: You attempted to run CX from a client workstation using a NetWare shell file (for example NETX.EXE). CX requires the client workstation to be using VLMs.Action: Unload the NetWare shell file from the workstation and run VLM.EXE. Then retry CX.900: An internal application error has occurred. Error code: codeCXAction: See IDREF="FM61529""Error Codes" in Appendix A.903: The command line syntax is invalid.CXAction: See message IDREF="FM18860""903: The command line syntax is invalid." in Appendix C.906: The Unicode files cannot be found.CXAction: See message IDREF="FM78951""906: The Unicode files cannot be found." in Appendix C.917: This utility was unable to set the context.CXAction: See message IDREF="FM32126""917: This utility was unable to set the context." in Appendix C.920: This utility was unable to allocate <number> bytes of memory.CXAction: See message IDREF="FM30331""920: This utility was unable to allocate number bytes of memory." in Appendix C.970: The attempt to open the Unicode table files failed.CXAction: See message IDREF="FM15675""970: The attempt to open the Unicode table files failed." in Appendix C.971: The workstation does not have enough memory to load the Unicode table files.CXAction: See message IDREF="FM55341""971: The workstation does not have enough memory to load the Unicode table files." in Appendix C.972: Access to the Unicode table files was denied.CXAction: See message IDREF="FM90152""972: Access to the Unicode table files was denied." in Appendix C.PAGENUM=147 ID="BP141"973: The Unicode table files cannot be found in the NLS directory or in the search path. Code page: <number>  Country:  <number>CXAction: See message IDREF="FM62778""973: The Unicode table files cannot be found in the NLS directory or in the search path. Code page: number Country: number" in Appendix C.974: The Unicode table files are corrupt.CXAction: See message IDREF="FM63405""974: The Unicode table files are corrupt." in Appendix C.975: The Unicode table files cannot be opened because there are already too many open files. Close some files or modify your CONFIG.SYS file.CXAction: See message IDREF="FM49793""975: The Unicode table files cannot be opened because there are already too many open files. Close some files or modify your CONFIG.SYS file." in Appendix C.998: The message file found (<utility_name>.MSG) is an incorrect version. The correct version is <number>. See your network supervisor for assistance.CXAction: See message IDREF="FM91957""998: The message file found (utility_name.MSG) is an incorrect version. The correct version is number. See your network supervisor for assistance." in Appendix C.999: The message file for this utility cannot be found.CXAction: See message IDREF="FM69424""999: The message file for this utility cannot be found." in Appendix C.PAGENUM=148 ID="BP142"DNWxxxxError messages for the NetWare Client for OS/2 NWOS2.EXE file. The following explanations assume that the NetWare files have been loaded in the default directories, C:\NWOS2 and C:\NETWARE, in all the directory references.DNW0099I: 010101DNWExplanation: This is the version check string. If the server cannot find this string, it aborts the installation. This ensures that you have the correct version of the message file.Action: None. This message is for information only.DNW0100: The program cannot open NetWare for OS/2's Physical Device Driver. Error code: code.DNWExplanation: The NetWare for OS/2 physical device driver, PNETWARE.SYS, has not been loaded.Action: Make sure that the CONFIG.SYS file contains the following statement:FORMAT="LINESPECIFIC"MOREINFO="NONE"DEVICE=C:\NETWARE\PNETWARE.SYS For more information about the CONFIG.SYS file, see 
BOOK="ws_osenu" COLLECTION="nw41"NetWare Client for OS/2 User Guide. For information on the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. DNW0101: The program cannot open NetWare for OS/2's Virtual Device Driver. Error code: code.DNWExplanation: The NetWare for OS/2 virtual device driver, VNETWARE.SYS, has not been loaded.Action: Make sure that the CONFIG.SYS file contains the following statement:FORMAT="LINESPECIFIC"MOREINFO="NONE"DEVICE=C:\NETWARE\VNETWARE.SYS For more information about the CONFIG.SYS file, see 
BOOK="ws_osenu" COLLECTION="nw41"NetWare Client for OS/2 User Guide. For information on the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. DNW0102: The program cannot initialize NetWare for OS/2's Virtual Device Driver. Error code: code.DNWExplanation: The NetWare for OS/2 virtual device driver VNETWARE.SYS could not be initialized. The machine may not have enough memory, or it may have reached the limit on available system semaphores.Action: Try one or more of the following.PAGENUM=149 ID="BP143"MARK=BULLETRemove or reduce the number of OS/2 applications running.Increase the available memory. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network or "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network.Reinstall NetWare for OS/2. You do not need to reinstall NetWare 4.For information on the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. DNW0103: The program cannot initialize a full screen for NetWare for OS/2. Error code: code.DNWExplanation: Too many screen groups might be in use.Action: Reduce the number of screen groups in use by terminating some of them. Also, try reinstalling NetWare for OS/2. For information on the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. DNW0104: NetWare for OS/2 must be started as a foreground process.DNWExplanation: You attempted to install NetWare for OS/2 as a background process.Action: NetWare for OS/2 will run only as a foreground process. Do not attempt to install NetWare for OS/2 in the background using the DETACH command. For more information about background and foreground processes, see "BOOK="ws_osenu" COLLECTION="nw41"NET.CFG Options Reference" in the NetWare Client for OS/2 User Guide.DNW0105: The program cannot create an Event semaphore. Error code: code.DNWExplanation: OS/2 has no available Event semaphores.Action: Remove or reduce the number of OS/2 applications running. Also try reinstalling NetWare for OS/2. For information on the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. DNW0106: The program cannot create the keyboard handler thread. Error code: code.DNWExplanation: Too many threads are running.Action: Try one or more of the following:MARK=BULLETRemove or reduce the number of OS/2 applications running.Reinstall NetWare for OS/2. You do not need to reinstall NetWare 4.Increase the THREADS environment variable in the CONFIG.SYS file.For information on the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. PAGENUM=150 ID="BP144"DNW0107: The program cannot create the messaging system thread. Error code: code.DNWExplanation: Too many threads are running.Action: Try one or more of the following:MARK=BULLETRemove or reduce the number of OS/2 applications running.Reinstall NetWare for OS/2. You do not need to reinstall NetWare 4.Increase the THREADS environment variable in the CONFIG.SYS file.For information on the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. DNW0108: The program cannot create the screen update thread. Error code: code.DNWExplanation: Too many threads are running.Action: Try one or more of the following:MARK=BULLETRemove or reduce the number of OS/2 applications running.Reinstall NetWare for OS/2. You do not need to reinstall NetWare 4.Increase the THREADS environment variable in the CONFIG.SYS file.. For information on the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. DNW0109: The program cannot create the NetWare for OS/2 server thread. Error code: code.DNWExplanation: Too many threads are running.Action: Try one or more of the following:MARK=BULLETRemove or reduce the number of OS/2 applications running.Reinstall NetWare for OS/2. You do not need to reinstall NetWare 4.Increase the THREADS environment variable in the CONFIG.SYS file.For information on the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. DNW0110: The program cannot create the DOS partition I/O thread. Error code: code.DNWExplanation: Too many threads are running.Action: Try one or more of the following:PAGENUM=151 ID="BP145"MARK=BULLETRemove or reduce the number of OS/2 applications running.Reinstall NetWare for OS/2. You do not need to reinstall NetWare 4.Increase the THREADS environment variable in the CONFIG.SYS file.For information on the specific error code, see IDREF="FM61529""Error Codes" in Appendix A.DNW0111: The program failed while waiting for an Event semaphore. Error code: code.DNWExplanation: This is an internal system error.Action: Contact your Novell Authorized Reseller. For information on the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. DNW0112: The program cannot change the server's thread priority. Error code: code.DNWExplanation: This is an internal system error.Action: Contact your Novell Authorized Reseller. For information on the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. DNW0113: The program cannot load the SERVER.EXE. Error code: code.DNWExplanation: By default, the SERVER.EXE file is installed in the NetWare for OS/2 directory on the boot drive. The SERVER.EXE file is missing from this directory.Action: Reinstall NetWare for OS/2. You do not need to reinstall NetWare 4. For information on the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. DNW0114: The program cannot change the keyboard's thread priority. Error code: code.DNWExplanation: This is an internal system error.Action: Contact your Novell Authorized Reseller. For information on the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. DNW0115: The program cannot lock the read/write buffers.DNWExplanation: This is an internal system error.Action: Contact your Novell Authorized Reseller.DNW0116: The program cannot install ring 3 exception handlers. Error code: code.DNWExplanation: This is an internal system error.Action: Contact your Novell Authorized Reseller. For information on the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. PAGENUM=152 ID="BP146"DNW0117: The program cannot allocate dynamic memory. Error code: code.DNWExplanation: The machine does not have enough memory to run NetWare for OS/2.Action: Try one or more of the following:MARK=BULLETIncrease the available memory. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network or "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network.Reinstall NetWare for OS/2. You do not need to reinstall NetWare 4.For information on the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. DNW0118: Insufficient memory is available to load NetWare for OS/2.DNWExplanation: The machine does not have enough memory to run NetWare for OS/2.Action: Try one or more of the following:MARK=BULLETIncrease the available memory. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network or "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network.Reinstall NetWare for OS/2. You do not need to reinstall NetWare 4.DNW0119: The program cannot find the SERVER.EXE file. The DOS Open function returned error code code.DNWExplanation: By default, the SERVER.EXE file is installed in the NetWare for OS/2 directory on the boot drive. The SERVER.EXE file is missing from this directory.Action: Reinstall NetWare for OS/2. You do not need to reinstall NetWare 4. For information on the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. DNW0120: The machine type cannot be identified.DNWExplanation: The machine type you are using does not support NetWare for OS/2.Action: To get a list of supported machine types, contact your Novell Authorized Reseller.DNW0121: The virtual driver VNETWARE.SYS failed during attempt to open PNETWARE.SYS.DNWExplanation: The NetWare for OS/2 physical device driver, PNETWARE.SYS, has not been loaded.Action: Make sure that the CONFIG.SYS file contains the following statement:FORMAT="LINESPECIFIC"MOREINFO="NONE"DEVICE=C:\NETWARE\PNETWARE.SYS 
PAGENUM=153 ID="BP147" For more information about the CONFIG.SYS file, see 
BOOK="ws_osenu" COLLECTION="nw41"NetWare Client for OS/2 User Guide.DNW0122: The program cannot read the SERVER.EXE. Error code: code.DNWExplanation: By default, the SERVER.EXE file is installed in the NetWare for OS/2 directory on the boot drive. The SERVER.EXE file is missing from this directory.Action: Reinstall NetWare for OS/2. You do not need to reinstall NetWare 4. For information on the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. DNW0123: Unresolved externals were encountered while the server was loading.DNWExplanation: You are using mismatched versions of NetWare for OS/2 and NetWare 4.Action: Reinstall the proper version of NetWare for OS/2.DNW0124: The devhlp call could not set a Timer Handler.DNWExplanation: This is an internal system error.Action: Contact your Novell Authorized Reseller.DNW0125: The program cannot resolve a public record.DNWExplanation: You are using mismatched versions of NetWare for OS/2 and NetWare 4.Action: Reinstall NetWare for OS/2 or contact your Novell Authorized Reseller.DNW0126: The program cannot allocate a server stack.DNWExplanation: There is not enough memory left on the machine to run NetWare for OS/2.Action: Try one or more of the following:MARK=BULLETIncrease the available memory. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network or "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network.Reinstall NetWare for OS/2. You do not need to reinstall NetWare 4.DNW0127: The NetWare for OS/2 loader discovered an invalid relocation record.DNWExplanation: Your NetWare for OS/2 files are probably corrupted.Action: Reinstall NetWare for OS/2. You do not need to reinstall NetWare 4.PAGENUM=154 ID="BP148"DNW0128: NetWare for OS/2 is already running in another session.DNWExplanation: NetWare for OS/2 has already been installed. It can be installed only once per machine.Action: None. This message is for information only.DNW0129: A NetWare for OS/2 server error has occurred.DNWExplanation: This is an internal system error.Action: Contact your Novell Authorized Reseller.DNW0130: The program's attempt to load the server was aborted.DNWExplanation: This is an internal system error.Action: Contact your Novell Authorized Reseller.DNW0131: The program cannot allocate an interrupt stack for the server.DNWExplanation: The machine does not have enough memory to run NetWare for OS/2.Action: Try one or more of the following:MARK=BULLETIncrease the available memory. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network or "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network.Reinstall NetWare for OS/2. You do not need to reinstall NetWare 4.DNW0132: The program cannot allocate shared memory for the server.DNWExplanation: The machine does not have enough memory to run NetWare for OS/2.Action: Try one or more of the following:MARK=BULLETIncrease the available memory. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network or "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network.Reinstall NetWare for OS/2. You do not need to reinstall NetWare 4.DNW0133: The program cannot allocate a timer stack.DNWExplanation: The machine does not have enough memory to run NetWare for OS/2.Action: Try one or more of the following:MARK=BULLETIncrease the available memory. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network or "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network.PAGENUM=155 ID="BP149"Reinstall NetWare for OS/2. You do not need to reinstall NetWare 4.DNW0134: The program cannot initialize server GDTs.DNWExplanation: This is an internal system error.Action: Contact your Novell Authorized Reseller.DNW0135: The program cannot initialize the server stack.DNWExplanation: This is an internal system error.Action: Contact your Novell Authorized Reseller.DNW0136: Insufficient memory is available to load the server.DNWExplanation: You do not have enough memory left on the machine to run NetWare for OS/2.Action: Try one or more of the following:MARK=BULLETIncrease the available memory. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network or "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network.Reinstall NetWare for OS/2. You do not need to reinstall NetWare 4.DNW0137: An invalid external record was detected during attempted server load.DNWExplanation: Your NetWare for OS/2 files are probably corrupted.Action: Reinstall NetWare for OS/2. You do not need to reinstall NetWare 4.DNW0138: An invalid file format was detected in the SERVER.EXE during attempted server load.DNWExplanation: Your NetWare for OS/2 files are probably corrupted.Action: Reinstall NetWare for OS/2. You do not need to reinstall NetWare 4. If the problem persists, contact your Novell Authorized Reseller.DNW0139: An invalid function was passed to VNETWARE.SYS.DNWExplanation: An internal error has occurred. A ring 3 application used an unsupported function code to call VNETWARE.SYS.Action: Contact your Novell Authorized Reseller.PAGENUM=156 ID="BP150"DNW0140: An invalid procedure offset was detected during attempted server load.DNWExplanation: Your NetWare for OS/2 files are probably corrupted.Action: Reinstall NetWare for OS/2. You do not need to reinstall NetWare 4.DNW0141: The server was not loaded; the reason is unknown.DNWExplanation: This is an internal system error.Action: Contact your Novell Authorized Reseller.DNW0142: The program cannot get the system type via a VDH service call.DNWExplanation: This is an internal system error.Action: Contact your Novell Authorized Reseller.DNW0143: The NWOS2.EXE and NWOS2.MSG files are not synchronized.DNWExplanation: You are using mismatched versions of NWOS2.EXE and NWOS2.MSG.Action: Reinstall NetWare for OS/2 or contact your Novell Authorized Reseller.DNW0144: A keyboard thread Kbd focus error has occurred. Error code: code.DNWExplanation: This is an internal system error.Action: Contact your Novell Authorized Reseller. For information on the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. DNW0145: The KbdGetStatus function has returned Error code: code.DNWExplanation: This is an internal system error.Action: Contact your Novell Authorized Reseller. For information on the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. DNW0146: The KbdSetStatus function has returned Error code: code.DNWExplanation: This is an internal system error.Action: Contact your Novell Authorized Reseller. For information on the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. DNW0147: A keyboard thread semaphore error has occurred. Error code: code.DNWExplanation: This is an internal system error.Action: Contact your Novell Authorized Reseller. For information on the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. PAGENUM=157 ID="BP151"DNW0148: The KbdCharIn function returned Error code: code.DNWExplanation: This is an internal system error.Action: Contact your Novell Authorized Reseller. For information on the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. DNW0149: Reset occurred after a debug error. Error code: code.DNWExplanation: This is an internal system error.Action: Contact your Novell Authorized Reseller. For information on the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. PAGENUM=158 ID="BP152"DOMAIN1: An unhandled exception has caused a domain to be quarantined. Exception: description. Domain: name. Process: name. Module: description. EIP: hex number.DOMAINExplanation: A memory protection fault occurred at the location specified in the message. The process causing the fault has been shut down and the domain has been quarantined. This means that any process that calls into the domain will be shut down.Action: Unload all NLM programs in the protected domain, then reload. If the problem persists, contact the NLM vendor.2: A fault occurred while validating pointers in the RPC Layer. API=nameDOMAINExplanation: A memory protection fault occurred while processing the parameters of the named API. Most likely, this means that one of the parameters was not valid. In some cases, the API name isn't known because it is a callback function that was not exported. This alert is always followed by the DOMAIN error message 1 (the preceding message), which gives more information about the call to the API.Action: Unload all NLM programs in the protected domain, then reload them. If the problem persists, contact the NLM vendor.3: The Console Command Processor has been restarted after error recovery.DOMAINExplanation: A memory protection fault occurred during the Console Command process. Normally this would make it impossible to enter console commands. Because DOMAIN.NLM was loaded, the Console Command Processor was restarted and you can still enter console commands.Action: If this error occurred as a result of a LOAD command, unload the NLM and contact the NLM vendor. Otherwise, contact your Novell Authorized Reseller.101: The DOMAIN NLM is unable to allocate resource tags.DOMAINExplanation: During the startup of DOMAIN.NLM, the server didn't have enough memory to allocate resource tags.Action: Since DOMAIN.NLM is supposed to be loaded before any other NLM, add more memory to make the server run properly. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.PAGENUM=159 ID="BP153"102: Domain must be loaded before any other NLM.DOMAINExplanation: DOMAIN.NLM is supposed to be loaded before any other NLM.Action: Bring down the server and exit to DOS. Move the "LOAD DOMAIN" command to the first line of the STARTUP.NCF file and run SERVER.EXE again.103: Domain has already been registered with NetWare.DOMAINExplanation: DOMAIN.NLM has already been loaded (registered) and is being loaded again.Action: Load DOMAIN.NLM only once.104: Versions of Domain and NetWare do not match.DOMAINExplanation: The version of DOMAIN.NLM you are trying to load is not compatible with the NetWare operating system.Action: Copy DOMAIN.NLM from the NetWare 4.1 CD-ROM to the server's volume SYS:, then load DOMAIN.NLM again. If this does not correct the problem, contact your Novell Authorized Reseller to get a compatible version of DOMAIN.NLM.105: The Domain cannot be registered with NetWare.DOMAINExplanation: For internal reasons, this copy of DOMAIN.NLM cannot load on this version of the NetWare operating system. Action: Copy the DOMAIN.NLM from the NetWare 4.1 CD-ROM to the server's volume SYS:, then load DOMAIN.NLM again. If this does not correct the problem, contact your Novell Authorized Reseller to get a compatible version of DOMAIN.NLM.106: Domain is unable to allocate physical pages.DOMAINExplanation: During the startup of DOMAIN.NLM, the server did not have enough memory to allocate physical pages to create the global code or OS_PROTECTED domain.Action: Since DOMAIN.NLM must be loaded before any other NLM, add more memory to make the server run properly. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.107: The Domain NLM ran out of memory.DOMAINExplanation: During the startup of DOMAIN.NLM, the server did not have enough memory to allocate to the module.Action: Since DOMAIN.NLM must be loaded before any other NLM, add more memory to make the server run properly. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.PAGENUM=160 ID="BP154"108: The DOMAIN NLM must be loaded before the second processor.DOMAINExplanation: DOMAIN.NLM must be loaded before any other NLM, including the second processor driver.Action: Down the server. Move the "LOAD DOMAIN" command to the first line of the STARTUP.NCF file and then run SERVER.EXE again.109: Unknown command line option "-option".DOMAINExplanation: DOMAIN.NLM received an unrecognized option on the command line.Action: See "BOOK="utlrfenu" COLLECTION="nw41"DOMAIN" in Utilities Reference for valid command line syntax and parameters, then load DOMAIN.NLM using a valid command. 110: Unknown command line argument "argument".DOMAINExplanation: DOMAIN.NLM received an unrecognized argument on the command line.Action: See "BOOK="utlrfenu" COLLECTION="nw41"DOMAIN" in Utilities Reference for valid command line syntax and parameters, then load DOMAIN.NLM using a valid command. 201: Unable to read the Server RPC descriptions.DOMAINExplanation: The operating system remote procedure call (RPC) data in the SERVER.RPC file has been corrupted.Action: Get a new copy of the SERVER.RPC file.202: The SERVER.RPC description file is incompatible with Domain.DOMAINExplanation: The operating system remote procedure call (RPC) data in the SERVER.RPC file has been corrupted.Action: Get a new copy of the SERVER.RPC file.205: The RPC Loader NLM name is not currently loaded.DOMAINExplanation: The RPC Loader NLM used by this NLM's remote procedure call (RPC) descriptions has not been loaded or has been unloaded. All NLM programs shipped by Novell use NWTIL.NLM and NWTILR.NLM.Action: Load the NWTIL.NLM and NWTILR.NLM files (or the appropriate other RPC loader NLM programs) before loading the NLM that caused this error.PAGENUM=161 ID="BP155"206: Unable to open the RPC description file filename.DOMAINExplanation: The named remote procedure call (RPC) description file could not be found or a disk error occurred while opening it.Action: Get a new copy of the named RPC description file, or restore it from a backup.207: The version of the RPC Loader does not match Domain's version.DOMAINExplanation: The internal version numbers of RPC Loader NLM and DOMAIN.NLM are incompatible. NLM programs shipped by Novell use the NWTIL.NLM and NWTILR.NLM files for the RPC loader.Action: Get new copies of DOMAIN.NLM, SERVER.RPC, NWTIL.NLM, and NWTILR.NLM as necessary.208: The Server RPC description file is incompatible with Domain. Wrong bagfile version: expected version, got version.DOMAINExplanation: The SERVER.RPC file has internal version numbers that do not match those in DOMAIN.NLM.Action: Get new copies of DOMAIN.NLM, SERVER.RPC, NWTIL.NLM, and NWTILR.NLM.301: Out of memory. Domain cannot recover.DOMAINExplanation: The server does not have enough memory to initialize DOMAIN.NLM or to access memory for special uses. This is an unrecoverable error. The server has shut down.Action: Do not use DOMAIN.NLM until you can add more memory to the server. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.404: Domain name does not exist.DOMAINExplanation: The user tried to change the current domain to a domain that does not exist. The only domains that exist in this release are OS and OS_PROTECTED.Action: Use only OS or OS_PROTECTED for domain names.601: Memory deallocation error: size mismatch.DOMAINExplanation: When deallocating memory, DOMAIN.NLM detected a size mismatch.Action: Contact your Novell Authorized Reseller.PAGENUM=162 ID="BP156"602: Memory deallocation error: page not in list.DOMAINExplanation: When deallocating memory, DOMAIN.NLM detected that it was freeing a page it had not allocated.Action: Contact your Novell Authorized Reseller.701: Local Address for symbol symbol name Not Found (hex address).DOMAINExplanation: This copy of DOMAIN.NLM is not synchronized with this version of the NetWare operating system.Action: Get the correct copy of DOMAIN.NLM and reboot the server before installing DOMAIN.NLM.PAGENUM=163 ID="BP157"DSIThis module contains some messages that are not numbered. These message are listed alphabetically after the numbered messages.1: An internal error has occurred. DSI cannot load the message file.DSIExplanation: The NLM was unable to load the message file. This is an internal error.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:MARK=BULLETThe DSI.MSG file if one is in the boot directory (where SERVER.EXE is found).The corresponding SYS:SYSTEM\NLS\X directory on the server.If the problem persists, contact your Novell Authorized Reseller.2: Insufficient memory is available to get a memory resource tag.DSIExplanation: There was insufficient memory for INSTALL to run.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.3: An internal error has occurred. DSI cannot insert a predefined entry. Error description: description.DSIExplanation: An internal system error has occurred.Action: Try the operation again. If the problem persists, contact your Novell Authorized Reseller.4: An internal error has occurred. Predefined entry IDs are out of alignment.DSIExplanation: An internal system error has occurred.Action: Try the operation again. If the problem persists, contact your Novell Authorized Reseller.5: An initialization internal table failure has occurred.DSIExplanation: An internal system error has occurred.Action: Try the operation again. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=164 ID="BP158"6: An internal error has occurred. DSI cannot insert a Schema entry. Error description: description.DSIExplanation: An internal system error has occurred.Action: Try the operation again. If the problem persists, contact your Novell Authorized Reseller.7: An internal error has occurred. DSI cannot insert a property value. Error description: description.DSIExplanation: An internal system error has occurred.Action: Try the operation again. If the problem persists, contact your Novell Authorized Reseller.8: An internal error has occurred. Predefined property IDs are out of alignment.DSIExplanation: An internal system error has occurred.Action: Try the operation again. If the problem persists, contact your Novell Authorized Reseller.9: An internal error has occurred. The class definition is too large.DSIExplanation: An internal system error has occurred.Action: Try the operation again. If the problem persists, contact your Novell Authorized Reseller.10: An internal error has occurred. DSI cannot insert a class entry. Error description: description.DSIExplanation: An internal system error has occurred.Action: Try the operation again. If the problem persists, contact your Novell Authorized Reseller.11: An internal error has occurred. DSI cannot insert a class value. Error description: description.DSIExplanation: An internal system error has occurred.Action: Try the operation again. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=165 ID="BP159"12: An internal error has occurred. Predefined class IDs are out of alignment.DSIExplanation: An internal system error has occurred.Action: Try the operation again. If the problem persists, contact your Novell Authorized Reseller.14: An internal error has occurred. DSI cannot insert predefined partitions. Error description: description.DSIExplanation: An internal system error has occurred.Action: Try the operation again. If the problem persists, contact your Novell Authorized Reseller.15: An internal error has occurred. DSI cannot get time stamps. Error description: description.DSIExplanation: An internal system error has occurred.Action: Try the operation again. If the problem persists, contact your Novell Authorized Reseller.16: The Directory Services context could not create DDSCONTEXT. Error description: description.DSIExplanation: There was insufficient memory for INSTALL to run.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.17: Insufficient memory is available to allocate a buffer. Error description: description.DSIExplanation: There was insufficient memory for INSTALL to run.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.18: An internal error has occurred. This version of DSI does not match the version of Directory Services you are using. DSI version: number. Directory Services version: number.DSIExplanation: An internal system error has occurred.Action: Try the operation again. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=166 ID="BP160"19: DSI cannot create the Directory database. Error description: description.DSIExplanation: Volume SYS: may not be mounted, may be corrupted, or may be out of disk space.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving File I/O Errors" in Supervising the Network.20: The Directory database cannot be opened. Error description: description.DSIExplanation: Volume SYS: may not be mounted, or it may be corrupted.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving File I/O Errors" in Supervising the Network.21: An internal error has occurred. DSI cannot translate a Unicode string to local. You may have a problem with the Unicode translation files. Error description: description.DSIExplanation: An internal system error has occurred.Action: Try the operation again. If the problem persists, contact your Novell Authorized Reseller.23: DSI cannot resolve to the master replica of the partition containing context name. (Error description: description. Make certain that the server containing the master replica of that context is up and on the network before retrying the installation.DSIExplanation: The server containing the master replica of the context may not be visible to this server, or it may be down. The server containing the master replica is typically the one on which the context was initially created.Action: Make sure that the server containing the master replica is running, connected to the network, and visible from workstations. Also, make sure the server you are installing has the proper LAN drivers loaded and is bound to the right network addresses, with the proper frame types.24: An internal error has occurred. DSI cannot generate key pair for "name." Error description: description.DSIExplanation: An internal system error has occurred.Action: Try the operation again. If the problem persists, contact your Novell Authorized Reseller.25: An internal error occurred while DSI was loading system Directory objects.DSIExplanation: An internal system error has occurred.Action: Try the operation again. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=167 ID="BP161"26: DSI cannot open the Directory database. Error description: description.DSIExplanation: Volume SYS: may not be mounted, or it may be corrupted.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving File I/O Errors" in Supervising the Network.27: DSI cannot create external reference to "server". Error description: description.DSIExplanation: DSI probably lost its connection with the server containing the master replica of the container context.Action: Make sure that the server containing the master replica is on the network. Try reinstalling a couple of more times. If the problem persists, contact your Novell Authorized Reseller.28: An internal error has occurred. DSI was unable to add pseudo server values. Error description: description.DSIExplanation: This is an internal error, but it may have been caused by insufficient memory or disk space.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network and "BOOK="superenu" COLLECTION="nw41"Resolving File I/O Errors" in Supervising the Network. If the problem persists, contact your Novell Authorized Reseller.29: The local Directory Services agent cannot be opened. Error description: description.DSIExplanation: The NetWare Directory Services database could not be opened and initialized properly. This could be due to internal errors, a database corruption problem, or excessive network traffic.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving File I/O Errors" in Supervising the Network. Also check external network traffic between this server and other servers in the same Directory tree, minimize traffic as much as possible, then retry the installation. If the problem persists, contact your Novell Authorized Reseller.30: DSI cannot resolve to the master replica of the partition containing context context. Error description: description.DSIExplanation: One of the following has probably occurred:MARK=BULLETThe server containing the master replica of the partition which contains the specified context may not be running.A network connection could not be established to that server.PAGENUM=168 ID="BP162"Action: You may have to use the Partition Manager (PARTMGR.EXE) utility, NetWare Administrator (GUI utility), or PMADMIN (OS/2 utility) to find out which server contains the master replica of the container's partition. Typically, this will be the first server on which this container was specified during installation. Make sure that the server is running and that it is visible from workstations on the network; then retry the installation.31: An attempt to place a replica of the partition on this server failed. The partition that failed is the one that holds this server's container object. Error description: description.DSIExplanation: This error may be due to excessive network traffic, or it may be an internal error.Action: Minimize external network traffic between this server and other servers in the same Directory tree as much as possible; then retry the installation. If the problem persists, contact your Novell Authorized Reseller.32: An internal error has occurred. DSI cannot add a partition replica. Error description: description.DSIExplanation: An internal system error has occurred.Action: Try the operation again. If the problem persists, contact your Novell Authorized Reseller.33: An internal error has occurred. DSI cannot create an internal Directory context structure. Error description: description.DSIExplanation: An internal system error has occurred.Action: Try the operation again. If the problem persists, contact your Novell Authorized Reseller.34: An attempt to place the master replica of the new partition on this server failed (Error description: description). The master replica of the new partition is located on server name, and a read/write replica exists on this server. You can change the type of the replica on this server to a master replica later by using the Partition Manager (PARTMGR) utility. The installation should continue normally.DSIExplanation: A new partition was created on the server containing the most recent parent of the new context. The new context was created in the new partition; then an attempt was made to migrate that partition so that it would become a local partition (on the new server being installed). The attempt to change the local partition to the master replica and delete the (remote) secondary replica failed. This could be due to excessive network traffic.Action: Continue with the installation. After it is completed, use Partition Manager (PARTMGR.EXE), NetWare Administrator (GUI utility), or PMADMIN (OS/2 utility) to change the read/write replica to a master replica. You can then delete the replica on the server identified in the error message. However, this is not absolutely necessary.PAGENUM=169 ID="BP163"35: An NLM version mismatch has occurred. DSI version: number. Directory Services version: number.DSIExplanation: DSI.NLM and DS.NLM have different database versions that don't work together properly.Action: Make sure that the INSTALL.NLM, DSI.NLM, and SERVER.EXE are all from the same software release.37: DSI cannot find a NetWare 4.x server.DSIExplanation: The installation program was unable to find the root server. Two possible explanations are thatMARK=BULLETNetwork traffic may be excessively heavy.The server containing the context into which this server is being installed suddenly went downAction: Minimize external network traffic between this server and other servers in the same Directory tree as much as possible; then retry the installation. If the problem persists, contact your Novell Authorized Reseller.39: A call to DSAgentOpenLocal failed. Error description: description.DSIExplanation: NetWare Directory Services was unable to open the local Directory agent (database handler). This could be due to insufficient disk space, excessive network traffic, or an internal error.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving File I/O Errors" in Supervising the Network. Also, minimize external network traffic between this server and other servers in the same Directory tree as much as possible; then retry the installation. If the problem persists, contact your Novell Authorized Reseller.40: An internal error has occurred. DSI cannot set the bindery context. Error description: description.DSIExplanation: An internal system error has occurred.Action: Try the operation again. If the problem persists, contact your Novell Authorized Reseller.41: DSI cannot modify the existing NCP server object. Error description: description.DSIExplanation: An internal system error has occurred.Action: Try the operation again. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=170 ID="BP164"42: DSI cannot delete the existing NCP server object. Error description: description.DSIExplanation: An NCP server object that had the same name as the server being installed was found in this context. To complete the installation, that object must be deleted and recreated. An initial attempt at deleting the object was unsuccessful. One possible explanation is that the object corresponding to the administrator that you logged in as does not have Delete rights in the context.Action: Use NetWare Administrator or NETADMIN to make sure you have the Supervisor right in the context (or to the nearest parent to the context) where you are installing. If this is not the case, give yourself the Supervisor right in the context and retry the installation. If the problem persists, contact your Novell Authorized Reseller.43: DSI cannot create the NCP server object. Error description: description.DSIExplanation: An attempt to create the NCP server object in the context specified for this server was unsuccessful. One possible explanation is that you do not have the Create right in the context.Action: Use NetWare Administrator or NETADMIN to make sure you have the Supervisor right in the context (or to the nearest parent to the context) where you are installing. If this is not the case, give yourself the Supervisor right in the context and retry the installation. If the problem persists, contact your Novell Authorized Reseller.44: DSI's attempt to add a new partition timed out.DSIExplanation: An attempt to create a new partition for the new context failed. The new partition should have been created on the server containing the master partition for the nearest existing parent context. The error may have been caused by excessive network traffic, or by the server containing the master suddenly going down.Action: Make sure that all servers above this one in the tree that contain master partitions are operating. Minimize external network traffic between this server and other servers in the same Directory tree as much as possible; then, retry the installation. If the problem persists, contact your Novell Authorized Reseller.45: An internal error has occurred. DSI cannot get the volume ID; you are not logged in to the Directory.DSIExplanation: An internal system error has occurred.Action: Try the operation again. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=171 ID="BP165"46: DSI cannot find the local server context. Error description: description.DSIExplanation: An attempt to get information from the Directory database failed. This may be due to file I/O errors, or it may be an internal error.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving File I/O Errors" in Supervising the Network.47: An internal error has occurred. DSI cannot translate a local string to Unicode. You may have a problem with the Unicode translation files. Error description: description.DSIExplanation: An internal system error has occurred.Action: Try the operation again. If the problem persists, contact your Novell Authorized Reseller.48: An internal error has occurred. The object for volume name cannot be created. Error description: description.DSIExplanation: An internal system error has occurred.Action: Try the operation again. If the problem persists, contact your Novell Authorized Reseller.49: An internal error has occurred. DSI cannot determine the base class from RDN. Error description: description.DSIExplanation: An internal system error has occurred.Action: Try the operation again. If the problem persists, contact your Novell Authorized Reseller.50: DSI cannot create object "name". Error description: description. Verify that the context is entered correctly and follows proper containment rules.DSIExplanation: An internal system error has occurred.Action: Try the operation again. If the problem persists, contact your Novell Authorized Reseller.51: An internal error has occurred. DSI cannot create the root partition. Error description: description.DSIExplanation: An internal system error has occurred.Action: Try the operation again. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=172 ID="BP166"52: DSI cannot create the Directory database. Error description: description.DSIExplanation: An attempt to create the Directory database failed. This may be due to insufficient disk space, or it may be an internal error.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving File I/O Errors" in Supervising the Network.53: DSI cannot open the record manager. Error description: description.DSIExplanation: An attempt to access the Directory database failed. It may be locked by another process, or an internal error may have occurred.Action: Unload all other NLM programs (such as DSREPAIR) that may be accessing the database; then, retry the installation. If the problem persists, contact your Novell Authorized Reseller.54: DSI cannot open the Directory database. Error description: description.DSIExplanation: An attempt to access the Directory database failed. It may be locked by another process, or an internal error may have occurred.Action: Unload all other NLM programs (such as DSREPAIR) that may be accessing the database; then retry the installation. If the problem persists, contact your Novell Authorized Reseller.55: An internal error has occurred. The Directory Services bindery is not open, and must be for the bindery to be upgraded.DSIExplanation: An internal system error has occurred.Action: Try the operation again. If the problem persists, contact your Novell Authorized Reseller.56: Bindery upgrade information cannot be saved to file SWITCH.UPG.DSIExplanation: A file I/O error occurred while the program was writing bindery upgrade information to the SWITCH.UPG Directory file.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving File I/O Errors" in Supervising the Network.57: DSI cannot read a previous bindery object. Error code: code.DSIExplanation: An error occurred while the program was attempting to read the old bindery files (SYS:\SYSTEM\NET$OBJ.SYS, SYS:\SYSTEM\NET$PROP.SYS, SYS:\SYSTEM\ NET$VAL.SYS). The bindery files may be corrupted, or the volume may be unreadable.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving File I/O Errors" in Supervising the Network. If the problem persists, contact your Novell Authorized Reseller. For information on the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. PAGENUM=173 ID="BP167"58: DSI cannot add a previous bindery object. Error code: code. Object: name.DSIExplanation: An error occurred while the program was adding an old bindery object to the Directory. This object will not be upgraded correctly even though the installation may be completed and even though other objects may be installed correctly. You may have to recreate the object manually later.Action: Write down the name of the object that failed, along with the error code. Complete the installation and recreate the object later. Also, contact your Novell Authorized Reseller. For information on the specific error code, see IDREF="FM61529""Error Codes" in Appendix A.59: DSI cannot map a previous bindery name to a Directory ID. Error code: code. Bindery object: name.DSIExplanation: An internal system error has occurred.Action: Try the operation again. If the problem persists, contact your Novell Authorized Reseller. For information on the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 62: DSI cannot add a previous bindery property. Error code: code. Object: name. Property: name.DSIExplanation: An error occurred while the program was adding an old bindery object to the Directory. This object will not be upgraded correctly even though the installation may be completed and even though other objects may be installed correctly. You may have to recreate the object manually later.Action: Write down the name of the object and property that failed, along with the error code. Complete the installation, and recreate the object later. Also, contact your Novell Authorized Reseller. For information on the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 63: DSI cannot add a previous bindery group member. Error code: code. Object: name. Property: name. Member: name.DSIExplanation: An error occurred while the program was adding an old bindery object to the Directory. This object will not be upgraded correctly even though the installation may be completed and even though other objects may be installed correctly. You may have to recreate the object manually later.Action: Write down the name of the object, property, and member that failed along with the error code. Complete the installation, and recreate the object later. Also, contact your Novell Authorized Reseller. For information on the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. PAGENUM=174 ID="BP168"64: DSI cannot write a previous bindery property. Error code: code. Object: name. Property: name.DSIExplanation: An error occurred while the program was adding an old bindery object to the Directory. This object will not be upgraded correctly even though the installation may be completed and even though other objects may be installed correctly. You may have to recreate the object manually later.Action: Write down the name of the object that failed along with the error code. Complete the installation, and recreate the object later. Also, contact your Novell Authorized Reseller. For information on the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 66: DSI cannot get the Directory NCP server object ID. Error code: code. Object: name.DSIExplanation: An internal system error has occurred.Action: Try the operation again. If the problem persists, contact your Novell Authorized Reseller. For information on the specific error code, see IDREF="FM61529""Error Codes" in Appendix A.68: DSI cannot allocate sufficient memory.DSIExplanation: There was insufficient memory for INSTALL to run.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.69: DSI cannot get Directory information for previous bindery object name. Error code: code.DSIExplanation: An internal system error has occurred.Action: Try the operation again. If the problem persists, contact your Novell Authorized Reseller. For information on the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 74: DSI cannot read a previous bindery property. Error description: description.DSIExplanation: An error occurred while the program attempted to read the old bindery files (SYS:\SYSTEM\NET$OBJ.SYS, SYS:\SYSTEM\NET$PROP.SYS, SYS:\SYSTEM\ NET$VAL.SYS). The bindery files may be corrupted, or the volume may be unreadable.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving File I/O Errors" in Supervising the Network. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=175 ID="BP169"75: DSI cannot read a previous bindery property. Error code: code. Object: name.DSIExplanation: An error occurred while the program attempted to read the old bindery files (SYS:\SYSTEM\NET$OBJ.SYS, SYS:\SYSTEM\NET$PROP.SYS, SYS:\SYSTEM\ NET$VAL.SYS). The bindery files may be corrupted, or the volume may be unreadable.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving File I/O Errors" in Supervising the Network. If the problem persists, contact your Novell Authorized Reseller. For information on the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 76: DSI cannot read a previous bindery value. Error code: code. Object: name. Property: name.DSIExplanation: An error occurred while the program attempted to read the old bindery files (SYS:\SYSTEM\NET$OBJ.SYS, SYS:\SYSTEM\NET$PROP.SYS, SYS:\SYSTEM\ NET$VAL.SYS). The bindery files may be corrupted, or the volume may be unreadable.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving File I/O Errors" in Supervising the Network. If the problem persists, contact your Novell Authorized Reseller. For information on the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 77: DSI cannot read a previous bindery object. Error code: code.DSIExplanation: An error occurred while the program attempted to read the old bindery files (SYS:\SYSTEM\NET$OBJ.SYS, SYS:\SYSTEM\NET$PROP.SYS, SYS:\SYSTEM\ NET$VAL.SYS). The bindery files may be corrupted, or the volume may be unreadable.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving File I/O Errors" in Supervising the Network. If the problem persists, contact your Novell Authorized Reseller. For information on the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 78: Bindery file SYS:SYSTEM\NET$OBJ.SYS is already open and was not expected to be.DSIExplanation: The file NET$OBJ.SYS is in an opened state when it should be closed. This problem is probably due to previous errors that occurred.Action: Dismount volume SYS: and remount it. If the problem persists, contact your Novell Authorized Reseller.79: Bindery file SYS:SYSTEM\NET$OBJ.SYS cannot be opened.DSIExplanation: An error occurred while the program attempted to open the old bindery file (SYS:SYSTEM\NET$OBJ.SYS). The bindery file may not exist, it may be corrupted, or the volume may be unreadable.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving File I/O Errors" in Supervising the Network. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=176 ID="BP170"80: Directory file SWITCH.UPG cannot be opened.DSIExplanation: The NetWare Directory Services file SWITCH.UPG may be corrupted or unreadable.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving File I/O Errors" in Supervising the Network.81: Some old ID's in SWITCH.UPG do not match the bindery. You have probably upgraded more than once. You must restore the original (first) SWITCH.UPG before you can downgrade a volume. Even then, some of your trustees, etc. may be irreversibly corrupted.DSIExplanation: The NetWare Directory Services file SWITCH.UPG is out of date with the bindery.Action: Delete the file SWITCH.UPG. You will need to recreate trustees on the volumes.82: DSI cannot switch bindery IDs to Directory Services IDs for volume name. Error code: code.DSIExplanation: An internal system error has occurred.Action: Try the operation again. If the problem persists, contact your Novell Authorized Reseller. For information on the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 83: An attempt to upgrade volume name failed because users were logged in. Remove all user connections and try the upgrade again.DSIExplanation: A volume cannot be upgraded until all users have logged out of it.Action: Load MONITOR.NLM and remove all connections. Retry the installation.84: DSI cannot allocate sufficient memory for ID tables.DSIExplanation: Sufficient memory was not available for INSTALL to run.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.86: DSI cannot read the Directory default Supervisor object.DSIExplanation: The Directory database may be corrupted or unreadable.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving File I/O Errors" in Supervising the Network.87: DSI cannot write the Directory default Supervisor object.DSIExplanation: The Directory database could not be written.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving File I/O Errors" in Supervising the Network.PAGENUM=177 ID="BP171"88: DSI cannot add attribute NNS domain name to the server context. Error code: code.DSIExplanation: An internal NetWare Directory Services error has occurred.Action: Try again. If the problem persists, contact your Novell Authorized Reseller. For information on the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 89: An attempt to remove an extraneous replica of the new Directory partition replica failed. Error: description. This is not a fatal problem, however, the installation should continue normally. A read/write replica of the partition will exist on server name. You may delete this replica after the installation is complete using the Partition Manager (PARTMGR) utility.DSIAction: As stated in the message, you may want to delete the read/write replica after the installation is complete using the Partition Manager or PARTMGR.90: DSI cannot resolve to the root of the Directory tree. Error description: description. Make certain that a server containing the replica of the root partition is up and connected to the network.DSIExplanation: A replica of the root partition for the Directory tree you are trying to install is not visible to this server, or internal errors have occurred.Action: Make sure a server containing a replica of the root partition is up. Resolve any network problems that may be present. If this fails, contact your Novell Authorized Reseller.91: DSI cannot resolve to the master partition containing the NCP Server object. Error description: description. Make certain that this server is up and connected to the network.DSIExplanation: DSI cannot find the NCP Server object for this server in any master Directory partition replica. This may be because the server that contains the master partition (which contains the server object) is not operating or is not visible on the network from this server.Action: Make sure a server containing the master replica of the partition containing the server object is operating. Resolve any network problems that may be present. If the problem persists, contact your Novell Authorized Reseller.92: Directory Services API interface versions do not match DSI internal interface version is: interface_version DSI API interface version is: DS_access_version_expected Directory Services API interface version is: DS_access_versionDSIExplanation: An incorrect version of one of the listed APIs exists.Action: Note the version for each API display, and contact your Novell Authorized Reseller to find out which version is required. PAGENUM=178 ID="BP172"93: Could not gain access to Directory Services. Either DS.NLM is not loaded or another NLM has already registered with DS. This could be one of DSI.NLM, DSMERGE.NLM, or DSREPAIR.NLM.DSIAction: Load the DS.NLM, and retry the operation.94: An internal error has occurred. DSI unable to timestamp schema. Error description: description.DSIExplanation: An internal system error has occurred at the operation noted in the message.Action: Note the error code displayed, see the IDREF="FM61529""Error Codes" in Appendix A, and follow the recommended suggestions. If the problem persists, contact your Novell Authorized Reseller.95: An internal error has occurred. DSI unable to add server to internal list. Error description: description.DSIExplanation: An internal system error has occurred at the operation noted in the message.Action: For information on the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. Retry the operation. If the problem persists, contact your Novell Authorized Reseller.96: An internal error has occurred. DSI unable to synchronize schema. Error description: description.DSIExplanation: An internal system error has occurred at the operation noted in the message.Action: For information on the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. Retry the operation. If the problem persists, contact your Novell Authorized Reseller.97: An internal error has occurred. DSI unable to get partition root information. Error description: description.DSIExplanation: An internal system error has occurred at the operation noted in the message.Action: Retry the operation. If the problem persists, contact your Novell Authorized Reseller. For information on the specific error code, see IDREF="FM61529""Error Codes" in Appendix A.1001: This server is not backlinked on server: name.DSIExplanation: This server participates in replica operations with the server displayed in the message. This condition may exist when NetWare Directory Services is being removed from the server. Insufficient information exists on the server displayed in the message to properly delete the server object.Action: Please try removing this server from the tree at a later time.PAGENUM=179 ID="BP173"1001: An internal error has occurred. DSI cannot set the bindery services context. Error description: description. Make certain that TTS is enabled before retrying the installation.DSIExplanation: An internal system error has occurred at the operation noted in the message. TTS may be disabled because of insufficient disk space.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Disk Space Problems" in Supervising the Network. Make sure TTS is enabled, and retry the operation. For information on the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the condition persists, contact your Novell Authorized Reseller.1002: The partition name is in a transitional state. The local server is participating in a replica operation that involves this partition. Please try removing this server from the tree at a later time.DSIExplanation: This condition may exist when NetWare Directory Services is being removed from the server.Action: Follow the action specified in the message. If the condition persists, contact your Novell Authorized Reseller.1003: This server cannot communicate with server name. Please try removing this server from the tree at a later time.DSIExplanation: This condition may exist when NetWare Directory Services is being removed from the server.Action: Follow the action specified in the message. If the condition persists, contact your Novell Authorized Reseller.1004: Could not change the replica type of the partition name on the server name. Error description description.DSIExplanation: This condition may exist when NetWare Directory Services is being removed from the server.Action: For information on the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. Make sure the server is operating. Wait a few minutes; then retry the operation. If the problem persists, contact your Novell Authorized Reseller.1005: Could not delete one of the namebase files. Error description description.DSIExplanation: This condition may exist when NetWare Directory Services is being removed from the server.Action: For information on the specific error code, see IDREF="FM61529""Error Codes" in Appendix A.PAGENUM=180 ID="BP174"1007: Error code beginning Directory operation.DSIAction: For information on the specific error code, see IDREF="FM61529""Error Codes" in Appendix A.1008: Could not change the replica type of the partition. Error description description.DSIExplanation: This condition may exist when NetWare Directory Services is being removed from the server.Action: For information on the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. Make sure the server is operating. Wait a few minutes; then retry the operation. If the problem persists, contact your Novell Authorized Reseller.Error description getting replica information for partition_name. Unable to make necessary replica changes during the removal of Directory Services from this server.DSIExplanation: This condition may exist when NetWare Directory Services is being removed from the server.Action: Note the error code displayed, see the IDREF="FM61529""Error Codes" in Appendix A, and follow the recommended suggestions. If the problem persists, contact your Novell Authorized Reseller.Error allocating memory for server certificate.DSIExplanation: The server is out of memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.Error create schema. Error description descriptionDSIExplanation: The message indicates the point in the installation process at which the error occurred.Action: Note the error code displayed, see the IDREF="FM61529""Error Codes" in Appendix A, and follow the recommended suggestions. If the problem persists, contact your Novell Authorized Reseller.Error getting server's public key. Error description description.DSIExplanation: The message indicates the point in the installation process at which the error occurred.Action: Note the error code displayed, see the IDREF="FM61529""Error Codes" in Appendix A, and follow the recommended suggestions. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=181 ID="BP175"Error getting server's state. Error description description.DSIExplanation: The message indicates the point in the installation process at which the error occurred.Action: Note the error code displayed, see the IDREF="FM61529""Error Codes" in Appendix A, and follow the recommended suggestions. If the problem persists, contact your Novell Authorized Reseller.Error setting server's state. Error description description.DSIExplanation: The message indicates the point in the installation process at which the error occurred.Action: Note the error code displayed, see the IDREF="FM61529""Error Codes" in Appendix A, and follow the recommended suggestions. If the problem persists, contact your Novell Authorized Reseller.Error upgrading the schema. Error description description.DSIExplanation: The message indicates the point in the installation process at which the error occurred.Action: Note the error code displayed, see the IDREF="FM61529""Error Codes" in Appendix A, and follow the recommended suggestions. If the problem persists, contact your Novell Authorized Reseller.The replica to be used for bindery services is not yet accessible. It is currently in the process of being added to this server. Please try again after a short while.DSIAction: Follow the suggestions in the message.This server does not contain a replica of the bindery services context, context. A read/write replica will be added to this server as the bindery upgrade continues.DSIAction: None. This message is for information only.This server holds a read only replica of the bindery services context, context. The replica type will be changed to read/write as the bindery upgrade continues.DSIAction: None. This message is for information only.Unable to change the replica type of partition name on server name to master. Error Description description.DSIExplanation: The message indicates the point in the installation process at which the error occurred.Action: Note the error code displayed, see the IDREF="FM61529""Error Codes" in Appendix A, and follow the recommended suggestions. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=182 ID="BP176"Unable to create the NCP server object. Error description description.DSIExplanation: The message indicates the point in the installation process at which the error occurred.Action: Note the error code displayed, see the IDREF="FM61529""Error Codes" in Appendix A, and follow the recommended suggestions. If the problem persists, contact your Novell Authorized Reseller.Unable to get the replica type. Error description descriptionDSIExplanation: The message indicates the point in the installation process at which the error occurred.Action: Note the error code displayed, see the IDREF="FM61529""Error Codes" in Appendix A, and follow the recommended suggestions. If the problem persists, contact your Novell Authorized Reseller.Unable to update the schema in this tree. The installation process will continue. Error description descriptionDSIExplanation: The installation process was unable to upgrade the tree schema to NetWare 4.10.Action: Note the error code displayed, see the IDREF="FM61529""Error Codes" in Appendix A, and follow the recommended suggestions. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=183 ID="BP177"DSKSHARE005: An internal error has occurred. System data could not be added to NetWare.DSKSHAREExplanation: The program attempted to add the OS/2 adapter board to NetWare using the function call AddDiskSystem; however, this call failed. This message could indicate a lack of server memory or an internal system error.Action: Increase the available memory. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. Load the driver again. If the problem persists, contact your Novell Authorized Reseller.010: An internal error has occurred. The program could not allocate a disk resource tag.DSKSHAREExplanation: The program tried to allocate a disk resource tag, and the call failed. This message could indicate a lack of server memory or an internal system error.Action: Increase the available memory. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. Load the driver again. If the problem persists, contact your Novell Authorized Reseller.015: An internal error has occurred. The program could not allocate a memory resource tag.DSKSHAREExplanation: The program tried to allocate a memory resource tag, and the call failed. This message could indicate a lack of server memory or an internal system error.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. Load the driver again. If the problem persists, contact your Novell Authorized Reseller.020: An internal error has occurred. The program could not allocate a polling resource tag.DSKSHAREExplanation: The program tried to allocate a polling resource tag, and the call failed. This message could indicate a lack of server memory or an internal system error.Action: Increase the available memory. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. Load the driver again. If the problem persists, contact your Novell Authorized Reseller.025: An internal error has occurred. The program could not get the 16:16 data selector.DSKSHAREExplanation: The program could not set up a 16-bit data selector to the data group.Action: Contact your Novell Authorized Reseller.PAGENUM=184 ID="BP178"030: This device driver is already loaded.DSKSHAREExplanation: DSKSHARE can only be loaded once. Because DSKSHARE understands all OS/2 disk drives, you do not need to load it more than once.Action: None. This message is for information only.PAGENUM=185 ID="BP179"DSMERGEContact your Novell Authorized Reseller.PAGENUM=186 ID="BP180"DSREPAIR001: Unknown switch pointer.DSREPAIRExplanation: Unknown command line switch.Action: For a list of command line switches, see "BOOK="utlrfenu" COLLECTION="nw41"DSREPAIR" in Utilities Reference.002: USAGE: (-L LogFileName) (-U) unattended mode.DSREPAIRExplanation: You have entered the DSREPAIR command with incorrect syntax.Action: Try the command again with the indicated syntax. Note: -L and -U are optional parameters. For information on DSREPAIR, see "BOOK="utlrfenu" COLLECTION="nw41"DSREPAIR" in Utilities Reference.003: Unable to allocate resource tag: name.DSREPAIRExplanation: An error occurred trying to register for the operating system resources.Action: Try running DSREPAIR again, or reboot the server. For information on DSREPAIR, see "BOOK="utlrfenu" COLLECTION="nw41"DSREPAIR" in Utilities Reference.004: Unable to register for volume dismount event.DSREPAIRExplanation: An error occurred trying to register for OS resources.Action: Try running DSREPAIR again, or reboot the server. For information on DSREPAIR, see "BOOK="utlrfenu" COLLECTION="nw41"DSREPAIR" in Utilities Reference.005: Unable to allocate memory for DSREPAIR process stack.DSREPAIRExplanation: Your server does not have enough available memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.007: Unable to open "DSREPAIR status screen."DSREPAIRExplanation: An error occurred when DSREPAIR attempted to register for OS resources.Action: Try running DSREPAIR again, or reboot the server. For information on DSREPAIR, see "BOOK="utlrfenu" COLLECTION="nw41"DSREPAIR" in Utilities Reference.PAGENUM=187 ID="BP181"008: Directory Services is loading the local database.DSREPAIRExplanation: There may be a delay when DSREPAIR exits and attempts to reload the NetWare Directory Services database.Action: None. This message is for information only.009: Directory Services remains locked, error code.DSREPAIRExplanation: When DSREPAIR.NLM unloads, it attempts to reload the NetWare Directory Services database. In this case, it failed.Action: Try running DSREPAIR again. If your attempt is not successful, reinstall NetWare Directory Services on this server.010: Process completed.DSREPAIRExplanation: DSREPAIR has completed operation and is unloading from the server.Action: None. This message is for information only.011: Stack overflow, frame size = hex number, ESP = hex number.DSREPAIRExplanation: An internal error occurred.Action: Try running DSREPAIR again, or reboot the server, then run DSREPAIR again. For information on DSREPAIR, see "BOOK="utlrfenu" COLLECTION="nw41"DSREPAIR" in Utilities Reference.013: Could not open all of the Directory Services files.DSREPAIRExplanation: The Directory database files are stored in a secure area of the NetWare server's SYS: volume. There are a total of four files; these files were found, but DSREPAIR could not access them.Action: Run VREPAIR. For information on VREPAIR, see "BOOK="utlrfenu" COLLECTION="nw41"VREPAIR" in Utilities Reference. If this does not solve the problem, reinstall NetWare Directory Services and restore the objects to the Directory if necessary.PAGENUM=188 ID="BP182"014: Could not establish basic access to record manager.DSREPAIRExplanation: A request was made to the DS.NLM record manager to gain control of the database, but the request failed.Action: Unload then reload NetWare Directory Services. If this does not work, reboot the server and try again.015: Could not establish full access to record manager.DSREPAIRExplanation: A request was made to the DS.NLM record manager to gain control of the database, but the request failed.Action: Unload then reload NetWare Directory Services. If this does not work, reboot the server and try again.016: Volume "SYS" is not mounted, cannot access Directory Services files.DSREPAIRExplanation: You cannot use NetWare Directory Services unless volume SYS: is mounted, because that is where the NetWare Directory Services database files are located.Action: Be sure volume SYS: is mounted.017: Cannot initialize directory path to Directory Services files.DSREPAIRExplanation: DSREPAIR could not find the directory that contains the NetWare Directory Services database files in volume SYS:.Action: Make sure volume SYS: is mounted, or run reinstall the server.018: Could not rename file: old_filename.DSREPAIRExplanation: A file of the same name may already exist.Action: Run DSREPAIR again. If necessary, run VREPAIR then running DSREPAIR again. Then try unloading and reloading NetWare Directory Services. For information on VREPAIR, see "BOOK="utlrfenu" COLLECTION="nw41"VREPAIR" in Utilities Reference. If these actions do not work, reboot the server and try again. Your final option is to reinstall the server. If the problem persists, contact your Novell Authorized Reseller.019: Could not read from file: filename, offset: offset.DSREPAIRExplanation: DSREPAIR could not read a record from the NetWare Directory Services database.Action: Try running VREPAIR then running DSREPAIR again. Then try unloading and reloading NetWare Directory Services. If these actions do not work, reboot the server and try again. Your final option is to reinstall the server. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=189 ID="BP183"020: Could not read entry of name: local_name.DSREPAIRExplanation: DSREPAIR could not read a record from the NetWare Directory Services database.Action: Run VREPAIR and DSREPAIR again. Then unload and reload NetWare Directory Services. If these actions do not work, reboot the server and try again. Your final option is to reinstall the server. If the problem persists, contact your Novell Authorized Reseller.021: Could not write to file: filename, offset offsetDSREPAIRExplanation: DSREPAIR could not write a record to the NetWare Directory Services database. The volume might be full, or the database might be corrupted.Action: Run VREPAIR then DSREPAIR again. Then unload and reload NetWare Directory Services. For information on VREPAIR, see "BOOK="utlrfenu" COLLECTION="nw41"VREPAIR" in Utilities Reference. If these actions do not work, reboot the server and try again. Your final option is to reinstall the server. If the problem persists, contact your Novell Authorized Reseller.022: Could not insert record for file: filename, offset offsetDSREPAIRExplanation: DSREPAIR could not write a record to the NetWare Directory Services database. The volume might be full, or the database might be corrupted.Action: Try running VREPAIR then running DSREPAIR again. Then try unloading and reloading NetWare Directory Services. If these actions do not work, reboot the server and try again. Your final option is to reinstall the server. If the problem persists, contact your Novell Authorized Reseller.023: Could not read the file size for file: "filename"DSREPAIRExplanation: DSREPAIR could not read a record from the NetWare Directory Services database.Action: Try running VREPAIR then running DSREPAIR again. Then try unloading and reloading NetWare Directory Services. If these actions do not work, reboot the server and try again. Your final option is to reinstall the server. If the problem persists, contact your Novell Authorized Reseller.024: Could not update whole value for file: filename, offset offsetDSREPAIRExplanation: DSREPAIR could not write a record to the NetWare Directory Services database. The volume might be full, or the database might be corrupted.Action: Try running VREPAIR then running DSREPAIR again. Then try unloading and reloading NetWare Directory Services. If these actions do not work, reboot the server and try again. Your final option is to reinstall the server. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=190 ID="BP184"025: Could not read whole value for file: filename, offset offsetDSREPAIRExplanation: DSREPAIR could not read a record from the NetWare Directory Services database.Action: Try running VREPAIR then running DSREPAIR again. Then try unloading and reloading NetWare Directory Services. If these actions do not work, reboot the server and try again. Your final option is to reinstall the server. If the problem persists, contact your Novell Authorized Reseller.026: Could not purge record in file filename, offset offsetDSREPAIRExplanation: DSREPAIR could not purge a record from the NetWare Directory Services database. The database could be corrupted.Action: Try running VREPAIR and running DSREPAIR again. Then try unloading and reloading NetWare Directory Services. If these actions do not work, reboot the server and try again. Your final option is to reinstall the server. If the problem persists, contact your Novell Authorized Reseller.027: Could not allocate number bytes of memory.DSREPAIRExplanation: Your server does not have enough available memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.028: Error encountered in schema cache DS_NLM_error_number.DSREPAIRExplanation: An internal error occurred in the NetWare Directory Services NLM.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.029: Could not insert record for file: "filename"DSREPAIRExplanation: DSREPAIR could not write a record to the NetWare Directory Services database. The volume could be full or the database could be corrupted.Action: Run VREPAIR, then try again. If the problem persists, contact your Novell Authorized Reseller.030: Error reading attribute attribute from entry entry.DSREPAIRExplanation: DSREPAIR could not read a record from the NetWare Directory Services database.Action: Run VREPAIR, then try again. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=191 ID="BP185"031: Could not truncate the file: filenameDSREPAIRExplanation: DSREPAIR could not write a record to the NetWare Directory Services database. The volume could be full, or the database could be corrupted.Action: Run VREPAIR, then try again. If the problem persists, contact your Novell Authorized Reseller.032: Internal API version mismatch, DSREPAIR is version number and DS is version number.DSREPAIRExplanation:  You must have the same release of DS and DSREPAIR to run DSREPAIR.Action: To check the version numbers of utilities and NDIR, type the VER. To check the version of the DSREPAIR.NLM, type NDIR DSREPAIR.NLM /VER. To check the DS.NLM version, type MODULES at the server console. Load a newer version of one or both files. If you are not sure about the correct version, contact your Novell Authorized Reseller.033: Could not create or open file: name.DSREPAIRExplanation: DSREPAIR could not create and open a file. The volume might be full, or no more directory entries may be available on the volume.Action: Try running VREPAIR then running DSREPAIR again. Also, use FILER to make sure you have available directory entries.034: Could not write to file: filename at location address.DSREPAIRExplanation: DSREPAIR could not write a record to the NetWare Directory Services database. The volume might be full or the database might be corrupted.Action: Try running VREPAIR then running DSREPAIR again. If the problem persists, contact your Novell Authorized Reseller.035: Internal versions do not match: DSREPAIR.NLM = version, DS.NLM = version, database files = numberDSREPAIRExplanation: You must have the same internal version of all programs (DSREPAIR.NLM and DS.NLM) and a matching version of the NetWare Directory Services database.Action: If the versions of the NLMs do not match, load the correct versions of the NLMs. If the database does not match, then use DSREPAIR.NLM to upgrade it to the most current version. (This is done automatically if DS.NLM and DSREPAIR.NLM are the same version and the NetWare Directory Services database is one version earlier.PAGENUM=192 ID="BP186"036: Could not gain access to Directory Services.  DS.NLM is not loaded.DSREPAIRExplanation: The directory services database is not accessible because the DS.NLM is not loaded.Action: Load the DS.NLM, and then try accessing the database again.037: Directory Services API interface versions do not match.  DSREPAIR internal interface version is version.  DSREPAIR API interface version is : version.  Directory Services API interface version is: version.  DSREPAIRExplanation: The version of DSREPAIR does not match with the version DS.NLM.Action: Get the correct version and try again.Note: The version's display in the message may all have the same value and still be the wrong version.  These versions do not indicate the correct version.  To get the correct version, contact your Novell Authorized Reseller.039: Internal Error, number number.DSREPAIRExplanation: An internal failure occurred in the NLM.Action: Reboot the server and try again. If the problem persists, contact your Novell Authorized Reseller or the NLM vendor.040: Error writing to error log file, log file closed.DSREPAIRExplanation: An error occurred while DSREPAIR was writing to the log file target device, or the device has no more room. The repair will continue without logging any more errors to the log file.Action: None. This message is for information only.041: This NLM requires a newer version of NWSNUT.DSREPAIRExplanation: While loading, DSREPAIR.NLM determined that the version of the NWSNUT.NLM does not support the required functionality.Action: Update the version of NWSNUT.NLM on the server.042: The NLM was unable to initialize NWSNUT.DSREPAIRExplanation: The support NLM, NWSNUT, returned an error from the initialization process because of an internal error or insufficient server memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems in Supervising the Network. Try the operation again.  If the server has at least 500 KB of free memory, contact your Novell Authorized Reseller.043: Unable to create an NWSNUT portal.DSREPAIRExplanation: The server may be out of memory.Action: Increase the available memory. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems in Supervising the Network.  Try the operation again.044: Could not read from file: name, offset number.  Record will be padded with 0's.DSREPAIRExplanation: DSREPAIR could not read a record from the NetWare Directory Services database; however, rather than aborting the repair, the record is filled with 0's and the repair operation will continue.Action: None. This message is for information only.045: Could not gain access to Directory Services. Another NLM has already registered with DS.  This could be one of DSI.NLM, DSMERGE.NLM, or DSREPAIR.NLM.DSREPAIRExplanation: Only one of the three described NLM programs can be loaded at a time.Action: Check to see if one of these NLM programs are loaded and unload it.  If that does not resolve the problem, bring down the server and bring it back up.  Then retry the operation.046: The Schema Tree is corrupt, no  repair strategy is available.  Remove the server from the Directory Services Tree and then re-install it.DSREPAIRExplanation: The schema cannot be repaired, and the NetWare Directory Services database on this server cannot operate without it.Action: Deinstall the server from the tree and reinstall it.047: Could not locate one or more Directory Services files.DSREPAIRAction: If database files are missing, you must deinstall the server from the tree, and then reinstall the server.PAGENUM=193 ID="BP187"EDIT6: A memory allocation error has occurred.EDITExplanation: The server may not have enough available memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.7: The file could not be written to disk.EDITExplanation: EDIT.NLM was unable to write the file to disk. This could have been caused by a variety of problems.Action: Make sure that the volume is mounted. If the problem persists, contact your Novell Authorized Reseller.8: The file could not be created.EDITExplanation: EDIT.NLM was unable to create the file. This could have been caused by a variety of problems.Action: Make sure that the volume is mounted. If the problem persists, contact your Novell Authorized Reseller.9: The file could not be read.EDITExplanation: EDIT.NLM was unable to read the file from disk. Action: Make sure that the volume is mounted and that the file exists in the specified directory. If the problem persists, contact your Novell Authorized Reseller.10: An invalid NetWare file path was specified.EDITExplanation: The directory supplied for the file was invalid.Action: Make sure the specified directory exists. Type the directory path correctly.14: The NLM could not allocate a resource tag.EDITExplanation: The server may not have enough available memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.16: The NLM could not get the process resource tag.EDITExplanation: The server may not have enough available memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.PAGENUM=194 ID="BP188"18: The NLM could not get the screen resource tag.EDITExplanation: The server may not have enough available memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.20: The NLM could not allocate memory for its stack.EDITExplanation: The server may not have enough available memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.21: The NLM could not open a screen.EDITExplanation: The server may not have enough available memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.50: The NLM was unable to initialize NWSNUT.NLM.EDITExplanation: An internal system error probably occurred.Action: If the problem persists, contact your Novell Authorized Reseller.PAGENUM=195 ID="BP189"EXOS-OS2001: The LSL is not loaded.EXOS-OS2Explanation: The Link Support Layer (LSL) module must be loaded before the driver can be installed.Action: Edit the CONFIG.SYS file to load LSL before the LAN driver, as in the following example:FORMAT="LINESPECIFIC"MOREINFO="NONE"DEVICE=C:\NETWARE\LSL.SYS 
DEVICE=C:\NETWARE\EXOS.SYS 021: Could not add MLID Protocol ID.EXOS-OS2Explanation: The Link Support Layer (LSL) is configured with resources for four Protocol Identifiers. This number has been exceeded.Action: None. This message is for information only.022: Could not allocate memory. Virtual board did not load.EXOS-OS2Explanation: The computer cannot allocate enough memory to load another network board.Action: Do one of the following:MARK=BULLETIncrease the available memory. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network or "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network.Edit the CONFIG.SYS file, and remove any unnecessary drivers.050: [ISA bus | Microchannel] The board cannot be found.EXOS-OS2Explanation: If the computer is using an ISA bus network board, the network board was not found due to one or more of the following conditions: MARK=BULLETThe network board is not present in the machine. The network board settings are not the defaults, and they are not defined in the NET.CFG file.Another network board is using the same hardware settings as this network board.PAGENUM=196 ID="BP190"The network board is bad.Action: Do one or more of the following:MARK=BULLETMake sure that the network board is properly seated into the slot. If the jumper settings are not the defaults, make sure that they match the settings in the NET.CFG file. If not using the NET.CFG file, make sure that the jumper settings are set to the defaults. If other network boards are using the same hardware settings, change the settings and try to reload the driver.Replace the bad network board with one that is good.Explanation: If the computer is using a microchannel network board, the network board is not in the machine, or the network board's configuration could not be obtained.Action: Do one of the following:MARK=BULLETMake sure that the network board is properly seated into a slot.Insert the network board into a slot, and run the CLASS=DISKReference diskette to install it.051: Board RAM failed the memory test.EXOS-OS2Explanation: The memory test on the network board's internal static RAM failed.Action: Check the network board and other hardware. If necessary, replace the network board.056: This interrupt is already used and cannot be shared.EXOS-OS2Explanation: The selected interrupt is being used by another device, so it cannot be used for this network board.Action: If the computer is using a microchannel network board, run the CLASS=DISKReference diskette that came with the computer, and change the jumper setting on the network board to use a different interrupt. See the EXOS hardware manual for information on jumper settings. Edit the NET.CFG file to reflect the correct interrupt level used by the network board. For information about the NET.CFG file, see "BOOK="ws_osenu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for OS/2 User Guide If the computer is using an ISA bus network board, change the jumper setting to specify a different interrupt; then edit the NET.CFG file to reflect the correct interrupt level used by the network board.PAGENUM=197 ID="BP191"064: Board cannot be found at slot/IO portEXOS-OS2Explanation: The network board cannot be found in the slot specified in the NET.CFG file.Action: If the computer is using an ISA Bus network board, Make sure the board is in the slot number and is using the I/O address specified in the NET.CFG file. For information about editing the NET.CFG file, see "BOOK="ws_osenu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for OS/2 User Guide.If the computer is using a microchannel network board, do one or more of the following:MARK=BULLETCorrect the slot number in the NET.CFG file to match the slot where the network board is physically located. For information about the NET.CFG file, see "BOOK="ws_osenu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for OS/2 User Guide.Move the network board to the slot specified in the NET.CFG file; then run the CLASS=DISKReference diskette to install the network board.Note: If no slot is specified in the NET.CFG file, the driver will search all slots for the network board. If more than one network board is in the machine, the slots must be specified in the NET.CFG file.070: The board has failed.EXOS-OS2Explanation: A hardware error has occurred.Action: Power off the computer; then reboot. Load the driver again. If the driver will not reload, a hardware failure has occurred. Replace the network board.PAGENUM=198 ID="BP192"FILER050: An error occurred during FILER's attempt to copy to server name.FILERExplanation: The system encountered an error while copying the file to a different server.Action: Make sure the user has appropriate user access rights. Try again. If the problem persists, contact your Novell Authorized Reseller.055: The destination entry name already exists.FILERExplanation: FILER cannot move the file or directory to the specified path because a file or directory with the same name already exists.Action: Select a different name and try again.060: File path is in use and the ownership can't be changed.FILERExplanation: FILER cannot change the ownership on the specified file because it is already in use.Action: Try again when the file is not being used. For more information, see "BOOK="utlrfenu" COLLECTION="nw41"FILER" in Utilities Reference.065: The first extended attribute couldn't be found.FILERExplanation: The file being copied has extended attributes associated with it, but they could not be found.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.070: This utility was unable to get the name space information for the target file.FILERExplanation: The file being copied has extended attributes associated with it, but the target file name space information could not be read.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.075: This utility was unable to get the handle information for the extended attributes.FILERExplanation: The file being copied has extended attributes associated with it, but the handle information could not be read.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=199 ID="BP193"080: This utility was unable to get the name space information for the source file.FILERExplanation: The file being copied has extended attributes associated with it, but the source file name space information could not be read.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.085: An error occurred during FILER's attempt to move the entry. Error code: code.FILERExplanation: The system encountered an error during an attempt to move the current entry.Action: Try again. For information on the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.090: An error occurred during FILER's attempt to get the name space. Error code: code.FILERExplanation: The system encountered an error while trying to get the MAC name space information.Action: Try again. For information on the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.100: You do not have rights to move an entry to that destination.FILERExplanation: The user needs the Create right in the destination path to move an entry.Action: Obtain the Create right. For more information, see "BOOK="utlrfenu" COLLECTION="nw41"FILER" in Utilities Reference.105: An error occurred during FILER's attempt to read the extended attributes.FILERExplanation: The file being copied has extended attributes associated with it. The system encountered an error while reading them.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.110: An error occurred during FILER's attempt to read from the source file.FILERExplanation: When copying a file, an error occurred while reading from the source file.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.115: The file is flagged Rename Inhibit and cannot be moved.FILERExplanation: A Rename Inhibit file cannot be moved.Action: Remove the file Rename Inhibit attribute and try again.PAGENUM=200 ID="BP194"120: An error occurred during FILER's attempt to set the attributes for file name.FILERExplanation: An error prevented FILER from setting the file attributes.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.125: The file is flagged Transactional and can't be moved.FILERExplanation: A Transactional file cannot be moved.Action: Remove the Transactional File attribute and try again.130: An error occurred during FILER's attempt to write to the extended attributes.FILERExplanation: The file has extended attributes associated with it, and the system encountered an error in writing them to the destination file.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.150: An error occurred during FILER's attempt to get the AFP entry ID.FILERExplanation: FILER couldn't get the entry ID for the specified path from the NetWare server.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.155: This file was unable to be opened. Error code: code.FILERExplanation: FILER couldn't open the specified file.Action: Try again. For information on the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.160: An error occurred during FILER's attempt to get the file information.FILERExplanation: An internal error occurred, and FILER couldn't get information for the specified file.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.165: An error prevented the file from being created.FILERExplanation: This error was caused by one of the following:MARK=BULLETThe user tried to copy a file to an existing file.The user account does not have sufficient rights to create the file.A subdirectory in the destination directory has the same name as the file to be copied.PAGENUM=201 ID="BP195"FILER encountered an error as it attempted to copy non-DOS files (such as MAC or OS/2) and create them in the destination directory.The file is in use in a nonsharing mode or is flagged Read Only. Action: Do one or more of the following: MARK=BULLETMake sure that the user account has appropriate rights to create a file in the destination directory. If the user account has the Modify right in the source directory, flag the file as Read Write; then try the command again. If the file is being used by another application or user, try again later.170: An error occurred during FILER's attempt to modify the date and time. The date and time for this file won't be correct.FILERExplanation: The system could not modify the date and time on the currently copied file.Action: None. This message is for information only. The file date and time will not be correct.175: An error occurred during FILER's attempt to push the list onto the stack. The newly created file won't appear in the directory contents list display.FILERExplanation: The currently created file will not show up in the directory contents list.Action: Return to the main menu and display the directory contents again. The list should be complete. For more information, see "BOOK="utlrfenu" COLLECTION="nw41"FILER" in Utilities Reference.180: The old file name was deleted from the selected directory, but the name of the file wasn't found in the directory's list of files.FILERExplanation: The file was deleted from the selected directory, but it was not found in the directory contents list. Action: None. This message is for information only.185: Error code was returned by the MapPath function.FILERExplanation: The MapPath function couldn't map a temporary drive to the current path.Action: Try again. For information on the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=202 ID="BP196"190: This utility was unable to set the directory attributes. Error code: code.FILERExplanation: An error occurred while trying to set the directory attributes.Action: Try again. For information on the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.195: The Find Directory attribute returned error code.FILERExplanation: The DOS function "dos_find_first" returned an error when trying to find the first directory entry in the current directory.Action: Try again. For information on the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.200: This utility couldn't get the volume number. Error code: code.FILERExplanation: FILER could not get the volume number from the NetWare server.Action: Try again. For information on the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.205: This utility was unable to get the volume attributes. Error code: code.FILERExplanation: An error occurred when FILER tried to get the volume attributes.Action: Try again. For information on the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.210: This utility was unable to set the volume attributes. Error code: code.FILERExplanation: An error occurred when FILER tried to set the volume attributes.Action: Try again. For information on the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.215: An invalid destination path has been specified. An entry can't be moved on or below the source path.FILERExplanation: A directory structure cannot be moved within itself.Action: Verify that the destination path is correct; then try the command again. For more information, see "BOOK="utlrfenu" COLLECTION="nw41"FILER" in Utilities Reference.220: An error occurred during FILER's attempt to get the volume number. Error code: code.FILERExplanation: FILER could not get the volume number from the NetWare server.Action: Try again. For information on the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=203 ID="BP197"225: Access has been denied.FILERExplanation: The user account does not have sufficient rights to delete the file. Action: Obtain the Delete right to the file. 230: Error code code was returned by the Scan386File function for file name.FILERExplanation: An error occurred while scanning the 386 file.Action: Try again. For information on the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.235: Error code code was returned by the SetDirectoryEntry function for file name.FILERExplanation: SetDirectoryEntry returned an error on the specified file.Action: Try again. For information on the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.240: The DOSCreate command returned error code code. The destination path was path. The destination volume may be out of file or directory entries.FILERExplanation: The error was caused by one of the following:MARK=BULLETThe user tried to copy a file to an area that has another file with the same name.The user account does not have sufficient rights to create the file. FILER encountered an error as it attempted to copy non-DOS files (such as MAC or OS/2) and create them in the destination directory.The file is in use in a nonsharing mode or is flagged Read Only. Action: Do one or more of the following: MARK=BULLETMake sure that the user account has sufficient rights to create a file in the destination directory. If the user account has Modify rights in the source directory, flag the file as Read Write; try again. If the file is in use, wait until the file is no longer in use.PAGENUM=204 ID="BP198"245: An error occurred writing to the destination file.FILERExplanation: When copying a file, FILER could not write to the destination file.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.250: An internal error occurred during FILER's attempt to copy the file.FILERExplanation: FILER tries to determine the cause of an error while copying a file. Sometimes the operating system (DOS or NetWare) is not explicit enough about the cause of the failure. This error message is followed by a secondary description of the problem. Action: Look up the secondary description of the problem to see if there are alternatives. For more information, see "BOOK="utlrfenu" COLLECTION="nw41"FILER" in Utilities Reference.255: The MOVE command can be used only to move items within the same volume. Choose a destination path that has the same volume as the source path.FILERExplanation: NetWare allows entries to be moved only within the same volume.Action: Choose a destination path that has the same volume as the source path.260: Error code occurred getting volume information.FILERExplanation: FILER could not get the volume information from the NetWare server.Action: Try again. For information on the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.265: The system is unable to GET or SET the directory limitation information.FILERExplanation: FILER could not get or set the directory information from the NetWare server.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.270: The current directory [name] contains a filename name which is an invalid DOS name. FILER can't copy directories or files with invalid names.FILERExplanation: An invalid DOS filename was found in the specified directory. Action: Rename the file to a valid DOS name; then try the command again.275: This utility can't attach to the server associated with volume object name.FILERExplanation: FILER cannot attach to the selected volume object on the server.Action: Make sure that the server is still running.PAGENUM=205 ID="BP199"280: This utility couldn't get the physical volume name associated with volume object name.FILERExplanation: The selected volume object is associated with a NetWare server. Each server has volumes, but FILER could not get the physical volume name.Action: Make sure that the server is still running.285: This utility couldn't create a context handle.FILERExplanation: FILER could not create a context handle. This could be a memory problem.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network.290: This utility couldn't get the default context.FILERExplanation: FILER encountered a problem while reading the NET.CFG file to get the user account default context.Action: Verify that "NAME CONTEXT=context" is in the NET.CFG file. For information on the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.295: This utility couldn't set the context.FILERExplanation: Either the user typed the NetWare Directory Services object name incorrectly, or the workstation does not have enough memory to set up the context.Action: Make sure that the object name is typed correctly. (You can use NETADMIN to verify the correct name.) If the problem is due to lack of memory, see "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network.300: This utility couldn't get the NFS extended file information. Error code: code.FILERExplanation: FILER encountered a problem while accessing the NFS extended file information.Action: For information on the specific error code, see IDREF="FM61529""Error Codes" in Appendix A.305: The number of extended attributes allowed per file on the destination server is smaller than the source server. The destination server limit must be the same or larger. Use the server NLM to change the parameter.FILERAction: Follow the actions specified in the message.907: The name file can't be found.FILERAction: Make sure the filename is spelled correctly. Make sure a file with the name specified really exists.PAGENUM=206 ID="BP200"908: The name file is an incorrect format and can't be used.FILERExplanation: The file is in a format that is incompatible with the action FILER is attempting to do with the file.Action: Change the format of the file so that FILER can recognize it.909: The name file is an incorrect version. Version version is required.FILERAction: Obtain the correct version, or contact your Novell Authorized Reseller.925: The server specified is a Personal NetWare server. You cannot attach to a Personal NetWare server with this utility. Use the Personal NetWare utilities to access this connection.FILERAction: See message IDREF="FM67645""925: The server specified is a Personal NetWare server. You cannot attach to a Personal NetWare server with this utility. Use the Personal NetWare utilities to access this connection." in Appendix C.970: The attempt to open the Unicode table files failed.FILERAction: See message IDREF="FM15675""970: The attempt to open the Unicode table files failed." in Appendix C.971: The workstation does not have enough memory to load the Unicode table files.FILERAction: See message IDREF="FM55341""971: The workstation does not have enough memory to load the Unicode table files." in Appendix C.972: Access to the Unicode table files was denied.FILERAction: See message IDREF="FM90152""972: Access to the Unicode table files was denied." in Appendix C.973: The Unicode table files cannot be found in the NLS directory or in the search path. Code page: <number>  Country:  <number>FILERAction: See message IDREF="FM62778""973: The Unicode table files cannot be found in the NLS directory or in the search path. Code page: number Country: number" in Appendix C.974: The Unicode table files are corrupt.FILERAction: See message IDREF="FM63405""974: The Unicode table files are corrupt." in Appendix C.PAGENUM=207 ID="BP201"975: The Unicode table files cannot be opened because there are already too many open files. Close some files or modify your CONFIG.SYS file.FILERAction: See message IDREF="FM49793""975: The Unicode table files cannot be opened because there are already too many open files. Close some files or modify your CONFIG.SYS file." in Appendix C.998: This utility couldn't load the Unicode tables.FILERAction: See message IDREF="FM15675""970: The attempt to open the Unicode table files failed." in Appendix C.999: The message file for this utility cannot be found.FILERAction: See message IDREF="FM69424""999: The message file for this utility cannot be found." in Appendix C.PAGENUM=208 ID="BP202"FIO1: The message file name is invalid. The program cannot be loaded.FIOExplanation: The .MSG file is invalid. This problem could be the result of a corrupted file, a faulty translation, or an outdated file version.Action: Either update the .MSG file with a valid copy or delete the file. The DOS Requester will use the default messages that are bound to the binary files.5: Module1.VLM is not loaded. The module2.VLM file cannot be loaded before module1.VLM. Load the module1.VLM file first then try to load the module2.VLM file.FIOExplanation: The module2.VLM requires that the module1.VLM be loaded first. Either the current configuration has module1.VLM and module2.VLM loading out of order, or module1.VLM did not load successfully.Action: Make sure that module1.VLM is configured to load before module2.VLM. To do this, change the load order of the "VLM=" parameter in the NET.CFG file.7: In order to load the module3.VLM, one of the following VLMs must be loaded: module1.VLM, module2.VLM.FIOExplanation: The module3.VLM requires that module1.VLM or module2.VLM be loaded first. Either the current configuration has module3.VLM loading before the modules in the module1.VLM or module2.VLM list, or module1.VLM or module2.VLM did not load successfully.Action: Make sure that module1.VLM or module2.VLM loads successfully before module3.VLM.42: There is a missing or invalid value for `parameter' on line number of the configuration file. This entry will be ignored. Correct the line specified in the configuration file before continuing.FIOExplanation: The configuration file contains a configuration keyword that has an invalid parameter or that does not specify a parameter. This invalid line will be ignored by the configuration process.Action: Because this line will be ignored, no action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message.PAGENUM=209 ID="BP203"43: There is a missing or invalid ON/OFF value for `parameter' on line number of the configuration file. This entry will be ignored. Correct the line specified in the configuration file before continuing.FIOExplanation: The configuration file contains a configuration keyword that is defined to use either an "On" or "Off" parameter, but a different parameter or no parameter has been specified. This invalid line will be ignored by the configuration process.Action: Because this line will be ignored, no action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message.45: The parameter specified for the following option was out of range and has been adjusted.FIOExplanation: A configurable parameter has been configured too high or too low to be valid. The parameter is specified on the line following the message.Action: Check and correct the parameter specified in the NET.CFG file. For information on the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.60: Too much cache is configured. The FIO.VLM file will reduce the cache blocks by number blocks and load successfully. Check the CACHE BUFFERS and BUFFER SIZE parameters in the NET.CFG file; then load the FIO.VLM file.FIOExplanation: The amount of cache available in DOS is limited by conventional memory. The parameters determining the amount of memory to be used are CACHE BUFFERS and BUFFER SIZE. These two buffers cannot be configured to use more than 64 KB of memory. One of these parameters must be reduced.Action: Reduce the "CACHE BUFFERS" or "BUFFER SIZE" parameter in the NET.CFG file. For information on the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.61: The IPX interface is not loaded. The FIO.VLM file will load successfully without packet burst support. Load the IPXODI 2.00 or later to use packet burst or add PB BUFFERS=0 to the NET.CFG file; then load FIO.VLM.FIOExplanation: This message is only a warning. The DOS Requester will function properly without the use of Packet Burst. The Packet Burst protocol, which is a part of FIO.VLM, requires IPXODI version 2.00 or later to function properly. There was no IPX interface loaded in this machine.PAGENUM=210 ID="BP204"Action: If Packet Burst is desired, make sure that IPXODI.COM version 2.00 or later is loaded before the DOS Requester. If Packet Burst is not desired, add "PB BUFFERS=0" to the NETWARE DOS REQUESTER section of the NET.CFG file. For information on the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.62: The LSL interface is not loaded. The FIO.VLM file will load successfully without packet burst support. Load the LSL module or add PB BUFFERS=0 to the NET.CFG file; then load FIO.VLM.FIOExplanation: An attempt was made to load the FIO.VLM file without the LSL module being previously loaded.Action: Before trying to load the FIO.VLM file, load the LSL.COM file. For information on the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.63: The IPX socket for packet burst could not be opened. The FIO.VLM file will load successfully without packet burst support. Configure the IPXODI.COM file for enough sockets in the NET.CFG file or add PB BUFFERS=0 to the NET.CFG file; then load the FIO.VLM file.FIOExplanation: This message is only a warning. The DOS Requester will function properly without the use of Packet Burst. The Packet Burst protocol, which is a part of the FIO.VLM module, requires an IPX socket to function properly. The request to open a socket failed, indicating that not enough IPX sockets are available.Action: If Packet Burst is desired, make sure that the IPX interface is configured for enough sockets in the NET.CFG file before loading the DOS Requester. If Packet Burst is not desired, add "PB BUFFERS=0" to the NETWARE DOS REQUESTER section of the NET.CFG file. For information on the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.64: The IPX interface is not version 2.00 or later. The FIO.VLM file will load successfully without packet burst support. Load the IPXODI.COM file version 2.00 or later or add PB BUFFERS=0 to the NET.CFG file; then load the FIO.VLM file.FIOExplanation: This message is only a warning. The DOS Requester will function properly without the use of Packet Burst. The Packet Burst protocol, which is a part of FIO.VLM, requires IPXODI version 2.00 or later to function properly. The version of IPXODI loaded was not version 2.00 or later.Action: If Packet Burst is desired, make sure that the IPXODI.COM file version 2.00 or later is loaded before the DOS Requester. If Packet Burst is not desired, add "PB BUFFERS=0" to the NETWARE DOS REQUESTER section of the NET.CFG file.PAGENUM=211 ID="BP205"65: The DOS Requester is being loaded in a Windows DOS box. The FIO.VLM file will load successfully without packet burst support.FIOExplanation: This message is only a warning. The DOS Requester will function properly without the use of Packet Burst. The Packet Burst protocol, which is a part of FIO.VLM, cannot function when loaded in a Windows DOS box.Action: The Packet Burst protocol cannot be enabled when loaded in a Windows DOS box. Your client workstation can use Packet Burst if it is loaded before Windows. To do this, exit Windows and load the VLM programs; then start Windows.PAGENUM=212 ID="BP206"FLAG001: Action has been terminated by the operator.FLAGExplanation: The FLAG was terminated by pressing MOREINFO="NONE"<Ctrl>+<C>, MOREINFO="NONE"<Ctrl>+<Break>, or MOREINFO="NONE"<Esc>.Action: None. This message is for information only.225: The mode you specified is reserved.FLAGExplanation: Mode 4 or 6 was entered. These modes are reserved and cannot be used.Action: Use modes 0, 1, 2, 3, 5, or 7.250: The assigned mode was invalid.FLAGExplanation: The mode that was entered was not in the valid range. Action: Use modes 0, 1, 2, 3, 5, or 7.275: Specify a file before assigning a mode.FLAGExplanation: You specified a valid directory path, not a filename. Directories cannot be assigned modes.Action: Specify a filename in the command. Type "FLAG /?" or see "BOOK="utlrfenu" COLLECTION="nw41"FLAG" in Utilities Reference for more information about FLAG command syntax.300: Access is denied.FLAGExplanation: The file is in use, or you are modifying directory attributes while another user is modifying the same directory. Or, you may not have adequate rights to access the file or modify directory attributes.Action: Use the RIGHTS utility to check your rights. If your user account has adequate rights, make sure that the file is not in use, or that another user is not currently modifying the directory attributes. For more information, see "BOOK="utlrfenu" COLLECTION="nw41"FLAG" in Utilities Reference.325: You do not have rights to change file or directory attributesFLAGExplanation: Your user account must have the Supervisor or Access Control right to modify file attributes.Action: Make sure the user has appropriate user access rights. Use the RIGHTS utility to find out what your user account rights are at the volume level, grant the appropriate user access rights, and try the command again.PAGENUM=213 ID="BP207"350: This utility was unable to set the attributes.FLAGExplanation: A request to change the attributes for a file or a directory was not successful for one of the following reasons:MARK=BULLETYour user account does not have the appropriate Supervisor or Access Control rights to change the attributes.The file is locked, or the directory attributes are being modified by another user.The file is in use or is corrupted.Action: Make sure the user has appropriate user access rights. Make sure the file is not in exclusive use by another process. Make sure that the file is not corrupted.400: This utility was unable to set the DOS file.FLAGExplanation: The file may be corrupted.Action: Try to read or run the file. If you can, flag the file again. If you can't, the file is probably corrupted. Get a new copy of the file, then flag the file.425: The specified attribute(s) is not supported in this version of NetWare.FLAGExplanation: You specified an attribute that is not supported by the NetWare server where the file is located. Action: Check the online help (type "FLAG /?") for a list of attributes supported by the server where the file is located. Be sure to run FLAG from the drive mapped to the file's location. For more information, see "BOOK="utlrfenu" COLLECTION="nw41"FLAG" in Utilities Reference.441: The /DO command is not supported for local drives.FLAGExplanation: The /DO command line option is not supported on local drives.Action: Do not use this option when referencing local drives.450: Owners cannot be assigned to local drives or files.FLAGExplanation: This attribute is not supported with files on local drives.Action: Do not use this attribute when assigning attributes to files on local drives. For more information, see "BOOK="utlrfenu" COLLECTION="nw41"FLAG" in Utilities Reference.PAGENUM=214 ID="BP208"450: The attribute_name attribute is not supported for local files.FLAGExplanation: The specified attribute is not supported for files on local drives.Action: Do not use this attribute when assigning attributes to files on local drives. For more information, see "BOOK="utlrfenu" COLLECTION="nw41"FLAG" in Utilities Reference.450: The Search mode is not supported for local files.FLAGExplanation: This attribute is not supported for files on local drives.Action: Do not use this attribute when assigning attributes to files on local drives. See "BOOK="utlrfenu" COLLECTION="nw41"FLAG" in Utilities Reference for more information about FLAG.575: This owner was not found.FLAGExplanation: The owner specified is not a user on the network.Action: Make sure that you typed the owner name correctly. Make sure that the owner you specified is a current user on the network. For more information, see "BOOK="utlrfenu" COLLECTION="nw41"FLAG" in Utilities Reference.625: This utility was unable to allocate the volume handle.FLAGExplanation: The client workstation is not attached to a server, or the volume does not exist, or it is not mounted.Action: If you use a server version prior to NetWare 4, the client workstation must be attached to the desired server. If you use a NetWare 4 server, the client workstation must map a drive to the volume and server or to the volume object. If the client workstation is attached to the server, make sure that the volume is mounted and that you typed the volume name correctly. For more information, see "BOOK="utlrfenu" COLLECTION="nw41"FLAG" in Utilities Reference.650: This utility cannot assign volume attributes in v2.x.FLAGExplanation: You cannot assign volume attributes on a NetWare 2 server.Action: Do not set volume attributes.673: This utility was unable to get the connection information.FLAGExplanation: For some reason, this utility was unable to get connection information.Action: Retry the command. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=215 ID="BP209"675: This utility was unable to change the volume attributes.FLAGExplanation: Your user account must have the Supervisor or Access Control right to change attributes.Action: Make sure the user has appropriate user access rights. Use the RIGHTS utility to find out what your user account rights are at the volume level, get the appropriate user access rights, and try the command again.700: The Execute Only attribute cannot be assigned to local files.FLAGExplanation: This attribute is not supported for files on local drives.Action: Do not use this attribute when assigning attributes to files on local drives. For more information, see "BOOK="utlrfenu" COLLECTION="nw41"FLAG" in Utilities Reference.725: The Private attribute cannot be assigned to local files.FLAGExplanation: This attribute is not supported for files on local drives.Action: Do not use this attribute when assigning attributes to files on local drives. For more information, see "BOOK="utlrfenu" COLLECTION="nw41"FLAG" in Utilities Reference.750: The Index attribute is not supported in v3.x or v4.x.FLAGExplanation: You tried to use the Index file attribute to flag a file located on a NetWare 3 or NetWare 4 server. This attribute only works on files located on NetWare 2 servers.Action: Do not use the Index file attribute to flag files located on NetWare 3 or NetWare 4 servers.775: The Private attribute is not supported in v3.x or v4.x.FLAGExplanation: You tried to use the Private file attribute on a file located on a NetWare 3 or NetWare 4 server. This attribute only works on files located on NetWare 2 servers.Action: Do not use the Private file attribute to flag files located on NetWare 3 or NetWare 4 servers.800: The Purge attribute is not supported in v2.x.FLAGExplanation: You tried to use the Purge file attribute on a file located on a NetWare 2 server. This attribute only works on files located on NetWare 3 and NetWare 4 servers.Action: Do not use the Purge file attribute to flag files located on NetWare 2 servers.PAGENUM=216 ID="BP210"819: You cannot assign a user and group at the same time.FLAGExplanation: Users and groups must be assigned in separate commands. You attempted to assign them at the same time.Action: Try again, assigning users and groups separately.825: The Copy Inhibit attribute is not supported in v2.xFLAGExplanation: You tried to use the Copy Inhibit file attribute to flag a file located on a NetWare 2 server. This attribute only works on files located on NetWare 3 and NetWare 4 servers.Action: Do not use Copy Inhibit file attribute to flag files on a NetWare 2 server.850: The Delete Inhibit attribute is not supported in v2.xFLAGExplanation: You tried to use the Delete Inhibit file attribute to flag a file located on a NetWare 2 server. This attribute only works on files located on NetWare 3 and NetWare 4 servers.Action: Do not use the Delete Inhibit file attribute to flag files located on NetWare 2 servers.875: The Rename Inhibit attribute is not supported in v2.xFLAGExplanation: You tried to use the Rename Inhibit file attribute to flag a file located on a NetWare 2 server. This attribute only works on files located on NetWare 3 and NetWare 4 servers.Action: Do not use the Rename Inhibit file attribute to flag files located on NetWare 2 servers.876: The Migrate attribute is supported only with NetWare v4.xFLAGExplanation: You tried to set the Migrate attribute on a server that is not a NetWare 4 server. This attribute is supported only on NetWare 4 servers. Action: Use the Migrate attribute only on a NetWare 4 server.877: The Compress attribute is supported only with NetWare v4.xFLAGExplanation: You tried to set the Immediate Compress or Don't Compress attribute on a server that is not a NetWare 4 server.Action: You cannot use the Immediate Compress or Don't Compress attribute on a server that is not a NetWare 4 server.PAGENUM=217 ID="BP211"878: You cannot set both the Immediate Compress and Don't Compress attributes.FLAGExplanation: You tried to set both the Immediate Compress file attribute and the Don't Compress file attribute. These two file attributes cannot both be set at the same time.Action: Decide if the file should be compressed or not compressed; then use the appropriate flag.879: Migration is not enabled on the server.FLAGExplanation: You attempted to use the Migration capability on a server that is not currently supporting migration.Action: Verify the Migration status on the server. If the problem persists, contact your Novell Authorized Reseller.880: Compression is not enabled on the server.FLAGExplanation: You attempted to use the Compression capability on a server that is not currently supporting compression.Action: Verify the Compression status on the server. If the problem persists, contact your Novell Authorized Reseller.901: You are not attached to the specified server.FLAGAction: See message IDREF="FM84261""901: You are not attached to the specified server." in Appendix C.903: The command line syntax is invalid.FLAGAction: See message IDREF="FM18860""903: The command line syntax is invalid." in Appendix C.905: This utility was unable to initialize the country information.FLAGAction: See message IDREF="FM55337""905: This utility was unable to initialize the country information." in Appendix C.908: The specified path is invalid.FLAGAction: See message IDREF="FM51165""908: The specified path is invalid." in Appendix C.909: You are not mapped to the specified drive.FLAGAction: See message IDREF="FM28663""909: You are not mapped to the specified drive." in Appendix C.910: This utility was unable to parse the specified path.FLAGAction: See message IDREF="FM47164""910: This utility was unable to parse the specified path." in Appendix C.PAGENUM=218 ID="BP212"911: Directory Services is not active at this time.FLAGAction: See message IDREF="FM53981""911: Directory Services is not active at this time." in Appendix C.912: The specified file cannot be found.FLAGAction: See message IDREF="FM74299""912: The specified file cannot be found." on page 1400.913: The specified directory cannot be found.FLAGAction: See message IDREF="FM19478""913: The specified directory cannot be found." in Appendix C.914: The specified file or directory cannot be found.FLAGAction: See message IDREF="FM82066""914: The specified file or directory cannot be found." in Appendix C.915: The specified volume does not exist.FLAGAction: See message IDREF="FM46881""915: The specified volume does not exist." in Appendix C.916: This utility only supports 25 levels of directories.FLAGAction: See message IDREF="FM77950""916: This utility only supports 25 levels of directories." in Appendix C.917: This utility was unable to set the context.FLAGAction: See message IDREF="FM32126""917: This utility was unable to set the context." in Appendix C.925: This utility is not supported on Personal NetWare servers.FLAGExplanation: FLAG does not support drives located on Personal NetWare servers.Action: Use the Personal NetWare utilities.970: The attempt to open the Unicode table files failed.FLAGAction: See message IDREF="FM15675""970: The attempt to open the Unicode table files failed." in Appendix C.971: The workstation does not have enough memory to load the Unicode table files.FLAGAction: See message IDREF="FM55341""971: The workstation does not have enough memory to load the Unicode table files." in Appendix C.972: Access to the Unicode table files was denied.FLAGAction: See message IDREF="FM90152""972: Access to the Unicode table files was denied." in Appendix C.PAGENUM=219 ID="BP213"973: The Unicode table files cannot be found in the NLS directory or in the search path. Code page: <number>  Country:  <number>FLAGAction: See message IDREF="FM62778""973: The Unicode table files cannot be found in the NLS directory or in the search path. Code page: number Country: number" in Appendix C.974: The Unicode table files are corrupt.FLAGAction: See messageIDREF="FM63405""974: The Unicode table files are corrupt." in Appendix C.975: The Unicode table files cannot be opened because there are already too many open files. Close some files or modify your CONFIG.SYS file.FLAGAction: See message IDREF="FM49793""975: The Unicode table files cannot be opened because there are already too many open files. Close some files or modify your CONFIG.SYS file." in Appendix C.998: The message file found (<utility_name>.MSG) is an incorrect version. The correct version is <number>. See your network supervisor for assistance.FLAGAction: See message IDREF="FM91957""998: The message file found (utility_name.MSG) is an incorrect version. The correct version is number. See your network supervisor for assistance." in Appendix C.999: The message file for this utility cannot be found.FLAGAction: See message IDREF="FM69424""999: The message file for this utility cannot be found." in Appendix C.PAGENUM=220 ID="BP214"FLTSRV0: Filter Services NLM did not load since it could not allocate Resource Tag.FLTSRVExplanation:  The server does not have enough memory to complete the operation.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.1: The system function at exit returned error code code.FLTSRVExplanation: This is an internal error.Action: Contact your Novell Authorized Reseller.2: The SNMP function PMFRegisterProtocolNotification returned error code code.FLTSRVExplanation:  This is an internal error that may occur if the system is low on memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.3: Error while parsing file filename line: line_text.FLTSRVExplanation: Someone may have edited the specified file and added an invalid or misspelled keyword.Action: Correct any editorial errors in the file. Unload FLTSRV. Do the operation again. If the problem persists, contact your Novell Authorized Reseller.4: The version of the filter database file filename is not compatible with the version of this NLM.FLTSRVExplanation: You may have hand-copied a version of the FLTSRV.NLM file that is incompatible with the filter database file in the system.Action: Follow the normal installation procedure to install FLTSRV. If the problem persists, contact your Novell Authorized Reseller.5: Unexpected keyword word in filter database file filename.FLTSRVExplanation: Someone may have edited the specified file and added an invalid or misspelled keyword.Action: Correct any editorial errors in the file. Unload FLTSRV. Do the operation again. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=221 ID="BP215"6: Could not open file filename for write access.FLTSRVExplanation: FLTSRV could not open the filter database file specified in the error message. The configured filters were not saved.Action:  Make sure that the directory specified in the filename  parameter exists and that the specified file does not already exist with read-only permission.7: Could not open configuration file filename. FLTSRVExplanation: FLTSRV could not read the configuration file NETINFO.CFG. The file may have been accidentally deleted.Action: Reinstall NetWare. If the problem persists, contact your Novell Authorized Reseller.8: The version of the configuration file filename is not compatible with this NLM.FLTSRVExplanation: This message refers to the configuration file NETINFO.CFG. You may have copied a version of the FLTSRV.NLM file that is incompatible with the version of the NETINFO.CFG file on the server.Action: Follow the normal installation procedure to install FLTSRV. If the problem persists, contact your Novell Authorized Reseller.9: Invalid Filter Status value status_word.FLTSRVExplanation: Someone may have edited the filter database file FILTERS.CFG and added an invalid Filter Status value. Valid status keywords are ENABLED and DISABLED.Action: Correct any editorial errors in the file. Unload FLTSRV. Do the operation again. If the problem persists, contact your Novell Authorized Reseller.10: Invalid Filter Action value action_word.FLTSRVExplanation: Someone may have edited the filter database file FILTERS.CFG and added an invalid filter action value. Valid filter action keywords are ALLOW and DENY.Action: Correct any editorial errors in the file. Unload FLTSRV. Do the operation again. If the problem persists, contact your Novell Authorized Reseller.11: Undefined Location location_name.FLTSRVExplanation: Someone may have edited the filter database file FILTERS.CFG and added a misspelled Location name.Action: Correct any editorial errors in the file. Unload FLTSRV. Do the operation again. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=222 ID="BP216"12: Undefined Service Group service_group_name.FLTSRVExplanation: Someone may have edited the filter database file FILTERS.CFG and added a misspelled service group name.Action: Correct any editorial errors in the file. Unload FLTSRV. Do the operation again. If the problem persists, contact your Novell Authorized Reseller.13: Could not allocate memory.FLTSRVExplanation: The server has insufficient memory to complete the operation.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.14: Unexpected input input_word in filter database file.FLTSRVExplanation: Someone may have edited the filter database file FILTERS.CFG and added an invalid or misspelled keyword.Action: Correct any editorial errors in the file. Unload FLTSRV. Do the operation again. If the problem persists, contact your Novell Authorized Reseller.15: Protocol protocol_name does not support Service Information filtering.FLTSRVExplanation: Someone may have edited the filter database file, FILTERS.CFG, and added an invalid protocol name for service information filters. Valid protocol names are IPX and APPLETLK.Action: Correct any editorial errors in the file. Unload FLTSRV. Do the operation again. If the problem persists, contact your Novell Authorized Reseller.16: Protocol protocol_name does not support Routing Information Filtering.FLTSRVExplanation: Someone may have edited the filter database file, FILTERS.CFG, and added an invalid protocol name for Routing Information filters. Valid protocol names are IPX, TCPIP, and APPLETLK.Action: Correct any editorial errors in the file. Unload FLTSRV. Do the operation again. If the problem persists, contact your Novell Authorized Reseller.17: Error code while delivering filters to the Bridge NLM.FLTSRVExplanation: This is an internal error.Action: Contact your Novell Authorized Reseller.PAGENUM=223 ID="BP217"18: Error code while delivering filters to protocol protocol_name.FLTSRVExplanation: This is an internal error.Action: Contact your Novell Authorized Reseller.19: Service service_name is not defined for protocol protocol_name.FLTSRVExplanation:  Someone may have edited the filter database file, FILTERS.CFG, and added an invalid or misspelled service name or protocol name.Action: Correct any editorial errors in the file. Unload FLTSRV. Do the operation again. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=224 ID="BP218"GENERAL1: The message file name is invalid. The program cannot be loaded.GENERALExplanation: The .MSG file is invalid. This could be the result of a corrupted file, a bad translation, or an outdated file version.Action: Either update the .MSG file with a valid copy or delete the file. The DOS Requester will use the default messages bound to the binary files.5: Module1.VLM is not loaded. The module2.VLM file cannot be loaded before module1.VLM. Load the module1.VLM file first then try to load the module2.VLM file.GENERALExplanation: The module2.VLM requires that the module1.VLM be loaded first. Either the current configuration has module1.VLM and module2.VLM loading out of order, or module1.VLM did not load successfully.Action: Make sure that module1.VLM is configured to load before module2.VLM. To do this, change the load order of the "VLM=" parameter in the NET.CFG file.7: In order to load the module3.VLM, one of the following VLM programs must be loaded: module1.VLM, module2.VLM.GENERALExplanation: The module3.VLM requires that module1.VLM or module2.VLM be loaded first. Either the current configuration has module3.VLM loading before the modules in the module1.VLM or module2.VLM list, or module1.VLM or module2.VLM did not load successfully.Action: Make sure that module1.VLM or module2.VLM loads successfully before module3.VLM.42: There is a missing or invalid value for `parameter' on line number of the configuration file. This entry will be ignored. Correct the line specified in the configuration file before continuing.GENERALExplanation: The configuration file contains a configuration keyword that has an invalid parameter or that does not specify a parameter. This invalid line will be ignored by the configuration process.Action: Because this line will be ignored, no action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message.PAGENUM=225 ID="BP219"43: There is a missing or invalid ON/OFF value for `parameter' on line number of the configuration file. This entry will be ignored. Correct the line specified in the configuration file before continuing.GENERALExplanation: The configuration file contains a configuration keyword that is defined to use either an "ON" or "OFF" parameter, but a different parameter or no parameter has been specified. This invalid line will be ignored by the configuration process.Action: Because this line will be ignored, no action is required at this point. However, to avoid this message the next time VLM.EXE is loaded, delete or correct the line specified by the error message.45: The parameter specified for the following option was out of range and has been adjusted.GENERALExplanation: A configurable parameter has been configured too high or too low to be valid. The parameter is specified on the line following the message.Action: Correct the parameter in the NET.CFG file. For information on the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.PAGENUM=226 ID="BP220"HCSS.NLM500: HCSS is unable to attain Low Threshold.HCSS.NLMExplanation: Files are on the HCSS volume that could not be migrated, which prevents the low threshold (settable through the NetWare Administrator "HCSS Parameters" dialog or the server console) from being reached; or the low threshold is not attainable, because of directory space overhead, etc., on the HCSS volume.Files that should be migrating might not be migrating because of the file attributes. Media may be full. Also, if the lower threshold is set to 0%, this message will be displayed regularly.Action: Remove the files outside the HCSS domain from the volume because they will not migrate. Make sure that the Don't Migrate file attribute is "Off." If the Migrate Unarchived Files file attribute is "Off," then files must be archived before they will migrate. If the Migrate Compressed Files Only file attribute is "On," make sure compression for the volume is enabled and the compression parameters are set appropriately.501: HCSS is unable to unload media.HCSS.NLMExplanation: One or more files on the media cannot be migrated. Files may be open, the Don't Migrate file attribute may be set to "On," or the HCSS Migrate Unarchived Files parameter (settable using NetWare Administrator "HCSS Parameters" dialog or the server console) may be set to "Off" while unarchived files are present in the media-label directories.Action: Close the open files. Set the Don't Migrate file attribute to "Off." Archive all the files in the directory. Set the Migrate Unarchived Files attribute to "On."Explanation: The media that is being exported may be so full that HCSS could not migrate all the files in this media-label directory to the media before exporting.Action: If the media is full, move or delete unmigrated files from the media-label directories before requesting an export of this media.503: HCSS is unable to migrate file full path and file name.HCSS.NLMExplanation: HCSS cannot migrate file full path and file name from the selected volume.Action: Make sure the volume is mounted. Also, make sure that Data Migration is set to "On" by selecting "Volume Options" from the "Selective Install" menu of the INSTALL NLM program, selecting the volume, then setting Data Migration to "On."Make sure the media is not full. See the HCSS console command "HCSS Media Status." If the media is full, and the file that failed to migrate must be migrated, then move or delete files from the media-label directory to make room for the file you wish to migrate.PAGENUM=227 ID="BP221"504: HCSS is unable to migrate files. Migration is inhibited on volume name.HCSS.NLMExplanation: The HCSS volume's migration attribute has been changed to the Don't Migrate file attribute, or the volume was not installed with Migration set to "On."Action: Use NetWare Administrator to turn off "Disable Migration," or use INSTALL to change the settings for this volume.505: HCSS is unable to access the jukebox.HCSS.NLMExplanation: HCSS could not verify that a jukebox device was present on the server when it tried to send the jukebox a command.Action: Make sure that the jukebox is on and that the cables and terminators are connected correctly. Make sure the SCSI controller card that is connected to the jukebox is functioning properly. Make sure the appropriate jukebox driver is loaded before loading HCSS, and SCAN FOR NEW DEVICES has been typed at the server console. Make sure the jukebox is listed by typing LIST DEVICES at the server console. If the jukebox is not listed, see "BOOK="superenu" COLLECTION="nw41"Migrating Data Using the High Capacity Storage System" in Supervising the Network for further information about troubleshooting the jukebox and SCSI controller card path.506: Write to media failed: numberHCSS.NLMExplanation: The HCSS request to write data to media in the jukebox optical drive failed. This is likely a result of a device failure.Action: Check the status of the jukebox, the jukebox optical drive, and the media in the drive. For more information, see the documentation for the hardware.507: Read from media failed: numberHCSS.NLMExplanation: The HCSS request to read data from the media in the jukebox optical drive failed. This is likely a result of a device failure.Action: Check the status of the jukebox, the jukebox optical drive, and the media in the drive. For more information, see the documentation for the hardware.508: Media labeled media label is unavailable for file migration/demigration.HCSS.NLMExplanation: The media labeled media label is no longer found in the jukebox, possibly because the media was manually ejected before HCSS was loaded. Action: Manually reload the media that was removed from the jukebox, and reload the jukebox driver and HCSS (run HRELOAD.NCF) to reinventory the jukebox.PAGENUM=228 ID="BP222"509: No HCSS directory corresponds to the media labelled label. Media is being ejected.HCSS.NLMExplanation: HCSS verifies that the first-level subdirectories correspond to the media in the jukebox. If the media does not correspond to a first-level subdirectory, the jukebox ejects the media.Action: Remove the media from the mail slot and type "media removed" at the server console. If the media was originally ejected from a jukebox using the HCSS Unload command, reload it using the HCSS Load command. For more information, see "BOOK="superenu" COLLECTION="nw41"Managing The HCSS File System" in Supervising the Network.510: Initialization (jukebox inventory) failed.HCSS.NLMAction: A hardware error or driver error occurred during inventory.Action: If other error messages are reported at the same time, resolve those errors and reload HCSS. If the error repeats, make sure the hardware and drivers are installed correctly.511: Movement of media in the jukebox failed.HCSS.NLMExplanation: When HCSS requested media to move in the jukebox, the jukebox failed to complete the requested movement, possibly because of media in the jukebox that was manually inserted without registering it with HCSS through NetWare Administrator. Action: Make sure the mailslot did not have media in it when media was requested to be ejected. Make sure the jukebox is functioning correctly (run any diagnostics recommended by the jukebox manufacturer). Make sure the SCSI cables are connected correctly.ID="FM63978"512: Non-HCSS media was found. Media is being ejected.HCSS.NLMExplanation: The media was not formatted by HCSS, was write-protected, or the media did not have the manufacturer's low-level format.Action: Do one of the following:MARK=BULLETIf the media was write-protected, remove the write-protection, unload HCSS by running HUNLOAD from the server, manually insert the media into the jukebox, then reload HCSS. If the media does not have a low-level format, use one that does.If the media was not formatted by HCSS, format it and assign it using NetWare Administrator.PAGENUM=229 ID="BP223"ID="FM53846"513: HCSS failed to mount the media.HCSS.NLMExplanation: HCSS was unable to mount media in a jukebox drive, probably because of a drive failure or media errors while reading the media.Action: Make sure each jukebox drive is functioning correctly. If dirty media is suspected, follow the manufacturer's recommended cleaning procedure for the media being used. If the problem persists, contact your Novell Authorized Reseller.514: HCSS is being unloaded.HCSS.NLMExplanation: HCSS has been requested to unload because of an HUNLOAD or HRELOAD command, a server requested to go down, or a manual unload of the HCSS NLM programs.Action: Wait for HCSS to finish the unload process.515: Error posting HCSS messages to Error log. Messages may have been lost.HCSS.NLMExplanation: The file SYS:HCSSERR.LOG was unavailable when HCSS tried to write to it, possibly because it was open or had been flagged Read Only.Action: Make sure the log file is not open. Make sure the file attributes are set correctly.Explanation: The server may have insufficient memory to run the Error Log.Action: Increase the available memory. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.Explanation: Disk space on the volume SYS: may be insufficient.Action: Increase the available disk space on the volume. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Disk Space Problems" in Supervising the Network.516: Available memory is insufficient.HCSS.NLMExplanation: The system does not have enough memory to complete the operation.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. Note: the results of low memory conditions are unpredictable.ID="FM25373"517: Media name exceeded remaining capacity limit.HCSS.NLMExplanation: The side of media labeled name has been filled to exceed the threshold set by the HCSS Remaining Capacity Before Warning parameter, which is settable through the NetWare Administrator "HCSS Parameters" dialog or the server console.Action: Delete or move the files assigned to this side of media, or raise the warning threshold percentage to a higher value. Increasing the warning frequency will decrease the frequency of the message.PAGENUM=230 ID="BP224"518:  Ejecting media with duplicate label name.HCSS.NLMExplanation: During an inventory, HCSS discovered duplicate media-label names and is ejecting all media with the same name.Action: After each ejected media is removed from the mailslot, type "media removed" at the server console. If each media that was ejected has valid data on it, reimport the first media and copy all the files from it to another media-label directory with a different name (if the files need to be migrated, or else copy the files to a volume with sufficient space for the files) Export this media, then import the next media and repeat the process until all files are assigned to a unique media-label directory.519: Failed to create name.HCSS.NLMExplanation: The HCSS domain or media-label directory labeled name could not be created.Action: Try another name for the directory.521: Could not restore attributes for name.HCSS.NLMExplanation: When media was imported, HCSS was unable to restore the NetWare attributes for file name.Action: Restore the NetWare attributes to the desired settings for the file name using FLAG.522: Info file failure. Some files may not have NetWare attributes.HCSS.NLMExplanation: When media was imported, part or all the information file that contains NetWare attributes for the importing files was not readable.Action: Make sure the NetWare attributes are set as desired and restore them as needed using FLAG for all files in both media-label directories on this media.523: Info file could not be opened. HCSS.NLMExplanation: When media was imported, the information file that contains NetWare attributes was not found or could not be opened. This error will occur if media is being imported that was not properly exported.Action: Using FLAG, restore the appropriate NetWare attributes for all files in both media-label directories on this media.524: Media label directory already exists.HCSS.NLMExplanation: A directory by the same name as one of the media labels on the importing media already exists in the domain directory.PAGENUM=231 ID="BP225"Action: If the media must be imported and the existing directory is not a media-label directory, then delete or rename the existing directory and attempt the import again. If the directory is a media-label directory, then export the media associated with the existing media-label directory and attempt the import again.525:  Failed to delete name.HCSS.NLMExplanation: Name could not be deleted from the media. Typically, this message is the result of a hardware failure.Action: None. This message is for information only.526: Upper threshold exceeded.HCSS.NLMExplanation: The HCSS volume has been filled to the upper threshold level, which is settable through NetWare Administrator or the server console. HCSS will now attempt to migrate files from the volume onto the media based on the migration algorithm until the lower threshold is reached. This message will repeat each time the polling frequency is reached as long as the upper threshold is exceeded.Action: If this threshold setting and HCSS operation is acceptable, no action is required. If this message appears frequently, try adjusting one or more HCSS parameters to customize the HCSS operation.527: Decider suspended due to volume name dismount.HCSS.NLMExplanation: For some reason, the HCSS volume name was dismounted. The program that determines whether migration needs to occur on volume name has been suspended until the volume is remounted.Action: Determine why the volume dismounted, and remount it if possible.528: Error loading message table for HCSS.HCSS.NLMExplanation: The HCSS message table could not be found or failed to load.Action: Make sure the HCSSERR.MSG file is in the appropriate SYS:\SYSTEM\NLS\* subdirectory for the language being used. When the file is in the correct directory, reload HCSS. If the message recurs, make sure the rights for this file are set appropriately.529: Asynchronous Deletes disabled.HCSS.NLMExplanation: HCSS was unable to create, open, or read the SYS:ASYNCDEL.QUE hidden file during initialization, or the file was corrupted. Media in the jukebox may not have the expected full capacity available because migrated files that were deleted from the volume may exist on the media.Action: None. This message is for information only.PAGENUM=232 ID="BP226"530: HCSS Disabled due to IO Engine Failure.HCSS.NLMExplanation: The NetWare® 4.1 SFT IIITM IO engine where HCSS is running has failed.Action: After restoring the IO engine, unload and reload HCSS.1000:  HCSS is up and running on name.HCSS.NLMExplanation: This message is to notify user ADMIN (if logged in) that HCSS on server name has finished initializing after an HCSS load or reload. This message is also recorded in SYS:HCSSERR.LOG on the server.Action: None. This message is for information only.PAGENUM=233 ID="BP227"HFSCD12: Resource tag allocation failure.HFSCDExplanation: An error occurred when HFSCD.NLM tried to obtain a resource tag from the operating system. Sever memory is probably low. HFSCD.NLM unloads when this error occurs.Action: For information on solving server memory problems, see "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.13: Unable to create CD-ROM Migrator process.HFSCDExplanation: When you load HFSCD.NLM, the module creates the process that enables you to remove CD-ROM data from the server's hard disk. This process is present all the time that HFSCD.NLM is loaded, but it runs only when you specify that the Migrator carry out its task. This error is returned when HFSCD.NLM is loaded, and it was unable to create the Migrator process, probably because the server does not have enough memory.Action: For information on solving server memory problems, see "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.14: No memory for launching Asynchronous Event Scheduler init process.HFSCDExplanation: The server is probably low on memory. HFSCD.NLM cannot be loaded.Action: For information on solving server memory problems, see "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.15: Error number registering application with Data Migration Manager.HFSCDExplanation: An error occurred when HFSCD.NLM attempted to register with RTDM.NLM. You may not be using the current versions of RTDM.NLM and HFSCD.NLM. Or, the server may be low on memory. HFSCD.NLM unloads when this error occurs.Action: Make sure you are loading the current versions of RTDM.NLM and HFSCD.NLM. If you are loading the current versions, check memory at the server.If memory is low, see "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. After server memory problems are resolved, retry loading HFSCD.NLM.16 Error number registering application with Media Manager.HFSCDPAGENUM=234 ID="BP228"Explanation: An error occurred when HFSCD.NLM attempted to register with the Media Manager in the NetWare operating system. You may not be using the current versions of the operating system and the HFSCD.NLM. Or, the server may be low on memory. HFSCD.NLM unloads when this error occurs. Action: Make sure you are loading the current versions of NetWare and HFSCD.NLM. If you are loading the correct versions, check memory at the server. If memory is low, see "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.17: This version of HFSCD.NLM is not compatible with the version of NetWare currently loaded. HFSCD.NLM requires NetWare v4.01 or higher.HFSCDExplanation: You are running a version of NetWare earlier than NetWare 4.01.Action: Upgrade the server to run NetWare 4.01 or later. 18: Error number registering application for volume events.HFSCDExplanation: You may not be using the current versions of the operating system and HFSCD.NLM. Or, the server may be low on memory. HFSCD.NLM unloads when this error occurs. Action: Make sure you are loading the current versions of NetWare and HFSCD.NLM. If you are loading the current versions, check memory at the server.If memory is low, see "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. After server memory problems are resolved, retry loading HFSCD.NLM.19: Error number registering application for media events.HFSCDExplanation: You may not be using the current versions of the operating system and HFSCD.NLM. Or, the server may be low on memory. HFSCD.NLM unloads when this error occurs. Action: Make sure you are loading the current versions of NetWare and HFSCD.NLM. If you are loading the current versions, check memory at the server.If memory is low, see "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. After server memory problems are resolved, retry loading HFSCD.NLM.20: Unable to allocate memory for Migrator stack.HFSCDExplanation: HFSCD.NLM was unable to allocate sufficient memory for a process stack to start the Migrator process. Action: For information on solving server memory problems, see "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.PAGENUM=235 ID="BP229"25: Unloading HFSCD will make migrated CD-ROM files inaccessible.HFSCDExplanation: This warning message appears when you try to unload HFSCD.NLM. Any CD-ROM files that have been removed from the server hard disk will no longer be accessible.Action: None. This message is for information only.31: No memory for processing media event. Event #num1 Media #num2HFSCDExplanation: A media event occurs whenever you insert a disc into or remove a disc from a disc drive, or whenever a disc drive experiences a fatal error. If a media event cannot be processed because memory is low, the status of discs appearing in the HFSCDCON Disc List may not be accurate.Action: For information on solving server memory problems, see "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.52: Migration Key created with newer version of HFSCD.NLM.HFSCDExplanation: This error can occur when you run a version of the HFSCD.NLM previous to 4.10 on the same machine on which a 4.10 version of this NLM has been run.Action: Run version 4.10 of HFSCD.NLM.53: Attempt made to de-migrate file name from the name disc. Disc not found!HFSCDExplanation: A user tried to access the file name on the CD-ROM disc name, but the disc is not in a CD-ROM drive.Action: Insert the appropriate disc in the drive.54: Attempt made to de-migrate file name from the name disc. Disc not mounted!HFSCDExplanation: A user attempted to access the file name on the CD-ROM disc name, but the disc is not mounted.Action: Insert the appropriate disc in the drive.55: Attempt made to de-migrate file name from the name disc. Error number activating the disc!HFSCDExplanation: A user tried to access the file name on the CD-ROM disc name, but an error occurred when HFSCD.NLM attempted to activate the disc. Action: Make sure the disc is inserted into the disc drive and the drive is operating properly.PAGENUM=236 ID="BP230"56: Migration Key created with newer version of HFSCD.NLM.HFSCDExplanation: This error can occur when you run a pre-4.10 version of HFSCD.NLM on the same machine on which a 4.10 version of HFSCD.NLM has been run.Action: Run version 4.10 of HFSCD.NLM.191: Error number initializing disc. Disc cannot be mounted.HFSCDExplanation: This error occurs when HFSCD.NLM attempts to mount a non-HFS disc.Action: Insert an HFSCD disc in the drive.PAGENUM=237 ID="BP231"HFSCDCON1: Unable to allocate memory.HFSCDCONExplanation: HFSCDCON.NLM was unable to allocate sufficient memory for the process the user tried to perform.Action: For information on solving server memory problems, see "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.2: Unable to allocate memory.HFSCDCONExplanation: HFSCDCON.NLM was unable to allocate sufficient memory for the process the user tried to perform.Action: For information on solving server memory problems, see "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.3: This version of HFSCDCON.NLM is not compatible with the HFSCD.NLM that is currently loaded.HFSCDCONExplanation: HFSCD.NLM and HFSCDCON.NLM are released as a set and have internal version numbers associated with them to ensure that the two are compatible. This error message indicates that the version of HFSCDCON.NLM you are running is older or newer than the version of HFSCD.NLM currently loaded.Action: Obtain and run the appropriate version of HFSCDCON.NLM.7: Resource tag allocation failure.HFSCDCONExplanation: An error occurred when HFSCD.NLM tried to obtain a resource tag from the operating system. Memory at the server is probably low. HFSCD.NLM unloads when this error occurs.Action: For information on solving server memory problems, see "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.9: Error number opening a screen.HFSCDCONExplanation: HFSCDCON.NLM generated this error when attempting to open a screen for display at the console. The most likely reason for this error is a low memory condition at the server.Action: For information on solving server memory problems, see "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.PAGENUM=238 ID="BP232"11: Unable to allocate memory for Main Process stack.HFSCDCONExplanation: HFSCDCON.NLM was unable to allocate sufficient memory for the process the user tried to perform.Action: For information on solving server memory problems, see "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.25: Unable to allocate memory.HFSCDCONExplanation: HFSCDCON.NLM was unable to allocate sufficient memory for the process the user tried to perform.Action: For information on solving server memory problems, see "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.27: Unable to allocate memory.HFSCDCONExplanation: HFSCDCON.NLM was unable to allocate sufficient memory for the process the user tried to perform.Action: For information on solving server memory problems, see "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.32: Unable to allocate memory.HFSCDCONExplanation: HFSCDCON.NLM was unable to allocate sufficient memory for the process the user tried to perform.Action: For information on solving server memory problems, see "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.34: The specified directory does not exist.HFSCDCONExplanation: The user specified that HFSCD.NLM should scan CD-ROM files into a directory that does not exist.Action: Specify the appropriate directory in HFSCDCON.NLM.36: Unable to allocate memory.HFSCDCONExplanation: HFSCDCON.NLM was unable to allocate sufficient memory for the process the user tried to perform.Action: For information on solving server memory problems, see "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.PAGENUM=239 ID="BP233"39: The specified directory does not exist.HFSCDCONExplanation: You specified that HFSCD.NLM should scan CD-ROM files into a directory that does not exist.Action: Specify the appropriate directory in HFSCDCON.NLM.40: Unable to find the selected disc.HFSCDCONExplanation: HFSCD.NLM cannot find a disc that appeared in the disc list. This error is most likely to occur on NetWare® 4.1 SFT IIITM systems when duplicate discs are not available on each system and one of the systems goes down.Action: Make sure that duplicate discs are available on each system.41: No root path found for this disc.HFSCDCONExplanation: The disc has not yet been scanned onto a mounted NetWare volume. Action: If the disc was scanned onto a NetWare volume that is not mounted, you should mount that NetWare volume. Or, you can scan the disc onto any mounted NetWare volume.43: Unable to allocate memory.HFSCDCONExplanation: HFSCDCON.NLM was unable to allocate sufficient memory for the process the user tried to perform.Action: For information on solving server memory problems, see "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.45: Unable to find the selected disc.HFSCDCONExplanation: HFSCD.NLM cannot find a disc that appeared in the disc list. This error is most likely to occur on NetWare® 4.1 SFT IIITM systems when duplicate discs are not available on each system and one of the systems goes down.Action: Make sure that duplicate discs are available on each system.46: Disc has not been scanned. Scan disc now?HFSCDCONExplanation: This message appears when you attempt to mount a previously unscanned disc volume.Action: To scan the disc, specify "Yes." If you do not want to scan the disc at this time, specify "No."PAGENUM=240 ID="BP234"48: Error number scanning disc: No Macintosh name space on this volume.HFSCDCONExplanation: HFSCD.NLM cannot scan the disc contents onto a NetWare volume because the Macintosh name space has not been added to the volume. Action: Add the Macintosh name space to the NetWare volume. For information, see "BOOK="nwmfpenu" COLLECTION="nw41"Adding the Macintosh Name Space after Installation" in NetWare for Macintosh File and Print Services.49: Error number scanning disc.HFSCDCONExplanation: An error occurred while HFSCD.NLM was scanning a disc onto a NetWare volume.Action: For information on how to proceed, refer to the error message specified by number.50: Error number Mounting Disc.HFSCDCONExplanation: An error occurred while HFSCD.NLM was attempting to mount a disc.Action: For information on how to proceed, refer to the error message specified by number.51: Disc in use! Cannot be dismounted.HFSCDCONExplanation: You tried to dismount a disc that is currently in use.Action: Wait until the disc is no longer in use before trying to dismount it.52: Error number Dismounting Disc.HFSCDCONExplanation: An error occurred while HFSCD.NLM was dismounting a disc.Action: For information on how to proceed, refer to the error message specified by number.54: Unable to allocate memory.HFSCDCONExplanation: HFSCDCON.NLM was unable to allocate sufficient memory for the process the user tried to perform.Action: For information on solving server memory problems, see "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.56: Unable to allocate memory.HFSCDCONExplanation: HFSCDCON.NLM was unable to allocate sufficient memory for the process the user tried to perform.Action: For information on solving server memory problems, see "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.PAGENUM=241 ID="BP235"59: Unable to add an entry to a menu.HFSCDCONExplanation: HFSCDCON.NLM generated this error when attempting to add items to a menu for display at the console. The most likely reason for this error is a low memory condition at the server.Action: For information on solving server memory problems, see "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.60: Unable to find the selected disc.HFSCDCONExplanation: HFSCD.NLM cannot find the disc you selected. This error is most likely to occur on NetWare® 4.1 SFT IIITM systems when duplicate discs are not available on each system and one of the systems goes down.Action: Make sure that duplicate discs are available on each system.63: Unable to allocate memory.HFSCDCONExplanation: HFSCDCON.NLM was unable to allocate sufficient memory for the process the user tried to perform.Action: For information on solving server memory problems, see "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.64: Unable to allocate memory.HFSCDCONExplanation: HFSCDCON.NLM was unable to allocate sufficient memory for the process the user tried to perform.Action: For information on solving server memory problems, see "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.66: Unable to allocate memory.HFSCDCONExplanation: HFSCDCON.NLM was unable to allocate sufficient memory for the process the user tried to perform.Action: For information on solving server memory problems, see "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.67: Unable to allocate memory.HFSCDCONExplanation: HFSCDCON.NLM was unable to allocate sufficient memory for the process the user tried to perform.Action: For information on solving server memory problems, see "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.PAGENUM=242 ID="BP236"70: Unable to allocate memory.HFSCDCONExplanation: HFSCDCON.NLM was unable to allocate sufficient memory for the process the user tried to perform.Action: For information on solving server memory problems, see "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.71: Unable to allocate memory.HFSCDCONExplanation: HFSCDCON.NLM was unable to allocate sufficient memory for the process the user tried to perform.Action: For information on solving server memory problems, see "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.73: Unable to allocate memory.HFSCDCONExplanation: HFSCDCON.NLM was unable to allocate sufficient memory for the process the user tried to perform.Action: For information on solving server memory problems, see "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.75: Unable to allocate memory.HFSCDCONExplanation: HFSCDCON.NLM was unable to allocate sufficient memory for the process the user tried to perform.Action: For information on solving server memory problems, see "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.92: Unable to allocate memory.HFSCDCONExplanation: HFSCDCON.NLM was unable to allocate sufficient memory for the process the user tried to perform.Action: For information on solving server memory problems, see "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.93: Unable to find the selected volume.HFSCDCONExplanation: HFSCD.NLM cannot find a disc that appeared in the disc list. This error is most likely to occur on NetWare® 4.1 SFT IIITM systems when duplicate discs are not available on each system and one of the systems goes down.Action: Make sure that duplicate discs are available on each system.PAGENUM=243 ID="BP237"95: Unable to allocate memory.HFSCDCONExplanation: HFSCDCON.NLM was unable to allocate sufficient memory for the process the user tried to perform.Action: For information on solving server memory problems, see "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.96: Unable to allocate memory.HFSCDCONExplanation: HFSCDCON.NLM was unable to allocate sufficient memory for the process the user tried to perform.Action: For information on solving server memory problems, see "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.98: Unable to allocate memory.HFSCDCONExplanation: HFSCDCON.NLM was unable to allocate sufficient memory for the process the user tried to perform.Action: For information on solving server memory problems, see "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.99: Unable to allocate memory.HFSCDCONExplanation: HFSCDCON.NLM was unable to allocate sufficient memory for the process the user tried to perform.AAction: For information on solving server memory problems, see "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.100: Error number saving the specified space limit on volume.HFSCDCONExplanation: HFSCD.NLM could not limit the NetWare volume space to be used by scanned files as specified in HFSCDCON.NLM.Action: For information on how to proceed, refer to the error message specified by number.103: Unable to allocate memory.HFSCDCONExplanation: HFSCDCON.NLM was unable to allocate sufficient memory for the process the user tried to perform.Action: For information on solving server memory problems, see "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.PAGENUM=244 ID="BP238"115: Error number saving parameters.HFSCDCONExplanation: HFSCDCON.NLM could not save the configuration parameters you entered to the volume SYS:.Action: For information on how to proceed, refer to the error message specified by number.116: Unable to allocate memory.HFSCDCONExplanation: HFSCDCON.NLM was unable to allocate sufficient memory for the process the user tried to perform.Action: For information on solving server memory problems, see "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.119: ERROR - Unable to start Migrator.HFSCDCONExplanation: HFSCD.NLM could not start the Migrator, probably because the server is low on memory.Action: For information on solving server memory problems, see "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.125: Unable to add an entry to a menu.HFSCDCONExplanation: HFSCDCON.NLM generated this error when attempting to add items to a menu for display at the console. The most likely reason for this error is a low memory condition at the server.Action: For information on solving server memory problems, see "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.127: Unable to add an entry to a menu.HFSCDCONExplanation: HFSCDCON.NLM generated this error when attempting to add items to a menu for display at the console. The most likely reason for this error is a low memory condition at the server.Action: For information on solving server memory problems, see "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.129: Unable to add an entry to a menu.HFSCDCONExplanation: HFSCDCON.NLM generated this error when attempting to add items to a menu for display at the console. The most likely reason for this error is a low memory condition at the server.Action: For information on solving server memory problems, see "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.PAGENUM=245 ID="BP239"131: Unable to add an entry to a menu.HFSCDCONExplanation: HFSCDCON.NLM generated this error when attempting to add items to a menu for display at the console. The most likely reason for this error is a low memory condition at the server.Action: For information on solving server memory problems, see "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.133: Unable to add an entry to a menu.HFSCDCONExplanation: HFSCDCON.NLM generated this error when attempting to add items to a menu for display at the console. The most likely reason for this error is a low memory condition at the server.Action: For information on solving server memory problems, see "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.135: Error number scanning disc: Migration disabled on volume or volume not found.HFSCDCONExplanation: You tried to scan a disc onto a NetWare that either has migration disabled or is not mounted.Action: Enable migration on the volume, or mount the appropriate volume.136: Error number scanning disc: Automatic scan of another disc is already in progress.HFSCDCONExplanation: You tried to have HFSCD.NLM scan a disc while another disc scan is in progress. HFSCD.NLM can only scan one disc at a time.Action: Wait until one disc scan is complete before you try to scan another one.255: This version of HFSCDCON.NLM is not compatible with the HFSCD.NLM that is currently loaded.HFSCDCONExplanation: HFSCD.NLM and HFSCDCON.NLM are released as a set and have internal version numbers associated with them to ensure that the two are compatible. This error message indicates that the version of HFSCDCON.NLM you are running is an older or newer than the version of HFSCD.NLM currently loaded.Action: Obtain and run the appropriate version of HFSCDCON.NLM.PAGENUM=246 ID="BP240"IDE.DSK005: IDE controller could not be added due to insufficient memory.IDE.DSKExplanation: This server does not have enough available memory to load this driver.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. Try loading the driver again.010: An unexpected problem prevented allocation of memory for this IDE driver.IDE.DSKExplanation: This server does not have enough available memory to load this driver.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. Try loading the driver again.015: The selected hardware is not available for this IDE driver.IDE.DSKExplanation: The driver searched for the hardware ports specified when the driver was loaded. It was not able to find hardware at the specified port locations.Action: Reload the driver, and specify the correct port for the controller.020: An invalid I/O parameter was selected.IDE.DSKExplanation: Either the port or the interrupt selected was invalid.Action: Reload the driver, and enter the correct port and interrupt.025: Drive drive does not support block commands.IDE.DSKExplanation: This drive does not support read/write multiple commands as defined by the CAM ATA specification.Action: None. This message is for information only. The driver simply will not attempt to use read/write multiple commands on this drive.040: Drive name does not support current parameters. Drive not registered with OS.IDE.DSKExplanation: This drive does not support Current drive geometry in the IDE Identify command. For this computer, drives must support this feature.Action: Use a drive that supports the Enhanced IDE specification with this machine. PAGENUM=247 ID="BP241"045: Drive name does not support current parameters. **WARNING** Novell does not recommend using this drive in this configuration.IDE.DSKExplanation: This drive does not support the Enhanced IDE specification by providing Current drive geometry in the Identify command. Novell does not recommend using this drive in this computer. The driver will use default disk geometry parameters to attempt to access this drive.Action: None. This message is for information only. This is a user command-line override of a NetWare safety feature. The user is using the drive in this configuration at his or her own risk.PAGENUM=248 ID="BP242"IDEATA.HAM001: HAM not compatible with detected bus type.IDEATA.HAMExplanation: The HAM driver did not load because the hardware bus type of the server is incompatible with the bus type the driver was designed to support. The IDEHAM.HAM Host Adapter Module supports IDE/ATA controller cards designed to work on ISA/EISA machines.Action: Use a controller card and compatible HAM driver appropriate for the server's I/O bus.002: Hot Replace not supported.IDEATA.HAMExplanation: The load of the driver failed because a previous version of the HAM driver is already loaded and the newer version that attempted to load does not support dynamic software hot replacement. Hot replacement is a term describing the ability to dynamically replace a HAM driver already loaded in server memory with a newer version of the driver without having to dismount associated volumes.Action: You can leave the existing version of the HAM driver in place and continue to operate. Or, if you really want to load the newer version, unload the existing version and then reload the newer version.003: Not enough memory to create HAM object.IDEATA.HAMExplanation: The load of the driver failed because the server could not give the HAM driver enough memory to create the objects necessary to support the controller and attached devices.Action: Unload any unnecessary NLM programs and reload the HAM driver.004: Could not establish reentrant object.IDEATA.HAMExplanation: The current load instance failed because the .HAM was unable to complete reentrant module registration with the NPA.Action: Unload any unnecessary .CDM and .HAM drivers. Then retry the reentrant load of the .HAM driver.005: Exceeded reentrant load-instance limit.IDEATA.HAMExplanation: You have attempted to reentrantly load the HAM beyond its supportable limit. The IDEHAM.HAM driver supports a total of four reentrant load instances, which corresponds to the number of I/O channels currently supported in the IDE/ATA specification. You have attempted to exceed the number of I/O channels allowable under the IDE/ATA interface.Action: None. This message is for information only.PAGENUM=249 ID="BP243"006: NPA HAM object not found.IDEATA.HAMExplanation: The load instance failed because the NPA NLM programs object database got corrupted.Action: Unload all .CDM and .HAM drivers; then unload NWPA.NLM. Reload the NWPA.NLM; then reload the .CDM and .HAM drivers. If the problem recurs, you may need to bring down the server and bring it back up.007: Support hardware resources were not specified.IDEATA.HAMExplanation: The load instance failed because the necessary hardware resources (port and interrupt values) for configuring the HAM driver were not specified on the command line.Action: Reload the driver and specify the appropriate hardware resources.008: Device not found at the specified port address.IDEATA.HAMExplanation: The load instance failed because the HAM driver did not detect any devices at the specified port address.Action: Determine the correct port address and reload the HAM driver using this value.009: Load failed because of a hardware resource conflict.IDEATA.HAMExplanation: The load failed because some other driver has reserved one or all the hardware resources (port or interrupt) specified for this driver.Action: Resolve the resource conflict between the competing controllers and reload the driver.010: I/O channel registration failed.IDEATA.HAMExplanation: The load instance failed because channel registration with the server failed.Action: Unload any unnecessary .CDM and .HAM drivers, the reload this .HAM driver.PAGENUM=250 ID="BP244"INETCFG4: Could not get tag for resource allocation.INETCFGExplanation:  INETCFG could not be loaded because a resource tag could not be allocated from the NetWare operating system. This usually means the server is low on memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. Reload INETCFG when more server memory is available.6: Could not initialize user interface.INETCFGExplanation: INETCFG could not initialize because the server is low on memory.Action:   See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. Reload INETCFG when more memory is available.PAGENUM=251 ID="BP245"IDEHD.CDM001: WARNING! This driver has not been tested with devicename; however, the driver has bound to the device to provide generic support. Contact the device manufacturer for a full-function driver.IDEHD.CDMExplanation: The device is not one the driver fully supports, nor is it a device that the driver excludes. Therefore, the driver is bound to the device to support the generic (basic) functionality typical of the device class type.Action: The best action is to contact the manufacturer and get a driver that fully supports the device.However, barring the idiosyncrasies of the device, this generic driver may support the device just fine. The choice to use the driver is yours, but until you feel comfortable that this driver supports the device adequately, do not use it to store critical data.002: WARNING! Driver has not been tested with devicename; therefore, driver did not bind to device. To invoke generic support, unload the driver and then reload it with the appropriate command line parameter. See INSTALL Driver Options for a list of these parameters and their descriptions.IDEHD.CDMExplanation: This condition is similar to that of message 001, except that the driver chose not to bind generically to the device. Possibly, all that is needed for generic support is some general configuration information about the device.Action: The best action is to contact the manufacturer and get a driver that fully supports the device.However, barring idiosyncrasies of the device, this generic driver may support the device just fine. The choice to use the driver is yours, but until you feel comfortable that this driver supports the device adequately, do not use it to store critical data.You may invoke generic support and provide the necessary information by unloading this driver and then reloading it with each appropriate command-line parameter. For a list of these parameters and their respective descriptions, read the driver's .DDI file or select the driver under the INSTALL utility's Driver Options menu.003: Warning! The driver did not bind to device_name because it does not support this device. Contact the manufacturer for a full-function driver.IDEHD.CDMExplanation: The driver recognizes this device as a known device that it cannot support, not even generically.Action: Contact the device manufacturer to get the appropriate driver.PAGENUM=252 ID="BP246"INSTALL1: An attempt to access INSTALL messages failed. It is likely that the message or help files (INSTALL.MSG or INSTALL.HLP) are out of date, missing, or corrupted.INSTALLExplanation: INSTALL.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:MARK=BULLETThe INSTALL.MSG file and INSTALL.HLP file are in the boot directory (where SERVER.EXE is found)The corresponding SYS:SYSTEM\NLS\X directory on the server2: An attempt to add an option to a menu failed.INSTALLExplanation: INSTALL was unable to build a menu on the screen. The server may not have enough available memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.3: Fatal error: The installation cannot complete successfully. An attempt to allocate memory failed. You must add (or reconfigure) memory and restart the installation.INSTALLExplanation: There was insufficient memory for INSTALL to run.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.4: The disk partition table could not be read.INSTALLExplanation: INSTALL was unable to read the disk partition information from the hard disk.Action: See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network. 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 may be faulty. If FDISK can see the disk but this error still appears, contact your Novell Authorized Reseller.5: No information about device number could be obtained.INSTALLExplanation: INSTALL was unable to read or write the disk partition table on device number.Action: See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.PAGENUM=253 ID="BP247"6: No disk partitions are defined on this drive.INSTALLExplanation: 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.Action: None. This message is for information only. INSTALL will create a partition table.7: An attempt to write out partition information failed. Error code: code.INSTALLExplanation: While writing the partition information to the disk drive, the operating system reported an error to INSTALL.Action: See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.8: An attempt to add a field to a form failed.INSTALLExplanation: INSTALL was unable to complete an operation to build a screen presentation. This could be caused by insufficient memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.9: An attempt to write out partition table information failed. Error code: code.INSTALLExplanation: While writing the partition information to the disk drive, the operating system reported an error from INSTALL.Action: See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network. For information on the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 10: The block allocation size does not match that of another volume with the same name.INSTALLExplanation: INSTALL found two volume segments with the same name, but the block 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.11: The number of segments in the volume does not match the number in another volume with the same name.INSTALLExplanation: INSTALL found two volumes with the same name, but the number of segments in 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.PAGENUM=254 ID="BP248"12: The volume flags do not match those of another volume with the same name.INSTALLExplanation: INSTALL 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.13: The total volume size does not match that of another volume with the same name.INSTALLExplanation: INSTALL 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.14: The first block of FAT table 0 of the volume does not match that of another volume with the same name.INSTALLExplanation: INSTALL 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.15: The first block of FAT table 1 of the volume does not match that of another volume with the same name.INSTALLExplanation: INSTALL 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.16: The first block of Directory table 0 does not match that of another volume with the same name.INSTALLExplanation: INSTALL 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.PAGENUM=255 ID="BP249"17: The first block of Directory table 1 does not match that of another volume with the same name.INSTALLExplanation: INSTALL 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.18: A volume was found whose name could not be determined.INSTALLExplanation: 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 your Novell Authorized Reseller.19: Volume name name must be at least two characters long.INSTALLExplanation: A volume name was entered which was shorter than two characters.Action: Enter a name at least two characters long.20: A volume was found with an invalid volume block size of number KB.INSTALLExplanation: 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 your Novell Authorized Reseller.21: A volume was found with an invalid number of volume segments (number). Check to be sure all disk drivers are configured properly.INSTALLExplanation: 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 your Novell Authorized Reseller.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.INSTALLExplanation: 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 your Novell Authorized Reseller.PAGENUM=256 ID="BP250"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.INSTALLExplanation: 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 your Novell Authorized Reseller.24: A volume was found with an invalid starting sector offset of number. Check to be sure all disk drivers are configured properly.INSTALLExplanation: 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 your Novell Authorized Reseller.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.INSTALLExplanation: 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 your Novell Authorized Reseller.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.INSTALLExplanation: An invalid volume has been found. This volume has become corrupted.Action: See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network. Also run VREPAIR. If these efforts fail, delete the volume. If the data is required, restore it from backups.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.INSTALLExplanation: An invalid volume has been found. This volume has become corrupted.Action: See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network. Also run VREPAIR. If these efforts fail, delete the volume. If the data is required, restore it from backups.PAGENUM=257 ID="BP251"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.INSTALLExplanation: An invalid volume has been found. This volume has become corrupted.Action: See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network. Also run VREPAIR. If these efforts fail, delete the volume. If the data is required, restore it from backups.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.INSTALLExplanation: An invalid volume has been found. This volume has become corrupted.Action: See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network. Also run VREPAIR. If these efforts fail, delete the volume. If the data is required, restore it from backups.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.INSTALLExplanation: An invalid volume has been found. This volume has become corrupted.Action: See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network. Also run VREPAIR. If these efforts fail, delete the volume. If the data is required, restore it from backups.31: Due to a memory allocation problem, the volume definitions were not updated on the disk.INSTALLExplanation: There is insufficient memory to accomplish the desired update.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. Then try the operation again.32: Volume information could not be written because INSTALL was unable to lock disk "label".INSTALLExplanation: The disk is probably being used by another process. A mounted volume may be using it.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Locked Device Errors" in Supervising the Network.PAGENUM=258 ID="BP252"33: An error occurred (error code: code) while writing to disk "label" sector number.INSTALLExplanation: The disk could not be written to. The driver or disk may not be configured correctly, or a hardware failure may have occurred.Action: See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 34: An attempt to expand the mounted volume tables failed. Error code: code.INSTALLExplanation: INSTALL could not write to the disk or allocate memory to expand the volume FAT and directory tables.Action: See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network and "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 35: The program could not allocate memory for the volume FAT table.INSTALLExplanation: There is insufficient memory to accomplish the desired operation.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.36: The program could not find a free block during FAT block allocation.INSTALLExplanation: An internal system error has occurred.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.37: Function FreeFATTable() was called when no FAT table was allocated.INSTALLExplanation: An internal system error has probably occurred.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.38: The program could not lock disk "label" in order to read volume information.INSTALLExplanation: The disk probably is being used by another process.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Locked Device Errors" in Supervising the Network.39: An error occurred (error code: code) while reading from disk "label", NetWare disk partition sector number. Error information: descriptionINSTALLExplanation: INSTALL could not read from the disk.Action: See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. PAGENUM=259 ID="BP253"40: The program could not read the primary FAT entry from a volume.INSTALLExplanation: INSTALL could not read from the volume.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Volume I/O Errors" in Supervising the Network.41: The program could not read the mirror FAT entry from a volume.INSTALLExplanation: INSTALL could not read from the volume.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Volume I/O Errors" in Supervising the Network.42: An error occurred while writing name FAT block sequence number.INSTALLExplanation: INSTALL could not write to the volume.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Volume I/O Errors" in Supervising the Network.43: The program could not find a free block to which to redirect the FAT block.INSTALLExplanation: The volume may be full or the drive parameters may 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 your Novell Authorized Reseller.44: End of file was encountered unexpectedly in the FAT file, FAT chain, sequence number number.INSTALLExplanation: An internal system error has occurred.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.45: The program could not find a free block during file system directory block allocation.INSTALLExplanation: The volume may be full or the drive parameters may 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 your Novell Authorized Reseller.46: The program could not allocate memory for the file system directory table.INSTALLExplanation: There is insufficient memory to accomplish the desired operation.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.PAGENUM=260 ID="BP254"47: An error occurred while writing name file system directory block sequence number.INSTALLExplanation: INSTALL could not write to the volume. This could indicate an internal system error.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Volume I/O Errors" in Supervising the Network.48: The program could not find a free block to which to redirect the file system directory block.INSTALLExplanation: The volume may be full or the drive parameters may 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 your Novell Authorized Reseller.49: End of file was encountered unexpectedly in the system directory file, FAT chain at sequence number.INSTALLExplanation: An internal system error has occurred.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.50: An attempt to read a primary file system directory entry failed.INSTALLExplanation: An error occurred when the program attempted to read a volume.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Volume I/O Errors" in Supervising the Network.51: An attempt to read a mirror file system directory entry failed.INSTALLExplanation: An error occurred when the program attempted to read a volume.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Volume I/O Errors" in Supervising the Network.52: A file creation error occurred.INSTALLExplanation: INSTALL could not write to a DOS or NetWare disk. If it is a floppy disk, it may be bad, write protected, or not inserted correctly. If it is a hard disk, the proper disk driver may not be loaded, the cabling may not be correct, or the drive parameters may be set incorrectly.Action: Make sure that there is a writable disk. Then check for the possible explanations listed above. See "BOOK="superenu" COLLECTION="nw41"Resolving Volume I/O Errors" in Supervising the Network. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=261 ID="BP255"53: An invalid NetWare file path was found in a configuration file record for file PRODUCTS.DAT.INSTALLExplanation: 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 your Novell Authorized Reseller.54: An attempt to read a file failed.INSTALLExplanation: INSTALL could not read from a DOS or NetWare disk. If it is a floppy disk, it may be bad, may not be inserted correctly, or may not contain the desired file. If it is a hard disk, the proper disk driver may not be loaded, the cabling may not be correct, or the drive parameters may be set incorrectly.Action: Make sure that there is a readable disk. Then check for the possible explanations listed above. See "BOOK="superenu" COLLECTION="nw41"Resolving Volume I/O Errors" in Supervising the Network. If the problem persists, contact your Novell Authorized Reseller.55: An attempt to write out the file failed.INSTALLExplanation: INSTALL could not write to a DOS or NetWare disk. If it is a floppy disk, it may be bad, write protected, or not inserted correctly. If it is a hard disk, the proper disk driver may not be loaded, the cabling may not be correct, or the drive parameters may be set incorrectly.Action: Make sure that there is a writable disk. Then check for the possible explanations listed above. See "BOOK="superenu" COLLECTION="nw41"Resolving Volume I/O Errors" in Supervising the Network. If the problem persists, contact your Novell Authorized Reseller.56: Fixed-point number representation "number" is incorrect. The representation must be a single integer or two integers separated by a decimal point.INSTALLExplanation: The number entered was not a valid number.Action: Enter a number of the format 1.2, 3.0, and so forth.57: Multiple system volumes exist.INSTALLExplanation: INSTALL 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 may have only one SYS: volume, take one of the physical disks offline.PAGENUM=262 ID="BP256"58: An unclaimed disk segment exists on logical partition number, starting sector number, size number sectors, name name, type type, flags flags.INSTALLExplanation: An internal system error has occurred.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.59: A system volume could not be created.INSTALLExplanation: INSTALL could not write to the disk. The proper disk driver may not be loaded, the cabling may be not correct, or the drive parameters may be set incorrectly.Action: See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.60: Volume name was not found in volume list.INSTALLExplanation: INSTALL could not read the disk. The proper disk driver may not be loaded, the cabling may be not correct, or the drive parameters may be set incorrectly.Action: See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.61: An invalid pointer to a segment of existing volume name was encountered.INSTALLExplanation: An internal system error has occurred.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.62: The program could not create a new menu or form.INSTALLExplanation: This error is probably caused by insufficient memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.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.INSTALLExplanation: An internal system error has occurred. Either the server does not have enough memory, or the text does not fit on the screen.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A.66: An attempt to find a non-conflicting volume name for free space failed.INSTALLExplanation: An internal system error has occurred.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=263 ID="BP257"67: The program was unable to read partition information for logical partition number.INSTALLExplanation: The disk is either offline or it is damaged so that the data has been corrupted.Action: See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network. Restore the data from backup after rebuilding the disk partitions.70: Logical partition number, segment number, is not contiguous; there is an overlap of number sectors.INSTALLExplanation: An internal system error has occurred.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.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.INSTALLExplanation: An internal system error has occurred.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.73: Two segments with volume name name were found having different block shift factors (number and number).INSTALLExplanation: 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.74: A resource tag could not be allocated.INSTALLExplanation: This error is probably caused by insufficient memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.75: Error number was returned by the AppendMultiEditText() function.INSTALLExplanation: An internal system error has occurred.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.76: Error number was returned by the MultiEditText function.INSTALLExplanation: An internal system error has occurred.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=264 ID="BP258"77: An invalid parameter was passed to a function at address address.INSTALLExplanation: An internal system error has occurred.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.78: An attempt to access DOS on this computer was unsuccessful.INSTALLExplanation: DOS probably has been removed from this server.Action: Try bringing up the server without removing DOS. If the problem persists, contact your Novell Authorized Reseller.79: File Name contains an incomprehensible version number (number). The version number should be number.INSTALLExplanation: The file is corrupted.Action: Obtain a new copy of the file.80: The program cannot get information about the number of devices available.INSTALLExplanation: The proper disk driver may not be loaded, the cabling may not be correct, or the drive parameters may be set incorrectly.Action: See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.81: The program's attempt to evaluate the driver dependency tree failed because of an internal error.INSTALLExplanation: An internal system error has occurred.Action: Get an updated driver or description file. If the problem persists, contact your Novell Authorized Reseller.82: The program cannot read the root directory entry.INSTALLExplanation: INSTALL could not read from the disk. The proper disk driver may not be loaded, the cabling may not be correct, or the drive parameters may be set incorrectly.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Volume I/O Errors" in Supervising the Network.83: The program cannot make a new NUT client.INSTALLExplanation: This error message is probably the result of insufficient memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.PAGENUM=265 ID="BP259"84: Volume name has multiple segments with different optimization flags (number and number).INSTALLExplanation: 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.85: Volume name has multiple segments with different DS object ID's (number and number).INSTALLExplanation: 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.86: The program cannot get conflict information. Error code: codeINSTALLExplanation: An internal system error has occurred.Action: Try again. If the problem persists, contact your Novell Authorized Reseller. For information on the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 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.INSTALLExplanation: The disk cannot be locked because it is currently being used by another process. A mounted volume may be using it.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Locked Device Errors" in Supervising the Network. PAGENUM=266 ID="BP260"88: Warning: Some invalid volume segment entries exist. This may be due to a drive that is not powered on, a driver that is not configured correctly, a device failure, a media error, or a mirrored group that for various reasons has not synchronized correctly. It could also be due to multiple volumes existing which have the same name. Until now, no changes have been made by this program to the devices themselves that would cause the data on these devices to be lost.  Following this message you will see a Confirm box asking you whether you would like to delete these invalid segments. If you indicate "Yes," the volume information on the devices will be lost. If you want to retain the data on these devices, indicate "No." If a device was not online, make sure it is powered up and the partitions are visible (from INSTALL) before proceeding. If you have mirrored devices, you must unmirror and recreate your mirrored groups before proceeding. Note: You may check partitions and redo mirrored groups from the Disk Options menu in INSTALL.INSTALLAction: Follow the directions on the screen.94: Overlapping disk segments were detected while free segments were being added.INSTALLExplanation: An internal system error has occurred.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.95: Abend: The GetVolumeNumber function was called with an unmounted volume.INSTALLExplanation: An internal system error has occurred. The installation process has terminated prematurely, and INSTALL will be unloaded.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.96: Abend: The program attempted to access FAT entry number, but the highest FAT entry is number.INSTALLExplanation: An internal system error has occurred. The installation process has terminated prematurely, and INSTALL will be unloaded.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.97: Abend: File block sequence number was not found in the FAT chain starting at entry number.INSTALLExplanation: An internal system error has occurred. The installation process has terminated prematurely, and INSTALL will be unloaded.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.98: Abend: Block number number is invalid for volume name.INSTALLExplanation: An internal system error has occurred. The installation process has terminated prematurely, and INSTALL will be unloaded.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.99: Abend: An incorrect sequence number was encountered in the FAT block while a bad block was being redirected.INSTALLExplanation: An internal system error has occurred. The installation process has terminated prematurely, and INSTALL will be unloaded.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=267 ID="BP261"100: Abend: The program attempted to assign a FAT block to an unreachable block.INSTALLExplanation: An internal system error has occurred. The installation process has terminated prematurely, and INSTALL will be unloaded.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.101: Abend: An error occurred in the FAT entry sequence of the last primary FAT block.INSTALLExplanation: An internal system error has occurred. The installation process has terminated prematurely, and INSTALL will be unloaded.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.102: Abend: An error occurred in the in FAT entry sequence of last mirror FAT block.INSTALLExplanation: An internal system error has occurred. The installation process has terminated prematurely, and INSTALL will be unloaded.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.103: Abend: The previous volume segment could not be found.INSTALLExplanation: INSTALL could not read from the disk. The proper disk driver may not be loaded, the cabling may not be correct, or the drive parameters may be set incorrectly.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Volume I/O Errors" in Supervising the Network.104: Abend: An invalid volume segment was found in the disk segment list.INSTALLExplanation: Either part of a volume is missing, or the volume segment is corrupted. The remainder of the volume may be offline.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Volume I/O Errors" in Supervising the Network.105: You have entered a name for the segment (volume number, segment number) that already exists (it is a duplicate). NetWare cannot have duplicate volumes segments. Specify a unique name for this volume segment.INSTALLExplanation: A unique volume name must be entered.Action: Enter a unique volume name.106: The operation aborted because CLIB could not be loaded.INSTALLExplanation: CLIB.NLM could not be loaded. This could be caused by insufficient memory or conflicts with exported functions.PAGENUM=268 ID="BP262"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, see "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. If the problem persists, contact your Novell Authorized Reseller.107: The operation aborted because BTRIEVE could not be loaded.INSTALLExplanation: 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, see "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. If the problem persists, contact your Novell Authorized Reseller.108: The operation aborted because the SYS:SYSTEM\\PRODUCTS.DAT file could not be accessed.INSTALLExplanation: To install products, the above file must be accessible.Action: Make sure volume SYS: is mounted. (Switch to the console screen and type "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 your Novell Authorized Reseller.109: BTRIEVE error number occurred while function number was being executed.INSTALLExplanation: INSTALL received an error from Btrieve.Action: Look up the error in a Btrieve manual and take appropriate action, or contact your Novell Authorized Reseller.110: This product has no configuration options.INSTALLExplanation: There are no options for configuration.Action: Pressing MOREINFO="NONE"<Enter> is not a supported action for this product. Try reinstalling the product and configure it differently. If the problem persists, contact your Novell Authorized Reseller.111: This product cannot be removed.INSTALLExplanation: The nature of the product prevents it from being removed.Action: Do not try to remove this product.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.INSTALLAction: Insert a disk with more free space on it. If the disk is write-protected, remove the write protection.PAGENUM=269 ID="BP263"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.INSTALLAction: Insert a disk with more free space on it. If the disk is write-protected, remove the write protection, or specify a different path.115: The operation aborted because BTRIEVE could not be accessed.INSTALLExplanation: Although Btrieve is loaded, it could not be accessed. The installation process has terminated prematurely, and INSTALL will be unloaded.Action: Make sure that the version of Btrieve is compatible with the NetWare 4 version of INSTALL. Unload and reload Btrieve to see if the problem persists. If the problem persists, contact your Novell Authorized Reseller.116: Warning: The volume will be deleted and all its contents lost if you indicate "Yes" in the Confirm Box that follows this message.INSTALLExplanation: As indicated, this is a warning message.Action: Select "Yes" only to delete the volume.117: A memory corruption problem has occurred. Program operation cannot continue.INSTALLExplanation: An internal system error has occurred. The installation process has terminated prematurely, and INSTALL will be unloaded.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.118: An attempt to free unallocated memory has failed. Program operation cannot continue.INSTALLExplanation: An internal system error has occurred. The installation process has terminated prematurely, and INSTALL will be unloaded.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.121: The Wait message is too large to be displayed.INSTALLExplanation: An internal system error has occurred.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.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.INSTALLAction: See "BOOK="superenu" COLLECTION="nw41"Resolving Locked Device Errors" in Supervising the Network.PAGENUM=270 ID="BP264"126: The option failed.INSTALLExplanation: This is an internal error probably caused by insufficient memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.127: The NetWare Loadable Module name could not be loaded.INSTALLExplanation: 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, see "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.128: The program cannot get a process resource tag.INSTALLExplanation: This error probably is caused by insufficient memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.129: The program cannot get a non-movable memory resource tag.INSTALLExplanation: This error probably is caused by insufficient memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.130: The program cannot get an Alloc resource tag.INSTALLExplanation: This error probably is caused by insufficient memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.131: The program cannot get resource tags.INSTALLExplanation: This error probably is caused by insufficient memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.132: The program cannot get a screen resource tag.INSTALLExplanation: This error probably is caused by insufficient memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.133: The program cannot get a timer resource tag.INSTALLExplanation: This error probably is caused by insufficient memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.PAGENUM=271 ID="BP265"134: The program cannot get an AES resource tag.INSTALLExplanation: This error probably is caused by insufficient memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.135: The program cannot get an IPX Socket resource tag.INSTALLExplanation: This error probably is caused by insufficient memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.136: The program cannot get memory for the install stack.INSTALLExplanation: The server does not have enough memory to complete the installation process.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.137: The program cannot get an event resource tag.INSTALLExplanation: This error probably is caused by insufficient memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.138: The program cannot open a screen.INSTALLExplanation: This error probably is caused by insufficient memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.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.INSTALLExplanation: 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. See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.140: This device is not writable.INSTALLExplanation: 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.PAGENUM=272 ID="BP266"141: No partitions can be viewed on a tape device.INSTALLExplanation: Tape devices do not have a partition table.Action: No action is possible.142: No NetWare partitions are on this CD-ROM device.INSTALLExplanation: 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.143: The source and destination drives are the same floppy device (drive). You must either specify a different source and destination, or copy the files manually.INSTALLAction: Proceed as appropriate for the situation.144: File "name" cannot be unpacked. Error: description.INSTALLExplanation: This error could result from inadequate disk space, from I/O errors, or from file corruption.Action: Do one or both of the following:MARK=BULLETSee "BOOK="superenu" COLLECTION="nw41"Resolving File I/O Errors" in Supervising the Network.Get a new distribution diskette, if available.If the problem persists, contact your Novell Authorized Reseller.145: Four disk partitions are already on this drive.INSTALLExplanation: 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.146: No NetWare disk partitions (post-NetWare 286 partitions) are on this drive. Create one before continuing.INSTALLExplanation: The user is trying to edit a partition table that does not contain a v3.x or v4.x disk partition.Action: Select "Disk Options" from the main INSTALL menu and create a partition.PAGENUM=273 ID="BP267"147: A NetWare disk partition already exists on this drive.INSTALLExplanation: 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.148: No free space is available on this drive for a NetWare disk partition.INSTALLExplanation: 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.149: The NetWare disk partition could not be located. The selected action cannot be completed.INSTALLExplanation: The NetWare disk partition was not created correctly.Action: See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.150: Warning: No valid entries for volume name were found on disk.INSTALLExplanation: Volume name was not found.Action: See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.151: Warning: More than one sync entry exists for volume name.INSTALLExplanation: 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.153: A volume name must be at least two characters long.INSTALLAction: Specify a volume name that is at least two characters.154: No accessible drives have NetWare partitions.INSTALLExplanation: The installation program cannot find a NetWare disk partition.Action: If no disk partitions have been created, make one. See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.PAGENUM=274 ID="BP268"156: Volume name already exists. Try another name.INSTALLExplanation: A volume name was entered that is already defined on the server.Action: Use a unique volume name.157: Volume name cannot be created.INSTALLExplanation: An error probably occurred while allocating memory, or an error occurred while accessing the disk.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network and "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.158: The segment link cannot be located.INSTALLExplanation: An internal system error has occurred.Action: Contact your Novell Authorized Reseller.159: Warning: Volume name has multiple sync entries. It cannot be deleted at this time.INSTALLExplanation: Multiple disk devices are online that contain volumes with name shown in 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.160: Warning: Adjacent disk segments do not line up.INSTALLExplanation: An internal system error has occurred.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.161: Volume name is currently mounted and cannot be deleted.INSTALLExplanation: A volume must be unmounted before it can be deleted.Action: Dismount the volume; then delete the volume.163: A volume must be dismounted before its name can be changed.INSTALLAction: Dismount the volume; then rename it.PAGENUM=275 ID="BP269"164: No available NetWare disk partitions are compatible with the selected drive.INSTALLExplanation: 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 approximately the same size. You may have to install an additional disk to mirror. If this is not the problem, there may be a disk problem. See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network. 165: Warning: The selected NetWare partition contains NetWare volume information. In order to complete the selected operation, the volume information must be deleted.INSTALLAction: Delete all volumes on the NetWare disk partition before deleting the disk partition.166: The NetWare disk partition is currently mirrored with another NetWare partition and must be unmirrored before the selected action can be completed.INSTALLAction: Unmirror the NetWare disk partition.168: The maximum number of NetWare disk partitions (8) has already been assigned to this mirrored partition group.INSTALLAction: Do not try to mirror more than eight disks.169: The mirror group contains an unavailable disk partition which must be removed from the group before any other partitions can be removed.INSTALLExplanation: A disk partition in the mirrored group cannot be accessed because it is not synchronized.Action: Press MOREINFO="NONE"<F3> to resynchronize the unsynchronized disk partition. You may have to delete the unreachable, unsynchronized drive from the mirror set.170: Out-of-sync disk partitions in the group must be removed before you can proceed.INSTALLExplanation: One or more disk partitions are not synchronized. Installation cannot proceed.Action: Remove the unsynchronized disk partitions.171: Volume SYS: must be mounted before you can proceed.INSTALLExplanation: Installation cannot be performed until volume SYS: is mounted.Action: Mount the SYS: volume.PAGENUM=276 ID="BP270"172: The selected disk cannot be tested at this time. Insufficient memory is available to begin another test.INSTALLExplanation: 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, see "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. 173: This disk drive is already being tested.INSTALLExplanation: You tried to test a disk drive that is currently being tested.Action: None. This message is for information only.174: The drive is not currently being tested.INSTALLExplanation: You tried to stop a test that was not being conducted.Action: Make sure that the correct drive is selected.175: Disk surface testing is currently being done. If you leave INSTALL, the testing will be terminated.INSTALLExplanation: You tried to leave INSTALL during a surface test.Action: Wait until surface testing is completed.176: Hot Fix is not currently installed on the selected disk. Hot Fix is necessary for the surface to be properly tested.INSTALLExplanation: There is no NetWare disk partition on the disk.Action: Create a NetWare disk partition on the disk. This will create a Hot Fix redirection area.177: A volume name cannot start with a period.INSTALLExplanation: The user tried to give a volume a name that begins with a period.Action: Use a volume name that does not begin with a period.178: Two volume segments with the same sync value have mismatched data. messageINSTALLExplanation: INSTALL found multiple instances of the same volume. This probably occurred because two physical disks each contain a volume with the same name.Action: Because a given server may have only one volume with the same name, take one of the physical disks offline. You may have to delete one of the volumes and then bring the disks online simultaneously.PAGENUM=277 ID="BP271"179: Volume segment entry number on "disk_description" is invalid: reason Check to be sure all disk drivers are loaded and configured properly.INSTALLExplanation: A segment of a volume is corrupted.Action: See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network. You may have to re-create the volume.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 there are not multiple volumes existing with the same name.INSTALLExplanation: Disk data may be corrupted, or an internal error may have occurred.Action: See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network. If the problem persists, contact your Novell Authorized Reseller.181: A mirror mismatch was detected for FAT block sequence number.INSTALLExplanation: Errors have occurred in the volume structure.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Volume I/O Errors" in Supervising the Network.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.INSTALLExplanation: Errors have occurred in the volume structure.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Volume I/O Errors" in Supervising the Network.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.INSTALLAction: See "BOOK="superenu" COLLECTION="nw41"Resolving Locked Device Errors" in Supervising the Network.184: A mirror mismatch was detected for file system directory block sequence number.INSTALLExplanation: Errors have occurred in the file system.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Volume I/O Errors" in Supervising the Network.185: Volume definition tables on "disk_description" are out of sync.INSTALLExplanation: A disk corruption error has occurred.Action: See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.PAGENUM=278 ID="BP272"186: Drive "name" is unusable.INSTALLExplanation: Four attempts were made to read information on the drive and all failed.Action: See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.187: Warning: The name of volume old_name was changed to both new_name and second_new_name.INSTALLExplanation: An internal system error has occurred.Action: Contact your Novell Authorized Reseller.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.INSTALLExplanation: An internal system error has occurred.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.189: Warning: Volume name has multiple sync definitions (there are multiple volumes which have the same name). All definitions except number have been discarded.INSTALLExplanation: 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 a given server may have only one volume with the same name, take one of the physical disks offline. You may have to delete one of the volumes and then bring the disks online simultaneously.190: Volume name has invalid segment number. This may be due to multiple volumes existing which have the same name, or one or more drivers not being loaded and configured properly.INSTALLExplanation: 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. See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.191: Two or more volume were found which have the same name (volume name has multiple definitions for segment numberPAGENUM=279 ID="BP273"). This could be due to formerly mirrored volumes being synchronized separately, then brought online together. If this is the case, you will need to unload the driver(s) or down the server, and 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.INSTALLExplanation: More than one volume was found with the same name.Action: Because a given server may have only one volume with the same name, take one of the physical disks offline. You may have to delete one of the volumes and then bring the disks online simultaneously.192: Warning: Volume name is missing segment number. Check to be sure all disk drivers are loaded and configured properly.INSTALLExplanation: An incomplete volume has been discovered. A segment is missing.Action: Make sure that all segments of the volume are online. See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.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 there are not multiple volumes with the same name.INSTALLExplanation: Volume segments were discovered that are inconsistent or corrupted.Action: Make sure that all segments of the volume are online. You may have to delete and re-create all volumes. See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.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 there are not multiple volumes with the same name.INSTALLExplanation: An incomplete volume was discovered. One or more segments is missing.Action: Make sure that all segments of the volume are online. See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.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 there are not multiple volumes with the same name.INSTALLExplanation: A volume segment was discovered that is inconsistent or corrupted.Action: Make sure that all segments of the volume are online. You may have to delete and re-create all volumes. See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.PAGENUM=280 ID="BP274"196: The definition for volume name is invalid. Check to be sure all disk drivers are loaded and configured properly, and that there are not multiple volumes with the same name.INSTALLExplanation: A corrupted or incomplete volume was found.Action: Make sure that all segments of the volume are online. You may have to delete and re-create the volume. See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.197: Volume name was not found in the list of existing volumes.INSTALLExplanation: An internal system error has occurred.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.198: The definition for sync (or instance) number of volume name was removed.INSTALLExplanation: Multiple volumes with the same name were found. One of them was discarded from memory. The data is still intact on disk.Action: Because a given server may have only one volume with the same name, take one of the physical disks offline. You may have to delete one of the volumes and then bring the disks online simultaneously.199: Volume name sync (or instance) number was not found in the volume's sync list.INSTALLExplanation: An internal system error has occurred.Action: Contact your Novell Authorized Reseller.200: Name change update for volume old_name to new_name is being completed.INSTALLExplanation: The volume name has been changed.Action: None. This message is for information only.207: The name "name" is reserved and cannot be used for a volume.INSTALLExplanation: 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.PAGENUM=281 ID="BP275"208: The volume definition table on name has invalid entries. Check to be sure all disk drivers are loaded and configured properly.INSTALLExplanation: 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 "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.209: The selected disk is no longer valid.INSTALLExplanation: The installation program can no longer access the disk drive.Action: See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.210: This volume is not currently mounted.INSTALLExplanation: The program tried to access a volume that was not mounted.Action: Mount the volume and try again. You may have to mount the volume by typing "mount volume_name" at the system console.211: Volume name could not be mounted. Refer to the system console screen for an error report.INSTALLExplanation: INSTALL 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.212: The volume is already mounted.INSTALLExplanation: The user tried to mount a volume that is already mounted.Action: None. This message is for information only.213: Hot Fix could not be installed on the drive. Error code: code.INSTALLExplanation: INSTALL made a request to the operating system to create Hot Fix on the drive, but the request failed.Action: See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network. For information on the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. PAGENUM=282 ID="BP276"214: Hot Fix for the boot partition could not be installed on the drive. Error code: code. INSTALLExplanation: While writing out the Hot Fix information on the boot partition, the operating system reported an error to INSTALL. Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server I/O Errors" in Supervising the Network.214: Drive information could not be read.INSTALLExplanation: An error occurred when the program attempted to read information from a disk drive.Explanation: Make sure that the drive can be accessed. See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.215: The drive could not be set up for mirroring.INSTALLExplanation: 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 "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.216: You must unmirror the drive before it can be tested.INSTALLAction: Unmirror the drive.218: Warning: The selected disk partition may contain valuable data; all data on the partition will be lost.INSTALLExplanation: 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.220: The partition table on drive numberPAGENUM=283 ID="BP277" 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.INSTALLExplanation: 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.221: This disk partition is out of date with respect to other mirror groups and must be resynchronized before it can be used.INSTALLExplanation: The disk partition cannot be accessed because it is not synchronized.Action: Resynchronize the disk partition using MOREINFO="NONE"<F3> in the mirror list.225: This segment exists on disk. Its size cannot be modified unless you delete and reassign it.INSTALLExplanation: 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.226: The system volume (SYS:) does not exist. Installation cannot be completed without it.INSTALLExplanation: System volume SYS: must be mounted before INSTALL.NLM can be used.Action: Mount the SYS: volume.228: File "name" is out of date (its version numbers are number and number, the expected values are number and number, respectively). Insert a diskette containing an updated file (if installing from floppy; if not, you must update the file and reinstall).INSTALLExplanation: The specified installation script file is out of date.Action: Get a current version of the script file.230: File copying was cancelled.INSTALLExplanation: File copying being done from a floppy diskette has been cancelled.Action: None. This message is for information only.PAGENUM=284 ID="BP278"231: Free space cannot be deleted. Move the cursor to a valid volume entry and then press <Del>.INSTALLExplanation: 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.232: An error occurred while parsing file "name", line number, at or near word or symbol "word_or_character". Error description: descriptionINSTALLExplanation: 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 your Novell Authorized Reseller.233: File "name" was not found.INSTALLExplanation: The specified file was not found during the copy phase.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.234: The name "volume_name" already exists in the segments list.INSTALLExplanation: The volume name that the segment is being assigned to already exists.Action: Choose a new name.235: File "name" cannot be opened. Error: description.INSTALLExplanation: This error could result from inadequate disk space on a NetWare volume or from a corrupted floppy disk.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving File I/O Errors" in Supervising the Network. If the error occurred while accessing a floppy, make sure all files can be read from a workstation. If the problem persists, contact your Novell Authorized Reseller.236: The maximum number of segments on this disk has been reached. If you want to add a new segment, first delete another segment.INSTALLExplanation: 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.PAGENUM=285 ID="BP279"239: The disk (logical partition number) is locked and cannot be accessed because another process is using it.INSTALLExplanation: Another process or NLM is using the disk partition.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Locked Device Errors" in Supervising the Network.240: Volume name cannot be locked because another process is using it. Volume configuration cannot proceed.INSTALLExplanation: Another process or NLM is using the volume.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Locked Device Errors" in Supervising the Network.242: File "name" cannot be read. Error: description.INSTALLExplanation: This error could result from inadequate disk space or from other I/O errors.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving File I/O Errors" in Supervising the Network. If the error occurred while accessing a floppy disk, make sure all files can be read from a workstation. If not, contact your Novell Authorized Reseller.243: The system volume is too small (number MB, number sectors). It should be at least number MB (number sectors).INSTALLExplanation: 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.244: The path you specified corresponds to a remote server and is not supported.INSTALLExplanation: You entered a remote server path. Remote paths are not supported.Action: Enter a local path.245: An error occurred while parsing file "name" on disk "disk_description", line number, at or near word or symbol "name". Error description: descriptionINSTALLExplanation: 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 your Novell Authorized Reseller.PAGENUM=286 ID="BP280"246: File "name" cannot be erased. Error: description.INSTALLExplanation: This error could result from file I/O errors or from a floppy disk being write-protected.Action: If a floppy disk is being accessed, make sure it is writable. See "BOOK="superenu" COLLECTION="nw41"Resolving File I/O Errors" in Supervising the Network.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.INSTALLExplanation: The specified NLM did not load in the time allotted. The NLM may be working properly and perhaps no error occurred.Action: Press MOREINFO="NONE"<Enter> to view the system console screen to determine whether an error occurred or to enter information. If no error has occurred, proceed normally.248: NLM_name did not load. Control will be switched to the system console screen, where you may see the error.INSTALLExplanation: The specified NLM failed to load.Action: Press MOREINFO="NONE"<Enter> to view the system console screen to determine what error has occurred.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.INSTALLExplanation: The specified NLM did not unload in the time allotted. You may have to enter information to complete the unload process.Action: Press MOREINFO="NONE"<Enter> to view the system console screen to see if an error occurred or to enter information. If no error has occurred, proceed normally.250: NLM_name did not unload. Control will be switched to the system console screen, where you may see the error.INSTALLExplanation: The specified NLM failed to unload.Action: Press MOREINFO="NONE"<Enter> to view the system console screen to determine what error has occurred.252: Directory "directory_name" cannot be created. Error: description.INSTALLExplanation: The specified directory could not be created.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving File I/O Errors" in Supervising the Network.PAGENUM=287 ID="BP281"254: Directory "name" cannot be removed. Error: description.INSTALLExplanation: The directory is in use or is not empty.Action: Make sure that the directory is empty before trying to remove it.256: NetWare path path is invalid. Specify a fixed or floppy drive path.INSTALLExplanation: NetWare paths cannot be used for this operation.Action: Specify a drive path for a floppy or fixed disk.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.INSTALLExplanation: 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.258: This diskette cannot be written to.INSTALLExplanation: The floppy disk is write-protected or defective.Action: Make the disk writable or obtain a new disk.259: A file copy error occurred. Error: description.INSTALLExplanation: This error could result from inadequate disk space or from other I/O errors.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving File I/O Errors" in Supervising the Network.260: A write error occurred on file "name". Error: description.INSTALLExplanation: This error could result from inadequate disk space or from other I/O errors.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving File I/O Errors" in Supervising the Network.261: An attempt to combine files into target file "filename" failed. Error: description.INSTALLExplanation: This error could result from inadequate disk space or from other I/O errors.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving File I/O Errors" in Supervising the Network.262: No installation file (*.IPS or PINSTALL.NLM) could be found at path "path".INSTALLExplanation: The necessary product installation files are not locatable in 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.PAGENUM=288 ID="BP282"263: Installation for the selected item has been aborted.INSTALLExplanation: This alert is for information only.Action: None, unless you wish to begin product installation again.264: Item "name" installation has been aborted.INSTALLExplanation: This alert is for information only.Action: None, unless you wish to begin product installation again.265: Directory path path is invalid.INSTALLExplanation: 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.266: Directory path path either is invalid or does not contain the desired file (name). Press <F3> (or <F4> if applicable) and specify a different path.INSTALLExplanation: The specified path does not exist, or does not contain the file, or contains invalid characters.Action: Enter a valid path.267: Directory path path either is invalid or does not contain the desired file (name).INSTALLExplanation: The specified path does not exist, does not contain the file, or contains invalid characters.Action: Enter a valid path.268: The specified directory path is invalid. Press <F3> (or <F4> if applicable) to enter a new path.INSTALLExplanation: The specified path either does not exist or contains invalid characters.Action: Enter a valid path.269: The system volume (SYS:) either is not mounted or does not exist.INSTALLExplanation: The SYS: volume is either not mounted or not visible to INSTALL.Action: Make sure that the volume is mounted, that all the necessary disk drivers are loaded, and that the disk is powered on. See "BOOK="superenu" COLLECTION="nw41"Resolving Volume I/O Errors" in Supervising the Network.PAGENUM=289 ID="BP283"270: The system volume (name:) is not mounted.INSTALLExplanation: You cannot use INSTALL.NLM until you have mounted the system volume.Action: Mount the volume. Do this at the system console by typing the following:MOREINFO="NONE"MOUNT volume_name 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.INSTALLAction: Follow the suggestions in the message.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.INSTALLExplanation: The size of the partition is not an even multiple of the number of heads, sectors, and cylinders on the drive.Action: See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network. 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.273: Volume name name already exists. Choose a different name.INSTALLExplanation: The volume name displayed in the message already exists.Action: Choose a different volume name.274: Some disk partitions already exist. INSTALL will delete them (including the files, user data, etc.) and create new ones if you confirm "Yes" on 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, you should confirm "No."INSTALLExplanation: Unless you specify otherwise, INSTALL 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."275: No ending signature (`DRIVER DESCRIPTION END') was found in file name. The file was ignored.INSTALLExplanation: 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.PAGENUM=290 ID="BP284"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.INSTALLExplanation: Unloading this driver may affect multiple devices that the driver controls. For instance, a LAN driver may control multiple network boards, or a disk driver may control multiple disks. If you unload the driver, all the devices this driver controls will be unavailable to you.Action: Choose the appropriate action.278: No disk driver files (*.DSK, *.HAM, *.CDM) were found.INSTALLExplanation: INSTALL was unable to access a disk because no disk driver was found.Action: Copy the needed driver to the boot directory.279: No LAN driver files (*.LAN) can be found. Volume SYS may be unmounted, or directory SYS:SYSTEM may not contain any driver files.INSTALLExplanation: INSTALL 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 may have to press MOREINFO="NONE"<Insert> and install from a floppy disk.280: The driver file (name) could not be found.INSTALLExplanation: 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.282: Logical name name already exists.INSTALLExplanation: The name already exists.Action: Specify a different name.283: The command line string for driver name was too long and could not be generated.INSTALLExplanation: INSTALL 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 INSTALL can generate.Action: Load the driver from the system console, providing the parameters by hand.PAGENUM=291 ID="BP285"284: A value must be entered for parameter "name." Enter a value before you load the driver.INSTALLExplanation: The specified parameter requires a value as in the example below:FORMAT="LINESPECIFIC"MOREINFO="NONE"NET=01240000 Action: Specify the proper value for the parameter.285: Value value cannot be interpreted.INSTALLExplanation: The specified value has no meaning to INSTALL.Action: Supply a valid value as indicated in the documentation for the indicated product.286: Value value is already in use. Choose another one.INSTALLExplanation: The value specified is already in use.Action: Choose another value (for example, a different interrupt number).287: Recoverable parameter dependency errors occurred with parameter "value". You may continue anyway.INSTALLExplanation: The value you supplied for a parameter required another parameter that was not supplied.Action: None. This message is for information only. INSTALL was able to recover from the error.288: A recoverable initialization problem occurred with parameter "value". You may continue anyway.INSTALLExplanation: The value supplied for a parameter caused a problem, but INSTALL was able to recover from the error.Action: None. This message is for information only. INSTALL was able to recover from the error.289: Value "value" is not in the list of acceptable values.INSTALLExplanation: An invalid value was entered.Action: Enter an acceptable value. See 
BOOK="instlenu" COLLECTION="nw41"Installation for more information.290: Value "value" is not within the range specified for this parameter.INSTALLExplanation: An invalid value was entered.Action: Enter an acceptable value. See 
BOOK="instlenu" COLLECTION="nw41"Installation for more information.PAGENUM=292 ID="BP286"293: Driver name did not unload correctly. Control will be switched to the system console screen where you may see the error.INSTALLExplanation: INSTALL 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.297: Driver name was successfully unloaded. Press <Enter> to continue.INSTALLExplanation: This alert is for information only.Action: None. This message is for information only.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.INSTALLAction: If you want a frame type different from the default, you will need to specify it later.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.INSTALLExplanation: 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.301: No LAN drivers are loaded. LAN drivers must be loaded and bound in order for INSTALL to communicate with other v4.x servers and install Directory Services as part of an existing Directory tree.INSTALLExplanation: INSTALL could not communicate with any other servers because no LAN drivers have been loaded.Action: If you want INSTALL to see other servers on your network, load and bind an appropriate LAN driver; then retry the operation.302: No volumes were found.INSTALLExplanation: 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.PAGENUM=293 ID="BP287"303: The network number you entered (address) is being used by another existing network. Enter a different (unique) number.INSTALLExplanation: Two networks cannot have the same network address.Action: Enter a different address.304: A physical device or partition in the set you selected is no longer valid.INSTALLExplanation: The device may have been powered off or in some other way made invisible to INSTALL.Action: Correct the problem and retry the operation.305: Driver name was successfully loaded but not bound to any protocol stacks. Press <Enter> to continue.INSTALLAction: To bind the driver to a protocol stack, switch to the system console screen and use the BIND command.306: Driver name could not be loaded because command file name could not be created. Load this driver manually from the system console.INSTALLExplanation: 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.307: Driver name could not be loaded because command file name could not be written. Load this driver manually from the system console.INSTALLExplanation: 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.308: No disk driver files (*.DSK, *.HAM, *.CDM) were found at this path.INSTALLExplanation: 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.PAGENUM=294 ID="BP288"309: No LAN driver files (*.LAN) were found at this path.INSTALLExplanation: 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.310: File name could not be saved to name.INSTALLExplanation: INSTALL 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.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.INSTALLAction: Make sure that the path contains valid characters, points to a valid directory, and contains the proper files.312: Driver name is currently not loaded.INSTALLAction: Either load the driver or select another one, as appropriate.313: No other volumes exist.INSTALLExplanation: 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.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.INSTALLExplanation: You may create a new volume using this segment, but you may not add it to any existing volume.Action: Proceed as appropriate for your situation.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.INSTALLExplanation: The volume will be deleted if you select "Yes."Action: Proceed as appropriate for your situation.PAGENUM=295 ID="BP289"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.INSTALLExplanation: The volume will be deleted if you select "Yes."Action: Proceed as appropriate for your situation.317: Directory 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 Directory tree.INSTALLExplanation: To locate existing Directory trees, INSTALL 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.318: Warning: Some volumes are not mounted and will not be upgraded to the Directory. You may mount and upgrade them later if you wish.INSTALLExplanation: This warning simply indicates that unmounted volumes are not upgraded.Action: Upgrade volumes as appropriate to your situation.319: INSTALL cannot get the root directory entry for volume name.INSTALLExplanation: The root directory (/) was not readable.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Volume I/O Errors" in Supervising the Network.320: The bindery upgrade failed. Some of the Bindery objects will have to be created and/or trustee rights changed manually later using Directory Services workstation utilities.INSTALLExplanation: INSTALL was unable to convert all of the Bindery objects to Directory Services objects.Action: You will have to manually create any missing objects after the installation is complete.321: The Directory ID cannot be stamped on volume name.INSTALLExplanation: An internal system error has occurred.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.322: Driver name on line number of the AUTOEXEC.NCF has no `FRAME=<frame_namePAGENUM=296 ID="BP290">' 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 after INSTALL is finished checking it, and you may then add a frame parameter for this driver if it is an Ethernet driver.INSTALLExplanation: 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 INSTALL program.Action: Proceed as appropriate for your situation.323: This option invoked NLM name, which cannot be loaded remotely. Install this product from the server console.INSTALLExplanation: The product installation script for this product has tried to load an NLM, however, NLMs cannot be loaded remotely. It may be copied from a remote workstation and loaded at the server console.Action: The existing product installation script will not work remotely. You will have to install this product at the server console.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.INSTALLExplanation: A full directory context is required.Action: Enter the directory context again.325: A password has not been entered for administrator object "name". You must enter a valid password to continue.INSTALLExplanation: Other users can accidentally make significant changes to your Directory Services configuration if this user name is not assigned a password.Action: Enter an Administrator password.326: Administrator name could not be authenticated. Verify that the administrator name and context is entered completely and correctly and that you have entered the correct password.INSTALLExplanation: 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.327: Context "name" could not be created. Verify that the context path is entered correctly and that object "name"PAGENUM=297 ID="BP291" has supervisor rights on the parent of the new context in the Directory. 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.INSTALLExplanation: INSTALL 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 Directory Services documentation.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) delete or rename the conflicting object from a workstation.INSTALLAction: Follow the instructions on the screen.331: The password was retyped incorrectly. Re-enter the password.INSTALLAction: Retype the new password correctly to confirm it.332: User object "name" could not be authenticated. Verify that the complete name is entered correctly and that you have the correct password.INSTALLExplanation: An invalid object name or password was entered.Action: Enter the complete name correctly. If the problem persists, contact your Novell Authorized Reseller.333: Warning: An attempt to login to the Directory failed, since the server context is not known. Directory Services may be uninitialized, removed, or corrupted.INSTALLExplanation: INSTALL was unable to determine the server context.Action: Execute the DSREPAIR.NLM; then install or reinstall Directory Services. See "BOOK="superenu" COLLECTION="nw41"Repairing the NetWare Directory Services Database" in Supervising the Network.334: Enter a new name for object name.INSTALLExplanation: You entered an invalid Directory Services object name.Action: Enter a valid object name. See "BOOK="utlrfenu" COLLECTION="nw41"NDS and Bindery Objects and Properties" in Utilities Reference for a list of valid object names.335: An object with name name already exists. Choose a different name.INSTALLExplanation: You attempted to assign an object name that already has been assigned to a Directory Services object.Action: Choose a new object name.PAGENUM=298 ID="BP292"336: Driver name could not be loaded because the command line is too long. Load this driver manually from the system console.INSTALLExplanation: The command line exceeded INSTALL's internal buffer length for command lines.Action: Switch to the system console and load the driver manually, supplying the necessary parameters.337: Warning: Typically, an organization with one or more servers should have only one tree. Different trees do not share Directory Services 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.INSTALLAction: Proceed as appropriate for your situation. For information, see "BOOK="getstenu" COLLECTION="nw41"Planning NetWare Directory Services Implementation" in Introduction to NetWare Directory Services.338: An error occurred while attempting to read Directory Services volume upgrade file name. Error code: code.INSTALLExplanation: An internal system error has occurred.Action: Try again. If the problem persists, contact your Novell Authorized Reseller. For information on the specific error code, see IDREF="FM61529""Error Codes" in Appendix A.339: You must upgrade the bindery before volumes may be installed in the directory.INSTALLAction: Upgrade the bindery before trying to install the volumes in the Directory.340: There are users logged into this server. Remove all user connections and try the Directory installation again.INSTALLExplanation: You cannot perform a Directory installation while users are logged in to the server.Action: Clear the users connections and retry the operation.PAGENUM=299 ID="BP293"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.INSTALLExplanation: 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 INSTALL.342: To see a list of existing objects in the directory (countries, organizations, divisions, etc.) when you press <Enter>, you must first authenticate to the directory. To authenticate, you must (1) enter the administrator name (note that if you type the country and company or organization name, a default administrator name will be created for you), and (2) enter the correct password.INSTALLAction: To see the list, follow the instructions in the message.343: INSTALL cannot lock the root directory entry for volume name. Some other process is modifying it.INSTALLExplanation: Only one process at a time may modify the root directory entry.Action: Wait until the other process finishes. If it takes more than a couple of hours, contact your Novell Authorized Reseller.345: The program was unable to initialize NWSNUT.NLM.INSTALLExplanation: 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: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. If the server has at least 500 KB of free memory, contact your Novell Authorized Reseller.346: A tree with the same name (name) already exists. Choose a different name.INSTALLExplanation: Another Directory tree exists on the network with the same name.Action: Choose a different name for the Directory tree.347: The tree name must have at least 1 character.INSTALLAction: Enter a name for the tree, containing at least 1 character.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; numberPAGENUM=300 ID="BP294" 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).INSTALLAction: Proceed as appropriate for the situation.349: The context name must have at least 3 characters (O=name).INSTALLAction: Enter a name for the context having at least 3 characters.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). Since 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).INSTALLExplanation: If you are replacing files with this copy operation (that is, if the files you are copying already exist on the server), then you may have enough space.Action: If sufficient space is available, continue with the operation; otherwise, follow the instructions in the message.351: Warning: TIMESYNC.NLM is not currently loaded. You should load it (from the system console screen) before continuing. Directory Services may have trouble synchronizing properly if the local time differs from the network time.INSTALLExplanation: Directory Services requires that TYMESYNC.NLM be loaded.Action: Load the TIMESYNC NLM.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.INSTALLExplanation: INSTALL will delete the volume segment from this device if you select "Yes."Action: Proceed as appropriate for your situation.353: The network and node you specified either did not correspond to a valid server, or no Directory trees are visible to that server.INSTALLAction: Make sure that the network and node address are correct. If they are correct, and if all servers are up and able to see each other, contact your Novell Authorized Reseller.PAGENUM=301 ID="BP295"354: An attempt to create a record for product name in the product database failed. Error: code.INSTALLExplanation: The disk space may be full or limited in some fashion so as to prohibit writing to this file. The file also may be flagged Read-Only or otherwise made inaccessible.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving File I/O Errors" in Supervising the Network. For information on the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 355: The network number must be non-zero. Enter a different number.INSTALLExplanation: You entered a zero for the network address.Action: Enter a nonzero number.356: The administrator name has too few characters. It should typically be of the form CN=name. [OU=suborganization...]. O=organization [.C=country].INSTALLExplanation: The syntax for the administrator name is incorrect.Action: Make sure that the name conforms to the specification listed.358: This server already contains Directory Services information. If you want to modify the Directory tree structure, use the Network Administrator (NETADMIN) utilities. Do not try to reinstall unless it is absolutely necessary. However, if you must reinstall, first remove Directory Services 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.INSTALLExplanation: Normally, you should not reinstall the Directory after it has been installed once.Action: Read the information in the message carefully; then proceed accordingly.PAGENUM=302 ID="BP296"359: Directory Services has previously been installed on this server. Do NOT reinstall unless absolutely necessary. The Directory 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 Directory Services reinstallation, confirm "No" in the box that follows this message. If you confirm "Yes" in the box that follows, you must login to the Directory 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.INSTALLExplanation: Normally, you should not reinstall Directory Services after it is been installed once.Action: Read the information in the message carefully; then proceed accordingly.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. V4.x servers may fail to update correctly if time services is configured improperly.INSTALLExplanation: The default time synchronization setup should be modified only if you are thoroughly familiar with how this product feature works.Action: See "BOOK="superenu" COLLECTION="nw41"Maintaining the NetWare Server" in Supervising the Network and review the documentation on Time Synchronization before you attempt to change the time server type from the default.361: Volume name is out of disk space. File "name" cannot be copied.INSTALLExplanation: There is not enough disk space to complete the installation.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Disk Space Problems" in Supervising the Network.365: The Directory ID cannot be removed from volume name.INSTALLExplanation: An internal error occurred which prevented clearing of an ID field on the volume. Perhaps the volume is read-only.Action: Contact your Novell Authorized Reseller.366: A virtual device does not have a mirror set that can be displayed or modified.INSTALLExplanation: 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.367: Warning: Some of the partitions are in an out-of-sync state. You will not be able to view, modify, or mount volumes contained on these partitions until they are resynchronized. An out-of-sync partition may be resynchronized by pressing <F3> on the corresponding mirror list entry.INSTALLAction: See the error message.PAGENUM=303 ID="BP297"368: Unable to get the data file that contains the valid license chain information needed to do the server license installation.INSTALLExplanation: INSTALL was unable to read the license file. If the file is on a floppy disk, it may be bad, or not inserted correctly. If it is a hard disk, the proper disk driver may not be loaded, the cabling may not be correct, or the drive parameters may be set incorrectly. Action: Make sure that the floppy disk is readable and inserted correctly. Then check for the possible explanations listed above. See "BOOK="superenu" COLLECTION="nw41"Resolving Volume I/O Errors" in Supervising the Network. 369: An attempt to read license file name failed.INSTALLExplanation: The license file SERVER.MLS could not be read. This could be due to a floppy disk error, or the insertion of the wrong disk.Action: Insert a valid license diskette (typically labeled "LICENSE").370: An error occurred while trying to read the last license installed on this server. Error: description. The new license will not be installed.INSTALLExplanation: An internal error occurred, or the current license on this server was corrupted.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving File I/O Errors" in Supervising the Network. If the problem persists, contact your Novell Authorized Reseller.371: The upgrade you are trying to install assumes a maximum of number connections; however, your server has a current maximum of number connections. You must install an upgrade that starts at the current maximum number of connections. The new license will not be installed.INSTALLExplanation: You are trying to install an upgrade that is incompatible with the current server license.Action: Contact your Novell Authorized Reseller. Obtain an upgrade that is compatible with your current server configuration. To view the current server license information, type "VERSION" at the system console.372: An error occurred while trying to read the original license on this server. Error: description. The new license will not be installed.INSTALLExplanation: An internal error occurred, or the current license on this server was corrupted.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving File I/O Errors" in Supervising the Network. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=304 ID="BP298"373: The serial number of the upgrade license you are installing doesn't match the serial number in the original license on this server. The new license will not be installed.INSTALLExplanation: You are trying to install an upgrade that is incompatible with the current server license.Action: Contact your Novell Authorized Reseller. Obtain an upgrade that is compatible with your current server configuration. To view the current server license information, type "VERSION" at the system console.374: An error occurred while creating the license file (name_number) on the server.INSTALLExplanation: An internal error occurred while attempting to copy/create the license file on this server.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving File I/O Errors" in Supervising the Network. If the problem persists, contact your Novell Authorized Reseller.375: An error occurred while creating the license file (name_number) on the server.INSTALLExplanation: An internal error occurred while attempting to copy/create the license file on this server.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving File I/O Errors" in Supervising the Network. If the problem persists, contact your Novell Authorized Reseller.377: The serial number of the reseller license you are installing doesn't match the serial number in the original license on this server. The new license will not be installed.INSTALLExplanation: You are trying to install a license that contains inconsistent information.Action: Contact your Novell Authorized Reseller. Obtain a license that is consistent.378: The upgrade id number of the reseller license you are installing doesn't match the upgrade id number in the license you are installing. The new license will not be installed. You must get a new license from your reseller.INSTALLExplanation: You are trying to install a license that contains inconsistent information.Action: Contact your Novell Authorized Reseller. Obtain a license that is consistent.379: The license file (name_number) has already been installed on this server. It will not be overwritten.INSTALLExplanation: You are trying to install a license the second time. Installation should continue normally.Action: None. This message is for information only.PAGENUM=305 ID="BP299"380: The license you just installed is NOT VALID and has been removed from the server. See the system error log (SYS:SYSTEM\SYS$LOG.ERR) on this server for more information.INSTALLExplanation: You are trying to install a license that is corrupted or illegal.Action: Contact your Novell Authorized Reseller. Obtain a valid license.381: The license file name has already been installed on this server. It will not be overwritten.INSTALLExplanation: You are trying to install a license the second time. Installation should continue normally.Action: None. This message is for information only.382: You are attempting to upgrade a server that has no original license installed. The license file name found was probably an upgrade license when an original license was expected. It is also possible that the license file you are installing is outdated or corrupted. You should get a new license file.INSTALLExplanation: You are trying to install an upgrade license on a computer that does not have an original license, or the license you are trying to install is corrupted.Action: Contact your Novell Authorized Reseller. Obtain a valid original license.383: A MAIN server license (which is the same type of server license as the one you are trying to install) already exists on the server. You may, however, overwrite the license at this time. If you choose not to overwrite the current MAIN server license the new MAIN server license will not be installed and the currently installed MAIN server license will remain in effect.INSTALLAction: See the error message.384: Unable to replace the currently installed MAIN server licenses due to IO error description.INSTALLExplanation: An internal error occurred while attempting to copy/create the license file on this server.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving File I/O Errors" in Supervising the Network. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=306 ID="BP300"385: Warning: Time is not synchronized to the network. Installation may continue, although Directory Services may have trouble synchronizing objects properly.  Some reasons for time being out of sync may include:  - The Time Server Type field may be set incorrectly.  - The hardware clock on this server was not set properly before starting the installation.  - Network problems or SAP restrictions may prevent network time servers from being seen by this server.  - Network time servers may down.  - TIMESYNC.NLM may not be loaded.  Read the time services documentation to find out how to correctly configure network time.INSTALLAction: See the error message.386: Warning: Do NOT remove the Directory unless absolutely necessary. The Directory is a database of information distributed across multiple servers.  If you confirm "Yes" in the following box, you will be prompted to login (press <Esc> in the login screen if this is impossible). Then this server's server object and volume objects (not the volume data) will be deleted.  Afterwards, you may need to reconfigure other services or objects that reference the server and volume objects. For example, you may need to reconfigure printing, directory map objects, home directory properties, etc.INSTALLAction: Follow the suggestions in the message.388: The system volume (SYS) has only number bytes of free space. You must have a minimum of number bytes preferably more) to install Directory Services. Increase the free space either by deleting and purging files or by adding another segment to the volume.INSTALLAction: Follow the suggestions in the message.389: An NCP Server object with name "name" already exists at context "context".INSTALLExplanation: 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.PAGENUM=307 ID="BP301"391: An attempt to mount CD-ROM volume name as a NetWare volume failed. Control will be switched to the system console screen, where you may view the error.INSTALLExplanation: The CD-ROM could not be mounted as a NetWare volume.Action: Press <Enter> to view the system console screen to determine what error has occurred.392: The program cannot allocate a semaphore.INSTALLExplanation: This error is probably caused by insufficient memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.393: The login attempt to remote server name by user username failed.  Remote server access requires a valid user login name and a valid password. A LAN driver must be loaded and bound to a protocol stack on this server. Also, the network cabling and the remote server must be functional. Login attempts will fail if your password is expired, if your connection limit on the remote server is reached, or if login is disabled on the remote server.INSTALLAction: Check the conditions listed in the message and verify all are correct.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.INSTALLExplanation: 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.395: An attempt to remove the last valid license which was a Main server license failed.  Serial Number: number for number connections. Error: codeINSTALLExplanation: The main server license file could not be deleted.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving File I/O Errors" in Supervising the Network.396: An attempt to remove the last valid Connection Upgrade server license failed. Upgrade ID: number (upgrades a number connection license to number connections). Error: codeINSTALLExplanation: The connection upgrade license file could not be deleted.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving File I/O Errors" in Supervising the Network.PAGENUM=308 ID="BP302"397: An attempt to remove the last valid Version Upgrade server license failed.  Upgrade ID: number  (upgrades a connection license chain to work with server version version.) Error: codeINSTALLExplanation: The version upgrade license file could not be deleted.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving File I/O Errors" in Supervising the Network.398: An attempt to remove the last valid license's companion Reseller license failed. Error: codeINSTALLExplanation: The reseller license file could not be deleted.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving File I/O Errors" in Supervising the Network.399: An attempt to access the installed license to be removed failed. Error: code Call support for further assistance on removing licenses.INSTALLExplanation: The license file could not be deleted.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving File I/O Errors" in Supervising the Network.400: An attempt to find an installed license failed. Use the "VERSION" console command to double check whether any installed licenses still exist. If there are any installed licenses left, call support for assistance on how to remove them.INSTALLExplanation: The license file could not be deleted.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving File I/O Errors" in Supervising the Network.401: Error executing file name: the file cannot be loaded remotely.INSTALLExplanation: 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 "BOOK="superenu" COLLECTION="nw41"Resolving File I/O Errors" in Supervising the Network.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.INSTALLPAGENUM=309 ID="BP303"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.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.INSTALLExplanation: 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 "BOOK="superenu" COLLECTION="nw41"Resolving Volume I/O Errors" in Supervising the Network. 405: No disk drivers were found by this program; it could not complete auto mirroring.INSTALLExplanation: The disk driver has been unloaded, or a major internal error has occurred.Action: Backup and reload disk drivers. If the problem persists, contact your Novell Authorized Reseller.406: This program could not find the other IO engine; it could not complete auto mirroring.INSTALLExplanation: 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 your Novell Authorized Reseller.407: An attempt by this program to allocate memory failed; auto mirroring could not be completed. INSTALLExplanation: This program could not allocate required memory to complete auto mirroring.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.408: This program was unable to get disk driver information; it could not complete auto mirroring. INSTALLExplanation: 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 your Novell Authorized Reseller.PAGENUM=310 ID="BP304"409: This program was unable to get partition information; it could not complete auto mirroring.INSTALLExplanation: 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 your Novell Authorized Reseller.410: This program was unable to get redirection information; it could not complete auto mirroring.INSTALLExplanation: 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 your Novell Authorized Reseller.411: This program was unable to create mirror information; it could not complete auto mirroring.INSTALLExplanation: 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 your Novell Authorized Reseller.412: This program was unable to get mirror information; it could not complete auto mirroring.INSTALLExplanation: 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 your Novell Authorized Reseller.413: This program could not find any Netware partitions on the original computer; it did not complete auto mirroring.INSTALLExplanation: 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 your Novell Authorized Reseller.414: This program could not find any Netware partitions on the new computer; it did not complete auto mirroring.INSTALLExplanation: 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 your Novell Authorized Reseller.PAGENUM=311 ID="BP305"415: Both computers do not have the same number of Netware partitions. This program did not complete auto mirroring.INSTALLExplanation: 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.416: The new server computer's Netware partition is orphaned, cloned or non-operational. This program did not complete auto mirroring.INSTALLExplanation: 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.417: The new server computer's Netware partition is already mirrored. This program did not complete auto mirroring.INSTALLExplanation: The program thinks that the new server's NetWare partition is already mirrored.Action: The mirror group should be deleted, re-created and mirrored.418: The new server's Netware partition contains a volume. This program did not complete auto mirroring.INSTALLExplanation: 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.419: The original server's Netware partition is orphaned, cloned or non-operational. This program did not complete auto mirroring.INSTALLExplanation: 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.420: The original server's Netware partition is already mirrored. This program did not complete auto mirroring.INSTALLExplanation: The program thinks that the original server's NetWare partition is already mirrored.Action: The mirror group should be deleted, re-created and mirrored.PAGENUM=312 ID="BP306"421: This program could not add a partition to a mirror group; it could not complete auto mirroring.INSTALLExplanation: An internal processing error exists.Action: Make sure that the correct disk driver is loaded. Retry the operation. If the problem persists, contact your Novell Authorized Reseller.422: This program could not set partition hotfix; it could not complete auto mirroring.INSTALLExplanation: There is an internal processing error.Action: Make sure that the correct disk driver is loaded. Retry the operation. If the problem persists, contact your Novell Authorized Reseller.423: The original server computer's netware partition is larger than the new computer's partition. This program did not complete auto mirroring.INSTALLExplanation: 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.425: Warning: You do not have a disk driver loaded. You will need to load the proper disk driver to complete the installation.INSTALLExplanation: 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.426: Warning: You do not have a LAN driver loaded. You will need to load the proper LAN driver to complete the installation.INSTALLExplanation: 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.427: Warning: You do not have disk drivers loaded on both server computers. You will need to load the proper disk drivers to complete the installation.INSTALLExplanation: 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.PAGENUM=313 ID="BP307"428: Warning: You do not have LAN drivers loaded on both server computers. You will need to load the proper LAN drivers to complete the installation.INSTALLExplanation: 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.429: You cannot edit/modify the parameters of a currently loaded driver. If you must modify the parameters, unload the driver and reload it.INSTALLAction: If the parameters need to be changed, unload the driver and reload it, changing the parameters as needed.431: Warning: If you continue and skip the remote server login, your original client network connection will be used to complete this installation. The server may lock up if you have LAN driver loaded on the server that access the same network boards as those being used for your client network communication.INSTALLExplanation: If both the client and server are accessing the same network board, the communication may have internal failures resulting in the computer locking up.Action: Do not skip the remote server login unless you are sure that the LAN driver on the server does not access the same network board as those being used by the client.432: Warning: For NetWare for OS/2, you need at least one LAN driver and also a shared LAN driver (TOKENSHR, etc). You will need the LAN driver to complete the installation, and the shared driver to see the network from OS/2.INSTALLExplanation: 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 may 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.PAGENUM=314 ID="BP308"433: Warning: You do not have a shared LAN driver loaded. You will need to choose the proper shared driver for OS/2 to see the network.INSTALLExplanation: 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).434: Some NetWare disk partitions already exist. INSTALL 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, you should confirm "No."INSTALLExplanation: 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."435: Warning: You had TCP/IP configured on the original server. You will need to load INETCFG.NLM after the install is completed and re-install TCP/IP support.INSTALLExplanation: The TCP/IP installation and configuration has been changed in this version of NetWare.Action: Follow the instructions in the message.436: Warning: You had APPLETALK configured on the original server. You will need to load INETCFG.NLM after the install is completed and re-install APPLETALK support.INSTALLExplanation: The APPLETALK installation and configuration has been changed in this version of NetWare.Action: Follow the instructions in the message.PAGENUM=315 ID="BP309"438: Some NetWare disk partitions already exist on the new server computer. INSTALL 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, you should confirm "No".INSTALLExplanation: 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."439: The server license chain has already been upgraded to the version contained in the VERSION UPGRADE license you are currently installing. Therefore, the VERSION UPGRADE server license will not be installed on this server.INSTALLExplanation: The VERSION UPGRADE server license that you are using has already been used on this computer.Action: None. This message is for information only.440: The attempt to attach to remote server servername at IPX address IPX_address failed.   AttachByAddress error code = code (code hex)  errno = code (code hex)  NetWareErrno = code (code hex)INSTALLExplanation: The attempt by this computer to attach to SERVERNAME failed.Action: Retry the action. Make sure the remote server is up and that there is a working path to it. Check the cabling and routers.441: The attempt to find the IPX address for remote server name failed.   Remote server name could not be found in this server's SAP table. Some possible causes may be: SAP filtering, LAN/WAN driver frame type incompatibility, or router/network problems.   You may override SAP filtering by entering the IPX internal network number of remote server name in the following screen.INSTALLAction: Follow the suggestions in the message.442: A user name is required to log in to the remote server.INSTALLExplanation: Both a user name and a password are required to log in to a server.Action: Enter the appropriate user name.443: 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; numberPAGENUM=316 ID="BP310" bytes). You must restart the installation and choose "Custom Installation". During the installation process, you must resize the system volume so it is large enough.INSTALLAction: Follow the suggestions in the message.444: 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). Since some files may be overwritten and replaced, you may have sufficient space, but that cannot be determined at this point.  You may need to restart the installation and choose "Custom Installation" to complete the installation process.INSTALLAction: Follow the suggestions in the message.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).INSTALLAction: Mount the system volume and create the NCF files to make sure the driver load and bind commands are added.447: The attempt to find a route to remote server name at IPX address IPX_address failed.   Network name could not be found in this server's RIP table. The probable cause is RIP filtering, router/network problems, or the address does not exist.   If RIP filtering is in effect, this server can not access the remote network installation area. Either establish a new network installation area on a server that is not RIP filtered from this network segment or reconfigure RIP filtering so it is not in effect on this network segment.INSTALLAction: Follow the suggestions in the message.448: You are trying to install an upgrade license when a main license is needed. This new license will not be installed. Check the label on the license diskette.INSTALLExplanation: There are main licenses and upgrade licenses. A main license is used when installing NetWare for the first time. An upgrade license is used when upgrading NetWare.Action: Make sure you have the right license diskette, and try again. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=317 ID="BP311"449: An attempt to remove the last valid Mirrored-Server license failed.  Upgrade ID: number (upgrades a license chain to work with mirrored-server system). Error: codeINSTALLExplanation: An internal error occurred, or the current license on this server was corrupted.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving File I/O Errors" in Supervising the Network.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.INSTALLExplanation: 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.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.INSTALLExplanation: 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 may not work with currently installed software.452: A problem has been detected with the network connection to remote server name.   The connection with the remote server has become inoperative. Consult with your network administrator for assistance. You may do one of the following:   Press <Enter> to Retry (try to reestablish the connection)   Press <Esc> to Abort (continue without correcting the problem)INSTALLExplanation: The connection to the remote server has been lost. No more communication with that computer is possible until the connection has been reestablished.Action: Press <Enter> to retry the connection or <Esc> to continue without correcting the problem.PAGENUM=318 ID="BP312"453: The Directory Services login attempt to the network by user "username" was unsuccessful.   Network access requires a valid user name and password. (Your user name should include the full Directory Services Distinguished Name such as "Admin.ACME"). A LAN driver must be loaded and bound to the network on this server. Also, the network cabling and the network must be functional.INSTALLAction: Follow the suggestions in the message.454: An error occurred while trying to attach to remote server name.  The remote server is not responding to the Create Service Connection NCP request. The probable cause is RIP filtering, router/network problems, there are no available connections on the remote server, or this server's internal IPX network number conflicts with an existing server's internal IPX network number.  If RIP filtering is in effect, you should begin the installation again using an IPX internal network number which is not RIP filtered (is visible) from the remote installation server. Please see your network administrator for assistance.  If you are experiencing router/network problems, you may retry the attempt to attach to server name by answering "Yes" to the following question.INSTALLAction: Follow the suggestions in the message. If the problem is that there are no available connections on the remote server, some of the connections will have to be broken. See your network administrator for assistance.455: The login attempt to remote 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.INSTALLExplanation: 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 designed server, log out of these other connections and try again. If you cannot find other logins, contact the system administrator of the remote server and increase the number of concurrent connections for this user.PAGENUM=319 ID="BP313"456: A complete Directory Services user distinguished name is required for a Directory Services login. Expanding names with trailing periods is not allowed here because there is no previous name context established before the Directory Services login.INSTALLExplanation: 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 Directory services user name. For example,FORMAT="LINESPECIFIC"MOREINFO="NONE" CN=USER_NAME.OU=ORGANIZATION.O=COMPANY 457: An attempt to get partition replica information on this server failed.INSTALLExplanation: This is an internal processing error.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.458: Warning: Partition "name" exists only on this server. If you continue and remove Directory Services, all objects in this partition will be deleted. The partition specified is not replicated on any other server. Removing this partition information will delete this partition and all objects it contains from the directory. INSTALLAction: This message is for information only. 459: Warning: Some partitions have master replicas that reside on this server. Before removing Directory Services on this server, the master replicas must be moved to a different server.  You may have INSTALL do this for you (see the box that follows), or may designate a server for each master yourself.INSTALLExplanation: Master replicas should not be deleted. Instead they should be moved to a server that contains NetWare Directory Services.Action: Follow the suggestions in the message.460: Warning: Replica and object synchronization operations are in progress. You should wait until they are complete before attempting to remove Directory Services from this server.INSTALLExplanation: Attempting to remove NetWare Directory Services before the objects are synchronized could result in a corrupted data base.Action: Wait for synchronization to complete before removing NetWare Directory Services. For more information on replicas and NetWare Directory Services, PAGENUM=320 ID="BP314"see BOOK="getstenu" COLLECTION="nw41"Introduction to NetWare Directory Services or "BOOK="cncptenu" COLLECTION="nw41"NetWare Directory Services" in Concepts and "BOOK="cncptenu" COLLECTION="nw41"NetWare Directory replica" in Concepts.461: Warning: This machine cannot currently contact other servers that must be notified before removing Directory Services from this server. You should make sure all servers in this Directory tree are up and visible from the network.INSTALLExplanation: When removing Directory Services, 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 NetWare Directory Services. For more information on replicas and NetWare Directory Services, see BOOK="getstenu" COLLECTION="nw41"Introduction to NetWare Directory Services or "BOOK="cncptenu" COLLECTION="nw41"NetWare Directory Services" in Concepts and "BOOK="cncptenu" COLLECTION="nw41"NetWare Directory replica" in Concepts.462: An attempt to remove Directory Services failed, probably due to a failure to allocate memory.INSTALLAction: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.463: An attempt to remove Directory Services failed. Error code: codeINSTALLExplanation: This in an internal processing error.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.464: An attempt to change the master replica of partition "name" failed. Error code: code.INSTALLExplanation: This in an internal processing error.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.465: Warning: The root (main) partition for Directory tree name exists only on this server.  If you continue, all objects in this Directory 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.INSTALLExplanation: The root partition for a Directory Services 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."PAGENUM=321 ID="BP315"466: The product version in the Upgrade license is earlier than the product version in the last installed license and therefore cannot be installed in the current license chain. You should get a license with the appropriate product version for your server.INSTALLExplanation: The license file being installed is older than the license file currently installed. Installing old over new is not permitted.Action: Make sure that the license diskette is correct. If the license diskette is correct, contact your Novell Authorized Reseller.467: Administrator "name" could not be authenticated due to an internal Directory Services error (code code).  The NetWare Directory Services installation has completed successfully, but no volume objects were created for mounted volumes. You may load INSTALL.NLM after the entire installation completes and create the volume objects. If this is a NetWare 3.x upgrade, you will also need to upgrade bindery information later.INSTALLExplanation: Due to an internal error, the administrator could not be authenticated; therefore no Directory Services objects could be created.Action: Follow the suggestions in the message. If the problem persists, contact your Novell Authorized Reseller.468: An organization with the same name (name) already exists. Choose a different name.INSTALLAction: Follow the suggestions in the message.469: The organization name must have at least 1 character.INSTALLExplanation: This message is for information only.470: A password has not been entered for the network administrator user "Admin". You must enter a valid password to continue.INSTALLExplanation: This message is for information only.Action: Enter a valid password.471: User Admin for organization name could not be authenticated. Verify that you have the correct password.INSTALLExplanation: The correct password for the Admin user in the given organization is required for authentication.Action: Enter the correct password for the Admin user.PAGENUM=322 ID="BP316"477: Warning: An attempt to open configuration file STARTUP.NCF failed. Error code: code   You may still configure drivers, but you will have to add the load commands to the configuration file manually later if you want the driver load operations to remain after the server reboots.INSTALLExplanation: Due to an internal error, the load commands will not be automatically inserted into the STARTUP.NCF file. Action: See "BOOK="superenu" COLLECTION="nw41"Resolving File I/O Errors" in Supervising the Network. You may also do as the message states and manually edit the STARTUP.NCF file by loading INSTALL and selecting "Maintenance/Selective Install."478: Warning: An attempt to open configuration files IOSTART.NCF and MSSTART.NCF failed. Error code: code.   You may still configure drivers, but you will have to add the load commands to the configuration files manually later if you want the driver load operations to remain after the server reboots. Due to an internal error the load commands will not be automatically inserted into the IOSTART.NCF and MSSTART.NCF files.INSTALLAction: See "BOOK="superenu" COLLECTION="nw41"Resolving File I/O Errors" in Supervising the Network. You may also do as the message states and manually edit the IOSTART.NCF and MSSTART.NCF files by loading INSTALL and selecting "Maintenance/Selective Install."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 you will have to add the load commands to the configuration file manually later if you want the driver load operations to remain after the server reboots.INSTALLExplanation: Due to an internal error, the load commands will not be automatically inserted into the AUTOEXEC.NCF file.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving File I/O Errors" in Supervising the Network. You may also do as the message states and manually edit the AUTOEXEC.NCF file by loading INSTALL and selecting "Maintenance/Selective Install."480: Warning: An attempt to open configuration files IOAUTO.NCF and MSAUTO.NCF failed. Error code: codePAGENUM=323 ID="BP317"   You may still configure drivers, but you will have to add the load commands to the configuration files manually later if you want the driver load operations to remain after the server reboots.INSTALLAction: See "BOOK="superenu" COLLECTION="nw41"Resolving File I/O Errors" in Supervising the Network. You may also do as the message states and manually edit the IOAUTO.NCF and MSAUTO.NCF files by loading INSTALL and selecting "Maintenance/Selective Install."481: The NetWare/IP product environment could not be set up. The reason could be that CLIB or BTRIEVE NLM did not load. Refer to the NetWare system console for the actual reason.INSTALLAction: 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 "BOOK="superenu" COLLECTION="nw41"Resolving File I/O Errors" in Supervising the Network.482: This server is a single reference time source. If there is another NetWare 4 server in this Directory tree, before you continue to remove NDS you should:  1) Press Alt-Esc and type "Set Timesync Type = Secondary" at the console prompt. 2) Go to another NetWare 4 server in this Directory tree, which has the time set correctly, and type "Set Timesync Type = Single" at the console prompt.   After NDS 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. This is to ensure that if the server is downed and brought back up the time server type will be correct.INSTALLExplanation: 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 Directory Services is being removed from is that single reference server, that role should be assigned to a different server BEFORE removing Directory Services.Action: Follow the steps in the message.483: The ISSLIB.NLM just loaded will not work with the CLIB.NLM currently loaded. For the ISSLIB.NLM to work, a version of the CLIB.NLM either having revision number 4.01e and above or v4.10 is required. Unload the currently loaded CLIB.NLM and reload the correct version of CLIB.NLM.INSTALLExplanation: ISSLIB.NLM only works with the more current versions of CLIB.NLM.Action: Follow the suggestions in the message.PAGENUM=324 ID="BP318"484: Warning: INSTALL has detected that no disk mirroring has been configured. This is allowable, but not recommended, since disk mirroring is an important part of full mirrored-server fault tolerance.INSTALLExplanation: Disk mirroring is an important part of full mirrored-server fault tolerance.Action: Before continuing with INSTALL, establish disk mirroring.485: Warning: Some problems still exist with disk mirroring. Mirror status description: description. These problems must be resolved before completing the installation. INSTALLExplanation: 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 your Novell Authorized Reseller.486: The INSTALL.NLM tried to load the NLM_name to enable Server to Server communication but failed to do so for some unknown reason. It is not possible now to copy files from an NetWare server. INSTALLExplanation: Server to Server communication, necessary for file copy, is not possible without the NLM indicated in the message being loaded.Action: Try to determine from the console screen why the indicated NLM did not load. If possible, fix the problem. Otherwise, contact your Novell Authorized Reseller.487: The password for user name on server name has expired.  You have successfully logged in to server name this time by using one grace login. You should change your password on server name before all of the grace logins have been used. INSTALLAction: Follow the suggestions in the message.488: For the installation to continue, the current version of ICMD.NLM is required to be loaded. INSTALL.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.INSTALLExplanation: ICMD.NLM must be loaded to continue the installation.Action: Contact your Novell Authorized Reseller.489: INSTALL.NLM could not modify the file attributes of the old pre-4.1 auditing file name on volume namePAGENUM=325 ID="BP319". To make this file visible to AUDITCON.EXE as an "old offline audit file", you must remove the SYstem and Hidden bits from the file with the FLAG utility.INSTALLAction: Follow the suggestions in the message.490: INSTALL.NLM could not move the old pre-4.1 DS container audit file name to the root of the SYS volume. Old audit information will not be available for the corresponding container.INSTALLAction: If old audit information is necessary, contact your Novell Authorized Reseller.491: NetWare Boot partition should be created at least on one of the devices so that INSTALL.NLM can copy NetWare server boot files to that NetWare Boot partition. This will let NetWare to boot from that device. INSTALLExplanation: A NetWare Boot partition is required to boot NetWare.Action: Create at least one NetWare Boot partition on one of the devices so that INSTALL.NLM can copy NetWare server boot files to that NetWare Boot partition. This will allow NetWare to boot from that device. 492: Warning: You will not be able to complete the installation unless the system files have been copied previously to the local disks. If this is not the case, indicate "No" (don't skip file copy) in the screen that follows.INSTALLAction: Follow the suggestions in the message.493: A volume name cannot start or end with an underscore. INSTALLAction: Choose a different volume name that does not start or end with an underscore character.494: A volume name cannot have multiple adjacent underscores.INSTALLAction: Choose a different volume name that does not have multiple adjacent underscores.495: INSTALL.NLM failed to detect any NetWare BOOT partitions; this could be because the partition table was incorrect; run INSTALL.NLM from the Server console, delete all the volumes from the Volume options, delete all partitions from the Disk partitions option and then restart sequential mode install.INSTALLAction: Follow the suggestions in the message.PAGENUM=326 ID="BP320"496: INSTALL.NLM could not detect any NetWare BOOT partitions; There must be at least one NetWare BOOT partition which can be identified as a destination drive.INSTALLAction: The INSTALL NLM searched for a NetWare Boot partition and failed to find any.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 your Novell Authorized Reseller.497: The destination drive specified_drive_name is not a valid NetWare BOOT partition. The only valid destination drive is valid_drive_name. INSTALLExplanation: The specified destination drive is not a valid NetWare Boot partition.Action: Choose the valid destination drive listed in the message.498: The destination drive specified_drive_name is not a valid NetWare BOOT partition. Valid destination drives are valid_drive_names. INSTALLExplanation: The specified destination drive is not a valid NetWare Boot partition.Action: Choose a valid destination drive from drive names listed in the message.499: The program was unable to initialize NWSNUT.NLM. Update NWSNUT.NLM to a newer version. INSTALLAction: Follow the suggestions in the message.500: The Directory Services login attempt to the network by user "name" was unsuccessful.  Network access requires a valid user name and password. (Your user name should include the full Directory Services Distinguished Name such as "Admin.ACME").INSTALLAction: Follow the suggestions in the message.501: The Install 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. INSTALLAction: If a code page other than 437 is needed, contact your Novell Authorized Reseller.502: The Install 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. INSTALLAction: If a language other than English is needed, contact your Novell Authorized Reseller.PAGENUM=327 ID="BP321"503: The Install NLM failed to set the correct creation date and time of the language configuration file LCONFIG.SYS. INSTALLAction: None. This message is for information only.504: Bindery files have been upgraded previously on this server. In the screen that follows you may elect to re-upgrade if you desire.  Re-upgrading the bindery is not advisable (although occasionally it may be necessary) since trustee rights on files for this server's volumes may be invalidated by a re-upgrade. INSTALLAction: Follow the suggestions in the message.505: Bindery files have been upgraded previously on this server. However, in the screen that follows you may elect to re-upgrade if you desire. INSTALLAction: Follow the suggestion in the message.506: The organization name cannot start or end with an underscore character (`_'), nor have multiple adjacent underscore characters.INSTALLAction: Choose a different organization name that does not start or end with an underscore character and does not have multiple adjacent underscore characters.507: The tree name cannot start or end with an underscore character (`_'), nor have multiple adjacent underscore characters.INSTALLAction: Choose a different tree name that does not start or end with an underscore character and does not have multiple adjacent underscore characters.5001: An error occurred copying `filename'. Execution cannot continue.INSTALLExplanation: An error occurred while trying to copy the file specified. Because this file is needed as part of the installation, the installation cannot continue.Action: Restart the installation. If the problem persists, contact your Novell Authorized Reseller.5002: The script file does not contain a list of SFT III files to copy.INSTALLExplanation: The user tried to install NetWare® 4.1 SFT IIITM; however, this version of the software does not contain SFT III installation information.Action: Contact your Novell Authorized Reseller.PAGENUM=328 ID="BP322"5003: Unable to create the directory "directory_name".INSTALLExplanation: The user tried to create a directory into which the new installation could take place. However, INSTALL was unable to create this directory. Action: Make sure enough space is on the hard disk. Make sure the disk is in a usable state.5004: Unable to read partition table on the hard disk. Check physical connections to the hard disk.INSTALLExplanation: The partition table on the hard disk is unreadable.Action: Make sure the hard disk is readable from DOS and formatted correctly.5005: The utility was unable to create the LCONFIG.SYS file. You must create this manually.INSTALLExplanation: As part of the installation process, INSTALL creates an LCONFIG.SYS file that contains the server language and other character translation tables. For some reason this file was not created as part of the installation. If you are installing an English version of NetWare, this missing file does not present a problem. However, if you are installing a language other than English, this file should be created.Action: If the server language is English, ignore the error. If the server language is any other language, make sure enough disk space is on the hard disk and that no previous copy of this file exists in the destination directory. You may install this file separately from the installation by typing INSTALL /LCONFIG at the command line, after completing the rest of the installation.5006: Unable to access command processor "filename".INSTALLExplanation: The command processor (usually COMMAND.COM) was not found in the search path.Action: Set the COMSPEC or SHELL variable in DOS to point to the correct directory and file.5007: Unable to access filename.INSTALLExplanation: The indicated file was found, but INSTALL was unable to access it.Action: If you are installing from the distribution CD-ROM, contact your Novell Authorized Reseller. PAGENUM=329 ID="BP323"5008: Unable to load help file.INSTALLExplanation: An internal problem occurred. Install was unable to load the "NWNSTLL.HLP" help file.Action: If you are installing from the distribution CD-ROM, contact your Novell Authorized Reseller. If you have copied the files from the CD-ROM to another location, make sure you copied all the files from the CD-ROM.5009: Unable to open installation command file "NETMAIN.ILS_filename".INSTALLExplanation: An internal problem has occurred.Action: If you are installing from the distribution CD-ROM, contact your Novell Authorized Reseller. If you have copied the files from the CD-ROM to another location, make sure you copied all the files from the CD-ROM.5010: An error prevented the utility from setting the language of the server to the preferred language.INSTALLExplanation: The server language will be set to English instead of the language specified.Action: You may set the language to the desired language later by typing INSTALL /LCONFIG at the command line, after completing the rest of the installation.5011: This utility can only be used for hard disk installation.INSTALLExplanation: The user tried to install to a destination that was not a hard disk.Action: Select a different path for your destination directory.5012: An error prevented the utility from selecting NetWare filenames.INSTALLExplanation: An error occurred during the creation of the LCONFIG.SYS file.Action: Make sure the destination directory is not write protected or in some other manner unusable. Retry the installation.5014: Unable to load system message file "name".INSTALLExplanation: The system message file could not be loaded. Action: Make sure that the file exists and that it is not read protected in some manner. 5015: No files matching the template filename could be found in the destination directory.INSTALLAction: Retry the installation. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=330 ID="BP324"5016: File "name" from the "label" diskette is missing. Unable to continue.INSTALLExplanation: An installation file is missing.Action: Contact your Novell Authorized Reseller.5017: The total space required by files that will be copied is larger than the free space available.INSTALLAction: Delete some of the files, install to a different disk, or create a larger partition on the disk.5018: You do not have write privileges for this file in the destination path.INSTALLExplanation: The file cannot be copied.Action: Make sure the user has normal Read Write access to the destination directory.5019: Unable to allocate sufficient memory to proceed.INSTALLExplanation: INSTALL needs more memory than is available on the server.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. After resolving the memory problem, restart the installation.5020: You have insufficient rights in the specified source path.INSTALLExplanation: The installation files cannot be read from the source directory.Action: If you are using the distribution CD-ROM, contact your Novell Authorized Reseller. If you have copied the files from the CD-ROM to a disk, make sure the user has Read access to the directories containing these files.5021: The destination drive does not exist, is not ready, or is a network drive.INSTALLAction: Select another drive.5022: The help file for this utility is not the correct version.INSTALLExplanation: An internal problem occurred.Action: Contact your Novell Authorized Reseller.5023: The installation script file contains an unrecognized command "name".INSTALLExplanation: An internal problem occurred.Action: Contact your Novell Authorized Reseller.PAGENUM=331 ID="BP325"5024: The server needs at least number kilobytes of free memory to boot. This machine has approximately number kilobytes of free memory. Press <F1> for help.INSTALLExplanation: Not enough free memory exists to load the server.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. 5025: This computer does not have an Intel 80386 or equivalent processor. NetWare 4.1 cannot be installed on this computer.INSTALLAction: Use another computer.5026: There is not enough space in the current destination path for all necessary boot files.INSTALLAction: Select a different path for installation.5027: One of the driver support files, "filename" was not copied. This must be copied by hand at a later time.INSTALLAction: Copy the designated file from its location on the distribution CD-ROM to the appropriate destination on the server.5028: A system error has occurred. Execution cannot continue.INSTALLAction: Restart the installation. If the problem persists, contact your Novell Authorized Reseller.5029: DOS returned error number while loading the installation utility "name".INSTALLAction: See the appropriate DOS reference manual.5030: An Expanded (EMS) Memory manager is loaded. The server cannot be loaded. Press <F1> for help.INSTALLExplanation: The server will not run with an EMS memory manager.Action: Remove EMM386 from the CONFIG.SYS file, and reboot the computer.PAGENUM=332 ID="BP326"INST_DOSThese messages are part of the online help in DOS Install.PAGENUM=333 ID="BP327"ID="FM24948"IOENGINE (SFT III)IOENGINE system messages originate in the input/output engine (IOEngine) of the NetWare® 4.1 SFT IIITM operating system.The IOEngine (input/output engine) is the part of the NetWare® 4.1 SFT IIITM operating system that handles physical processes such as network and disk I/O, hardware interrupts, device drivers, timing, and routing. The IOEngine is not mirrored; an error that occurs in the IOEngine occurs on one SFT III server only.The MSEngine (mirrored server engine) is the part of SFT III that handles nonphysical processes such as the NetWare file system, NetWare Directory Services, and queue management. An error that occurs in the MSEngine occurs on both SFT III servers. MSENGINE message numbers correspond to the SERVER error messages. For explanations of MSENGINE messages, see the IDREF="FM51388""SERVER" section of this manual.1561: Error transferring IOEngine error log to MSEngine. Error log remaining in DOS file.IOENGINE (SFT III)Explanation: The system is unable to move the IOEngine's error log file (IO$LOG.ERR) from the DOS partition to volume SYS: (MSEngine). Old messages will remain on the DOS partition, but new messages will be written to the SYS: volume.Action: Verify that volume SYS: is mounted and that enough space is on that volume for the log file.3896: Unable to allocate memory for other IOEngine screen.IOENGINE (SFT III)Explanation: Not enough IOEngine memory is available to service the other IOEngine's screen code, or an error occurred allocating additional memory for this use.Action: To view the amount of memory available in the IOEngine, use the MEMORY MAP command at each IOEngine console. Increase the memory available to the IOEngine, if necessary, by using the SET parameter New Start Address for Unclaimed Memory Block before the MSEngine is loaded. 3902: Attempt to bind protocol_name LAN protocol to the MSENGINE failed.IOENGINE (SFT III)Explanation: Some protocols need to be bound to the MSEngine. The system was unable to complete the bind for some reason.Action: Note the error code displayed with the message. Try the BIND command again. If you get the same the error code displayed with the message again, contact contact your Novell Authorized Reseller.PAGENUM=334 ID="BP328"3904: Protocol_name LAN protocol was NOT bound to the MSENGINEIOENGINE (SFT III)Explanation: The bind command for the protocol in the MSEngine didn't complete.Action: Note the error code displayed with the message. Try the BIND command again. If you get the same error code displayed with the message again, contact your Novell Authorized Reseller.3905: Attempt to unbind protocol_name LAN protocol from the MSENGINE failed.IOENGINE (SFT III)Explanation: The protocol bound to the MSEngine couldn't be unbound.Action: Note the error code displayed with the message. Try the UNBIND command again. If you get the same error code displayed with the message again, contact your Novell Authorized Reseller.3962: Secondary server had error claiming memory for MSEngine.IOENGINE (SFT III)Explanation: To synchronize, both primary and secondary servers must have matching memory to be claimed by the MSEngine. The secondary server must have at least as much unclaimed memory as the primary server, at the same memory address, or synchronization cannot happen. In most cases, the unclaimed memory on both servers (after the IOEngines are active) will be exactly the same.Action: Use the MEMORY MAP command to view what memory space is assigned to each engine and what memory is "unclaimed" or available. Align the memory on both servers so that the MSEngine has the same amount, at the same address, on each server using the New End Address for Unclaimed Memory Block and New Start Address for Unclaimed Memory Block SET parameters, as necessary.3965: Borrowed memory list does not match borrowed memory amount.IOENGINE (SFT III)Explanation: Occasionally the IOEngine "borrows" memory from the MSEngine. When borrowing or returning this memory, the same amount must be returned as was borrowed. In this case, those two amounts do not match.Action: Restart the IOEngine exhibiting the problem, especially if it's the secondary server. If it's the primary server, be sure the secondary server is in a state ready to take over (synchronized, fully mirrored, no inactive devices).3977: Error registering resource for SFT III MS-IO Communications.IOENGINE (SFT III)Explanation: The MSEngine and IOEngine communicate via internal queues managed by the NetWare® 4.1 SFT IIITM operating system. A resource registration (an essential part of interengine communication) failed.Action: Restart the IOEngine where the failure occurred.PAGENUM=335 ID="BP329"4019: Date_and_time: Failed trying to rename IO$LOG.ERR, file was deleted instead.IOENGINE (SFT III)Explanation: If the file IO$LOG.ERR cannot be renamed, the system deletes the file and starts a new log file with the same name.Action: Verify that the IO$LOG.ERR file is not flagged Read-Only. Search for another file named IO$LOG.??? and rename or delete it.4026: Error creating DOS file for mirrored server status dump.IOENGINE (SFT III)Explanation: The system was unable to write the MSSTATUS.DMP file to the DOS partition, probably because one or both servers failed and the system couldn't find the DOS partition.Action: Correct the server problem. Verify that the MSSTATUS.DMP file is not flagged Read-Only. Make sure that there is enough space on the DOS partition for the file.4027: Error seeking prior to writing mirrored server status dump to DOS file.IOENGINE (SFT III)Explanation: The DOS partition doesn't have enough space for the MSSTATUS.DMP file to be written.Action: Compare the available space on the DOS partition to the size of the MSSTATUS.DMP file. Limit the size of this file by using the Status Dump File Overflow Size SET parameter.4028: Error writing mirrored server status dump to DOS file.IOENGINE (SFT III)Explanation: The system was unable to write the MSSTATUS.DMP file to the DOS partition. The file may have been too large to fit in the available space on the DOS partition.Action: Compare the available space on the DOS partition to the size of the MSSTATUS.DMP file. Limit the size of this file by using the Status Dump File Overflow Size SET parameter.4029: Error creating file for mirrored server status dump.IOENGINE (SFT III)Explanation: The system couldn't create the MSSTATUS.DMP file.Action: Verify that the file attributes of MSSTATUS.DMP are not Read-Only. Verify that volume SYS: is mounted. Make sure that there is enough space on the DOS partition and the volume SYS: to create this file.4030: Error getting file size for mirrored server status dump.IOENGINE (SFT III)Explanation: An error occurred getting the size of the MSSTATUS.DMP file. The file size may have been zero, or too large for the system to handle.Action: To control the size of this file, use the Status Dump File Overflow Size SET parameter.PAGENUM=336 ID="BP330"4033: Date_and_time: failed trying to rename MSSTATUS.DMP, file was deleted instead.IOENGINE (SFT III)Explanation: If the file MSSTATUS.DMP cannot be renamed, the system deletes the file and starts a new dump file with the same name.Action: Verify that the MSSTATUS.DMP file is not flagged Read-Only. Search for another file named IO$LOG.??? and rename or delete it.4034: Error writing mirrored server status dump.IOENGINE (SFT III)Explanation: The MSSTATUS.DMP file from the DOS partition couldn't be appended to the MSSTATUS.DMP file in SYS:SYSTEM because volume SYS: is out of space.Action: Make room on volume SYS: by deleting old dump files or log files.4035: Error creating file for mirrored server status dump.IOENGINE (SFT III)Explanation: The system couldn't create the MSSTATUS.DMP file.Action: Verify that the file attributes of MSSTATUS.DMP are not Read-Only. Make sure that there is enough space on the DOS partition and volume SYS: to create this file. Verify that volume SYS: is mounted.4036: Error writing to file MSSTATUS.DMP for mirrored server status dump.IOENGINE (SFT III)Explanation: The MSSTATUS.DMP file from the DOS partition couldn't be appended to the MSSTATUS.DMP file in SYS:SYSTEM because volume SYS: is out of space.Action: Make room on volume SYS: by deleting old dump files or log files.4043: Unable to transfer mirrored server status dumps from DOS to SYS:SYSTEM.IOENGINE (SFT III)Explanation: The MSSTATUS.DMP file couldn't be moved to the SYS: volume because the volume wasn't mounted at the time.Action: Delete the MSSTATUS.DMP file from the DOS partition. Make sure that volume SYS: is mounted.4270: IPX Network number is now returning status check packets.IOENGINE (SFT III)Explanation: Status check packets are sent once per second for each network board in the server. A network board that failed previously is now functioning correctly, that is, responding with the correct packets.Action: No action is required unless this message frequently recurs with message 4271. If this is the case, give the system a little more time before determining that a network board has failed by increasing the IPX Internet Down Wait Time SET parameter.PAGENUM=337 ID="BP331"4271: IPX Network number is no longer returning status check packets.IOENGINE (SFT III)Explanation: A network board has failed, maybe only for a packet or two. If this server is the primary server, and the system determines that the other server has more functional network boards, that server will become the primary server.Action: No action is required unless this message frequently recurs with message 4270. If this is the case, give the system a little more time before determining that a network board has failed by increasing the IPX Internet Down Wait Time SET parameter.4272: IPX Network number is no longer returning status check packets and the LAN adapter is jammed transmitting packets.IOENGINE (SFT III)Explanation: A network board in this server cannot return or transmit status check packets.Action: Unload and reload the driver of the jammed network board. As a last resort, restart the server to force the network board to reset.4273: Failure reason as detected by other server: failure_typeIOENGINE (SFT III)Explanation: This is the surviving server's "best guess" as to why the other server failed. It's a good indication of where to start checking for hardware failures.Action: Note the failure type and contact your Novell Authorized Reseller. (The specific action to take varies with the failure type.)4275: The IPX internet may be too slow to notify the secondary server if the MSL fails...increase the `Secondary Take Over Wait Time'.IOENGINE (SFT III)Explanation: The IPX internet timeout is close to a limit that makes it difficult for the system to decide whether the network is really down or is just temporarily sluggish.Action: Add a second or more to the Secondary Take Over Wait Time SET parameter.4277: The IPX Internet appears to be down (no "I'm alive" packets received for a second).IOENGINE (SFT III)Explanation: A network board in one of the servers may have failed.Action: Verify that the network cables and connections are installed correctly. Make sure the LAN drivers are loaded and bound to the network boards. If this message frequently recurs, give the system a little more time before reporting that a network board has failed by increasing the IPX Internet Down Wait Time SET parameter.PAGENUM=338 ID="BP332"4280: IPX route to the other server has been lost.IOENGINE (SFT III)Explanation: A network board in one of the servers may have failed, a network cable may have been disconnected, or a router may have failed.Action: Make sure that the LAN drivers are loaded and the correct protocols are bound to the network boards. Make sure that the network boards and cables in each server are installed correctly. Make sure that routers between the two servers are functioning.4284: Error starting the 2nd processor.IOENGINE (SFT III)Explanation: The dual processor driver supplied by your hardware vendor couldn't activate the second processor.Action: Unload and reload the dual processor driver. Also, make sure the hardware is installed correctly and that you have the right DP driver. If necessary, call the DP hardware vendor.4286: MSL Failure on all MSLs.IOENGINE (SFT III)Explanation: When an MSL fails, if there's an alternate board available the system will try to use it. If all of the MSLs fail, this message appears after the secondary server runs its diagnostic test.Action: Run hardware diagnostic tests on the MSL boards, and install new MSL boards if necessary.4287: MSL deactivated.IOENGINE (SFT III)Explanation: One of the MSLs in the server failed and has been deactivated.Action: Reload the MSL driver, or restart the server. Run a hardware diagnostic test on the MSL board to verify its functionality.4288: Other server attempted to synchronize but this server is down.IOENGINE (SFT III)Explanation: The servers cannot synchronize unless both IOEngines are active and a functional MSL driver is loaded.Action: Type EXIT from this server's IOEngine prompt. Type MSERVER at the other server's console prompt. Make sure both servers have an IOEngine before typing ACTIVATE SERVER.4289: Mirrored Server Link broken then reestablished with other server.IOENGINE (SFT III)Explanation: Some MSL drivers can reestablish the MSL connection if it is broken briefly, as in this situation.Action: None. If this message recurs frequently, there may be a problem with your MSL hardware.PAGENUM=339 ID="BP333"4291: Invalid mirrored server initialization message received from the other server.IOENGINE (SFT III)Explanation: The messages received from the other server over the MSL are not valid.Action: Verify that the cables for the MSL boards and the network boards are installed correctly. Also, make sure the correct MSL driver is loaded. Unload the MSL drivers on both IOEngines, then reload them one at a time. The servers should synchronize when the second MSL driver is loaded. If the MSL connection is functioning properly, increase the number of seconds in the Restart Minimum Delay Amount SET parameter. If the servers are in Test Mode, no action is required as long as the servers continue to synchronize.4292: MSL failure during initialization.IOENGINE (SFT III)Explanation: This MSL has failed during its initial diagnostic test, before becoming fully active as a mirrored server link.Action: Unload the MSL driver, then reload it. If this message recurs, you may have to install a new MSL.4293: Failure_type failure during synchronization.IOENGINE (SFT III)Explanation: The servers couldn't synchronize due to the specified failure.Action: (The specific action to take varies with the failure type.) Try to resynchronize the servers by bringing up the secondary IOEngine again.4297: MSL driver failure notification during hold off...Since this is the secondary server, clients may hang or lose connection. Updated MSL driver recommended.IOENGINE (SFT III)Explanation: Unless you replace your MSL driver, some clients may lose their connection with the server when a switchover occurs.Action: Contact your MSL vendor for a newer MSL driver.4299: This error was unexpected (not generated by server test).IOENGINE (SFT III)Explanation: A genuine hardware error occurred during Server Test Mode.Action: Turn off the "Server Test Mode" until the hardware problem is resolved.4300: Synchronization error generated by custom mirrored server NLM.IOENGINE (SFT III)Explanation: A custom NLM using the MSL board couldn't handle a change of state in the operating system.Action: Unload the custom mirrored server NLM. If this isn't possible, reboot the server.PAGENUM=340 ID="BP334"4301: This server discovered a "stuck" LAN packet, which precludes server synchronization.IOENGINE (SFT III)Explanation: The network board or driver has failed to transmit a packet and cannot receive or transmit additional packets.Action: Unload and reload the LAN driver. Or, unload and reload the MSL driver on either server. You may have to turn off the server with the bad network board to reset the server. Make sure the other server is fully functional before powering off this server.4302: Mirrored server will be revived since the other server seems to be halted.IOENGINE (SFT III)Explanation: The secondary server was supposed to shut down, but a system check revealed that the primary server is not functioning, so the secondary server kept running.Action: Resolve the problems with the other server and resynchronize it with this server.4304: This server does not know how to route via IPX to the secondary server.IOENGINE (SFT III)Explanation: A network board in one of the servers may have failed, a network cable may have been disconnected, or a router may have failed.Action: Make sure the LAN drivers are loaded and bound to the network boards in the primary and secondary servers, and that the hardware is installed correctly. Also, make sure any routers between the two SFT III servers are functional.4306: Error giving additional RAM to MSEngine.IOENGINE (SFT III)Explanation: Unequal amounts of RAM have been installed in the two SFT III servers (such as during an upgrade).Action: Use MEMORY MAP to view how the system has assigned memory to the different engines; then, as necessary, align the memory on both servers so that the MSEngine has the same amount on each server by using the New End Address for Unclaimed Memory Block and New Start Address for Unclaimed Memory Block SET parameters.4309: This server does not know how to route via IPX to the primary server.IOENGINE (SFT III)Explanation: A network board in one of the servers may have failed, a network cable may have been disconnected, or a router may have failed.Action: Make sure the LAN drivers are loaded and bound to the network boards in the primary and secondary servers, and that the hardware is installed correctly. Also, make sure any routers between the two SFT III servers are functional.PAGENUM=341 ID="BP335"4311: Failure_type failure...checking if the primary server is alive over the IPX internet.IOENGINE (SFT III)Explanation: The MSL has failed and the secondary server is verifying that the primary server is still functional. If the primary server is functional, the secondary server will restart or abend.Action: Restart the secondary server. If restarting the secondary server doesn't solve the problem, note the failure type and contact your Novell Authorized Reseller. The specific action to take varies with the failure type.4312: Primary server failed due to failure_type ...this server is becoming the primary but the server has been downed.IOENGINE (SFT III)Explanation: The failure brought down the MSEngine, and the primary server exited to DOS. The secondary server ("this server") started to assume the primary server role, then detected that the MSEngine was down.Action: Reboot both servers.4314: Number of memory segments exceeds synchronization record limit.IOENGINE (SFT III)Explanation: The MSEngine memory space on this server is fragmented into more than nine segments and cannot synchronize memory with the other server.Action: Reconfigure this server to reduce the memory fragmentation. Use the MEMORY MAP command to make sure that memory destined for the MSEngine (shown as "Unclaimed" memory before the server is activated) is identical on both computers.4315: Number of screen modes exceeds synchronization record limit.IOENGINE (SFT III)Explanation: The number of screen modes on this server has exceeded 10 and is more than the MSEngine screen driver can handle.Action: Unload one or more screen drivers in the MSEngine.4316: Other server's IOEngine software version does not match.IOENGINE (SFT III)Explanation: The versions of MSERVER.EXE on both servers are different.Action: Update the older of the two files so that they match.4317: Other server's protection level does not match.IOENGINE (SFT III)Explanation: The settings for DOMAIN.NLM on both servers are different.Action: Load DOMAIN.NLM identically on the two servers.PAGENUM=342 ID="BP336"4318: Other server's screen address does not match (cannot mirror monochrome to color screen).IOENGINE (SFT III)Explanation: The monitor types on both servers are not identical (VGA, CGA, and so forth) and the servers cannot synchronize.Action: Make sure both servers have the same type of monitors and monitor boards installed. Also, make sure both servers have the same brand and version of DOS installed.4319: Other server's IOEngine not loaded at the same location in memory (this server at number, other server at number).IOENGINE (SFT III)Explanation: The memory locations for both IOEngines do not match.Action: Use MEMORY MAP to view how the system has assigned memory to the different IOEngines; then, as necessary, align the memory on both servers by using the New End Address for Unclaimed Memory Block and New Start Address for Unclaimed Memory Block SET parameters.4320: Both servers have active MSEngines.IOENGINE (SFT III)Explanation: Both servers are acting as primary servers and are servicing clients. They are no longer mirrored.Action: Decide which server should be primary server and bring down the other server.4321: Neither server has an active MSEngine...will auto synchronize when one is activated.IOENGINE (SFT III)Explanation: Both IOEngines are active and the MSLs are communicating, but no MSEngine is active yet.Action: Type ACTIVATE SERVER at the IOEngine prompt of one server.4322: Secondary server is missing RAM at number length number.IOENGINE (SFT III)Explanation: The secondary server does not have enough RAM to match the primary server, so it cannot synchronize.Action: Align the server memory by using the New End Address for Unclaimed Memory Block and New Start Address for Unclaimed Memory Block SET parameters. You may also bring down both servers and make the server with the smaller amount of RAM the primary server by typing ACTIVATE SERVER at its IOEngine prompt.4323: Both server's IOEngines have the same IPX internal network number.IOENGINE (SFT III)Explanation: Each IOEngine must have a unique IPX internal network number.Action: Edit the IOSTART.NCF file on one server to change its IPX internal network number, then restart that server.PAGENUM=343 ID="BP337"4324: Secondary IOEngine IPX internal net number matches the MSEngine's IPX internal net number.IOENGINE (SFT III)Explanation: The IOEngines and the MSEngine must have unique IPX internal network numbers.Action: Edit the IOSTART.NCF file on the secondary server to change the IPX internal network number, then restart that server.4325: IOEngines have different LAN receive buffer sizes (this server has number, other server number)IOENGINE (SFT III)Explanation: The LAN receive buffer sizes on both IOEngines must match so that no packets are lost during or after a server switchover.Action: Edit the IOSTART.NCF file for each server and make sure the Minimum Packet Receive Buffers setting is the same.4326: IOEngines have the same names (give the secondary a different name)IOENGINE (SFT III)Explanation: Each IOEngine must have a unique name.Action: Type in a different IOEngine name. To prevent this problem the next time the server boots, at the console prompt, edit the secondary server's IOSTART.NCF file and change its IOEngine name.4327: Insufficient memory to store other IOEngine's name. IOENGINE (SFT III)Explanation: Each IOEngine stores the name of its "partner" IOEngine. This error occurs if the allocation of memory for storing this name failed, or if the IOEngine is out of memory.Action: Unload one or more NLMs from this server's IOEngine. Or, increase the memory available to the IOEngine by using the MEMORY MAP command and the SET parameter New Start Address for Unclaimed Memory Block.4330: MSEngine activated...will synchronize with other server if it's there.IOENGINE (SFT III)Explanation: This SFT III server is running standalone, with a fully active IOEngine and MSEngine.Action: Type MSERVER at the other server's console prompt.4365: Failure_type (this server is remaining the primary server).IOENGINE (SFT III)Explanation: The secondary server has failed, but the primary server is unaffected. Fault tolerance is compromised, but no switch over occurred.Action: Resolve the problem with the secondary server and resynchronize it with the primary server to restore fault tolerance.PAGENUM=344 ID="BP338"4402: Mirrored server comm link switched MSLs.IOENGINE (SFT III)Explanation: The active or first-loaded MSL has failed, and the server has begun using an alternate MSL for the server-to-server communication.Action: Find out why the first MSL failed.4403: Waiting for first loaded MSL to respond. Wait may take up to one minute.IOENGINE (SFT III)Explanation: When an MSL failure occurs and the secondary server restarts, SFT III will try to use the first-loaded MSL first. In many cases, restarting the MSL is enough to solve the problem. If the first MSL still doesn't respond to the internal diagnostic check, the system will continue to try for up to a minute before giving up and using the alternate MSL.Action: This message may indicate a problem with your first MSL hardware.PAGENUM=345 ID="BP339"IPCONFIG1: Could not create a screen for error messages.IPCONFIGExplanation: IPCONFIG encountered some errors while parsing the database, and when it tried to report the errors, it could not create a screen. This usually indicates a memory shortage. Action: Use INETCFG to check the static routing table for obvious problems. For information on INETCFG, see "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference. Try releasing some memory and reloading IPCONFIG. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. 3: Could not identify the token: filename.IPCONFIGExplanation: IPCONFIG could not parse an entry in the GATEWAYS file (this file contains the static routes). The token given was not a known parameter. Action: The GATEWAYS file is created by INETCFG. If you have edited this file, use INETCFG to correct any errors, and then reload IPCONFIG. For information on INETCFG, see "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference.4: No destination address.IPCONFIGExplanation: A destination address is missing for an entry in the GATEWAYS file. Action: Use INETCFG and make sure each static route has a corresponding IP address. For information on INETCFG, see "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference.5: No GATEWAY parameter.IPCONFIGExplanation: The GATEWAY parameter is missing from a static route in the GATEWAYS file. The GATEWAY parameter is required in all entries. Action: Use INETCFG and make sure each static route has a valid GATEWAY (Next Hop Type) parameter. For correct syntax, see BOOK="tcpipenu" COLLECTION="nw41"NetWare TCP/IP Reference. For information on INETCFG, see "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference.6: Redundant GATEWAY parameter.IPCONFIGExplanation: Two GATEWAY parameters are assigned for a single route. Action: Edit the GATEWAYS file and remove any extra GATEWAY parameters. For correct syntax, BOOK="tcpipenu" COLLECTION="nw41"NetWare TCP/IP Reference.PAGENUM=346 ID="BP340"7: No METRIC parameter.IPCONFIGExplanation: The METRIC parameter is missing in the GATEWAYS file. Action: Use INETCFG to edit the TCP/IP static routes. Ensure that all entries in the TCP/IP static routing table have been assigned a METRIC parameter between 1 and 16. For correct syntax, see BOOK="tcpipenu" COLLECTION="nw41"NetWare TCP/IP Reference. For information on INETCFG, see "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference.8: Redundant METRIC parameter. IPCONFIGExplanation: Two METRIC parameters are in the TCP/IP static routing table. Action: Edit the GATEWAYS file and remove any extra METRIC parameters. For correct syntax, see BOOK="tcpipenu" COLLECTION="nw41"NetWare TCP/IP Reference. 9: Invalid METRIC parameter. IPCONFIGExplanation: A METRIC parameter in the static routing table is invalid. The accepted range of values is between 1 and 16. Action: Use INETCFG to edit the TCP/IP static routing table. Check the METRIC parameter for each entry and ensure that the value is within the valid range. For correct syntax, see BOOK="tcpipenu" COLLECTION="nw41"NetWare TCP/IP Reference.10: Redundant PASSIVE parameter. IPCONFIGExplanation: Two PASSIVE parameters are assigned for a single static route in the TCP/IP static routing table. Action: Edit the GATEWAYS file and remove any extra PASSIVE parameters. For the correct syntax, see BOOK="tcpipenu" COLLECTION="nw41"NetWare TCP/IP Reference.11: Redundant ACTIVE parameter. IPCONFIGExplanation: Two ACTIVE parameters are assigned for a single static route in the TCP/IP static routing tables. Action: Edit the GATEWAYS file and remove any extra ACTIVE parameters. For correct syntax, see BOOK="tcpipenu" COLLECTION="nw41"NetWare TCP/IP Reference.15: GATEWAY and CALL cannot be used together. IPCONFIGExplanation: The GATEWAY and CALL parameters are in conflict. A static route can be either a CALL (WAN Call Destination) or a GATEWAY. Action: Edit the GATEWAYS file and change the static route to be either a CALL or a GATEWAY.PAGENUM=347 ID="BP341"16: You must specify either a next hop gateway or a WAN call destination. IPCONFIGExplanation: Every static route must be configured as either a next hop gateway or a WAN Call Destination. One or more entries in the TCP/IP static routing table are missing the GATEWAY and the CALL parameters. Action: Use INETCFG to edit the TCP/IP static routing table. Make sure every entry in the table has the "Next Hop Type" set. For information on INETCFG, see "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference.17: Gateway IP_address is not directly connected to this node. IPCONFIGExplanation: IPCONFIG cannot locate the specific gateway, or the gateway is not connected to this network. Action: Check the provided address and make sure the gateway is directly on the same network as this node. If not, use INETCFG to change the TCP/IP static routing table. For information on INETCFG, see "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference.20: No resources for routing entry. IPCONFIGExplanation: The routing entry could not be added to the TCP/IP static routing table. Action: Unload IPCONFIG. Increase the available memory. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. Reload IPCONFIG.21: Could not open filename. IPCONFIGExplanation: IPCONFIG could not open the file indicated by the file parameter. The most common reason for this error is that the file does not exist. Action: Unload IPCONFIG. Use INETCFG to create a TCP/IP static routing table. Reload IPCONFIG. For information on INETCFG, see "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference.22: No static routes configured. IPCONFIGExplanation: IPCONFIG did not configure any static routes. This means it found the database; however, the database was empty. Action: If you want a TCP/IP static routing table, use INETCFG to add static routes to the database. For information on INETCFG, see "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference.23: Aborted reading from filename. IPCONFIGExplanation: IPCONFIG encountered an error and stopped reading the SYS\ETC\GATEWAYS file. PAGENUM=348 ID="BP342"Action: Unload IPCONFIG. Use INETCFG to correct the TCP/IP static routing table, or edit the GATEWAYS file and look for syntax errors that would cause IPCONFIG to abort. For correct syntax, see BOOK="tcpipenu" COLLECTION="nw41"NetWare TCP/IP Reference. Once the errors are corrected, reload IPCONFIG. For information on INETCFG, see "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference.24: The following errors were encountered while reading filename: IPCONFIGExplanation: IPCONFIG lists all errors that it discovered while processing the database. These routes were not entered in the TCP/IP static routing table for the given reasons.Action: Use INETCFG to correct the routes, and then reload IPCONFIG. For information on INETCFG, see "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference.25: Ignoring mask for host IP_address. IPCONFIGExplanation: A mask is not required for a static route to a host. This route was added to the routing table, but the mask was ignored. Action: If the intent was to specify a static route to a host, no action is required. If a route to a subnet was intended, use INETCFG and change the "Route to Network or Host" field to "Network"; then reload IPCONFIG. To avoid this error, remove the mask when the route is to a host. For information on INETCFG, see "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference.26: The network address network is incorrect. Using address network. IPCONFIGExplanation: Host bits were detected in a (sub)network static route. The route was added to the routing table, but the host bits were ignored. Action: If the intent was to specify a static route to a (sub)network, no action is required. To resolve the message condition, load INETCFG and remove the host bits from the address. If a route to a host was intended, use INETCFG to change the "Route to Network or Host" field to "Host"; then reload IPCONFIG. For information on INETCFG, see "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference.27: The loopback host IP_address is not a legal destination or gateway. IPCONFIGExplanation: The loopback host address was given as the static route. This address is not allowed in the TCP/IP static routing table. Action: To eliminate this warning, use INETCFG to remove the loopback address from the TCP/IP static routing table. For information on INETCFG, see "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference.28: The loopback network 127.0.0.0 is not a legal route destination. IPCONFIGExplanation: The loopback network address was given as a static route to a network. This address is not allowed in the TCP/IP static routing table. Action: To eliminate this warning, use INETCFG to remove the loopback address from the TCP/IP static routing table. For information on INETCFG, see "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference.PAGENUM=349 ID="BP343"29: Null pointer passed to inet_hostent library function.IPCONFIGExplanation: An invalid parameter was given to an internal routine (the inet_hostent function).Action: Contact your Novell Authorized Reseller.30: Null pointer passed to inet_netent library function. IPCONFIGExplanation: An invalid parameter was given to an internal routine (the inet_netent function). Action: Contact your Novell Authorized Reseller.31: Unknown error returned by inet_hostent. Error code: code. IPCONFIGExplanation: The inet_hostent routine returned an error trying to resolve an IP address. The error code given is the error returned by the inet_hostent function.Action: Contact your Novell Authorized Reseller.32: Unknown error returned by inet_netent. Error code: code. IPCONFIGExplanation: The inet_netent routine returned an error trying to resolve a network address. The error code given is the error returned by the inet_netent function.Action: Contact your Novell Authorized Reseller.33: Invalid token token. Could not parse input string.IPCONFIGExplanation: IPCONFIG could not parse the load line. The indicated parameters were unknown. Action: The correct load line is as follows:FORMAT="LINESPECIFIC"MOREINFO="NONE"load IPCONFIG [active | passive] 34: Invalid address IP_address: must be class A, B, or C. IPCONFIGExplanation: The address given in the database was an invalid IP address. IP addresses must be in dotted decimal notation: nn.nn.nn.nn.Action: Use INETCFG to check the IP addresses given in the TCP/IP static routing table. Make sure all addresses are in dotted decimal notation. For information on INETCFG, see "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference.PAGENUM=350 ID="BP344"35: Invalid address IP_address. First byte cannot be zero. IPCONFIGExplanation: The indicated IP address is invalid. Action: Use INETCFG to change the incorrect IP address in the TCP/IP static routing table. For information on INETCFG, see "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference.36: Invalid address IP_address. Subnet field is all ones. IPCONFIGExplanation: The indicated IP address is invalid. Subnets are not allowed to be all 1's. Action: Use INETCFG to change the incorrect IP address in the TCP/IP static routing table. For information on INETCFG, see "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference.37: Invalid address IP_address. Host field is all zeros or all ones. IPCONFIGExplanation: The indicated IP address is invalid. Host fields are not allowed to be all 0's or all 1's. Action: Use INETCFG to correct the IP address in the TCP/IP static routing table. For information on INETCFG, see "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference.38: Invalid mask IP_address. Mask must be at least length. IPCONFIGExplanation: The subnet mask provided is too short. Action: Use INETCFG to correct the subnet mask. For information on INETCFG, see "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference.39: Invalid mask mask. Mask for default route must be zero. IPCONFIGExplanation: The subnet mask for the default route MUST be all 0's.Action:  Use INETCFG to correct the subnet mask for the default route, and then reload IPCONFIG. For information on INETCFG, see "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference.40: IP_address is a local address. The next hop for a remote route must not be a local address. IPCONFIGExplanation: The address given was an IP address of the local server. Action: Use INETCFG to correct the IP address, and then reload IPCONFIG. For information on INETCFG, see "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference.PAGENUM=351 ID="BP345"41: IP_address is a host address. A NET route requires a network or subnetwork destination.IPCONFIGExplanation: The provided IP address is a full host address. The setting for Route to Network or Host is set to "Network." A full address is not required for a network destination.Action:  Use INETCFG to reset the address to just a network address. If the intent was to indicate a host, set the "Route to Network or Host" field to "Host." For information on INETCFG, see "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference.PAGENUM=352 ID="BP346"IPTUNNEL3: Could not validate the peer address (IP_address). IPTUNNELExplanation: The IP address specified is not a valid IP address. Action: Change the peer IP address to a valid class A, B, or C address. For information on class A, B, or C addresses, see 
BOOK="tcpipenu" COLLECTION="nw41"NetWare TCP/IP Reference4: IP_address is an illegal peer address. The peer cannot be the address of one of the local IP interfaces. IPTUNNELExplanation: A peer parameter has been given to the IP tunnel, indicating that a local address is an IP tunnel peer. This is not valid. Action: Do not use a local address as an IP tunnel peer.6: IP must be bound to at least one network interface. IPTUNNEL will not load until it detects an IP address for this node.IPTUNNELExplanation: IP cannot find any local IP addresses because IP has not been bound to any drivers. Action: Bind IP to a LAN driver before loading the IP tunnel.7: Could not allocate memory to add IP_address to the peer list.IPTUNNELExplanation: The server is out of memory. The IP tunnel could not add the indicated peer to the peer list. Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. 8: Could not allocate a resource tag.IPTUNNELExplanation: The server is out of memory. The IP tunnel cannot complete the initialization. Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. 9: IP_address is not currently a local IP address.IPTUNNELExplanation: The IP tunnel found the "local" parameter, but the indicated address is not a local IP address. Action: Provide a local address for the "local" parameter, or bind IP to a LAN driver with the indicated address as the "addr" parameter before loading the IP tunnel.PAGENUM=353 ID="BP347"12: UDP port port_number (hex_port_number) is in use. IPTUNNELExplanation: The IP tunnel tried to use the indicated UDP port for IP tunnel traffic, but the port was already in use. Action: Specify the correct UDP port in the port parameter, or unload the application that is using that UDP port.13: Could not register port port_number with UDP (error code). IPTUNNELExplanation: The IP tunnel encountered an unexpected error while trying to register with the UDP port. Action: Contact your Novell Authorized Reseller.14: UDP rejected port port_number (hex_port_number) as invalid. IPTUNNELExplanation: UDP could not use the port number you gave the IP tunnel in the port parameter. Port numbers must be less than 65,536.Action: Specify a port number within the range.15: UDP rejected UDP interface version number. IPTUNNELExplanation: UDP no longer supports the UDP interface version that the IP tunnel uses. This can happen only if your versions of the IPTUNNEL.LAN and TCPIP.NLM files are incompatible. Action: Use the IPTUNNEL.LAN and TCPIP.NLM files from the same release of the NetWare operating system.16: `Port_number' is not a valid port value. IPTUNNELExplanation: The value given for the port parameter is not a valid UDP port value. Port numbers must be less than 65,536. Action: Specify a port number within the range.20: The address value is illegal. IPTUNNELExplanation: The command line contains an IP address that contains a syntax error. Action: Correct the IP address. Make sure all addresses are in dotted decimal notation.22: Found `character'. Each byte of IP address must be separated by `.'. IPTUNNELExplanation: The command line contained an IP address in which two bytes were separated by the indicated character rather than the required dot. Action: Correct the IP address. Make sure all addresses are in dotted decimal notation.PAGENUM=354 ID="BP348"23: Please use `Yes' or `No' as the argument to `name' parameter.IPTUNNELExplanation: A parameter that requires a "Yes" or "No" argument had neither.Action:  Use "Yes" or "No" as the parameter.24: `Token' is not recognized as affirmative or negative. IPTUNNELExplanation: The token is not valid for a parameter that requires a "Yes" or "No" argument. Action: Use "Yes" or "No" as the parameter.25: Ignored the ambiguous parameter `name'. IPTUNNELExplanation: A parameter on the load line does not have enough characters specified to be unique.Action: Reload IPTUNNEL with enough characters specified so that each parameter is unique.26: Ignored the unrecognized parameter `name'. IPTUNNELExplanation: The indicated parameter is not a valid IPTUNNEL parameter. Action: Correct the parameter and reload IPTUNNEL.LAN.27: `Name' is a duplicate parameter. The previous one has been overridden. IPTUNNELExplanation: The previously specified value for the parameter is replaced with the new value. Action: None if you intended to change the value of the parameter.PAGENUM=355 ID="BP349"IPXCON161: Unexpected failure from SMILE initialization: router.IPXCONExplanation: To retrieve information from this router and/or remote routers, you need to register with SNMP.NLM. The registration failed; therefore, you cannot get any information.Action: Contact your Novell Authorized Reseller.366: Unexpected failure from TUI initialization: router.IPXCONExplanation: To display information from this router and/or remote routers, you need to register with TUI.NLM. The registration failed; therefore, you cannot display any information.Action: Contact your Novell Authorized Reseller.368: Setting the locale failed.IPXCONExplanation: You tried to set the local language value. Action: Contact your Novell Authorized Reseller.371: The community name parameter value is not valid.IPXCONExplanation: You did not enter a community name, or you entered a community name longer than 32 characters.Action: Enter a valid community name (no longer than 32 characters).372: The request poll interval value is not valid.IPXCONExplanation: You entered an invalid poll interval value.Action: Remove the parameter option, or specify a value between 0 and 900.373: This parameter is not recognized: value.IPXCONExplanation: You entered an invalid parameter name on the load line.Action: Enter a valid parameter name.PAGENUM=356 ID="BP350"IPXFLT2: Error registering IPX Filter with the Filter Services module.IPXFLTExplanation: Could not register the IPX filter with the filter services module.Action: Check the error messages generated by FILTSRV.NLM. Also, make sure the software versions are compatible.3: Error registering IPX Filter with IPXRTR.IPXFLTExplanation: The IPX filter could not be registered with the IPXRTR module. The filters have not taken effect.Action: Make sure the IPXRTR.NLM file is loaded. Also, make sure the software versions are compatible.4: Error allocating memory for maximum number of boards possible.IPXFLTExplanation: The server may not have enough available memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.5: Error allocating Resource Tags.IPXFLTExplanation: The server may not have enough available memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.7: Unable to allocate memory for filter on board name.IPXFLTExplanation: The server may not have enough available memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.10: Unable to allocate memory while adding filter.IPXFLTExplanation: The server may not have enough available memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.11: Error registering virtual network with IPX Filter module.IPXFLTExplanation: Fatal program error. This might indicate that another module is trying to use the NLSP filter interface illegally.Action: Check system modules and unload anything suspicious. Check the configuration and reboot server.PAGENUM=357 ID="BP351"12: Unable to register exit function with the operating system.IPXFLTExplanation: The server may not have enough available memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.PAGENUM=358 ID="BP352"IPXNCP1: The message file name is invalid. The program cannot be loaded.IPXNCPExplanation: The .MSG file is invalid. This problem could be the result of a corrupted file, a bad translation, or an outdated file version.Action: Either update the.MSG file with a valid copy or delete the file. The NetWare DOS Requester will use the default messages that are bound to the binary files.5: Module1.VLM is not loaded. The module2.VLM file cannot be loaded before module1.VLM. Load the module1.VLM file first then try to load the module2.VLM file.IPXNCPExplanation: The module2.VLM requires that the module1.VLM be loaded first. Either the current configuration has module1.VLM and module2.VLM loading out of order, or module1.VLM did not load successfully.Action: Make sure that module1.VLM is configured to load before module2.VLM. To do this, change the load order of the "VLM=" parameter in the NET.CFG file. For information on the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.7: In order to load the module3.VLM, one of the following VLM programs must be loaded: module1.VLM, module2.VLM.IPXNCPExplanation: The module3.VLM requires that module1.VLM or module2.VLM be loaded first. Either the current configuration has module3.VLM loading before the modules in the module1.VLM or module2.VLM list, or module1.VLM or module2.VLM did not load successfully.Action: Make sure that module1.VLM or module2.VLM load successfully before loading module3.VLM.42: There is a missing or invalid value for `parameter' on line number of the configuration file. This entry will be ignored. Correct the line specified in the configuration file before continuing.IPXNCPExplanation: The configuration file contains a configuration keyword that has an invalid parameter or that does not specify a parameter. This invalid line will be ignored by the configuration process.Action: Because this line will be ignored, no action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the message.PAGENUM=359 ID="BP353"43: There is a missing or invalid ON/OFF value for `parameter' on line number of the configuration file. This entry will be ignored. Correct the line specified in the configuration file before continuing.IPXNCPExplanation: The configuration file contains a configuration keyword that is defined to use either an "ON" or "OFF" parameter, but a different parameter or no parameter has been specified. This invalid line will be ignored by the configuration process.Action: Because this line will be ignored, no action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the message.45: The parameter specified for the following option was out of range and has been adjusted.IPXNCPExplanation: A configurable parameter has been configured too high or too low to be valid. The parameter is specified on the line following the message.Action: Check and correct the parameter specified in the NET.CFG file. For information on the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.53: The IPX interface is not loaded. The IPXNCP.VLM file cannot be loaded. Load the IPXODI.COM file first and then try loading the IPXNCP.VLM file.IPXNCPExplanation: An attempt was made to load the IPXNCP.VLM file without having previously loaded the IPX interface.Action: Load IPXODI.COM before trying to load IPXNCP.VLM.54: The IPX sockets could not be opened. The IPXNCP.VLM file cannot be loaded. Configure the IPXODI.COM file for enough sockets in the NET.CFG file and then try to load the IPXNCP.VLM file.IPXNCPExplanation: The IPXNCP.VLM file failed to open the IPX sockets needed to run. The IPXNCP.VLM module requires four or more IPX sockets be available.Action: Increase the number of IPX sockets available by using the "IPX SOCKETS=" parameter in the NET.CFG file; then reload IPXODI.COM and then IPXNCP.VLM.55: The IPX interface does not support checksums. The IPXNCP.VLM file will load successfully without using checksums. Make sure the installed IPXODI.COM is version 2.01 or later and that it is not bound to a board configured to use the ETHERNET_802.3 frame format.IPXNCPPAGENUM=360 ID="BP354"Explanation: IPXNCP.VLM will load without supporting checksums. For checksum to be supported, the loaded IPXODI.COM file must support checksums. Either the loaded version of IPXODI.COM does not have checksum support, or the protocol bound to IPX does not support checksums.Action: Because IPXNCP.VLM can load without support for checksums, no action is required at this point. However, to avoid receiving this message the next time the IPXNCP.VLM file is loaded, either load IPXODI.COM with checksum support enabled, or add "CHECKSUM=OFF" to the NET.CFG file. For information on the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.56: The IPX socket for large internet packets could not be opened. The IPXNCP.VLM file will load successfully without using large internet packets. Configure the IPXODI.COM file for enough sockets in the NET.CFG file or add LARGE INTERNET PACKETS=OFF to the NET.CFG file; then load the IPXNCP.VLM file.IPXNCPExplanation: This message is only a warning. The NetWare DOS Requester functions properly without the use of Large Internet Packets. The Large Internet Packet protocol, which is a part of the IPXNCP.VLM module, requires an IPX socket to function properly. The request to open a socket failed indicating that not enough IPX sockets are available.Action: If you want Large Internet Packets, make sure that the IPX interface is configured for enough sockets in the NET.CFG file before loading the NetWare DOS Requester. If Large Internet Packets are not desired, add "LARGE INTERNET PACKETS=OFF" to the "NETWARE DOS REQUESTER" section of the NET.CFG file. For information on the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.PAGENUM=361 ID="BP355"IPXODI1: Message file name is invalid. Program load aborted.IPXODIExplanation: An external IPXODI.MSG file was encountered in one of the message file search paths.Action: Remove or replace the *.MSG file with a correct version; then attempt to load IPXODI.COM again.12: The IPX protocol has already been loaded.IPXODIExplanation: You attempted to load IPXODI.COM more than once.Action: None. This message is for information only.13: The LSL is not loaded. Please load the LSL then IPXODI.IPXODIExplanation: You attempted to load IPXODI.COM before loading LSL.COM.Action: Load LSL.COM and IPXODI.COM in the correct sequence.14: The loaded LSL is too old. LSL.COM must be 1.20 or higher.IPXODIExplanation: You attempted to use IPXODI.COM with a version of LSL.COM that is older than 1.20.Action: Replace your Link Support Layer (LSL) with LSL.COM v1.20 or later.15: Cannot find an IPX protocol to unload.IPXODIExplanation: You attempted to remove (unload) IPXODI from memory, but IPXODI could not be located in memory.Action: None. This message is for information only.16: Cannot unload IPXODI because another program has been loaded above it. Unload the other program or programs and try again.IPXODIExplanation: An attempt to unload IPXODI from memory was made, and IPXODI detected that another program was loaded above it. Unloading IPXODI when other programs are loaded above it can produce a variety of undesirable consequences.Action: Unload TSR (terminate-and-stay-resident) programs that were loaded after IPXODI.COM; then unload IPXODI.COM, or use the /F (force) command line option instead of the /U option to remove IPXODI.PAGENUM=362 ID="BP356"17: IPXODI cannot be unloaded because the installed IPXODI is a different version than this IPXODI module.IPXODIExplanation: You attempted to unload a resident IPXODI from memory using an IPXODI.COM file that is not the same version as the resident IPXODI.COM.Action: Use the same IPXODI.COM version that was used to load IPXODI.18: IPXODI cannot be unloaded because interrupt hex_number is owned by another program. Unload the other program; then unload IPXODI.IPXODIExplanation: You attempted to unload IPXODI from memory while one of the interrupt vectors used by IPXODI was being used by another program. The hex number specifies which interrupt vector another program was using. Possible values are 64, 7A, and 2F.Action: Unload the TSR (terminate-and-stay-resident) program that has used the interrupt; then unload IPXODI.19: A network adapter driver must be loaded before IPXODI.COM can be loaded.IPXODIExplanation: You attempted to load IPXODI.COM before loading a LAN driver.Action: Load a LAN driver; then load IPXODI.COM.20: IPX could not find a board to bind to. Please specify a board in the NET.CFG file by adding a `BIND' entry to the `PROTOCOL IPX' section; then specify which protocol ID IPX should use for that board by adding a `PROTOCOL IPX id frametype' entry to the board's `LINK DRIVER' section.IPXODIExplanation: You attempted to load IPXODI.COM, but IPXODI could not locate a network board that corresponds to an IPX protocol ID.Action: Enter BIND #n (where n is a network board number) under IPX's section heading in the NET.CFG file; then try loading IPXODI again. For more information on the BIND #n keyword, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.21: IPX cannot bind to board number because an IPX protocol ID for the type frame type has not been registered with the LSL. Please register an ID by adding a `PROTOCOL IPX id number' entry to the `LINK DRIVER name' NET.CFG section, replacing `id' with the appropriate protocol ID for IPX to use on this frame type. For the new ID to be recognized the number LAN Driver must be reloaded.IPXODIExplanation: You attempted to load IPXODI.COM and to have it bind to a particular network board, but an IPX protocol ID is not known for that network board.Action: Enter a PROTOCOL IPX n frame_typePAGENUM=363 ID="BP357" entry into the NET.CFG file under the section header for the LAN driver to which IPX is binding. For more information on how to register a protocol ID, see "BOOK="ws_d2enu" COLLECTION="nw41"IPXODI Protocol" in NetWare Client for DOS and MS Windows Technical Reference.23: Maximum number of stacks already loaded. Either unload an existing stack or increase the maximum by adding a `MAX STACKS' entry to the `LINK SUPPORT' section in the NET.CFG file.IPXODIExplanation: You attempted to load the IPXODI.COM file, but IPXODI determined that the LSL.COM did not have any internal room to register the IPXODI protocol stack.Action: Increase the maximum number of stack resources. For more information, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.24: Attempt to register an IPX Protocol ID failed. Increase the maximum number of stacks in the LSL.COM by adding a `MAX STACKS' entry to the `LINK SUPPORT' section in the NET.CFG file.IPXODIExplanation: IPXODI.COM could not register a protocol ID with the Link Support Layer (LSL) because the LSL did not have any more room for another protocol ID.Action: Increase the maximum number of stack resources. For more information, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.25: An IPX protocol stack is already registered with the LSL.IPXODIExplanation: You attempted to load the IPXODI.COM file, but IPXODI determined that an IPX protocol stack is already registered with the Link Support Layer (LSL).Action: None. This message is for information only.26: Invalid command line option was specified: invalid_entry.IPXODIExplanation: You specified an invalid command line option when trying to load the IPXODI.COM file.Action: Correct the option and try again. For more information about the IPXODI.COM file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.PAGENUM=364 ID="BP358"27: Missing or invalid value for parameter on line number of the configuration file. Entry was ignored.IPXODIExplanation: IPXODI.COM encountered an invalid value for one of its parameters in the NET.CFG file.Action: Correct the value. For information on the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.28: Missing or invalid ON/OFF value for parameter on line number of the configuration file. Entry was ignored.IPXODIExplanation: IPXODI.COM encountered an invalid value for one of its configuration file parameters (for example, token, keyword). The only valid values for the parameter are "ON" or "OFF."Action: Either specify "ON" or "OFF" in the entry.29: Missing or invalid IPATCH values on line number of the configuration file. Entry was ignored.IPXODIExplanation: IPXODI.COM encountered an invalid value for the "IPATCH" parameter in the network configuration file.Action: Correct the values. For information on the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.30: Specified board in `BIND' statement on line number of the configuration file does not exist. Entry was ignored.IPXODIExplanation: IPXODI.COM encountered a BIND parameter in the NET.CFG file with a network board number that does not exist.Action: Specify a network board number that exists. For information on the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.31: Invalid `BIND' statement on line number of the configuration file. Requires a board number (Example, BIND 2). Entry was ignored.IPXODIExplanation: IPXODI.COM encountered a BIND parameter with an invalid network board number in the NET.CFG file.Action: Specify a network board number after the BIND keyword. For information on the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.PAGENUM=365 ID="BP359"32: Duplicate `BIND' statement on line number of the configuration file. IPXODI cannot be bound to more than one board. Entry was ignored.IPXODIExplanation: IPXODI.COM encountered a BIND parameter in the NET.CFG file after it had already processed a previous BIND parameter.Action: Specify only one BIND keyword under IPX's NET.CFG section header. For information on the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.33: An invalid entry was found on line number of the configuration file. Entry invalid_entry ignored.IPXODIExplanation: IPXODI.COM encountered an invalid parameter under its main section heading (for example, PROTOCOL IPX) in the NET.CFG file.Action: Remove the entry. For information on the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.PAGENUM=366 ID="BP360"IPXRTR1: Compression memory or ECB resource tag allocation failed. IPXRTRExplanation: The resource tag for the Memory/ECBs used by the compression modules failed allocation. This is due to lack of resources in the system.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.2: RIP router configuration error detected. Node name claims network address address should be address.IPXRTRExplanation: A RIP packet was received indicating that the network numbers on the workstation and the server or router do not agree. This is a configuration error.Action: Change the network number on either the local system or the remote system so that all servers and routers on the media use the same network number.4: SAP router configuration error detected. Node name claims network address address should be address. IPXRTRExplanation: A SAP packet was received indicating that one of the servers or routers specified in the message does not agree with the local computer about the network number for the connecting circuit. This is a configuration error.Action: Change the network number on either the local system or the remote system so that all servers and routers on the media use the same network number.8: Unable to bind to board name. Memory allocation failed. IPXRTRExplanation: The bind IPX command to the specified board has failed because the system does not have adequate resources to complete the bind. This is caused by allocation failures while trying to allocate memory to handle the bind process. Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network10: Unable to bind to board name. Unable to allocate circuit information.IPXRTRExplanation: IPX was not bound to the specified board due to a lack of resources in the local system, and the circuit allocation failed. This could mean that the system under the current configuration has used up all available resources.Action: Add more memory to the system or change the configuration.PAGENUM=367 ID="BP361"12: Unable to initialize I/O process. IPXRTRExplanation: The IPXRTR I/O process failed during initialization, and IPXRTR cannot  load. This could be due to a lack of resources in the system. Action: Add more memory to the system.13: Unable to register with ICM_SPX module. IPXRTRExplanation: IPXRTR could not be loaded because the registration with the ICM_SPX module failed.Action: Check ICM-SPX error message for details.16: Version number, rev number, of ICM_SPX is required.IPXRTRExplanation:  IPXRTR requires the specified version of ICM_SPX to run. Action: Load the specified version of ICM_SPX.18: Out of number NLSP packets received in the last number seconds, number have been discarded.IPXRTRExplanation: NLSP packets have been dropped because more NLSP packets were received than the number that can be queued. The queue limit for NLSP packets depends on the number of Receive ECBs in the system. The queue limit is set to prevent NLSP packets from using up all the Receive ECBs in the system, thereby preventing other packets from being received. The system recovers from this condition automatically. Action: If this condition occurs frequently, the local system must be configured with a greater number of Receive ECBs. This can be done on the command line by using the SET command for Maximum Packet Receive Buffers and increasing the value. Also, include the SET command in the AUTOEXEC.NCF file to set this parameter each time the system is restarted. See "BOOK="superenu" COLLECTION="nw41"Resolving Event Control Block Allocation Errors" in Supervising the Network.19: Out of number RIP packets received in the last number seconds, number have been discarded.IPXRTRExplanation: RIP packets have been dropped because more RIP packets were received than the number that can be queued. The queue limit for RIP packets depends on the number of Receive ECBs in the system. The queue limit is set to prevent RIP packets from using up all the Receive ECBs, thereby preventing other packets from being received. The system recovers from this condition automatically. Action: If this condition occurs frequently, set the Maximum Packet Receive Buffers to a larger value. Also, include the SET command in the AUTOEXEC.NCF file to set this parameter each time the system is restarted.PAGENUM=368 ID="BP362"20: IPXRTR: Unable to register lower layers debug input screen.IPXRTRExplanation: The debug screen for the lower layers could not be registered.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.21: IPXRTR: Unable to open lower layers debug screen.IPXRTRExplanation: The debug screen for the lower layers could not be opened for displaying the debug messages when the lower layers debug screen is turned on.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.23: Unable to deregister IPXRTR lower layers debug screen.IPXRTRExplanation: The debug screen for the lower layers could not be deregistered.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.24: Debug screen resource tag allocation failed. IPXRTRExplanation: The resource tag could not be allocated for the lower layers debug screen. This is due to lack of resources on the server.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.25: Debug input screen resource tag allocation failed. IPXRTRExplanation: The resource tag could not be allocated for the lower layers debug input screen. This condition is due to a lack of resources on the server.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.26: Out of number SAP packets received in the last number seconds, number have been discarded.IPXRTRExplanation: SAP packets have been dropped because more SAP packets were received than the number that can be queued. The queue limit for SAP packets depends on the number of Receive ECBs in the system. The queue limit is set to prevent SAP packets from using up all the Receive ECBs, thereby preventing other packets from being received. The system recovers from this condition automatically.Action: If this condition occurs frequently, set the Maximum Packet Receive Buffers to a larger value. Also, include the SET command in the AUTOEXEC.NCF file to set this parameter when the system is restarted.PAGENUM=369 ID="BP363"28: Attempt to add route with network number number was ignored. Network numbers of 00000000 and FFFFFFFF are not valid.IPXRTRExplanation: An attempt to initialize a route with network number zero was ignored. This conditions sometimes occurs when a bad static route is specified.Action: Check the static route configuration.32: Failed to unbind duplicate LAN board name. IPXRTRExplanation: While unloading IPXRTR, an attempt to unbind from a duplicate network boards failed (if you have IPX bound to more than one network board on the same network). This is a warning message indicating that the internal router cannot handle multiple binds to the same LAN.Action: Make sure IPXRTR is loaded to support multiple boards.38: Operating system interface error. Use released version of NetWare 4. IPXRTRExplanation: IPXRTR could not operate as a loadable router with the NetWare operating system version on the server.Action: Upgrade the server to a released version of the NetWare 4 operating system.39: Configuration memory resource tag allocation failed. IPXRTRExplanation: The resource tag could not be allocated for the memory used by the configuration. This is due to a lack of resources in the local system.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.40: General short term memory resource tag failed. IPXRTRExplanation: The resource tag could not be allocated for general short-term memory allocations used by IPXRTR. The local system does not have the resources to run IPXRTR.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.41: Error in configuration file.IPXRTRExplanation: The NLSP.CFG file has an error or is corrupted. IPXRTR failed while parsing the file.Action: Delete the NLSP.CFG file and redo the configuration using the INETCFG utility. This file should never be edited manually; manual editing could lead to file corruption. For information on INETCFG, see "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference.PAGENUM=370 ID="BP364"42: An invalid parameter was specified on the load line for IPXRTR.IPXRTRExplanation: The command line for loading IPXRTR has an invalid parameter.Action: Check the syntax of the IPXRTR LOAD command. For the correct syntax, see 
BOOK="ipxrtenu" COLLECTION="nw41"NetWare IPX Router Reference for the correct syntax.44: Insufficient memory to synchronize LSP database. Entering LSP overload state. An attempt will be made to exit the overload state automatically. IPXRTRExplanation: The system does not have the resources to synchronize the LSP database. This condition is caused when memory could not be allocated to handle a valid LSP, or to create or regenerate a local LSP. IPXRTR enters the overload state and sets a timer to make an attempt to exit overload if no more allocation failures happen for the overload time interval. The local system also indicates to other routers that the system is in overload and should be used to route through, although access to the local system is available through network management. The system remains in overload; this means that the system requires more memory to operate under the current configuration.Action: IPXRTR tries to overcome this situation automatically. If the error consistently remains overloaded, see "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.45: Out of memory condition has not occurred for Maximum Overload Timeout period. Exiting LSP overload state. IPXRTRExplanation: An out-of-memory condition has not been experienced by an overloaded router for the overload interval. The router tries to exit overload and synchronize its LSP database. It also resets the overload flag in the LSP.Action: None. This message is for information only.46: Memory is still not available to synchronize the LSP database. Remaining in LSP overload state. IPXRTRExplanation: The overloaded system has experienced an out-of-memory condition within less than the overload interval since the last out-of-memory condition. The local system resets its timer to exit overload. Action: None. This message is for information only. The system remains in overload for the overload interval if no other out-of-memory condition occurs during that interval.PAGENUM=371 ID="BP365"47: The local area contains more than three configured area addresses. Dropping the locally configured system area: number with area mask: number. IPXRTRExplanation: The local area of which the system is a part has more than the maximum of three area addresses describing it. The local area is now defined as only the three lowest area addresses configured in all the systems in the area. This is a configuration error.Action: This condition can be resolved by reconfiguring the area addresses for the local system. It might require reconfiguring a network number to conform to the newly defined area addresses.58: Error getting AES resource tag for IPXRTR Forwarding Cache Manager. IPXRTRExplanation: The resource tag for the AES process that dynamically adjusts the forwarding cache table size could not be allocated. This is due to a lack of resources in the NetWare operating system.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.69: Timer Process resource tag allocation failed. IPXRTRExplanation: The resource tag allocation for the timer process failed. This is due to a lack of resources in the NetWare operating system.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.75: Cannot find pointer to reply to get nearest server. IPXRTRExplanation: The pointer to the Reply To Get Nearest Server argument (ON or OFF) SET parameter could not be found. This might be due to an error in the version of the NetWare operating system running. The version of the NetWare operating system currently running on your system might be an unreleased version.Action: Contact your Novell Authorized Reseller.76: Cache memory resource tag allocation failed. IPXRTRExplanation: The resource tag could not be allocated for cache memory allocations. This is due to lack of resources in the NetWare operating system.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.90: Attempt to add static route with network number number was ignored because the hop count was incorrectly configured with a zero value.IPXRTRExplanation: An attempt was made to add a static route with a zero hop count. Action: Check the static route configuration.PAGENUM=372 ID="BP366"91: Attempt to add static route with network number number was ignored because the time to reach the network was incorrectly configured with zero.IPXRTRExplanation: An attempt was made to add a static route with a zero time to the network number.Action: Check the static route configuration.124: Incoming call rejected because of insufficient memory in the local system.IPXRTRExplanation: The incoming call was rejected due to a lack of resources in the local system.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.127: Alloc Memory resource tag allocation failed.IPXRTRExplanation:  The resource tag for alloc (allocation) memory could not be allocated. This could be due to lack of resources in the local system.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.137: Unable to operate on this version of NetWare. IPXRTRExplanation: IPXRTR cannot run on the version of the NetWare operating system you are running. This could mean that the version of NetWare currently running on your system is an unreleased version.Action: Contact your Novell Authorized Reseller.146: Unable to register pause routine.IPXRTRExplanation: Unable to register the pause routine for the RIP or SAP tracking screens. Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. Also, check the operating system error message for details.147: Unable to deregister pause routine. IPXRTRExplanation: Unable to deregister the pause routine for the RIP or SAP tracking screens. Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. Also, check the operating system error message for details.PAGENUM=373 ID="BP367"152: Packet ignored because of an invalid packet length. IPXRTRExplanation: This message is displayed on the RIP tracking screen when a RIP packet is received with no valid routes in the packet. This means that there exists a router in the local connected network that is not sending correct RIP packets.Action: Determine which router is sending the incorrect RIP packets and correct the problem.159: Required network number is missing. IPXRTRExplanation: The network number was not specified in the BIND command. Binding IPX to a board requires a network number.Action: Specify a network number using the INETCFG utility. For more information about the BIND #n keyword, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference. For information on INETCFG, see "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference.161: Bind failed because network address address is already used as an internal network address. IPXRTRExplanation: The BIND command was issued to bind IPX to a board having an external network number the same as the internal network number.Action: Change the BIND command using the INETCFG utility. For more information about the BIND #n keyword, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference. For information on INETCFG, see "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference.162: Bind failed because network address address is already used by a remote server name. IPXRTRExplanation: The BIND command was issued with a network number that is in use by a remote system to which the local system is connected. This is a configuration error.Action:  Use the INETCFG utility to change the network address used for the bind process. For more information about the BIND #n keyword, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference. For information on INETCFG, see "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference.163: Bind failed because network address address is already used for another board. IPXRTRExplanation: The BIND command was issued to a board having a network number the same as the network number for another board on which IPX is already bound. This is a configuration error. Action: Use the INETCFG utility to change the network address. For information on INETCFG, see "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference.PAGENUM=374 ID="BP368"165: Network address not within configured level 1 address range.IPXRTRExplanation: The network address is not within the range of valid network addresses that can be configured using the area addresses for the current local area.Action: Change the network address to an address within the valid network addresses range for the local area.166: Unable to bind LAN board name to IPX using network address address. IPXRTRExplanation: The IPX bind to the specified network board could not be completed because the network address for the bind process is not within the range of valid network addresses that can be configured using the area addresses for the current local area.Action: Change the network address to an address within the valid network addresses range for the local area.167: Fatal Error: Attempt to add a timer that already exists. Restart router/server. IPXRTRExplanation: An active timer is being added to the timer queue without deleting the existing timer. This is a fatal error.Action: Restart the server.170: name packet received on circuit name from name with network address address is truncated.IPXRTRExplanation: A truncated NLSP packet was received containing only a portion of the information sent. This could be caused by a hardware error or a misbehaving system.Action: Check your hardware and system.171: Name packet received on circuit name from name with network address address has a bad packet type name.IPXRTRExplanation: This message could indicate one of the following conditions:MARK=BULLETNLSP packet that was received had an unknown packet typeThe packet was received for one of the known packet types but was from a system that was not a Level 1 router; this is indicated by the "Router Type" field in the LSP (Link State Packet) header.Action: Check the NLSP routers on locally connected network.PAGENUM=375 ID="BP369"173: Name packet received on circuit name from name with network address address has a bad header length number.IPXRTRExplanation: This message is displayed for all NLSP packets. The packet received had a bad length field in the LSP header for the specified packet type.Action: Correct the length field in the NLSP header. 174: Mismatched version number number in name packet received on circuit name from name with network address address.IPXRTRExplanation: The NLSP received had a value for the major version number not equal to 1.Action: Check the NLSP routers on locally connected network. 175: Router name on circuit name claims network name should be name.IPXRTRExplanation: The local system disagrees with a neighboring system about the IPX network number assigned to the circuit. This is a configuration error.Action: Change the network number for the circuit in the BIND command for the circuit on the local system or the neighboring system to make all the systems on the circuit agree on the network number for the circuit. For more information on the BIND #n keyword, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.176: Name packet received on circuit name from name with network address address has a malformed option code number.IPXRTRExplanation: The syntax check on the received LSP  failed. This could be, for example, an LSP with the length field for the link option not equal to the valid link option length.Action: Correct the length field in the NLSP header.177: LSP received on circuit name from name with network address address has a bad checksum.IPXRTRExplanation: The LSP received on the specified circuit has a bad checksum. This could be due to packet corruption in the media connecting the system that sent the LSP to the local system. It could also be that the LSP was corrupted in the memory of the system that sent this LSP. The error could also be in the ODI drivers, which could have caused the corruption. This could also be a bug in the checksum calculation routine, either in the local system or in the system that sent this LSP.Action: Check your hardware and system.PAGENUM=376 ID="BP370"178: Bad checksum detected on stored LSP from system name length number. There has been a memory corruption or software error.IPXRTRExplanation: The LSP specified has been corrupted in the local system's memory. This means that the LSP database was overwritten accidentally by some process in the local system (possibly a misbehaving application). The system tries to recover from it by flushing its database and its routing tables.Action: None. This message is for information only. IPXRTR tries to recover automatically.180: LSP/graph inconsistency detected in stored LSP from system name length number. There has been a memory corruption or software error.IPXRTRExplanation: The graph that is built reflecting the network, as described by the LSPs in the link state database, is inconsistent. This could mean that Links, External Routes, Services, or Management Information in the LSP have not been reflected in the graph correctly. The system tries to recover from it automatically by resetting the router. This condition could occur due to accidental memory overwrites.Action: None. This message is for information only. IPXRTR tries to recover automatically.181: Router name has the same internal network address of address but a System ID of number.IPXRTRExplanation: The router specified has a duplicate internal network number and a different system ID, compared with the local system's internal network number. This means that there is a configuration error, and the local system and the router specified have the same IPX internal network number. Action: Change the IPX internal network number on one of the systems.182: Router name has an internal network address of address but the same System ID of number.IPXRTRExplanation: The router specified and the local system have the same system ID but different internal network numbers. This is a configuration error.Action: Use the INETCFG utility to change the system ID on one of the systems. For information on INETCFG, see "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference. 183: Missing option in name packet received on circuit name from name with network address address code number.IPXRTRExplanation: The NLSP packet failed the syntax check and a mandatory option (for example, Local MTU in Hello packets) was absent.Action: Check for a misbehaving NLSP router on the network.PAGENUM=377 ID="BP371"184: A mismatched source node/data-link address address/address in name packet received on circuit name from name.IPXRTRExplanation: The source node address in the IPX header does not match the source node address in the data-link header for the NLSP packet received. This could be because the NLSP packet was forwarded by a system on the circuit specified with the data-link address specified in the message.Action: Check for a misbehaving NLSP router on the network.185: Too many NLSP neighbors on circuit name. The maximum allowed for a packet size of number is number.IPXRTRExplanation: Too many routers are attached to the same circuit. The number of routers that can be attached to a circuit is determined by the MTU size of the circuit media, because Hellos cannot include all the neighbors on the circuit if the number of neighbors exceeds the value specified in the message.Action: Split the LAN into two or more LAN segments and add router between the LAN segments, or change to media with a larger MTU.187: The link between routers name and name has a zero throughput. A default of 10 MB will be used for the link throughput.IPXRTRExplanation: The LSPs of two systems reporting a link between them have specified a throughput of zero for the link. This is an invalid throughput value; the system will use a default value for the throughput of the link (10 Mbps for Ethernet media).Action: None. This message is for information only.194: System name has the same name, internal network address of address and System ID of number as the local system.IPXRTRExplanation: The router specified has the same name, IPX internal network address, and system ID as the local system, and is a duplicate of the local system. This is a configuration error.Action: Use the INETCFG utility to change the name, IPX internal network address, and system ID. For information on INETCFG, see "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference.PAGENUM=378 ID="BP372"IPXRTRNM1: Resource tag allocation failed.IPXRTRNMExplanation: The resource tag could not be allocated because of a lack of memory on the server.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.3: Unable to allocate AES Process resource tag. IPXRTRNMExplanation: The resource tag used for the Asynchronous Event Scheduler (AES) process could not be allocated because of a lack of memory on the server.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.4: Unable to register IPXRTRNM with the SNMP agent. IPXRTRNMExplanation: The network management instrumentation could not register with the SNMP agent.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.PAGENUM=379 ID="BP373"IPXS1: IPX STREAM module still in use, unloading will have unknown consequences.IPXSExplanation: The IPXS.NLM is currently being referenced by another NLM or NetWare driver. Unloading the module while it is being used may produce unwanted results.Action: Wait until the module is not being used; then retry the unload.4: Unable to register module_name device with STREAMS.IPXSExplanation: IPXS was unable to register the device with Streams.Action: If available, see your NetWare Streams developer's documentation. Otherwise, contact your Novell Authorized Reseller or application developer.9: Unable to open IPX configuration file "name". Trying default file "name".IPXSExplanation: The specified IPX configuration file could not be opened. The default configuration file will be used.Action: None if the default file is opened successfully.10: Error number was returned while trying to open "filename"; unable to configure RIP, SAP or IPX.IPXSExplanation: The error specified was returned when IPXS attempted to open the file containing the RIP, SAP, or IPX configuration information. Configuration of RIP, SAP, or IPX was not accomplished.Action: If the problem persists, contact your Novell Authorized Reseller.12: Unable to configure IPX for number open IPX sockets, IPXS not loaded.IPXSExplanation: The "ipx_init" function was unable to configure IPX for the indicated number of IPX open sockets.Action: Try the operation again. If the problem persists, contact your Novell Authorized Reseller.13: Unable to configure IPXS for number open IPX sockets, IPXS not loaded.IPXSExplanation: The "ipx_init" function was unable to configure IPX for the indicated number of IPX open sockets.Action: Try the operation again. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=380 ID="BP374"14: Invalid format in file "name"; unable to configure RIP, SAP or IPX.IPXSExplanation: IPXS cannot configure RIP, SAP, or IPX due to an incorrect configuration file format. This error could be caused by a corrupted configuration file.Action: Run SERVMAN to regenerate the file. See "BOOK="utlrfenu" COLLECTION="nw41"SERVMAN" in Utilities Reference.15: Invalid format in file "name"; unable to configure IPX.IPXSExplanation: IPXS cannot configure IPX due to an incorrect configuration file format. This error could be caused by a corrupted configuration file.Action: Run SERVMAN to regenerate the file. See "BOOK="utlrfenu" COLLECTION="nw41"SERVMAN" in Utilities Reference.16: Error number was returned while trying to open "name"; unable to load SAP restrictions.IPXSExplanation: The specified error was returned while IPXS attempted to open the configuration file containing the SAP restriction information.Action: Try the operation again. If the problem persists, contact your Novell Authorized Reseller.17: Bad record format; unable to complete loading SAP restrictions.IPXSExplanation: IPXS cannot configure SAP due to an incorrect record format. This error could be caused by a corrupted configuration file.Action: Run SERVMAN to regenerate the file. See "BOOK="utlrfenu" COLLECTION="nw41"SERVMAN" in Utilities Reference.18: Invalid format in file "name"; unable to configure RIP and SAP.IPXSExplanation: IPXS cannot configure RIP and SAP due to an incorrect configuration file format. This error could be caused by a corrupted configuration file.Action: Run SERVMAN to regenerate the file. See "BOOK="utlrfenu" COLLECTION="nw41"SERVMAN" in Utilities Reference.19: Bad record format; unable to complete loading IPX configuration.IPXSExplanation: IPXS cannot configure IPX due to an incorrect configuration file format. This error could be caused by a corrupted configuration file.Action: Run SERVMAN to regenerate the file. See "BOOK="utlrfenu" COLLECTION="nw41"SERVMAN" in Utilities Reference.20: Bad record value; unable to complete loading IPX configuration.IPXSExplanation: IPXS cannot configure IPX due to an incorrect configuration file format. This error could be caused by a corrupted configuration file.Action: Run SERVMAN to regenerate the file. See "BOOK="utlrfenu" COLLECTION="nw41"SERVMAN" in Utilities Reference.PAGENUM=381 ID="BP375"22: Unable to open default IPX configuration file "name". Using internal defaults.IPXSExplanation: The specified IPX configuration file could not be opened. The default configuration file will be used.Action: None if the default file is opened successfully.23: Bad record format; unable to complete loading RIP/SAP configuration.IPXSExplanation: IPXS cannot configure RIP and SAP due to an incorrect configuration file format. This error could be caused by a corrupted configuration file.Action: Run SERVMAN to regenerate the file. See "BOOK="utlrfenu" COLLECTION="nw41"SERVMAN" in Utilities Reference.PAGENUM=382 ID="BP376"ISADISK005: An invalid I/O parameter was selected.ISADISKExplanation: Either the port or the interrupt selected was invalid.Action: Reload the driver and enter the correct port and interrupt.010: A secondary controller is not allowed with redirected drive tables. ISADISKExplanation: Controllers with drive tables that are mapped into a nonstandard part of the computer's memory cannot be used as secondary controllers.Warning: When using the "LOAD ISADISK /l" option, Novell cannot guarantee that the drive will be set up correctly if this type of controller drive table mapping is used.Action: Novell has provided a command line option, "LOAD ISADISK /l," that doesn't set any memory limitations in regard to where the controller may map its drive tables. Use the "LOAD ISADISK /l" option with caution.015: CMOS has not been set. Run SETUP.ISADISKExplanation: The drive types in the CMOS have not been set up.Action: Run "System Setup" and set up the drive types.020: ISA controller could not be added due to insufficient memory. ISADISKExplanation: This computer currently does not have enough memory available to load this driver.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. Try loading the driver again.025: The selected hardware is not available for this ISA driver. ISADISKExplanation: The driver looked for the hardware ports specified when the driver was loaded, and it was not able to find hardware at the specified port locations.Action: Reload the driver and give the correct port for the controller.030: An unexpected problem prevented allocation of memory for ISA driver. ISADISKExplanation: This computer currently does not have enough memory available to load this driver.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. Try loading the driver again.PAGENUM=383 ID="BP377"040: A bad request was received from GetRequest.ISADISKExplanation: An internal Media Manager system error has occurred.Action: Restart the server. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=384 ID="BP378"LANSUP-DOS001: The LSL is not loaded.LANSUP-DOSExplanation: The computer must load the Link Support Layer (LSL) before loading the driver.Action: Load the LSL; then load the driver, as in the following example:FORMAT="LINESPECIFIC"MOREINFO="NONE"C:\NWCLIENT\LSL MOREINFO="NONE"<Enter> 
C:\NWCLIENT\LANSUP MOREINFO="NONE"<Enter> 002: The LSL has no room for a board using frame type.LANSUP-DOSExplanation: The Link Support Layer (LSL) is configured with resources for a set number of network boards. (The default is 4.) This number has been exceeded.Action: Edit the NET.CFG file, and add the MAX BOARDS keyword to reflect the number of network boards to be loaded, as in the following example:FORMAT="LINESPECIFIC"MOREINFO="NONE"LINK SUPPORT 
   MAX BOARDS 6 Unload the driver; then reload it as in the following example:FORMAT="LINESPECIFIC"MOREINFO="NONE"C:\NWCLIENT\LANSUP /u MOREINFO="NONE"<Enter> 
C:\NWCLIENT\LANSUP MOREINFO="NONE"<Enter> 003: Could not find LANSUP MLID to unload. LANSUP-DOSExplanation: The LANSUP driver is not loaded. Action: None. This message is for information only. 004: A TSR is loaded above the LANSUP MLID.LANSUP-DOSExplanation: Another TSR (terminate-and-stay-resident) program was loaded after the LANSUP driver.Action: The drivers must be unloaded in reverse order, as follows:FORMAT="LINESPECIFIC"MOREINFO="NONE"C:\NWCLIENT\NETX /u MOREINFO="NONE"<Enter> 
C:\NWCLIENT\IPXODI /u MOREINFO="NONE"<Enter> 
C:\NWCLIENT\LANSUP /u MOREINFO="NONE"<Enter> 
PAGENUM=385 ID="BP379"Unload the TSRs; then try to unload the LANSUP driver. You can force the LANSUP driver to unload from the command line by using the "/F" switch after the driver name, as follows:FORMAT="LINESPECIFIC"MOREINFO="NONE"C:\NWCLIENT\LANSUP /f MOREINFO="NONE"<Enter> Use caution when using the "/F" switch because it could cause the system to hang.005: LANSUP MLID could not be unloaded; the operation was aborted.LANSUP-DOSExplanation: The LANSUP driver could not be shut down and unregistered; consequently, it cannot be unloaded.Action: To unload the driver, reboot the system.006: The adapter did not initialize. LANSUP did not load.LANSUP-DOSExplanation: The LANSUP driver encountered an error while loading.Action: Corrective action can vary. See the preceding driver-specific message on the screen for specific information about the error that occurred.007: You need another MLID Section Heading in the NET.CFG file in order to load the MLID again. LANSUP-DOSExplanation: The NET.CFG file does not have an individual entry for each driver that is intended to be loaded.  This means that one of the drivers is not loaded into memory.Action: Unload the LANSUP driver. Modify the NET.CFG file to contain a unique entry for each driver to be loaded. This requires an individual Link Driver heading in the NET.CFG file for each driver or each instance of the same driver. Reload the driver. For information on the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.008: A NET.CFG is required to load the MLID again.LANSUP-DOSExplanation: The NET.CFG file does not have an individual entry for each driver that is intended to be loaded.  This means that one of the drivers is not loaded into memory.Action: Unload the LANSUP driver. Modify the NET.CFG file to contain a unique entry for each driver to be loaded. This requires an individual Link Driver heading in the NET.CFG file for each driver or each instance of the same driver. Reload the driver. For information on the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.PAGENUM=386 ID="BP380"009: The NET.CFG entry has been ignored.LANSUP-DOSExplanation: The NET.CFG file does not have an individual entry for each driver that is intended to be loaded.  This means that one of the drivers is not loaded into memory..Action: Unload the LANSUP driver. Modify the NET.CFG file to contain a unique entry for each driver to be loaded. This requires an individual Link Driver heading in the NET.CFG file for each driver or each instance of the same driver. Load the drivers again. For information on the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.011: The MLID does not support frame type. The protocol keyword has been ignored.LANSUP-DOSExplanation: An unsupported or incorrectly typed frame type has been specified with the protocol keyword.Action: Verify that the frame type assigned in the NET.CFG file under the protocol keyword is valid. For a list of valid frame types, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.012: The protocol keyword must have a frame type. Entry ignored.LANSUP-DOSExplanation: The PROTOCOL keyword entry is incomplete.Action: Correct the protocol entry in the NET.CFG file. The proper syntax for the protocol keyword is as follows:FORMAT="LINESPECIFIC"MOREINFO="NONE"PROTOCOL LANSUP hex_protocol_ID frame_type For information regarding the PROTOCOL keyword, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.013: The MLID could not register Protocol ID number for protocol stack name for frame type frame.LANSUP-DOSExplanation: The Link Support Layer (LSL) is configured with resources for a set number of Protocol Identifiers. (The default is 4.) This number has been exceeded.Action: Edit the NET.CFG file, and add the MAX STACKS keyword to reflect the number of network boards to be loaded, as in the following example:FORMAT="LINESPECIFIC"MOREINFO="NONE"LINK SUPPORT 
   MAX STACKS 6 Unload the driver; then reload it as in the following example:FORMAT="LINESPECIFIC"MOREINFO="NONE"C:\NWCLIENT\LANSUP /u MOREINFO="NONE"<Enter> 
C:\NWCLIENT\LSL /u MOREINFO="NONE"<Enter> 
PAGENUM=387 ID="BP381"C:\NWCLIENT\LSL MOREINFO="NONE"<Enter> 
C:\NWCLIENT\LANSUPMOREINFO="NONE" <Enter> 014: This version of the LSL is not supported.LANSUP-DOSExplanation: The driver the computer is using supports only Link Support Layer (LSL) versions later than 1.0.Action: Unload the LSL and replace it with a newer version.015: The frame type is already active for frame type.LANSUP-DOSExplanation: The frame type is already loaded, and it cannot be loaded repeatedly.Action: Edit the NET.CFG file to load the frame type only once for a given network board. For information regarding frame types, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.016: The node address was incorrectly specified in the NET.CFG file.LANSUP-DOSExplanation: The node address override in the NET.CFG file is too long.Action: Edit the NET.CFG file and correct the node address. The node address must be less than or equal to 12 hex digits. For information regarding node address override, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.017: An invalid keyword was specified in NET.CFG on line number.LANSUP-DOSExplanation: The key word on the line indicated was not recognized.Action: Edit the NET.CFG file and correct the spelling of the keyword. For valid keywords, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.018: The frame type specified in the NET.CFG is not supported.LANSUP-DOSExplanation: The frame type specified with the FRAME keyword is not supported by the driver.Action: Edit the NET.CFG file and fix frame type. For information on supported frame types, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.PAGENUM=388 ID="BP382"019: An invalid LANSUP node address is specified in NET.CFG. The MLID modified the incorrect address bits.LANSUP-DOSExplanation: The node address specified in the NET.CFG file has set reserved bits.Action: Edit the NET.CFG file and correct the node address. For information regarding node addresses, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.050: [ISA bus | Microchannel] The board cannot be found.LANSUP-DOSExplanation: If the computer is using an ISA bus network board, the network board was not found due to one or more of the following conditions: MARK=BULLETThe network board is not present in the computer. The network board settings are not the defaults, and they are not defined in the NET.CFG file.Another network board is using the same hardware settings as this network board.The network board is does not work.Action: Do one or more of the following:MARK=BULLETMake sure the network board is properly seated into the slot. If the jumper settings are not the defaults, make sure that they match the settings in the NET.CFG file. If the computer is not using the NET.CFG file, make sure the jumper settings are set to the defaults. If other network boards are using the same hardware settings, change the settings and try to reload the driver.Replace the network board with one that you know works.Explanation: If the computer is using a microchannel network board, the network board is not in the computer, or the network board's configuration could not be obtained.Action: Do one of the following:MARK=BULLETMake sure that the network board is properly seated into a slot.Insert the network board into a slot, and run the CLASS=DISKReference diskette to install it.PAGENUM=389 ID="BP383"051: Board RAM failed the memory test.LANSUP-DOSExplanation: The memory test on the network board's internal static RAM failed.Action: Check the network board and other hardware. If necessary, replace the network board.PAGENUM=390 ID="BP384"LANSUP-OS2001: The LSL is not loaded.LANSUP-OS2Explanation: The Link Support Layer (LSL) module must be loaded before the computer can install the driver.Action: Edit the CONFIG.SYS file to load the LSL before the LAN driver, as in the following example:FORMAT="LINESPECIFIC"MOREINFO="NONE"DEVICE=C:\NETWARE\LSL.SYS 
DEVICE=C:\NETWARE\LANSUP.SYS 021: Could not add MLID Protocol ID.LANSUP-OS2Explanation: The Link Support Layer (LSL) is configured with resources for four Protocol Identifiers. This number has been exceeded.Action: None. This message is for information only.022: Could not allocate memory. Virtual board did not load.LANSUP-OS2Explanation: The computer cannot allocate enough memory to load another network board.Action: Increase the available memory. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.050: [ISA bus| Microchannel] The board cannot be found.LANSUP-OS2Explanation: If the computer is using an ISA bus network board, the network board was not found due to one or more of the following conditions: MARK=BULLETThe network board is not present in the computer. The network board settings are not the defaults, and they are not defined in the NET.CFG file.Another network board is using the same hardware settings as this network board.The network board does not work.Action: Do one or more of the following:MARK=BULLETMake sure that the network board is properly seated into the slot.PAGENUM=391 ID="BP385"If the jumper settings are not the defaults, make sure that they match the settings in the NET.CFG file. If the computer is not using the NET.CFG file, make sure that the jumper settings are set to the defaults. If other network boards are using the same hardware settings, change the settings and try to reload the driver.Replace the network board with one works.Explanation: If the computer is using a microchannel network board, the network board is not in the computer, or the network board's configuration could not be obtained.Action: Do one of the following:MARK=BULLETMake sure that the network board is properly seated into a slot.Insert the network board into a slot, and run the CLASS=DISKReference diskette to install it.221: IBM communications manager LAN driver has not been installed.LANSUP-OS2Explanation: The IBM Communication Manager Lan Driver is not installed properly.Action: Make sure that the CONFIG.SYS files correctly installs the IBM Communication Manager Lan Driver. For more information about the CONFIG.SYS file, see 
BOOK="ws_osenu" COLLECTION="nw41"NetWare Client for OS/2 User Guide.222: Frame types Ethernet_II and Ethernet 802.3 are not supported.LANSUP-OS2Explanation: The two frame types indicated in the message are not supported.Action: Select a frame type other than Ethernet_II or Ethernet 802.3.PAGENUM=392 ID="BP386"LANZENET-DOS001: The LSL is not loaded.LANZENET-DOSExplanation: The computer must load the Link Support Layer (LSL) before loading the driver.Action: Load the LSL; then load the driver, as in the following example:FORMAT="LINESPECIFIC"MOREINFO="NONE"C:\NWCLIENT\LSL MOREINFO="NONE"<Enter> 
C:\NWCLIENT\LANZENET MOREINFO="NONE"<Enter> 002: The LSL has no room for a board using frame type.LANZENET-DOSExplanation: The Link Support Layer (LSL) is configured with resources for a set number of network boards. (The default is 4.) This number has been exceeded.Action: Edit the NET.CFG file, and add the MAX BOARDS keyword to reflect the number of network boards to be loaded, as in the following example: FORMAT="LINESPECIFIC"MOREINFO="NONE"LINK SUPPORT
  MAX BOARDS 6Unload the driver; then reload it as in the following example:FORMAT="LINESPECIFIC"MOREINFO="NONE"C:\NWCLIENT\LANZENET /u MOREINFO="NONE"<Enter> 
C:\NWCLIENT\LANZENET MOREINFO="NONE"<Enter> 003: Could not find LANZENET MLID to unload.LANZENET-DOSExplanation: The LANZENET driver is not loaded.Action: None. This message is for information only.004: A TSR is loaded above the LANZENET MLID.LANZENET-DOSExplanation: Another TSR (terminate-and-stay-resident) program was loaded after the LANZENET driver.Action: The drivers must be unloaded in reverse order, as follows:FORMAT="LINESPECIFIC"MOREINFO="NONE"C:\NWCLIENT\NETX /u MOREINFO="NONE"<Enter> 
C:\NWCLIENT\IPXODI /u MOREINFO="NONE"<Enter> 
C:\NWCLIENT\LANZENET /u MOREINFO="NONE"<Enter> 
PAGENUM=393 ID="BP387"Unload the TSRs; then try to unload the LANZENET driver. You can force the LANZENET driver to unload from the command line by using the /F switch after the driver name, as follows:FORMAT="LINESPECIFIC"MOREINFO="NONE"C:\NWCLIENT\LANZENET /f MOREINFO="NONE"<Enter> Use caution when using the /F switch because it could cause the system to hang.005: LANZENET MLID could not be unloaded; the operation was aborted.LANZENET-DOSExplanation: The LANZENET driver could not be shut down and unregistered; consequently, it cannot be unloaded.Action: To unload the driver, reboot the system.006: The adapter did not initialize. LANZENET did not load.LANZENET-DOSExplanation: The LANZENET driver encountered an error while loading.Action: Corrective action can vary. See the preceding driver-specific message on the screen for specific information about the error that occurred.007: You need another MLID Section Heading in the NET.CFG file in order to load the MLID again. LANZENET-DOSExplanation: The NET.CFG file does not have an individual entry for each driver that is intended to be loaded.  This means that one of the drivers is not loaded into memory.Action: Unload the LANZENET driver. Modify the NET.CFG file to contain a unique entry for each driver to be loaded. This requires an individual Link Driver heading in the NET.CFG file for each driver or each instance of the same driver. Load the drivers again. For information on the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.008: A NET.CFG is required to load the MLID again.LANZENET-DOSExplanation: The NET.CFG file does not have an individual entry for each driver that is intended to be loaded.  This means that one of the drivers is not loaded into memory.Action: Unload the LANZENET driver. Modify the NET.CFG file to contain a unique entry for each driver to be loaded. This requires an individual Link Driver heading in the NET.CFG file for each driver or each instance of the same driver. Load the drivers again. For information on the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.PAGENUM=394 ID="BP388"009: The NET.CFG entry has been ignored.LANZENET-DOSExplanation: The NET.CFG file does not have an individual entry for each driver that is intended to be loaded.  This means that one of the drivers is not loaded into memory.Action: Unload the LANZENET driver. Modify the NET.CFG file to contain a unique entry for each driver to be loaded. This requires an individual Link Driver heading in the NET.CFG file for each driver or each instance of the same driver. For information on the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference. Reload the LANZENET driver.011: The MLID does not support frame type. The protocol keyword has been ignored.LANZENET-DOSExplanation: An unsupported or incorrectly typed frame type has been specified with the protocol keyword.Action: Verify that the frame type assigned in the NET.CFG file under the protocol keyword is valid. For a list of valid frame types, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.012: The protocol keyword must have a frame type. Entry ignored.LANZENET-DOSExplanation: The PROTOCOL keyword entry is incomplete.Action: Correct the protocol entry in the NET.CFG file. The proper syntax for the protocol keyword is as follows:FORMAT="LINESPECIFIC"MOREINFO="NONE"PROTOCOL LANZENET hex_protocol_ID frame_type For information regarding the PROTOCOL keyword, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.013: The MLID could not register Protocol ID number for protocol stack name for frame type frame.LANZENET-DOSExplanation: The Link Support Layer (LSL) is configured with resources for a set number of Protocol Identifiers. (The default is 4.) This number has been exceeded.Action: Edit the NET.CFG file, and add the MAX STACKS keyword to reflect the number of network boards to be loaded, as in the following example:FORMAT="LINESPECIFIC"MOREINFO="NONE"LINK SUPPORT 
MAX STACKS 6 Unload the driver; then reload it as in the following example:FORMAT="LINESPECIFIC"MOREINFO="NONE"C:\NWCLIENT\LANZENET /u MOREINFO="NONE"<Enter> 
C:\NWCLIENT\LSL /u MOREINFO="NONE"<Enter> 
PAGENUM=395 ID="BP389"C:\NWCLIENT\LSL MOREINFO="NONE"<Enter> 
C:\NWCLIENT\LANZENETMOREINFO="NONE" <Enter> 014: This version of the LSL is not supported.LANZENET-DOSExplanation: The driver the computer is using supports only Link Support Layer (LSL) versions later than 1.0.Action: Unload the LSL and replace it with a newer version.015: The frame type is already active for frame type.LANZENET-DOSExplanation: The frame type is already loaded, and it cannot be loaded repeatedly.Action: Edit the NET.CFG file to load the frame type only once for a given network board. For information regarding frame types, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.016: The node address was incorrectly specified in the NET.CFG file.LANZENET-DOSExplanation: The node address override in the NET.CFG file is too long.Action: Edit the NET.CFG file and correct the node address. The node address must be less than or equal to 12 hex digits. For information regarding node address override, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.017: An invalid keyword was specified in NET.CFG on line number.LANZENET-DOSExplanation: The key word on the line indicated was not recognized.Action: Edit the NET.CFG file and correct the spelling of the keyword. For valid keywords, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.018: The frame type specified in the NET.CFG is not supported.LANZENET-DOSExplanation: The frame type specified with the FRAME keyword is not supported by the driver.Action: Edit the NET.CFG file and fix frame type. For information on supported frame types, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.PAGENUM=396 ID="BP390"019: An invalid LANZENET node address is specified in NET.CFG. The MLID modified the incorrect address bits.LANZENET-DOSExplanation: The node address specified in the NET.CFG file has set reserved bits.Action: Edit the NET.CFG file and correct the node address. For information regarding node addresses, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.050: The board cannot be found.LANZENET-DOSExplanation: The network board was not found due to one or more of the following conditions: MARK=BULLETThe network board is not present in the computer. The network board settings are not the defaults, and they are not defined in the NET.CFG file.Another network board is using the same hardware settings as this network board.The network board does not work.Action: Do one or more of the following:MARK=BULLETMake sure that the network board is properly seated into the slot. If jumper settings are not the defaults, make sure that they match the settings in the NET.CFG file. If the computer is not using the NET.CFG file, make sure that the jumper settings are set to the defaults. If other network boards are using the same hardware settings, change the settings and try to reload the driver.Replace the network board with one works.051: Board RAM failed the memory test.LANZENET-DOSExplanation: The memory test on the network board's internal static RAM failed.Action: Check the network board and other hardware. If necessary, replace the network board.PAGENUM=397 ID="BP391"056: This interrupt is already used and cannot be shared.LANZENET-DOSExplanation: The selected interrupt is in use by another device, so it cannot be used for this network board.Action: Change the jumper settings to specify a different interrupt; then edit the NET.CFG file to reflect the correct interrupt level used by the network board. For information on the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.070: The board has failed.LANZENET-DOSExplanation: A hardware error has occurred.Action: Power down the system; then reboot it. Try to reload the driver. If the driver will not reload, a hardware failure has occurred. Replace the network board.PAGENUM=398 ID="BP392"LOADER1: The load file, name, is invalid. Code code.LOADERExplanation: The SERVER.EXE file has been corrupted. This is usually caused by disk media errors.Action: Verify the reliability of the boot disk media and then copy a new version of SERVER.EXE into the boot area.3: Insufficient memory is available to load the OS.LOADERExplanation: The computer needs at least 4 MB of memory for the operating system to come up. The computer should have at least 8 MB for it to function efficiently; additional memory will be required depending on the size of the NetWare volumes on the server.Action: Increase the available memory. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.4: The Message File, name, is invalid.LOADERExplanation: A SERVER.MSG file in the server's boot directory is corrupted or out of synchronization with the SERVER.EXE file. Note that SERVER.MSG files are only needed for international versions of NetWare. When this file is invalid, the server will come up in English.Action: Delete the SERVER.MSG file or replace it with a current or uncorrupted version.6: An exception interrupt occurred while loading the OS. Exception number number, (string). LoaderMain is at register. EIP is register. ESP is register. EAX is register. EBX is register. ECX is register. EDX is register. EDI is register. ESI is register.LOADERExplanation: A major software failure has occurred. This is caused by a code problem in the hardware independent loader or the operating system's initialization code.Action: Make sure that the SERVER.EXE file has not been corrupted and try again. If the problem persists, contact your Novell Authorized Reseller.7: A debugger interrupt occurred while loading the OS. Program terminated.LOADERExplanation: A major software failure has occurred. This is caused by a problem in the hardware independent loader or the OS initialization code.Action: Make sure that the SERVER.EXE file has not been corrupted and try again. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=399 ID="BP393"8: An "Int 3" occurred while loading the OS. Program terminated.LOADERExplanation: A major software failure has occurred. This is caused by a problem in the hardware independent loader or the OS initialization code.Action: Make sure that the SERVER.EXE file has not been corrupted and try again. If the problem persists, contact your Novell Authorized Reseller.9: An invalid interrupt occurred while loading the OS. Program terminated.LOADERExplanation: A major software failure has occurred. This is caused by a problem in the hardware independent loader or the OS initialization code.Action: Make sure that the SERVER.EXE file has not been corrupted and try again. If the problem persists, contact your Novell Authorized Reseller.10: An OS procedure was called before the OS completed loading. Program terminated.LOADERExplanation: A major software failure has occurred. This is caused by a problem in the hardware independent loader or the OS initialization code.Action: Make sure that the SERVER.EXE file has not been corrupted and try again. If the problem persists, contact your Novell Authorized Reseller.11: The Loader was unable to get the DOS country information, so USA was assumed.LOADERExplanation: The NetWare server was unable to get the DOS country information for DOS, so the USA defaults will be used. If the computer has an LCONFIG.SYS file in the boot directory, it will override the DOS country information obtained from DOS or the default.Action: If the computer has an LCONFIG.SYS file in the server's boot directory, then ignore the message. If the computer does not have an LCONFIG.SYS file, then find the proper one for the country and place it in the server's boot directory.12: Additional number bytes of memory above 16 megabytes will not be used.LOADERExplanation: The server was unable to auto-register memory above 16 MB. This can be caused by hardware that does not follow the EISA or microchannel specifications.Action: If you want the server to use the memory, then use the "REGISTER MEMORY" console command. Place this command in the server's AUTOEXEC.NCF file.13: The attempt to auto-register memory above 16 megabytes failed.LOADERExplanation: The server was unable to auto-register memory above 16 MB. This can be caused by hardware that does not follow the EISA or microchannel specifications.Action: If you want the server to use the memory, then use the "REGISTER MEMORY" console command. Place this command in the server's AUTOEXEC.NCF file.PAGENUM=400 ID="BP394"19: Error reading load file name.LOADERExplanation: The SERVER.EXE file has been corrupted. This is usually caused by disk media errors.Action: Make sure that the boot disk media is reliable; then copy a new version of SERVER.EXE into the boot area.PAGENUM=401 ID="BP395"LOGIN100: Access has been denied.LOGINExplanation: The user has no rights to log in for one of the following reasons:MARK=BULLETThe username or password was typed incorrectly.The username entered does not have an account.The account balance is zero.On multiserver networks using bindery mode, this message may mean that the user is not on the server to which the NetWare shell connected the workstation.Action: Log in again and type the username and password correctly. Make sure that the workstation is logging in to a server or NetWare Directory Services network on which the user is defined. If the user is not attached to the server or network you want to log in to, specify the server or network in the LOGIN command. For more information, see "BOOK="utlrfenu" COLLECTION="nw41"LOGIN" in Utilities Reference.105: You are trying to attach to your current tree (current tree name: tree name).LOGINExplanation: You cannot reattach (INS) to the same tree.Action: None required, unless you want to attach to a different tree.110: You are already in a tree and cannot attach to another tree (current tree: tree name).LOGINExplanation: You cannot use INS to attach to a second tree.Action: Logout and try again.115: The selected tree (name) cannot be found. Error code: code.LOGINExplanation: LOGIN tried to log the user in to a Directory tree that is either down, is not responding, or does not exist.Action: Verify that the Directory tree name was entered correctly and that the network is up and running. For information on the specific error code, see IDREF="FM61529""Error Codes" in Appendix A.130: Access has been denied and you have been logged out.LOGINExplanation: The user has no rights to log in for one of the following reasons:MARK=BULLETThe username or password was typed incorrectly.PAGENUM=402 ID="BP396"The user does not have an account.The account balance is zero.On multiserver networks using bindery mode, this message may mean that the user is not defined on the server that the NetWare shell connected the workstation to.Action: Log in again and type the username and password correctly. Log in to a server or NetWare Directory Services network where the user is defined. If the workstation is not connected to the server or network you want, specify the server or network in the LOGIN command. For more information, see "BOOK="utlrfenu" COLLECTION="nw41"LOGIN" in Utilities Reference.140: This account has expired or been disabled by the supervisor.LOGINExplanation: This message could occur for one of the following reasons:MARK=BULLETThe account has expired. The network supervisor can limit a user's account to a specific period, after which the account expires and is no longer accessible.The account has been disabled. The network supervisor can disable a user's account for any reason.The user did not type a password correctly. The network supervisor can limit the number of consecutive failed attempts to log in to a user's account.Action: Enable the user's account.150: You could not be authenticated to server name. (code)LOGINExplanation: Authentication means that the workstation attaches and logs the user in to a server without prompting for the password. In this instance, LOGIN could not authenticate to the specified server. The cause of this error is unknown.Action: Log out and try again. For information on the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.180: The login script contains a misplaced control command.LOGINExplanation: The parser found a control command (such as ATTACH, MAP, or SET) that LOGIN did not know existed. This error can occur for one of the following reasons:MARK=BULLETThe control command was correctly parsed, but in an odd position in the line.A programming error exists that prevented LOGIN from using all of the commands that the parser used. This is the more likely of the two scenarios.Action: Use the correct syntax. For example login script syntax, see "BOOK="superenu" COLLECTION="nw41"Creating Login Scripts" in Supervising the Network. PAGENUM=403 ID="BP397"200: The MAP command cannot change local drives.LOGINExplanation: A MAP CHANGE command was issued within the login script that referenced a local drive. Local drives cannot be changed to or from search drives by using MAP.Action: Do not try to change local drives using MAP.210: This server is being used to read login scripts. You cannot log out.LOGINExplanation: LOGIN encountered a LOGOUT command in a login script. LOGIN makes sure you were trying to log out of the same server that it was using to read the login script. If that has happened, various errors could occur; for example, the workstation could hang, or output could be unintelligible.Action: Determine which login script was being read and the server on which it resides. Do not try to log out of that server. For more information, see"BOOK="utlrfenu" COLLECTION="nw41"LOGIN" in Utilities Reference.215: An internal system error occurred during LOGIN's attempt to canonicalize the context: (name).LOGINExplanation: LOGIN tried to expand the relative name to a full name.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.220: Script file name cannot be included.LOGINExplanation: The login script had a "include script file name" entry, and LOGIN was unable to include it. This error occurs if no script file exists or if the specified path or filename is wrong.Action: Make sure that the path and filename specified are correct.240: This utility was unable to open script file name.LOGINExplanation: LOGIN tried to open the specified script file, but the file was not found or it could not be opened.Action: Make sure that the login script file is in the directory specified. If it is, make sure that the file is flagged to allow the user to access it. Make sure the user has appropriate user access rights to the directory and the file.241: This utility was unable to open profile script script name.LOGINExplanation: LOGIN tried to open the specified script file, but the file was not found or it could not be opened.Action: Make sure that the login script file is in the directory specified. If it is, make sure that the file is flagged to allow the user to access it. Make sure the user has appropriate user access rights to the directory and the file.PAGENUM=404 ID="BP398"250: This utility was unable to set the default drive to drive letter.LOGINExplanation: An invalid drive was probably specified.Action: Validate the drive letter indicated in the login script by first mapping the letter to a valid drive and directory.260: The maximum number of server attachments has been reached.LOGINExplanation: Each NetWare server can be configured in a variety of ways (for example, as a 1000-user, 250-user, or 10-user network). Each configuration allows a certain number of connections.Action: Try again after a user has logged out of the server.280: This utility could not get your connection status.LOGINExplanation: LOGIN failed to verify whether the user was logged in.Action: Attach using MAP. If this fails, reboot and reestablish all current connections.283: This utility could not get the preferred Directory Services name or connection ID.LOGINExplanation: LOGIN could not find the preferred Directory tree.Action: Verify that the preferred Directory tree or server in the NET.CFG file is correct.285: A network drive could not be found.LOGINExplanation: LOGIN couldn't find the first available network drive. If the login attempt fails (for example, if you have entered an incorrect password or an invalid username), the drive mapping is placed on this drive. LOGIN exits if it can not find an available network drive as a fall-back drive.Action: Make sure the last drive in CONFIG.SYS is not set to Z:. For more information, see "BOOK="utlrfenu" COLLECTION="nw41"LOGIN" in Utilities Reference.287: This utility could not find the preferred server.LOGINExplanation: LOGIN could not find the preferred server as specified in the NET.CFG file.Action: Verify that the preferred server in the NET.CFG file is correct.290: This utility was unable to log you out, so you cannot be reattached.LOGINPAGENUM=405 ID="BP399"Explanation: Before LOGIN can reattach the user to any server, it must first log the user out. LOGIN's attempt to log out failed; therefore, it cannot reattach. This error occurs only with the /NS option, which allows the user to remain logged in to other servers or NetWare Directory Services networks when the user is logging in to a new server or network.Action: Try logging out using the LOGOUT utility; then try to log in using the /NS option. For more information, see "BOOK="utlrfenu" COLLECTION="nw41"LOGIN" in Utilities Reference.295: This utility could not create a context.LOGINExplanation: LOGIN unsuccessfully tried to allocate a context handle. This error can be caused by low memory.Action: Make sure the user's name context in the NET.CFG file is correct and try again. If you suspect low workstation memory, see IDREF="FM55341""971: The workstation does not have enough memory to load the Unicode table files." in Appendix C.310: The workstation date and time could not be set.LOGINExplanation: LOGIN could not synchronize the workstation's date or time with the server or the NetWare Directory Services network's date or time, probably because of an internal memory error in the workstation.Action: Save your work and reboot the workstation. If the error persists, turn off the workstation. Wait approximately 15 seconds, turn it on, and log in again.320: An operator in the login script attempted to divide by zero.LOGINExplanation: You did a division by zero in the login script through the DIVISION or MODULUS arithmetic operators.Action: Change the login script so that it does not do a division by zero.340: IF statements are nested too deeply. The nesting limit is number levels.LOGINExplanation: IF statements can be nested up to the number of levels indicated in the message. The login script can have unlimited IF statements, but the login script is limited to number of nested IF statements indicated in the message.Example of four levels of nested IF statements:FORMAT="LINESPECIFIC"MOREINFO="NONE"IF........ 
IF......... 
IF....... 
IF..... 
...... 
ENDIF 
ENDIF 
ENDIF 
PAGENUM=406 ID="BP400"ENDIF Action: Where possible, take the IF statements out of the nested format and placing them after the sequence of nested IF statements. For more information about "IF...THEN" statements, see "BOOK="superenu" COLLECTION="nw41"Creating Login Scripts" in Supervising the Network.370: The specified search drive does not exist.LOGINExplanation: When the login script uses a SET COMSPEC= or COMSPEC=, if a network drive is specified, LOGIN ensures that the specified drive is a search drive and can be used for the COMSPEC command.Action: Before issuing the SET COMSPEC or COMSPEC command, do one of the following:MARK=BULLETSet the COMSPEC to a local (nonnetwork) search drive.Map a search drive to the path where the command processor is located.380: The line is too long.LOGINExplanation: A line in the login script exceeded the maximum limit of 254 bytes.Action: Shorten the line or split the command into two commands so that they have the same functionality but occur on two lines. For more information about logging in, see "BOOK="utlrfenu" COLLECTION="nw41"LOGIN" in Utilities Reference.400: A network drive cannot be mapped to a drive that is designated as a local drive.LOGINExplanation: You tried to map a local drive to volume or directory on the network.Action: Map the volume or directory from the network to a network drive.410: The supervisor has disabled the login function for this server.LOGINExplanation: This account is locked. The network supervisor can disable the login function temporarily to prevent users from logging in or attaching during system maintenance. Most likely, the network supervisor is doing maintenance work.Action: This condition is usually temporary. Try to log in after the login function has been enabled. If using CAPTURE or NPRINT, attach to another server and use its printer. Make sure that the SYS: volume is mounted on the server. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=407 ID="BP401"430: The following drive mapping operation could not be completed. Mapping. The error code was code.LOGINExplanation: You tried to map a drive to a path that does not exist or cannot be found by LOGIN.Action: Make sure that the you are mapping the drive to a valid path. For information on the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 440: The operation was attempted on an invalid drive.LOGINExplanation: You tried to manipulate an invalid drive using MAP. For example, "MAP DEL L:" would produce this error if L: had not been previously mapped.Action: Make sure that the command is entered correctly in the login script.Make sure that the drive is mapped correctly. For more information, see "BOOK="superenu" COLLECTION="nw41"Creating Login Scripts" in Supervising the Network.450: This utility was unable to map drive. The limit of 16 search drives was exceeded.LOGINExplanation: The workstation is limited to 16 search drives.Action: Delete an unwanted search drive to make room for the drive to be added. (Use the MAP DEL search_drive or MAP REM search_drive command to delete the drive.)460: The server that you attempted to map a drive to is not accessible. The map command was command.LOGINExplanation: The server is probably down; therefore, LOGIN could not attach to the server.Action: Verify that the network is up and running and try again.470: The specified drive mapping is an invalid path: path.LOGINExplanation: LOGIN tried to map a drive to a path that does not exist.Action: Verify that the user is are logged in to the server (if it is a bindery server) that you are trying to map to. Verify that the path exists and that it was typed correctly.480: The MACHINE NAME command is not supported in DOS versions prior to DOS 3.1.LOGINExplanation: When using the "MACHINE NAME =" command in the login script, the workstation must be running DOS 3.1 or later. Note: The "MACHINE NAME =" command is the only command that will return this error.Action: Upgrade to DOS 3.1 or do not use the specified command.PAGENUM=408 ID="BP402"500: You do not have an account balance.LOGINExplanation: The user does not have an account on this server or NetWare Directory Services network.Action: Obtain an account or reestablish a previous account.520: Your credit limit has been exceeded.LOGINExplanation: LOGIN denied access because the user has no more credit on the server or on the NetWare Directory Services network.Action: Ask the supervisor to give the user more credit. Credit is given by the supervisor through NETADMIN.530: The line contains no end quote.LOGINExplanation: A line in the login script does not contain an end quote. For example, WRITE "Hello World! is missing the second double quote mark.Action: Put the end quote in the login script at the end of the specified line. For more information, see "BOOK="superenu" COLLECTION="nw41"Creating Login Scripts" in Supervising the Network.550: The maximum number of connections allowed on this server has been reached. Wait until another user logs out.LOGINExplanation: The user is trying to log in to or attach to a server via the login script, but too many users are already logged in to the server. The servers come with 5, 10, 1000, or other programmed number of user versions.Action: Either wait until a user logs out (thus freeing a connection that will allow the user to log in), or, if this is a common problem, upgrade to a server with a greater number of user connections.560: This utility could not find the label label.LOGINExplanation: The label used in the GOTO command was not found. A common cause of this problem is shown in the following example:FORMAT="LINESPECIFIC"MOREINFO="NONE"IF FILE_SERVER = "911" THEN GOTO need_help FORMAT="LINESPECIFIC"MOREINFO="NONE"........ 
need_help: 
....... 
....... 
ENDIF 
PAGENUM=409 ID="BP403"Note that need_help and the label need_hep are spelled differently; therefore, LOGIN cannot find the label specified by the GOTO command. Also, if the colon is left off the label name, LOGIN will not know that it is a label and will not find it.Action: Use NETADMIN or NetWare Administrator to edit the login script. Make sure that the label is spelled correctly and that a colon follows the label name. For more information, see "BOOK="superenu" COLLECTION="nw41"Creating Login Scripts" in Supervising the Network.580: Your password has expired and all grace logins have been used.LOGINExplanation: The account is locked because the user did not change an expired password. The network supervisor can limit the number of times a user can log in with an expired password.Action: Unlock the user's account.600: This utility could not interpret the line.LOGINExplanation: LOGIN could not parse the line indicated in the login script.Action: Verify that the line has been typed correctly and has the proper syntax.610: The file server does not respond.LOGINExplanation: The workstation or user tried to attach to the server, but the server did not respond for one of the following reasons:MARK=BULLETThe server lost power or was shut off before the DOWN command was issued.A broken or loose connection exists on the internetwork between the server and the server you tried to attach to.When a server is brought down, the DOWN command sends a message to all other servers informing them that the server is no longer active. However, if a server is shut off before the DOWN command is issued, all other servers assume that the server is still active. In this situation, the server name still appears when the NLIST command is invoked, even though the server is no longer active. The server can be seen with NLIST up to 15 minutes after it has lost its power or halts abnormally. This error message appears if the user tries to log in to or issue a command on the server in question.Action: Try the command again when the server has been brought back up.630: The NetWare shell is not loaded.LOGINPAGENUM=410 ID="BP404"Explanation: The user tried to log in to a server without loading the NetWare NETX or VLM bindery shell into the workstation's memory. When the workstation is booted, DOS is loaded into the workstation's memory. The NetWare shell is then loaded on top of DOS. The shell allows the workstation to communicate with the server. A user cannot log in to any server on the network unless the NetWare shell has been loaded into the workstation's memory.Action: Give the user a boot diskette that contains both DOS and the NetWare shell files. Then ask the user to try rebooting the workstation and logging in again. If the error persists, the boot diskette may be corrupted.640: Server name is part of domain name. This version of LOGIN is not a NetWare Name Service utility and cannot synchronize passwords in a domain. Use the NetWare Name Service utility SETPASS to change your password.LOGINExplanation: LOGIN found that a server the user is attached to is a NetWare Name Service server. This LOGIN version cannot handle NetWare Name Service's synchronization of passwords.Action: Use a NetWare Name Service (NNS) version of SETPASS to synchronize passwords.650: The COMSPEC variable is not supported in OS/2.LOGINExplanation: You tried to use the COMSPEC variable in the login script for OS/2.Action: Do not use the COMSPEC command in the login script when using OS/2.660: The DOS BREAK command is not supported in OS/2.LOGINExplanation: The login script has BREAK variable. BREAK is not supported in OS/2, only in DOS.Action: Do not use the BREAK command in the login script when using OS/2.665: The EXIT command followed by a string is not supported on this machine.LOGINExplanation: The EXIT command was followed by a text string in the user's login script.Action: Remove the text string that follows the EXIT command in the user's login script.670: The variable MACHINE NAME is not supported in OS/2.LOGINExplanation: The login script has a MACHINE_NAME variable. MACHINE_NAME is not supported in OS/2, only in DOS.Action: Do not use the MACHINE_NAME command in the login script when using OS/2.680: OS/2 does not support search drives.LOGINExplanation: You tried to use search drives in OS/2.Action: Do not specify search mappings in the login script when using OS/2.PAGENUM=411 ID="BP405"690: Insufficient memory is available to add the variable to the path environment in mapping: [mapping]LOGINExplanation: There is not enough room in the master environment.Action: Increase the size of the master environment. In the CONFIG.SYS file, include the command SHELL=directory of command.com /e:size of master environment. For example:FORMAT="LINESPECIFIC"MOREINFO="NONE"SHELL=C:\COMMAND.COM /E:1024 700: The specified path is invalid.LOGINExplanation: When using the DISPLAY or FDISPLAY command in the login script, the specified file or path was invalid.Action: Make sure that the path name is a path. If necessary, correct the path in the login script.710: The password could not be changed. Error code.LOGINExplanation: LOGIN was unable to change the password.Action: For information on the specific error code, see IDREF="FM61529""Error Codes" in Appendix A.720: This utility could not add variable to the local environment variables.LOGINExplanation: This error occurs when you try to map a search drive. LOGIN was unable to add the variable to the local path environment variable. LOGIN will try to update the master environment and, upon successful completion, will try to update its local environment. This error is usually an indication of having too little memory to allocate the new variables.Action: Increase the available memory. See "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network. (Adding more than 640 KB will not correct this error because 640 KB is the maximum that can be used.) This is not a serious error; however, you will not be able to access those search drives as search drives until login has been completed. These drives will still be mapped as regular drives. Because they were successfully placed in the master environment, they can become search drives once login has been completed.725: The context you want to change to does not exist. You tried to change to: [name]. Your context will be left unchanged.LOGINExplanation: LOGIN tried to change to a context that does not exist.Action: Verify the name of the context to which you want to change.PAGENUM=412 ID="BP406"730: The context [name] is invalid. Your current context will be left unchanged.LOGINExplanation: LOGIN tried to change to a context that does not exist.Action: Verify the name of the context to which you want to change.740: This utility could not execute external program name.LOGINExplanation: The specified file is not executable or has an invalid executable-file format.Action: Execute an executable file. The files usually have the .EXE or .COM extension.750: This utility could not execute external program name. You do not have enough memory space available.LOGINExplanation: For DOS to run a program, it must allocate enough memory to run that program. Programs that are very large will frequently have this problem.Action: Increase the available memory. See "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network. If running from a shell (such as WordPerfect's shell), try running LOGIN from the command line.760: This utility could not execute external program name. The program was not found.LOGINExplanation: LOGIN tried to execute a command using the #command syntax in the login script. However, the program was not found, and LOGIN could not execute the command. For example:FORMAT="LINESPECIFIC"MOREINFO="NONE"#EMAIL should execute E-mail. If LOGIN cannot find the program, either in the current directory or in the path, it will display this error message.Action: Make sure the workstation has a mapping to the directory where the program is located before you try to execute the program. Make sure that you have entered the full path name and the name of the program, as in the following example:FORMAT="LINESPECIFIC"MOREINFO="NONE"C:\APPS\MAIL\EMAIL Be sure to copy the program to a location that has a current mapping.770: This utility could not execute external program name. Either the environment is too big or the command line is too long.LOGINExplanation: The following are two possible explanations:MARK=BULLETThe login script may have tried to execute a command using the #command. DOS allows only 128 characters on the command line. If the command is too long, it cannot be executed when using DOS, and LOGIN will warn you of this problem.PAGENUM=413 ID="BP407"The space required for the environment information may have been greater than 32 KB.Action: Limit the external command, or set the environment string length to 128. If possible, divide the command into two separate commands executed one after another.780: This utility could not execute external program name. Error number occurred.LOGINExplanation: For an unknown reason, LOGIN could not execute the external program.Action: To get specifics on the error displayed and on the appropriate procedure, contact your Novell Authorized Reseller.790: The parser string table is full.LOGINExplanation: Internally, the parser used by LOGIN is storing strings. The parser string table holds a set number of strings. If the table becomes so full that it cannot hold any more strings, it will report this error.Action: Try using fewer commands on a single line in the login script.800: The number of script parameters exceeds the program limit (number).LOGINExplanation: You have exceeded the number of arguments that you can pass from the command line to the login script. The correct limit is displayed.Action: Pass in fewer arguments to the login script.810: An invalid string occurred in an EXIT command. The string contained more than number characters.LOGINExplanation: When you are using the EXIT command to pass a command to COMMAND.COM, the specified command cannot exceed 14 characters.Action: Use fewer characters.830: You are trying to log in to too many stations simultaneously. The supervisor has limited the number of connections you may have.LOGINExplanation: You could not log in for one of the following reasons:MARK=BULLETYou are already logged in with the maximum number of workstations allowed. You must log out of one workstation before you can log in from another workstation.PAGENUM=414 ID="BP408"You could not log in because the user account is currently being used by the maximum number of users allowed. You must wait for a user to log out from this account before you can log in.Action: In either case, the account you are trying to log in to is already being accessed by the maximum number of workstations or users. A user must log out from the account before you can log in.840: This utility is unable to set the context to name.LOGINExplanation: LOGIN was unable to set the context to the context specified. No further information is available.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.850: You are trying to log in from an unauthorized station. The supervisor has limited the stations you may log in from.LOGINExplanation: The account was accessed from an unauthorized workstation. A network supervisor restricted the account to specific workstation workstations.Action: Access the account only from authorized workstations.860: You are trying to log in during an unauthorized time period. The supervisor has limited the times that you may log in.LOGINExplanation: The network supervisor has set specific time periods when the user can use the server or the NetWare Directory Services network. The user cannot use the server until the next authorized time period.Action: Give the user a list of authorized time periods.870: An unknown error was returned during LOGIN's attempt to attach. (code)LOGINExplanation: An error has occurred that the operating system cannot identify; however, this error message usually indicates that the server or the NetWare Directory Services network is servicing the maximum number of logged-in users it can accommodate with the amount of memory installed.Action: Ask some users to log out of the system temporarily. If the error persists, contact your Novell Authorized Reseller. For information on the specific error code, see IDREF="FM61529""Error Codes" in Appendix A.PAGENUM=415 ID="BP409"880: An unknown, but correctly parsed, command was found in the login script.LOGINExplanation: A command in the login script was correctly parsed, but LOGIN did not know what command it was and could not execute it.Action: Make sure that the command has been entered correctly in the login script. A script error has probably occurred that was, somehow, parsed correctly.890: The specified server is unknown.LOGINExplanation: You mistyped the name of the server, specified a server that is not on the network, or specified a server that has been brought down for system maintenance.Action: Use NLIST or NETADMIN to list the servers that the station recognizes. Type the name of the server correctly. If the server has been brought down for maintenance, try the command after the server has been brought back up.895: The user does not exist in the specified context.LOGINExplanation: The user specified in the command line does not exist.Action: Specify a valid username in the command line.903: The command line syntax is invalid.LOGINExplanation: The LOGIN command type is not correct.Action: Type LOGIN /? for help.905: This utility was unable to initialize the country information.LOGINExplanation: The shell or VLM failed to load, or some of the memory is corrupted.Action: See message IDREF="FM55337""905: This utility was unable to initialize the country information." in Appendix C.915: The specified volume does not exist.LOGINAction: See message IDREF="FM46881""915: The specified volume does not exist." in Appendix C.918: This utility was unable to get connection information.  Error code: <code>.LOGINAction: See message IDREF="FM25772""918: This utility was unable to get connection information. Error code: code." in Appendix C.919: This utility could not create a connection list.  Error <code>.LOGINAction: See message IDREF="FM68419""919: This utility could not create a connection list. Error code." in Appendix C.PAGENUM=416 ID="BP410"920: This utility does not have enough memory.LOGINExplanation: LOGIN does not have enough workstation conventional memory to execute.Action: Free conventional memory by unloading device drivers or other TSA programs. See message IDREF="FM30331""920: This utility was unable to allocate number bytes of memory." in Appendix C.For additional help, see message IDREF="FM55341""971: The workstation does not have enough memory to load the Unicode table files." in Appendix C.921: Either the supervisor has locked the bindery or volume SYS: is not mounted.LOGINAction: See message IDREF="FM49837""921: Either the supervisor has locked the bindery or volume SYS: is not mounted." in Appendix C.922: Intruder detection lockout has disabled this account.LOGINAction: See message IDREF="FM41618""922: Intruder detection lockout has disabled this account." in Appendix C.923: An unexpected error has occurred. Error code: <code>.LOGINAction: See message IDREF="FM30182""923: An unexpected error has occurred. Error code: code." in Appendix C.924: All drives are in use.LOGINAction: See message IDREF="FM81823""924: All drives are in use." in Appendix C.ID="FM84974"925: This function is not supported on Personal NetWare servers.LOGINAction: See message IDREF="FM67645""925: The server specified is a Personal NetWare server. You cannot attach to a Personal NetWare server with this utility. Use the Personal NetWare utilities to access this connection." in Appendix C.970: The attempt to open the Unicode table files failed.LOGINAction: See message IDREF="FM15675""970: The attempt to open the Unicode table files failed." in Appendix C.ID="FM77041"971: The workstation does not have enough memory to load the Unicode table files.LOGINAction: See message IDREF="FM55341""971: The workstation does not have enough memory to load the Unicode table files." in Appendix C.972: Access to the Unicode table files was denied.LOGINAction: See message IDREF="FM90152""972: Access to the Unicode table files was denied." in Appendix C.PAGENUM=417 ID="BP411"973: The Unicode table files cannot be found in the NLS directory or in the search path. Code page: <number>  Country:  <number>LOGINAction: See message IDREF="FM62778""973: The Unicode table files cannot be found in the NLS directory or in the search path. Code page: number Country: number" in Appendix C.974: The Unicode table files are corrupt.LOGINAction: See message IDREF="FM63405""974: The Unicode table files are corrupt." in Appendix C.975: The Unicode table files cannot be opened because there are already too many open files. Close some files or modify your CONFIG.SYS file.LOGINAction: See message IDREF="FM49793""975: The Unicode table files cannot be opened because there are already too many open files. Close some files or modify your CONFIG.SYS file." in Appendix C.998: The message file found (<utility_name>.MSG) is an incorrect version. The correct version is <number>. See your network supervisor for assistance.LOGINAction: See message IDREF="FM91957""998: The message file found (utility_name.MSG) is an incorrect version. The correct version is number. See your network supervisor for assistance." in Appendix C.999: The message file for this utility cannot be found.: Login.msgLOGINAction: See message IDREF="FM69424""999: The message file for this utility cannot be found." in Appendix C.2030: The password for user name on server name has expired.LOGINExplanation: The user's account is locked because the password has expired. The network supervisor can require periodic password changes on accounts to prevent unauthorized access to the accounts. The network supervisor can also assign a grace period during which users can still use their expired passwords before having to choose new ones.Action: Use the SETPASS command to change the password. If the current password is used during the user's grace period, it must be changed before the grace period ends. If the grace period expires and a new password has not been set, the network supervisor will have to change the user account password.2032: The password for user name has expired.LOGINPAGENUM=418 ID="BP412"Explanation: The user's account is locked because the password has expired. The network supervisor can require periodic password changes on accounts to prevent unauthorized access to the accounts. The network supervisor can also assign a grace period during which users can still use their expired passwords before having to choose new ones.Action: Use the SETPASS command to change the password. If the current password is used during the user's grace period, it must be changed before the grace period ends. If the grace period expires and a new password has not been set, the network supervisor will have to change the user account password.2040: This is your last chance to change your password. You have no grace logins remaining.LOGINExplanation: This is the last chance the user has to change the password. If the password is not changed before the user logs out, the user will be denied access to the server or to the NetWare Directory Services network on the next login attempt, and the network supervisor will have to change the account password.Action: Use SETPASS to Change the password.2050: The new password was retyped incorrectly.LOGINExplanation: When changing the password, you were asked to enter the new password and then retype it. You did not type it exactly the same way the second time as you did the first time.Action: Retype the password again.2070: The new password has been used previously.LOGINExplanation: The network supervisor can restrict users from using previous passwords.Action: Select a password that you have not already used with the account.2080: New password is too short.LOGINExplanation: The user tried to define a password that is shorter than the minimum length set by the network supervisor.Action: Tell the user to use a longer password.PAGENUM=419 ID="BP413"LOGOUT100: This workstation could not be detached from server name. Error code: code.LOGOUTExplanation: LOGOUT failed to detach a workstation from a server.Action: Try rebooting the workstation to clear all server connections. For information on the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.150: This utility was unable to get the server name. Error code: code.LOGOUTExplanation: During the process of logging out, LOGOUT looks through the list of servers you are attached to and finds the specified server. Because the workstation does not maintain a list of servers except through the connection number, LOGOUT takes the connection number and asks for the server name. If LOGOUT does not receive the server name, LOGOUT reports this error and identifies it by the code shown in the message.Action: For information on the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.160: Logout from server name cannot be completed. Error code: code.LOGOUTExplanation: An unexpected error has prevented LOGOUT from allowing you to log out from the server indicated in the message.Action: For information on the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.170: NetWare Name Services is not supported in this version of LOGOUT. Use a NetWare Name Service version of LOGOUT to log out of domains.LOGOUTExplanation: This version of LOGOUT does not support NetWare Name Service logouts.Action: Follow the instruction in the message.180: You have only one network connection left. LOGOUT cannot detach from it.LOGOUTExplanation: You tried to break the last connection to the network.Action: None. This message is for information only.190: A default connection cannot be found.LOGOUTExplanation: LOGOUT could not get the default connection identification number.Action: Log out from a different drive. This changes the default connection to a different server.PAGENUM=420 ID="BP414"200: You are not attached to any NetWare servers.LOGOUTExplanation: You are not attached to any NetWare servers.Action: Attach or log in to a NetWare server before trying to log out.210: No valid drives are available to assign default to.LOGOUTExplanation: LOGOUT could not find a valid drive. When LOGOUT completely logs you out of all servers, it leaves you attached to one of them, but it does not leave you logged in to it. LOGOUT tries to leave you mapped to a valid network, or to a local drive if a network is not found.Action: Change to the local drive and try to log in again, or issue the MAP command to see if any drives are available. If these attempts fail and you cannot find the LOGIN.EXE, ATTACH.EXE, or MAP.EXE program, reboot and allow the shell to connect you to a server that contains LOGIN.EXE, ATTACH.EXE, or MAP.EXE.220: You are not attached to server name.LOGOUTExplanation: You tried to log out of a server that you were not attached to.Action: Make sure that you type the server name correctly.222: You are not logged in to a Directory Services tree.LOGOUTExplanation: The /TR option was used in a LOGOUT command when you were not logged in to a Directory tree.Action: Do not use the /TR option in a LOGOUT command.230: Default drive cannot be remapped to drive drive.LOGOUTExplanation: LOGOUT thought a certain drive was valid, and DOS could not set the default drive to that letter. When LOGOUT has logged you out of the default server, it will leave you attached, but not logged in. LOGOUT tries to leave you mapped to a valid network or local drive. LOGOUT tries to find the first valid drive. If a valid drive is not found, you get the error message "No valid drives are available to assign default to." If it does find a valid drive, LOGOUT calls DOS to set the default drive to that drive letter. If DOS cannot locate the drive that LOGOUT thought was valid, or cannot set the drive to the proper letter, you will get this message.Action: Try issuing the MAP command to see if any drives are available; then change to that drive with the drive letter: command. If these attempts fail and you cannot find the LOGIN.EXE, ATTACH.EXE, or MAP.EXE program, reboot and allow the shell to connect you to a server that contains LOGIN.EXE, ATTACH.EXE, or MAP.EXE.PAGENUM=421 ID="BP415"295: This utility could not create a context.LOGOUTExplanation: The workstation does not have enough memory to set up the context.Action: If you suspect insufficient workstation memory, see "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network.ID="FM55073"903: The command line syntax is invalid. For help, type LOGOUT /?LOGOUTAction: See message IDREF="FM18860""903: The command line syntax is invalid." in Appendix C.905: This utility was unable to initialize the country information.LOGOUTAction: See message IDREF="FM55337""905: This utility was unable to initialize the country information." in Appendix C.918: This utility was unable to get connection information.  Error code: <code>.LOGOUTAction: See message IDREF="FM25772""918: This utility was unable to get connection information. Error code: code." in Appendix C.919: This utility could not create a connection list.  Error <code>.LOGOUTAction: See message IDREF="FM68419""919: This utility could not create a connection list. Error code." in Appendix C.920: This utility was unable to allocate <number> bytes of memory.LOGOUTAction: See message IDREF="FM30331""920: This utility was unable to allocate number bytes of memory." in Appendix C.970: The attempt to open the Unicode table files failed.LOGOUTAction: See message IDREF="FM15675""970: The attempt to open the Unicode table files failed." in Appendix C.971: The workstation does not have enough memory to load the Unicode table files.LOGOUTAction: See message IDREF="FM55341""971: The workstation does not have enough memory to load the Unicode table files." in Appendix C.972: Access to the Unicode table files was denied.LOGOUTAction: See message IDREF="FM90152""972: Access to the Unicode table files was denied." in Appendix C.PAGENUM=422 ID="BP416"973: The Unicode table files cannot be found in the NLS directory or in the search path. Code page: <number>  Country:  <number>LOGOUTAction: See message IDREF="FM62778""973: The Unicode table files cannot be found in the NLS directory or in the search path. Code page: number Country: number" in Appendix C.974: The Unicode table files are corrupt.LOGOUTAction: See message IDREF="FM63405""974: The Unicode table files are corrupt." in Appendix C.975: The Unicode table files cannot be opened because there are already too many open files. Close some files or modify your CONFIG.SYS file.LOGOUTAction: See message IDREF="FM49793""975: The Unicode table files cannot be opened because there are already too many open files. Close some files or modify your CONFIG.SYS file." in Appendix C.998: The message file found (<utility_name>.MSG) is an incorrect version. The correct version is <number>. See your network supervisor for assistance.LOGOUTAction: See message IDREF="FM91957""998: The message file found (utility_name.MSG) is an incorrect version. The correct version is number. See your network supervisor for assistance." in Appendix C.999: Could not find message file LOGOUT.MSG.LOGOUTAction: See message IDREF="FM69424""999: The message file for this utility cannot be found." in Appendix C.PAGENUM=423 ID="BP417"MacIPXMessages for this module are in "BOOK="macclenu" COLLECTION="nw41"Error Messages" in Using MacNDS Client for NetWare 4.PAGENUM=424 ID="BP418"MacIPX Control Panel Messages for this module are in "BOOK="macclenu" COLLECTION="nw41"Error Messages" in Using MacNDS Client for NetWare 4.PAGENUM=425 ID="BP419"MACIPXGW1: Unloading MACIPXGW.LAN because of initialization failure.MACIPXGWExplanation: The MACIPXGW.LAN file did not load. Action: Use NetWare Administrator to review the resource utilization of the server or router. See "BOOK="utlrfenu" COLLECTION="nw41"NetWare Administrator" in Utilities Reference. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. When more memory is available, reload the MACIPXGW.LAN file.2: Fatal Error: Could not allocate a memory resource tag.MACIPXGWExplanation: The server has insufficient memory available to support MACIPXGW.Action:  See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. When more memory is available, reload MACIPXGW.3: Fatal Error: Could not allocate an ECB resource tag.MACIPXGWExplanation: The gateway could not get the resources that it required. The MACIPXGW.LAN file did not load.Action:  See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. When more memory is available, reload MACIPXGW. 4: Error error_code creating thread.MACIPXGWExplanation: MACIPXGW could not create the send thread. This usually occurs when the server is very low on memory or numerous NLMs are overloading the server.Action:  See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. When more memory is available, reload MACIPXGW. 5: Error [error_code] starting timer.MACIPXGWExplanation: The server has insufficient memory to start the timer thread. The MACIPXGW.LAN file did not load.Action:  See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. Reload MACIPXGW when more memory is available.PAGENUM=426 ID="BP420" 6: Failed to open socket.MACIPXGWExplanation: MACIPXGW failed to open a DDP socket and did not load. The server probably does not have enough available memory to support MACIPXGW.Action:  See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. When more memory is available, reload MACIPXGW.LAN. 7: Failed to initialize CLIB.MACIPXGWExplanation: The server has insufficient memory resources to load MACIPXGW.LAN. Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. When more memory is available, reload MACIPXGW. 8: Unable to open filename.MACIPXGWExplanation: The configuration file MACIPXGW.DAT exists in the SYS:SYSTEM directory; however, the IPX gateway is unable to open the file.Action:  Determine whether the volume SYS: is mounted. Check the file access. 9: Insufficient memory to read filename.MACIPXGWExplanation: The server does not have enough available memory to read the MACIPXGW.DAT configuration file.Action:  See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. When more memory is available, reload MACIPXGW.10: Warning: Failed to add IPX's protocol ID.MACIPXGWExplanation: The MACIPXGW could not add the IPX protocol ID to the protocol list of the MACIPX gateway media. This is an internal error. Action: Contact your Novell Authorized Reseller. 100: Bad command line parameter.MACIPXGWExplanation: The LOAD MACIPXGW command contains an invalid parameter.Action:  Use INETCFG to configure MACIPXGW to prevent invalid command lines. If you do not use INETCFG, manually correct the command line.101: Incomplete command line parameter.MACIPXGWExplanation: The LOAD MACIPXGW command contains an incomplete parameter.Action:  Use INETCFG to configure MACIPXGW to prevent invalid command lines. If you do not use INETCFG, manually correct the command line.PAGENUM=427 ID="BP421" 102: Board name is too long and was truncated board_name.MACIPXGWExplanation: The board name given on the load line was too long so the gateway truncated it to the maximum of 17 characters.Action: No action is required; however, you should use INETCFG update the configuration to the correct name. See "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference. 103: Gateway name must be delimited by double quotes.MACIPXGWExplanation: The name for the gateway, specified with the GATEWAY_NAME parameter on the LOAD MACIPXGW command line, lacks the necessary double quotes. Action: Use INETCFG to configure MACIPXGW.LAN. It will assure the gateway name is valid. See "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference. If you do not use INETCFG you must correct the gateway name on the command line and reload MACIPXGW.LAN. 104: Gateway name truncated to 32 characters. MACIPXGWExplanation: The gateway name that was specified with the GATEWAY_NAME parameter on the LOAD MACIPXGW command line exceeded the 32-character limit. Action: No action is required; however, you should update the configuration to reflect the correct gateway name.105: Failed processing entry entry in filename. MACIPXGWExplanation: A bad entry is found in the configuration file MACIPXGW.DAT. Action: Use INETCFG to configure MACIPXGW.LAN. INETCFG will not allow duplicate or overlapping network numbers. See "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference. After correcting the configuration, reload MACIPXGW. 106: Duplicate or overlapping net numbers in filename. MACIPXGWExplanation: There are duplicate or overlapping network numbers specified in the gateway configuration file. Action: Use INETCFG to configure MACIPXGW.LAN. INETCFG does not allow duplicate or overlapping network numbers. See "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities Reference. After correcting the configuration, reload MACIPXGW.PAGENUM=428 ID="BP422"110: MACIPXGW: Unloading MACIPXGW.LAN because of incorrect AppleTalk API version major_version.minor_version, version 2.0 expected.MACIPXGWExplanation: The version of APPLETLK.NLM did not match the one expected by MACIPXGW. Action: Record the version numbers of APPLETLK.NLM and ADSP.NLM files and contact your Novell Authorized Reseller. 111: Failed to get AppleTalk information.MACIPXGWExplanation: MACIPXGW could not obtain information about the AppleTalk interface on which the AppleTalk stack is homed. This information is required to advertise the MACIPX gateway with the AppleTalk Name Binding Protocol. The AppleTalk stack must be homed on the internal network or on one of the bound AppleTalk interfaces.Action:  Determine whether APPLETLK.NLM loaded without error and whether the interfaces are initialized successfully. Load INETCFG or ATCON to review the AppleTalk configuration. See "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" or "BOOK="utlrfenu" COLLECTION="nw41"ATCON"in Utilities Reference.112: Failed to find zone for gateway.MACIPXGWExplanation: The gateway is unable to find the AppleTalk zone in which the IPX gateway should be registered.Action:  Make sure the APPLETLK.NLM was loaded successfully. Make sure that the zone lists for AppleTalk's interfaces were initialized successfully. 113: Failed to build NBP entry for gateway.MACIPXGWExplanation: The gateway could not build an NBP entry for itself. The zone list for AppleTalk's interfaces may not have initialized successfully or the volume SYS: may not be mounted. If the volume SYS: is not mounted, the IPX gateway may fail to get the local server or router name required to build its NBP name.Action: Load ATCON to determine whether the zone lists for AppleTalk's interfaces were initialized successfully. See "BOOK="utlrfenu" COLLECTION="nw41"ATCON" in Utilities Reference. Make sure that volume SYS: is mounted. 114: Failed to register gateway with NBP.MACIPXGWExplanation: Another NVE (network-visible entity) with the same name may be on the network, or the gateway may have lost its connection to AppleTalk. Action: Load ATCON and check for a duplicate NVE on the network. See "BOOK="utlrfenu" COLLECTION="nw41"ATCON" in Utilities Reference. If there is a duplicated name, load INETCFG and change the gateway name in the MACIPXGW configuration. See "BOOK="utlrfenu" COLLECTION="nw41"INETCFG" in Utilities ReferencePAGENUM=429 ID="BP423". (If you are not using INETCFG, change the NAME parameter on the LOAD MACIPXGW command line.) Reinitialize the server or reload MACIPXGW. If there is no duplicated name, try unloading the gateway and, if necessary, APPLETLK.NLM, and then reload these NLM files again. 200: MACIPXGW: Fatal error error_code! MACIPXGW.LAN is no longer functional. Please unload the module. MACIPXGWExplanation: MACIPXGW encountered a STREAM error while attempting to receive an AppleTalk packet. The server has removed itself from the IPX network and closed the DDP socket it was using so that the server will no longer process any incoming or outgoing packets. Action: Unload MACIPXGW.LAN and reload it to use it again. 201: Unable to allocate ECB.MACIPXGWExplanation: MACIPXGW could not allocate an ECB needed to deliver data to IPX.Action: If this problem persists, see "BOOK="superenu" COLLECTION="nw41"Resolving Event Control Block Allocation Errors" in Supervising the Network.202: Failed to send AppleTalk packet, error [error_code].MACIPXGWExplanation: The gateway may have lost its connection with AppleTalk.Action: If the problem persists, unload MACIPXGW.LAN and, if necessary, unload APPLETLK.NLM. Then reload these NLM files. 203: Failed to receive AppleTalk packet, error [error_code].MACIPXGWExplanation: The gateway is unable to get AppleTalk packets from the AppleTalk stack. Either the gateway has lost its connection to AppleTalk or there are insufficient server resources available.Action: If the problem persists, unload MACIPXGW.LAN and, if necessary, unload APPLETLK.NLM. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. When more memory is available, reload MACIPXGW. 204: IPX packet too big.MACIPXGWExplanation: An IPX packet sent by the server exceeds 586 bytes, the maximum specified for encapsulating IPX in AppleTalk.Action: MACIPXGW cannot support the application on the server if the application's NLM file generates IPX packets greater than 586 bytes. Review the configuration parameters for the applications that impact the maximum packet size.PAGENUM=430 ID="BP424" 205: Unknown option number in received encapsulated packet.MACIPXGWExplanation: The gateway received an AppleTalk packet addressed to the encapsulation socket; however, an unknown option was found in the packet. This is probably caused by a misbehaving client. Action: Take a packet trace and try to locate the packet originator.PAGENUM=431 ID="BP425"MacNCPMessages for this module are in "BOOK="macclenu" COLLECTION="nw41"Error Messages" in Using MacNDS Client for NetWare 4. After going to the chapter in the book, type MACNCP in the search field and press <Enter>.PAGENUM=432 ID="BP426"MacNCP Control PanelMessages for this module are in "BOOK="macclenu" COLLECTION="nw41"Error Messages" in Using MacNDS Client for NetWare 4. After going to the chapter in the book, type MACNCP Control Panel in the search field and press <Enter>.PAGENUM=433 ID="BP427"MacNDS Client Installer Messages for this module are in "BOOK="macclenu" COLLECTION="nw41"Error Messages" in Using MacNDS Client for NetWare 4. After going to the chapter in the book, type Installer Errors in the search field and press <Enter>.PAGENUM=434 ID="BP428"MacNDS Client DS Login MenuMessages for this module are in "BOOK="macclenu" COLLECTION="nw41"Error Messages" in Using MacNDS Client for NetWare 4. After going to the chapter in the book, type UAM and DS Login Errors in the search field and press <Enter>.PAGENUM=435 ID="BP429"MAP100: Access to the server was denied.MAPExplanation: The user incorrectly entered the username, the password, or both; or the user tried to attach to a server on which the user is not defined as a user.Action: When the utility requests login information, type the username and password correctly. A user can attach to most servers as GUEST since user GUEST seldom requires a password.115: Drive letter: is mapped to a bad directory handle. Try remapping it.MAPExplanation: The user tried to delete a drive that had a bad directory handle. This usually occurs because someone has removed the directory with the DOS RD command, and the user still had a mapping to that directory.Action: If MAP DEL does not remove the drive, try remapping it to another area; then delete it. For example, ifFORMAT="LINESPECIFIC"MOREINFO="NONE"S4:= T:. [SERVER\SYS: \TOOLS] and someone deleted the TOOLS directory, try the following:FORMAT="LINESPECIFIC"MOREINFO="NONE"> MAP DEL T: 
Drive T: is used by the following search mapping: 
SEARCH4 
Do you still want to change it? (Y/N) Y 
Error: drive T: is mapped to a bad directory handle. Try remapping it. 
The mapping for drive T: was NOT deleted. 
> MAP T:=SERVER\SYS: 
Drive T is in use as a search drive. 
Do you want to reassign this search drive? (Y/N) Y 
Drive T: = SERVER\SYS: \ Then to delete it, do the following:FORMAT="LINESPECIFIC"MOREINFO="NONE"> MAP DEL T: 
Drive T: is used by the following search mapping: 
SEARCH4 
Do you still want to change it? (Y/N) Y 
The mapping for drive T: has been deleted. 
PAGENUM=436 ID="BP430"For information, see "BOOK="utlrfenu" COLLECTION="nw41"MAP" in Utilities Reference.130: Access has been denied and you have been logged out.MAPExplanation: The user tried to map a drive to a server to which the user was not already logged in. An invalid username or password may have been used.Action: Retry with a valid username and password.140: This account has expired or been disabled by the supervisor.MAPExplanation: This message could be displayed for one of the following reasons:MARK=BULLETThe user's account has expired. The network supervisor can limit a user's account to a specific period, after which the account expires and is no longer accessible.The account has been disabled. The network supervisor can disable a user's account.The user did not type the password correctly. The network supervisor can limit the number of failed attempts to log in to an account. For example, if the maximum number of failed login attempts for an account is three, and the user types the password incorrectly on four attempts, the operating system considers the user an intruder and disables the account.Action: Enable the user's account.150: You could not be authenticated to server name.MAPExplanation: The user tried to map a drive to a Volume object off of the Directory tree to which the user was not already logged in. An invalid username or password may have been used.Action: Retry with a valid username and password.195: Directory [name] cannot be located.MAPExplanation: The user used an invalid directory name with either an INCLUDE command or a MAP command. If this error occurs during login, the incorrect INCLUDE or MAP command is located in the login script.Action: Do one or both of the following:MARK=BULLETIf the error occurs at the network prompt, use the LISTDIR command or the FILER utility to examine the directory structure; then make sure all directory names in the MAP command are typed correctly.If the message appears during login, use the SYSCON utility to access the login script and to modify the INCLUDE or MAP command.PAGENUM=437 ID="BP431"200: This utility cannot change local drives.MAPExplanation: A MAP CHANGE command was issued that referenced a local drive. Local drives cannot be changed to or from search drives using the MAP command.Action: Do not try to change a local drive to a search drive. To make a local drive a search drive use the SET PATH= DOS command. For information on the PATH= environment variable, see the DOS user guide.215: The source drive was not defined. MAP cannot complete this operation.MAPExplanation: The user tried to map an existing network drive to a network drive that is not yet defined.Action: Reverse the order of the drives in the command. For example, if drive F: is an existing network drive and the user wants to map drive F: to drive G: (an undefined drive), use the following command format:FORMAT="LINESPECIFIC"MOREINFO="NONE"MAP G:=F: For information on the MAP command syntax, see "BOOK="utlrfenu" COLLECTION="nw41"MAP" in Utilities Reference.260: You have reached the maximum number of server attachments.MAPExplanation: Each NetWare server has a limited number of connection slots. A NetWare server can be configured in various configurations (for example, 1000 user, 250 user, 10 user, etc.). The server has filled all of its connection slots.Action: Try again after a user has logged out of the server.287: This utility could not find the preferred server.MAPExplanation: An internal problem may have occurred.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.295: This utility could not create a context.MAPExplanation: MAP unsuccessfully tried to allocate a context handle. Either you entered the name context in the NET.CFG file incorrectly, or the workstation does not have enough memory to set up the context.Action: Check your NET.CFG file for the correct name context. If you suspect insufficient workstation memory, see "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network.PAGENUM=438 ID="BP432"400: You attempted to map a network drive to an unmapped drive or to a local drive.MAPExplanation: The path from the command line was either to a local drive or was an invalid network drive (a drive that does not exist on the server).Action: Use the SUBST DOS command instead. If the user is trying to map to a network drive, verify that the path exists and that the user has access to it; then try the mapping again.410: The supervisor has disabled the login function for this server.MAPExplanation: The user account on the server is locked. The network supervisor can disable the login function temporarily to prevent users from logging in or from attaching to the server during system maintenance. Most likely the network supervisor is doing maintenance work on the server.Action: This condition is usually temporary. Try to log in to the server after the login function has been enabled. If the user is using CAPTURE or NPRINT, attach to another server and use its printer.430: The following drive mapping operation could not be completed: [mapping].MAPExplanation: An unexpected error occurred during a mapping attempt.Action: Usually this is an indication of an invalid drive being mapped or of a command being mistyped. Try the command again to verify that the specified drive and path exist. If this does not work, contact your Novell Authorized Reseller to get information on the error.440: The operation was attempted on an invalid drive.MAPExplanation: The user tried to map a drive to a path that is invalid or not locatable. This error message may appear if the user tried to map to a local drive.Action: Verify the existence of the path specified and be sure that it does not map to a local drive; then try the mapping again.500: You do not have an account balance. This server charges for file services.MAPExplanation: The user does not have an account on this server.Action: Create an account for the user or reestablish a previous account.520: You have exceeded your credit limit for this server.MAPExplanation: MAP denied the user access to the server because the user has no more credit on the server.Action: Give the user more credit using NETADMIN.PAGENUM=439 ID="BP433"550: The maximum number of connections allowed on this server has been reached. Wait until another user logs out.MAPExplanation: Each NetWare server has a limited number of connection slots. A NetWare 2.1x server can have up to 100 users connected. A NetWare 3 server can have up to 250 users connected.Action: Try again after a user has logged out of the server.580: Your password has expired and all grace logins have been used.MAPExplanation: The user account is locked because the user did not change the expired password. The network supervisor can limit the number of times a user can log in with an expired password.Action: Ask the network supervisor or the workgroup manager to unlock the account.610: The server did not respond.MAPExplanation: The user tried to attach to the NetWare server, but the server did not respond for one of the following reasons:MARK=BULLETThe server lost power or was shut off before the DOWN command was issued.A broken or loose connection exists on the internetwork between this server and the server the user tried to attach to.When a NetWare server is brought down with the DOWN command, that command sends a message to all other servers on the internetwork to inform them that the NetWare server is no longer active on the internetwork. However, if a NetWare server is shut off before the DOWN command is issued, all other servers assume that the NetWare server is still on the internetwork, even though it is not. In this situation, the NetWare server name still appears with the SLIST command, even though that server is no longer active on the internetwork.The NetWare server can be seen with SLIST up to 15 minutes after it has lost its power, or abends. This error message appears if a user tries to log in to or issue a command on the NetWare server.Action: Try the command again when the NetWare server has been brought back up.640: Server name is part of domain name. This version of MAP is not a NetWare Name Service utility and cannot synchronize passwords in a domain. Use the NetWare Name Service utility SETPASS to change your password.MAPExplanation: The workstation is using a version of MAP that does not support NetWare Name Services. The passwords in a domain cannot be synchronized with this MAP version.Action: Use a version of SETPASS that supports NetWare Name Services to change the password.PAGENUM=440 ID="BP434"680: The search drive command is not supported in OS/2.MAPExplanation: The user used a command not supported by OS/2.Action: None. This message is for information only.690: There is no room to expand the path environment variable with the mapping: [name].MAPExplanation: This error occurs when a user tries to map a search drive. LOGIN could not add the variable to the local path environment variable. LOGIN attempts to update the master environment and, upon successful completion, attempts to update its own local environment. The workstation probably does not have enough available memory to allocate the new variables.Action: "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network. (Adding more than 640 KB will not help, because 640 KB is the maximum that can be used.This is not a serious error; however, you cannot access those search drives (that came back with this error) as search drives until login has been completed. These drives are mapped as regular drives, and because they were successfully placed in the master environment, they can become search drives once login has been completed.710: The password could not be changed. (code)MAPExplanation: MAP could not change the password.Action: Contact your Novell Authorized Reseller. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A.830: You are trying to log in to too many stations simultaneously. The supervisor has limited the number of active connections you may have.MAPExplanation: The user could not log in for one of the following reasons:MARK=BULLETThe user could not log in to the NetWare server because the user is already logged in from the maximum number of workstations allowed. The network supervisor can limit the maximum number of workstations from which the user can log in. In this case, the user has used the maximum number. Log out of a workstation before logging in from another workstation.PAGENUM=441 ID="BP435"The user could not log in to the user account because the account is currently being used by the maximum number of users allowed. Wait for someone to log out from this account before you log in. The network supervisor can limit the number of users who can be concurrently logged in to a user account. For example, the supervisor can limit the GUEST account to a maximum of five concurrent connections.Action: In either case, the account the user is trying to log in to is already being accessed by the maximum number of workstations or users. Another user must log out from the account before this user can log in.850: You are trying to log in from an unauthorized station. The supervisor has limited the stations you are allowed to log in from.MAPExplanation: The user tried to access an account from an unauthorized workstation. A network supervisor can restrict an account to one or more particular workstations from which users can access the account.Action: Use only authorized workstations to access the account.860: You are trying to login during an unauthorized time period. The supervisor has limited the time period during which you can log in to this server.MAPExplanation: The network supervisor has set specific time periods when the user can use the server. The user cannot use the server until the next authorized time period.Action: Notify the user of the restricted time periods.870: An unknown error was returned during MAP's attempt to attach. (code)MAPExplanation: An error occurred that the operating system cannot identify. The error number is identified by code. This usually indicates that the server is servicing the maximum number of logged-in users it can accommodate with its memory.Action: Ask some users to log out. If the error persists, record the error value and contact your Novell Authorized Reseller. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 890: The specified server is unknown.MAPExplanation: The user mistyped the name of the server, specified a server that is not on the network, or specified a server that is down.Action: Use NLIST or NETADMIN to list the servers that the station recognizes. Type the name of the server correctly. If the server is down, try the command when the server has been brought back up. If the problem persists, contact your Novell Authorized Reseller.903: The command line syntax is invalid. For help, type MAP /?MAPAction: See message IDREF="FM18860""903: The command line syntax is invalid." in Appendix C.PAGENUM=442 ID="BP436"905: This utility was unable to initialize the country information.MAPAction: See message IDREF="FM55337""905: This utility was unable to initialize the country information." in Appendix C.915: The specified volume does not exist.MAPAction: See message IDREF="FM46881""915: The specified volume does not exist." in Appendix C.919: This utility could not create a connection list.  Error <code>.MAPAction: See message IDREF="FM68419""919: This utility could not create a connection list. Error code." in Appendix C.920: This utility does not have enough memory available.MAPAction: See message IDREF="FM30331""920: This utility was unable to allocate number bytes of memory." in Appendix C.921: Either the supervisor has locked the bindery or volume SYS: is not mounted.MAPAction: See message IDREF="FM49837""921: Either the supervisor has locked the bindery or volume SYS: is not mounted." in Appendix C.922: Intruder detection lockout has disabled this account.MAPAction: See message IDREF="FM49837""921: Either the supervisor has locked the bindery or volume SYS: is not mounted." in Appendix C.923: An unexpected error has occurred. Error code: <code>.MAPAction: See message IDREF="FM30182""923: An unexpected error has occurred. Error code: code." in Appendix C.924: All drives are in use.MAPAction: See message IDREF="FM81823""924: All drives are in use." in Appendix C.925: The server specified is a Personal NetWare server. You cannot attach to a Personal NetWare server with this utility. Use the Personal NetWare utilities to access this connection.MAPAction: See message IDREF="FM67645""925: The server specified is a Personal NetWare server. You cannot attach to a Personal NetWare server with this utility. Use the Personal NetWare utilities to access this connection." in Appendix C.PAGENUM=443 ID="BP437"970: The attempt to open the Unicode table files failed.MAPAction: See message IDREF="FM15675""970: The attempt to open the Unicode table files failed." in Appendix C.971: The workstation does not have enough memory to load the Unicode table files.MAPAction: See message IDREF="FM55341""971: The workstation does not have enough memory to load the Unicode table files." in Appendix C.972: Access to the Unicode table files was denied.MAPAction: See message IDREF="FM90152""972: Access to the Unicode table files was denied." in Appendix C.973: The Unicode table files cannot be found in the NLS directory or in the search path. Code page: <number>  Country:  <number>MAPAction: See message IDREF="FM62778""973: The Unicode table files cannot be found in the NLS directory or in the search path. Code page: number Country: number" in Appendix C.974: The Unicode table files are corrupt.MAPAction: See message IDREF="FM63405""974: The Unicode table files are corrupt." in Appendix C.975: The Unicode table files cannot be opened because there are already too many open files. Close some files or modify your CONFIG.SYS file.MAPAction: See message IDREF="FM49793""975: The Unicode table files cannot be opened because there are already too many open files. Close some files or modify your CONFIG.SYS file." in Appendix C.998: The message file found (<utility_name>.MSG) is an incorrect version. The correct version is <number>. See your network supervisor for assistance.MAPAction: See message IDREF="FM91957""998: The message file found (utility_name.MSG) is an incorrect version. The correct version is number. See your network supervisor for assistance." in Appendix C.999: The message file for this utility cannot be found.MAPAction: See message IDREF="FM69424""999: The message file for this utility cannot be found." in Appendix C.2030: The password for user name on server name has expired.MAPPAGENUM=444 ID="BP438"Explanation: The user's account is locked because the password has expired. The network supervisor can require periodic password changes for accounts to protect them from access by unauthorized persons. The network supervisor can assign a grace period during which users can still use their recently expired passwords before having to choose new ones. The user has exceeded the grace period.Action: Use the SETPASS command to change the password. Whenever a user is notified that a password has expired, it must be changed before the grace period ends. If it is not, the network supervisor must change it for the user.2032: The password for user name has expired.MAPExplanation: The user's account is locked because the password has expired. The network supervisor can require periodic password changes for accounts to protect them from access by unauthorized persons. The network supervisor can assign a grace period during which users can still use their recently expired passwords before having to choose new ones. The user has exceeded the grace period.Action: Use the SETPASS command to change the password. Whenever a user is notified that a password has expired, it must be changed before the grace period ends. If it is not, the network supervisor must change it for the user.2040: This is your last chance to change your password. You have no grace logins remaining.MAPExplanation: If the user does not change the password during this session, the user will not be able to log in next session.Action: Change the password.2050: The new password was retyped incorrectly.MAPExplanation: The password typed the second time was different from the password typed initially.Action: Try again.2070: The new password has been used previously.MAPExplanation: The user tried to change the password to one the user had used previously. The network supervisor can require periodic password changes for accounts to protect them from access by unauthorized persons. The network supervisor can restrict users from changing their passwords back to words they have used before.Action: Ask the user to select a password that has not already been used with this account.2080: The new password is too short.MAPExplanation: Passwords on this server are required to be a certain minimum number of characters to be valid. You entered a password that is too short.Action: Use a longer password.PAGENUM=445 ID="BP439"MHSMHS-4.10 system messages are displayed on the screen and posted in the event log file \MHS\SYS\MHSLOG.TXT. 100: Routing initialization: Unable to get more memory. MHS_error_reason.MHSExplanation: The MHS router module could not allocate enough memory during startup. This condition will cause MHS to unload immediately. Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.105: Routing initialization: Unable to create semaphore. MHS_error_reason.MHSExplanation: The MHS router module could not allocate a NetWare system resource during startup. This condition will cause MHS to unload immediately.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.110: Routing initialization: NetWare Directory Service connect failed. MHS_error_reason.MHSExplanation: The MHS router module could not establish a conversation with NetWare Directory Services during startup. This condition will cause MHS to unload immediately.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.115: Routing initialization: NetWare Directory Service NCP server  lookup failed `local_NetWare_server_name'. MHS_error_reason.MHSExplanation: The MHS router module could not read some NetWare Directory Services attributes for the NCP server during startup.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.120: Routing message: Unable to access message in message storage `message_filename'. MHS_error_reason.MHSExplanation: The MHS router is having problems reading or writing to the specified message file. MHS will try to route the message again at a later time. If the problem persists, MHS discards the message and sends a nondelivery notification to the message sender.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.PAGENUM=446 ID="BP440"125: Routing message: Hop count check failed. MHS_error_reason.MHSExplanation: MHS determines how many MHS servers a message has been routed between. If the number exceeds the configured limit, MHS discards the message and sends a nondelivery notification to the message sender. This check ensures that a message does not bounce from server to server, forever. Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.130: Routing message: Unable to get more memory `message_filename'. MHS_error_reason.MHSExplanation: The MHS router module could not allocate enough memory while routing the message. MHS will route the message again at a later time. If the problem persists, MHS discards the message and sends a nondelivery notification to the message sender.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.135: Routing recipient: Address recognition failure. `recipient_name'. MHS_error_reason.MHSExplanation: The MHS router module could not recognize the recipient's address. The address is for another messaging system, or it does not conform to the SMF-71 format. MHS will route the message to the rest of the recipients and send a nondelivery notification about this recipient to the message sender.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.140: Routing recipient: NetWare Directory Services lookup failed `recipient_name'. MHS_error_reason.MHSExplanation: The MHS router module could not find the specified message recipient in the NetWare Directory Services database. MHS will route the message to the rest of the recipients and send a nondelivery notification about this recipient to the message sender.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.145: Routing recipient: Unable to expand distribution list `distribution_list_name'. MHS_error_reason.MHSExplanation: The MHS router module could not identify all the members of the specified distribution list (so that it could route a message to them). MHS will route the message to the rest of the recipients and send a nondelivery notification about this recipient to the message sender.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.PAGENUM=447 ID="BP441"150: Routing recipient: Configuration incomplete `recipient_name'. MHS_error_reason.MHSExplanation: The MHS router module could not read the mailbox ID or location of the specified message recipient. This error probably occurred because the configuration information for them in the NDS database is incomplete. MHS will route the message to the rest of the recipients and send a nondelivery notification about this recipient to the message sender.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.155: Routing recipient: Unable to find message spooling area `remote_messaging_server_name'. MHS_error_reason.MHSExplanation: MHS holds messages for delivery to remote servers in a spooling area in the \MHS\STORE\QUEUES directory. The directory contains one file for each remote server, and the filename begins with the first few characters. The MHS router module could not find a message spooling area for the specified remote messaging server. MHS will route the message to the rest of the recipients and send a nondelivery notification about this recipient to the message sender.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.160: Routing recipient: Unable to get more memory `recipient_name'. MHS_error_reason.MHSExplanation: The MHS router module could not allocate enough memory while routing the message to the specified recipient. MHS will route the entire message again at a later time. If the problem persists, MHS will discard the message and send a nondelivery notification to the message sender.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.165: Finding remote servers: NetWare Directory Services Message Routing Group lookup failed `messaging_pipeline_name'. MHS_error_reason.MHSExplanation: The MHS router module could not access the specified Message Routing Group object in the Directory database. If MHS is just starting, this condition will cause MHS to unload immediately. If MHS has already been running for a time, the error will be ignored, but MHS will not be able to refresh its list of messaging servers that are members of the Message Routing Group.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.PAGENUM=448 ID="BP442"170: Finding remote servers: NetWare Directory Services message server lookup failed `messaging_server_name'. MHS_error_reason.MHSExplanation: The MHS router module could not access the specified messaging Server object in the NetWare Directory Services database. If MHS is just starting, this condition will cause MHS to unload immediately. If MHS has already been running for a time, the error will be ignored; however, MHS will not be able to refresh its information on the specified messaging server. MHS will discontinue searching for remote servers.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.175: Finding remote servers: Unable to create message spooling area `messaging_server_name'. MHS_error_reason.MHSExplanation: MHS holds messages for delivery to remote servers in a spooling area in the \MHS\STORE\QUEUES directory. The directory contains one file for each remote server, and the filename begins with the first few characters. The MHS router module could not create a message spooling area for the specified messaging server. MHS will not be able to route messages to this server, and MHS will discontinue searching for remote servers. If MHS is just starting, this condition will cause MHS to unload immediately.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.180: Finding remote servers: Unable to get more memory `messaging_server_name'. MHS_error_reason.MHSExplanation: The MHS router module could not allocate enough memory while finding servers belonging to the same Message Routing Group as the local messaging server. If MHS is just starting, this condition will cause MHS to unload immediately.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.185: Message spooling: Unable to spool message to remote server `remote_messaging_server_name'. MHS_error_reason.MHSExplanation: MHS holds messages for delivery to remote servers in a spooling area in the \MHS\STORE\QUEUES directory. The directory contains one file for each remote server, and the filename begins with the first few characters. The MHS router could not put a message in the specified remote messaging server's message spooling area. MHS will try to route the message again at a later time. If the problem persists, MHS will discard the message and send a nondelivery notification to the message sender.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.PAGENUM=449 ID="BP443"190: Message spooling: Unable to spool message notification `message_filename'. MHS_error_reason.MHSExplanation: MHS holds message delivery and nondelivery notifications in a message spooling area until it is ready to route these notifications to the original sender of a message. This spooling area consists of a file named REPORT.QUE in the \MHS\STORE\QUEUES directory. The MHS router module could not spool a nondelivery notification to the notification message spooling area.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.195: Message Rerouting: Unable to access message in message storage. `message_filename'. MHS_error_reason.MHSExplanation: Messages submitted to MHS are temporarily stored in an internal message file in the \MHS\STORE directory, while they are being processed. The MHS router is having problems reading or writing to the specified internal message file while verifying the recipient mailbox IDs and locations for the message. MHS will try to route the message again at a later time. If the problem persists, MHS will discard the message and send a nondelivery notification to the message sender.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.205: Message Retry: Unable to access message in message storage. `message_filename'. MHS_error_reason.MHSExplanation: Messages submitted to MHS are temporarily stored in an internal message file in the \MHS\STORE directory while they are being processed. The MHS router is having problems reading or writing to the specified internal message file while retrying to route a message. MHS will try to route the message again at a later time. If the problem persists, MHS will discard the message and send a notification to the message sender.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.210: Inbound Initialization: NetWare Directory Service connection failed. MHS_error_reason.MHSExplanation: The MHS message pickup/transfer-in module could not establish a connection with NetWare Directory Services during startup. This condition will cause MHS to unload immediately. Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.PAGENUM=450 ID="BP444"215: Inbound Initialization: Unable to create semaphore. MHS_error_reason.MHSExplanation: The MHS message pickup/transfer-in module could not allocate a NetWare system resource during startup. This condition will cause MHS to unload immediately. Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.220: Inbound Initialization: Unable to get more memory. MHS_error_reason.MHSExplanation: The MHS message pickup/transfer-in module could not allocate enough memory during startup. This condition will cause MHS to unload immediately. Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.225: Message File Operation: Unable to access directory `directory_name'. MHS_error_reason.MHSExplanation: The MHS message pickup/transfer-in module could not access files in the specified file system directory. The MHS message pickup/transfer-in will continue to try this operation and will generate an error message each time it fails.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.230: Message File Operation: Unable to create a file in `directory_name'. MHS_error_reason.MHSExplanation: The MHS message pickup/transfer-in module could not create an internal message file in the specified file system directory. The MHS message pickup/transfer-in will continue to try this operation and will generate an error message each time it fails.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.235: Message File Operation: Unable to rename a file. `Message_filename'. MHS_error_reason.MHSExplanation: The MHS message pickup/transfer-in module could not rename a message file. The MHS message pickup/transfer-in will continue to try this operation and will generate an error message each time it fails.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.PAGENUM=451 ID="BP445"240: Message Pickup: Unable to access directory. MHS_error_reason.MHSExplanation: The MHS message pickup/transfer-in module could not access files in the specified file system directory. The MHS message pickup/transfer-in will continue to try this operation, and will generate an error message each time it fails.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.245: Message Routing: Unable to route a message `message_filename'. MHS_error_reason.MHSExplanation: The MHS message pickup/transfer-in module could not pass a message on to the MHS route module.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.250: Message Sender Validation: Unable to validate the sender `message_sender_name'. MHS_error_reason.MHSExplanation: If MHS sender validation is enabled, a message sender must be the owner of the message that is submitted to the MHS SND directory. If the sender is not the owner, the message will be discarded and a nondelivery notification will be sent to the postmaster of the local messaging server.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.255: Message Submission as Bad Message: Unable to submit the message `message_filename'. MHS_error_reason.MHSExplanation: While picking up a message, the MHS message pickup module discovered that the message did not conform to the SMF-71 format. The MHS message pickup module marked the file as "bad." The MHS message pickup module created a bad message notification but could not submit it to the internal message storage area. The original message will be left in the \MHS\MAIL\SND directory, and no more attempts will be made to generate a "Bad message" nondelivery notification.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.PAGENUM=452 ID="BP446"260: Message Submission: Unable to submit the message `message_filename'. MHS_error_reason.MHSExplanation: The MHS message pickup/transfer-in module could not submit a message to the internal message storage area. The MHS message pickup/transfer-in module will try to pick up the message again at a later time.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.265: Message Submission: Unable to create a new message in the message storage `message_filename'. MHS_error_reason.MHSExplanation: The MHS message pickup/transfer-in module could not create a message in the internal message storage area. The MHS message pickup/transfer-in module will try to pick up the message again at a later time.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.285: Delivery Expiration: Unable to create a new message in the message storage `message_filename'. MHS_error_reason.MHSExplanation: The MHS delivery module was processing a message whose expiration date was reached before it could be successfully delivered. The MHS delivery module could not create a nondelivery notification for this message.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.290: Delivery Expiration: Unable to get submission-date information from message file `message_filename'. MHS_error_reason.MHSExplanation: The MHS delivery module was processing a message whose expiration date was reached before it could be successfully delivered. The module could not read the submission date from the message it was trying to generate, and the "Expiration" nondelivery notification could not be sent.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.295: Delivery Statistics: Unable to get statistics data for the message `message_filename'. MHS_error_reason.MHSPAGENUM=453 ID="BP447"Explanation: The MHS delivery module was retrieving statistical information on a message from the internal message storage area. The MHS delivery module could not retrieve the statistics for the specified message. The module will try deliver the message; however, some statistical information may be lost.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.300: Message Delivery: A NULL message retrieved for the server `message_server_name'. MHS_error_reason.MHSExplanation: The MHS delivery module retrieved an empty message from the message spooling area for the specified message server. The empty message will be discarded.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.305: Message Delivery: Unable to find mailbox for the user `Username'. MHS_error_reason.MHSExplanation: User mailboxes are implemented as subdirectories under the \MHS\MAIL\USERS subdirectory. The MHS delivery module could not find the user's mailbox. The user may have been moved or removed after the message was routed, or the access rights to the user's subdirectory may be misconfigured, or the subdirectory may not exist.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.310: Message Delivery: Unable to access the directory `directory_name'. MHS_error_reason.MHSExplanation: The MHS delivery module could not access the specified subdirectory. The remote messaging server may have been moved to a different Message Routing Group or removed from the system, or the access rights to the subdirectory may have been misconfigured, or the subdirectory may not exist.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.315: Message Delivery: Unable to access the mailbox directory `Mailbox_directory_name'. MHS_error_reason.MHSExplanation: User mailboxes are implemented as subdirectories under the \MHS\MAIL\USERS subdirectory. The MHS delivery module could not find the mailbox directory. The access rights to the mailbox subdirectory may be misconfigured, or the subdirectory may have been inadvertently deleted.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.PAGENUM=454 ID="BP448"320: Message Delivery: Unable to access the recipient `message_filename'. MHS_error_reason.MHSExplanation: While trying to deliver a message, the MHS delivery module could not read a user's name from the internal message storage.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.325: Message Delivery: Unable to create a message file in `Remote_messaging_server_and_directory_name". MHS_error_reason.MHSExplanation: The MHS delivery module was unable to create a message on a remote messaging server for message transfer purposes.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.330: Message Delivery: Unable to create a notification message. MHS_error_reason.MHSExplanation: The MHS delivery module could not create a delivery or nondelivery notification message in the internal message storage area for the message the MHS delivery module just processed.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.335: Message Delivery: Unable to defer delivery of the message `message_filename'. MHS_error_reason.MHSExplanation: The MHS delivery module could not deliver a message. MHS tried to put the message back in the message spool area for the local messaging server; however, this operation failed. The message will be lost.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.340: Message Delivery: Unable to deliver the message `message_filename'. MHS_error_reason.MHSExplanation: The MHS delivery module could not deliver a message. MHS will try to deliver the message again at a later time. If the problem persists, MHS will discard the message and send a notification to the message sender.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.PAGENUM=455 ID="BP449"345: Message Delivery: Unable to forward message for the user `Username'. MHS_error_reason.MHSExplanation: The MHS delivery module found a "Forward Message" directive in a user's mailbox. However, it could not forward the message. MHS will try to forward the message again at a later time. If the problem persists, MHS will discard the message and send a notification to the message sender.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.350: Message Delivery: Unable to open message `message_filename'. MHS_error_reason.MHSExplanation: The MHS delivery module tried to open the specified message file in the internal message storage area. This operation failed. MHS will try to deliver the message again at a later time. If the problem persists, MHS will discard the message and send a notification to the message sender.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.355: Message Delivery: Unable to open network connection to the remote server `Remote_messaging_server_name'. MHS_error_reason.MHSExplanation: The MHS delivery module tried to open a network connection to a remote server to transfer messages. This operation failed. MHS will try to transfer the messages again at a later time. If the problem persists, MHS will discard the message and send a notification to the message sender.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.360: Message Delivery: Unable to rename the file. MHS_error_reason.MHSExplanation: The MHS delivery module tried to transfer a message to a remote server. The rename operation failed. MHS will try to transfer the messages again at a later time. If the problem persists, MHS will discard the message and send a notification to the message sender.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.365: Message Rerouting: Unable to access recipient. MHS_error_reason.MHSPAGENUM=456 ID="BP450"Explanation: While trying to reroute a message, the MHS delivery module could not access a recipient's mailbox from the internal message storage. MHS will try to reroute the message again at a later time. If the problem persists, MHS will discard the message and send a notification to the message sender.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.370: Message Rerouting: Unable to create a copy of the message. MHS_error_reason.MHSExplanation: As part of rerouting a message, a copy of a message is created in the internal message storage area. The MHS delivery module could not create a copy of the message. MHS will reroute the message again at a later time. If the problem persists, MHS will discard the message and send a notification to the message sender.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.375: Message Spooling: Unable to claim the server `message_server_name'. MHS_error_reason.MHSExplanation: MHS holds messages for delivery to remote servers in a spooling area in the \MHS\STORE\QUEUES directory. The directory contains one file for each remote server, and the filename begins with the first few characters. The MHS delivery module could not deliver messages to the specified messaging server.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.380: Message Spooling: Unable to deliver message to the server `message_server_name'. MHS_error_reason.MHSExplanation: MHS holds messages for delivery to remote servers in a spooling area in the \MHS\STORE\QUEUES directory. The directory contains one file for each remote server, and the filename begins with the first few characters. The MHS delivery module tried to transfer a message to a remote server. The rename operation failed. MHS will try to transfer the messages again at a later time. If the problem persists, MHS will discard the message and send a notification to the message sender.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.385: Message Spooling: Unable to find next remote server. MHS_error_reason.MHSPAGENUM=457 ID="BP451"Explanation: MHS holds messages for delivery to remote servers in a spooling area in the \MHS\STORE\QUEUES directory. The directory contains one file for each remote server, and the filename begins with the first few characters. The MHS delivery module was trying to deliver a message to a remote server but could not find the remote server. MHS will try to find the message server again at a later time. Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.390: Message Spooling: Unable to get control information for the server `message_server_name'. MHS_error_reason.MHSExplanation: MHS holds messages for delivery to remote servers in a spooling area in the \MHS\STORE\QUEUES directory. The directory contains one file for each remote server, and the filename begins with the first few characters. The MHS delivery module found a remote server where the messages can be delivered; however, MHS could not get the messaging server's configuration information. MHS will try to deliver to this remote server again at a later time. Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.395: Message Spooling: Unable to open message list for the server `message_server_name'. MHS_error_reason.MHSExplanation: MHS holds messages for delivery to remote servers in a spooling area in the \MHS\STORE\QUEUES directory. The directory contains one file for each remote server, and the filename begins with the first few characters. The MHS delivery module found a remote server where the messages can be delivered; however, MHS could not retrieve the list of messages from the message spooling area. MHS will try to deliver to this remote server again at a later time. Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.400: Message Spooling: Unable to record statistics for the server `message_server_name'. MHS_error_reason.MHSExplanation: MHS holds messages for delivery to remote servers in a spooling area in the \MHS\STORE\QUEUES directory. The directory contains one file for each remote server, and the filename begins with the first few characters. Some statistical information may be lost but the message delivery to that server will continue.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.405: Message Spooling: Unable to release the server `message_server_name'. MHS_error_reason.MHSPAGENUM=458 ID="BP452"Explanation: MHS holds messages for delivery to remote servers in a spooling area in the \MHS\STORE\QUEUES directory. The directory contains one file for each remote server, and the filename begins with the first few characters. The MHS delivery module could not release the lock which prevents transferring multiple messages to the same server simultaneously. Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.410: Message Spooling: Unable to reroute the message `message_filename'. MHS_error_reason.MHSExplanation: MHS holds messages destined for rerouting in a message spooling area until it is ready to reroute these messages. This spooling area consists of a file named VERIFY.QUE in the \MHS\STORE\QUEUES directory. The MHS delivery module could not submit a rerouted message to the MHS Reroute message spooling area. MHS will try to reroute the message at a later time. Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.415: Message Spooling: Unable to retrieve messages for the server `message_server_name'. MHS_error_reason.MHSExplanation: MHS holds messages for delivery to remote servers in a spooling area in the \MHS\STORE\QUEUES directory. The directory contains one file for each remote server, and the filename begins with the first few characters. The MHS delivery module could not retrieve the messages from the message spooling area. MHS will try to deliver to this remote server again at a later time. Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.420: Message Spooling: Unable to set control information for the server `message_server_name'. MHS_error_reason.MHSExplanation: MHS holds messages for delivery to remote servers in a spooling area in the \MHS\STORE\QUEUES directory. The directory contains one file for each remote server, and the filename begins with the first few characters. MHS was not able to set the control information for that server's spooling area.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.425: Message Spooling: Unable to spool the notification message `message_filename'. MHS_error_reason.MHSPAGENUM=459 ID="BP453"Explanation: MHS holds messages for delivery to remote servers in a spooling area in the \MHS\STORE\QUEUES directory. The directory contains one file for each remote server, and the filename begins with the first few characters. The MHS delivery module could not submit a delivery or nondelivery notification to the notification message spooling area. The notification will be discarded.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.430: Outbound Initialization: Unable to create semaphore. MHS_error_reason.MHSExplanation: The MHS message delivery module could not allocate a NetWare system resource during startup. This condition will cause MHS to unload immediately. Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.435: Outbound Initialization: Unable to get more memory. MHS_error_reason. MHSExplanation: The MHS message pickup/transfer-in module could not allocate enough memory during startup. This condition will cause MHS to unload immediately. Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.440: Btrieve File Creation: Unable to create a temporary database file. MHS_error_reason. filenameMHSExplanation: MHS could not create the temporary file specified in filename to store extract file entries.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.445: Btrieve File Open: Unable to open the database file. MHS_error_reason. filenameMHSExplanation: MHS could not open the temporary file specified in filename to store extract file entries.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.470: Extract File Generation: Unknown container specified MHS_error_reason. NDS_container.MHSExplanation: The NDS_container value specified for the "Extract-Subtree" or "Extract-Container" parameter does not correspond to a valid container in the NDS tree.Action: Correct the value and reload MHS.NLM.PAGENUM=460 ID="BP454"480: MHSLIB.NLM is not ready. MHS_error_reason (errCode=nnnn).MHSExplanation: MHS automatically loads a secondary library NLM, MHSLIB.NLM. This library has common functions that are shared by many MHS Services-related NLM programs (such as MHSINS). MHSLIB.NLM might be unable to complete its registration with NetWare Directory Services.The actual error code is supplied in case MHS cannot correlate it with an error reason.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B. Unload the MHSLIB.NLM, and try loading MHS again. Make sure Directory Services is operating correctly. Try running DSREPAIR.485: Cannot register with MHSLIB.NLM. MHS_error_reason (errCode=nnnn).MHSExplanation: MHS automatically loads a secondary library NLM, MHSLIB.NLM. This library has common functions that are shared by many MHS Services-related NLM programs (such as MHSINS). MHS must register itself with MHSLIB.NLM at MHS startup time. The registration process is failing.The actual error code is supplied in case MHS cannot correlate it with an error reason.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.490: MHS not installed or no NDS messaging server object.MHSExplanation: At startup time, MHS searches the NetWare Directory for its local messaging server object. The local messaging server object could not be found. No error reason is available.Action: Install MHS if you have not already done so. If you think you have already installed MHS, deinstall MHS, run DSREPAIR and try to install MHS again.495: MHS volume not defined in NDS messaging server object.MHSExplanation: At startup time, MHS searches the NetWare Directory for its local messaging server object. MHS queries this object to find out the local NetWare volume on which MHS is installed. This object attribute could not be found on the local messaging server object. No error reason is available.Action: Allow time for NetWare Directory Services (NDS) to synchronize its database copies on all servers in the NDS tree. Run DSREPAIR to correct any errors. Deinstall MHS and reinstall MHS again.500: MHS volume is not mounted. MHS_error_reason (errCode=nnnn). MHSPAGENUM=461 ID="BP455"Explanation: At startup time, MHS searches the NetWare Directory for its local messaging server object. MHS queries this object to find out the local NetWare volume on which MHS is installed. MHS tries to determine if this volume is currently mounted. This error message might contain an error reason.The actual error code is supplied in case MHS cannot correlate it with an error reason. Action: If there is no error reason, mount the volume on which MHS is installed. If there is an error reason, see the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.505: Cannot process the MHS.CFG file. MHS_error_reason (errCode=nnnn).MHSExplanation: As part of MHS installation, the MHS.CFG file is created in the SYS:\SYSTEM directory. This file contains customization information for MHS. MHS cannot read this file.The actual error code is supplied in case MHS cannot correlate it with an error reason.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.510: Cannot register for NetWare O/S events. MHS_error_reason (errCode=nnnn).MHSExplanation: At startup time, MHS registers with the NetWare operating system so that MHS will be notified of critical events (low memory, low disk space, volumes being dismounted or server shutdown). MHS was not able to complete the registration with NetWare.The actual error code is supplied in case MHS cannot correlate it with an error reason.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.515: Cannot initialize the MHSLOG.TXT file. MHS_error_reason (errCode=nnnn).MHSExplanation: At startup time, MHS initializes the MHSLOG.TXT file in the \MHS\SYS directory. This file contains all the log events generated by MHS. MHS could not set up this file or run the associated event-logging software.The actual error code is supplied in case MHS cannot correlate it with an error reason.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.520: Cannot initialize message store. MHS_error_reason (errCode=nnnn).MHSExplanation: Messages submitted to MHS are temporarily stored in an internal message file in the \MHS\STORE directory. MHS could not initialize the software that handles these internal message files.The actual error code is supplied in case MHS cannot correlate it with an error reason.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.PAGENUM=462 ID="BP456"525: Cannot initialize message spooling area. MHS_error_reason (errCode=nnnn).MHSExplanation: MHS holds messages for delivery to remote servers in a spooling area in the \MHS\STORE\QUEUES directory. MHS could not initialize the software that manages the message spooling area.The actual error code is supplied in case MHS cannot correlate it with an error reason.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.530: Cannot initialize statistics. MHS_error_reason (errCode=nnnn).MHSExplanation: At startup time, MHS initializes statistics-gathering software. The STATS.TOT file in the \MHS\SYS directory contains the global message delivery statistics. Statistics for individual messaging servers are kept in the associated outbound message spooling area. MHS could not initialize the statistics-gathering files or software.The actual error code is supplied in case MHS cannot correlate it with an error reason.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.535: Cannot initialize router. MHS_error_reason (errCode=nnnn). MHSExplanation: MHS could not initialize the message-routing software.The actual error code is supplied in case MHS cannot correlate it with an error reason.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.540: Cannot login router MHS_error_reason (errCode=nnnn).MHSExplanation: The MHS router module must make some NetWare Directory Service calls to fulfill its functions. It must also obtain an authenticated local connection handle, which is needed for special NetWare Directory Service operations. The MHS router was not able to log in to NetWare Directory Services or allocate or authenticate its local connection handle.The actual error code is supplied in case MHS cannot correlate it with an error reason.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.545: Cannot initialize extract. MHS_error_reason (errCode=nnnn). MHSPAGENUM=463 ID="BP457"Explanation: At startup time, MHS initializes extract file-generation software. The extract file is located in \MHS\MAIL\PUBLIC\SMF_NS.XRT. It contains information about users with mailboxes. (The extract file is used by various MHS applications to create pop-up Address Books, which simplify addressing of messages.) MHS was not able to initialize the extract code or the extract file.The actual error code is supplied in case MHS cannot correlate it with an error reason.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.550: Cannot verify local message server group.MHS_error_reason (errCode=nnnn).MHSExplanation: At startup time, MHS obtains information from the NetWare Directory about all messaging servers belonging to the local message routing group. It uses this information to verify routes to these remote messaging servers. MHS was not able to verify the routes to these remote messaging servers or was not able to read all the information about its local messaging server object.The actual error code is supplied in case MHS cannot correlate it with an error reason.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B. If out-of-memory-errors (error code -150) keep being returned, some other server might belong to the same NetWare Directory Services tree as your server, so be sure to check the free memory status on all these servers.555: Message store repair failed. MHS_error_reason (errCode=nnnn).MHSExplanation: At startup time, MHS tries to determine whether the NetWare server crashed while MHS was running or whether the message spooling areas have been corrupted. If either of these conditions is true, MHS tries to verify the integrity of the files in the message store and message spooling areas. If MHS finds corrupted files, it tries to repair them. MHS was not able to complete the repair of these files.The actual error code is supplied in case MHS cannot correlate it with an error reason.Action: If this error message appears, you might need to contact your Novell Authorized Reseller for additional information on how to recover messages that are in the process of being delivered.See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.560: Cannot create message shadow directories. MHS_error_reason (errCode=nnnn).MHSPAGENUM=464 ID="BP458"Explanation: As part of message loss protection, MHS creates a special set of shadow subdirectories in the \MHS\STORE subdirectory. In these directories, MHS keeps copies of messages submitted for delivery (in their original form) until they have been delivered. If these directories do not exist at startup time, MHS tries to create them. MHS was not able create the shadow directories.The actual error code is supplied in case MHS cannot correlate it with an error reason.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.565: Cannot initialize message delivery. MHS_error_reason (errCode=nnnn).MHSExplanation: MHS was not able to initialize the message-delivery software. The actual error code is supplied in case MHS cannot correlate it with an error reason.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.570: Cannot initialize message pickup. MHS_error_reason (errCode=nnnn).MHSExplanation: MHS was not able to initialize the message-pickup software. The actual error code is supplied in case MHS cannot correlate it with an error reason.Action: See the applicable MHS error reason IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.PAGENUM=465 ID="BP459"MHSCONMHSCON-4.10 system messages are displayed on the screen and posted in the event log file \MHS\SYS\MHSLOG.TXT. 105: Messages: Unable to get message information. MHS_error_reasonMHSCONExplanation: MHSCON tried to get information on the currently selected message but could not obtain this information. Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.110: Messages: Unable to build message list. MHS_error_reasonMHSCONExplanation: MHSCON tried to build a list of all pending messages for the currently selected messaging server but could not build the list.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.115: Messages: Unable to return message. MHS_error_reasonMHSCONExplanation: MHSCON tried to return the selected message but could not return the message.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.120: Messages: Unable to reroute message. MHS_error_reasonMHSCONExplanation: MHSCON tried to reroute the selected message but could not reroute the message. Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.125: Messages: Unable to reroute messages. MHS_error_reasonMHSCONExplanation: MHSCON tried to reroute all messages associated with the currently selected messaging server but could not reroute the messages. Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.PAGENUM=466 ID="BP460"130: Messages: Unable to return messages. MHS_error_reasonMHSCONExplanation: MHSCON tried to return all messages associated with the currently selected messaging server but could not return all the messages. Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.135: Messages: Unable to retry messages. MHS_error_reasonMHSCONExplanation: MHSCON tried to reroute all messages associated with the currently selected messaging server to trigger MHS to transfer the message again. Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.140: Messages: Unable to get Messaging Server status. MHS_error_reasonMHSCONExplanation: MHSCON tried to obtain status information for the currently selected messaging server but could not obtain the information. Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.145: Messages: Unable to suspend/resume Messaging Server. MHS_error_reasonMHSCONExplanation: MHSCON tried to suspend or resume the transfer of messages to the currently selected messaging server but could not do the applicable task. Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.155: Messages: Unable to get Messaging Server information. MHS_error_reasonMHSCONExplanation: MHSCON tried to obtain message delivery status information for the currently selected messaging server but could not get the information. Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.160: Messages: Unable to build Messaging Server List. MHS_error_reasonMHSCONExplanation: MHSCON tried to build a list of messaging servers on the same pipeline as the local messaging server but could not build the list. Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.PAGENUM=467 ID="BP461"165: Logs: Unable to build log filter form. MHS_error_reason.MHSCONExplanation: MHSCON tried and failed to build the log filter form, probably due to lack of memory.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.170: Logs: Unable to reset the log file. MHS_error_reasonMHSCONExplanation: MHSCON tried to reset the log file but could not reset the file. Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.175: Logs: Unable to view the log file. MHS_error_reasonMHSCONExplanation: MHSCON tried to view the log file but could not view the file. Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.180: Logs: Unable to save log filter information. MHS_error_reasonMHSCONExplanation: MHSCON tried to save the current log filter settings to a disk file but could not save the information. Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.185: Log: Unable to get log filter information. MHS_error_reasonMHSCONExplanation: MHSCON tried to obtain log filter information stored on disk but could not get the information. Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.190: Statistics: Unable to get messaging server statistics. MHS_error_reasonMHSCONExplanation: MHSCON tried to get statistics for the currently selected messaging server but could not get the statistics. Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.PAGENUM=468 ID="BP462"195: Statistics: Unable to write statistics. MHS_error_reasonMHSCONExplanation: MHSCON tried to write statistics for the currently selected messaging server to a disk file but could not write the information. Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.200: Statistics: Unable to display statistics screen. MHS_error_reasonMHSCONExplanation: MHSCON tried to create a background thread for use in refreshing the statistics screen. Creation of this thread failed.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.205: Configuration: Unable to read configuration file. MHS_error_reasonMHSCONExplanation: MHSCON tried to read the configuration file MHS.CFG but could not read the file.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.210: Configuration: Unable to write to the configuration file. MHS_error_reasonMHSCONExplanation: MHSCON tried to write to the configuration file MHS.CFG but could not write to the file.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.215: Applications: Unable to get local users. MHS_error_reasonMHSCONExplanation: MHSCON queried NetWare Directory Services for all users who have a mailbox on the local messaging server but could not get the user information. Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.220: Applications: Unable to save local user data. MHS_error_reasonMHSCONExplanation: MHSCON tried to save information on the local user in the local messaging database but could not save the information.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.PAGENUM=469 ID="BP463"225: Applications: Unable to get application data. MHS_error_reasonMHSCONExplanation: MHSCON tried to read application information from the local messaging database but could not read the information.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.230: Applications: Unable to save application data. MHS_error_reasonMHSCONExplanation: MHSCON tried to write application information to the local messaging database but could not write the information. Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B235: Applications: Unable to get application data. MHS_error_reason.MHSCONExplanation: MHSCON tried and failed to read application registration information from the NETDIR.TAB file.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.240: Utility: NWSNUT internal error. MHS_error_reason.MHSCONExplanation: MHSCON performed an NWSNUT operation that resulted in an internal NWSNUT error. This error could be caused by insufficient memory.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.PAGENUM=470 ID="BP464"MHSDEINSMHSDEINS-4.10 system messages are displayed on the screen and posted in the event log file \MHS\SYS\MHSLOG.TXT. 100: Postmaster: NetWare Directory Services login failure. MHS_error_reason.MHSDEINSExplanation: MHS deinstallation tried and failed to log in to NetWare Directory Services with the name and password entered. Remember to enter the full distinguished name (preceded by a period) of a highly privileged user who is designated as the owner and administrator of the Messaging Pipeline NDS object.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.105: Unable to get more memory. MHS_error_reason.MHSDEINSExplanation: MHS deinstallation tried and failed to allocate enough RAM memory to fulfill its functions.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.110: Unable to find NDS messaging server object: `messaging_server_name'. MHS_error_reason.MHSDEINSExplanation: The messaging server object may have already been deleted (using NetWare Administrator or NETADMIN or because MHSDEINS.NLM has already been executed). Action: Make sure that at least one server that stores the NDS messaging server object is operating and that your server can communicate with it. Check for low memory and disk conditions. Run DSREPAIR.NLM and try again.See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.115: Unable to delete NDS messaging server object: `messaging_server_name'. MHS_error_reason.MHSDEINSExplanation: The user may not have the appropriate rights to delete the local messaging server object.Action: To see what the user's effective rights are in relationship to the local messaging server object, use NetWare Administrator or NETADMIN. Do the normal checks for low memory or disk conditions. Run DSREPAIR.NLM and try again.PAGENUM=471 ID="BP465"120: Unable to remove NCP server messaging attributes: `NCP_server_name'. MHS_error_reason.MHSDEINSExplanation: The user may not have the appropriate rights to modify the local NCP server object.Action: To see what the user's effective rights are in relationship to the local NCP server object, use NetWare Administrator or NETADMIN. Do the normal checks for low memory or disk conditions. Run DSREPAIR.NLM and try again.125: Unable to initialize NDS interface. MHS_error_reason.MHSDEINSExplanation: MHS deinstallation was not able to read the NDS objects it needs (such as NCP server object) to continue deinstallation.Action:  Check for low memory and disk conditions. Run DSREPAIR.NLM and try again.PAGENUM=472 ID="BP466"MHSINSMHSINS-4.10 system messages are displayed on the screen and posted in the event log file \MHS\SYS\MHSLOG.TXT. 100: MHS database: Unable to create MHS subdirectories. MHS_error_reason.MHSINSExplanation: MHS Installation could not create its subdirectory tree, starting with the subdirectory \MHS.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.105: Postmaster: NetWare Directory Services login failure. MHS_error_reason.MHSINSExplanation: MHS Installation tried and failed to log in to the NetWare Directory with the name and password entered. Remember to enter the full distinguished name of a highly privileged user who is designated as the owner and administrator of the Messaging Pipeline NDS object.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.110: MHS Routing Group: NetWare Directory Services create failure `routing_group_name'. MHS_error_reason.MHSINSExplanation: MHS Installation tried and failed to create the messaging routing group name. The messaging routing group name may already exist as a different class of object, or the postmaster may not have the appropriate rights to create the messaging routing group.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.115: MHS installation: Unable to get more memory. MHS_error_reason.MHSINSExplanation: MHS Installation could not allocate enough RAM memory to fulfill its functions.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.PAGENUM=473 ID="BP467"120: MHS database: Unable to create MHS NETDIR.TAB file. MHS_error_reason.MHSINSExplanation: MHS Installation could not create the database file \MHS\MAIL\PUBLIC\NETDIR.TAB.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.125: MHS Routing Group: Unable to grant file system rights. `routing_group_name'. MHS_error_reason.MHSINSExplanation: MHS Installation could not add the MHS Routing Group as a trustee to the necessary subdirectories in the \MHS subdirectory tree.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.130: Messaging Server: Unable to grant file system rights. `messaging_server_name'. MHS_error_reason.MHSINSExplanation: MHS Installation could not add the messaging server as a trustee to the necessary subdirectories in the \MHS subdirectory tree.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.135: [Public]: Unable to grant file system rights. `[Public]' MHS_error_reason.MHSINSExplanation: MHS Installation could not add the Netware Directory Services meta-object [Public] as a trustee to the necessary subdirectories in the \MHS subdirectory tree.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.140: Disk Volumes: NetWare Directory Services search failure. MHS_error_reason.MHSINSExplanation: MHS Installation could not find any NetWare disk volumes defined in the NetWare Directory Services database for the NetWare server on which you are installing MHS.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.PAGENUM=474 ID="BP468"145: Cannot create messaging server object: `messaging_server_name'. MHS_error_reason.MHSINSExplanation: MHS Installation tried and failed to create the messaging server name. The messaging server name may already exist as a different class of object, or the postmaster may not have the appropriate rights to create the messaging server.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.150: Cannot add postmaster to messaging server: `messaging_server_name'. MHS_error_reason.MHSINSExplanation: MHS Installation tried and failed to add the Postmaster as a member of the local NetWare Directory Services messaging server object.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.155: Cannot create mail box for Postmaster: `postmaster_name'. MHS_error_reason.MHSINSExplanation: MHS Installation tried and failed to create a set of mailbox subdirectories under the \MHS\MAIL\USER subdirectory for the postmaster (the logged-in user).Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.160: Cannot make Postmaster: `postmaster_name' MHS_error_reason.MHSINSExplanation: MHS Installation tried and failed to add the necessary Access Control List properties and Security Equivalence properties to the postmaster's NetWare Directory Services object. These properties are necessary to allow the postmaster to fulfill administrative functions.Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.Explanation: 165: Cannot add attributes to MHS Routing Group object: `routing_group_name'. MHS_error_reason.MHSINSExplanation: MHS Installation tried and failed to add the necessary Access Control List properties to the messaging routing group's NetWare Directory Service object. These properties are necessary to allow the proper access control rights for the messaging servers (which inherit the rights from the messaging routing group). Action: See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.PAGENUM=475 ID="BP469"175: Problem setting DS search confidence to high. MHS_error_reason.MHSINSExplanation: MHS Installation needs to set the search confidence to "high" so that it can more easily find newly created NetWare Directory Services objects.Action: Check for low memory and disk conditions. Run DSREPAIR.NLM and try again. See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.180: Unable to initialize NDS interface. MHS_error_reason.MHSINSExplanation: MHS Installation tried and failed to read the NetWare Directory Services objects it needs (such as NCP server object) to continue installation.Action: Check for low memory and disk conditions. Run DSREPAIR.NLM and try again. See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.185: Cannot read messaging server object: `messaging_server_name'. MHS_error_reason.MHSINSExplanation: MHS Installation tried and failed to read the messaging server object it just created. MHS installation normally needs to do this to assign file system trustee rights to the messaging server object.Action: You will be given the option to retry reading the object. Retry for at least five minutes before giving up. If the problem persists, most likely low memory or NetWare Directory Services problems exist. Check for low memory and disk conditions. Run DSREPAIR.NLM and try again.See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.190: Cannot add messaging server object to routing group: `routing_group_name'. MHS_error_reason.MHSINSExplanation: The user may not have the appropriate rights to modify the NDS routing group object.Action: To see what the user's effective rights are in relationship to the routing group object, use NetWare Administrator or NETADMIN. Do the normal checks for low memory or disk conditions. Run DSREPAIR.NLM and try again.See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.PAGENUM=476 ID="BP470"195: Cannot read Postmaster object:MHSINSExplanation: MHS Installation could not read the NDS object of the user you just logged in as. Action: You will be given the option to retry reading the object. Retry for at least five minutes before giving up. If the problem persists, most likely low memory or NetWare Directory Services problems exist. Check for low memory and disk conditions. Run DSREPAIR.NLM and try again.See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.200: Cannot read NDS public object: `[Public]'. MHS_error_reason.MHSINSExplanation: MHS Installation is not able to read the NDS meta-object [Public].Action: Check for low memory and disk conditions. Run DSREPAIR.NLM and try again. See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.205: Cannot add messaging server attributes to NCP server object: `NCP Server Name'. MHS_error_reason.MHSINSExplanation: The user may not have the appropriate rights to modify the local NCP server object.Action: To see what the user's effective rights are in relationship to the local NCP server object, use NetWare Administrator or NETADMIN. Do the normal checks for low memory or disk conditions. Run DSREPAIR.NLM and try again.See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.210: There are currently not enough free user license slots to install or operate MHS.MHSINSExplanation: To operate, MHS needs at least six free user-licensed connections.Action: Make sure the user's license is properly installed. To see how many licenses are installed, type "version" on the NetWare server console. To see how many licensed connections are currently in use, load MONITOR.NLM. See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.PAGENUM=477 ID="BP471"215: Cannot read MHS Routing Group: `routing_group_name'. MHS_error_reason.MHSINSExplanation: MHS installation tried and failed to read the routing group object (which may have been just created). MHS installation normally needs to do this to assign file system trustee rights to the routing group. Action: You will be given the option to retry reading the object. Retry for at least five minutes before giving up. If the problem persists, most likely low memory or NetWare Directory Services problems exist. Check for low memory and disk conditions. Run DSREPAIR.NLM and try again.See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.220: Cannot add attributes to messaging server object: `messaging_server_name'. MHS_error_reason.MHSINSExplanation: MHS Installation tried and failed to modify the messaging server object it just created.Action: You will be given the option to retry reading the object. Retry for at least five minutes before giving up. If the problem persists, most likely low memory or NetWare Directory Services problems exist. Check for low memory and disk conditions. Run DSREPAIR.NLM and try again.See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.225: Cannot add a trustee to file system object: `file_system_object' MHS_error_reason.MHSINSExplanation: MHS tried and failed to add trustees to a file or subdirectory. Action: Make sure the user logged in has the appropriate rights to perform these operations. Make sure the file or subdirectory exists. See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.230: MHS Routing Group search failed. MHS_error_reason (errCode=nnnn).MHSINSExplanation: An NDS error occurred while the installation program was trying to find existing MHS Routing Groups. This error occurs if the NDS database is corrupted or not upgraded to the current schema.The actual error code is supplied in case MHS cannot correlate it with an error reason.Action:  Make sure Directory Services is operating correctly. Try running DSREPAIR. See the applicable MHS error reason in IDREF="FM86922""MHS Error Reasons, Explanations, and Actions" in Appendix B.PAGENUM=478 ID="BP472"MIGRATE001: The program cannot update an account balance.MIGRATEExplanation: The program could not update a user or print server's account balance property.Action: Make sure that the workstation running the migration still has a valid connection to the network and that the destination server's bindery is not locked.002: The program cannot set up an account server.MIGRATEExplanation: While setting up accounting services for either the destination NetWare server or one of the migrated print servers, the program could not write to the bindery.Action: Make sure that the workstation running the migration still has a valid connection to the network and that the destination server's bindery is not locked.003: The program could not allocate number bytes of memory.MIGRATEExplanation: The program could not allocate workstation memory, and failed.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network.004: The program cannot add a trustee to a directory.MIGRATEExplanation: This error can occur during two phases of the migration: while creating print servers, and while writing trustee assignments to the destination server. In both cases, the program could not write trustee information to the destination server.Action: Make sure that the workstation running the migration still has a valid connection to the network and that the destination server's bindery is not locked.006: The program cannot give console operator privileges to a user or group.MIGRATEExplanation: The program could not access the bindery to make a user or group a console operator.Action: Make sure that the workstation running the migration still has a valid connection to the network and that the destination server's bindery is not locked.007: The program cannot create a directory on the destination server.MIGRATEExplanation: The program could not create either a user's home directory or a print server's working directory on the destination server.PAGENUM=479 ID="BP473"Action: Make sure that the workstation running the migration still has a valid connection to the network and that the destination server's bindery is not locked. Make sure the named directory path already exists on the destination, and make sure the user has rights to access that directory path.008: The program cannot create a file.MIGRATEExplanation: The program could not create a login script file by accessing DOS services.Action: Make sure that the workstation running the migration still has a valid connection to the network and that the destination server's bindery is not locked. Make sure that the named file exists and that the user has access rights to that file.009: The program cannot create an object.MIGRATEExplanation: The program could not create an object in the destination server's bindery.Action: Make sure that the workstation running the migration still has a valid connection to the network and that the destination server's bindery is not locked. Make sure that the destination server has enough disk space on volume SYS: to allow creation of more Bindery objects. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Disk Space Problems" in Supervising the Network.010: The program cannot create a bindery property.MIGRATEExplanation: The program could not create a bindery property for a Bindery object (such as user, group, print server, or print queue).Action: Make sure that the workstation running the migration still has a valid connection to the network and that the destination server's bindery is not locked. Make sure that the destination server has enough disk space on volume SYS: to allow the bindery to expand. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Disk Space Problems" in Supervising the Network.012: The program cannot delete a bindery property.MIGRATEExplanation: This message may occur in the following circumstances:MARK=BULLETIntruder detection is being turned off on the destination server.Accounting services is being installed on the destination server by the program.Accounting services is being deleted from the destination server by the program.The program has finished writing all users, groups, etc., and is cleaning up after itself. The program adds an extra property to each object it creates on the destination server to keep track of which objects have been migrated and which have not. As a final operation before copying data files and setting up trustee assignments, this property is deleted from the migrated objects.Action: Make sure that the workstation running the migration still has a valid connection to the network and that the destination server's bindery is not locked.PAGENUM=480 ID="BP474"013: The program cannot update the full name of a user, group, or print server.MIGRATEExplanation: The program could not write the full name of the object to the bindery.Action: Make sure that the workstation running the migration still has a valid connection to the network and that the destination server's bindery is not locked. Also, make sure that the Bindery object being updated has not been modified or deleted by another user on the network.014: The program cannot obtain the target server's name.MIGRATEExplanation: The program queries the destination server to obtain its name before proceeding with the migration. In this case, the query failed.Action: Make sure that the workstation running the migration still has a valid connection to the network and that the destination server's bindery is not locked.015: The program cannot obtain an object's bindery ID.MIGRATEExplanation: To make a trustee assignment on the destination server, the program must first obtain the Bindery object ID of the trustee. The try to obtain this ID has failed.Action: Make sure that the workstation running the migration still has a valid connection to the network and that the destination server's bindery is not locked. Also, make sure that the Bindery object being given trustee rights has not been modified or deleted by another user on the network.016: The program cannot obtain the NetWare server's date and time.MIGRATEExplanation: The program queries the destination server to obtain the date and time before proceeding with the migration. In this case, the query failed.Action: Make sure that the workstation running the migration still has a valid connection to the network and that the destination server's bindery is not locked.017: The program cannot obtain file server information.MIGRATEExplanation: The program queries the destination server to obtain its NetWare version information before proceeding with the migration. In this case, the query failed.Action: Make sure that the workstation running the migration still has a valid connection to the network and that the destination server's bindery is not locked.018: The program cannot read migration information from the intermediate file.MIGRATEExplanation: This error occurs whenever the program cannot access the intermediate file (in the working directory).PAGENUM=481 ID="BP475"Action: If the working directory is on the network, make sure that the workstation still has a valid connection to the NetWare server where the working directory is located; make sure that the intermediate file has not been locked or deleted by another network user. If the working directory is on the workstation's hard disk, check the integrity of the hard disk.019: The program cannot add a user to a group.MIGRATEExplanation: When users are created on the destination server, they are automatically added to group EVERYONE. Later, users are added to other groups to which they belonged on the source server. This message indicates that the program could not access the destination server's bindery to add a user to a group.Action: Make sure that the workstation running the migration still has a valid connection to the network and that the destination server's bindery is not locked. Also, make sure that the named user and group being updated have not been modified or deleted by another user on the network.020: The program cannot add a group to a user's list of groups.MIGRATEExplanation: Each user's Bindery object contains a property that lists the names of groups to which the user belongs. An attempt by the program to update this list in the bindery has failed.Action: Make sure that the workstation running the migration still has a valid connection to the network and that the destination server's bindery is not locked. Also, make sure that the named user and group being updated have not been modified or deleted by another user on the network.021: The program cannot install accounting on the target server.MIGRATEExplanation: This error occurs when accounting charge rates are migrated from a source server that has accounting services installed to a destination server that does not have accounting services installed. In this scenario, the program tries to install accounting on the destination server by adding a bindery property to the destination server's bindery. This message indicates that the attempt to add that property failed.Action: Make sure that the workstation running the migration still has a valid connection to the network and that the destination server's bindery is not locked.022: The program cannot give a user or group account manager privileges for another user or group.MIGRATEExplanation: To give a user or group manager rights for another Bindery object, the program must write to the destination server's bindery. This message indicates that this attempt to access the bindery failed.Action: Make sure that the workstation running the migration still has a valid connection to the network and that the destination server's bindery is not locked. Also, make sure that the Bindery object being updated has not been modified or deleted by another user on the network.PAGENUM=482 ID="BP476"023: An internal error has occurred. The program cannot convert a NetWare-style path to a UNC path.MIGRATEExplanation: To access files on the destination server, the program must convert NetWare paths so that DOS can interpret them. The naming convention that DOS understands is called the Universal Naming Convention (UNC) and has the following format:FORMAT="LINESPECIFIC"MOREINFO="NONE"\\server\volume\directory\directory While trying to convert a name from the NetWare naming convention to the UNC naming convention, the program failed.Action: Exit the utility, ensure the integrity of the workstation's memory, and run the utility again.024: The program cannot open a file.MIGRATEExplanation: The program accesses DOS services to open files on the destination server. This message indicates that the call to DOS has failed.Action: Make sure that the workstation's CONFIG.SYS file allows a sufficient number of files to be opened (for example: "FILES=20").025: The program cannot designate a user or group as an operator of a print queue or print server.MIGRATEExplanation: To designate a user or group as the operator of a print queue or print server, the program must write to the destination server's bindery. This message indicates that this bindery access has failed.Action: Make sure that the workstation running the migration still has a valid connection to the network and that the destination server's bindery is not locked. Also, make sure that the Bindery object being updated has not been modified or deleted by another user on the network.026: The program cannot read the value of a bindery property.MIGRATEExplanation: The program could not read a bindery property from the destination server.Action: Make sure that the workstation running the migration still has a valid connection to the network and that the destination server's bindery is not locked. Also, make sure that the Bindery object being read from has not been modified or deleted by another user on the network.027: The program cannot find an object in the bindery.MIGRATEPAGENUM=483 ID="BP477"Explanation: This error can occur whenever the program turns accounting services off for the destination server, or when the program is cleaning up Bindery objects it has created during the migration. The message indicates that the program could not read an object in the bindery.Action: Make sure that the workstation running the migration still has a valid connection to the network and that the destination server's bindery is not locked. Also, make sure that the Bindery object being updated has not been modified or deleted by another user on the network.028: The program cannot find a bindery property.MIGRATEExplanation: The program could not find a property for an object in the bindery.Action: Make sure that the workstation running the migration still has a valid connection to the network and that the destination server's bindery is not locked. Also, make sure that the Bindery object being updated has not been modified or deleted by another user on the network.029: The program cannot make a user security equivalent to another user or group.MIGRATEExplanation: To make a user security-equivalent to another user or group, the program must modify properties in the destination server's bindery. This message is displayed whenever the program's attempt to modify those properties fails.Action: Make sure that the workstation running the migration still has a valid connection to the network and that the destination server's bindery is not locked. Also, make sure that the Bindery object being updated has not been modified or deleted by another user on the network.030: The program cannot designate a print server to service a print queue.MIGRATEExplanation: To designate a print server to service a print queue, the program must modify properties in the destination server's bindery. This message indicates that the attempted access failed.Action: Make sure that the workstation running the migration still has a valid connection to the network and that the destination server's bindery is not locked. Also, make sure that the Bindery object being updated has not been modified or deleted by another user on the network.031: An internal error has occurred. The program cannot translate a path on the source server to its corresponding path on the destination server.MIGRATEPAGENUM=484 ID="BP478"Explanation: To translate directory path names from the source server to their corresponding location on the destination server, the program must use information supplied in the destination volume's table of the destination configuration form. This message indicates that a source path could not be translated, given the information in the destination volume's table.Action: Return to the configuration form, and make sure that the destination volume's table is properly configured.032: The program cannot designate a user or group as the user of a print queue or print server.MIGRATEExplanation: To designate a user of a print queue or print server, the program must modify properties in the destination server's bindery. This message indicates that the attempt to modify those properties failed.Action: Make sure that the workstation running the migration still has a valid connection to the network and that the destination server's bindery is not locked. Also, make sure that the Bindery object being updated has not been modified or deleted by another user on the network.033: The program cannot give workgroup manager privileges to a user or group.MIGRATEExplanation: To give workgroup manager privileges to a user or group, the program must modify properties in the destination server's bindery. This message indicates that the program could not modify those properties.Action: Make sure that the workstation running the migration still has a valid connection to the network and that the destination server's bindery is not locked. Also, make sure that the Bindery object being updated has not been modified or deleted by another user on the network.034: The program cannot write a value to a bindery property.MIGRATEExplanation: To properly set up objects created in the destination server's bindery, the program must read properties from those objects, modify them, and write them back to the bindery. This message indicates that the program could not write a modified property back to the destination server's bindery.Action: Make sure that the workstation running the migration still has a valid connection to the network and that the destination server's bindery is not locked. Also, make sure that the Bindery object being updated has not been modified or deleted by another user on the network.035: The program cannot write to a file.MIGRATEPAGENUM=485 ID="BP479"Explanation: This error can occur whenever the program is writing a file (for example, a user login script, the NEW.PWD file, printer definition files, or print server files) to the destination server. The program relies on DOS services for its file access. This message indicates that the DOS request to write to a file failed.Action: Check the integrity of the workstation's memory.036: The program cannot write a user's login control property to the bindery.MIGRATEExplanation: Each user's account restrictions are contained in what is known as the login control property. This property is modified when users are created and again when user restrictions are migrated to the destination server. This message indicates that the program could not write the modified login control property to the destination server.Action: Make sure that the workstation running the migration still has a valid connection to the network and that the destination server's bindery is not locked. Also, make sure that the Bindery object being updated has not been modified or deleted by another user on the network.037: The program cannot read a user's login control property from the bindery.MIGRATEExplanation: Each user's account restrictions are contained in what is known as the login control property. This property is modified when users are created and again when user restrictions are migrated to the destination server. This message indicates that the program could not read a user's login control property from the destination server.Action: Make sure that the workstation running the migration still has a valid connection to the network and that the destination server's bindery is not locked. Also, make sure that the Bindery object being updated has not been modified or deleted by another user on the network.038: A random password was generated for the following object, but could not be set. The password has not been recorded in the NEW.PWD file. This object will be able to log in to the network without a password.MIGRATEExplanation: The program must modify a property in the bindery to change a user or print server's password. This message indicates that the attempt to modify the bindery property failed.Action: After the migration, the network supervisor can set a password for the named Bindery object either through NETADMIN (for users) or PCONSOLE (for print servers).039: An internal error has occurred. The program cannot compress an accounting charge rate.MIGRATEExplanation: Accounting charge rates are stored in the bindery in compressed form. While trying to compress an accounting charge rate table, the program failed.Action: After the migration, the network supervisor may need to manually set up the named charge rate on the destination server.PAGENUM=486 ID="BP480"045: The program cannot create a user's mail directory.MIGRATEExplanation: The program relies upon the services of DOS for its directory services. This message indicates that an attempt to create a mail directory on the destination server failed.Action: Check the mail directory of the destination server to make sure that all mail directories of deleted users have been deleted. The failure to create the directory may have occurred because a directory by the same name already exists, in which case a new directory could not be created.046: The program cannot give a user rights to his mail directory.MIGRATEExplanation: Whenever the program creates a mail directory for a user, it grants the user a default set of trustee rights to that directory. This message indicates that the attempt to assign those rights failed.Action: After the migration, the network supervisor can manually assign rights to the named user in the named directory.047: The program cannot obtain trustee information from the target server.MIGRATEExplanation: For each trustee assignment migrated from the source server, the program reads existing trustee rights on the destination server for the translated directory path. If trustee assignments have already been made, the program combines the existing assignment with the migrated assignment to ensure that no trustee rights are lost on the destination server. This message indicates that the attempt to read existing trustee assignments from the destination server failed.Action: The previous trustee assignment will be lost if the migrated trustee rights are successfully set up on the destination server. If this occurs, the network supervisor will need to manually examine the named directory to evaluate whether or not to grant additional rights to the named user.048: The following user's account has been disabled, so a random password could not be set. When the account is enabled, the user will be able to log in without a password.MIGRATEExplanation: The bindery will not allow a password to be changed for a user whose account has been disabled. This message is displayed if a migrated user is given a random password on the destination server, but the account is disabled (because it was disabled on the source server).Action: Since the account is disabled, the user will not be able to log in, and the account is secure. However, as soon as the network supervisor enables the account, he or she must manually assign a password to the account to maintain proper security.PAGENUM=487 ID="BP481"049: The program cannot set the status of the print queue.MIGRATEExplanation: The server returned an unexpected error while trying to set the status of the print queue.Action: After the migration, the network supervisor can use PCONSOLE to manually set the printer queue status on the destination server.050: An invalid NetWare object name was used.MIGRATEExplanation: This error is probably the result of an extended ASCII character in the object name, especially if you are migrating from a LAN Server or PCLP. Action: Rename objects with names that conform to the NetWare file server naming convention. 100: The program attempted to access LAN Server network information, but the network failed to process the request. LAN Server error code: number.MIGRATEExplanation: An unexpected error has occurred on the LAN Server network, and the program is unable to complete the current operation.Action: See the LAN Server documentation for the meaning of the error code.102: You must specify a working directory before proceeding.MIGRATEExplanation: Either you did not specify a working directory, or the path you entered is invalid. This message reappears until a valid directory is specified.Action: Specify a valid path and directory name.103: An internal error has occurred. The NWParsePath() function failed with path.MIGRATEExplanation: This indicates a problem with a directory path or with the connection to the server that a path is pointing to. This usually happens when a connection has developed a problem or has been lost.Action: Restart the Migration utility.105: A memory allocation failure has occurred. Restart this utility after configuring DOS for more memory.MIGRATEExplanation: The workstation may not have enough available memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network.PAGENUM=488 ID="BP482"106: You cannot create more than 999 migration reports. Delete some reports and try again.MIGRATEExplanation: The report file uses a three-digit number in the report filename. This number is incremented with each new report, so the maximum is 999.Action: Delete some report files. (Copy them elsewhere if needed.)107: The report file cannot be opened.MIGRATEExplanation: The user may not have appropriate rights to write or modify the report file.Action: Make sure the user has access rights to the file.108: The report file cannot be written to.MIGRATEExplanation: The user may not have appropriate rights to write or modify the report file.Action: Make sure that the user has access rights to the file. If the problem persists, contact your Novell Authorized Reseller.109: No report filenames could be read from the working directory.MIGRATEExplanation: The working directory name specified is invalid.Action: Make sure that the working directory exists and that you specified the correct name for the directory.110: The report file, name, cannot be deleted.MIGRATEExplanation: The user may not have the Delete right to the report file.Action: Obtain the Delete right. If the problem persists, contact your Novell Authorized Reseller.111: You do not have enough memory to create a screen portal.MIGRATEExplanation: The workstation may not have enough available memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network.113: An internal error occurred during an attempt to display text.MIGRATEExplanation: The scrolling function used for the report file has encountered an error.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=489 ID="BP483"114: An internal error occurred during an attempt to read the report file.MIGRATEExplanation: The report file is probably corrupted.Action: Review the report file with an ASCII text editor.117: The program cannot create the intermediate file.MIGRATEExplanation: The database file for the migration cannot be created.Action: Make sure that the user has the Create right in the working directory. If the problem persists, contact your Novell Authorized Reseller.118: The program cannot write to the destination bindery.MIGRATEExplanation: The write portion of the migration has had a general failure. This could have happened because the correct message file was not found, or because the intermediate file is corrupted.Action: Make sure that the message file is current and located in SYS:PUBLIC. Reboot the workstation and try again. If the problem persists, contact your Novell Authorized Reseller.119: The migration report cannot be opened.MIGRATEExplanation: The report file cannot be opened, perhaps because the user does not have appropriate file rights, or because an invalid path to the working directory was specified.Action: Make sure that the user has file rights to the current report file. Make sure that the working directory path exists and was specified correctly.120: The intermediate file (MIGRATE.GMF) could not be opened.MIGRATEExplanation: The report file cannot be opened, perhaps because the user does not have appropriate access rights or because an invalid path to the working directory was specified.Action: Make sure that the user has access rights on the current report file. Make sure that the working directory path exists and was specified correctly.121: The program cannot get the connection ID for the destination server.MIGRATEExplanation: The shell has lost its connection to the destination server, and it needs to be reestablished.Action: Go back into the configuration form and reestablish a connection to the destination server. PAGENUM=490 ID="BP484"122: The directory path cannot be created.MIGRATEExplanation: The program tried to create a directory, but the specified directory could not be created. This may occur while specifying the program's working directory, or while specifying destination directories for data files migrated from the source server.Action: If the path is on a NetWare server, check the user rights in each directory in the path. The user needs the Create right to create subdirectories. If this is not the problem, reboot the workstation and try again. If the problem persists, contact your Novell Authorized Reseller.123: An internal error has occurred. The program cannot get the current working directory.MIGRATEExplanation: This is an internal DOS error. DOS cannot get the working directory string.Action: Reboot the workstation and try again. If the problem persists, contact your Novell Authorized Reseller.124: An internal error has occurred. The drives cannot be changed.MIGRATEExplanation: This is an internal DOS error. The drive indicated in the working directory cannot be made the current drive.Action: Reboot the workstation and try again. If the problem persists, contact your Novell Authorized Reseller.125: An internal error has occurred. The directories cannot be changed.MIGRATEExplanation: An internal DOS error has occurred preventing you from changing to the working directory.Action: Reboot the workstation and try again. If the problem persists, contact your Novell Authorized Reseller.126: An internal error has occurred. The program cannot get your effective rights.MIGRATEExplanation: An internal system error has occurred. The program could not get an Effective Rights Mask from the server for the working directory.Action: Reboot the workstation and try again. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=491 ID="BP485"127: An internal error has occurred. The program cannot get NetWare server information.MIGRATEExplanation: An internal system error has occurred. Version information could not be read from the NetWare server.Action: Reboot the workstation and try again. If the problem persists, contact your Novell Authorized Reseller.128: An internal error has occurred. Could not expand path fragment - fragment.MIGRATEExplanation: An internal system error has occurred. The path fragment shown in the message could not be expanded to a full path.Action: Reboot the workstation and try again. If the problem persists, contact your Novell Authorized Reseller.129: An internal error has occurred. The program cannot make directory name.MIGRATEExplanation: The directory cannot be created.Action: Make sure that the path string is correct. If this is not the problem, reboot the workstation and try again. If the problem persists, contact your Novell Authorized Reseller.130: The program could not allocate memory while migrating to the destination LAN.MIGRATEExplanation: The workstation may not have enough available memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network.131: The program could not allocate memory while migrating from the source LAN.MIGRATEExplanation: The workstation may not have enough available memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network.132: An internal error has occurred. The source bindery could not be read.MIGRATEExplanation: The import part of the migration failed because the bindery information could not be read.Action: Make sure that the workstation running the migration still has a valid connection to the network and that the destination server's bindery is not locked.133: A directory specified in the path was longer than the 8.3 DOS standard.MIGRATEExplanation: All directory names and filenames must conform to the DOS eight-character filename and three-character extension standard.Action: Rename files or directories that do not conform to the standard.PAGENUM=492 ID="BP486"135: The specified path points to a file, not a directory.MIGRATEExplanation: The last element in the path was a file when a directory was needed.Action: Enter a valid directory path.137: You must have the Administrative privilege in the LAN Server domain to access LAN Server network information.MIGRATEExplanation: The LAN Server user is not of the appropriate type to perform this task.Action: Exit the Migration utility; log on to the LAN Server domain as a user that has Administrative privileges, and run the utility again.138: You are not logged on to the LAN Server domain. Please log on to the LAN Server domain as a user with administrative privileges, and try again.MIGRATEExplanation: The workstation is not logged on to the LAN Server domain.Action: Exit the Migration utility; log on to the LAN Server domain as a user that has Administrative privileges, and run the utility again.140: The requester service has not been started.MIGRATEExplanation: Either the DOS LAN Requester has not been started, or it has been started with an incorrect setting for the /NMS parameter.Action: Make sure that the NET START command has been used to start the requester at the workstation. Also, make sure that this command has been issued with a non-zero setting for the /NMS parameter, either on the command line itself, or in the file DOSLAN.INI. For further information, see the DOS LAN Requester documentation.150: LAN Server network access is denied.MIGRATEExplanation: The LAN Server network refused access to the program.Action: Make sure that the workstation is logged in to the LAN Server network as a user that has Administrative privileges. Make sure that the servers in the domain are still up and operational.151: No domain controller was found on this domain.MIGRATEExplanation: The program could not locate a domain controller for the domain that the workstation is logged on to.Action: Make sure that the domain's domain controller is operational. See the LAN Server documentation.PAGENUM=493 ID="BP487"152: The server is not configured for transactions.MIGRATEExplanation: The LAN Server domain controller has not been configured to allow programs to access network information.Action: Reconfigure the server to allow the IPC resource to be shared. See the LAN Server documentation.153: OS/2: sufficient memory is not available.MIGRATEExplanation: The LAN Server server does not have enough memory to complete the requested operation.Action: See the LAN Server and OS/2 documentation to determine how to free more memory on the LAN Server server.154: The LAN Server network device driver has not been started on the workstation.MIGRATEExplanation: The LAN Server device driver must be loaded on the workstation to perform the migration.Action: Start the DOS LAN Requester on the workstation. See the LAN Server and DOS LAN Requester documentation for information.157: The Requester service has not been started.MIGRATEExplanation: The Requester service must be started on all domain servers and on the client workstation to access LAN Server network resources.Action: Make sure that the Requester service has been started on all servers in the LAN Server domain, and that the service is not paused. Make sure that the DOS LAN Requester has been properly started on the client workstation. For information, see the LAN Server and DOS LAN Requester documentation.158: The server service has not been started.MIGRATEExplanation: The server service must be started on all LAN Server servers in the domain before migration can proceed.Action: Make sure that the server service is started and not paused on all servers in the LAN Server domain. For information, see the LAN Server documentation.159: An Across the Wire migration cannot be performed from a server to itself.MIGRATEExplanation: You have specified the same server name for both the source and destination servers.Action: Be sure that the destination server name is different from the source server name.PAGENUM=494 ID="BP488"201: An internal error has occurred. The program cannot obtain the name of a Bindery object.MIGRATEExplanation: This error can occur while the program is reading relationships among objects in the bindery (for example, security equivalences, group membership, and managed users). Whenever the error occurs, the relationship between the Bindery objects is lost on the destination server. (Note that the source server's Bindery object ID of the object whose name could not be obtained is displayed with this error.)Action: After the migration, you can restore the relationships by identifying the object whose name could not be read on the source server, then manually setting up the relationship on the destination server.For example, assume that this error occurred while the program was reading the names of members of the group TOP_SECRET from the source server. This means that the user whose object ID is displayed would not appear as a member of TOP_SECRET on the destination server. Assume that the migration ran to completion in such a way that group TOP_SECRET was successfully created on the destination server. To make sure that the destination server's TOP_SECRET group had the missing user added as a member, the migrator could run SYSCON on the source server and look at the "Other Information" field of each defined user to determine which User object ID was displayed with the error message. Then, taking the name of the user that was left out of group TOP_SECRET, the migrator could change to the destination server and add the missing user to group TOP_SECRET.Note that object IDs for users and groups can be viewed with SYSCON, while object IDs for print queues and print servers can be viewed with PCONSOLE.202: The program cannot obtain the NetWare server's date and time.MIGRATEExplanation: The program could not obtain the date and time from the source NetWare server.Action: Make sure that the workstation still has a connection to the source server and that the bindery is not locked.203: The program cannot obtain NetWare server information.MIGRATEExplanation: Prior to reading trustee assignments from the source server, the program could not obtain the version information from the source NetWare server. As a result, the program is unable to translate trustee rights masks.Action: Make sure that the workstation still has a connection to the source server and that the bindery is not locked.PAGENUM=495 ID="BP489"204: The program cannot obtain the name of the NetWare server.MIGRATEExplanation: While preparing to read information from the source NetWare server, the program could not obtain the name of the server.Action: Make sure that the workstation still has a connection to the source server and that the bindery is not locked.205: The program cannot get a volume's number.MIGRATEExplanation: To obtain trustee rights masks from a volume, the program must first obtain NetWare's ID number for that volume. The attempt to obtain the volume's number has failed.Action: Make sure that the volume is mounted and that the workstation still has a connection to the source server.206: The program cannot read a user's account balance.MIGRATEExplanation: The program could not read the user's account balance property from the source server's bindery.Action: Make sure that the workstation still has a connection to the source server, that the bindery is not locked, and that the user still exists. Also, make sure that the accounting feature was not removed from the server by another user during the migration.207: The program cannot read a user's account restrictions from the bindery.MIGRATEExplanation: To get a user's account restrictions, the program must read the user's login control property from the source server's bindery. The attempt to read that property has failed.Action: Make sure that the workstation still has a connection to the source server and that the bindery is not locked. Also, make sure that the user was not deleted by another user during the migration.208: The program cannot read an accounting charge rate from the bindery.MIGRATEExplanation: To get the accounting charge rates from the source server, the program must read a series of properties from the source server object in the bindery. The program could not read one of these properties.Action: Make sure that the workstation still has a connection to the source server and that the bindery is not locked. Also, make sure that the accounting feature was not deleted by another user during the migration.PAGENUM=496 ID="BP490"209: The program cannot read the default user restrictions.MIGRATEExplanation: To obtain default user restrictions from the source server, the program must read the user defaults property from the Supervisor object in the bindery. The attempt to read this property failed.Action: Make sure that the workstation still has a connection to the source server and that the bindery is not locked. Also, use the NETADMIN utility to view the user default values to make sure that they are set up correctly; then run this Migration utility again.210: The program cannot read an object's full name from the bindery.MIGRATEExplanation: The program could not read the object's identification property from the bindery.Action: Make sure that the workstation still has a connection to the source server and that the bindery is not locked. Also, make sure that the object was not deleted by another user during the migration.211: The program cannot read the default home directory.MIGRATEExplanation: The home directory path is obtained from the home directory property of the Supervisor user in the source server's bindery. The program could not read this property.Action: Make sure that the workstation still has a connection to the source server and that the bindery is not locked.212: The program cannot read the value from a bindery property.MIGRATEExplanation: The program could not read the named property from the source server's bindery.Action: Make sure that the workstation still has a connection to the source server and that the bindery is not locked.213: The program cannot read security equivalences for a user.MIGRATEExplanation: Security equivalences have been defined for the given user on the source server, but the program could not read the bindery property that contains those equivalences.Action: Make sure that the workstation still has a connection to the source server and that the bindery is not locked. Also, make sure that the named user was not deleted by another user during the migration.PAGENUM=497 ID="BP491"214: The program cannot read a user's station restrictions.MIGRATEExplanation: Each user's station restrictions are contained in the bindery, in the node control property which is associated with the given User object. The program could not read this property from the bindery.Action: Make sure that the workstation still has a connection to the source server and that the bindery is not locked. Also, make sure that the user's account was not deleted by another user during the migration process.216: The program cannot read the next group name from the bindery.MIGRATEExplanation: While reading groups from the source server, the program could not obtain the name of a group from the bindery.Action: Make sure that the workstation still has a connection to the source server and that the bindery is not locked.217: The program cannot read the next print queue name from the bindery.MIGRATEExplanation: While reading print queues from the source server, the program could not obtain the name of a print queue from the bindery.Action: Make sure that the workstation still has a connection to the source server and that the bindery is not locked.218: The program cannot read the next print server name from the bindery.MIGRATEExplanation: While reading print servers from the source server, the program could not obtain the name of a print server from the bindery.Action: Make sure that the workstation still has a connection to the source server and that the bindery is not locked.219: The program cannot find an object's property from the bindery.MIGRATEExplanation: The program scanned the named object to determine if it had the given property but could not read from the bindery.Action: Make sure that the workstation still has a connection to the source server and that the bindery is not locked.220: The program cannot read the next username from the bindery.MIGRATEExplanation: While reading users from the source server, the program could not obtain the name of a user from the bindery.Action: Make sure that the workstation still has a connection to the source server and that the bindery is not locked.PAGENUM=498 ID="BP492"221: The program cannot update the intermediate file.MIGRATEExplanation: The program could not write information to the intermediate file.Action: Make sure that the workstation still has access to the working directory.222: An attempt to allocate number bytes of memory failed.MIGRATEExplanation: The workstation may not have enough available memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network.223: An internal error has occurred. A NetWare-style path could not be converted to a UNC path.MIGRATEExplanation: To access files on the destination server, the program must convert NetWare paths so that DOS can interpret them. The naming convention that DOS understands is called the Universal Naming Convention (UNC) and has the following format:FORMAT="LINESPECIFIC"MOREINFO="NONE" \\server\volume\directory\directory... While trying to convert a name from the NetWare naming convention to the UNC naming convention, the program failed.Action: Exit the utility, ensure the integrity of the workstation's memory, and run the utility again.224: The program cannot obtain the size of a file.MIGRATEExplanation: When reading login scripts, printer definition files, and print server setup files, the program tries to determine the size of the file by issuing a call to DOS. When this error message is displayed, the call to DOS has failed.Action: Make sure that the workstation still has a connection to the source server. Make sure that the workstation's memory has not been corrupted. If the problem persists, consult the DOS manuals.225: The program cannot read from a file.MIGRATEExplanation: The file may not exist or it may be locked by another user. A DOS error may have occurred.Action: Make sure that the file has not been deleted and that it is not locked by another user. If neither of these possibilities is the cause, consult the DOS manuals.PAGENUM=499 ID="BP493"226: The program cannot verify an object's password.MIGRATEExplanation: While determining whether a user or print server has a password, the utility could not access the bindery.Action: Make sure that the workstation still has a connection to the source server and that the bindery is not locked. Also, make sure that the user or print server has not been deleted from the bindery by another user.227: An internal error has occurred. The program cannot add a field to a record.MIGRATEExplanation: The program has run out of memory on the client workstation, preventing the program from assembling a record before writing it to the intermediate file.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network.228: The program could not read intruder detection information from the source server's bindery.MIGRATEExplanation: The program tried to access the source server's bindery to read intruder detection information, but the attempt resulted in a network error.Action: Make sure that the workstation running the migration still has a valid connection to the NetWare network, that the source server is still operational, and that the source server's bindery is not locked.229: The program could not read the status of a print queue from the source server.MIGRATEExplanation: A call to the NetWare server returned an unexpected error.Action: After migration, the network supervisor can manually set the print queue status on the destination server using PCONSOLE.230: The program could not read a file or directory's trustee information from the source server.MIGRATEExplanation: The program failed in its attempt to read trustee information of a file or directory on the source server.Action: After migration, the trustee information will have to be set up manually on the destination server using RIGHTS. The required trustee information can be obtained from the source server using RIGHTS.PAGENUM=500 ID="BP494"231: The program could not obtain an object's type from the source server.MIGRATEExplanation: The program failed in its attempt to read trustee information of a file or directory on the source server.Action: After migration, the trustee information will have to be set up manually on the destination server using the RIGHTS utility. The required trustee information can be obtained from the source server using the RIGHTS utility.302: The program cannot get the specified volume's number.MIGRATEExplanation: To copy files to or from a NetWare server, the program must first obtain NetWare's ID number for the volumes being affected by the copy. The attempt to obtain the volume's number has failed.Action: Make sure that the volume is mounted and that the workstation still has a valid connection to the NetWare server.303: The program cannot get the destination file's long name.MIGRATEExplanation: If the source server supports long names, the program tries to create and read long names for files that it copies from the source server. This error occurs when the program knows there is a long name associated with a file on the source server, but is unable to read it.Action: Make sure that the source server supports long names, and try again. If the problem persists, contact your Novell Authorized Reseller.305: An invalid path was specified.MIGRATEExplanation: This is an internal error. The path was invalid.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.308: The maximum number of directory levels has been exceeded. MIGRATE supports a maximum of 25 subdirectory levels.MIGRATEExplanation: The Migration utility cannot support more than 25 levels in a Directory tree. Files and directories farther from the root than level 25 will not be copied. Action: Decrease the number of levels in the directory structure on the source server before trying to copy data files to the destination server.317: The program cannot create the destination directory.MIGRATEExplanation: The program tried to create a directory, but failed.Action: Reboot the workstation and try again. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=501 ID="BP495"318: A destination Macintosh file already exists. This file cannot be copied.MIGRATEExplanation: The Migration utility will not copy over files that already exist in the destination directory.Action: Try renaming the file in the destination directory.319: A destination file already exists. This file cannot be copied.MIGRATEExplanation: The Migration utility will not copy over files that already exist in the destination directory.Action: Try renaming the file in the destination directory.322: An unexpected error has occurred.MIGRATEExplanation: This message can indicate a variety of possible errors.Action: If you cannot continue, try rebooting the workstation and try again. If the problem persists, contact your Novell Authorized Reseller.324: DOS has denied access to the file.MIGRATEExplanation: This error is returned by DOS. No other information is available.Action: Consult the DOS manual.325: The file cannot be created because a file with the same name exists in the destination directory that DOS cannot delete.MIGRATEExplanation: The Migration utility will not copy over existing files.Action: Try renaming the file in the destination directory; then retry the copy.328: The file cannot be copied.MIGRATEExplanation: An internal error has occurred while copying files.Action: Reboot the workstation and try again. If the problem persists, contact your Novell Authorized Reseller.329: The file cannot be created.MIGRATEExplanation: An internal error has occurred.Action: Reboot the workstation and try again. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=502 ID="BP496"330: The program cannot obtain an AFP entry ID.MIGRATEExplanation: An internal error has occurred.Action: Reboot the workstation and try again. If the problem persists, contact your Novell Authorized Reseller.331: The destination file cannot be opened.MIGRATEExplanation: An internal error has occurred.Action: Reboot the workstation and try again. If the problem persists, contact your Novell Authorized Reseller.332: The source file cannot be opened.MIGRATEExplanation: An internal error has occurred.Action: Reboot the workstation and try again. If the problem persists, contact your Novell Authorized Reseller.333: The file cannot be read.MIGRATEExplanation: An internal error has occurred.Action: Reboot the workstation and try again. If the problem persists, contact your Novell Authorized Reseller.334: File information could not be scanned on the destination file.MIGRATEExplanation: An internal error has occurred.Action: Reboot the workstation and try again. If the problem persists, contact your Novell Authorized Reseller.335: File information could not be scanned on the source file.MIGRATEExplanation: An internal error has occurred.Action: Reboot the workstation and try again. If the problem persists, contact your Novell Authorized Reseller.336: File information cannot be set.MIGRATEExplanation: An internal error has occurred.Action: Reboot the workstation and try again. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=503 ID="BP497"337: The specified file cannot be written to the disk.MIGRATEExplanation: An internal error has occurred.Action: Reboot the workstation and try again. If the problem persists, contact your Novell Authorized Reseller.338: An application error has detached this file.MIGRATEExplanation: An internal error has occurred.Action: Reboot the workstation and try again. If the problem persists, contact your Novell Authorized Reseller.339: The specified file is already being used by another workstation.MIGRATEExplanation: You cannot copy a file that is in use.Action: Wait until the file is no longer in use; then try the copy again.340: FTAM name space is not supported on the destination volume. Only the data will be copied.MIGRATEExplanation: FTAM name space is not loaded. Only file data can be transferred.Action: If FTAM information is needed, load the name space functionality and restart migration.341: A bad sector was found on the hard disk for the destination volume.MIGRATEExplanation: This error indicates a bad sector on the destination server's hard disk.Action: Either choose a different hard disk as the destination, or reformat the destination disk and try again.343: This operation cannot be completed due to insufficient memory.MIGRATEExplanation: The workstation does not have enough available RAM.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network.344: The specified file handle is invalid.MIGRATEExplanation: An internal error has occurred.Action: Reboot the workstation and try again. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=504 ID="BP498"345: The specified filename is invalid.MIGRATEExplanation: An internal error has occurred.Action: Reboot the workstation and try again. If the problem persists, contact your Novell Authorized Reseller.346: The specified file contains a record that is currently locked.MIGRATEExplanation: An internal error has occurred.Action: Reboot the workstation and try again. If the problem persists, contact your Novell Authorized Reseller.347: Macintosh name space is not supported on the destination volume. Only the data fork will be copied.MIGRATEExplanation: An internal error has occurred, indicating that the Macintosh name space is not loaded on the destination volume.Action: If Macintosh files are to be copied, load the Macintosh name space.348: No more file handles are available on the network.MIGRATEExplanation: An internal error has occurred.Action: Reboot the workstation and try again. If the problem persists, contact your Novell Authorized Reseller.349: You do not have Create/Erase rights on the destination directory.MIGRATEExplanation: NetWare security rights control what users can do with directories, files, or objects. Create and erase operations can be done only if the user has been granted the rights to perform them.Action: Make sure that the user has the necessary rights.350: You do not have Create rights necessary to create this file.MIGRATEExplanation: NetWare security rights control what users can do with directories, files, or objects. Create and erase operations can be done only if the user has been granted the rights to perform them.Action: Make sure that the user has the necessary rights.PAGENUM=505 ID="BP499"351: You do not have Erase rights on the destination directory.MIGRATEExplanation: NetWare security rights control what users can do with directories, files, or objects. Create and erase operations can be done only if the user has been granted the rights to perform them.Action: Make sure that the user has the necessary rights.352: No such DOS file or directory exists.MIGRATEExplanation: The file or directory may exist on a different path, or the file or directory may have been deleted somehow. Another possibility is that an internal system error occurred.Action: Make sure you specified a valid filename or directory name, that the path is correct, and that the file or directory exists. If none of these is the problem, reboot the workstation and try again. If the problem persists, contact your Novell Authorized Reseller.353: You do not have Modify rights on the destination directory.MIGRATEExplanation: Novell's security determines what users can do with files and directories. Security rights are assigned by the network supervisor. The user is required to have the Modify right to the destination directory to complete this procedure.Action: Make sure that the user has the necessary rights.354: You do not have Open rights necessary to open this file.MIGRATEExplanation: Novell's security determines what users can do with files and directories. Security rights are assigned by the network supervisor. The user is required to have the Open right to the file to complete this procedure.Action: Make sure that the user has the necessary rights.355: You do not have Read rights on the destination directory.MIGRATEExplanation: Novell's security determines what users can do with files and directories. Security rights are assigned by the network supervisor. The user is required to have the Read right to the destination directory to complete this procedure.Action: Make sure that the user has the necessary rights.356: You do not have Rename rights on the destination directory.MIGRATEExplanation: Novell's security determines what users can do with files and directories. Security rights are assigned by the network supervisor. The user is required to have the Rename right to the destination directory to complete this procedure.Action: Make sure that the user has the necessary rights.PAGENUM=506 ID="BP500"357: You do not have Search rights on the destination directory.MIGRATEExplanation: Novell's security determines what users can do with files and directories. Security rights are assigned by the network supervisor. The user is required to have the Search right to the destination directory to complete this procedure.Action: Make sure that the user has the necessary rights.358: You do not have Write rights on the destination directory.MIGRATEExplanation: Novell's security determines what users can do with files and directories. Security rights are assigned by the network supervisor. The user is required to have the Write right to the destination directory to complete this procedure.Action: Make sure that the user has the necessary rights.359: The destination file is flagged Read Only.MIGRATEExplanation: The Migration utility does not allow you to copy over an existing file. Action: Try renaming the source file so that it has a unique name.360: The OS/2 name space is not supported on the destination volume. Only the data will be copied.MIGRATEExplanation: As with all name spaces, OS/2 name space support must be loaded if it is to be used.Action: Load OS/2 name space support.361: The server is out of directory entries.MIGRATEExplanation: Only a set percentage of a hard disk is set aside for directory information. This percentage has been exceeded.Action: If all directories are to be migrated, the server will probably need a larger hard disk.362: No more disk space exists in the destination directory.MIGRATEExplanation: The destination directory's disk drive does not have sufficient capacity to hold all migrated data.Action: If all data is to be migrated, the server will probably need a larger hard disk.363: The server has run out of dynamic memory.MIGRATEExplanation: The server may not have enough available memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.PAGENUM=507 ID="BP501"364: The server does not have enough disk space for spool files.MIGRATEExplanation: The server may not have enough available memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.365: You cannot rename across volumes or servers.MIGRATEExplanation: The Migration utility does not allow you to rename files or directories.Action: None. This message is for information only. The file or directory will not be renamed.366: The specified subdirectory is in use by another workstation.MIGRATEExplanation: You cannot migrate until all users are logged off.Action: Wait until all users are logged off; then try again.367: The specified subdirectory is not empty.MIGRATEExplanation: This message may appear if the a failure occurs while the Migration utility is copying files. This message can appear if you try to delete a directory that is not empty.Action: Try copying the files again. If the problem persists, contact your Novell Authorized Reseller.368: The UNIX name space is not supported on the destination volume. Only the data will be copied.MIGRATEExplanation: As with all name spaces, UNIX name space support must be loaded if it is to be used.Action: Load UNIX name space support.369: The specified volume does not exist.MIGRATEExplanation: You cannot migrate to a volume that does not exist.Action: Make sure that the volume you want to migrate to is mounted, and that you have spelled the volume's name correctly; then try again.370: The resource fork for Macintosh directories cannot be copied.MIGRATEExplanation: The source volume supports Macintosh name space, but the destination volume does not.Action: Load Macintosh name space support on the destination server.PAGENUM=508 ID="BP502"372: No more file handles are available on the workstation.MIGRATEExplanation: The workstation has used all its file handles, as specified in the CONFIG.SYS file.Action: Increase the number of file handles in the CONFIG.SYS file, reboot the workstation, and run the migration again.373: The source directory's name space information cannot be copied to the destination volume.MIGRATEExplanation: Name space information may exist on the source that will not be copied to the destination because the destination lacks support for that name space.Action: Load the correct name space support on the destination server.375: The source file's name space information cannot be copied to the destination volume.MIGRATEExplanation: Name space information may exist on the source that will not be copied to the destination because the destination lacks support for that name space.Action: Load the correct name space support on the destination server.376: The connection to the source server has been lost.MIGRATEExplanation: The connection to the source server may have been lost due to one of the following:MARK=BULLETHeavy network traffic.Large number of routing links between the source server and the destination server (where the utility is running).Source server may be down.Physical connection may be broken to either the source server or the destination server.Action: Depending on the cause of the error, stop migration and then do one of the following:MARK=BULLETGo back to the configuration screen and edit the Source Server field to re-establish the source server connection.Make sure that the source server is up and running.Check the physical network connections on the source server and the destination server.Retry the migration.PAGENUM=509 ID="BP503"377: The connection to the destination server has been lost.MIGRATEExplanation: The connection to the destination server may have been lost due to one of the following:MARK=BULLETHeavy network traffic.Large number of routing links between the source server and the destination server.Destination server may be down.Physical connection may be broken to either the source server or the destination server.Action: Depending on the cause of the error, stop migration and then do one of the following:MARK=BULLETGo back to the configuration screen and edit the Destination Server field to re-establish the destination server connection.Make sure that the destination server is up and running.Check the physical network connections on the source server and the destination server.Retry the migration.378: The program could not read the source file's extended attributes.MIGRATEExplanation: The source file contains corrupted extended attributes that cannot be read, so the file was not copied.Action: After migration, obtain a valid copy of the source file and manually copy it (using NCOPY) to the destination server.379: The program could not write an extended attribute to the destination directory.MIGRATEExplanation: The program failed in its attempt to write extended attributes to a file or directory on the destination server.Action: After migration, use NCOPY to manually copy the files or directories to the destination server.380: The program could not read an extended attribute from the source directory.MIGRATEExplanation: The program failed in its attempt to read extended attributes of a file or directory on the source server.Action: After migration, use NCOPY to manually copy the files and/or directories from the source server.PAGENUM=510 ID="BP504"381: An extended attribute could not be copied from the source server to the destination server.MIGRATEExplanation: The program failed in its attempt to copy extended attributes to a file or directory on the destination server.Action: After migration, use NCOPY to manually copy the files or directories to the destination server.382: An error occurred while writing an extended attribute to the destination server.MIGRATEExplanation: The program failed in its attempt to write extended attributes to a file or directory on the destination server.Action: After migration, use NCOPY to manually copy the files or directories to the destination server.383: The program could not locate an extended attribute for a file or directory on the source server.MIGRATEExplanation: The source file or directory contains extended attributes, but the extended attributes could not be found.Action: After migration, use NCOPY to manually copy the files or directories to the destination server.400: The program could not read the number of groups in the domain.MIGRATEExplanation: The program could not determine the number of groups to read from the LAN Server domain controller.Action: Make sure that the workstation running the migration still has a valid connection to the LAN Server network and that the domain controller is still running and available.401: The program could not read the number of users in the domain.MIGRATEExplanation: The program could not determine the number of users to read from the LAN Server domain controller.Action: Make sure that the workstation running the migration still has a valid connection to the LAN Server network and that the domain controller is still running and available.402: The program could not obtain the date and time from the domain controller.MIGRATEExplanation: The program could not access the domain controller to retrieve the date and time.PAGENUM=511 ID="BP505"Action: Make sure that the workstation running the migration still has a valid connection to the LAN Server network and that the domain controller is still running and available. Also, make sure that the LAN Server object being read has not been modified or deleted by another user on the network.405: The program could not read group information. No groups will be read from the domain controller.MIGRATEExplanation: A network error occurred while the program was reading group information from the domain controller of the LAN Server network.Action: Make sure that the workstation running the migration still has a valid connection to the LAN Server network and that the domain controller is still running and available.406: An internal error has occurred. The program could not allocate a record for the intermediate file.MIGRATEExplanation: The workstation may not have enough available memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network.407: An internal error has occurred. The program could not add a data field to a record.MIGRATEExplanation: The workstation may not have enough available memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network.408: The program could not read the number of members in a group.MIGRATEExplanation: The program received an error from the LAN Server network while trying to read the number of members in a group.Action: Make sure that the workstation running the migration still has a valid connection to the LAN Server network and that the domain controller is still running and available. Also, make sure that the LAN Server group being read has not been modified or deleted by another user on the network.409: The program could not read the members of a group from the domain controller.MIGRATEExplanation: The program received an error from the LAN Server network while reading the names of the members of a group.Action: Make sure that the workstation running the migration still has a valid connection to the LAN Server network and that the domain controller is still running and available. Also, make sure that the LAN Server group whose members are being read has not been modified or deleted by another user on the network.PAGENUM=512 ID="BP506"410: The program could not read the number of aliases in the domain. No aliases will be read from the domain controller.MIGRATEExplanation: Most likely, the program could not read the number of aliases defined on the LAN Server domain controller. This can occur while the program is reading printers.Action: Make sure that the workstation running the migration still has a valid connection to the LAN Server network and that the domain controller is still running and available.411: The program could not read alias information.MIGRATEExplanation: Most likely, the program could not read alias names from the LAN Server domain controller. This error can occur while the program is reading printers.Action: Make sure that the workstation running the migration still has a valid connection to the LAN Server network and that the domain controller is still running and available.412: The program could not read user modal information.MIGRATEExplanation: The program could not read LAN Server user modal information (data that affects all users in the domain) from the domain controller.Action: Make sure that the workstation running the migration still has a valid connection to the LAN Server network and that the domain controller is still running and available.413: The program could not read user information.MIGRATEExplanation: The program could not read the list of all usernames or all information for an individual user.Action: Make sure that the workstation running the migration still has a valid connection to the LAN Server network and that the domain controller is still running and available. Also, make sure that the LAN Server user being read has not been modified or deleted by another user on the network.414: The program could not read printer queue information.MIGRATEExplanation: The program could not read information on a printer from the LAN Server domain controller.Action: Make sure that the workstation running the migration still has a valid connection to the LAN Server network and that the domain controller is still running and available. Also, make sure that the LAN Server printer being read has not been modified or deleted by another user on the network.PAGENUM=513 ID="BP507"416: The program could not obtain the number of LAN Server servers in the domain.MIGRATEExplanation: To read all access control assignments from the domain, the program needs to determine how many servers are in the domain and what their names are. An error occurred during the program's attempt to read the number of servers in the LAN Server domain.Action: Make sure that the workstation running the migration still has a valid connection to the LAN Server network and that the domain controller is still running and available.417: The program could not obtain workstation information.MIGRATEExplanation: The program could not obtain the name of the domain that the workstation is logged on to.Action: Make sure that the workstation running the migration still has a valid connection to the LAN Server network and that the domain controller is still running and available.421: The program could not update the intermediate file.MIGRATEExplanation: The program could not write migration information to the intermediate file.Action: If the intermediate file is located on the network, make sure that the workstation still has access to the file. If it is on the workstation's hard disk, check the integrity of the hard disk and the intermediate file (MIGRATE.GMF).422: The program could not allocate number bytes of memory.MIGRATEExplanation: The workstation may not have enough available memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network.426: The program could not read the number of access control entries for a resource.MIGRATEExplanation: The program could not obtain the number of access control records for a resource. Action: Make sure that the workstation running the migration still has a valid connection to the LAN Server network and that the domain controller is still running and available. Also, make sure that the LAN Server resource whose access control is being read has not been deleted by another user on the network.427: The program could not read access permission records for a path.MIGRATEExplanation: The program could not obtain access control information for the named directory path.Action: Make sure that the workstation running the migration still has a valid connection to the LAN Server network and that the domain controller is still running and available.PAGENUM=514 ID="BP508"428: The program could not read the size of an access control list.MIGRATEExplanation: The program could not determine the size of buffer needed to hold access control information.Action: Make sure that the workstation running the migration still has a valid connection to the LAN Server network and that the domain controller is still running and available.429: The program could not read an access control list.MIGRATEExplanation: The program could not obtain access control information for a network resource.Action: Make sure that the workstation running the migration still has a valid connection to the LAN Server network and that the domain controller is still running and available.430: The program could not read the names of the domain's servers.MIGRATEExplanation: The program could not obtain the names of all servers in the domain.Action: Make sure that the workstation running the migration still has a valid connection to the LAN Server network and that the domain controller is still running and available.431: The program could not read the list of hard drives for a server on the network.MIGRATEExplanation: The program could not read the list of hard drives available on the named server.Action: Make sure that the workstation running the migration still has a valid connection to the LAN Server network and that the domain controller is still running and available. Also, make sure that the named LAN Server is still functioning properly.432: The program could not obtain the size of a buffer for holding LAN Server information.MIGRATEExplanation: The program could not determine the memory requirements for retrieving information.Action: Make sure that the workstation running the migration still has a valid connection to the LAN Server network and that the domain controller is still running and available.433: An internal error has occurred. The program could not extract the server name from a UNC path.MIGRATEExplanation: To access files on the destination server, the program must convert NetWare paths so that DOS can interpret them. The naming convention that DOS understands is called the Universal Naming Convention (UNC) and has the following format:FORMAT="LINESPECIFIC"MOREINFO="NONE"\\server\volume\directory\directory 
PAGENUM=515 ID="BP509"While trying to obtain access control information, the program could not determine the server name from the given UNC path.Action: Exit the utility and ensure the integrity of the LAN Server connection. Then retry the utility.501: An attempt to allocate memory for writing to the intermediate file failed.MIGRATEExplanation: The workstation may not have enough available memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network.502: An internal error has occurred. An attempt to add a data field to a record failed.MIGRATEExplanation: The workstation may not have enough available memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network.503: An attempt to write to the intermediate file failed.MIGRATEExplanation: The program could not write information to the intermediate file.Action: If the intermediate file is located on the network, make sure that the workstation still has access to the file. If it is on the workstation's hard disk, check the integrity of the hard disk and the intermediate file (MIGRATE.GMF).504: An attempt to read this group's list of users from the DCDB file failed.MIGRATEExplanation: The program could not read the list of users that belong to the group currently being read from the DCDB file. The DCDB file is probably corrupted.Action: Run the Migration utility again. If the problem persists, contact your Novell Authorized Reseller.505: An attempt to read a group from the DCDB file failed.MIGRATEExplanation: The program had trouble reading a group record from the DCDB file. The DCDB file is probably corrupted. Action: Run the Migration utility again. If the problem persists, contact your Novell Authorized Reseller.506: An attempt to read this group's description from the DCDB file failed.MIGRATEExplanation: The program had trouble reading the description for the group currently being read from the DCDB file. The DCDB file is probably corrupted. Action: Run the Migration utility again. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=516 ID="BP510"507: An attempt to read a print queue from the DCDB file failed.MIGRATEExplanation: The program had trouble reading a print queue record from the DCDB file. The DCDB file is probably corrupted. Action: Run the Migration utility again. If the problem persists, contact your Novell Authorized Reseller.508: An attempt to read this print queue's description from the DCDB file failed.MIGRATEExplanation: The program had trouble reading the description for the print queue currently being read from the DCDB file. The DCDB file is probably corrupted. Action: Run the migration again. If the problem persists, contact your Novell Authorized Reseller.509: An attempt to read a user from the DCDB file failed.MIGRATEExplanation: The program had trouble reading a user record from the DCDB file. The DCDB file is probably corrupted. Action: Run the Migration utility again. If the problem persists, contact your Novell Authorized Reseller.510: An attempt to read this user's description from the DCDB file failed.MIGRATEExplanation: The program had trouble reading the description for the user currently being read from the DCDB file. The DCDB file is probably corrupted. Action: Run the Migration utility again. If the problem persists, contact your Novell Authorized Reseller.511: An attempt to read this user's administrator privilege flag from the DCDB file failed.MIGRATEExplanation: The program had trouble reading the Supervisor Equivalent Flag for the user currently being read from the DCDB file. The DCDB file is probably corrupted. Action: Run the Migration utility again. If the problem persists, contact your Novell Authorized Reseller.512: An attempt to read this user's password required flag from the DCDB file failed.MIGRATEExplanation: The program had trouble reading the Password Required Flag for the user currently being read from the DCDB file. The DCDB file is probably corrupted. Action: Run the Migration utility again. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=517 ID="BP511"513: An attempt to read this user's logon revoked flag from the DCDB file failed.MIGRATEExplanation: The program had trouble reading the Logon Revoked Flag for the user currently being read from the DCDB file. The DCDB file is probably corrupted. Action: Run the Migration utility again. If the problem persists, contact your Novell Authorized Reseller.514: An attempt to read an access control profile's server from the DCDB file failed.MIGRATEExplanation: The program had trouble reading the server name for the access control profile currently being read from the DCDB file. The DCDB file is probably corrupted. Action: Run the Migration utility again. If the problem persists, contact your Novell Authorized Reseller.515: An attempt to read an access control profile's resource name from the DCDB file failed.MIGRATEExplanation: The program had trouble reading the resource name for the access control profile currently being read from the DCDB file. The DCDB file is probably corrupted.Action: Run the Migration utility again. If the problem persists, contact your Novell Authorized Reseller.516: An attempt to read an access control profile's user entry from the DCDB file failed.MIGRATEExplanation: The program had trouble reading the user entry list for the access control profile currently being read from the DCDB file. The DCDB file is probably corrupted. Action: Run the Migration utility again. If the problem persists, contact your Novell Authorized Reseller.517: An attempt to read this user's server from the DCDB file failed.MIGRATEExplanation: The program had trouble reading the user's server from the DCDB file. The DCDB file is probably corrupted. Action: Run the Migration utility again. If the problem persists, contact your Novell Authorized Reseller.518: An attempt to read this printer's server from the DCDB file failed.MIGRATEExplanation: The program had trouble reading the printer's server from the DCDB file. The DCDB file is probably corrupted.Action: Run the Migration utility again. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=518 ID="BP512"MONITOR60: The NLM could not allocate memory.MONITORExplanation: The server does not have enough memory available.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.198: The NLM could not allocate a resource tag.MONITORExplanation: The server does not have enough memory available.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.207: The NLM could not open a screen.MONITORExplanation: The server does not have enough memory available.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.208: The NLM could not register for event notification.MONITORExplanation: The server does not have enough memory available.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.236: This NLM requires a newer version of NWSNUT.NLM.MONITORExplanation: While loading, MONITOR determined that the version of NWSNUT.NLM loaded in server memory does not support the required functionality.Action: Update the version of NWSNUT.NLM on the server.PAGENUM=519 ID="BP513"MSENGINE (SFT III)MSENGINE message numbers correspond to the SERVER error messages. See the messages in IDREF="FM51388"SERVER for explanations of MSENGINE messages.MSENGINE error messages originate in the mirrored server engine of NetWare® 4.1 SFT IIITM. The mirrored server engine, or MSEngine, is the part of SFT III that handles nonphysical processes such as the NetWare file system, NetWare Directory Services, and queue management. An error that occurs in the MSEngine occurs on both SFT III servers.The IOEngine (input/output engine) is the part of SFT III that handles physical processes such as network and disk I/O, hardware interrupts, device drivers, timing, and routing. The IOEngine is not mirrored; an error that occurs in the IOEngine occurs on only one SFT III server. See IDREF="FM24948"IOENGINE (SFT III) for explanations of IOENGINE messages.PAGENUM=520 ID="BP514"NCOPY000: This utility does not allow copies to or from the console.NCOPYExplanation: The text string "CON" is a reserved text string, and it cannot be used as a directory or filename.Action: Use a directory or filename other than CON.005: This utility was unable to generate a valid OS/2 name.NCOPYExplanation: Given the source filename and the mask pattern, a valid OS/2 name could not be generated.Action: Rename the source file and select a different mask pattern.010: This utility was unable to get the specified volume's number.NCOPYExplanation: The volume does not exist on the server, or the volume name was typed incorrectly.Action: Use FILER to see which volumes are defined on the server. When specifying a volume name in a command, always type a colon after the volume name.015: This utility was unable to get the destination file's long name.NCOPYExplanation: If the NetWare servers and operating systems support long names, NCOPY attempts to create a file during the copy process with that file's long name. This error occurs when NCOPY is unable to get a long name associated with a file from the operating system.Action: Make sure the user has rights in the directory; then retry the operation. If the problem persists, contact your Novell Authorized Reseller.ID="FM49197"020: The specified destination path is invalid.NCOPYExplanation: The path does not exist, or the directory path was typed incorrectly.Action: Do one or more of the following:MARK=BULLETUse FILER to examine the directory structure to be used. Type the directory path correctly.If the workstation has mapped a network drive to the directory path, use the mapped drive in the command instead of the directory path.If the error occurs when logging in, use NETADMIN to access the login script; then correct the error.PAGENUM=521 ID="BP515"025: This specified path is invalid.NCOPYAction: See messageIDREF="FM49197" "020: The specified destination path is invalid."  030: The specified source path is invalid.NCOPYAction: See messageIDREF="FM49197" "020: The specified destination path is invalid."  035: The current source directory is the original destination directory. To avoid making copies infinitely, this directory and its subdirectories will not be copied.NCOPYExplanation: The user is trying to copy a subdirectory structure to itself or within the same structure.Action: Make sure the destination path is correct, or specify a different path.040: The maximum number of directory structure levels supported by NCOPY (25) has been exceeded.NCOPYExplanation: NetWare supports only 25 directory structure levels. This limit has been exceeded.Action: Make sure the directory structure does not exceed 25 levels. Or, move farther down the directory structure and perform the copy at that point.045: Multiple files cannot be copied to a single file.NCOPYExplanation: NCOPY will not copy multiple files to a single file.Action: Change the destination name to a new directory name and try again.050: Your station is not attached to server.NCOPYExplanation: The workstation is not attached to a server, or the server does not exist.Action: Use ATTACH or MAP to attach to the server. Make sure the server name is valid.065: Volume name: does not exist.NCOPYExplanation: The volume does not exist on the current server, or the volume name was typed incorrectly.Action: Use FILER to see which volumes exist on the server. Make sure the spelling is correct.PAGENUM=522 ID="BP516"070: NWGetEffectiveDirectoryRights returned an error.NCOPYExplanation: The directory does not exist, or the directory path was typed incorrectly. There could also be an internal error.Action: Make sure the directory exists, and make sure the path is typed correctly. Try the operation again. If the problem persists, obtain a new copy of NCOPY.075: Files cannot be copied to themselves.NCOPYExplanation: NCOPY will not allow a file to be copied to itself.Action: Change the name of the new file and make sure the destination path is correct.080: This utility was unable to get the file server name.NCOPYExplanation: NCOPY could not get the name of the NetWare server from the given connection ID.Action: Make sure the server is still connected to the network; then try the operation again.085: The /E parameter (copy empty directories) is valid only with the /S parameter (copy subdirectories).NCOPYExplanation: The /E option can be used only with the /S option.Action: To use the /E option, copy the entire subdirectory structure using both the /E and /S options.090: The destination directory could not be created.NCOPYExplanation: NCOPY could not create a directory when it tried to copy a subdirectory.Action: Use RIGHTS to verify that the user has the Create right in the destination directory; then try the command again.095: The empty destination directory could not be deleted.NCOPYExplanation: When the /S command line option is used, NCOPY copies all subdirectories, including empty ones. If, by the end of the scan for files in a particular subdirectory, no files were found and the /E option was not used, the directory is deleted. This error occurs when NCOPY is not able to delete the subdirectory. NCOPY may have been unable to delete this directory because the directory is in use at another workstation and NCOPY cannot delete a file in use, or NCOPY may be corrupted.Action: Make sure no one else is using the directory; then retry the copy. If the problem recurs, NCOPY could be corrupted. Copy NCOPY from the original CD-ROM or the NetWare diskettes, (or get the latest copy of NCOPY from a Novell Authorized reseller); then retry the copy. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=523 ID="BP517"100: Internal error number has occurred; the cause is unknown.NCOPYExplanation: NCOPY tries to determine the cause of any error that occurs during the copy of a file. In some instances, the operating system (DOS or NetWare) is not explicit enough about the cause of a failure. This error message is followed by a secondary description (the symptom) of the problem.Action: Read the secondary description of the symptom to see if there are any alternatives.105: An unknown switch (option) was found on the command line.NCOPYExplanation: The user specified an invalid option in the command.Action: Enter the command syntax correctly, including the path and optional parameters. Type the command correctly. For information about the correct command line syntax, type "NCOPY /?" to access the Help screen, or see "BOOK="utlrfenu" COLLECTION="nw41"NCOPY" in Utilities Reference. 110: DOS has denied access to the file.NCOPYExplanation: DOS will not allow the file to be copied. It may be in use, or the user may not have appropriate rights to copy the file.Action: Make sure the file is not in use or is unlocked. Make sure the user has appropriate rights to access the file.115: The file cannot be created because a file of the same name exists on the destination directory that DOS cannot delete.NCOPYExplanation: NCOPY attempted to use a filename that already exists. NCOPY attempted to delete the destination file but could not. Action: Determine why the file could not be deleted (the user may not have rights to copy to that area). Correct the problem and delete the file from the destination directory.120: The destination filename was shortened to a valid DOS name: name.NCOPYExplanation: DOS filenames are limited to eleven characters: eight in the name and three in the extension. When copying non-DOS files into a DOS environment, or to a new server, NCOPY tries to create the new files using the file's long name. Under DOS, the filename gets truncated to a regular DOS short name that could change, depending on whether other files exist with the same short name. The warning shows that the file has been given a truncated DOS name.This warning also appears when NCOPY is given a correctable, invalid DOS name at the command line. NCOPY is emulating DOS by accepting long filenames at the command line and truncating them to valid names.Action: None. This message is for information only.PAGENUM=524 ID="BP518"130: The file cannot be copied.NCOPYExplanation: Several explanations are possible:MARK=BULLETThe user does not have the appropriate rights to read from or write to the file.The file is locked because it is in use.A record in the file is locked by another user.NetWare or DOS cannot read or write to the file because of hardware problems.The workstation has lost its connection to the server and cannot detach the connection to an open file. In this case, NCOPY appears to work normally but returns this error. Action: Make sure the file is not in use or locked and that the user has the appropriate rights. Make sure the workstation is still connected to both source and destination servers. Reboot the workstation and try again. If the problem persists, contact your Novell Authorized Reseller.135: The file cannot be created.NCOPYExplanation: This error is caused by one of the following:MARK=BULLETThe file was copied to an existing file.A subdirectory in the destination directory has the same name as the file to be copiedThe user does not have the appropriate rights to create the file.NCOPY encountered an error as it attempted to copy non-DOS files (such as Macintosh or OS/2) and to create them in the destination directory.The file is currently open in a nonsharing mode.The file is flagged Read Only.Action: Make sure the name of the file is different than any existing file and subdirectory in the destination directory. Make sure the user has the appropriate rights to create a file in the destination directory. If the user has the Modify right in the source directory, flag the file as Read/Write; then try the command again. If the file is being used, wait until the file is no longer in use.PAGENUM=525 ID="BP519"140: This utility cannot get the AFP entry ID.NCOPYExplanation: The computer couldn't obtain the MAC entry ID for a Macintosh file.Action: Verify that the file is a Macintosh file; then try the operation again. NCOPY might be corrupted. Copy NCOPY from the original CD-ROM or the NetWare diskettes, or get the latest copy of NCOPY from your Novell Authorized Reseller. If the problem persists, contact your Novell Authorized Reseller.145: The destination file cannot be opened.NCOPYExplanation: The file is in use or flagged Read Only, or the user does not have the appropriate rights to access the file.Action: If the file is in use, wait until the file is no longer being used. Make sure the user has the appropriate rights in the specified directory. If the user has the Modify right in the destination directory, flag the file as Read/Write; then try the command again.150: The source file cannot be opened.NCOPYExplanation: The file is in use or flagged Read Only, or the user does not have the appropriate rights to access the file.Action: If the file is in use, wait until the file is no longer being used. Make sure the user has the appropriate rights in the specified directory. If the user has the Modify right in the source directory, flag the file as Read/Write; then try the command again.155: The file cannot be read.NCOPYExplanation: A network error, a local hard disk error, or a floppy disk error prevented NCOPY from copying the source file correctly, or the file is in use or is flagged Execute Only.Action: If the error is hardware related, use the DOS CHKDSK command. If the error occurred on a network drive, use NDIR or FLAG to determine the file's attributes. If the file is flagged Execute Only, the user can not copy the file or remove the flag. If the file is in use, wait until the file is no longer in use.160: File information could not be scanned on the destination file.NCOPYExplanation: The workstation could not obtain the file information. The file may be corrupted.Action: Try the operation again. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=526 ID="BP520"165: File information could not be scanned on the source file.NCOPYExplanation: The workstation could not obtain the file information. The file or NCOPY may be corrupt.Action: Try the operation again. If you suspect, NCOPY might be corrupted, copy NCOPY from the original CD-ROM or the NetWare diskettes, or get the latest copy of NCOPY from your Novell Authorized Reseller; then try the operation again. If the problem persists, contact your Novell Authorized Reseller.170: File information cannot be set.NCOPYExplanation: The workstation could not set the destination file information. The file may be corrupted.Action: Try the operation again. If you suspect, NCOPY might be corrupted, copy NCOPY from the original CD-ROM or the NetWare diskettes, or get the latest copy of NCOPY from your Novell Authorized Reseller; then try the operation again. If the problem persists, contact your Novell Authorized Reseller.175: The specified file cannot be written to the disk.NCOPYExplanation: When the file was copied, one of the following problems existed:MARK=BULLETThe connection to the destination server was lost.The user did not have the appropriate rights in the destination directory.The destination directory did not have enough space available for the file.Action: Make sure the workstation is still connected to the destination server and the user has Read/Write rights to the destination directory. If the workstation is connected and the user has the proper rights, use FILER to view the number of free kilobytes in the volume and to check for disk restrictions. Perform one or more of the following actions:MARK=BULLETIf the volume is full, delete unwanted files from the destination directory, or copy the file to a different volume.If the disk has no more space, increase the available disk space on the volume. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Disk Space Problems" in Supervising the Network.PAGENUM=527 ID="BP521"180: An application error has detached this file.NCOPYExplanation: NCOPY tried to read from or write to a file that has been detached by an application running on NetWare. A file can become detached if it is open when the application issues a ReleaseFileSet call.Action: Notify the software developer of the error. Use INSTALL /M to dismount and remount the volume; then try the operation again.185: The specified file is already being used by another workstation.NCOPYExplanation: The destination file is already open at another workstation.Action: If the file needs to be updated, close the file at the workstation where it is in use; then try the operation again.195: A bad sector was found on the hard disk for the destination volume.NCOPYExplanation: NCOPY detected a bad sector on the destination volume and could not copy the file.Action: Make a backup of the files. Then run the diagnostic utility that came with the hard disk. Repair or replace any disk-related hardware that may not be working properly. If necessary, reinstall the operating system; then restore the files from the backup.200: The file will NOT be copied because the source and destination file names are the same.NCOPYExplanation: NCOPY will not allow a file to be copied to a file with the same name.Action: Change the destination filename.205: This operation cannot be completed due to insufficient memory.NCOPYAction: See "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network.210: The specified file handle is invalid.NCOPYExplanation: The file handle became corrupted during the copy, or NCOPY might be corrupted.Action: Try the operation again. NCOPY might be corrupted. Copy NCOPY from the original CD-ROM or the NetWare diskettes, or get the latest copy of NCOPY from NETWIRE; then try the operation again. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=528 ID="BP522"215: The specified file name is invalid.NCOPYExplanation: The filename specified on the command line is invalid.Action: Make sure there are no invalid characters in the filename. Make sure the filename does not exceed the DOS limit of eight characters for the name and three characters for the extension.220: The specified file contains a record that is currently locked.NCOPYExplanation: NCOPY attempted to read from or write to a file that has a locked record. Another user might have the record open.Action: Wait until the lock is released and try the operation again.230: No more file handles are available on the network.NCOPYExplanation: DOS does not have any file handles available to open for copying.Action: Increase the "FILES=number" parameter in the CONFIG.SYS file, and reboot the workstation; then try the operation again.235: You do not have right rights in the destination directory.NCOPYExplanation: The user must have specific rights in the source and destination directories to copy files on the network. NCOPY has detected that the user does not have the appropriate rights in the specified directory.Action: If appropriate, grant the rights indicated in the message.235: You do not have Create rights necessary to create this file.NCOPYExplanation: The user must have Create rights to create the specified file. The user does not have Create rights to create the specified file.Action: If appropriate, grant the Create rights to the specified file.235: You do not have Open rights necessary to open this file.NCOPYExplanation: The user must have Open rights on the specified file. The user does not have Open rights on the specified file.Action: If appropriate, grant the Open rights to the specified file.235: You do not have rights to copy from the specified directory.NCOPYExplanation: The user must have Read rights in the source directory to copy files from it. The user does not have Read rights in the source directory.Action: If appropriate, grant the users Read rights in the source directory.PAGENUM=529 ID="BP523"235: You do not have rights to copy to the destination directory.NCOPYExplanation: The user must have Create and Write rights in the destination directory to copy files to it. The user does not have Create and Write rights in the destination directory.Action: If appropriate, grant the user Create and Write rights in the destination directory.250: No such DOS file or directory exists.NCOPYExplanation: The file does not exist, or the directory path does not exist.Action: Make sure the path to the file or directory is valid. Do the operation again.290: The destination file is flagged Read Only.NCOPYExplanation: A Read Only file already exists in the destination path. Because it is Read Only, it cannot be deleted or overwritten by the new file.Action: If the file needs to be updated, use FLAG to flag the file as Normal; then copy the file again.300: The server is out of directory entries.NCOPYExplanation: Each volume is limited to a specific number of directory entries according to the size of the volume. Each file or directory is considered one directory entry. The volume has reached the maximum number of directories allowed.Action: To increase the number of directory entries, use FILER to delete or purge unwanted files from the destination volume.305: No more disk space exists in the destination directory.NCOPYExplanation: All disk space on the destination directory has been used.Action: If the destination directory is on a workstation's hard disk, delete unnecessary files or install a larger hard disk. If the destination directory is on a server, see "BOOK="superenu" COLLECTION="nw41"Resolving Server Disk Space Problems" in Supervising the Network.310: The server has run out of dynamic memory.NCOPYAction: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.315: The server does not have enough disk space for spool files.NCOPYAction: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Disk Space Problems" in Supervising the Network.PAGENUM=530 ID="BP524"325: The specified subdirectory is being used by another workstation.NCOPYExplanation: NCOPY tried to delete a directory while another workstation was using it.Action: Specify the correct directory; then delete it when it is no longer in use.330: The specified subdirectory is not empty.NCOPYExplanation: NCOPY tried to delete a directory that has files in it. Instead of checking directories to see if they are empty before copying them, NCOPY copies all directories. If the directory is empty and the /E option is not specified, the directory is deleted. This makes it possible for a file to get into the empty subdirectory between the time NCOPY checks for files in the directory and the time NCOPY deletes the empty directory.Action: Remove all files from the directory; then try the operation again.340: The specified volume does not exist.NCOPYExplanation: The volume was typed incorrectly, or it does not exist on the server.Action: Type the volume name correctly, or run FILER to find out which volumes exist on the server.345: The resource fork for Macintosh directories cannot be copied.NCOPYExplanation: NCOPY does not copy the resource fork for Macintosh directories (folders). It is possible for DOS directories on the network to appear as Macintosh directories if they have been accessed from a Macintosh workstation. This error is displayed for DOS directories as well as for Macintosh directories.Action: If you need the resource fork for the directory, copy the folder from a Macintosh workstation.350: No more file handles are available on the workstation.NCOPYExplanation: DOS does not have file handles available to open for copying.Action: Increase the "FILES=number" parameter in the CONFIG.SYS file, and reboot the workstation; then try the operation again.360: Cannot copy extended attributes.NCOPYExplanation: The file has extended attributes. NCOPY could not copy them.Action: Make sure the OS/2 name space exists on the destination volume; then try the operation again.PAGENUM=531 ID="BP525"365: The /U parameter (unsupported media) is valid only with the /R parameter (retain compression).NCOPYExplanation: NCOPY tried to use the /U parameter without using the /R parameter. The /U parameter can only be used with the /R parameter.Action: Reissue the command using both the /U and /R parameters.370: The number of extended attributes allowed per file on the destination server is smaller than the source server.NCOPYExplanation: The maximum extended attributes is a server parameter. The setting on the destination server is smaller than the setting on the source server, and the file being copied exceeds the destination limit.Action: Use the SET.NLM to change the parameter. 903: The command line syntax is invalid.NCOPYAction: See message IDREF="FM18860""903: The command line syntax is invalid." in Appendix C.970: The attempt to open the Unicode table files failed.NCOPYAction: See message IDREF="FM15675""970: The attempt to open the Unicode table files failed." in Appendix C.971: The workstation does not have enough memory to load the Unicode table files.NCOPYAction: See message IDREF="FM55341""971: The workstation does not have enough memory to load the Unicode table files." in Appendix C.972: Access to the Unicode table files was denied.NCOPYAction: See message IDREF="FM90152""972: Access to the Unicode table files was denied." in Appendix C.973: The Unicode table files cannot be found in the NLS directory or in the search path. Code page: <number>  Country:  <number>NCOPYAction: See message IDREF="FM62778""973: The Unicode table files cannot be found in the NLS directory or in the search path. Code page: number Country: number" in Appendix C.974: The Unicode table files are corrupted.NCOPYAction: See message IDREF="FM63405""974: The Unicode table files are corrupt." in Appendix C.PAGENUM=532 ID="BP526"975: The Unicode table files cannot be opened because there are already too many open files. Close some files or modify your CONFIG.SYS file.NCOPYAction: See message IDREF="FM49793""975: The Unicode table files cannot be opened because there are already too many open files. Close some files or modify your CONFIG.SYS file." in Appendix C.998: The message file found (utility_name.MSG) is an incorrect version. The correct version is number. See your network supervisor for assistance.NCOPYAction: See message IDREF="FM91957""998: The message file found (utility_name.MSG) is an incorrect version. The correct version is number. See your network supervisor for assistance." in Appendix C.999: The message file for this utility cannot be found.NCOPYAction: See message IDREF="FM69424""999: The message file for this utility cannot be found." in Appendix C.PAGENUM=533 ID="BP527"NCUPDATE200: You do not have proper rights to update the configuration file.NCUPDATEExplanation: The file attributes for the NET.CFG file are set for Read Only.Action: Make sure file attributes for the NET.CFG file are set to Read Write and that the NET.CFG file can be accessed.210: This program was unable to determine which configuration file was used.NCUPDATEExplanation: NCUPDATE searched for the NET.CFG file from which the requester was loaded and was unable to determine which configuration file was used.Action: Make sure the user has only one NET.CFG file, or use the /C option when loading the requester.220: An error occurred during NCUPDATE'S attempt to create the context.NCUPDATEExplanation: NCUPDATE searched for the user's name context in the Requester section of the NET.CFG file and could not find the parameter.Action: Make sure a name context parameter is specified in the Requester section of the user's NET.CFG file.230: NetWare DOS Requester section in configuration file is not found. No changes have been made.NCUPDATEExplanation: NCUPDATE tried to make changes to the DOS Requester section of the NET.CFG file, but this section is missing.Action: Make sure the user's NET.CFG file has a DOS Requester section and try updating again.230: NetWare Requester section in configuration file is not found. No changes have been made.NCUPDATEExplanation: NCUPDATE tried to make changes to the NetWare Requester of the NET.CFG file, but this section is missing.Action: Make sure the user's NET.CFG file has a NetWare Requester section and try updating again.PAGENUM=534 ID="BP528"826: The VLMs are not loaded.NCUPDATEExplanation: NCUPDATE requires the workstation VLMs to be loaded in order to search for the NET.CFG file.Action: Load the VLM programs and try updating again.900: An internal application error has occurred. Error code: codeNCUPDATEAction: For information on the specific error code, see IDREF="FM61529""Error Codes" in Appendix A.903: The command line syntax is invalid. For help, type NCUPDATE /?.NCUPDATEAction: See message IDREF="FM18860""903: The command line syntax is invalid." in Appendix C.920: This utility was unable to allocate number bytes of memory.NCUPDATEAction: See message IDREF="FM30331""920: This utility was unable to allocate number bytes of memory." in Appendix C.970: The attempt to open the Unicode table files failed.NCUPDATEAction: See message IDREF="FM15675""970: The attempt to open the Unicode table files failed." in Appendix C.971: The workstation does not have enough memory to load the Unicode table files.NCUPDATEAction: See message IDREF="FM55341""971: The workstation does not have enough memory to load the Unicode table files." in Appendix C.972: Access to the Unicode table files was denied.NCUPDATEAction: See message IDREF="FM90152""972: Access to the Unicode table files was denied." in Appendix C.973: The Unicode table files cannot be found in the NLS directory or in the search path. Code page: number  Country: numberNCUPDATEAction: See message IDREF="FM62778""973: The Unicode table files cannot be found in the NLS directory or in the search path. Code page: number Country: number" in Appendix C.974: The Unicode table files are corrupted.NCUPDATEAction: See message IDREF="FM63405""974: The Unicode table files are corrupt." in Appendix C.PAGENUM=535 ID="BP529"975: The Unicode table files can't be opened because there are already too many open files. Close some files or modify your CONFIG.SYS file.NCUPDATEAction: See message IDREF="FM49793""975: The Unicode table files cannot be opened because there are already too many open files. Close some files or modify your CONFIG.SYS file." in Appendix C.PAGENUM=536 ID="BP530"NDIR120: Control characters cannot be used in the command line. NDIRExplanation: NDIR parameters cannot include characters combined with the MOREINFO="NONE"<Ctrl> key (for example: MOREINFO="NONE"<Ctrl>+<E>). NDIR found one or more of these characters in the command line and has terminated. Of course, MOREINFO="NONE"<Ctrl>+<C> will abort the NDIR command. Action: Do not use control characters in NDIR parameters.130: An illegal or missing operator was found before the number or name.NDIRExplanation: Restriction options that act on a name or a number rely on comparative operators such as [not] equal, less, greater, before, after. An invalid comparative operator was used, terminating NDIR.Action: Use valid syntax. For usage information, type "NDIR /?" for online help, or see "BOOK="utlrfenu" COLLECTION="nw41"NDIR" in Utilities Reference.140: The given date is missing or mistyped. The format mm-dd-yy is expected. You entered incorrect_entry. NDIRExplanation: NDIR expects date parameters to be entered for options requiring a date comparison. Date parameter must be in the specified format. The message parameters were incorrect, terminating NDIR.Action: Type the command again, making sure that the date is included and is in the correct format.142: The specified month does not exist.NDIRExplanation: A date parameter included a month designation less than 1 or greater than 12. NDIR has terminated.Action: Make sure the month designations are between 1 and 12.144: The specified day does not exist.NDIRExplanation: NDIR knows how many days are in each month. The day given in the date parameter is less than 1 or greater than the number of days possible in the given month. NDIR has terminated.Action: Make sure the day designation is within the correct range for the given month.PAGENUM=537 ID="BP531"146: A missing or mistyped year was found in the date.NDIRExplanation: Date parameters passed to NDIR did not include a valid year in the format "mm-dd-yy." NDIR has terminated.Action: Make sure the year given is valid and is in the correct format.150: A missing or mistyped number was found after the SIZE operator: numberNDIRExplanation: NDIR allows a sorted display of files or directories according to various options, including size. The size must be an unsigned long integer. The "Size" option specified was invalid, and NDIR has terminated.Action: Make sure the "Size" option restriction includes a number within the acceptable range.160: SORT is followed by an unknown ordering. NDIRExplanation: The "Sort" option delivers output sorted by the specified ordering (as shown on the help screen). This error indicates that the ordering specified is other than OWner, SIze, UPdate, CReate, ACcess, ARchive, or UNsorted. NDIR has terminated.Action: Make sure the "Sort" option is being used correctly. For information, type "NDIR /?" or see "BOOK="utlrfenu" COLLECTION="nw41"NDIR" in Utilities Reference.170: An illegal or missing flag was found after the word NOT.NDIRExplanation: NDIR allows filtering of files and directories according to file and directory attributes. You are looking for files or directories with an attribute that NDIR does not recognize. NDIR has terminated.Action: Make sure the parameters given to NDIR are valid. For information, type "NDIR /?" or see "BOOK="utlrfenu" COLLECTION="nw41"NDIR" in Utilities Reference.190: This utility requires NetWare 386 file system support. NDIRExplanation: Certain aspects of NDIR require NetWare 3 file support (for example, the /SP option). Without NetWare 3.x file support, this message appears, and NDIR terminates.Action: Use NDIR only with NetWare 3 support or higher.240: An error occurred during NDIR's attempt to read path restriction information. NDIRExplanation: NDIR's "/spa" option allows you to get volume space restriction information. If NDIR cannot find the space limitations, this message is given, and NDIR terminates.Action: Try again. If the problem persists, check for error messages at the server.PAGENUM=538 ID="BP532"260: An error occurred during NDIR's attempt to read volume restriction information.NDIRExplanation: NDIR's "/vol" option allows you to get volume restriction information. If NDIR cannot find the information, this message is given and NDIR terminates.Action: Try again. If the problem persists, check for error messages at the server.270: An error occurred during NDIR's attempt to get server information.NDIRExplanation: NDIR's "/vol" option might not have been able to get information from the server. NDIR has terminated.Action: Try again. If the problem persists, check for error messages at the server.280: An error occurred during NDIR's attempt to get volume information.NDIRExplanation: NDIR's "/vol" option might not have been able to get information from the server. NDIR has terminated.Action: Try again. If the problem persists, check for error messages at the server.290: An error occurred during NDIR's attempt to map drive name:.NDIRExplanation: NDIR's "/vol" option makes a call to get information such as total blocks available, number of sectors per block, etc. The call has failed even though the bindery is not locked. NDIR has terminated.Action: Try again. If the problem persists, check for error messages at the server.300: An error occurred during NDIR's attempt to get the volume number.NDIRExplanation: NDIR's "/vol" option makes a call to get the volume number before it calls for volume information. This call has failed, and NDIR has terminated.Action: Try again. If the problem persists, check for error messages at the server.400: The Login Control property cannot be found. NDIRExplanation: NDIR's "/vol" option makes a call to get information about the volume's login control property. This call has failed, and NDIR has terminated.Action: Try again. If the problem persists, check for problems at the server.410: The NetWare server cannot be accessed to get the number of volumes. NDIRExplanation: NDIR's "/vol" option makes a call to get the number of volumes. This call has failed, and NDIR has terminated.Action: Try again. If the problem persists, check for problems at the server.PAGENUM=539 ID="BP533"810: The chain contains too many filenames.NDIRExplanation: NDIR allows you to chain together up to 16 filenames in a search. More than 16 filenames were given, so NDIR has terminated.Action: Restrict the search to 16 filenames.852: Macintosh files are not supported on this server or drive.NDIRExplanation: NDIR allows the display of long name spaces supported on a server. However, the Macintosh file system is not supported on the given path, and NDIR has terminated.Action: Try one or both of the following:MARK=BULLETInstall Macintosh name space support.Specify another server or drive.854: Long names are not supported on this server or drive.NDIRExplanation: NDIR will display information about long name space file systems if name spaces are supported on the server or drive. However, no name space support has been loaded on the server or drive, and NDIR has terminated.Action: Try one or both of the following:MARK=BULLETLoad name space support.Specify another server or drive.856: The specified display format is not valid for local drives.NDIRExplanation: Information specific to NetWare or a server (for example, object property information, such as owners) is not available about files or directories on local drives. Action: For information about which formats may be available for local drives, see 
BOOK="ws_d1enu" COLLECTION="nw41"NetWare Client for DOS and MS Windows User Guide or 
BOOK="ws_osenu" COLLECTION="nw41"NetWare Client for OS/2 User Guide.858: The /COMPRESSED display option for compressed files is not supported on the specified server or drive.NDIRExplanation: The "Compressed" option is a new display option which gives information about compressed files, which are supported beginning with 4.0.Action: Use the "Compressed" option only with NetWare 4 and above.901: You are not attached to the specified server.NDIRAction: See message IDREF="FM84261""901: You are not attached to the specified server." in Appendix C.PAGENUM=540 ID="BP534"903: The command line syntax is invalid.NDIRAction: See message IDREF="FM18860""903: The command line syntax is invalid." in Appendix C.905: This utility was unable to initialize the country information.NDIRAction: See message IDREF="FM55337""905: This utility was unable to initialize the country information." in Appendix C.908: The specified path is invalid.NDIRAction: See message IDREF="FM51165""908: The specified path is invalid." in Appendix C.909: You are not mapped to the specified drive.NDIRAction: See message IDREF="FM28663""909: You are not mapped to the specified drive." in Appendix C.910: An error occurred during NDIR's attempt to parse the given path.NDIRAction: See message IDREF="FM47164""910: This utility was unable to parse the specified path." in Appendix C.912: The specified path or filename is invalid: path NDIRAction: See message IDREF="FM74299""912: The specified file cannot be found." in Appendix C.913: The specified directory cannot be found.NDIRAction: See message IDREF="FM19478""913: The specified directory cannot be found." in Appendix C.915: The specified volume could not be found.NDIRAction: See message IDREF="FM46881""915: The specified volume does not exist." in Appendix C.916: You have reached the maximum number of directory levels allowed. NDIRAction: See message IDREF="FM77950""916: This utility only supports 25 levels of directories." in Appendix C.917: This utility was unable to create context.NDIRAction: See message IDREF="FM32126""917: This utility was unable to set the context." in Appendix C.918: This utility was unable to get connection information.NDIRExplanation: This utility was unable to obtain information about a particular server. No other information is available.Action: Try issuing the command again from a different drive. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=541 ID="BP535"920: This utility was unable to allocate number bytes of memory.NDIRAction: See message IDREF="FM30331""920: This utility was unable to allocate number bytes of memory." in Appendix C.921: Either the supervisor has locked the bindery or volume SYS: is not mounted.NDIRAction: See message IDREF="FM49837""921: Either the supervisor has locked the bindery or volume SYS: is not mounted." in Appendix C.925: The server specified is a Personal NetWare server. You cannot attach to a Personal NetWare server with this utility. Use the Personal NetWare utilities to access this connection.NDIRAction: See message IDREF="FM67645""925: The server specified is a Personal NetWare server. You cannot attach to a Personal NetWare server with this utility. Use the Personal NetWare utilities to access this connection." in Appendix C.970: The attempt to open the Unicode table files failed.NDIRAction: See message IDREF="FM15675""970: The attempt to open the Unicode table files failed." in Appendix C.971: The workstation does not have enough memory to load the Unicode table files.NDIRAction: See message IDREF="FM55341""971: The workstation does not have enough memory to load the Unicode table files." in Appendix C.972: Access to the Unicode table files was denied.NDIRExplanation: See message IDREF="FM90152""972: Access to the Unicode table files was denied." in Appendix C.973: The Unicode table files cannot be found in the NLS directory or in the search path. Code page: number  Country:  numberNDIRAction: See message IDREF="FM62778""973: The Unicode table files cannot be found in the NLS directory or in the search path. Code page: number Country: number" in Appendix C.PAGENUM=542 ID="BP536"974: The Unicode table files are corrupt.NDIRExplanation: See message IDREF="FM63405""974: The Unicode table files are corrupt." in Appendix C.975: The Unicode table files cannot be opened because there are already too many open files. Close some files or modify your CONFIG.SYS file.NDIRAction: See message IDREF="FM49793""975: The Unicode table files cannot be opened because there are already too many open files. Close some files or modify your CONFIG.SYS file." in Appendix C.991: An error occurred in function_name. Error code: code.NDIRAction: See message IDREF="FM92553""991: An error occurred in function_name. Error code: code." in Appendix C.998: The message file found (<utility_name>.MSG) is an incorrect version. The correct version is number. See your network supervisor for assistance.NDIRAction: See message IDREF="FM91957""998: The message file found (utility_name.MSG) is an incorrect version. The correct version is number. See your network supervisor for assistance." in Appendix C.999: The message file for this utility cannot be found.NDIRAction: See message IDREF="FM69424""999: The message file for this utility cannot be found." in Appendix C.PAGENUM=543 ID="BP537"NDS1: The message file name is invalid. The program cannot be loaded.NDSExplanation: The .MSG file is invalid. This problem could be the result of a corrupted file, a faulty translation, or an outdated file version.Action: Either update the .MSG file with a valid copy, or delete the file. The DOS Requester will use the default messages that are bound to the binary files.5: Module1.VLM is not loaded. The module2.VLM file cannot be loaded before module1.VLM. Load the module1.VLM file first then try to load the module2.VLM file.NDSExplanation: The module2.VLM requires that the module1.VLM be loaded first. Either the current configuration has module1.VLM and module2.VLM loading out of order, or module1.VLM did not load successfully.Action: Make sure the module1.VLM is configured to load before module2.VLM. To do this, change the load order of the "VLM=" parameter in the NET.CFG file.7: In order to load the module3.VLM, one of the following VLMs must be loaded: module1.VLM, module2.VLM.NDSExplanation: The module3.VLM requires that module1.VLM or module2.VLM be loaded first. Either the current configuration has module3.VLM loading before the modules in the module1.VLM or module2.VLM list, or module1.VLM or module2.VLM did not load successfully.Action: Make sure the module1.VLM or module2.VLM loads successfully before module3.VLM.42: There is a missing or invalid value for `parameter' on line number of the configuration file. This entry will be ignored. Correct the line specified in the configuration file before continuing.NDSExplanation: The configuration file contains a configuration keyword that has an invalid parameter or that does not specify a parameter. This invalid line will be ignored by the configuration process.Action: Because this line will be ignored, no action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message.PAGENUM=544 ID="BP538"43: There is a missing or invalid ON/OFF value for `parameter' on line number of the configuration file. This entry will be ignored. Correct the line specified in the configuration file before continuing.NDSExplanation: The configuration file contains a configuration keyword that is defined to use either an "On" or "Off" parameter, but a different parameter or no parameter has been specified. This invalid line will be ignored by the configuration process.Action: Because this line will be ignored, no action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message.45: The parameter specified for the following option was out of range and has been adjusted.NDSExplanation: A configurable parameter has been configured too high or too low to be valid. The parameter is specified on the line following the message.Action: Correct the parameter specified in the NET.CFG file. For more information about the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.PAGENUM=545 ID="BP539"NE1000-DOS001: The LSL is not loaded.NE1000-DOSExplanation: The computer must load the Link Support Layer (LSL) before loading the driver.Action: Load the LSL; then load the driver, as in the following example:FORMAT="LINESPECIFIC"MOREINFO="NONE"C:\NWCLIENT\LSL MOREINFO="NONE"<Enter> 
C:\NWCLIENT\NE1000 MOREINFO="NONE"<Enter> 002: The LSL has no room for a board using frame type.NE1000-DOSExplanation: The Link Support Layer (LSL) is configured with resources for a set number of network boards. (The default is 4.) This number has been exceeded.Action: Edit the NET.CFG file, and add the MAX BOARDS keyword to reflect the number of network boards to be loaded, as in the following example: FORMAT="LINESPECIFIC"MOREINFO="NONE"LINK SUPPORT 
   MAX BOARDS 6 Unload the driver; then reload it as in the following example:FORMAT="LINESPECIFIC"MOREINFO="NONE"C:\NWCLIENT\NE1000 /u MOREINFO="NONE"<Enter> 
C:\NWCLIENT\NE1000 MOREINFO="NONE"<Enter> 003: Could not find NE1000 MLID to unload.NE1000-DOSExplanation: The NE1000 driver is not loaded.Action: None. This message is for information only.004: A TSR is loaded above the NE1000 MLID.NE1000-DOSExplanation: Another TSR (terminate-and-stay-resident) program was loaded after the NE1000 driver.Action: The drivers must be unloaded in reverse order, as follows:FORMAT="LINESPECIFIC"MOREINFO="NONE"C:\NWCLIENT\NETX /u MOREINFO="NONE"<Enter> 
C:\NWCLIENT\IPXODI /u MOREINFO="NONE"<Enter> 
C:\NWCLIENT\NE1000 /u MOREINFO="NONE"<Enter> 
PAGENUM=546 ID="BP540"Unload the TSRs; then try to unload the NE1000 driver. You can force the NE1000 driver to unload from the command line by using the "/F" switch after the driver name, as follows:FORMAT="LINESPECIFIC"MOREINFO="NONE"C:\NWCLIENT\NE1000 /f MOREINFO="NONE"<Enter> Use caution when using the /F switch because it could cause the computer to hang.005: NE1000 MLID could not be unloaded; the operation was aborted.NE1000-DOSExplanation: The NE1000 driver could not be shut down and unregistered; consequently, it cannot be unloaded.Action: To unload the driver, reboot the computer.006: The adapter did not initialize. NE1000 did not load.NE1000-DOSExplanation: The NE1000 driver encountered an error while loading.Action: Corrective action can vary. See the preceding driver-specific message on the screen for specific information about the error that occurred.007: You need another MLID section heading in the NET.CFG file in order to load the MLID again. NE1000-DOSExplanation: The NET.CFG file does not have an individual entry for each driver that is intended to be loaded.  This means that one of the drivers is not loaded into memory.Action: Unload the NE1000 driver. Modify the NET.CFG file to contain a unique entry for each driver to be loaded. This requires an individual Link Driver heading in the NET.CFG file for each driver or each instance of the same driver. Load the drivers again. For information on the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.008: A NET.CFG is required to load the MLID again.NE1000-DOSExplanation: The NET.CFG file does not have an individual entry for each driver that is intended to be loaded.  This means that one of the drivers is not loaded into memory.Action: Unload the NE1000 driver. Modify the NET.CFG file to contain a unique entry for each driver to be loaded. This requires an individual Link Driver heading in the NET.CFG file for each driver or each instance of the same driver. Load the drivers again. For information on the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.PAGENUM=547 ID="BP541"009: The NET.CFG entry has been ignored.NE1000-DOSExplanation: The NET.CFG file does not have an individual entry for each driver that is intended to be loaded.  This means that one of the drivers is not loaded into memory.Action: Unload the NE1000 driver. Modify the NET.CFG file to contain a unique entry for each driver to be loaded. This requires an individual Link Driver heading in the NET.CFG file for each driver or each instance of the same driver. Load the drivers again. For information on the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.011: The MLID does not support frame type. The protocol keyword has been ignored.NE1000-DOSExplanation: An unsupported or incorrectly typed frame type has been specified with the protocol keyword.Action: Verify that the frame type assigned under the protocol keyword in the NET.CFG file is valid. For a list of valid frame types, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.012: The protocol keyword must have a frame type. Entry ignored.NE1000-DOSExplanation: The PROTOCOL keyword entry is incomplete.Action: Correct the protocol entry in the NET.CFG file. The proper syntax for the protocol keyword is as follows:FORMAT="LINESPECIFIC"MOREINFO="NONE"PROTOCOL NE1000 hex_protocol_ID frame_type For information about the PROTOCOL keyword, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.013: The MLID could not register Protocol ID number for protocol stack name for frame type type.NE1000-DOSExplanation: The Link Support Layer (LSL) is configured with resources for a set number of Protocol Identifiers. (The default is 4.) This number has been exceeded.Action: Edit the NET.CFG file, and add the MAX STACKS keyword to reflect the number of network boards to be loaded, as in the following example:FORMAT="LINESPECIFIC"MOREINFO="NONE"LINK SUPPORT 
   MAX STACKS 6 Unload the driver; then reload it as in the following example:FORMAT="LINESPECIFIC"MOREINFO="NONE"C:\NWCLIENT\NE1000 /u MOREINFO="NONE"<Enter> 
C:\NWCLIENT\LSL /u MOREINFO="NONE"<Enter> 
PAGENUM=548 ID="BP542"C:\NWCLIENT\LSL MOREINFO="NONE"<Enter> 
C:\NWCLIENT\NE1000MOREINFO="NONE" <Enter> 014: This version of the LSL is not supported.NE1000-DOSExplanation: The driver the computer is using supports only Link Support Layer (LSL) versions later than 1.0.Action: Unload the LSL and replace it with a newer version.015: The frame type is already active for frame frame_type.NE1000-DOSExplanation: The frame type is already loaded, and it cannot be loaded repeatedly.Action: Edit the NET.CFG file to load the frame type only once for a given network board. For information about frame types, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.016: The node address was incorrectly specified in the NET.CFG file.NE1000-DOSExplanation: The node address override in the NET.CFG file is too long.Action: Edit the NET.CFG file and correct the node address. The node address must be less than or equal to 12 hex digits. For information about node address override, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.017: An invalid keyword was specified in NET.CFG on line number.NE1000-DOSExplanation: The key word on the indicated line was not recognized.Action: Edit the NET.CFG file and correct the spelling of the keyword. For valid keywords, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.018: The frame type specified in the NET.CFG is not supported.NE1000-DOSExplanation: The frame type specified with the FRAME keyword is not supported by the driver.Action: Edit the NET.CFG file and fix frame type. For information about supported frame types, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.PAGENUM=549 ID="BP543"019: An invalid NE1000 node address is specified in NET.CFG. The MLID modified the incorrect address bits.NE1000-DOSExplanation: The node address specified in the NET.CFG file contains set reserved bits.Action: Edit the NET.CFG file and correct the node address. For information about node addresses, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.050: The board cannot be found.NE1000-DOSExplanation: The network board was not found due to one or more of the following conditions: MARK=BULLETThe network board is not present in the computer. The network board settings are not the defaults, and they are not defined in the NET.CFG file.Another network board is using the same hardware settings as this network board.The network board is bad.Action: Do one or more of the following:MARK=BULLETMake sure the network board is properly seated into the slot. If jumper settings are not the defaults, make sure they match the settings in the NET.CFG file. If the computer is not using the NET.CFG file, make sure the jumper settings are set to the defaults. If other network boards are using the same hardware settings, change the settings and try to reload the driver.Replace the bad network board with one that is good.051: Board RAM failed the memory test.NE1000-DOSExplanation: The memory test on the network board's internal static RAM failed.Action: Check the network board and other hardware.  If necessary, replace the network board.PAGENUM=550 ID="BP544"NE1000-NW025: You cannot load MSM31X on a NetWare 3.10 server.NE1000-NWExplanation: The computer attempted to load MSM31X.NLM on a NetWare 3.10 server. MSM31X.NLM will run only on a NetWare 3.11 server.Action: Either load a version of the Media Support Module (MSM) that will run on a NetWare 3.10 server, or upgrade the server to NetWare 3.11. For information on MSM, see "BOOK="cncptenu" COLLECTION="nw41"Media Support Module (MSM)" in Concepts.026: On a NetWare 3.11 server, you must load LSLENH.NLM before you load MSM31X.NLM.NE1000-NWExplanation: The Link Support Layer (LSL) and Media Support Module (MSM) have been loaded on a NetWare 3.11 server. An attempt was made to load LSLENH.NLM. The computer cannot load LSLENH.NLM once the MSM has been loaded. (LSLENH.NLM adds enhancement to the LSL.)Action: Unload MSM31X.NLM; then load LSLENH.NLM. Once the LSLENH.NLM has been loaded, load MSM31X.NLM again. For information about LSL and MSM, see "BOOK="cncptenu" COLLECTION="nw41"Link Support Layer (LSL)" and "BOOK="cncptenu" COLLECTION="nw41"Media Support Module (MSM)" in Concepts.051: Board RAM failed the memory test.NE1000-NWExplanation: The memory test on the network board's internal static RAM failed.Action: Make sure the I/O port settings on the network board match the I/O port settings in the AUTOEXEC.NCF file. For information about the AUTOEXEC.NCF file, see "BOOK="superenu" COLLECTION="nw41"Maintaining the NetWare Server" in Supervising the Network. If the settings match, replace the network board.054: The board did not respond to the initialization command.NE1000-NWExplanation: The network board didn't respond to a reset command.Action: Make sure the I/O port settings on the network board match the I/O port settings in the AUTOEXEC.NCF file. For information about the AUTOEXEC.NCF file, see "BOOK="superenu" COLLECTION="nw41"Maintaining the NetWare Server" in Supervising the Network. If the settings match, replace the network board.PAGENUM=551 ID="BP545"066-Adapter 1: The cable might be disconnected on the board.NE1000-NWExplanation: The cable may be disconnected, or heavy traffic on the wire is delaying a packet from being sent.Action: If the problem persists, check the cable, or consider adding more networks to decrease LAN traffic.067: The group bit in the node address override was cleared.NE1000-NWExplanation: You entered a node address with the Group address bit set; the Topology Specific Module (TSM) cleared it.Action: None. This message is for information only. For information about TSM, see "BOOK="cncptenu" COLLECTION="nw41"Topology Specific Module (TSM)" in Concepts.068: The local bit in the node address override was set.NE1000-NWExplanation: You entered a node address without the local bit being set; the Topology Specific Module (TSM) set it. Action: None. This message is for information only. For information about TSM, see "BOOK="cncptenu" COLLECTION="nw41"Topology Specific Module (TSM)" in Concepts.071: The matching virtual adapter could not be found.NE1000-NWExplanation: A new frame was being added to an existing network board, but the Media Support Module (MSM) could not locate a previous network board to link it with.Action: Obtain the most current version of MSM.NLM. For information about MSM, see "BOOK="cncptenu" COLLECTION="nw41"Media Support Module (MSM)" in Concepts072: A resource tag is unavailable.NE1000-NWExplanation: The server may not have enough available memory. NetWare cannot allocate memory for a resource tag.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.073: Unable to allocate memory.NE1000-NWExplanation: The server may not have enough available memory. NetWare cannot allocate memory for the LAN driver.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.PAGENUM=552 ID="BP546"074: The hardware interrupt cannot be set.NE1000-NWExplanation: NetWare could not set the hardware interrupt that the LAN driver registered. The LAN driver must have changed information in the configuration table (IntNumber, SharingFlags) after the hardware options were registered.Action: Make sure the interrupt setting on the board matches the setting in the AUTOEXEC.NCF file. For information about the AUTOEXEC.NCF file, see "BOOK="superenu" COLLECTION="nw41"Maintaining the NetWare Server" in Supervising the Network.075: The MLID cannot be registered with the LSL.NE1000-NWExplanation: The LAN driver's Link Support Layer (LSL) ran out of logical boards, or it could not allocate memory for its internal structures.Action: Unload nonessential LAN drivers that are consuming large numbers of logical boards. Increase the available memory. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. For information about LSL, see "BOOK="cncptenu" COLLECTION="nw41"Link Support Layer (LSL)" in Concepts.076: The polling procedure cannot be added.NE1000-NWExplanation: Too many polling processes are registered with the operating system.Action: Unload nonessential NLMs that may be using a polling procedure.077: The event notification routine cannot be registered.NE1000-NWExplanation: The server may not have enough available memory. NetWare cannot allocate memory for internal structures related to event notification. Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.079: The MLID did not initialize MSMTxFreeCount.NE1000-NWExplanation: The .LAN file is either outdated or corrupted.Action: Obtain a new .LAN file.086: The driver parameter block is too small.NE1000-NWExplanation: The .LAN file is designed to run with an older version of the MSM.NLM.Action: Obtain a newer version of the .LAN file or an older version of the MSM.NLM.087: The media parameter block is too small.NE1000-NWExplanation: The topology NLM is designed to run with an older version of the MSM.NLM.Action: Obtain a newer version of the topology NLM or an older version of the MSM.NLM.PAGENUM=553 ID="BP547"091: The hardware configuration conflicts.NE1000-NWExplanation: Another hardware resource is being used, which the LAN driver is trying to register.Action: Change the hardware configuration of the network board or of the conflicting device.092: Cannot schedule AES without an HSM routine.NE1000-NWExplanation: The LAN driver is either outdated or corrupted.Action: Obtain a new .LAN file.093: Cannot schedule interrupt time call back without an HSM routine.NE1000-NWExplanation: The LAN driver is either outdated or corrupted.Action: Obtain a new .LAN file.094: Cannot set hardware interrupt without an HSM routine.NE1000-NWExplanation: The LAN driver is either outdated or corrupted.Action: Obtain a new .LAN file.095: Cannot add polling without an HSM routine.NE1000-NWExplanation: The LAN driver is either outdated or corrupted.Action: Obtain a new .LAN file.200-Adapter 1: The board's DMA did not complete the write.NE1000-NWExplanation: The network board didn't complete a DMA transaction within the specified time. The driver will attempt to correct the problem by resetting the network board and resending the packet.Action: If the problem occurs often (more than once or twice a day), replace the network board.PAGENUM=554 ID="BP548"NE1000-OS2001: The LSL is not loaded.NE1000-OS2Explanation: The Link Support Layer (LSL) module must be loaded before the computer can install the driver.Action: Edit the CONFIG.SYS file to load the LSL before the LAN driver, as in the following example:FORMAT="LINESPECIFIC"MOREINFO="NONE"DEVICE=C:\NETWARE\LSL.SYS 
DEVICE=C:\NETWARE\NE1000.SYS For information about LSL, see "BOOK="cncptenu" COLLECTION="nw41"Link Support Layer (LSL)" in Concepts.021: Could not add MLID Protocol ID.NE1000-OS2Explanation: The Link Support Layer (LSL) is configured with resources for four Protocol Identifiers. This number has been exceeded.Action: None. This message is for information only. For information about LSL, see "BOOK="cncptenu" COLLECTION="nw41"Link Support Layer (LSL)" in Concepts.022: Could not allocate memory. Virtual board did not load.NE1000-OS2Explanation: The computer cannot allocate enough memory to load another network board.Action: Do one of the following:MARK=BULLETInstall more memory in the computer.Edit the CONFIG.SYS file, and remove any nonessential drivers. For information about the CONFIG.SYS file, see 
BOOK="ws_osenu" COLLECTION="nw41"NetWare Client for OS/2 User Guide. 050: The board cannot be found.NE1000-OS2Explanation: The network board was not found due to one or more of the following conditions: MARK=BULLETThe network board is not present in the computer. The network board settings are not the defaults, and they are not defined in the NET.CFG file.Another network board is using the same hardware settings as this network board.PAGENUM=555 ID="BP549"The network board is bad.Action: Do one or more of the following:MARK=BULLETMake sure the network board is properly seated into the slot. If jumper settings are not the defaults, make sure they match the settings in the NET.CFG file. If the computer is not using the NET.CFG file, make sure the jumper settings are set to the defaults. If other network boards are using the same hardware settings, change the settings and try to reload the driver.Replace the bad network board with one that is good.056: This interrupt is already used and cannot be shared.NE1000-OS2Explanation: The selected interrupt is being used by another device, so it cannot be used for this network board.Action: Change the jumper setting on the network board to use a different interrupt. See the NE1000 hardware manual for information about jumper settings. Edit the NET.CFG file to reflect the correct interrupt level used by the network board. For information about the NET.CFG file, see "BOOK="ws_osenu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for OS/2 User Guide.240: Invalid Node Override, Group Address bit was set now reset.NE1000-OS2Explanation: The driver address specified in the NET.CFG file contains the group bit set. Note: If no address is specified, the driver will use the default address assigned by the network board's manufacturer.Action: No action is necessary; the bit was cleared by the driver. However, to prevent this error message from being displayed every time the driver is loaded, edit the NET.CFG file and correct the node address override, as is shown in the following example:FORMAT="LINESPECIFIC"MOREINFO="NONE"LINK DRIVER NE1000 
    NODE ADDRESS address For information about editing the NET.CFG file, see "BOOK="ws_osenu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for OS/2 User Guide.PAGENUM=556 ID="BP550"241: Invalid Node Override, Local Administrated bit was set now reset.NE1000-OS2Explanation: The driver address specified in the NET.CFG file does not have the locally administered bit set. Note: If no address is specified, the driver will use the default address assigned by the network board's manufacturer.Action: No action is necessary; the bit was set by the driver. However, to prevent this error message from being displayed every time the driver is loaded, edit the NET.CFG file and correct the node address override, as is shown in the following example:FORMAT="LINESPECIFIC"MOREINFO="NONE"LINK DRIVER NE1000 
    NODE ADDRESS address For information about editing the NET.CFG file, see "BOOK="ws_osenu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for OS/2 User Guide.PAGENUM=557 ID="BP551"NE1500T-DOS001: The LSL is not loaded.NE1500T-DOSExplanation: The computer must load the Link Support Layer (LSL) before loading the driver.Action: Load the LSL; then load the driver, as in the following example:FORMAT="LINESPECIFIC"MOREINFO="NONE"C:\NWCLIENT\LSL MOREINFO="NONE"<Enter> 
C:\NWCLIENT\NE1500T MOREINFO="NONE"<Enter> For information about LSL, see"BOOK="cncptenu" COLLECTION="nw41"Link Support Layer (LSL)" in Concepts.002: The LSL has no room for a board using frame type.NE1500T-DOSExplanation: The Link Support Layer (LSL) is configured with resources for a set number of network boards. (The default is 4.) This number has been exceeded.Action: Edit the NET.CFG file, and add the MAX BOARDS keyword to reflect the number of network boards to be loaded, as in the following example: FORMAT="LINESPECIFIC"MOREINFO="NONE"LINK SUPPORT 
    MAX BOARDS 6 Unload the driver; then reload it as in the following example:FORMAT="LINESPECIFIC"MOREINFO="NONE"C:\NWCLIENT\NE1500T /u MOREINFO="NONE"<Enter> 
C:\NWCLIENT\NE1500TMOREINFO="NONE" <Enter> For information on the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.003: Could not find NE1500T MLID to unload.NE1500T-DOSExplanation: The NE1500T driver is not loaded.Action: None. This message is for information only.004: A TSR is loaded above the NE1500T MLID.NE1500T-DOSExplanation: Another TSR (terminate-and-stay-resident) program was loaded after the NE1500T driver.Action: The drivers must be unloaded in reverse order, as follows:FORMAT="LINESPECIFIC"MOREINFO="NONE"C:\NWCLIENT\NETX /u MOREINFO="NONE"<Enter> 
PAGENUM=558 ID="BP552"C:\NWCLIENT\IPXODI /u MOREINFO="NONE"<Enter> 
C:\NWCLIENT\NE1500T /u MOREINFO="NONE"<Enter> Unload the TSRs; then try to unload the NE1500T driver. You can force the NE1500T driver to unload from the command line by using the /F switch after the driver name, as follows:FORMAT="LINESPECIFIC"MOREINFO="NONE"C:\NWCLIENT\NE1500T /f MOREINFO="NONE"<Enter> Use caution when using the /F switch because it could cause the computer to hang.005: NE1500T MLID could not be unloaded; the operation was aborted.NE1500T-DOSExplanation: The NE1500T driver could not be shut down and unregistered; consequently, it cannot be unloaded.Action: To unload the driver, reboot the computer.006: The adapter did not initialize. NE1500T did not load.NE1500T-DOSExplanation: The NE1500T driver encountered an error while loading.Action: Corrective action can vary. See the preceding driver-specific message on the screen for specific information about the error that occurred.007: You need another MLID section heading in the NET.CFG file in order to load the MLID again. NE1500T-DOSExplanation: The NET.CFG file does not have an individual entry for each driver that is intended to be loaded.  This means that one of the drivers is not loaded into memory.Action: Unload the NE1500T driver. Modify the NET.CFG file to contain a unique entry for each driver to be loaded. This requires an individual Link Driver heading in the NET.CFG file for each driver or each instance of the same driver. Load the drivers again. For information on the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.008: A NET.CFG is required to load the MLID again.NE1500T-DOSExplanation: The NET.CFG file does not have an individual entry for each driver that is intended to be loaded.  This means that one of the drivers is not loaded into memory.Action: Unload the NE1500T driver. Modify the NET.CFG file to contain a unique entry for each driver to be loaded. This requires an individual Link Driver heading in the NET.CFG file for each driver or each instance of the same driver. Load the drivers again. For information on the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.PAGENUM=559 ID="BP553"009: The NET.CFG entry has been ignored.NE1500T-DOSExplanation: The NET.CFG file does not have an individual entry for each driver that is intended to be loaded.  This means that one of the drivers is not loaded into memory.Action: Unload the Link Driver. Modify the NET.CFG file to contain a unique entry for each driver to be loaded. This requires an individual Link Driver heading in the NET.CFG file for each driver or each instance of the same driver. Load the drivers again. For information on the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.011: The MLID does not support frame type. The protocol keyword has been ignored.NE1500T-DOSExplanation: An unsupported or incorrectly typed frame type has been specified with the protocol keyword.Action: Verify that the frame type assigned under the protocol keyword in the NET.CFG file is valid. For a list of valid frame types, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.012: The protocol keyword must have a frame type. Entry ignored.NE1500T-DOSExplanation: The PROTOCOL keyword entry is incomplete.Action: Correct the protocol entry in the NET.CFG file. The proper syntax for the protocol keyword is as follows:FORMAT="LINESPECIFIC"MOREINFO="NONE"PROTOCOL NE1500T hex_protocol_ID frame_type For information about the PROTOCOL keyword, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.013: The MLID could not register Protocol ID number for protocol stack name for frame type frame_type.NE1500T-DOSExplanation: The Link Support Layer (LSL) is configured with resources for a set number of Protocol Identifiers. (The default is 4.) This number has been exceeded.Action: Edit the NET.CFG file, and add the MAX STACKS keyword to reflect the number of network boards to be loaded, as in the following example:FORMAT="LINESPECIFIC"MOREINFO="NONE"LINK SUPPORT 
    MAX STACKS 6 Unload the driver; then reload it as in the following example:FORMAT="LINESPECIFIC"MOREINFO="NONE"C:\NWCLIENT\NE1500T /u MOREINFO="NONE"<Enter> 
C:\NWCLIENT\LSL /u MOREINFO="NONE"<Enter> 
PAGENUM=560 ID="BP554"C:\NWCLIENT\LSL MOREINFO="NONE"<Enter> 
C:\NWCLIENT\NE1500TMOREINFO="NONE" <Enter> For information on the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.014: This version of the LSL is not supported.NE1500T-DOSExplanation: The Link Driver the computer is using supports only Link Support Layer (LSL) versions later than 1.0.Action: Unload the LSL and replace it with a newer version. For information about LSL, see "BOOK="cncptenu" COLLECTION="nw41"Link Support Layer (LSL)" in Concepts.015: The frame type is already active for frame frame_type.NE1500T-DOSExplanation: The frame type is already loaded, and it cannot be loaded repeatedly.Action: Edit the NET.CFG file to load the frame type only once for a given network board. For information about frame types, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.016: The node address was incorrectly specified in the NET.CFG file.NE1500T-DOSExplanation: The node address override in the NET.CFG file is too long.Action: Edit the NET.CFG file and correct the node address. The node address must be less than or equal to 12 hex digits. For information about node address override, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.017: An invalid keyword was specified in NET.CFG on line number.NE1500T-DOSExplanation: The key word on the line indicated was not recognized.Action: Edit the NET.CFG file and correct the spelling of the keyword. For valid keywords, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.018: The frame type specified in the NET.CFG is not supported.NE1500T-DOSExplanation: The frame type specified with the FRAME keyword is not supported by the driver.Action: Edit the NET.CFG file and fix frame type. For information on supported frame types, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.PAGENUM=561 ID="BP555"019: An invalid NE1500T node address is specified in NET.CFG. The MLID modified the incorrect address bits.NE1500T-DOSExplanation: The node address specified in the NET.CFG file contains set reserved bits.Action: Edit the NET.CFG file and correct the node address. For information about node addresses, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.050: The board cannot be found.NE1500T-DOSExplanation: The network board was not found due to one or more of the following conditions: MARK=BULLETThe network board is not present in the computer. The network board settings are not the defaults, and they are not defined in the NET.CFG file.Another network board is using the same hardware settings as this network board.The network board is bad.Action: Do one or more of the following:MARK=BULLETMake sure the network board is properly seated into the slot. If jumper settings are not the defaults, make sure they match the settings in the NET.CFG file. If the computer is not using the NET.CFG file, make sure the jumper settings are set to the defaults. If other network boards are using the same hardware settings, change the settings and try to reload the driver.Replace the bad network board with one that is good.054: The board did not respond to the initialization command.NE1500T-DOSExplanation: A hardware error has occurred.Action: Power down the computer; then reboot it. If the network board still does not respond, replace it with one that is good.PAGENUM=562 ID="BP556"NE1500T-NW025: You cannot load MSM31X on a NetWare 3.10 server.NE1500T-NWExplanation: The computer attempted to load MSM31X.NLM on a NetWare 3.10 server. MSM31X.NLM will run only on a NetWare 3.11 server.Action: Either load a version of the Media Support Module (MSM) that will run on a NetWare 3.10 server, or upgrade the server to NetWare 3.11. For information about MSM, see "BOOK="cncptenu" COLLECTION="nw41"Media Support Module (MSM)" in Concepts.026: On a NetWare 3.11 server, you must load LSLENH.NLM before you load MSM31X.NLM.NE1500T-NWExplanation: The Link Support Layer (LSL) and Media Support Module (MSM) have been loaded on a NetWare 3.11 server. An attempt was made to load LSLENH.NLM. The computer cannot load LSLENH.NLM once the MSM has been loaded. (LSLENH.NLM adds enhancement to the LSL.)Action: Unload MSM31X.NLM; then load LSLENH.NLM. Once the LSLENH.NLM has been loaded, load MSM31X.NLM again. For information about LSL and MSM, see "BOOK="cncptenu" COLLECTION="nw41"Link Support Layer (LSL)" and "BOOK="cncptenu" COLLECTION="nw41"Media Support Module (MSM)" in Concepts.054: The board did not respond to the initialization command.NE1500T-NWExplanation: The network board didn't respond to a reset command.Action: Make sure the I/O port settings on the network board match the I/O port settings in the AUTOEXEC.NCF file. For information about the AUTOEXEC.NCF file, see "BOOK="superenu" COLLECTION="nw41"Maintaining the NetWare Server" in Supervising the Network.) If the settings match, replace the network board.066-Adapter 1: The cable might be disconnected on the board.NE1500T-NWExplanation: The cable may be disconnected, or heavy traffic on the wire is delaying a packet from being sent.Action: If the problem persists, check the cable, or consider adding more networks to decrease LAN traffic.067: The group bit in the node address override was cleared.NE1500T-NWExplanation: You entered a node address with the Group address bit set; the Topology Specific Module (TSM) cleared it. For information about TSM, see "BOOK="cncptenu" COLLECTION="nw41"Topology Specific Module (TSM)" in Concepts.Action: None. This message is for information only.PAGENUM=563 ID="BP557"068: The local bit in the node address override was set.NE1500T-NWExplanation: You entered a node address without the local bit being set; the Topology Specific Module (TSM) set it. Action: None. This message is for information only. For information about TSM, see "BOOK="cncptenu" COLLECTION="nw41"Topology Specific Module (TSM)" in Concepts.071: The matching virtual adapter could not be found.NE1500T-NWExplanation: A new frame was being added to an existing network board, but the Media Support Module (MSM) could not locate a previous network board to link it with.Action: Obtain the most current version of MSM.NLM. For information about MSM, see "BOOK="cncptenu" COLLECTION="nw41"Media Support Module (MSM)" in Concepts.072: A resource tag is unavailable.NE1500T-NWExplanation: The server may not have enough available memory. NetWare cannot allocate memory for a resource tag.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.073: Unable to allocate memory.NE1500T-NWExplanation: The server may not have enough available memory. NetWare cannot allocate memory for the LAN driver.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.074: The hardware interrupt cannot be set.NE1500T-NWExplanation: NetWare could not set the hardware interrupt that the LAN driver registered. The LAN driver must have changed information in the configuration table (IntNumber, SharingFlags) after the hardware options were registered.Action: Make sure the interrupt setting on the board matches the setting in the AUTOEXEC.NCF file. For information about the AUTOEXEC.NCF file, see "BOOK="superenu" COLLECTION="nw41"Maintaining the NetWare Server" in Supervising the Network.075: The MLID cannot be registered with the LSL.NE1500T-NWExplanation: The LAN driver's Link Support Layer (LSL) ran out of logical boards, or it could not allocate memory for its internal structures.Action: Unload nonessential LAN drivers that are consuming large numbers of logical boards. Increase the available memory. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. For information about LSL, see "BOOK="cncptenu" COLLECTION="nw41"Link Support Layer (LSL)" in Concepts.PAGENUM=564 ID="BP558"076: The polling procedure cannot be added.NE1500T-NWExplanation: Too many polling processes are registered with the operating system.Action: Unload nonessential NLMs that may be using a polling procedure.077: The event notification routine cannot be registered.NE1500T-NWExplanation: The server may not have enough available memory. NetWare cannot allocate memory for internal structures related to event notification. Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.079: The MLID did not initialize MSMTxFreeCount.NE1500T-NWExplanation: The .LAN file may be outdated or corrupted.Action: Obtain a new .LAN file.086: The driver parameter block is too small.NE1500T-NWExplanation: The .LAN file is designed to run with an older version of the MSM.NLM.Action: Obtain a newer version of the .LAN file or an older version of the MSM.NLM.087: The media parameter block is too small.NE1500T-NWExplanation: The topology NLM is designed to run with an older version of the MSM.NLM.Action: Obtain a newer version of the topology NLM or an older version of the MSM.NLM.091: The hardware configuration conflicts.NE1500T-NWExplanation: Another hardware resource is being used, which the LAN driver is trying to register.Action: Change the hardware configuration of the network board or of the conflicting device.092: Cannot schedule AES without an HSM routine.NE1500T-NWExplanation: The LAN driver is either outdated or corrupted.Action: Obtain a new .LAN file.093: Cannot schedule interrupt time call back without an HSM routine.NE1500T-NWExplanation: The LAN driver is either outdated or corrupted.Action: Obtain a new .LAN file.PAGENUM=565 ID="BP559"094: Cannot set hardware interrupt without an HSM routine.NE1500T-NWExplanation: The LAN driver is either outdated or corrupted.Action: Obtain a new .LAN file.095: Cannot add polling without an HSM routine.NE1500T-NWExplanation: The LAN driver is either outdated or corrupted.Action: Obtain a new .LAN file.PAGENUM=566 ID="BP560"NE1500T-OS2001: The LSL is not loaded.NE1500T-OS2Explanation: The Link Support Layer (LSL) module must be loaded before the computer can install the driver.Action: Edit the CONFIG.SYS file to load the LSL before the LAN driver, as in the following example:FORMAT="LINESPECIFIC"MOREINFO="NONE"DEVICE=C:\NETWARE\LSL.SYS 
DEVICE=C:\NETWARE\NE1500T.SYS For information about the CONFIG.SYS file, see 
BOOK="ws_osenu" COLLECTION="nw41"NetWare Client for OS/2 User Guide. For information about LSL, see "BOOK="cncptenu" COLLECTION="nw41"Link Support Layer (LSL)" in Concepts.021: Could not add MLID Protocol ID.NE1500T-OS2Explanation: The Link Support Layer (LSL) is configured with resources for four Protocol Identifiers. This number has been exceeded.Action: None. This message is for information only.022: Could not allocate memory. Virtual board did not load.NE1500T-OS2Explanation: The computer cannot allocate enough memory to load another network board.Action: Do one of the following:MARK=BULLETInstall more memory in the computer.Edit the CONFIG.SYS file, and remove any unneeded drivers. For information about the CONFIG.SYS file, see 
BOOK="ws_osenu" COLLECTION="nw41"NetWare Client for OS/2 User Guide.050: The board cannot be found.NE1500T-OS2Explanation: The network board was not found due to one or more of the following conditions: MARK=BULLETThe network board is not present in the computer. The network board settings are not the defaults, and they are not defined in the NET.CFG file.Another network board is using the same hardware settings as this network board.PAGENUM=567 ID="BP561"The network board is bad.Action: Do one or more of the following:MARK=BULLETMake sure the network board is properly seated into the slot. If jumper settings are not the defaults, make sure they match the settings in the NET.CFG file. If the computer is not using the NET.CFG file, make sure the jumper settings are set to the defaults. If other network boards are using the same hardware settings, change the settings and try to reload the driver.Replace the bad network board with one that is good.056: This interrupt is already used and cannot be shared.NE1500T-OS2Explanation: The selected interrupt is being used by another device, so it cannot be used for this network board.Action: Change the jumper setting on the network board to use a different interrupt. For information about jumper settings, see the NE1500T hardware manual. Edit the NET.CFG file to reflect the correct interrupt level used by the network board. For information about the NET.CFG file, see "BOOK="ws_osenu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for OS/2 User Guide.073: Unable to allocate memory.NE1500T-OS2Explanation: Not enough free memory is available for the driver to initialize. The driver did not load.Action: Modify the CONFIG.SYS file so it loads only needed devices and drivers. Load the driver again. For information about the CONFIG.SYS file, see 
BOOK="ws_osenu" COLLECTION="nw41"NetWare Client for OS/2 User Guide. If necessary, install more memory on the computer. 240: Invalid Node Override, Group Address bit was set now reset.NE1500T-OS2Explanation: The driver address specified in the NET.CFG file contains the group bit set. Note: If no address is specified, the driver will use the default address assigned by the network board's manufacturer.Action: No action is necessary; the bit was cleared by the driver. However, to prevent this error message from being displayed every time the driver is loaded, edit the NET.CFG file and correct the node address override, as is shown in the following example:PAGENUM=568 ID="BP562"FORMAT="LINESPECIFIC"MOREINFO="NONE"LINK DRIVER NE1500T 
    NODE ADDRESS address For information about editing the NET.CFG file, see "BOOK="ws_osenu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for OS/2 User Guide.241: Invalid Node Override, Local Administrated bit was set now reset.NE1500T-OS2Explanation: The driver address specified in the NET.CFG file does not have the locally administered bit set. Note: If no address is specified, the driver will use the default address assigned by the network board's manufacturer.Action: No action is necessary; the bit was set by the driver. However, to prevent this error message from being displayed every time the driver is loaded, edit the NET.CFG file and correct the node address override, as is shown in the following example:FORMAT="LINESPECIFIC"MOREINFO="NONE"LINK DRIVER NE1500T 
    NODE ADDRESS address For information about editing the NET.CFG file, see "BOOK="ws_osenu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for OS/2 User Guide.242: Only one NE1500T board can be present in the machine.NE1500T-OS2Explanation: Only one physical network board can be present in the computer at one time. The driver does not support more than one logical board.Action: Remove one of the network boards from the computer, and edit the NET.CFG file to reflect that only one physical network board is present. For information on the NET.CFG file, see "BOOK="ws_osenu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for OS/2 User Guide.PAGENUM=569 ID="BP563"NE2_32-DOS001: The LSL is not loaded.NE2_32-DOSExplanation: The computer must load the Link Support Layer (LSL) before loading the driver.Action: Load the LSL; then load the driver, as in the following example:FORMAT="LINESPECIFIC"MOREINFO="NONE"C:\NWCLIENT\LSL MOREINFO="NONE"<Enter> 
C:\NWCLIENT\NE2_32 MOREINFO="NONE"<Enter> For information about LSL, see "BOOK="cncptenu" COLLECTION="nw41"Link Support Layer (LSL)" in Concepts.002: The LSL has no room for a board using frame type.NE2_32-DOSExplanation: The Link Support Layer (LSL) is configured with resources for a set number of network boards. (The default is 4.) This number has been exceeded.Action: Edit the NET.CFG file, and add the MAX BOARDS keyword to reflect the number of network boards to be loaded, as in the following example: FORMAT="LINESPECIFIC"MOREINFO="NONE"LINK SUPPORT 
    MAX BOARDS 6 Unload the driver; then reload it as in the following example:FORMAT="LINESPECIFIC"MOREINFO="NONE"C:\NWCLIENT\NE2_32 /u MOREINFO="NONE"<Enter> 
C:\NWCLIENT\NE2_32 
 MOREINFO="NONE"<Enter> For information on the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.003: Could not find NE2_32 MLID to unload.NE2_32-DOSExplanation: The NE2_32 driver is not loaded.Action: None. This message is for information only.004: A TSR is loaded above the NE2_32 MLID.NE2_32-DOSExplanation: Another TSR (terminate-and-stay-resident) program was loaded after the NE2_32 driver.Action: The drivers must be unloaded in reverse order, as follows:PAGENUM=570 ID="BP564"FORMAT="LINESPECIFIC"MOREINFO="NONE"C:\NWCLIENT\NETX /u MOREINFO="NONE"<Enter> 
C:\NWCLIENT\IPXODI /u MOREINFO="NONE"<Enter> 
C:\NWCLIENT\NE2_32 /u MOREINFO="NONE"<Enter> Unload the TSRs; then try to unload the NE2_32 driver. You can force the NE2-32 driver to unload from the command line by using the /F switch after the driver name, as follows:FORMAT="LINESPECIFIC"MOREINFO="NONE"C:\NWCLIENT\NE2_32 /f MOREINFO="NONE"<Enter> Use caution when using the /F switch because it could cause the computer to hang.005: NE2_32 MLID could not be unloaded; the operation was aborted.NE2_32-DOSExplanation: The NE2_32 driver could not be shut down and unregistered; consequently, it cannot be unloaded.Action: To unload the driver, reboot the computer.006: The adapter did not initialize. NE2_32 did not load.NE2_32-DOSExplanation: The NE2_32 driver encountered an error while loading.Action: Corrective action can vary. See the preceding driver-specific message on the screen for specific information about the error that occurred.007: You need another MLID section heading in the NET.CFG file in order to load the MLID again. NE2_32-DOSExplanation: The NET.CFG file does not have an individual entry for each driver that is intended to be loaded.  This means that one of the drivers is not loaded into memory.Action: Unload the NE2_32 driver. Modify the NET.CFG file to contain a unique entry for each driver to be loaded. This requires an individual Link Driver heading in the NET.CFG file for each driver or each instance of the same driver. Load the drivers again. For information on the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.Action: 008: A NET.CFG is required to load the MLID again.NE2_32-DOSExplanation: The NET.CFG file does not have an individual entry for each driver that is intended to be loaded.  This means that one of the drivers is not loaded into memory.Action: Unload the NE2_32 driver. Modify the NET.CFG file to contain a unique entry for each driver to be loaded. This requires an individual Link Driver heading in the NET.CFG file for each driver or each instance of the same driver. Load the drivers again. For information on the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.PAGENUM=571 ID="BP565"009: The NET.CFG entry has been ignored.NE2_32-DOSExplanation: The NET.CFG file does not have an individual entry for each driver that is intended to be loaded.  This means that one of the drivers is not loaded into memory..Action: Unload the Link Driver. Modify the NET.CFG file to contain a unique entry for each driver to be loaded. This requires an individual Link Driver heading in the NET.CFG file for each driver or each instance of the same driver. Load the drivers again. For information on the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.011: The MLID does not support frame type. The protocol keyword has been ignored.NE2_32-DOSExplanation: An unsupported or incorrectly typed frame type has been specified with the protocol keyword.Action: Verify that the frame type assigned under the protocol keyword in the NET.CFG file is valid. For a list of valid frame types, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.012: The protocol keyword must have a frame type. Entry ignored.NE2_32-DOSExplanation: The PROTOCOL keyword entry is incomplete.Action: Correct the protocol entry in the NET.CFG file. The proper syntax for the protocol keyword is as follows:FORMAT="LINESPECIFIC"MOREINFO="NONE"PROTOCOL NE2_32 hex_protocol_ID frame_type For information about the PROTOCOL keyword, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.013: The MLID could not register Protocol ID number for protocol stack name for frame type frame_type.NE2_32-DOSExplanation: The Link Support Layer (LSL) is configured with resources for a set number of Protocol Identifiers. (The default is 4.) This number has been exceeded.Action: Edit the NET.CFG file, and add the MAX STACKS keyword to reflect the number of network boards to be loaded, as in the following example:FORMAT="LINESPECIFIC"MOREINFO="NONE"LINK SUPPORT 
    MAX STACKS 6 Unload the driver; then reload it as in the following example:FORMAT="LINESPECIFIC"MOREINFO="NONE"C:\NWCLIENT\NE2_32 /u MOREINFO="NONE"<Enter> 
C:\NWCLIENT\LSL /u MOREINFO="NONE"<Enter> 
PAGENUM=572 ID="BP566"C:\NWCLIENT\LSL MOREINFO="NONE"<Enter> 
C:\NWCLIENT\NE2_32MOREINFO="NONE" <Enter> For information on the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.014: This version of the LSL is not supported.NE2_32-DOSExplanation: The Link Driver the computer is using supports only Link Support Layer (LSL) versions later than 1.0.Action: Unload the LSL and replace it with a newer version. For information about LSL, see "BOOK="cncptenu" COLLECTION="nw41"Link Support Layer (LSL)" in Concepts.015: The frame type is already active for frame frame_type.NE2_32-DOSExplanation: The frame type is already loaded, and it cannot be loaded repeatedly.Action: Edit the NET.CFG file to load the frame type only once for a given network board. For information about frame types, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.016: The node address was incorrectly specified in the NET.CFG file.NE2_32-DOSExplanation: The node address override in the NET.CFG file is too long.Action: Edit the NET.CFG file and correct the node address. The node address must be less than or equal to 12 hex digits. For information about node address override, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.017: An invalid keyword was specified in NET.CFG on line number.NE2_32-DOSExplanation: The key word on the line indicated was not recognized.Action: Edit the NET.CFG file and correct the spelling of the keyword. For valid keywords, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.018: The frame type specified in the NET.CFG is not supported.NE2_32-DOSExplanation: The frame type specified with the FRAME keyword is not supported by the driver.Action: Edit the NET.CFG file and fix frame type. For information on supported frame types, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.PAGENUM=573 ID="BP567"019: An invalid NE2_32 node address is specified in NET.CFG. The MLID modified the incorrect address bits.NE2_32-DOSExplanation: The node address specified in the NET.CFG file contains set reserved bits.Action: Edit the NET.CFG file and correct the node address. For information about node addresses, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.050: The board cannot be found.NE2_32-DOSExplanation: The network board is not present in the computer, or the network board's configuration cannot be obtained.Action: Do one of the following:MARK=BULLETMake sure the network board is properly seated into the slot. Insert the network board in a slot, and run the CLASS=DISKReference diskette to install it.051: Board RAM failed the memory test.NE2_32-DOSExplanation: The memory test on the network board's internal static RAM failed.Action: Check the network board and other hardware.  If necessary, replace the network board.052: The board cannot be found at the slot designated in NET.CFG.NE2_32-DOSExplanation: The NET.CFG file specifies that the network board is placed in a specific slot, but the network board cannot be found. If no slot is specified in the NET.CFG file, the driver searches all slots for the network board. If more than one network board is in the computer, the slots must be specified in the NET.CFG file.Action: If the slot that the network board is in does not match the slot specified in the NET.CFG file, do one of the following:MARK=BULLETCorrect the slot number in the NET.CFG file to match the slot where the network board is physically located. For information on the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.Move the network board to the slot specified in the NET.CFG file; then run the CLASS=DISKReference diskette to install the network board.PAGENUM=574 ID="BP568"053: The specified slot contains the correct board, but board is not enabled.NE2_32-DOSExplanation: When the network board was installed using the CLASS=DISKReference diskette, the option to disable the network board was selected.Action: Run the CLASS=DISKReference diskette and set the option to enable the network board.054: The board did not respond to the initialization command.NE2_32-DOSExplanation: A hardware error has occurred.Action: Power down the computer; then reboot it. If the network board still does not respond, replace it with one that is good.201: RAM address invalid. RAM address must be C0000h or D0000h.NE2_32-DOSExplanation: The configuration for the card is invalid.Action: Run the CLASS=DISKReference diskette and set the RAM memory address to either C0000h or D0000h.PAGENUM=575 ID="BP569"NE2_32-NW025: You cannot load MSM31X on a NetWare 3.10 server.NE2_32-NWExplanation: The computer attempted to load MSM31X.NLM on a NetWare 3.10 server. MSM31X.NLM will run only on a NetWare 3.11 server.Action: Either load a version of the Media Support Module (MSM) that will run on a NetWare 3.10 server, or upgrade the server to NetWare 3.11. For information about MSM, see "BOOK="cncptenu" COLLECTION="nw41"Media Support Module (MSM)" in Concepts.026: On a NetWare 3.11 server, you must load LSLENH.NLM before you load MSM31X.NLMNE2_32-NWExplanation: The Link Support Layer (LSL) and Media Support Module (MSM) have been loaded on a NetWare 3.11 server. An attempt was made to load LSLENH.NLM. The computer cannot load LSLENH.NLM once the MSM has been loaded. (LSLENH.NLM adds enhancement to the LSL.)Action: Unload MSM31X.NLM; then load LSLENH.NLM. Once the LSLENH.NLM has been loaded, load MSM31X.NLM again. For information on LSL and MSM, see "BOOK="cncptenu" COLLECTION="nw41"Link Support Layer (LSL)" and "BOOK="cncptenu" COLLECTION="nw41"Media Support Module (MSM)" in Concepts.050: The board cannot be found.NE2_32-NWExplanation: Either the network board is not present in the computer, or the network board's configuration cannot be obtained.Action: Do one of the following:MARK=BULLETMake sure the network board is properly seated into the slot. Insert the network board into a slot, and run the CLASS=DISKReference diskette to install it.051: Board RAM failed the memory test.NE2_32-NWExplanation: The memory test on the network board's internal static RAM failed.Action: Make sure the I/O port settings on the network board match the I/O port settings in the AUTOEXEC.NCF file. For information about the AUTOEXEC.NCF file, see "BOOK="superenu" COLLECTION="nw41"Maintaining the NetWare Server" in Supervising the Network. If the settings match, replace the network board.PAGENUM=576 ID="BP570"066-Adapter 1: The cable might be disconnected on the board.NE2_32-NWExplanation: The cable may be disconnected, or heavy traffic on the wire is delaying a packet from being sent.Action: If the problem persists, check the cable, or consider adding more networks to decrease LAN traffic.067: The group bit in the node address override was cleared.NE2_32-NWExplanation: You entered a node address with the Group address bit set; the Topology Specific Module (TSM) cleared it. For information about TSM, see "BOOK="cncptenu" COLLECTION="nw41"Topology Specific Module (TSM)" in Concepts.Action: None. This message is for information only.068: The local bit in the node address override was set.NE2_32-NWExplanation: You entered a node address without the local bit being set; the Topology Specific Module (TSM) set it. For information about TSM, see "BOOK="cncptenu" COLLECTION="nw41"Topology Specific Module (TSM)" in Concepts.Action: None. This message is for information only.071: The matching virtual adapter could not be found.NE2_32-NWExplanation: A new frame was being added to an existing network board, but the Media Support Module (MSM) could not locate a previous network board to link it with.Action: Obtain the most current version of MSM.NLM. For information about MSM see "BOOK="cncptenu" COLLECTION="nw41"Media Support Module (MSM)" in Concepts.072: A resource tag is unavailable.NE2_32-NWExplanation: The server may not have enough available memory. NetWare cannot allocate memory for a resource tag.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.073: Unable to allocate memory.NE2_32-NWExplanation: The server may not have enough available memory. NetWare cannot allocate memory for the LAN driver.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.PAGENUM=577 ID="BP571"074: The hardware interrupt cannot be set.NE2_32-NWExplanation: NetWare could not set the hardware interrupt that the LAN driver registered. The LAN driver must have changed information in the configuration table (IntNumber, SharingFlags) after the hardware options were registered.Action: Make sure the interrupt setting on the board matches the setting in the AUTOEXEC.NCF file. For information about the AUTOEXEC.NCF file, see "BOOK="superenu" COLLECTION="nw41"Maintaining the NetWare Server" in Supervising the Network.075: The MLID cannot be registered with the LSL.NE2_32-NWExplanation: The LAN driver's Link Support Layer (LSL) ran out of logical boards, or it could not allocate memory for its internal structures.Action: Unload nonessential LAN drivers that are consuming large numbers of logical boards. Increase the available memory. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. For information about LSL, see "BOOK="cncptenu" COLLECTION="nw41"Link Support Layer (LSL)" in Concepts.076: The polling procedure cannot be added.NE2_32-NWExplanation: Too many polling processes are registered with the operating system.Action: Unload nonessential NLMs that may be using a polling procedure.077: The event notification routine cannot be registered.NE2_32-NWExplanation: The server may not have enough available memory. NetWare cannot allocate memory for internal structures related to event notification. Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.079: The MLID did not initialize MSMTxFreeCount.NE2_32-NWExplanation: The .LAN file is either outdated or corrupted.Action: Obtain a new .LAN file.086: The driver parameter block is too small.NE2_32-NWExplanation: The .LAN file is designed to run with an older version of the MSM.NLM file.Action: Obtain a newer version of the .LAN file or an older version of the MSM.NLM file.087: The media parameter block is too small.NE2_32-NWExplanation: The topology NLM is designed to run with an older version of the MSM.NLM.Action: Obtain a newer version of the topology NLM or an older version of the MSM.NLM.PAGENUM=578 ID="BP572"091: The hardware configuration conflicts.NE2_32-NWExplanation: Another hardware resource is being used, which the LAN driver is trying to register.Action: Change the hardware configuration of the network board or of the conflicting device.092: Cannot schedule AES without an HSM routine.NE2_32-NWExplanation: The LAN driver is either outdated or corrupted.Action: Obtain a new .LAN file.093: Cannot schedule interrupt time call back without an HSM routine.NE2_32-NWExplanation: The LAN driver is either outdated or corrupted.Action: Obtain a new .LAN file.094: Cannot set hardware interrupt without an HSM routine.NE2_32-NWExplanation: The LAN driver is either outdated or corrupted.Action: Obtain a new .LAN file.095: Cannot add polling without an HSM routine.NE2_32-NWExplanation: The LAN driver is either outdated or corrupted.Action: Obtain a new .LAN file.PAGENUM=579 ID="BP573"NE2_32-OS2001: The LSL is not loaded.NE2_32-OS2Explanation: The Link Support Layer (LSL) module must be loaded before the computer can install the driver.Action: Edit the CONFIG.SYS file to load the LSL before the LAN driver, as in the following example:FORMAT="LINESPECIFIC"MOREINFO="NONE"DEVICE=C:\NETWARE\LSL.SYS 
DEVICE=C:\NETWARE\NE2_32.SYS For information about the CONFIG.SYS file, see 
BOOK="ws_osenu" COLLECTION="nw41"NetWare Client for OS/2 User Guide. For information about LSL, see "BOOK="cncptenu" COLLECTION="nw41"Link Support Layer (LSL)" in Concepts.021: Could not add MLID Protocol ID.NE2_32-OS2Explanation: The Link Support Layer (LSL) is configured with resources for four Protocol Identifiers. This number has been exceeded.Action: None. This message is for information only. For information about LSL, see "BOOK="cncptenu" COLLECTION="nw41"Link Support Layer (LSL)" in Concepts.022: Could not allocate memory. Virtual board did not load.NE2_32-OS2Explanation: The computer cannot allocate enough memory to load another network board.Action: Do one of the following:MARK=BULLETInstall more memory in the computer.Edit the CONFIG.SYS file, and remove any nonessential drivers. For information about the CONFIG.SYS file, see 
BOOK="ws_osenu" COLLECTION="nw41"NetWare Client for OS/2 User Guide.050: The board cannot be found.NE2_32-OS2Explanation: Either the network board is not present in the computer, or the network board's configuration cannot be obtained.Action: Do one of the following:MARK=BULLETMake sure the network board is properly seated into the slot. Insert the network board into a slot, and run the CLASS=DISKReference diskette to install it.PAGENUM=580 ID="BP574"051: Board RAM failed the memory test.NE2_32-OS2Explanation: The memory test on the network board's internal static RAM failed.Action: Check the network board and other hardware.  If necessary, replace the network board.052: The board cannot be found at the slot designated in NET.CFG.NE2_32-OS2Explanation: The NET.CFG file specifies that the network board is placed in a specific slot, but it cannot be found in that slot.Action: Make sure the network board is properly seated in the slot. If the slot that the network board is in doesn't match the slot specified in the NET.CFG file, do one of the following:MARK=BULLETCorrect the slot number in the NET.CFG file to match the slot where the network board is physically located. For information about the NET.CFG file, see "BOOK="ws_osenu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for OS/2 User Guide.To install the board., move the network board to the slot specified in the NET.CFG file; then run the CLASS=DISKReference diskette that came with the computer.Note: If no slot is specified in the NET.CFG file, the driver will search all slots for the network board. If more than one board is in the computer, the slots must be specified in the NET.CFG file.053: The specified slot contains the correct board, but board is not enabled.NE2_32-OS2Explanation: When the network board was installed using the CLASS=DISKReference diskette, the option to disable the network board was selected.Action: Run the CLASS=DISKReference diskette that came with the computer, and enable the network board.054: The board did not respond to the initialization command.NE2_32-OS2Explanation: A hardware error has occurred.Action: Power down the computer; then reboot it. If the network board still does not respond, replace it with one that is good.056: This interrupt is already used and cannot be shared.NE2_32-OS2Explanation: The selected interrupt is being used by another device, so it cannot be used for this network board.Action: Run the CLASS=DISKReferencePAGENUM=581 ID="BP575" diskette that came with the computer, and change the jumper setting on the network board to use a different interrupt. For information about jumper settings, see the NE2_32 hardware manual. Edit the NET.CFG file to reflect the correct interrupt level used by the network board. For information about the NET.CFG file, see "BOOK="ws_osenu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for OS/2 User Guide.240: Invalid Node Override, Group Address bit was set now reset.NE2_32-OS2Explanation: The driver address specified in the NET.CFG file contains the group bit set. Note: If no address is specified, the driver will use the default address assigned by the network board's manufacturer.Action: No action is necessary; the bit was cleared by the driver. However, to prevent this error message from being displayed every time the driver is loaded, edit the NET.CFG file and correct the node address override, as is shown in the following example:FORMAT="LINESPECIFIC"MOREINFO="NONE"LINK DRIVER NE2_32 
    NODE ADDRESS address For information about editing the NET.CFG file, see "BOOK="ws_osenu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for OS/2 User Guide.241: Invalid Node Override, Local Administrated bit was set now reset.NE2_32-OS2Explanation: The driver address specified in the NET.CFG file does not have the locally administered bit set. Note: If no address is specified, the driver will use the default address assigned by the network board's manufacturer.Action: No action is necessary; the bit was set by the driver. However, to prevent this error message from being displayed every time the driver is loaded, edit the NET.CFG file and correct the node address override, as is shown in the following example:FORMAT="LINESPECIFIC"MOREINFO="NONE"LINK DRIVER NE2_32 
    NODE ADDRESS address For information about editing the NET.CFG file, see "BOOK="ws_osenu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for OS/2 User Guide.PAGENUM=582 ID="BP576"NE2-DOS001: The LSL is not loaded.NE2-DOSExplanation: The computer must load the Link Support Layer (LSL) before loading the driver.Action: Load the LSL; then load the driver, as in the following example:FORMAT="LINESPECIFIC"MOREINFO="NONE"C:\NWCLIENT\LSL MOREINFO="NONE"<Enter> 
C:\NWCLIENT\NE2 MOREINFO="NONE"<Enter> For information about LSL, see "BOOK="cncptenu" COLLECTION="nw41"Link Support Layer (LSL)" in Concepts.002: The LSL has no room for a board using frame type.NE2-DOSExplanation: The Link Support Layer (LSL) is configured with resources for a set number of network boards. (The default is 4.) This number has been exceeded.Action: Edit the NET.CFG file, and add the MAX BOARDS keyword to reflect the number of network boards to be loaded, as in the following example: FORMAT="LINESPECIFIC"MOREINFO="NONE"LINK SUPPORT 
    MAX BOARDS 6 Unload the driver; then reload it as in the following example:FORMAT="LINESPECIFIC"MOREINFO="NONE"C:\NWCLIENT\NE2 /u MOREINFO="NONE"<Enter> 
C:\NWCLIENT\NE2 MOREINFO="NONE"<Enter> For information on the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference. For information about LSL, see "BOOK="cncptenu" COLLECTION="nw41"Link Support Layer (LSL)" in Concepts.003: Could not find NE2 MLID to unload.NE2-DOSExplanation: The NE2 driver is not loaded.Action: None. This message is for information only.004: A TSR is loaded above the NE2 MLID.NE2-DOSExplanation: Another TSR (terminate-and-stay-resident) program was loaded after the NE2 driver.Action: The drivers must be unloaded in reverse order, as follows:PAGENUM=583 ID="BP577"FORMAT="LINESPECIFIC"MOREINFO="NONE"C:\NWCLIENT\NETX /u MOREINFO="NONE"<Enter> 
C:\NWCLIENT\IPXODI /u MOREINFO="NONE"<Enter> 
C:\NWCLIENT\NE2 /u MOREINFO="NONE"<Enter> Unload the TSRs; then try to unload the NE2 driver. You can force the NE2 driver to unload from the command line by using the /F switch after the driver name, as follows:FORMAT="LINESPECIFIC"MOREINFO="NONE"C:\NWCLIENT\NE2 /f MOREINFO="NONE"<Enter> Use caution when using the /F switch because it could cause the computer to hang.005: NE2 MLID could not be unloaded; the operation was aborted.NE2-DOSExplanation: The NE2 driver could not be shut down and deregistered; consequently, it cannot be unloaded.Action: To unload the driver, reboot the computer.006: The adapter did not initialize. NE2 did not load.NE2-DOSExplanation: The NE2 driver encountered an error while loading.Action: Corrective action can vary. See the preceding driver-specific message on the screen for specific information about the error that occurred.007: You need another MLID section heading in the NET.CFG file in order to load the MLID again. NE2-DOSExplanation: The NET.CFG file does not have an individual entry for each driver that is intended to be loaded.  This means that one of the drivers is not loaded into memory..Action: Unload the NE2 driver. Modify the NET.CFG file to contain a unique entry for each driver to be loaded. This requires an individual Link Driver heading in the NET.CFG file for each driver or each instance of the same driver. Load the drivers again. For information on the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.008: A NET.CFG is required to load the MLID again.NE2-DOSExplanation: The NET.CFG file does not have an individual entry for each driver that is intended to be loaded.  This means that one of the drivers is not loaded into memory.Action: Unload the NE2 driver. Modify the NET.CFG file to contain a unique entry for each driver to be loaded. This requires an individual Link Driver heading in the NET.CFG file for each driver or each instance of the same driver. Load the drivers again. For information on the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.PAGENUM=584 ID="BP578"009: The NET.CFG entry has been ignored.NE2-DOSExplanation: The NET.CFG file does not have an individual entry for each driver that is intended to be loaded.  This means that one of the drivers is not loaded into memory.Action: Unload the NE2 driver. Modify the NET.CFG file to contain a unique entry for each driver to be loaded. This requires an individual Link Driver heading in the NET.CFG file for each driver or each instance of the same driver. Load the drivers again. For information on the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.011: The MLID does not support frame type. The protocol keyword has been ignored.NE2-DOSExplanation: An unsupported or incorrectly typed frame type has been specified with the protocol keyword.Action: Verify that the frame type assigned under the protocol keyword in the NET.CFG file is valid. For a list of valid frame types, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.012: The protocol keyword must have a frame type. Entry ignored.NE2-DOSExplanation: The PROTOCOL keyword entry is incomplete.Action: Correct the protocol entry in the NET.CFG file. The proper syntax for the protocol keyword is as follows:FORMAT="LINESPECIFIC"MOREINFO="NONE"PROTOCOL NE2 hex_protocol_ID frame_type For information about the PROTOCOL keyword, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.013: The MLID could not register Protocol ID number for protocol stack name for frame type type.NE2-DOSExplanation: The Link Support Layer (LSL) is configured with resources for a set number of Protocol Identifiers. (The default is 4.) This number has been exceeded. For information about LSL, see "BOOK="cncptenu" COLLECTION="nw41"Link Support Layer (LSL)" in Concepts.Action: Edit the NET.CFG file, and add the MAX STACKS keyword to reflect the number of network boards to be loaded, as in the following example:FORMAT="LINESPECIFIC"MOREINFO="NONE"LINK SUPPORT 
    MAX STACKS 6 Unload the driver; then reload it as in the following example:FORMAT="LINESPECIFIC"MOREINFO="NONE"C:\NWCLIENT\NE2 /u MOREINFO="NONE"<Enter> 
PAGENUM=585 ID="BP579"C:\NWCLIENT\LSL /u MOREINFO="NONE"<Enter> 
C:\NWCLIENT\LSL MOREINFO="NONE"<Enter> 
C:\NWCLIENT\NE2MOREINFO="NONE" <Enter> For information on the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.014: This version of the LSL is not supported.NE2-DOSExplanation: The Link Driver the computer is using supports only Link Support Layer (LSL) versions later than 1.0.Action: Unload the LSL and replace it with a newer version. For information about LSL, see "BOOK="cncptenu" COLLECTION="nw41"Link Support Layer (LSL)" in Concepts.015: The frame type is already active for frame frame_type.NE2-DOSExplanation: The frame type is already loaded, and it cannot be loaded repeatedly.Action: Edit the NET.CFG file to load the frame type only once for a given network board. For information about frame types, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.016: The node address was incorrectly specified in the NET.CFG file.NE2-DOSExplanation: The node address override in the NET.CFG file is too long.Action: Edit the NET.CFG file and correct the node address. The node address must be less than or equal to 12 hex digits. For information about node address override, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.017: An invalid keyword was specified in NET.CFG on line number.NE2-DOSExplanation: The key word on the line indicated was not recognized.Action: Edit the NET.CFG file and correct the spelling of the keyword. For valid keywords, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.018: The frame type specified in the NET.CFG is not supported.NE2-DOSExplanation: The frame type specified with the FRAME keyword is not supported by the driver.Action: Edit the NET.CFG file and fix frame type. For information on supported frame types, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.PAGENUM=586 ID="BP580"019: An invalid NE2 node address is specified in NET.CFG. The MLID modified the incorrect address bits.NE2-DOSExplanation: The node address specified in the NET.CFG file contains set reserved bits.Action: Edit the NET.CFG file and correct the node address. For information about node addresses, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.050: The board cannot be found.NE2-DOSExplanation: Either the network board is not present in the computer, or the network board's configuration cannot be obtained.Action: Do one of the following:MARK=BULLETMake sure the network board is properly seated into the slot. Insert the network board into a slot, and run the CLASS=DISKReference diskette to install it.051: Board RAM failed the memory test.NE2-DOSExplanation: The memory test on the network board's internal static RAM failed.Action: Check the network board and other hardware.  If necessary, replace the network board.052: The board cannot be found at the slot designated in NET.CFG.NE2-DOSExplanation: The NET.CFG file specifies that the network board is placed in a specific slot, but the network board cannot be found. If no slot is specified in the NET.CFG file, the driver searches all slots for the network board. If more than one network board is in the computer, the slots must be specified in the NET.CFG file.Action: If the slot that the network board is in does not match the slot specified in the NET.CFG file, do one of the following:MARK=BULLETCorrect the slot number in the NET.CFG file to match the slot where the network board is physically located. For information on the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference. Move the network board to the slot specified in the NET.CFG file; then run the CLASS=DISKReference diskette to install the network board.PAGENUM=587 ID="BP581"053: The specified slot contains the correct board, but board is not enabled.NE2-DOSExplanation: When the network board was installed using the CLASS=DISKReference diskette, the option to disable the network board was selected.Action: Run the CLASS=DISKReference diskette and set the option to enable the network board.054: The board did not respond to the initialization command.NE2-DOSExplanation: A hardware error has occurred.Action: Power down the computer; then reboot it. If the network board still does not respond, replace it with one that is good.PAGENUM=588 ID="BP582"NE2-NW025: You cannot load MSM31X on a NetWare 3.10 server.NE2-NWExplanation: The computer attempted to load MSM31X.NLM on a NetWare 3.10 server. MSM31X.NLM will run only on a NetWare 3.11 server.Action: Either load a version of the Media Support Module (MSM) that will run on a NetWare 3.10 server, or upgrade the server to NetWare 3.11. For information on MSM, see "BOOK="cncptenu" COLLECTION="nw41"Media Support Module (MSM)" in Concepts.026: On a NetWare 3.11 server, you must load LSLENH.NLM before you load MSM31X.NLM.NE2-NWExplanation: The Link Support Layer (LSL) and Media Support Module (MSM) have been loaded on a NetWare 3.11 server. An attempt was made to load LSLENH.NLM. The computer cannot load LSLENH.NLM once the MSM has been loaded. (LSLENH.NLM adds enhancement to the LSL.)Action: Unload MSM31X.NLM; then load LSLENH.NLM. Once the LSLENH.NLM has been loaded, load MSM31X.NLM again. For information about LSL and MSM, see "BOOK="cncptenu" COLLECTION="nw41"Link Support Layer (LSL)" and "BOOK="cncptenu" COLLECTION="nw41"Media Support Module (MSM)" in Concepts.050: The board cannot be found.NE2-NWExplanation: Either the network board is not present in the computer, or the network board's configuration cannot be obtained.Action: Do one of the following:MARK=BULLETMake sure the network board is properly seated into the slot. Insert the network board into a slot, and run the CLASS=DISKReference diskette to install it.051: Board RAM failed the memory test.NE2-NWExplanation: The memory test on the network board's internal static RAM failed.Action: Make sure the I/O port settings on the network board match the I/O port settings in the AUTOEXEC.NCF file. For information about the AUTOEXEC.NCF file, see "BOOK="superenu" COLLECTION="nw41"Maintaining the NetWare Server" in Supervising the Network. If the settings match, replace the network board.PAGENUM=589 ID="BP583"054: The board did not respond to the initialization command.NE2-NWExplanation: The network board didn't respond to a reset command.Action: Make sure the I/O port settings on the network board match the I/O port settings in the AUTOEXEC.NCF file. For information about the AUTOEXEC.NCF file, see "BOOK="superenu" COLLECTION="nw41"Maintaining the NetWare Server" in Supervising the Network. If the settings match, replace the network board.066-Adapter 1: The cable might be disconnected on the board.NE2-NWExplanation: The cable may be disconnected, or heavy traffic on the wire is delaying a packet from being sent.Action: If the problem persists, check the cable, or consider adding more networks to decrease LAN traffic.067: The group bit in the node address override was cleared.NE2-NWExplanation: You entered a node address with the Group address bit set; the Topology Specific Module (TSM) cleared it.Action: None. This message is for information only. For information about TSM, see "BOOK="cncptenu" COLLECTION="nw41"Topology Specific Module (TSM)" in Concepts.068: The local bit in the node address override was set.NE2-NWExplanation: You entered a node address without the local bit being set; the Topology Specific Module (TSM) set it.Action: None. This message is for information only. For information about TSM, see "BOOK="cncptenu" COLLECTION="nw41"Topology Specific Module (TSM)" in Concepts.071: The matching virtual adapter could not be found.NE2-NWExplanation: A new frame was being added to an existing network board, but the Media Support Module (MSM) could not locate a previous network board to link it with.Action: Obtain the most current version of MSM.NLM. For information about MSM, see "BOOK="cncptenu" COLLECTION="nw41"Media Support Module (MSM)" in Concepts.072: A resource tag is unavailable.NE2-NWExplanation: The server may not have enough available memory. NetWare cannot allocate memory for a resource tag.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.PAGENUM=590 ID="BP584"073: Unable to allocate memory.NE2-NWExplanation: The server may not have enough available memory. NetWare cannot allocate memory for the LAN driver.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.074: The hardware interrupt cannot be set.NE2-NWExplanation: NetWare could not set the hardware interrupt that the LAN driver registered. The LAN driver must have changed information in the configuration table (IntNumber, SharingFlags) after the hardware options were registered.Action: Make sure the interrupt setting on the board matches the setting in the AUTOEXEC.NCF file. For information about the AUTOEXEC.NCF file, see "BOOK="superenu" COLLECTION="nw41"Maintaining the NetWare Server" in Supervising the Network.075: The MLID cannot be registered with the LSL.NE2-NWExplanation: The LAN driver's Link Support Layer (LSL) ran out of logical boards, or it could not allocate memory for its internal structures.Action: Unload nonessential LAN drivers that are consuming large numbers of logical boards. Increase the available memory. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. For information about LSL, see "BOOK="cncptenu" COLLECTION="nw41"Link Support Layer (LSL)" in Concepts.076: The polling procedure cannot be added.NE2-NWExplanation: Too many polling processes are registered with the operating system.Action: Unload nonessential NLMs that may be using a polling procedure.077: The event notification routine cannot be registered.NE2-NWExplanation: The server may not have enough available memory. NetWare cannot allocate memory for internal structures related to event notification. Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.079: The MLID did not initialize MSMTxFreeCount.NE2-NWExplanation: The .LAN file is either outdated or corrupted.Action: Obtain a new .LAN file.PAGENUM=591 ID="BP585"086: The driver parameter block is too small.NE2-NWExplanation: The .LAN file is designed to run with an older version of the MSM.NLM.Action: Obtain a newer version of the .LAN file or an older version of the MSM.NLM.087: The media parameter block is too small.NE2-NWExplanation: The topology NLM is designed to run with an older version of the MSM.NLM.Action: Obtain a newer version of the topology NLM or an older version of the MSM.NLM.091: The hardware configuration conflicts.NE2-NWExplanation: Another hardware resource is being used, which the LAN driver is trying to register.Action: Change the hardware configuration of the network board or of the conflicting device.092: Cannot schedule AES without an HSM routine.NE2-NWExplanation: The LAN driver is either outdated or corrupted.Action: Obtain a new .LAN file.093: Cannot schedule interrupt time call back without an HSM routine.NE2-NWExplanation: The LAN driver is either outdated or corrupted.Action: Obtain a new .LAN file.094: Cannot set hardware interrupt without an HSM routine.NE2-NWExplanation: The LAN driver is either outdated or corrupted.Action: Obtain a new .LAN file.095: Cannot add polling without an HSM routine.NE2-NWExplanation: The LAN driver is either outdated or corrupted.Action: Obtain a new .LAN file.PAGENUM=592 ID="BP586"200-Adapter 1: The board's DMA did not complete the write.NE2-NWExplanation: The network board didn't complete a DMA transaction within the specified time. The driver will attempt to correct the problem by resetting the network board and resending the packet.Action: If the problem occurs often (more than once or twice a day), replace the network board.PAGENUM=593 ID="BP587"NE2-OS2001: The LSL is not loaded.NE2-OS2Explanation: The Link Support Layer (LSL) module must be loaded before the computer can install the driver.Action: Edit the CONFIG.SYS file to load the LSL before the LAN driver, as in the following example:FORMAT="LINESPECIFIC"MOREINFO="NONE"DEVICE=C:\NETWARE\LSL.SYS 
DEVICE=C:\NETWARE\NE2.SYS For information about the CONFIG.SYS file, see 
BOOK="ws_osenu" COLLECTION="nw41"NetWare Client for OS/2 User Guide. For information about LSL, see "BOOK="cncptenu" COLLECTION="nw41"Link Support Layer (LSL)" in Concepts.021: Could not add MLID Protocol ID.NE2-OS2Explanation: The Link Support Layer (LSL) is configured with resources for four Protocol Identifiers. This number has been exceeded.Action: None. This message is for information only.022: Could not allocate memory. Virtual board did not load.NE2-OS2Explanation: The computer cannot allocate enough memory to load another network board.Action: Do one of the following:MARK=BULLETInstall more memory in the computer.Edit the CONFIG.SYS file, and remove any nonessential drivers. For information about the CONFIG.SYS file, see 
BOOK="ws_osenu" COLLECTION="nw41"NetWare Client for OS/2 User Guide.050: The board cannot be found.NE2-OS2Explanation: Either the network board is not present in the computer, or the network board's configuration cannot be obtained.Action: Do one of the following:MARK=BULLETMake sure the network board is properly seated into the slot. Insert the network board into a slot, and run the CLASS=DISKReference diskette to install it.PAGENUM=594 ID="BP588"051: Board RAM failed the memory test.NE2-OS2Explanation: The memory test on the network board's internal static RAM failed.Action: Check the network board and other hardware.  If necessary, replace the network board.054: The board did not respond to the initialization command.NE2-OS2Explanation: A hardware error has occurred.Action: Power down the computer; then reboot it. If the network board still does not respond, replace it with one that is good.056: This interrupt is already used and cannot be shared.NE2-OS2Explanation: The selected interrupt is being used by another device, so it cannot be used for this network board.Action: Run the CLASS=DISKReference diskette that came with the computer, and change the jumper setting on the network board to use a different interrupt. For information about jumper settings see the NE2-32 hardware manual. Edit the NET.CFG file to reflect the correct interrupt level used by the network board. For information about the NET.CFG file, see "BOOK="ws_osenu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for OS/2 User Guide.240: Invalid Node Override, Group Address bit was set now reset.NE2-OS2Explanation: The driver address specified in the NET.CFG file contains the group bit set. Note: If no address is specified, the driver will use the default address assigned by the network board's manufacturer.Action: No action is necessary; the bit was cleared by the driver. However, to prevent this error message from being displayed every time the driver is loaded, edit the NET.CFG file and correct the node address override, as is shown in the following example:FORMAT="LINESPECIFIC"MOREINFO="NONE"LINK DRIVER NE2 
   NODE ADDRESS address For information about editing the NET.CFG file, see "BOOK="ws_osenu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for OS/2 User Guide.PAGENUM=595 ID="BP589"241: Invalid Node Override, Local Administrated bit was set now reset.NE2-OS2Explanation: The driver address specified in the NET.CFG file does not have the locally administered bit set. Note: If no address is specified, the driver will use the default address assigned by the network board's manufacturer.Action: No action is necessary; the bit was set by the driver. However, to prevent this error message from being displayed every time the driver is loaded, edit the NET.CFG file and correct the node address override, as is shown in the following example:FORMAT="LINESPECIFIC"MOREINFO="NONE"LINK DRIVER NE2 
   NODE ADDRESS address For information about editing the NET.CFG file, see "BOOK="ws_osenu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for OS/2 User Guide.PAGENUM=596 ID="BP590"NE2000-DOS001: The LSL is not loaded.NE2000-DOSExplanation: The computer must load the Link Support Layer (LSL) before loading the driver.Action: Load the LSL; then load the driver, as in the following example:FORMAT="LINESPECIFIC"MOREINFO="NONE"C:\NWCLIENT\LSL MOREINFO="NONE"<Enter> 
C:\NWCLIENT\NE2000 MOREINFO="NONE"<Enter> For information about LSL, see "BOOK="cncptenu" COLLECTION="nw41"Link Support Layer (LSL)" in Concepts.002: The LSL has no room for a board using frame type.NE2000-DOSExplanation: The Link Support Layer (LSL) is configured with resources for a set number of network boards. (The default is 4.) This number has been exceeded.Action: Edit the NET.CFG file, and add the MAX BOARDS keyword to reflect the number of network boards to be loaded, as in the following example: FORMAT="LINESPECIFIC"MOREINFO="NONE"LINK SUPPORT 
   MAX BOARDS 6 Unload the driver; then reload it as in the following example:FORMAT="LINESPECIFIC"MOREINFO="NONE"C:\NWCLIENT\NE2000 /u MOREINFO="NONE"<Enter> 
C:\NWCLIENT\NE2000 MOREINFO="NONE"<Enter> For information on the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference. For information about LSL, see "BOOK="cncptenu" COLLECTION="nw41"Link Support Layer (LSL)" in Concepts.003: Could not find NE2000 MLID to unload.NE2000-DOSExplanation: The NE2000 driver is not loaded.Action: None. This message is for information only.004: A TSR is loaded above the NE2000 MLID.NE2000-DOSExplanation: Another TSR (terminate-and-stay-resident) program was loaded after the NE2000 driver.Action: The drivers must be unloaded in reverse order, as follows:PAGENUM=597 ID="BP591"FORMAT="LINESPECIFIC"MOREINFO="NONE"C:\NWCLIENT\NETX /u MOREINFO="NONE"<Enter> 
C:\NWCLIENT\IPXODI /u MOREINFO="NONE"<Enter> 
C:\NWCLIENT\NE2000 /u MOREINFO="NONE"<Enter> Unload the TSRs; then try to unload the NE2000 driver. You can force the NE2000 driver to unload from the command line by using the /F switch after the driver name, as follows:FORMAT="LINESPECIFIC"MOREINFO="NONE"C:\NWCLIENT\NE2000 /f MOREINFO="NONE"<Enter> Use caution when using the /F switch because it could cause the computer to hang.005: NE2000 MLID could not be unloaded; the operation was aborted.NE2000-DOSExplanation: The NE2000 driver could not be shut down and unregistered; consequently, it cannot be unloaded.Action: To unload the driver, reboot the computer.006: The adapter did not initialize. NE2000 did not load.NE2000-DOSExplanation: The NE2000 driver encountered an error while loading.Action: Corrective action can vary. See the preceding driver-specific message on the screen for specific information about the error that occurred.007: You need another MLID section heading in the NET.CFG file in order to load the MLID again.NE2000-DOSExplanation: The NET.CFG file does not have an individual entry for each driver that is intended to be loaded.  This means that one of the drivers is not loaded into memory.Action: Unload the NE2000 driver. Modify the NET.CFG file to contain a unique entry for each driver to be loaded. This requires an individual Link Driver heading in the NET.CFG file for each driver or each instance of the same driver. Load the drivers again. For information on the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.008: A NET.CFG is required to load the MLID again.NE2000-DOSExplanation: The NET.CFG file does not have an individual entry for each driver that is intended to be loaded.  This means that one of the drivers is not loaded into memory.Action: Unload the NE2000 driver. Modify the NET.CFG file to contain a unique entry for each driver to be loaded. This requires an individual Link Driver heading in the NET.CFG file for each driver or each instance of the same driver. Load the drivers again. For information on the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.PAGENUM=598 ID="BP592"009: The NET.CFG entry has been ignored.NE2000-DOSExplanation: The NET.CFG file does not have an individual entry for each driver that is intended to be loaded.  This means that one of the drivers is not loaded into memory.Action: Unload the NE200 driver. Modify the NET.CFG file to contain a unique entry for each driver to be loaded. This requires an individual Link Driver heading in the NET.CFG file for each driver or each instance of the same driver. Load the drivers again. For information on the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.011: The MLID does not support frame type. The protocol keyword has been ignored.NE2000-DOSExplanation: An unsupported or incorrectly typed frame type has been specified with the protocol keyword.Action: Verify that the frame type assigned under the protocol keyword in the NET.CFG file is valid. For a list of valid frame types, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.012: The protocol keyword must have a frame type. Entry ignored.NE2000-DOSExplanation: The PROTOCOL keyword entry is incomplete.Action: Correct the protocol entry in the NET.CFG file. The proper syntax for the protocol keyword is as follows:FORMAT="LINESPECIFIC"MOREINFO="NONE"PROTOCOL NE2000 hex_protocol_ID frame_type For information about the PROTOCOL keyword, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.013: The MLID could not register Protocol ID number for protocol stack name for frame type frame_type.NE2000-DOSExplanation: The Link Support Layer (LSL) is configured with resources for a set number of Protocol Identifiers. (The default is 4.) This number has been exceeded.Action: Edit the NET.CFG file, and add the MAX STACKS keyword to reflect the number of network boards to be loaded as in the following example:FORMAT="LINESPECIFIC"MOREINFO="NONE"LINK SUPPORT 
   MAX STACKS 6 Unload the driver; then reload it as in the following example:FORMAT="LINESPECIFIC"MOREINFO="NONE"C:\NWCLIENT\NE2000 /u MOREINFO="NONE"<Enter> 
C:\NWCLIENT\LSL /u MOREINFO="NONE"<Enter> 
PAGENUM=599 ID="BP593"C:\NWCLIENT\LSL MOREINFO="NONE"<Enter> 
C:\NWCLIENT\NE2000MOREINFO="NONE" <Enter> For information on the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference. For information about LSL, see "BOOK="cncptenu" COLLECTION="nw41"Link Support Layer (LSL)" in Concepts.014: This version of the LSL is not supported.NE2000-DOSExplanation: The Link Driver the computer is using supports only Link Support Layer (LSL) versions later than 1.0.Action: Unload the LSL and replace it with a newer version. For information about LSL, see "BOOK="cncptenu" COLLECTION="nw41"Link Support Layer (LSL)" in Concepts.015: The frame type is already active for frame frame_type.NE2000-DOSExplanation: The frame type is already loaded, and it cannot be loaded repeatedly.Action: Edit the NET.CFG file to load the frame type only once for a given network board. For information about frame types, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.016: The node address was incorrectly specified in the NET.CFG file.NE2000-DOSExplanation: The node address override in the NET.CFG file is too long.Action: Edit the NET.CFG file and correct the node address. The node address must be less than or equal to 12 hex digits. For information about node address override, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.017: An invalid keyword was specified in NET.CFG on line number.NE2000-DOSExplanation: The key word on the line indicated was not recognized.Action: Edit the NET.CFG file and correct the spelling of the keyword. For valid keywords, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.018: The frame type specified in the NET.CFG is not supported.NE2000-DOSExplanation: The frame type specified with the FRAME keyword is not supported by the driver.Action: Edit the NET.CFG file and fix frame type. For information on supported frame types, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.PAGENUM=600 ID="BP594"019: An invalid NE2000 node address is specified in NET.CFG. The MLID modified the incorrect address bits.NE2000-DOSExplanation: The node address specified in the NET.CFG file contains set reserved bits.Action: Edit the NET.CFG file and correct the node address. For information about node addresses, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.050: The board cannot be found.NE2000-DOSExplanation: The network board was not found due to one or more of the following conditions: MARK=BULLETThe network board is not present in the computer. The network board settings are not the defaults, and they are not defined in the NET.CFG file.Another network board is using the same hardware settings as this network board.The network board is bad.Action: Do one or more of the following:MARK=BULLETMake sure the network board is properly seated into the slot. If jumper settings are not the defaults, make sure they match the settings in the NET.CFG file. For information on the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.If the computer is not using the NET.CFG file, make sure the jumper settings are set to the defaults. If other network boards are using the same hardware settings, change the settings and try to reload the driver.Replace the bad network board with one that is good.051: Board RAM failed the memory test.NE2000-DOSExplanation: The memory test on the network board's internal static RAM failed.Action: Check the network board and other hardware.  If necessary, replace the network board.PAGENUM=601 ID="BP595"054: The board did not respond to the initialization command.NE2000-DOSExplanation: A hardware error has occurred.Action: Power down the computer; then reboot it. If the network board still does not respond, replace it with one that is good.PAGENUM=602 ID="BP596"NE2000-NW025: You cannot load MSM31X on a NetWare 3.10 server.NE2000-NWExplanation: You attempted to load MSM31X.NLM on a NetWare 3.10 server. MSM31X.NLM will run only on a NetWare 3.11 server.Action: Either load a version of the Media Support Module (MSM) that will run on a NetWare 3.10 server, or upgrade the server to NetWare 3.11. For information about MSM, see "BOOK="cncptenu" COLLECTION="nw41"Media Support Module (MSM)" in Concepts.026: On a NetWare 3.11 server, you must load LSLENH.NLM before you load MSM31X.NLM.NE2000-NWExplanation: The Link Support Layer (LSL) and Media Support Module (MSM) have been loaded on a NetWare 3.11 server. An attempt was made to load LSLENH.NLM. The computer cannot load LSLENH.NLM once the MSM has been loaded. (LSLENH.NLM adds enhancement to the LSL.)Action: Unload MSM31X.NLM; then load LSLENH.NLM. Once the LSLENH.NLM has been loaded, load MSM31X.NLM again. For information about LSL and MSM, see "BOOK="cncptenu" COLLECTION="nw41"Link Support Layer (LSL)" and "BOOK="cncptenu" COLLECTION="nw41"Media Support Module (MSM)" in Concepts.050: The board cannot be found.NE2000-NWExplanation: The network board was not found because of one or more of the following: MARK=BULLETThe network board is not present in the computer. The network board settings are not the defaults, and they are not defined in the AUTOEXEC.NCF file.Another network board is using the same hardware settings as this network board.The network board is bad.Action: Do one or more of the following:MARK=BULLETMake sure the network board is properly seated into the slot. If jumper settings are not the defaults, make sure they match the settings in the AUTOEXEC.NCF file. For information about the AUTOEXEC.NCF file, see "BOOK="superenu" COLLECTION="nw41"Maintaining the NetWare Server" in Supervising the Network.PAGENUM=603 ID="BP597"If the computer is not using the AUTOEXEC.NCF file, make sure the jumper settings are set to the defaults. If other network boards are using the same hardware settings, change the settings and try to reload the driver.Replace the bad network board with one that is good.051: Board RAM failed the memory test.NE2000-NWExplanation: The memory test on the network board's internal static RAM failed.Action: Make sure the I/O port settings on the network board match the I/O port settings in the AUTOEXEC.NCF file. For information about the AUTOEXEC.NCF file, see "BOOK="superenu" COLLECTION="nw41"Maintaining the NetWare Server" in Supervising the Network. If the settings do match, the network board may need to be replaced.054: The board did not respond to the initialization command.NE2000-NWExplanation: The network board didn't respond to a reset command.Action: Make sure the I/O port settings on the network board match the I/O port settings in the AUTOEXEC.NCF file. For information about the AUTOEXEC.NCF file, see "BOOK="superenu" COLLECTION="nw41"Maintaining the NetWare Server" in Supervising the Network. If the settings match, replace the network board.066-Adapter 1: The cable might be disconnected on the board.NE2000-NWExplanation: The cable may be disconnected, or heavy traffic on the wire is delaying a packet from being sent.Action: If the problem persists, check the cable, or consider adding more networks to decrease LAN traffic.067: The group bit in the node address override was cleared.NE2000-NWExplanation: You entered a node address with the Group address bit set; the Topology Specific Module (TSM) cleared it.Action:  None. This message is for information only. For information about TSM, see "BOOK="cncptenu" COLLECTION="nw41"Topology Specific Module (TSM)" in Concepts.068: The local bit in the node address override was set.NE2000-NWExplanation: You entered a node address without the local bit being set; the Topology Specific Module (TSM) set it.Action: None. This message is for information only. For information about TSM, see "BOOK="cncptenu" COLLECTION="nw41"Topology Specific Module (TSM)" in Concepts.PAGENUM=604 ID="BP598"071: The matching virtual adapter could not be found.NE2000-NWExplanation: A new frame was being added to an existing network board, but the Media Support Module (MSM) could not locate a previous network board to link it with.Action: Obtain the most current version of MSM.NLM. For information about MSM, see "BOOK="cncptenu" COLLECTION="nw41"Media Support Module (MSM)" in Concepts.072: A resource tag is unavailable.NE2000-NWExplanation: The server may not have enough available memory. NetWare cannot allocate memory for a resource tag.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.073: Unable to allocate memory.NE2000-NWExplanation: The server may not have enough available memory. NetWare cannot allocate memory for the LAN driver.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.074: The hardware interrupt cannot be set.NE2000-NWExplanation: NetWare could not set the hardware interrupt that the LAN driver registered. The LAN driver must have changed information in the configuration table (IntNumber, SharingFlags) after the hardware options were registered.Action: Make sure the interrupt setting on the board matches the setting in the AUTOEXEC.NCF file. For information about the AUTOEXEC.NCF file, see "BOOK="superenu" COLLECTION="nw41"Maintaining the NetWare Server" in Supervising the Network.075: The MLID cannot be registered with the LSL.NE2000-NWExplanation: The LAN driver's Link Support Layer (LSL) ran out of logical boards, or it could not allocate memory for its internal structures.Action: Unload unneeded LAN drivers that are consuming large numbers of logical boards. Increase the available memory. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. For information about LSL, see "BOOK="cncptenu" COLLECTION="nw41"Link Support Layer (LSL)" in Concepts.076: The polling procedure cannot be added.NE2000-NWExplanation: Too many polling processes are registered with the operating system.Action: Unload nonessential NLMs that may be using a polling procedure.PAGENUM=605 ID="BP599"077: The event notification routine cannot be registered.NE2000-NWExplanation: NetWare cannot allocate memory for internal structures related to event notification. The server may not have enough available memory. Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.079: The MLID did not initialize MSMTxFreeCount.NE2000-NWExplanation: The .LAN file is either outdated or corrupted.Action: Obtain a new .LAN file.086: The driver parameter block is too small.NE2000-NWExplanation: The .LAN file is designed to run with an older version of the MSM.NLM.Action: Obtain a newer version of the .LAN file or an older version of the MSM.NLM. For information about MSM, see "BOOK="cncptenu" COLLECTION="nw41"Media Support Module (MSM)" in Concepts.087: The media parameter block is too small.NE2000-NWExplanation: The topology NLM is designed to run with an older version of the MSM.NLM.Action: Obtain a newer version of the topology NLM or an older version of the MSM.NLM. For information about MSM, see "BOOK="cncptenu" COLLECTION="nw41"Media Support Module (MSM)" in Concepts.091: The hardware configuration conflicts.NE2000-NWExplanation: Another hardware resource is being used, which the LAN driver is trying to register.Action: Change the hardware configuration of the network board or of the conflicting device.092: Cannot schedule AES without an HSM routine.NE2000-NWExplanation: The LAN driver is either outdated or corrupted.Action: Obtain a new .LAN file.093: Cannot schedule interrupt time call back without an HSM routine.NE2000-NWExplanation: The LAN driver is either outdated or corrupted.Action: Obtain a new .LAN file.PAGENUM=606 ID="BP600"094: Cannot set hardware interrupt without an HSM routine.NE2000-NWExplanation: The LAN driver is either outdated or corrupted.Action: Obtain a new .LAN file.095: Cannot add polling without an HSM routine.NE2000-NWExplanation: The LAN driver is either outdated or corrupted.Action: Obtain a new .LAN file.200-Adapter 1: The board's DMA did not complete the write.NE2000-NWExplanation: The network board didn't complete a Direct Memory Access (DMA) transaction within the specified time. The driver will attempt to correct the problem by resetting the network board and resending the packet.Action: If the problem occurs often (more than once or twice a day), replace the network board.223: The board must be placed in a 16-bit slot.NE2000-NWExplanation: The network board was placed in an 8-bit slot.Action: Move the network board to a 16-bit slot.224: This board is configured as an NE1000.NE2000-NWExplanation: The board is responding with an NE1000 ROM signature.Action: Make sure the I/O port settings on the network board match the I/O port settings in the AUTOEXEC.NCF file. For information about the AUTOEXEC.NCF file, see "BOOK="superenu" COLLECTION="nw41"Maintaining the NetWare Server" in Supervising the Network. If the settings match, replace the network board.PAGENUM=607 ID="BP601"NE2000-OS2001: The LSL is not loaded.NE2000-OS2Explanation: The Link Support Layer (LSL) module must be loaded before the computer can install the driver.Action: Edit the CONFIG.SYS file to load the LSL before the LAN driver, as in the following example:FORMAT="LINESPECIFIC"MOREINFO="NONE"DEVICE=C:\NETWARE\LSL.SYS 
DEVICE=C:\NETWARE\NE2000.SYS For information about the CONFIG.SYS file, see 
BOOK="ws_osenu" COLLECTION="nw41"NetWare Client for OS/2 User Guide. For information about LSL, see "BOOK="cncptenu" COLLECTION="nw41"Link Support Layer (LSL)" in Concepts.021: Could not add MLID Protocol ID.NE2000-OS2Explanation: The Link Support Layer (LSL) is configured with resources for four Protocol Identifiers. This number has been exceeded.Action: None. This message is for information only. For information about LSL, see "BOOK="cncptenu" COLLECTION="nw41"Link Support Layer (LSL)" in Concepts.022: Could not allocate memory. Virtual board did not load.NE2000-OS2Explanation: The computer cannot allocate enough memory to load another network board.Action: Do one of the following:MARK=BULLETInstall more memory in the computer.Edit the CONFIG.SYS file, and remove any nonessential drivers. For information about the CONFIG.SYS file, see 
BOOK="ws_osenu" COLLECTION="nw41"NetWare Client for OS/2 User Guide.050: The board cannot be found.NE2000-OS2Explanation: The network board was not found due to one or more of the following conditions: MARK=BULLETThe network board is not present in the computer. The network board settings are not the defaults, and they are not defined in the NET.CFG file.PAGENUM=608 ID="BP602"Another network board is using the same hardware settings as this network board.The network board is bad.Action: Do one or more of the following:MARK=BULLETMake sure the network board is properly seated into the slot. If jumper settings are not the defaults, make sure they match the settings in the NET.CFG file. For information about the NET.CFG file, see "BOOK="ws_osenu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for OS/2 User Guide.If the computer is not using the NET.CFG file, make sure the jumper settings are set to the defaults. If other network boards are using the same hardware settings, change the settings and try to reload the driver.Replace the bad network board with one that is good.051: Board RAM failed the memory test.NE2000-OS2Explanation: The memory test on the network board's internal static RAM failed.Action: Check the network board and other hardware.  If necessary, replace the network board.056: This interrupt is already used and cannot be shared.NE2000-OS2Explanation: The selected interrupt is being used by another device, so it cannot be used for this network board.Action: Change the jumper setting on the network board to use a different interrupt. For information about jumper settings, see the NE2000 hardware manual. Edit the NET.CFG file to reflect the correct interrupt level used by the network board. For information about the NET.CFG file, see "BOOK="ws_osenu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for OS/2 User Guide.223: The board must be placed in a 16-bit slot.NE2000-OS2Explanation: The network board is in an 8-bit slot.Action: Turn off the computer and move the network board from the 8-bit slot to a 16-bit slot. Reboot the computer, and load the driver.PAGENUM=609 ID="BP603"240: Invalid Node Override, Group Address bit was set now reset.NE2000-OS2Explanation: The driver address specified in the NET.CFG file contains the group bit set. (Note: If no address is specified, the driver will use the default address assigned by the network board's manufacturer.)Action: No action is necessary; the bit was cleared by the driver. However, to prevent this error message from being displayed every time the driver is loaded, edit the NET.CFG file and correct the node address override, as is shown in the following example:FORMAT="LINESPECIFIC"MOREINFO="NONE"LINK DRIVER NE2000 
   NODE ADDRESS address For information about editing the NET.CFG file, see "BOOK="ws_osenu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for OS/2 User Guide.241: Invalid Node Override, Local Administrated bit was set now reset.NE2000-OS2Explanation: The driver address specified in the NET.CFG file does not have the locally administered bit set. Note: If no address is specified, the driver will use the default address assigned by the network board's manufacturer.Action: No action is necessary; the bit was set by the driver. However, to prevent this error message from being displayed every time the driver is loaded, edit the NET.CFG file and correct the node address override, as is shown in the following example:FORMAT="LINESPECIFIC"MOREINFO="NONE"LINK DRIVER NE2000 
   NODE ADDRESS address For information about editing the NET.CFG file, see "BOOK="ws_osenu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for OS/2 User Guide.PAGENUM=610 ID="BP604"NE2000+-DOS001: The LSL is not loaded.NE2000+-DOSExplanation: The computer must load the Link Support Layer (LSL) before loading the driver.Action: Load the LSL; then load the driver, as in the following example:FORMAT="LINESPECIFIC"MOREINFO="NONE"C:\NWCLIENT\LSL MOREINFO="NONE"<Enter> 
C:\NWCLIENT\NE2000+ MOREINFO="NONE"<Enter> For information about LSL, see "BOOK="cncptenu" COLLECTION="nw41"Link Support Layer (LSL)" in Concepts.002: The LSL has no room for a board using frame type.NE2000+-DOSExplanation: The Link Support Layer (LSL) is configured with resources for a set number of network boards. (The default is 4.) This number has been exceeded.Action: Edit the NET.CFG file, and add the MAX BOARDS keyword to reflect the number of network boards to be loaded, as in the following example: FORMAT="LINESPECIFIC"MOREINFO="NONE"LINK SUPPORT 
   MAX BOARDS 6 Unload the driver; then reload it as in the following example:FORMAT="LINESPECIFIC"MOREINFO="NONE"C:\NWCLIENT\NE2000+ /u MOREINFO="NONE"<Enter> 
C:\NWCLIENT\NE2000+ MOREINFO="NONE"<Enter> For information on the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference. For information about LSL, see "BOOK="cncptenu" COLLECTION="nw41"Link Support Layer (LSL)" in Concepts.003: Could not find NE2000+ MLID to unload.NE2000+-DOSExplanation: The NE2000+ driver is not loaded.Action: None. This message is for information only.004: A TSR is loaded above the NE2000+ MLID.NE2000+-DOSExplanation: Another TSR (terminate-and-stay-resident) program was loaded after the NE2000+ driver.Action: The drivers must be unloaded in reverse order, as follows:PAGENUM=611 ID="BP605"FORMAT="LINESPECIFIC"MOREINFO="NONE"C:\NWCLIENT\NETX /u MOREINFO="NONE"<Enter> 
C:\NWCLIENT\IPXODI /u MOREINFO="NONE"<Enter> 
C:\NWCLIENT\NE2000+ /u MOREINFO="NONE"<Enter> Unload the TSRs; then try to unload the NE2000+ driver. You can force the NE2000+ driver to unload from the command line by using the /F switch after the driver name, as follows:FORMAT="LINESPECIFIC"MOREINFO="NONE"C:\NWCLIENT\NE2000+ /f MOREINFO="NONE"<Enter> Use caution when using the /F switch because it could cause the computer to hang.005: NE2000+ MLID could not be unloaded; the operation was aborted.NE2000+-DOSExplanation: The NE2000+ driver could not be shut down and unregistered; consequently, it cannot be unloaded.Action: To unload the driver, reboot the computer.006: The adapter did not initialize. NE2000+ did not load.NE2000+-DOSExplanation: The NE2000+ driver encountered an error while loading.Action: Corrective action can vary. See the preceding driver-specific message on the screen for specific information about the error that occurred.007: You need another MLID section heading in the NET.CFG file in order to load the MLID again. NE2000+-DOSExplanation: The NET.CFG file does not have an individual entry for each driver that is intended to be loaded.  This means that one of the drivers is not loaded into memory.Action: Unload the NE2000+ driver. Modify the NET.CFG file to contain a unique entry for each driver to be loaded. This requires an individual Link Driver heading in the NET.CFG file for each driver or each instance of the same driver. Load the drivers again. For information on the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.008: A NET.CFG is required to load the MLID again.NE2000+-DOSExplanation: The NET.CFG file does not have an individual entry for each driver that is intended to be loaded.  This means that one of the drivers is not loaded into memory.Action: Unload the NE2000+ driver. Modify the NET.CFG file to contain a unique entry for each driver to be loaded. This requires an individual Link Driver heading in the NET.CFG file for each driver or each instance of the same driver. Load the drivers again. For information on the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.PAGENUM=612 ID="BP606"009: The NET.CFG entry has been ignored.NE2000+-DOSExplanation: The NET.CFG file does not have an individual entry for each driver that is intended to be loaded.  This means that one of the drivers is not loaded into memory.Action: Unload the NE2000 driver. Modify the NET.CFG file to contain a unique entry for each driver to be loaded. This requires an individual Link Driver heading in the NET.CFG file for each driver or each instance of the same driver. Load the drivers again. For information on the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.011: The MLID does not support frame type. The protocol keyword has been ignored.NE2000+-DOSExplanation: An unsupported or incorrectly typed frame type has been specified with the protocol keyword.Action: Verify that the frame type assigned under the protocol keyword in the NET.CFG file is valid. For a list of valid frame types, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.012: The protocol keyword must have a frame type. Entry ignored.NE2000+-DOSExplanation: The PROTOCOL keyword entry is incomplete.Action: Correct the protocol entry in the NET.CFG file. The proper syntax for the protocol keyword is as follows:FORMAT="LINESPECIFIC"MOREINFO="NONE"PROTOCOL NE2000+ hex_protocol_ID frame_type For information about the PROTOCOL keyword, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.013: The MLID could not register Protocol ID number for protocol stack name for frame type frame_type.NE2000+-DOSExplanation: The Link Support Layer (LSL) is configured with resources for a set number of Protocol Identifiers. (The default is 4.) This number has been exceeded.Action: Edit the NET.CFG file, and add the MAX STACKS keyword to reflect the number of network boards to be loaded as in the following example:FORMAT="LINESPECIFIC"MOREINFO="NONE"LINK SUPPORT 
   MAX STACKS 6 Unload the driver; then reload it as in the following example:FORMAT="LINESPECIFIC"MOREINFO="NONE"C:\NWCLIENT\NE2000+ /u MOREINFO="NONE"<Enter> 
C:\NWCLIENT\LSL /u MOREINFO="NONE"<Enter> 
PAGENUM=613 ID="BP607"C:\NWCLIENT\LSL MOREINFO="NONE"<Enter> 
C:\NWCLIENT\NE2000+MOREINFO="NONE" <Enter> For information on the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference. For information about LSL, see "BOOK="cncptenu" COLLECTION="nw41"Link Support Layer (LSL)" in Concepts.014: This version of the LSL is not supported.NE2000+-DOSExplanation: The Link Driver the computer is using supports only Link Support Layer (LSL) versions later than 1.0.Action: Unload the LSL and replace it with a newer version. For information about LSL, see "BOOK="cncptenu" COLLECTION="nw41"Link Support Layer (LSL)" in Concepts.015: The frame type is already active for frame frame_type.NE2000+-DOSExplanation: The frame type is already loaded, and it cannot be loaded repeatedly.Action: Edit the NET.CFG file to load the frame type only once for a given network board. For information about frame types, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.016: The node address was incorrectly specified in the NET.CFG file.NE2000+-DOSExplanation: The node address override in the NET.CFG file is too long.Action: Edit the NET.CFG file and correct the node address. The node address must be less than or equal to 12 hex digits. For information about node address override, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.017: An invalid keyword was specified in NET.CFG on line number.NE2000+-DOSExplanation: The key word on the line indicated was not recognized.Action: Edit the NET.CFG file and correct the spelling of the keyword. For valid keywords, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.018: The frame type specified in the NET.CFG is not supported.NE2000+-DOSExplanation: The frame type specified with the FRAME keyword is not supported by the driver.Action: Edit the NET.CFG file and fix frame type. For information on supported frame types, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.PAGENUM=614 ID="BP608"019: An invalid NE2000+ node address is specified in NET.CFG. The MLID modified the incorrect address bits.NE2000+-DOSExplanation: The node address specified in the NET.CFG file contains set reserved bits.Action: Edit the NET.CFG file and correct the node address. For information about node addresses, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.050: The board cannot be found.NE2000+-DOSExplanation: The network board was not found due to one or more of the following conditions: MARK=BULLETThe network board is not present in the computer. The network board settings are not the defaults, and they are not defined in the NET.CFG file.Another network board is using the same hardware settings as this network board.The network board is bad.Action: Do one or more of the following:MARK=BULLETMake sure the network board is properly seated into the slot. If jumper settings are not the defaults, make sure they match the settings in the NET.CFG file. For information on the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.If the computer is not using the NET.CFG file, make sure the jumper settings are set to the defaults. If other network boards are using the same hardware settings, change the settings and try to reload the driver.Replace the bad network board with one that is good.051: Board RAM failed the memory test.NE2000+-DOSExplanation: The memory test on the network board's internal static RAM failed.Action: Check the network board and other hardware.  If necessary, replace the network board.PAGENUM=615 ID="BP609"054: The board did not respond to the initialization command.NE2000+-DOSExplanation: A hardware error has occurred.Action: Power down the computer; then reboot it. If the network board still does not respond, replace it with one that is good.PAGENUM=616 ID="BP610"NE2000+-NW025: You cannot load MSM31X on a NetWare 3.10 server.NE2000+-NWExplanation: The computer attempted to load MSM31X.NLM on a NetWare 3.10 server. MSM31X.NLM will run only on a NetWare 3.11 server.Action: Either load a version of the Media Support Module (MSM) that will run on a NetWare 3.10 server, or upgrade the server to NetWare 3.11. For information about MSM, see "BOOK="cncptenu" COLLECTION="nw41"Media Support Module (MSM)" in Concepts.026: On a NetWare 3.11 server, you must load LSLENH.NLM before you load MSM31X.NLM.NE2000+-NWExplanation: The Link Support Layer (LSL) and Media Support Module (MSM) have been loaded on a NetWare v3.11 server. An attempt was made to load LSLENH.NLM. The computer cannot load LSLENH.NLM once the MSM has been loaded. (LSLENH.NLM adds enhancement to the LSL.)Action: Unload MSM31X.NLM; then load LSLENH.NLM. Once the LSLENH.NLM has been loaded, load MSM31X.NLM again. For information about LSL and MSM, see "BOOK="cncptenu" COLLECTION="nw41"Link Support Layer (LSL)" and "BOOK="cncptenu" COLLECTION="nw41"Media Support Module (MSM)" in Concepts.050: The board cannot be found.NE2000+-NWExplanation: The network board was not found because of one or more of the following: MARK=BULLETThe network board is not present in the computer. The network board settings are not the defaults, and they are not defined in the AUTOEXEC.NCF file.Another network board is using the same hardware settings as this network board.The network board is bad.Action: Do one or more of the following:MARK=BULLETMake sure the network board is properly seated into the slot. If jumper settings are not the defaults, make sure they match the settings in the AUTOEXEC.NCF file. For information about the AUTOEXEC.NCF file, see "BOOK="superenu" COLLECTION="nw41"Maintaining the NetWare Server" in Supervising the Network.PAGENUM=617 ID="BP611"If the computer is not using the AUTOEXEC.NCF file, make sure the jumper settings are set to the defaults. If other network boards are using the same hardware settings, change the settings and try to reload the driver.Replace the faulty network board with one that works.051: Board RAM failed the memory test.NE2000+-NWExplanation: The memory test on the network board's internal static RAM failed.Action: Make sure the I/O port settings on the network board match the I/O port settings in the AUTOEXEC.NCF file. For information about the AUTOEXEC.NCF file, see "BOOK="superenu" COLLECTION="nw41"Maintaining the NetWare Server" in Supervising the Network. If the settings match, replace the network board.054: The board did not respond to the initialization command.NE2000+-NWExplanation: The network board didn't respond to a reset command.Action: Make sure the I/O port settings on the network board match the I/O port settings in the AUTOEXEC.NCF file. For information about the AUTOEXEC.NCF file, see "BOOK="superenu" COLLECTION="nw41"Maintaining the NetWare Server" in Supervising the Network. If the settings match, replace the network board.066-Adapter 1: The cable might be disconnected on the board.NE2000+-NWExplanation: The cable may be disconnected, or heavy traffic on the wire is delaying a packet from being sent.Action: If the problem persists, check the cable, or consider adding more networks to decrease LAN traffic.067: The group bit in the node address override was cleared.NE2000+-NWExplanation: You entered a node address with the Group address bit set; the Topology Specific Module (TSM) cleared it.Action: None. This message is for information only. For information about TSM, see "BOOK="cncptenu" COLLECTION="nw41"Topology Specific Module (TSM)" in Concepts.068: The local bit in the node address override was set.NE2000+-NWExplanation: You entered a node address without the local bit being set; the Topology Specific Module (TSM) set it.Action: None. This message is for information only. For information about TSM, see "BOOK="cncptenu" COLLECTION="nw41"Topology Specific Module (TSM)" in Concepts.PAGENUM=618 ID="BP612"071: The matching virtual adapter could not be found.NE2000+-NWExplanation: A new frame was being added to an existing network board, but the Media Support Module (MSM) could not locate a previous network board to link it with.Action: Obtain the most current version of MSM.NLM. For information about MSM, see "BOOK="cncptenu" COLLECTION="nw41"Media Support Module (MSM)" in Concepts.072: A resource tag is unavailable.NE2000+-NWExplanation: The server may not have enough available memory. NetWare cannot allocate memory for a resource tag.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.073: Unable to allocate memory.NE2000+-NWExplanation: The server may not have enough available memory. NetWare cannot allocate memory for the LAN driver.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.074: The hardware interrupt cannot be set.NE2000+-NWExplanation: NetWare could not set the hardware interrupt that the LAN driver registered. The LAN driver must have changed information in the configuration table (IntNumber, SharingFlags) after the hardware options were registered.Action: Make sure the interrupt setting on the board matches the setting in the AUTOEXEC.NCF file. For information about the AUTOEXEC.NCF file, see "BOOK="superenu" COLLECTION="nw41"Maintaining the NetWare Server" in Supervising the Network.075: The MLID cannot be registered with the LSL.NE2000+-NWExplanation: The LAN driver's Link Support Layer (LSL) ran out of logical boards, or it could not allocate memory for its internal structures.Action: Unload unneeded LAN drivers that are consuming large numbers of logical boards. Increase the available memory. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. For information about LSL, see "BOOK="cncptenu" COLLECTION="nw41"Link Support Layer (LSL)" in Concepts.076: The polling procedure cannot be added.NE2000+-NWExplanation: Too many polling processes are registered with the operating system.Action: Unload nonessential NLMs that may be using a polling procedure.PAGENUM=619 ID="BP613"077: The event notification routine cannot be registered.NE2000+-NWExplanation: The server may not have enough available memory. NetWare cannot allocate memory for internal structures related to event notification. Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.079: The MLID did not initialize MSMTxFreeCount.NE2000+-NWExplanation: The .LAN file is either outdated or corrupted.Action: Obtain a new .LAN file.086: The driver parameter block is too small.NE2000+-NWExplanation: The .LAN file is designed to run with an older version of the MSM.NLM.Action: Obtain a newer version of the .LAN file or an older version of the MSM.NLM. For information about MSM, see "BOOK="cncptenu" COLLECTION="nw41"Media Support Module (MSM)" in Concepts.087: The media parameter block is too small.NE2000+-NWExplanation: The topology NLM is designed to run with an older version of the MSM.NLM.Action: Obtain a newer version of the topology NLM or an older version of the MSM.NLM. For information about MSM, see "BOOK="cncptenu" COLLECTION="nw41"Media Support Module (MSM)" in Concepts.091: The hardware configuration conflicts.NE2000+-NWExplanation: Another hardware resource is being used, which the LAN driver is trying to register.Action: Change the hardware configuration of the network board or of the conflicting device.092: Cannot schedule AES without an HSM routine.NE2000+-NWExplanation: The LAN driver is either outdated or corrupted.Action: Obtain a new .LAN file.093: Cannot schedule interrupt time call back without an HSM routine.NE2000+-NWExplanation: The LAN driver is either outdated or corrupted.Action: Obtain a new .LAN file.PAGENUM=620 ID="BP614"094: Cannot set hardware interrupt without an HSM routine.NE2000+-NWExplanation: The LAN driver is either outdated or corrupted.Action: Obtain a new .LAN file.095: Cannot add polling without an HSM routine.NE2000+-NWExplanation: The LAN driver is either outdated or corrupted.Action: Obtain a new .LAN file.200-Adapter 1: The board's DMA did not complete the write.NE2000+-NWExplanation: The network board didn't complete a Direct Memory Access (DMA) transaction within the specified time. The driver will attempt to correct the problem by resetting the network board and resending the packet.Action: If the problem occurs often enough (more than once or twice a day), replace the network board.223: The board must be placed in a 16-bit slot.NE2000+-NWExplanation: The network board was placed in an 8-bit slot.Action: Move the network board to a 16-bit slot.224: This board is configured as an NE1000.NE2000+-NWExplanation: The board is responding with an NE1000 ROM signature.Action: Make sure the I/O port settings on the network board match the I/O port settings in the AUTOEXEC.NCF file. For information about the AUTOEXEC.NCF file, see "BOOK="superenu" COLLECTION="nw41"Maintaining the NetWare Server" in Supervising the Network. If the settings match, replace the network board.PAGENUM=621 ID="BP615"NE2000+-OS2001: The LSL is not loaded.NE2000+-OS2Explanation: The Link Support Layer (LSL) module must be loaded before the computer can install the driver.Action: Edit the CONFIG.SYS file to load the LSL before the LAN driver, as in the following example:FORMAT="LINESPECIFIC"MOREINFO="NONE"DEVICE=C:\NETWARE\LSL.SYS 
DEVICE=C:\NETWARE\NE2000+.SYS For information about the CONFIG.SYS file, see 
BOOK="ws_osenu" COLLECTION="nw41"NetWare Client for OS/2 User Guide. For information about LSL, see "BOOK="cncptenu" COLLECTION="nw41"Link Support Layer (LSL)" in Concepts.021: Could not add MLID Protocol ID.NE2000+-OS2Explanation: The Link Support Layer (LSL) is configured with resources for four Protocol Identifiers. This number has been exceeded.Action: None. This message is for information only. For information about LSL, see "BOOK="cncptenu" COLLECTION="nw41"Link Support Layer (LSL)" in Concepts.022: Could not allocate memory. Virtual board did not load.NE2000+-OS2Explanation: The computer cannot allocate enough memory to load another network board.Action: Do one of the following:MARK=BULLETInstall more memory in the computer.Edit the CONFIG.SYS file, and remove any nonessential drivers. For information about the CONFIG.SYS file, see 
BOOK="ws_osenu" COLLECTION="nw41"NetWare Client for OS/2 User Guide.050: The board cannot be found.NE2000+-OS2Explanation: The network board was not found due to one or more of the following conditions: MARK=BULLETThe network board is not present in the computer. The network board settings are not the defaults, and they are not defined in the NET.CFG file.PAGENUM=622 ID="BP616"Another network board is using the same hardware settings as this network board.The network board is bad.Action: Do one or more of the following:MARK=BULLETMake sure the network board is properly seated into the slot. If jumper settings are not the defaults, make sure they match the settings in the NET.CFG file. For information about the NET.CFG file, see "BOOK="ws_osenu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for OS/2 User Guide.If the computer is not using the NET.CFG file, make sure the jumper settings are set to the defaults. If other network boards are using the same hardware settings, change the settings and try to reload the driver.Replace the bad network board with one that is good.051: Board RAM failed the memory test.NE2000+-OS2Explanation: The memory test on the network board's internal static RAM failed.Action: Check the network board and other hardware.  If necessary, replace the network board.056: This interrupt is already used and cannot be shared.NE2000+-OS2Explanation: The selected interrupt is being used by another device, so it cannot be used for this network board.Action: Change the jumper setting on the network board to use a different interrupt. For information about jumper settings, see the NE2000+ hardware manual. Edit the NET.CFG file to reflect the correct interrupt level used by the network board. For information about the NET.CFG file, see "BOOK="ws_osenu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for OS/2 User Guide.223: The board must be placed in a 16-bit slot.NE2000+-OS2Explanation: The network board is in an 8-bit slot.Action: Turn off the computer and move the network board from the 8-bit slot to a 16-bit slot. Reboot the computer, and load the driver.PAGENUM=623 ID="BP617"240: Invalid Node Override, Group Address bit was set now reset.NE2000+-OS2Explanation: The driver address specified in the NET.CFG file contains the group bit set. (Note: If no address is specified, the driver will use the default address assigned by the network board's manufacturer.)Action: No action is necessary; the bit was cleared by the driver. However, to prevent this error message from being displayed every time the driver is loaded, edit the NET.CFG file and correct the node address override, as is shown in the following example:FORMAT="LINESPECIFIC"MOREINFO="NONE"LINK DRIVER NE2000+ 
   NODE ADDRESS address For information about editing the NET.CFG file, see "BOOK="ws_osenu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for OS/2 User Guide.241: Invalid Node Override, Local Administrated bit was set now reset.NE2000+-OS2Explanation: The driver address specified in the NET.CFG file does not have the locally administered bit set. Note: If no address is specified, the driver will use the default address assigned by the network board's manufacturer.Action: No action is necessary; the bit was set by the driver. However, to prevent this error message from being displayed every time the driver is loaded, edit the NET.CFG file and correct the node address override, as is shown in the following example:FORMAT="LINESPECIFIC"MOREINFO="NONE"LINK DRIVER NE2000+ 
   NODE ADDRESS address For information about editing the NET.CFG file, see "BOOK="ws_osenu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for OS/2 User Guide.PAGENUM=624 ID="BP618"NE2100-DOS001: The LSL is not loaded.NE2100-DOSExplanation: The computer must load the Link Support Layer (LSL) before loading the driver.Action: Load the LSL; then load the driver, as in the following example:FORMAT="LINESPECIFIC"MOREINFO="NONE"C:\NWCLIENT\LSL MOREINFO="NONE"<Enter> 
C:\NWCLIENT\NE2100MOREINFO="NONE" <Enter> For information about LSL, see "BOOK="cncptenu" COLLECTION="nw41"Link Support Layer (LSL)" in Concepts.002: The LSL has no room for a board using frame type.NE2100-DOSExplanation: The Link Support Layer (LSL) is configured with resources for a set number of network boards. (The default is 4.) This number has been exceeded.Action: Edit the NET.CFG file, and add the MAX BOARDS keyword to reflect the number of network boards to be loaded, as in the following example: FORMAT="LINESPECIFIC"MOREINFO="NONE"LINK SUPPORT 
   MAX BOARDS 6 Unload the driver; then reload it as in the following example:FORMAT="LINESPECIFIC"MOREINFO="NONE"C:\NWCLIENT\NE2100 /u MOREINFO="NONE"<Enter> 
C:\NWCLIENT\NE2100 MOREINFO="NONE"<Enter> For information on the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference. For information about LSL, see "BOOK="cncptenu" COLLECTION="nw41"Link Support Layer (LSL)" in Concepts.003: Could not find NE2100 MLID to unload.NE2100-DOSExplanation: The NE2100 driver is not loaded.Action: None. This message is for information only.004: A TSR is loaded above the NE2100 MLID.NE2100-DOSExplanation: Another TSR (terminate-and-stay-resident) program was loaded after the NE2100 driver.Action: The drivers must be unloaded in reverse order, as follows:PAGENUM=625 ID="BP619"FORMAT="LINESPECIFIC"MOREINFO="NONE"C:\NWCLIENT\NETX /u MOREINFO="NONE"<Enter> 
C:\NWCLIENT\IPXODI /u MOREINFO="NONE"<Enter> 
C:\NWCLIENT\NE2100 /u MOREINFO="NONE"<Enter> Unload the TSRs; then try to unload the NE2100 driver. You can force the NE2100 driver to unload from the command line by using the /F switch after the driver name, as follows:FORMAT="LINESPECIFIC"MOREINFO="NONE"C:\NWCLIENT\NE2100 /f MOREINFO="NONE"<Enter> Use caution when using the /F switch because it could cause the computer to hang.005: NE2100 MLID could not be unloaded; the operation was aborted.NE2100-DOSExplanation: The NE2100 driver could not be shut down and unregistered; consequently, it cannot be unloaded.Action: To unload the driver, reboot the computer.006: The adapter did not initialize. NE2100 did not load.NE2100-DOSExplanation: The NE2100 driver encountered an error while loading.Action: Corrective action can vary. See the preceding driver-specific message on the screen for specific information about the error that occurred.007: You need another MLID section heading in the NET.CFG file in order to load the MLID again. NE2100-DOSExplanation: The NET.CFG file does not have an individual entry for each driver that is intended to be loaded.  This means that one of the drivers is not loaded into memory.Action: Unload the NE2100 driver. Modify the NET.CFG file to contain a unique entry for each driver to be loaded. This requires an individual Link Driver heading in the NET.CFG file for each driver or each instance of the same driver. Load the drivers again. For information on the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.008: A NET.CFG is required to load the MLID again.NE2100-DOSExplanation: The NET.CFG file does not have an individual entry for each driver that is intended to be loaded.  This means that one of the drivers is not loaded into memory.Action: Unload the NE2100 driver. Modify the NET.CFG file to contain a unique entry for each driver to be loaded. This requires an individual Link Driver heading in the NET.CFG file for each driver or each instance of the same driver. Load the drivers again. For information on the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.PAGENUM=626 ID="BP620"009: The NET.CFG entry has been ignored.NE2100-DOSExplanation: The NET.CFG file does not have an individual entry for each driver that is intended to be loaded.  This means that one of the drivers is not loaded into memory.Action: Unload the NE2100 driver. Modify the NET.CFG file to contain a unique entry for each driver to be loaded. This requires an individual Link Driver heading in the NET.CFG file for each driver or each instance of the same driver. Load the drivers again. For information on the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.011: The MLID does not support frame type. The protocol keyword has been ignored.NE2100-DOSExplanation: An unsupported or incorrectly typed frame type has been specified with the protocol keyword.Action: Verify that the frame type assigned under the protocol keyword in the NET.CFG file is valid. For a list of valid frame types, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.012: The protocol keyword must have a frame type. Entry ignored.NE2100-DOSExplanation: The PROTOCOL keyword entry is incomplete.Action: Correct the protocol entry in the NET.CFG file. The proper syntax for the protocol keyword is as follows:FORMAT="LINESPECIFIC"MOREINFO="NONE"PROTOCOL NE2100 hex_protocol_ID frame_type For information about the PROTOCOL keyword, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.013: The MLID could not register Protocol ID number for protocol stack name for frame type frame_type.NE2100-DOSExplanation: The Link Support Layer (LSL) is configured with resources for a set number of Protocol Identifiers. (The default is 4.) This number has been exceeded.Action: Edit the NET.CFG file, and add the MAX STACKS keyword to reflect the number of network boards to be loaded, as in the following example:FORMAT="LINESPECIFIC"MOREINFO="NONE"LINK SUPPORT 
   MAX STACKS 6 Unload the driver; then reload it as in the following example:FORMAT="LINESPECIFIC"MOREINFO="NONE"C:\NWCLIENT\NE2100 /u MOREINFO="NONE"<Enter> 
C:\NWCLIENT\LSL /u MOREINFO="NONE"<Enter> 
C:\NWCLIENT\LSL MOREINFO="NONE"<Enter> 
C:\NWCLIENT\NE2100MOREINFO="NONE" <Enter> 
PAGENUM=627 ID="BP621"For information on the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference. For information about LSL, see "BOOK="cncptenu" COLLECTION="nw41"Link Support Layer (LSL)" in Concepts.014: This version of the LSL is not supported.NE2100-DOSExplanation: The Link Driver the computer is using supports only Link Support Layer (LSL) versions later than 1.0.Action: Unload the LSL and replace it with a newer version.015: The frame type is already active for frame frame_type.NE2100-DOSExplanation: The frame type is already loaded, and it cannot be loaded repeatedly.Action: Edit the NET.CFG file to load the frame type only once for a given network board. For information about frame types, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.016: The node address was incorrectly specified in the NET.CFG file.NE2100-DOSExplanation: The node address override in the NET.CFG file is too long.Action: Edit the NET.CFG file and correct the node address. The node address must be less than or equal to 12 hex digits. For information about node address override, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.017: An invalid keyword was specified in NET.CFG on line number.NE2100-DOSExplanation: The key word on the line indicated was not recognized.Action: Edit the NET.CFG file and correct the spelling of the keyword. For valid keywords, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.018: The frame type specified in the NET.CFG is not supported.NE2100-DOSExplanation: The frame type specified with the FRAME keyword is not supported by the driver.Action: Edit the NET.CFG file and fix frame type. For information on supported frame types, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.PAGENUM=628 ID="BP622"019: An invalid NE2100 node address is specified in NET.CFG. The MLID modified the incorrect address bits.NE2100-DOSExplanation: The node address specified in the NET.CFG file contains set reserved bits.Action: Edit the NET.CFG file and correct the node address. For information about node addresses, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.050: The board cannot be found.NE2100-DOSExplanation: The network board was not found due to one or more of the following conditions: MARK=BULLETThe network board is not present in the computer. The network board settings are not the defaults, and they are not defined in the NET.CFG file.Another network board is using the same hardware settings as this network board.The network board is bad.Action: Do one or more of the following:MARK=BULLETMake sure the network board is properly seated into the slot. If jumper settings are not the defaults, make sure they match the settings in the NET.CFG file. For information on the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.If the computer is not using the NET.CFG file, make sure the jumper settings are set to the defaults. If other network boards are using the same hardware settings, change the settings and try to reload the driver.Replace the bad network board with one that is good.054: The board did not respond to the initialization command.NE2100-DOSExplanation: A hardware error has occurred.Action: Power down the computer; then reboot it. If the network board still does not respond, replace it with one that is good.PAGENUM=629 ID="BP623"NE2100-NW025: You cannot load MSM31X on a NetWare 3.10 server.NE2100-NWExplanation: The computer attempted to load MSM31X.NLM on a NetWare 3.10 server. MSM31X.NLM will run only on a NetWare 3.11 server.Action: Either load a version of the Media Support Module (MSM) that will run on a NetWare 3.10 server, or upgrade the server to NetWare v3.11. For information about MSM, see "BOOK="cncptenu" COLLECTION="nw41"Media Support Module (MSM)" in Concepts.026: On a NetWare 3.11 server, you must load LSLENH.NLM before you load MSM31X.NLM.NE2100-NWExplanation: The Link Support Layer (LSL) and Media Support Module (MSM) have been loaded on a NetWare 3.11 server. An attempt was made to load LSLENH.NLM. The computer cannot load LSLENH.NLM once the MSM has been loaded. (LSLENH.NLM adds enhancement to the LSL.)Action: Unload MSM31X.NLM; then load LSLENH.NLM. Once the LSLENH.NLM has been loaded, load MSM31X.NLM again. For information about LSL and MSM, see "BOOK="cncptenu" COLLECTION="nw41"Link Support Layer (LSL)" and "BOOK="cncptenu" COLLECTION="nw41"Media Support Module (MSM)" in Concepts.054: The board did not respond to the initialization command.NE2100-NWExplanation: The network board didn't respond to a reset command.Action: Make sure the I/O port settings on the network board match the I/O port settings in the AUTOEXEC.NCF file. For information about the AUTOEXEC.NCF file, see "BOOK="superenu" COLLECTION="nw41"Maintaining the NetWare Server" in Supervising the Network. If the settings match, replace the network board.066-Adapter 1: The cable might be disconnected on the board.NE2100-NWExplanation: The cable may be disconnected, or heavy traffic on the wire is delaying a packet from being sent.Action: If the problem persists, check the cable, or consider adding more networks to decrease LAN traffic.067: The group bit in the node address override was cleared.NE2100-NWExplanation: You entered a node address with the Group address bit set; the Topology Specific Module (TSM) cleared it.Action: None. This message is for information only. For information about TSM, see "BOOK="cncptenu" COLLECTION="nw41"Topology Specific Module (TSM)" in Concepts.PAGENUM=630 ID="BP624"068: The local bit in the node address override was set.NE2100-NWExplanation: You entered a node address without the local bit being set; the Topology Specific Module (TSM) set it.Action: None. This message is for information only. For information about TSM, see "BOOK="cncptenu" COLLECTION="nw41"Topology Specific Module (TSM)" in Concepts.071: The matching virtual adapter could not be found.NE2100-NWExplanation: A new frame was being added to an existing network board, but the Media Support Module (MSM) could not locate a previous network board to link it with.Action: Obtain the most current version of MSM.NLM. For information about MSM, see "BOOK="cncptenu" COLLECTION="nw41"Media Support Module (MSM)" in Concepts.072: A resource tag is unavailable.NE2100-NWExplanation: The server may not have enough available memory. NetWare cannot allocate memory for a resource tag.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.073: Unable to allocate memory.NE2100-NWExplanation: The server may not have enough available memory. NetWare cannot allocate memory for the LAN driver.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.074: The hardware interrupt cannot be set.NE2100-NWExplanation: NetWare could not set the hardware interrupt that the LAN driver registered. The LAN driver must have changed information in the configuration table (IntNumber, SharingFlags) after the hardware options were registered.Action: Make sure the interrupt setting on the board matches the setting in the AUTOEXEC.NCF file. For information about the AUTOEXEC.NCF file, see "BOOK="superenu" COLLECTION="nw41"Maintaining the NetWare Server" in Supervising the Network.075: The MLID cannot be registered with the LSL.NE2100-NWExplanation: The LAN driver's Link Support Layer (LSL) ran out of logical boards, or it could not allocate memory for its internal structures.Action: Unload nonessential LAN drivers that are consuming large numbers of logical boards. Increase the available memory. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. For information about LSL, see "BOOK="cncptenu" COLLECTION="nw41"Link Support Layer (LSL)" in Concepts.PAGENUM=631 ID="BP625"076: The polling procedure cannot be added.NE2100-NWExplanation: Too many polling processes are registered with the operating system.Action: Unload nonessential NLMs that may be using a polling procedure.077: The event notification routine cannot be registered.NE2100-NWExplanation: The server may not have enough available memory. NetWare cannot allocate memory for internal structures related to event notification. Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.079: The MLID did not initialize MSMTxFreeCount.NE2100-NWExplanation: The .LAN file is either outdated or corrupted.Action: Obtain a new .LAN file.084: Couldn't allocate memory below the 16 Megabyte boundary.NE2100-NWExplanation: NetWare ran out of memory buffers from the pool below 16 megabytes.Action: Set reserved buffers below 16 MB (in STARTUP.NCF) to a higher number. For information about the STARTUP.NCF file, see "BOOK="superenu" COLLECTION="nw41"Maintaining the NetWare Server" in Supervising the Network 086: The driver parameter block is too small.NE2100-NWExplanation: The .LAN file is designed to run with an older version of the MSM.NLM.Action: Obtain a newer version of the .LAN file or an older version of the MSM.NLM. 087: The media parameter block is too small.NE2100-NWExplanation: The topology NLM is designed to run with an older version of the MSM.NLM.Action: Obtain a newer version of the topology NLM or an older version of the MSM.NLM. For information about MSM, see "BOOK="cncptenu" COLLECTION="nw41"Media Support Module (MSM)" in Concepts.091: The hardware configuration conflicts.NE2100-NWExplanation: Another hardware resource is being used, which the LAN driver is trying to register.Action: Change the hardware configuration of the network board or of the conflicting device.PAGENUM=632 ID="BP626"092: Cannot schedule AES without an HSM routine.NE2100-NWExplanation: The LAN driver is either outdated or corrupted.Action: Obtain a new .LAN file.093: Cannot schedule interrupt time call back without an HSM routine.NE2100-NWExplanation: The LAN driver is either outdated or corrupted.Action: Obtain a new .LAN file.094: Cannot set hardware interrupt without an HSM routine.NE2100-NWExplanation: The LAN driver is either outdated or corrupted.Action: Obtain a new .LAN file.095: Cannot add polling without an HSM routine.NE2100-NWExplanation: The LAN driver is either outdated or corrupted.Action: Obtain a new .LAN file.PAGENUM=633 ID="BP627"NE2100-OS2001: The LSL is not loaded.NE2100-OS2Explanation: The Link Support Layer (LSL) module must be loaded before the computer can install the driver.Action: Edit the CONFIG.SYS file to load the LSL before the LAN driver, as in the following example:FORMAT="LINESPECIFIC"MOREINFO="NONE"DEVICE=C:\NETWARE\LSL.SYS 
DEVICE=C:\NETWARE\NE2100.SYS For information about the CONFIG.SYS file, see 
BOOK="ws_osenu" COLLECTION="nw41"NetWare Client for OS/2 User Guide. For information about LSL, see "BOOK="cncptenu" COLLECTION="nw41"Link Support Layer (LSL)" in Concepts.021: Could not add MLID Protocol ID.NE2100-OS2Explanation: The Link Support Layer (LSL) is configured with resources for four Protocol Identifiers. This number has been exceeded.Action: None. This message is for information only. For information about LSL, see "BOOK="cncptenu" COLLECTION="nw41"Link Support Layer (LSL)" in Concepts.022: Could not allocate memory. Virtual board did not load.NE2100-OS2Explanation: The computer cannot allocate enough memory to load another network board.Action: Do one of the following:MARK=BULLETInstall more memory in the computer.Edit the CONFIG.SYS file, and remove any unneeded drivers. For information about the CONFIG.SYS file, see 
BOOK="ws_osenu" COLLECTION="nw41"NetWare Client for OS/2 User Guide.050: The board cannot be found.NE2100-OS2Explanation: The network board was not found due to one or more of the following conditions: MARK=BULLETThe network board is not present in the computer. The network board settings are not the defaults, and they are not defined in the NET.CFG file.PAGENUM=634 ID="BP628"Another network board is using the same hardware settings as this network board.The network board is bad.Action: Do one or more of the following:MARK=BULLETMake sure the network board is properly seated into the slot. If jumper settings are not the defaults, make sure they match the settings in the NET.CFG file. For information about the NET.CFG file, see "BOOK="ws_osenu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for OS/2 User Guide.If the computer is not using the NET.CFG file, make sure the jumper settings are set to the defaults. If other network boards are using the same hardware settings, change the settings and try to reload the driver.Replace the bad network board with one that is good.056: This interrupt is already used and cannot be shared.NE2100-OS2Explanation: The selected interrupt is being used by another device, so it cannot be used for this network board.Action: Change the jumper setting on the network board to use a different interrupt. See the NE2100 hardware manual for information about jumper settings. Edit the NET.CFG file to reflect the correct interrupt level used by the network board. For information about the NET.CFG file, see "BOOK="ws_osenu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for OS/2 User Guide.073: Unable to allocate memory.NE2100-OS2Explanation: Not enough free memory is available for the driver to initialize. The driver did not load.Action: Modify the CONFIG.SYS file to load only needed devices and drivers. Load the driver again. For information about the CONFIG.SYS file, see 
BOOK="ws_osenu" COLLECTION="nw41"NetWare Client for OS/2 User Guide. If necessary, install more memory on the computer. 240: Invalid Node Override, Group Address bit was set now reset.NE2100-OS2Explanation: The driver address specified in the NET.CFG file contains the group bit set. Note: If no address is specified, the driver will use the default address assigned by the network board's manufacturer.)PAGENUM=635 ID="BP629"Action: None. This message is for information only. The bit was cleared by the driver. However, to prevent this error message from being displayed every time the driver is loaded, edit the NET.CFG file and correct the node address override, as is shown in the following example:FORMAT="LINESPECIFIC"MOREINFO="NONE"LINK DRIVER NE2100 
   NODE ADDRESS address For information about editing the NET.CFG file, see "BOOK="ws_osenu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for OS/2 User Guide.241: Invalid Node Override, Local Administrated bit was set now reset.NE2100-OS2Explanation: The driver address specified in the NET.CFG file does not have the locally administered bit set. Note: If no address is specified, the driver will use the default address assigned by the network board's manufacturer.Action: None. This message is for information only. The bit was set by the driver. However, to prevent this error message from being displayed every time the driver is loaded, edit the NET.CFG file and correct the node address override, as is shown in the following example:FORMAT="LINESPECIFIC"MOREINFO="NONE"LINK DRIVER NE2100 
   NODE ADDRESS address For information about editing the NET.CFG file, see "BOOK="ws_osenu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for OS/2 User Guide.242: Only one NE2100 board can be present in the machine.NE2100-OS2Explanation: Only one physical network board can be present in the computer at one time. The driver does support more than one logical board.Action: Remove one of the network boards from the computer, and edit the NET.CFG file to reflect that only one physical network board is present. For information on the NET.CFG file, see "BOOK="ws_osenu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for OS/2 User Guide.PAGENUM=636 ID="BP630"NE3200-DOS001: The LSL is not loaded.NE3200-DOSExplanation: The computer must load the Link Support Layer (LSL) before loading the driver.Action: Load the LSL; then load the driver, as in the following example:FORMAT="LINESPECIFIC"MOREINFO="NONE"C:\NWCLIENT\LSL MOREINFO="NONE"<Enter> 
C:\NWCLIENT\NE3200 MOREINFO="NONE"<Enter> For information about LSL, see "BOOK="cncptenu" COLLECTION="nw41"Link Support Layer (LSL)" in Concepts.002: The LSL has no room for a board using frame type.NE3200-DOSExplanation: The Link Support Layer (LSL) is configured with resources for a set number of network boards. (The default is 4.) This number has been exceeded.Action: Edit the NET.CFG file, and add the MAX BOARDS keyword to reflect the number of network boards to be loaded, as in the following example: FORMAT="LINESPECIFIC"MOREINFO="NONE"LINK SUPPORT 
   MAX BOARDS 6 Unload the driver; then reload it as in the following example:FORMAT="LINESPECIFIC"MOREINFO="NONE"C:\NWCLIENT\NE3200 /u MOREINFO="NONE"<Enter> 
C:\NWCLIENT\NE3200 MOREINFO="NONE"<Enter> For information on the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference. For information about LSL, see "BOOK="cncptenu" COLLECTION="nw41"Link Support Layer (LSL)" in Concepts.003: Could not find NE3200 MLID to unload.NE3200-DOSExplanation: The NE3200 driver is not loaded.Action: None. This message is for information only.004: A TSR is loaded above the NE3200 MLID.NE3200-DOSExplanation: Another TSR (terminate-and-stay-resident) program was loaded after the NE3200 driver.Action: The drivers must be unloaded in reverse order, as follows:PAGENUM=637 ID="BP631"FORMAT="LINESPECIFIC"MOREINFO="NONE"C:\NWCLIENT\NETX /u MOREINFO="NONE"<Enter> 
C:\NWCLIENT\IPXODI /u MOREINFO="NONE"<Enter> 
C:\NWCLIENT\NE3200 /u MOREINFO="NONE"<Enter> Unload the TSRs; then try to unload the NE3200 driver. You can force the NE3200 driver to unload from the command line by using the /F switch after the driver name, as follows:FORMAT="LINESPECIFIC"MOREINFO="NONE"C:\NWCLIENT\NE3200 /f MOREINFO="NONE"<Enter> Use caution when using the /F switch because it could cause the computer to hang.005: NE3200 MLID could not be unloaded; the operation was aborted.NE3200-DOSExplanation: The NE3200 driver could not be shut down and unregistered; consequently, it cannot be unloaded.Action: To unload the driver, reboot the computer.006: The adapter did not initialize. NE3200 did not load.NE3200-DOSExplanation: The NE3200 driver encountered an error while loading.Action: Corrective action can vary. For specific information about the error that occurred, see the preceding driver-specific message on the screen.007: You need another MLID section heading in the NET.CFG file in order to load the MLID again. NE3200-DOSExplanation: The NET.CFG file does not have an individual entry for each driver that is intended to be loaded.  This means that one of the drivers is not loaded into memory.Action: Unload the NE3200 driver. Modify the NET.CFG file to contain a unique entry for each driver to be loaded. This requires an individual Link Driver heading in the NET.CFG file for each driver or each instance of the same driver. Load the drivers again. For information on the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.008: A NET.CFG is required to load the MLID again.NE3200-DOSExplanation: The NET.CFG file does not have an individual entry for each driver that is intended to be loaded.  This means that one of the drivers is not loaded into memory.Action: Unload the NE3200 driver. Modify the NET.CFG file to contain a unique entry for each driver to be loaded. This requires an individual Link Driver heading in the NET.CFG file for each driver or each instance of the same driver. Load the drivers again. For information on the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.PAGENUM=638 ID="BP632"009: The NET.CFG entry has been ignored.NE3200-DOSExplanation: The NET.CFG file does not have an individual entry for each driver that is intended to be loaded.  This means that one of the drivers is not loaded into memory.Action: Unload the NE3200 driver. Modify the NET.CFG file to contain a unique entry for each driver to be loaded. This requires an individual Link Driver heading in the NET.CFG file for each driver or each instance of the same driver. Load the drivers again. For information on the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.011: The MLID does not support frame type. The protocol keyword has been ignored.NE3200-DOSExplanation: An unsupported or incorrectly typed frame type has been specified with the protocol keyword.Action: Verify that the frame type assigned under the protocol keyword in the NET.CFG file is valid. For a list of valid frame types, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.012: The protocol keyword must have a frame type. Entry ignored.NE3200-DOSExplanation: The PROTOCOL keyword entry is incomplete.Action: Correct the protocol entry in the NET.CFG file. The proper syntax for the protocol keyword is as follows:FORMAT="LINESPECIFIC"MOREINFO="NONE"PROTOCOL NE3200 hex_protocol_ID frame_type For information about the PROTOCOL keyword, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.013: The MLID could not register Protocol ID number for protocol stack name for frame type frame_type.NE3200-DOSExplanation: The Link Support Layer (LSL) is configured with resources for a set number of Protocol Identifiers. (The default is 4.) This number has been exceeded.Action: Edit the NET.CFG file, and add the MAX STACKS keyword to reflect the number of network boards to be loaded, as in the following example:FORMAT="LINESPECIFIC"MOREINFO="NONE"LINK SUPPORT 
   MAX STACKS 6 Unload the driver; then reload it as in the following example:FORMAT="LINESPECIFIC"MOREINFO="NONE"C:\NWCLIENT\NE3200 /u MOREINFO="NONE"<Enter> 
C:\NWCLIENT\LSL /u MOREINFO="NONE"<Enter> 
PAGENUM=639 ID="BP633"C:\NWCLIENT\LSL MOREINFO="NONE"<Enter> 
C:\NWCLIENT\NE3200MOREINFO="NONE" <Enter> For information on the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.014: This version of the LSL is not supported.NE3200-DOSExplanation: The Link Driver the computer is using supports only Link Support Layer (LSL) versions later than 1.0.Action: Unload the LSL and replace it with a newer version. For information about LSL, see "BOOK="cncptenu" COLLECTION="nw41"Link Support Layer (LSL)" in Concepts.015: The frame type is already active for frame frame_type.NE3200-DOSExplanation: The frame type is already loaded, and it cannot be loaded repeatedly.Action: Edit the NET.CFG file to load the frame type only once for a given network board. For information about frame types, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.016: The node address was incorrectly specified in the NET.CFG file.NE3200-DOSExplanation: The node address override in the NET.CFG file is too long.Action: Edit the NET.CFG file and correct the node address. The node address must be less than or equal to 12 hex digits. For information about node address override, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.017: An invalid keyword was specified in NET.CFG on line number.NE3200-DOSExplanation: The key word on the line indicated was not recognized.Action: Edit the NET.CFG file and correct the spelling of the keyword. For valid keywords, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.018: The frame type specified in the NET.CFG is not supported.NE3200-DOSExplanation: The frame type specified with the FRAME keyword is not supported by the driver.Action: Edit the NET.CFG file and fix frame type. For information on supported frame types, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.PAGENUM=640 ID="BP634"019: An invalid NE3200 node address is specified in NET.CFG. The MLID modified the incorrect address bits.NE3200-DOSExplanation: The node address specified in the NET.CFG file contains set reserved bits.Action: Edit the NET.CFG file and correct the node address. For information about node addresses, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.050: The board cannot be found.NE3200-DOSExplanation: The network board was not found because it is not present in the computer. Action: Do one or more of the following:MARK=BULLETMake sure the network board is properly seated into the slot.Insert the network board into a slot, and run the CLASS=DISKConfiguration diskette to install it.051: Board RAM failed the memory test.NE3200-DOSExplanation: The memory test on the network board's internal static RAM failed.Action: Check the network board and other hardware.  If necessary, replace the network board.070: The board has failed.NE3200-DOSExplanation: A hardware error has occurred.Action: Power off the computer; then reboot it. Try to reload the driver. If the driver will not reload, a hardware failure has occurred, and you will need to replace the network board.235: No interrupt was selected. The board must be reconfigured.NE3200-DOSExplanation: When the network board was configured, no interrupt was selected. Note: This driver will not function with the no interrupt or the level-triggered options selected.Action: Run the CLASS=DISKConfiguration diskette and select an edge-triggered interrupt. 237: The firmware cannot be initialized.NE3200-DOSExplanation: The firmware is on the network board, but will not respond with the "initialization complete" status.Action: Possibly this is a hardware error. Replace the network board or contact the network board's vendor.PAGENUM=641 ID="BP635"238: The firmware cannot be started.NE3200-DOSExplanation: The network board did not reset. The firmware cannot be downloaded.Action: This is possibly a hardware error. Replace the network board or contact the network board's vendor.PAGENUM=642 ID="BP636"NE3200-NW025: You cannot load MSM31X on a NetWare 3.10 server.NE3200-NWExplanation: The computer attempted to load MSM31X.NLM on a NetWare v3.10 server. MSM31X.NLM will run only on a NetWare 3.11 server.Action: Either load a version of the Media Support Module (MSM) that will run on a NetWare 3.10 server, or upgrade the server to NetWare 3.11. For information about MSM, see"BOOK="cncptenu" COLLECTION="nw41"Media Support Module (MSM)" in Concepts.026: On a NetWare 3.11 server, you must load LSLENH.NLM before you load MSM31X.NLM.NE3200-NWExplanation: The Link Support Layer (LSL) and Media Support Module (MSM) have been loaded on a NetWare 3.11 server. An attempt was made to load LSLENH.NLM. The computer cannot load LSLENH.NLM once the MSM has been loaded. (LSLENH.NLM adds enhancement to the LSL.)Action: Unload MSM31X.NLM; then load LSLENH.NLM. Once the LSLENH.NLM has been loaded, load MSM31X.NLM again. For information about LSL and MSM, see "BOOK="cncptenu" COLLECTION="nw41"Link Support Layer (LSL)" and "BOOK="cncptenu" COLLECTION="nw41"Media Support Module (MSM)" in Concepts.050: The board cannot be found.NE3200-NWExplanation: Either the network board is not present in the computer, or the network board's configuration cannot be obtained.Action: Do one of the following:MARK=BULLETMake sure the network board is properly seated into the slot. Insert the network board into a slot, and run the CLASS=DISKConfiguration diskette to install it.051: Board RAM failed the memory test.NE3200-NWExplanation: The memory test on the network board's internal static RAM failed.Action: Make sure the I/O port settings on the network board match the I/O port settings in the AUTOEXEC.NCF file. For information about the AUTOEXEC.NCF file, see "BOOK="superenu" COLLECTION="nw41"Maintaining the NetWare Server" in Supervising the Network. If the settings match, replace the network board.PAGENUM=643 ID="BP637"067: The group bit in the node address override was cleared.NE3200-NWExplanation: You entered a node address with the Group address bit set; the Topology Specific Module (TSM) cleared it.Action: None. This message is for information only. For information about TSM, see "BOOK="cncptenu" COLLECTION="nw41"Topology Specific Module (TSM)" in Concepts.068: The local bit in the node address override was set.NE3200-NWExplanation: You entered a node address without the local bit being set; the Topology Specific Module (TSM) set it.Action: None. This message is for information only. For information about TSM, see "BOOK="cncptenu" COLLECTION="nw41"Topology Specific Module (TSM)" in Concepts.070: The board has failed.NE3200-NWExplanation: Firmware was downloaded to the network board, but the network board did not accept commands.Action: Check the network board and other hardware.  If necessary, replace the network board.071: The matching virtual adapter could not be found.NE3200-NWExplanation: A new frame was being added to an existing network board, but the Media Support Module (MSM) could not locate a previous network board to link it with.Action: Obtain the most current version of MSM.NLM. For information about MSM, see "BOOK="cncptenu" COLLECTION="nw41"Media Support Module (MSM)" in Concepts.072: A resource tag is unavailable.NE3200-NWExplanation: The server may not have enough available memory. NetWare cannot allocate memory for a resource tag.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.073: Unable to allocate memory.NE3200-NWExplanation: The server may not have enough available memory. NetWare cannot allocate memory for the LAN driver.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.PAGENUM=644 ID="BP638"074: The hardware interrupt cannot be set.NE3200-NWExplanation: NetWare could not set the hardware interrupt that the LAN driver registered. The LAN driver must have changed information in the configuration table (IntNumber, SharingFlags) after the hardware options were registered.Action: Make sure the interrupt setting on the board matches the setting in the AUTOEXEC.NCF file. For information about the AUTOEXEC.NCF file, see "BOOK="superenu" COLLECTION="nw41"Maintaining the NetWare Server" in Supervising the Network 075: The MLID cannot be registered with the LSL.NE3200-NWExplanation: The LAN driver's Link Support Layer (LSL) ran out of logical boards, or it could not allocate memory for its internal structures.Action: Unload nonessential LAN drivers that are consuming large numbers of logical boards. Increase the available memory. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. For information about LSL, see "BOOK="cncptenu" COLLECTION="nw41"Link Support Layer (LSL)" in Concepts.076: The polling procedure cannot be added.NE3200-NWExplanation: Too many polling processes are registered with the operating system.Action: Unload nonessential NLMs that may be using a polling procedure.077: The event notification routine cannot be registered.NE3200-NWExplanation: The server may not have enough available memory. NetWare cannot allocate memory for internal structures related to event notification. Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.078: The firmware file cannot be read.NE3200-NWExplanation: NetWare could not read from the .LAN file on the disk from which it was loaded.Action: Check for hardware problems with the disk from which the LAN driver was loaded.079: The MLID did not initialize MSMTxFreeCount.NE3200-NWExplanation: The .LAN file is either outdated or corrupted.Action: Obtain a new .LAN file.PAGENUM=645 ID="BP639"086: The driver parameter block is too small.NE3200-NWExplanation: The .LAN file is designed to run with an older version of the MSM.NLM.Action: Obtain a newer version of the .LAN file or an older version of the MSM.NLM.087: The media parameter block is too small.NE3200-NWExplanation: The topology NLM is designed to run with an older version of the MSM.NLM.Action: Obtain a newer version of the topology NLM or an older version of the MSM.NLM. For information about MSM, see "BOOK="cncptenu" COLLECTION="nw41"Media Support Module (MSM)" in Concepts.091: The hardware configuration conflicts.NE3200-NWExplanation: Another hardware resource is being used, which the LAN driver is trying to register.Action: Change the hardware configuration of the network board or of the conflicting device.092: Cannot schedule AES without an HSM routine.NE3200-NWExplanation: The LAN driver is either outdated or corrupted.Action: Obtain a new .LAN file.093: Cannot schedule interrupt time call back without an HSM routine.NE3200-NWExplanation: The LAN driver is either outdated or corrupted.Action: Obtain a new .LAN file.094: Cannot set hardware interrupt without an HSM routine.NE3200-NWExplanation: The LAN driver is either outdated or corrupted.Action: Obtain a new .LAN file.095: Cannot add polling without an HSM routine.NE3200-NWExplanation: The LAN driver is either outdated or corrupted.Action: Obtain a new .LAN file.235: No interrupt was selected. The board must be reconfigured.NE3200-NWExplanation: No interrupt was specified when the network board was installed.Action: Run the CLASS=DISKEISA Configuration diskette that came with the computer, and select an interrupt. PAGENUM=646 ID="BP640"236: No RCBs are available for the board to initialize.NE3200-NWExplanation: The computer could not initially allocate Receive Control Blocks for this network board.Action: Set the minimum packet receive buffers (in STARTUP.NCF) to a higher number. For information about the STARTUP.NCF, see "BOOK="superenu" COLLECTION="nw41"Maintaining the NetWare Server" in Supervising the Network.237: The firmware cannot be initialized.NE3200-NWExplanation: The network board did not inform the host that it was alive after it was reset.Action: Check the network board and other hardware.  If necessary, replace the network board.238: The firmware cannot be started.NE3200-NWExplanation: The network board passed the self-test after being reset, but it did not download the firmware.Action: Make sure the network board is in a bus-master compatible slot. You may need to replace the board.241: The board's ROM has checksum errors.NE3200-NWExplanation: The network board failed the self-test; a ROM checksum error occurred.Action: Check the network board and other hardware.  If necessary, replace the network board.PAGENUM=647 ID="BP641"NE3200-OS2001: The LSL is not loaded.NE3200-OS2Explanation: The Link Support Layer (LSL) module must be loaded before the computer can install the driver.Action: Edit the CONFIG.SYS file to load the LSL before the LAN driver, as in the following example:FORMAT="LINESPECIFIC"MOREINFO="NONE"DEVICE=C:\NETWARE\LSL.SYS 
DEVICE=C:\NETWARE\NE3200.SYS For information about editing the NET.CFG file, see "BOOK="ws_osenu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for OS/2 User Guide. For information about LSL, see "BOOK="cncptenu" COLLECTION="nw41"Link Support Layer (LSL)" in Concepts.021: Could not add MLID Protocol ID.NE3200-OS2Explanation: The Link Support Layer (LSL) is configured with resources for four Protocol Identifiers. This number has been exceeded.Action: None. This message is for information only. For information about LSL, see "BOOK="cncptenu" COLLECTION="nw41"Link Support Layer (LSL)" in Concepts.022: Could not allocate memory. Virtual board did not load.NE3200-OS2Explanation: The computer cannot allocate enough memory to load another network board.Action: Do one of the following:MARK=BULLETInstall more memory in the computer.Edit the CONFIG.SYS file, and remove any nonessential drivers. For information about editing the NET.CFG file, see "BOOK="ws_osenu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for OS/2 User Guide.050: The board cannot be found.NE3200-OS2Explanation: The network board's configuration cannot be obtained.Action: Do one of the following:MARK=BULLETMake sure the network board is properly seated into the slot. Insert the network board into a slot, and run the CLASS=DISKConfiguration diskette to install it.PAGENUM=648 ID="BP642"051: Board RAM failed the memory test.NE3200-OS2Explanation: The memory test on the network board's internal static RAM failed.Action: Check the network board and other hardware.  If necessary, replace the network board.060: The board did not reset.NE3200-OS2Explanation: This is a hardware error. The network board did not respond to a reset command.Action: Check the network board and other hardware.  If necessary, replace the network board.070: The board has failed.NE3200-OS2Explanation: A hardware error has occurred.Action: Make sure there are no hardware conflicts. Power off the computer; then reboot it. Try to reload the driver. If the driver will not reload, a hardware failure has occurred, and you will need to replace the network board.235: No interrupt was selected. The board must be reconfigured.NE3200-OS2Explanation: No interrupt was specified when the network board was installed.Action: Run the CLASS=DISKEISA Configuration diskette that came with the computer, and select an interrupt. Set it so that it is edge triggered.236: No RCBs are available for the board to initialize.NE3200-OS2Explanation: The computer could not initially allocate Receive Control Blocks for this network board. The driver needs an ECB from the Link Support Layer (LSL) to receive packets into. The LSL defaults to 15 ECBs; currently they are all in use.Action: Edit the NET.CFG file and add or edit the key word buffers under the LINK SUPPORT heading, as in the following example:FORMAT="LINESPECIFIC"MOREINFO="NONE"LINK SUPPORT 
   Buffers number For information about editing the NET.CFG file, see "BOOK="ws_osenu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for OS/2 User Guide.PAGENUM=649 ID="BP643"237: The firmware cannot be initialized.NE3200-OS2Explanation: The network board did not inform the host that it was alive after it was reset.Action: Check the network board and other hardware.  If necessary, replace the network board.240: Invalid Node Override, Group Address bit was set now reset.NE3200-OS2Explanation: The driver address specified in the NET.CFG file contains the group bit set. Note: If no address is specified, the driver will use the default address assigned by the network board's manufacturer.)Action: None. This message is for information only. The bit was cleared by the driver. However, to prevent this error message from being displayed every time the driver is loaded, edit the NET.CFG file and correct the node address override, as is shown in the following example:FORMAT="LINESPECIFIC"MOREINFO="NONE"LINK DRIVER NE3200 
   NODE ADDRESS address For information about editing the NET.CFG file, see "BOOK="ws_osenu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for OS/2 User Guide.241: Invalid Node Override, Local Administrated bit was set now reset.NE3200-OS2Explanation: The driver address specified in the NET.CFG file does not have the locally administered bit set. Note: If no address is specified, the driver will use the default address assigned by the network board's manufacturer.)Action: None. This message is for information only. The bit was set by the driver. However, to prevent this error message from being displayed every time the driver is loaded, edit the NET.CFG file and correct the node address override, as is shown in the following example:FORMAT="LINESPECIFIC"MOREINFO="NONE"LINK DRIVER NE3200 
   NODE ADDRESS address For information about editing the NET.CFG file, see "BOOK="ws_osenu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for OS/2 User Guide.243: The adapter failed diagnostics test.NE3200-OS2Explanation: The network board is defective.Action: Replace the network board.PAGENUM=650 ID="BP644"NE32HUB-NW050: The board cannot be found.NE32HUB-NWExplanation: Either the NE32HUB network board is not present in the computer, or the network board has a bad PROM.Action: Make sure the network board is seated properly in the computer. If the problem persists, replace the board.054: The board did not respond to the initialization command.NE32HUB-NWExplanation: An internal error occurred. There is something wrong with the relationship between the NE32HUB-Base and NE32HUB-TPE (Twisted Pair Extension) network boards.Action: Contact your Novell Authorized Reseller.073: Unable to allocate memory.NE32HUB-NWExplanation: NetWare does not have enough memory for the requested operation.Action: Do one or more of the following:MARK=BULLETDelete unused files and directories on the specified volume.Change the SET server utility's "Minimum File Delete Wait Time" parameter so that files can be purged immediately, rather than being retained in a salvageable state on the volume.Use FILER or the Network Administrator utility to purge deleted files on the specified directory that cannot be purged automatically. (Unpurged files are using up directory table space.)Use REMOVE DOS or SECURE CONSOLE to free the memory in the server that is reserved for DOS.Unload some loadable modules (such as INSTALL or MONITOR) that are not currently needed.Dismount any volumes that are not being used.If the problem persists, back up all files in the volume, bring down the server, and use INSTALL to reinitialize the volume. Specify a block size of 64 KB and turn the Block Suballocation option to OFF. (This setting wastes a lot of disk space, but increases the amount of memory available.)PAGENUM=651 ID="BP645"For information, see "BOOK="superenu" COLLECTION="nw41"Maintaining the NetWare Server" in Supervising the Network and "BOOK="utlrfenu" COLLECTION="nw41"SET" in Utilities Reference.080: The board could not be configured.NE32HUB-NWExplanation: When the NE32HUB network board tried to read the EISA BIOS file to check the interrupt level and shared memory settings, it found that the interrupt level and/or the shared memory was not set, or was set incorrectly.Action: Use the EISA CONFIG utility to set the NE32HUB's interrupt level and shared memory correctly.200: The board is present, but its ID number cannot be found.NE32HUB-NWExplanation: An NE32HUB-TPE (Twisted Pair Extension) network board is present in the computer, but its ID number cannot be found. This error indicates that there is a bad connection between an NE32HUB-TPE network board and an NE32HUB-Base network board, or a bad PROM on the TPE board.Action: Make sure the ribbon cable between the NE32HUB-TPE network board and the NE32HUB-Base network board is connected properly, or replace the NE32HUB-TPE network board with one that is good.201: Either all of the Twisted Pair Extension (TPE) network boards are attached to a base network board, or no (TPE) boards are present.NE32HUB-NWExplanation: The NE32HUB driver was loaded using the "HUBTYPE=TPE" keyword. Use this keyword only when you want a TPE network board to be present in one of the computer's slots without being attached to a Base network board. This allows the TPE network board to manage the hub. If all of the TPEs present in the computer are attached to a Base network board, or if no TPEs are present in the computer, this message will appear.Action: Insert a TPE network board that is not attached to a Base network board, or reload the driver and do not use the "HUBTYPE=TPE" keyword.235: No interrupt was selected. The board must be reconfigured.NE32HUB-NWExplanation: All of the interrupts are being used.Action: Use the EISA CONFIG utility to see which interrupts are being used, then clear the interrupt you want to use.241: The board's ROM has checksum errors.NE32HUB-NWExplanation: The NE32HUB network board has a bad ID PROM.Action: Replace the NE32HUB network board.PAGENUM=652 ID="BP646"NETADMIN001: The utility can't get the syntax ID for property name.NETADMINExplanation: An internal system error has occurred. The program could not get the syntax ID for the specified object property.Action: Restart NETADMIN and retry the operation. If the problem persists, contact your Novell Authorized Reseller.002: The utility can't create the change buffer. Error code: code. NETADMINExplanation: An internal system error has occurred. The buffer required for changing properties could not be created.Action: Restart  NETADMIN and retry the operation. If the problem persists, contact your Novell Authorized Reseller.003: An attempt to open file file failed. NETADMINExplanation: The user tried to open a file to save or restore search parameters; however, the file could not be opened.Action: Make sure the file exists. Make sure the user has the appropriate rights to read from and write to the file.004:  The search parameter was not found in search file file. The restore operation was abandoned. NETADMINExplanation: The .SCH file did not contain one of the required parameters for an .SCH file. The file is not usable for restoring search parameters. These files must follow a specific format. Being named with an .SCH extention is only a small part of the requirements.Action: Perform the following actions:MARK=BULLETIf a NetWare utility was used to create the file, report this error to your Novell reseller. Choose a different file. Make sure you have the approprite rights to write to the file.PAGENUM=653 ID="BP647"030: Field property was deleted by someone else. Restart your editing of this screen by selecting this screen again.NETADMINExplanation: The program could not modify an object's property because the property had been deleted by another workstation.  NETADMIN will continue.Action: Edit the field again.  For information about object properties, see "BOOK="utlrfenu" COLLECTION="nw41"NDS and Bindery Objects and Properties" in Utilities Reference.040: Field property was added by someone else. Edit this screen again.NETADMINExplanation: The program could not modify an object's property because this property accepts only one piece of information, and it has already been added.  NETADMIN will continue.Action: Edit the field again to make sure that it is correct. For information about object properties, see "BOOK="utlrfenu" COLLECTION="nw41"NDS and Bindery Objects and Properties" in Utilities Reference.060: Field value has been added by someone else. Restart by selecting this screen again.NETADMINExplanation: The property value could not be modified because the value had already been added by another user.  NETADMIN will continue.Action: Edit the field again to verify that the property value cannot be modified. For information, see "BOOK="utlrfenu" COLLECTION="nw41"NDS and Bindery Objects and Properties" in Utilities Reference.070: Field: property can't have duplicate values.NETADMINExplanation: The object property could not be modified because the property cannot be assigned duplicate values.  NETADMIN will continue.Action: None. This message is for information only.080: Another workstation deleted one of the values. Property name will not be changed.NETADMINExplanation: The object property could not be modified because another user has deleted the value you wanted to modify.  NETADMIN will continue.Action: None. This message is for information only.090: Object name for field name does not exist.NETADMINExplanation: This field has a value that refers to an object that is not in the database.Action: Delete this object from the field.PAGENUM=654 ID="BP648"101: The utility can't add property name to object name. Error code: code.NETADMINExplanation: An internal system error was reported by the NWDSModifyObject function.Action: Restart  NETADMIN and retry the operation. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.104: The utility cannot rename object type name to new_name. Error code: code.NETADMINExplanation: An internal system error was reported by the NWDSModifyDN function.Action: Restart  NETADMIN and retry the operation. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.106: The utility cannot create object name named name. Error code: code.NETADMINExplanation: The object could not be created for some reason other than that it already exists.Action: Restart  NETADMIN and retry the operation. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.107: The utility cannot add the Script property. Error code: code.NETADMINExplanation: An internal system error was reported by the NWDSModifyObject function.Action: Restart  NETADMIN and retry the operation. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.109:  The utility can't open the Unicode translation tables.NETADMINAction: See the action in message IDREF="FM15675""970: The attempt to open the Unicode table files failed." in Appendix C.110: The utility can't open the script file. Error code: code.NETADMINExplanation: An internal system error was reported by the NWDSOpenStream function.Action: Restart  NETADMIN and retry the operation. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=655 ID="BP649"111: The utility can't read the login script for object name. Error code: code.NETADMINExplanation: An internal DOS call to read the login script file failed.Action: Restart  NETADMIN and retry the operation. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.112: The utility can't write the script file information. Error code: code.NETADMINExplanation: An internal system error prevented the program from writing information to the script file.Action: Restart  NETADMIN and retry the operation. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.113: The utility can't change the Group object's membership list. The user's group membership and security equivalence will not be updated either. Error code: code.NETADMINExplanation: When adding a user to a group, the program must update three properties: the user's group membership, the user's security equivalence, and the group's member list. This error occurred because the group's member list could not be updated. The User object probably does not have rights to read and update the member list property of the group object. Because the group's member list could not be updated, the user's group membership and security equivalence properties will not be updated, either.Action: Make sure the user has appropriate user access rights for the Group object to perform this update. Try the operation again. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A.114: The utility can't change the role occupant property. Error code: code.NETADMINExplanation: When you add an object as a role occupant of an organizational role, the program must update the object's security equivalence, as well as the role occupant property of the Organizational Role object. In this case, the User object did not have appropriate rights to modify the role occupant property.Action: Make sure the user has appropriate user access rights to this property. Retry the operation. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A.115: The utility can't change the user's membership list. This is usually caused by not having enough rights to modify the group membership property. The group's member list will not be updated either. Error code: code.NETADMINPAGENUM=656 ID="BP650"Explanation: When adding a user to a group, the program must update three properties: the user's group membership, the user's security equivalence, and the group's member list. This error occurred because the group's member list could not be updated. The User object probably does not have rights to read and update the member list property of the group object. Because the group's member list could not be updated, the user's group membership and security equivalence properties will not be updated either.Action: Make sure the user has appropriate user access rights to both the User object and the Group object. Retry the operation. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A.116: The utility can't change the user's security equivalence property. Error code: code.NETADMINExplanation: The Security Equivalence property cannot be updated. This is usually caused by inappropriate rights to the object. The group membership and the group's member list will be updated anyway.Action: Manually add the group to the security equivalence property of this object. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A.118: The utility can't get the data from the Directory Services for this screen. Error code: code.NETADMINExplanation: An internal error occurred. Property information cannot be obtained.Action: Restart NETADMIN and retry the operation. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.120: Field name was not changed because it contains incorrect data.NETADMINExplanation: Incorrect data was entered for this field. For example, characters in a numeric field.Action: Enter the information correctly, making sure it matches the types of information the field requires. For information, see "BOOK="utlrfenu" COLLECTION="nw41"NETADMIN" in Utilities Reference.123: You are not logged in to Directory Services. You must be logged in to Directory Services before you can run NETADMIN.NETADMINExplanation: The User object has not been authenticated as an authorized NetWare Directory Services user, so the attempt to use  NETADMIN has failed.  NETADMIN will not continue.Action: Log in as a valid NetWare Directory Services user; then retry the operation.Note: To complete this task, unloading the VLMs and reloading them may be necessary.PAGENUM=657 ID="BP651"124: Object name of class name was not deleted. Error code: code.NETADMINExplanation: An internal error prevented the user from deleting the object.Action: Restart  NETADMIN and retry the operation. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.127: The user template could not be read. Error code: code.NETADMINExplanation: An internal error prevented the program from reading the template user. (The User object exists, but it cannot be read.)Action: Restart  NETADMIN and retry the operation. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.128: The utility can't rename object type name to new_name because an object named new_name already exists.NETADMINExplanation: The user tried to rename an object; however, the new name has already been assigned to another object.  NETADMIN will continue.Action: Give the object a unique name. For information about object name, see "BOOK="utlrfenu" COLLECTION="nw41"NDS and Bindery Objects and Properties" in Utilities Reference.129: The utility can't rename object type name to new_name because object name new_name is invalid.NETADMINExplanation: The user tried to rename an object; however, the new name is invalid.  NETADMIN will continue.Action: Make sure the name qualifier (CNMOREINFO="NONE"=, OMOREINFO="NONE"=, OUMOREINFO="NONE"=) is the correct type for this object. Use a valid object name; then retry the operation. For information about object names, see "BOOK="utlrfenu" COLLECTION="nw41"NDS and Bindery Objects and Properties" in Utilities Reference .PAGENUM=658 ID="BP652"130: The user could not be removed from the group's membership list. An error occurred attempting to add the group to the user's membership and security equivalence lists. When the utility attempted to remove the user from the group's membership list, an error occurred. This means that this user will appear as a member of this group when editing the group object. Error code: codeNETADMINExplanation: The user could not be added to the group member list. The user's group membership and security equivalence properties have already been updated. This problem could be caused by not having appropriate rights to update the Group object.Action: Update the group member list by editing the Group object itself. This requires that the User object has appropriate rights to update the field. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A.131: The utility added the user to the Group object. However, an error occurred when the utility attempted to add the Group object to the user's group membership list and security equivalence list. Error code: code.NETADMINExplanation: The Group object was added to the User's Object Group membership and security equivalence; however, the User object could not be added to the Group object's member list property. This was probably caused by inappropriate rights to the Group object.Action: Delete this Group object from the User object's group membership and security equivalence; then add the User object to the group again. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A.132: The user was added as a role occupant, but the user's Security Equivalence was not updated. Error code: code.NETADMINExplanation: When adding a user as a role occupant, both the Organizational Role object and User object must be updated. The user's security equivalence property must be updated. An error occurred when the user tried to add the organizational role to the security equivalence property of the User object. This is usually caused by not having appropriate rights to the User object.Action: Update the security equivalence property of the user. This requires that the User object has appropriate rights to update this field. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A.133: Server name does not support accounting.NETADMINExplanation: Accounting information was requested on a server that does not support accounting. Accounting is supported only on NetWare 3 and later.  NETADMIN will continue.Action: None. This message is for information only.PAGENUM=659 ID="BP653"134: Disk restrictions cannot be removed. Error code: code.NETADMINExplanation: An internal error prevented the program from removing disk restrictions.Action: Restart  NETADMIN and retry the operation. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.136: The utility cannot attach to server name. Error code: code.NETADMINAction: See message IDREF="FM32454" "137: The utility cannot attach to the server associated with volume object name. Error code: code." ID="FM32454"137: The utility cannot attach to the server associated with volume object name. Error code: code.NETADMINExplanation: An internal error prevented the program from getting the server connection ID; therefore, the utility could not attach to the server.Action: Restart  NETADMIN and retry the operation. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.138: The utility can't get the object restrictions for this volume. Error code: code.NETADMINExplanation: An internal error prevented the program from getting disk restrictions.Action: Restart  NETADMIN and retry the operation. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.140: The path includes a file or directory name not conforming to the DOS 8.3 format.NETADMINExplanation: When using DOS, file and directory names can include no more than eight characters plus a three-character extension. One of the names in the path does not conform to this limitation.Action: Specify a valid path.141: The utility cannot get information about the volume. Error code: code.NETADMINExplanation: An internal error prevented the program from getting directory space information for the volume.Action: Restart  NETADMIN and retry the operation. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=660 ID="BP654"142: The utility can't read volume restrictions for an object. Error code: code.NETADMINExplanation: An internal error prevented the program from getting an object's disk restrictions.Action: Restart  NETADMIN and retry the operation. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.143: The utility can't get effective rights. Error code: code.NETADMINExplanation: An internal error prevented the program from getting an object's effective rights. This error may also appear when entering the User object as a trustee and trying to view the User object's effective rights.Action: Restart  NETADMIN and retry the operation. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.144: The utility can't get the volume number. Error code: code.NETADMINExplanation: An internal error prevented the program from getting the volume number for volume information.Action: Restart  NETADMIN and retry the operation. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.145: Filename name is invalid. The operation can't be performed.NETADMINAction: Use a valid filename, and make sure the file exists and the path is correct.146: No search files are in directory name.NETADMINExplanation: No files with the .SCH extension are in the specified directory.Action: Select a new directory from a list of drive mappings by pressing <Insert>.147: No files are in directory name. Trustees can't be assigned.NETADMINExplanation: No files in the specified path to which trustees rights may be assigned.Action: Make sure the user has appropriate user access rights to assign trustees in this path. Make sure that the files exist in the path. For information about right, see "BOOK="utlrfenu" COLLECTION="nw41"NETADMIN" in Utilities Reference.PAGENUM=661 ID="BP655"148: The utility can't get or set the volume limitation information.NETADMINExplanation: Even though the User object may have had the proper Modify rights, an internal error prevented the program from setting an object's volume space limit.Action: Restart  NETADMIN and retry the operation. If the problem persists, contact your Novell Authorized Reseller.149: The utility can't get the volume restrictions. Error code: code.NETADMINExplanation: An internal error prevented the program from scanning volume disk restrictions.Action: Restart  NETADMIN and retry the operation. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.150: Object name does not exist on server name. Error code: code.NETADMINExplanation: The selected server does not have a reference to the object. This server may not be in the Directory tree, and therefore does not have a reference to the object.Action: Make sure that the selected server is a NetWare 4 server that is in the current Directory tree. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A.151: The utility can't set user volume space restrictions. Error code: code.NETADMINExplanation: Even though the User object may have the proper Modify rights, an internal error prevented the program from setting volume space restrictions for a user.Action: Restart NETADMIN and retry the operation. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.152: NetWare server name supports accounting version number. This version of NETADMIN supports accounting version number.NETADMINExplanation: NETADMIN supports version 1.0 of NetWare accounting. This server does not support the same version. The user cannot update accounting information on this server.Action: Make sure that the version of accounting is supported by this server.PAGENUM=662 ID="BP656"153: This utility cannot generate the key pair for object name. Error code: code.NETADMINExplanation: An internal error prevented the program from generating a public/private key pair for a specified object.Action: Restart  NETADMIN and retry the operation. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.154: You do not have rights to read property name.NETADMINExplanation: The User object does not have the Read right to read the property.Action: Make sure the User object has the Read right before trying to read the property. For information about assigning rights, see "BOOK="utlrfenu" COLLECTION="nw41"NETADMIN" in Utilities Reference.155: Property name does not exist. You do not have rights to create it.NETADMINExplanation: The User object does not have Supervisor rights or the Create right to create the property.Action: Make sure the user has appropriate user access rights. For information about assigning rights, see "BOOK="utlrfenu" COLLECTION="nw41"NETADMIN" in Utilities Reference.156: You do not have rights to write property name.NETADMINExplanation: The User object does not have Right rights to modify the property named in the message.Action: Before modifying the property, make sure that the User object has the Write right.157: You do not have rights to read the property name of container name.NETADMINExplanation: The User object does not have the Read right for the property of the container indicated in the message.Action:  Before reading the property of the container, make sure that the User object has the Read right.158: You do not have rights to write the property name of container name.NETADMINExplanation: You tried to modify the property named in the message of the indicated container from a User object that does not have the appropriate rights.Action: Make sure that the User object has the Write right before modifying the property of the container.PAGENUM=663 ID="BP657"159: Change password failed because the account is disabled or expired.NETADMINAction: Enable or activate the account and assign a password. The user may then change the password later.160: No physical server name was found for Volume object name.NETADMINExplanation: The Volumen object has no Host Server property.Action: Edit the Volume object and add the Host Server property. For information, see "BOOK="utlrfenu" COLLECTION="nw41"NDS and Bindery Objects and Properties" in Utilities Reference.161: No physical volume name was found for Volume object name.NETADMINExplanation: The Volumen object has no Host Resource property.Action: Edit the Volume object and add the Host Resource property. This property contains the physical name of the volume, such as volume SYS:. For information, see "BOOK="utlrfenu" COLLECTION="nw41"NDS and Bindery Objects and Properties" in Utilities Reference.170: File and directory trustees can't be selected together.NETADMINExplanation: The Object Rights property and other properties cannot be modified at the same time. The rights for the Object Rights property are different from other rights.Action: Select the Object Rights property and modify it. Then select the other properties to modify. For information, see "BOOK="utlrfenu" COLLECTION="nw41"NDS and Bindery Objects and Properties" in Utilities Reference.171: Mixed ACL types can't be selected together.NETADMINExplanation: Access control list types such as Object Rights property and other properties cannot be modified at the same time. The rights for Object Rights property are different from other rights.Action: Select Object Rights property and modify it. Then select the other properties to modify. For information, see "BOOK="utlrfenu" COLLECTION="nw41"NDS and Bindery Objects and Properties" in Utilities Reference.172: The utility can't open the Translation Table SCHEMA.XLT.NETADMINExplanation: In the DOS, MS Windows, and OS/2 environments, NETADMIN searches the following areas for the translation files:MARK=BULLETThe current directory.The load directory (the directory containing the current utility's .EXE file). This is usually the PUBLIC directory.PAGENUM=664 ID="BP658"The NLS directory that is located within the load directory (the directory containing the current utility's .EXE file). If the Unicode files are not found in the NLS directory within the load file, the program searches the NLS directory that is a sibling of the load directory (that is, at the same level as the load directory). Note: The NWLANGUAGE environment variable does not apply here.The PATH and DPATH (for OS/2 only) environment variables. These environment variables may be found either in the user's login script or in the AUTOEXEC.BAT file.Action: Make sure these files are loaded into PUBLIC and that the workstation has a search path mapped to PUBLIC; then retry the operation again. If the workstation has a search path mapped to PUBLIC and the files still cannot be found, contact your Novell Authorized Reseller.173: This object already has an Inherited Rights Filter on property name. Error code: code.NETADMINExplanation: You tried to place an Inherited Rights Filter on a property where a filter already exists.Action: Make sure that the property does not already have an Inherited Rights Filter before placing one on it. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A.174: This object already has a trustee assignment for object name on property name. Error code: code.NETADMINExplanation: You tried to assign the trustee named in the message to a property that the trustee is already assigned to.Action: Before making the assignment, make sure that the trustee is not already assigned to the property. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A.176: Masking off the Supervisor right will hide the object name. Until an object is assigned the Supervisor right to this object, this ACL modification will not be permitted.NETADMINExplanation: You tried to mask off the Supervisor right to this object. Masking off the Supervisor right to the object will hide the object from everyone, including the supervisor.Action: Create a trustee of this object that has the Supervisor right to the object. This could be the supervisor or it could be a User object. Once there is a trustee with this right,  NETADMIN can mask off the Supervisor right to this object.PAGENUM=665 ID="BP659"177: A filter ACL masks off Supervisor, and the Supervisor rights of object name is the only ACL that keeps object name visible. This ACL can't be deleted until the filter allows Supervisor or another object is assigned as Supervisor.NETADMINExplanation: You tried to delete the indicated trustee. If this trustee is deleted, no one will be able to view this object.Action: To delete this trustee, do one of the following:MARK=BULLETAssign another user as a trustee with the Supervisor right to this object.Change the Inherited Rights Filter to allow the Supervisor right to flow down.178: A filter ACL masks off Supervisor, and the Supervisor rights for object name is the only ACL that keeps object name visible. This trustee Supervisor right can't be removed until the filter allows Supervisor or another object is assigned as Supervisor.NETADMINExplanation: You tried to remove the Supervisor right for the indicated trustee. If this trustee's Supervisor right is removed, no one will be able to see this object.Action: To remove this trustee's Supervisor right, do one of the following:MARK=BULLETAssign another user as a trustee with the Supervisor right to this object.Change the Inherited Rights Filter to allow the Supervisor right to flow down.180: Physical volume name was not found on physical server name.NETADMINExplanation: The specified volume is not on the specified server. The volume may not be mounted.Action: Specify a volume that exists and is mounted on the specified server.181: The utility cannot attach to server name. There is insufficient memory available. Error code: code.NETADMINAction: See "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A.182: The utility cannot attach to the server associated with volume name. There is insufficient memory available. Error code: code.NETADMINAction: See "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A.PAGENUM=666 ID="BP660"183: The utility cannot attach to the server associated with volume name. (Connection information cannot be obtained.) Error code: code.NETADMINExplanation: An internal error prevented  NETADMIN from attaching the workstation to the server associated with the specified volume.Action: Restart  NETADMIN and retry the operation. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.185: The utility cannot attach to the server associated with volume name. (The property value cannot be obtained.) Error code: code.NETADMINExplanation: An internal error prevented  NETADMIN from attaching the workstation to the server associated with the specified volume.Action: Restart  NETADMIN and retry the operation. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.186: The utility cannot attach to server name. (Authentication cannot be completed.) Error code: code.NETADMINAction: See the explanation and action in messageIDREF="FM35288" "187: The utility cannot attach to the server associated with volume name. (Authentication cannot be completed.) Error code: code." ID="FM35288"187: The utility cannot attach to the server associated with volume name. (Authentication cannot be completed.) Error code: code.NETADMINExplanation: An internal error prevented  NETADMIN from attaching the workstation to the server associated with the specified volume.Action: Restart  NETADMIN and retry the operation. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.188: The utility cannot attach to the server associated with volume name. (A connection ID cannot be obtained.) Error code: code.NETADMINAction: See the explanation and action in messageIDREF="FM35288" "187: The utility cannot attach to the server associated with volume name. (Authentication cannot be completed.) Error code: code." PAGENUM=667 ID="BP661"189: The utility cannot attach to server name. (Connection information cannot be obtained.) Error code: code.NETADMINAction: See the explanation and action in messageIDREF="FM35288" "187: The utility cannot attach to the server associated with volume name. (Authentication cannot be completed.) Error code: code." 190: The utility cannot attach to the server associated with volume name. (The network address cannot be obtained.) Error code: code.NETADMINAction: See the explanation and action in messageIDREF="FM35288" "187: The utility cannot attach to the server associated with volume name. (Authentication cannot be completed.) Error code: code." 191: The utility cannot attach to the server name. (A connection slot cannot be obtained.) Error code: code.NETADMINAction: See the explanation and action in messageIDREF="FM35288" "187: The utility cannot attach to the server associated with volume name. (Authentication cannot be completed.) Error code: code." .192: The utility cannot attach to the server associated with volume name. (A connection slot cannot be obtained.) Error code: code.NETADMINExplanation: See the explanation and action in messageIDREF="FM35288" "187: The utility cannot attach to the server associated with volume name. (Authentication cannot be completed.) Error code: code." 193: Server name is represented by object name in the tree. You attached through object name, which object may not reflect your true rights on the server.NETADMINExplanation: The server uses the object named in the message when communicating with NetWare Directory Services. Another Server object that represents the same server was created. If you tried to add trustees to the unofficial server, the physical server will not acknowledge the trustees of the unofficial Server object.Action: Delete the unofficial Server object. To refer to a server in another context, create an alias of the original server.197: The password was not changed. Error code: code.NETADMINExplanation: The attempt to change the password was unsuccessful.Action: Retry the operation. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=668 ID="BP662"200: You do not have rights to modify field name. Press <F1> for more information.NETADMINExplanation: The User object needs the Modify right to change the indicated field.Action: Obtain the Modify right.202: Object name of class type type has subordinates in the Directory tree and can't be renamed.NETADMINExplanation: You tried to rename a container object (Organization, Organizational Unit, Country) that has other objects in it. A container object cannot be renamed if it contains other objects. For information, see "BOOK="cncptenu" COLLECTION="nw41"Object" in Concepts.Action: Do not rename a container object if it has other objects in it. If you must rename the container object, delete the objects in it; then rename the container object.203: The utility can't write the script file information. Error code: code. EINVAL: (invalid value for origin, or position specified by offset is before the beginning of the file).NETADMINExplanation: The script file could not be written.Action: Retry the operation. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.204: The utility can't write the script file information. Error code: code. EBADF: (invalid file handle).NETADMINExplanation: The script file could not be written.Action: Retry the operation. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.205: This utility cannot get your rights for all of the properties on this screen. Error code: code.NETADMINExplanation: The User object's rights to all of the properties that will be displayed on the screen cannot be retrieved.Action: Retry the operation. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=669 ID="BP663"206: The utility can't get the network address of NCP Server name. You can't add this server as an object. Error code: code.NETADMINExplanation: The utility cannot attach to the specified server to get its address. Because the workstation cannot attach to the specified server, the user cannot add it as an object.Action: Make sure the server is operating. Make sure the user has appropriate user access rights to attach to the specified server. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A.207: This utility can't synchronize your password on the servers to which you are attached. Error code: code.NETADMINExplanation: The utility failed to synchronize the passwords on others servers to which the workstation is attached.Action: Use SETPASS to change the passwords on other bindery servers. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A.208: This utility can't synchronize your passwords on the other servers to which you are attached. Your machine does not have enough free memory to perform this action.NETADMINExplanation: The workstation did not have enough memory to create the list of servers. The password was not changed on the other servers to which the workstation is attached.Action: Increase the available memory. Retry the operation. (See "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network.) You may also change the passwords on the other bindery servers using SETPASS.212: This utility cannot attach to server name. Error code: code.NETADMINExplanation: The utility cannot attach to the specified server.Action: Make sure the server is operating. Make sure the user has appropriate user access rights to attach to the server. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A.213: The utility cannot attach to server name. (Cannot get connection status.) Error code: code.NETADMINExplanation: The utility cannot attach to the specified server.Action: Make sure the server is operating. Make sure the user has appropriate user access rights to attach to the server. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A.PAGENUM=670 ID="BP664"214: The utility cannot write the script file information. There is no space on the drive. Error code: code.NETADMINExplanation: More space on the volume SYS: is required to write out the script file.Action: Free up some additional space on the volume SYS: and retry the operation. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A .215: Not enought memory to modify the mailbox location. Mailbox location: location Mailbox ID: numberNETADMINExplanation: The user's workstation ran out of memory while trying to modify the mailbox location.Action: Modify the user's workstation memory use to increase the largest executable program size (display by using MEM command from the DOS prompt). If modifying mailbox locations for a large list of users, try modifying a smaller list.216: Mailbox location not changed. Messaging server name does not have a database location property.NETADMINExplanation: The Messaging Server object does not have a database location specified. This i s found in the Message Server Identification Screen; however it is not editable. The NetWare MHS install NLM should have inserted the location in this screen.Action: Reinstall NetWare MHS at the server console.907: The name file can't be found.NETADMINAction: See the message in IDREF="FM48610""907: This utility cannot open the translation table SCHEMA.XLT." in Appendix C.908: The name file is an incorrect format and can't be used.NETADMINAction: See the message in IDREF="FM51165""908: The specified path is invalid." in Appendix C.909: The name file is an incorrect version. Version number is required.NETADMINAction: See the message IDREF="FM28663""909: You are not mapped to the specified drive." in Appendix C.920: This utility was unable to allocate <number> bytes of memory.NETADMINAction: See the action in message IDREF="FM30331""920: This utility was unable to allocate number bytes of memory." in Appendix C.PAGENUM=671 ID="BP665"970: The attempt to open the Unicode table files failed.NETADMINAction: See the action in message IDREF="FM15675""970: The attempt to open the Unicode table files failed." in Appendix C.971: The workstation does not have enough memory to load the Unicode table files.NETADMINAction: See the action in message IDREF="FM55341""971: The workstation does not have enough memory to load the Unicode table files." in Appendix C.972: Access to the Unicode table files was denied.NETADMINAction: See the action in message IDREF="FM90152""972: Access to the Unicode table files was denied." in Appendix C.973: The Unicode table files (for code page number and country id number) can't be found in the NLS dirctory or in the search drives.NETADMINAction: See the action in message IDREF="FM62778""973: The Unicode table files cannot be found in the NLS directory or in the search path. Code page: number Country: number" in Appendix C.974: The Unicode table files have been corrupted.NETADMINAction: See the action in message IDREF="FM63405""974: The Unicode table files are corrupt." in Appendix C.975: The Unicode table files can't be opened because there are already too many open files. Close some files or modify your CONFIG.SYS file to allow more open files.NETADMINAction: See the action in message IDREF="FM49793""975: The Unicode table files cannot be opened because there are already too many open files. Close some files or modify your CONFIG.SYS file." in Appendix C.991: An error occurred explanation Error code: code.NETADMINAction: See the action in message IDREF="FM92553""991: An error occurred in function_name. Error code: code." in Appendix C.998: The message file found (<utility_name>.MSG) is an incorrect version. The correct version is <number>. See your network supervisor for assistance.NETADMINAction: See the action in message IDREF="FM91957""998: The message file found (utility_name.MSG) is an incorrect version. The correct version is number. See your network supervisor for assistance." in Appendix C.PAGENUM=672 ID="BP666"999: This utility can't find the message file name.NETADMINAction: See the action in message IDREF="FM69424""999: The message file for this utility cannot be found." in Appendix C.PAGENUM=673 ID="BP667"NETSYNC1: Unable to initiate new process.NETSYNCExplanation: This message appears on NetWare 3 and NetWare 4 servers. It usually indicates a NetWare operating system error or a server that is out of memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.2: Unable to get NCP Extension Information from remote server.NETSYNCExplanation: This message appears on NetWare 3 servers. It usually indicates that a remote NetWare 4 server does not have the NETSYNC4.NLM file loaded.Action: Load the NETSYNC4.NLM file on the remote server first, then do the operation again.3: Unable to get Internetwork Address of local server.NETSYNCExplanation: This message can appear on a NetWare 3 server, but this is an operating system error that should never occur.Action: Do the operation again. If the problem persists, contact your Novell Authorized Reseller.4: Unable to create screen for NetSync.NETSYNCExplanation: This message appears on NetWare 3 and NetWare 4 servers. It usually indicates that an NWSNUT call failed, which indicates that a server is out of memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.5: Unable to create or change to NetSync directory.NETSYNCExplanation: This message appears on NetWare 3 and NetWare 4 servers. It usually indicates that NWSNUT call failed, which indicates that a server is out of memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.6: Unable to authenticate to remote server.NETSYNCPAGENUM=674 ID="BP668"Explanation: This message appears on NetWare 3 servers. It usually indicates that an attempt to do mutual authentication of the two servers failed. Either the NetWare 4 server didn't recognize this server as valid for attaching for NetSync purposes, or this (NetWare 3) server was unable to verify the NetWare 4 server password that was returned (a possible security problem).Action: A possible solution would be to reauthorize a NetWare 3 server on a NetWare 4 server validation screen and do the operation again. Note: If this occurs, respecify the remote server information (server to attach to, password for attach) after reauthorizing on the NetWare 4 server.7: This server is not authorized to attach to the remote server.NETSYNCExplanation: This NetWare 3 server is not in the list of authorized servers on the indicated NetWare 4 server.Action: Reauthorize NetWare 3 server on the NetWare 4 server validation screen and do the operation again. Note: If this error occurs, respecify the remote server information (that is, the server to attach to and the password for the attach) after reauthorizing on the NetWare 4 server.8: Unable to open IPX socket for remote communication.NETSYNCExplanation: A NetWare operating system call failed or that a server is out of memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.9: The password doesn't match the ID returned.NETSYNCExplanation: This message appears on NetWare 3 servers. It usually indicates that the remote NetWare 4 server returned an ID for this server that did not match the saved ID, making the saved password invalid.Action: Reauthorize NetWare 3 server on 4.x server validation screen and do the operation again. Note: If this occurs, respecify the remote server information (server to attach to, password for attach) after re-authorizing on the NetWare 4 server.10: Unable to register NCP Extension.NETSYNCExplanation: A NetWare operating system failure occurred. The server may not have enough available memory..Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.11: Unable to allocate NWSNut Resource Tag.NETSYNCExplanation: A NetWare operating system call failed or the server is out of memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.PAGENUM=675 ID="BP669"12: Unable to allocate a Semaphore.NETSYNCExplanation: A NetWare operating system call failed or the server is out of memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.13: Unable to send an NCP extension packet.NETSYNCExplanation: A NetWare operating system call failed or the server is out of memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.PAGENUM=676 ID="BP670"NETUSER100: An unknown error has prevented NETUSER from capturing to print_queue.NETUSERExplanation: An internal error has occurred in the program. Possible causes of the error are an invalid connection or queue ID or a malfunctioning requester. An error message originated by the CAPTURE utility will probably accompany this error message.Action: Refer to the accompanying message for additional information. Reboot the workstation, then run CAPTURE again. See if other workstations have the same problem. If so, re-create the queue. If not, reinstall the VLMs. If the problem persists, contact your Novell Authorized Reseller.101: NETUSER cannot add the script property. Error code: code.NETUSERExplanation: An internal system error was reported by the NWDSModifyObject function.Action: Restart NETUSER and do the operation again. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.102: The utility cannot open the script file. Error code: code.NETUSERExplanation: An internal system error was reported by the NWDSOpenStream function.Action: Restart NETUSER and do the operation again. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.103: The utility cannot read the login script for object name. Error code: code.NETUSERExplanation: An internal DOS call to read the login script file failed.Action: Restart NETUSER and do the operation again. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.104: The utility cannot write the script file information. Error code: code.NETUSERExplanation: An internal system error prevented the program from writing information to the login script file.Action: Restart NETUSER and do the operation again. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=677 ID="BP671"105: The utility cannot write the script file information. Error code: code, EBADF.NETUSERExplanation: An internal system error prevented the program from writing information to the login script file.Action: Do the operation again. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.106: The utility cannot write the script file information. Error code: code, EINVAL.NETUSERExplanation: An internal system error prevented the program from writing information to the login script file.Action: Do the operation again. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.107: The utility cannot write the script file information. There is no space on the drive. Error code: code.NETUSERExplanation: There is no room on volume SYS: to write the login script file.Action: Free up disk space on volume SYS: and do the operation again. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A.907: This utility cannot open the translation table SCHEMA.XLT.NETUSERAction: See message IDREF="FM48610""907: This utility cannot open the translation table SCHEMA.XLT." in Appendix C.970: The attempt to open the Unicode table files failed.NETUSERAction: See message IDREF="FM15675""970: The attempt to open the Unicode table files failed." in Appendix C.971: The workstation does not have enough memory to load the Unicode table files.NETUSERAction: See message IDREF="FM55341""971: The workstation does not have enough memory to load the Unicode table files." in Appendix C.972: Access to the Unicode table files was denied.NETUSERAction: See message IDREF="FM90152""972: Access to the Unicode table files was denied." in Appendix C.973: The Unicode table files cannot be found in the NLS directory or in the search path. Code page: <number>  Country:  <number>NETUSERAction: See message IDREF="FM62778""973: The Unicode table files cannot be found in the NLS directory or in the search path. Code page: number Country: number" in Appendix C.PAGENUM=678 ID="BP672"974: The Unicode table files are corrupt.NETUSERAction: See message IDREF="FM63405""974: The Unicode table files are corrupt." in Appendix C.975: The Unicode table files cannot be opened because there are already too many open files. Close some files or modify your CONFIG.SYS file.NETUSERAction: See message IDREF="FM49793""975: The Unicode table files cannot be opened because there are already too many open files. Close some files or modify your CONFIG.SYS file." in Appendix C.991: An error occurred in <function_name>. Error code: <code>.NETUSERAction: See message IDREF="FM92553""991: An error occurred in function_name. Error code: code." in Appendix C.998: The message file found (<utility_name>.MSG) is an incorrect version. The correct version is <number>. See your network supervisor for assistance.NETUSERAction: See message IDREF="FM91957""998: The message file found (utility_name.MSG) is an incorrect version. The correct version is number. See your network supervisor for assistance." in Appendix C.999: The message file for this utility cannot be found.NETUSERAction: See message IDREF="FM69424""999: The message file for this utility cannot be found." in Appendix C.PAGENUM=679 ID="BP673"NETX1: The message file name is invalid. The program cannot be loaded.NETXExplanation: The .MSG file is invalid. This problem could be the result of a corrupted file, a bad translation, or an outdated file version.Action: Either update the .MSG file with a valid copy or delete the file. The DOS Requester will use the default messages that are bound to the binary files.5: Module1.VLM is not loaded. The module2.VLM file cannot be loaded before module1.VLM. Load the module1.VLM file first; then try to load the module2.VLM file.NETXExplanation: The module2.VLM requires that the module1.VLM be loaded first. Either the current configuration has module1.VLM and module2.VLM loading out of order, or module1.VLM did not load successfully.Action: Make sure that module1.VLM is configured to load before module2.VLM. To do this, change the load order of the "VLM=" parameter in the NET.CFG file.7: In order to load the module3.VLM, one of the following VLMs must be loaded: module1.VLM, module2.VLM.NETXExplanation: The module3.VLM requires that module1.VLM or module2.VLM be loaded first. Either the current configuration has module3.VLM loading before the modules in the module1.VLM or module2.VLM list, or, module1.VLM or module2.VLM did not load successfully.Action: Make sure that module1.VLM or module2.VLM load successfully before loading module3.VLM.42: There is a missing or invalid value for `parameter' on line number of the configuration file. This entry will be ignored. Correct the line specified in the configuration file before continuing.NETXExplanation: The configuration file contains a configuration keyword that has an invalid parameter, or that does not specify a parameter. This invalid line will be ignored by the configuration process.Action: Because this line will be ignored, no action is required now. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message.PAGENUM=680 ID="BP674"43: There is a missing or invalid ON/OFF value for `parameter' on line number of the configuration file. This entry will be ignored. Correct the line specified in the configuration file before continuing.NETXExplanation: The configuration file contains a configuration keyword that is defined to use either an "ON" or "OFF" parameter, but a different parameter, or no parameter, or () has been specified. This invalid line will be ignored by the configuration process.Action: Because this line will be ignored, no action is required now. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message.45: The parameter specified for the following option was out of range and has been adjusted.NETXExplanation: A configurable parameter has been configured too high or too low to be valid. The invalid parameter is specified on the line following the message.Action: Check and correct the parameter specified in the NET.CFG file. For information on the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.57: DOS is only configured for number drives, NETX.VLM requires 26 drives for full functionality. The NETX.VLM file will load with partial support. Add LASTDRIVE=Z to the CONFIG.SYS file and reboot the workstation; then load the NETX.VLM file.NETXExplanation: This message is only a warning. For full NetWare shell compatibility the LASTDRIVE parameter in the CONFIG.SYS file must be set to Z. Otherwise problems will occur when mapping drives, etc.Action: Add "LASTDRIVE=Z" to the CONFIG.SYS file; then reboot the workstation before loading the DOS Requester.58: The PRINT.VLM file has not been loaded. The NETX.VLM file will load successfully without print services. To enable printing services, load the PRINT.VLM file before loading the NETX.VLM file.NETXExplanation: This message is only a warning. For full NetWare shell compatibility the PRINT.VLM file must be loaded. Otherwise, problems will arise when using pre-4.0 NetWare print utilities.Action: If print functionality is desired, load the PRINT.VLM before loading NETX.VLM.PAGENUM=681 ID="BP675"NLIST001: The property name is too long.NLISTExplanation: If the property name is more than 65 characters long, this error message will appear.Action: Make sure that the property name is spelled correctly and that it is not longer than 65 characters. For a list of valid property names for every object type, see "BOOK="utlrfenu" COLLECTION="nw41"NDS and Bindery Objects and Properties" in Utilities Reference. Use exact property names for NLIST to work properly.010: Property property does not exist. For help, type NLIST /?.NLISTExplanation: You entered an invalid property name, or you typed the property name incorrectly. (If the property name is not the same as one of the properties listed in Utilities Reference, this error message will appear.)Action: Make sure that the property name is valid and typed correctly. For a list of valid property names for every object type, see "BOOK="utlrfenu" COLLECTION="nw41"NDS and Bindery Objects and Properties" in Utilities Reference. If the property name consists of two or more words, with a space between the words, the property name should be enclosed by double quotation marks. For example, the property Facsimile Telephone Number should be used this way: "Facsimile Telephone Number."030: The property value is too long. For help, type NLIST /?.NLISTExplanation: If the property value is more than 80 characters, this error message will appear.Action: Make sure that the property value is no longer than 80 characters. Type "NLIST /? MOREINFO="NONE"<Enter>" to access online help, or for information about property value syntax, see "BOOK="utlrfenu" COLLECTION="nw41"NDS and Bindery Objects and Properties" in Utilities Reference. If the property value syntax is Boolean, use "Yes" or "No" only. If the property value syntax is an integer, use numbers only.040: An incorrect context has been entered: incorrect_context. For help, type NLIST /?.NLISTExplanation: The context following /CO is not valid.Action: Use the CX /TR command to make sure the context exists and is correct.PAGENUM=682 ID="BP676"050: An error prevented the bindery from being read.NLISTExplanation: An error occurred when the program tried to read the information about a property from the bindery.Action: Make sure bindery services is loaded, and that the bindery context is set on the NetWare 4 server.060: The Where property must be given a value of Yes or No. For help, type NLIST /?.NLISTExplanation: If any value other than "Yes" or "No" is given to this property, this error message will appear.Action: Use "Yes" or "No" for this property value.074: This utility cannot build the search filter.NLISTExplanation: An internal application error has occurred.Action: Retry the utility. If the problem persists, contact your Novell Authorized Reseller.075: This utility cannot create a context.NLISTExplanation: The application is unable to create a context.Action: Retry the utility. If the problem persists, contact your Novell Authorized Reseller.080: Available memory is insufficient to scan all levels.NLISTAction: See "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network.082: The program cannot set the context to: new_contextNLISTExplanation: The utility cannot set the context.Action: Use the CX command to see where in the Directory tree the new context exists, or use the CX /TR command to see if the new context exists. Also, make sure the "NAME CONTEXT" in NET.CFG file is correct.090: The class name is too long. For help, type NLIST /?.NLISTExplanation: If the class name is longer than 256 characters, this error message will appear.Action: Make sure that the class name is spelled correctly, and that it is no longer than 256 characters. If the class name includes a space between words, be sure to place double quotes around the name. (For a list of valid class names, see "BOOK="utlrfenu" COLLECTION="nw41"NDS and Bindery Objects and Properties" in Utilities Reference.) If the class name is two or more words with a space between the words, the property name should be enclosed by double quotation marks.PAGENUM=683 ID="BP677"100: The class type is too long. For help, type NLIST /?.NLISTExplanation: If the class type is longer than 65 characters, this error message will appear.Action: Use a valid class type (no longer than 65 characters). For a list of valid class names, see "BOOK="utlrfenu" COLLECTION="nw41"NDS and Bindery Objects and Properties" in Utilities Reference. If the class name is two or more words with a space between the words, the property name should be enclosed by double quotation marks.110: The context is too long. For help, type NLIST /?.NLISTExplanation: If the context length is longer than 513 characters, this error message will appear.Action: Change context to the desired length, one character at a time, until it reaches an acceptable length.120: Control characters were found in the command line. For help, type NLIST /?.NLISTExplanation: This error message will appear if any control characters (for example, MOREINFO="NONE"<Ctrl>+<C>) are found in the command line.Action: Remove the control characters from the command line, then try the operation again.130: Dates prior to 1980 are invalid. For help, type NLIST /?.NLISTExplanation: You entered a date that is prior to 1980.Action: Enter a date after January 1, 1980.140: Only an Equals or Not-equals operator is valid for strings. For help, type NLIST /?.NLISTExplanation: When the property value has a string syntax, no operator other than an "Equal" or "NEqual" can be used.Action: Use the "Equal" or "NEqual" operator for properties that have a string syntax.150: Only an Equals operator can be entered for Yes/No properties. For help, type NLIST /?.NLISTExplanation: When the property value is "Yes" or "No," no operator other than "Equal" can be used.Action: Use the "Equal" operator for properties that have a "Yes" or "No" syntax.PAGENUM=684 ID="BP678"170: A hexadecimal value (0-9, a-f) must be entered for the Where property value. For help, type NLIST /?.NLISTExplanation: A non-hexadecimal value was entered for a property which needed a hexadecimal value.Action: Enter a hexadecimal value (0 through 9, and a through f) for the property.180: An integer value must be entered for the Where parameter. For help, type NLIST /?.NLISTExplanation: A nondecimal value was entered for a property that needed a decimal value.Action: Make sure the number is a decimal value.190: The comparison requested is not supported by the Where parameter. For help, type NLIST /?.NLISTExplanation: The utility returned an error while trying to interpret the comparison.Action: Type "NLIST /? MOREINFO="NONE"<Enter>" to verify that the command was entered correctly.210: An invalid context has been entered. For help, type NLIST /?.NLISTExplanation: You entered a context that does not exist.Action: Use the CX command to see where in the Directory tree you are located; then use the CX /TR command to see if the desired context exists.220: An invalid date was entered with the Where parameter. For help, type NLIST /?.NLISTExplanation: An invalid date has been entered.Action: Enter a date after January 1, 1980 and type the date correctly.230: You have entered the name of a server to which you are not attached. For help, type NLIST /?.NLISTExplanation: The workstation is not attached to the server from which you tried to get information.Action: Make sure the workstation is connected to the needed server.240: An invalid Show property has been entered. For help, type NLIST /?.NLISTExplanation: The property name has been entered incorrectly, or the property name does not exist. (If the property name is not the same as one of the properties listed in Utilities Reference, this error message will appear.)PAGENUM=685Action: Make sure the property name is valid and spelled correctly. For a list of valid property names for every object type, see "BOOK="utlrfenu" COLLECTION="nw41"NDS and Bindery Objects and Properties" in Utilities Reference. If the property name is two or more words with a space between the words, the property name should be enclosed by double quotation marks. For example, the property Facsimile Telephone Number should be used this way: "Facsimile Telephone Number."250: An invalid Where property name has been entered. For help, type NLIST /?.NLISTExplanation: The property name has been entered incorrectly, or the property name does not exist. (If the property name is not the same as one of the properties listed in Utilities Reference, this error message will appear.)Action: Make sure the property name is valid and spelled correctly. For a list of valid property names for every object type, see "BOOK="utlrfenu" COLLECTION="nw41"NDS and Bindery Objects and Properties" in Utilities Reference. If the property name is two or more words with a space between the words, the property name should be enclosed by double quotation marks. For example, the property Facsimile Telephone Number should be used this way: "Facsimile Telephone Number."260: You are not attached to a server.NLISTExplanation: If you tried to use NLIST in the bindery mode before logging in to a server, this error message will appear.Action: Log in to the desired server; then try the operation again.270: Available memory is insufficient to complete the process.NLISTAction: See "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network.280: The Where option contains an invalid property. For help, type NLIST /?.NLISTExplanation: An invalid property name is used in the command line.Action: Make sure the property name is valid and spelled correctly. For a list of valid property names for every object type, see "BOOK="utlrfenu" COLLECTION="nw41"NDS and Bindery Objects and Properties" in Utilities Reference. If the property name is two or more words with a space between the words, the property name should be enclosed by double quotation marks. For example, the property Facsimile Telephone Number should be used this way: "Facsimile Telephone Number."290: Class name does not exist. For help, type NLIST /?.NLISTExplanation: A class name was entered incorrectly, or the class name is invalid.Action: Enter the class name correctly, and make sure that it is a valid class name. For a list of valid class names, see "BOOK="utlrfenu" COLLECTION="nw41"NDS and Bindery Objects and Properties" in Utilities Reference. If the class name is two or more words with a space between the words, the property name should be enclosed by double quotation marks.PAGENUM=686 ID="BP680"300: Wildcard characters (*, ?) are not permitted in property names. For help, type NLIST /?.NLISTExplanation: A wildcard was used in the command line in place of a property name.Action: Make sure the property name is valid and spelled correctly.. For a list of valid property names for every object type, see "BOOK="utlrfenu" COLLECTION="nw41"NDS and Bindery Objects and Properties" in Utilities Reference. If the property name is two or more words with a space between the words, the property name should be enclosed by double quotation marks. For example, the property Facsimile Telephone Number should be used this way: "Facsimile Telephone Number."310: Wildcard characters are not permitted in the class type. For help, type NLIST /?.NLISTExplanation: A wildcard was used in the bindery class type.Action: Enter a valid class type, and spell the class type correctly. For a list of valid class names, see "BOOK="utlrfenu" COLLECTION="nw41"NDS and Bindery Objects and Properties" in Utilities Reference. If the class name is two or more words with a space between the words, the property name should be enclosed by double quotation marks.350: The stream file for object: object property: property cannot be opened.NLISTExplanation: The stream file for the specified object cannot be opened.Action: Check NetWare Directory Services to find out why NWDSOpenStream() was not successful; then try the operation again. If the problem persists, contact your Novell Authorized Reseller.360: The translation file (SCHEMA.XLT) cannot be opened.NLISTAction: See message IDREF="FM48610""907: This utility cannot open the translation table SCHEMA.XLT." in Appendix C.480: Use only one of the following options: Show, /Detailed, or /Name. For help, type NLIST /?.NLISTExplanation: An attempt was make to use more than one of the following options: SHOW, /D, or /N.Action: Use the SHOW, /D, or /N options separately; then try the operation again.485: The stream file cannot be read.NLISTExplanation: The stream file for the specified object cannot be opened.Action: Check with NetWare Directory Services to find out why NWDSOpenStream() was not successful; then try the operation again. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=687 ID="BP681"490: The specified server name is too long. For help, type NLIST /?.NLISTExplanation: You entered a server name that exceeds 47 characters.Action: Type the server name correctly, and make sure that the server name does not exceed 47 characters.500: More attributes have been entered than can be shown. For help, type NLIST /?.NLISTExplanation: The maximum number of attributes (or properties) that can be shown is 25.Action: Do not enter more than 25 attributes (or properties) at one time.510: An error has occured when scanning for directory trees. Error: codeNLISTExplanation: The utility cannot find an NDS tree.Action: Check NDS and try again. If the problem persists, contact your Novell Authorized Reseller.520: An invalid object name name has been entered.NLISTAction: Check the spelling of the object name and try again. If the problem persists, contact your Novell Authorized Reseller.702: An error occurred attempting to read a print job configuration. Error: codeNLISTExplanation: The print job configuration could not be read.Action: Check NDS to verify the correct print job configuration.703:An error occurred attempting to read the job record for owner owner, job name name. Error: codeNLISTExplanation: The utility could not read the job record.Action: Make sure your command line syntax is correct and try the operation again. If the problem persists, contact your Novell Authorized Reseller.899: An internal application error occurred. Error: codeNLISTExplanation: An internal error occurred.Action: Try the operation again. If the problem persists, contact your Novell Authorized Reseller.903: The command line syntax is invalid.NLISTAction: See message IDREF="FM18860""903: The command line syntax is invalid." in Appendix C.PAGENUM=688 ID="BP682"907: This utility cannot open the translation table SCHEMA.XLT.NLISTAction: See message IDREF="FM48610""907: This utility cannot open the translation table SCHEMA.XLT." in Appendix C.908: The specified path is invalid.NLISTAction: See message IDREF="FM51165""908: The specified path is invalid." in Appendix C.909: You are not mapped to the specified drive.NLISTAction: See message IDREF="FM28663""909: You are not mapped to the specified drive." in Appendix C.925: The server specified is a Personal NetWare server. You cannot attach to a Personal NetWare server with this utility. Use the Personal NetWare utilities to access this connection.NLISTAction: See message IDREF="FM67645""925: The server specified is a Personal NetWare server. You cannot attach to a Personal NetWare server with this utility. Use the Personal NetWare utilities to access this connection." in Appendix C.970: The utility cannot open the Unicode table files. It cannot proceed without them.NLISTAction: See message IDREF="FM15675""970: The attempt to open the Unicode table files failed." in Appendix C.971: The workstation does not have enough memory to load the Unicode table files.NLISTAction: See message IDREF="FM55341""971: The workstation does not have enough memory to load the Unicode table files." in Appendix C.972: Access to the Unicode table files was denied.NLISTAction: See message IDREF="FM90152""972: Access to the Unicode table files was denied." in Appendix C.973: The Unicode table files cannot be found in the NLS directory or in the search path. Code page: <number>  Country:  <number>NLISTAction: See message IDREF="FM62778""973: The Unicode table files cannot be found in the NLS directory or in the search path. Code page: number Country: number" in Appendix C.974: The Unicode table files are corrupt.NLISTAction: See message IDREF="FM63405""974: The Unicode table files are corrupt." in Appendix C.PAGENUM=689 ID="BP683"975: The Unicode table files cannot be opened because there are already too many open files. Close some files or modify your CONFIG.SYS file.NLISTAction: See message IDREF="FM15675""970: The attempt to open the Unicode table files failed." in Appendix C.991: An error occurred in <function_name>. Error code: <code>.NLISTAction: See message IDREF="FM92553""991: An error occurred in function_name. Error code: code." in Appendix C.998: The message file found (<utility_name>.MSG) is an incorrect version. The correct version is <number>. See your network supervisor for assistance.NLISTAction: See message IDREF="FM91957""998: The message file found (utility_name.MSG) is an incorrect version. The correct version is number. See your network supervisor for assistance." in Appendix C.999: The message file for this utility cannot be found.NLISTAction: See message IDREF="FM69424""999: The message file for this utility cannot be found." in Appendix C.PAGENUM=690 ID="BP684"NMENU003: Display program name cannot be found.NMENUExplanation: This file is necessary for the NMENU utility to execute. It should be located in the PUBLIC directory. It may have been deleted, or the workstation mappings may be incorrect.Action: Make sure that the workstation mappings are correct. If they are, use NWXTRACT to get a copy of MENU.OVL from the original CD-ROM or NetWare diskettes.004: EXEC file format error.NMENUExplanation: The program has an internal error.Action: Retry the operation. If the problem persists, contact your Novell Authorized Reseller.005: Insufficient memory.NMENUExplanation: The workstation may not have enough available memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network.006: Cannot create execution file name.NMENUExplanation: The User object may not have rights to create this file, or the workstation may not have enough disk space.Action: Make sure the user has appropriate user access rights. Increase the available disk space at the workstation. See "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Disk Space Problems" in Supervising the NetworkID="FM96147"008: Cannot create temporary file name.NMENUExplanation: Some possible causes for this error are the following:MARK=BULLETThe environment variables may not have been set properly when creating the directory. NMENU could not determine where to put the directory.The User object does not have rights to create a directory in the specified area.Action: To create the directory to hold temporary files on the network, use FILER or the DOS MD command. Make sure the user has appropriate user access rights. Make sure that the environment variables are properly set. Then retry the operation. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=691 ID="BP685"009: Cannot create temporary file name.NMENUAction: See message IDREF="FM96147" "008: Cannot create temporary file name." in this section.010: Menu must be started using NMENU.BAT.NMENUExplanation: "MENU" instead of "NMENU" may have been typed when starting this utility.Action: To start the utility, type NMENU.011: Cannot create temporary file name.NMENUAction: See message IDREF="FM96147" "008: Cannot create temporary file name." in this section.012: COMMAND.COM cannot be located using COMSPEC setting.NMENUExplanation: The current command processor is not supported by this utility.Action: Make sure the processor is supported by NMENU.013: Menu is already resident.NMENUExplanation: The NMENU utility is already running.Action: None. This message is for information only.018: Batch command tail is too long.NMENUExplanation: The workstation COMSPEC setting exceeds the DOS limit of 128 characters.Action: Change the workstation COMSPEC setting so that it does not exceed 128 characters.019: You must specify a menu filename.NMENUExplanation: "NMENU" was typed without a file name.Action: Type "NMENU filename."105: Data file processing has stopped in Menu #number because data file name is corrupted.NMENUExplanation: The menu file is corrupted.Action: Delete the corrupted file and recreate it.115: Menu number does not exist in data file name.NMENUExplanation: A menu number was called that was not created. This message can only occur during a call to a submenu from the main menu.Action: Call a menu number that exists.PAGENUM=692 ID="BP686"120: DATGetMenu ran out of memory while searching for Menu #number in data file name.NMENUExplanation: The workstation may not have enough available memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network.125: The program ran out of memory while DATGetNextCommand was attempting to parse the data file.NMENUExplanation: The workstation may not have enough available memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network.130: The program has failed because the workstation ran out of memory while reading menu items from the data file.NMENUExplanation: The workstation may not have enough available memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network.140: Initialization has failed. MENU cannot communicate with engine interrupt.NMENUExplanation: MENUEXE.EXE and MENU.OVL are incompatible versions.Action: Use the most current versions of each of these files. Note: MENU.EXE came with the NetWare 3 and NetWare 2.Do not confuse the MENU.EXE file that came with the NetWare 3 and NetWare 2 with the MENUEXE.EXE file from NMENU.)150: You are attempting to use too many menu levels at the same time on the display. Menus which cascade to this depth are difficult to use and should be redesigned. Please consult the Supervising the Network manual for hints on good menu design.NMENUExplanation: Programs have a maximum of 11 menus levels (one main menu and 10 submenus). You have reached 11 menu levels.Action: Limit the number of menu levels to 11.155: You have too many menus.NMENUExplanation: Programs can contain no more than 255 menu screens. This program has reached 256 menu screens.Action: Reduce the total number of menus screens in this program below 256.PAGENUM=693 ID="BP687"500: An unidentified error has occurred.  Error code=numberNMENUExplanation: An unexpected error occurred. No other information is available.Action: Try the operation again. If the problem persists, contact your Novell Authorized Reseller. 991: An error occurred in <function_name>. Error code: <code>.NMENUAction: See message IDREF="FM92553""991: An error occurred in function_name. Error code: code." in Appendix C.998: The message file found (<utility_name>.MSG) is an incorrect version. The correct version is <number>. See your network supervisor for assistance.NMENUAction: See message IDREF="FM91957""998: The message file found (utility_name.MSG) is an incorrect version. The correct version is number. See your network supervisor for assistance." in Appendix C.999: The message file for this utility cannot be found.NMENUAction: See message IDREF="FM69424""999: The message file for this utility cannot be found." in Appendix C.PAGENUM=694 ID="BP688"NMR1: The message file name is invalid. The program cannot be loaded.NMRExplanation: The .MSG file is invalid. This problem could be the result of a corrupted file, a bad translation, or an outdated file version.Action: Either update the .MSG file with a valid copy or delete the file. The DOS Requester will use the default messages that are bound to the binary files.5: Module1.VLM is not loaded. The module2.VLM file cannot be loaded before module1.VLM. Load the module1.VLM file first; then try to load the module2.VLM file.NMRExplanation: The module2.VLM requires that the module1.VLM be loaded first. Either the current configuration has module1.VLM and module2.VLM loading out of order, or module1.VLM did not load successfully.Action: Make sure that module1.VLM is configured to load before module2.VLM. To do this, change the load order of the "VLM=" parameter in the NET.CFG file.7: In order to load the module3.VLM, one of the following VLMs must be loaded: module1.VLM, module2.VLM.NMRExplanation: The module3.VLM requires that module1.VLM or module2.VLM be first. Either the current configuration has module3.VLM loading before the modules in the module1.VLM or module2.VLM list, or module1.VLM or module2.VLM did not load successfully.Action: Make sure that module1.VLM or module2.VLM load successfully before module3.VLM.42: There is a missing or invalid value for `parameter' on line number of the configuration file. This entry will be ignored. Correct the line specified in the configuration file before continuing.NMRExplanation: The configuration file contains a configuration keyword that has an invalid parameter or that does not specify a parameter. This invalid line will be ignored by the configuration process.Action: Because this line will be ignored, no action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message.PAGENUM=695 ID="BP689"43: There is a missing or invalid ON/OFF value for `parameter' on line number of the configuration file. This entry will be ignored. Correct the line specified in the configuration file before continuing.NMRExplanation: The configuration file contains a configuration keyword that is defined to use either an "ON" or "OFF" parameter, but a different parameter, or no parameter, has been specified. This invalid line will be ignored by the configuration process.Action: Because this line will be ignored, no action is required now. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message.45: The parameter specified for the following option was out of range and has been adjusted.NMRExplanation: A configurable parameter has been configured too high or too low to be valid. The parameter is specified on the line following the message.Action: Check and correct the parameter specified in the NET.CFG file. For information on the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.PAGENUM=696 ID="BP690"NPATH015: This utility was unable to open filename.NPATHExplanation: NetWare tried to open the indicated file to read the version number and language of the file. The file may have been deleted, so that it is not in the search sequence, or the User object might not have rights to read the file.Action: Use a utility like NDIR to find out if the file exists on the network. If the file cannot be located, use NWXTRACT to get the file from diskette or CD. If the file is on the network, make sure the file has Read rights. For information on NetWare's search sequence, see  "BOOK="cncptenu" COLLECTION="nw41"Search algorithm" in Concepts.020: This utility was unable to get the current working directory path.NPATHExplanation: An unexpected error has prevented NPATH from locating the current directory path. The workstation may have lost the search drive mapping due to a server error.Action: Remap a search drive to your current path and run NPATH again.025: Filename is an invalid filename.NPATHExplanation: The filename was mistyped, more than eight characters were used in the root of the filename, or more than three characters were used in the filename's extension.Action: Type the filename correctly. Use eight characters or less in the root of the filename and three characters or less in the extension.030: Filename contains illegal characters.NPATHExplanation: NetWare, like DOS, does not use the following keyboard characters in filenames: ."\ / {} : * < > | + + ; , ? Action: Do not use invalid characters in the filename.035: Filename was not found in the search sequence.NPATHExplanation: The filename entered in the command was not found in NetWare's search sequence.Action:  Use NDIR to locate the directory the file is in, then map a search drive to that directory. The workstation should then be able to find the file in the search sequence. For information on NetWare's search sequence, see "BOOK="cncptenu" COLLECTION="nw41"Search algorithm" in Concepts.PAGENUM=697 ID="BP691"050: Filename could not be found.NPATHExplanation: NetWare searched for the executable file but could not find it in the search sequence or did not recognize the filename.Action: Type the name of the file correctly. Use NDIR to determine whether the executable file is on the system. If you locate the directory the file is in, map a search drive to that directory. If the file does not exist, use NWXTRACT to get the file from diskette or CD. For information on NetWare's search sequence, see "BOOK="cncptenu" COLLECTION="nw41"Search algorithm" in Concepts.903: The command line syntax is invalid.NPATHAction: See message IDREF="FM18860""903: The command line syntax is invalid." in Appendix C.908: The specified path is invalid.NPATHAction: See message IDREF="FM51165""908: The specified path is invalid." in Appendix C.917: This utility was unable to set the context.NPATHAction: See message IDREF="FM32126""917: This utility was unable to set the context." in Appendix C.920: This utility was unable to allocate <number> bytes of memory.NPATHAction: See message IDREF="FM30331""920: This utility was unable to allocate number bytes of memory." in Appendix C.970: The attempt to open the Unicode table files failed.NPATHAction: See message IDREF="FM15675""970: The attempt to open the Unicode table files failed." in Appendix C.971: The workstation does not have enough memory to load the Unicode table files.NPATHAction: See message IDREF="FM55341""971: The workstation does not have enough memory to load the Unicode table files." in Appendix C.972: Access to the Unicode table files was denied.NPATHAction: See message IDREF="FM90152""972: Access to the Unicode table files was denied." in Appendix C.973: The Unicode table files cannot be found in the NLS directory or in the search path. Code page: <number>  Country:  <number>NPATHAction: See message IDREF="FM62778""973: The Unicode table files cannot be found in the NLS directory or in the search path. Code page: number Country: number" in Appendix C.PAGENUM=698 ID="BP692"974: The Unicode table files are corrupt.NPATHAction: See message IDREF="FM63405""974: The Unicode table files are corrupt." in Appendix C.975: The Unicode table files cannot be opened because there are already too many open files. Close some files or modify your CONFIG.SYS file.NPATHAction: See message IDREF="FM49793""975: The Unicode table files cannot be opened because there are already too many open files. Close some files or modify your CONFIG.SYS file." in Appendix C.998: The message file found (utility_name.MSG) is an incorrect version. The correct version is number. The default English message file will be used. See your network supervisor for assistance.NPATHAction: See message IDREF="FM91957""998: The message file found (utility_name.MSG) is an incorrect version. The correct version is number. See your network supervisor for assistance." in Appendix C.999: The message file for this utility cannot be found.NPATHAction: See message IDREF="FM69424""999: The message file for this utility cannot be found." in Appendix C.PAGENUM=699 ID="BP693"NPRINT104, 105, and 106: Message.NPRINTAction: Follow the actions specified in the message. If the problem persists, contact your Novell Authorized Reseller.107: This utility was unable to delete the file after sending it to the print queue.NPRINTExplanation: You used the "Delete" option with the NPRINT command; however, the NetWare server could not delete the specified file for one of the following reasons:MARK=BULLETThe file was locked by another user or application.The file was deleted by another user or application after it was printed.The User object does not have the Delete right to the file.The file is flagged Read-Only.Action: If the file was not successfully deleted with the NPRINT command, use the DOS DEL command or the DOS ERASE command to delete the file. (Flag the file Read/Write or use RIGHTS to grant the Delete right.)109, 110, 111, 112, 113, 114, 115, 116, 117, 120, 121, 122, 123, 124, 130, 132, 133, 134, 135, 136, 137, 139, and 140: Message.NPRINTAction: Follow the actions specified in the message. If the problem persists, contact your Novell Authorized Reseller.141: An invalid username or password was typed in. Access to NetWare server name has been denied.NPRINTAction: Enter a valid name or password and try the operation again.142: Message.NPRINTAction: Follow the actions specified in the message. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=700 ID="BP694"150: The print queue is full. Either the print job capacity of the print queue has been reached or the server volume is out of disk space. Try again.NPRINTExplanation: The print queue is full.Action: Wait for some of the print jobs to be completed on the print queue, then retry the operation. If you suspect disk space is the problem, see "BOOK="superenu" COLLECTION="nw41"Resolving Server Disk Space Problems" in Supervising the Network.151, 152, 153, 154, and 155: Message.NPRINTAction: Follow the actions specified in the message. If the problem persists, contact your Novell Authorized Reseller.156: An unknown print queue error code occurred. Wait a few minutes and try again. For information on the specific error code, refer to the System Messages documentation.NPRINTAction: For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A.157 and 158: Message.NPRINTAction: Follow the actions specified in the message. If the problem persists, contact your Novell Authorized Reseller.160, 162, 170, and 171: Message.NPRINTAction: Follow the actions specified in the message. If the problem persists, contact your Novell Authorized Reseller.180: There is insufficient disk space to store the print job in the print queue. Have the supervisor increase the available disk space on the volume where the print queue is located.NPRINTAction: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Disk Space Problems" in Supervising the Network.181, 182, and 183:  Message.NPRINTAction: Follow the actions specified in the message. If the problem persists, contact your Novell Authorized Reseller.184: A read error has occurred. This could indicate a possible problem with your hard disk.NPRINTExplanation: A read error on the source file failed. This may indicate a hard disk problem.Action: See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.PAGENUM=701 ID="BP695"200, 201, 210, 211, 219, 220, 221, 222, 223, 224: Message.NPRINTAction: Follow the actions specified in the message. If the problem persists, contact your Novell Authorized Reseller.229: The job configuration contains a form that does not exist.NPRINTExplanation: The form specified in the print job configuration may have been deleted.Action: Modify the print job configuration to specify a form that exists. Or, specify the form on the command line using the Form= command. For more information on specifying forms in print job configurations, see "BOOK="printenu" COLLECTION="nw41"Setting Up and Servicing Print Servers" in Print Services.230, 231, 232, 233, 240,241, 242, 243, 253, 298, 300, 301, 302, 400, 401, 402, 403, 404, 405, 500, 501, 502, 503, 504, 505, 506, 507, 600, 601, 602, 603, 604, 605, 606, 607, 608, 609, 611, 612, 613, 614, 615, 616, and 700: Message.NPRINTAction: Follow the actions specified in the message. If the problem persists, contact your Novell Authorized Reseller.903: The command line syntax is invalid.NPRINTAction: See message IDREF="FM18860""903: The command line syntax is invalid." in Appendix C.906: The Unicode files cannot be found.NPRINTAction: See message IDREF="FM78951""906: The Unicode files cannot be found." in Appendix C.917: This utility was unable to set the context.NPRINTAction: See message IDREF="FM32126""917: This utility was unable to set the context." in Appendix C.920: This utility was unable to allocate <number> bytes of memory.NPRINTAction: See message IDREF="FM30331""920: This utility was unable to allocate number bytes of memory." in Appendix C.921: Either the supervisor has locked the bindery or volume SYS: is not mounted on server name.NPRINTAction: See message IDREF="FM49837""921: Either the supervisor has locked the bindery or volume SYS: is not mounted." in Appendix C.922: Intruder detection lockout has disabled this account.NPRINTAction: See message IDREF="FM41618""922: Intruder detection lockout has disabled this account." in Appendix C.PAGENUM=702 ID="BP696"923: An unexpected error has occurred: code.NPRINTAction: See message IDREF="FM30182""923: An unexpected error has occurred. Error code: code." in Appendix C.PAGENUM=703 ID="BP697"NPRINTER-DOS07: This program could not connect to print server name. Error code code.NPRINTER-DOSExplanation: A network error prevented the network printer from connecting to the print server.Explanation: Make sure the print server is operating. Retry the operation. If the error persists and the specified print server is running, contact your Novell Authorized Reseller. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A.12: Print server name is down.NPRINTER-DOSExplanation: The print server is currently down.Action: Load the print server and retry the operation.13: Printer number on print server name is already in use.NPRINTER-DOSExplanation: Another NPRINTER is using the number specified.Action: Unload the other NPRINTER and retry the operation. The other NPRINTER may be an NLM running on a NetWare server or another NPRINTER.EXE running on the workstation. (Note: The name of the NetWare Network Printer Driver NLM may not be NPRINTER.NLM.) 50: This program could not get the network address for print server name. Error code code.NPRINTER-DOSExplanation: The bindery is locked, and NPRINTER is unable to access necessary bindery information. Usually, the bindery is only locked momentarily.Action: Retry the operation. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A.51: This program could not load the schema translation table (SCHEMA.XLT). Error code code.NPRINTER-DOSExplanation: The printer was selected by selecting the Printer Object. Selecting the printer by Printer Object requires the most memory. As a result, there is not enough memory left to load the schema translation table.Action: Try selecting the print server first, or reducing the amount of memory used before loading the NPRINTER. See "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network.PAGENUM=704 ID="BP698"52: This program could not open an IPX socket. Error code code.NPRINTER-DOSExplanation: NPRINTER.EXE is unable to open an IPX socket.Action: This may be a temporary problem due to a high volume of server or network traffic at the time NPRINTER was executed. Try loading the NPRINTER again. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A.53: This program could not find and open the schema translation file (SCHEMA.XLT). Error code code.NPRINTER-DOSAction: See message IDREF="FM48610""907: This utility cannot open the translation table SCHEMA.XLT." in Appendix C.54: This program could not get Directory Services to provide a context handle.NPRINTER-DOSExplanation: NetWare Directory Services was unable to provide a context structure for NPRINTER to use.Action: The NetWare Directory Services connection table may have become corrupted. Try rebooting the workstation and allowing the VLM to reconstruct NetWare Directory Services.55: The IPX/SPX protocols (IPXODI.COM) are not installed.NPRINTER-DOSExplanation: IPX has not been loaded in this workstation. NPRINTER requires IPX to execute.Action: Load IPXODI or the dedicated driver with IPX linked in.56: The system could not allocate number bytes of memory.NPRINTER-DOSExplanation: The workstation needs more than 350 KB of available memory to load NPRINTER. During the initialization of NPRINTER, the amount of memory needed will vary depending on how the network is configured, and on the way you determine to load NPRINTER. Less memory is required to load NPRINTER directly from the command line. The most memory is required when selecting the Printer Object from the directory first as opposed to selecting the Print Server first. After NPRINTER is initialized, NPRINTER needs only 6 KB of memory to run.Action: Load the NPRINTER by selecting the Print Server first. If this error persists, try loading the NPRINTER directly from the command line. See "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network.PAGENUM=705 ID="BP699"57: This program has already been loaded the maximum number of times (7) on this workstation.NPRINTER-DOSExplanation: NPRINTER supports LPT1-LPT3 and COM1-COM4. If all seven ports are physically available in the workstation, then the NPRINTER can be loaded up to seven times on one workstation.Action: No action can be taken until one or more ports is freed up.58: The specified network printer was not loaded.NPRINTER-DOSExplanation: The printer specified on the command line was defined as type "Other." Printers of type "Other" allow the user to configure the printer at load time. This message displays when the user cancels loading the specified printer, or when some other error has occurred (and printed the error report).Action: Make sure there are no input errors in the menu and retry the operation.59: Network printer name was not unloaded. Either it is not the last one loaded or some other problem occurred.NPRINTER-DOSExplanation: Either a TSR (terminate-and-stay-resident) program has been loaded after the specified NPRINTER, or the Interrupt table has become corrupted.Action: Try the following:MARK=BULLETUnload all TSR programs that may have been loaded after NPRINTER; remove them in the reverse order that they were loaded.If an application has been run that shared an interrupt with the NPRINTER and has not properly restored the interrupt information, NPRINTER cannot be unloaded safely. Reboot the workstation to remove the NPRINTER and the offending programs.60: No network printer is loaded.NPRINTER-DOSExplanation: NPRINTER /S (Show) has been run, but there are no NPRINTERs loaded.Action: None. This message is for information only. However, you may want to load NPRINTER.61: No network printers are available on print server name.NPRINTER-DOSExplanation: The selected print server does not have any network printers defined as manual load, or all the network printers are currently attached to other NetWare network printer drivers.Action: If you are attaching a new network printer, check the configuration of the network printers on the print server.PAGENUM=706 ID="BP700"62: This program could not find NPRINTER loaded in memory.  No network printer driver was unloaded.NPRINTER-DOSExplanation: You tried to unload NPRINTER, but NPRINTER had not been loaded previously.Action: None. This message is for information only.63: Print server name is unknown at this time.NPRINTER-DOSExplanation: The print server specified in the command is not currently running, or the name specified is not the Advertising Print Server name (SAP).Action: Verify the correct spelling of the print server's Advertising name.64: Printer number on print server name does not exist.NPRINTER-DOSExplanation: The Print Server reported that the given printer number is undefined.Action: Configure the printer.65: The specified printer is not the last one loaded. Type NPRINTER /s to show all loaded printers in the order loaded. Type NPRINTER /u with no other parameters to unload the last one loaded.NPRINTER-DOSExplanation: You specified which NPRINTER to unload, but that NPRINTER is not the last TSR loaded.Action: Unload any TSR that was loaded after the specified NPRINTER. Running NPRINTER /U will remove the last NPRINTER loaded.66: Directory Services could not find the context. Error code code.NPRINTER-DOSExplanation: The Context Table may have become corrupted.Action: Reboot the workstation to restore the NetWork Directory Services Tables. You may still be able to load NPRINTER by choosing the Print Server first when this error occurs. If not then reboot. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A.67: Print server name is out of memory.NPRINTER-DOSAction: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.PAGENUM=707 ID="BP701"68: Printer name is configured for printer ports not present or failing on this machine. Verify that the port settings in the printer configuration match the workstation hardware configuration.NPRINTER-DOSExplanation: The printer was configured for a port that the workstation doesn't have, or the hardware failed the verification tests.Action: Make sure that the hardware settings on the workstation provide the correct hardware ports.69: A previously loaded NPRINTER is using the selected port.NPRINTER-DOSExplanation: Another NPRINTER is using the specified port. Only one NPRINTER may use a port at a time.Action: Unload the other NPRINTER and retry the operation.70: Printer name has not been assigned to a print server. Error code code.NPRINTER-DOSExplanation: The Printer Object selected doesn't have the Print Server property set.Action: Run PCONSOLE to assign the printer to a print server.71: Printer name doesn't exist in the current context. Error code code.NPRINTER-DOSExplanation: The Printer Object name given on the command line is not in the current context.Action: Change to the context where the Printer Object is defined, or give either the full distinguished name or the relative name of the Printer Object. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A.72: This program could not communicate with print server name due to a communication error. Error code code.NPRINTER-DOSExplanation: SPX, the guaranteed packet delivery protocol used by NPRINTER, has had a fatal error. There is no communication between the workstation and the print server.Action: Make sure that the workstation has not limited the number of SPX connections available. Make sure IPXODI was not loaded with the /A option. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A.PAGENUM=708 ID="BP702"73: Printer name's type is not supported by NPRINTER.NPRINTER-DOSExplanation: NPRINTER supports printers configured as parallel, serial, or other (which are configured to be parallel or serial at load time).Action: Select a different printer definition for NPRINTER.74: Windows is loaded in enhanced mode. Load/unload NPRINTER before loading Windows.NPRINTER-DOSExplanation: You cannot load or unload NPRINTER while Windows is loaded.Action: Unload Windows before trying to load or unload NPRINTER.75: Printer name is configured to have the print server load NPRINTER.NLM on the NetWare server. The printer is defined as auto load (local to print server).NPRINTER-DOSExplanation: The specified Printer Object is configured to be loaded by the print server automatically (local).Action: Use PCONSOLE to reconfigure the printer as manual load (remote).76: No active print servers could be found at this time.NPRINTER-DOSExplanation: No print servers are currently running.Action: Retry the operation when a print server is running.77: Directory Services reports that print server name is currently down. Please select another printer.NPRINTER-DOSExplanation: The Print Server Object reported that the print server is down. Replicas on the network may not have the update yet.Action: Make sure the print server is operating. If the print server is operating, allow time for synchronization of the replica you are using to be completed. Otherwise, try loading NPRINTER by selecting the Print Server first. If the Print Server does not appear in the list, then reverify that the print server is running.78: Printer name's configuration could not be found. Error code code.NPRINTER-DOSExplanation: Either the Printer Object has not been configured, or an error occurred when the printer object's Printer Configuration property was being read.Action: Make sure that the printer object has the Printer Configuration property set.PAGENUM=709 ID="BP703"79: This workstation is not authorized to run NPRINTER for print server name, printer number number, printername name.NPRINTER-DOSExplanation: The printer configuration has set the address restriction to exclude the workstation that is being used.Action: Use an authorized workstation to run NPRINTER.80: The specified printer is not loaded.NPRINTER-DOSExplanation: You specified a printer name or printer number that cannot be found.Action: Make sure that the name or number was typed correctly. If so, load that printer and then retry the operation.81: Unable to get the advertising name for printer server name, used by printer name Error code: code.NPRINTER-DOSExplanation: When NPRINTER is called with a DS printer object, it must determine the SAP (advertising) name for the associated print server. No such determination could be made. This might occur if the printer object has not been assigned to a print server.Action: Use PCONSOLE or NWADMIN to make sure that the printer is assigned to a print server and that the print server has a valid SAP (advertising) name.82: The specified network printer was not loaded. The /t= timing interval is out of range. If used, it must be from number to number.NPRINTER-DOSExplanation: If the /t= command line option is used with NPRINTER, it must be in range specified.Action: Retry the operation with a number in the specified range.83: The specified network printer was not loaded. The /b= buffers setting is out of range. If used, it must be from number to number.NPRINTER-DOSExplanation: If the /b= command line option is used with NPRINTER, it must be in the range specified.Action: Retry the operation with a number in the specified range.887: The name file could not be found.NPRINTER-DOSExplanation: The SCHEMA.XLT file could not be found in any of the expected places.Action: See the message IDREF="FM48610""907: This utility cannot open the translation table SCHEMA.XLT." in Appendix C.PAGENUM=710 ID="BP704"889: The name file found was the wrong version. The correct version is version.NPRINTER-DOSExplanation: The wrong version of the required file SCHEMA.XLT was found.Action: See the message IDREF="FM48610""907: This utility cannot open the translation table SCHEMA.XLT." in Appendix C.970: The attempt to open the Unicode table files failed. Error code code.NPRINTER-DOSAction: See message IDREF="FM15675""970: The attempt to open the Unicode table files failed." in Appendix C.971: The workstation does not have enough memory to load the Unicode table files.NPRINTER-DOSAction: See message IDREF="FM55341""971: The workstation does not have enough memory to load the Unicode table files." in Appendix C.972: Access to the Unicode table files was denied.NPRINTER-DOSAction: See message IDREF="FM90152""972: Access to the Unicode table files was denied." in Appendix C.973: The Unicode table files cannot be found in the NLS directory or in the search path. Code page: <number>  Country:  <number>NPRINTER-DOSAction: See message IDREF="FM62778""973: The Unicode table files cannot be found in the NLS directory or in the search path. Code page: number Country: number" in Appendix C.974: The Unicode table files are corrupt.NPRINTER-DOSAction: See message IDREF="FM63405""974: The Unicode table files are corrupt." in Appendix C.975: The Unicode table files cannot be opened because there are already too many open files. Close some files or modify your CONFIG.SYS file.NPRINTER-DOSAction: See message IDREF="FM49793""975: The Unicode table files cannot be opened because there are already too many open files. Close some files or modify your CONFIG.SYS file." in Appendix C.998: The message file found (<utility_name>.MSG) is an incorrect version. The correct version is <number>. See your network supervisor for assistance.NPRINTER-DOSAction: See message IDREF="FM91957""998: The message file found (utility_name.MSG) is an incorrect version. The correct version is number. See your network supervisor for assistance." in Appendix C.PAGENUM=711 ID="BP705"999: The message file name could not be found.NPRINTER-DOSAction: See message IDREF="FM69424""999: The message file for this utility cannot be found." in Appendix C.PAGENUM=712 ID="BP706"NPRINTER-NLM01: This program could not set up the AIO printer parameters as configured. Error code code.NPRINTER-NLMExplanation: The AIO port driver was unable to set up the "Flow Control" or "Buffer Size" as configured.Action: Make sure that the configuration used is valid. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A.02: AIO.NLM and a port driver must be loaded in order to service printer number.NPRINTER-NLMExplanation: The AIO.NLM and an AIO port driver must be loaded for NPRINTER to access the AIO functions and features. These two programs (along with others) control the actual hardware.Action: Load the AIO.NLM and the appropriate AIO port driver for the hardware.03: The AIO.NLM module does not support one or more functions required by the NPRINTER.NPRINTER-NLMExplanation: The AIO.NLM provides functions that must be present when NPRINTER is configured to be an AIO printer. If all functions are not present, NPRINTER cannot continue.Action: Use the most current versions of the AIO.NLM and associated drivers.04: The AIO port could not be configured. Error code code.NPRINTER-NLMExplanation: NPRINTER tried to give the AIO port driver the parameters for the AIO printer. The port driver reported an error.Action: Make sure that the AIO port driver supports the port you are trying to load.05: This program could not allocate an AIO resource tag.NPRINTER-NLMExplanation: Resource tags are used by the NetWare server to track what each NLM is doing. The server may not have enough available memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. Load MONITOR to track resource use in the future.PAGENUM=713 ID="BP707"06: The AIO port for printer number could not be acquired. Error code code.NPRINTER-NLMExplanation: Another program is using the AIO port.Action: Unload the other program that is using the port. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A.07: This program could not connect to print server name. Error code code.NPRINTER-NLMExplanation: A network error prevented the network printer from connecting to the print server.Action: Retry the operation. Make sure the server is operating. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.08: This program could not get the network printer information from print server name.NPRINTER-NLMExplanation: A communication error has occurred that has prevented NPRINTER from getting the server information.Action: Retry the operation. Make sure the print server is operating.09: No IPX socket is available.NPRINTER-NLMExplanation: The IPX table is full, and there is not another free socket for NPRINTER to use.Action: Unload any NLMs that are not needed, then retry the operation. To prevent the problem from occurring in the future, use SERVMAN to modify the "Maximum IPX socket table size" parameter (the default is 1200). From the main menu, select "IPX/SPX Configuration," then select "IPX Parameters" to access this parameter.10: IRQ number number requested by printer number on print server name is not available.NPRINTER-NLMExplanation: The most common error on a server is a hardware interrupt conflict. This error message indicates either a conflict between the IRQ number and the hardware port number, or the absence of one of these numbers in the configuration file.Action: Make sure the hardware configuration is correct.11: The selected printer is not supported.NPRINTER-NLMExplanation: The NPRINTER.NLM supports only parallel, serial, and AIO printer types.Action: Select a printer that is configured for a supported type.PAGENUM=714 ID="BP708"12: Print server name is down.NPRINTER-NLMExplanation: The specified print server is currently down.Action: Reload the print server and retry the operation.13: Printer number on print server name is already in use.NPRINTER-NLMExplanation: Another NPRINTER is using the number specified.Action: Unload the other NPRINTER and retry the operation. The other NPRINTER may be an NLM running on a NetWare server or another NPRINTER.EXE running on the workstation. Note: The name of the NetWare Network Printer Driver NLM may not be NPRINTER.NLM.14: This program could not get an AES event resource tag.NPRINTER-NLMExplanation: Resource tags are used by the NetWare server to track what each NLM is doing. The server may not have enough available memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. Load MONITOR to track resource use in the future.15: This program could not get an interrupt resource tag for the network printer.NPRINTER-NLMExplanation: Resource tags are used by the NetWare server to track what each NLM is doing. The server may not have enough available memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. Load MONITOR to track resource use in the future.16: This program could not get a resource tag for the network printer port.NPRINTER-NLMExplanation: Resource tags are used by the NetWare server to track what each NLM is doing. The server may not have enough available memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. Load MONITOR to track resource use in the future.17: This program could not get a resource tag for the polling procedure.NPRINTER-NLMExplanation: Resource tags are used by the NetWare server to track what each NLM is doing. The server may not have enough available memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. Load MONITOR to track resource use in the future.PAGENUM=715 ID="BP709"18: This program could not get an IPX socket resource tag for the network printer.NPRINTER-NLMExplanation: Resource tags are used by the NetWare server to track what each NLM is doing. The server may not have enough available memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. Load MONITOR to track resource use in the future.19: This program could not import a symbol.NPRINTER-NLMAction: Contact your Novell Authorized Reseller.20: The accessed port is not supported by hardwareNPRINTER-NLMAction: Contact your Novell Authorized Reseller.79: This NetWare server is not authorized to run NPRINTER for print server name, printer number number, printername name.NPRINTER-NLMExplanation: The printer configuration has set the address restriction to exclude the NetWare server that is being used.Action: Use an authorized NetWare server to run NPRINTER.PAGENUM=716 ID="BP710"NPRINTER-OS2932: The connection status could not be retrieved.NPRINTER-OS2Explanation: NPRINTER cannot get the connection status. There may not be any more sockets available, or the print server may not be running.Action: Make sure the print server is operating. Make sure that you have not used all of the NET.CFG sockets. Close applications that are currently running and free up some hard disk space by deleting unnecessary programs. If using multiple disk partitions, consider moving the OS/2 swapper file to a larger partition. If you suspect a memory problem, try adding RAM, reducing the configuration options in the CONFIG.SYS file, or removing optional device drivers from the CONFIG.SYS file. Disk compression utilities may also be available that can help resolve this problem. After completing these actions, shut down OS/2 and then reboot the system. If the problem persists, contact your Novell Authorized Reseller.933: The socket cannot be opened.NPRINTER-OS2Explanation: NPRINTER cannot get a connection or open a socket for communications. There may not be available sockets, or the print server may not be running.Action: Make sure the print server is operating. Make sure that you have not used all of the NET.CFG sockets. Close applications that are currently running and free up hard disk space by deleting unnecessary programs. If using multiple disk partitions, consider moving the OS/2 swapper file to a larger partition. If you suspect a memory problem, try adding RAM, reducing the configuration options in the CONFIG.SYS file, or removing optional device drivers from the CONFIG.SYS file. Disk compression utilities may also be available that can help resolve this problem. After completing these actions, shut down OS/2 and then reboot the system. If the problem persists, contact your Novell Authorized Reseller.934: The connection cannot be established.NPRINTER-OS2Explanation: NPRINTER cannot get a connection or open a socket for communications. There may not be any available sockets, or the print server may not be running.PAGENUM=717 ID="BP711"Action: Make sure the print server is operating. Make sure that you have not used all of the NET.CFG sockets. Close applications that are currently running and free up hard disk space by deleting unnecessary programs. If you are using multiple disk partitions, consider moving the OS/2 swapper file to a larger partition. If you suspect a memory problem, try adding RAM, reducing the configuration options in the CONFIG.SYS file, or removing optional device drivers from the CONFIG.SYS file. Disk compression utilities may also be available that can help resolve this problem. After completing these actions, shut down OS/2 and then reboot the system. If the problem persists, contact your Novell Authorized Reseller.935: No network connections can be found.NPRINTER-OS2Explanation: NPRINTER cannot get a connection or open a socket for communications. The workstation may not have any more sockets available, or the print server may not be running.Action: Make sure the print server is operating. Make sure that you have not used up all of the NET.CFG sockets. Close applications that are currently running and free up hard disk space by deleting unnecessary programs. If using multiple disk partitions, consider moving the OS/2 swapper file to a larger partition. If you suspect a memory problem, try adding RAM, reducing the configuration options in the CONFIG.SYS file, or removing optional device drivers from the CONFIG.SYS file. Disk compression utilities may also be available that can help resolve this problem. After completing these actions, shut down OS/2 and then reboot the system. If the problem persists, contact your Novell Authorized Reseller.936: The socket cannot be disconnected.NPRINTER-OS2Explanation: NPRINTER could not disconnect from a socket. This error could result from a bad packet or an invalid socket parameter. A programming error may have caused this problem.Action: Retry the operation. If the problem persists, contact your Novell Authorized Reseller.937: Sufficient memory cannot be allocated.NPRINTER-OS2Explanation: OS/2 could not give NPRINTER the memory requested.Action: Try adding RAM, reducing the configuration options in the CONFIG.SYS file (for example, reducing the size of DIRCACHE), removing optional device drivers from the CONFIG.SYS file, and freeing up some hard disk space by deleting unnecessary programs. If using multiple disk partitions, consider moving the OS/2 swapper file to a larger partition. Disk compression utilities may also be available that can help resolve this problem. After completing these actions, shut down OS/2 and then reboot the system. If the problem persists, contact your Novell Authorized Reseller.938: Attachment cannot be made to the print server.NPRINTER-OS2Explanation: NPRINTER could not attach to the print server.Action: Make sure the print server is operating. Make sure the print server can be seen when you run NLIST from the workstation.PAGENUM=718 ID="BP712"962: The print job cannot continue. An error was encountered writing data to the OS/2 spool file. Check disk space.NPRINTER-OS2Explanation: NPRINTER could not write the print job to the OS/2 queue.Action: Try adding RAM, reducing the configuration options in the CONFIG.SYS file (for example, reducing the size of DIRCACHE), removing optional device drivers from the CONFIG.SYS file, or freeing up some hard disk space by deleting unnecessary programs. If using multiple disk partitions, consider moving the OS/2 swapper file to a larger partition. Disk compression utilities may also be available that can help resolve this problem. After completing these actions, shut down OS/2 and then reboot the system. If the problem persists, contact your Novell Authorized Reseller.963: The NPRINTER system information cannot be saved.NPRINTER-OS2Explanation: The printer definition information could not be written out to disk. This could be a memory problem, or the User object may have Read Only rights to this information.Action: Make sure the user has appropriate user access rights. Try adding RAM, reducing the configuration options in the CONFIG.SYS file (for example, reducing the size of DIRCACHE), removing optional device drivers from the CONFIG.SYS file, or freeing up some hard disk space by deleting unnecessary programs. If using multiple disk partitions, consider moving the OS/2 swapper file to a larger partition. Disk compression utilities may also be available that can help resolve this problem. After completing these actions, shut down OS/2 and then reboot the system. If the problem persists, contact your Novell Authorized Reseller.964: An OS/2 print queue cannot be located. NPRINTER is unable to start. Set up an OS/2 print queue and restart NPRINTER.NPRINTER-OS2Explanation: No OS/2 print queue has been defined.Action: From the template folder, drag out a printer template and create a print queue.965: A Directory Services context cannot be created.NPRINTER-OS2Explanation: One of the following may have occurred:MARK=BULLETThe workstation is using an outdated version of the Requester.The workstation is not authenticated to a NetWare 4 server.NetWare Directory Services is not loaded.You incorrectly typed in the NetWare Directory Services object name.PAGENUM=719 ID="BP713"The workstation does not have enough memory to set up the context.Action: Make sure that the workstation is running the latest version of the Requester. Make that the workstation is authenticated to a NDS server. If you suspect a memory problem, try adding RAM, reducing the configuration options in the CONFIG.SYS file (for example, reducing the size of DIRCACHE), removing optional device drivers from the CONFIG.SYS file, or freeing up some hard disk space by deleting unnecessary programs. If using multiple disk partitions, consider moving the OS/2 swapper file to a larger partition. Disk compression utilities may also be available that can help resolve this problem. After completing these actions, shut down OS/2 and then reboot the system. If the problem persists, contact your Novell Authorized Reseller.966: NPRINTER cannot attach to the print server. NPRINTER cannot initialize.NPRINTER-OS2Explanation: NPRINTER cannot get a connection to the print server.Action: Make sure the print server is operating. Make sure that you have not used up all of the connections as defined in the NET.CFG file.969: The printer did not initialize.NPRINTER-OS2Explanation: OS/2 could not create a printer thread.Action: Try adding RAM, reducing the configuration options in the CONFIG.SYS file (for example, reducing the size of DIRCACHE), removing optional device drivers from the CONFIG.SYS file, and freeing up some hard disk space by deleting unnecessary programs. If using multiple disk partitions, consider moving the OS/2 swapper file to a larger partition. Disk compression utilities may also be available that can help resolve this problem. After completing these actions, shut down OS/2 and then reboot the system. If the problem persists, contact your Novell Authorized Reseller.970: The attempt to open the Unicode table files failed.NPRINTER-OS2Action: See IDREF="FM15675""970: The attempt to open the Unicode table files failed." in Appendix C.971: The workstation does not have enough memory to load the Unicode table files.NPRINTER-OS2Explanation: During its processing, this utility needed more memory and tried to allocate more. There was no more available memory.Action: Try adding RAM, reducing the configuration options in the CONFIG.SYS file (for example, reducing the size of DIRCACHE), removing optional device drivers from the CONFIG.SYS file, and freeing up some hard disk space by deleting unnecessary programs. If using multiple disk partitions, consider moving the OS/2 swapper file to a larger partition. Disk compression utilities may also be available that can help resolve this problem. After completing these actions, shut down OS/2 and then reboot the system. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=720 ID="BP714"972: Access to the Unicode table files was denied.NPRINTER-OS2Action: See message IDREF="FM90152""972: Access to the Unicode table files was denied." in Appendix C.973: The Unicode table files cannot be found in the NLS directory or in the search path. Code page: <number>  Country:  <number>NPRINTER-OS2Action: See IDREF="FM62778""973: The Unicode table files cannot be found in the NLS directory or in the search path. Code page: number Country: number" in Appendix Cmessage 974: The Unicode table files are corrupt.NPRINTER-OS2Action: See message IDREF="FM63405""974: The Unicode table files are corrupt." in Appendix C.975: The Unicode table files cannot be opened because there are already too many open files. Close some files or modify your CONFIG.SYS file.NPRINTER-OS2Action: See message IDREF="FM49793""975: The Unicode table files cannot be opened because there are already too many open files. Close some files or modify your CONFIG.SYS file." in Appendix C.976: Resource file NPRINTER.DLL could not be loaded.NPRINTER-OS2Explanation: The resource file cannot be found.Action: Make sure that NPRINTER.DLL is in the NetWare directory or NLS directory under the directory where it will be run. It can also be in the libpath.979: Only number printers can be running at the same time. NPRINTER has already encountered number printers to load at startup.NPRINTER-OS2Explanation: In NetWare 4, the number of printers that can be running concurrently is seven.Action: Do not set more than seven printers to be loaded at startup. Choose "Define Printers" from the "Config" menu. Highlight a printer and press the "Edit" button to unmark the "Load at Startup" option.991: An error occurred in <function_name>. Error code: <code>.NPRINTER-OS2Action: See message IDREF="FM92553""991: An error occurred in function_name. Error code: code." in Appendix C.PAGENUM=721 ID="BP715"998: The message file found (<utility_name>.MSG) is an incorrect version. The correct version is <number>. See your network supervisor for assistance.NPRINTER-OS2Action: See message IDREF="FM91957""998: The message file found (utility_name.MSG) is an incorrect version. The correct version is number. See your network supervisor for assistance." in Appendix C.999: The message file for this utility cannot be found.NPRINTER-OS2Action: See message IDREF="FM69424""999: The message file for this utility cannot be found." in Appendix C.PAGENUM=722 ID="BP716"NVER001: NVER has been halted by the user.NVERExplanation: The user has forced NVER to terminate by pressing <MOREINFO="NONE"Ctrl>+<MOREINFO="NONE"C>, <MOREINFO="NONE"Ctrl>+<MOREINFO="NONE"Break>, or MOREINFO="NONE"<Esc>.Action: None. This message is for information only.100: Unable to get DOS version information.NVERExplanation: For some reason, NVER could not get the version number of the DOS shell.Action: None. This message is for information only. NVER will continue to get other version information.210: The system was unable to get the connection list. Connect server information cannot be listed.NVERExplanation: NVER uses a library call to get a list of workstation connections. If the call fails, this message is given, but NVER continues as well as it can with other available information.Action: Reboot the workstation. If the problem persists, contact your Novell Authorized Reseller.220: Connect server information cannot be listed.NVERExplanation: This message is used in connection with message 920. If memory cannot be allocated for a connection list, message 920 is displayed, followed by this message. NVER then terminates.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network.900: An internal application error has occurred. Error code: code.NVERAction: None. This message is for information only.903: The command line syntax is invalid.  For help, type NVER /?.NVERAction: See message IDREF="FM18860""903: The command line syntax is invalid." in Appendix C.920: This utility was unable to allocate <number> bytes of memory.NVERAction: See message IDREF="FM30331""920: This utility was unable to allocate number bytes of memory." in Appendix C.PAGENUM=723 ID="BP717"998: The message file found (<utility_name>.MSG) is an incorrect version. The correct version is <number>. See your network supervisor for assistance.NVERAction: See message IDREF="FM91957""998: The message file found (utility_name.MSG) is an incorrect version. The correct version is number. See your network supervisor for assistance." in Appendix C.999: The message file for this utility cannot be found.NVERAction: See message IDREF="FM69424""999: The message file for this utility cannot be found." in Appendix C.PAGENUM=724 ID="BP718"NWDRV00: The NetWare VLM is not loaded or is not configured correctly. All network functions will be disabled. Reconfigure the VLM and restart Windows.NWDRVExplanation: Without the NetWare DOS Requester (VLM.EXE and .VLM files), the workstation cannot communicate with NetWare servers. The NetWare Windows driver (NETWARE.DRV) depends on the VLM to provide network support for Windows.Action: Exit Windows. Go to the directory where the VLM.EXE is located and type "VLM." For information about the NetWare VLM, see 
BOOK="ws_d1enu" COLLECTION="nw41"NetWare Client for DOS and MS Windows User Guide.10: The VNETWARE.386 file has not been loaded. All network functions will be disabled. To use NetWare, install VNETWARE.386 and restart Windows.NWDRVExplanation: The NetWare Windows driver (NETWARE.DRV) depends on the VNETWARE.386 file to run Windows in enhanced mode.Action: Exit Windows. Copy VNETWARE.386 to the Windows subdirectory (for example, C:\WINDOWS). VNETWARE.386 should be on the CLASS=DISKWSWIN_1 diskette. (VNETWARE.386 is located on CD-ROM under CLIENT\DOSWIN\WSWIN_1.) Also make sure that the "[386Enh]" section of the SYSTEM.INI file has the following line:FORMAT="LINESPECIFIC"MOREINFO="NONE"network=*vnetbios, vnetware.386, vipx.386 Then restart Windows.20: There was a problem loading or executing the NetWare Directory Services support libraries. All NetWare Directory Services functions are now disabled.NWDRVExplanation: To access NetWare Directory Services, the Windows driver (NETWARE.DRV) depends on the following .DLL files:FORMAT="LINESPECIFIC"MOREINFO="NONE"NWNET.DLL 
NWLOCALE.DLL 
NWCALLS.DLL Action: Exit Windows. Copy these .DLL files to the Windows subdirectory (for example, C:\WINDOWS). The .DLL files are located on the CLASS=DISKWSWIN_1 diskette. (The .DLL files are located on CD-ROM under CLIENT\DOSWIN\WSWIN_1.) Then restart Windows.PAGENUM=725 ID="BP719"30: There was a problem loading the Unicode tables. All NetWare Directory Services functions are now disabled.NWDRVExplanation: Unicode tables support international languages. They are located in the .001 files (for example, 437_UNI.001). In the DOS, Windows, and OS/2 environments, the program searches the following areas for the Unicode files:MARK=BULLETThe current directory (for DOS and OS/2 environments) or the Windows directory.The load directory (the directory containing the current utility's .EXE file). Normally this will be the PUBLIC directory.The NLS directory that is located within the load directory (the directory containing the current utility's .EXE file). If the Unicode files are not found in the NLS directory within the load file, the program searches the NLS directory that is a sibling of the load directory (that is, at the same level as the load directory). Note: The NWLanguage environment variable does not apply here.The PATH and DPATH (for OS/2 only) environment variables. These environment variables are usually in the user's login script or in the AUTOEXEC.BAT file.The following four files must be in one of these locations of the user's search drive, or this error message is displayed:FORMAT="LINESPECIFIC"MOREINFO="NONE"code_page_UNI.country_id 
UNI_
code_page country_id 
UNI_MON.
country_id 
UNI_COL.
country_id Action: While this error can be caused by insufficient memory, inappropriate rights, or even file corruption, most commonly it results from the files not being found in the correct path. Copy the .001 files from the CLASS=DISKWSWIN_1 diskette (or the original CD-ROM) to the Windows subdirectory or any other directory that is in the PATH environment setting. Select a language for Windows that is supported by NetWare. Do this by choosing the International icon from the Control Panel.50: The temporary drive could not be mapped. Contact the network administrator.NWDRVExplanation: The NetWare Windows driver (NETWARE.DRV) allocates temporary drives on the server to perform some functions.Action: Make sure the server is operating.PAGENUM=726 ID="BP720"NWDSBRWS920: This utility was unable to allocate <number> bytes of memory. The error code is: code.NWDSBRWSAction: See message IDREF="FM30331""920: This utility was unable to allocate number bytes of memory." in Appendix C.991: An error occurred in function_name. The error code is: code.NWDSBRWSAction: See message IDREF="FM92553""991: An error occurred in function_name. Error code: code." in Appendix C.998: The message file found (<utility_name>.MSG) is an incorrect version. The correct version is <number>. See your network supervisor for assistance.NWDSBRWSAction: See message IDREF="FM91957""998: The message file found (utility_name.MSG) is an incorrect version. The correct version is number. See your network supervisor for assistance." in Appendix C.999: The message file for this utility cannot be found.NWDSBRWSAction: See message IDREF="FM69424""999: The message file for this utility cannot be found." in Appendix C.PAGENUM=727 ID="BP721"NWDxxxxThese messages are part of the online help in NetWare Administrator.PAGENUM=728 ID="BP722"NWP1: The message file name is invalid. The program cannot be loaded.NWPExplanation: The .MSG file is invalid. This problem could be the result of a corrupted file, a bad translation, or an outdated file version.Action: Either update the .MSG file with a valid copy or delete the file. The DOS Requester will use the default messages that are bound to the binary files.5: Module1.VLM is not loaded. The module2.VLM file cannot be loaded before module1.VLM. Load the module1.VLM file first then try to load the module2.VLM file.NWPExplanation: The module2.VLM requires that the module1.VLM be loaded. Either the current configuration has module1.VLM and module2.VLM loading out of order, or module1.VLM did not load successfully.Action: Make sure that module1.VLM is configured to load before module2.VLM. To do this, change the load order of the "VLM=" parameter in the NET.CFG file.7: In order to load the module3.VLM, one of the following VLMs must be loaded: module1.VLM, module2.VLM.NWPExplanation: The module3.VLM requires that module1.VLM or module2.VLM be loaded. Either the current configuration has module3.VLM loading before the modules in the module1.VLM or module2.VLM list, or module1.VLM or module2.VLM did not load successfully.Action: Make sure that module1.VLM or module2.VLM load successfully before module3.VLM.42: There is a missing or invalid value for `parameter' on line number of the configuration file. This entry will be ignored. Correct the line specified in the configuration file before continuing.NWPExplanation: The configuration file contains a configuration keyword that has an invalid parameter or that does not specify a parameter. This invalid line will be ignored by the configuration process.Action: Because this line will be ignored, no action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message.PAGENUM=729 ID="BP723"43: There is a missing or invalid ON/OFF value for `parameter' on line number of the configuration file. This entry will be ignored. Correct the line specified in the configuration file before continuing.NWPExplanation: The configuration file contains a configuration keyword that is defined to use either an "ON" or "OFF" parameter, but a different parameter or no parameter has been specified. This invalid line will be ignored by the configuration process.Action: Because this line will be ignored, no action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message.45: The parameter specified for the following option was out of range and has been adjusted.NWPExplanation: A configurable parameter has been configured too high or too low to be valid. The parameter is specified on the line following the message.Action: Check and correct the parameter specified in the NET.CFG file. For information on the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.59: The SECURITY.VLM file has not been loaded. The NWP.VLM file will load successfully without NCP signature support. Load the SECURITY.VLM file before loading the NWP.VLM file or add SIGNATURE LEVEL=0 to the NET.CFG file; then load NWP.VLM.NWPExplanation: This message is only a warning. The DOS Requester will function properly without NCP authentication. For NCP authentication to operate properly, the SECURITY.VLM module must be loaded before NWP.VLM. Either the NWP.VLM is being loaded before SECURITY.VLM or SECURITY.VLM did not load successfully.Action: If NCP authentication is desired, make sure that the SECURITY.VLM is configured to load before NWP.VLM and that it loads successfully before trying to load NWP.VLM. If NCP authentication is not desired, add "SIGNATURE LEVEL=0" to the "NETWARE DOS REQUESTER" section of the NET.CFG file.PAGENUM=730 ID="BP724"NWPA.NLM001: HAMDriverName returned success without calling HAI_Complete_HACB.NWPA.NLMExplanation: The indicated Host Adapter Module (HAM) driver did not follow the proper pattern to abort the current I/O request. However, the NPA NLM program detected this condition and made the appropriate corrections.Action: Because this condition is recoverable, continued use of this HAM driver may work. However, contacting the driver manufacturer for an update is best.002: Ran out of Below16Meg buffers. Increase the reserve-number specified in the STARTUP.NCF file.NWPA.NLMExplanation: The condition that issues this message is no cause for alarm, and it only applies to 16-bit host adapters because of their 16 MB addressing limitation. The message is indicating that the server cannot allocate any new memory buffers below 16 MB for I/O use. All I/O channels are still valid, but I/O performance will decrease because the server must wait for existing buffers to recycle.Action: If the maximum has not already been specified, increase the value specified for the Reserved Buffers Below 16 Meg parameter in the STARTUP.NCF file.003: The CDM driver deactivated device name.NWPA.NLMExplanation: The Custom Device Module (CDM) could not complete the request because of a device or an adapter failure. Action: Try reactivating the device using MONITOR.NLM. If this does not work, try a power-on reset. If the reset does not work, the device or adapter is possibly malfunctioning. Contact the manufacturer of the device or adapter.PAGENUM=731 ID="BP725"NWSNUT9: CreatePortal was unable to create a portal.NWSNUTExplanation: The server may not have enough available memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.10: ComputePortalPosition was called with height=number, and width=number.NWSNUTExplanation: This is an error within the calling NLM. The values passed to this NUT call were incorrect.Action: Retry the operation. If the problem persists, contact the vendor of the NLM.12: AlignListDisplay could not find element name in the current list.NWSNUTExplanation: This is an error within the calling NLM. The values passed to this NUT call were incorrect.Action: Retry the operation. If the problem persists, contact the vendor of the NLM.13: AlignChangedList could not find element name in the current list.NWSNUTExplanation: This is an error within the calling NLM. The values passed to this NUT call were incorrect.Action: Retry the operation. If the problem persists, contact the vendor of the NLM.14: GetListIndex could not find element name in the current list.NWSNUTExplanation: This is an error within the calling NLM. The values passed to this NUT call were incorrect.Action: Retry the operation. If the problem persists, contact the vendor of the NLM.17: Your list stack is full.NWSNUTExplanation: This is an internal error.Action: Contact your Novell Authorized Reseller.18: AppendToMenu failed to add an entry to the current list.NWSNUTExplanation: The server may not have enough available memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.PAGENUM=732 ID="BP726"19: PopList failed to reset the current list.NWSNUTExplanation: This is an internal system error.Action: Retry the operation. If the problem persists, contact the vendor that supplied the software.20: EditPortalString returned an error of code.NWSNUTExplanation: This is an internal system error.Action: Retry the operation. If the problem persists, contact the vendor that supplied the software. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A.23: AppendToList failed to add an entry to the current list.NWSNUTExplanation: The server may not have enough available memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.24: EnableFunctionKey called with key = code.NWSNUTExplanation: This is an internal system error.Action: Retry the operation. If the problem persists, contact the vendor that supplied the software. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A.25: The field edit routine returned a value of number.NWSNUTExplanation: This is an internal system error.Action: Retry the operation. If the problem persists, contact the vendor that supplied the software.26: AppendToForm was unable to add an element to the form.NWSNUTExplanation: The server may not have enough available memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.27: The number must be between number and number.NWSNUTExplanation: This is an error within the calling NLM. The values passed to this NUT call were incorrect.Action: Retry the operation. If the problem persists, contact the vendor of the NLM.PAGENUM=733 ID="BP727"28: The number must be between number and number.NWSNUTExplanation: This is an error within the calling NLM. The values passed to this NUT call were incorrect.Action: Retry the operation. If the problem persists, contact the vendor of the NLM.30: EditText was unable to allocate a work buffer.NWSNUTExplanation: The server may not have enough available memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.31: EditText was passed a bad parameter.NWSNUTExplanation: This is an error within the calling NLM. The values passed to this NUT call were incorrect.Action: If you are a developer, review the documentation for this function and modify the program accordingly. If purchased software displays this error, contact the supplier of that software.36: The description for this error is not available.NWSNUTExplanation: This is an error within the calling NLM. The calling NLM has not provided a description for this error.Action: If you are a developer, review the documentation for this function and modify the program accordingly. If purchased software displays this error, contact the supplier of that software.38: Function function_name returned an error code of number.NWSNUTExplanation: This is an internal system error.Action: Retry the operation. If the problem persists, contact the vendor that supplied the software.39: SelectFromTextList was called with the default item (item) greater than or equal to the total number of items (number).NWSNUTExplanation: This is an error within the calling NLM. The values passed to this NUT call were incorrect.Action: If you are a developer, review the documentation for this function and modify the program accordingly. If purchased software displays this error, contact the supplier the software.PAGENUM=734 ID="BP728"40: A call to PushList within SelectFromTextList failed.NWSNUTExplanation: The server may not have enough available memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.41: A memory allocation within SelectFromTextList failed.NWSNUTExplanation: The server may not have enough available memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.42: The maximum number of arguments (number) in SelectFromMessages was exceeded.NWSNUTExplanation: This is an error within the calling NLM. The values passed to this NUT call were incorrect.Action: If you are a developer, review the documentation for this function and modify the program accordingly. If purchased software displays this error, contact the supplier of the software.44: The NLM could not be unlinked from the compatibility list.NWSNUTExplanation: This is an internal system error.Action: Retry the operation. If the problem persists, contact your Novell Authorized Reseller.45: NUT was unable to resolve a reference to name.NWSNUTExplanation: This is an internal system error. The version of the NUTCOMP.NLM file does not match the version of the NUT.NLM file.Action: Place the appropriate version of NUTCOMP.NLM in the SYS:SYSTEM directory.46: The NLM passed NUT an invalid message table pointer.NWSNUTExplanation: This is an error within the calling NLM. The values passed to this NUT call were incorrect.Action: If you are a developer, review the documentation for this function and modify the program accordingly. If software displays this error, contact the supplier of the software.PAGENUM=735 ID="BP729"47: This NLM contains no messages.NWSNUTExplanation: The calling NLM passed a NULL to NUT for the "messageTable" parameter. However, the calling NLM did not have any messages linked into it. This must be done with the "messages" parameter to NLMLINKP or NLMLINKR.Action: The calling NLM must pass a valid message table pointer, or it must have messages linked in properly.48: An invalid resource tag was passed to the NUT initialization procedure.NWSNUTExplanation: This is an error within the calling NLM. The values passed to this NUT call were incorrect.Action: If you are a developer, review the documentation for this function and modify the program accordingly. If purchased software displays this error, contact the supplier of the software.49: The NUT compatibility NLM (NUTCOMP) could not be loaded.NWSNUTExplanation: NUT was unable to locate the NUTCOMP.NLM module. This NLM is required to support NLMs that use the NetWare 3.11 NUT interface.Action: Copy the NUTCOMP.NLM module to the SYS:SYSTEM directory.PAGENUM=736 ID="BP730"NWSxxxxThis section lists error messages for NetWare for OS/2's LANSHARE device driver. The following explanations assume that the NetWare files have been loaded in the default directories, C:\NWOS2 and C:\NetWare, in all the directory references.NWS0104: The CGroup Data variables cannot be initialized.NWSxxxxExplanation: This is an internal system error.Action: Retry the operation. If the problem persists, contact your Novell Authorized Reseller.NWS0105: Support hooks from the Link Support Layer cannot be obtained.NWSxxxxExplanation: The LSL.SYS driver has not been loaded.Action: Make sure the CONFIG.SYS file has the following statement before the statement for LANSHARE.SYS:FORMAT="LINESPECIFIC"MOREINFO="NONE"DEVICE=C:\NETWARE\LSL.SYS If the NetWare for OS/2 files were not installed in C:\NETWARE, substitute the correct path to the file. For information, see BOOK="ws_osenu" COLLECTION="nw41"NetWare Client for OS/2 User Guide.NWS0106: The callgate cannot be initialized.NWSxxxxExplanation: This is an internal system error.Action: Retry the operation. If the problem persists, contact your Novell Authorized Reseller.NWS0107: The DOShlp variables cannot be initialized.NWSxxxxExplanation: This is an internal system error.Action: Retry the operation. If the problem persists, contact your Novell Authorized Reseller.NWS0108: The Link Support Layer is not installed.NWSxxxxExplanation: The LSL.SYS driver has not been installed.Action: Make that sure the CONFIG.SYS file has the following statement before the statement for LANSHARE.SYS:FORMAT="LINESPECIFIC"MOREINFO="NONE"DEVICE=C:\NETWARE\LSL.SYS 
PAGENUM=737 ID="BP731"If the NetWare for OS/2 files were not installed in C:\NETWARE, substitute the correct path to the file. For information, see"BOOK="ws_osenu" COLLECTION="nw41"NetWare Client for OS/2 User Guide.NWS0109: The Lan Sharing MLID cannot be registered as a physical device driver.NWSxxxxExplanation: This is an internal system error.Action: Retry the operation. If the problem persists, contact your Novell Authorized Reseller.NWS0130: The program cannot obtain configuration information.NWSxxxxExplanation: The NET.CFG file is missing or invalid.Action: Make sure that the NET.CFG file is in the DPATH in the CONFIG.SYS file. Make sure that there are no control characters in the NET.CFG file. For information about the NET.CFG file and DPATH, see BOOK="ws_osenu" COLLECTION="nw41"NetWare Client for OS/2 User Guide.NWS0140: The configuration parser cannot be obtained; NET.CFG cannot be parsed.NWSxxxxExplanation: The NET.CFG file is missing or invalid.Action: Make sure the NET.CFG file is in DPATH and that it does not have any invalid characters.PAGENUM=738 ID="BP732"NWTIL101: The TIL Loader is unable to allocate resource tags.NWTILExplanation: During the startup of NWTIL. NLM, the server did not have enough memory to allocate resource tags.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.201: RPC data attached to NLM is inconsistent.NWTILExplanation: An invalid TIL opcode was found while translating the remote procedure call (RPC) descriptions. Most likely, the RPC descriptions have been corrupted.Action: Get a new copy of the SERVER.RPC file if this condition occurs while loading DOMAIN.NLM, or a get new copy of DOMAIN.NLM if this condition occurs while loading other NLMs.202: RPC data attached to this NLM has been truncated.NWTILExplanation: While translating remote procedure call (RPC) descriptions, a description terminated unexpectedly. Most likely, the RPC descriptions have been corrupted.Action: Get a new copy of the SERVER.RPC file if this condition occurs while loading DOMAIN.NLM, or get a new copy of DOMAIN.NLM if this condition occurs while loading other NLMs.203: The NLM name contains an RPC description for symbol name that does not exist.NWTILExplanation: The named NLM has a remote procedure call (RPC) description for a symbol that does not exist.Action: Contact the vendor of the NLM.204: An RPC description for symbol name already exists.NWTILExplanation: The NLM being loaded has a remote procedure call (RPC) description for the named symbol, but that symbol has already had an RPC description loaded for it.Action: Contact the vendor of NWTIL.NLM.207: The RPC description attached to this NLM has been corrupted.NWTILExplanation: An unknown record type was encountered in the remote procedure call (RPC) descriptions. Most likely the file has been corrupted.Action: Get a new copy of the NLM.PAGENUM=739 ID="BP733"208: An error occurred during RPC translation.NWTILExplanation: An error was encountered while translating a remote procedure call (RPC) description. This is most likely due to a corrupted file.Action: Contact the vendor, and get a new copy of the NLM.209: The RPC description attached to this NLM is not compatible with Domain.NWTILExplanation: The internal version numbers in NWTIL do not match the version numbers in the SERVER.RPC file.Action: Get versions of SERVER.RPC, DOMAIN.NLM, NWTIL.NLM, and NWTILR.NLM that were released together.210: Could not reallocate a larger RPC source buffer.NWTILExplanation: An out of memory error occurred while translating a remote procedure call (RPC) description.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.211: A file read error occurred while reading an RPC description.NWTILExplanation: A disk read error occurred while reading a remote procedure call (RPC) description.Action: Fix the disk problem. Get a new copy of the NLM or SERVER.RPC, and retry the operation.PAGENUM=740 ID="BP734"NWTILR101: The TIL Runtime is unable to allocate resource tags.NWTILRExplanation: During the startup of NWTILR.NLM, the server did not have enough memory to allocate resource tags.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.PAGENUM=741 ID="BP735"NWTOOLS9: Detach from server name?NWTOOLSExplanation: The user account or User object is about to detach from the specified server. If it detaches from the server, the workstation will lose the connections to all resources residing on that server.Action: To detach from the server, reply "Yes." Otherwise, reply "No."22: Your password has expired. Contact your network supervisor.NWTOOLSAction: Enable the user's account or User object and assign a temporary password to the account so the user can access it.23: Your password has expired on server name. You have number grace logins. Do you want to change it now?NWTOOLSExplanation: The password for the user account has expired. The User object was logged in using one of the grace logins.Action: To change the password now, reply "Yes," then enter a new password in the "Change Password" window. The user may change the password later using the NetWare Tools Change Password menu option.If the user does not change the password, the user will be prompted to on each login until the password is changed or all the grace logins are used.25: You cannot attach to the specified server.NWTOOLSExplanation: A network error occurred when the workstation tried to attach to the server. The server may be down, or the client software may not be communicating with the server.Action: Make sure the server is operating. Check the integrity of the physical network connections. Retry the command.26: The new password fields do not match. Please re-enter the new password.NWTOOLSExplanation: The new password was not retyped exactly as it was typed the first time.Action: Type and then retype the new password again.27: The password on server name cannot be changed.NWTOOLSExplanation: One of the following probably occurred: MARK=BULLETThe configuration of the account does not allow the password to be changed.PAGENUM=742 ID="BP736"A network error occurred on the server or the client that prevented the password from being changed.Action: If the user account has rights to change the password, try changing the password again. If the server continues to reject the new password, determine if a network error has occurred. If the problem persists, contact your Novell Authorized Reseller.29: Do you want to detach from all servers? All network connections will be lost.NWTOOLSExplanation: The user account or User object is about to log out from all servers to which the user is attached. The user will lose the connections to all the network resources.Action: To log out from all servers, reply "Yes." Otherwise, reply "No."31: The network drive cannot be mapped.NWTOOLSExplanation: One of the following probably occurred: MARK=BULLETAn invalid path was entered.The user account or User object is not be connected to the server containing the requested path.The user account or User object does not have rights to the requested path.A network error occurred that did not allow the drive to be mapped.Action: Select the path from the resource list displayed for volumes and directories, then retry the operation. If the desired path is not shown in the list boxes, use the Attach button to attach to the requested server, then select the path from the list boxes and retry the operation. If the user still cannot map the drive, make sure the user has the appropriate rights to the path.33: The printer port cannot be captured.NWTOOLSExplanation: One of the following probably occurred: MARK=BULLETThe printer or queue name entered is invalid.A network error occurred that did not allow the printer to be captured.The user account or User object may not be connected to the server where the printer or queue resides.PAGENUM=743 ID="BP737"Action: Check the printer or queue name, or use the Printer/Queue list box to select an available printer or queue, then retry the operation. If the target printer or queue is not shown in the list box, use the Attach button to attach to the requested server, then select the printer or queue from the list boxes and retry the operation.34: Either you specified an invalid server name or no more connections are available.NWTOOLSMARK=BULLETReason: The server name specified cannot be located.Explanation: An invalid server name was specified or the server name was type incorrectly.Action: Make sure the server name is typed correctly (or use the Server list box to specify a locatable server); then retry the operation.Reason: The server could not support any more workstation.Explanation: The server has reached its maximum number of connections limit.Action: Detach another client from the server and try attaching again.38: You specified an invalid filename or path.NWTOOLSExplanation: A network settings file cannot be found in the given path with the specified filename.Action: Use the list boxes to scan the available drives to locate the correct file. Select that path and filename and retry the operation.41: Load settings couldn't connect to one or more network resources.NWTOOLSExplanation: One of the following may have occurred:MARK=BULLETA server attachment failed because of an invalid server name, user name, or password, or because the server is not availableThe login to a Directory tree failed because of an invalid Directory tree name, user name, or password, or because NetWare Directory Services is not available for the given Directory tree.Unicode tables are not available.A mapping to a drive failed because the server or Directory tree connection was unsuccessful.A capture of a print queue failed because the server or Directory tree connection was unsuccessful.PAGENUM=744 ID="BP738"The setting file is damaged.Action: Use the Directory tree, server, drive, and printer window to make sure the current network settings are correct. If the user is missing a needed setting or connection, make the attachment manually from the respective Window's menu options, then continue with the task.If the user still cannot log into the Directory tree, verify the location of the Unicode tables, then make sure the DPATH statement in the user's CONFIG.SYS file includes the path to the tables. If the CONFIG.SYS file was changed, the user must reboot the workstation for the changes to take effect.If loading of the same settings file fails again but the user can make the connections manually, the user may want to delete the existing settings file and save the settings in a new file.44: The drive is not ready.NWTOOLSExplanation: NetWare Tools could not read from the selected disk drive.Action: Use the DIR command to verify that the specified drive exists and is readable. If the drive is a local diskette drive, make sure a diskette is in the drive and that the drive is closed properly.46: You are using a diskette that is either defective or unformatted.NWTOOLSExplanation: NetWare Tools could not read the diskette.Action: Use the DIR command to verify that the diskette is formatted. The user may need to format the diskette. Or, use a different formatted disk.47: A general disk drive fault has occurred.NWTOOLSExplanation: NetWare Tools could not read from the selected disk drive.Action: Use the DIR command to verify that the specified drive exists and is readable. If the drive specified is a local diskette drive, make sure that the diskette is in the drive and that the drive is closed properly.48: The queue cannot be viewed.NWTOOLSExplanation: The queue name is invalid, or a network error occurred when NetWare Tools tried to read a list of jobs from the selected queue.Action: Use  NETADMIN to verify that the queue exists and that the user object is a member of the Queue User property, then retry the operation.PAGENUM=745 ID="BP739"62: The send command has failed.NWTOOLSExplanation: A network error occurred when the user tried to send a broadcast message. The user or users that were selected may or may not have received the broadcast message that was sent.Action: Send the message again.65: This account has been disabled due to too many unsuccessful attempts to access it.NWTOOLSExplanation: The account has been disabled by intruder detection because too many unsuccessful attempts have been made to log in to the server or the Directory tree.Action: Use NWADMIN or NETADMIN to enable the account, or wait for the account to become enabled again (the default waiting period is 15 minutes).68: Your connection to server_or_tree_name is no longer valid. The current window is now closed.NWTOOLSExplanation: The workstation has lost its connection with a server or a Directory tree on which a userlist or print queue window was dependent. The userlist or print queue window has been closed.Action: Log in to the server or the Directory tree and open the window again.69: Do you want to synchronize your new password on server name?NWTOOLSExplanation: The user may choose to have the password for the username automatically changed on the given server. Synchronizing passwords makes it easier to log in to multiple servers without having to remember multiple passwords.Action: To synchronize the password, reply "Yes;" otherwise, reply "No."70: The new password has been used previously on server name.NWTOOLSExplanation: The password has already been used on the user account. The user account does not allow passwords to be reused.Action: Enter a password that has not been used before, or change the user account to allow passwords to be reused.73: The new password is too short for name.NWTOOLSExplanation: The password specified is too short for the user account.Action: Enter a longer password, or change the account to allow shorter passwords to be used.PAGENUM=746 ID="BP740"77: The network is busy. Try again later.NWTOOLSExplanation: A large amount of network activity is preventing the request from being handled right now. A busy network condition could vary in duration.Action: Try the request again, or wait until there is not as much activity on the network. If the condition occurs frequently, the network may need to be reconfigured. 78: You do not have access rights to queue name.NWTOOLSAction: Add the username to the print queue's user list using NWADMIN or NETADMIN.82: Log out from Directory tree name as user name?NWTOOLSExplanation: The user account or User object is about to log out from the specified Directory tree. The workstation will lose all connections to resources and objects in the Directory tree.Action: To log out, reply "Yes"; otherwise, reply "No." 83: Your password has expired on Directory tree name. Do you want to change it now?NWTOOLSExplanation: The password for the user account has expired. The user logged in using a grace login.Action: To change the password now, reply "Yes," then enter the change password information in the "Change Password" window. The user may change the password later using the Change Password menu option.If the user does not change the password, the user will be prompted for each login until the password is changed or all grace logins are used.84: You specified an invalid Directory tree or server name. You cannot access the Directory tree.NWTOOLSExplanation: The server name entered is not a NetWare Directory Services server, or the specified Directory tree was not found.Action: Enter an NetWare Directory Services server, or select a Directory tree from the Directory tree list box.85: You entered an invalid tree name, username, or password. You cannot log in to the Directory tree.NWTOOLSExplanation: The Directory tree name entered is not valid, the username entered was not found in the current context, or the password was incorrect.Action: Change to the current Directory tree and browse the context until the username is in the Directory tree window. Double-click on the username, enter the password, and try logging in again.PAGENUM=747 ID="BP741"87: You cannot log in to the Directory tree.NWTOOLSExplanation: A network error occurred that did not allow the client to locate and log in to the Directory tree. The Unicode tables may not be accessible.Action: Use the "Change Tree" option with the Directory tree list box to select the Directory tree to change to, then change the context by browsing the Directory tree or by using the "Set Context" option. Make sure the username is in the current context, and try logging in again.If the username can be seen and the error still occurs, do the following:MARK=BULLETMake sure that the workstation is using the most current version of the client requester software.Make sure the server is operating and available on the network.Make sure the user has appropriate user access rights to that server.If the user still cannot see the Directory tree, make sure the DPATH statement in the user's CONFIG.SYS file includes the path to the Unicode tables. If the CONFIG.SYS file was changed, reboot the workstation for the changes to take effect.88: The new password has been used previously on Directory tree name.NWTOOLSExplanation: The password has already been used on the user account. The user account does not allow passwords to be reused.Action: Enter a password that has not been used before, or change the user account to allow passwords to be reused using NWADMIN or NETADMIN.89: The old password you entered is invalid. Your password cannot be changed on server_or_tree_name.NWTOOLSExplanation: The user entered an incorrect old password for the account.Action: Try changing the password again and reenter the old password; or using NWADMIN or NETADMIN, change the password to a word that has not been previously used. (The user can change the password again later as needed.)90: Your password cannot be changed on Directory tree name.NWTOOLSExplanation: One of the following probably occurred: MARK=BULLETThe account configuration does not allow passwords to be changed.PAGENUM=748 ID="BP742"A network error occurred on the server or the client.Action: Try changing the password again. If this problem persists, enter a password that has not been used before; or, using NWADMIN or NETADMIN, change the user account to allow passwords to be reused.Action: 91: You are not attached to server name. Do you want to attach this NetWare server?NWTOOLSExplanation: A NetWare Directory Services connection could not be established.Action: To attach to the server as a bindery user, reply "Yes"; otherwise, reply "No." 93: You cannot get a Directory Services connection to server name. Do you want to attach to the server anyway?NWTOOLSExplanation: The user could not authenticate to a NetWare Directory Services server that is part of the specified Directory tree. The user can still attach to that server and get a bindery connection.Action: To get a bindery connection, reply "Yes" and enter a bindery username and password.95: The Directory tree cannot be changed.NWTOOLSExplanation: A valid Directory tree was specified, but the client could not change its context to the specified Directory tree.Action: Select the Directory tree from the list box and try changing to it again. If this fails, verify the client software and any server that is contained in the specified Directory tree. Also, make sure the client software is the latest version for the server.97: The Directory context cannot be changed.NWTOOLSExplanation: The user entered an invalid context, or the user does not have rights to see the entered context.Action: Try entering the context again. With browse rights, the user can change the context by browsing the Directory tree. Or, change the user's right to allow viewing of the directory tree.101: Do you want to set server name as your primary connection?NWTOOLSExplanation: The user is about to set the specified server as the primary connection.Action: To set the specified server as the primary connection, reply "Yes." Otherwise, reply "No."PAGENUM=749 ID="BP743"102: The server name, username or password entered is invalid. You cannot log in to the server.NWTOOLSAction: Enter the correct server, username, and password. Use the server list box and choose the server from this list of available servers.103: The path to print queue cannot be found. The printer port cannot be captured.NWTOOLSExplanation: NetWare Directory Services was unable to find the path to the given print queue.Action: Using NWADMIN or NETADMIN, make sure the definition of the print queue is correct .104: You do not have an account balance.NWTOOLSExplanation: The user tried to log in to an account with no account balance remaining.Action: Using NWADMIN or NETADMIN, increase the account balance. Also, make sure the server is up and operational.105: Your credit limit has been exceeded.NWTOOLSExplanation: The user tried to log in to an account with no credit available.Action: Using NWADMIN or NETADMIN, give more credit to the account.106: You are trying to log in from too many stations simultaneously.NWTOOLSExplanation: The user tried to log in to an account that has a limit on the number of simultaneous connections. That number of connections has already been reached.Action: Log the user out from one of other connections not in use; or using NWADMIN or NETADMIN, increase the number of simultaneous connections allowed for the account.107: You are trying to log in during an unauthorized time period.NWTOOLSExplanation: The user tried to log in during a time period that is unauthorized for the account. The account has time restrictions.Action: Log in during an authorized time, or using NWADMIN or NETADMIN, change the account's time restrictions.108: You are trying to log in from an unauthorized station.NWTOOLSExplanation: The user tried to log in from an unauthorized station to an account that is limited to specific workstations.Action: Log in from an authorized workstation; or using NWADMIN or NETADMIN, change the account's station restrictions.PAGENUM=750 ID="BP744"109: This account has expired or has been disabled by the supervisor.NWTOOLSExplanation: The user tried to log in to an account that has expired or has been disabled.Action: Using NWADMIN or NETADMIN, reenable the account.110: The network settings file name could not be found. NetWare settings were not loaded.NWTOOLSExplanation: The specified network settings file could not be found. If no path name was given, NetWare Tools searches the current directory.Action: Do one or more of the following:MARK=BULLETVerify that the specified filename exists in the current directory.If the file is in a different directory, specify the full path name and the filename.Using the "Load Settings" menu item, display a dialog that will let you search for and select the settings file.111: The printer modes defined in your print configuration file could not be set.NWTOOLSExplanation: The printer modes could not be set because the print configuration file has printer definition that are not correct.Action: Correct the printer definitions in the print configuration file.112: The mode for the device cannot be found in the PRINTDEF database.NWTOOLSExplanation: Entries in the PRINTDEF database are not correct.Action: Correct the entries in the PRINTDEF database.113: The Unicode tables could not be loaded. You will not be able to access directory services.NWTOOLSExplanation: The Unicode tables are not accessible.Action: Ask the network supervisor for the location of the Unicode tables, then make sure the DPATH statement in the CONFIG.SYS file includes the path to the tables. If the CONFIG.SYS file is changed, reboot the workstation for the changes to take effect.114: There are no unmapped drive letters available.NWTOOLSExplanation: The user tried to map the next available drive letter; however, all drive letters are currently mapped.Action: Delete a drive mapping from a drive letter, then try the request again.PAGENUM=751 ID="BP745"NWXTRACT100: This utility was unable to complete the copy operation. Press Enter to continue, Esc to exit.NWXTRACTExplanation: This error could occur if the decompression routines prematurely reach the end of the file buffer in memory. The workstation may not have enough memory available.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network.101: This utility was unable to read the source file. Press Enter to continue, Esc to exit.NWXTRACTExplanation: The file being extracted from the CD-ROM or Novell diskettes is in compressed format. For some reason, the file cannot be read. While this could be the result of a hardware failure, it is most likely caused by corrupted software. Perhaps the source file is corrupted, or something happened to the disk operating system that would not let it read the file.Action: Make sure that DOS is functioning properly. If it is, try making a copy of the original file from a backup of the Install files that came with the original CD-ROM or CLASS=DISKInstall diskette. If the problem persists, contact your Novell Authorized Reseller.102: This utility was unable to write the destination file. Press Enter to continue, Esc to exit.NWXTRACTExplanation: The destination file cannot be written to. While this could be the result of a hardware failure, it is most likely caused by corrupted software. Perhaps the source or destination file is corrupted, or something happened to the disk operating system that would not let it write the file.Action: Make sure that DOS is functioning properly. If it is, and the destination file had been created prior to this attempt to write to it, try deleting the file and starting over. If neither of these actions resolves the problem, try making a copy of the original source file from a backup of the Install files that came with the original CD-ROM or CLASS=DISKInstall diskette. If the problem persists, contact your Novell Authorized Reseller.103: The source file is not the correct version. Press Enter to continue, Esc to exit.NWXTRACTExplanation: The file being extracted is in compressed format. The file is not a version supported by the decompression routines.Action: Probably no corrective action can be taken; although, the user might want to retry the operation to be sure.PAGENUM=752 ID="BP746"104: The source file could not be copied. Press Enter to continue, Esc to exit.NWXTRACTExplanation: The file being extracted is in compressed format, and the decompression routines were unable to decompress it.Action: Retry the operation, either by exiting and starting over, or by rebooting and starting over.105: This utility was unable to allocate sufficient memory. Press Enter to continue, Esc to exit.NWXTRACTAction: See "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network.106: This utility does not support the source file's format. Press Enter to continue, Esc to exit.NWXTRACTExplanation: The program has tried to decompress a file that cannot be decompressed. The program will not be able to extract that file because either it has been corrupted, or it has been compressed incorrectly.Action: Retry the operation. If the problem persists, try to restore an uncompressed copy of the file from a backup.107: The master data file was not found on drive drive.NWXTRACTExplanation: The master data file FILES.DAT was not found on the CD-ROM or CLASS=DISKInstall diskette. This file is needed for NWXTRACT to execute. If using diskettes, the user may be trying to use the wrong diskette first.Action: Place the correct diskette in the drive. If this error occurs when using the NetWare CD-ROM, contact your Novell Authorized Reseller.108: A destination may not be specified with the /S switch.NWXTRACTExplanation: NWXTRACT does not allow a destination path and the /S switch on the same command line.Action: Either specify a destination or use the /S=SERVER command line switch, not both.109: The master data file on drive drive is not the correct type of file.NWXTRACTExplanation: The FILES.DAT file is not the correct version to allow extraction of the installation files. (Depending on the current setup, this file may be on the CLASS=DISKInstall diskette, on the original NetWare CD-ROM, or on a network directory.)Action: When copying NWXTRACT on to the network, make sure to run it only on the correct CD-ROM or CLASS=DISKInstall diskettes containing a current FILES.DAT file.PAGENUM=753 ID="BP747"110: The specified drive is invalid.NWXTRACTExplanation: The user specified an invalid drive. Currently NWXTRACT will support only drives A through Z.Action: Enter everything correctly.111: The specified file or group was not found.NWXTRACTExplanation: The user specified a file or group of files that are not on the NetWare CD-ROM or CLASS=DISKInstall diskettes.Action: Enter the file or group name correctly. Then retry the operation.112: An error occurred while copying the file's extended attributes. Press Enter to continue, Esc to exit.NWXTRACTExplanation: This error can occur when running NWXTRACT under OS/2 and it fails to copy the specified file's extended attributes. The source file may be corrupted, or the workstation may not have enough memory.Action: Try one or both of the following:MARK=BULLETMake sure the print server is operating. Make sure that NET.CFG sockets are available. Close applications that are currently running. Free up hard disk space by deleting unnecessary programs. When using multiple disk partitions, consider moving the OS/2 swapper file to a larger partition. Try adding RAM, reducing the configuration options in the CONFIG.SYS file, or removing optional device drivers from the CONFIG.SYS file. After completing these actions, shut down OS/2 then reboot the system. Run NWXTRACT again. If the problem persists, contact your Novell Authorized Reseller.When suspecting corruption, try making a copy of the original file from a backup of the Install files that came with the original CD-ROM or CLASS=DISKInstall diskette. If that fails, try using the same source path and filename as before; however, this time try copying the file from the source using NCOPY. This may work if the file is not in compressed format. However, if the file is compressed, NCOPY may copy it but will not decompress it. If the problem persists, contact your Novell Authorized Reseller.113: An error occurred creating file name. Press Enter to continue, Esc to exit.NWXTRACTExplanation: NWXTRACT failed to create the file being extracted at the destination. This could be caused by one of the following:MARK=BULLETA file system problem occurred at the destination.PAGENUM=754 ID="BP748"The workstation does not have any file handles left to create the file.Action: Make sure DOS is functioning properly. If it is, make sure the destination has enough disk space to copy the file. Also, if the workstation has other files currently opened, close some of the files and retry the operation.901: You are not attached to the specified server.NWXTRACTAction: See message IDREF="FM84261""901: You are not attached to the specified server." in Appendix C.903: The command line syntax is invalid.NWXTRACTAction: See message IDREF="FM18860""903: The command line syntax is invalid." in Appendix C.905: This utility was unable to initialize the country information.NWXTRACTAction: See message IDREF="FM55337""905: This utility was unable to initialize the country information." in Appendix C.912: The specified file cannot be found.NWXTRACTAction: See message IDREF="FM74299""912: The specified file cannot be found." in Appendix C.917: This utility was unable to set the context.NWXTRACTAction: See message IDREF="FM32126""917: This utility was unable to set the context." in Appendix C.920: This utility was unable to allocate <number> bytes of memory.NWXTRACTAction: See message IDREF="FM30331""920: This utility was unable to allocate number bytes of memory." in Appendix C.970: The attempt to open the Unicode table files failed.NWXTRACTAction: See message IDREF="FM15675""970: The attempt to open the Unicode table files failed." in Appendix C.971: The workstation does not have enough memory to load the Unicode table files.NWXTRACTAction: See message IDREF="FM55341""971: The workstation does not have enough memory to load the Unicode table files." in Appendix C.972: Access to the Unicode table files was denied.NWXTRACTAction: See message IDREF="FM90152""972: Access to the Unicode table files was denied." in Appendix C.PAGENUM=755 ID="BP749"973: The Unicode table files cannot be found in the NLS directory or in the search path. Code page: <number>  Country:  <number>NWXTRACTAction: See the action in message IDREF="FM62778""973: The Unicode table files cannot be found in the NLS directory or in the search path. Code page: number Country: number" in Appendix C.974: The Unicode table files are corrupt.NWXTRACTAction: See the action in message IDREF="FM63405""974: The Unicode table files are corrupt." in Appendix C.975: The Unicode table files cannot be opened because there are already too many open files. Close some files or modify your CONFIG.SYS file.NWXTRACTAction: See the action in message IDREF="FM49793""975: The Unicode table files cannot be opened because there are already too many open files. Close some files or modify your CONFIG.SYS file." in Appendix C.998: The message file found (<utility_name>.MSG) is an incorrect version. The correct version is <number>. See your network supervisor for assistance.NWXTRACTAction: See the action in message IDREF="FM91957""998: The message file found (utility_name.MSG) is an incorrect version. The correct version is number. See your network supervisor for assistance." in Appendix C.999: The message file for this utility cannot be found.NWXTRACTAction: See the action message IDREF="FM69424""999: The message file for this utility cannot be found." in Appendix C.PAGENUM=756 ID="BP750"NetWare Client for OS/2 INSTALLThis chapter includes system messages and explanations for all NetWare ClientTM for OS/2* drivers and daemons. REQ0106: An error occurred during attempt to get shared memory. NetWare Client for OS/2 INSTALLExplanation: DDAEMON.EXE attempted to access the daemon's shared memory, but failed. At this point, the program has verified that the shared memory exists, but is unable to access it. This may be an internal program error. Action: Try rebooting your system. If the problem persists, call your Novell Authorized Reseller. REQ0107: An error occurred during attempt to allocate a shared segment. NetWare Client for OS/2 INSTALLExplanation: DDAEMON.EXE tried to create shared memory, but none is available. This error usually occurs when the device drivers and applications currently running on your system require more memory than your system has available. Action: Try adding RAM, reducing your configuration options in the CONFIG.SYS file (for example, reducing the size of DIRCACHE), removing optional device drivers from the CONFIG.SYS file, and freeing up some hard disk space by deleting unnecessary programs. If you are using multiple disk partitions, consider moving the OS/2 swapper file to a larger partition. Disk compression utilities may also be available that can help resolve this problem. After completing these actions, shut down OS/2; then reboot the system. If the problem persists, contact your Novell Authorized Reseller.REQ0108: The daemon cannot access the Link Support Layer. Error: <code>. NetWare Client for OS/2 INSTALLExplanation: DDAEMON.EXE cannot find the Link Support device driver LSL.SYS. Action: Make sure that the device driver LSL.SYS has been properly entered in the CONFIG.SYS file. If so, check the messages displayed by the LSL for any errors or warnings, and correct the problems indicated. Try again. If this error persists, call your Novell Authorized Reseller.PAGENUM=757 ID="BP751"REQ0109: The DDAEMON is already loaded. NetWare Client for OS/2 INSTALLExplanation: DDAEMON.EXE tried to create shared memory for the first time, but the memory already exists. Another daemon is already running. The attempt to create shared memory is terminated. Action: Make sure that you are not trying to run multiple copies of the daemon. Typically the daemon is run from the CONFIG.SYS file at system startup and does not need to be executed again.REQ0204: The system does not have enough memory for socket tables. NetWare Client for OS/2 INSTALLExplanation: OS/2 lacks sufficient system memory for IPX to allocate memory for its socket tables. Action: Try adding RAM, reducing your configuration options in the CONFIG.SYS file (for example, reducing the size of DIRCACHE), removing optional device drivers from the CONFIG.SYS file, and freeing up some hard disk space by deleting unnecessary programs. If you are using multiple disk partitions, consider moving the OS/2 swapper file to a larger partition. Disk compression utilities may also be available that can help resolve this problem. After completing these actions, shut down OS/2; then reboot the system. If the problem persists, contact your Novell Authorized Reseller.REQ0205: The LAN support module could not be installed. NetWare Client for OS/2 INSTALLExplanation: Either the LSL.SYS driver failed to load, or the "DEVICE=" statement is missing from the CONFIG.SYS file.Action: Either correct the problem that kept the LSL.SYS driver from loading (indicated in an error message preceding this one), or add the "DEVICE=" statement to the CONFIG.SYS file. REQ0206: The IPX MLID could not be installed. NetWare Client for OS/2 INSTALLExplanation: Either the Multiple Link Interface Driver (MLID) specified in the CONFIG.SYS failed to load, or the "DEVICE=" statement for an MLID is missing from the CONFIG.SYS file. Action: Either correct the problem that kept the MLID from loading (indicated in an error message preceding this one), or add the "DEVICE=" statement to the CONFIG.SYS file. REQ0207: The configured LAN-A driver does not support IPX. NetWare Client for OS/2 INSTALLExplanation: The Multiple Link Interface Driver (MLID) to which IPX.SYS attempted to bind does not support IPX-based data transmissions. Action: Bind IPX to an MLID that supports IPX-based data transmissions.PAGENUM=758 ID="BP752"REQ0208: The IPX protocol handler cannot be registered. NetWare Client for OS/2 INSTALLExplanation: IPX cannot register with the LSL.SYS driver because the LSL is servicing its maximum number of protocol stacks. Action: Remove the "DEVICE=" statements for any unnecessary protocol stacks from the CONFIG.SYS file. REQ0209: The IPX entry point cannot be initialized. NetWare Client for OS/2 INSTALLExplanation: The IPX and link support layer (LSL) versions may not be compatible versions.Action: Make sure that the IPX.SYS driver and LSL.SYS driver are compatible. If they are not, obtain compatible drivers from your Novell Authorized Reseller. If this is not the problem, contact your Novell Authorized Reseller for customer assistance.REQ0210: An internal error occurred. The IPX router socket cannot be opened. NetWare Client for OS/2 INSTALLExplanation: IPX was unable to open the router socket due to an internal program error. Action: Try again. If the problem persists, contact your Novell Authorized Reseller.REQ0211: An internal error occurred. A router selector cannot be allocated. NetWare Client for OS/2 INSTALLExplanation: IPX was unable to allocate an OS/2 router selector due to an internal program error. Action: Try again. If the problem persists, contact your Novell Authorized Reseller.REQ0212: The system has insufficient memory to allocate a router. NetWare Client for OS/2 INSTALLExplanation: OS/2 cannot access sufficient system memory for IPX routing purposes. Action: Try adding RAM, reducing your configuration options in the CONFIG.SYS file (for example, reducing the size of DIRCACHE), removing optional device drivers from the CONFIG.SYS file, and freeing up some hard disk space by deleting unnecessary programs. If you are using multiple disk partitions, consider moving the OS/2 swapper file to a larger partition. Disk compression utilities may also be available that can help resolve this problem. After completing these actions, shut down OS/2; then reboot the system. If the problem persists, contact your Novell Authorized Reseller.REQ0213: Router memory is exhausted. NetWare Client for OS/2 INSTALLExplanation: IPX did not have enough memory previously allocated for routing purposes. Action: Increase the size of the IPX router memory in the NET.CFG "ROUTER MEM" statement.PAGENUM=759 ID="BP753"REQ0214: An internal error prevented CGroup variable initialization. NetWare Client for OS/2 INSTALLExplanation: An internal program error has occurred. IPX was unable to initialize internal variables. Action: Try again. If the problem persists, contact your Novell Authorized Reseller.REQ0215: An internal error prevented DosHlp variable initialization. NetWare Client for OS/2 INSTALLExplanation: OS/2 internal variables were either incomplete or invalid. Action: Try again. If the problem persists, contact your Novell Authorized Reseller.REQ0216: IPX cannot register with OS/2 for PDD-to-VDD communications. NetWare Client for OS/2 INSTALLExplanation: This is an internal program error. IPX cannot register with OS/2 for VIPX.SYS driver support. Action: Try again. If the problem persists, contact your Novell Authorized Reseller.REQ0217: The IPX device driver is not running. NetWare Client for OS/2 INSTALLExplanation: Either IPX.SYS encountered a fatal error during system initialization, or the "DEVICE=[path]IPX.SYS" statement was missing from the CONFIG.SYS file. If the problem is a fatal error, another message should precede this one that identifies the specific error that occurred.Action: Either resolve the fatal problem (indicated in a preceding message), or add the "DEVICE=" statement to the CONFIG.SYS file; then try again. If the problem persists, contact your Novell Authorized Reseller.REQ0231: The default protocol configuration option is not used for IPX. NetWare Client for OS/2 INSTALLExplanation: IPX cannot be configured as a default protocol stack. Action: Remove this option statement from the NET.CFG file.REQ0232: The prescan protocol configuration option is not used for IPX. NetWare Client for OS/2 INSTALLExplanation: IPX cannot be configured as a prescan protocol stack. Action: Remove this option statement from the NET.CFG file.REQ0233: The OS/2 version number cannot be found; OS/2 v2.0 is assumed. NetWare Client for OS/2 INSTALLExplanation: IPX's query of OS/2 for the version number returned a value that did not match the value it expected to receive. Action: Make sure the OS/2 version installed on the machine is v2.0 or later.PAGENUM=760 ID="BP754"REQ0304: An LSL error occurred. NET.CFG buffers are too big for ECB pool.NetWare Client for OS/2 INSTALLExplanation: The configured buffer size for the Link Support component is too large. Total available buffer space is around 60 KB, but the Link Support Layer (LSL) is unable to allocate even one buffer of the requested size in its buffer space. See "BOOK="cncptenu" COLLECTION="nw41"Link Support Layer" in Concepts for more information about LSL.Action: Reduce the Link Support component's buffer size in the NET.CFG file. It is more important to have several smaller buffers available than one large one. It is a waste of system memory to configure buffers much larger than the communications media can support.REQ0305: The Link Support module (LSL) could not install the AES timer.NetWare Client for OS/2 INSTALLExplanation: The Link Support Layer (LSL) could not register its timer handler with the operating system because the maximum number of handlers have already been installed. This timer handler is a critical component of NetWare Client for OS/2, and none of the Novell-supplied communication handlers can be expected to work properly without it. See "BOOK="cncptenu" COLLECTION="nw41"Link Support Layer" in Concepts for more information about LSL.Action: Previously installed device drivers (those entered before LSL.SYS in the CONFIG.SYS file) have used all available timer resources. Identify those device drivers and either remove or reconfigure them. Since the Requestor's communications handlers all use a common timer service in the LSL, only one available timer handler is required for proper operation. If you are unable to resolve this problem, contact your Novell Authorized Reseller.REQ0306: The Link Support module could not initialize its call gate.NetWare Client for OS/2 INSTALLExplanation: The Link Support module could not register its entry point with the operating system. This entry point is vital to most of NetWare Client for OS/2's communications components, and its absence will cause them to fail. The most likely cause of this error is a previously loaded device driver that is using too many kernel resources. Action: Try removing application device drivers installed before LSL.SYS in the CONFIG.SYS file. It is highly unlikely that a device driver from the OS/2 base system has caused this error. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=761 ID="BP755"REQ0404: NetBIOS error occurred. Link Support module cannot be installed. NetWare Client for OS/2 INSTALLExplanation: NetBIOS could not open or communicate with the Link Support LINKSUP_ device driver. This can happen if the Link Support Layer (LSL) driver has not been properly installed or if you are using the wrong version of the driver. See "BOOK="cncptenu" COLLECTION="nw41"Link Support Layer" in Concepts for more information about LSL.Action: Make sure that the device driver LSL.SYS has been properly entered in the CONFIG.SYS file. If so, check the messages displayed by the LSL for any errors or warnings, and correct the problems indicated. If the Link Support device driver is initializing properly, the problem is with incompatible versions of the software. NetBIOS and Link Support are usually installed together from a single installation diskette. Try reinstalling them. If the problem persists, contact your Novell Authorized Reseller.REQ0405: NetBIOS error occurred. The IPX module is not installed. NetWare Client for OS/2 INSTALLExplanation: NetBIOS could not open or communicate with the Link Support LINKSUP_ device driver. This can happen if the Link Support Layer (LSL) driver has not been properly installed or if you are using the wrong version of the driver. See "BOOK="cncptenu" COLLECTION="nw41"Link Support Layer" in Concepts for more information about LSL.Action: Make sure that the device driver LSL.SYS has been properly entered in the CONFIG.SYS file. If so, check the messages displayed by the LSL for any errors or warnings, and correct the problems indicated. If the Link Support device driver is initializing properly, the problem is with incompatible versions of the software. NetBIOS and Link Support are usually installed together from a single installation diskette. Try reinstalling them. If the problem persists, contact your Novell Authorized Reseller.REQ0406: The NetBIOS call gate cannot be initialized. NetWare Client for OS/2 INSTALLExplanation: This is an internal program error. Action: Try again. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=762 ID="BP756"REQ0407: NetBIOS error occurred. The program cannot initialize local NCBs. NetWare Client for OS/2 INSTALLExplanation: Insufficient memory is available for the NCBs requested. Usually this error is caused by incorrect configuration information in the NET.CFG file. However, the underlying problem could also be a lack of global system resources in the OS/2 Global Descriptor Table. Action: Reduce the number of commands in the NetBIOS section of the CONFIG.SYS file. (The default number of commands is 12; the maximum allowed is 25.) You also might be able to reduce the number of node names (possible range is 0-126). Additional possibilities include adding RAM, reducing your configuration options (for example, reducing the size of DIRCACHE) or removing optional device drivers from the CONFIG.SYS file, and freeing up some hard disk space by deleting unnecessary programs. If you are using multiple disk partitions, consider moving the OS/2 swapper file to a larger partition. Disk compression utilities may also be available that can help resolve this problem. After completing these actions, shut down OS/2 and then reboot the system. If the problem persists, contact your Novell Authorized Reseller.REQ0408: NetBIOS emulator parameters are too large for the memory pool. NetWare Client for OS/2 INSTALLExplanation: Insufficient memory is available for all of the control tables needed by the NetBIOS emulator. Action: The amount of table space available to the NetBIOS emulator cannot be increased. The only way to solve this problem is to reduce the number of NetBIOS resources you are requesting. You can do this by modifying the NETBIOS parameters in the NET.CFG file. If the problem persists, contact your Novell Authorized Reseller.REQ0409: Incompatible versions of OS/2 and NetBIOS are running. NetWare Client for OS/2 INSTALLExplanation: You are attempting to run NetBIOS v2.10 on some version of OS/2 earlier than OS/2 v2.1. Action: Either install OS/2 v2.1 to run with NetBIOS v2.10, or install a different version of NetWare NetBIOS to match your OS/2 version.REQ0504: The SPX module is not installed. NetWare Client for OS/2 INSTALLExplanation: The NMPIPE.SYS driver could not open or communicate with the SPX.SYS driver. Action: Make sure that the SPX.SYS driver has been properly entered in the CONFIG.SYS file. PAGENUM=763 ID="BP757"If so, check the messages displayed by the driver for any errors or warnings, and correct the problems indicated; then try again. If the problem persists, contact your Novell Authorized Reseller.REQ0505: The IPX module is not installed. NetWare Client for OS/2 INSTALLExplanation: NMPIPE.SYS could not open or communicate with the IPX.SYS driver. Action: Make sure that the IPX.SYS driver has been properly entered in the CONFIG.SYS file. If so, check the messages displayed by the driver for any errors or warnings, and correct the problems indicated; then try again. If the problem persists, contact your Novell Authorized Reseller.REQ0519: An incorrect OS/2 version is being used. NetWare Client for OS/2 INSTALLExplanation: Either the DosGetVersion call failed (an internal program error), or the OS/2 version currently running is not v2.0 or later. Action: Make sure the client OS and NMPIPE.SYS driver are compatible versions. If the problem persists, contact your Novell Authorized Reseller. REQ0520: The driver cannot register the PDD for VDD-to-PDD communications. NetWare Client for OS/2 INSTALLExplanation: NMPIPE.SYS could not register IPX as a PDD so that PDD to VDD communication may take place. Action: Make sure the IPX.SYS driver has been properly entered in the CONFIG.SYS file. If so, check the messages displayed by the driver for any errors or warnings, and correct the problems indicated. Also make sure the OS/2 version is v2.0 or later; then try again. If the problem persists, contact your Novell Authorized Reseller.REQ0613: Invalid characters were specified in COMPUTERNAME. NetWare Client for OS/2 INSTALLExplanation: The Named Pipes server name specified after NPDAEMON.EXE is invalid. Action: Make sure the server name is not more than 15 characters and is composed of letters, numbers, and these special characters: !#$%&()-.@^_\Q{}~REQ0614: An error occurred during attempt to initialize NPCALLS.DLL. NetWare Client for OS/2 INSTALLExplanation: The NPDaemon could not initialize NPCALLS.DLL. Action: Make sure the NPCALLS.DLL file in the NetWare Client for OS/2 directory is included in the LIBPATH statement of the CONFIG.SYS file. If you are running Named Pipes, make sure the NMPIPE.SYS driver and NPSERVER.SYS are correctly configured in the CONFIG.SYS file.PAGENUM=764 ID="BP758"REQ0615: The Named Pipes daemon could not be registered. Error: <code>. NetWare Client for OS/2 INSTALLExplanation: The NPDaemon could not open or communicate with the NMPIPE.SYS driver. Action: Make sure the NMPIPE.SYS driver has been properly entered in the CONFIG.SYS file. If so, check the messages displayed by the driver for any errors or warnings, and correct the problems. Try again. If the problem persists, contact your Novell Authorized Reseller.REQ0616: An error occurred during attempt to allocate shared memory. NetWare Client for OS/2 INSTALLExplanation: The NPDaemon could not allocate shared memory. Action: Try adding RAM, reducing your configuration options in the CONFIG.SYS file (for example, reducing the size of DIRCACHE), removing optional device drivers from the CONFIG.SYS file, and freeing up some hard disk space by deleting unnecessary programs. If you are using multiple disk partitions, consider moving the OS/2 swapper file to a larger partition. Disk compression utilities may also be available that can help resolve this problem. After completing these actions, shut down OS/2; then reboot the system. If the problem persists, contact your Novell Authorized Reseller.REQ0617: An error occurred during attempt to allocate the ECB pool. NetWare Client for OS/2 INSTALLExplanation: The NPDaemon could not allocate memory for the ECB pool. Action: Try adding RAM, reducing your configuration options in the CONFIG.SYS file (for example, reducing the size of DIRCACHE), removing optional device drivers from the CONFIG.SYS file, and freeing up some hard disk space by deleting unnecessary programs. If you are using multiple disk partitions, consider moving the OS/2 swapper file to a larger partition. Disk compression utilities may also be available that can help resolve this problem. After completing these actions, shut down OS/2; then reboot the system. If the problem persists, contact your Novell Authorized Reseller.REQ0618: An error occurred during attempt to create a system semaphore. NetWare Client for OS/2 INSTALLExplanation: A DosCreateSem call failed. An internal program error may have occurred. Action: Try again. If the error persists, contact your Novell Authorized Reseller.REQ0619: An error occurred during attempt to create a thread. NetWare Client for OS/2 INSTALLExplanation: A beginthread call failed. An internal program error may have occurred.Action: Try again. If the error persists, contact your Novell Authorized Reseller.PAGENUM=765 ID="BP759"REQ0620: A dynamic socket could not be opened. Error: <code>. NetWare Client for OS/2 INSTALLExplanation: The NPDaemon failed to open a dynamic socket. Action: Increase the socket count specified in the NET.CFG file; then reboot the system and try again. If the problem persists, contact your Novell Authorized Reseller. REQ0621: A well-known socket could not be opened. Error: <code>. NetWare Client for OS/2 INSTALLExplanation: The NPDaemon could not open Netware's registered Named Pipe socket; the socket may already be in use. Action: Increase the SPX socket count in the NET.CFG and shut down OS/2; then reboot the system.REQ0622: The NPDaemon cannot get the internet address. Error: <code>. NetWare Client for OS/2 INSTALLExplanation: An IpxGetInternetworkAddress call failed. Action: Make sure the IPX.SYS driver has been properly entered in the CONFIG.SYS file. If so, check the messages displayed by the driver for any errors or warnings, and correct the problems indicated. Also make sure the IPXCALLS.DLL file is in the NetWare Client for OS/2 directory; then try again. If the problem persists, notify your Novell Authorized Reseller.REQ0623: The NPDaemon cannot get the local target. Error: <code>. NetWare Client for OS/2 INSTALLExplanation: An IpxGetLocalTarget call failed. Action: Make sure the IPX.SYS driver has been properly entered in the CONFIG.SYS file. If so, check the messages displayed by the driver for any errors or warnings, and correct the problems indicated. Also make sure the IPXCALLS.DLL file is in the NetWare Client for OS/2 directory; then try again. If the problem persists, contact your Novell Authorized Reseller.REQ0624: The service advertising function failed. Error: <code>. NetWare Client for OS/2 INSTALLExplanation: An IpxSend call to advertise this workstation as Named Pipe Server failed. Action: Make sure the IPX.SYS driver has been properly entered in the CONFIG.SYS file. If so, check the messages displayed by the driver for any errors or warnings, and correct the problems indicated. Also make sure the IPXCALLS.DLL file is in the NetWare Client for OS/2 directory; the try again. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=766 ID="BP760"REQ0625: The broadcast socket cannot be opened. Error: <code>. NetWare Client for OS/2 INSTALLExplanation: The broadcast socket cannot be opened. This is a registered socket by which SAPs can be received. Possibly this socket has already been opened. Action: Increase the socket count in the NET.CFG file and shut down OS/2 and then reboot the system. If the problem persists, contact your Novell Authorized Reseller. REQ0626: An error occurred during attempt to get code page information. NetWare Client for OS/2 INSTALLExplanation: A call to DosGetCtryInfo failed. This may be an internal program error. Action: Make sure the OS/2 is version 2.0 or later. If so, and the problem persists, contact your Novell Authorized Reseller.REQ0628: Memory cannot be allocated for turbo buffers. NetWare Client for OS/2 INSTALLExplanation: The NPDaemon could not allocate memory for turbo buffers. Action: Try adding RAM, reducing your configuration options in the CONFIG.SYS file (for example, reducing the size of DIRCACHE), removing optional device drivers from the CONFIG.SYS file, and freeing up some hard disk space by deleting unnecessary programs. If you are using multiple disk partitions, consider moving the OS/2 swapper file to a larger partition. Disk compression utilities may also be available that can help resolve this problem. After completing these actions, shut down OS/2; then reboot the system. If the problem persists, contact your Novell Authorized Reseller.REQ0629: A connection thread died abnormally. Error: <code>. NetWare Client for OS/2 INSTALLExplanation: The connection controller thread died unexpectedly. Action: Make sure that the SPX.SYS driver has been properly entered in the CONFIG.SYS file. If so, check the messages displayed by the driver for any errors or warnings, and correct the problems indicated. Also make sure all of your Named Pipe drivers are within the same major version (for example, v2.x); then try again. If the problem persists, contact your Novell Authorized Reseller.REQ0630: The specified computer name is already registered on the internet. NetWare Client for OS/2 INSTALLExplanation: The Named Pipes server name specified in the CONFIG.SYS file has already been used on the network. Action: Use a different server name.PAGENUM=767 ID="BP761"REQ0631: The receive buffer manager died abnormally. Error: <code>. NetWare Client for OS/2 INSTALLExplanation: The receive buffer manager thread died unexpectedly. Action: Make sure that your Named Pipes drivers are within the same major version (for example, v2.x). If so, try adding RAM, reducing your configuration options in the CONFIG.SYS file (for example, reducing the size of DIRCACHE), removing optional device drivers from the CONFIG.SYS file, and freeing up some hard disk space by deleting unnecessary programs. If you are using multiple disk partitions, consider moving the OS/2 swapper file to a larger partition. Disk compression utilities may also be available that can help resolve this problem. After completing these actions, shut down OS/2; then reboot the system. If the problem persists, contact your Novell Authorized Reseller.REQ0635: General Service Query for Named Pipe Servers failed. Error: %1.%0NetWare Client for OS/2 INSTALLExplanation: A call to IpxSend to issue a general service query for named Pipe Servers failed.Action: Make sure the IPX.SYS driver has been properly entered in the CONFIG.SYS file. If so, check the messages displayed by the driver for any errors or warnings, and correct the problems indicated. Also make sure the IPXCALLS.DLL file is in the NetWare Client for OS/2 directory.Try again. If the problem persists, contact your Novell authorized reseller.REQ0636: An error occurred while obtaining the IPX card table.%0NetWare Client for OS/2 INSTALLExplanation: A call to the npserver.sys driver to obtain the IPX card table failed.Action: Make sure the IPX.SYS driver and the NPSERVER.SYS driver have been properly entered in the CONFIG.SYS file. If so, check the messages displayed by the drivers for any errors or warnings, and correct the problems indicated. Also make sure the IPXCALLS.DLL and NPCALLS.DLL files are in the NetWare Client for OS/2 directory. Try again. If the problem persists, contact your Novell authorized reseller.REQ0704: The SPX module is not installed. NetWare Client for OS/2 INSTALLExplanation: The Named Pipes daemon could not open or communicate with the SPX.SYS driver. Action: Make sure that the SPX.SYS driver has been properly entered in the CONFIG.SYS file. PAGENUM=768 ID="BP762"If so, check the messages displayed by the driver for any errors or warnings, and correct the problems indicated; then try again. If the problem persists, contact your Novell Authorized Reseller.REQ0705: The IPX module is not installed. NetWare Client for OS/2 INSTALLExplanation: The Named Pipes daemon could not open or communicate with the IPX.SYS driver. Action: Make sure that the IPX.SYS driver has been properly entered in the CONFIG.SYS file. If so, check the messages displayed by the driver for any errors or warnings, and correct the problems indicated; then try again. If the problem persists, contact your Novell Authorized Reseller.REQ0719: An incorrect OS/2 version is being used. NetWare Client for OS/2 INSTALLExplanation: The DosGetVersion call failed (which would indicate an internal program error) or the OS/2 version currently running is not v2.0 or later. Action: Make sure that the client OS and NMPIPE.SYS driver are compatible; then try again. If the problem persists, contact your Novell Authorized Reseller. REQ0806: The program cannot get code page information. Error: <code>. NetWare Client for OS/2 INSTALLExplanation: The OS/2 system is not returning code page information. This may be an internal program error. Action: Try again. If the problem persists, contact your Novell Authorized Reseller.REQ0807: The Requester device driver and daemon are incompatible versions. NetWare Client for OS/2 INSTALLExplanation: The most likely cause of this problem is that NWDAEMON.EXE and NWREQ.SYS driver were not installed from the same installation disk. Action: Install NetWare Client for OS/2 driver again, making sure it is from the correct installation disk.REQ0808: The worker DLL cannot be registered. Error: <code>. NetWare Client for OS/2 INSTALLExplanation: The NWWORKER.DLL could not register with NetWare Client for OS/2. This may be an internal program error. Action: Try again. If the problem persists, contact your Novell Authorized Reseller.REQ0809: The broadcast handler cannot be registered. Error: <code>. NetWare Client for OS/2 INSTALLExplanation: This may be an internal program error. Action: Try again. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=769 ID="BP763"REQ0810: The program cannot get system information. Error: <code>. NetWare Client for OS/2 INSTALLExplanation: The OS/2 system is not returning system information. This may be an internal program error. Action: Try again. If the problem persists, contact your Novell Authorized Reseller.REQ0811: The janitor thread priority cannot be set. Error: <code>. NetWare Client for OS/2 INSTALLExplanation: The janitor thread is set to run at regular priority. The system had trouble setting the priority. Action: Ignore the error.REQ0812: The janitor daemon cannot be registered. Error: <code>. NetWare Client for OS/2 INSTALLExplanation: This may be an internal program error. Action: Try again. If the problem persists, contact your Novell Authorized Reseller.REQ0813: The program cannot get the current drive map. Error: <code>. NetWare Client for OS/2 INSTALLExplanation: The OS/2 system is not returning the current drive map. This may be an internal program error. Action: Try again. If the problem persists, contact your Novell Authorized Reseller.REQ0814: The program cannot set the current drive map. Error: <code>. NetWare Client for OS/2 INSTALLExplanation: The OS/2 system is not setting the current drive map. This may be an internal program error. Action: Try again. If the problem persists, contact your Novell Authorized Reseller.REQ0815: The program cannot get the connection ID. Error: <code>. NetWare Client for OS/2 INSTALLExplanation: NetWare Client for OS/2 tried to locate a NetWare server when it initialized. Either no servers are currently running or a cabling problem exists. Action: Make sure the NetWare server is running and functioning properly. Also make sure the OS/2 machine has a working connection to the network; then try again. If the problem persists, contact your Novell Authorized Reseller.REQ0816: An error occurred during attempt to initialize the cache. NetWare Client for OS/2 INSTALLExplanation: The caching function is not working. This may be an internal program error. Action: Try again. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=770 ID="BP764"REQ0817: The daemon could not boost the thread priority. NetWare Client for OS/2 INSTALLExplanation: The thread is set to run at a greater priority. The system had trouble setting the priority. Action: Ignore the error.REQ0818: The daemon could not register the DosBox handler. NetWare Client for OS/2 INSTALLExplanation: This may be an internal program error. Action: Try again. If the problem persists, contact your Novell Authorized Reseller.REQ0820: Not enough memory for diagnostic daemon. Error: <code>. NetWare Client for OS/2 INSTALLExplanation: The NWDaemon program tried to allocate memory from the system for the diagnostic thread to use as a stack, but the system returned an error. Action: Try adding RAM, reducing your configuration options in the CONFIG.SYS file (for example, reducing the size of DIRCACHE), removing optional device drivers from the CONFIG.SYS file, and freeing up some hard disk space by deleting unnecessary programs. If you are using multiple disk partitions, consider moving the OS/2 swapper file to a larger partition. Disk compression utilities may also be available that can help resolve this problem. After completing these actions, shut down OS/2; then reboot the system. If the problem persists, contact your Novell Authorized Reseller.REQ0821: The diagnostic daemon cannot be started. Error: <code>. NetWare Client for OS/2 INSTALLExplanation: The NWDaemon tried to start the diagnostic thread but the system encountered an error condition. The system may have too many threads already running, or this may be an internal program error. Action: Try closing other applications that are currently running. If the problem persists, contact your Novell Authorized Reseller.REQ0822: The diagnostic daemon priority cannot be changed. Error: <code>. NetWare Client for OS/2 INSTALLExplanation: The diagnostic thread is set to run at regular priority. The system had trouble setting the priority. Action: Ignore the error.PAGENUM=771 ID="BP765"REQ0823: Not enough memory to start a new thread. Error: <code>. NetWare Client for OS/2 INSTALLExplanation: The NWDaemon could not allocate memory from the system to create a thread for a new task. Action: Try adding RAM, reducing your configuration options in the CONFIG.SYS file (for example, reducing the size of DIRCACHE), removing optional device drivers from the CONFIG.SYS file, and freeing up some hard disk space by deleting unnecessary programs. If you are using multiple disk partitions, consider moving the OS/2 swapper file to a larger partition. Disk compression utilities may also be available that can help resolve this problem. After completing these actions, shut down OS/2; then reboot the system. If the problem persists, contact your Novell Authorized Reseller.REQ0824: The SPX send thread cannot be started. Error: <code>. NetWare Client for OS/2 INSTALLExplanation: This may be an internal program error. Action: Try again. If the problem persists, contact your Novell Authorized Reseller.REQ0825: The SPX receive thread cannot be started. Error: <code>. NetWare Client for OS/2 INSTALLExplanation: This may be an internal program error. Action: Try again. If the problem persists, contact your Novell Authorized Reseller.REQ0826: The SFT 3 handler cannot be registered. NetWare Client for OS/2 INSTALLExplanation: This may be an internal program error. Action: Try again. If the problem persists, contact your Novell Authorized Reseller.REQ0827: Packet Burst cannot be initialized. NetWare Client for OS/2 INSTALLExplanation: This may be an internal program error. Action: Try again. If the problem persists, contact your Novell Authorized Reseller.ID="FM69340"REQ0843: Not enough memory for a network management thread (<error code>). NetWare Client for OS/2 INSTALLExplanation: The NWDaemon tried to allocate memory from the system for a thread to initialize network management, but memory was not available. Network management cannot be initialized. Action: Try adding RAM, reducing your configuration options in the CONFIG.SYS file (for example, reducing the size of DIRCACHE), removing optional device drivers from the CONFIG.SYS file, and freeing up some hard disk space by deleting unnecessary programs. PAGENUM=772 ID="BP766"If you are using multiple disk partitions, consider moving the OS/2 swapped file to a larger partition. Disk compression utilities may also be available that can help resolve this problem. After completing these actions, shut down OS/2; then reboot the system. If the problem persists, contact your Novell Authorized Reseller.REQ0844: A named pipe cannot be started for network management (<error code>). NetWare Client for OS/2 INSTALLExplanation: The NWDaemon could not allocate a named pipe. Network management will not be supported until the computer is rebooted. This error could result from a variety of causes. Named Pipes or SPX may not be loaded, one of your drivers may have opened too many Named Pipes already, you may not have enough memory or disk space, or it may be an internal program error. Action: Make sure that Named Pipes and SPX are loaded and that your system has enough memory. If you suspect a memory problem, see message IDREF="FM69340" "REQ0843: Not enough memory for a network management thread (<error code>)." After completing these actions, reboot the system and try again. If the problem persists, contact your Novell Authorized Reseller.REQ0845: Not enough memory to run network management (<error code>). NetWare Client for OS/2 INSTALLExplanation: The NWDaemon program tried to allocate memory from the system to run network management, but memory is not available. Network Management will not run until memory is available and the system is rebooted. Action: Try adding RAM, reducing your configuration options in the CONFIG.SYS file (for example, reducing the size of DIRCACHE), removing optional device drivers from the CONFIG.SYS file, and freeing up some hard disk space by deleting unnecessary programs. If you are using multiple disk partitions, consider moving the OS/2 swapped file to a larger partition. Disk compression utilities may also be available that can help resolve this problem. After completing these actions, shut down OS/2; then reboot the system. If the problem persists, contact your Novell Authorized Reseller.REQ0904: The NWREQ.SYS driver is not loaded. NetWare Client for OS/2 INSTALLExplanation: NetWare Client for OS/2 cannot be initialized until the driver is loaded. Action: Load the NWREQ.SYS driver.PAGENUM=773 ID="BP767"REQ0914: The program cannot allocate selectors for the workspace table. NetWare Client for OS/2 INSTALLExplanation: All available memory selectors are being used by the system or by previously loaded device drivers. Action: Remove optional or unneeded device drivers from the CONFIG.SYS file and try again. If the problem persists, contact your Novell Authorized Reseller.REQ0915: The program cannot allocate memory for the workspace table. NetWare Client for OS/2 INSTALLExplanation: All available system memory is in use. NetWare Client for OS/2 cannot load properly. Action: Try adding RAM, reducing your configuration options in the CONFIG.SYS file (for example, reducing the size of DIRCACHE), removing optional device drivers from the CONFIG.SYS file, and freeing up some hard disk space by deleting unnecessary programs. If you are using multiple disk partitions, consider moving the OS/2 swapper file to a larger partition. Disk compression utilities may also be available that can help resolve this problem. After completing these actions, shut down OS/2; then reboot the system. If the problem persists, contact your Novell Authorized Reseller.REQ0917: Memory is not available for the cache table. Caching is disabled. NetWare Client for OS/2 INSTALLExplanation: All available system memory is in use by the system. NetWare Client for OS/2 cannot load properly. Action: Try adding RAM, reducing your configuration options in the CONFIG.SYS file (for example, reducing the size of DIRCACHE), removing optional device drivers from the CONFIG.SYS file, and freeing up some hard disk space by deleting unnecessary programs. If you are using multiple disk partitions, consider moving the OS/2 swapper file to a larger partition. Disk compression utilities may also be available that can help resolve this problem. After completing these actions, shut down OS/2; then reboot the system. If the problem persists, contact your Novell Authorized Reseller.REQ0919: An incorrect OS/2 version is being used. NetWare Client for OS/2 INSTALLExplanation: The major versions of NetWare Client for OS/2 and OS/2 do not match. Action: Upgrade NetWare Client for OS/2 or OS/2.PAGENUM=774 ID="BP768"REQ0937: The Requester driver version does not match the IFS version. NetWare Client for OS/2 INSTALLExplanation: NWIFS.IFS and NWREQ.SYS were not installed from the same installation disk. Action: Install NetWare Client for OS/2 again. If the problem persists, contact your Novell Authorized Reseller.REQ1005: The LAN support module is not installed. NetWare Client for OS/2 INSTALLExplanation: NetWare Client for OS/2 driver requires the LSL.SYS driver to be running when it loads. Either the "DEVICE=C:\NETWARE\LSL.SYS" line is missing from the CONFIG.SYS file or the LSL encountered an error while loading. Action: Check the CONFIG.SYS file for the LSL.SYS driver. If this is not the problem, contact your Novell Authorized Reseller.REQ1008: A NetWare server cannot be found. NetWare Client for OS/2 INSTALLExplanation: NetWare Client for OS/2 tries to locate a NetWare server when it initializes. Either no servers are currently running or there is a cabling problem. Action: Make sure that the NetWare server is running and operating properly. Also make sure that the OS/2 machine is connected to the network.REQ1010: The program cannot allocate selectors for the connection table. NetWare Client for OS/2 INSTALLExplanation: All available memory selectors are being used by the system or by previously loaded device drivers. Action: Remove optional or unneeded device drivers from the CONFIG.SYS file and try again. If the problem persists, contact your Novell Authorized Reseller.REQ1011: The program cannot allocate memory for the connection table. NetWare Client for OS/2 INSTALLExplanation: All available system memory is in use. NetWare Client for OS/2 cannot load properly. Action: Try adding RAM, reducing your configuration options in the CONFIG.SYS file (for example, reducing the size of DIRCACHE), removing optional device drivers from the CONFIG.SYS file, and freeing up some hard disk space by deleting unnecessary programs. If you are using multiple disk partitions, consider moving the OS/2 swapper file to a larger partition. Disk compression utilities may also be available that can help resolve this problem. After completing these actions, shut down OS/2; then reboot the system.If the problem persists, contact your Novell Authorized Reseller.PAGENUM=775 ID="BP769"REQ1019: An incorrect OS/2 version is being used. NetWare Client for OS/2 INSTALLExplanation: The major version of NetWare Client for OS/2 and OS/2 do not match. Action: Upgrade NetWare Client for OS/2 or OS/2.REQ1021: The config file cannot be parsed. Default parameters will be used. NetWare Client for OS/2 INSTALLExplanation: NetWare Client for OS/2 driver could not read parameters in the NET.CFG file. Action: Make sure the syntax for the NetWare Client for OS/2 section of the file is correct.REQ1022: An unrecoverable error occurred. The driver was not loaded. NetWare Client for OS/2 INSTALLExplanation: The driver could not load properly. This is probably an internal program error. Action: Try again. If the problem persists, contact your Novell Authorized Reseller.REQ1024: The program cannot allocate selectors for worker support. NetWare Client for OS/2 INSTALLExplanation: All available memory selectors are being used by the system or by previously loaded device drivers. Action: Remove optional or unneeded device drivers from the CONFIG.SYS file. Then try again. If the problem persists, contact your Novell Authorized Reseller.REQ1038: The program cannot allocate memory for the error message buffer. NetWare Client for OS/2 INSTALLExplanation: All available system memory is in use by the system. NetWare Client for OS/2 cannot load properly. Action: Try adding RAM, reducing your configuration options in the CONFIG.SYS file (for example, reducing the size of DIRCACHE), removing optional device drivers from the CONFIG.SYS file, and freeing up some hard disk space by deleting unnecessary programs. If you are using multiple disk partitions, consider moving the OS/2 swapper file to a larger partition. Disk compression utilities may also be available that can help resolve this problem. After completing these actions, shut down OS/2; then reboot the system. If the problem persists, contact your Novell Authorized Reseller.REQ1039: The Requester could not send to NetWare server <number> as <number>. NetWare Client for OS/2 INSTALLExplanation: NetWare Client for OS/2 waits for a response from the server after each request. If the server does not respond within a certain amount of time, NetWare Client for OS/2 times out. Action: Make sure that the server is still running and functioning properly. Also make sure that all routers between the workstation and the server are still running. PAGENUM=776 ID="BP770"If the problem persists, contact your Novell Authorized Reseller.REQ1040: The Requester timed out waiting for reply from server <number>. NetWare Client for OS/2 INSTALLExplanation: NetWare Client for OS/2 waits for a response from the server after each request. If the server does not respond within a certain amount of time, NetWare Client for OS/2 times out. Action: Make sure that the server is still running and functioning properly. Also make sure that all routers between the workstation and the server are still running. If the problem persists, contact your Novell Authorized Reseller.REQ1041: Server <number> did not respond to a request. NetWare Client for OS/2 INSTALLExplanation: NetWare Client for OS/2 waits for a response from the server after each request. If the server does not respond within a certain amount of time, NetWare Client for OS/2 times out. This error can also occur if the server responds with an unexpected response.Action: Make sure that the server is still running and functioning properly. Also make sure that all routers between the workstation and the server are still running. If the problem persists, contact your Novell Authorized Reseller.REQ1042: Connection to NetWare server <number> as <number> is now invalid. NetWare Client for OS/2 INSTALLExplanation: NetWare Client for OS/2 waits for a response from the server after each request. If the server does not respond within a certain amount of time, NetWare Client for OS/2 times out. Action: Make sure that the server is still running and functioning properly. Also make sure that all routers between the workstation and the server are still running. If the problem persists, contact your Novell Authorized Reseller.REQ1043: Routing to NetWare server <number> has been disrupted. NetWare Client for OS/2 INSTALLExplanation: The network route to the server has been disrupted. Action: Make sure that the server is still running and functioning properly. Also make sure that all routers between the workstation and the server are still running. If the problem persists, contact your Novell Authorized Reseller.REQ1045: Routing to NetWare server <number> has been disrupted. NetWare Client for OS/2 INSTALLExplanation: The network route to the server has been disrupted. Action: Make sure that the server is still running and functioning properly. PAGENUM=777 ID="BP771"Also make sure that all routers between the workstation and the server are still running. If the problem persists, contact your Novell Authorized Reseller.REQ1106: The SPDaemon cannot get the SPX version. Error: <code>. NetWare Client for OS/2 INSTALLExplanation: The SpxGetVersion call failed. This may be an internal program error. Action: Make sure that the SPX.SYS driver has been properly entered in the CONFIG.SYS file. If so, check the messages displayed by the driver for any errors or warnings, and correct the problems indicated. Check for a mismatch of driver versions. If the problem persists, contact your Novell Authorized Reseller.REQ1107: The SPX driver and the SPX daemon are incompatible versions. NetWare Client for OS/2 INSTALLExplanation: The SPX.SYS driver and SPDAEMON.EXE versions may not match. Action: Make sure that the client SPX.SYS driver and SPDAEMON.EXE are compatible versions. If the problem persists, contact your Novell Authorized Reseller. REQ1108: The SPX driver entry cannot be obtained. Error: <code>. NetWare Client for OS/2 INSTALLExplanation: The SPDaemon could not get a handle to the SPX.SYS driver. This may be an internal program error. Action: Make sure that the client SPX.SYS driver and SPDAEMON.EXE versions are compatible. If the problem persists, contact your Novell Authorized Reseller. REQ1109: The SPX daemon is already loaded. Error: <code>. NetWare Client for OS/2 INSTALLExplanation: The SPDAEMON.EXE has already registered with the SPX.SYS driver, which means it is already loaded. Action: Make sure that the daemon SPDAEMON.EXE has not been entered in the CONFIG.SYS file more than once. REQ1110: The daemon cannot register with the SPX driver. Error: <code>. NetWare Client for OS/2 INSTALLExplanation: The SPDaemon cannot communicate with the SPX.SYS driver. Action: Make sure that the SPX.SYS file has been properly entered in the CONFIG.SYS file. If so, check the messages displayed by the driver for any errors or warnings, and correct the problems indicated. Check for a mismatch of driver versions. If the problem persists, contact your Novell Authorized Reseller. PAGENUM=778 ID="BP772"REQ1111: The SPX device handle cannot be closed. Error: <code>. NetWare Client for OS/2 INSTALLExplanation: The SPDeamon cannot close the device handle. This may be an internal program error. Action: Try again. If the problem persists, contact your Novell Authorized Reseller.REQ1112: The SPDaemon cannot wait on semaphore. Error: <code>. NetWare Client for OS/2 INSTALLExplanation: A DosSemSetWait call failed. This may be an internal program error. Action: Try again. If the problem persists, contact your Novell Authorized Reseller.REQ1113: System information segments cannot be obtained. Error: <code>. NetWare Client for OS/2 INSTALLExplanation: The DosGetInfoSeg call failed. This may be an internal program error. Action: Try again. If the problem persists, contact your Novell Authorized Reseller.REQ1114: Priority for the lock thread cannot be set. Error: <code>. NetWare Client for OS/2 INSTALLExplanation: The DosSetPrty call failed. This may be internal program error. Action: Try again. If the problem persists, contact your Novell Authorized Reseller.REQ1115: The SPX driver cannot be accessed. Error: <code>. NetWare Client for OS/2 INSTALLExplanation: The SPDaemon was not able to access SPX.SYS through the call gate. Action: Make sure that the SPX.SYS driver has been properly entered in the CONFIG.SYS file. If so, check the messages displayed by the driver for any errors or warnings, and correct the problems indicated. Also check for a mismatch of driver versions; then try again. If the problem persists, contact your Novell Authorized Reseller.REQ1116: Priority for an AES thread cannot be set. Error: <code>. NetWare Client for OS/2 INSTALLExplanation: The DosSetPrty call failed. This may be an internal program error. Action: Try again. If the problem persists, contact your Novell Authorized Reseller.REQ1117: Priority for a watchdog thread cannot be set. Error: <code>. NetWare Client for OS/2 INSTALLExplanation: The DosSetPrty call failed. This may be an internal program error. Action: Try again. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=779 ID="BP773"REQ1118: Priority for a session thread cannot be set. Error: <code>. NetWare Client for OS/2 INSTALLExplanation: The DosSetPrty call failed. This may be an internal program error. Action: Try again. If the problem persists, contact your Novell Authorized Reseller.REQ1119: The SPXCALLS.DLL cannot register with the SPX driver. NetWare Client for OS/2 INSTALLExplanation: The SPXCALLS.DLL cannot communicate with the SPX.SYS driver. Action: Check to see if the SPX.SYS driver has been properly entered in the CONFIG.SYS file. If so, check the messages displayed by the driver for any errors or warnings, and correct the problems indicated. Check for a mismatch of driver versions; then try again. If the problem persists, contact your Novell Authorized Reseller.REQ1205: The driver cannot initialize the CGroup Data variables. NetWare Client for OS/2 INSTALLExplanation: Normally, key data variable are stored in the driver's CGroup for easy and reliable access. However, in this instance the variables could not be initialized due to a memory-related error. Action: Try adding RAM, reducing your configuration options in the CONFIG.SYS file (for example, reducing the size of DIRCACHE), removing optional device drivers from the CONFIG.SYS file, and freeing up some hard disk space by deleting unnecessary programs. If you are using multiple disk partitions, consider moving the OS/2 swapper file to a larger partition. Disk compression utilities may also be available that can help resolve this problem. After completing these actions, shut down OS/2; then reboot the system. If the problem persists, contact your Novell Authorized Reseller. REQ1206: The driver cannot configure SPX. NetWare Client for OS/2 INSTALLExplanation: The driver in conjunction with the NWCONFIG.DLL failed to parse the NET.CFG file for the SPX parameters. Action: Make sure the format of the NET.CFG file is correct.REQ1207: The driver failed to get support hooks from the LSL or IPX. NetWare Client for OS/2 INSTALLExplanation: SPX could not open or communicate with either the LINKSUP_ (LSL.SYS) or the IPX_ (IPX.SYS) drivers. The most likely cause of this error is that one or both of these drivers has been improperly installed. Action: Make sure that the device drivers LSL.SYS and IPX.SYS have been properly entered in the CONFIG.SYS file. PAGENUM=780 ID="BP774"If so, check the messages displayed by the driver for any errors or warnings, and correct the problems indicated. Check for a mismatch of driver versions; then try again. If the problem persists, contact your Novell Authorized Reseller.REQ1208: The OS/2 version cannot be obtained; OS/2 v2.0 is assumed. NetWare Client for OS/2 INSTALLExplanation: The DosGetVersion call failed (an internal program error), or the OS\2 version currently running is not v2.0 or later. Action: Make sure that OS/2 and the SPX.SYS driver are compatible versions. If this is not the problem, contact your Novell Authorized Reseller.REQ1209: The driver cannot get OS/2 DOS variables. NetWare Client for OS/2 INSTALLExplanation: The SPX.SYS driver could not obtain either the system or local information segment. This may be an internal program error. Action: Try again. If the problem persists, contact your Novell Authorized Reseller.REQ1210: The driver cannot initialize the SPX call gate. NetWare Client for OS/2 INSTALLExplanation: The SPX.SYS driver could not register a call gate with the LSL.SYS driver. Action: Make sure that the LSL.SYS driver has been properly entered in the CONFIG.SYS file. If so, check the messages displayed by the driver for any errors or warnings, and correct the problems indicated. Check for a mismatch of driver versions; then try again. If the problem persists, contact your Novell Authorized Reseller.REQ1211: The driver cannot allocate memory for SPX use. NetWare Client for OS/2 INSTALLExplanation: The system does not have enough memory to run SPX. Action: Try adding RAM, reducing your configuration options in the CONFIG.SYS file (for example, reducing the size of DIRCACHE), removing optional device drivers from the CONFIG.SYS file, and freeing up some hard disk space by deleting unnecessary programs. If you are using multiple disk partitions, consider moving the OS/2 swapper file to a larger partition. Disk compression utilities may also be available that can help resolve this problem. After completing these actions, shut down OS/2; then reboot the system. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=781 ID="BP775"REQ1301: The application cannot initialize named pipes. NetWare Client for OS/2 INSTALLExplanation: The application could not open or communicate with the NMPIPE.SYS driver. Most likely, the NMPIPE.SYS driver is not entered in the CONFIG.SYS file. Action: Make sure that the NMPIPE.SYS driver has been properly entered in the CONFIG.SYS file. If so, check the messages displayed by the driver for any errors or warnings, and correct the problems indicated. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=782 ID="BP776"PARTITION2: All referrals to a server, necessary to perform this operation, have failed.PARTITIONExplanation: The replicas or the server itself is being deleted. An unexpected internal program error has occurred.Action: For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. Try the operation again. For troubleshooting NetWare server problems, see "BOOK="superenu" COLLECTION="nw41"Troubleshooting the NetWare Server" in Supervising the Network. If the problem persists, contact your Novell Authorized Reseller.3: Unexpected master replica operation.PARTITIONExplanation: An unexpected internal program error has occurred.Action: The partition creation takes a few minutes to complete. Wait a few minutes and retry the operation. For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.4: Directory services is locked. Please wait a couple minutes and try again.PARTITIONExplanation: NetWare Directory Services is synchronizing the replicas, or someone may be running DSREPAIR.Action: Make sure the replicas are not in the process of synchronizing by waiting a few minutes then trying the operation again. Make sure DSREPAIR is not being run.If the problem persists for more than 24 hours, make sure the server is operating properly. For troubleshooting NetWare server problems, see "BOOK="superenu" COLLECTION="nw41"Troubleshooting the NetWare Server" in Supervising the Network.5: Container operation performed on non-container object.PARTITIONExplanation: This operation cannot be performed on a leaf object.Action: None. This message is for information only.6: The server does not have enough memory to perform the requested operation.PARTITIONAction: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.PAGENUM=783 ID="BP777"7: Cannot add or delete partition when partition or its parent has a non-master replica.PARTITIONExplanation: The partition cannot be added or deleted when the partition or its parent does not have a master replica.Action: Change the replica from a read/write or read-only type to a master replica, and retry the operation. See "BOOK="superenu" COLLECTION="nw41"Guidelines for Managing Partitions and Replicas" in Supervising the Network.8: Access denied. No rights to perform this operation.PARTITIONExplanation: The user must have Supervisory rights to perform this operation.Action: If appropriate, make sure the user has Supervisory rights for performing this operation. For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A.9: The workstation could not get a valid connection to the server.PARTITIONExplanation: A disk I/O failure or hardware failure may have occurred.Action: Check the cabling and the workstation's network board. Find out if the server is advertising by using the DISPLAY NETWORKS command on the server console. See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network. For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A.10: Directory services attribute does not exist.PARTITIONExplanation: An unexpected internal program error has occurred.Action: For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. Try the operation again. If the problem persists, contact your Novell Authorized Reseller.11: Directory services entry does not exist.PARTITIONExplanation: An unexpected internal program error has occurred.Action: For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. Try the operation again. If the problem persists, contact your Novell Authorized Reseller.12: No such partition.PARTITIONExplanation: The selected object is not a partition anymore. An unexpected internal program error has occurred.Action: For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. Try the operation again. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=784 ID="BP778"13: No such directory services value.PARTITIONExplanation: An unexpected internal program error has occurred.Action: For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. Try the operation again. If the problem persists, contact your Novell Authorized Reseller.14: Workstation has insufficient memory to perform this operation.PARTITIONAction: See "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network.15: Server not found.PARTITIONExplanation: A general disk I/O failure or hardware failure may have occurred.Action: See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network. Check the cabling and the workstation's network board. Determine if the server is advertising by using the DISPLAY NETWORKS command at the server console. For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A.If the server is down permanently, run DSREPAIR on the servers in the same replica ring as the server that is not operating.17: Partition already exists.PARTITIONExplanation: The object is already a partition; it cannot be partitioned again.Action: None. This message is for information only. For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A.18: Partition is busy synchronizing. Please wait a couple of minutes and try again.PARTITIONExplanation: The partition may be busy synchronizing the replicas.Action: Make sure the replicas are not in the process of synchronizing by waiting a few minutes then trying the operation again. For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A.19: Directory services record in use.PARTITIONExplanation: NetWare Directory Services is synchronizing the replicas.Action: Make sure the replicas are not in the process of synchronizing by waiting a few minutes then trying the operation again. For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A.If the problem persists for more than 24 hours, make sure the server is operating properly. For troubleshooting NetWare server problems, see "BOOK="superenu" COLLECTION="nw41"Troubleshooting the NetWare Server" in Supervising the Network.PAGENUM=785 ID="BP779"20: Replica already exists.PARTITIONExplanation: Another replica of the partition is already located on this server. Two replicas of the same partition cannot be on the same server.Action: Create the replica on another server because this server already has a replica of the partition.21: Replica unavailable. Replica operation currently in progress.PARTITIONExplanation: The selected replica is busy synchronizing and cannot send all the object information to all the other replicas.Action: Make sure the replicas are not in the process of synchronizing by waiting a few minutes then trying the operation again. Other NetWare Directory Services errors may also be displayed; check these messages. For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A.22: Directory services schema synchronization in progress.PARTITIONAction: Make sure the replicas are not in the process of synchronizing by waiting a few minutes then trying the operation again. Other NetWare Directory Services errors may also be displayed; check these messages. For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A.23: Invalid NCP packet format. Possible intruder detected.PARTITIONExplanation: The most likely explanation is that an intruder has sent an invalid NCP packet. Another possibility is that an unexpected internal program error occurred.Action: First determine if an intruder has tried to access the network. If this is not the problem, an internal error may have occurred. For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. Try the operation again. If the problem persists, contact your Novell Authorized Reseller.24: Directory services synchronization in progress.PARTITIONAction: Make sure the replicas are not in the process of synchronizing by waiting a few minutes then trying the operation again. Other NetWare Directory Services errors may also be displayed; check these messages. For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A.PAGENUM=786 ID="BP780"25: Unable to attach to required server.PARTITIONExplanation: The server may not be operating, or it may not be a NetWare 4 server. The replicas may be in the process of synchronizing.Action: Make sure the server is a NetWare 4 server, is operating, and is properly installed. If so, wait a few minutes to allow the replicas to finish synchronizing; then try the operation again. For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A.26: Unexpected directory services error.PARTITIONExplanation: An unexpected NetWare Directory Services error has occurred.Action: For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. Try the operation again. Check the NetWare Directory Services errors that may have been displayed also. If the problem persists, contact your Novell Authorized Reseller.28: The requested operation cannot be performed on the selected replica.PARTITIONExplanation: An unexpected internal program error has occurred.Action: For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. The partition creation takes a few minutes to complete. Wait a few minutes and try the operation again. If the problem persists, contact your Novell Authorized Reseller.29: Unable to get the required information from the remote server.PARTITIONExplanation: The server may be down, or a general disk I/O failure or hardware failure may have occurred.Action: See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network. Check the cabling and the workstation's network board. Determine if the server is advertising by using the DISPLAY NETWORKS command at the server console. For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A.If the server is down permanently, run DSREPAIR on the servers in the same replica ring as the server that is not operating.30: The replica is in synchronization state. Please wait a couple of minutes and try again.PARTITIONExplanation: NetWare Directory Services is synchronizing the replicas.Action: Make sure the replicas are not in the process of synchronizing by waiting a few minutes then trying the operation again. For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A.If the problem persists for more than 24 hours, make sure the server is operating properly. For troubleshooting NetWare server problems, see "BOOK="superenu" COLLECTION="nw41"Troubleshooting the NetWare Server" in Supervising the Network.PAGENUM=787 ID="BP781"31: This operation cannot be performed on a container which is not a root of a partition.PARTITIONExplanation: The user tried to perform the partition operation from an nonpartition container object.Action: Make the container object a partition, and retry the operation. Make sure the replicas are not in the process of synchronizing by waiting a few minutes then trying the operation again.32: The partition is busy synchronizing to complete a previous process of moving. Please wait a couple minutes and try again.PARTITIONExplanation: The partition is busy splitting, joining, or moving. This process may take a long time depending on the number of objects and the traffic on the network.Action: Wait a few minutes and try the operation again. For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A.33: This is an invalid operation at this time.PARTITIONExplanation: The operation of splitting, joining, or moving is already completed, and it is too late to abort the operation.Action: If desired, you can wait for the operation to be completed, and then you can reverse the operation. Make sure you do not reverse the operation before the completion of the previously specified operation.34: This operation cannot be aborted.PARTITIONExplanation: An unexpected NetWare Directory Services error has occurred. The status of the partition operation may be at a point at which an abort request is too early or too late.Action: Check the NetWare Directory Services errors that may have been displayed, and take the appropriate action to solve the problem.35: The context you were in when launching Partition Manager no longer exists. The container may have been moved or deleted, so Partition Manager will set the context to your default context as specified in NET.CFG.PARTITIONAction: None. This message is for information only.PAGENUM=788 ID="BP782"PARTMGR005: The replica cannot be created on server name. Error code: codePARTMGRExplanation: An unexpected NetWare Directory Services error occurred when this utility tried to create a replica for the selected partition. The replica cannot be created.Action: Make sure the replicas are not in the process of synchronizing by waiting a few minutes and trying the operation again.If the problem persists after a few minutes, make sure the server indicated in the message is a NetWare 4.0 server, the server is properly installed, the server is operating when adding the replica, and the server is the server object in the Directory tree that is really pointing to the physical server.If the problem persists for more than 24 hours, make sure the server is operating properly. For troubleshooting NetWare server problems, see "BOOK="superenu" COLLECTION="nw41"Troubleshooting the NetWare Server" in Supervising the Network. For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.010: The selected replica could not send all the changes to other replicas. Error code: codePARTMGRExplanation: The selected replica is busy synchronizing and cannot send all the object information to all the other replicas.Action: Make sure the replicas are not in the process of synchronizing by waiting a few minutes and trying the operation again. Other NetWare Directory Services errors may also be displayed; check these messages. For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A.015: The selected replica could not receive all the changes to other replicas. Error code: codePARTMGRExplanation: The master replica is busy synchronizing and cannot send all the object information to the selected replicas.Action: Make sure the replicas are not in the process of synchronizing by waiting a few minutes and trying the operation again. Other NetWare Directory Services errors may also be displayed; check these messages. For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A.PAGENUM=789 ID="BP783"020: The context could not be created. Error code: codePARTMGRExplanation: A context handle needs to be created in this application to run this utility, but the handle could not be created. The user is not logged in to Directory Services and authenticated, or the workstation is out of memory.Action: Make sure the user is logged in to NetWare Directory Services and is authenticated. Make sure the workstation has memory available. See "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network. For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A.025: The list of replicas on the selected server cannot be obtained. Error code: codePARTMGRExplanation: The replicas on the selected server could not be listed. The server may not be operating, or it may not be a NetWare 4 server. The replicas may be in the process of synchronizing.Action: Make sure the server is a NetWare 4 server, is operating, and is properly installed. If so, wait a few minutes to allow the replicas to finish synchronizing; then try the operation again. For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 030: The system cannot get the current context. Error code: codePARTMGRExplanation: PARTMGR is unable to get the current context that the NDS.VLM has set for the user.Action: Make sure the VLM programs are loaded properly. Try using the CX utility to change the context. For information, see "BOOK="utlrfenu" COLLECTION="nw41"CX" in Utilities Reference. For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.040: The replica type could not be changed. Error code: codePARTMGRExplanation: The replicas may be in the process of synchronizing. Another possibility is that the user does not have appropriate rights to change replica types.Action: Make sure the replicas are not in the process of synchronizing by waiting a few minutes and trying the operation again. Make sure the user has the appropriate rights to perform this operation.If the problem persists for more than 24 hours, make sure the server is operating properly. For troubleshooting NetWare server problems, see "BOOK="superenu" COLLECTION="nw41"Troubleshooting the NetWare Server" in Supervising the Network. 045: The replica could not be deleted. Error code: codePARTMGRPAGENUM=790 ID="BP784"Explanation: The replica cannot be deleted if it is the only replica for the selected partition. Other reasons the replica could not be deleted may be because the replicas may be in the process of synchronizing, the server may not be operating, or the user may not have the appropriate rights to change replica types.Action: Make sure the replica is not the only replica for the selected partition. Make sure the replicas are not in the process of synchronizing by waiting a few minutes and trying the operation again. Make sure the server is operating. Make sure the user has the appropriate rights to perform this operation. For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A.055: Multiple replicas are found and the system is unable to continue. Error code: codePARTMGRExplanation: The partition cannot be deleted. One or more replicas of the selected partition in addition to the master replica have been found.Action: Delete all the Read Only and Read Write replicas of the selected partition; then merge or join the partition again. For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A.060: The partitions could not be joined. Error code: codePARTMGRExplanation: The selected partition could not be merged with its parent partition. The replicas of the selected or the parent partition may be synchronizing.Action: Make sure the replicas are not in the process of synchronizing by waiting a few minutes and trying the operation again. For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.075: A Directory Services server must be present to run this application.PARTMGRExplanation: The workstation must have the VLM programs loaded, and the user must be logged in to a Directory tree before the user can continue.Action: Make sure the VLM programs are loaded at the user's workstation. Make sure the user is logged in and authenticated to NetWare Directory Services using the WHOAMI utility.080: The information on the object could not be read. Error code: codePARTMGRExplanation: The properties of the selected object could not be read. An internal program error probably occurred.Action: For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. Try the operation again. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=791 ID="BP785"085: The replica information could not be read. Error code: codePARTMGRExplanation: The properties of the replicas could not be read. An internal program error probably occurred.Action: Make sure the replicas are not in the process of synchronizing by waiting a few minutes and trying the operation again. For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. Try again.If the problem persists for more than 24 hours, make sure the server is operating properly. For troubleshooting NetWare server problems, see "BOOK="superenu" COLLECTION="nw41"Troubleshooting the NetWare Server" in Supervising the Network.090: The context could not be set. Error code: codePARTMGRExplanation: PARTMGR is unable to set the context to the required context.Action: Navigate through the Directory tree using CX. For information, see "BOOK="utlrfenu" COLLECTION="nw41"CX" in Utilities Reference. If this fails to solve the problem, reboot the computer and try again. For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A.095: The partition could not be created. Error code: codePARTMGRExplanation: The partition cannot be created. The parent partition may be busy synchronizing the replicas.Action: Make sure the replicas are not in the process of synchronizing by waiting a few minutes and trying the operation again. For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A.If the problem persists for more than 24 hours, make sure the server is operating properly. For troubleshooting NetWare server problems, see "BOOK="superenu" COLLECTION="nw41"Troubleshooting the NetWare Server" in Supervising the Network.100: This operation could not be aborted. Error code: codePARTMGRExplanation: An unexpected NetWare Directory Services error has occurred.Action: Check the NetWare Directory Services errors that may have been displayed, and take the appropriate actions to resolve the problem.105: The workstation is out of memory.PARTMGRAction: See "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network.110: The translation table file SCHEMA.XLT is not found or cannot be read.PARTMGRAction: See message IDREF="FM48610""907: This utility cannot open the translation table SCHEMA.XLT." in Appendix C.PAGENUM=792 ID="BP786"115: This workstation cannot attach to server name. Check the server, the cables, and the network board in the server. Error code: codePARTMGRExplanation: A general disk I/O failure or hardware failure may have occurred.Action: See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network. Check the cabling and the workstation's network board. Determine if the server is advertising by using the DISPLAY NETWORKS command at the server console. For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A.If the server is down permanently, run DSREPAIR on the servers in the same replica ring as the server that is not operating.120: The server cannot repair the time stamps of the replicas of the selected partition. Error code: codePARTMGRExplanation: The replicas are busy synchronizing, so they cannot be updated with the master replica at this time.Action: Make sure the replicas are not in the process of synchronizing by waiting a few minutes and trying the operation again. For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists for more than 24 hours, make sure the server is operating properly. For troubleshooting NetWare server problems, see "BOOK="superenu" COLLECTION="nw41"Troubleshooting the NetWare Server" in Supervising the Network.125: The server name is not valid or is not found in the current context. Use the Browse screen to select a valid server name. Error code: codePARTMGRExplanation: The selected object is not found in the current context.Action: Find out where that object is located by using the CX /T /A command. For information, see "BOOK="utlrfenu" COLLECTION="nw41"CX" in Utilities Reference. For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A.130: The server name is not a Directory Services server or it is not installed properly. Please check the version of the server. Error code: codePARTMGRExplanation: The server in use may not be running NetWare 4.Action: Make sure the server in use is running NetWare 4.x by using the NLIST SERVER SHOW VERSION command. For information, see "BOOK="utlrfenu" COLLECTION="nw41"NLIST" in Utilities Reference. The string should include "[DS]" if it is a 4.x server. For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A.PAGENUM=793 ID="BP787"135: The master replica is already located on this server and another replica of this partition can not be created on server name. Error code: codePARTMGRExplanation: Another replica of the partition is already located on this server. A server cannot contain two replicas of the same partition.Action: Create the replica on another NetWare Directory Services server. For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A.140: Directory Services is locked. Please wait a couple minutes and try again. Error code: codePARTMGRExplanation: NetWare Directory Services is synchronizing the replicas, or someone may be running DSREPAIR.Action: Make sure the replicas are not in the process of synchronizing by waiting a few minutes and trying the operation again. Make sure DSREPAIR is not being run. For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A.If the problem persists for more than 24 hours, make sure the server is operating properly. For troubleshooting NetWare server problems, see "BOOK="superenu" COLLECTION="nw41"Troubleshooting the NetWare Server" in Supervising the Network.145: The Directory Services record is in use. Error code: codePARTMGRExplanation: NetWare Directory Services is synchronizing the replicas.Action: Make sure the replicas are not in the process of synchronizing by waiting a few minutes and trying the operation again. For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A.If the problem persists for more than 24 hours, make sure the server is operating properly. For troubleshooting NetWare server problems, see "BOOK="superenu" COLLECTION="nw41"Troubleshooting the NetWare Server" in Supervising the Network.150: The selected partition is busy synchronizing. Please wait a couple of minutes and try again. Error code: codePARTMGRExplanation: The partition is busy splitting, joining, or moving. This process may take a long time depending on the number of objects and the traffic on the network.Action: Wait a few minutes and try the operation again. For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A.PAGENUM=794 ID="BP788"155: Directory Services is currently synchronizing the data base. Please wait a couple minutes and try again. Error code: codePARTMGRExplanation: NetWare Directory Services is synchronizing the replicas.Action: Make sure the replicas are not in the process of synchronizing by waiting a few minutes and trying the operation again. For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A.If the problem persists for more than 24 hours, make sure the server is operating properly. For troubleshooting NetWare server problems, see "BOOK="superenu" COLLECTION="nw41"Troubleshooting the NetWare Server" in Supervising the Network.170: This workstation cannot get a valid connection to the server. Error code: codePARTMGRExplanation: A disk I/O failure or hardware failure may have occurred.Action: Check the cabling and the workstation's network board. Find out if the server is advertising by using the DISPLAY NETWORKS command on the server console. For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A.175: The user does not have sufficient rights to perform this operation. Error code: codePARTMGRExplanation: The user must have Supervisory rights to perform this operation.Action: If appropriate, make sure the user has Supervisory rights for performing this operation. For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A.180: A container operation cannot be performed on a non-container object. Error code: codePARTMGRExplanation: This operation cannot be performed on a leaf object.Action: For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.185: An internal system error has occurred. The necessary Directory Services property does not exist. Error code: codePARTMGRExplanation: An unexpected internal program error has occurred.Action: For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. Try the operation again. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=795 ID="BP789"190: An internal system error has occurred. This Directory Services entry does not exist. Error code: codePARTMGRExplanation: An unexpected internal program error has occurred.Action: For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. Try the operation again. If the problem persists, contact your Novell Authorized Reseller.195: The selected partition does not exist. Error code: codePARTMGRExplanation: The selected object is not a partition anymore. An unexpected internal program error has occurred.Action: For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. Try the operation again. If the problem persists, contact your Novell Authorized Reseller.200: An internal system error has occurred. A Directory Services property value does not exist. Error code: codePARTMGRExplanation: An unexpected internal program error has occurred.Action: For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. Try the operation again. If the problem persists, contact your Novell Authorized Reseller.205: This partition already exists. Error code: codePARTMGRExplanation: The object is already a partition; it cannot be partitioned again.Action: None. This message is for information only. For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A.210: The server does not have enough memory to perform the requested operation. Error code: codePARTMGRAction: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A.215: An unexpected master replica operation has occurred. Please wait a couple minutes and try again. Error code: codePARTMGRExplanation: An unexpected internal program error has occurred.Action: For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. The partition creation takes a few minutes to complete. Wait a few minutes and try the operation again. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=796 ID="BP790"220: An invalid NCP packet was sent. Possible intruder detection. Error code: codePARTMGRExplanation: The most likely explanation is that an intruder has sent an invalid NCP packet. Another possibility is that an unexpected internal program error occurred.Action: First determine if an intruder has tried to access the network. If this is not the problem, an internal error may have occurred. For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. Try the operation again. If the problem persists, contact your Novell Authorized Reseller.230: A replica of this partition already exists on this server. Error code: codePARTMGRExplanation: Another replica of the partition is already located on this server. Two replicas of the same partition cannot be on the same server.Action: Create the replica on another server because this server already has a replica of the partition.235: The server that had the information about this object cannot be found. Error code: codePARTMGRExplanation: The replicas or the server itself is being deleted. An unexpected internal program error has occurred.Action: For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. Try the operation again. If the problem persists, contact your Novell Authorized Reseller.245: This is an invalid operation at this time. Error code: codePARTMGRExplanation: The operation of splitting, joining, or moving is already completed, and it is too late to abort the operation.Action: If desired, you can wait for the operation to be completed, and then you can reverse the operation. Make sure you do not reverse the operation before the completion of the previously specified operation.255: This operation cannot be performed with incompatible versions of Directory Services. Error code: codePARTMGRExplanation: The versions of Directory Services are incompatible.Action: Before performing any partition operations, load the same version of Directory Services on each server in the replica ring of the partition.907: This filename file can't be found. Error code: codePARTMGRAction: See message IDREF="FM48610""907: This utility cannot open the translation table SCHEMA.XLT." in Appendix C.PAGENUM=797 ID="BP791"908: The filename file is an incorrect format and can't be used.PARTMGRAction: See message IDREF="FM48610""907: This utility cannot open the translation table SCHEMA.XLT." in Appendix C.909: The filename file is an incorrect version. Version version is required.PARTMGRAction: Check the version of SCHEMA.XLT using NDIR schema.xlt /ver. Use PARTMGR /ver to check the version of SCHEMA.XLT the partition manager is using. Also, see message IDREF="FM91957""998: The message file found (utility_name.MSG) is an incorrect version. The correct version is number. See your network supervisor for assistance." in Appendix C.970: The attempt to open the Unicode table files failed.PARTMGRAction: See message IDREF="FM15675""970: The attempt to open the Unicode table files failed." in Appendix C.971: The workstation does not have enough memory to load the Unicode table files.PARTMGRAction: See message IDREF="FM55341""971: The workstation does not have enough memory to load the Unicode table files." in Appendix C.972: Access to the Unicode table files was denied.PARTMGRAction: See message IDREF="FM90152""972: Access to the Unicode table files was denied." in Appendix C.973: The Unicode table files cannot be found in the NLS directory or in the search drives. Code page: number Country: numberPARTMGRAction: See message IDREF="FM62778""973: The Unicode table files cannot be found in the NLS directory or in the search path. Code page: number Country: number" in Appendix C.974: The Unicode table files are corrupted.PARTMGRAction: See message IDREF="FM63405""974: The Unicode table files are corrupt." in Appendix C.975 The Unicode table files can't be opened because there are already too many open files. Close some files or modify your CONFIG.SYS file.PARTMGRAction: See message IDREF="FM49793""975: The Unicode table files cannot be opened because there are already too many open files. Close some files or modify your CONFIG.SYS file." in Appendix C.991: An error has occurred in function_name. Error code: code.PARTMGRAction: See message IDREF="FM92553""991: An error occurred in function_name. Error code: code." in Appendix C.PAGENUM=798 ID="BP792"991: An error has occurred in NWDSCanonicalizeName and the full server name cannot be obtained. Error code: code.PARTMGRAction: See message IDREF="FM92553""991: An error occurred in function_name. Error code: code." in Appendix C.999: The message file for this utility cannot be found.PARTMGRAction: See message IDREF="FM69424""999: The message file for this utility cannot be found." in Appendix C.PAGENUM=799 ID="BP793"PCN2L-NW025: You cannot load MSM31X on a NetWare 3.10 server.PCN2L-NWExplanation: The computer tried to load MSM31X.NLM on a NetWare  3.1 server. MSM31X.NLM will run only on a NetWare 3.11 server.Action: Either load a version of the Media Support Module (MSM) that will run on a NetWare 3.10 server, or upgrade the server to NetWare 3.11. For information about MSM, see "BOOK="cncptenu" COLLECTION="nw41"Media Support Module (MSM)" in Concepts.026: On a NetWare 3.11 server, you must load LSLENH.NLM before you load MSM31X.NLM.PCN2L-NWExplanation: The Link Support Layer (LSL) and Media Support Module (MSM) have been loaded on a NetWare 3.11 server. An attempt was made to load LSLENH.NLM. The computer cannot load LSLENH.NLM once the MSM has been loaded. (LSLENH.NLM adds enhancement to the LSL.)Action: Unload MSM31X.NLM; then load LSLENH.NLM. Once the LSLENH.NLM has been loaded, load MSM31X.NLM again. For information about LSL and MSM, see "BOOK="cncptenu" COLLECTION="nw41"Link Support Layer (LSL)" and "BOOK="cncptenu" COLLECTION="nw41"Media Support Module (MSM)" in Concepts.050: [ISA bus | Microchannel] The board cannot be found.PCN2L-NWExplanation: If the computer is using an ISA bus network board, the network board was not found due to one or more of the following conditions: MARK=BULLETThe network board is not present in the computer. The network board settings are not the defaults, and they are not defined in the NET.CFG file.Another network board is using the same hardware settings as this network board.The network board is bad.Action: Do one or more of the following:MARK=BULLETMake sure that the network board is properly seated into the slot. If the jumper settings are not the defaults, make sure that they match the settings in the NET.CFG file. PAGENUM=800 ID="BP794"If the computer is not using the NET.CFG file, make sure that the jumper settings are set to the defaults. If other network boards are using the same hardware settings, change the settings and try to reload the driver.Replace the bad network board with one that is good.Explanation: If the computer is using a microchannel network board, the network board is not in the computer, or the network board's configuration could not be obtained.Action: Do one of the following:MARK=BULLETMake sure the network board is properly seated into a slot.Insert the network board into a slot, and run the CLASS=DISKReference diskette to install it.051: Board RAM failed the memory test.PCN2L-NWExplanation: The memory test on the network board's internal static RAM failed.Action: Make sure that the I/O port settings on the network board match the I/O port settings in the AUTOEXEC.NCF file. For information about the AUTOEXEC.NCF file, see "BOOK="superenu" COLLECTION="nw41"Maintaining the NetWare Server" in Supervising the Network. If the settings match, replace the network board.054: The board did not respond to the initialization command.PCN2L-NWExplanation: The network board did not respond to a reset command.Action: Make sure that the I/O port settings on the network board match the I/O port settings in the AUTOEXEC.NCF file. For information about the AUTOEXEC.NCF file, see "BOOK="superenu" COLLECTION="nw41"Maintaining the NetWare Server" in Supervising the Network. If the settings match, replace the network board.067: The group bit in the node address override was cleared.PCN2L-NWExplanation: You entered a node address with the Group address bit set; the Topology Specific Module (TSM) cleared it.Action: None. This message is for information only. For information about TSM, see "BOOK="cncptenu" COLLECTION="nw41"Topology Specific Module (TSM)" in Concepts.PAGENUM=801 ID="BP795"068: The local bit in the node address override was set.PCN2L-NWExplanation: You entered a node address without the local bit being set; the Topology Specific Module (TSM) set it. For information about TSM, see "BOOK="cncptenu" COLLECTION="nw41"Topology Specific Module (TSM)" in Concepts.Action: None. This message is for information only.071: The matching virtual adapter could not be found.PCN2L-NWExplanation: A new frame was being added to an existing network board, but the Media Support Module (MSM) could not locate a previous network board to link it with.Action: Obtain the most current version of MSM.NLM. For information about MSM, see "BOOK="cncptenu" COLLECTION="nw41"Media Support Module (MSM)" in Concepts.072: A resource tag is unavailable.PCN2L-NWExplanation: This message indicates a shortage of server memory. NetWare cannot allocate memory for a resource tag.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.073: Unable to allocate memory.PCN2L-NWExplanation: This message indicates a shortage of server memory. NetWare cannot allocate memory for the LAN driver.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.074: The hardware interrupt cannot be set.PCN2L-NWExplanation: NetWare could not set the hardware interrupt that the LAN driver registered. The LAN driver must have changed information in the configuration table (IntNumber, SharingFlags) after the hardware options were registered.Action: Make sure that the interrupt setting on the board matches the setting in the AUTOEXEC.NCF file. For information about the AUTOEXEC.NCF file, see "BOOK="superenu" COLLECTION="nw41"Creating or Editing a Server Batch (.NCF) File" in Supervising the Network.075: The MLID cannot be registered with the LSL.PCN2L-NWExplanation: The LAN driver's Link Support Layer (LSL) ran out of logical boards, or it could not allocate memory for its internal structures. Action: Unload unneeded LAN drivers that are consuming large numbers of logical boards. Increase the available memory. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. For information about LSL, see "BOOK="cncptenu" COLLECTION="nw41"Link Support Layer (LSL)" in Concepts.PAGENUM=802 ID="BP796"076: The polling procedure cannot be added.PCN2L-NWExplanation: Too many polling processes are registered with the operating system.Action: Unload unneeded NLMs that may be using a polling procedure.077: The event notification routine cannot be registered.PCN2L-NWExplanation: This message indicates a shortage of server memory. NetWare cannot allocate memory for internal structures related to event notification. Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.079: The MLID did not initialize MSMTxFreeCount.PCN2L-NWExplanation: The .LAN file is either outdated or corrupted.Action: Obtain a new .LAN file.086: The driver parameter block is too small.PCN2L-NWExplanation: The .LAN file is designed to run with an older version of the MSM.NLM.Action: Obtain a newer version of the .LAN file or an older version of the MSM.NLM.087: The media parameter block is too small.PCN2L-NWExplanation: The topology NLM is designed to run with an older version of the MSM.NLM.Action: Obtain a newer version of the topology NLM or an older version of the MSM.NLM.091: The hardware configuration conflicts.PCN2L-NWExplanation: Another hardware resource is being used, which the LAN driver is trying to register.Action: Change the hardware configuration of the network board or of the conflicting device.092: Cannot schedule AES without an HSM routine.PCN2L-NWExplanation: The LAN driver is either outdated or corrupted.Action: Obtain a new .LAN file.093: Cannot schedule interrupt time call back without an HSM routine.PCN2L-NWExplanation: The LAN driver is either outdated or corrupted.Action: Obtain a new .LAN file.PAGENUM=803 ID="BP797"094: Cannot set hardware interrupt without an HSM routine.PCN2L-NWExplanation: The LAN driver is either outdated or corrupted.Action: Obtain a new .LAN file.095: Cannot add polling without an HSM routine.PCN2L-NWExplanation: The LAN driver is either outdated or corrupted.Action: Obtain a new .LAN file.PAGENUM=804 ID="BP798"PCN2L-OS2001: The LSL is not loaded.PCN2L-OS2Explanation: The Link Support Layer (LSL) module must be loaded before the driver.Action: Edit the CONFIG.SYS file to load the LSL before the LAN driver, as in the following example:FORMAT="LINESPECIFIC"MOREINFO="NONE"DEVICE=C:\NETWARE\LSL.SYS 
DEVICE=C:\NETWARE\PCN2L.SYS 021: Could not add MLID Protocol ID.PCN2L-OS2Explanation: The Link Support Layer (LSL) is configured with resources for four Protocol Identifiers. This number has been exceeded.Action: None. This message is for information only.022: Could not allocate memory. Virtual board did not load.PCN2L-OS2Explanation: The computer does not have enough memory to load another network board.Action: Do one of the following:MARK=BULLETInstall more memory in the computer.Edit the CONFIG.SYS file, and remove any unneeded drivers.050: [ISA bus | Microchannel] The board cannot be found.PCN2L-OS2Explanation: If the computer is using an ISA bus network board, the network board was not found due to one or more of the following conditions: MARK=BULLETThe network board is not present in the computer. The network board settings are not the defaults, and they are not defined in the NET.CFG file.Another network board is using the same hardware settings as this network board.The network board is bad.Action: Do one or more of the following:MARK=BULLETMake sure that the network board is properly seated into the slot. PAGENUM=805 ID="BP799"If the jumper settings are not the defaults, make sure that they match the settings in the NET.CFG file. If the computer is not using the NET.CFG file, make sure that the jumper settings are set to the defaults. If other network boards are using the same hardware settings, change the settings and try to reload the driver.Replace the bad network board with one that is good.Explanation: If the computer is using a microchannel network board, the network board is not in the computer, or the network board's configuration could not be obtained.Action: Do one of the following:MARK=BULLETMake sure the network board is properly seated into a slot.Insert the network board into a slot, and run the CLASS=DISKReference diskette to install it.051: Board RAM failed the memory test.PCN2L-OS2Explanation: The memory test on the network board's internal static RAM failed.Action: Check the network board and other hardware.  If necessary, replace the network board.056: This interrupt is already used and cannot be shared.PCN2L-OS2Explanation: The selected interrupt is being used by another device, so it cannot be used for this network board.Action: If the computer is using a microchannel network board, run the CLASS=DISKReference diskette that came with the computer, and change the jumper setting on the network board to use a different interrupt. For information about jumper settings, see the TOKEN hardware manual. Edit the NET.CFG file to reflect the correct interrupt level used by the network board. For information about the NET.CFG file, see"BOOK="ws_osenu" COLLECTION="nw41"Creating or Editing NET.CFG" in NetWare Client for OS/2 User Guide.If the computer is using an ISA bus network board, change the jumper settings to specify a different interrupt; then edit the NET.CFG file to reflect the correct interrupt level used by the network board.PAGENUM=806 ID="BP800"064: Board cannot be found at slot/IO port.PCN2L-OS2Explanation: The network board cannot be found in the slot specified in the NET.CFG file.Action: If the computer is using an ISA bus network board, make sure that the slot number and the I/O address are correct in the NET.CFG file. For information about the NET.CFG file, see"BOOK="ws_osenu" COLLECTION="nw41"Creating or Editing NET.CFG" in NetWare Client for OS/2 User Guide.If the computer is using a microchannel network board, do one or more of the following:MARK=BULLETCorrect the slot number in the NET.CFG file to match the slot where the network board is physically located.Move the network board to the slot specified in the NET.CFG file; then run the CLASS=DISKReference diskette to install the network board.Note: If no slot is specified in the NET.CFG file, the driver will search all slots for the network board. If more than one network board is in the computer, the slots must be specified in the NET.CFG file.070: The board has failed.PCN2L-OS2Explanation: A hardware error has occurred.Action: Power off the computer; then reboot it. Try to reload the driver. If the driver will not reload, a hardware failure has occurred. Replace the network board.PAGENUM=807 ID="BP801"PCONSOLE005: PCONSOLE could not add print server name to the directory. Error code: code.PCONSOLEExplanation: You may have entered an invalid name.Action: Try a different name, preferably one with alphanumeric characters only. For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 010: PCONSOLE could not create the printer name in the directory. Error code: code.PCONSOLEExplanation: You may have entered an invalid name.Action: Try a different name, preferably one with alphanumeric characters only. For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 015: PCONSOLE could not create print queue name in the directory. The volume may not be accessible. Error code: code.PCONSOLEExplanation: You may have specified an invalid queue name, or the volume may not be accessible.Action: Try specifying a different queue name, preferably one with alphanumeric characters only. Make sure the volume is mounted. For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 020: PCONSOLE could not add the object to this printer's notification list. Error code: code.PCONSOLEExplanation: The user doesn't have sufficient privileges to the printer, or the partition where the printer object resided may not exist.Action: Make sure that the user has supervisory rights in the current context. If the printer is being serviced by a print server, make sure that the user is defined as an operator of that print server. For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 025: PCONSOLE could not add object name to the group. Error code: code.PCONSOLEExplanation: One of the following probably occurred:MARK=BULLETThe user lost the supervisory rights to this object.The server where the object is defined is not available.Action: Make sure that the user or the group is still listed in this object's operator list and that the server where the object is defined is running. For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. PAGENUM=808 ID="BP802"030: PCONSOLE could not assign printer name to print server name. Error code: code.PCONSOLEExplanation: One of the following probably occurred:MARK=BULLETThe user lost the supervisory rights to the print server.The server where the object is defined is not available.Action: Make sure that the user or the group is still listed in this print server's operator list and that the server where the object is defined is running. For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 035: PCONSOLE could not add the printer's restriction attribute. Error code: code.PCONSOLEExplanation: One of the following probably occurred:MARK=BULLETThe user lost the supervisory rights to the printer.The server where the object is defined is not available.Action: Make sure the server where the object is defined is running. For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 040: PCONSOLE could not add the print queue to the active print queues serviced by the printer. Error code: code.PCONSOLEExplanation: One of the following probably occurred:MARK=BULLETThe user lost the operator rights to the print server servicing the printer.The workstation lost the attachment to the print server currently servicing this printer.Action: Try the following:MARK=BULLETMake sure that the user or the group is listed in the operator list of the print server servicing this printer.Press MOREINFO="NONE"<Esc> to return to PCONSOLE's main menu. Select the "Print Server" option; then select the print server that is servicing the printer where the error occurred. Make sure that the print server status is "Running." If the status is "Down," check the computer where the print server was loaded. Try the initial operation again. For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. PAGENUM=809 ID="BP803"045: PCONSOLE could not add the queue to the printer's configuration. Error code: code.PCONSOLEExplanation: One of the following probably occurred:MARK=BULLETThe user lost the supervisory rights to the printer or to the print server assigned to it.The server where the object is defined is not available.Action: Try again. For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 050: PCONSOLE does not have sufficient memory on this PC for translation tables.PCONSOLEAction: See "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network.055: PCONSOLE could not change this printer's default print queue. Error code: code.PCONSOLEExplanation: One of the following probably occurred:MARK=BULLETThe user lost the supervisory rights to the printer or to the print server assigned to it.The server where the object is defined is not available.Action: Try again. For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 060: PCONSOLE could not change the object's password. Error code: code.PCONSOLEExplanation: The user may not have rights to change this object's password.Action: Make sure that the user has the necessary rights to perform this operation. Try again. For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 065: PCONSOLE could not change the print queue's priority. Error code: code.PCONSOLEExplanation: One of the following probably occurred:MARK=BULLETThe user lost the supervisory rights to the printer or to the print server assigned to it.The server where the object is defined is not available.Action: Try again. For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. PAGENUM=810 ID="BP804"070: PCONSOLE could not create a Directory Services context. Error code: code.PCONSOLEExplanation: Either the computer lost the connection to the Directory tree, or the connection is unlicensed.Action: Exit PCONSOLE and log in to the Directory tree again. For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 075: PCONSOLE could not delete the audit file name. Error code: code.PCONSOLEExplanation: The PSERVER.LOG file may be flagged as Read-Only, or the user has lost rights to the directory where the file resides.Action: Use PCONSOLE's Audit option to get the location of the PSERVER.LOG file. Make sure that the user has rights to the directory where the PSERVER.LOG file resides and that the file is not write protected. For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 080: PCONSOLE could not delete print server name. Error code: code.PCONSOLEExplanation: The user may not have rights to delete the print server (Supervisor rights required).Action: Check rights and try again. For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 085: PCONSOLE could not delete the printer. Error code: code.PCONSOLEExplanation: The user may not have rights to delete the printer (Supervisor rights required).Action: Check rights and try again. For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 090: PCONSOLE could not remove the object from the list for notification. Error code: code.PCONSOLEExplanation: A NetWare Directory Services error prevented the object name from being removed from the notification list.Action: Reauthenticate and try again. For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 095: PCONSOLE could not delete the printer from the print server. Error code: code.PCONSOLEExplanation: A NetWare Directory Services error prevented the printer from being deleted from the print server.Action: Reauthenticate and try again. For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. PAGENUM=811 ID="BP805"100: PCONSOLE could not delete the printer's restriction attribute. Error code: code.PCONSOLEExplanation: A NetWare Directory Services error prevented the printer's restriction property from being deleted.Action: Reauthenticate and try again. For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 101: PCONSOLE could not remove the queue from this printer's queue list. Error code: code.PCONSOLEExplanation: A NetWare Directory Services error prevented the print queue from being removed from the printer's queue list.Action: Reauthenticate and try again. For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 105: PCONSOLE could not enable auditing.PCONSOLEExplanation: PCONSOLE tried to set the Auditing flag, but was denied access to the file where the flag is kept.Action: Using the Auditing option in PCONSOLE, make sure the user has rights to read and write the PSERVER.AUD file in the path indicated.106: PCONSOLE could not get the location of the log file for this print server. Error code: code.PCONSOLEAction: For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 110: Either the volume where this print queue resides is not available at this time or PCONSOLE encountered an unexpected error while getting the print queue ID. Error code: code.PCONSOLEExplanation: One of the following probably caused this error:MARK=BULLETThe server where the queue resides is down.The queue has just been added to or removed from its host server, and the change is still being synchronized.Action: Select the queue again after a short wait. For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. PAGENUM=812 ID="BP806"115: PCONSOLE could not get the server information and cannot continue. Error code: code.PCONSOLEExplanation: PCONSOLE was unable to read the extended information of the selected server.Action: Make sure that the selected server is still part of the network. For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 130: PCONSOLE could not change the notification intervals for object name. Error code: code.PCONSOLEExplanation: One of the following probably occurred:MARK=BULLETThe user lost the supervisory rights to the printer or to the print server assigned to it.The server where the object is defined is not available.Action: Reauthenticate and try again. For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 135: PCONSOLE could not modify this print server's description. Error code: code.PCONSOLEExplanation: One of the following probably occurred:MARK=BULLETThe user lost the supervisory rights to the print server.The server where the object is defined is not available.Action: Reauthenticate and try again. For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 140: PCONSOLE could not open the PRINTQ.MSG file. Error code: code.PCONSOLEExplanation: When you tried to view the job entries in a print queue, PCONSOLE needed the message file PRINTQ.MSG but could not find it.Action: Make sure that PRINTQ.MSG is in one of the directories in the search path. For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 141: PCONSOLE is out of conventional memory.PCONSOLEExplanation: PCONSOLE.EXE is out of conventional memory.Action: Make more conventional memory available and try executing PCONSOLE again.146: PCONSOLE could not rename the object. Error code: code.PCONSOLEAction: For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. PAGENUM=813 ID="BP807"150: PCONSOLE could not save the changes to the printer configuration. Error code: codePCONSOLEExplanation: You modified the printer configuration, but PCONSOLE was unable to record the change in the printer's configuration file.Action: Make sure that the user has supervisory rights. For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 155: PCONSOLE could not save the new printer number. Error code: codePCONSOLEExplanation: The user modified the printer number, but PCONSOLE was unable to record the change in the printer's configuration file.Action: Make sure that the user has supervisory rights. For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 165: PCONSOLE encountered an error while scanning the objects in the current context. Error code: codePCONSOLEAction: For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 170: An error occurred which prevents the object type of type from being identified. An assumption of type `group' will be made while trying to delete this notify from the active printer. NWDSReadObjectInfo returned Error code: codePCONSOLEAction: For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 175: The object type of object can not be identified. The object may no longer exist in the Directory. An assumption of type `group' will be made while trying to delete this notify from the active printer.PCONSOLE180: Object name could not be added as active. Error code: FDA5 This probably means that no message is assigned to the object, which can be done via NetAdmin through the Default Server field of the object's environment information.PCONSOLEAction: Using NETADMIN or NetWare Administrator, make the assignment through the default server field of the objects's environment information.185: This is a reference to Bindery queue name which does not currently exist on server name.PCONSOLEExplanation: The directory still has a reference to a bindery queue that no longer exists.Action: Delete the queue name or re-create the queue in the original location.PAGENUM=814 ID="BP808"190: NWAttachToFileServer failed. Error code code - UNKNOWN_FILE_SERVER NetWare server name may be down or a router or other intervening component may have failed.PCONSOLEAction: Wait a few minutes and then try again. For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.200: An error occurred while trying to action description. Error code: code (See the System Messages manual)PCONSOLEExplanation: An error occurred while trying to perform an action on an active print server. The action is displayed in the message. If error code 303A occurs when trying to perform the "Notify Object" action, this may indicate that the message server is not accessible or not operating.Action: If error code 303A occurs, make sure the specified message server is operating. For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A.585: The PRINTQ.MSG file is the wrong version. The correct version is number. Queue jobs can not be viewed.PCONSOLEExplanation:  The message file used to manipulate the print jobs was the wrong version.Action: Enter the correct version of the message file.887: The name file could not be found.PCONSOLEExplanation:  The SCHEMA.XLT file could not be found.Action: IDREF="FM48610""907: This utility cannot open the translation table SCHEMA.XLT." in Appendix C.889: The name file is the wrong version. The correct version is version.PCONSOLEExplanation: The SCHEMA.XLT file version is the wrong version.Action: IDREF="FM48610""907: This utility cannot open the translation table SCHEMA.XLT." in Appendix C.907: The name translation tables failed to load. Error code: code.PCONSOLEAction: See message IDREF="FM48610""907: This utility cannot open the translation table SCHEMA.XLT." in Appendix C.908: The name translation tables failed to initialize. Error code: code.PCONSOLEAction: See message IDREF="FM51165""908: The specified path is invalid." in Appendix C.PAGENUM=815 ID="BP809"970: The attempt to open the Unicode table files failed. Error code: code.PCONSOLEAction: See message IDREF="FM15675""970: The attempt to open the Unicode table files failed." in Appendix C.971: The workstation does not have enough memory to load the Unicode table files.PCONSOLEAction: See message IDREF="FM55341""971: The workstation does not have enough memory to load the Unicode table files." in Appendix C.972: Access to the Unicode table files was denied.PCONSOLEAction: See message IDREF="FM90152""972: Access to the Unicode table files was denied." in Appendix C.973: The Unicode table files (*.001) cannot be found in the NLS directory or in the search drives.PCONSOLEAction: See message IDREF="FM62778""973: The Unicode table files cannot be found in the NLS directory or in the search path. Code page: number Country: number" in Appendix C.974: The Unicode table files are corrupted.PCONSOLEAction: See message IDREF="FM63405""974: The Unicode table files are corrupt." in Appendix C.975: The Unicode table files cannot be opened because there are already too many open files. Close some files or modify your CONFIG.SYS file.PCONSOLEAction: See message IDREF="FM49793""975: The Unicode table files cannot be opened because there are already too many open files. Close some files or modify your CONFIG.SYS file." in Appendix C.998: The file name is version version; must be version version.PCONSOLEAction: See message IDREF="FM91957""998: The message file found (utility_name.MSG) is an incorrect version. The correct version is number. See your network supervisor for assistance." in Appendix C.999: PCONSOLE could not find the message file NWDSBRWS.MSG. Error Code: code.PCONSOLEAction: See message IDREF="FM69424""999: The message file for this utility cannot be found." in Appendix C.PAGENUM=816 ID="BP810"PING5: Could not open ICMP socket.PINGExplanation: PING could not open the Internet Control Message Protocol (ICMP) socket to communicate with the other IP hosts.Action: Use INETCFG to determine if another utility is using the Internet Control Message Protocol (ICMP) socket. If the ICMP socket is being used, unload the utility that is using the ICMP socket. After freeing the ICMP socket, reload PING.6: Could not create enough threads to support Ping.PINGExplanation: The server may not have enough available memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.PAGENUM=817 ID="BP811"PMMON005: The VNETWARE.SYS driver is not installed.PMMONExplanation: The NWOS2 device driver VNETWARE.SYS has not been installed.Action: Make sure the file CONFIG.SYS has the following entry:FORMAT="LINESPECIFIC"MOREINFO="NONE"DEVICE=C:\NETWARE\VNETWARE.SYS 010: The VNetWare (VNW$) device driver is not installed.PMMONExplanation: The NWOS2 device driver VNETWARE.SYS has not been installed.Action: Make sure the file CONFIG.SYS has the following entry:FORMAT="LINESPECIFIC"MOREINFO="NONE"DEVICE=C:\NETWARE\VNETWARE.SYS 015: A VNetWare (VNW$) request failed. Error code: code.PMMONExplanation: An application request is not supported by the current version of VNETWARE.SYS.Action: To get an updated version of VNETWARE.SYS, contact your Novell Authorized Reseller.PAGENUM=818 ID="BP812"PNWxxxxPNW0151: An internal error has occurred. The CGroup information cannot be loaded.PNWxxxxExplanation: During normal operation, the program obtains a data selector to a particular code segment to store needed data variables. This message indicates that either the selector could not be obtained, or the data could not be loaded into the code segment.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.PNW0152: An internal error has occurred. The program cannot get configuration information.PNWxxxxExplanation: The program could not find the routine to parse the configuration information in the NET.CFG file. The routine is located in NWCONFIG.DLL.Action: Make sure the NWCONFIG.DLL file is present and is pointed to in the LIBPATH statement in the CONFIG.SYS file. For information, see 
BOOK="ws_osenu" COLLECTION="nw41"NetWare Client for OS/2 User Guide.PNW0153: An internal error has occurred. The program cannot get the DOS Help vectors.PNWxxxxExplanation: During normal operation, the program gets pointers from OS/2 to do certain routines. These pointers cannot be found.Action: Make sure the computer is using the proper version of NetWare for OS/2 for the version of OS/2 that is being run. If the problem persists, contact your Novell Authorized Reseller.PNW0154: An internal error has occurred. The program cannot get the support hooks.PNWxxxxExplanation: During normal operation, the program obtains several support hooks from OS/2. Some of those hooks could not be found.Action: Make sure the computer is using the proper version of NetWare for OS/2 for the version of OS/2 that is being run. If the problem persists, contact your Novell Authorized Reseller.PNW0155: An internal error has occurred. The program cannot allocate server memory.PNWxxxxExplanation: During normal operation, the program has to allocate a fixed and contiguous block of memory for the server. The call to allocate this memory failed.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.PAGENUM=819 ID="BP813"PNW0157: An internal error has occurred. The program cannot register PNetWare as a PDD.PNWxxxxExplanation: The OS/2 call to register PNETWARE as a Physical Device Driver (PDD) has failed. VNETWARE and PNETWARE are not able to communicate.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.PNW0158: A hardware error has occurred. The i386 microprocessor is defective.PNWxxxxExplanation: The computer is using a defective i386 microprocessor.Action: Replace the processor.PNW0161: Memory cannot be freed; the server is not running.PNWxxxxExplanation: A call to free the server memory failed after the server was brought down. Because the server is not running, the memory could not be returned to OS/2.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.PNW0162: An internal error has occurred. The program cannot initialize the GDT information.PNWxxxxExplanation: During normal operation, the program allocates and sets up certain GDTs. These initialization functions have failed.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.PNW0190: The optimal amount of contiguous memory for initialization is not available. The program will try to initialize with a lesser amount.PNWxxxxExplanation: The memory requested by OS/2 was not available; therefore, the amount of memory will be reduced until the requested allocation succeeds.Action: None. This message is for information only. The server will still function properly, but with less memory than requested. In the future, you may want to do one or more of the following:MARK=BULLETAllocate less memory.Allocate memory at PNETWARE initialization time if the computer is not currently doing that.Put more memory in the computer.PAGENUM=820 ID="BP814"PNW0191: An internal error has occurred. The program cannot parse NET.CFG because the configuration parser cannot be obtained.PNWxxxxExplanation: The program could not find the configuration parser in the NWCONFIG.DLL file.Action: Make sure the NWCONFIG.DLL file was installed and a path to it is in the LIBPATH statement in the CONFIG.SYS file.PNW0231: An error occurred during an attempt to read message file name.PNWxxxxExplanation: The message file is corrupted.Action: Reload the message file from the distribution CD-ROM or diskettes, or contact your Novell Authorized Reseller.PNW0232: A spurious hardware interrupt number was detected.PNWxxxxExplanation: An interrupt from an unknown source was passed to NetWare.Action: None. This message is for information only.PNW0233: Invalid message file name was detected.PNWxxxxExplanation: The given message file is not in the correct format.Action: Reload the message file from the distribution CD-ROM or diskettes or contact your Novell Authorized Reseller.PNW0234: An unresolved CLIB function was encountered: function.PNWxxxxExplanation: During normal operation, the program tried to find a given CLIB function, but could not.Action: Make sure the CLIB version is correct for the NetWare for OS/2 files. Or, make sure the computer is using the proper version of NetWare for OS/2 for the version of OS/2 that the computer is running. For information, contact your Novell Authorized Reseller.PNW0235: Unresolved externals were encountered: number.PNWxxxxExplanation: NetWare tried to find an external reference in the OS/2 loader, but could not find it.Action: Make sure the NetWare and NetWare for OS/2 versions are correct.PAGENUM=821 ID="BP815"PNW0236: The loader cannot the find public symbol symbol.PNWxxxxExplanation: The OS/2 loader needs certain variables and functions from the NetWare operating system kernel. These could not be found.Action: Make sure the NetWare and NetWare for OS/2 versions are correct.PNW0237: An invalid interrupt was encountered.PNWxxxxExplanation: Interrupt routines were called for which the program does not have an interrupt handler installed.Action: None. This message is for information only.PNW0238: An operating system procedure was called before the SERVER.NLM was loaded.PNWxxxxExplanation: The operating system has not been loaded.Action: Load SERVER.NLM. If SERVER.NLM has been loaded and you still get this message, contact your Novell Authorized Reseller.PNW0241: Server public symbol symbol cannot be found.PNWxxxxExplanation: NetWare tried to find an external reference in the OS/2 loader that was not found.Action: Make sure the NetWare and NetWare for OS/2 versions are correct.PNW0243: LANSHARE was not loaded. NetWare Server has a dedicated LAN card.PNWxxxxExplanation: The LANSHARE.SYS file was not loaded. Without LANSHARE, you must install two network boards if you want NetWare Requester for OS/2 support.Action: No action is necessary if two network boards are desired. However, if you want the server and the OS/2 Requester to share a network board, load LANSHARE.SYS by modifying the CONFIG.SYS file.Note: Use the installation program for NetWare for OS/2 to perform this function.PNW0244: The LANSHARE board size (size) does not match the server buffer size (number).PNWxxxxExplanation: The buffer size for LANSHARE must match the buffer size in the server.Action: Modify the NET.CFG file Virtual MLID for LANSharing option to make it match the server's buffer size. For information about the NET.CFG file, see"BOOK="ws_osenu" COLLECTION="nw41"Creating or Editing NET.CFG" in NetWare Client for OS/2 User Guide.PAGENUM=822 ID="BP816"PNW0246: The NetWare server and NetWare for OS/2 are out of sync. Number unresolved server public symbols were encountered. Do you want to continue loading?  (y/n): yPNWxxxxExplanation: The version of NetWare for OS/2 the computer is using is not compatible with the version of NetWare that is running. Action: Make sure the computer is using the proper version of NetWare for OS/2 for the version of NetWare that is running. If the problem persists, contact your Novell Authorized Reseller.PNW0247: File name cannot be found.PNWxxxxExplanation: An attempt was made to load the file, but it could not be found in the path specified.Action: Make sure the path is correct and the file exists.PNW0248: Load file name is invalid. Error code: code.PNWxxxxExplanation: An NLM file format is invalid. The NLM could be corrupted, or it could be a version incompatible with NetWare for OS/2.Action: Contact the NLM developer or contact your Novell Authorized Reseller.PNW0249: An error occurred during attempt to read load file name.PNWxxxxExplanation: The read operation on a given NLM has failed. The file may be corrupted, or an internal system error may have occurred.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.PNW0250: The load file referenced an undefined public variable.PNWxxxxExplanation: The loader could not find an external reference that the NLM needed.Action: Make sure the version number of the NLM is correct for the version of NetWare that is running.PNW0251: Insufficient memory is available to load the operating system.PNWxxxxExplanation: The server must have at least 4 MB of memory to load the operating system.Action: Increase the amount of memory either by using the server memory entry in the NET.CFG or by using the runtime switch -om KB. For information about the NET.CFG file, see"BOOK="ws_osenu" COLLECTION="nw41"Creating or Editing NET.CFG" in NetWare Client for OS/2 User Guide.PAGENUM=823 ID="BP817"PNW0252: Attempt to initialize the operating system failed.PNWxxxxExplanation: This is an internal system error.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.PNW0253: The message file name is invalid.PNWxxxxExplanation: The file format of the indicated message file is invalid.Action: To get a new message file, contact your Novell Authorized Reseller.PAGENUM=824 ID="BP818"PRINT1: The message file name is invalid. The program cannot be loaded.PRINTExplanation: The .MSG file is invalid. This problem could be the result of a corrupted file, a bad translation, or an outdated file version.Action: Either update the .MSG file with a valid copy or delete the file, and the DOS Requester will use the default messages that are bound to the binary files.5: Module1.VLM is not loaded. The module2.VLM file cannot be loaded before module1.VLM. Load the module1.VLM file first then try to load the module2.VLM file.PRINTExplanation: The module2.VLM requires that the module1.VLM be loaded before module2.VLM can run effectively. Either the current configuration has module1.VLM and module2.VLM loading out of order, or module1.VLM did not load successfully.Action: Make sure that module1.VLM is configured to load before module2.VLM. To do this, change the load order of the VLM= parameter in the NET.CFG file.7: In order to load the module3.VLM, one of the following VLMs must be loaded: module1.VLM, module2.VLM.PRINTExplanation: The module3.VLM requires that module1.VLM or module2.VLM be loaded before module3.VLM can run effectively. Either the current configuration has module3.VLM loading before the Modules in the module1.VLM or module2.VLM list, or module1.VLM or module2.VLM did not load successfully.Action: Make sure that module1.VLM or module2.VLM loads successfully before trying to load module3.VLM.42: There is a missing or invalid value for `parameter' on line number of the configuration file. This entry will be ignored. Correct the line specified in the configuration file before continuing.PRINTExplanation: The configuration file contains a configuration keyword that has an invalid parameter or that does not specify a parameter. This invalid line will be ignored by the configuration process.Action: Because this line will be ignored, no action is required now. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message.PAGENUM=825 ID="BP819"43: There is a missing or invalid ON/OFF value for `parameter' on line number of the configuration file. This entry will be ignored. Correct the line specified in the configuration file before continuing.PRINTExplanation: The configuration file contains a configuration keyword that is defined to use either an ON or OFF parameter, but a different parameter, or no parameter, has been specified. This invalid line will be ignored by the configuration process.Action: Because this line will be ignored, no action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message.45: The parameter specified for the following option was out of range and has been adjusted.PRINTExplanation: A configurable parameter has been configured too high or too low to be valid. The invalid parameter is specified on the line following the message.Action: Correct the parameter specified in the NET.CFG file. For information on the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.PAGENUM=826 ID="BP820"PRINTCONID="FM21029"005: An error occurred while clearing the default print job. Error code: codePRINTCONExplanation: One of the following errors probably occurred:MARK=BULLETIf error code 7774 is displayed, another user may be reading the database.If error code 777C is displayed, the workstation is probably out of memory.The database may be damaged. Several error codes could be returned if this problem occurs.Action: Try one of the following, depending on the error that occurred:MARK=BULLETIf another user is reading the database, try to add the print job later.If the workstation does not have enough available memory, see "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network.If the PRINTCON database is damaged, restore the database from backup.For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 015: An error occurred while creating a Directory Services context.PRINTCONExplanation: One of the following errors probably occurred:MARK=BULLETThe connection with the server has been lost.The workstation has a memory problem or insufficient memory.There is a hardware problem in the workstation, server, or network equipment.Action: Try one of the following:MARK=BULLETMake sure that the server is up. If it is, check the cabling. Then try logging in to the server again.Find out how much program memory is available on the workstation. If needed, run a diagnostic test on the workstation memory. See "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network.PAGENUM=827 ID="BP821"Check hardware for problems. See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.020: An error occurred while deleting the print job. Error code: codePRINTCONExplanation: One of the following errors probably occurred:MARK=BULLETIf error code 7774 is displayed, another user may be reading the database.If error code 777C is displayed, the workstation is probably out of memory.The database may be damaged. Several error codes could be returned if this problem occurs.Action: Try one of the following, depending on the error that occurred:MARK=BULLETIf another user is reading the database, try again to add the mode later.If the workstation does not have enough available memory, see "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network.If the PRINTCON database seems to be damaged, restore the database from a backup.For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 030: Insufficient memory remains to allocate number bytes. Further modification of the PRINTCON database may not be possible at this time.PRINTCONAction: See "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network.035: An error occurred while reading the print job from the PRINTCON database. Error code: codePRINTCONExplanation: Another user may be reading the database, the workstation may be out of memory, or the database may be damaged.Action: See PRINTCON message IDREF="FM21029" "005: An error occurred while clearing the default print job. Error code: code" . For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. PAGENUM=828 ID="BP822"040: An error occurred while reading the form. Error code: codePRINTCONExplanation: Another user may be reading the database, the workstation may be out of memory, or the database may be damaged.Action: See PRINTCON message IDREF="FM21029" "005: An error occurred while clearing the default print job. Error code: code" . For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 045: An error occurred while reading the function. Error code: codePRINTCONExplanation: Another user may be reading the database, the workstation may be out of memory, or the database may be damaged.Action: See PRINTCON message IDREF="FM21029" "005: An error occurred while clearing the default print job. Error code: code" . For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 050: An error occurred while setting the default configuration. Error code: codePRINTCONExplanation: Another user may be reading the database, the workstation may be out of memory, or the database may be damaged.Action: See PRINTCON message IDREF="FM21029" "005: An error occurred while clearing the default print job. Error code: code" . For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 055: An error occurred while writing the new print job configuration to the PRINTCON database. Error code: code.PRINTCONExplanation: Another user may be reading the database, the workstation may be out of memory, or the database may be damaged.Action: See PRINTCON message IDREF="FM21029" "005: An error occurred while clearing the default print job. Error code: code"  For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. PAGENUM=829 ID="BP823"060: An error occurred writing the print job to the PRINTCON database. Error code: codePRINTCONExplanation: Another user may be reading the database, the workstation may be out of memory, or the database may be damaged.Action: See PRINTCON message IDREF="FM21029" "005: An error occurred while clearing the default print job. Error code: code" . For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 887: The name file could not be found.PRINTCONExplanation: The required SCHEMA.XLT file could not be found in any of the expected places.Action: See message IDREF="FM48610""907: This utility cannot open the translation table SCHEMA.XLT." in Appendix C.889: The name file found was the wrong version. The correct version is version.PRINTCONExplanation: The wrong version of the SCHEMA.XLT file was found.Action: See message IDREF="FM48610""907: This utility cannot open the translation table SCHEMA.XLT." in Appendix C.907: The Directory Services SCHEMA.XLT translation tables cannot be loaded.PRINTCONAction: See message IDREF="FM48610""907: This utility cannot open the translation table SCHEMA.XLT." in Appendix C.908: The Directory Services SCHEMA.XLT translation tables cannot be initialized.PRINTCONAction: See message IDREF="FM51165""908: The specified path is invalid." in Appendix C.970: The attempt to open the Unicode table files failed.PRINTCONAction: See message IDREF="FM15675""970: The attempt to open the Unicode table files failed." in Appendix C.971: The workstation does not have enough memory to load the Unicode table files.PRINTCONAction: See message IDREF="FM55341""971: The workstation does not have enough memory to load the Unicode table files." in Appendix C.972: Access to the Unicode table files was denied.PRINTCONAction: See message IDREF="FM90152""972: Access to the Unicode table files was denied." in Appendix C.PAGENUM=830 ID="BP824"973: The Unicode table files (*.001) cannot be found in the NLS directory or in the search drives.PRINTCONAction: See message IDREF="FM62778""973: The Unicode table files cannot be found in the NLS directory or in the search path. Code page: number Country: number" in Appendix C.973: The Unicode table files are corrupted.PRINTCONAction: See message IDREF="FM63405""974: The Unicode table files are corrupt." in Appendix C.975: The Unicode table files cannot be opened because there are already too many open files. Close some files or modify your CONFIG.SYS file.PRINTCONAction: See message IDREF="FM49793""975: The Unicode table files cannot be opened because there are already too many open files. Close some files or modify your CONFIG.SYS file." in Appendix C.998: The file name is version version; must be version version.PRINTCONAction: See message IDREF="FM91957""998: The message file found (utility_name.MSG) is an incorrect version. The correct version is number. See your network supervisor for assistance." in Appendix C.999: The utility cannot find the message file NWDSBRWS.MSG.PRINTCONAction: See message IDREF="FM69424""999: The message file for this utility cannot be found." in Appendix C.PAGENUM=831 ID="BP825"PRINTDEF005: An error has occurred while adding an element to the list of functions for this mode.PRINTDEFExplanation: The workstation does not have enough memory to build a complete list.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network.ID="FM35747"010: This function could not be added to this mode. Error code: codePRINTDEFExplanation: One of the following errors probably occurred:MARK=BULLETIf error code 7774 is displayed, another user may be reading the database.If error code 777C is displayed, the workstation is probably out of memory.The database may be damaged. Several error codes could be returned if this problem occurs.Action: Try one of the following, depending on the error that occurred:MARK=BULLETIf another user is reading the database, try to add the function later.If the workstation does not have enough available memory, see "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network.If the PRINTDEF database is damaged, restore the database from a backup.For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 015: An error has occurred while adding device name to the database. Error code: codePRINTDEFExplanation: Another user may be reading the database, the workstation may be out of memory, or the database may be damaged.Action: See the suggested actions for PRINTDEF message IDREF="FM35747" "010: This function could not be added to this mode. Error code: code" .PAGENUM=832 ID="BP826"020: An error has occurred while adding form name to the database. Error code: codePRINTDEFExplanation: Another user may be reading the database, the workstation may be out of memory, or the database may be damaged.Action: See the suggested actions for PRINTDEF message IDREF="FM35747" "010: This function could not be added to this mode. Error code: code" .025: An error has occurred while adding function name to the database. Error code: codePRINTDEFExplanation: Another user may be reading the database, the workstation may be out of memory, or the database may be damaged.Action: See the suggested actions for PRINTDEF message IDREF="FM35747" "010: This function could not be added to this mode. Error code: code" .030: An error has occurred while adding mode name to the database. Error code: codePRINTDEFExplanation: Another user may be reading the database, the workstation may be out of memory, or the database may be damaged.Action: See the suggested actions for PRINTDEF message IDREF="FM35747" "010: This function could not be added to this mode. Error code: code" .035: A network connection failure has occurred. Error code: codePRINTDEFExplanation: One of the following errors probably occurred:MARK=BULLETThe connection with the server has been lost.The workstation has a memory problem or insufficient memory.There is a hardware problem in the workstation, server, or network equipment.If the error code is 8801, you may have encountered a programming error. This error occurs when the user logs in as a bindery-based user, runs PRINTDEF, and then selects to import a device. When the error is displayed, and you press MOREINFO="NONE"<Enter> to continue, the computer is returned to the DOS prompt. This error has been corrected; the fix should be available on NetWire.Action: If this is not error 8801 described above, try one of the following:MARK=BULLETMake sure the server is up. If it is, check the cabling. Then log in to the server again.PAGENUM=833 ID="BP827"Find out how much program memory is available on the workstation. If needed, run a diagnostic test on the workstation memory. See "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network.See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 040: An error has occurred while creating the default context. Error code: codePRINTDEFExplanation: One or more of the following errors probably occurred:MARK=BULLETThe connection with the server has been lost.The workstation has a memory problem or insufficient available memory.The workstation, server, or network equipment has a hardware problem.Action: For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network and "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network.045: An error has occurred while deleting the device. Error code: codePRINTDEFExplanation: Another user may be reading the database, the workstation may be out of memory, or the database may be damaged.Action: See the suggested actions for PRINTDEF message IDREF="FM35747" "010: This function could not be added to this mode. Error code: code" .050: An error has occurred while deleting the form. Error code: codePRINTDEFExplanation: Another user may be reading the database, the workstation may be out of memory, or the database may be damaged.Action: See the suggested actions for PRINTDEF message IDREF="FM35747" "010: This function could not be added to this mode. Error code: code" .PAGENUM=834 ID="BP828"055: An error has occurred while deleting the function. Error code: codePRINTDEFExplanation: Another user may be reading the database, the workstation may be out of memory, or the database may be damaged.Action: See the suggested actions for PRINTDEF message IDREF="FM35747" "010: This function could not be added to this mode. Error code: code" . 060: An error has occurred while deleting the mode. Error code: codePRINTDEFExplanation: Another user may be reading the database, the workstation may be out of memory, or the database may be damaged.Action: See the suggested actions for PRINTDEF message IDREF="FM35747" "010: This function could not be added to this mode. Error code: code" . 065: An error has occurred while seeking information on the current object. Error code: codePRINTDEFExplanation: One of the following errors probably occurred:MARK=BULLETThe connection with the server has been lost.The workstation has a memory problem or insufficient memory.A hardware problem has occurred in the workstation, server, or network equipment.Action: Try one of the following:MARK=BULLETMake sure that the server is up. If it is, check the cabling. Then try logging in to the server again.Find out how much program memory is available on the workstation. If needed, run a diagnostic test on the workstation memory. See "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network.See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.PAGENUM=835 ID="BP829"070: An error has occurred while exporting device name. Error code: codePRINTDEFExplanation: Another user may be reading the database, the workstation may be out of memory, or the database may be damaged.Action: See the suggested actions for PRINTDEF message IDREF="FM35747" "010: This function could not be added to this mode. Error code: code" .072: An error has occurred while trying to open file name for writing. This may be due to an improper file name or some disk or directory problem. Error code: codePRINTDEFExplanation: An error occurred while trying to export a PDF file, and the open failed.Action: Make sure the user has appropriate user access rights to the disk or volume. Make sure the server is operating. Make sure the volume is mounted. For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A.075: An error has occurred while getting the current Directory Services context. Error code: codePRINTDEFExplanation: One of the following errors probably occurred:MARK=BULLETThe connection with the server has been lost.The workstation has a memory problem or insufficient memory.The workstation, server, or network equipment has a hardware problem.Action: Try one of the following:MARK=BULLETMake sure the server is up. If it is, check the cabling. Then try logging in to the server again.Find out how much program memory is available on the workstation. If needed, run a diagnostic test on the workstation memory. See "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network.See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. PAGENUM=836 ID="BP830"080: An error has occurred while importing device name. Error code: codePRINTDEFExplanation: Another user may be reading the database, the workstation may be out of memory, or the database may be damaged.Action: See the action for PRINTDEF message 010. 085: Insufficient memory remains to allocate number bytes of memory. Further modification of the PRINTDEF database may not be possible at this time.PRINTDEFExplanation: The workstation may not have enough available memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network.090: This function could not be removed from this mode. Error code: codePRINTDEFExplanation: Another user may be reading the database, the workstation may be out of memory, or the database may be damaged.Action: See the suggested actions for PRINTDEF message IDREF="FM35747" "010: This function could not be added to this mode. Error code: code" .095: An error has occurred while updating device name in the database. Error code: codePRINTDEFExplanation: Another user may be reading the database, the workstation may be out of memory, or the database may be damaged.Action: See the suggested actions for PRINTDEF message IDREF="FM35747" "010: This function could not be added to this mode. Error code: code" .100: An error has occurred while updating form name in the database. Error code: codePRINTDEFExplanation: Another user may be reading the database, the workstation may be out of memory, or the database may be damaged.Action: See the suggested actions for PRINTDEF message IDREF="FM35747" "010: This function could not be added to this mode. Error code: code" .PAGENUM=837 ID="BP831"105: An error has occurred while updating function name in the database. Error code: codePRINTDEFExplanation: Another user may be reading the database, the workstation may be out of memory, or the database may be damaged.Action: See the suggested actions for PRINTDEF message IDREF="FM35747" "010: This function could not be added to this mode. Error code: code" .110: An error has occurred while updating mode name in the database. Error code: codePRINTDEFExplanation: Another user may be reading the database, the workstation may be out of memory, or the database may be damaged.Action: See the suggested actions for PRINTDEF message IDREF="FM35747" "010: This function could not be added to this mode. Error code: code" .887: The name file could not be found.PRINTDEFExplanation: The required SCHEMA.XLT file could not be found in any of the expected places.Action: See message IDREF="FM48610""907: This utility cannot open the translation table SCHEMA.XLT." in Appendix C.889: The name file found was the wrong version. The correct version is version.PRINTDEFExplanation: The wrong version of the SCHEMA.XLT file was found.Action: See message IDREF="FM48610""907: This utility cannot open the translation table SCHEMA.XLT." in Appendix C.907: The Directory Services SCHEMA.XLT translation tables cannot be loaded. Error code: codePRINTDEFAction: See message IDREF="FM48610""907: This utility cannot open the translation table SCHEMA.XLT." in Appendix C.908: The Directory Services SCHEMA.XLT translation tables cannot be initialized. Error code: codePRINTDEFAction: See message IDREF="FM51165""908: The specified path is invalid." in Appendix C.PAGENUM=838 ID="BP832"970: The attempt to open the Unicode table files failed. Error code: codePRINTDEFAction: See message IDREF="FM15675""970: The attempt to open the Unicode table files failed." in Appendix C.971: The workstation does not have enough memory to load the Unicode table files.PRINTDEFAction: See message IDREF="FM55341""971: The workstation does not have enough memory to load the Unicode table files." in Appendix C.972: Access to the Unicode table files was denied.PRINTDEFAction: See message IDREF="FM90152""972: Access to the Unicode table files was denied." in Appendix C.973: The Unicode table files (*.001) cannot be found in the NLS directory or in the search drives.PRINTDEFAction: See message IDREF="FM62778""973: The Unicode table files cannot be found in the NLS directory or in the search path. Code page: number Country: number" in Appendix C.973: The Unicode table files are corrupted.PRINTDEFAction: See message IDREF="FM63405""974: The Unicode table files are corrupt." in Appendix C.975: The Unicode table files cannot be opened because there are already too many open files. Close some files or modify your CONFIG.SYS file.PRINTDEFAction: See message IDREF="FM49793""975: The Unicode table files cannot be opened because there are already too many open files. Close some files or modify your CONFIG.SYS file." in Appendix C.998: The utility_name.MSG file found is an incorrect version. The correct version is number.PRINTDEFAction: See message IDREF="FM91957""998: The message file found (utility_name.MSG) is an incorrect version. The correct version is number. See your network supervisor for assistance." in Appendix C.999: The browser message file name.MSG initialization failed, probably because the file could not be found. Error code: codePRINTDEFAction: See message IDREF="FM69424""999: The message file for this utility cannot be found." in Appendix C.PAGENUM=839 ID="BP833"PS2ESDIID="FM60636"005: ESDI controller cannot be initialized.PS2ESDIExplanation: The driver timed out while waiting for the disk controller to respond from initialization.Action: Try replacing the disk controller.010: Hardware needed for the ESDI controller cannot be reserved.PS2ESDIExplanation: The driver was not able to reserve the specified hardware.Action: Check for interrupt or port conflicts with the CLASS=DISKPS/2 setup diskette.015: ESDI controller cannot be added due to insufficient memory.PS2ESDIExplanation: An error occurred in registering the driver.Action: Unload other NLMs and try loading the driver first. Increase the available memory. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.020: You must allocate memory below 16 MB for disk driver DMA buffer. Unload modules and try loading the disk driver again.PS2ESDIExplanation: The driver was unable to allocate memory below 16 MB.Action: Unload other NLMs and try loading the driver first. Increase the available memory. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.PAGENUM=840 ID="BP834"PS2SCSI005: Card structures limit has been exceeded.PS2SCSIExplanation: The maximum number of controller boards this driver can support on the host computer has been exceeded. The driver's last attempt to load a device failed.Action: Load the driver for another network board, unload the driver and dismount all volumes. Load the driver again with the selected options to register the desired controller board.010: Device assignment is invalid. A hardware problem has occurred. Down the server and solve the hardware problem before continuing.PS2SCSIExplanation: When the driver is loaded, a network board reset is issued and all of the adapter ID numbers are set to zero. The driver then automatically assigns the seven SCSI bus IDs to the adapter numbers. If one or more SCSI bus IDs are identical, this message appears. The driver will not operate correctly until all of the device's SCSI ID conflicts have been resolved.Action: Turn off the host computer and make sure that all of the devices on the SCSI bus each device have a different SCSI ID.015: Card structure could not be allocated.PS2SCSIExplanation: This device driver could not be loaded. The operating system does not have enough contiguous memory to initialize the network board with the new configuration structure.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.020: Hardware options could not be reserved.PS2SCSIExplanation: This is a hardware conflict. The operating system or another NLM has already registered the hardware option that was selected when the driver was loaded.Action: Do one of the following:MARK=BULLETRemove the NLM that registered conflicting hardware.Change the hardware settings of the controller board that was selected.PAGENUM=841 ID="BP835"035: No request was found for device number with interrupt code number.PS2SCSIExplanation: The network board has an interrupt pending, but cannot find a corresponding request. This may be caused by a noisy bus or by a network board that is going bad.Action: If the problem persists, try another network board.040: No device structure was found for device number with interrupt code number.PS2SCSIExplanation: The network board has an interrupt pending but cannot find a corresponding device assignment.Action: None. This message is for information only.050: Unassignment command on device number produced an error.PS2SCSIExplanation: After a reset, all devices are unassigned, then reassigned. During this process, the network board would not allow the selected device to be reassigned.Action: Power down the computer to force all devices to reset to the cold boot state. Correct all ID conflicts, then reboot the computer. This reloads the SCSI drivers and restarts the NetWare operating system.055: Assignment command on device number produced an error.PS2SCSIExplanation: After a reset, all devices are unassigned, then reassigned. During the process, the network board would not allow the selected device to be assigned.Action: Power down the computer and then check all of the SCSI bus IDs for conflicts. This also forces all devices to reset to the cold boot state. Correct all ID conflicts, then reboot the computer. This reloads the SCSI drivers and restarts the NetWare operating system.060: Block size could not be set on tape device.PS2SCSIExplanation: The tape device is not responding to the SCSI command that was sent. For example, an attempt to set the block size to the device driver default value may have failed. All I/O operations to this device will be invalid.Action: Verify that this type of tape device can be used with this device driver. If it cannot, replace the tape device. If the device type is correct, unload the device driver, then reload it to force a device reset and reinitialization. If the problem persists, try another device.065: Slot number does not contain the IBM SCSI adapter card.PS2SCSIExplanation: The network board in the selected slot number is not responding. This slot may not contain a valid network board for this device driver.Action: Replace the network board or clean the network board's edge connector; then restart the computer.PAGENUM=842 ID="BP836"PSC007: More memory is required on your workstation to run PSC.PSCAction: See"BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network.014: The unload command to print server name could not be cancelled. See your network supervisor.PSCExplanation: The command could not be cancelled because an internal system error occurred. (The NWPSComCancelDownRequest call failed.)Action: Retry the operation. Be sure no associated problems have occurred (such as the network going down, a connection being lost, or previous errors having been ignored). If the problem persists, contact your Novell Authorized Reseller.045: An error occurred while getting the connection status. See your network supervisor.PSCExplanation: The operation could not be completed because an internal system error occurred. (The NWGetConnectionStatus call failed.)Action: Retry the operation. Be sure no associated problems have occurred (such as the network going down, a connection being lost, or previous errors having been ignored). If the problem persists, contact your Novell Authorized Reseller.064: An error occurred while creating a context. See your network supervisor.PSCAction: See message IDREF="FM32126""917: This utility was unable to set the context." in Appendix C.065: An error occurred while trying to get the default connection. See your network supervisor.PSCExplanation: The default connection could not be obtained because an internal system error occurred. (The NWGetDefaultConnectionID call failed.)Action: Retry the operation. Be sure no associated problems have occurred (such as the network going down, a connection being lost, or previous errors having been ignored). If the problem persists, contact your Novell Authorized Reseller.066: An error occurred while getting the connection type. See your network supervisor.PSCExplanation: The connection type could not be obtained because an internal system error occurred. (The NWIsDSAuthenticated call failed.)Action: Retry the operation. Be sure no associated problems have occurred (such as the network going down, a connection being lost, or previous errors having been ignored). If the problem persists, contact your Novell Authorized Reseller.PAGENUM=843 ID="BP837"074: Form #number could not be ejected. See your network supervisor.PSCExplanation: The form could not be ejected because an internal system error occurred. (The NWPSComEjectForm call failed.)Action: Retry the operation. Be sure no associated problems have occurred (such as the network going down, a connection being lost, or previous errors having been ignored). If the problem persists, contact your Novell Authorized Reseller.075: Form #number could not be mounted on printer number. See your network supervisor.PSCExplanation: The form could not be mounted on the indicated printer because an internal system error occurred. (The NWPSComSetMountedForm call failed.)Action: Retry the operation. Be sure no associated problems have occurred (such as the network going down, a connection being lost, or previous errors having been ignored). If the problem persists, contact your Novell Authorized Reseller.076: Printer number could not be started. See your network supervisor.PSCExplanation: The indicated printer could not be started because an internal system error occurred. (The NWPSComStartPrinter call failed.)Action: Retry the operation. Be sure no associated problems have occurred (such as the network going down, a connection being lost, or previous errors having been ignored). If the problem persists, contact your Novell Authorized Reseller.077: Printer number could not be stopped. See your network supervisor.PSCExplanation: The indicated printer could not be stopped because an internal system error occurred. (The NWPSComStopPrinter call failed.)Action: Retry the operation. Be sure no associated problems have occurred (such as the network going down, a connection being lost, or previous errors having been ignored). If the problem persists, contact your Novell Authorized Reseller.078: The current job on printer number could not be aborted. See your network supervisor.PSCExplanation: The current print job cannot be aborted because an internal system error occurred. (The NWPSComAbortPrintJob call failed.)Action: Retry the operation. Be sure no associated problems have occurred (such as the network going down, a connection being lost, or previous errors having been ignored). If the problem persists, contact your Novell Authorized Reseller.PAGENUM=844 ID="BP838"079: Printer number could not be marked. See your network supervisor.PSCExplanation: The indicated printer could not be marked because an internal system error occurred. (The NWPSComMarkTopOfForm call failed.)Action: Retry the operation. Be sure no associated problems have occurred (such as the network going down, a connection being lost, or previous errors having been ignored). If the problem persists, contact your Novell Authorized Reseller.081: Network printer number did not change mode. See your network supervisor.PSCExplanation: The indicated printer did not change mode because an internal system error occurred. (The NWPSComSetRemoteMode call failed.)Action: Retry the operation. Be sure no associated problems have occurred (such as the network going down, a connection being lost, or previous errors having been ignored). If the problem persists, contact your Novell Authorized Reseller.082: Attempt to attach to NetWare server failed. Verify NetWare server name.PSCExplanation: The attempt to attach to the server failed either because the server is not running, or because an internal system error occurred. (The NWAttachToFileServer call failed.)Action: Retry the operation. Be sure no associated problems have occurred (such as the network going down, a connection being lost, or previous errors having been ignored). If the problem persists, contact your Novell Authorized Reseller.083: Printer number could not be paused. See your network supervisor.PSCExplanation: The indicated printer could not be paused because an internal system error occurred. (The NWPSComPausePrinter call failed.)Action: Retry the operation. Be sure no associated problems have occurred (such as the network going down, a connection being lost, or previous errors having been ignored). If the problem persists, contact your Novell Authorized Reseller.100: The NWGetMonitoredConnection call failed. Error code: code Try again. If the error persists, notify your network supervisor.PSCAction: For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.970: The attempt to open the Unicode table files failed.PSCAction: See message IDREF="FM15675""970: The attempt to open the Unicode table files failed." in Appendix C.PAGENUM=845 ID="BP839"971: The workstation does not have enough memory to load the Unicode table files.PSCAction: See message IDREF="FM55341""971: The workstation does not have enough memory to load the Unicode table files." in Appendix C.972: Access to the Unicode table files was denied.PSCAction: See message IDREF="FM90152""972: Access to the Unicode table files was denied." in Appendix C.973: The Unicode table files cannot be found in the NLS directory or in the search path. Code page: <number>  Country:  <number>PSCAction: See message IDREF="FM62778""973: The Unicode table files cannot be found in the NLS directory or in the search path. Code page: number Country: number" in Appendix C.974: The Unicode table files are corrupt.PSCAction: See message IDREF="FM63405""974: The Unicode table files are corrupt." in Appendix C.975: The Unicode table files cannot be opened because there are already too many open files. Close some files or modify your CONFIG.SYS file.PSCAction: See message IDREF="FM49793""975: The Unicode table files cannot be opened because there are already too many open files. Close some files or modify your CONFIG.SYS file." in Appendix C.998: The message file found (<utility_name>.MSG) is an incorrect version. The correct version is <number>. See your network supervisor for assistance.PSCAction: See message IDREF="FM91957""998: The message file found (utility_name.MSG) is an incorrect version. The correct version is number. See your network supervisor for assistance." in Appendix C.999: The message file for this utility cannot be found.PSCAction: See message IDREF="FM69424""999: The message file for this utility cannot be found." in Appendix C.PAGENUM=846 ID="BP840"PSERVER2: Insufficient memory is available to initialize client communications.PSERVERExplanation: The server running PSERVER does not have enough available memory to run the print server.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.4: The program does not have enough available memory to continue.PSERVERExplanation: The server does not have enough available memory to run the PSERVER NLM.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.7: The program cannot create utilization processes.PSERVERExplanation: The print server may not have enough available memory to initialize.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.8: The program cannot initialize the kernel.PSERVERExplanation: The print server may not have enough available memory to initialize.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.9: The program cannot create a console process.PSERVERExplanation: The print server may not have enough available memory to initialize.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.11: The Service Advertising name, name, is already in use by another print server.PSERVERExplanation: All print servers running on the same internet must have unique SAP names. Another print server with the same name is already running.Action: Rename one of the print servers, or change the SAP name using PCONSOLE.13: The program cannot create the advertising process.PSERVERExplanation: The print server may not have enough available memory to initialize.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.PAGENUM=847 ID="BP841"17: The program cannot open the client communications socket.PSERVERExplanation: The socket number assigned to the print server for client communications is in use by another process.Action: Determine which process is using the print servers socket and unload the process. If the problem persists, contact your Novell Authorized Reseller.18: There is insufficient memory for the print server to add an additional printer.PSERVERExplanation: The print server does not have enough available memory for another printer.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.19: The program cannot create client service processes.PSERVERExplanation: The print server may not have enough available memory to initialize.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.20: All send buffers have been consumed.PSERVERExplanation: A network communications error occurred, causing all the print server communication buffers to be consumed without being freed.Action: Until you can locate the communication problem, unload and reload the print server to reinitialize its communication buffers.26: The program cannot create the down monitor process.PSERVERExplanation: The print server may not have enough available memory to initialize.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.28: A bad process ID was passed to the kernel.PSERVERExplanation: An internal print server error occurred.Action: Until you can locate the problem, unload and reload the print server to reinitialize its communication buffers.29: A host device was not specified in the print server's Directory Services attribute list, the print server will attempt to use the local server as a host device.PSERVERExplanation: Two possible explanations for this message are known:MARK=BULLETThe print server object was created in bindery mode with a pre-4.02 server, and it could not be accessed when you are logged in as a NetWare Directory Services user.PAGENUM=848 ID="BP842"During the in-place migration from NetWare 3.1x to NetWare 4, NetWare Directory Services objects were not created for the print server and print queues.Action: If you do not plan to use auditing, no action is necessary. If you do plan to use auditing, delete the print server object. Recreate it using a server version 4.02 or newer; then reattach the printers.64: Insufficient memory is available to create the main menu. The print server console will be disabled.PSERVERExplanation: The print server may not have enough available memory to initialize.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.79: The program cannot create the server status form.PSERVERExplanation: The print server may not have enough available memory to initialize.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.80: The program cannot push the main menu.PSERVERExplanation: The print server may not have enough available memory to initialize.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.81: Insufficient memory is available to build a NetWare server list.PSERVERExplanation: The print server may not have enough available memory to initialize.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.88: The program cannot get the object ID for the print server.PSERVERExplanation: Directory Services, which must be opened to get object IDs, is locked or corrupted. Directory Services is usually locked only momentarily.Action: Try again in a few minutes. Run DSREPAIR if the error persists.89: The print server is already attached to too many NetWare servers and cannot attach to NetWare server name.PSERVERExplanation: A print server queue can be serviced by up to 25 print servers. Twenty-five servers are already attached and servicing this queue.Action: If the print server needs to service this queue, detach one of the other print servers from the queue.PAGENUM=849 ID="BP843"90: NetWare server name is unknown at this time.PSERVERExplanation: You may have mistyped the name of the server, specified a server that is not on the network, or specified a server that is down for maintenance.Action: Use the NLIST command to list all the servers that the station can recognize. Type the name of the server correctly. If the server is down for maintenance, try the command when the server is back up. 91: The NetWare server's bindery is locked. You cannot attach to NetWare server name at this time.PSERVERExplanation: The network supervisor locked the bindery for maintenance. Usually this situation is only temporary.Action: Try the command when the server is back up. 92: You cannot attach to NetWare server name because it has no more connections available.PSERVERExplanation: The print server needs one connection slot to run. All 100 connection slots are in use.Action: Wait until a connection slot becomes available. You can use MONITOR to clear a connection.93: NetWare server name does not respond.PSERVERExplanation: The specified server is down.Action: No action can be taken until the server is up and running again.94: You cannot attach to NetWare server name at this time.PSERVERExplanation: A network error prevented the print server from attaching to the specified server.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.95: The print server has no account balance on NetWare server name.PSERVERExplanation: Accounting is installed on the specified server, but an error occurred that has given the print server a zero balance.Action: Make sure that you are using a NetWare 4 version of NETADMIN or NetWare Administrator with the specified server. Either delete the print server and recreate it, or remove accounting and reinstall accounting.PAGENUM=850 ID="BP844"MARK=BULLETTo delete the print server, run PCONSOLE, select Print Server Information, and delete the print server from the list. Then recreate the print server.To delete accounting, run NETADMIN or NetWare Administrator and select "Accounting;" then select "Accounting Servers." Delete all servers from the list. Press MOREINFO="NONE"<Esc> and answer "Yes" to the prompt to remove accounting. Then reinstall accounting.96: The print server has no credit left on NetWare server name.PSERVERExplanation: Accounting was installed on the specified server with a version of SYSCON below NetWare 3.11 or NetWare 2.2. You should be using a NetWare 4 version of NETADMIN.Action: Make sure that you are using a NetWare 4 version of NETADMIN with the specified server. Then either delete the print server and recreate it, or remove accounting and reinstall accounting.MARK=BULLETTo delete the print server, run PCONSOLE, select Print Server Information, and delete the print server from the list. Then recreate the print server.To delete accounting, run NETADMIN or NetWare Administrator and select "Accounting," then select "Accounting Servers." Delete all servers from the list. Press MOREINFO="NONE"<Esc> and answer "Yes" to the prompt to remove accounting. Then reinstall accounting.97: Account on NetWare server name was disabled because of intruder detection.PSERVERExplanation: The login property for intruder detection is set. NetWare does not have a program that sets this property for print servers. Either the bindery is corrupted, or you have used a third-party program to set this property.Action: Complete one of the following:MARK=BULLETIf you have not used a third-party utility to set this property, run BINDFIX on the bindery server.If you have a third-party program that sets this property, use it to remove the station restriction.98: The supervisor has limited the number of concurrent connections the print server can have on NetWare server name.PSERVERExplanation: The print server reached the allowed limit for concurrent connections to the file server.Action: None. This message is for information only.PAGENUM=851 ID="BP845"99: The supervisor has disabled the print server's account on NetWare server name.PSERVERExplanation: The print server no longer has an account on the server.Action: If you have appropriate rights, establish a new account for the print server.100: Login was attempted at an unauthorized time. The supervisor on NetWare server name has limited the times when the print server can log in.PSERVERExplanation: Specific time periods have been established when you can use the print server. You cannot use the print server until the next authorized time period.Action: Give the user a list of authorized time periods.101: Login was attempted from an unauthorized station. The supervisor on NetWare server name has limited the stations the print server can log in from.PSERVERExplanation: The user tried to access a print server from an unauthorized workstation. A network supervisor can limit login access to a print server to one or more workstations.Action: Make sure the user attempts to access the print server account only from authorized workstations.102: The password on NetWare server name has expired. All grace logins have been used. Access is denied.PSERVERExplanation: The login properties that force expiration of passwords and limit grace logins have been set. NetWare does not have a program that sets these properties for print servers. Either the bindery is corrupted, or you have used a third-party program to set this property.Action: Complete one of the following:MARK=BULLETIf you have a third-party program that sets this property, use it to remove the login properties.Use PCONSOLE to change the print server's password.103: The supervisor on NetWare server name has disabled logins.PSERVERExplanation: The user's account is locked. The network supervisor can disable the login function temporarily to prevent users from logging in or attaching during maintenance. Most likely, the network supervisor is doing maintenance work.Action: This condition is usually only temporary.The user should be able to log in after the login function is enabled. Meanwhile, the user can attach to another server and use its printer.PAGENUM=852 ID="BP846"105: The print server's password on NetWare server name has expired. Please change it.PSERVERExplanation: The password for logging in to the print server must be changed periodically. The time period for using the current password expired.Action: If you are an authorized print server operator or network supervisor, change the password. 106: Access to NetWare server name denied. Either there is no account for this print server on the NetWare server, or the password was incorrect.PSERVERExplanation: The print server's name or password was entered incorrectly.Action: Type the print server's name and password correctly.107: You cannot log in to NetWare server name at this time.PSERVERExplanation: The specified server returned a condition that prevented the print server from logging in to the server.Action: Try again later. If the problem persists, contact your Novell Authorized Reseller.108: The print server is already attached to NetWare server name.PSERVERExplanation: You tried to attach to a server that you are already attached to.Action: None. This message is for information only.110: The program cannot create the user interface because of problems in the current environment.PSERVERExplanation: The print server may not have enough available memory to initialize.Action: Increase the memory in the server, or reduce the number of printers configured, queues serviced, or users notified. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.111: Insufficient memory is available for the buffer for printer number, name. The printer was not initialized. Requested buffer size was number KB.PSERVERAction: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.112: Insufficient memory is available to initialize printer number, name.PSERVERExplanation: The server that is running PSERVER does not have enough available memory to do one of the following:MARK=BULLETRun the print server.PAGENUM=853 ID="BP847"Service remote printers.Add services.Add the specified user to the notify list of the specified printer.Add the specified printer.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.113: The program cannot read the configuration file for printer number. The printer was not initialized.PSERVERExplanation: The configuration file for the specified printer is corrupted.Action: Run PCONSOLE, delete the printer from the print server, and re-create the printer.114: Printer number, name, is of an unknown type. The printer was not initialized.PSERVERExplanation: The Directory Services for the specified printer may be corrupted.Action: Run DSREPAIR.115: The program cannot create the printer driver process for printer number, name. The printer is not initialized.PSERVERExplanation: The print server may not have enough available memory to initialize.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.123: Network printer communications are not initialized. Network printers cannot be installed. Printer number, name was not installed.PSERVERExplanation: The print server may not have enough available memory to initialize.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.124: The program cannot open a socket for network printer communications. Network printers will not be initialized.PSERVERExplanation: The socket assigned to the print server for communication with remote printers is in use by another process.Action: Find the process that opened the print servers communication socket and unload it.125: Insufficient memory is available to initialize network printer communications. Network printers cannot be installed.PSERVERAction: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.PAGENUM=854 ID="BP848"127: Print queue name is unknown. The print queue will not be serviced by printer number, name.PSERVERExplanation: The specified queue was deleted, but the specified printer's configuration file was not modified to reflect the deletion.Action: Use PCONSOLE to either recreate the queue or delete the queue from the printer's configuration file.128: Print queue name was not added to the list of queues to be serviced by printer number, name, because it was already in the list.PSERVERExplanation: Two queues in the list of queues to be serviced have the same name.Action: Run PCONSOLE and select "Print Server Information"; then select the print server. Select "Print Server Configuration"; then select "Queues Service by Printer." Select the printer specified in the message. Delete the duplicate queue named in the list.129: Print queue name cannot be serviced by printer number, name, because a print queue operator has disabled print servers from attaching to the print queue.PSERVERExplanation: A print server operator set the "Servers Can Service Entries in Queue" option in PCONSOLE to No. This prevents print servers from attaching and servicing the specified queue.Action: Run PCONSOLE and set the "Servers Can Service Entries in Queue" option to Yes. This allows print servers to attach and service the queue.130: This print server is not authorized to service queue name. Queue will not be serviced by printer number, name.PSERVERExplanation: The print server must be authorized by the network supervisor to service print queues.Action: Use PCONSOLE to authorize the print server to service the desired queue.131: Print queue name cannot be serviced by printer number, name, because you have already reached the maximum number of print servers that can be attached to the print queue.PSERVERExplanation: The maximum number of print servers that can be attached to a print queue at the same time has been reached.Action: Detach one of the print servers from the queue.PAGENUM=855 ID="BP849"132: Print queue name cannot be serviced by printer number, name.PSERVERExplanation: The server returned a condition that prevented the specified queue from being serviced by the specified printer.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.133: Insufficient memory is available to add queue name to printer number, name. The queue will not be serviced by this printer.PSERVERExplanation: The print server may not have enough available memory to initialize.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.137: Insufficient memory is available to create a printer list.PSERVERExplanation: The print server may not have enough available memory to initialize.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.164: The program cannot save the printer list.PSERVERExplanation: The print server may not have enough available memory to initialize.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.165: The program cannot create the printer status form.PSERVERExplanation: The print server may not have enough available memory to initialize.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.172: Insufficient memory is available to create a queue list.PSERVERExplanation: The print server may not have enough available memory to initialize.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.174: The program cannot create network printer communications processes.PSERVERExplanation: The print server may not have enough available memory to initialize.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.176: Insufficient memory is available to get an IPX socket resource tag for print server communication.PSERVERExplanation: The print server may not have enough available memory to initialize.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.PAGENUM=856 ID="BP850"178: Insufficient memory is available to get an alloc resource tag for the print server interface.PSERVERExplanation: The print server may not have enough available memory to initialize.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.179: The program cannot create a background process.PSERVERExplanation: The print server may not have enough available memory to initialize.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.180: Insufficient memory is available to get a polling resource tag for the print server.PSERVERExplanation: The print server may not have enough available memory to initialize.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.182: Insufficient memory is available to get an interrupt resource tag for the print server.PSERVERExplanation: The print server may not have enough available memory to initialize.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.183: An error occurred during attempt to write to the audit file name. The entry was not logged.PSERVERExplanation: One of the following could cause this error:MARK=BULLETThe print server has insufficient rights to the file or directory containing the log file.The file is flagged so that it cannot be written to.The directory that contained the file has been deleted.Action: Use PCONSOLE to determine where the print server is keeping its audit file. Verify that the directory exists and that the print server has sufficient rights to write to the directory and file. Verify that the file is not flagged Read Only.184: Insufficient memory is available to get a resource tag for printer ports.PSERVERExplanation: The print server may not have enough available memory to initialize.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.PAGENUM=857 ID="BP851"185: The print server received error code during attempt to log in to the network. Access to the network was denied. Verify that the print server name and password are correct.PSERVERExplanation: You probably specified an invalid print server name or password.Action: Try again, making sure that the print server is running and that you type a valid print server name and password. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 186: Insufficient memory is available to get an AES event resource tag.PSERVERExplanation: The print server may not have enough available memory to initialize.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.190: Insufficient memory is available to add a new print queue.PSERVERAction: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.191: The program cannot save the current print queue list.PSERVERExplanation: The print server may not have enough available memory to initialize.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.205: Insufficient memory is available to add usertype username to the notification list for printer number, name.PSERVERAction: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.214: The print server was unable to login to server name specified in the print server's Directory Services attribute list as the host device. Warning, the job audit logging feature may not function properly.  Program execution may not continue normally.PSERVERExplanation: During login, if the server that contains the audit files is not available, this message will appear. If the user ignores the message, everything will proceed normally, but auditing will not be enabled.Action: If you do not plan to use auditing, no action is necessary. If you wish to use auditing, find out why the specified server is not available (perhaps the server is down, or a router is malfunctioning). When the server is available, load PSERVER again, and auditing will be enabled.PAGENUM=858 ID="BP852"217: The print server could not get a Directory Services context handle. Error code: code.PSERVERExplanation: NetWare Directory services returned an error to PCONSOLE during an attempt to establish a context handle.Action: For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 224: The program cannot initialize the notification process. Error notices will not be sent to users.PSERVERExplanation: The print server may not have enough available memory to initialize.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.228: Insufficient memory is available for the print server to service print jobs at this time.PSERVERExplanation: The print server may not have enough available memory to initialize.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.240: Invalid or missing printer configuration information was specified for printer name.PSERVERExplanation: The print server was unable to interpret the configuration information for the printer.Action: Using PCONSOLE, either reconfigure the printer, or delete and add it again.241: An error (code) occurred during attempt to add print queue name. This queue will not be serviced by printer_number, printer_name.PSERVERExplanation: An error occurred during an attempt to add the queue to the printer.Action: For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A.242: An error (code) occurred during attempt to add object name to the notification list. This object will not be notified of printer errors for printer number, name.PSERVERExplanation: An error occurred during an attempt to add the object to the notify list.Action: For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 247: Attempt to add printer name as printer number failed. A printer already exists with that number.PSERVERExplanation: The print server is configured to service two printers with the same number. Each printer serviced by the print server must have a unique number for that print server.Action: Use PCONSOLE to change one of the printers' numbers.PAGENUM=859 ID="BP853"268: There is insufficient memory for the print server to complete the requested task.PSERVERExplanation: The print server does not have enough available memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.269: An error occurred attempting to read the audit file name. The audit file may be corrupted.PSERVERExplanation: The print server was unable to successfully read its audit file. One of the following should account for the error:MARK=BULLETThe file may be corrupted.The print server has insufficient rights to the file or directory where it keeps its log file.The file is flagged so that it cannot be written to.The directory where the print server configuration file is located has been deleted.Action: Use PCONSOLE to determine where the print server is keeping its audit. Verify that the directory exists and that the print server has sufficient rights to write to the directory and file. Verify that the file is not flagged Read Only. If you suspect file corruption, delete the file; then use PCONSOLE to enable audit tracking again.275: The print server encountered an error (code) while attempting to set a Directory Services context handle.PSERVERExplanation: An error occurred during an attempt to access the Directory.Action: For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A.276: There is insufficient memory to browse the directory.PSERVERExplanation: The server does not have enough available memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.277: The print server encountered an error (code) attempting to read a Directory Services context.PSERVERExplanation: An error occurred during an attempt to access the directory.Action: For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A.PAGENUM=860 ID="BP854"278: The print server encountered an error (code) while attempting to search the directory.PSERVERExplanation: An error occurred during an attempt to search the directory.Action: For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A.279: The print server encountered an error (code) while attempting to access the directory.PSERVERExplanation: An error occurred during an attempt to access the directory.Action: For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A.280: The print server was unable to build a list of objects in the directory. An unexpected Directory Services error occurred while attempting to read the directory.PSERVERExplanation: An error occurred during an attempt to build an object list in the Directory.Action: Run DSREPAIR.999: The message file for this NLM cannot be found.PSERVERAction: See message IDREF="FM69424""999: The message file for this utility cannot be found." in Appendix C.PAGENUM=861 ID="BP855"PUPGRADE6: The main menu for PUPGRADE cannot be created.PUPGRADEExplanation: The server does not have enough memory to complete this operation.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.16: The NET$PRN.DAT file is corrupt.PUPGRADEExplanation: The PRINTDEF database from NetWare 3.11 was invalid. The header was not of the expected value. This probably means that the 3.11 version of PRINTDEF terminated in some unexpected way.Action: Recreate the PRINTDEF database after upgrading. Either enter the data manually in PRINTDEF or import the PDF files that come with NetWare 4.17: Error number occurred during attempt to open status log filename. No log of this upgrade will be kept.PUPGRADEExplanation: A log is kept for each upgrade. The file could not be opened to keep a log. This error can occur for one of the following reasons:MARK=BULLETThe user does not have rights to SYS:SYSTEM. You may need to log in as Supervisor to run PUPGRADE.The server is out of disk space.Action: Try one or more of the following:MARK=BULLETNormally, a log is kept so you can complete the upgrade and correct errors later. Since you will not have a log, view the status a page at a time instead of pressing "C" to have the status scroll by continuously. This way, you can take notes manually as errors occur. Correct the errors after all status messages have been displayed.Increase the available disk space on the volume. "BOOK="superenu" COLLECTION="nw41"Resolving Server Disk Space Problems" in Supervising the Network.PAGENUM=862 ID="BP856"18: Error number occurred during attempt to write the log file name. No further entries will be made in the log file.PUPGRADEExplanation: This error usually indicates that the server has run out of disk space. It may also indicate a disk failure.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Disk Space Problems" in Supervising the Network. If lack of disk space is not the problem, see "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.25: A status portal cannot be created.PUPGRADEExplanation: The server does not have enough memory to complete this operation.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.28: A work buffer for PRINTCON data cannot be obtained.PUPGRADEExplanation: The server does not have enough memory to complete this operation.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.33: An I/O error occurred during attempt to access old bindery files.PUPGRADEExplanation: Because PUPGRADE is migrating bindery data, it must be able to access old data. For some reason, it could not do so. This error may indicate a corruption problem in the old bindery; however, if this were the case, the error probably would have shown up during the regular upgrade.Action: Instead of using PUPGRADE, use PCONSOLE to redefine the print servers and printers manually. Use PRINTDEF to redefine the printer definitions. Use PRINTCON to redefine the print job configurations.38: PUPGRADE was unable to create a Directory Services context.PUPGRADEExplanation: The server does not have enough memory to complete this operation.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.48: Error number occurred during attempt to open NET$PRN.DAT file.PUPGRADEExplanation: This is probably a rights problem. You probably need to be logged in as Supervisor to run PUPGRADE.Action: Log in as Supervisor.PAGENUM=863 ID="BP857"53: Error number occurred during attempt to get the length of the NET$PRN.DAT file.PUPGRADEExplanation: A disk I/O error may have occurred during the attempt to use PUPGRADE.Action: Use PRINTDEF to redefine the printer definitions. See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.57: Memory is not available to process the NET$PRN.DAT file.PUPGRADEExplanation: The server does not have enough memory to complete this operation.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.58: Error number occurred during attempt to read the NET$PRN.DAT file.PUPGRADEExplanation: A disk I/O error may have occurred during the attempt to use PUPGRADE.Action: Redefine the printer definitions using PRINTDEF. See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.59: Error number occurred during attempt to delete the old NET$PRN.DAT file.PUPGRADEExplanation: PUPGRADE was unable to delete the old NET$PRN.DAT file, even though you told it to. The file is normally flagged Read-Only, but PUPGRADE changes this flag so the file can be deleted. One possible reason for PUPGRADE being unable to delete this file is that the file was flagged differently than it should have been.Action: Normally, this is not a serious problem and you can simply leave the old file where it is. However, if you are concerned about wasted disk space, use FILER to delete the file from SYS.PUBLIC. (If you expect to have people logging in as bindery users, delete the old file.)65: The new object ID cannot be obtained.PUPGRADEExplanation: An object may have been deleted since you upgraded, but before you ran PUPGRADE.Action: Instead of using PUPGRADE, use PCONSOLE to redefine the print servers and printers manually. Use PRINTDEF to redefine the printer definitions. Use PRINTCON to redefine the print job configurations.71: An error occurred during attempt to create a portal.PUPGRADEExplanation: The server does not have enough memory to complete this operation.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.PAGENUM=864 ID="BP858"75: The mode cannot be written to the database.PUPGRADEExplanation: An unknown error has prevented PUPGRADE from adding the mode to the database.Action: Redefine the printer definitions using PRINTDEF.78: The Print Server menu cannot be created.PUPGRADEExplanation: The server does not have enough memory to complete this operation.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.90: A Directory context cannot be created.PUPGRADEExplanation: The server does not have enough memory to complete this operation.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.91: Directory context cannot be set. Error code: code.PUPGRADEExplanation: Either you typed in the NetWare Directory Services object name incorrectly or the server does not have enough memory to set up the context.Action: Type in the object name correctly. Increase the available memory. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A.99: An error occurred during attempt to read bindery files on server name.PUPGRADEExplanation: Because PUPGRADE is migrating bindery data, it must be able to access old data. For some reason, it could not do so. This error may indicate a corruption problem in the old bindery; however, if this were the case, the error probably would have shown up during the regular upgrade.Action: Instead of using PUPGRADE, use PCONSOLE to redefine the print servers and printers manually. Use PRINTDEF to redefine the printer definitions. Use PRINTCON to redefine the print job configurations.101: An error occurred during attempt to read the upgrade history file on server name.PUPGRADEExplanation: The user may not have the rights equivalent to a network supervisor that are necessary to use PUPGRADE.Action: If possible, log in as Supervisor. Otherwise, instead of using PUPGRADE, use PCONSOLE to redefine the print servers and printers manually. Use PRINTDEF to redefine the printer definitions. Use PRINTCON to redefine the print job configurations.PAGENUM=865 ID="BP859"107: PUPGRADE was unable to allocate a context handle in order to search the directory.PUPGRADEExplanation: The server does not have enough memory to complete this operation.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.108: PUPGRADE was unable to set a Directory Services context in order to search the directory. Error code: code.PUPGRADEExplanation: Either you typed in the NetWare Directory Services object name incorrectly or the server does not have enough memory to set up the context.Action: Type in the correct object name. Increase the available memory. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 109: There is insufficient memory for PUPGRADE to search the directory.PUPGRADEExplanation: The server does not have enough memory to complete this operation.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.110: PUPGRADE was unable to read a Directory Services context. Error code: code.PUPGRADEExplanation: NetWare Directory Services returned an unexpected error to PUPGRADE.Action: For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 111: PUPGRADE was unable to create a list to display the contents of the current directory.PUPGRADEExplanation: The server does not have enough memory to complete this operation.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.113: PUPGRADE received an unexpected error while attempting to search the directory. Error code:  code.PUPGRADEExplanation: NetWare Directory Services returned an unexpected error to PUPGRADE.Action: For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 114: PUPGRADE received an unexpected error while attempting to access the directory. Error code: code.PUPGRADEExplanation: NetWare Directory Services returned an unexpected error to PUPGRADE.Action: For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. PAGENUM=866 ID="BP860"117: PUPGRADE was unable to set the Directory Services context.PUPGRADEExplanation: Either you typed in the NetWare Directory Services object name incorrectly or the server does not have enough memory to set up the context.Action: Type the object name correctly. Increase the available memory. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.PAGENUM=867 ID="BP861"PURGE005: This utility was unable to find all erased files in the current directory. Error code: code.PURGEExplanation: The PURGE utility was scanning for all deleted files when an error occurred. The error code identifies the type of error that occurred.Action: For information about the specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 010: You don't have sufficient rights in the current directory to purge files.PURGEExplanation: The user must have the Delete right to the directory to purge files in the directory.Action: If appropriate, grant the Delete right to the user.015: You don't have sufficient rights to purge filename.PURGEExplanation: The user must have the Delete right to this file to purge it.Action: If appropriate, grant the Delete right to the user.020: This utility was unable to purge filename. Error code: code.PURGEAction: For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 100: This utility was unable to allocate a temporary directory handle to the specified path. Error code: code.PURGEAction: For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 110: This utility was unable to get the effective rights for the current directory. Error code: code.PURGEExplanation: The utility was searching for the Delete right but was unable to find the user's effective rights. The error code identifies the type of error that occurred.Action: For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 115: This utility only works on network drives.PURGEExplanation: A local drive was probably specified. PURGE works only on network drives.Action: Specify only network drives.120: This utility was unable to purge erased files on server name. Error code: code.PURGEAction: For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. PAGENUM=868 ID="BP862"901: You are not attached to server name.PURGEAction: See message IDREF="FM84261""901: You are not attached to the specified server." in Appendix C.903: The command line syntax is invalid. For help, type PURGE /?.PURGEAction: See message IDREF="FM18860""903: The command line syntax is invalid." in Appendix C.908: The specified path is invalid. PURGEAction: See message IDREF="FM51165""908: The specified path is invalid." in Appendix C.909: You are not mapped to the specified drive.PURGEAction: See message IDREF="FM28663""909: You are not mapped to the specified drive." in Appendix C.916: This utility only supports 25 levels of directories.PURGEAction: See message IDREF="FM77950""916: This utility only supports 25 levels of directories." in Appendix C.925: This utility is not supported on Personal NetWare Servers. Use the Personal NetWare utilities.PURGEAction: See message IDREF="FM67645""925: The server specified is a Personal NetWare server. You cannot attach to a Personal NetWare server with this utility. Use the Personal NetWare utilities to access this connection." in Appendix C970: The attempt to open the Unicode table files failed.PURGEAction: See message IDREF="FM15675""970: The attempt to open the Unicode table files failed." in Appendix C.971: The workstation does not have enough memory to load the Unicode table files.PURGEAction: See message IDREF="FM55341""971: The workstation does not have enough memory to load the Unicode table files." in Appendix C.972: Access to the Unicode table files was denied.PURGEAction: See message IDREF="FM90152""972: Access to the Unicode table files was denied." in Appendix C.973: The Unicode table files cannot be found in the NLS directory or in the search path. Code page: <number>  Country:  <number>PURGEAction: See message IDREF="FM62778""973: The Unicode table files cannot be found in the NLS directory or in the search path. Code page: number Country: number" in Appendix C.PAGENUM=869 ID="BP863"974: The Unicode table files are corrupted.PURGEAction: See message IDREF="FM63405""974: The Unicode table files are corrupt." in Appendix C.974: The Unicode table files can't be opened because there are already too many open files. Close some files or modify your CONFIG.SYS file.PURGEAction: See message IDREF="FM49793""975: The Unicode table files cannot be opened because there are already too many open files. Close some files or modify your CONFIG.SYS file." in Appendix C.PAGENUM=870 ID="BP864"RCONSOLE7: The driver was unable to initialize IPX.RCONSOLEExplanation: This is probably a hardware, connection, or configuration problem.Action: Make sure the network board is properly inserted in the workstation and attached to the network. If the error recurs, replace the board.16: The utility was unable to close file name.RCONSOLEExplanation: This is an internal error that occurred during the file transfer process.Action: Retry the operation. If the problem persists, contact your Novell Authorized Reseller.17: The utility was unable to open file name. The path may be invalid, or nonexistent. Press <F1> for examples of valid paths.RCONSOLEExplanation: The file could not be located, or the user does not have rights to open the file.Action: Make sure the file exists. Make sure the user has the appropriate rights to the file. If appropriate, grant the user's the appropriate rights to the file.18: The utility was unable to read file name.RCONSOLEExplanation: This is an internal error.Action: Retry the operation. If the problem persists, contact your Novell Authorized Reseller.19: The utility was unable to write to file name.RCONSOLEExplanation: The file could not be located, or the user does not have rights to open the file.Action: Make sure the file exists. Make sure the user has the appropriate rights to the file. If appropriate, grant the user's the appropriate rights to the file.20: An error occurred copying file name.RCONSOLEExplanation: This is an internal error.Action: Retry the operation. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=871 ID="BP865"25: The utility was unable to allocate memory.RCONSOLEExplanation: The workstation does not have enough memory to complete this operation.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network.41: The utility was unable to set the date and time for file name.RCONSOLEExplanation: This is an internal error.Action: Retry the operation. If the problem persists, contact your Novell Authorized Reseller.64: The utility was unable to write the modem configuration file to the current directory.RCONSOLEExplanation: The user probably does not have rights to open the file.Action: Make sure the user has the appropriate rights to the directory. If appropriate, grant the appropriate rights to the user.68: An invalid user ID was specified in the configuration option.RCONSOLEExplanation: You specified an invalid user ID in the Configuration option of the main menu.Action: Specify a valid user ID.72: The utility was unable to establish a connection with server.RCONSOLEExplanation: This problem could have a variety of causes.Action: Check the modem connection and its configuration to assure that the modem is transmitting properly.76: Wild card specifiers are not allowed in the target path.RCONSOLEExplanation: While using the Transfer Files menu, wildcard characters (such as * and ?) were used to specify the target path or file.Action: Remove the wildcard characters from the target path.78: The utility was unable to create the directory name.RCONSOLEExplanation: The volume is not mounted or is damaged.Action: Try to mount the volume. If the volume will not mount, run VREPAIR.PAGENUM=872 ID="BP866"79: The utility was unable to find the file name.RCONSOLEExplanation: The filename or the path was typed incorrectly.Action: Retype the file path with the correct name and path.82: The specified server was not found.RCONSOLEExplanation: The server is not broadcasting remote services.Action: Ask the network supervisor to load the REMOTE, RSPX, and RS232 NLMs on the remote server.84: The utility was unable to invoke the operating system (path = path error = code).RCONSOLEExplanation: This is an internal error. The program could not find COMMAND.COM, some other error occurred while bringing up DOS, or the workstation may be out of memory.Action: Retry the operation. Make sure COMMAND.COM is in the path. Increase the available memory. See "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.85: There is insufficient memory to invoke the operating system.RCONSOLEExplanation: The workstation does not have enough memory to complete this operation.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network. 90: The directory is empty or no matching file was found.RCONSOLEAction: Make sure the directory name and path was type correctly; then retry the operation.95: An invalid call back number was specified in the configuration option.RCONSOLEExplanation: No callback number was specified in the configuration menu.Action: Using the RCONSOLE configuration menu, specify the callback number.107: The utility could not determine the workstation address.RCONSOLEExplanation: The workstation queried the server for the workstation address, but received no reply.Action: This message may be ignored.PAGENUM=873 ID="BP867"108: The utility could not initialize SPX.RCONSOLEExplanation: This is an internal error.Action: Retry the operation. If the problem persists, contact your Novell Authorized Reseller.109: The utility could not open an IPX socket.RCONSOLEExplanation: This is an internal error. One possible cause may be an incorrect shell version.Action: Retry the operation. If the problem persists, contact your Novell Authorized Reseller.110: The utility could not locate a route to the designated server.RCONSOLEExplanation: This is a routing or hardware error. A router could be down, or the server may be malfunctioning.Action: Check the routers and make sure the server is functioning properly. Retry the operation. If the problem persists, contact your Novell Authorized Reseller.111: The SPXEstablishConnection table is full. The utility cannot establish a connection.RCONSOLEExplanation: This error usually means that all connections are in use.Action: Wait a few minutes; then retry the operation. If the problem persists, contact your Novell Authorized Reseller.112: SPXEstablishConnection failed to establish a connection to the desired server.RCONSOLEExplanation: This is an internal error that could have a number of causes. There may be a cabling problem.Action: Check the cabling; then retry the operation. If the problem persists, contact your Novell Authorized Reseller.113: The server connection was terminated by AllocateConnection.RCONSOLEExplanation: This is an internal error. A possible cause is unusually high network activity.Action: Check MONITOR's Connection Information for possible clues. Also check MONITOR's LAN Information for the density of packet activity on the network. If you cannot determine the cause of the problem, retry the operation. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=874 ID="BP868"114: No response has been received from the server.RCONSOLEExplanation: Either the server is down or it is not broadcasting RCONSOLE support.Action: Reload RCONSOLE to reestablish a connection with the server. Use NLIST to determine whether the server is down, or check the network status using LANalyzer.115: The utility attempted to send a packet with an invalid size.RCONSOLEExplanation: This is an internal error.Action: Retry the operation. If the problem persists, contact your Novell Authorized Reseller.116: The server connection was terminated by SendRequest.RCONSOLEExplanation: This is an internal error.Action: Retry the operation. If the problem persists, contact your Novell Authorized Reseller.117: The server connection was terminated by SendRequestAndGetReply.RCONSOLEExplanation: This is an internal error.Action: Retry the operation. If the problem persists, contact your Novell Authorized Reseller.118: The utility was unable to send a request to the server.RCONSOLEExplanation: The server is down, or it is not broadcasting RCONSOLE services.Action: Reload RCONSOLE to reestablish the connection. Make sure the server the has REMOTE, RS232, and/or RSPX NLM programs loaded.124: The utility received more packets than it has buffers to hold. Data was lost.RCONSOLEExplanation: This is an internal error.Action: Contact your Novell Authorized Reseller.125: No source file was specified.RCONSOLEExplanation: This error, encountered in the Transfer Files menu, indicates that a source path or file was not entered.Action: Press MOREINFO="NONE"<Enter>, then enter the full path to the source file.PAGENUM=875 ID="BP869"126: No target path was specified.RCONSOLEExplanation: This error, encountered in the Transfer Files menu, indicates that a target path or file was not entered.Action: Press MOREINFO="NONE"<Enter>, then enter the full path to the source file.127: The utility was unable to read the asynchronous I/O overlay.RCONSOLEExplanation: An error occurred when the program tried to read the file xxx$AIO.OVL. (xxx is the short machine name as defined for the workstation; for example, IBM or CPQ.)Action: Contact your Novell Authorized Reseller.128: The utility was unable to locate the asynchronous I/O overlay.RCONSOLEExplanation: The file xxx$AIO.OVL was not found. (xxx is the short machine name as defined for the workstation; for example, IBM, CPQ, etc.)Action: Make sure this file is in the search path.129: The asynchronous I/O overlay is the wrong version.RCONSOLEExplanation: The file xxx$AIO.OVL was the wrong version. (xxx is the short machine name as defined for the workstation; for example, IBM or CPQ.)Action: Make sure the latest version of this file is in the search path.130: The utility was unable to unpack the file name.RCONSOLEExplanation: This is an internal error.Action: Retry the operation. If the problem persists, contact your Novell Authorized Reseller.131: The utility was unable to read the header of file name.RCONSOLEExplanation: This is an internal error.Action: Retry the operation. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=876 ID="BP870"REDIR1: The message file name is invalid. The program cannot be loaded.REDIRExplanation: The .MSG file is invalid. This problem could be the result of a corrupted file, a bad translation, or an outdated file version.Action: Either update the .MSG file with a valid copy or delete the file. The DOS Requester will use the default messages that are bound to the binary files.5: Module1.VLM is not loaded. The module2.VLM file cannot be loaded before module1.VLM. Load the module1.VLM file first then try to load the module2.VLM file.REDIRExplanation: The module2.VLM requires that the module1.VLM be loaded. Either the current configuration has module1.VLM and module2.VLM loading out of order, or module1.VLM did not load successfully.Action: Make sure the module1.VLM is configured to load before module2.VLM. To do this, change the load order of the VLM= parameter in the NET.CFG file.7: In order to load the module3.VLM, one of the following VLMs must be loaded: module1.VLM, module2.VLM.REDIRExplanation: The module3.VLM requires that module1.VLM or module2.VLM be loaded. Either the current configuration has module3.VLM loading before the modules in the module1.VLM or module2.VLM list, or module1.VLM or module2.VLM did not load successfully.Action: Make sure the module1.VLM or module2.VLM loads successfully before loading module3.VLM.42: There is a missing or invalid value for `parameter' on line number of the configuration file. This entry will be ignored. Correct the line specified in the configuration file before continuing.REDIRExplanation: The configuration file contains a configuration keyword that has an invalid parameter or that does not specify a parameter. This invalid line will be ignored by the configuration process.Action: Because this line will be ignored, no action is required now. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message.PAGENUM=877 ID="BP871"43: There is a missing or invalid ON/OFF value for `parameter' on line number of the configuration file. This entry will be ignored. Correct the line specified in the configuration file before continuing.REDIRExplanation: The configuration file contains a configuration keyword that is defined to use either an "ON" or "OFF" parameter, but a different parameter, or no parameter, has been specified. This invalid line will be ignored by the configuration process.Action: Because this line will be ignored, no action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message.45: The parameter specified for the following option was out of range and has been adjusted.REDIRExplanation: A configurable parameter has been configured too high or too low to be valid. The invalid parameter is specified on the line following the message.Action: Correct the parameter specified in the NET.CFG file. For more information about the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.PAGENUM=878 ID="BP872"REMOTE1: The workstation response could not be located.REMOTEExplanation: A response was received from a remote workstation, but it did not apply to this connection. This is an internal error; possibly a corrupted NLM file.Action: Retry the operation. If the problem persists, contact your Novell Authorized Reseller.3: The NLM could not allocate a resource tag.REMOTEExplanation: The server does not have enough memory to load the REMOTE NLM.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.4: The NLM could not allocate a timer event resource tag.REMOTEExplanation: The server does not have enough memory to load the REMOTE NLM.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.7: The NLM could not allocate an AES Event resource tag.REMOTEExplanation: The server does not have enough memory to load the REMOTE NLM.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.9: The NLM could not allocate a console command resource tag.REMOTEExplanation: The server does not have enough memory to load the REMOTE NLM.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.11: The NLM could not allocate a process resource tag.REMOTEExplanation: The server does not have enough memory to load the REMOTE NLM.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.13: The NLM could not allocate an Event resource tag.REMOTEExplanation: The server does not have enough memory to load the REMOTE NLM.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network."PAGENUM=879 ID="BP873"14: The NLM could not register for event notification.REMOTEExplanation: The server does not have enough memory to load the REMOTE NLM.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.15: The NLM could not register for audit event notification.REMOTEExplanation: The server does not have enough memory to load the REMOTE NLM.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.16: The NLM could not allocate memory for a process stack.REMOTEExplanation: The server does not have enough memory to load the REMOTE NLM.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.17: The NLM could not register for event notification.REMOTEExplanation: The server does not have enough memory to load the REMOTE NLM.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.23: A response buffer could not be found for workstation response delivery.REMOTEExplanation: More responses were present from workstations than there were buffers to hold them. The workstation may be hung.Action: Reboot the workstation. If the problem persists, contact your Novell Authorized Reseller.27: The NLM was unable to create the file.REMOTEExplanation: REMOTE.NLM wa not able to create the LDREMOTE.NCF file.Action: Search the SYS:SYSTEM directory for the LDREMOTE.NCF file and delete it if it exists. Then retry the operation.92: The NLM could not allocate a resource tag for connections.REMOTEExplanation: The server does not have enough memory to load the REMOTE NLM.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.PAGENUM=880 ID="BP874"RENDIR100: You may not move a directory to another device like LPT1 or CON.RENDIRExplanation: The directory must be remain on the same volume or drive. RENDIR cannot move directories.Action: To move the directory, create a directory on the destination volume or drive; then copy the directory and subdirectories from the old directory to the new directory using NCOPY or FILER.200: The new directory name is invalid.RENDIRExplanation: The specified directory name contains invalid characters.Action: Type the new directory name using only acceptable characters (A through Z, 0 through 9, or the underscore).300: You must be attached to server name before renaming a directory.RENDIRExplanation: The user is not attached to the server identified in the path.Action: Attach to the desired server with the LOGIN utility; then rename the directory.400: The specified directory already exists.RENDIRExplanation: The directory cannot be renamed to a directory name that is already being used.Action: Specify a directory name that is not already in use.450: The source directory name was not found.RENDIRExplanation: The directory specified to be renamed does not exist.Action: Type the directory name correctly. Change directories so that the directory to be renamed is a subdirectory of the current directory. For information, see "BOOK="utlrfenu" COLLECTION="nw41"RENDIR" in Utilities Reference.475: This utility was unable to get the proper directory handle.RENDIRExplanation: An error prevented the directory from being renamed. No other information is available.Action: Make sure the old directory exists and that the new directory does not exist; then retype the command with the correct directory paths.PAGENUM=881 ID="BP875"500: This directory is in use by another account. An active directory cannot be renamed.RENDIRExplanation: Another workstation is currently mapped to the directory. A directory cannot be renamed while another workstation is using the directory.Action: Retry the command later.550: You do not have the appropriate rights to rename this directory.RENDIRExplanation: The user does not have the necessary rights to rename the directory.Action: Make sure the user has appropriate user access rights.575: The root directory cannot be renamed with the RENDIR command.RENDIRExplanation: The root directory name cannot be changed.Action: To rename the volume, create a new volume on the server. Make sure the server has sufficient memory to create a new volume. If it does, create the new volume, and copy the information from the old volume to the new volume. Then delete the old volume. For instructions to create new volumes on the server, see "BOOK="superenu" COLLECTION="nw41"Maintaining the NetWare Server" in Supervising the Network.625: An unknown error has occurred, code = codeRENDIRExplanation: The last two digits of the error code will help determine the cause of the error.Action: For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A.700: No mapping exists for the current drive.RENDIRExplanation: The drive specified in the command line is not currently mapped.Action: Either map the drive letter to the appropriate area, or change to a drive letter already pointing to the desired area; then retry the operation.750: Two parameters must be specified.RENDIRExplanation: Only one path was specified in the command line. Both the old directory name and the new directory name are required.Action: To rename a directory, type the old directory name; then type the new directory name.903: The command line syntax is invalid.RENDIRAction: See message IDREF="FM18860""903: The command line syntax is invalid." in Appendix C.PAGENUM=882 ID="BP876"905: This utility was unable to initialize the country information.RENDIRAction: See message IDREF="FM55337""905: This utility was unable to initialize the country information." in Appendix C.908: The specified path is invalid.RENDIRAction: See message IDREF="FM51165""908: The specified path is invalid." in Appendix C.910: This utility was unable to parse the specified path.RENDIRAction: See message IDREF="FM47164""910: This utility was unable to parse the specified path." in Appendix C.913: The specified directory cannot be found.RENDIRAction: See message IDREF="FM19478""913: The specified directory cannot be found." in Appendix C.917: This utility was unable to set the context.RENDIRAction: See message IDREF="FM32126""917: This utility was unable to set the context." in Appendix C.970: The attempt to open the Unicode table files failed.RENDIRAction: See message IDREF="FM15675""970: The attempt to open the Unicode table files failed." in Appendix C.971: The workstation does not have enough memory to load the Unicode table files.RENDIRAction: See message IDREF="FM55341""971: The workstation does not have enough memory to load the Unicode table files." in Appendix C.972: Access to the Unicode table files was denied.RENDIRAction: See message IDREF="FM90152""972: Access to the Unicode table files was denied." in Appendix C.Action: 973: The Unicode table files (*.001) cannot be found in the NLS directory or in the search drives.RENDIRAction: See message IDREF="FM62778""973: The Unicode table files cannot be found in the NLS directory or in the search path. Code page: number Country: number" in Appendix C.974: The Unicode table files are corrupt.RENDIRAction: See message IDREF="FM63405""974: The Unicode table files are corrupt." in Appendix C.PAGENUM=883 ID="BP877"975: The Unicode table files cannot be opened because there are already too many open files. Close some files or modify your CONFIG.SYS file.RENDIRAction: See message IDREF="FM49793""975: The Unicode table files cannot be opened because there are already too many open files. Close some files or modify your CONFIG.SYS file." in Appendix C.998: The message file found (<utility_name>.MSG) is an incorrect version. The correct version is <number>. See your network supervisor for assistance.RENDIRAction: See message IDREF="FM91957""998: The message file found (utility_name.MSG) is an incorrect version. The correct version is number. See your network supervisor for assistance." in Appendix C.999: The message file for this utility cannot be found.RENDIRAction: See message IDREF="FM69424""999: The message file for this utility cannot be found." in Appendix C.PAGENUM=884 ID="BP878"REQxxxxThis section includes error messages for all NetWare Requester for OS/2 2.01 drivers and daemons.REQ0106: An error occurred during attempt to get shared memory.REQxxxxExplanation: DDAEMON.EXE tried to access the daemon's shared memory, but failed. At this point, the program has verified that the shared memory exists, but is unable to access it. This may be an internal program error.Action: Try rebooting the computer. If the problem persists, contact your Novell Authorized Reseller.REQ0107: An error occurred during attempt to allocate a shared segment.REQxxxxExplanation: DDAEMON.EXE tried to create shared memory, but none is available. This error usually occurs when the device drivers and applications currently running on the system require more memory than the system has available.Action: Try adding RAM, reducing the configuration options in the CONFIG.SYS file (for example, reducing the size of DIRCACHE), removing optional device drivers from the CONFIG.SYS file, and freeing up some hard disk space by deleting unnecessary programs. If the workstation's hard disk is using multiple disk partitions, consider moving the OS/2 swapper file to a larger partition. Disk compression utilities may also be available that can help resolve this problem. After completing these actions, shut down OS/2; then reboot the system. If the problem persists, contact your Novell Authorized Reseller.REQ0108: The daemon cannot access the Link Support Layer. Error: code.REQxxxxExplanation: DDAEMON.EXE cannot find the Link Support device driver LSL.SYS.Action: Make sure the device driver LSL.SYS has been properly entered in the CONFIG.SYS file. If so, check the messages displayed by the LSL for any errors or warnings, and correct the problems indicated. Action: For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. Then retry the operation. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=885 ID="BP879"REQ0109: The DDAEMON is already loaded.REQxxxxExplanation: DDAEMON.EXE tried to create shared memory for the first time, but the memory already exists. Another daemon is already running. The attempt to create shared memory is terminated.Action: Make sure the workstation is not trying to run multiple copies of the daemon. Typically the daemon is run from the CONFIG.SYS file at system startup and does not need to be re-executed.REQ0204: The system does not have enough memory for socket tables.REQxxxxExplanation: OS/2 lacks sufficient system memory for IPX to allocate memory for its socket tables.Action: Try adding RAM, reducing the configuration options in the CONFIG.SYS file (for example, reducing the size of DIRCACHE), removing optional device drivers from the CONFIG.SYS file, and freeing up some hard disk space by deleting unnecessary programs. If the workstation's hard disk is using multiple disk partitions, consider moving the OS/2 swapper file to a larger partition. Disk compression utilities may also be available that can help resolve this problem. After completing these actions, shut down OS/2; then reboot the system. If the problem persists, contact your Novell Authorized Reseller.REQ0205: The LAN support module could not be installed.REQxxxxExplanation: Either the LSL.SYS driver failed to load, or the "DEVICE=" statement is missing from the CONFIG.SYS file.Action: Either correct the problem that kept the LSL.SYS driver from loading (indicated in an error message preceding this one), or add the "DEVICE=" statement to the CONFIG.SYS file.REQ0206: The IPX MLID could not be installed.REQxxxxExplanation: Either the Multiple Link Interface Driver (MLID) specified in the CONFIG.SYS failed to load, or the "DEVICE=" statement for an MLID is missing from the CONFIG.SYS file.Action: Either correct the problem that kept the MLID from loading (indicated in an error message preceding this one), or add the "DEVICE=" statement to the CONFIG.SYS file.REQ0207: The configured LAN-A driver does not support IPX.REQxxxxExplanation: The Multiple Link Interface Driver (MLID) to which IPX.SYS tried to bind does not support IPX-based data transmissions.Action: Bind IPX to an MLID that supports IPX-based data transmissions.PAGENUM=886 ID="BP880"REQ0208: The IPX protocol handler cannot be registered.REQxxxxExplanation: IPX cannot register with the LSL.SYS driver because the LSL is servicing its maximum number of protocol stacks.Action: Remove the "DEVICE=" statements for any unnecessary protocol stacks from the CONFIG.SYS file.REQ0209: The IPX entry point cannot be initialized.REQxxxxExplanation: The IPX and Link Support Layer (LSL) versions may not be compatible versions.Action: Make sure the IPX.SYS driver and LSL.SYS driver are compatible. If they are not, obtain compatible drivers from your Novell Authorized Reseller.REQ0210: An internal error occurred. The IPX router socket cannot be opened.REQxxxxExplanation: IPX was unable to open the router socket due to an internal program error.Action: Retry the operation. If the problem persists, contact your Novell Authorized Reseller.REQ0211: An internal error occurred. A router selector cannot be allocated.REQxxxxExplanation: IPX was unable to allocate an OS/2 router selector due to an internal program error.Action: Retry the operation. If the problem persists, contact your Novell Authorized Reseller.REQ0212: The system has insufficient memory to allocate a router.REQxxxxExplanation: OS/2 cannot access sufficient system memory for IPX routing purposes.Action: Try adding RAM, reducing the configuration options in the CONFIG.SYS file (for example, reducing the size of DIRCACHE), removing optional device drivers from the CONFIG.SYS file, and freeing up some hard disk space by deleting unnecessary programs. If the workstation's hard disk is using multiple disk partitions, consider moving the OS/2 swapper file to a larger partition. Disk compression utilities may also be available that can help resolve this problem. After completing these actions, shut down OS/2; then reboot the system. If the problem persists, contact your Novell Authorized Reseller.REQ0213: Router memory is exhausted.REQxxxxExplanation: IPX did not have enough memory previously allocated for routing purposes.Action: Increase the size of the IPX router memory in the NET.CFG "ROUTER MEM" statement.PAGENUM=887 ID="BP881"REQ0214: An internal error prevented CGroup variable initialization.REQxxxxExplanation: An internal program error has occurred. IPX was unable to initialize internal variables.Action: Retry the operation. If the problem persists, contact your Novell Authorized Reseller.REQ0215: An internal error prevented DosHlp variable initialization.REQxxxxExplanation: OS/2 internal variables were either incomplete or invalid.Action: Retry the operation. If the problem persists, contact your Novell Authorized Reseller.REQ0216: IPX cannot register with OS/2 for PDD-to-VDD communications.REQxxxxExplanation: This is an internal program error. IPX cannot register with OS/2 for VIPX.SYS driver support.Action: Retry the operation. If the problem persists, contact your Novell Authorized Reseller.REQ0217: The IPX device driver is not running.REQxxxxExplanation: Either IPX.SYS encountered a fatal error during system initialization, or the "DEVICE=[path]IPX.SYS" statement was missing from the CONFIG.SYS file. If the problem is a fatal error, another message should precede this one that identifies the specific error that occurred.Action: Either resolve the fatal problem (indicated in a preceding message), or add the "DEVICE=" statement to the CONFIG.SYS file; then retry the operation. If the problem persists, contact your Novell Authorized Reseller.REQ0231: The default protocol configuration option is not used for IPX.REQxxxxExplanation: IPX cannot be configured as a default protocol stack.Action: Remove this option statement from the NET.CFG file.REQ0232: The prescan protocol configuration option is not used for IPX.REQxxxxExplanation: IPX cannot be configured as a prescan protocol stack.Action: Remove this option statement from the NET.CFG file.PAGENUM=888 ID="BP882"REQ0233: The OS/2 version number cannot be found; OS/2 2.0 is assumed.REQxxxxExplanation: IPX's query of OS/2 for the version number returned a value that did not match the value it expected to receive.Action: Make sure the OS/2 version installed on the workstation is 2.0 or later.REQ0304: An LSL error occurred. NET.CFG buffers are too big for ECB pool.REQxxxxExplanation: The configured buffer size for the Link Support component is too large. Total available buffer space is approximately 60 KB, but the Link Support Layer (LSL) is unable to allocate even one buffer of the requested size in its buffer space. For information about LSL, see "BOOK="cncptenu" COLLECTION="nw41"Link Support Layer (LSL)" in Concepts.Action: Reduce the Link Support component's buffer size in the NET.CFG file. It is more important to have several smaller buffers available than one large one. It is a waste of system memory to configure buffers much larger than the communications media can support.REQ0305: The Link Support module (LSL) could not install the AES timer.REQxxxxExplanation: The Link Support Layer (LSL) could not register its timer handler with the operating system because the maximum number of handlers have already been installed. This timer handler is a critical component of the Requester, and none of the Novell-supplied communication handlers can be expected to work properly without it. For information about LSL, see "BOOK="cncptenu" COLLECTION="nw41"Link Support Layer (LSL)" in Concepts.Action: Previously installed device drivers (those entered before LSL.SYS in the CONFIG.SYS file) have used all available timer resources. Identify those device drivers and either remove or reconfigure them. Since the Requester's communications handlers all use a common timer service in the LSL, only one available timer handler is required for proper operation. If the problem persists, contact your Novell Authorized Reseller.REQ0306: The Link Support module could not initialize its call gate.REQxxxxExplanation: The Link Support module could not register its entry point with the operating system. This entry point is vital to most of the Requester's communications components, and its absence will cause them to fail. The most likely cause of this error is a previously loaded device driver that is using too many kernel resources.Action: Try removing application device drivers installed before LSL.SYS in the CONFIG.SYS file. It is highly unlikely that a device driver from the OS/2 base system has caused this error. If the problem persists, contact your Novell Authorized Reseller.REQ0404: NetBIOS error occurred. Link Support module cannot be installed.REQxxxxPAGENUM=889 ID="BP883"Explanation: NetBIOS could not open or communicate with the Link Support LINKSUP_ device driver. This can happen if the Link Support Layer (LSL) driver has not been properly installed or if the workstation is using the wrong version of the driver. For information about LSL, see "BOOK="cncptenu" COLLECTION="nw41"Link Support Layer (LSL)" in Concepts.Action: Make sure the device driver LSL.SYS has been properly entered in the CONFIG.SYS file. If so, check the messages displayed by the LSL for any errors or warnings, and correct the problems indicated. If the Link Support device driver is initializing properly, the problem is with incompatible versions of the software. NetBIOS and Link Support are usually installed together from a single installation diskette. Try reinstalling them. If the problem persists, contact your Novell Authorized Reseller.REQ0405: NetBIOS error occurred. The IPX module is not installed.REQxxxxExplanation: NetBIOS could not open or communicate with the Link Support LINKSUP_ device driver. This can happen if the Link Support Layer (LSL) driver has not been properly installed or if the workstation is using the wrong version of the driver.Action: Make sure the device driver LSL.SYS has been properly entered in the CONFIG.SYS file. Check the messages displayed by the LSL for any errors or warnings, and correct the problems indicated.If the Link Support device driver is initializing properly, the problem is incompatible versions of the software. NetBIOS and Link Support are usually installed together from a single installation diskette. Try reinstalling them. If the problem persists, contact your Novell Authorized Reseller. For information about LSL, see "BOOK="cncptenu" COLLECTION="nw41"Link Support Layer (LSL)" in Concepts.REQ0406: The NetBIOS call gate cannot be initialized.REQxxxxExplanation: This is an internal program error.Action: Retry the operation. If the problem persists, contact your Novell Authorized Reseller.REQ0407: NetBIOS error occurred. The program cannot initialize local NCBs.REQxxxxExplanation: The workstation does not have enough memory available for the NCBs requested. Usually this error is caused by incorrect configuration information in the NET.CFG file. However, the underlying problem could also be a lack of global system resources (memory or hard disk space) in the OS/2 Global Descriptor Table.Action: Reduce the number of commands in the NetBIOS section of the CONFIG.SYS file. (The default number of commands is 12; the maximum allowed is 25.) For information about the CONFIG.SYS file, see 
BOOK="ws_osenu" COLLECTION="nw41"NetWare Client for OS/2 User Guide.Reduce the number of node names (possible range is 0 to 126). Add RAM, reducing the configuration options (for example, reducing the size of DIRCACHE) or removing optional device drivers from the CONFIG.SYS file, and freeing up some hard disk space by deleting unnecessary programs. PAGENUM=890 ID="BP884"If the workstations hard drive has multiple disk partitions, consider moving the OS/2 swapper file to a partition with more space. Disk compression utilities may also be available that can help resolve this problem. After completing these actions, shut down OS/2 and then reboot the system. If the problem persists, contact your Novell Authorized Reseller.REQ0408: NetBIOS emulator parameters are too large for the memory pool.REQxxxxExplanation: The workstation does not have enough memory available for all of the control tables needed by the NetBIOS emulator.Action: The amount of table space available to the NetBIOS emulator cannot be increased. The only way to solve this problem is to reduce the number of NetBIOS resources the workstation is requesting. Do this by modifying the NETBIOS parameters in the NET.CFG file. If the problem persists, contact your Novell Authorized Reseller.REQ0409: Incompatible versions of OS/2 and NetBIOS are running.REQxxxxExplanation: The workstation is trying to run NetBIOS 2.01 on a version of OS/2 earlier than OS/2 2.0.Action: Either install OS/2 2.0 to run with NetBIOS 2.01, or install a different version of NetWare NetBIOS to match the OS/2 version.REQ0504: The SPX module is not installed.REQxxxxExplanation: The NMPIPE.SYS driver could not open or communicate with the SPX.SYS driver.Action: Make sure the SPX.SYS driver has been properly entered in the CONFIG.SYS file. If so, check the messages displayed by the driver for any errors or warnings, and correct the problems indicated; then retry the operation. If the problem persists, contact your Novell Authorized Reseller.REQ0505: The IPX module is not installed.REQxxxxExplanation: NMPIPE.SYS could not open or communicate with the IPX.SYS driver.Action: Make sure the IPX.SYS driver has been properly entered in the CONFIG.SYS file. If so, check the messages displayed by the driver for any errors or warnings, and correct the problems indicated; then retry the operation. If the problem persists, contact your Novell Authorized Reseller.REQ0519: An incorrect OS/2 version is being used.REQxxxxExplanation: Either the DosGetVersion call failed (an internal program error), or the OS/2 version currently running is not 2.0 or later.Action: Make sure the client OS and NMPIPE.SYS driver are compatible versions. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=891 ID="BP885"REQ0520: The driver cannot register the PDD for VDD-to-PDD communications.REQxxxxExplanation: NMPIPE.SYS could not register IPX as a PDD so that PDD to VDD communication may take place.Action: Make sure the IPX.SYS driver has been properly entered in the CONFIG.SYS file. If so, check the messages displayed by the driver for any errors or warnings, and correct the problems indicated. Make sure the OS/2 version is 2.0 or later; then retry the operation. If the problem persists, contact your Novell Authorized Reseller.REQ0613: Invalid characters were specified in COMPUTERNAME.REQxxxxExplanation: The named pipes server name specified after NPDAEMON.EXE is invalid.Action: Make sure the server name is not more than 15 characters. It can be composed of letters, numbers, and these special characters: !#$%&()-.@^_\Q{}~REQ0614: An error occurred during attempt to initialize NPCALLS.DLL.REQxxxxExplanation: The NPDaemon could not initialize NPCALLS.DLL.Action: Make sure the NPCALLS.DLL file in the NetWare Requester directory is included in the LIBPATH statement of the CONFIG.SYS file. If the workstation is running named pipes, make sure the NMPIPE.SYS driver and NPSERVER.SYS are correctly configured in the CONFIG.SYS file.REQ0615: The Named Pipes daemon could not be registered. Error: code.REQxxxxExplanation: The NPDaemon could not open or communicate with the NMPIPE.SYS driver.Action: Make sure the NMPIPE.SYS driver has been properly entered in the CONFIG.SYS file. If so, check the messages displayed by the driver for any errors or warnings, and correct the problems. Retry the operation. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.REQ0616: An error occurred during attempt to allocate shared memory.REQxxxxExplanation: The NPDaemon could not allocate shared memory.Action: Try adding RAM, reducing the configuration options in the CONFIG.SYS file (for example, reducing the size of DIRCACHE), removing optional device drivers from the CONFIG.SYS file, and freeing up some hard disk space by deleting unnecessary programs. If the workstation is using multiple disk partitions, consider moving the OS/2 swapper file to a larger partition. Disk compression utilities may also be available that can help resolve this problem. After completing these actions, shut down OS/2; then reboot the system. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=892 ID="BP886"REQ0617: An error occurred during attempt to allocate the ECB pool.REQxxxxExplanation: The NPDaemon could not allocate memory for the ECB pool.Action: Try adding RAM, reducing the configuration options in the CONFIG.SYS file (for example, reducing the size of DIRCACHE), removing optional device drivers from the CONFIG.SYS file, and freeing up some hard disk space by deleting unnecessary programs. If the workstation is using multiple disk partitions, consider moving the OS/2 swapper file to a larger partition. Disk compression utilities may also be available that can help resolve this problem. After completing these actions, shut down OS/2; then reboot the system. If the problem persists, contact your Novell Authorized Reseller.REQ0618: An error occurred during attempt to create a system semaphore.REQxxxxExplanation: A DosCreateSem call failed. An internal program error may have occurred.Action: Retry the operation. If the problem persists, contact your Novell Authorized Reseller.REQ0619: An error occurred during attempt to create a thread.REQxxxxExplanation: A beginthread call failed. An internal program error may have occurred.Action: Retry the operation. If the problem persists, contact your Novell Authorized Reseller.REQ0620: A dynamic socket could not be opened. Error: code.REQxxxxExplanation: The NPDaemon failed to open a dynamic socket.Action: Increase the socket count specified in the NET.CFG file; then reboot the system and retry the operation. If the problem persists, contact your Novell Authorized Reseller. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A.REQ0621: A well-known socket could not be opened. Error: code.REQxxxxExplanation: The NPDaemon could not open NetWare's registered Named Pipe socket; the socket may already be in use.Action: Increase the socket count in the NET.CFG and shut down OS/2; then reboot the system. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A.REQ0622: The NPDaemon cannot get the Internet address. Error: code.REQxxxxExplanation: An IpxGetInternetworkAddress call failed.PAGENUM=893 ID="BP887"Action: Make sure the IPX.SYS driver has been properly entered in the CONFIG.SYS file. If so, check the messages displayed by the driver for any errors or warnings, and correct the problems indicated. Make sure the IPXCALLS.DLL file is in the NetWare Requester directory; then retry the operation. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.REQ0623: The NPDaemon cannot get the local target. Error: code.REQxxxxExplanation: An IpxGetLocalTarget call failed.Action: Make sure the IPX.SYS driver has been properly entered in the CONFIG.SYS file. If so, check the messages displayed by the driver for any errors or warnings, and correct the problems indicated. Make sure the IPXCALLS.DLL file is in the NetWare Requester directory; then retry the operation. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.REQ0624: The service advertising function failed. Error: code.REQxxxxExplanation: An IpxSend call to advertise this workstation as a Named Pipe Server failed.Action: Make sure the IPX.SYS driver has been properly entered in the CONFIG.SYS file. If so, check the messages displayed by the driver for any errors or warnings, and correct the problems indicated. Make sure the IPXCALLS.DLL file is in the NetWare Requester directory; then retry the operation. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.REQ0625: The broadcast socket cannot be opened. Error: code.REQxxxxExplanation: The broadcast socket cannot be opened. This is a registered socket by which SAPs can be received. Possibly this socket has already been opened.Action: Increase the socket count in the NET.CFG file and shut down OS/2; then reboot the system. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.REQ0626: An error occurred during attempt to get code page information.REQxxxxExplanation: A call to DosGetCtryInfo failed. This may be an internal program error.Action: Make sure the OS/2 is version 2.0 or later. If the problem persists, contact your Novell Authorized Reseller.REQ0628: Memory cannot be allocated for turbo buffers.REQxxxxExplanation: The NPDaemon could not allocate memory for turbo buffers.PAGENUM=894 ID="BP888"Action: Try adding RAM, reducing the configuration options in the CONFIG.SYS file (for example, reducing the size of DIRCACHE), removing optional device drivers from the CONFIG.SYS file, and freeing up some hard disk space by deleting unnecessary programs. If the workstation' hard disk is using multiple disk partitions, consider moving the OS/2 swapper file to a larger partition. Disk compression utilities may also be available that can help resolve this problem. After completing these actions, shut down OS/2; then reboot the system. If the problem persists, contact your Novell Authorized Reseller.REQ0629: A connection thread died abnormally. Error: code.REQxxxxExplanation: The connection controller thread died unexpectedly.Action: Make sure the SPX.SYS driver has been properly entered in the CONFIG.SYS file. If so, check the messages displayed by the driver for any errors or warnings, and correct the problems indicated. Also make sure all of the named pipe drivers are within the same major version (for example, 2.x); then retry the operation. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.REQ0630: The specified computer name is already registered on the Internet.REQxxxxExplanation: The named pipe server name specified in the CONFIG.SYS file has already been used on the internetwork.Action: Use a different server name.REQ0631: The receive buffer manager died abnormally. Error: code.REQxxxxExplanation: The receive buffer manager thread died unexpectedly.Action: Make sure the named pipe drivers are within the same major version (for example, 2.x). If so, try adding RAM, reducing the configuration options in the CONFIG.SYS file (for example, reducing the size of DIRCACHE), removing optional device drivers from the CONFIG.SYS file, and freeing up some hard disk space by deleting unnecessary programs. If the workstation's hard disk is using multiple disk partitions, consider moving the OS/2 swapper file to a larger partition. Disk compression utilities may also be available that can help resolve this problem. After completing these actions, shut down OS/2; then reboot the system. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.REQ0632: An error occurred checking for nondedicated server.REQxxxxExplanation: The NPDaemon could not open or communicate with the NWREQ.SYS driver.Action: Make sure the NWREQ.SYS driver has been properly entered in the CONFIG.SYS file. If so, check the messages displayed by the driver for any errors or warnings, and correct the problems indicated. Make sure the NWREQ.SYS is version 2.0 or greater. Then retry the operation. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=895 ID="BP889"REQ0633: An error occurred allocating memory for nondedicated SAP buffer.REQxxxxExplanation: NPDaemon could not allocate memory.Action: Try adding RAM, reducing the configuration options in the CONFIG.SYS file (for example, reducing the size of DIRCACHE), removing optional device drivers from the CONFIG.SYS file, and freeing up some hard disk space by deleting unnecessary programs. If the workstation's hard disk is using multiple disk partitions, consider moving the OS/2 swapper file to a larger partition. Disk compression utilities may also be available that can help resolve this problem. After completing these actions, shut down OS/2; then reboot the system. If the problem persists, contact your Novell Authorized Reseller.REQ0634: The NPDaemon could not obtain a server list.REQxxxxExplanation: The named pipes daemon failed to obtain a list of servers from the NetWare for OS/2 server running on the same workstation.Action: Make sure the workstation is running the latest version of the NetWare for OS/2 server. If the problem persists, contact your Novell Authorized Reseller.REQ0704: The SPX module is not installed.REQxxxxExplanation: The named pipes daemon could not open or communicate with the SPX.SYS driver.Action: Make sure the SPX.SYS driver has been properly entered in the CONFIG.SYS file. If so, check the messages displayed by the driver for any errors or warnings, and correct the problems indicated; then retry the operation. If the problem persists, contact your Novell Authorized Reseller.REQ0705: The IPX module is not installed.REQxxxxExplanation: The named pipes daemon could not open or communicate with the IPX.SYS driver.Action: Make sure the IPX.SYS driver has been properly entered in the CONFIG.SYS file. If so, check the messages displayed by the driver for any errors or warnings, and correct the problems indicated; then retry the operation. If the problem persists, contact your Novell Authorized Reseller.REQ0719: An incorrect OS/2 version is being used.REQxxxxExplanation: The DosGetVersion call failed (which would indicate an internal program error) or the OS/2 version currently running is not 2.0 or later.Action: Make sure the client OS and NMPIPE.SYS driver are compatible; then retry the operation. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=896 ID="BP890"REQ0806: The program cannot get code page information. Error: code.REQxxxxExplanation: The OS/2 system is not returning code page information. This may be an internal program error.Action: Retry the operation. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.REQ0807: The Requester device driver and daemon are incompatible versions.REQxxxxExplanation: The most likely cause of this problem is that NWDAEMON.EXE and NWREQ.SYS driver were not installed from the same installation disk.Action: Reinstall the Requester driver using the correct installation disk.REQ0808: The worker DLL cannot be registered. Error: code.REQxxxxExplanation: The NWWORKER.DLL could not register with the requester. This may be an internal program error.Action: Retry the operation. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.REQ0809: The broadcast handler cannot be registered. Error: code.REQxxxxExplanation: This may be an internal program error.Action: Retry the operation. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.REQ0810: The program cannot get system information. Error: code.REQxxxxExplanation: The OS/2 system is not returning system information. This may be an internal program error.Action: Retry the operation. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.REQ0811: The janitor thread priority cannot be set. Error: code.REQxxxxExplanation: The janitor thread is set to run at regular priority. The system could not set the priority.Action: For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A.PAGENUM=897 ID="BP891"REQ0812: The janitor daemon cannot be registered. Error: code.REQxxxxExplanation: This may be an internal program error.Action: Retry the operation. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.REQ0813: The program cannot get the current drive map. Error: code.REQxxxxExplanation: The OS/2 system is not returning the current drive map. This may be an internal program error.Action: Retry the operation. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.REQ0814: The program cannot set the current drive map. Error: code.REQxxxxExplanation: The OS/2 system is not setting the current drive map. This may be an internal program error.Action: Retry the operation. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.REQ0815: The program cannot get the connection ID. Error: code.REQxxxxExplanation: The Requester tried to locate a NetWare server when it initialized. Either no servers are currently running or a cabling problem exists.Action: Make sure the NetWare server is running and functioning properly. make sure the OS/2 workstation has a working connection to the network; then retry the operation. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.REQ0816: An error occurred during attempt to initialize the cache.REQxxxxExplanation: The caching function is not working. This may be an internal program error.Action: Retry the operation. If the problem persists, contact your Novell Authorized Reseller.REQ0817: The daemon could not boost the thread priority.REQxxxxExplanation: The thread is set to run at a greater priority. The system could not set the priority.Action: None. This message is for information only.PAGENUM=898 ID="BP892"REQ0818: The daemon could not register the DosBox handler.REQxxxxExplanation: This may be an internal program error.Action: Retry the operation. If the problem persists, contact your Novell Authorized Reseller.REQ0820: Not enough memory for diagnostic daemon. Error: code.REQxxxxExplanation: The NWDaemon program tried to allocate memory from the system for the diagnostic thread to use as a stack, but the system returned an error.Action: Try adding RAM, reducing the configuration options in the CONFIG.SYS file (for example, reducing the size of DIRCACHE), removing optional device drivers from the CONFIG.SYS file, and freeing up some hard disk space by deleting unnecessary programs. If the workstation's hard disk is using multiple disk partitions, consider moving the OS/2 swapper file to a larger partition. Disk compression utilities may also be available that can help resolve this problem. After completing these actions, shut down OS/2; then reboot the system. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.REQ0821: The diagnostic daemon cannot be started. Error: code.REQxxxxExplanation: The NWDaemon tried to start the diagnostic thread, but the system encountered an error condition. The system may have too many threads already running, or this may be an internal program error.Action: Try closing other applications that are currently running. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.REQ0822: The diagnostic daemon priority cannot be changed. Error: code.REQxxxxExplanation: The diagnostic thread is set to run at regular priority. The system could not set the priority.Action: None. This message is for information only. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A.REQ0823: Not enough memory to start a new thread. Error: code.REQxxxxExplanation: The NWDaemon could not allocate memory from the system to create a thread for a new task.PAGENUM=899 ID="BP893"Action: Try adding RAM, reducing the configuration options in the CONFIG.SYS file (for example, reducing the size of DIRCACHE), removing optional device drivers from the CONFIG.SYS file, and freeing up some hard disk space by deleting unnecessary programs. If the workstation's hard disk is using multiple disk partitions, consider moving the OS/2 swapper file to a larger partition. Disk compression utilities may also be available that can help resolve this problem. After completing these actions, shut down OS/2; then reboot the system. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.REQ0824: The SPX send thread cannot be started. Error: code.REQxxxxExplanation: This may be an internal program error.Action: Retry the operation. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.REQ0825: The SPX receive thread cannot be started. Error: code.REQxxxxExplanation: This may be an internal program error.Action: Retry the operation. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.REQ0826: The SFT III handler cannot be registered.REQxxxxExplanation: This may be an internal program error.Action: Retry the operation. If the problem persists, contact your Novell Authorized Reseller.REQ0827: Packet Burst cannot be initialized.REQxxxxExplanation: This may be an internal program error.Action: Retry the operation. If the problem persists, contact your Novell Authorized Reseller.ID="FM43668"REQ0843: Not enough memory for a network management thread (error code).REQxxxxExplanation: The NWDaemon tried to allocate memory from the system for a thread to initialize network management, but memory was not available. Network management cannot be initialized.Action: Try adding RAM, reducing the configuration options in the CONFIG.SYS file (for example, reducing the size of DIRCACHE), removing optional device drivers from the CONFIG.SYS file, and freeing up some hard disk space by deleting unnecessary programs. If the workstation's hard disk is using multiple disk partitions, consider moving the OS/2 swapper file to a larger partition. Disk compression utilities may also be available that can help resolve this problem.PAGENUM=900 ID="BP894"After completing these actions, shut down OS/2; then reboot the system. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.REQ0844: A named pipe cannot be started for network management (error code).REQxxxxExplanation: The NWDaemon could not allocate a named pipe. Network management will not be supported until the workstation is rebooted. This error could result from a variety of causes. Named Pipes or SPX may not be loaded, one of the drivers may have opened too many named pipes already, the workstation may not have enough memory or disk space, or it may be an internal program error.Action: Make sure the named pipes and SPX are loaded and that the system has enough memory. If memory problems are suspected, see message IDREF="FM43668" "REQ0843: Not enough memory for a network management thread (error code)."  After completing these actions, reboot the system and retry the operation. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.REQ0845: Not enough memory to run network management (error code).REQxxxxExplanation: The NWDaemon program tried to allocate memory from the system to run network management, but memory is not available. Network Management will not run until memory is available and the system is rebooted.Action: Try adding RAM, reducing the configuration options in the CONFIG.SYS file (for example, reducing the size of DIRCACHE), removing optional device drivers from the CONFIG.SYS file, and freeing up some hard disk space by deleting unnecessary programs. If the workstation's hard disk is using multiple disk partitions, consider moving the OS/2 swapper file to a larger partition. Disk compression utilities may also be available that can help resolve this problem.After completing these actions, shut down OS/2; then reboot the system. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.REQ0904: The NWREQ.SYS driver is not loaded.REQxxxxExplanation: The Requester cannot be initialized until the driver is loaded.Action: Load the NWREQ.SYS driver.PAGENUM=901 ID="BP895"REQ0914: The program cannot allocate selectors for the workspace table.REQxxxxExplanation: All available memory selectors are being used by the system or by previously loaded device drivers.Action: Remove optional or unneeded device drivers from the CONFIG.SYS file and retry the operation. If the problem persists, contact your Novell Authorized Reseller.REQ0915: The program cannot allocate memory for the workspace table.REQxxxxExplanation: All available system memory is in use. The Requester cannot load properly.Action: Try adding RAM, reducing the configuration options in the CONFIG.SYS file (for example, reducing the size of DIRCACHE), removing optional device drivers from the CONFIG.SYS file, and freeing up some hard disk space by deleting unnecessary programs. If the workstation's hard disk is using multiple disk partitions, consider moving the OS/2 swapper file to a larger partition. Disk compression utilities may also be available that can help resolve this problem. After completing these actions, shut down OS/2; then reboot the system. If the problem persists, contact your Novell Authorized Reseller.REQ0917: Memory is not available for the cache table. Caching is disabled.REQxxxxExplanation: All available system memory is in use by the system. The Requester cannot load properly.Action: Try adding RAM, reducing the configuration options in the CONFIG.SYS file (for example, reducing the size of DIRCACHE), removing optional device drivers from the CONFIG.SYS file, and freeing up some hard disk space by deleting unnecessary programs. If the workstation's hard disk is using multiple disk partitions, consider moving the OS/2 swapper file to a larger partition. Disk compression utilities may also be available that can help resolve this problem. After completing these actions, shut down OS/2; then reboot the system. If the problem persists, contact your Novell Authorized Reseller.REQ0919: An incorrect OS/2 version is being used.REQxxxxExplanation: The major versions of the Requester and OS/2 do not match.Action: Upgrade the Requester or OS/2.REQ0937: The Requester driver version does not match the IFS version.REQxxxxExplanation: NWIFS.IFS and NWREQ.SYS were not installed from the same installation diskette.Action: Reinstall the Requester. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=902 ID="BP896"REQ1004: The LAN support module is not installed.REQxxxxExplanation: The Requester driver requires the LSL.SYS driver to be running when it loads. Either the "DEVICE=C:\NETWARE\LSL.SYS" line is missing from the CONFIG.SYS file or the LSL encountered an error while loading.Action: Check the CONFIG.SYS file for the LSL.SYS driver. If the problem persists, contact your Novell Authorized Reseller.REQ1008: A NetWare server cannot be found.REQxxxxExplanation: The Requester tries to locate a NetWare server when it initializes. Either no servers are currently running or there is a cabling problem.Action: Make sure the NetWare server is running and operating properly. Make sure the OS/2 workstation is connected to the network.REQ1010: The program cannot allocate selectors for the connection table.REQxxxxExplanation: All available memory selectors are being used by the system or by previously loaded device drivers.Action: Remove optional or unneeded device drivers from the CONFIG.SYS file and retry the operation. If the problem persists, contact your Novell Authorized Reseller.REQ1011: The program cannot allocate memory for the connection table.REQxxxxExplanation: All available system memory is in use. The Requester cannot load properly.Action: Try adding RAM, reducing the configuration options in the CONFIG.SYS file (for example, reducing the size of DIRCACHE), removing optional device drivers from the CONFIG.SYS file, and freeing up some hard disk space by deleting unnecessary programs. If the workstation's hard disk is using multiple disk partitions, consider moving the OS/2 swapper file to a larger partition. Disk compression utilities may also be available that can help resolve this problem. After completing these actions, shut down OS/2; then reboot the system. If the problem persists, contact your Novell Authorized Reseller.REQ1019: An incorrect OS/2 version is being used.REQxxxxExplanation: The major version of the Requester and OS/2 do not match.Action: Upgrade the Requester or OS/2.REQ1021: The config file cannot be parsed. Default parameters will be used.REQxxxxExplanation: The Requester driver could not read parameters in the NET.CFG file.Action: Make sure the syntax for the NetWare Requester for OS/2 section of the file is correct.PAGENUM=903 ID="BP897"REQ1022: An unrecoverable error occurred. The driver was not loaded.REQxxxxExplanation: The driver could not load properly. This is probably an internal program error.Action: Retry the operation. If the problem persists, contact your Novell Authorized Reseller.REQ1024: The program cannot allocate selectors for worker support.REQxxxxExplanation: All available memory selectors are being used by the system or by previously loaded device drivers.Action: Remove optional or unneeded device drivers from the CONFIG.SYS file. Then retry the operation. If the problem persists, contact your Novell Authorized Reseller.REQ1038: The program cannot allocate memory for the error message buffer.REQxxxxExplanation: All available system memory is in use by the system. The requester cannot load properly.Action: Try adding RAM, reducing the configuration options in the CONFIG.SYS file (for example, reducing the size of DIRCACHE), removing optional device drivers from the CONFIG.SYS file, and freeing up some hard disk space by deleting unnecessary programs. If the workstation's hard disk is using multiple disk partitions, consider moving the OS/2 swapper file to a larger partition. Disk compression utilities may also be available that can help resolve this problem. After completing these actions, shut down OS/2; then reboot the system. If the problem persists, contact your Novell Authorized Reseller.REQ1039: The Requester could not send to NetWare server number as number.REQxxxxExplanation: The Requester waits for a response from the server after each request. If the server does not respond within a certain amount of time, the requester times out.Action: Make sure the server is still running and functioning properly. Make sure all routers between the workstation and the server are still running. If the problem persists, contact your Novell Authorized Reseller.REQ1040: The Requester timed out waiting for reply from server number.REQxxxxExplanation: The Requester waits for a response from the server after each request. If the server does not respond within a certain amount of time, the Requester times out.Action: Make sure the server is still running and functioning properly. Make sure all routers between the workstation and the server are still running. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=904 ID="BP898"REQ1041: Server number did not respond to a request.REQxxxxExplanation: The Requester waits for a response from the server after each request. If the server does not respond within a certain amount of time, the Requester times out. This error can also occur if the server responds with an unexpected response.Action: Make sure the server is still running and functioning properly. Make sure all routers between the workstation and the server are still running. If the problem persists, contact your Novell Authorized Reseller.REQ1042: Connection to NetWare server number as number is now invalid.REQxxxxExplanation: The Requester waits for a response from the server after each request. If the server does not respond within a certain amount of time, the Requester times out.Action: Make sure the server is still running and functioning properly. Make sure all routers between the workstation and the server are still running. If the problem persists, contact your Novell Authorized Reseller.REQ1043: Routing to NetWare server number has been disrupted.REQxxxxExplanation: The routing to the network server has been disrupted.Action: Make sure the server is still running and functioning properly. Make sure all routers between the workstation and the server are still running. If the problem persists, contact your Novell Authorized Reseller.REQ1045: Routing to NetWare server number has been disrupted.REQxxxxExplanation: The network route to the server has been disrupted.Action: Make sure the server is still running and functioning properly. Make sure all routers between the workstation and the server are still running. If the problem persists, contact your Novell Authorized Reseller.REQ1106: The SPDaemon cannot get the SPX version. Error: code.REQxxxxExplanation: The SpxGetVersion call failed. This may be an internal program error.Action: Make sure the SPX.SYS driver has been properly entered in the CONFIG.SYS file. If so, check the messages displayed by the driver for any errors or warnings, and correct the problems indicated. Check for a mismatch of driver versions. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=905 ID="BP899"REQ1107: The SPX driver and the SPX daemon are incompatible versions.REQxxxxExplanation: The SPX.SYS driver and SPDAEMON.EXE versions may not match.Action: Make sure the client SPX.SYS driver and SPDAEMON.EXE are compatible versions. If the problem persists, contact your Novell Authorized Reseller.REQ1108: The SPX driver entry cannot be obtained. Error: code.REQxxxxExplanation: The SPDaemon could not get a handle to the SPX.SYS driver. This may be an internal program error.Action: Make sure the client SPX.SYS driver and SPDAEMON.EXE versions are compatible. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.REQ1109: The SPX daemon is already loaded. Error: code.REQxxxxExplanation: The SPDAEMON.EXE has already registered with the SPX.SYS driver, which means it is already loaded.Action: Make sure the daemon SPDAEMON.EXE has not been entered in the CONFIG.SYS file more than once. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A.REQ1110: The daemon cannot register with the SPX driver. Error: code.REQxxxxExplanation: The SPDaemon cannot communicate with the SPX.SYS driver.Action: Make sure the SPX.SYS file has been properly entered in the CONFIG.SYS file. If so, check the messages displayed by the driver for any errors or warnings, and correct the problems indicated. Check for a mismatch of driver versions. If the problem persists, contact your Novell Authorized Reseller.REQ1111: The SPX device handle cannot be closed. Error: code.REQxxxxExplanation: The SPDeamon cannot close the device handle. This may be an internal program error.Action: Retry the operation. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.REQ1112: The SPDaemon cannot wait on semaphore. Error: code.REQxxxxExplanation: A DosSemSetWait call failed. This may be an internal program error.Action: Retry the operation. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=906 ID="BP900"REQ1113: System information segments cannot be obtained. Error: code.REQxxxxExplanation: The DosGetInfoSeg call failed. This may be an internal program error.Action: Retry the operation. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.REQ1114: Priority for the lock thread cannot be set. Error: code.REQxxxxExplanation: The DosSetPrty call failed. This may be internal program error.Action: Retry the operation. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.REQ1115: The SPX driver cannot be accessed. Error: code.REQxxxxExplanation: The SPDaemon was not able to access SPX.SYS through the call gate.Action: Make sure the SPX.SYS driver has been properly entered in the CONFIG.SYS file. If so, check the messages displayed by the driver for any errors or warnings, and correct the problems indicated. Also check for a mismatch of driver versions; then retry the operation. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.REQ1116: Priority for an AES thread cannot be set. Error: code.REQxxxxExplanation: The DosSetPrty call failed. This may be an internal program error.Action: Retry the operation. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.REQ1117: Priority for a watchdog thread cannot be set. Error: code.REQxxxxExplanation: The DosSetPrty call failed. This may be an internal program error.Action: Retry the operation. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.REQ1118: Priority for a session thread cannot be set. Error: code.REQxxxxExplanation: The DosSetPrty call failed. This may be an internal program error.Action: Retry the operation. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=907 ID="BP901"REQ1119: The SPXCALLS.DLL cannot register with the SPX driver.REQxxxxExplanation: The SPXCALLS.DLL cannot communicate with the SPX.SYS driver.Action: Make sure the SPX.SYS driver has been properly entered in the CONFIG.SYS file. If so, check the messages displayed by the driver for any errors or warnings, and correct the problems indicated. Check for a mismatch of driver versions; then retry the operation. If the problem persists, contact your Novell Authorized Reseller.REQ1205: The driver cannot initialize the CGroup Data variables.REQxxxxExplanation: Normally, key data variable are stored in the driver's CGroup for easy and reliable access. However, in this instance the variables could not be initialized due to a memory-related error.Action: Try adding RAM, reducing the configuration options in the CONFIG.SYS file (for example, reducing the size of DIRCACHE), removing optional device drivers from the CONFIG.SYS file, and freeing up some hard disk space by deleting unnecessary programs. If the workstation's hard disk is using multiple disk partitions, consider moving the OS/2 swapper file to a larger partition. Disk compression utilities may also be available that can help resolve this problem. After completing these actions, shut down OS/2; then reboot the system. If the problem persists, contact your Novell Authorized Reseller.REQ1206: The driver cannot configure SPX.REQxxxxExplanation: The driver in conjunction with the NWCONFIG.DLL failed to parse the NET.CFG file for the SPX parameters.Action: Make sure the format of the NET.CFG file is correct.REQ1207: The driver failed to get support hooks from the LSL or IPX.REQxxxxExplanation: SPX could not open or communicate with either the LINKSUP_ (LSL.SYS) or the IPX_ (IPX.SYS) drivers. The most likely cause of this error is that one or both of these drivers has been improperly installed.Action: Make sure the device drivers LSL.SYS and IPX.SYS have been properly entered in the CONFIG.SYS file. If so, check the messages displayed by the driver for any errors or warnings, and correct the problems indicated. Check for a mismatch of driver versions; then retry the operation. If the problem persists, contact your Novell Authorized Reseller.REQ1208: The OS/2 version cannot be obtained; OS/2 2.0 is assumed.REQxxxxExplanation: The DosGetVersion call failed (an internal program error), or the OS/2 version currently running is not 2.0 or later.Action: Make sure the OS/2 and the SPX.SYS driver are compatible versions. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=908 ID="BP902"REQ1209: The driver cannot get OS/2 DOS variables.REQxxxxExplanation: The SPX.SYS driver could not obtain either the system or local information segment. This may be an internal program error.Action: Retry the operation. If the problem persists, contact your Novell Authorized Reseller.REQ1210: The driver cannot initialize the SPX call gate.REQxxxxExplanation: The SPX.SYS driver could not register a call gate with the LSL.SYS driver.Action: Make sure the LSL.SYS driver has been properly entered in the CONFIG.SYS file. If so, check the messages displayed by the driver for any errors or warnings, and correct the problems indicated. Check for a mismatch of driver versions; then retry the operation. If the problem persists, contact your Novell Authorized Reseller.REQ1211: The driver cannot allocate memory for SPX use.REQxxxxExplanation: The system does not have enough memory to run SPX.Action: Try adding RAM, reducing the configuration options in the CONFIG.SYS file (for example, reducing the size of DIRCACHE), removing optional device drivers from the CONFIG.SYS file, and freeing up some hard disk space by deleting unnecessary programs. If the workstation's hard disk is using multiple disk partitions, consider moving the OS/2 swapper file to a larger partition. Disk compression utilities may also be available that can help resolve this problem. After completing these actions, shut down OS/2; then reboot the system. If the problem persists, contact your Novell Authorized Reseller.REQ1301: The application cannot initialize named pipes.REQxxxxExplanation: The application could not open or communicate with the NMPIPE.SYS driver. Most likely, the NMPIPE.SYS driver is not entered in the CONFIG.SYS file.Action: Make sure the NMPIPE.SYS driver has been properly entered in the CONFIG.SYS file. If so, check the messages displayed by the driver for any errors or warnings, and correct the problems indicated. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=909 ID="BP903"REQINSTALL001: Unable to save install setup to disk.REQINSTALLExplanation: The installation program saves any target directories specified during the installation process. It puts the information in a file called NWINST.DAT, which is located in a directory in the DPATH. This lets the same directories be used each time the installation program is run. This error indicates the file was found, but the data within the file is not correct.Action: All target directory settings will now be reset to default values. Manually type directory changes if you want the target directories to be anything but the default, even if the installation program was run previously.002: Drive not ready or disk error.REQINSTALLExplanation: Either An invalid drive letter was specified or the disk drive does not contain a diskette.Action: Place the appropriate diskette in the disk drive. If the drive letter is invalid, enter the correct drive letter in the dialog box. If necessary, cancel the current operation to return to the step where you are prompted for the drive letter. In this case, retry the operation after entering the drive letter.004: Unable to open the file CONFIG.SYS.REQINSTALLExplanation: The program cannot find the CONFIG.SYS file. It is normally found in the root directory of the boot drive.Action: Make sure the CONFIG.SYS file exists in the directory specified. If the CONFIG.SYS file does not exist, OS/2 keeps a backup copy in the OS2\INSTALL subdirectory so it can be copied it to the root directory.005: Unable to make directory.REQINSTALLExplanation: The target disk or partition is full.Action: Delete some files to free up some disk space.006: Unable to copy file.REQINSTALLExplanation: The file being copied tried to overwrite an existing file with the same name while the existing file was in use by a process.Action: Close the target file. If you cannot close the target file, you may have to boot with DOS and manually copy the file.PAGENUM=910 ID="BP904"007: Remote boot workstations have not been installed on this server.REQINSTALLAction: None. This message is for information only.008: Unable to open the file. Do you want to create one?REQINSTALLExplanation: The installation program tried to save changes to a file that does not exist.Action: To create the file, choose CLASS=MENUITEM MOREINFO="NONE""Yes"; otherwise, choose CLASS=MENUITEM MOREINFO="NONE""No".009: Unable to open or create filename. Please check the path and filename.REQINSTALLAction: Make sure the path and filename are correct.013: You must specify a Network board driver.REQINSTALLExplanation: A network board driver has not been specified.Action: Either choose an LAN board driver from the scroll list or type the name of a third party driver that you have on another disk. Complete this step before continuing the installation. If you type the name of a third-party driver, insert the diskette it is located on into the disk drive.014: You must specify a machine name.REQINSTALLExplanation: The server option must have a name associated with it, such as NP_SERVER1. You have not specified a machine name.Action: If you do not want to enter a name, change the option to client support only.015: Unknown server name.REQINSTALLExplanation: The user is trying to attach to a server that is unknown.Action: Click on the down arrow for a list of available servers to be displayed in the server dialog box.016: An invalid username or password was specified.REQINSTALLExplanation: The user or password is not valid for the server you are trying to attach to.Action: Use a valid username and password. Make sure the user has rights to the server you are trying to attach to.PAGENUM=911 ID="BP905"017: You do not have sufficient rights on this server.REQINSTALLExplanation: The user needs Supervisor rights in SYS:\ to install remote workstations and install the utilities on the server.Action: Log in to the server as user Admin or as a user with Supervisor rights in this directory.018: The workstation address is not valid.REQINSTALLExplanation: The address is not the proper length. The network address must be 8 characters long and the node address must be 12 characters long.Action: Enter the correct number of characters. Be sure to include any leading zeros.019: You must specify a username.REQINSTALLExplanation: When installing remote workstations, enter a valid username for each workstation to be added.Action: Enter a valid username. Make sure the user has rights in the SYS:\RPL2 and SYS:\LOGIN directories.020: You must specify a driver.REQINSTALLExplanation: Each remote workstation must have a network board driver associated with it. Network board drivers have a .200 extension and are found in the SYS:\LOGIN directory.Action: Choose a valid driver from the list.022: Unable to open BOOTCONF.SYS.REQINSTALLExplanation: The remote workstations use the BOOTCONF.SYS file in the SYS:\LOGIN directory. This error can occur if another user on the network has this file open (in an editor, for example).Action: Have the user release control of this file.023: Unable to backup BOOTCONF.SYS file to BOOTCONF.BAK.REQINSTALLExplanation: The disk is full, or someone is accessing the backed up file.Action: If you are not concerned with restoring the file to its previous state, ignore this error.024: Unable to create CONFIG.WSS file in the COMPUTER directory.REQINSTALLExplanation: The installation creates this file for each remote workstation. The file may be in use by one of the workstations.Action: Check the server console for a list of users who are accessing this file.PAGENUM=912 ID="BP906"025: Unable to open file NET.CFG.REQINSTALLExplanation: The NET.CFG file is currently in use.Action: Find the process that has the file open and close it.027: The destination drive is full.REQINSTALLExplanation: The target drive has too many files on it.Action: Delete some files or get a bigger disk drive.028: You must enter a full path to the network board driver.REQINSTALLExplanation: Third party network board drivers must contain a full path.Action: Enter the full path. For example: FORMAT="LINESPECIFIC"MOREINFO="NONE"A:\DRIVERS\MYDRIVER.SYS 030: Unable to open file PROTOCOL.INI.REQINSTALLExplanation: The PROTOCOL.INI file is currently in use, or it cannot be found.Action: Find the process that has the file open and close it, or make sure the path to the file is valid.031: Unable to complete ODINSUP set up.REQINSTALLExplanation: No additional information is available for this message.Action: Contact your Novell Authorized Reseller.032: DriverName name for label name does not exist in PROTOCOL.INI.REQINSTALLExplanation: No additional information is available for this message.Action: Contact your Novell Authorized Reseller.033: You must specify and Adapter Type for the selected driver.REQINSTALLExplanation: No additional information is available for this message.Action: Contact your Novell Authorized Reseller.035: Unable to open file used to communicate with server install.REQINSTALLExplanation: No additional information is available for this message.Action: Contact your Novell Authorized Reseller.PAGENUM=913 ID="BP907"037: One of the support files for name was not copied. This must be copied by hand at a later time.REQINSTALLExplanation: No additional information is available for this message.Action: Contact your Novell Authorized Reseller.038: Unable to open installation command file filename.REQINSTALLExplanation: The installation program is unable to open the NETMAIN.ILS file because it does not exist, or it has become corrupted.Action: Contact your Novell Authorized Reseller.039: Unable to read installation command file filename.REQINSTALLExplanation: No additional information is available for this message.Action: Contact your Novell Authorized Reseller.040: Installation command file filename does not contain a fileset of class.REQINSTALLExplanation: No additional information is available for this message.Action: Contact your Novell Authorized Reseller.041: NetWare and OS/2 are not using the same code page.REQINSTALLExplanation: No additional information is available for this message.Action: Contact your Novell Authorized Reseller.PAGENUM=914 ID="BP908"RIGHTS125: You must have Access rights in order to modify rights.RIGHTSExplanation: The user does not have the appropriate rights to change user rights in the specified path.Action: If appropriate, grant the user the Access Control right in the desired path.130: There is insufficient memory for this utility to execute properly.RIGHTSAction: Free up additional conventional memory in your workstation.150: You do not have Supervisor rights.RIGHTSExplanation: To grant the Supervisor right, the user must have the Supervisor right.Action: If appropriate, grant the user the Supervisor right.225: The specified user was not found.RIGHTSExplanation: The username specified after the /NAME= command line parameter is not a user on that server.Action: Make sure the user's name was typed correctly.250: An error prevented the trustee from being added.RIGHTSExplanation: RIGHTS failed to add the rights or trustee. The bindery or NetWare Directory Services file may be corrupted, the user may not have a valid connection to the server, or an internal program error may have occurred.Action: Make sure the user is connected to the server and the server is operating. Restart RIGHTS and try again. If the problem persists, make sure the bindery or NetWare Directory Services file is not corrupted.300: User or group name is not a trustee of the specified path.RIGHTSExplanation: The specified user or group cannot be deleted from the specified path because the user or group is not a trustee of that file or directory.Action: None. This message is for information only.375: The specified group was not found.RIGHTSExplanation: The group name that was entered on the command line is not a group in the server.Action: Enter a valid group name, then try the operation again.PAGENUM=915 ID="BP909"450: An error occurred while the program was getting the user ID.RIGHTSExplanation: RIGHTS was unable to get the object ID from the specified server. The bindery or NetWare Directory Services file may be corrupted, the user may not have a valid connection to the server, or an internal program error may have occurred.Action: Make sure the user is connected to the server and the server is operating. Restart RIGHTS and try again. If the problem persists, make sure the bindery or NetWare Directory Services file is not corrupted.525: You do not have rights to this directory area.RIGHTSExplanation: The user tried to access a directory in which he or she has no rights.Action: If appropriate, grant the user the appropriate rights.550: The system was unable to get the rights. Error code: code.RIGHTSExplanation: The rights requested did not execute successfully. The bindery or NetWare Directory Services file may be corrupted, the user may not have a valid connection to the server, or an internal program error may have occurred.Action: Make sure the user is connected to the server and the server is operating. Restart RIGHTS and try again. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A.575: An error occurred while RIGHTS was deleting the specified trustee.RIGHTSExplanation: RIGHTS could not delete the specified trustee. The bindery or NetWare Directory Services file may be corrupted, the user may not have a valid connection to the server, or an internal program error may have occurred.Action: Make sure the user is connected to the server and the server is operating. Restart RIGHTS and try again. If the error persists, make sure the bindery or NetWare Directory Services file is not corrupted.625: You cannot use rights on a local drive.RIGHTSExplanation: The user tried to define rights for a local drive. Users cannot be given rights to local drives.Action: Do not grant rights to a local drive.650: This utility was unable to get the connection number.RIGHTSPAGENUM=916 ID="BP910"Explanation: A time-out may have occurred preventing RIGHTS from getting the connection number. The bindery or NetWare Directory Services file may be corrupted, the user may not have a valid connection to the server, or an internal program error may have occurred.Action: Make sure the user is connected to the server and the server is operating. Restart RIGHTS and try again. If the error recurs, make sure the bindery or NetWare Directory Services file is not corrupted. If the problem persists, contact your Novell Authorized Reseller.675: This utility was unable to get the connection information.RIGHTSExplanation: RIGHTS could not get the connection information. The bindery or NetWare Directory Services file may be corrupted, the user may not have a valid connection to the server, or an internal program error may have occurred.Action: Make sure the user is connected to the server and the server is operating. Restart RIGHTS and try again. If the error recurs, check the connection status. If the problem persists, contact your Novell Authorized Reseller.700: This utility was unable to get the user's name.RIGHTSExplanation: RIGHTS was unable to get the user's name from the specified server. The bindery or NetWare Directory Services file may be corrupted, the user may not have a valid connection to the server, or an internal program error may have occurred.Action: Make sure the user is connected to the server and the server is operating. Restart RIGHTS and try again. If you get the same error, make sure the bindery or NetWare Directory Services file is not corrupted.725: You must be Supervisor equivalent to access the Inheritance option for objects other than yourself.RIGHTSAction: If appropriate, grant the Supervisor or equivalent rights to the user, or show the inheritance of the specified user using the utility.726: RIGHTS was unable to get your effective rights.RIGHTSExplanation: RIGHTS could not get the effective rights for the user. The bindery or NetWare Directory Services file may be corrupted, the user may not have a valid connection to the server, or an internal program error may have occurred.Action: Make sure the user is connected to the server and the server is operating. Restart RIGHTS and try again. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=917 ID="BP911"727: RIGHTS was unable to get the servername.RIGHTSExplanation: RIGHTS could not get the name of the server. The bindery or NetWare Directory Services file may be corrupted, the user may not have a valid connection to the server, or an internal program error may have occurred.Action: Make sure the user is connected to the server and the server is operating. Restart RIGHTS and try again. If the problem persists, contact your Novell Authorized Reseller.728: RIGHTS was unable to get the user's security equivalents.RIGHTSExplanation: RIGHTS could not get the security equivalents for this user. The bindery or NetWare Directory Services file may be corrupted, the user may not have a valid connection to the server, or an internal program error may have occurred.Action: Make sure the user is connected to the server and the server is operating. Restart RIGHTS and try again. If the problem persists, contact your Novell Authorized Reseller.729: RIGHTS was unable to get the trustees for this path.RIGHTSExplanation: RIGHTS could not determine the trustee for this path. The bindery or NetWare Directory Services file may be corrupted, the user may not have a valid connection to the server, or an internal program error may have occurred.Action: Make sure the user is connected to the server and the server is operating. Restart RIGHTS and try again. If the problem persists, contact your Novell Authorized Reseller.730: RIGHTS was unable to get the objects effective rights.RIGHTSExplanation: RIGHTS could not get the effective rights for the object. The bindery or NetWare Directory Services file may be corrupted, the user may not have a valid connection to the server, or an internal program error may have occurred.Action: Make sure the user is connected to the server and the server is operating. Restart RIGHTS and try again. If the problem persists, contact your Novell Authorized Reseller.800: An error occurred attempting to get directory information for file filename. Error code: code.RIGHTSExplanation: RIGHTS could not get the directory information for the filename displayed in the message.Action: For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A.PAGENUM=918 ID="BP912"825: Open is only valid with NetWare 2.x.RIGHTSExplanation: You tried to use the Open right on a NetWare 3 or NetWare 4 server. This right is only supported on NetWare 2.x servers.Action: Do not try to use the Open right on NetWare 3 or 4 servers.901: You are not attached to the specified server.RIGHTSAction: See message IDREF="FM84261""901: You are not attached to the specified server." in Appendix C.903: The command line syntax is invalid. For help, type RIGHTS /?.RIGHTSAction: See message IDREF="FM18860""903: The command line syntax is invalid." in Appendix C.905: This utility was unable to initialize the country information.RIGHTSAction: See message IDREF="FM55337""905: This utility was unable to initialize the country information." in Appendix C.908: The specified path is invalid.RIGHTSAction: See message IDREF="FM51165""908: The specified path is invalid." in Appendix C.909: You are not mapped to the specified drive.RIGHTSAction: See message IDREF="FM28663""909: You are not mapped to the specified drive." in Appendix C.910: This utility was unable to parse the specified path.RIGHTSAction: See message IDREF="FM47164""910: This utility was unable to parse the specified path." in Appendix C.911: This utility works on directories only for NetWare v2.15.RIGHTSAction: Use the utility appropriate to the version of NetWare you are using.913: The specified directory cannot be found.RIGHTSAction: See message IDREF="FM19478""913: The specified directory cannot be found." in Appendix C.914: The specified file or directory cannot be found.RIGHTSAction: See message IDREF="FM82066""914: The specified file or directory cannot be found." in Appendix C.916: This utility only supports 25 levels of directories. It can't display path.RIGHTSAction: See message IDREF="FM77950""916: This utility only supports 25 levels of directories." in Appendix C.PAGENUM=919 ID="BP913"917: This utility was unable to set the context.RIGHTSAction: See message IDREF="FM32126""917: This utility was unable to set the context." in Appendix C.925: This utility is not supported on Personal NetWare servers. Use the Personal NetWare utilities.RIGHTSAction: Use the equivalent Personal NetWare utility.970: The attempt to open the Unicode table files failed.RIGHTSAction: See message IDREF="FM15675""970: The attempt to open the Unicode table files failed." in Appendix C.971: The workstation does not have enough memory to load the Unicode table files.RIGHTSAction: See message IDREF="FM55341""971: The workstation does not have enough memory to load the Unicode table files." in Appendix C.972: Access to the Unicode table files was denied.RIGHTSAction: See message IDREF="FM90152""972: Access to the Unicode table files was denied." in Appendix C.973: The Unicode table files cannot be found in the NLS directory or in the search path. Code page: <number>  Country:  <number>RIGHTSAction: See message IDREF="FM62778""973: The Unicode table files cannot be found in the NLS directory or in the search path. Code page: number Country: number" in Appendix C.974: The Unicode table files are corrupt.RIGHTSAction: See message IDREF="FM63405""974: The Unicode table files are corrupt." in Appendix C.975: The Unicode table files cannot be opened because there are already too many open files. Close some files or modify your CONFIG.SYS file.RIGHTSAction: See message IDREF="FM49793""975: The Unicode table files cannot be opened because there are already too many open files. Close some files or modify your CONFIG.SYS file." in Appendix C.998: The message file found (<utility_name>.MSG) is an incorrect version. The correct version is <number>. See your network supervisor for assistance.RIGHTSAction: See message IDREF="FM91957""998: The message file found (utility_name.MSG) is an incorrect version. The correct version is number. See your network supervisor for assistance." in Appendix C.PAGENUM=920 ID="BP914"999: The message file for this utility cannot be found.RIGHTSAction: See message IDREF="FM69424""999: The message file for this utility cannot be found." in Appendix C.PAGENUM=921 ID="BP915"RS2321: The NLM was unable to open the call back list file.RS232Explanation: The call back option has been enabled, but the call back list file, SYS:SYSTEM\CALLBACK.LST, could not be located. You will not be able to complete calls with the call back option enabled until this file is created.Action: If you are a network supervisor, either create the file or disable the call back function.5: The NLM could not allocate a Screen resource tag.RS232Explanation: The server does not have enough memory to load the RS232 NLM.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.6: The NLM could not open the modem interaction screen.RS232Explanation: The server does not have enough memory to load the RS232 NLM.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.8: The NLM could not allocate a memory resource tag.RS232Explanation: The server does not have enough memory to load the RS232 NLM.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.10: The NLM could not allocate a timer event resource tag.RS232Explanation: The server does not have enough memory to load the RS232 NLM.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.12: The NLM could not allocate a console command resource tag.RS232Explanation: The server does not have enough memory to load the RS232 NLM.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.14: The NLM could not allocate an AES Event resource tag.RS232Explanation: The server does not have enough memory to load the RS232 NLM.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.PAGENUM=922 ID="BP916"16: The NLM could not allocate a resource tag for the process.RS232Explanation: The server does not have enough memory to load the RS232 NLM.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.18: The NLM could not allocate an asynchronous IO resource tag.RS232Explanation: The server does not have enough memory to load the RS232 NLM.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.19: The AIO NLM and a COM port driver NLM must be loaded first.RS232Explanation: The server tried to load the RS232 NLM before the AIO NLM and a COM port driver NLM were loaded.Action: Load the AIO.NLM file. Load the appropriate COM port driver (such as AIOCOMX.NLM). Load the RS232 NLM.21: The NLM could not allocate a hardware interrupt resource tag.RS232Explanation: The server does not have enough memory to load the RS232 NLM.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.23: The NLM could not allocate a hardware configuration resource tag.RS232Explanation: The server does not have enough memory to load the RS232 NLM.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.24: The NLM could not allocate memory for the process stack.RS232Explanation: The server does not have enough memory to load the RS232 NLM.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.25: The NLM could not allocate memory for the read process stack.RS232Explanation: The server does not have enough memory to load the RS232 NLM.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.26: The NLM was unable to reference AIO support functions.RS232Explanation: Although the AIO NLM (Asynchronous I/O) is loaded, the functions necessary to support RS232 are not available.Action: Make sure the AIO NLM is the Novell-supplied product. If it is, contact your Novell Authorized Reseller.PAGENUM=923 ID="BP917"27: Null Modem and Call Back options cannot be used simultaneously.RS232Explanation: RS232.NLM has been loaded with the call back option. This prohibits the use of the null modem feature.Action: Unload the RS232 NLM; then reload it without the call back feature.28: The NLM could not get AIO port information.RS232Explanation: The AIO NLM (Asynchronous I/O) is either not loaded or is improperly initialized. If the AIO NLM is loaded, no COM port driver NLM (for example, AIOCOMX.NLM) is loaded; hence, AIO cannot recognize any COM ports.Action: Make sure the AIO NLM and the COM port driver are loaded and initialized properly.42: The NLM could not reserve IRQ number and Port Address address.RS232Explanation: This number and address are being used by another NLM.Action: Unload the other NLM; then load this one.43: The NLM could not initialize and attach a driver to REMOTE.NLM. The error was code.RS232Explanation: The REMOTE NLM is not loaded.Action: Make sure the REMOTE NLM is loaded before loading this NLM.For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.44: The modem was initialized.RS232Explanation: The modem was initialized.Action: No action is required. This message is for information only.45: The modem could not be initialized.RS232Explanation: The modem may not be properly connected, or the settings may be incorrect.Action: Make sure the modem is connected properly and that all switches are set properly according to the owner's manual.51: Please re-initialize the modem.RS232Explanation: The modem is not functioning properly.Action: Turn the power to the modem off and back on. Unload then reload RS232.NLM, or type MODEM and type the proper initialization command for the modem.PAGENUM=924 ID="BP918"54: The call back number was not received. The NLM is unable to reconnect.RS232Explanation: A workstation tried to use an outdated version of RCONSOLE.EXE to attach to this server.Action: Update the RCONSOLE.EXE and retry the operation. If the problem persists, contact your Novell Authorized Reseller.55: The NLM was unable to read the call back list file.RS232Explanation: The call back option has been enabled, but the call back list file, SYS:SYSTEM\CALLBACK.LST, could not be read. You will not be able to complete calls with the call back option enabled until this file is created.Action: If you are a network supervisor, either create the file or disable the call back function.56: The number number is an unauthorized call back number.RS232Explanation: The call back option has been enabled, but the call back list file, SYS:SYSTEM\CALLBACK.LST, does not contain the number that was sent from the remote workstation.Action: If the remote number is a legal number for connection to this server, add it to the lists in the call back list file. Use EDIT.NLM to do this from the server, or use any text editor to do this from a workstation.61: Remote console connection refused for workstation.RS232Explanation: An incorrect password was given by the remote workstation user.Action: Make sure the workstation operator has a valid password and that it is typed correctly.81: A zero-byte packet was received.RS232Explanation: This is a serious internal system error.Action: Contact your Novell Authorized Reseller.93: Modem commands are not allowed during an active asynchronous session.RS232Action: To enter modem commands, wait until no workstations are connected to the server via the asynchronous connection.125: The requested port is already owned by user name or number.RS232Explanation: The communication port is unavailable.Action: Choose a different port.PAGENUM=925 ID="BP919"125: The port is unavailable.RS232Explanation: The specified port is being used or does not exist.Action: Find out what NLM is using the port and unload it, or choose another port.126: AIO write of number bytes only wrote number bytes.RS232Explanation: This is an internal system error. Asynchronous I/O failed. The cause for this error is unknown.Action: Contact your Novell Authorized Reseller.PAGENUM=926 ID="BP920"RSA1: The message file name is invalid. The program cannot be loaded.RSAExplanation: The .MSG file is invalid. This problem could be the result of a corrupted file, a bad translation, or an outdated file version.Action: Either update the .MSG file with a valid copy or delete the file. The DOS Requester will use the default messages that are bound to the binary files.5: Module1.VLM is not loaded. The module2.VLM file cannot be loaded before module1.VLM. Load the module1.VLM file first then try to load the module2.VLM file.RSAExplanation: The module2.VLM requires that the module1.VLM be loaded first. Either the current configuration has module1.VLM and module2.VLM loading out of order, or module1.VLM did not load successfully.Action: Make sure the module1.VLM is configured to load before module2.VLM. To do this, change the load order of the "VLM=" parameter in the NET.CFG file.7: In order to load the module3.VLM, one of the following VLMs must be loaded: module1.VLM, module2.VLM.RSAExplanation: The module3.VLM requires that module1.VLM or module2.VLM be loaded first. Either the current configuration has module3.VLM loading before the modules in the module1.VLM or module2.VLM list, or module1.VLM or module2.VLM did not load successfully.Action: Make sure the module1.VLM or module2.VLM loads successfully before loading module3.VLM.42: There is a missing or invalid value for `parameter' on line number of the configuration file. This entry will be ignored. Correct the line specified in the configuration file before continuing.RSAExplanation: The configuration file contains a configuration keyword that has an invalid parameter, or that does not specify a parameter. This invalid line will be ignored by the configuration process.Action: Because this line will be ignored, no action is required now. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message.PAGENUM=927 ID="BP921"43: There is a missing or invalid ON/OFF value for `parameter' on line number of the configuration file. This entry will be ignored. Correct the line specified in the configuration file before continuing.RSAExplanation: The configuration file contains a configuration keyword that is defined to use either an "ON" or "OFF" parameter, but a different parameter, or no parameter, has been specified. This invalid line will be ignored by the configuration process.Action: Because this line will be ignored, no action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message.45: The parameter specified for the following option was out of range and has been adjusted.RSAExplanation: A configurable parameter has been configured too high or too low to be valid. The invalid parameter is specified on the line following the message.Correct the parameter specified in the NET.CFG file. For more information about the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.PAGENUM=928 ID="BP922"RSPX2: The NLM could not allocate an alloc resource tag.RSPXExplanation: The server does not have enough memory to load the RSPX NLM.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.4: The NLM could not allocate an AES event resource tag.RSPXExplanation: The server does not have enough memory to load the RSPX NLM.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.6: The NLM could not allocate a timer event resource tag.RSPXExplanation: The server does not have enough memory to load the RSPX NLM.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.8: The NLM could not allocate a console command resource tag.RSPXExplanation: The server does not have enough memory to load the RSPX NLM.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.10: The NLM could not allocate a process resource tag.RSPXExplanation: The server does not have enough memory to load the RSPX NLM.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.12: The NLM could not allocate a resource tag for IPX sockets.RSPXExplanation: The server does not have enough memory to load the RSPX NLM.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.13: The NLM could not allocate memory for a process stack.RSPXExplanation: The server does not have enough memory to load the RSPX NLM.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.14: The NLM could not open an IPX socket.RSPXExplanation: The cause of this error is uncertain.Action: Contact your Novell Authorized Reseller.PAGENUM=929 ID="BP923"16: The NLM could not attach the SPX driver to REMOTE.NLM.RSPXExplanation: REMOTE.NLM was not loaded properly on the server.Action: Reload REMOTE.NLM and retry the operation.24: Remote console connection refused for address.RSPXExplanation: An incorrect password was supplied by the workstation at the given address.Action: The remote user must type in the correct password.PAGENUM=930 ID="BP924"SALVAGE020: You do not have sufficient rights to salvage files in the selected directory. Please enter a new path.SALVAGEExplanation: The user doesn't have the Create right in the selected directory to salvage files.Action: Make sure the user has the Create right in the selected directory.025: You do not have sufficient rights to purge salvageable files in the selected directory.SALVAGEExplanation: The user doesn't have the Delete right in the selected directory to purge files.Action: Make sure the user has the Delete right in the selected directory.035: You are not attached to any servers.SALVAGEExplanation: No file servers were detected in the stations connection list.Action: Log out; then log in again.040: Error code occurred during the program's attempt to salvage files.SALVAGEExplanation: The system encountered an error while restoring deleted files.Action: Try again to restore the deleted files. If the problem persists, contact your Novell Authorized Reseller. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 045: An attempt to purge the file name returned the error code.SALVAGEExplanation: The system encountered an error while purging deleted files.Action: Try again to purge the file. If the problem persists, contact your Novell Authorized Reseller. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 050: An attempt to recover filename as new_name returned the error code.SALVAGEExplanation: The system encountered an error while restoring a file to another name.Action: Try to restore the file without renaming it. If the problem persists, contact your Novell Authorized Reseller. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. PAGENUM=931 ID="BP925"055: An attempt to recover filename as new_name returned the error code. The new filename is too long.SALVAGEExplanation: The system detected that the new filename exceeded the DOS limit of eight characters for the name and three characters for the extension.Action: Try again. Make sure that the new filename doesn't exceed the eight-character name, three-character extension limit. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 070: You do not have rights to recover files from deleted directories on this volume.SALVAGEExplanation: The user doesn't have the Create right to salvage files in the selected directory.Action: If the user needs to salvage files from the selected directory, make sure the user has the Create right.085: The searchable subdirectory is too deep in the Directory tree.SALVAGEExplanation: NetWare supports only 25 subdirectory levels, and Purge has exceeded this limit.Action: Use MAP to map a drive path deeper into the directory, and try again. Limit the directory structures to 25 levels.090: Salvageable files cannot be viewed because your workstation does not have enough memory.SALVAGEExplanation: The workstation may not have enough available memory.Action: Select only the file or files needed when prompted for the file name pattern to match. Increase the available memory. See "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network.095: An error occurred during an attempt to change the path, and path name cannot be restored. The program cannot continue.SALVAGEExplanation: The user selected a new path that didn't exist, and the salvage failed to restore the old path.Action: Verify that the directory still exists, and run the utility again.100: The path is being shortened to volume level for 286 server.SALVAGEExplanation: NetWare 2.x supports salvaging only on a volume basis, so the path will be truncated to server/volume:.Action: None. This message is for information only.PAGENUM=932 ID="BP926"105: You do not have sufficient rights to purge files in the current directory.SALVAGEExplanation: The user doesn't have the Delete right in the selected directory to purge files.Action: Make sure the user has the Delete right in the selected directory.110: This volume does not support salvageable files.SALVAGEExplanation: Files cannot be salvaged on the current volume.Action: None. This message is for information only.115: The DELETED.SAV directory doesn't exist on the selected volume. Have the network supervisor create the directory and flag it as a hidden directory.SALVAGEAction: Create a directory named DELETED.SAV and flag it as a hidden directory.901: You are not attached to the specified server.SALVAGEAction: See message IDREF="FM84261""901: You are not attached to the specified server." in Appendix C.915: The specified volume (name) does not exist. Please enter a new path.SALVAGEAction: See message IDREF="FM46881""915: The specified volume does not exist." in Appendix C.918: This utility was unable to get connection information.  Error code: <code>.SALVAGEAction: See message IDREF="FM25772""918: This utility was unable to get connection information. Error code: code." in Appendix C.991: An error occurred in <function_name>. Error code: <code>.SALVAGEAction: See message IDREF="FM90152""972: Access to the Unicode table files was denied." in Appendix C.PAGENUM=933 ID="BP927"SBACKUP0:  This version of SBACKUP cannot use magazines or changes. Please select a single-media device.SBACKUPExplanation: The hardware is a set up as a multiple-media device, but this version of SBACKUP doesn't support the use of magazines or changes.Action: Check the hardware documentation to determine if and how your hardware can be setup as a single-media device.8: SBACKUP cannot parse path path.SBACKUPExplanation: The directory path for the log file was typed incorrectly or does not exist.Action: Check the log file path for spelling errors, and make sure that the specified volumes and directories exist.14: Selected server name is not allowed. Only server name is allowed.SBACKUPExplanation: You specified a path for log files that is not on the current server. Log files may not be redirected to another server.Action: Select a directory for the log files on the current server.17: Error code occurred in GetServerInformation.SBACKUPExplanation: The program was unable to read the server configuration information, including the list of mounted volumes.Action: Exit SBACKUP and restart the backup process. If the error occurs again, test the server for correct operation and configuration. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.18: Error code occurred during SBACKUP's attempt to open directory name.SBACKUPExplanation: The specified directory in the directory selection list could not be opened. The directory may not exist, or the user may not have rights to the directory. Action: Make sure that the specified directory exists and that the user has access rights. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. PAGENUM=934 ID="BP928"19: An invalid error message number has been generated.SBACKUPExplanation: An internal system error occurred when the program tried to assign a number to an error message.Action: None. This message is for information only.47: Error code occurred during SBACKUP's attempt to seek on media name.SBACKUPExplanation: The backup program could not locate itself at the requested media position.Action: Make sure that the correct media is in the device. If restore is being done with session files, check the file for integrity by returning to the main menu and selecting "Log/Error File Administration, View Log File." Also make sure that the storage device is operating correctly. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 53: SBACKUP cannot put a name in the data set name: name.SBACKUPExplanation: No name could be assigned to the data set name in the list. Action: Make sure a valid data set name for the name space type is specified. For more information, see "BOOK="cncptenu" COLLECTION="nw41"Data Set" in Concepts. Increase the available memory. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.58: The session file name is corrupted.SBACKUPExplanation: The backup session's log file does not have valid header information. This file can no longer be used.Action: Complete the restore session without a session log file. For more information, see "BOOK="superenu" COLLECTION="nw41"Backing Up and Restoring Data" in Supervising the Network.59: A data set does not exist.SBACKUPExplanation: The specified data set (probably a file or directory) could not be found.Action: Use a valid name for the file or directory and type the name correctly.60: Error code occurred during SBACKUP's attempt to read from a file.SBACKUPExplanation: The program could not completely read the file. The file may be corrupted.Action: If possible, make sure the file is not corrupted. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. PAGENUM=935 ID="BP929"61: Error code occurred during SBACKUP's attempt to get the data set number.SBACKUPExplanation: An internal error has occurred. The DOS name space name for the data set could not be read.Action: None. This message is for information only. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 67: Error code occurred during SBACKUP's attempt to open file name.SBACKUPExplanation: You may have specified an invalid filename, or the user may not have access rights to the file. Action: Make sure the file exists and the filename is valid for the specified name space type. Make sure that appropriate file access flags have been set. Make sure the user has appropriate user access rights. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 68: Error code occurred during SBACKUP's attempt to close file name. Processing will continue.SBACKUPExplanation: The indicated file could not be closed, but the backup session is continuing. It is possible that the file or volume may be corrupted. Action: After the backup finishes, check the session and error files. Repeat the backup procedure on any files that were not backed up. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 69: Error code occurred during SBACKUP's attempt to seek within file name.SBACKUPExplanation: An error prevented the program from completing the seek process within the indicated file.Action: Make sure that the file exists and that it is not corrupted. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 73: Session mode mode is invalid.SBACKUPExplanation: SBACKUP doesn't know whether it is supposed to back up or to restore.Action: Exit SBACKUP and try the operation again.74: An undefined error has occurred: code.SBACKUPExplanation: An undefined error has been received by SBACKUP.Action: None. This message is for information only. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. PAGENUM=936 ID="BP930"75: Error code occurred during SBACKUP's attempt to create file name.SBACKUPExplanation: The new file could not be given the name you tried to give it.Action: Make sure a valid path (including volume name) is specified. Make sure the file exists and the filename is valid. Make sure the user has appropriate user access rights to create a file in this directory. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 85: The date format is invalid.SBACKUPExplanation: An invalid date format was typed.Action: Enter the date using a valid date format. To see the correct format, press MOREINFO="NONE"<F1>.87: A bad session ID was encountered on the backup media cartridge. The session ID in the data field did not match the expected session ID. Either the data is corrupted or the data file was renamed.SBACKUPExplanation: The session ID on the media does not match the session log filename.Action: Use the "Restore without session files" option.107: Error code occurred during SBACKUP's attempt to delete file name.SBACKUPExplanation: An invalid filename has been specified. The file may not exist, or the user may not have rights to delete the file.Action: Make sure the file exists and the filename is valid. Make sure the user has appropriate user access rights. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 109: An error occurred during SBACKUP's attempt to read from media name.SBACKUPExplanation: The media could not be read, possibly due to a media defect or device failure.Action: Make sure that the device is functioning properly, and verify that the media is not corrupted.110: An error occurred during SBACKUP's attempt to write to media name.SBACKUPExplanation: This is a media write error, or a possible media or device failure.Action: Make sure that the device is functioning properly make sure that the media is not corrupted.PAGENUM=937 ID="BP931"115: The time format is invalid.SBACKUPExplanation: An invalid time was typed.Action: Enter the time using a valid format. To see the correct format, press MOREINFO="NONE"<F1>.116: SBACKUP cannot list the Target Service Agents: TSA_message.SBACKUPExplanation: No target service agents (TSAs) have been loaded on the selected target server.Action: Make sure that target service agents are loaded on the selected server or workstation. You might also need to unload the Storage Management Data Requester (SMDR) and any other files you are prompted to unload; then reload the TSA.120: The message buffer is full. Internal error: message_lengthSBACKUPExplanation: An error message exceeds the maximum allowable length, possibly due to message expansion during translation.Action: If the problem persists, contact your Novell Authorized Reseller.126: The storage media label does not match the label you typed in.SBACKUPExplanation: The requested media does not match the media in the device.Action: Place correct media in the device and retry.127: No Target Service Agents are available. Exit SBACKUP and load a TSA for the target you want to back up.SBACKUPExplanation: No target service agents (TSAs) are found on the selected server or workstation.Action: Load a TSA on the selected target server, or select a server that has a TSA loaded.128: An error occurred during SBACKUP's attempt to mount the media: media_label.SBACKUPExplanation: SBACKUP is unable to mount a media in the selected device. Another media may already be in the device.Action: Check for media in the device. Insert media if none are found, or select another device.129: An error occurred during SBACKUP's attempt to dismount media media_label.SBACKUPExplanation: SBACKUP cannot dismount the media.Action: Check for media in the device. If none are present, make sure the device is operating properly.PAGENUM=938 ID="BP932"131: SBACKUP cannot read the data set: data_set_name.SBACKUPExplanation: SBACKUP encountered a problem reading the data set (probably a file or directory) from the disk. The data set on the backup media may not be correct.Action: Make sure that the data set (probably a file or directory) is not corrupted; then try the backup again.135: SBACKUP cannot append name to the current list.SBACKUPExplanation: The server may not have enough available memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.136: The list stack is full. SBACKUP cannot perform the function you requested.SBACKUPExplanation: SBACKUP cannot add another list. The server may not have enough available memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.137: The program cannot connect to SDI; it may not be loaded: SDI_message.SBACKUPExplanation: The storage device interface (SDI) module could not be found.Action: Make sure that the SDI is loaded on this server; load it if it is not.139: SBACKUP cannot append to empty media.SBACKUPExplanation: An append was requested on media having no label or a label that cannot be read. If the media has been used previously, an error has occurred reading the media header, indicating that the media could be damaged.Action: If the media has not been used previously, restart without the append option. If the media has been used, service the device and inspect the media for damage.140: An attempt to restore an internal list failed. SBACKUP probably will abort.SBACKUPExplanation: An internal error occurred in SBACKUP.Action: Exit SBACKUP and try the operation again. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=939 ID="BP933"143: A TLI Transport timeout failure has occurred.SBACKUPExplanation: A failure occurred in transport layer interface (TLI) communication (time-out). SBACKUP could not communicate with a remote Storage Management Services (SMS) module (for example, TSA-400 or TSA-311).Action: Make sure that communication exists between the server on which SBACKUP is loaded and the server on which the other SMS modules are loaded. Also make sure that transport layer NLM programs are loaded and functional on both servers.153: SBACKUP cannot append a prompt field.SBACKUPExplanation: SBACKUP failed to add the PROMPT field to the form (data entry screen). The server may not have enough available memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.154: SBACKUP cannot append to a menu.SBACKUPExplanation: SBACKUP cannot add another item to the menu. The server may not have enough available memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.155: SBACKUP cannot append a hot spot field.SBACKUPExplanation: SBACKUP cannot add the HOT SPOT field item to the form (data entry screen). The server may not have enough available memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.156: SBACKUP cannot append a string field.SBACKUPExplanation: SBACKUP cannot add a string to the current screen. The server may not have enough available memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.158: SBACKUP cannot append a boolean field.SBACKUPExplanation: SBACKUP cannot add a Boolean field item to the current form (data entry screen). The server may not have enough available memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.PAGENUM=940 ID="BP934"162: The media could not be released: name.SBACKUPExplanation: Another application may be using the requested media, or the media may not be in the specified device.Action: Make sure that the media is in the specified device. If it is, wait a moment and then try again.163: The media could not be selected: SDI_message.SBACKUPExplanation: The storage device interface (SDI) could not select the requested media.Action: Make sure that the storage device contains the correct media. Make sure that the media is not in exclusive use by another process. Make sure that the device is operating properly.164: An error occurred during SBACKUP's attempt to get the media status: SDI_message.SBACKUPExplanation: The storage device interface (SDI) could not read the status information on the requested media.Action: Make sure that the storage device contains the correct media and that the device is operating properly. Make sure that the media is available for use.165: An error occurred during SBACKUP's attempt to get the device status: SDI_message.SBACKUPExplanation: The storage device interface (SDI) could not read the status information on the requested device.Action: Make sure that the device is available for use. Make sure the device is operating properly.166: An error occurred in InsertInPortalList. Error code: code.SBACKUPExplanation: This is an SBACKUP screen interface error; the program could not process the menu list correctly. The server may not have enough available memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 170: An error occurred during SBACKUP's attempt to access the session file.SBACKUPExplanation: SBACKUP could not access the session log files.Action: Check the session log file directory path to make sure that the path is valid and that log files exist in the specified directory. Make sure the user has appropriate user access rights to the log file directory.PAGENUM=941 ID="BP935"174: SBACKUP cannot append to the form.SBACKUPExplanation: An SBACKUP screen interface error occurred when the program tried to process the current screen form. The server may not have enough available memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.183: This device cannot be selected: SDI_message.SBACKUPExplanation: The storage device interface (SDI) cannot select the requested device.Action: Make sure the user has appropriate user access rights to the requested device. Make sure the device is available. Make sure the device is operating properly.184: The device cannot be released: SDI_message.SBACKUPExplanation: The storage device interface (SDI) could not release the requested device.Action: Make sure the user has appropriate user access rights to the device, and that the requested device has been previously reserved. Make sure there are no pending requests for the specified device. Make sure that the device is operating properly.186: The device could not be labeled: SDI_message.SBACKUPExplanation: The storage device interface (SDI) could not label the requested device.Action: Make sure the user has appropriate user access rights to the device. Make sure the requested device has been reserved for use. Make sure the device is operating properly.188: An error occurred during SBACKUP's attempt to position the media: SDI_message.SBACKUPExplanation: The storage device interface (SDI) could not be positioned to the requested place on the media.Action: Make sure that the correct media is being used in the selected device. Make sure the device is operating properly.189: An error occurred during SBACKUP's attempt to read the media header: SDI_message.SBACKUPExplanation: The storage device interface (SDI) could not read the media header on the requested media.Action: Make sure that the correct media is being used in the selected device. Make sure the device is operating properly.PAGENUM=942 ID="BP936"190: An error occurred during SBACKUP's attempt to interpret media header: SDI_message.SBACKUPExplanation: SBACKUP could not recognize the data in the media header.Action: Make sure that the correct media is being used in the selected device. Make sure the media is in Storage Management Services (SMS) format. Make sure it is not damaged. Make sure that the device is operating properly.195: SBACKUP cannot put the next name in the data set name: SDI_message.SBACKUPExplanation: SBACKUP could not add a data set name (probably a file or directory) to the processing list. The name may be invalid. The server may not have enough available memory.Action: Make sure a valid data set name for the name space type is specified. Increase the available memory. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.208: The SBACKUP screen cannot be opened.SBACKUPExplanation: SBACKUP cannot create a user screen. The server may not have enough available memory.Explanation: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.211: SBACKUP cannot allocate the resource_name resource tag.SBACKUPExplanation: SBACKUP cannot allocate a required server resource. The server may not have enough available memory.Explanation: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.219: There are no session files in directory name.SBACKUPExplanation: SBACKUP found no session log files in the specified log file directory.Action: Specify the correct session log file directory. Make sure the user has appropriate user access rights to the session log file directory.221: An invalid file type was used.SBACKUPExplanation: SBACKUP has an invalid filename.Action: Check the syntax of the filename for the specified name space. The filename must be complete and contain no "wildcard" characters (for example, * and ?).PAGENUM=943 ID="BP937"227: SBACKUP cannot create the path path.SBACKUPExplanation: SBACKUP cannot create the specified directory path.Action: Make sure a valid path (including volume name) is specified. Make sure the user has appropriate user access rights to create the specified directory path.228: An error occurred during SBACKUP's attempt to get name space type information name_space_type.SBACKUPExplanation: SBACKUP could not get the name space information for the specified name space.Action: Make sure that name spaces are supported on the volume and that name space driver NLM programs are loaded.229: This program cannot concatenate a data set name name and name.SBACKUPExplanation: SBACKUP cannot concatenate the specified names. The names may have invalid lengths. The server may not have enough available memory.Action: Make sure that the names are within valid length range. Increase the available memory. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.230: This backup utility cannot separate a data set name name.SBACKUPExplanation: SBACKUP cannot recognize a data set name (probably a file or directory) in the specified path.Action: Make sure that the specified path conforms to syntax requirements for the specified name space.231: An error occurred during SBACKUP's attempt to get the devices list: device_name.SBACKUPExplanation: SBACKUP cannot read the list of devices available from the storage device interface (SDI).Action: Make sure that the SDI module is loaded and that the storage devices are operating properly. (The SDI module should have been loaded by SBACKUP.) If the problem persists, contact your Novell Authorized Reseller.232: An error occurred during SBACKUP's attempt to open a session: session_name.SBACKUPExplanation: SBACKUP cannot find or cannot read the specified session on the selected media.Action: Select a media that resides in the device you selected. Make sure the user has appropriate user access rights for the requested session.PAGENUM=944 ID="BP938"235: An error occurred during SBACKUP's attempt to get the list of media: SDI_message.SBACKUPExplanation: SBACKUP cannot read a list of available media from the storage device interface (SDI).Action: Make sure the media is loaded in the selected device and that the device is operating correctly. Make sure the user has appropriate user access rights to the media and device.249: The server is out of memory.SBACKUPExplanation: SBACKUP cannot access enough memory to allocate memory from the dynamic memory pool in the server. The backup process cannot continue.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.250: SBACKUP cannot get a buffer for data transfer.SBACKUPExplanation: SBACKUP cannot access enough dynamic memory from the server to complete data transfer; SBACKUP will terminate.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.257: Media cannot be identified.SBACKUPExplanation: The media does not have a readable label. It may be unlabeled.Action: Make sure the media does not contain data that you want to keep. If you continue, SBACKUP will relabel the media and write over any data.261: The Storage Device Interface connection has become invalid.SBACKUPExplanation: SBACKUP has lost its communication connection to the storage device interface (SDI).Action: Check the communication link between servers; then reload SBACKUP and SDI. (SDI should be loaded automatically by SBACKUP.)265: This device cannot be selected: SDI_message.SBACKUPExplanation: The storage device interface (SDI) could not reserve the requested device.Action: Make sure that the device is not already being used. Make sure the user has appropriate user access rights to the device. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=945 ID="BP939"266: A previously selected device cannot be freed: SDI_message.SBACKUPExplanation: The storage device interface (SDI) could not release the requested device.Action: Make sure that the selected device has no pending or uncompleted requests and that the selected device was not previously reserved. If the problem persists, contact your Novell Authorized Reseller.274: File name could not be restored completely, and may be corrupted.SBACKUPExplanation: SBACKUP ran out of disk space while restoring this file, so only part of the file was restored and it may be corrupted or incomplete.Action: Examine the file. Delete it and other files that are corrupted or incomplete. Increase the available disk space on the volume. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Disk Space Problems" in Supervising the Network. Repeat the restore session.278: Volume name does not exist.SBACKUPExplanation: SBACKUP has received a volume name that is not on the specified target.Action: Make sure the specified volume exists. Make sure the volume name was typed correctly.280: Error code occurred during SBACKUP's attempt to create a portal.SBACKUPExplanation: SBACKUP cannot create the requested portion of the user screen. The backup process cannot continue.Explanation: Increase the available memory. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 283: Error code has occurred.SBACKUPExplanation: SBACKUP has encountered an unspecified error.Action: For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.284: SBACKUP cannot write a label to the media: SDI_message.SBACKUPExplanation: The storage device interface (SDI) could not write the requested label on the selected media.Action: Make sure the user has appropriate user access rights to the selected media. Make sure that the media was not previously labeled.PAGENUM=946 ID="BP940"329: An invalid option was specified. Buffers = number_of_buffers.SBACKUPExplanation: SBACKUP found an invalid command line specification for the number of buffers to use for this session.Action: Replace the invalid option with a valid option. Retry the command. For more information, see "BOOK="superenu" COLLECTION="nw41"Backing Up and Restoring Data" in Supervising the Network.330: An invalid option was specified. Size = buffer_size.SBACKUPExplanation: SBACKUP found an invalid command line specification for the size of data buffers to use for this session.Action: Replace the invalid option with a valid option. Retry the command. For more information, see "BOOK="superenu" COLLECTION="nw41"Backing Up and Restoring Data" in Supervising the Network.369: The program cannot connect to a Target Service Agent: message.SBACKUPExplanation: SBACKUP cannot connect to the requested target service agent (TSA).Action: Make sure that the TSA name is correct and that it is loaded on the server. Make sure the user has appropriate user access rights to the specified TSA.370: The program cannot connect to a target service: message.SBACKUPExplanation: SBACKUP cannot connect to the requested target service.Action: Make sure that the target service is available. Make sure the user has appropriate user access rights to the target service agent.474: SBACKUP cannot list the target services: message.SBACKUPExplanation: SBACKUP cannot find any available target service agents (TSAs). TSAs may not be loaded, or the link between the two nodes may be broken.Action: Load the necessary TSAs. Make sure the LAN communication is working between nodes.520: SBACKUP cannot put the first name in the data set name: message.SBACKUPExplanation: SBACKUP cannot begin a data set (probably a file or directory) name list with the requested name. The server may not have enough available memory.Action: Make sure that the data set name exists and is valid for the specified name space. Increase the available memory. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.PAGENUM=947 ID="BP941"522: SBACKUP cannot build a selection list. Error code: code.SBACKUPExplanation: SBACKUP cannot build a data set (probably a file or directory) selection list. The server may not have enough available memory.Action: Increase the available memory. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 523: An error occurred during SBACKUP's attempt to get one name: message.SBACKUPExplanation: SBACKUP expected to read a data set name from the media and failed. The media may be damaged, or the device may be malfunctioning.Action: Make sure the media is not damaged. Then restart the session and make sure that the device is operating correctly.531: An error occurred during SBACKUP's attempt to get a record header: message.SBACKUPExplanation: SBACKUP expected to read a record header from the media and failed. The media may be damaged, or the device may be malfunctioning.Action: Make sure the media is not damaged. Then restart the session and make sure that the device is operating correctly.532: SBACKUP cannot start a data set scan: message.SBACKUPExplanation: SBACKUP cannot find any data sets that match those specified.Action: Check the "scan begin" criteria for valid syntax and format.533: SBACKUP cannot open the data set for backup: message.SBACKUPExplanation: SBACKUP cannot open the requested data set (probably a file or directory) for backup (read mode). The data set may be locked by another application, or be flagged Execute Only. The user may not have the appropriate user access rights.Action: Check the data set's flags. Make sure the user has appropriate user access rights. Make sure the file is not in exclusive use by another process. Try again.534: SBACKUP cannot write the transfer buffer to the media. Error code: code.SBACKUPExplanation: The storage device interface (SDI) could not write the transfer buffer to the selected media. The media or storage device may not be functioning properly.Action: Make sure that the media and storage device are operating correctly. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. PAGENUM=948 ID="BP942"535: SBACKUP cannot set the archive status: message.SBACKUPExplanation: SBACKUP cannot set (or reset) the Archive status flag on the data set just processed.Action: None. This message is for information only. The Archive status will be left as is; the status was probably set to indicate that the file has been modified.536: SBACKUP cannot close data set: message.SBACKUPExplanation: SBACKUP could not close the data set (probably a file or directory) just processed.Action: Make sure the user has appropriate user access rights. Check the file attributes for the data set.537: SBACKUP cannot scan the next data set: message.SBACKUPExplanation: SBACKUP could not read the scan information for the requested data set (probably a file or directory).Action: Make sure the user has appropriate user access rights. Check the file attributes for the data set. Make sure the file is not in exclusive use by another process.539: SBACKUP cannot open the data set for restore: message.SBACKUPExplanation: This error could have a variety of causes.Action: Make sure that the desired "Overwrite" option is selected and the data set is not in use. Make sure the user has appropriate user access rights. Check the attributes for the data set. For more information, see "BOOK="superenu" COLLECTION="nw41"Backing Up and Restoring Data" in Supervising the Network.542: SBACKUP cannot write the data set: message.SBACKUPExplanation: SBACKUP could not write the requested data set.Action: Make sure the user has appropriate user access rights. Make sure the data set is not already in use.PAGENUM=949 ID="BP943"SCSI154X.HAM001: Failure attempting to parse and validate hardware options. Verify proper switch settings on adapter board.SCSI154X.HAMExplanation: The HAM driver did not load because the specified hardware resources (port, interrupt, DMA values) did not correspond with the settings of the host adapter.Action: Set the switches on the adapter board to their proper settings; then reload the HAM driver.002: All possible Adapter ports currently in use.SCSI154X.HAMExplanation: The load instance failed because all ports on the adapter are in use.Action: None. This message is for information only.003: This driver only supports boards in an ISA or EISA Bus.SCSI154X.HAMExplanation: The HAM driver did not load because the hardware bus type of the server is incompatible with the bus type that the driver was designed to support. The SCSI154X.HAM Host Adapter Module supports SCSI controller cards designed to work on ISA/EISA machines.Action: Use a controller card and compatible HAM driver appropriate for the server's I/O bus.004: Allocate Memory Below 16 Meg Failed. Use: `set reserved buffers below 16 meg = XX' to increase number of buffers.SCSI154X.HAMExplanation: The load of the driver failed because the server could not give the HAM driver below 16 meg memory to create the objects necessary to support the controller and attached devices.Action: If the maximum has not already been specified, increase the value specified for the Reserved Buffers Below 16 Meg parameter in the STARTUP.NCF file.005: Adapter failed to initialize.SCSI154X.HAMExplanation: The load instance failed because the host adapter hardware did not initialize.Action: Verify that the adapter board settings are correct, then reload the HAM driver. If the adapter continues to fail initialization, you may need a new board.PAGENUM=950 ID="BP944"006: HAI_Activate_Bus() returned code.SCSI154X.HAMExplanation: The load instance failed because channel registration with the server failed.Action: Unload any unnecessary .CDM and .HAM drivers, then reload this .HAM driver.007: NPA_Spawn_Thread() returned code.SCSI154X.HAMExplanation: The load instance failed because the asynchronous threads necessary for proper operation could not be scheduled.Action: Unload any unnecessary NLM programs, then reload this .HAM driver.PAGENUM=951 ID="BP945"SCSI2TP.CDM001: WARNING! Driver has not been tested with [DEVICE_NAME]. The driver has bound to the device to provide Generic support. Contact the device manufacturer for a full-functioned driver.SCSI2TP.CDMExplanation: The device has not been tested with this driver by Novell. The driver will attempt to treat the device in a generic fashion. Users are responsible for all testing to ensure that the device and driver work properly with whatever applications rely on them. Action: Contact the device manufacturer for a certified device driver.  003: WARNING! Driver does not support [DEVICE_NAME]; therefore, driver did not bind to device. Contact the device manufacturer for a full-function driver.SCSI2TP.CDMExplanation: The driver recognizes this device as a known device that it cannot support.Action: Contact the device manufacturer for a certified device driver.PAGENUM=952 ID="BP946"SCSICD.CDM001: WARNING! This driver has not been tested with devicename; however, the driver has bound to the device to provide generic support. Contact the device manufacturer for a full-function driver.SCSICD.CDMExplanation: The device is not one that the driver fully supports, nor is it a device that the driver excludes. Therefore, the driver has bound to the device to support the generic (basic) functionality typical of the device class type.Action: The best action is to contact the manufacturer and get a driver that fully supports the device.However, barring idiosyncrasies of the device, this generic driver may support the device just fine. The choice to use the driver is yours, but until you feel comfortable that this driver supports the device adequately, do not use it to store critical data.002: WARNING! Driver has not been tested with devicename; therefore, driver did not bind to device. To invoke generic support, unload the driver and then reload it with the appropriate command line parameter. See INSTALL Driver Options for a list of these parameters and their descriptions.SCSICD.CDMExplanation: This condition is similar to that of message 001, except that the driver chose not to bind generically to the device. Possibly, all that is needed for generic support is some general configuration information about the device.Action: The best action is to contact the manufacturer and get a driver that fully supports the device.However, barring idiosyncrasies of the device, this generic driver may support the device just fine. The choice to use the driver is yours, but until you feel comfortable that this driver supports the device adequately, do not use it to store critical data.You may invoke generic support and provide the necessary information by unloading this driver then reloading it with each appropriate command-line parameter. For a list of these parameters and their respective descriptions, read the driver's .DDI file or select the driver under the INSTALL utility's Driver Options menu.003: WARNING! Driver does not support devicename; therefore, driver did not bind to device. Contact the device manufacturer for a full-function driver.SCSICD.CDMExplanation: The driver recognizes this device and knows that it cannot support the device, not even generically.Action: Contact the device manufacturer to get the appropriate driver.PAGENUM=953 ID="BP947"SCSIHD.CDM001: WARNING! This driver has not been tested with devicename; however, the driver has bound to the device to provide generic support. Contact the device manufacturer for a full-function driver.SCSIHD.CDMExplanation: The device is not one that the driver fully supports, nor is it a device that the driver excludes. Therefore, the driver has bound to the device to support the generic (basic) functionality typical of the device class type.Action: The best action is to contact the manufacturer and get a driver that fully supports the device.However, barring idiosyncrasies of the device, this generic driver may support the device just fine. The choice to use the driver is yours, but until you feel comfortable that this driver supports the device adequately, do not use it to store critical data.002: WARNING! Driver has not been tested with devicename; therefore, driver did not bind to device. To invoke generic support, unload the driver and then reload it with the appropriate command line parameter. See INSTALL Driver Options for a list of these parameters and their descriptions.SCSIHD.CDMExplanation: This condition is similar to that of message 001, except that the driver chose not to bind generically to the device. Possibly, all that is needed for generic support is some general configuration information about the device.Action: The best action is to contact the manufacturer and get a driver that fully supports the device.However, barring idiosyncrasies of the device, this generic driver may support the device just fine. The choice to use the driver is yours, but until you feel comfortable that this driver supports the device adequately, do not use it to store critical data.You may invoke generic support and provide the necessary information by unloading this driver then reloading it with each appropriate command-line parameter. For a list of these parameters and their respective descriptions, read the driver's .DDI file or select the driver under the INSTALL utility's Driver Options menu.003: WARNING! Driver does not support devicename; therefore, driver did not bind to device. Contact the device manufacturer for a full-function driver.SCSIHD.CDMExplanation: The driver recognizes this device as a known device that it cannot support, not even generically.Action: Contact the device manufacturer to get the appropriate driver.PAGENUM=954 ID="BP948"SCSIMO.CDM001: WARNING! This driver has not been tested with devicename; however, the driver has bound to the device to provide generic support. Contact the device manufacturer for a full-function driver.SCSIMO.CDMExplanation: The device is not one that the driver fully supports, nor is it a device that the driver excludes. Therefore, the driver has bound to the device to support the generic (basic) functionality typical of the device class type.Action: The best action is to contact the manufacturer and get a driver that fully supports the device.However, barring idiosyncrasies of the device, this generic driver may support the device just fine. The choice to use the driver is yours, but until you feel comfortable that this driver supports the device adequately, do not use it to store critical data.002: WARNING! Driver has not been tested with devicename; therefore, driver did not bind to device. To invoke generic support, unload the driver and then reload it with the appropriate command line parameter. See INSTALL Driver Options for a list of these parameters and their descriptions.SCSIMO.CDMExplanation: This condition is similar to that of message 001, except that the driver chose not to bind generically to the device. Possibly, all that is needed for generic support is some general configuration information about the device. Action: The best action is to contact the manufacturer and get a driver that fully supports the device.However, barring idiosyncrasies of the device, this generic driver may support the device just fine. The choice to use the driver is yours, but until you feel comfortable that this driver supports the device adequately, do not use it to store critical data.You may invoke generic support and provide the necessary information by unloading this driver then reloading it with each appropriate command-line parameter. For a list of these parameters and their respective descriptions, read the driver's .DDI file or select the driver under the INSTALL utility's Driver Options menu.003: WARNING! Driver does not support devicename; therefore, driver did not bind to device. Contact the device manufacturer for a full-function driver.SCSIMO.CDMExplanation: The driver recognizes this device and knows that it cannot support the device, not even generically.Action: Contact the device manufacturer to get the appropriate driver.PAGENUM=955 ID="BP949"SCSIPS2.HAM001: Selected IBM SCSI Adapter is Enabled.SCSIPS2.HAMExplanation: The driver was successfully loaded for the selected SCSI adapter.Action: None. This message is for information only.002: Selected IBM SCSI Adapter with Cache is Enabled.SCSIPS2.HAMExplanation: The driver was successfully loaded for the selected SCSI adapter. Cache was detected for this adapter.Action: None. This message is for information only.003: System Board IBM SCSI Support Enabled.SCSIPS2.HAMExplanation: The driver was successfully loaded for the selected SCSI adapter. This adapter is a built-in adapter on the system board.Action: None. This message is for information only.100: Could NOT register this module with NPA.SCSIPS2.HAMExplanation: The driver was unable to register with NWPA.NLM. Possible causes for the error may be that incompatible versions of NWPA.NLM and the driver were used or that the server is out of memory.Action: Make sure the versions of the SCSIPS2.HAM and NWPA.NLM used are compatible. For server memory problems, see "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.101: Incorrect BUS type for this HAM.SCSIPS2.HAMExplanation: The driver was loaded on a computer system that does not have a Micro Channel (MCA) bus. This driver is only for IBM Micro Channel SCSI adapters.Action: Use a different driver that is appropriate for the adapter installed.102: Exceeded Card Structures Limit.SCSIPS2.HAMExplanation: The driver is being loaded for too many adapters. This driver can control up to eight adapters and is currently being loaded for a ninth adapter.Action: Restrict a server to eight SCSI adapters.PAGENUM=956 ID="BP950"103: NPA Parse Options has failed.SCSIPS2.HAMExplanation: An error occurred while trying to parse the command-line parameters. Possible causes for the error may be that a command-line string that is too long was entered, or parameters that are too long or invalid were entered.Action: Retry loading the driver again with valid command line parameters that consist of SLOT=(slot number of adapter), /host, /SG=(0 or 1), /NWDIAG.104: Registered Option has been rejected.SCSIPS2.HAMExplanation: A conflict with the hardware options associated with the adapter exists. The operating system could not register the hardware options (that is, interrupts) associated with the adapter, or another adapter has already registered the same options.Action: Make sure a SCSI adapter is installed into the slot specified. If the adapter is installed in the specified slot, rerun the system configuration from the Reference Diskette included with the system to make sure it is a valid configuration without a conflict.105: Selected Slot does not contain the IBM SCSI Adapter Card.SCSIPS2.HAMExplanation: The slot number specified in the SLOT= parameter does not contain an IBM SCSI adapter. The wrong slot may have been selected.Action: The easiest way to select a valid slot is to load the driver without the slot number specified. The driver will automatically scan the bus and report the slots that contain IBM SCSI adapters. Select a slot from the list displayed.106: Unable to get memory for HAM structure.SCSIPS2.HAMExplanation: The server does not have enough memory for the driver to initialize.Action: To solve server memory problems, see "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.107: Unable to get memory for local device.SCSIPS2.HAMExplanation: The server does not have enough memory for the driver to initialize data for the devices attached to the adapter.Action: For server memory problems, see "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.108: Unable to get memory for local media buffer.SCSIPS2.HAMExplanation: The server does not have enough memory for the driver to allocate data buffers for the devices attached to the adapter.Action: To solve server memory problems, see "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.PAGENUM=957 ID="BP951"109: Could NOT register the HAM.SCSIPS2.HAMExplanation: The driver was unable to finalize registration with NWPA.NLM. Possible causes for the error may be that incompatible versions of NWPA.NLM and the driver were used or that the server is out of memory.Action: Verify versions of SCSIPS2.HA and NWPA.NLM. For server memory problems, see "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.110: Failed to replace HAM.SCSIPS2.HAMExplanation: An attempt to "Hot Swap" the driver with a new driver failed. Hot Swap is defined as loading a new driver to replace a functioning driver without bringing down the server or dismounting the volumes. In this case, the new driver did not properly exchange information with the functioning driver.Action: Make sure the new module is designed to hot swap with SCSIPS2.HAM. Drivers are written to hot swap only with certain other drivers.111: No more Slot options found.SCSIPS2.HAMExplanation: The driver is being loaded more times than there are adapters installed. The driver is indicating that no more slots are found which contain an IBM Micro Channel SCSI adapter.Action: If an IBM Micro Channel SCSI adapter is installed but not recognized by the driver, rerun the computer's configuration to allow the adapter to be recognized by the driver. 112: A Software Sequencing Error was detected.SCSIPS2.HAMExplanation: An error occurred in the driver that caused too many commands to be sent to the adapter. This may apply to certain adapters with an old revision of firmware.Action: Report this error to your Novell Authorized Reseller indicating the adapter used including type, revision, and firmware date (date printed on the label of the large Integrated Components).PAGENUM=958 ID="BP952"SECURITY1: The message file name is invalid. The program cannot be loaded.SECURITYExplanation: The .MSG file is invalid. This problem could be the result of a corrupted file, a bad translation, or an outdated file version.Action: Update the .MSG file with a valid copy, or delete the file. The DOS Requester will use the default messages that are bound to the binary files.5: Module1.VLM is not loaded. The module2.VLM file cannot be loaded before module1.VLM. Load the module1.VLM file first then try to load the module2.VLM file.SECURITYExplanation: The module2.VLM requires that the module1.VLM be loaded first. The current configuration has module1.VLM and module2.VLM loading out of order, or module1.VLM did not load successfully.Action: Make sure that module1.VLM is configured to load before module2.VLM. To do this, change the load order of the "VLM=" parameter in the NET.CFG file.7: In order to load the module3.VLM, one of the following VLMs must be loaded: module1.VLM, module2.VLM.SECURITYExplanation: The module3.VLM requires that module1.VLM or module2.VLM be loaded first. The current configuration has module3.VLM loading before the modules in the module1.VLM or module2.VLM list, or module1.VLM or module2.VLM did not load successfully.Action: Make sure that module1.VLM or module2.VLM load successfully before loading module3.VLM.42: There is a missing or invalid value for `parameter' on line number of the configuration file. This entry will be ignored. Correct the line specified in the configuration file before continuing.SECURITYExplanation: The configuration file contains a configuration keyword that has an invalid parameter, or that does not specify a parameter. This invalid line will be ignored by the configuration process.Action: None. This message is for information only. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message.PAGENUM=959 ID="BP953"43: There is a missing or invalid ON/OFF value for `parameter' on line number of the configuration file. This entry will be ignored. Correct the line specified in the configuration file before continuing.SECURITYExplanation: The configuration file contains a configuration keyword that is defined to use an "ON" or "OFF" parameter, but a different parameter, or no parameter, or () has been specified. This invalid line will be ignored by the configuration process.Action: None. This message is for information only. However, to avoid this message the next time VLM.EXE is loaded, delete or correct the line specified by the error message.45: The parameter specified for the following option was out of range and has been adjusted.SECURITYExplanation: A configurable parameter has been configured too high or too low to be valid. The invalid parameter is specified on the line following the message.Action: Check and correct the parameter specified in the NET.CFG file. For more information about the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.Action: 67: The SECURITY.VLM file must be loaded before any other NetWare Protocol Module. The SECURITY.VLM file will not be loaded. Load the SECURITY.VLM file before loading any NetWare Protocol Modules.SECURITYExplanation: This message is only a warning. The DOS Requester will function properly without the use of NCP authentication. The SECURITY.VLM file must be loaded before any NetWare Protocol Modules (such as BIND.VLM or NDS.VLM) to function properly.Action: If authentication is desired, load the SECURITY.VLM after TRAN.VLM and before any NetWare Protocol Module (such as BIND.VLM or NDS.VLM); then set the "SIGNATURE LEVEL=" parameter in the NET.CFG file. If NCP authentication is not desired, set "SIGNATURE LEVEL=0" in the NET.CFG file. For more information about the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.PAGENUM=960 ID="BP954"SEND010: This utility cannot determine the broadcasting mode on connection number. Error code: code.SENDExplanation: The status of the workstation mode using the connection number shown in the message cannot be obtained. The last mode you were in may or may not be the current mode.Action: Using the correct command syntax, try to set the desired mode. If you do not receive an error message, the mode has been changed to match the request. For more information, see "BOOK="utlrfenu" COLLECTION="nw41"SEND" in Utilities Reference. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 020: This utility does not recognize the broadcast mode number set for this workstation on connection number. This workstation may or may not receive incoming messages.SENDExplanation: The status of the workstation mode cannot be obtained. The last mode you were in may or may not be the current mode.Action: Using the correct command syntax, try to set the desired mode. If you do not receive an error message, the mode has been changed to match the request. For more information, see "BOOK="utlrfenu" COLLECTION="nw41"SEND" in Utilities Reference. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 030: Your connection (number number) is invalid. The program cannot poll the server to retrieve messages that may be stored for this workstation. Error code: code.SENDExplanation: In poll mode, the server keeps one message for a user. If the server does not recognize the connection number of the user's workstation, it cannot identify the user for that connection. This message may be logged for this user at the server.Action: Try to switch the mode to /A=A.Warning: Rebooting the workstation will probably result in losing the message that was stored.If necessary, reboot the workstation. For more information, see "BOOK="utlrfenu" COLLECTION="nw41"SEND" in Utilities Reference. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. PAGENUM=961 ID="BP955"031: A workstation error (code) has occurred on connection code. The program cannot poll the server to retrieve potentially stored messages for this workstation.SENDExplanation: In poll mode, the server keeps one message for a user. If the server does not recognize the connection number of the user's workstation, it cannot identify the user for that connection. This message may be logged for this user at the server.Action: Try to switch the mode to /A=A.Warning: Rebooting the workstation will probably result in losing the message that was stored.If necessary, reboot the workstation. For more information, see "BOOK="utlrfenu" COLLECTION="nw41"SEND" in Utilities Reference. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 032: A shell or requester error (code) has occurred on connection number. The program cannot poll the server to retrieve potentially stored messages for this workstation.SENDExplanation: The shell keeps the broadcasting mode of the workstation and interfaces with the server to arbitrate how to handle messages. If the server does not communicate properly with this workstation, or if it is experiencing hardware problems, the workstation may not be able to request messages because the server may not receive or handle the request.Action: Try rebooting the workstation. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.033: A NetWare error (code) has occurred on connection number: The program cannot poll the server to retrieve potentially stored messages for this workstation.SENDExplanation: The shell keeps the broadcasting mode of the workstation and interfaces with the server to arbitrate how to handle messages. If the server does not communicate properly with this workstation, or if it is experiencing hardware problems, the workstation may not be able to request messages because the server may not receive or handle the request.Action: Reboot if you think it is a workstation problem. Make sure that the server is up and running properly. Then try again. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.034: An unknown polling error (code) has occurred on connection number. The program cannot poll the server to retrieve potentially stored messages for this workstation.SENDPAGENUM=962 ID="BP956"Explanation: An unidentified element in the chain failed to respond to the request. The problem could have a variety of causes: low-level drivers may be malfunctioning, this utility might be corrupted, or cabling to the server (or servers, if routers are used) could be faulty.Action: Try rebooting the computer. See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.035: Your connection number is invalid. This message cannot be sent to user name through message server name.SENDExplanation: To send a synchronous message to a user, the workstation must have a valid connection to the server on which the recipient of the message resides.Action: Reestablish a connection for that server by attaching or logging in again.036: Your connection number is invalid. This message cannot be sent to user name on connection number.SENDExplanation: To send a synchronous message to a user, the workstation must have a valid connection to the server on which the recipient of the message resides.Action: Reestablish a connection for that server by attaching or logging in again.040: A workstation error has occurred (error code: code). Your message was not sent to user name.SENDExplanation: An error coming from a module loaded on the workstation prevents SEND from performing its function.Action: Check drivers, TSRs, shells, or requesters. If necessary, reboot the workstation. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller or the vendor for the software causing the problem.100: An unknown error has occurred. To get help, type: SEND /?SENDExplanation: This error message appears when a problem occurs that the program cannot identify. Potential problems range from a system error to a typing error.Action: Use the correct syntax. To verify the syntax, type "SEND /?" on the command line or see "BOOK="utlrfenu" COLLECTION="nw41"SEND" in Utilities Reference. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=963 ID="BP957"101: An unknown error occurred when this utility sent a broadcast to user name. Error code: code.SENDExplanation: The reason for this error is unknown.Action: Try to reboot. Make sure that the cabling is working, and that the server is responding as expected. See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.102: An unknown error occurred when this utility sent a broadcast to user name. Error code: code.SENDExplanation: The reason for this error is unknown.Action: Try to reboot. Make sure that the cabling is working, and that the server is responding as expected. See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.105: This utility cannot allocate enough memory for internal tables.SENDExplanation: The workstation does not have enough memory to run the utility as requested.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network.110: This utility's attempt to add a filter token failed. Error code: code.SENDExplanation: This is a NetWare Directory Services error. The workstation may not have enough available memory. The user may lack proper rights in the directory to perform this action.Explanation: If the problem is workstation memory, see "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A.120: A search error has occurred. Information on properties of group objects cannot be found.SENDExplanation: This is a NetWare Directory Services error. The user does not have rights to look at the properties of group objects. Specifically, the user does not have access to the message server property, so it cannot send to an object in a group.Action: Make sure the user has appropriate user access rights. Use NETADMIN or NetWare Administrator to change the rights so that the user is allowed to examine the message server property. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. PAGENUM=964 ID="BP958"125: This utility cannot create a Directory Services context.SENDExplanation: To send the message to the directory object you specified, SEND must have a NetWare Directory Services context, but it cannot create one.Action: Make sure that you have loaded the proper NetWare Directory Services NETX, VLM, and REDIR files. Make sure the NET.CFG file has a default context set.130: This utility cannot get the syntax ID for Directory Services context context. Error code: code.SENDExplanation: To parse an object, such as the context, you need to know what particular syntax the object is made of. The call to get this syntax failed, so you cannot continue sending.Action: The Directory database may have been tampered with, or the replica you are using may be corrupted. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 135: This utility cannot process object name from group name.SENDExplanation: One of the objects for the specified group cannot be processed. That object may no longer exist (this might occur if a user is deleted from a server), or it might have been renamed.Action: Update the group membership to reflect current objects.140: This utility cannot read object information for object name.SENDExplanation: This is a NetWare Directory Services error. The following are possible causes:MARK=BULLETThe user did not set the proper NetWare Directory Services context.The user lacks proper rights to read the property information for the object.The object property field is empty.Action: Do some or all of the following:MARK=BULLETUsing the CX utility, make sure the current context is in the proper location of the Directory tree so that the object is visible. For more information, see "BOOK="utlrfenu" COLLECTION="nw41"CX" in Utilities Reference.Use NETADMIN or the NetWare Administrator to grant the user access to this object. For more information on these utilities, see 
BOOK="utlrfenu" COLLECTION="nw41"Utilities Reference.Make sure that the message server property contains a valid value.PAGENUM=965 ID="BP959"For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 145: This utility cannot submit a filter buffer created to receive information on a group object. Error code: code.SENDExplanation: This is a NetWare Directory Services error. An internal recipient buffer cannot be handed back to NetWare Directory Services to receive the requested property information.Action: For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.150: A buffer initialization error has occurred.SENDExplanation: This is a NetWare Directory Services error. Before using internal buffers to pass information back and forth between the Directory base and the client workstation, NetWare Directory Services requires that those buffers be properly initialized. This error might have occurred because insufficient memory was allocated to the buffer, and the buffer is full.Action: For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.155: Your message cannot be sent. Make sure user name has a defined default server.SENDExplanation: The message server property was not filled when the user was created.Action: Make sure that the message server property contains a valid server object name for each object you want to send a message to.165: The following context either is invalid or does not exist: "name."SENDExplanation: The CX utility tried to change the context of a given object. CX was unable to find the object in the given context, or it was unable to create the path in the Directory tree. This error also can occur if an error has occurred in the program. CX has terminated.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.170: This utility cannot get connection numbers for user server/user.SENDExplanation: The user is not logged in, or the server is malfunctioning.Action: Make sure that the user is logged in. Check for hardware problems. See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.PAGENUM=966 ID="BP960"201: A NetWare error has occurred (error code: code). Your message cannot be sent to user server/user on connection number.SENDExplanation: The SEND utility cannot identify the nature of the error.Action: Try to reboot. Make sure that the cabling is working and that the server is responding as expected. This might be a hardware problem. See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.203: A shell or requester error has occurred (error code: code). Your message cannot be sent to user server/user on connection number.SENDExplanation: Without a properly working shell or requester, messaging does not occur.Action: Unload, then reload the current shell or requester. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 206: A workstation error has occurred (error code: code). Your message was not sent to user server/user on connection number.SENDExplanation: The SEND utility has identified an error originating at the workstation.Action: Try to reboot, and make sure that the cabling is working. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 300: This utility cannot set the receive message mode. Error code: code.SENDExplanation: The SEND utility cannot set the message mode to ALL, CONSOLE, or NONE.Action: Reboot the computer and try again. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.310: An invalid number of parameters was specified. To get help, type: SEND /?SENDExplanation: You omitted one or more parameters necessary to send the message.Action: Type "SEND /? MOREINFO="NONE"<Enter>" to display a help screen, or see "BOOK="utlrfenu" COLLECTION="nw41"SEND" in Utilities Reference for more information about the proper syntax. 400: The server name cannot be found.SENDExplanation: You selected a server/console, a server/user, or a server/group combination, but no such server combination can be located. One of the following probably occurred:MARK=BULLETThe server is down or no longer exists.PAGENUM=967 ID="BP961"The server has been renamed.A cabling or routing problem exists.Action: Determine the status of the server.410: This utility cannot get log information from server name. Error code: code.SENDExplanation: SEND cannot locate the list of all users who are logged in to the specified server and who can, therefore, receive messages. The server may be down (or going down). The workstation may not have enough available memory. The network may have a cabling or routing problem.Action: Try one or more of the following:MARK=BULLETReboot the workstation.Check the cable connections. See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.Make sure the connection to the server does not have a defective router or bridge.Increase the available memory. See "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network.Bring down the server and reboot.For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 420: Your message cannot be sent because the server did not allocate space for this message.SENDExplanation: The server maintains a user table with a buffer for one incoming message for each user. The server might be out of space or, its memory might have been corrupted.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.441: Server name does not have a station number.SENDExplanation: You sent a message using a connection address that is not recorded in the server connection list.Action: Do one of the following:MARK=BULLETSend the message using the username.PAGENUM=968 ID="BP962"Run NLIST to identify the connections associated with this user on that server, and select the desired ones; then resend the message.442: Server name cannot be found.SENDExplanation: One of the following might have caused this error:MARK=BULLETThe server is down or no longer in service.The server has been renamed.The server is experiencing hardware problems. See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.There might be cabling or routing problems.Action: Make sure the server is operating and available on the network. Check the cabling and routing.443: You cannot attach to default server name.SENDExplanation: The user does not have rights to the message server property, so it cannot send a message to a user.Action: Give the user rights to the message server property.500: Your message was NOT sent to user name.SENDExplanation: The server did not receive an acknowledgment that the destination workstation received the message. The destination workstation may be in "CASTOFF" broadcasting mode.Action: Tell the intended recipient to set the broadcasting mode to "CASTON."505: User name cannot be found.SENDExplanation: The requested user is not on the server.Action: Check the spelling of the username.506: The specified user on this connection is unknown to Directory Services. Error code: code.SENDExplanation: The workstation may have a bindery connection to this NetWare Directory Services server.Action: Use the /B option to emulate bindery send. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. PAGENUM=969 ID="BP963"515: This utility cannot get the user object ID for user name. No message will be sent to this user. Error code: code.SENDExplanation: This is a NetWare Directory Services error. The user object ID represents the user within the directory base. For some reason, the utility cannot access the object ID.Action: For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 516: Directory Services error code occurred. This utility cannot get information on user name.SENDExplanation: The SEND utility cannot get information about the message recipient's default server.Action: Make sure that the recipient has a default server value, and that the rights to this field are public. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 520: A connection number cannot be found for user name.SENDExplanation: The requested user does not have a current connection to a host server or message server. You cannot send a message to a user who is not logged in.Action: Try again later when the user is logged in.525: This utility cannot determine the maximum number of supported connections for default server name. Error code: code.SENDExplanation: This is a NetWare Directory Services error. The SEND utility determines the maximum number of connections supported by the server indicated in the message.Action: Reboot and check the routing. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 530: This utility cannot get connection information for user name, who is connected to message server name through connection number. Error code: code.SENDExplanation: This is a NetWare Directory Services error. The SEND utility cannot get the list of all the connections to the message server for the specified user.Action: For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. PAGENUM=970 ID="BP964"531: This utility is unable to get the server name for connection number. Error code: code.SENDExplanation: The SEND utility cannot get the name of the default server on which the message recipient receives broadcasts. If the workstation cannot get the server name, it cannot access that server, so a message cannot be sent.Action: Make sure that the user's default server is in the Directory tree, and that the default server is running; then try again. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 535: You cannot attach to message server name. Error code: code.SENDExplanation: To send a message to a user, the user must be attached to the user's host message server. The user does not have rights to attach to that server, or it cannot reach that server.Action: Check the network cabling, routing, or bridges. Make sure the user has appropriate user access rights to the message server. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 899: This utility cannot initialize NWCALLS.SENDExplanation: NWCALLS, a Novell internal library of function calls, cannot be found.Action: Make sure that the workstation has a search drive mapped to NWCALLS. If the problem persists, contact your Novell Authorized Reseller.901: You are not attached to server name.SENDAction: See message IDREF="FM84261""901: You are not attached to the specified server." in Appendix C.903: The command line syntax is invalid.SENDAction: See message IDREF="FM18860""903: The command line syntax is invalid." in Appendix C.917: This utility was unable to set the context.SENDAction: See message IDREF="FM32126""917: This utility was unable to set the context." in Appendix C.918: This utility was unable to get connection information. The message may not have been sent. Error code: code.SENDAction: See message IDREF="FM25772""918: This utility was unable to get connection information. Error code: code." in Appendix C.920: This utility was unable to allocate <number> bytes of memory.SENDAction: See message IDREF="FM30331""920: This utility was unable to allocate number bytes of memory." in Appendix C.PAGENUM=971 ID="BP965"921: Either the supervisor has locked the bindery or volume SYS: is not mounted.SENDAction: See message IDREF="FM49837""921: Either the supervisor has locked the bindery or volume SYS: is not mounted." in Appendix C.925: The server specified is a Personal NetWare server. You cannot attach to a Personal NetWare server with this utility. Use the Personal NetWare utilities to access this connection.SENDAction: See message IDREF="FM67645""925: The server specified is a Personal NetWare server. You cannot attach to a Personal NetWare server with this utility. Use the Personal NetWare utilities to access this connection." in Appendix C.970: The attempt to open the Unicode table files failed.SENDAction: See message IDREF="FM15675""970: The attempt to open the Unicode table files failed." in Appendix C.971: The workstation does not have enough memory to load the Unicode table files.SENDAction: See message IDREF="FM55341""971: The workstation does not have enough memory to load the Unicode table files." in Appendix C.972: Access to the Unicode table files was denied.SENDAction: See message IDREF="FM90152""972: Access to the Unicode table files was denied." in Appendix C.973: The Unicode table files cannot be found in the NLS directory or in the search path. Code page: <number>  Country:  <number>SENDAction: See message IDREF="FM62778""973: The Unicode table files cannot be found in the NLS directory or in the search path. Code page: number Country: number" in Appendix C.974: The Unicode table files are corrupt.SENDAction: See message IDREF="FM63405""974: The Unicode table files are corrupt." in Appendix C.975: The Unicode table files cannot be opened because there are already too many open files. Close some files or modify your CONFIG.SYS file.SENDAction: See message IDREF="FM49793""975: The Unicode table files cannot be opened because there are already too many open files. Close some files or modify your CONFIG.SYS file." in Appendix C.PAGENUM=972 ID="BP966"998: The message file found (<utility_name>.MSG) is an incorrect version. The correct version is <number>. See your network supervisor for assistance.SENDAction: See message IDREF="FM91957""998: The message file found (utility_name.MSG) is an incorrect version. The correct version is number. See your network supervisor for assistance." in Appendix C.999: The message file for this utility cannot be found.SENDAction: See message IDREF="FM69424""999: The message file for this utility cannot be found." in Appendix C.PAGENUM=973 ID="BP967"ID="FM51388"SERVER6: Invalid screen ID passed to screen manager. Module: name. Code offset in module: offset.SERVERExplanation: An NLM program (the module named in the message) tried to print to a nonexistent screen. The NLM program is probably an outdated version or is corrupted.Action: Replace the NLM program with an updated or uncorrupted copy.19: Router configuration error detected. Node address (name) claims network number should be number.SERVERExplanation: Packet routing cannot be completed. The BIND command issued to bind IPX to a LAN driver specified an incorrect network number. Other bridges or servers on the network think that the cabling system has a different network number. You may not be able to locate servers because of failed or improper routing of packets.Action: Unbind the LAN driver; then bind the LAN driver with the correct number displayed in the message. Reissue the BIND command at the system console using the network number shown in the alert message. Two or more servers will detect this condition. Set the network address correctly or the condition will recur.20: A router is falsely claiming that my internal network number has changed from correct_node to incorrect_node. Information came from router at router's_node.SERVERExplanation: Another server's router is claiming that the node address is different from what the node address really is. The router is probably malfunctioning.Action: Seek out and fix the router that is sending the incorrect information.30: This module is using number outdated API calls. You should upgrade to a newer module when it becomes available.SERVERExplanation: The operating system displays this message whenever a loadable module (NLM program) is loaded that is using old API calls. NetWare 4 renamed some of the APIs as additional resources were tracked. Resource tracking provides statistical information about how many resources are being used. It also protects the server from NLM programs that try to use more than their share of resources and forces them to relinquish all their resources when they are unloaded. The old APIs work; however, they are slower than the new APIs.Action: Contact the vendor of the module for an updated version using NetWare 4 APIs. Continue to use the current version until you receive the newer version.PAGENUM=974 ID="BP968"45: Connection number user name exceeded outstanding NCP directory search limit.SERVERExplanation: The structure that DOS uses to track the current status of a directory search does not have enough fields to track the file that should be found next on a NetWare volume. Because of this, NetWare must keep a separate search structure in server memory that tracks the status of the search and the next file to be found. DOS does not tell NetWare when it has finished a search, so NetWare must guess when it can discard the search information that it is keeping. The number of searches that NetWare will track is controlled by the SET utility's "Maximum Outstanding NCP Searches" parameter, which is set to a default value of 51 per connection. This message indicates that a program tried to continue a search that NetWare is no longer tracking. Because of this, NetWare cannot return the next filename that should be found.Action: You can increase the number of searches that the server tracks by changing the SET utility's "Maximum Outstanding NCP Searches" parameter. However, doing so will use a lot more memory to track searches. (Searches must be tracked separately for each connection.) It also may degrade performance if it causes the number of cache buffers available to be too small.If performance is degraded, add additional memory to the server. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. A second solution is to determine which program tried to continue a search that the server was not tracking. The search method that the program uses can be modified so that it does not require more than 51 searches to be tracked. Or, if available, an alternate program could be used.46: System file lock threshold exceeded. Number file open or lock requests failed.SERVERExplanation: The number indicates the requests that failed to open or lock a file because the limit was exceeded. The number of open files and file locks on the server exceeded the maximum specified by the SET utility's "Maximum File Locks: number" parameter. The default is 10,000. The file open or lock requests are not being serviced.Action: Increase the number of file locks using the SET MAXIMUM FILE LOCKS command. For more information, see "BOOK="utlrfenu" COLLECTION="nw41"SET" in Utilities Reference.84: Invalid resource tag passed to CreateProcess.SERVERPAGENUM=975 ID="BP969"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 program that was trying to create the new process. The process was not created. The NLM program may have had a problem when it tried to get the resource tag prior to 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 program, or the NLM program may be corrupted. In either case, the NLM program will not be able to complete the operation for which the process was needed. If the NLM program is in the process of loading, it may fail to load.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. If there is no memory problem, try reloading the NLM program from the manufacturer's original media. If the error persists, contact the vendor for an updated version of the NLM program.85: CreateProcess called with stack size too small.SERVERExplanation: The system tried to load an NLM program that allocated an inadequate amount of stack space for itself. The NLM program is outdated or corrupted.Action: Try reloading the NLM program from its original media and try again. If the problem persists, contact the vendor for an updated version of the NLM program.86: CreateProcess could not allocate a process control block.SERVERExplanation: The system does not have enough memory to start a new process. The request to create a new process may have been internal to the server or generated by an NLM program. If this error occurs while the system is trying to load an NLM program, the NLM program will not be able to load and run properly.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.236: Error prevented preservation of file path during file erase.SERVERExplanation: The operating system was unable to retain the specified deleted file in a salvageable state. The file being deleted was purged, and it cannot be salvaged. This message should be preceded by a message stating the actual error condition (such as a disk-write error or out-of-memory error).Action: Use the message displayed before this one to determine the actual cause of and solution for the problem.237: Insufficient directory space (or memory) to preserve path during file erase.SERVERExplanation: While trying to delete a file, the server was unable to obtain the needed directory table space or memory to retain the deleted file in a state in which it could be salvaged. The file was deleted and purged. A preceding message on the screen should indicate the cause of this error.Action: Use the message displayed before this one to determine the actual cause of and solution for the problem.286: Drive_name deactivated due to hotfix failure.SERVERExplanation: The indicated drive was deactivated because of a Hot Fix error.Action: None. This message is for information only.PAGENUM=976 ID="BP970"298: Account number deleted by user number on station number. Number active connection terminated.SERVERExplanation: Someone, probably the network supervisor, has terminated the connection.Action: None. This message is for information only.353: Number Incomplete Transactions Found. Last record was written at date_and_time.SERVERExplanation: This message indicates that a database has closed improperly. This message lists the number of incomplete transactions and the time the last complete record was written.Action: None. This message is for information only.383: Internal compression error: file `name' volume number intermediate size number. Offset totals from intermediate file generation (number) and intermediate file processing (number) mismatch invalidating intermediate file.SERVERExplanation: This error resulted from an internal consistency check done by compression to guarantee the integrity of the data being compressed. During file compression, an intermediate file is created that describes the compressed version of the file. The file contains codes describing what should be encoded in the compressed version of the file. The totals from processing the original file do not match the totals from processing the intermediate file. This would only be caused by insufficient memory or by a disk returning corrupted data. The file that was being compressed will remain uncompressed, and the system will try again later to compress it.Action: No immediate action is necessary. Note the volume number and watch for more of these same alerts. Also, watch for other errors indicating that the memory or disk is failing. If these alerts or other data corruption problems happen often on a particular volume, the disk or hardware supporting the disk should be repaired or replaced. See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.406: Redirection table inconsistencies on partition number cannot be corrected.SERVERExplanation: The Hot Fix tables contain inconsistencies. All data on the partition has been lost.Action: Reset the Hot Fix tables for the partition. For more information on Hot Fix, see "BOOK="superenu" COLLECTION="nw41"Managing Server Hard Disks" in Supervising the Network.407: Redirection table inconsistencies on partition number were corrected.SERVERExplanation: Hot Fix detected inconsistencies between redirection tables on mirrored drives. The tables on one disk were updated with the latest information on the other.Action: None. This message is for information only. For more information on Hot Fix, see "BOOK="superenu" COLLECTION="nw41"Managing Server Hard Disks" in Supervising the Network.PAGENUM=977 ID="BP971"410: Insufficient memory to autoload modules.SERVERExplanation: An unsuccessful attempt to automatically load specified NLM programs during startup was made. The server may 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 "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.411: Directory FAT chain has a hole.SERVERExplanation: A File Allocation Table (FAT) chain is a list of directory block locations. If the FAT chain skips a block, a hole appears in the chain. (A hole is a section that is not sequential.) A hole indicates that the location was never allocated. This message indicates that while a volume was being initialized, a directory volume structure initialization routine found that the file allocation table was not sequential. The FAT value did not match the directory length. The volume mount was aborted and all resources were returned. This error probably indicates 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, recreate it using INSTALL, and restore the data from the backup.412: Error reading in volume directory.SERVERExplanation: The current directory entry being examined did not have the correct root subdirectory code number. This error probably indicates 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, recreate it using INSTALL, and restore the data from the backup.413: Invalid maximum space defined in subdirectory.SERVERExplanation: The operating system encountered a problem while mounting a volume. This error probably indicates corruption.Action: Run VREPAIR. Warning: If you delete the volume, all data will be destroyed. You will have to restore the data from a backup.PAGENUM=978 ID="BP972"If the problem persists, make sure a volume backup exists. Delete the volume, recreate it using INSTALL, and restore the data from the backup.414: Subdirectory entry refers to invalid directory block.SERVERExplanation: The operating system encountered a problem while mounting a volume. A test of the subdirectory first block entry did not return with the correct value. The entry contained a value not equal to zero, indicating the wrong directory block or corruption.Action: Run VREPAIR. 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, recreate it using INSTALL, and restore the data from the backup.415: Not enough memory to validate directory.SERVERExplanation: The server had enough memory to read the directory tables, but it did not have enough memory to validate the directories. Before the volume was dismounted, you received a warning that the you were running out of memory and that you could not remount the volume because it had grown too much. This error could occur at one of the following points in the volume mount:MARK=BULLETAfter comparing mirrored directory lengths.During setup of extra directory structures.During directory space restriction routines.While adding directory trustees.During maintenance routines.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.416: Mirror copies of the volume directory don't match.SERVERExplanation: The contents of directory 0 were compared with those of directory 1. The compare routine found they did not match. This error probably indicates corruption.Action: Run VREPAIR. 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, recreate it using INSTALL, and restore the data from the backup.PAGENUM=979 ID="BP973"417: Volume directory is too large (over 2 million files).SERVERExplanation: While allocating directory tables during a volume mount, the system found the number of directory entries for the volume exceeded 2 million entries. This error probably indicates corruption.Action: Run VREPAIR. 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, recreate it using INSTALL, and restore the data from the backup.418: Connection number, Negotiate Packet request failed using Buffer Size = number, which was larger than Maximum Buffer size of number.SERVERExplanation: A station tried to negotiate a packet size that was larger than the maximum packet size allowed by the Link Support Layer (LSL). See "BOOK="cncptenu" COLLECTION="nw41"Link Support Layer (LSL)" in Concepts for more information.Action: None. This message is for information only.425: Insufficient memory for directory tables.SERVERExplanation: One of the steps in volume directory initialization is to request resource tags and memory for directory tables, directory hash tables, and extended directory tables. The volume did not mount because the server does not have enough memory available.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.433: Invalid deleted file.SERVERExplanation: While checking deleted file directory entries, the system aborted the volume mount process for one of the following reasons:MARK=BULLETThe FAT chain check did not return with a successful completion code.The directory entry file size did not equal zero.This error probably indicates corruption.Action: Run VREPAIR and restart the system. If the problem persists, make sure a volume backup exists. Delete the volume, recreate it using INSTALL, and restore the data from the backup.PAGENUM=980 ID="BP974"438: Invalid available entry.SERVERExplanation: While scanning the volume directory for valid subdirectories, the system encountered a subdirectory entry that contained information stating it was a file. This error probably indicates corrupted data or a corrupted volume.Action: Run VREPAIR and restart the system. If the problem persists, make sure a volume backup exists. Delete the volume, recreate it using INSTALL, and restore the data from the backup.439: Invalid root directory entry.SERVERExplanation: The current directory entry being examined did not have the correct root subdirectory code number. This error probably indicates corruption.Action: Run VREPAIR and restart the system. If the problem persists, make sure a volume backup exists. Delete the volume, recreate it using INSTALL, and restore the data from the backup.440: Invalid name space value.SERVERExplanation: One of the following probably occurred:MARK=BULLETWhile scanning volume directories, the system found that the defined name space was greater than the maximum number of name space entries available.The user tried to mount a volume that had a particular name space supported on the volume, but did not load the name space support before mounting the volume.Action: Load the name space support before mounting the volume. If the error persists, run VREPAIR on the volume.444: Name space support not loaded.SERVERExplanation: The name space NLM program did not load properly. One possibility is that the name space module had not been loaded before you tried to mount the volume. Other possibilities are that the module is corrupted or is the wrong type.Action: Load a correct working version of the name space module before mounting the volume. If this doesn't correct the problem, run VREPAIR on the volume.445: Invalid name space list.SERVERPAGENUM=981 ID="BP975"Explanation: While scanning subdirectory name space list entries, the system found that the next name space list entry was greater than or equal to the number of defined name spaces for the volume. Another reason for this error might be the next entry scanned was greater than the maximum directory entries. In either case, this error probably indicates corruption.Action: Run VREPAIR and restart the system. If the problem persists, make sure a volume backup exists. Delete the volume, recreate it using INSTALL, and restore the data from the backup.446: Invalid name space list order.SERVERExplanation: While scanning subdirectory name space list entries, the system found that the next name space list entries are not in the correct sequence. This error probably indicates corruption.Action: Run VREPAIR and restart the system. If the problem persists, make sure a volume backup exists. Delete the volume, recreate it using INSTALL, and restore the data from the backup.447: Invalid subdirectory number in trustee directory entry.SERVERExplanation: While the system was scanning subdirectory entries, the trustee subdirectory number was greater than or equal to the number of directory entries. The trustee subdirectory number is less than zero. This error probably indicates corruption.Action: Run VREPAIR and restart the system. If the problem persists, make sure a volume backup exists. Delete the volume, recreate it using INSTALL, and restore the data from the backup.448: Invalid suballocation directory entry.SERVERExplanation: While scanning directory entries, the system found an invalid suballocation entry. This error probably indicates corruption.Action: Run VREPAIR and restart the system. If the problem persists, make sure a volume backup exists. Delete the volume, recreate it using INSTALL, and restore the data from the backup.449: Invalid trustee directory entry.SERVERExplanation: While scanning directories in the current volume for trustees, the system found one of the following problems:MARK=BULLETThe trustee count was greater than the number of trustee entries.The trustee count equaled zero.PAGENUM=982 ID="BP976"In either case, this error indicates file system corruption.Action: Run VREPAIR and restart the system. If the problem persists, make sure a volume backup exists. Delete the volume, recreate it using INSTALL, and restore the data from the backup.450: Deleted file is a subdirectory.SERVERExplanation: While in the process of initializing the directory volume structures, the system found that one or both of the members of the work directory (directory flag and directory file attribute) had their subdirectory bit turned on. What was thought to be a file was in fact a subdirectory. The directory volume did not initialize properly and all resources were returned. This error probably indicates file system corruption.Action: Run VREPAIR and restart the system. If the problem persists, make sure a volume backup exists. Delete the volume, recreate it using INSTALL, and restore the data from the backup.451: Invalid subdirectory number in user restriction directory entry.SERVERExplanation: While scanning subdirectories on a volume to be mounted, the system found a subdirectory with a restriction subdirectory number not equal to zero. This number should always equal zero because it is predefined. This error probably indicates file system corruption.Action: Run VREPAIR and restart the system. If the problem persists, make sure a volume backup exists. Delete the volume, recreate it using INSTALL, and restore the data from the backup.452: Invalid user restriction node...too many trustees.SERVERExplanation: The operating system encountered a problem while mounting a volume. This error probably indicates file system corruption.Action: Run VREPAIR. If the problem persists, make sure a volume backup exists. Delete the volume, recreate it using INSTALL, and restore the data from the backup.453: Insufficient memory available for user restriction nodes.SERVERExplanation: The server does not have enough memory. A call for memory from within the set_user_restriction routine failed. This memory would have been used to create user restriction node IDs.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.PAGENUM=983 ID="BP977"454: Invalid directory number code.SERVERExplanation: The system found that the subdirectory entry it was about to examine did not have the correct directory number (-4) of user restrictions, trustees, and deleted file blocks.Action: Run VREPAIR and restart the system. If the problem persists, make sure a volume backup exists. Delete the volume, recreate it using INSTALL, and restore the data from the backup.455: Invalid subdirectory number in file directory entry.SERVERExplanation: A subdirectory had a number that was greater than or equal to the maximum number of directory entries. This error probably indicates file system corruption.Action: Run VREPAIR and restart the system. If the problem persists, make sure a volume backup exists. Delete the volume, recreate it using INSTALL, and restore the data from the backup.456: Directory block is inconsistent...has several subdirectory numbers.SERVERExplanation: The volume's directory tables have been corrupted. Upon initialization, the subdirectory number vector table should contain a value of -1 (which is then changed to a zero). If the value residing in the table is not equal to -1 or 0, the volume mount is aborted and all resources are returned to the system. In this case, the table contained a different value.Action: Run VREPAIR and restart the system. If the problem persists, make sure a volume backup exists. Delete the volume, recreate it using INSTALL, and restore the data from the backup.498: Insufficient memory to allocate initial memory test block.SERVERExplanation: System initialization failed because the server does not have enough memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.508: Invalid resource tag passed to RegisterHardwareOptions.SERVERExplanation: An NLM program 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 program. The NLM program will not be able to perform properly.PAGENUM=984 ID="BP978"The NLM program may have had a problem when it tried to get the resource tag prior to calling RegisterHardwareOptions. If the server is low on memory, the NLM program's request to create the resource tag may have failed. In this case a preceding error message should indicate the out- of-memory problem. There could also be a bug in the NLM program that is calling RegisterHardwareOptions with an invalid resource tag.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. If memory is not the problem and the error persists, contact the vendor for an updated version of the NLM program.510: CheckAndAddHardware could not allocate a resource tag.SERVERExplanation: This error could occur for one of the following reasons:MARK=BULLETThe NLM program made a call to an API for a previous version of NetWare.The operating system tried to allocate memory for the resource, but the server does not have enough memory.In either case, the NLM program that called CheckAndAddHardware is not able to register the hardware resources that it needs to use. The NLM program will not be able to function properly.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. If the error persists, contact your Novell Authorized Reseller or the NLM program's vendor.518: RemoveHardwareOptions called with invalid pointer.SERVERExplanation: When a LAN or disk driver tried to unload, it called the RemoveHardwareOptions function with an invalid pointer. This error probably indicates an outdated driver.Action: Update the offending LAN or disk driver with a newer version. If the problem persists, contact your Novell Authorized Reseller.560: Volume already supports this Name Space.SERVERExplanation: The specified name space has already been added to the volume. A volume can be configured only once for a specific type of name space.Action: None. This message is for information only.568: Add name space aborted by the user.SERVERExplanation: After beginning installation of a name space, the user opted to discontinue the operation.Action: None. This message is for information only.PAGENUM=985 ID="BP979"569: Volume already supports this Name Space.SERVERExplanation: The specified name space has already been added to the volume. A volume can be configured only once for a specific type of name space.Action: None. This message is for information only.ID="FM57635"571: Error reading directory on NameSpace upgrade...volume is left in a bad state.SERVERExplanation: This error occurred when an ADD NAME SPACE command was issued. The error could indicate file system corruption.Action: Run VREPAIR with the "Remove Name Space Support from the Volume" option. If the problem persists, make sure a volume backup exists. Delete the volume, recreate it using INSTALL, and restore the data from the backup.572: Error reading directory on NameSpace upgrade...volume is left in a bad state.SERVERAction: See message IDREF="FM57635""571: Error reading directory on NameSpace upgrade...volume is left in a bad state."574: Error reading directory on NameSpace upgrade...volume is left in a bad state.SERVERAction: See message IDREF="FM57635""571: Error reading directory on NameSpace upgrade...volume is left in a bad state."579: Add name space aborted by the user due to insufficient disk space.SERVERExplanation: There is insufficient disk space to add the desired name space.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Disk Space Problems" in Supervising the Network.580: Add name space aborted due to insufficient server RAM.SERVERExplanation: The server may not have enough available memory. There is insufficient memory to add the desired name space.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.581: Error allocating new entry on NameSpace upgrade...volume is left in a bad state.SERVERExplanation: An error occurred when an ADD NAME SPACE command was issued. The error could indicate file system corruption.Action: Run VREPAIR with the "Remove Name Space Support from the Volume" option. If the problem persists, make sure a volume backup exists. Delete the volume, recreate it using INSTALL, and restore the data from the backup.PAGENUM=986 ID="BP980"582: Error setting entry name on NameSpace upgrade...volume is left in a bad state.SERVERExplanation: An attempt to set a name space name has failed. The name space will not be effective, and problems with other name spaces may occur. There may not be enough disk space or system memory to handle the name space.Action: Verify that the system is large enough to handle the name space. Increase the available memory. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. Increase the available disk space on the volume. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Disk Space Problems" in Supervising the Network. Then re-create the volume.583: AddNameSpace error reading volume header...volume is left in a bad state.SERVERExplanation: An error occurred when an ADD NAME SPACE command was issued.Action: Run VREPAIR. If the problem persists, make sure a volume backup exists. Delete the volume, recreate it using INSTALL, and restore the data from the backup.584: Error writing to the extended directory space.SERVERExplanation: The operating system was trying to write extended directory information to disk. When it tried to write the information, it got a disk error. The information was not written to the disk and will be lost. The information which was lost may have been extended attribute data. This error may have been caused by a hard disk or channel failure. The disk may have other data integrity problems.Action: Use the warning message that preceded this message to determine the actual cause and solution of the problem. See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.607: DeleteFileToLimbo failed, unable to save migrated file (path).SERVERExplanation: This is probably an internal program error. Action: Retry the operation. If the problem persists, contact your Novell Authorized Reseller.613: Invalid line in command file.SERVERExplanation: A message that was to be displayed on the screen was too long. This problem may have occurred when this product was translated.Action: None. This message is for information only.PAGENUM=987 ID="BP981"618: Invalid startup command: string.SERVERExplanation: 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 "BOOK="superenu" COLLECTION="nw41"Creating or Editing a Server Batch (.NCF) File" in Supervising the Network.633: Account number deleted by user number on station number. 1 active connection terminated.SERVERExplanation: Someone, probably the network supervisor, has terminated the connection.Action: None. This message is for information only.635: Drive_name deactivated for unknown reason.SERVERExplanation: A hardware error probably occurred which deactivated the drive.Action: See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.677: Station number file lock threshold exceeded. Total violations number.SERVERExplanation: The number of open files and file locks on the server for the specified station exceeded the limit specified. The total violations number indicates the total number of requests to lock a record that failed.Action: Use the SET console command to increase the number of file locks per connection:FORMAT="LINESPECIFIC"MOREINFO="NONE"SET MAXIMUM FILE LOCKS PER CONNECTION=number 
Minimum = 10 
Maximum = 1000 
Default = 250 Increasing the number of file locks will increase the amount of memory used by the server. You may need to increase the available memory on the workstation. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.678: System record lock threshold exceeded. Number record lock requests failed.SERVERExplanation: The number of record locks on the server exceeded the maximum specified. Applications that lock records will not function properly. The number in the message indicates the total number of record lock requests for the station that failed because the limit was exceeded.Action: Use the SET console command to increase the number of system record locks:FORMAT="LINESPECIFIC"MOREINFO="NONE"SET MAXIMUM RECORD LOCKS=number 
PAGENUM=988 ID="BP982"Minimum = 10 
Maximum = 10,000 
Default = 500 Increasing the number of record locks will increase the amount of memory required by the server. You may need to increase the available memory on the server. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.679: Station number record lock threshold exceeded. Total violations number.SERVERExplanation: The number of record locks on the server for the specified station exceeded the limit specified. Applications that request record locks do not function properly until record locks are released by other applications. The total violations number indicates the number of requests that failed to lock a record because the record lock threshold limit was exceeded.Action: Use the SET console command to increase the number of record locks:FORMAT="LINESPECIFIC"MOREINFO="NONE"SET MAXIMUM RECORD LOCKS PER CONNECTION=number 
Minimum = 100 
Maximum = 200,000 
Default = 20,000 Increasing the number of record locks will increase the amount of memory required by the server. The server may need more available memory. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.684: Drive deactivated due to driver unload.SERVERExplanation: The drive indicated was deactivated because the driver was unloaded.Action: None. This message is for information only.685: You exceeded your outstanding NCP directory search limit.SERVERExplanation: You cannot search directories beyond a certain depth.Action: None. This message is for information only. If this error appears often, increase the search limit.694: Login was disabled by user name on station number.SERVERExplanation: The specified user issued a command to disable login.Action: None. This message is for information only.PAGENUM=989 ID="BP983"695: Login was enabled by user name on station number.SERVERExplanation: The specified user issued a command to enable login.Action: None. This message is for information only.719: Error reading message file.SERVERExplanation: This error may indicate file system or data corruption.Action: Run VREPAIR and restart the system. If the problem persists, make sure a volume backup exists. Delete the volume, recreate it using INSTALL, and restore the data from the backup.720: Error allocating memory for message file.SERVERExplanation: The server probably does not have enough memory to load the message file.Action: Increase the available memory. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. If memory is not the problem, try running VREPAIR; then restart the system. If the problem persists, make sure a volume backup exists. Delete the volume, recreate it using INSTALL, and restore the data from the backup.726: RT Data Migrator Default Read Write Support Module has been changed.SERVERExplanation: The default support module has been changed to a new support module.Action: None. This message is for information only.739: Directory block refers to nonsubdirectory directory entry.SERVERExplanation: A volume's directory block has been corrupted. While scanning directory blocks, the system found a block that did not have a corresponding subdirectory node. (The entry did not exist, or a bit within the subdirectory bit table was not set to ON.)Action: Run VREPAIR and restart the system. If the problem persists, make sure a volume backup exists. Delete the volume, recreate it using INSTALL, and restore the data from the backup.745: User name on station number cleared by connection watchdog. Connection cleared due to communication or station failure.SERVERExplanation: The user at the workstation is no longer attached to the server. The server has purged the connection and all associated system resources are freed. If the SET server utility's "Display Watchdog Logouts" parameter has been set to ON, this message will appear when a station is turned off or rebooted before the user has logged out.PAGENUM=990 ID="BP984"Action: During a normal workstation power down or reboot, no action is required. If the station is failing to receive or send watchdog packets, check the cabling and cable termination points. On slow networks (wide area networks or networks with T-links or modem connections), workstations may have their connections cleared if the interval between watchdog packets is too small.If the loss of contact is unexpected, potential problems can be isolated from the network map. Look for routers that are offline or inoperative.For information on the watchdog feature, see "BOOK="utlrfenu" COLLECTION="nw41"SET" in Utilities Reference and "BOOK="cncptenu" COLLECTION="nw41"Watchdog" in Concepts.746: Server NetWare Copyright Violation! Call SUPERVISOR! Server at address number/node also has my serial number.SERVERExplanation: The copy of NetWare 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, and buy a valid copy of NetWare to run on the server.747: Write to a protected or nonpresent page. Process: process Module: module Code offset in module: offset Access address: addressSERVERExplanation: An NLM program tried to write to non-existent memory or memory that does not belong to that NLM program, which creates a page fault in memory. The server may be using an outdated NLM program, the server memory could be corrupted, or there could be a programming error in the software.Action: Replace the NLM program with an updated version. If you cannot replace the NLM program, use the SET server utility to set the "Write Fault Emulation" parameter to ON, to allow the old NLM program to continue running. If the problem persists, contact your Novell Authorized Reseller.748: Read from a nonpresent page. Process: process Module: module Code offset in module: module Access address: addressSERVERPAGENUM=991 ID="BP985"Explanation: An NLM program tried to write to non-existent memory, or from memory that does not belong to that NLM program, which creates a page fault in memory. The server may be using an outdated NLM program, the server memory could be corrupted, or there could be a programming error in the software.Action: Replace the NLM program with an updated version. If you cannot replace the NLM program, use the SET server utility to set the "Write Fault Emulation" parameter to ON, to allow the old NLM program to continue running. If the problem persists, contact your Novell Authorized Reseller.750: IPX received an incomplete packet from network number/node. Number incomplete packets received.SERVERExplanation: The LAN driver from the specified node sent a valid IPX packet, but the data field was empty or incomplete. The operating system has discarded the packet to prevent data corruption. Users on the affected network node will experience interrupted network service and shell time-outs.Action: Update the LAN driver for the specified node.751: Insufficient memory available to mount volume. Volume name was NOT mounted.SERVERExplanation: The server does not have enough memory to mount the volume.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.752: The FAT chain used to define the FAT is invalid. Volume name was NOT mounted.SERVERExplanation: A File Allocation Table (FAT) chain is a list of directory block locations. This error probably indicates file system corruption.Action: Run VREPAIR. If the problem persists, make sure a volume backup exists. Delete the volume, recreate it using INSTALL, and restore the data from the backup.753: The FAT chain used to define the FAT overlaps on itself. Volume name was NOT mounted.SERVERExplanation: A File Allocation Table (FAT) chain is a list of directory block locations. This error probably indicates file system corruption.Action: Run VREPAIR. If the problem persists, make sure a volume backup exists. Delete the volume, recreate it using INSTALL, and restore the data from the backup.754: Error reading in the FAT. Volume name was NOT mounted.SERVERExplanation: A File Allocation Table (FAT) is an index to one or more disk allocation blocks in which a file is located. This error probably indicates file system corruption.Action: Run VREPAIR. If the problem persists, make sure a volume backup exists. Delete the volume, recreate it using INSTALL, and restore the data from the backup.PAGENUM=992 ID="BP986"755: The mirror copies of the FAT don't match. Volume name was NOT mounted.SERVERExplanation: A File Allocation Table (FAT) is an index to one or more disk allocation blocks in which a file is located. This error probably indicates file system corruption.Action: Run VREPAIR. If the problem persists, make sure a volume backup exists. Delete the volume, recreate it using INSTALL, and restore the data from the backup.756: The FAT chain used to define the FAT has an invalid forward reference. Volume name was NOT mounted.SERVERExplanation: A File Allocation Table (FAT) chain is a list of directory block locations. This error probably indicates file system corruption.Action: Run VREPAIR. If the problem persists, make sure a volume backup exists. Delete the volume, recreate it using INSTALL, and restore the data from the backup.757: A file's FAT chain contains entries out of order. Volume name was NOT mounted.SERVERExplanation: A File Allocation Table (FAT) chain is a list of directory block locations. The data of the file may not be damaged, but the file is invalid due to the sequence of the data. This error probably indicates file system corruption.Action: Run VREPAIR. If the problem persists, make sure a volume backup exists. Delete the volume, recreate it using INSTALL, and restore the data from the backup.758: A file's FAT chain collides with another FAT chain.SERVERExplanation: The File Allocation Table (FAT) chain is a list of directory block locations. Both files involved are invalid; updates to either file could cause damage to both of them.Action: Run VREPAIR. If the problem persists, make sure a volume backup exists. Delete the volume, recreate it using INSTALL, and restore the data from the backup.759: The first entry of a file's FAT chain is invalid. Volume name was NOT mounted.SERVERExplanation: A File Allocation Table (FAT) chain is a list of directory block locations. This error probably indicates file system corruption.Action: Run VREPAIR. If the problem persists, make sure a volume backup exists. Delete the volume, recreate it using INSTALL, and restore the data from the backup.760: A FAT chain has an invalid next link. Volume name was NOT mounted.SERVERPAGENUM=993 ID="BP987"Explanation: A File Allocation Table (FAT) chain is a list of directory block locations. This message indicates that the next link in a FAT chain is invalid. This error probably indicates file system corruption. If this problem occurs during a volume mount, the operating system will try to load VREPAIR to correct the problem.Action: Run VREPAIR. If the problem persists, make sure a volume backup exists. Delete the volume, recreate it using INSTALL, and restore the data from the backup.761: A file with a nonzero length doesn't have a FAT chain. Volume name was NOT mounted.SERVERExplanation: A File Allocation Table (FAT) chain is a list of directory block locations. This error indicates an invalid file, probably due to corruption.Action: Run VREPAIR. If the problem persists, make sure a volume backup exists. Delete the volume, recreate it using INSTALL, and restore the data from the backup.762: Error rereading a directory entry. Volume name was NOT mounted.SERVERExplanation: The operating system encountered a problem while mounting a volume because the second time a directory entry was read, the read failed. This error probably indicates file system corruption.Action: Run VREPAIR. If the problem persists, make sure a volume backup exists. Delete the volume, recreate it using INSTALL, and restore the data from the backup.763: Invalid directory FAT chain. Volume name was NOT mounted.SERVERExplanation: A File Allocation Table (FAT) chain is a list of directory block locations. There are duplicate extended directory chains (chain0 and chain1). If these chains do not match for some reason, this error is produced and the volume will not mount. This error probably indicates file system corruption.Action: Run VREPAIR and restart the system. If the problem persists, make sure a volume backup exists. Delete the volume, recreate it using INSTALL, and restore the data from the backup.816: Unable to open file NET$ACCT.DAT to add audit record.SERVERExplanation: A disk I/O has failed.Action: See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.829: Suballocation node used on TTS enabled file. Volume name was NOT mounted.SERVERExplanation: The ending node of the TTS file was a suballocation node. This error probably indicates file system corruption.Action: Try running VREPAIR. If the problem persists, make sure a volume backup exists. Delete the volume, recreate it using INSTALL, and restore the data from the backup.If the problem persists, contact your Novell Authorized Reseller.PAGENUM=994 ID="BP988"830: Short term memory allocator is out of memory. Number attempts to get more memory failed.SERVERExplanation: The request for short-term memory failed because the server is out of memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.831: Process_name Process did not relinquish control frequently. Module: name. Code offset in module: offset.SERVERExplanation: 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 program is not relinquishing control when it should, preventing higher priority processes from executing. The NLM program may be corrupted, or the server may have a prerelease version of the NLM program.Action: Unload the NLM program. Make sure the server has the most current version of the NLM program; then reload it from the original CD-ROM or diskettes. If the problem persists, contact the vendor of the NLM program.832: User name connection number attempted to extend the length of a file with no owner. Filename: name.SERVERExplanation: A file needed to be extended; however, because the file had no owner, the operation was aborted.Action: Delete the file, or assign the file an owner.841: AUDIT event number = number. Invalid volume number = number.SERVERExplanation: An invalid volume number was used during a call to audit the event indicated in the message. This may be an internal program error.Action: Reboot the server. If the problem persists, contact your Novell Authorized Reseller.842: Open volume auditing failure. Enter volume audit password to mount with auditing disabled. Enter password:SERVERExplanation: The operating system failed when it tried to open volume auditing. (No other information is available.)Action: Restart the server, or enter the password and continue with auditing disabled. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=995 ID="BP989"843: Unable to open AUDIT configuration file error. Press enter to continue.SERVERExplanation: The operating system failed when trying to open the AUDIT configuration file. (No other information is available.)Action: Restart the server. If the problem persists, contact your Novell Authorized Reseller.844: Error rereading a directory entry.SERVERExplanation: An attempt to locate the directory entry of a previously identified file or directory has failed. The directory entry table may have become corrupted.Action: Check the network connection and retry the function. Run VREPAIR if necessary to repair the directory entry table.845: Auditing disabled, cannot open valid audit configuration file, volume: name.SERVERExplanation: The operating system disabled auditing for the indicated volume because the configuration file is an old version, or it is corrupted.Action: Delete the old audit files.846: Cannot open audit data file. Enter volume audit password to mount with auditing disabled. Enter password:SERVERExplanation: The auditing system could not open the audit data file because the audit file has been corrupted or accidentally deleted.Action: Follow the directions after the message. In most instances, the system can continue operation if the auditor's password is entered. This will result in the system working with auditing disabled. If the system does not continue, reboot the server. If the problem persists, contact your Novell Authorized Reseller.847: Audit file full, volume: name.SERVERExplanation: The operating system encountered a full audit file when trying to mount a volume.Action: Use AUDITCON to reset the audit file. You also may need to increase the maximum size of the audit file.866: Directory tree is circularly linked.SERVERExplanation: A directory contains a subdirectory that is also its parent.Action: Run VREPAIR and restart the system. If the problem persists, make sure a volume backup exists. Delete the volume, recreate it using INSTALL, and restore the data from the backup.PAGENUM=996 ID="BP990"867: Directory tree is too deep.SERVERExplanation: The maximum subdirectory tree depth of 25 levels has been exceeded.Action: Change the SET server utility's "Maximum Subdirectory Tree Depth" parameter to be able to go beyond the default limit of 25. This SET parameter can be set to a maximum of 100 levels. See "BOOK="utlrfenu" COLLECTION="nw41"SET" in Utilities Reference for more information.868: Subdirectory entry and first directory block do not match.SERVERExplanation: While verifying subdirectory entries, the system scanned the subdirectory number vector table of the current volume. The value of the current element in the table does not have a value of -1 (which indicates a subdirectory); therefore, the attempt to mount the volume has been aborted.Action: Run VREPAIR. If the problem persists, make sure a volume backup exists. Delete the volume, recreate it using INSTALL, and restore the data from the backup.869: Length differences on mirror directory chains could not be resolved.SERVERExplanation: The operating system encountered a problem while mounting a volume. The amount of directory blocks of directory 0 didn't match the number of directory 1. The volume mount was aborted because the directory integrity was disrupted.Action: Run VREPAIR. If the problem persists, make sure a volume backup exists. Delete the volume, recreate it using INSTALL, and restore the data from the backup.870: File without trustee definitions had a trustee node.SERVERExplanation: The information about a given file indicated that the file had specific trustee assignments, but no trustee assignments could be found. This is a warning error, but in most cases it will not cause serious problems.Action: Run VREPAIR. If the problem persists, make sure a volume backup exists. Delete the volume, recreate it using INSTALL, and restore the data from the backup.879: Invalid path specified.SERVERExplanation: 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.881: DOS has been removed. DOS paths can no longer be searched.SERVERExplanation: After DOS has been removed, DOS paths cannot be included in the search path.Action: None. This message is for information only.PAGENUM=997 ID="BP991"ID="FM75713"882: Insufficient memory to add search path.SERVERExplanation: The SEARCH ADD command was used, but the server cannot allocate memory to expand the search path mapping.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.884: Insufficient memory to add search path.SERVERAction: See message IDREF="FM75713""882: Insufficient memory to add search path."889: Invalid path specified.SERVERExplanation: 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.891: DOS has been removed, DOS paths can no longer be searched.SERVERExplanation: After DOS has been removed, DOS paths cannot be included in the search path.Action: None. This message is for information only.ID="FM73299"892: Insufficient memory to add search path.SERVERExplanation: The SEARCH ADD command was used, but the server cannot allocate memory to expand the search path mapping.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.893: Insufficient memory to add search path.SERVERAction: See message IDREF="FM73299""892: Insufficient memory to add search path." 894: Insufficient memory to add search path.SERVERAction: See message IDREF="FM73299""892: Insufficient memory to add search path." 909: Mirrored partition number cannot be remirrored.SERVERExplanation: A mirrored group cannot be remirrored because a redirected block with missing data could not be replicated on the out-of-synch partition. The drive may be faulty.Action: If possible, try replacing the drive that has the malfunctioning redirection area. See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.PAGENUM=998 ID="BP992"911: A scheduled "Work To Do" took over one minute to be run.SERVERExplanation:  Low priority threads are used for file compression, etc. Set `Upgrade Low Priority Threads' to ON or unload the NLM program. An NLM program is not allowing low priority jobs to be processed. The server is probably using an NLM program that is unlicensed or under development.Action: Follow the directions in the error message.919: Invalid connection type passed to AllocateConnectionNumber.SERVERExplanation: The server was processing a request to create a new connection, but the connection type 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 program that requested the connection. This is an internal program error in the NLM program.Action: The NLM program needs to be corrected by the developer so it can use a valid connection type when asking the server for a new connection. Contact the NLM program's reseller to obtain a corrected copy of the NLM program.921: Invalid resource tag passed to AllocateConnectionNumber.SERVERExplanation: 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 program that requested the connection. This may be an internal program error in the NLM program, or it may be associated with lack of available memory.Action: This problem may have been caused by a previous out-of-memory error when the NLM program tried to get the connection resource tag. If the preceding message indicates that the system is out of memory, make more memory available. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. If the problem does not appear to be memory related, contact your Novell Authorized Reseller and provide an accurate account of the circumstances that led to the error so the reseller can re-create the problem and find a solution.923: Out of server connections. Connect request failed.SERVERExplanation: The server is operating at its maximum connection capacity. No additional connections are allowed until current connections are terminated.Action: Try again later when other users have logged out of the system. A list of attached and logged in users is available from the "Connection Information" window for this server. Idle users can be cleared from the system with MONITOR.PAGENUM=999 ID="BP993"930: User name at station number connection terminated. User did not log out within 5 minutes after security watchdog notice.SERVERExplanation: The user disregarded a system warning to log out and was logged out by the server 5 minutes later. The warning was given for one of the following reasons:MARK=BULLETThe user's connection time expired.The user's account expired.The user's account balance went below the limit.Action: None. This message is for information only.932: Volume name mounted with no Migration NLM loaded, some files may be inaccessible.SERVERExplanation: The volume was mounted with files that cannot be accessed until the RTDM.NLM is loaded.Action: Load RTDM.NLM and the appropriate support module.933: User account name disabled by user name on station number. Number active connection(s) requested to log out.SERVERExplanation: A user's account was disabled while logged in to the server. This message shows who disabled the account and how many connections are affected. The specified user no longer has access to the server.Action: None. This message is for information only.937: Volume name mounted without a specified Migration Support NLM. Some files maybe inaccessible.SERVERExplanation: A volume has been mounted with files that cannot be accessed until the support module needed to access the files has been loaded.Action: Load the appropriate support NLM program.943: Redirected block old_block to new_block on partition number.SERVERExplanation: An I/O error occurred on one of the disks allocated to the designated partition. Hot Fix redirected the data to another physical disk block. There is full data integrity for the file being written. (See "BOOK="cncptenu" COLLECTION="nw41"Device numbering" in Concepts for an explanation of the partition number.)PAGENUM=1000 ID="BP994"Action: None. This message is for information only. If this message appears every few minutes, load MONITOR and check the disk's Hot Fix statistics. Disks that are rapidly using up their Hot Fix redirection blocks usually need to be repaired or replaced. See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.944: Could not redirect block number on partition number.SERVERExplanation: A potential device failure and data loss has been caused by one of the following:MARK=BULLETAn 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 "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.945: Warning: There are no more redirection blocks.SERVERExplanation: The partition has used all its redirection blocks. Future I/O errors cannot be redirected to Hot Fix.Action: See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.946: Warning: There are only number redirection blocks left.SERVERExplanation: 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: See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.957: Invalid deleted file block.SERVERExplanation: While scanning subdirectory entries, the system found that the value of the deleted sequence number of the current block did not equal zero, indicating a corrupted file system.Action: Run VREPAIR and restart the system.1111: Invalid deleted file trustee node.SERVERExplanation: A directory entry indicates that trustee assignments exist for the directory, but none can be found. This error could be caused by file system corruption.Action: re-create the directory or run VREPAIR. If the problem persists, make sure a volume backup exists. Delete the volume, recreate it using INSTALL, and restore the data from the backup.PAGENUM=1001 ID="BP995"1112: Invalid deleted filename space.SERVERExplanation: A check of the next block list table (used to point to members of a subdirectory or available blocks) found its value to be zero. This indicates that no value was present or that it has been deleted. The value should have been greater than zero, which indicates availability or activity. This error could indicate file system corruption.Action: Run VREPAIR and restart the system. If the problem persists, make sure a volume backup exists. Delete the volume, recreate it using INSTALL, and restore the data from the backup.1117: Extended directory entry duplicate chains lengths don't match.SERVERExplanation: While trying to validate extended directory structures, the system compared directory 0's length against the length of directory 1 and found they did not match. One of the duplicate directories has become corrupted.Action: Run VREPAIR and restart the system. If the problem persists, make sure a volume backup exists. Delete the volume, recreate it using INSTALL, and restore the data from the backup.1118: Extended directory entry mirrored copies don't match.SERVERExplanation: The volume mount was aborted when an attempt to compare mirrored directories failed. This error could indicate file system corruption.Action: Run VREPAIR and restart the system. If the problem persists, make sure a volume backup exists. Delete the volume, recreate it using INSTALL, and restore the data from the backup.1119: Invalid extended directory entry FAT chain.SERVERExplanation: A File Allocation Table (FAT) chain is a list of directory block locations. This error may indicate file system corruption.Action: Run VREPAIR and restart the system. If the problem persists, make sure a volume backup exists. Delete the volume, recreate it using INSTALL, and restore the data from the backup.1120: Invalid extended attribute in directory entry.SERVERExplanation: An attempt to identify the extended attributes of a directory has failed.Action: Check the extended attributes of the directory and reset them if necessary.1121: Error allocating a directory entry to add a name space root.SERVERPAGENUM=1002 ID="BP996"Explanation: The system tried to add a name space root and failed. The AllocateDirectoryEntry routine found there were no available directory entries in the subdirectory, so the system tried to extend it. This attempt failed because there were too many directory blocks or not enough memory was available for the volume's directory tables.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.1122: UNIX Hard Link flags set with no UNIX name space.SERVERExplanation: You tried to create a hard link before loading the UNIX name space.Action: Load the UNIX name space before creating a hard link.1123: UNIX Hard Link flags don't match between the name spaces.SERVERExplanation: The name spaces cannot be linked because their flags do not match.Action: Make sure that the UNIX hard link flags match before trying to link the name spaces.1124: The server is not configured to support this volume's DOS type.SERVERExplanation: You tried to mount a volume whose name space (for example, Macintosh) has not yet been configured on the server.Action: Try to mount the volume again after configuring the server to support the appropriate name space. See "BOOK="utlrfenu" COLLECTION="nw41"ADD NAME SPACE" in Utilities Reference for more information.1125: Error creating suballocation file space.SERVERExplanation: This error may indicate file system corruption.Action: Run VREPAIR. If the problem persists, make sure a volume backup exists. Delete the volume, recreate it using INSTALL, and restore the data from the backup.1126: File compression bits set on noncompression volume.SERVERExplanation: A file or files have been assigned the "Immediate Compress" (Ic) attribute, but the volume on which they reside is not configured to perform file compression.Action: Use FLAG to remove the "Immediate Compress" (Ic) attribute on the files involved, move the files to a volume that performs file compression, or use the SET server utility's "Enable File Compression" attribute to ON.PAGENUM=1003 ID="BP997"1127: File is flagged as both compressible and uncompressible.SERVERExplanation: The system does not know whether to perform file compression on a given file because the file has been assigned both the "Immediate Compress" (Ic) and "Don't Compress" (Dc) attribute.Action: Use FLAG to remove the "Immediate Compress" or the "Don't Compress" file attribute on the given file.1132: Error reading from load file.SERVERExplanation: The NLM program 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 program from the vendor or replace the disk. See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network. 1134: Invalid load file format.SERVERExplanation: The description text field of an NLM program was invalid. This field should contain text (about the NLM program) that is greater than zero and less than 128 characters long. The NLM program in this case did not meet these criteria. This problem is due to manufacturer error, NLM program corruption, or disk malfunction.Action: Reload the NLM program from the master CD-ROM or diskette. If the error persists, make sure the disk drive is operating properly. See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network. If the drive functions correctly, contact the vendor of the NLM program for updates or fixes.1136: Invalid load file version.SERVERExplanation: The version number of the file to be loaded is incorrect.Action: Specify the name of a valid NetWare loadable file (probably an NLM program), or find out if the file has been corrupted. If the file is corrupted, get a new copy of the file.1143: Unable to unload module name (error number).SERVERExplanation: The NLM program could not be unloaded. The module may 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 program. 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.PAGENUM=1004 ID="BP998"1200: Number of supported frame types too big.SERVERExplanation: The driver passed in a number of supported media types to the operating system that exceeded the system's internal buffer limit of 32. The server may be using an outdated driver.Action: Make sure the driver is certified for NetWare 4 and is functioning properly. If the server has a current and functional driver and the problem persists, contact your Novell Authorized Reseller.1226: Board name is too long and was truncated: board_name.SERVERExplanation: The name for a network board can be no more than 17 characters long. You entered a name longer than 17 characters. The name was truncated to the name displayed in the message.Action: To enter a new name, unload the LAN driver and reload it with a name using 17 characters or fewer. Use the CONFIG server utility to display the current name.1249: Memory for auditing cannot be allocated. Volume name is being dismounted.SERVERExplanation: The operating system ran out of memory when it tried to start up auditing while mounting a volume.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.1250: Error writing to the audit file for volume: name.SERVERExplanation: The operating system encountered an error when trying to write to the audit file. The file system may be failing.Action: See"BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.1251: The audit file for volume name is full.SERVERExplanation: The operating system filled up the audit file when it wrote an audit record.Action: Use AUDITCON to reset the audit file, or increase the maximum size of the audit file. See "BOOK="utlrfenu" COLLECTION="nw41"AUDITCON" in Utilities Reference for more information.1258: The audit file for volume name has reached its overflow threshold.SERVERExplanation: The operating system encountered a warning threshold level for the volume when writing an audit record. The audit file is approaching the maximum size.Action: No immediate action is necessary. This is a warning message.PAGENUM=1005 ID="BP999"ID="FM54325"1301: Error reading filename.SERVERExplanation: The size or type of the NLM program being loaded could not be read. This error probably indicates a corrupted NLM program file.Action: Recopy the NLM program from the original disk and try again. If the problem persists, contact the vendor of the NLM program.1302: Error reading filename.SERVERAction: See message IDREF="FM54325""1301: Error reading filename."1305: Error reading filename.SERVERAction: See message IDREF="FM54325""1301: Error reading filename."1306: Error reading filename.SERVERAction: See message IDREF="FM54325""1301: Error reading filename."1307: Invalid packed NLM filename.SERVERExplanation: An NLM program that is not a File System Engine NLM program is too large to be loaded. Four megabytes is the maximum size allowed.Action: Do not try to load that NLM program.1308: Unable to allocate memory for NLM unpacking.SERVERExplanation: The operating system was unable to allocate memory for unpacking the NLM program because the operating system is out of memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.1310: Filename is not a packed NLM.SERVERExplanation: You are trying to load a file as an NLM program that is not packed as NLM programs should be. This file may not be an NLM program at all.Action: Make sure that the file the server is loading is really an NLM program. Replace it with a copy of the original if the server is still having problems.1311: This version of the loader doesn't support this NLM compression format (version version).SERVERExplanation: The operating system tried to load an NLM program that is in an unsupported compression format.Action: Make sure that any compressed NLM programs to be loaded are in compression format v1.10.PAGENUM=1006 ID="BP1000"1312: Filename has an invalid size.SERVERExplanation: This message reports when and how many incomplete packets were received. This problem can result from a defective network board, a malfunctioning LAN driver, or a problem with some other LAN hardware component.Action: See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.1316: Unable to allocate memory for data trees.SERVERExplanation: The operating system was unable to allocate memory for data trees because it is out of memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.1317: Invalid Shannon - Fano Tree.SERVERExplanation: While a packed NLM program was being unloaded, an error was found in the Shannon-Fano tree used to pack and unpack the NLM program.Action: None. This message is for information only.1318: Read past end of read buffer.SERVERExplanation: While an NLM program was being loaded, a read error occurred because the system did not recognize the end-of-file marker.Action: Try to reload the original NLM program. If the original NLM program file is corrupted, contact the vendor of the NLM program.1319: Error reading source file.SERVERExplanation: The operating system tried to load an NLM program, but the process failed. This error is caused by internal errors relating to the NLM program or to physical disk errors in the loading process.Action: This is a warning error. The NLM program is corrupted, or the disk system is faulty. Load a new copy of the NLM program from the master disk. If the NLM program is not at fault, check the disk system (cables, disk drive, and controller) for potential problems. See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network. If the server is still unable to load the NLM program, call the vendor of the NLM program for any fixes or updates.1320: Compression Maximum tree depth exceeded on free.SERVERExplanation: While an NLM program was being loaded, a read error occurred because the system did not recognize the end-of-file marker.Action: Try to reload the original NLM. If the original NLM program file is corrupted, contact the vendor of the NLM program.PAGENUM=1007 ID="BP1001"1321: Error reading load file.SERVERExplanation: The operating system tried to load an NLM program, but the process failed. This error is caused by internal errors relating to the NLM program or to physical disk errors in the loading process.Action: This is a warning error. The NLM program is corrupted, or the disk system is faulty. Load a new copy of the NLM program from the master diskette. If the NLM is not at fault, check the disk system (cables, disk drive, and controller) for potential problems. See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network. If the server is still unable to load the NLM program, call the vendor of the NLM program for any fixes or updates.1325: Username station number cleared. Connection terminated.SERVERExplanation: This message indicates that the user's connection was terminated.Action: None. This message is for information only.1343: Unable to register router tracking screen pause routine.SERVERExplanation: This message refers to the key input pause routine activated by using the TRACK ON command. For some reason, the routine cannot be executed.Action: None. This message is for information only. The operating system will continue operating normally.1344: Unable to unregister router tracking screen pause routine. SERVERExplanation: This message refers to the key input pause routine deactivated by using the TRACK OFF command. For some reason, the routine cannot be deactivated.Action: None. This message is for information only. The operating system will continue operating normally.1353: Drive deactivated by driver due to device failure.SERVERExplanation: This is a hardware error that usually generates other messages.Action: Look for other messages for additional information about the problem. See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.1354: Drive deactivated due to user request.SERVERExplanation: The specified drive was deactivated due to the user's request.Action: None. This message is for information only.PAGENUM=1008 ID="BP1002"1355: Drive deactivated due to media dismount.SERVERExplanation: The specified drive was deactivated.Action: None. This message is for information only.1356: Drive deactivated due to media eject.SERVERExplanation: The specified drive was deactivated.Action: None. This message is for information only.1357: Drive_name deactivated due to server down.SERVERExplanation: The specified drive was deactivated because the server went down.Action: None. This message is for information only.1358: Drive_name deactivated due to server failure.SERVERExplanation: The specified drive was deactivated because of a server failure.Action: None. This message is for information only.1365: Router configuration error detected. Node parameter claims network number should be number.SERVERExplanation: Packet routing cannot be completed. The BIND command issued to bind IPX to a LAN driver specified an incorrect network number. Other routers or servers on the network think that the cabling system has a different network number. Users may not be able to locate servers because of failed or improper routing of packets.Action: Unbind the LAN driver; then bind the LAN driver with the correct number displayed in the message. Reissue the BIND command at the system console using the network number shown in the alert message.Two or more servers will detect this condition. Set the network address correctly or the condition will recur.1375: Invalid message file.SERVERExplanation: The message file for an NLM program on the console was invalid. The server may be using an outdated version of the file.Action: Determine why the file is invalid and replace it with a valid file.1391: Username connection number cleared by user name on station number.SERVERExplanation: A user's connection was cleared by another user.Action: None. This message is for information only.PAGENUM=1009 ID="BP1003"1392: Down file server requested by user name station number.SERVERExplanation: The specified user issued a command to bring down the file server.Action: None. This message is for information only.1394: Unknown error (number) returned from file compress.SERVERExplanation: This is an internal consistency check done by compression to guarantee the integrity of the data being compressed. The file that was being compressed will remain uncompressed, and the system will try again later to compress it.Action: No immediate action is necessary. Note the volume number and watch for more of these same alerts. Also, watch for other errors indicating that the memory or disk is failing. If these alerts or other data corruption problems happen often on a particular volume, the disk or hardware supporting the disk should be repaired or replaced.ID="FM62280"1398: API name is not accessible from global code.SERVERExplanation: There is probably a programming error in the NLM program.Action: Contact the NLM program's vendor. The developer will have to fix the problem.1399: API name is not accessible from global code.SERVERAction: See message IDREF="FM62280""1398: API name is not accessible from global code."1400: Error unloading killed loadable module.SERVERExplanation: An error occurred while an NLM program was being unloaded. The NLM program is still loaded. A preceding message should explain why the module could not be unloaded.The error may have occurred because another module is still referencing public symbols or resources exported by this module. An NLM program 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 program was not unloaded. If necessary, unload the NLM program that is using this module's public symbols or resources; then unload this NLM program.1401: Invalid resource tag passed to ParseDriverParameters.SERVERExplanation: An NLM program 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 program.PAGENUM=1010 ID="BP1004"1413: Volume manager error. Volume name not mounted.SERVERExplanation: An error prevented the volume from being mounted.Action: Run VREPAIR. If the problem persists, make sure a volume backup exists. Delete the volume, recreate it using INSTALL, and restore the data from the backup.1415: Unknown error (number) returned from file decompress.SERVERExplanation: This is an internal consistency check done by decompression to guarantee the integrity of the data being decompressed. The file that was being decompressed will remain compressed, and the system will try again later to decompress it.Action: No immediate action is necessary. Note the volume number and watch for more of these same alerts. Also, watch for other errors indicating that the memory or disk is failing. If these alerts or other data corruption problems happen often on a particular volume, the disk or hardware supporting the disk should be repaired or replaced.1427: Unknown error (number) returned from decompress for file filename.SERVERExplanation: This is an internal consistency check done by decompression to guarantee the integrity of the data being decompressed. The file that was being decompressed will remain compressed, and the system will try again later to decompress it.Action: No immediate action is necessary. Note the volume number and watch for more of these same alerts. Also, watch for other errors indicating that the memory or disk is failing. If these alerts or other data corruption problems happen often on a particular volume, the disk or hardware supporting the disk should be repaired or replaced.1457: Insufficient RAM to decompress file name.SERVERExplanation: The system tried to allocate memory to decompress a file and failed. The file that was being decompressed will remain compressed, and the system will try again later to decompress it.Action: Wait until the server is less congested and try again. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.1459: Unable to open file "filename"; NLM not loaded.SERVERExplanation: The specified NLM program cannot be opened or cannot be found. The NLM is not loaded, or a wrong path was specified.Action: Make sure the NLM program is loaded and that you have specified the path correctly. Then try again.PAGENUM=1011 ID="BP1005"1460: Unable to open file "filename". Directory support NLM not loaded.SERVERExplanation: The operating system NLM program cannot be loaded. The SERVER.EXE file is corrupted or an outdated version.Action: Make sure the NLM program is the most current version. If you suspect corruption, reinstall the NLM program using a fresh copy from the original media CD-ROM or diskette.ID="FM73601"1483: Unable to read file "filename"; NLM not loaded.SERVERExplanation: The NLM program is corrupted, or the server is out of system resources.Action: Make sure the NLM program is the most current version. If you suspect corruption, reinstall the NLM program using a fresh copy from the original media CD-ROM or diskette. Increase the available memory. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.1485: Unable to read file "filename"; NLM not loaded.SERVERAction: See message IDREF="FM73601""1483: Unable to read file "filename"; NLM not loaded."1502: Could not create filename.SERVERExplanation: The core dump file could not be created on the specified path.Action: Make sure a valid path (including volume name) is specified. Make sure the user has appropriate user access rights to write to that path. Make sure that the disk is formatted properly. If the file already exists, make sure it is not write-protected. If the file exists and other measures fail, delete the file.1509: File filename has an invalid NLM type; NLM not loaded.SERVERExplanation: The file has an .NLM as an extension, but it is not a valid NLM program.Action: Verify the NLM program against the original CD-ROM or diskette.1511: Invalid filename being loaded.SERVERExplanation: This is a warning. The portion of the header that contains the name of the NLM program has become corrupted. The NLM program tried to pass (to the system) a filename that was zero characters or greater than 12 characters long. The NLM program may have been damaged by the manufacturer, or the disk drive may be malfunctioning.Action: Reload the NLM program from the master disks, or fix any faulty hardware. See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network. If the error persists, contact the vendor of the NLM program for updates or fixes.PAGENUM=1012 ID="BP1006"1512: Invalid load file format.SERVERExplanation: The description text field of an NLM program was invalid. This field should contain text (about the NLM program) that is greater than zero and less than 128 characters long. The NLM program in this case did not meet these criteria. This problem is due to manufacturer error, NLM program corruption, or disk malfunction.Action: Reload the NLM program from the master diskettes. If the error persists, make sure that the disk drive is operating properly. See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network. If the drive functions correctly, contact the vendor of the NLM program for updates or fixes.1514: Invalid procedure offsets within load file.SERVERExplanation: Values within the load file header for a particular NLM program 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 program or a faulty disk system. Reload the NLM program from the master CD-ROM or diskette, and check the disk system for potential problems. See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.1515: RIP socket was open when router was trying to open the RIP socket.SERVERExplanation: Before the Loader was ready to load, another NLM program had already opened the RIP socket used by IPX. The offending NLM program may be an unlicensed version.Action: None. This message is for information only. The loader will automatically override the offending NLM program. However, if the problem persists, bring down the server and bring it back up without the offending NLM program.1516: Router configuration error detected. Router at node parameter claims network correct_number should be incorrect_number.SERVERExplanation: Packet routing cannot be completed. The BIND command issued to bind IPX to a LAN driver specified an incorrect network number. Other bridges or servers on the network think that the cabling system has a different network number. Users may not be able to locate servers because of failed or improper routing of packets.Action: Unbind the LAN driver; then bind the LAN driver with the correct number displayed in the message. Reissue the BIND command at the system console using the network number shown in the message.PAGENUM=1013 ID="BP1007"1517: LAN driver loopback error detected. Driver for network number received its own send packet.SERVERExplanation: Packets have been transmitted incorrectly. The installed LAN driver is sending packets to itself. This error indicates a potential software problem in the LAN driver.Action: Contact the LAN driver's vendor for assistance.1538: Volume name DOS Type (number) does not match the file server DOS Type (number).SERVERExplanation: Different language types can be specified for the file system by the LCONFIG.SYS file. The default is English. After upgrading the system, you tried to remount a volume that had a previously specified language type different from the language type the server is now using. If you do not change the language for the volume, this error occurs.Action: If you are using a language type other than English, make sure that the LCONFIG.SYS and SERVER.MSG are both in the server's boot directory.If you are trying to change from one of the other languages to English, you may get errors that need to be fixed by running VREPAIR.1542: Could not create filename.SERVERExplanation: The core dump file could not be created on the specified path.Action: Make sure a valid path (including volume name) is specified. Make sure the user has appropriate user access rights to that path. Make sure that the disk is formatted properly. If the file already exists, make sure it is not write-protected. If the file exists and other measures fail, delete the file.1545: Insufficient memory to load NLM.SERVERExplanation: The server does not have enough memory to load a given NLM program.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.1546: Invalid record in load file.SERVERExplanation: The operating system tried to load an NLM program that had invalid code or data segments.Action: Relink the NLM program. If the problem persists, contact your Novell Authorized Reseller or the vendor of the NLM program.PAGENUM=1014 ID="BP1008"1547: Error reading load file.SERVERExplanation: The operating system tried to load an NLM program, but the process failed. This error is probably caused by internal errors relating to the NLM program or to physical disk errors in the loading process.Action: This is a warning error. The NLM program is corrupted, or the disk system is faulty. Load a new copy of the NLM program from the master diskette. If the NLM program is not at fault, check the disk system (cables, disk drive, and controller) for potential problems. See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network. If the server is still unable to load the NLM program, call the vendor of the NLM program for any fixes or updates.1548: Load file referenced undefined public variable.SERVERExplanation: The loader could not find the module's public symbol name in the Public Symbol table.Action: Complete one of the following:MARK=BULLETIf you are a user, see the documentation for the NLM program. 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.1549: Load file contains invalid public variable name.SERVERExplanation: The public variable name in the NLM program's file header had a zero-character length. The name field can store up to 256 characters. This message indicates a corrupted NLM program.Action: Reload the NLM program from the master diskette. If this does not correct the problem, contact the vendor of the NLM program.1550: Load file defines a public variable that has already been defined.SERVERExplanation: While the system was loading an NLM program, it found that one or more of the module's public variables had been defined previously. An NLM program cannot use a previously defined public variable, because system integrity could be compromised. This error is not fatal. The NLM program will continue to load until all previously defined symbols have been listed to screen. The NLM program will then be unloaded and all resources will be returned to the operating system.Action: Contact the vendor of the NLM program about updates or patches.PAGENUM=1015 ID="BP1009"1551: Public variables exported by this auto load file have already been defined.SERVERExplanation: An NLM program is trying to auto-load another NLM program that is exporting public variables that are already present.Action: Make sure that each of the NLM programs is the correct version for the other NLM program and that they are compatible with the operating system.1553: Module initialization failed.SERVERExplanation: 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.1554: Invalid public record offset in load file.SERVERExplanation: This error indicates a corrupted NLM program or a faulty disk system.Action: Reload the NLM program from the master CD-ROM or diskette, and check the disk system for potential problems. See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.1555: Unable to load the message support files.SERVERExplanation: An error occurred when the operating system tried to load the message and help files for an NLM program it was loading.Action: None. This message is for information only.1556: Error processing cross domain call data.SERVERExplanation: The loader asked the DOMAIN.NLM to process data from an RPC (Remote Procedure Call), and DOMAIN returned an error indicating that the data was invalid. This message is issued by the loader, and follows a message issued by DOMAIN that specifies the specific error that occurred.Action: Refer to the message preceding this one for specific error information.ID="FM54456"1557: API name is not accessible from domain name.SERVERExplanation: The API that the loading NLM program is trying to use is not available through the selected domain.Action: Switch to the correct domain. For information on using the DOMAIN.NLM, see "BOOK="utlrfenu" COLLECTION="nw41"Domain" in Utilities Reference.1558: API name is not accessible from domain name.SERVERAction: See message IDREF="FM54456""1557: API name is not accessible from domain name."PAGENUM=1016 ID="BP1010"1559: Module is using old API: API_name.SERVERExplanation: While the NLM program was being loaded, its public records were checked. The records indicated that NetWare 3.11 operating system's application programming interfaces (APIs) were emulated by the NLM program. This is a warning message. The NLM program will still function.Action: Even though this message is a warning and is not fatal, the NLM programs in question should be upgraded to the latest version of NetWare.1563: Router configuration error detected. Another router is claiming the same Internet address.SERVERExplanation: Packet routing cannot be completed. This error occurs when an incorrect network number is issued by the BIND command to an IPX LAN driver. Another router claims to have the same network and node address as one of the network boards in this router. This is a configuration error and may cause network errors. Users may not be able to locate servers because of failed or improper routing of packets.Action: Find out which board has the incorrect network and node addresses; then change the configuration. Reissue the BIND command at the system console using the network number shown in the message.1565: IPX local network number removed because LAN board is unreachable.SERVERExplanation: This server no longer uses the designated network. No network traffic can be sent by or received from the designated network board.Action: Try one or more of the following:MARK=BULLETIf the driver was unloaded with UNLOAD, no action is required.Try to bring the network board back on line by loading its driver.If this fails, run the manufacturer's diagnostics to determine the operational status of the network board.1574: Needed support modules are not present.SERVERExplanation: The server is trying to load an NLM program 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 program to operate properly.Action: Make sure that the required modules are loaded before loading the current NLM program.PAGENUM=1017 ID="BP1011"1586: Loader cannot find public symbol: required_symbol.SERVERExplanation: When an NLM program is loaded, it links itself to the operating system. One reason it does this is so that it can share common variables with the system and with other linked NLM programs. If the NLM program is outdated, this message appears and lists all unresolved external public variables.Action: Obtain an updated version of the NLM program and try again.1587: This module is using one outdated API call. You should upgrade to a newer module when it becomes available.SERVERExplanation: The operating system displays this message whenever an NLM program is loaded that is using old API calls. NetWare 4 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 APIs work; however, they are slower than the new APIs.Action: Contact the vendor of the NLM program for an updated version using NetWare 4 APIs. Continue to use the version until you receive the newer version.1590: Symbol already defined: symbol.SERVERExplanation: An NLM program is trying to auto-load another NLM program that is exporting public variables that have already been loaded. The server may be trying to use NLM programs that are incompatible versions.Action: Make sure the NLM program versions are compatible with each other and with the operating system.1600: Unable to load module messages in preferred language; the default language will be used.SERVERExplanation: While loading an NLM program 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.Action: None. This message is for information only. If the error persists, change the preferred language.PAGENUM=1018 ID="BP1012"1601: Unable to load module help in preferred language; the default language will be used.SERVERExplanation: While loading an NLM program, 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.Action: None. This message is for information only. If this error persists, change the preferred language.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.SERVERExplanation: An NLM program 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 program.If this NLM program is from a vendor other than Novell, try loading the NLM program using the following command line syntax:FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD NLM (CLIB_OPT)/Y This syntax causes the NLM program to use a different method of yielding CPU calls (using a "handicapped queue") that allows priority threads to run.1631: The mirrored partitions on this system are not all synchronized.SERVERExplanation: During remirroring, one device was found to be out of sync. Until all of the mirrors are synchronized, single device or network board failure can cause file service disruption.Action: None. This message is for information only.1642: Attempt to allocate memory to hold NetWare partition information failed. SERVERExplanation: The server does not have enough memory to hold partition information.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.ID="FM98032"1644: Allow unowned files to be extended.SERVERExplanation: The server does not have enough memory to mount the volume.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.PAGENUM=1019 ID="BP1013"1645: Attempt to allocate memory to read volume definition tables failed.SERVERExplanation: The server does not have enough memory to mount the volume.Action: See message IDREF="FM98032""1644: Allow unowned files to be extended."1646: Control whether or not an unowned file can be extended.SERVERAction: See message IDREF="FM98032""1644: Allow unowned files to be extended."1649: Volume name could NOT be mounted. Some or all volume segments cannot be locatedSERVERExplanation: The volume specified in the MOUNT command could not be mounted. The volume has segments on more than one hard disk, and at least one of the hard disks is not responding.Action: Make sure all disk drivers have been loaded. See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.1652: Unable to read volume definition table from NetWare partition on drive.SERVERExplanation: The volume definition table on the specified drive could not be read because of a disk error. Consequently, the volume could not be mounted.Action: Check the disk drive and the cable. See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.1656: Volume definition table mirror mismatch on drive. NetWare partition ignored.SERVERExplanation: Four copies of the Volume Segment Definition table are kept on each NetWare partition. This error indicates that these copies do not match.Action: Run the INSTALL program and select "Volume Options."1657: Block allocation size does not match.SERVERExplanation: Two segments of the volume claim different block allocation sizes. This error could be caused by one of the following:MARK=BULLETTwo volumes on the server have identical names, and a segment from each volume is causing the error.The volume is corrupted.Action: If you have two volumes with the same name, unload the disk driver for the volume that you do not want to rename. Rename the other volume (the volume that is on the hard disk that still has its disk driver loaded). Then load the disk driver that you just unloaded. Mount both volumes.PAGENUM=1020 ID="BP1014"If the volume is corrupted, run VREPAIR. 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, recreate it using INSTALL, and restore the data from the backup.1658: Number of segments in the volume does not match.SERVERExplanation: Two segments of the volume claim different numbers of segments. This error could occur for one of the following reasons:MARK=BULLETTwo volumes on the server have identical names and a segment from each volume is causing the error.The volume is corrupted.Action: If you have two volumes with the same name, unload the disk driver for the volume that you do not want to rename. Rename the other volume (the volume that is on the hard disk that still has its disk driver loaded). Then load the disk driver that you just unloaded. Mount both volumes.If the volume is corrupted, run VREPAIR. 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, recreate it using INSTALL, and restore the data from the backup.1712: Volume flags do not match.SERVERExplanation: Two segments of the volume claim that the volume has different flags. This error could occur for one of the following reasons:MARK=BULLETTwo volumes on the server have identical names and a segment from each volume is causing the error.The volume is corrupted.Action: If you have two volumes with the same name, unload the disk driver for the volume that you do not want to rename. Rename the other volume (the volume that is on the hard disk that still has its disk driver loaded). Then load the disk driver that you just unloaded. Mount both volumes.If the volume is corrupted, run the INSTALL program and select "Volume Options." PAGENUM=1021 ID="BP1015"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, recreate it using INSTALL, and restore the data from the backup.1713: Total volume size does not match.SERVERExplanation: Two segments of the volume claim different numbers of segments. This error can occur for one of the following reasons:MARK=BULLETTwo volumes on the server have identical names and a segment from each volume is causing the error.The volume is corrupted.Action: If you have two volumes with the same name, unload the disk driver for the volume that you do not want to rename. Rename the other volume (the volume that is on the hard disk that still has its disk driver loaded). Then load the disk driver that you just unloaded. Mount both volumes.If the volume is corrupted, run VREPAIR.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, recreate it using INSTALL, and restore the data from the backup.1714: First block for FAT table 0 does not match.SERVERExplanation: A File Allocation Table (FAT) is an index to one or more disk allocation blocks in which a file is located. Two segments of the volume claim a different File Allocation Table 0's (or 1's) first block. This error could be caused by one of the following:MARK=BULLETTwo volumes mounted on the server have identical names and a segment from each volume is causing the error.The volume is corrupted.Action: If you have two volumes with the same name, unload the disk driver for the volume that you do not want to rename. Use INSTALL to rename the other volume (the volume that is on the hard disk that still has its disk driver loaded). Then load the disk driver that you just unloaded. Mount both volumes.If the volume is corrupted, run VREPAIR. Warning: If you delete the volume, all data will be destroyed. You will have to restore the data from a backup.PAGENUM=1022 ID="BP1016"If the problem persists, make sure a volume backup exists. Delete the volume, recreate it using INSTALL, and restore the data from the backup.1715: First block for FAT table 1 does not match.SERVERExplanation: A File Allocation Table (FAT) is an index to one or more disk allocation blocks in which a file is located. Two segments of the volume claim a different File Allocation Table 0's (or 1's) first block. This error could be caused by one of the following:MARK=BULLETTwo volumes mounted on the server have identical names and a segment from each volume is causing the error.The volume is corrupted.Action: If you have two volumes with the same name, unload the disk driver for the volume that you do not want to rename. Use INSTALL to rename the other volume (the volume that is on the hard disk that still has its disk driver loaded). Then load the disk driver that you just unloaded. Mount both volumes.If the volume is corrupted, run VREPAIR. 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, recreate it using INSTALL, and restore the data from the backup.1716: First block for directory table 0 does not match.SERVERExplanation: Two segments of the volume claim a different directory table zero's first block. This error could be caused by one of the following:MARK=BULLETTwo volumes mounted on the server have identical names and a segment from each volume is causing the error.The volume is corrupted.Action: If you have two volumes with the same name, unload the disk driver for the volume that you do not want to rename. Rename the other volume (the volume that is on the hard disk that still has its disk driver loaded). Then load the disk driver that you just unloaded. Mount both volumes.If the volume is corrupted, run VREPAIR. 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, recreate it using INSTALL, and restore the data from the backup.PAGENUM=1023 ID="BP1017"1717: First block for directory table 1 does not match.SERVERExplanation: Two segments of the volume claim a different directory table one's first block. This error could be caused by one of the following:MARK=BULLETTwo volumes mounted on the server have identical names and a segment from each volume is causing the error.The volume is corrupted.Action: If you have two volumes with the same name, unload the disk driver for the volume that you do not want to rename. Rename the other volume (the volume that is on the hard disk that still has its disk driver loaded). Then load the disk driver that you just unloaded. Mount both volumes.If the volume is corrupted, run VREPAIR. 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, recreate it using INSTALL, and restore the data from the backup.1718: Volume segment entry number on drive is invalid:SERVERExplanation: An entry in the Volume Segment table is invalid. You may receive this message for one of the following reasons.MARK=BULLETThe Volume Segment table is corrupted.The Volume Segment table does not have a volume name.The volume name is illegal.The block allocation size is illegal.One of the other entry fields is illegal.Another message should follow this message. It will indicate which field is illegal. The segment will not be added to the volume tables. If the segment is needed for mounting the volume, then the volume will not be mounted.Action: Run INSTALL and select "Volume Options."PAGENUM=1024 ID="BP1018"1720: Two volume segments with same sync value have mismatched data.SERVERExplanation: The values specified by two segments on the volume do not match. Another message should follow this message to indicate which values do not match.Action: Run VREPAIR. 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, recreate it using INSTALL, and restore the data from the backup.1721: Volume has no volume name.SERVERExplanation: The MOUNT or DISMOUNT command was issued, but the volume name was not specified.Action: Specify a volume name.1722: Volume name name is too short.SERVERExplanation: A volume name must be at least two characters long.Action: Make sure that you typed a valid volume name in the MOUNT console command and that you spelled it correctly.1723: Invalid block allocation size number.SERVERExplanation: During an attempt to mount a volume, the operating system determined that the volume contained an invalid allocation size.Action: Run INSTALL and select "Volume Options" to ensure that the allocation size is correct. Be careful not to reinitialize the volume unless that is what you want to do.1724: Invalid number of volume segments number.SERVERExplanation: During an attempt to mount a volume, the operating system determined that the volume contained too many segments (there is an eight segment limit).Action: Run VREPAIR. 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, recreate it using INSTALL, and restore the data from the backup.PAGENUM=1025 ID="BP1019"1725: Invalid volume segment position of position_number of number segments.SERVERExplanation: The segment position is greater than the number of segments.Action: Run VREPAIR. 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, recreate it using INSTALL, and restore the data from the backup.1726: Invalid starting sector offset of number on a drive of size number.SERVERExplanation: The offset of the starting sector of a partition is greater than the size of the partition.Action: Run VREPAIR. 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, recreate it using INSTALL, and restore the data from the backup.1727: Invalid starting sector offset of number.SERVERExplanation: The offset of the starting sector is invalid. The sector is probably corrupted.Action: Run VREPAIR. 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, recreate it using INSTALL, and restore the data from the backup.1728: Invalid segment length of number starting at number on a drive of size number.SERVERExplanation: A segment of a partition has too many sectors or has sectors that exceed allowable size. The segment is probably corrupted.Action: Run VREPAIR. 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, recreate it using INSTALL, and restore the data from the backup.PAGENUM=1026 ID="BP1020"1729: Invalid FAT table 0 starting block of number on volume of size number.SERVERExplanation: A File Allocation Table (FAT) is an index to one or more disk allocation blocks in which a file is located. The FAT table on this volume has an invalid table zero starting block. The table is probably corrupted.Action: Run VREPAIR. 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, recreate it using INSTALL, and restore the data from the backup.1730: Invalid FAT table 1 starting block of number on volume of size number.SERVERExplanation: A File Allocation Table (FAT) is an index to one or more disk allocation blocks in which a file is located. The FAT table on this volume has an invalid table one starting block. The table is probably corrupted.Action: Run VREPAIR. 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, recreate it using INSTALL, and restore the data from the backup.1731: Invalid directory table 0 starting block of number on volume of size number.SERVERExplanation: A segment on the primary volume has an inconsistency in the starting point of the directory table of block pointers. The table is probably corrupted.Action: Run VREPAIR on the primary volume. 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, recreate it using INSTALL, and restore the data from the backup.1732: Invalid directory table 1 starting block of number on volume of size number.SERVERExplanation: A segment on the mirrored volume has an inconsistency in the starting point of the directory table of block pointers.Action: Run VREPAIR on the mirrored volume. Warning: If you delete the volume, all data will be destroyed. You will have to restore the data from a backup.PAGENUM=1027 ID="BP1021"If the problem persists, make sure a volume backup exists. Delete the volume, recreate it using INSTALL, and restore the data from the backup.1733: Reserved area is not zero filled.SERVERExplanation: While mounting a volume, the operating system found that the reserved area of a segment definition was not zero-filled as it should be. Therefore, the segment was not included in the volume definition table.Action: Run VREPAIR. 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, recreate it using INSTALL, and restore the data from the backup.1734: Volume name has multiple sync definitions. All definitions except number discarded.SERVERExplanation: While checking a volume definition during mounting of the volume, the operating system discarded all unneeded synchronization values.Action: None. This message is for information only.1735: Volume name has multiple definitions for segment number.SERVERExplanation: While mounting a volume, the operating system found multiple definitions for the specified segment, indicating that the current synchronization value is invalid. The operating system will discard the invalid synchronization value.Action: None. This message is for information only.1736: Volume name is missing segment number.SERVERExplanation: While checking a volume definition during mounting of the volume, the operating system found that a segment was missing. Segments are consecutively numbered.Action: None. This message is for information only. If the problem persists, contact your Novell Authorized Reseller.1737: Volume name segment number ends at block number and segment number starts at block number.SERVERExplanation: The volume segments are not contiguous.Action: Back up all data before troubleshooting the problem. Make sure that the operating system can recognize all disks over which the volume is distributed and that none have been corrupted. Run VREPAIR. PAGENUM=1028 ID="BP1022"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, recreate it using INSTALL, and restore the data from the backup.1742: Aborted remirror of partition number.SERVERExplanation: The system found the remirroring process to be out of synchronization due to hardware failure. The designated partition cannot be mirrored. Data integrity may be lost for the volumes that reside on the designated partition.The operating system supports the partition as an unmirrored device. This error may have been caused by a hard disk or channel failure. Another possibility is that the directory was corrupted.Action: See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network. Also see "BOOK="cncptenu" COLLECTION="nw41"Device numbering" in Concepts.1745: Logical Partition number has mirror inconsistencies.SERVERExplanation: The indicated logical partition contains inconsistent data across the physical partitions that it spans; disk mirroring and duplexing are no longer active for this partition. Data integrity after remirroring cannot be guaranteed.Synchronization probably failed because of Hot Fix failure (all the redirection blocks on one of the disks are full), hardware failure, or device deactivation.Action: See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.1757: Error opening or creating TTS$LOG.ERR file.SERVERExplanation: The Transaction Tracking System (TTS) could not open or create the TTS$LOG.ERR file, which is a file containing a history of what TTS has done. The volume may be running out of disk or directory space.Action: Erase or purge unnecessary files, or add more disk space to the volume containing the TTS files. See"BOOK="superenu" COLLECTION="nw41"Resolving Server Disk Space Problems" in Supervising the Network.1761: Error writing to TTS$LOG.ERR file.SERVERExplanation: A Transaction Tracking System (TTS) error could not be logged in the TTS error log file. The volume is probably out of space.Action: Add more disk space to the volume containing the TTS files. See"BOOK="superenu" COLLECTION="nw41"Resolving Server Disk Space Problems" in Supervising the Network.PAGENUM=1029 ID="BP1023"1808: 1 Incomplete Transaction Found. Last record was written at date_and_time.SERVERExplanation: TTS found an incomplete transaction. "Begin TTS" was called without a subsequent ABORT or END.Action: None. This message is for information only.1814: Transactions will be backed out and not displayed or logged.SERVERExplanation: Transactions will be backed out, and they will not be displayed or logged.Action: None. This message is for information only.1820: Error opening file referenced by the backout file on volume name; file was deleted.SERVERExplanation: The referenced file has been deleted before the Transaction Tracking System (TTS) could open it to back it out.Action: None. This message is for information only.1823: Error opening file for backout. Completion code = code.SERVERExplanation: This is probably a hardware error.Action: See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 1825: File has been changed (at time) since this backout file ended (at time).SERVERExplanation: The file has changed since it was backed out.Action: None. This message is for information only.1828: Error reading original data.SERVERExplanation: This error may indicate hardware failure or a corrupted Transaction Tracking System (TTS) backout file.Action: See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network. If you suspect file corruption, delete the corrupted file and replace it with a backup.1829: Record data in the file before the backout.SERVERExplanation: The record data was in the file before it was backed out.Action: None. This message is for information only.PAGENUM=1030 ID="BP1024"1830: Original record data from the backout file (being written back to the file).SERVERExplanation: The original record data from the backout file is being written back to the file.Action: None. This message is for information only.1835: Error opening file referenced by the backout file on volume name; file was deleted.SERVERExplanation: The referenced file was deleted before the Transaction Tracking System (TTS) could open it to back it out.Action: None. This message is for information only.1836: Backout information for transaction number (original write occurred at time).SERVERExplanation: This message is displaying the backout information for the transaction indicated.Action: None. This message is for information only.1838: Error opening file for backout. Completion code = code.SERVERExplanation: This is probably a hardware error.Action: See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A 1839: File has been changed (at time) since this backout file ended (at time).SERVERExplanation: The file has changed since it was backed out.Action: None. This message is for information only.1855: Attempt to unbind protocol_name LAN protocol from board_name failed. (error=number)SERVERExplanation: Another message should appear before this one, indicating what went wrong during the BIND (or UNBIND) process. This error usually occurs when the protocol was not bound in the first place.Action: Ensure that you are unbinding the correct protocol. Look up the message that appeared before this message for additional help.1867: Compressed file name is corrupted and unrecoverable.SERVERPAGENUM=1031 ID="BP1025"Explanation: The compressed file has been corrupted on the disk. During decompression, the integrity of the data describing the compressed file is checked. If any of the checks fail, data corruption is assumed, and compression cannot be completed, as is the case here. This error can only be caused by the data changing on the disk. Changed data can result from one of the following causes:MARK=BULLETMagnetic or electronic media close to the disk driveFailure of the disk drive or supporting hardwareIf the disk drive is failing, other files will be corrupted and will not contain the original data.Action: Try restoring the file from an earlier backup. If you cannot restore the data from a backup, the file is lost. See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.1868: Compressed file name in use by station number is corrupted and unrecoverable.SERVERExplanation: The first block of the compressed file has been corrupted on the disk. During decompression, the integrity of the data describing the compressed file is checked. If any of the checks fail, data corruption is assumed, and compression cannot be completed, as is the case here. This error can only be caused by the data changing on the disk. Changed data can result from one of the following causes:MARK=BULLETMagnetic or electronic media close to the disk driveFailure of the disk drive or supporting hardwareIf the disk drive is failing, other files will be corrupted and will not contain the original data.Action: Try restoring the file from an earlier backup. If you cannot restore the data from a backup, the file is lost. See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.1929: Protocol ID could NOT be registered (error number).SERVERExplanation: The PROTOCOLS REGISTER command was used to register a new protocol ID number, but the number could not be registered because of an error.Action: Another message should be displayed before this message to indicate why the command failed. Correct the problem accordingly.1942: Unable to find load file filename.SERVERExplanation: The specified load file could not be found. Perhaps the file is not in the specified directory or 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.PAGENUM=1032 ID="BP1026"1944: Hole In File Restored To Offset offset.SERVERExplanation: This message indicates that a hole in the file has been restored to the indicated offset. (A hole is a section that is not sequential.)Action: None. This message is for information only.1948: Unable to find load file filename.SERVERExplanation: 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: Check the spelling and extension of the file. Make sure the file exists in the directory.ID="FM14525"1949: Error reading from load file.SERVERExplanation: The NLM program is not readable. A disk error occurred, or the NLM program is corrupted.Action: Get a new copy of the NLM program, or replace the disk.1952: Error reading from load file.SERVERAction: See message IDREF="FM14525""1949: Error reading from load file."1954: Invalid load file format.SERVERExplanation: The description text field of an NLM program was invalid. This field should contain text (about the NLM program) that is greater than zero and less than 128 characters long. The NLM program in this case did not meet these criteria. This problem is due to manufacturer error, NLM program corruption, or disk malfunction.Action: Reload the NLM program from the master diskettes. If the error persists, make sure that the disk drive is operating properly. See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network. If the drive functions correctly, contact the vendor of the NLM program for updates or fixes.1955: Invalid load file version.SERVERExplanation: The version number of the file to be loaded is incorrect.Action: Specify the name of a valid NetWare loadable file, or find out if the file has been corrupted. If the file is corrupted, get a new copy of the file.PAGENUM=1033 ID="BP1027"1956: Module name is name not name.SERVERExplanation: The NLM program file has been renamed to the second name shown. The operating system will use this second name when displaying modules that are currently loaded.However, the original name (the first name shown) is coded into the NLM program. This prevents users from loading a renamed NLM program more times than the module allows. Because the NLM program is aware of its original name, it can monitor the number of times it is loaded and prevent users from loading it more than the allowable number of times.Action: None. This message is for information only.1957: Attempt to reinitialize reentrant module FAILED.SERVERExplanation: The LOAD command was used to load an NLM program that has already been loaded. As a result, the existing code image was used reentrantly. An error occurred while the operating system was reinitialize the module.Action: Complete one or more of the following:MARK=BULLETCheck the configuration information given on the command line. The hardware configuration information specified for the second LOAD command may have been invalid.Check the hardware. Make sure the network board is properly seated. The hardware may not be responding. See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.1961: Incomplete transactions referencing unmounted volumes were preserved.SERVERExplanation: Not all of the volumes are mounted yet, so the Transaction Tracking System (TTS) backout file is being saved. An incomplete transaction occurred on one of these unmounted volumes.Action: None. This message is for information only.1972: Error opening backout file.SERVERExplanation: This error could indicate a hardware failure, or a corrupted Transaction Tracking System (TTS) backout file.Action: See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network. If you suspect file corruption, make sure a file backup exists.Warning: If you delete the file, all data will be destroyed. You will have to restore the data from a backup.Delete the corrupted file and replace it with a backup.PAGENUM=1034 ID="BP1028"1976: TTS disabled by operator.SERVERExplanation: Someone issued the DISABLE TTS command from the server's console.Action: None. This message is for information only. This message is generated to the screen, and to the TTS$LOG.ERR file, just for a chronological record of when TTS was disabled, and to indicate that it was disabled by the operator rather than by TTS itself (as is the case when the TTS runs out of disk space).1977: TTS disabled because of error reading backout file.SERVERExplanation: The Transaction Tracking System (TTS) could not read the backout file. TTS was disabled because it could not reliably back out any transactions. TTS protection is gone, but completed transactions are intact.Action: None. This message is for information only. You may continue without TTS protection.1978: TTS disabled because of error writing to file during backout.SERVERExplanation: The Transaction Tracking System (TTS) had a problem writing to the actual database for which it was backing out transactions, so it disabled itself to prevent further problems. The database is probably corrupted.Action: Try to determine whether the database application can read the database. Some database programs have recovery utilities that can detect and repair corruption.1979: TTS disabled because of too many defined volumes.SERVERExplanation: The Transaction Tracking System (TTS) can track transactions on only a certain number of volumes. This number has been exceeded.Action: Combine volumes so that the number is within the limit set by TTS.1980: TTS disabled because of error writing volume definition information.SERVERExplanation: This error could indicate hardware failure.Action: See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.1981: TTS disabled because of error reading backout file during record generation.SERVERExplanation: The Transaction Tracking System (TTS) may have disabled itself because it failed to generate records to be written to a file. This failure occurred when TTS could not read the backout file for some reason. The problem could be a hardware failure, a power failure, or a corrupted file.Action: See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network. If you suspect file corruption, delete the file and restore from a backup.PAGENUM=1035 ID="BP1029"1982: TTS disabled because of error growing TTS memory tables.SERVERExplanation: The server may not have enough memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.1983: TTS disabled because of error allocating more disk space for the backout file.SERVERExplanation: The backout volume is full.Action: Try adding another drive to the backout volume, deleting or compressing existing files on the backout volume, or moving files from the backout volume to another volume. (Increasing disk space on volumes other than the backout volume will not help.)1984: TTS disabled because of directory error on TTS backout file.SERVERExplanation: There is not enough memory space available on the volume for the directory.Action: Increase the percentage of volume space that can be used by the directory.ID="FM72029"1987: TTS cannot allocate sufficient memory.SERVERExplanation: The server may not have enough memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.1989: TTS cannot allocate sufficient memory.SERVERAction: See message IDREF="FM72029""1987: TTS cannot allocate sufficient memory."1990: TTS cannot allocate sufficient memory.SERVERAction: See message IDREF="FM72029""1987: TTS cannot allocate sufficient memory."1993: Error renaming old TTS backout file.SERVERExplanation: This could be a hardware error.Action: See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.1996: Error creating TTS backout file.SERVERExplanation: The volume may not have enough space to create the Transaction Tracking System (TTS) backout file.Action: Try adding another drive to the backout volume, deleting or compressing existing files on the backout volume, or moving files from the backout volume to another volume. (Increasing disk space on volumes other than the backout volume probably will not help.)PAGENUM=1036 ID="BP1030"1998: Error hiding TTS backout file.SERVERExplanation: A hardware error occurred before the volume was mounted.Action: See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.1999: Error writing volume name information to TTS backout file.SERVERExplanation: A hardware error occurred.Action: See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.2000: Error writing header information to TTS backout file.SERVERExplanation: A hardware error occurred.Action: See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.2002: Error manipulating the TTS backout file.SERVERExplanation: A hardware error occurred.Action: See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.2003: Station connection_number attempted to use an unencrypted password call.SERVERExplanation: The indicated station could not log in. An application or utility tried to log in, verify a password, or change a password without first encrypting the password. The server is configured to accept only encrypted passwords.Action: Try one or more of the following:MARK=BULLETReplace the application or utility with one that encrypts passwords when making calls to log in, verify, or change passwords. If the utility is a NetWare 2.x utility, replace it with a NetWare 3.x or 4.0 utility.Use the SET server utility's "Allow Unencrypted Passwords" parameter to configure the server to accept unencrypted passwords.2005: TTS cannot allocate memory to do the transaction backouts.SERVERExplanation: The server may not have enough memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.PAGENUM=1037 ID="BP1031"2006: TTS not initialized.SERVERExplanation: The message notifies you that TTS has not initialized.Action: No action is necessary unless you want to initialize transaction tracking. For more information on initializing transaction tracking, see "BOOK="utlrfenu" COLLECTION="nw41"SETTTS" in Utilities Reference.2007: TTS has been shut down.SERVERExplanation: The message notifies you that TTS has been shut down.Action: No action is necessary unless you want to initialize transaction tracking. See "BOOK="utlrfenu" COLLECTION="nw41"SETTTS" in Utilities Reference for more information.2009: Server TTS shut down because backout volume name was dismounted.SERVERExplanation: The message is an alert to create a chronological history for troubleshooting. The Transaction Tracking System (TTS) is automatically disabled when the backout volume is dismounted.Action: None. This message is for information only.2016: Disable TTS requested by user name on station number.SERVERExplanation: The message indicates that the user issued a DISABLE Transaction Tracking System (TTS) request.Action: None. This message is for information only.2021: Enable TTS requested by user name on station number.SERVERExplanation: The user indicated in the message issued an ENABLE Transaction Tracking System (TTS) request.Action: None. This message is for information only.2024: Transaction tracking system enabled.SERVERExplanation: The message indicates that the Transaction Tracking System (TTS) has been enabled.Action: None. This message is for information only.PAGENUM=1038 ID="BP1032"ID="FM32175"2026: Transaction aborted for station number task number.SERVERExplanation: Due to a CLEAR STATION command, or some other external connection, the transaction was aborted and backed out.Action: Use the SET server utility's "TTS Abort Dump Flag" parameter to dump backouts to the TTS$ERR.LOG file; then you can see what the user was working on and when it was changed.2028: Transaction aborted for station number task number.SERVERAction: See message IDREF="FM32175""2026: Transaction aborted for station number task number."2029: Abort transaction attempted on station number and could not occur because transactions were disabled.SERVERExplanation: A station requested an "abort transaction" when TTS was not enabled.Action: Determine why TTS is disabled. A preceding message will indicate whether the operating system disabled TTS on its own. Otherwise, "disable TTS" may have been entered at the system console.2030: Abort transaction attempted on station number and could not occur because transactions were disabled.SERVERAction: See message IDREF="FM32175""2026: Transaction aborted for station number task number."2031: Backout information for transaction aborted by station number.SERVERExplanation: The backout information for the transaction was aborted by the station indicated in the message.Action: None. This message is for information only.2037: Error reading original data.SERVERExplanation: This error may indicate hardware failure or a corrupted Transaction Tracking System (TTS) backout file.Action: See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network. If you suspect file corruption, delete the corrupted file and replace it with a backup.2038: Record data in the file before the backout =.SERVERExplanation: This message indicates that the record data was in the file before it was backed out.Action: None. This message is for information only.PAGENUM=1039 ID="BP1033"2039: Original record data from the backout file (being written back to the file) =.SERVERExplanation: This message indicates that the original record data from the backout file is being written back to the file.Action: None. This message is for information only.2044: Hole Restored To File At Offset = offset.SERVERExplanation: This message indicates that a hole in the file has been restored to the indicated code. (A hole is a section that is not sequential.)Action: None. This message is for information only.ID="FM42190"2047: TTS exceeded the limit of number of active transactions. Number transactions delayed.SERVERExplanation: Because the limit of active transactions was exceeded, the Transaction Tracking System (TTS) must delay additional requests to complete transactions until the number of active transactions comes within the limit.Action: None. This message is for information only. If the limit of active transactions is adjustable, you may be able to increase it if it hasn't already been set to the maximum. For more information on setting TTS, see "BOOK="utlrfenu" COLLECTION="nw41"SETTTS" in Utilities Reference.2049: TTS exceeded the limit of number of active transactions. Number transactions delayed.SERVERAction: See message IDREF="FM42190""2047: TTS exceeded the limit of number of active transactions. Number transactions delayed."2050: TTS ran out of memory expanding transaction node tables. Number memory allocation requests failed.SERVERExplanation: The system has run out of memory for more transactions.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.ID="FM58776"2053: TTS ran out of memory expanding transaction node tables. Number memory allocation requests failed.SERVERExplanation: The system has run out of memory for more transactions.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.2078: Volume name first segment (number) does not start at block 0.SERVERPAGENUM=1040 ID="BP1034"Explanation: The first segment of a volume must start with block 0. While mounting the specified volume, which is distributed over multiple physical disks, the operating system could not find the first segment. The segment that it found is not the first segment in the volume because it does not begin with block 0. One reason the operating system may not be able to find the segment is that the disk was corrupted. Another is that the operating system may not be able to access the disk at all because of a hardware problem on the network.Action: Back up all data on the affected disk before troubleshooting the problem. See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.2079: Volume name last segment (number) ends at block number instead of number.SERVERExplanation: The segment ends at a block which is incorrect based on the operating system's calculation of where the segment begins and how large it is.Action: None. This message is for information only.2080: Definition for volume name is invalid.SERVERExplanation: While mounting one or more volumes, the operating system found an invalid definition for the specified volume.Action: None. This message is for information only.2081: Volume name not found in existing volumes list.SERVERExplanation: The operating system cannot find a volume that it tried to discard.Action: None. This message is for information only.2082: Definition for sync number of volume name removed.SERVERExplanation: While checking a volume definition during mounting of the volume, the operating system discarded an unneeded synchronization value.Action: None. This message is for information only.2083: Volume name sync number not found in volume's sync list.SERVERExplanation: While trying to discard an unneeded or invalid synchronization value, the operating system found that the value was not in the volume's synchronization list.Action: None. This message is for information only.2087: Volume name could not be mounted. There are already number volumes mounted. No more volumes can be mounted.SERVERExplanation: Mounting another volume would exceed the allowed limit for volumes concurrently mounted.Action: Dismount one or more volumes and try the MOUNT server utility again.PAGENUM=1041 ID="BP1035"2091: Volume SYS: can not be mounted with write protected device.SERVERExplanation: Because NetWare must be able to make changes to the files on the volume SYS:, it cannot reside on a write-protected disk drive.Action: Remove write protection from the disk drive or reinstall NetWare, placing SYS: on another disk drive. (Make sure that you back up all data on the affected server before you reinstall NetWare.)2097: Compressed file is corrupted and unrecoverable.SERVERExplanation: The compressed file has been corrupted on the disk. During decompression, the integrity of the data describing the compressed file is checked. If any of the checks fail, data corruption is assumed, and compression cannot be completed, as is the case here. This error can only be caused by the data changing on the disk. Changed data can result from one of the following causes:MARK=BULLETMagnetic or electronic media close to the disk driveFailure of the disk drive or supporting hardwareIf the disk drive is failing, other files will be corrupted and will not contain the original data.Action: Try restoring the file from an earlier backup. If you cannot restore the data from a backup, the file is lost. See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.2110: Unable to initialize system auditing on volume name. Volume mount aborted.SERVERExplanation: Some possible reasons why the operating system cannot initialize system auditing on the named volume are that it cannot open the audit file or that the audit file is already at its maximum size.Action: Check the size of the auditing file before continuing.2111: Unable to allocate memory to mount volume name.SERVERExplanation: The operating system was unable to mount the volume because it is out of memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.2115: Overlapping segment entry found starting at offset number on server for volume name segment number.SERVERExplanation: When the operating system tried to mount the volume, it found an overlapping disk area. The operating system will discard the volume.Action: None. This message is for information only.PAGENUM=1042 ID="BP1036"2117: Drive failed while reading in volume information tables.SERVERExplanation: The drive holding the volume had a physical failure while the volume information tables were being read.Action: See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.2134: IPX local network number removed because of unbind request.SERVERExplanation: A user issued an UNBIND command to a LAN driver that IPX was using to reach a network. Users on the affected network cannot communicate with this server. Service to this network is terminated, unless alternate routes are available.Action: None. This message is for information only.2135: SAP socket was open when router was trying to open the SAP socket.SERVERExplanation: Before the loader was ready to load, another NLM program had already opened the SAP socket used by IPX. The offending NLM program may be an unlicensed version.Action: Normally, no action is necessary; the loader will automatically override the offending NLM program. However, if the problem persists, bring down the server and bring it back up without the offending NLM program.2136: Router configuration error detected. Server is claiming my same Internet address.SERVERExplanation: This error occurs when two active servers use the same Internet address. Users may not be able to locate servers on the network because of failed or improper routing of packets.Action: Bring down one of the servers, and reconfigure it with a unique network address. If routing problems persist, issue RESET ROUTER commands to all routers.2140: Directory entry contains an invalid filename.SERVERExplanation: The volume directory has become scrambled, which can have a variety of causes. For example, the system checks the overall length of the filename, which must not exceed 12 characters including the period. The system also verifies the existence of only one period, and does not allow more than three characters after the period.Action: Run VREPAIR and reboot the server. 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, recreate it using INSTALL, and restore the data from the backup.PAGENUM=1043 ID="BP1037"2143: Unable to create VOL$LOG.ERR on volume.SERVERExplanation: The system cannot log the error messages it produces. The VOL$LOG.ERR file (the volume's error file) could not be created because the volume was out of room, or because a disk error occurred. Historical error information for this volume will not be recorded at the server.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Disk Space Problems" in Supervising the Network.2144: Unable to write to VOL$LOG.ERR on volume.SERVERExplanation: The system was unable to write to the volume's error file because of a disk failure.Action: Another message should appear that indicates what went wrong. Correct the problem according to the information in the message. See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.2151: Volume name still operational despite drive deactivation.SERVERExplanation: One of the disk drives in the volume has gone down. However, the volume's integrity has not been compromised sufficiently to bring the entire volume down.Action: See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.2152: Volume name dismounted due to drive deactivation.SERVERExplanation: The specified volume was dismounted for one of the following reasons:MARK=BULLETA disk driver was unloaded.A disk failure occurred.The operating system initiated the driver unload.The volume is offline and unavailable to users.Action: Make sure the disk driver is loaded. See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.2187: A subdirectory is named PIPE.SERVERExplanation: "PIPE" is a reserved DOS name. No subdirectories can have this name or the volume will not mount. In most instances, NetWare will not allow this name to be used.Action: Rename the subdirectory or contact your Novell Authorized Reseller for suggestions on resolving this problem.PAGENUM=1044 ID="BP1038"2188: Subdirectory entry refers to invalid directory block.SERVERExplanation: The operating system encountered a problem while mounting a volume. A test of the subdirectory first block entry did not return with the correct value. The entry contained a value not equal to zero, indicating the wrong directory block or corruption.Action: Run VREPAIR. 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, recreate it using INSTALL, and restore the data from the backup.2189: Two subdirectories reference the same first directory block.SERVERExplanation: The operating system encountered a problem while mounting a volume because two subdirectories reference the same directory block.Action: Run VREPAIR. 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, recreate it using INSTALL, and restore the data from the backup.2190: Not enough memory to validate directory.SERVERExplanation: The server had enough memory to read the directory tables, but not enough memory to validate the directories. Before dismounting the volume, the user received a warning that the server was running out of memory and that the volume could not be remounted because it has grown too much. This error could occur at one of the following points in the volume mount:MARK=BULLET After comparing mirrored directory lengthsDuring setup of extra directory structuresDuring directory space restriction routinesDuring directory trustee addition and maintenance routinesAction: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.2191: Invalid maximum space defined in subdirectory.SERVERExplanation: The operating system encountered a problem while mounting a volume.Action: Run VREPAIR. PAGENUM=1045 ID="BP1039"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, recreate it using INSTALL, and restore the data from the backup.2192: Duplicate filenames in the same directory.SERVERExplanation: The operating system encountered a problem while mounting a volume because the directory contains two files with identical names.Action: Complete one or more of the following:MARK=BULLETCheck the version of the operating system. Do not run NetWare 3.0 or 3.1 on a server that has been running NetWare 3.11 (or later) or NetWare 4.0 (or later). If you need to return the server to an earlier version, run the earlier version's VREPAIR on all volumes, or purge all deleted files.Run VREPAIR.If the problem persists, make sure a volume backup exists. Delete the volume, recreate it using INSTALL, and restore the data from the backup.2193: Error rereading a directory entry.SERVERExplanation: An attempt to locate the directory entry of a previously identified file or directory has failed. The directory entry table may have become corrupted.Action: Check the network connection and retry the function. Run VREPAIR if necessary to repair the directory entry table. If the problem persists, make sure a volume backup exists. Delete the volume, recreate it using INSTALL, and restore the data from the backup.2308: GetOriginalNameSpace could not find the originating name space. The DOS name space was assumed. You should run VREPAIR to fix this!SERVERExplanation: This error indicates an inconsistent state of the directory table. The server needed to determine which name space generated the current name of a file. When it searched for which name space assigned the filename, none of the name spaces was marked as the originating name space. NetWare assumes that the name was generated by the DOS name space.Action: Run VREPAIR. 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, recreate it using INSTALL, and restore the data from the backup.PAGENUM=1046 ID="BP1040"2311: Error writing to file (filename not accessible) data stream number. Write was requested by the SERVER.SERVERExplanation: A write error has prevented the operating system from correctly writing file data to the disk. Hot Fix was not able to redirect the data to a new block. The data stream number indicates the name space stream (0=DOS or Macintosh data fork, 1=Macintosh resource fork). The data was not written to disk and will be lost.This error may be due to a hard disk or channel failure. The disk may have other problems with data integrity.Action: See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.2312: Error writing to file (filename not accessible) data stream number. Write was requested by user name on station number.SERVERExplanation: A write error has prevented the operating system from correctly writing file data to the disk. Hot Fix was not able to redirect the data to a new block. The data stream number indicates the name space stream (0=DOS or Macintosh data fork, 1=Macintosh resource fork). The data was not written to disk and will be lost.This error may be due to a hard disk or channel failure. The disk may have other problems with data integrity.Action: See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.2313: Error writing to file name data stream number. Write was requested by the SERVER. File path path.SERVERExplanation: A write error occurred on the system while writing data to disk. Hot Fix was not able to redirect the data to a new block. The data stream number indicates the name space stream (0=DOS or Macintosh data fork, 1=Macintosh resource fork).This error may have been caused by a hard disk or channel failure. The disk may have other data integrity problems.Action: See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.2314: Error writing to file name data stream number. Write was requested by user name on station number. File path server/volume.SERVERExplanation: A write error occurred on the system, while writing file data to disk. Hot Fix was not able to redirect the data to another block on the disk. The data stream number indicates the name space stream (0=DOS or Macintosh data fork, 1=Macintosh resource fork). The data was not written to disk and will be lost.This error may have been caused by a hard disk or channel failure. The disk may have other data integrity problems. Another possibility is that the designated file was lost or corrupted.Action: See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.PAGENUM=1047 ID="BP1041"2315: File read error at offset offset data stream number. Error getting filename. Read was requested by the SERVER.SERVERExplanation: The server was processing a file-read request. When the server tried to read the disk block with the file data, a disk-read error occurred. Some data was lost that could cause the user's applications to fail on reading data from files.The operating system was unable to determine the name of the file where the read error occurred because it received additional errors when it tried to read directory blocks to generate the filename.The data stream number indicates the name space stream (0=DOS or Macintosh data fork, 1=Macintosh resource fork.)This error may have been caused by a hard disk or channel failure. The disk may have other data integrity problems.Action: See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.2316: File read error at offset offset data stream number. Error getting filename. Read was requested by user name on station number.SERVERExplanation: The system cannot read the file from disk. Some data was lost that could cause the user's applications to fail on reading data from files.The data stream number indicates the name space stream (0=DOS or Macintosh data fork, 1=Macintosh resource fork.)This error may have been caused by a hard disk or channel failure. The disk may have other data integrity problems.Action: See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.2317: Error reading file name. Offset offset data stream number. Read was requested by the SERVER. File path path.SERVERExplanation: The operating system was processing a request to read data from a file, and it encountered an error while reading the data. The file read request will fail, possibly causing the applications that were requesting the read to fail.The data stream number indicates the name space stream (0=DOS or Macintosh data fork, 1=Macintosh resource fork).This error may have been caused by a hard disk or channel failure. The disk may have other data integrity problems.Action: See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.PAGENUM=1048 ID="BP1042"2318: Error reading file name. Offset offset data stream number. Read was requested by user name on station number. File path path.SERVERExplanation: When the operating system tried to read existing data from disk, it got a disk read error. The operating system was unable to determine the name of the file where the read error occurred because it got additional errors when it tried to read directory blocks to generate the filename.This error may have been caused by a hard disk or channel failure. The disk may have other data integrity problems.Action: See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.2319: File write pre-read error. Offset offset data stream number. Error getting filename. Read was requested by the SERVER.SERVERExplanation: When the operating system tried to write data to an existing file, it got an error in trying to read existing data from the disk. The new data could not be written to the disk and will be lost. The operating system was unable to determine the name of the file where the read error occurred because it got additional errors when it tried to read directory blocks to generate the filename.This error may have been caused by a hard disk or channel failure. The disk may have other data integrity problems.Action: See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.2320: File write preread error. Offset offset data stream number. Error getting filename. Read was requested by user name on station number.SERVERExplanation: When the operating system tried to write data to an existing file, it got an error in trying to read existing data from the disk. The new data could not be written to the disk and will be lost. The operating system was unable to determine the name of the file where the read error occurred because it got additional errors when it tried to read directory blocks to generate the filename.This error may have been caused by a hard disk or channel failure. The disk may have other data integrity problems.Action: See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.2321: File name write preread error. Offset offset data stream number. Read was requested by the SERVER. File path path.SERVERPAGENUM=1049 ID="BP1043"Explanation: When the operating system tried to write data to an existing file, it got an error in trying to read existing data from the disk. The new data could not be written to the disk and will be lost. The operating system was unable to determine the name of the file where the read error occurred because it got additional errors when it tried to read directory blocks to generate the filename.This error may have been caused by a hard disk or channel failure. The disk may have other data integrity problems.Action: See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.2322: File name write pre-read error. Offset offset data stream number. Read was requested by user name on station number. File path path.SERVERExplanation: When the operating system tried to write data to an existing file, it got an error in trying to read existing data from the disk. The new data could not be written to the disk and will be lost. The operating system was unable to determine the name of the file where the read error occurred because it got additional errors when it tried to read directory blocks to generate the filename.This error may have been caused by a hard disk or channel failure. The disk may have other data integrity problems.Action: See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.2323: Cache memory allocator exceeded minimum cache buffer left limit.SERVERExplanation: 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. The default minimum for both parameters is 20 buffers. 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 may 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: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.2324: Cache memory allocator out of available memory.SERVERExplanation: All cache memory has been used. System performance is severely degraded. 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: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.2325: Number of cache buffers is getting too low.SERVERExplanation: The number of cache buffers has dropped below a preset value and the system is running out of memory. However, the requested cache buffer was allocated successfully.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.PAGENUM=1050 ID="BP1044"2326: Volume server\volume out of disk space. There are no deleted files using disk space.SERVERExplanation: When the volume is out of disk space, this message will be broadcast to all users on the system. All attempts to write to files will fail because of insufficient disk space.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Disk Space Problems" in Supervising the Network.2327: Volume server\volume out of disk space. Number KB of disk space is in use by deleted files. No deleted files have been deleted long enough to purge yet.SERVERExplanation: When the volume is out of disk space, this message will be broadcast to all users on the system. All attempts to write to files will fail because of insufficient disk space. The second line of the message indicates that deleted files have not yet been purged. The third line indicates that all the deleted files cannot be purged yet because the preset purge time has not elapsed. Users may not be able to save files they are using and may lose data.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Disk Space Problems" in Supervising the Network.2328: Volume server\volume almost out of disk space.SERVERExplanation: The volume is about to run out of disk space. Users should save files currently in use to another volume or to another server to prevent data loss.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Disk Space Problems" in Supervising the Network.2329: Error writing FAT table for volume server\volume.SERVERExplanation: A write error has prevented the operating system from recording changes made to the File Allocation Table (FAT). The FAT tracks what disk blocks are allocated and free; it also records what disk blocks are grouped together to store a file's data. The server will still have the correct FAT information in memory, and it still can access the volume correctly. However, when you try to mount this volume the next time, the FAT information on disk will be incorrect, and the volume probably will not mount.This error may have been caused by a hard disk or channel failure. The disk may have other data integrity problems.Action: See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.2330: Error writing to the directory on server\volume.SERVERExplanation: A write error prevented the server from writing updated directory table information to a directory block. The updated directory information was not recorded on the disk. When the directory block is flushed from the directory cache, the server will not be able to read the information from the disk.This error may have been caused by a hard disk or channel failure. The disk may have other data integrity problems.Action: See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.PAGENUM=1051 ID="BP1045"2331: Error reading one copy of the directory on server\volume.SERVERExplanation: The server maintains two copies of the directory on each volume. An error occurred while the server was reading from one copy of the directory. The server was able to read the other copy, and it found the needed information.This error may have been caused by a hard disk or channel failure. The disk may have other data integrity problems.Action: Run VREPAIR when this error first appears. If both directory copies become corrupted, VREPAIR cannot fix the problem. The possibility of losing data increases significantly when the system uses only one of the mirrored directories. See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.2332: Error reading both copies of the directory on server\volume.SERVERExplanation: The system was trying to read a directory block from disk, but both the primary and secondary copies were inaccessible. Because the system could not read the directory information, it will not be able to process the request that needed this information.If this error occurs during the mount process, the volume will not mount because the system is not able to properly access and update the volume directory information. The volume tables may become damaged. Data on the volume may be lost, requiring it to be restored from backup copies.This error may have been caused by a hard disk or channel failure. The disk may have other data integrity problems.Action: See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.2333: Error writing to a newly allocated directory block on server\volume.SERVERExplanation: A write error prevented the server from allocating a new directory block and writing the directory information to the disk. When this directory block is flushed from the directory cache, the server will not be able to read the data from disk when it is needed again.This error may have been caused by a hard disk or channel failure. The disk may have other data integrity problems.Action: See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.PAGENUM=1052 ID="BP1046"2334: Error expanding server\volume directory due to disk write errors.SERVERExplanation: The system encountered a disk error while it was trying to allocate a block on the disk. The station making the request will not be able to create the new file or directory.This error may have been caused by a hard disk or channel failure. The disk may have other data integrity problems.Action: See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.2335: Error expanding server\volume directory because directory size limit was exceeded.SERVERExplanation: The system needs to allocate another directory block on the volume, but the maximum number of directory blocks has been reached. The server limits the amount of disk space used for the directory table to between 5% and 50% of the total space on a volume. This is controlled by the SET server utility's "Maximum Percent Of Volume Used By Directory" parameter, and it defaults to 13% of the disk space. The system allocates new directory blocks when a new directory is created, or when a new file is added to an existing directory, and it did not have any entries left to track the new file. Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Disk Space Problems" in Supervising the Network and "BOOK="superenu" COLLECTION="nw41"Maintaining the NetWare Server" in Supervising the Network.2336: Error expanding server\volume directory because no more disk space is available.SERVERExplanation: The system needs to allocate another directory block on the volume, but the volume is out of disk space. The system tries to allocate new directory blocks when a new directory is created or when a new file is added to an existing directory, but in this instance it did not have any entries left to track the new file.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Disk Space Problems" in Supervising the Network.2337: Error expanding server\volume directory because no more memory is available for tables.SERVERExplanation: The system needs to allocate another directory block on the volume, and it needs to expand the tables that it uses to track the directory within memory. When the system tried to expand the memory directory tables, there was not enough memory available to allocate the additional directory block. The station making the request will not be able to create the new file or directory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.2338: Server\volume directory size is getting too large for available memory. If the directory grows much larger, you may need to add more memory to the file server.SERVERPAGENUM=1053 ID="BP1047"Explanation: The size of the volume directory table has increased since the volume was mounted. The next time this volume is mounted, more memory will be used for the directory tables because a larger hash table will be created. The system has determined that the amount of memory available in the server is very low, and there may not be enough memory available to mount this volume again.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.2339: Low priority processes (in run order):SERVERExplanation: A SET parameter limits the number of Packet Receive Buffers that the operating system can allocate for itself. That limit has been reached.Action: Use SET or SERVMAN to view the current maximum setting. (Select "Communications" and view the "Maximum Packet Receive Buffers" parameter.) The server should have at least one packet receive buffer for each workstation attached to it.If the server does not have one buffer per attached workstation, increase the parameter and enter the command in the server's AUTOEXEC.NCF file. See "BOOK="superenu" COLLECTION="nw41"Maintaining the NetWare Server" in Supervising the Network for instructions.If the server has one buffer per workstation and the server is too slow in responding to disk I/O requests, add more memory to the server to help reduce the need for disk I/O's. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.2356: Rejected an incomplete NCP packet from Station number (NCP number number).SERVERExplanation: An NCP packet received from a client program had an invalid length, which invalidated the packet. The client program may be an outdated version or it may be corrupted.Action: Replace the offending client program with updated or uncorrupted software.2361: Processed an incomplete NCP from Station number (NCP number number).SERVERExplanation: The NCP engine processed an NCP packet even though the packet contained one or more fields with an invalid length.Action: None. This message is for information only.2388: Insufficient memory to load module.SERVERExplanation: An attempt to load an NLM program failed because the server does not have enough memory currently available to load it.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.PAGENUM=1054 ID="BP1048"2476: IPX internal network number was NOT set.SERVERExplanation: There is a command in the AUTOEXEC.NCF file that sets the internal network number, but the specified number is not a valid hexadecimal number.Action: Load INSTALL and edit the AUTOEXEC.NCF file. Make sure the specified number is a valid hexadecimal number. See "BOOK="superenu" COLLECTION="nw41"Creating or Editing a Server Batch (.NCF) File" in Supervising the Network for more information.2487: Invalid drive specification.SERVERExplanation: You have specified a drive or path that does not exist or is inaccessible.Action: Enter a valid path.2489: Not enough room on drive to dump diagnostics file.SERVERExplanation: The drive you specified for use in writing out the diagnostics dump does not have enough space to hold all the dump information.Action: Use a different drive or disk, or make space on the disk. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Disk Space Problems" in Supervising the Network.2490: Supervisor account lockout cleared from the console.SERVERExplanation: The supervisor's lockout has been cleared from the console.Action: None. This message is for information only.2491: Unable to clear supervisor account lockout.SERVERExplanation: An ENABLE LOGIN command was issued, but the system was unable to clear the locked-out Supervisor account. This failure may have been caused by an error in accessing the bindery files or writing to the disks. Another possible cause is a corrupted bindery.Action: Try the command again. If it fails, bring down the server and then bring it back up. Try the command again. If the Supervisor's account is still locked, you may have to run BINDFIX to locate errors and inconsistencies that may be causing problems in the bindery.2505: Unable to remove DOS.SERVERExplanation: The operating system was not able to remove DOS from memory when you entered the REMOVE DOS or SECURE CONSOLE command.Action: None. This message is for information only.PAGENUM=1055 ID="BP1049"2506: An NCP request with an invalid security signature was received from user name at address. Possible intruder or network corruption.SERVERExplanation: One of the security features in NetWare 4.0 is digital signature signing of packets. Both the originating workstation and the receiving server must "sign" packet requests to ensure the authenticity of the request. In this case, the server received a request that did not have a valid signature, indicating an intruder on the system or data corruption on the network.Action: Verify that you do not have an intruder on the system. (You will probably have to do this manually by determining who is actually using each workstation.) Run VREPAIR and restart the system. If the problem persists, make sure a volume backup exists. Delete the volume, recreate it using INSTALL, and restore the data from the backup.2514: Date and time are not set.SERVERExplanation: The time and date on the personal computer are not set. The operating system will read them in just like DOS and other PC operating systems do.Action: Bring down the server and run the SETUP program that came with the PC. If the time and date cannot be set, or will not remain set, contact your Novell Authorized Reseller to determine the problem.2541: System time changed from file server console. New time is time.SERVERExplanation: The system time has been changed from the server console. The new time is indicated.Action: None. This message is for information only.2543: System time changed by station number. New time is time.SERVERExplanation: The system time has been changed by the indicated station. The new time is indicated.Action: None. This message is for information only.ID="FM83235"2544: Command file processor unable to allocate work buffer.SERVERExplanation: The server is running out of Alloc Short Term memory and cannot allocate enough of this type of memory to process command files.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.2545: Command file processor unable to allocate work buffer.SERVERAction: See message IDREF="FM83235""2544: Command file processor unable to allocate work buffer."PAGENUM=1056 ID="BP1050"2547: Command files can be executed from a command file a maximum of 6 levels.SERVERExplanation: Command files can be nested up to six levels. One command file is being nested repeatedly more than six times, or more than six command files have been included.Action: Reduce the number of nested levels.2548: Invalid line in command file - line length exceeds number characters.SERVERExplanation: 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. See "BOOK="superenu" COLLECTION="nw41"Creating or Editing a Server Batch (.NCF) File" in Supervising the Network for more information. (The file being processed should be a command (DOS) text file.)2566: An IPX NCP packet with an invalid checksum was received from user name at address. Possible network corruption.SERVERExplanation: One of the error checking features in NetWare is the use of checksum to compare the binary value of a message sent with the value of the message when it is received. In this case, the server received a request with a checksum value different from the value it had when it was sent from a workstation, indicating data corruption on the network or a hardware malfunction.Action: See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network. After ensuring that the hardware is running properly, 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, recreate it using INSTALL, and restore the data from the backup.2599: Error moving trustee node on NetWare 4 file upgrade.SERVERExplanation: An error in rebuilding the directory entry table while upgrading to NetWare 4 occurred. This may be due to not enough disk space or other disk problems.Action: You may need to increase the volume size or repair the volume using VREPAIR. See"BOOK="superenu" COLLECTION="nw41"Resolving Server Disk Space Problems" in Supervising the Network.2603: File marked as migrated, but volume trustees not converted.SERVERExplanation: This is a report of a seeming inconsistency after a volume upgrade. When migrating data files the trustee assignments associated with that file have not been moved but the file is marked as fully migrated.Action: Perform the migration again or update the trustee assignments manually.PAGENUM=1057 ID="BP1051"2608: Unable to get spooler number information (error number).SERVERExplanation: The SPOOL command cannot list the mapping for the specified spool because of the specified bindery error.Action: None. This message is for information only. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A 2618: Unable to set spooler number (error number).SERVERExplanation: The operating system was not able to set the spool to the specified queue because of the specified bindery error.Action: None. This message is for information only. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 2707: LCONFIG.SYS file exists but is invalid. NOT overriding default values.SERVERExplanation: Each language supported by NetWare has a language configuration file (LCONFIG.SYS) that is loaded into the operating system tables. This message indicates that the LCONFIG.SYS file exists, but somehow the file has been corrupted.Action: Delete the corrupted LCONFIG.SYS file and copy the original file from the master CD-ROM or diskette.2713: Module did not release one resource. Module: module Resource: resource Description: descriptionSERVERExplanation: An NLM program failed to release an allocated resource when it was unloaded. In many cases, the NLM program 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 program to determine whether the NLM program should have released the resource. The vendor may have a newer NLM program that corrects the problem.2715: Module did not release number resources Module: PAGENUM=1058 ID="BP1052"module Resource: resource Description: descriptionSERVERExplanation: An NLM program 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 program to determine whether the NLM program should have released the resources. The vendor may have a newer NLM program that corrects the problem.2985: Internal compression error: file `name' volume number intermediate size number. Data encode counts from intermediate file generation (encode_count) and intermediate file processing (encode_count) mismatch invalidating intermediate file.SERVERExplanation: This is an internal consistency check done by compression to guarantee the integrity of the data being compressed. The file that was being compressed will remain uncompressed, and the system will try again later to compress it.Action: No immediate action is necessary. Note the volume number and watch for more of these same alerts. Also, watch for other errors indicating that the memory or disk is failing. If these alerts or other data corruption problems happen often on a particular volume, the disk or hardware supporting the disk should be repaired or replaced. See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.2994: Unable to allocate memory for new language name.SERVERExplanation: The operating system was unable to allocate memory for a new language name because it is out of memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.2995: Unable to allocate memory for new language.SERVERExplanation: The operating system was unable to allocate memory for a new language because it is out of memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.3003: Insufficient RAM to compress file.SERVERExplanation: The compression system could not allocate enough memory to compress the file. The server could be congested or the server may not have enough memory to compress a file.Action: None. This message is for information only. The file will remain uncompressed; the system will try to compress it later. If the message occurs even during periods of low network traffic, the server probably needs more memory. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.PAGENUM=1059 ID="BP1053"3004: Disk I/O error compressing file.SERVERExplanation: A bad I/O has occurred during file compression. The disk drive or disk hardware may be starting to malfunction. The file that was being compressed will remain uncompressed, and the system will try again later to compress it.Action: See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.3033: File has both do compression and don't compress attributes set.SERVERExplanation: The system does not know whether to perform file compression on a given file because the file has been assigned both the Immediate Compress (Ic) and Don't Compress (Dc) attribute.Action: Use FLAG to remove the Ic or Dc attribute on the given file.3034: Directory has both do file compression and don't file compress attributes set.SERVERExplanation: The system does not know whether to perform file compression in a directory because the directory has been assigned the Immediate Compress (Ic) and Don't Compress (Dc) attribute.Action: Use FLAG to remove the Ic or the Dc directory attribute.3035: File compression bits set on noncompression volume.SERVERExplanation: A file or files have been assigned the Immediate Compress (Ic) attribute, but the volume on which they reside is not configured to perform file compression.Action: Use FLAG to remove the Ic attribute on the files involved and move the files to a volume that performs file compression, or use the SET server utility's Enable File Compression attribute to "ON."3036: File is flagged as both compressible and noncompressible.SERVERExplanation: The system does not know whether to perform file compression on a given file because the file has been assigned both the Immediate Compress (Ic) and Don't Compress (Dc) attribute.Action: Use FLAG to remove the Ic or the Dc file attribute on the given file.3039: Invalid suballocation node. Volume was NOT mounted.SERVERExplanation: Corruption has occurred in the file system, possibly due to a power outage.Action: Run VREPAIR and restart the system. If the problem persists, make sure a volume backup exists. Delete the volume, recreate it using INSTALL, and restore the data from the backup. Also, make sure the server has a good UPS system installed and that the UPS system is operating properly.PAGENUM=1060 ID="BP1054"3040: Suballocation node used by multiple files. Volume name was NOT mounted.SERVERExplanation: More than one file was using the same block. This error could be due to a variety of causes, including a faulty disk drive or other hardware problem, premature downing of the server, or data corruption.Action: See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network. If you suspect corruption, 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, recreate it using INSTALL, and restore the data from the backup.3041: Suballocation encountered but not enabled on this volume. Volume name was NOT mounted.SERVERExplanation: This error could be due to a variety of causes, including a faulty disk drive or other hardware problem, premature downing of the server, or data corruption.Action: See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network. If you suspect corruption, 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, recreate it using INSTALL, and restore the data from the backup.3043: Too many memory fragments. Diagnostic image dump to DOS hard drive aborted.SERVERExplanation: The maximum number of memory fragments the core dump can handle has been exceeded. This message is for information only.Action: None. This message is for information only.3044: Out of disk drive space.SERVERExplanation: There is insufficient disk space to write the core dump to a DOS partition. If the DOS partition is full, this error can occur.Action: Make sure there is sufficient space on the destination drive before performing the core dump. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Disk Space Problems" in Supervising the Network.3045: Error writing to diagnostic image file (code = code).SERVERExplanation: An error occurred while writing the core dump to floppy diskette.Action: Get a good set of formatted diskettes before performing a core dump. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. PAGENUM=1061 ID="BP1055"3061: Compression: Invalid length or offset.SERVERExplanation: An I/O error has occurred during file compression. The disk drive or disk hardware may be starting to malfunction. The file that was being compressed will remain uncompressed and the system will try again later to compress it.Action: See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.3063: A fault occurred in a registered console command handler.SERVERExplanation: An NLM program caused a memory protection page fault when the command parser was called. The server may be using an unlicensed or outdated version of the NLM program, or a version that is still under development.Action: Determine which NLM program caused the error and unload it.3093: Migrated Data Streams have been corrupted.SERVERExplanation: The data for a migrated file is corrupted.Action: Replace the corrupted file from a backup.3094: Unable to access the Data Migration Look Up Key.SERVERExplanation: Data that was migrated to a writable disk player (or jukebox) for storage cannot be found. The Data Migration Look Up Key is the pointer that tells where stored data is located in the CD. The directory entry for the file containing the data still exists, but no data exists in the file.Action: Unless there is a backup of the file, the data is lost. Delete the file from the directory.3098: Rejected an NCP with a bad subfunction length, Station number (NCP number number).SERVERExplanation: 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. The client program may be an outdated version or it may be corrupted.Action: Replace the offending client program with updated or uncorrupted software.3101: Processed an NCP with a bad subfunction length, Station number (NCP number number).SERVERExplanation: 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. The client program may be an outdated version or it may be corrupted.Action: None. This message is for information only.PAGENUM=1062 ID="BP1056"3120: Illegal hole in suballocation FAT chain.SERVERExplanation: A File Allocation Table (FAT) chain is a list of directory block locations. If the FAT chain skips a block, a hole appears in the chain. (A hole is a section that is not sequential.) A hole indicates that the location was never allocated.Action: Run VREPAIR. 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, recreate it using INSTALL, and restore the data from the backup.3121: Suballocation FAT chain entry exceeds maximum.SERVERExplanation: A File Allocation Table (FAT) chain is a list of directory block locations.Action: Run VREPAIR. 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, recreate it using INSTALL, and restore the data from the backup.3122: Suballocation FAT already claimed.SERVERExplanation: A File Allocation Table (FAT) is an index to one or more disk allocation blocks in which a file is located.Action: Run VREPAIR. 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, recreate it using INSTALL, and restore the data from the backup.3123: Suballocation out of memory.SERVERExplanation: The operating system was unable to allocate memory for the suballocation FAT because it is out of memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.3143: Insufficient disk space to decompress file filename for station number.SERVERPAGENUM=1063 ID="BP1057"Explanation: The disk space required for the decompressed file is not available, so the file cannot be decompressed. Disk restrictions for the user, volume, or directory could have been assigned, or the volume could be full. The system will try again later to compress the file.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Disk Space Problems" in Supervising the Network.3149: Compressed file filename being decompressed for station number uses unknown compression format.SERVERExplanation: Each compressed file has a value indicating which compression format it is in. If NetWare opens a file and does not recognize the compression format, it cannot decompress the file. This file could be corrupted, or it could be flagged as compressed when it is not really compressed.Action: Try restoring the file from a backup.3151: Insufficient RAM to decompress file.SERVERExplanation: Insufficient memory is available to decompress the file. The file that was being decompressed will remain compressed and the system will try again later to decompress it.Action: "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.3191: Server name address has changed from old_address to new_address. Information came from router at address.SERVERExplanation: The server has been assigned a new internal network number.Action: None. This message is for information only.3225: Unable to get DOS entry for Migrated File.SERVERExplanation: A migrated file's DOS counterpart cannot be found.Action: Delete the file that was migrated.3226: Collision when Claiming Extended Directory space for a migrated file.SERVERExplanation: The volume's extended directory space has been corrupted.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, recreate it using INSTALL, and restore the data from the backup.PAGENUM=1064 ID="BP1058"3227: Compressed files are not being committed decompressed on volume name due to lack of disk space.SERVERExplanation: The volume does not have enough disk space to decompress the compressed files. The files that were being decompressed will remain compressed, and the system will try again later to decompress them.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Disk Space Problems" in Supervising the Network.3280: Internal compression error: file `name' volume number intermediate size number. Length/Offset encode counts from intermediate file generation (number) and intermediate file processing (number) mismatch invalidating intermediate file.SERVERExplanation: This is an internal consistency check done by compression to guarantee the integrity of the data being compressed. During file compression, an intermediate file is created that describes the compressed version of the file. The file contains codes describing what should be encoded in the compressed version of the file. The codes in the intermediate file do not match those found in the file being compressed. The file that was being compressed will remain uncompressed, and the system will try again later to compress it.Action: No immediate action is necessary. Note the volume number and watch for more of these same alerts. Also, watch for other errors indicating that the memory or disk is failing. If these alerts or other data corruption problems happen often on a particular volume, the disk or hardware supporting the disk should be repaired or replaced. See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.3281: Internal compression error: file `name' volume number intermediate size number. Large length/offset encode counts from intermediate file generation (number) and intermediate file processing (number) mismatch invalidating intermediate file.SERVERExplanation: This is an internal consistency check done by compression to guarantee the integrity of the data being compressed. During file compression, an intermediate file is created that describes the compressed version of the file. The file contains codes describing what should be encoded in the compressed version of the file. The codes in the intermediate file do not match those found in the file being compressed. The file that was being compressed will remain uncompressed, and the system will try again later to compress it.Action: No immediate action is necessary. Note the volume number and watch for more of these same alerts. Also, watch for other errors indicating that the memory or disk is failing. If these alerts or other data corruption problems happen often on a particular volume, the disk or hardware supporting the disk should be repaired or replaced. See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.PAGENUM=1065 ID="BP1059"3282: Compress error file name, volume number, size size. Read beyond end of name file at offset offset.SERVERExplanation: The disk has returned zero bytes for a compression read request, and compression believes that there is still some data to read.Action: If this seldom happens, it is not a problem and no action is necessary. The file that was being compressed will remain uncompressed and the system will try again later to compress it. If the problem persists, contact your Novell Authorized Reseller.3283: Internal compression error: file name volume number size size. Shannon Tree depth exceeded 32 generating bit codes uncontainable in a single LONG.SERVERExplanation: This is an internal consistency check done by compression to guarantee the integrity of the data being compressed. During file compression, an intermediate file is created that describes the compressed version of the file. The file contains codes describing what should be encoded in the compressed version of the file. The totals from processing the original file do not match the totals from processing the intermediate file. This would only be caused by a memory hit or a disk returning faulty data. The file that was being compressed will remain uncompressed, and the system will try again later to compress it.Action: No immediate action is necessary. Note the volume number and watch for more of these same alerts. Also, watch for other errors indicating that the memory or disk is failing. If these alerts or other data corruption problems happen often on a particular volume, the disk or hardware supporting the disk should be repaired or replaced. See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.3284: Internal compression error: file name volume number size size. The projected size of the compressed file (byte_size) did not match the byte size of the compressed file (byte_size).SERVERExplanation: This is an internal consistency check done by compression to guarantee the integrity of the data being compressed. During file compression, an intermediate file is created that describes the compressed version of the file. The file contains codes describing what should be encoded in the compressed version of the file. The totals from processing the original file do not match the totals from processing the intermediate file. This would only be caused by a memory hit or a disk returning faulty data. The file that was being compressed will remain uncompressed, and the system will try again later to compress it.Action: No immediate action is necessary. Note the volume number and watch for more of these same alerts. Also, watch for other errors indicating that the memory or disk is failing. If these alerts or other data corruption problems happen often on a particular volume, the disk or hardware supporting the disk should be repaired or replaced. See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.PAGENUM=1066 ID="BP1060"3285: Compress error file name, volume number, size size. Had original sparse count of number. Internal linked list showed only name sparse count.SERVERExplanation: This is an internal consistency check done by compression to guarantee the integrity of the data being compressed. During file compression, an intermediate file is created that describes the compressed version of the file. The file contains codes describing what should be encoded in the compressed version of the file. In sparse files, a count is maintained while the original and temporary files are being processed. If these sparse counts mismatch, this message is displayed. The file that was being compressed will remain uncompressed, and the system will try again later to compress it.Action: No immediate action is necessary. Note the volume number and watch for more of these same alerts. Also, watch for other errors indicating that the memory or disk is failing. If these alerts or other data corruption problems happen often on a particular volume, the disk or hardware supporting the disk should be repaired or replaced. See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.3536: The Main Server License companion Reseller file (name) could not be found. string.SERVERExplanation: The Main Server License requires that a Reseller License created by the reseller at the time of purchase must also have been installed and valid.Action: Use INSTALL.NLM to install a companion Reseller License. If you do not have one, contact your Novell Authorized Reseller.3537: The Main Server License file (name) could not be found. string.SERVERExplanation: The Main Server License has not been installed using INSTALL.NLM, and it cannot be found and validated.Action: Use the INSTALL.NLM to install the Main Server License on the server. Without this license, the server will allow only one connection. If you do not have one, contact your Novell Authorized Reseller.3538: The Upgrade License companion Reseller License file (name) could not be found. string.SERVERExplanation: The Upgrade License requires a companion Reseller License. The companion Reseller License has not been installed.Action: Use the INSTALL.NLM to install the companion Reseller License along with the Upgrade License.PAGENUM=1067 ID="BP1061"3539: The License Version in the license document from the file (name) is invalid for this server. string.SERVERExplanation: The version of the license format (Main or Upgrade) in the license document does not work with the license format required by the server that is currently running.Action: Use INSTALL.NLM to install the correct version of the license document. If you do not have one, contact your Novell Authorized Reseller.3540: The Product Version in the license document from the file (name) is invalid for this server. string.SERVERExplanation: The product version in the license document does not match the product version of the server.Action: Use INSTALL.NLM to install the license document that contains the correct product version. If you do not have one, contact your Novell Authorized Reseller.3542: The Product Identification in the license document from the file (name) is invalid for this server. string.SERVERExplanation: The product identification string in the license document does not match the one for the server that is running.Action: Use INSTALL.NLM to install the license document that contains the correct product identification string. If you do not have one, contact your Novell Authorized Reseller.3543: The content of the license document from the file (name) is not valid. string.SERVERExplanation: The license document contents did not match when reencrypted and compared to the encryption in the document itself.Action: Use INSTALL.NLM to install the license document. If you do not have one, contact your Novell Authorized Reseller.3544: The Upgrade license document came from the Main Server License file (name) and therefore is not valid. string.SERVERExplanation: The license that was installed as a Main Server License is really an Upgrade Server License and cannot be used.Action: Use INSTALL.NLM to install a valid Main Server License. If you do not have one, contact your Novell Authorized Reseller.PAGENUM=1068 ID="BP1062"3545: The Previous Maximum Connections in the license document from the file (name) do not match with the current maximum. string.SERVERExplanation: The Upgrade License being validated specifies a "Previous Maximum Connections" number that does not match the "Maximum Connections" number specified by the currently installed license.Action: Use INSTALL.NLM to install an Upgrade license that specifies the same number for its "Previous Maximum Connections" as the currently installed license's "Maximum Connections." If you do not have one, contact your Novell Authorized Reseller.3546: The Content of the Reseller License (name) is invalid. string.SERVERExplanation: The reencryption of the license document contents of the companion Reseller license does not match the encryption of the contents in the license itself.Action: Use INSTALL.NLM to install a valid companion Reseller License with the regular license (Main or Upgrade). If you do not have one, contact your Novell Authorized Reseller.3547: The serial number in the Main Server License and the companion Reseller License do not match. string.SERVERExplanation: The companion Reseller License is not for the Main Server License that has been installed. The server cannot grant connections without a valid one. The serial number in the Main Server License and the companion Reseller License for that Main License must match.Action: Use INSTALL.NLM to install the correct companion Reseller License with the Main Server License. If you do not have one, contact your Novell Authorized Reseller.3548: The Connection Upgrade ID number in the companion Reseller License (name) does not match the one in the Upgrade License document. string.SERVERExplanation: The companion Reseller License is not for the Upgrade Server License that has been installed. The server cannot grant the additional connections allowed by the Upgrade License without a valid one. The identification number in the Upgrade Server License and the identification number in the companion Reseller License must match.Action: Use INSTALL.NLM to install the correct companion Reseller License with the Upgrade Server License. If you do not have one, contact your Novell Authorized Reseller.3549: Unable to open the license file (name). string.SERVERExplanation: 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 INSTALL.NLM. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=1069 ID="BP1063"3550: The Reseller License (description) intended to be a companion to the Main Server License is a companion to an Upgrade License and is invalid. string.SERVERExplanation: The Reseller License installed and being validated as the companion of the Main Server License is really a companion license for some other Upgrade Server License and, therefore, is not valid.Action: Use INSTALL.NLM to reinstall the companion Reseller License and the Main Server License. If the problem persists, contact your Novell Authorized Reseller.3551: The Serial Number in the Upgrade license document from the file (name) does not match the one in the Main Server License document. string.SERVERExplanation: The current license policy requires that the Upgrade Server License be serialized with the serial number contained in the Main Server License already installed. Because the serial numbers do not match, the Upgrade license cannot work with the Main Server License and the additional connections allowed by the upgrade will not be used.Action: Use INSTALL.NLM to reinstall an Upgrade Server License that has been serialized for use with the Main Server License. If the problem persists, contact your Novell Authorized Reseller.3552: Unable to remove the invalid Main Server License file (name). string.SERVERExplanation: 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 your Novell Authorized Reseller.3553: Unable to remove the invalid Upgrade License file (name). string.SERVERExplanation: 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 your Novell Authorized Reseller.3554: Unable to remove the invalid companion Reseller License file (name). string.SERVERExplanation: 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 your Novell Authorized Reseller.PAGENUM=1070 ID="BP1064"3555: Unable to get a File Size for the license file (name). string.SERVERExplanation: 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 your Novell Authorized Reseller.3556: Unknown license type in the file (name). string.SERVERExplanation: During the license validation process, the type of license to be validated could not be determined. The validation for that license has failed.Action: The faulty license should have been deleted by the system. Try reinstalling the license using INSTALL.NLM. If the problem persists, contact your Novell Authorized Reseller.3557: Unable to read in the license document from the file (name). string.SERVERExplanation: 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 INSTALL.NLM. If the problem persists, contact your Novell Authorized Reseller.3558: The license document in the file (name) is not the correct size for the license document type. The license cannot be validated. string.SERVERExplanation: The license document retrieved from the file was not the correct size and, therefore, is not valid for use. It should have been removed by the server.Action: Reinstall the license using INSTALL.NLM. If the problem persists, contact your Novell Authorized Reseller.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. stringSERVERExplanation: The license file is invalid for some reason and has been removed by the server.Action: Reinstall the license using INSTALL.NLM. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=1071 ID="BP1065"SERVMAN003: The NLM could not allocate number bytes of memory.SERVMANExplanation: The server does not have enough memory available.Action: For information on solving server memory problems, see "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.004: The NLM could not allocate memory.SERVMANExplanation: The server does not have enough memory available.Action: For information on solving server memory problems, see "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.032: No devices are registered.SERVMANExplanation: The NLM program attempted to obtain information about storage devices on the server, but no devices were registered with the server.Action: To view device information, load the appropriate device drivers and mount the volumes.106: The NLM could not open a screen.SERVMANExplanation: The server probably does not have enough memory available.Action: For information on solving server memory problems, see "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.109: The value you entered is out of range. Please enter a value within the displayed limits.SERVMANExplanation: While changing a server parameter, you entered a value that was above or below the acceptable limits.Action: Note the limits as displayed in the help window at the bottom of the screen, and enter a value that falls within those limits.117: You have entered the value in an invalid format.SERVMANExplanation: While changing a server parameter, you entered a value in an improper format.Action: Enter the value again using a valid format. For information on the valid format for server parameters, see "BOOK="utlrfenu" COLLECTION="nw41"SET" in Utilities Reference.PAGENUM=1072 ID="BP1066"146: The string is too long. Please shorten the string to within the displayed limits.SERVMANExplanation: While changing the value of a string server parameter, you entered a string that was too long.Action: Note the limits as displayed in the help window at the bottom of the screen, and shorten the length of the string parameter to a length within the displayed limits.147: Invalid input. Enter a value in the format "+xx:xx:xx".SERVMANExplanation: While changing the value of a time offset server parameter, you entered a value in an improper format.Action: Enter the value using the correct format. For information on the valid format for server parameters, see "BOOK="utlrfenu" COLLECTION="nw41"SET" in Utilities Reference.148: An unknown error has occurred.SERVMANExplanation: While setting the value of a server parameter, an unexpected error occurred.Action: Try setting the parameter using the SET command at the server's command line prompt.156: The NLM could not modify file name. The file may be locked or flagged Read Only. Please check the specified path.SERVMANExplanation: SERVMAN was unable to open, create, or write to the named file.Action: Make sure the file is not locked and that it has not been flagged Read Only or Delete Inhibit, then retry the operation.170: The NLM could not open file name.SERVMANExplanation: This error could be caused by one of the following:MARK=BULLETThe specified path is invalid.The specified file exists but is currently locked or in use by another user.Action: Make sure the specified path is typed correctly. Using MONITOR, make sure the file is not in use by another user.PAGENUM=1073 ID="BP1067"171: DOS is not available on one or both of the mirrored servers. The file MSSTART.NCF cannot be modified.SERVMANExplanation: On a pair of NetWare® 4.1 SFT IIITM servers, DOS has been removed from memory on one or both servers, preventing SERVMAN from accessing the DOS partition. Action: For information on removing a DOS partition, see "BOOK="utlrfenu" COLLECTION="nw41"REMOVE DOS" in Utilities Reference.172: The NLM could not modify file name on the mirrored server. Please check the specified path.SERVMANExplanation:  This error could be caused by one of the following:MARK=BULLETThe mirrored NetWare® 4.1 SFT IIITM server is unavailable.The specified path is invalid.The specified file exists but is flagged Read Only or Delete Inhibit.The specified file exists but is currently locked or in use by another user.Action: Make sure the mirrored server is operating. If the mirrored server is operational, make sure the specified path and file name are typed correctly and the file is flagged with the appropriate access rights. Using MONITOR, make sure the file is not in use by another user.195: The NLM could not obtain volume information.SERVMANExplanation:  While requesting information about a mounted volume, an unexpected error occurred.Action:  Make sure the specified volume is mounted and the server is operating.218: The NLM could not create and open file name.SERVMANExplanation:  This error could be caused by one of the following:MARK=BULLET The specified path is invalid. The specified file exists but is flagged Read Only or Delete Inhibit. The specified file exists but is currently locked or in use by another user.Action:  Make sure the specified path is typed correctly. If the specified path is correct, make sure the file is flagged with the appropriate attributes. Using MONITOR, make sure the file is not in use by another user.PAGENUM=1074 ID="BP1068"219: The file you specified has been flagged Read Only. It cannot be overwritten.SERVMANExplanation:  You tried to write to a file that has been flagged Read Only.Action:  Remove the Read Only flag from the file, and try again.222: This NLM requires a newer version of NWSNUT.NLM.SERVMANExplanation: While loading, SERVMAN determined that the version of NWSNUT loaded in server memory does not support the required functionality.Action: Update the version of NWSNUT.NLM on the server.225: The NLM could not allocate a resource tag.SERVMANExplanation: The server is probably out of memory.Action: For information on solving server memory problems, see "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.PAGENUM=1075 ID="BP1069"SETPASS110: The supervisor has locked the bindery on server name in domain name.SETPASSExplanation: The system bindery on this server is inaccessible. The network supervisor may be doing maintenance work on the system. The system bindery contains information such as the names of users, their rights, and the servers to which they are attached.Action: The system bindery is usually locked only momentarily. Wait a few minutes and try the command again.120: Password for user name could not be changed. Error code code.SETPASSExplanation: SETPASS failed in its attempt to change the user's password on the network. This is a NetWare Directory Services error.Action: For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 130: This utility could not create a context.SETPASSExplanation: SETPASS was unable to create a context. This could be a memory problem.Action: See"BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network.150: User name does not exist on the network.SETPASSExplanation: A user tried to log in to an account using a name that does not exist.Action: None. This message is for information only. However, a new user object can be created if needed.190: An error occurred during SETPASS's attempt to check for the presence of Directory Services.SETPASSExplanation: SETPASS tried to determine whether NetWare Directory Services was present on the network. An unexpected error was returned.Action: Unload VLM by typing "VLM /u MOREINFO="NONE"<Enter>"; then reload VLM and try the command again.200: You have no connection to a default server. Specify a default server on the command line.SETPASSExplanation: SETPASS could not determine the default connection. If you specify a server on the command line, SETPASS will not use the default connection.Action: Specify a server on the command line. See "BOOK="utlrfenu" COLLECTION="nw41"SETPASS" in Utilities Reference for more information about SETPASS command syntax.PAGENUM=1076 ID="BP1070"210: You are not connected to server name.SETPASSExplanation: The user tried to set the password on a server that the user was not attached to.Action: Attach to the server and try the command again. Make sure the server name is typed correctly.250: The new password was not retyped correctly.SETPASSExplanation: When changing a password, the user did not retype it exactly the same the second time as it was typed the first time.Action: Repeat the procedure, taking special care to type accurately.260: The new password for server/user has been used previously. Your password was not changed.SETPASSExplanation: The user tried to change a password to one that had been previously used. The network supervisor can require periodic password changes for any or all accounts on the server to protect against access by unauthorized persons. The network supervisor can also restrict users from repeating passwords they have used previously.Action: Select a password that has not already been used.261: The password for user: name has been used previously. Your password was not changed.SETPASSExplanation: The user tried to change a password to one that had been used previously. The network supervisor can require periodic password changes for any or all accounts on the server to protect against access by unauthorized persons. The network supervisor can also restrict users from repeating passwords they have used previously.Action: Select a password that has not already been used.280: The new password was too short for user: server/user. Your password was not changed.SETPASSExplanation: The user tried to define a password that is shorter than the required minimum length for passwords. The network supervisor can restrict all passwords to a minimum length.Action: Select a longer password.281:The new password was too short for user: name. Your password was not changed.SETPASSExplanation: The user tried to define a password that is shorter than the required minimum length for passwords. Action: Make sure the user selects a longer password.PAGENUM=1077 ID="BP1071"320: Account for server/user is restricted. Your password was not changed.SETPASSExplanation: The system cannot accept the user's password because all grace logins have been used up. Validating passwords uses up grace logins.Action: Change the user's password.321: Account is restricted for user: name. Your password was not changed.SETPASSExplanation: The system cannot accept the user's password because all grace logins have been used up. Validating passwords uses up grace logins.Action: Change the user's password.390: An error occurred during SETPASS's attempt to create a list of this workstation's connections. Error code: code.SETPASSExplanation: SETPASS was unable to create a list of the workstation's connections. The bindery or NetWare Directory Services file may be corrupted. The user also may not have a valid connection to the server. An internal program error also may have occurred. Action: Make sure that the user is connected to the server and that the server is up. If so, restart SETPASS and try again. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the error recurs, make sure that the bindery or NetWare Directory Services file is not corrupted.400: This utility could not get your security access level.SETPASSExplanation: The security access level of the user is required to run SETPASS. The bindery may be locked, or an internal program error may have occurred.Action: Restart SETPASS and try again. If the error recurs, make sure that the bindery or NetWare Directory Services file is not corrupted.405: This utility could not get your effective rights.SETPASSExplanation: SETPASS was unable to get the user's effective rights. The bindery or NetWare Directory Services file may be corrupted. The user also may not have a valid connection to the server. An internal program error also may have occurred. Action: Make sure that the workstation is connected to the server and that the server is up. If so, restart SETPASS and try again. If the error recurs, make sure that the bindery or NetWare Directory Services file is not corrupted.PAGENUM=1078 ID="BP1072"410: You must be a supervisor to set someone else's password.SETPASSExplanation: The user tried to set another user's password, but the user is not a Supervisor or equivalent.Action: Log in as a Supervisor or equivalent; then try to set the other user's password.420: You must be a supervisor or workgroup manager to set someone else's password.SETPASSExplanation: The user tried to set another user's password, but the user is not a Supervisor or equivalent.Action: Log in as a Supervisor or equivalent; then try to set the other user's password.470: User server/user was denied access to the server. The password could not be changed.SETPASSExplanation: The server/user was denied access to the server; therefore, SETPASS could not change the password. The old password was probably typed incorrectly.Action: Type the username and old password correctly.471: Access to the network has been denied to user: name. The password could not be changed.SETPASSExplanation: The user was denied access to the server; therefore, SETPASS could not change the password. The old password was probably typed incorrectly.Action: Type the username and old password correctly.490: User name was denied access on the network. The password was not changed.SETPASSExplanation: The specified user was denied access on the network; therefore, SETPASS could not change the password. The old password was probably typed incorrectly.Action: Type the username and old password correctly.500: An unexpected error occurred. The password for server/user was not changed. Error code: code.SETPASSExplanation: The attempt to change the password failed due to a system error.Action: Try again. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=1079 ID="BP1073"520: An error occurred during SETPASS's attempt to get a list of this workstation's connections for changing the password.SETPASSExplanation: SETPASS could not get a list of the workstation's connections. The bindery or NetWare Directory Services file may be corrupted. The user also may not have a valid connection to the server. An internal program error also may have occurred. Action: Make sure that the user is connected to the server and that the server is up. If so, restart SETPASS and try again. If the error recurs, make sure that the bindery or NetWare Directory Services file is not corrupted903: The command line syntax is invalid.SETPASSAction: See message IDREF="FM18860""903: The command line syntax is invalid." in Appendix C.905: This utility was unable to initialize the country information.SETPASSAction: See message IDREF="FM55337""905: This utility was unable to initialize the country information." in Appendix C.919: This utility could not create a connection list.  Error <code>.SETPASSAction: See message IDREF="FM68419""919: This utility could not create a connection list. Error code." in Appendix C.920: This utility was unable to allocate <number> bytes of memory.SETPASSAction: See message IDREF="FM30331""920: This utility was unable to allocate number bytes of memory." in Appendix C.921: Either the supervisor has locked the bindery or volume SYS: is not mounted.SETPASSAction: See message IDREF="FM49837""921: Either the supervisor has locked the bindery or volume SYS: is not mounted." in Appendix C.922: Intruder detection lockout has disabled this account.SETPASSAction: See message IDREF="FM41618""922: Intruder detection lockout has disabled this account." in Appendix C.923: An unexpected error has occurred. Error code: <code>.SETPASSAction: See message IDREF="FM30182""923: An unexpected error has occurred. Error code: code." in Appendix C.PAGENUM=1080 ID="BP1074"925: The server specified is a Personal NetWare server. You cannot attach to a Personal NetWare server with this utility. Use the Personal NetWare utilities to access this connection.SETPASSAction: See message IDREF="FM67645""925: The server specified is a Personal NetWare server. You cannot attach to a Personal NetWare server with this utility. Use the Personal NetWare utilities to access this connection." in Appendix C.970: The attempt to open the Unicode table files failed.SETPASSAction: See message IDREF="FM15675""970: The attempt to open the Unicode table files failed." in Appendix C.971: The workstation does not have enough memory to load the Unicode table files.SETPASSAction: See message IDREF="FM55341""971: The workstation does not have enough memory to load the Unicode table files." in Appendix C.972: Access to the Unicode table files was denied.SETPASSAction: See message IDREF="FM90152""972: Access to the Unicode table files was denied." in Appendix C.973: The Unicode table files cannot be found in the NLS directory or in the search path. Code page: <number>  Country:  <number>SETPASSAction: See message IDREF="FM62778""973: The Unicode table files cannot be found in the NLS directory or in the search path. Code page: number Country: number" in Appendix C.974: The Unicode table files are corrupt.SETPASSAction: See message IDREF="FM63405""974: The Unicode table files are corrupt." in Appendix C.975: The Unicode table files cannot be opened because there are already too many open files. Close some files or modify your CONFIG.SYS file.SETPASSAction: See message IDREF="FM49793""975: The Unicode table files cannot be opened because there are already too many open files. Close some files or modify your CONFIG.SYS file." in Appendix C.998: The message file found (<utility_name>.MSG) is an incorrect version. The correct version is <number>. See your network supervisor for assistance.SETPASSAction: See message IDREF="FM91957""998: The message file found (utility_name.MSG) is an incorrect version. The correct version is number. See your network supervisor for assistance." in Appendix C.PAGENUM=1081 ID="BP1075"999: The message file for this utility cannot be found.SETPASSAction: See message IDREF="FM69424""999: The message file for this utility cannot be found." in Appendix C.PAGENUM=1082 ID="BP1076"SETTTS100: An invalid control character was encountered in the command line.SETTTSExplanation: SETTTS does not handle control characters.Action: Enter only numbers in the range between 0 and 255 or the letters D or N. Type SETTTS /? to access the online help. For more information about the Transaction Tracking System, see "BOOK="utlrfenu" COLLECTION="nw41"SETTTS" in Utilities Reference or "BOOK="cncptenu" COLLECTION="nw41"TTS" in Concepts.200: The current lock threshold level cannot be obtained.SETTTSExplanation: The utility was unable to get the threshold levels for the server. No other information is available.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.300: The lock threshold level cannot be set.SETTTSExplanation: The utility was unable to set the threshold levels from the server.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.500: Logical level number is invalid. The logical level must be between 0 and 255.SETTTSExplanation: The user typed in characters outside the accepted range.Action: Enter only numbers in the range between 0 and 254 to set the logical level. Type 255 or the letter D to disable the level. Type the letter N to reset the level to normal. Type SETTTS /? to access the online help. For more information about the Transaction Tracking System, see "BOOK="utlrfenu" COLLECTION="nw41"SETTTS" in Utilities Reference or "BOOK="cncptenu" COLLECTION="nw41"TTS" in Concepts.600: Physical level number is invalid. The physical level must be between 0 and 255.SETTTSExplanation: The user typed in characters outside the accepted range.Action: Enter only numbers in the range between 0 and 254 to set the physical level. Type 255 or the letter D to disable the level. Type the letter N to reset the level to normal. Type SETTTS /? to access the online help. For more information about the Transaction Tracking System, see "BOOK="utlrfenu" COLLECTION="nw41"SETTTS" in Utilities Reference or "BOOK="cncptenu" COLLECTION="nw41"TTS" in Concepts.700: This utility works only with Advanced NetWare 2.0 or later.SETTTSExplanation: The user tried to use this utility on a server with an operating system earlier than Advanced NetWare 2.Action: Make sure the server's operating system is an appropriate version. Use NetWare 3 or NetWare 4 if possible.PAGENUM=1083 ID="BP1077"850: The transaction tracking system is not installed on server name.SETTTSExplanation: TTS is not installed.Action: Install TTS on the desired server.875: The transaction tracking system is not available.SETTTSExplanation: TTS is not on this server at this time.Action: Install TTS. If the server is not version 3.x or later, TTS is not supported.901: You are not attached to the specified server.SETTTSAction: See message IDREF="FM84261""901: You are not attached to the specified server." in Appendix C.903: The command line syntax is invalid. For help, type SETTTS /?SETTTSAction: See message IDREF="FM18860""903: The command line syntax is invalid." in Appendix C.905: This utility was unable to initialize the country information.SETTTSAction: See message IDREF="FM55337""905: This utility was unable to initialize the country information." in Appendix C.925: This utility is not supported on Personal NetWare servers. Use the Personal NetWare utilities.SETTTSExplanation: Personal NetWare servers do not recognize this utility.Action: Use the Personal NetWare utilities.970: The attempt to open the Unicode table files failed.SETTTSAction: See message IDREF="FM15675""970: The attempt to open the Unicode table files failed." in Appendix C.971: The workstation does not have enough memory to load the Unicode table files.SETTTSAction: See message IDREF="FM55341""971: The workstation does not have enough memory to load the Unicode table files." in Appendix C.972: Access to the Unicode table files was denied.SETTTSAction: See message IDREF="FM90152""972: Access to the Unicode table files was denied." in Appendix C.PAGENUM=1084 ID="BP1078"973: The Unicode table files cannot be found in the NLS directory or in the search path. Code page: <number>  Country:  <number>SETTTSAction: See message IDREF="FM62778""973: The Unicode table files cannot be found in the NLS directory or in the search path. Code page: number Country: number" in Appendix C.974: The Unicode table files are corrupt.SETTTSAction: See message IDREF="FM63405""974: The Unicode table files are corrupt." in Appendix C.975: The Unicode table files cannot be opened because there are already too many open files. Close some files or modify your CONFIG.SYS file.SETTTSAction: See message IDREF="FM49793""975: The Unicode table files cannot be opened because there are already too many open files. Close some files or modify your CONFIG.SYS file." in Appendix C.999: The message file for this utility cannot be found.SETTTSAction: See message IDREF="FM69424""999: The message file for this utility cannot be found." in Appendix C.PAGENUM=1085 ID="BP1079"SMDR1: An internal error has occurred. An external SMDR requested a connection that cannot be opened.SMDRExplanation: An internal error has occurred in the program. The underlying transport was unable to complete the connection transaction due to a network disruption or failure in the protocol driver (for example, SPXS.NLM, etc.).Action: Retry the operation. If the problem persists, contact your Novell Authorized Reseller.2: An internal error has occurred. The SMDR was unable to provide a thread to service the connection.SMDRExplanation: Normally SMDR creates a thread (communication line) for a new service process for each connection. In this case, the server did not have enough memory for this process.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.3: An internal error has occurred. The SMDR was unable to broadcast a SAP. The SMDR will unload.SMDRExplanation: An internal error has occurred in the program. The SAP protocol failed.Action: Try bringing down the server, then rebooting it. Reload the SMDR. If the problem persists, contact your Novell Authorized Reseller.4: An internal error has occurred. The SMDR was unable to allocate a listening socket. The SMDR will unload.SMDRExplanation: The server may not have enough available memory. The SMDR "listens" for remote SMDRs requesting local access, and uses a listening socket with the underlying transport. If no sockets are available, the SMDR cannot recognize connection requests.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.5: An internal error has occurred. Insufficient memory is available for SMDR tables. The SMDR will unload.SMDRExplanation: The server may not have enough available memory. When SMS resources (such as TSAs or SDIs) are loaded on the server, they register with a SMDR. If the SMDR cannot allocate a table to record these registrations, other SMS modules (local or remote) will not be able to access SMS resources.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.PAGENUM=1086 ID="BP1080"6: An internal error has occurred. The connection number to a module is invalid.SMDRExplanation: An internal error has occurred in the program. An SMS resource user (SBACKUP, for example) is using an obsolete or damaged connection number. No resources (TSAs or SDIs, for example) can be accessed through the connection number given.Action: Report the error to the vendor of the SMS compliant software.7: An internal error has occurred. An invalid parameter was passed.SMDRExplanation: An internal error has occurred in the program. An SMS resource user (SBACKUP, for example) passed corrupted data to an SMS routine. There may be a bug in the program.Action: Report the error to the vendor of the SMS compliant software.8: An internal error has occurred. One or more of the parameters is null or invalid.SMDRExplanation: An internal error has occurred in the program. An SMS resource user (SBACKUP, for example) passed corrupted data to an SMS routine. There may be a bug in the program.Action: Report the error to the vendor of the SMS compliant software.9: The server is unable to allocate sufficient memory.SMDRAction: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.10: An internal error has occurred. The TLI transport underlying SMS has failed.SMDRExplanation: An internal error has occurred in the TLI transport for the SMDR. The likelihood of this error occurring increases as the number of hops between servers increases. The reason for the failure is internal to the supported protocol (SPX, TCP/IP, or ADSP). Heavy traffic can also contribute to the difficulty.Action: Run the backup or restore on a server closer to the target, during off hours. If the problem persists, contact your Novell Authorized Reseller.11: An internal error has occurred. The requested function is not supported.SMDRExplanation: An internal error has occurred. This error message indicates a software malfunction.Action: Report the error to the vendor of the SMS compliant software.PAGENUM=1087 ID="BP1081"12: The named module is already registered to SMDR.SMDRExplanation: SMS resources (TSAs or SDIs, for example) can only be loaded once per server. Subsequent attempts to load multiple copies will result in this error message.Action: None. This message is for information only.13: The SMDR received an encrypted password it could not decode.SMDRExplanation: When SMS resource users (such as SBACKUP) try to connect to remote SMS resources (TSAs or SDIs, for example), the password is encrypted and packed into an SMSP datagram. If the data is corrupted before it is sent, during transmission, or after it is received, the decryption routine will not recognize the data, and the connect attempt will fail.Action: Try to reconnect. If the problem persists, contact your Novell Authorized Reseller.14: The SMDR was unable to encrypt the password.SMDRExplanation: When SMS resource users (such as SBACKUP) try to connect to remote SMS resources (TSAs or SDIs, for example), the password is encrypted and packed into an SMSP datagram. If the data is corrupted before it is sent, during transmission, or after it is received, the decryption routine will not recognize the data, and the connect attempt will fail.Action: Try to reconnect. If the problem persists, contact your Novell Authorized Reseller.15: The named TSA is not loaded on the SMDR. Load the TSA; then try again.SMDRExplanation: The TSA you want to connect to is not loaded on the target computer. The name of the SMDR is the same as the name of the server it is running on. The wrong SMDR name was specified, or the TSA is not loaded. Action: Load the TSA on the correct SMDR and try the operation again.16: The named SMDR is unknown, does not exist, or is not loaded.SMDRExplanation: An invalid SMDR name may have been typed, or one that is outside the SAP advertising scope and is therefore "invisible."Action: Make sure that the SMDR is loaded and the name is specified correctly.17: An external SMDR failed to respond to the connection request.SMDRPAGENUM=1088 ID="BP1082"Explanation: An invalid SMDR name may have been typed, or one that is outside the SAP advertising scope and is therefore "invisible." Visible SMDRs may remain visible somewhat longer than they are available. When SMDR is unloaded, it may still be visible to other servers for a short time. Also, a loaded SMDR may fail to respond to a connection request if the CPU is too busy with higher priority tasks and cannot process the SMDR request within an allotted time.Action: Make sure that the SMDR is properly loaded; then retry the operation. If the problem persists, contact your Novell Authorized Reseller.18: No matching data remains for the given scan parameters.SMDRAction: None. This message is for information only.19: An internal error has occurred. No sockets are available for remote communication. The SMDR will unload.SMDRExplanation: The server may not have enough available memory. The SMDR "listens" for remote SMDRs requesting local access, and it uses a listening socket with the underlying transport. If no sockets are available, the SMDR cannot recognize connection requests.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.20: An internal error has occurred. The protocol selected by the redirector is not available.SMDRExplanation: SMS uses proxy TSAs, loaded on the server, to represent workstations to the SMS architecture. When a workstation (including Macintosh, DOS, Windows, UNIX, etc.) registers with the appropriate proxy TSA on the server, it gives its name, address, and identifies the underlying protocol. When a backup engine connects to the proxy TSA, it assumes it has connected to the actual workstation. However, the proxy TSA informs the backup engine that it is only a proxy, and broadcasts the real workstation address and protocol. At an underlying level, the SMDR disconnects the proxy TSA, and uses the information it has received to try to connect to the real workstation. This error message indicates that the workstation is available only on a protocol not supported by that SMDR, causing the redirection attempt to fail.Action: Replace the SMDR with one that supports the needed protocols and retry the operation. If the problem persists, contact your Novell Authorized Reseller.21: The maximum number of connections allowed through the SMDR (64) has been exceeded.SMDRExplanation: The SMDR allows a maximum of 64 simultaneous connections.Action: Eliminate unneeded connections; then try the operation again.PAGENUM=1089 ID="BP1083"22: An internal error has occurred. A handle is tagged invalid or the pointer to the handle is null.SMDRExplanation: An internal error has occurred in the program. An SMS resource user (SBACKUP, for example) passed corrupted data to an SMS routine. There might be a bug in the software program.Action: Report the error to the vendor of the SMS compliant software.23: An internal error has occurred. The offset to the end of the field did not reference the correct field ending.SMDRExplanation: A data format error occurred in the SIDF data.Action: Retry the operation. If the error recurs, check hardware read-write head, then retry the operation. If the problem persists, the media may be faulty.24: An internal error has occurred. Either the list has no more entries or the specified name space type does not exist.SMDRExplanation: This error indicates to a developer that all of the name spaces in the data set have been represented and processed to completion by SMS.Action: Report the error to the vendor of the SMS compliant software.25: An internal error has occurred. The SIDF data type is corrupted on overflow.SMDRExplanation: This error indicates corrupted data in the file or in the tape format.Action: Retry the operation. If the problem persists, contact your Novell Authorized Reseller.26: An internal error has occurred. The SIDF data type is corrupted on underflow.SMDRExplanation: This error indicates corrupted data in the file or in the tape format.Action: Retry the operation. If the problem persists, contact your Novell Authorized Reseller.27: An internal error has occurred. The SMDR encountered an invalid field identifier.SMDRExplanation: This error indicates corrupted data in the file or in the tape format.Action: Retry the operation. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=1090 ID="BP1084"SMSDI256: An attempt was made to read or write when that access was not granted.SMSDIExplanation: Access has been denied because another application has reserved the requested device or medium.Action: Select a medium or device to which the user has access and make sure that access was granted before proceeding with the read or write operation.257: Upon checking the buffer header on a read operation, the SMSDI determined that it is not what it was expecting.SMSDIExplanation: The medium was not written to correctly.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.258: BufferSize requested is not sufficient for application's and SMSDI's blockHeaderSize.SMSDIExplanation: An internal error occurred between SBACKUP and SMSDI.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.259: A media error was encountered, but was corrected by the driver.SMSDIExplanation: The read or write operation was successful, but the device had to use its error correction feature to recover the data.Action: Replace the device or medium as soon as possible.260: The deviceHandle passed is invalid.SMSDIExplanation: The selected device is no longer valid or has changed.Action: Try selecting the device again. If the problem persists, contact your Novell Authorized Reseller.261: While getting the list of devices available, a change in the list of available devices has occurred. Restart the NWSMSDListDevices.SMSDIExplanation: A device was added or deleted while SBACKUP was getting the list of devices.Action: Select the "Storage Device Administration" menu again to rescan the devices.PAGENUM=1091 ID="BP1085"262: Device exists but is not available (for example, already subjugated by another application in a nonsharing mode).SMSDIExplanation: The requested device has been reserved by another application.Action: Select another device, or find the application that has reserved the device and free it from that application.263: Device does not exist. SMSDIExplanation: TA device error probably caused the device to become deactivated, or the device driver was unloaded.Action: Re-scan the device list by reselecting the "Storage Device Administration" menu again.264: Early warning was detected on the media.SMSDIExplanation: The medium has reached the early warning. This is dealt with by the engine.Action: None. This message is for information only.265: The end of media was detected.SMSDIExplanation: The requested session was not found.Action: Request another session or insert another medium.266: The medium has been unexpectedly changed since it was last identified.SMSDIExplanation: SMSDI keeps track of what medium it expects to find in the device. It verifies the medium before executing reads or writes. In this instance, the wrong medium was in the device.Action: Put the correct medium into the device, or reselect the current medium from the "Storage Device Administration" menu item.267: An unexpected internal SMSDI error has occurred.SMSDIExplanation: An internal error has occurred.Action: Write down the sequence of events that led to this error, along with any other error messages. If the problem persists, contact your Novell Authorized Reseller.268: An invalid connection number was passed to SMSDI.SMSDIExplanation: An internal error has occurred in the program that SBACKUP was unable to handle.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=1092 ID="BP1086"269: An invalid message number was passed to SMSDI.SMSDIExplanation: An internal error has occurred in the program that SBACKUP was unable to handle.Action: Write down the number of any SBACKUP messages that are displayed with this message. Diagnose and correct the problem from the information in the SBACKUP message if possible. Try again. If the problem persists, contact your Novell Authorized Reseller.270: One or more of the parameters is NULL or invalid.SMSDIExplanation: An internal error has occurred in the program that SBACKUP was unable to handle.Action: Write down the number of any SBACKUP messages that are displayed with this message. Diagnose and correct the problem from the information in the SBACKUP messages, if possible. Try again. If the problem persists, contact your Novell Authorized Reseller.271: NWSMSDWriteSector or NWSMSDReadSector requested fractional sector size.SMSDIExplanation: The media may not be compatible with SMS. If the media is compatible with SMS, this is probably an internal program error.Action: Use SMS compatible media. Try again. If the problem persists, contact your Novell Authorized Reseller.272: An invalid session data type was passed in a control block to NWSMSDWriteSessionData/NWSMSDReadSessionData.SMSDIExplanation: The medium was not written to correctly. This is probably an internal error that SBACKUP was unable to handle.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.273: An invalid destination location was specified.SMSDIExplanation: The medium was not written to correctly. This is probably an internal error that SBACKUP was unable to handle.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.274: Data from media is valid but error correction had to be used to read.SMSDIExplanation: The read or write operation was successful, but the device had to use its error correction feature to recover the data.Action: Replace the device or medium as soon as possible.PAGENUM=1093 ID="BP1087"275: Media Manager reported a failure when attempting the requested read or write operation.SMSDIExplanation: The device or the media reported a hardware failure.Action: Replace the media or service the device.276: The mediaHandle passed is invalid.SMSDIExplanation: The selected media is no longer valid or has changed.Action: Try selecting the media again by selecting the device under the "Storage Device Administration" menu. If the problem persists, contact your Novell Authorized Reseller.277: An attempt was made to label an already labeled media.SMSDIExplanation: This alert is handled by SBACKUP. The message informs the user that a valid label already exists.Action: None. This message is for information only.278: While getting the list of media available, a change in the available media has occurred. Start listing the media from the beginning.SMSDIExplanation: A device was added or deleted while SBACKUP was getting the list of devices.Action: Select the "Storage Device Administration" menu again to rescan the devices.279: A file mark was encountered while reading media. This is not fatal and data in buffer up to number of sectors read is valid.SMSDIExplanation: The media was not correctly written. This is probably an internal error that SBACKUP was unable to handle.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.280: A set mark was encountered while reading the medium. This is not fatal and data in buffer up to number of sectors read is valid.SMSDIExplanation: The medium was not written to correctly. This is probably an internal error that SBACKUP was unable to handle.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.281: An attempt was made to perform an action (for example, Move Media) on a mounted medium which is illegal.SMSDIExplanation: This is probably an internal error that SBACKUP was unable to handle.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=1094 ID="BP1088"282: The medium exists but is not available (for example, already subjugated by another application in a non-sharing mode).SMSDIExplanation: The requested medium has been reserved by another application.Action: Select another medium, or find the application that has reserved the medium and free it from that application.283: The medium does not exist.SMSDIExplanation: The requested medium no longer exists.Action: Select another device under the "Storage Device Administration" menu.284: The medium does not have a valid SMS label.SMSDIExplanation: The medium was not written to correctly. This is probably an internal error that SBACKUP was unable to handle.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.285: The medium has not been mounted using the Mount Media function.SMSDIExplanation: This is probably an internal error that SBACKUP was unable to handle.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.286: The requested operation, if completed, would have resulted in creating media that would not have been SMS compliant.SMSDIExplanation: The media is not SMS compliant.Action: Select another device under the "Storage Device Administration" menu.287: No more connections available for Alert Routines.SMSDIExplanation: This is probably an internal error that SBACKUP was unable to handle.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.288: No memory is available for any size block.SMSDIExplanation: The server may not have enough available memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.PAGENUM=1095 ID="BP1089"289: The application has requested an operation that requires READ access mode, but this has not been granted.SMSDIExplanation: In NetWare 4, this message will only appear if an internal error has occurred.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.290: A call was made to ReadSessionData but the media is at the end of the session [including session and media index].SMSDIExplanation: An internal error has occurred in the program.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.291: The application has requested an operation that requires WRITE access mode, but this has not been granted.SMSDIExplanation: In NetWare 4, this message will only appear if an internal error has occurred in the program.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.292: The request for non-share subjugation failed because the device or medium is already subjugated in share mode by another SMS application or an attempt to perform an operation on a shared medium or device which requires non-share mode.SMSDIExplanation: In NetWare 4, this message will only appear if an internal error has occurred in the program.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.293: SMSDI memory allocation failed.SMSDIExplanation: The server may not have enough available memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.294: The partition is not an SMS medium or partition.SMSDIExplanation: The medium or the partition cannot support SMS media.Action: For a read operation, select an SMS medium. For a write operation, overwrite the device or medium with caution. Just because SMS cannot identify the media does not mean that it contains no valuable data.PAGENUM=1096 ID="BP1090"295: The position requested is not valid (for example, a relative mode was specified but either the expected sessionNumber or the expected blockNumber is NULL).SMSDIExplanation: The medium was not written to correctly. This is probably an internal error that SBACKUP was unable to handle.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.296: The position requested was not located on the media.SMSDIExplanation: The medium was not written to correctly. This is probably an internal error that SBACKUP was unable to handle.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.297: The requested session handle is not valid either because the session was not opened or the medium is no longer positioned within the requested session.SMSDIExplanation: The medium was not written to correctly. This is probably an internal error that SBACKUP was unable to handle.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.298: The specified session header was not found at the location specified, or if a location was not specified, there is not a session header that matches the specified description.SMSDIExplanation: The medium was not written to correctly. You may have inserted the wrong medium. Another possibility is that an internal error occurred that SBACKUP was unable to handle.Action: Insert the medium that contains the requested session or request a session that exists on this medium. Try again. If the problem persists, contact your Novell Authorized Reseller.299: The operation timedout.SMSDIExplanation: The length of time allowed for the requested operation has been exceeded. This may have been due to a media error, a media failure, or a problem with the device.Action: Make sure the device is running and functioning properly. Use the correct media. Try again. If the problem persists, contact your Novell Authorized Reseller.300: The transfer buffer passed was not large enough to hold the entire transfer buffer from the media. SMSDI returned as much of the transfer buffer as would fit.SMSDIExplanation: An internal error has occurred in the program.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=1097 ID="BP1091"301: One or more of the requested transfer requests was not able to be canceled. SMSDI will complete those requests normally.SMSDIExplanation: Even though an error occurred, SMSDI was able to complete the request(s).Action: None. This message is for information only.302: A function was called which is not supported by this version of SMSDI.SMSDIExplanation: A required device driver function is not supported by the current version of SMSDI.Action: Make sure the device driver is a current version and supports SMS. Also, make sure that the server is running the most recent version of SMSDI. Upgrade the device driver, device, or SMSDI if necessary. Try again. If the problem persists, contact your Novell Authorized Reseller.303: An SMSDI function was asked to perform a service that is not supported in this version of SMSDI.SMSDIExplanation: An internal error has occurred in the program.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.304: The NetWare operating system returned an error.SMSDIExplanation: An error occurred in the NetWare operating system.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.305: The device driver or device itself returned an error.SMSDIExplanation: The device or the medium may have failed.Action: Make sure the device is running and functioning properly. Check the medium. Try again. If the problem persists, contact your Novell Authorized Reseller.306: An I/O function was successfully aborted.SMSDIExplanation: An internal error occurred that SBACKUP could not handle.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.307: An I/O function was aborted due to a previous error.SMSDIExplanation: An internal error occurred that SBACKUP could not handle.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=1098 ID="BP1092"308: An attempt was made to use a function that is not supported by the device driver.SMSDIExplanation: A required device driver function is not supported by the current device driver or device.Action: Make sure the device driver is a current version and supports SMS. Upgrade the device driver or device if necessary. Try again. If the problem persists, contact your Novell Authorized Reseller.309: Invalid data was encountered on the media.SMSDIExplanation: The medium was not written to correctly. It may be defective.Action: Use a new device or medium.310: The medium is write protected.SMSDIExplanation: The write-protect switch on the medium is set.Action: Use another medium or remove the write-protection from the currently selected medium.311: The device driver or device itself returned an unknown error.SMSDIExplanation: An unknown error occurred in the device driver or the device itself.Action: Make sure the device is functioning properly. Also make sure the server is running a current, uncorrupted copy of the driver. Then try again. If the problem persists, contact your Novell Authorized Reseller.312: The header is too large to fit in a physical sector.SMSDIExplanation: The medium may not be compatible with SMSDI.Action: Make sure the medium is compatible with SMS. Try again. If the problem persists, contact your Novell Authorized Reseller.313: The medium is not formatted.SMSDIExplanation: This type of medium needs to be formatted before using.Action: Format the medium.314: The medium is blank.SMSDIExplanation: This message is associated with a prompt from SBACKUP telling the user to label the medium.Action: None. This message is for information only.PAGENUM=1099 ID="BP1093"315: The beginning of media was detected.SMSDIExplanation: An internal program error has occurred.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.316: The sector size is not valid.SMSDIExplanation: SMS cannot support the sector size of the currently selected medium.Action: Select a new medium.317: The medium was written in old media format and is therefore not appendable.SMSDIExplanation: The NetWare 4 version of SBACKUP cannot append to NetWare 3.11 media.Action: Back up to NetWare 4 media.318: The medium is unavailable for use by an SMS application.SMSDIExplanation: The requested device or medium has been reserved by another application.Action: Select another device or medium, or find the application that has reserved the media and free it from that application.319:  Starting a Work to do failed. Usually out of memory.SMSDIExplanation: SMSDI tried to start a new execution thread, but not enough memory was available.Action: Remove one or more NLM programs from memory, or upgrade to more memory in the server. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.320: The mediaHandle passed is invalid.SMSDIExplanation: The application passed a media handle to SMSDI that never existed or is no longer valid.Action: This problem is normally handled by the application. However, if this error does appear, try selecting the device or medium again and restarting the operation.321: The specific info change requested for the object is not changeable.SMSDIExplanation: The application tried to change a parameter for a device or medium that the device or medium does not allow to be changed.Action: None. This message is for information only.PAGENUM=1100 ID="BP1094"323: The magazine does not exist.SMSDIExplanation: The requested magazine no longer exists.Action: Select another device under the "Storage Device Administration" menu. 324: Magazine exists but is not available (for example, already subjugated by another application in a non-sharing mode).SMSDIExplanation: The requested magazine has been reserved by another application.Action: Select another magazine, or search for the application that has reserved the magazine and free it from that application.325: A requested abort is pending.SMSDIExplanation: The application normally deals with this message internally. It means that the request to abort an operation has been accepted and the abort operation is pending.Action: None. This message is for information only.326: An undefined error occurred.SMSDIExplanation: An error from the device driver that is not recognized by the NetWare operating system has been reported to SMSDI.Action: Contact a Novell Authorized Service Center.327: Cannot append to media written with SBACKUP version 3.11.SMSDIExplanation: While SMSDI will read SBACKUP for NetWare 3.11 media, it will not write the NetWare 3.11 media format. Therefore, it will not append a NetWare 4.x session onto media that was written using NetWare 3.11 SBACKUP.Action: Use another medium to write the requested session.328: The device is either not active or is offline.SMSDIExplanation: The device driver has been removed, or the device has been deactivated or is offline.Action: Perform the requested operation on another device or reactivate the requested device.329: The magazine is either not active or is offline.SMSDIExplanation: The magazine has been removed or is otherwise not active.Action: Choose another magazine or reactivate the magazine and reselect it.PAGENUM=1101 ID="BP1095"330: The media is either not active or is offline.SMSDIExplanation: The media has been removed or is otherwise not active.Explanation: Choose another magazine or reactivate the medium and reselect it.331: The media has been using a pre-release version of SMSDI. Don't use this media for production media.SMSDIExplanation: The medium has been written using pre-release software. The media format used on this medium may not be compatible with released software.Action: Do not use this media for production data.332: Attempted to open a session for writing or write data while not at end of media.SMSDIExplanation: The engine (such as SBACKUP) has not placed the media at the end. Media can only be appended to.Action: Contact the third-party engine developer, or contact your Novell Authorized Reseller.333: The transfer buffers have been received out of order.SMSDIExplanation: SMSDI has detected an incorrect sequence for the returned transfer buffers. This is usually caused by an error from the originating system of this media, because an error caused by the NetWare operating system would generate error 334.Action: Do not use data recovered from the media until the problem has been resolved. Contact the third-party engine developer, or contact your Novell Authorized Reseller.334: The transfer buffers have been received out of order from the OS.SMSDIExplanation: The operating system returned the transfer buffers out of the expected sequence. This error is most likely caused by a device driver.Action: Do not use data recovered from the media until the problem has been resolved. Contact your Novell Authorized Reseller.335: The transfer buffer does not belong to the opened session.SMSDIExplanation: This is used when reading interleaved sessions to notify SBACKUP that a transfer buffer is to be ignored. This error is only to be used internally by SBACKUP and should not be displayed. Action: Contact the third-party engine developer, or contact your Novell Authorized Reseller.PAGENUM=1102 ID="BP1096"336: NWSMSDSessionOpenForReading excludes all further session opens on the media handle.SMSDIExplanation: An attempt to open a write session has been issued on a media that already has a session open for writing. Open sessions for reading exclude all other open attempts.Action: Wait until the currently open session finishes and retry the operation.337: NWSMSDSessionOpenForWriting excludes all further session open with different transfer buffer sizes.SMSDIExplanation: All interleaved write sessions must have the same transfer buffer size. An attempt to open a write session with a different transfer buffer size than the one already open was attempted.Action: Wait until the currently open session finishes and retry the operation.338: NWSMSDSessionOpenForReading was attempted while a session is open for writing on the media handle.SMSDIExplanation: An attempt to open a read session while a write session is in progress was made. A read session may not be opened while a write session is in process.Action: Wait until the currently open session finishes and retry the operation.PAGENUM=1103 ID="BP1097"SNMP9: Could not send IPX reply.SNMPExplanation: SNMP was not able to send an SNMP response packet over the IPX transport.Action: Update the TLI.NLM, IPXS.NLM, and STREAMS.NLM files on the server displaying this message.PAGENUM=1104 ID="BP1098"SNMP ClientContact your Novell Authorized Reseller.PAGENUM=1105 ID="BP1099"SNMPLOG0: Failed to get the message table. Exiting.SNMPLOGExplanation: SNMPLOG could not locate its messages.Action: When using NetWare 3.1x servers or routers, make sure that the directory where SNMPLOG is located is included in the search path.1:  /dev/[nipx | udp] returned unexplained event bits (number) from poll.SNMPLOGExplanation: An error was detected in NetWare's IPX or UDP streams implementation.Action: Contact your Novell Authorized Reseller.2: SNMP logging discontinued.SNMPLOGExplanation: SNMPLOG is exiting because of the error that SNMPLOG just reported to the console.Action: If the error SNMPLOG encountered is intermittent, SNMPLOG can be loaded again to resume SNMP logging.3: Poll function failed.SNMPLOGExplanation: SNMPLOG has detected an internal error.Action: Contact your Novell Authorized Reseller.4: Could not open filename.SNMPLOGExplanation: The requested log file could not be opened.Action: Correct the problem by using the text explaining why the I/O system refused to open the file.5: SNMP logging for [IPX | UDP] is temporarily unavailable.SNMPLOGExplanation: SNMPLOG can't log SNMP traps arriving over the indicated protocol. SNMPLOG will resume logging SNMP traps when the protocol becomes available.Action: Usually no action needs to be taken because the SNMPLOG adjusts in response to a console action. To restore logging of the protocol, correct the problem that SNMPLOG detected. For example, load the appropriate protocol support NLM program.PAGENUM=1106 ID="BP1100"6: Continuous trouble with [IPX | UDP]. Permanently disabled.SNMPLOGExplanation: The indicated protocol stack has encountered a problem. The SNMPLOG will no longer log SNMP traps delivered on it.Action: Correct the problem with the protocol stack and reload SNMPLOG.7: Support for [IPX | UDP] enabled.SNMPLOGExplanation: SNMPLOG is now logging SNMP traps arriving on the indicated protocol.Action: None. This message is for information only.10: Disconnecting [IPX | UDP] support.SNMPLOGExplanation: SNMPLOG is unloading and has stopped logging SNMP traps for the indicated protocol.Action: To resume logging SNMP traps, load SNMPLOG back into the server or router.13: Receive on device /dev/[nipx | udp] failed.SNMPLOGExplanation: SNMPLOG encountered an unexpected failure when reading the next packet from the indicated protocol device.Action: If possible, correct the problem with the protocol support module. If the reason the device failed is cannot be determined, contact your Novell Authorized Reseller.PAGENUM=1107 ID="BP1101"SPXS5: There is insufficient memory for allocation.SPXSExplanation: SPXII was unable to allocate the requested amount of memory for the Protocol ID table or the board registration table. The server may not have enough available memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.6: There insufficient memory for allocation.SPXSExplanation: SPXII was unable to allocate the requested amount of memory for the Protocol ID table or the board registration table. The server may not have enough available memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.7: SPXII cannot be configured.SPXSExplanation: An attempt was made to configure SPXII, but SPXII parameters cannot be configured.Action: None. This message is for information only.9: There is no LAN board registered with LSL.SPXSExplanation: An attempt was made to load SPXS before loading a network board. The operating system must have a board registered with the LSL with a valid IPX and SPX frame type to initialize SPXS.Action: Load a network board; then load SPXS again.10, 11: The name device cannot be loaded by STREAMS.SPXSExplanation: This message is probably preceded by error messages from the STREAMS module. You may have specified a duplicate or invalid device name, or you may be trying to load too many devices.Action: Make sure that the specified device name is valid, and is not a duplicate. Refer to any preceding error messages to help determine the exact cause of the problem.12: Module_name STREAM module still in use. Unloading will have unknown consequences.SPXSExplanation: The indicated module is currently being referenced by another NLM program or NetWare driver. Unloading the module while it is being used may produce unwanted results.Action: Wait until the module is not being used; then retry the unload.PAGENUM=1108 ID="BP1102"16: SPXS requires STREAMS version version to operate correctly; initialization unable to complete. Please load correct version of STREAMS.NLM before attempting to reload SPXS.SPXSExplanation: The server is not using the correct version of STREAMS.Action: Get a current version of STREAMS.NLM.PAGENUM=1109 ID="BP1103"STREAMS6: The routine timeout could not allocate number bytes of memory. This may cause applications to lock up waiting for a timer event that will never happen.STREAMSExplanation: The server may not have enough available memory. The function could not allocate the requested number of bytes for the timer structure. Applications waiting for timer events might hang when these events do not occur.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.9: Number invalid handles were passed to StreamCancel from StreamCleanup. A STREAMS protocol module or device may have been unloaded prematurely!STREAMSExplanation: The indicated number of invalid file handles were passed to the function "StreamCancel" from "StreamCleanup." A STREAMS protocol module might have been unloaded prematurely. This is not a fatal error, but allocated memory pieces might become lost.Action: If the problem persists, contact your Novell Authorized Reseller or the application developer.16: An invalid streamtab pointer was used for protocol device name; device cannot be installed.STREAMSExplanation: A called function could not install the device because of an invalid streamtab pointer.Action: If you have access to developer documentation, consult it for the proper streamtab pointer format. If the problem persists, contact your Novell Authorized Reseller or the application developer.18:The protocol device name name is too long; device cannot be installed.STREAMSExplanation: The name specified for the device is too long.Action: If you have access to developer documentation, consult it for the valid name length. If the problem persists, contact your Novell Authorized Reseller or the application developer.PAGENUM=1110 ID="BP1104"21: An invalid streamtab pointer was used for protocol module device_name; module cannot be installed.STREAMSExplanation: A called function could not install the module because of an invalid streamtab pointer.Action: If you have access to developer documentation, consult it for the proper streamtab pointer format. If the problem persists, contact your Novell Authorized Reseller or the application developer.23: The protocol module name device_name is too long; module cannot be installed.STREAMSExplanation: The name specified for the module was too long.Action: If you have access to developer documentation, consult it for the valid name length. If the problem persists, contact your Novell Authorized Reseller or the application developer.28: Unable to allocate a queue within the sth_ipush function; module not added to stream.STREAMSExplanation: The server may not have enough available memory. The sth_ipush function could not allocate a queue, so the new module was not added to the stream.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. If the problem persists, contact your Novell Authorized Reseller.29: Unable to unlink modules within the sth_osr_close function.STREAMSExplanation: The sth_osr_close function could not unlink the modules.Action:  If the problem persists, contact your Novell Authorized Reseller or the application developer.32: Could not perform the I/O control operation from within the sth_unlink function; closing anyway.STREAMSExplanation: The sth_unlink function could not perform ioctl, but it will continue closing the application or process anyway.Action:  If the problem persists, contact your Novell Authorized Reseller or the application developer.PAGENUM=1111 ID="BP1105"87: Could not allocate a callback control structure within the bufcall function. This may cause applications to lock up waiting for a callback event that will never happen.STREAMSExplanation: The server may not have enough available memory. Bufcall could not allocate a callback control structure. Not having a callback control structure might cause the application to lock up while waiting for a callback event that will never happen.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.88: An undetermined cleanup error occurred with device name; unloading will continue.STREAMSExplanation: The exact cause of this error is unknown. However, the unloading procedure for the device will continue.Action: None. This message is for information only.89: An undetermined cleanup error occurred with module name; unloading will continue.STREAMSExplanation: The exact cause of this error is unknown. However, the unloading procedure for the module will continue.Action: None. This message is for information only.90: The message name was too long to print using mi_printf.STREAMSExplanation: The mi_printf function cannot print this message because the messages is too long.Action: If the problem persists, contact your Novell Authorized Reseller, the application developer, or the protocol developer.91: An invalid handle was passed to StreamCancel from StreamCleanup. A STREAMS protocol module or device may have been unloaded prematurely!STREAMSExplanation: The indicated number of invalid file handles were passed to the function "StreamCancel" from "StreamCleanup." A STREAMS protocol module might have been unloaded prematurely. This is not a fatal error, but allocated memory might be lost.Action: If the problem persists, contact your Novell Authorized Reseller or the application developer.95: Unable to locate signal structure in sig table listSTREAMSExplanation: A function was unable to locate the signal structure from within the sig table list. The signal will be lost and the application might hang.Action: If the problem persists, contact your Novell Authorized Reseller or the application developer.PAGENUM=1112 ID="BP1106"113: An undetermined initialization error occurred with device name; STREAMS cannot load successfully.STREAMSExplanation: An unknown error prevented the indicated device from being initialized. This device is necessary for STREAMS to operate correctly.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.114: An undetermined initialization error occurred with module name; STREAMS cannot load successfully.STREAMSExplanation: An unknown error prevented the indicated module from being initialized. This module is necessary for STREAMS to operate correctly.Action: Try again. If the problem persists, contact your Novell Authorized Reseller or the application developer.115: An undetermined cleanup error occurred with device name; unloading will continue.STREAMSExplanation: The exact cause of this error is unknown. However, the unloading procedure for the device will continue.Action: None. This message is for information only.116: An undetermined cleanup error occurred with module name; unloading will continue.STREAMSExplanation: The exact cause of this error is unknown. However, the unloading procedure for the module will continue.Action: None. This message is for information only.120: Attempted to send a signal to an NLM not initialized for signals; signal ignored.STREAMSExplanation: The NLM program has not been initialized to receive the controlling signals.Action: Initialize the NLM program to receive and process signals. If the problem persists, contact your Novell Authorized Reseller or the application developer.121: NLM signal thread not waiting for a signal; number signals have been ignored.STREAMSExplanation: The signal thread was not waiting for a signal, so it ignored the signals it received.Action: None. This message is for information only.PAGENUM=1113 ID="BP1107"131: Unable to create CLIB thread for controlling tty.STREAMSExplanation: The controlling tty is used for some protocol management functions that will not be available.Action: If the problem persists, contact your Novell Authorized Reseller or the application developer.PAGENUM=1114 ID="BP1108"SYSTIME100: This utility cannot get the time and date from the server.SYSTIMEExplanation: The utility might not be attached to the network. Another possibility is that a problem occurred in getting the information across the wire.Action: Make sure that the user is logged in or attached to the network.200: This utility was unable to set the work station time and date.SYSTIMEExplanation: An invalid time and date format was entered.Action: Check the DOS documentation for the correct format.900: The default server cannot be found.SYSTIMEAction: See message IDREF="FM81494""900: The default server cannot be found." in Appendix C.901: You are not attached to the specified server.SYSTIMEAction: See message IDREF="FM84261""901: You are not attached to the specified server." in Appendix C.903: The command line syntax is invalid.SYSTIMEAction: See message IDREF="FM18860""903: The command line syntax is invalid." in Appendix C.904: The server name is invalid.SYSTIMEAction: See message IDREF="FM42246""904: The server name is invalid." in Appendix C.905: This utility was unable to initialize the country information.SYSTIMEAction: See message IDREF="FM55337""905: This utility was unable to initialize the country information." in Appendix C.917: This utility was unable to set the context.SYSTIMEAction: See message IDREF="FM32126""917: This utility was unable to set the context." in Appendix C.970: The attempt to open the Unicode table files failed.SYSTIMEAction: See message IDREF="FM15675""970: The attempt to open the Unicode table files failed." in Appendix C.PAGENUM=1115 ID="BP1109"971: The workstation does not have enough memory to load the Unicode table files.SYSTIMEAction: See message IDREF="FM55341""971: The workstation does not have enough memory to load the Unicode table files." in Appendix C.972: Access to the Unicode table files was denied.SYSTIMEAction: See message IDREF="FM90152""972: Access to the Unicode table files was denied." in Appendix C.973: The Unicode table files cannot be found in the NLS directory or in the search path. Code page: <number>  Country:  <number>SYSTIMEAction: See message IDREF="FM62778""973: The Unicode table files cannot be found in the NLS directory or in the search path. Code page: number Country: number" in Appendix C.974: The Unicode table files are corrupt.SYSTIMEAction: See message IDREF="FM63405""974: The Unicode table files are corrupt." in Appendix C.975: The Unicode table files cannot be opened because there are already too many open files. Close some files or modify your CONFIG.SYS file.SYSTIMEAction: See message IDREF="FM49793""975: The Unicode table files cannot be opened because there are already too many open files. Close some files or modify your CONFIG.SYS file." in Appendix C.998: The message file found (<utility_name>.MSG) is an incorrect version. The correct version is <number>. See your network supervisor for assistance.SYSTIMEAction: See message IDREF="FM91957""998: The message file found (utility_name.MSG) is an incorrect version. The correct version is number. See your network supervisor for assistance." in Appendix C.999: The message file for this utility cannot be found.SYSTIMEAction: See message IDREF="FM69424""999: The message file for this utility cannot be found." in Appendix C.PAGENUM=1116 ID="BP1110"TASKID18: Invalid command line argument! Use /? or /H for command line help information.TASKIDExplanation: TASKID was followed by an invalid argument on the command line.Action: For information, type TASKID /? to access the online help screen, or see "BOOK="ws_d1enu" COLLECTION="nw41"Setting Up Network Support for Task-Switching Environments" in NetWare Client for DOS and MS Windows User Guide.19: TASKID was not unloaded. TASKID has not been loaded. TASKID must be loaded in memory before it can be unloaded.TASKIDExplanation: TASKID was not unloaded because a copy of TASKID had never been loaded.Action: None. This message is for information only.20: TASKID was not unloaded. Interrupt 8h has been hooked. Unload the TSR that hooked interrupt 8h before unloading TASKID.TASKIDExplanation: Another application is using this interrupt. TASKID cannot be unloaded until the other application is unloaded.Action: Unload the TSR (terminate-and-stay-resident) program that is using interrupt 8h; then unload TASKID.21: TASKID was not unloaded. Interrupt 2Fh has been hooked. Unload the TSR that hooked interrupt 2Fh before unloading TASKID.TASKIDExplanation: TASKID was not unloaded because an application was loaded in memory after TASKID that is using interrupt 2Fh.Action: Unload the TSR (terminate-and-stay-resident) program that is using interrupt 2Fh; then unload TASKID.22: TASKID reports there were outstanding TASKID requests. Run TBMI /D and TASKID /D to find the outstanding requests.TASKIDExplanation: TASKID was not unloaded due to outstanding requests with TBMI.Action: Use the TBMI /D option and the TASKID /D option to find the outstanding TASKID requests; then unload TASKID.PAGENUM=1117 ID="BP1111"23: TASKID was not loaded. TBMI is not loaded. TBMI (version 1.x) must be loaded before TASKID.TASKIDExplanation: TASKID was not loaded because TBMI was not resident in memory. TBMI (version 1.x) must be resident in memory before TASKID can be successfully loaded.Action: Load TBMI 1.x; then load TASKID.24: TASKID was not loaded. TASKID has already been loaded. Only one copy of TASKID can be loaded per VM (virtual machine).TASKIDExplanation: TASKID was not loaded because TASKID was already resident in memory. TASKID can be loaded only once per DOS session.Action: Do not attempt to load more than one copy of TASKID per DOS session.25: TASKID was not loaded. Windows 3.0 not running. TASKID is specially designed to run under Windows 3.0 only.TASKIDExplanation: TASKID was not loaded because Windows 3.0 was not running. TASKID can be loaded only from a DOS prompt under Windows 3.0.Action: Start Windows 3.0; then load TASKID from a DOS prompt.PAGENUM=1118 ID="BP1112"TBMI232: Cannot find a TBMI2 module to unload.TBMI2Explanation: The TBMI2/u option was entered on the command line, but no version of TBMI2 is currently loaded in memory.Action: None. This message is for information only.33: TBMI2 was not unloaded because the currently loaded version of TBMI2 is different from the version of this TBMI2 module.TBMI2Explanation: The TBMI2 /u option was entered on the command line, but the version of TBMI2 currently loaded in memory is different from the TBMI2 version you are trying to unload.Action: Unload the version of TBMI2 that is currently loaded in memory. To access the help screen, type TBMI2 /?. For more information, see "BOOK="ws_d1enu" COLLECTION="nw41"Setting Up Network Support for Task-Switching Environments" in NetWare Client for DOS and MS Windows User Guide.34: TBMI2 was not unloaded because a task switcher is running. Exit the task switcher before unloading TBMI2.TBMI2Explanation: The TBMI2 /u option was entered on the command line; however, a task switcher is running in memory.Action: Exit the task switcher; then try to unload TBMI2 again. To access the help screen, type TBMI2 /?. For more information, see "BOOK="ws_d1enu" COLLECTION="nw41"Setting Up Network Support for Task-Switching Environments" in NetWare Client for DOS and MS Windows User Guide.35: TBMI2 was not unloaded because Windows is running. Exit Windows before unloading TBMI2.TBMI2Explanation: The TBMI2 /u option was entered on the command line; however, Windows is running.Action: Exit Windows; then try to unload TBMI2 again. To access the help screen, type TBMI2 /?. For more information, see "BOOK="ws_d1enu" COLLECTION="nw41"Setting Up Network Support for Task-Switching Environments" in NetWare Client for DOS and MS Windows User Guide.PAGENUM=1119 ID="BP1113"36: TBMI2 was not unloaded. Interrupt 2Fh has been hooked. Unload the TSR that hooked interrupt 2Fh before unloading TBMI2.TBMI2Explanation: A TSR (terminate-and-stay-resident) program is using interrupt 2Fh. TBMI2 cannot be unloaded until the other TSR is unloaded.Action: Unload the TSR (terminate-and-stay-resident) program that is using interrupt 2Fh; then unload TBMI2. To access the help screen, type TBMI2 /?. For more information, see "BOOK="ws_d1enu" COLLECTION="nw41"Setting Up Network Support for Task-Switching Environments" in NetWare Client for DOS and MS Windows User Guide.37: TBMI2 cannot be unloaded because interrupt 64h has been hooked. Unload the TSR that hooked interrupt 64h before unloading TBMI2.TBMI2Explanation: A TSR (terminate-and-stay-resident) program is using interrupt 64h. TBMI2 cannot be unloaded until the other TSR is unloaded.Action: Unload the TSR (terminate-and-stay-resident) program that is using interrupt 64h; then unload TBMI2. To access the help screen, type TBMI2 /?. For more information, see "BOOK="ws_d1enu" COLLECTION="nw41"Setting Up Network Support for Task-Switching Environments" in NetWare Client for DOS and MS Windows User Guide.38: TBMI2 was not unloaded because interrupt 7Ah has been hooked. Unload the TSR that hooked interrupt 7Ah before unloading TBMI2.TBMI2Explanation: A TSR (terminate-and-stay-resident) program is using interrupt 7Ah. TBMI2 cannot be unloaded until the other TSR is unloaded.Action: Unload the TSR (terminate-and-stay-resident) program that is using the Int7AHandler interrupt; then unload TBMI2. To access the help screen, type TBMI2 /?. For information on workstation configurations, see "BOOK="ws_d1enu" COLLECTION="nw41"Setting Up Network Support for Task-Switching Environments" in NetWare Client for DOS and MS Windows User Guide.39: TBMI2 reports there were outstanding TASKID IDs. Run TASKID /d to find the outstanding IDs.TBMI2Explanation: The TBMI2 /u option was executed from the command line, but TBMI2 detected that all instances of TASKID had not been unloaded.Action: Use the TASKID /d option to find the instances of TASKID that have not been unloaded. Use the TASKID /u option to unload all instances of TASKID, then unload TBMI2.PAGENUM=1120 ID="BP1114"40: TBMI2 was not loaded. IPX is not loaded or is the wrong version or the installed IPX is the wrong version.TBMI2Explanation: An attempt was made to load TBMI2 (version 3.01) after loading a version of IPX that does not support TBMI2 (version 3.01).Action: Get the latest version of IPX from your Novell Authorized Reseller.41: The TBMI2 module has already been loaded.TBMI2Explanation: The user tried to load a second copy of TBMI or TBMI2 into memory.Action: Do not attempt to load a second copy of TBMI or TBMI2 into memory.42: TBMI2 cannot be loaded while Windows is active.TBMI2Explanation: The user attempted to load TBMI2 from a DOS box in Windows.Action: Exit Windows and load TBMI2; then restart Windows.43: TBMI2 cannot be loaded while a DOS task switcher is active.TBMI2Explanation: An attempt was made to load TBMI2, but either a task-switching application or an operating system is already running.Action: Exit the task-switching application and load TBMI2; then restart the task-switching application. To access the help screen, type TBMI2 /?. For more information, see "BOOK="ws_d1enu" COLLECTION="nw41"Setting Up Network Support for Task-Switching Environments" in NetWare Client for DOS and MS Windows User Guide.44: The workstation doesn't have enough memory for TBMI2 to allocate the minimum number of ECB buffers.TBMI2Explanation: The server does not have enough memory available to allocate the minimum number of Event Control Block (ECB) buffers.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network and "BOOK="superenu" COLLECTION="nw41"Resolving Event Control Block Allocation Errors" in Supervising the Network. To access the help screen, type TBMI2 /?. For information, see "BOOK="ws_d1enu" COLLECTION="nw41"Setting Up Network Support for Task-Switching Environments" in NetWare Client for DOS and MS Windows User Guide.45: The specified configuration file could not be opened. TBMI2 was loaded using NET.CFG.TBMI2Explanation: An attempt was made to execute the TBMI2 /C=filename option; however, the specified file could not be found.PAGENUM=1121 ID="BP1115"Action: Make sure the filename was spelled correctly, or check the file's current location in the directory structure. Correct the entry in the NET.CFG file, reboot the computer, and do the operation again. To access the help screen, type TBMI2 /?. For information, see "BOOK="ws_d1enu" COLLECTION="nw41"Setting Up Network Support for Task-Switching Environments" in NetWare Client for DOS and MS Windows User Guide.46: Set ECB value to maximum number allowed.TBMI2Explanation: The maximum number of Event Control Blocks (ECBs) allowed is 255. This number has been exceeded.Action: Make sure the ECB count is between 10 and 255. If you consistently get ECB allocation errors, see "BOOK="superenu" COLLECTION="nw41"Resolving Event Control Block Allocation Errors" in Supervising the Network. To access the help screen, type TBMI2 /?. For more information, see "BOOK="ws_d1enu" COLLECTION="nw41"Setting Up Network Support for Task-Switching Environments" in NetWare Client for DOS and MS Windows User Guide.47: The entry on line number of the configuration file was not recognized. Invalid entry ignored.TBMI2Explanation: An invalid entry was included in the configuration file on the line indicated.Action: Check the NET.CFG file for the invalid entry on the line indicated. To access the help screen, type TBMI2 /?. For more information, see "BOOK="ws_d1enu" COLLECTION="nw41"Setting Up Network Support for Task-Switching Environments" in NetWare Client for DOS and MS Windows User Guide.48: Missing or invalid ON/OFF value for file entry on line number of the configuration file. Entry ignored.TBMI2Explanation: An ON/OFF configuration entry is missing an ON or OFF value.Action: Check the NET.CFG file for the missing value on the line indicated. Rewrite the line or add the missing value, reboot the computer, and do the operation again. To access the help screen, type TBMI2 /?. For more information, see "BOOK="ws_d1enu" COLLECTION="nw41"Setting Up Network Support for Task-Switching Environments" in NetWare Client for DOS and MS Windows User Guide.49: Missing or invalid value for config option on line number of the configuration file. Entry ignored.TBMI2Explanation: An entry in the configuration file had an invalid or missing value.Action: Check the NET.CFG file for the invalid or missing value on the line indicated. Rewrite the line or add the missing value, reboot the computer, and do the operation again. To access the help screen, type TBMI2 /?. For more information, see "BOOK="ws_d1enu" COLLECTION="nw41"Setting Up Network Support for Task-Switching Environments" in NetWare Client for DOS and MS Windows User Guide.PAGENUM=1122 ID="BP1116"50: Resident TBMI2 or TBMI is a different version.TBMI2Explanation: The version of TBMI or TBMI2 in memory is different from the one being executed at the command line.Action: Unload TBMI or TBMI2 from memory; then load the same version of TBMI or TBMI2 that is being executed at the command line. To access the help screen, type TBMI2 /?. For more information, see "BOOK="ws_d1enu" COLLECTION="nw41"Setting Up Network Support for Task-Switching Environments" in NetWare Client for DOS and MS Windows User Guide.51: Windows cannot be loaded in enhanced mode while TBMI2 is installed. Unload TBMI2 and then load Windows.TBMI2Explanation: Windows cannot be loaded in enhanced mode while TBMI2 is installed. Action: Unload TBMI or TBMI2 from memory, load Windows in standard mode, then load TBMI or TBMI2. To access the help screen, type TBMI2 /?. For more information, see "BOOK="ws_d1enu" COLLECTION="nw41"Setting Up Network Support for Task-Switching Environments" in NetWare Client for DOS and MS Windows User Guide.PAGENUM=1123 ID="BP1117"TCPCON34: Could not get resource tag. TCPCONExplanation: TCPCON could not get a resource tag to start the NLM program. This usually means the server is low on memory. Action: Increase the available memory. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. Reload TCPCON when more memory is available.35: Could not initialize SNMP. TCPCONExplanation: TCPCON could not establish communication with SNMP. This error usually occurs if the server is low on memory or if the SNMP version isn't compatible with TCPCON version. Action: Use NetWare Administrator or MONITOR to determine if the server is low on memory. MARK=BULLETIf the server is low on memory, see "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. Reload TCPCON when more memory is available. If the server is not low on memory, the server probably has incompatible versions of SNMP.NLM and TCPCON.NLM. Record the version numbers of SNMP.NLM and TCPCON.NLM, then contact your Novell Authorized Reseller.36: Could not initialize TUI.TCPCONExplanation:  TCPCON could not establish communication with the Textual User Interface (TUI) library. This error usually occurs if the server is low on memory or if the TUI version doesn't match the one expected by TCPCON. Action: Use NetWare Administrator or MONITOR to determine if the server is low on memory.MARK=BULLETIf the server is low on memory, see "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. Reload TCPCON when more memory is available. If the server is not low on memory, the server probably has incompatible versions of TUI.NLM and TCPCON.NLM. Record the version numbers of the TUI.NLM and TCPCON.NLM, then contact your Novell Authorized Reseller.PAGENUM=1124 ID="BP1118"TCP/IP0: Could not open UDP port for RIP. RIP is disabled.TCP/IPExplanation:  RIP could not open the UDP port assigned to RIP.Action: Contact your Novell Authorized Reseller.3: Received a RIP update with invalid network from IP_address.TCP/IPExplanation: RIP received an invalid network route from the router using the specified IP address. Action: Review the configuration of this server and the indicated router. Make sure both nodes have a valid IP address on the same IP subnetwork.4: Could not allocate the resource tag for SNMP support. TCP/IP MIB will not be available.TCP/IPExplanation: The server may not have enough available memory. TCP/IP will continue to function but will not respond to SNMP requests.Action: Increase the available memory. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network 5: Could not register TCP/IP MIB with SNMP agent.TCP/IPExplanation: An internal error prevented SNMP from accessing the TCP/IP MIB. TCP/IP will still be functional.Action: Contact your Novell Authorized Reseller.6: Could not add reception for OSPF multicast (error_code).TCP/IPExplanation: OSPF could not receive multicast OSPF packets.Action: Contact your Novell Authorized Reseller.7: Could not register SNMP as UDP client. SNMP will not operate over UDP.TCP/IPExplanation: An internal error prevented SNMP from receiving SNMP packets over UDP. TCP/IP will still be functional.Action: Contact your Novell Authorized Reseller.PAGENUM=1125 ID="BP1119"8: Could not register TCP as IP client (TCP/IP_error_code). TCP will not receive any packet.TCP/IPExplanation: TCP tried to register with IP; but the registration failed unexpectedly with the indicated error code.Action: Contact your Novell Authorized Reseller.9: Could not allocate TCP timer process. TCP is disabled.TCP/IPExplanation: The server may not have enough available memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.10: Could not start TCP trivial service.TCP/IPExplanation: The TCP trivial service could not be started. The service is not required for normal operations. The server may not have enough available memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.11: Could not start TCP Character Generator service on port 19, or Could not start TCP Discard service on port 9, or Could not start TCP Echo Generator service on port 7.TCP/IPExplanation: The indicated service could not be started. These services are not required for normal operations. The server may not have enough available memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.12: Could not register UDP adapter with BSD sockets. UDP sockets will not be available.TCP/IPExplanation: UDP BSD socket support could not register with CLIB.Action: Use CLIB.NLM and TCPIP.NLM from the same NetWare release.13: Could not register TCP adapter for BSD sockets. TCP sockets will not be available.TCP/IPExplanation: TCP BSD socket support could not register with CLIB.Action: Use CLIB.NLM and TCPIP.NLM from the same NetWare release.14: Could not register ICMP adapter for BSD sockets. ICMP sockets will not be available.TCP/IPExplanation: The Internet Control Message Protocol (ICMP) BSD socket support could not register with BSD sockets.Action: Use CLIB.NLM and TCPIP.NLM from the same NetWare release.PAGENUM=1126 ID="BP1120"16: Could not load the streams device /dev/{tcp | udp | ip}.TCP/IPExplanation: The indicated STREAMS device is not available. The server may not have enough available memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.17: Could not unload the streams device /dev/{tcp | udp | ip}.TCP/IPExplanation: The NetWare STREAMS support module did not let TCP delete one of its STREAMS devices.Action: Contact your Novell Authorized Reseller.22: The {first | second | third | fourth} byte of the address is illegal.TCP/IPExplanation: The command line contained an IP address with a syntax problem in the indicated byte.Action: Correct the IP address.23: Found `character'. Each byte of an IP address must be separated by `.'. TCP/IPExplanation: The command line contained an IP address in which two bytes were separated by the indicated character rather than the required period.Action: Correct the IP address.24: Ignored `character_string' following an IP address.TCP/IPExplanation: After command line processing parsed an IP address, it found extra characters in the token that it did not understand, so it ignored them.Action: None. This message is for information only. To avoid this problem in the future, use INETCFG to modify the address parameter for the IP bind command. If you do not use INETCFG, you must modify the bind line directly.25: Could not understand `argument' as an IP address.TCP/IPExplanation: A parameter argument was encountered that should have been an IP address, but it does not have the correct format. Other error messages supply additional information to help you identify the nature of the problem.Action: Enter the correct address when prompted. To avoid this problem in the future, use INETCFG to modify the address parameter for the IP bind command. If you do not use INETCFG, you must modify the bind line directly.PAGENUM=1127 ID="BP1121"30: Will be acting as a default router on the interface IP_address in order to support the stub subnet.TCP/IPExplanation: The local server will advertise itself as the default router on the interface being bound.Action: None. This message is for information only.31: Automatically enabled Proxy ARP on interface IP_address to support the stub subnet.TCP/IPExplanation: The network or subnetwork of this interface encompasses the subnetwork of an already bound interface. The already bound interface is called a stub subnet. The stub subnet is not visible to other hosts on the network interface being bound. Proxy ARP is enabled on this interface to provide access to hosts on the stub subnet.Action: None. This message is for information only.32: Ignored unexpected `wan' parameter on a LAN interface.TCP/IPExplanation: The "wan" parameter applies only to WAN interfaces.Action: Remove the parameter from the bind line. Or, if you have installed a product that does support WAN interfaces, bind IP to the correct WAN interface.33: IP_address is already being used by another interface. Each interface must have its own unique IP addressTCP/IPExplanation: The IP address being bound to this interface is already bound to another interface in the server.Action: Use a different IP address for this interface. Be sure the IP address has the correct network value for the interface's network.35: Will assume subnet mask used with IP_address since none is given.TCP/IPExplanation: No mask parameter was given on the BIND command line. The IP address used in this command has a different subnetwork number, but the same network number as the network number of the IP address of another interface already bound. Subnetworks of the same network should have the same mask, so IP has used the other interface's subnetwork mask.Action: Review your subnet configuration. If you require variable subnetwork masks, rebind the interfaces specifying the "mask" parameter for each interface.36: The subnetwork mask disagrees with the mask used with IP_address.TCP/IPPAGENUM=1128 ID="BP1122"Explanation: The value of the "mask" parameter on the BIND command line was different from the value used to bind to the interface with despecified IP address. The subnet masks are usually the same for all subnets of the same network. RIP 1 will not function properly if they are different.Action: Make sure that you intended the subnet masks to be different. If you are using RIP 1, you should correct the subnet mask so the same subnet mask is used on all subnets of the network.37: Cannot support IP_address with mask subnet_mask because it conflicts with IP_address_2 with mask subnet_mask_2, an address IP is already supporting on another interface.TCP/IPExplanation: The subnet mask that you specified is illegal.Action: Review your subnet configurations and rebind the interfaces involved with the correct subnet masks.44: You already bound that IP network to the interface with address IP_address. TCP/IPExplanation: For each binding of IP to an interface, the network or subnetwork number must be different. This message occurs when they are the same. IP_address is the local IP address of the previous binding that conflict with the current binding. You can determine the IP network or subnetwork number by masking the local IP address with the subnet mask.Action: Change the network number or subnetwork number in either binding.47: IP_address is illegal. IP address must be class A, B or C. TCP/IPExplanation: The "addr" parameter in the BIND command carried an IP address that was not a legal class for a local address. The first byte of the IP address must be less than 224 (decimal).Action: Obtain a legal IP address and use it for the interface.48: IP_address is a loop back network address. TCP/IPExplanation: The IP address specified in the BIND command is reserved for the loopback address.Action: Obtain a legal IP address and use it for the interface.49: There are no network bits set in IP_address. TCP/IPExplanation: The "addr" parameter carried an IP address that had no bits set in the network field.Action: get a legal IP address and use it for the interface.PAGENUM=1129 ID="BP1123"50: IP_address is illegal. Host field is zero or all ones. TCP/IPExplanation: The IP address host number is zero or all ones. Zero or all ones are invalid for the IP address host number and cannot be assigned to an interface.Action: Obtain a valid IP address with a valid host number.51: IP_address is illegal. Subnet field is all ones.TCP/IPExplanation: The IP address subnet number is zero or all ones. Zero or all ones are invalid for the IP address subnet number and cannot be assigned to an interface.Action: Use a valid IP address with a valid subnet number.53: Ignored unexpected `targetname' parameter on a LAN interface.TCP/IPExplanation: "targetname" parameter applies only to WAN interfaces.Action: Remove the parameter from the bind line. Or, if you have installed a product that does support WAN interfaces, bind IP to the correct WAN interface.58: OSPF is disabled.TCP/IPExplanation: OSPF has been disabled because a memory or configuration error was encountered. The server may not have enough available memory.Action: Use INETCFG to review the OSPF configuration and correct any errors. Use NetWare Administrator or MONITOR to determine if the server has a memory shortage. If so, increase the available memory. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.61: Could not turn on Proxy ARP. I am not configured to act as a router.TCP/IPExplanation: Proxy ARP functions only if TCP/IP is configured as a router.Action: If you don't want TCP/IP to function as a router, remove the "proxyarp" parameter from the bind line. If you do want TCP/IP to act as a router, unload and then reload TCP/IP with the "forward=yes" parameter.62: Could not turn on Proxy ARP. The media does not support ARP.TCP/IPExplanation: The interface does not support ARP, and Proxy ARP requires ARP functionality.Action: Remove "proxyarp=yes" parameter from the bind command.67: IP_address_1 is not on the same network as IP_address_2. Nevertheless, IP will assume IP_address_2 is on the local network, and will use it as the default gateway.TCP/IPPAGENUM=1130 ID="BP1124"Explanation: A "gate" parameter was given on the BIND IP command line, but the indicated gateway did not have the same network number as the interface itself. IP expects to send traffic directly to the gateway; therefore, the gateway must be connected directly to the interface networks.Action: If the indicated IP address for the gateway is incorrect, supply the correct IP address for the gateway. In some unusual configurations, this may not be an error and, in this case, no action is required.73: `Argument' is an invalid RIP cost.TCP/IPExplanation: The cost parameter carried an argument that cannot be understood as a cost value. The RIP cost is a decimal number between 1 and 15.Action: Correct the cost parameter.76: IP_address is illegal address for a multicast override address. I will be using the broadcast address IP_address_2 instead.TCP/IPExplanation: The "mcast" parameter included in the BIND command is not a valid multicast address for this interface. The specified address will be used instead.Action: None. This message is for information only. However, you should review your configuration using INETCFG to correct the multicast address. If you do not use INETCFG, you must manually edit the BIND command line.78: Media_address is using our IP address: IP_address.TCP/IPExplanation: The ARP protocol has detected another IP node on the network using the local node's IP address. Either the local server or the server with the indicated six-byte hardware address is using the wrong IP address.Action: Correct the IP address used by the misconfigured node.79: Could not allocate resource tag for ARP.TCP/IPExplanation: The server may not have enough available memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.80: ARP does not recognize the media `name'. Default media is assumed.TCP/IPExplanation: The ARP module does not recognize the medium that IP is being bound to, so ARP is treating the media the same way it treats an Ethernet. This could indicate a problem with the LAN driver for that medium, or an old version of TCP/IP.Action: See the LAN driver documentation for instruction on allowing ARP and IP to use this medium.PAGENUM=1131 ID="BP1125"81: You cannot bind ARP directly to a device.TCP/IPExplanation: A BIND ARP command was issued at the server console. It is not legal to bind ARP directly to a media device. ARP is bound automatically when IP is bound.Action: Do not try to bind ARP to the device.82: Could not allocate memory for the ARP interface block.TCP/IPExplanation: The server may not have enough available memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.83: Could not add ARP's protocol ID to LSL (error_code).TCP/IPExplanation: ARP could not register its protocol ID for the medium that IP is being bound to. By itself, this error is not fatal, and it may not be a problem unless the bind subsequently fails. This message could indicate an excessively complicated network configuration.Action: Contact your Novell Authorized Reseller.84: Could not determine ARP's protocol ID.TCP/IPExplanation: ARP cannot determine its protocol ID for the medium that IP is being bound to, because that medium has no protocol ID for ARP. Normally this error follows the message:  MOREINFO="NONE"TCP/IP-3.00 80:ARP does not recognize the media nameMOREINFO="NONE". Default media is assumed.When ARP does not recognize a media type, the ARP protocol ID must be registered manually using the PROTOCOL REGISTER console command, but this has not been done.Action: See the LAN driver documentation for instruction on registering the correct protocol ID for ARP before binding IP to that board.85: Could not register ARP with LSL.TCP/IPExplanation: NetWare refused to recognize the IP protocol module. Some other NLM program running on the server has already claimed to be the IP protocol.Action: Remove the software that has claimed to be the IP protocol.86: System rejected ARP's bind request.TCP/IPExplanation: NetWare did not allow ARP to bind to the indicated board. This message could indicate an overly complicated network configuration in the NET.CFG file.Action: Simplify the NET.CFG file and reboot the computer. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=1132 ID="BP1126"88: Because you disabled ARP, IP_address is incorrect. I am using the correct local IP address for this interface.TCP/IPExplanation: ARP was disabled on the BIND command line. Therefore, IP must use an alternative address mapping mechanism for this medium that requires the local IP address used must be the one specified in the message.Action: None. This message is for information only. 90: The interface IP_address is a stub-subnet of the interface IP_address_2.TCP/IPExplanation: This interface is a subnetwork of an interface that is already bound. The stub subnet will not be visible to nodes on the interface that is already bound.Action: None. This message is for information only.91: The board number is out of range.TCP/IPExplanation: This is an internal error.Action: Contact your Novell Authorized Reseller.92: IP does not recognize the media `name'. Default media is assumed.TCP/IPExplanation: IP does not recognize the media it is being bound to, so it is treating the media in much the same way it treats Ethernet. This could indicate a problem with the LAN driver for the medium or an old version of TCP/IP.Action: See the LAN driver documentation for instructions on allowing IP to use this medium.93: Hardware failure is detected on board number.TCP/IPExplanation: The IP address was previously bound to a network board in the server. The LAN driver supporting that network board has detected a hardware failure for the network board and has removed it from service. IP can no longer use that network board.Action: Fix the hardware, then rebind IP to the board.95: Could not get MLID configuration for the board.TCP/IPExplanation: IP could not obtain the board's configuration information from the LAN driver.Action: Record the name and version of the LAN driver and contact your Novell Authorized Reseller.PAGENUM=1133 ID="BP1127"96: Could not register ICMP with IP (error_code). ICMP is disabled.TCP/IPExplanation: The Internet Control Message Protocol (ICMP) tried to register with IP, but it could not. This condition should not affect TCP/IP operations. Action: If the problem does affect TCP/IP operations, contact your Novell Authorized Reseller.97: Could not allocate memory for IP interface block.TCP/IPExplanation: The server may not have enough available memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.98: Could not add the interface to the routing database.TCP/IPExplanation: The server may not have enough available memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.99: Could not add IP's protocol ID to LSL (error_code).TCP/IPExplanation: IP could not register its protocol ID for the medium it is being bound to. By itself, this error is not fatal, and it may not be a problem unless the bind subsequently fails. This message could indicate a complicated network configuration.Action: Simplify the NET.CFG file and reboot the computer. If the problem persists, contact your Novell Authorized Reseller.100: Could not determine IP's protocol ID.TCP/IPExplanation: IP cannot determine its protocol ID for the medium it is being bound to. Action: Contact your Novell Authorized Reseller.101: System rejected IP's register request.TCP/IPExplanation: NetWare refused to recognize the IP protocol module. Some other NLM program running on the server has already claimed to be the protocol IP.Action: Remove the software that claimed to be IP.102: System rejected IP's bind request.TCP/IPExplanation: NetWare did not allow IP to bind to the indicated board. This message could indicate a complicated network configuration.Action: Contact your Novell Authorized Reseller.PAGENUM=1134 ID="BP1128"103: You cannot disable ARP on that interface. The media has no alternative mapping mechanism.TCP/IPExplanation: The BIND command line had the argument ARP=NO, but IP does not have an alternate address mapping mechanism for that medium.Action: Do not use ARP=NO for that medium.104: Could allocate memory for OSPF control blocks.TCP/IPExplanation: The server may not have enough available memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.105: No protocol ID for IP is found on that media.TCP/IPExplanation: IP could not connect to the indicated board because the board medium has no protocol ID for IP. Normally, this error follows the message: MOREINFO="NONE"TCP/IP-3.00 92:IP does not recognize the media `nameMOREINFO="NONE"'. Default media is assumed. When IP does not recognize a medium, the IP protocol ID must be registered manually using the PROTOCOL REGISTER console command, but this has not been done.Action: See the LAN driver documentation for instructions to register the correct protocol for IP before binding IP to the board.106: User canceled request.TCP/IPExplanation: The Esc key was pressed in response to a request from IP for additional information.Action: None. This message is for information only.107: Some applications have TCP/IP sockets open. TCP/IP services to those applications will be terminated.TCP/IPExplanation: Some utilities have open BSD sockets to the TCP/IP protocol stack.Action: If you want the utilities to continue to use TCP/IP, abort the UNLOAD command. Unload NLM programs that are using the TCP/IP protocol stack before unloading the TCP/IP.PAGENUM=1135 ID="BP1129"108: Some applications have TCP/IP streams open. TCP/IP services to those applications will be terminated, and SYSTEM INTEGRITY MAY BE COMPROMISED.TCP/IPExplanation: An attempt was made to unload TCPIP.NLM when one or more utilities still have AT&TTM STREAMS open to TCP/IP STREAMS devices. If any of these utilities are actively transmitting data, the server could abend if you unload TCPIP. NLM.Action: Abort the UNLOAD command. Unload the NLM programs that use the TCP/IP protocol stack. Unload TCPIP.NLM.110: Unbound local IP address IP_address from the board number.TCP/IPExplanation: The indicated IP address was previously bound to a board in the server and it has now been unbound. This could be caused by either unbinding IP from the board or unloading the LAN driver that is supporting the interface.Action: Normally, this is not a problem because the action was taken intentionally by the console operator. Load INETCFG and issue the reinitialize server command.113: The streams device /dev/{tcp| udp} is still being used.TCP/IPExplanation: An attempt was made to unload TCPIP.NLM when one or more utilities still have AT&TTM STREAMS open to the TCP/IP STREAMS device indicated. The server may abend if you unload the TCPIP.NLM.Action:  Abort the UNLOAD command. Unload the NLM files that are using the TCP/IP protocol stack. Unload TCPIP.NLM.117: Could not register name service with UDP (error_code). That UDP service will not be available.TCP/IPExplanation: One of the trivial UDP test services cannot be set up, indicating an internal failure.Action: Contact your Novell Authorized Reseller. 118: Could not register UDP with IP (TCP/IP_error_code).TCP/IPExplanation: UDP tried to register with IP; but the registration failed unexpectedly with the indicated error code.Action: Contact your Novell Authorized Reseller.121: Could not register IP with LSL (error_code).TCP/IPExplanation: IP could not obtain the board's control routing from the LAN driver.Action: Record the name and version of the LAN driver and contact your Novell Authorized Reseller.PAGENUM=1136 ID="BP1130"124: Could not register IP with CSL (error_code).TCP/IPExplanation: CSL or CSLSTUB returned an error when IP attempted to register.Action: Contact your Novell Authorized Reseller.126: Please use `Yes' or `No' as the argument to `parameter' parameter.TCP/IPExplanation: A parameter that requires a Yes or No argument had neither.Action: Use "Yes" or "No" as the argument of the parameter.129: IP_address is illegal for a broadcast address. I will be using 255.255.255.255 instead.TCP/IPExplanation: The "bcast" parameter included in the BIND command is not a valid broadcast address for this interface. The default value will be used.Action: None. This message is for information only. However, you should review your configuration using INETCFG to correct the broadcast address. If you do not use INETCFG, manually edit the BIND command line.132: IP is not compatible with the CSL version.TCP/IPExplanation: The installed version CSL or CSLSTUB.NLM file is not compatible with TCPIP.NLM. This usually happens when CSL or TCP/IP is manually copied into the server.Action: Reinstall the product using proper installation utility.133: `argument' is not recognized as either affirmative or negative.TCP/IPExplanation: A parameter that requires a Yes or No argument had neither.Action: Use "Yes" or "No" as the argument of the parameter.134: IP has detected an SFT-III configuration error. The primary IOEngine is bound to address address with mask mask; the secondary server is bound to address address with mask mask. The configurations for the primary and secondary IOEngines must be identical.TCP/IPExplanation: TCP/IP was configured with different address and mask pairs for the NetWare® 4.1 SFT IIITM network in the two SFT III IOEngines. TCP/IP should be configured with the same SFT III network address and mask in both IOEngines. TCP/IP will ignore the address and mask configured in the secondary IOEngine and only use the SFT III network configuration in the primary IOEngine.Action: If the SFT III network address and mask configured in the primary IOEngine is correct, no action is required. Otherwise, use INETCFG to correctly configure the SFT III network and reinitialize the server in both IOEngines. Even if no current action is required, you should use INETCFG to configure the two IOEngines correctly.PAGENUM=1137 ID="BP1131"135: Ignored the ambiguous parameter `parameter'.TCP/IPExplanation: A parameter was given on the command line that could be an abbreviation for either of two possible parameters.Action: Use a longer abbreviation, or do not abbreviate.136: Ignored the unrecognized parameter `parameter'.TCP/IPExplanation: A parameter was encountered that is not recognized as a legal parameter in the current context. Usually the problem is that the parameter is misspelled.Action: Correct the parameter.137: `parameter' is a duplicate parameter. The previous one is overridden.TCP/IPExplanation: A parameter occurred twice on the command line. The command processor is discarding the previous parameter in favor of the new one.Action: Remove the duplicate parameter.138: IP could not schedule a delayed bind to the SFT-III virtual LAN because of memory shortages. The bind request has been discarded.TCP/IPExplanation: IP could not allocate the memory necessary to bind to the VIRTUAL_BOARD of the NetWare® 4.1 SFT IIITM network. IP will not be able to route to the MSEngine. The server may not have enough available memory.Action: Increase the available memory and reboot the computer. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.139: Could not understand SNMP trap target `IP_address'. No trap will be sent to it.TCP/IPExplanation: The expected IP address parameter could not be understood. No SNMP traps will be sent to the intended IP address.Action: Correct the IP address.140: Could not register IP_address as a SNMP trap target (error_code). No trap will be sent to it.TCP/IPExplanation: SNMP agent could not accept trap target due to inadequate memory. The server may not have enough available memory.Action: Increase the available memory and reboot the computer. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.PAGENUM=1138 ID="BP1132"141: Could not allocate resource tag for SNMP trap handler. SNMP traps will not be sent over UDP.TCP/IPExplanation: This message occurs when TCP/IP could not allocate the system resource tag for SNMP trap handler. The server may not have enough available memory.Action: Increase the available memory and reboot the computer. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.143: Could not register UDP as an SNMP trap handler (error_code). SNMP traps will not be sent over UDP.TCP/IPExplanation: This message occurs when SNMP agent returns an error for TCP/IP's attempt to register UDP as SNMP's trap handler. The server may not have enough available memory.Action: Increase the available memory and reboot the computer. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.145: IP address IP_address is not bound to that interface.TCP/IPExplanation: This message happens when you try to unbind a specific IP address from the interface, and that address is not found on the interface.Action: Specify the correct IP address to unbind from the interface.147: Ignored `gate' parameter value. Argument is illegal.TCP/IPExplanation: The specified gateway argument could not be interpreted as a valid IP address.Action: Provide the IP address of the default gateway.154: Could not initialize the SFT-III support module.TCP/IPExplanation: TCP/IP could not successfully complete its NetWare® 4.1 SFT IIITM specific initialization and will not load. It is possible the version of the SFT III operating system that you are using is incompatible with the version of TCP/IP that you are attempting to load.Action: Record the version numbers of your SFT III operating system and the TCPIP NLM that you are attempting to load, and contact your Novell Authorized Reseller.155: Could not allocate resource tags for SFT-III support.TCP/IPExplanation: The server may not have enough available memory. TCP/IP will not load.Action: Increase the available memory and reboot the computer. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.PAGENUM=1139 ID="BP1133"188: Could not import public symbol name.TCP/IPExplanation: TCP/IP could not find the specified symbol in the NetWare® 4.1 SFT IIITM operating system, and it could not load. TCP/IP should only attempt to access this symbol when loading on a SFT III system, and the symbol should be available there. The version of the operating system that you are using is probably incompatible with the version of TCP/IP that you are loading.Action: Record the version numbers of your SFT III operating system and the TCPIP.NLM that you are attempting to load, and contact your Novell Authorized Reseller.193: The CSL version is incompatible with IP.TCP/IPExplanation: The installed version of CSL or CSLSTUB is incompatible with CSL. This usually happens when the wrong version of CSL or TCP/IP is manually copied to the server.Action: Reinstall the product using the proper installation utility.218: Media_address is using our IP address: IP_address.TCP/IPExplanation: The ARP protocol has detected another IP node on the network using the local node's IP address. Either the local server or the server with the indicated 6-byte hardware address is using the wrong IP address.Action: Correct the IP address used by the misconfigured node.237: Could not enable TCP/IP header compression. The media does not support it.TCP/IPExplanation: You enabled header compression on media that does not support TCP/IP header compression.Action: Verify that correct interface port is specified on the bind command line. If it is correct interface, remove "compression" parameter from the bind line.238: Could not register OSPF with IP.TCP/IPExplanation: This is an internal error.Action: Contact your Novell Authorized Reseller.242: Could not register OSPF MIB with SNMP agent. MIB will not be available.TCP/IPExplanation: SNMP agent returned error when OSPF tried to register its MIB. This is an internal error.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=1140 ID="BP1134"243: Could not allocate resource tags for OSPF.TCP/IPExplanation: The server may not have enough available memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.245: Could not allocate the resource tag for configuration. Will run without configuration fileTCP/IPExplanation: The server could not allocate a resource tag for TCP/IP's configuration.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.247: Aborted reading config file at line #number (error_code).TCP/IPExplanation: This can happen if the TCP/IP configuration file is operated on while TCP/IP is loading.Action: Close all editing sessions and unload INETCFG. Reconfigure the server using INETCFG. Do not access the TCP/IP configuration file manually.248: Line #number of the configuration file contains missing or invalid value.TCP/IPExplanation: TCP/IP could not interpret the specified line in the configuration file. This usually happens when somebody tampers with TCP/IP configuration file.Action: Delete the configuration file, SYS:\ETC\TCPIP.CFG. Reconfigure TCP/IP using INETCFG configuration utility. Do not access the file in any other way.249: Line #number of configuration file contains invalid or misplaced parameter `parameter'.TCP/IPExplanation: TCP/IP could not interpret the specified line in the configuration file. This usually happens when someone tampers with TCP/IP's configuration file.Action: Remove the configuration file, SYS:\ETC\TCPIP.CFG and reconfigure TCP/IP using INETCFG configuration utility. Do not access the file in any other way.250: Could not open the configuration file (error_code).TCP/IPExplanation: TCP/IP could not open the configuration file, SYS:\ETC\TCPIP.CFG. This error usually happens when TCP/IP is being configured with INETCFG configuration utility.Action: Exit INETCFG. If the file is opened using EDIT command, close it as well. Do not access the configuration file manually.PAGENUM=1141 ID="BP1135"251: Could not register EGP MIB with SNMP agent.TCP/IPExplanation: SNMP agent returned an error when EGP tried to register its MIB. This is an internal error.Action: Use Monitor to determine if there is sufficient memory in the server. If there is insufficient memory, increase the available memory. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. If the problem persists, contact your Novell Authorized Reseller.254: Could not add reception for OSPF DR multicast on interface {IP_address|host_name} (error_code).TCP/IPExplanation: This is an internal error.Action: Contact your Novell Authorized Reseller.255: Received mismatching OSPF LS request packet from IP_address.TCP/IPExplanation: OSPF received an LS request packet from the neighbor IP_address, but could not find the matching LS advertisement in its LS database. This error can happen if the requested LS advertisement has been flushed out of the OSPF domain after database summary has been exchanged with the neighbor.Action: Usually, OSPF is able to recover from this error. If this error persists, it may indicate that the neighbor router is broken. In that case, take it off line and contact its supplier.256: OSPF SeqNumMismatch event has occurred with IP_address.TCP/IPExplanation: OSPF detected a sequence number mismatch in the Link State information exchanged with a neighbor OSPF router.Action: Usually, OSPF is able to recover this error. If this error persists, the neighbor router is broken. In that case, take it off line and contact its supplier.257: IP_address is using my OSPF Router ID.TCP/IPExplanation: The router with IP_address is configured with same router ID as the local server. All OSPF routers must have a unique router ID.Action: Change the router ID on either machine to a unique value.PAGENUM=1142 ID="BP1136"258: Received OSPF packet with bad area ID from IP_address.TCP/IPExplanation: An OSPF packet from the IP_address does not match the area ID of received interface. This error is usually caused by a misconfiguration.Action: Determine the correct area ID for the network that the packet came from. Reconfigure either or both servers with the correct area ID. Use "Bind" screen of INETCFG to get to OSPF interface configuration where area ID for the interface is specified.259: Received OSPF packet with bad auth type from IP_address.TCP/IPExplanation: TCP/IP received an OSPF packet with an authentication type that does not match the configuration of the area. The packet originated at IP_address.Action: Determine the right authentication type of the area for the network through which the local router is attached to the specified neighbor. Reconfigure either or both machines with the right authentication type. 260: Received OSPF packet with bad auth key from IP_address.TCP/IPExplanation: TCP/IP received an OSPF packet with a bad authentication value from the IP_address. This error is usually caused by a misconfiguration.Action: Determine the correct authentication key value for the network. Reconfigure either or both machines with the correct value.261: Received an OSPF hello packet with bad configuration from IP_address.TCP/IPExplanation: The configuration values in the hello packet received from the IP_address does not match the configured values.Action: Determine correct Hello interval and Dead Interval for the network. Reconfigure either or both machines with the correct values.262: System packet buffer is too small for RIP. RIP is disabled.TCP/IPExplanation: The size of the Packet Receive Buffer (also called ECB) is too small to hold the maximum size RIP packet. The local server will not be able to receive maximum size RIP packets, and routing information may be lost.Action: Use the default ECB size. See "BOOK="superenu" COLLECTION="nw41"Resolving Event Control Block Allocation Errors" in Supervising the Network.263: Received an empty OSPF DD packet with M bit set from IP_address.TCP/IPExplanation: The received OSPF Data Description packet is empty when contents are expected. An OSPF router should not send empty Data Description packets when there are more contents to exchange. The router is probably not behaving correctly.Action: Contact the supplier of the router.PAGENUM=1143 ID="BP1137"TEXTUTIL-utility_nameThe messages listed in this section may be initiated by one or more text or print utilities. The specific utility name is shown in the prefix to the message when displayed on the screen.10: The system could not load overlay file name_RUN.OVL. TEXTUTIL-Explanation: This problem could mean the file is missing or not in the proper search path. Another possibility is that the workstation does not have enough memory. Action: Make sure the directory where the .OVL file is located is in the search path. If necessary, increase the workstation's available memory. See "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network.15: The system error library file filename is missing.TEXTUTIL-Explanation: This problem could mean the file is missing or not in the proper search path. Action: Check the drive mappings to make sure the file is located in the correct search path.16: The error portal cannot be created during program initialization. TEXTUTIL-Explanation: This error could indicate lack of workstation memory or an internal problem in the program.Action: To resolve workstation memory errors, see "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network.17: The system could not create a new portal because the portal control block table is full.TEXTUTIL-Explanation: Too many screens are active at one time. This is a program logic error.Action: Contact your Novell Authorized Reseller.18: The system could not allocate additional memory.TEXTUTIL-Explanation: The workstation does not have sufficient memory to complete the attempted operation.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network.PAGENUM=1144 ID="BP1138"19: The system cannot create a portal with a height of number and a width of number because it is too large.TEXTUTIL-Explanation: The program calculated a portal height and width that is too large. This is a program logic error that could have occurred because of a message expansion that was not planned for.Action: Report the problem to your Novell Authorized Reseller.20: The system could not seek a specific position in file name.TEXTUTIL-Explanation: The user may not have access rights to the file, or the problem could indicate a corrupted file or a hardware failure.Action: Try one or more of the following:MARK=BULLETMake sure the file is flagged properly.If the user has a corrupted file, replace it, if possible.Find out if other users and workstations are experiencing the same problem. If so, report the problem to your Novell Authorized Reseller.If the problem persists and is isolated to this workstation, check the hardware and cabling. Contact your Novell Authorized Reseller.21: An End_Of_File error was returned while attempting to read file name. The read request was for number bytes.TEXTUTIL-Explanation: One possibility is that the user does not have access rights to the file. Other possibilities are that the file is corrupted or a hardware failure has occurred.Action: Try one or more of the following:MARK=BULLETMake sure the file is flagged properly.If the user has a corrupted file, replace it if possible.Find out if other users and workstations are experiencing the same problem. If so, report it to your Novell Authorized Reseller.If the problem persists and is isolated to this workstation, check the hardware and cabling. Contact your Novell Authorized Reseller..PAGENUM=1145 ID="BP1139"22: File name could not be read. The read request was for number bytes.TEXTUTIL-Explanation: One possibility is that the user does not have access rights to the file. Other possibilities are that the file is corrupted or a hardware failure has occurred.Action: Try one or more of the following:MARK=BULLETMake sure the file is flagged properly.If the user has a corrupted file, replace it if possible.Find out if other users and workstations are experiencing the same problem. If so, report it to your Novell Authorized Reseller.If the problem persists and is isolated to this workstation, check the hardware and cabling. Contact your Novell Authorized Reseller..23: File name should have had number bytes read from it.TEXTUTIL-Explanation: One possibility is that the user does not have access rights to the file. Other possibilities are that the file is corrupted or a hardware failure has occurred.Action: Try one or more of the following:MARK=BULLETMake sure the file is flagged properly.If the user has a corrupted file, replace it if possible.Find out if other users and workstations are experiencing the same problem. If so, report it to your Novell Authorized Reseller.If the problem persists and is isolated to this workstation, check the hardware and cabling. Contact your Novell Authorized Reseller.24: The system could not push a list onto the stack because the list stack is already full.TEXTUTIL-Explanation: To initialize a new list, the old list must be pushed onto the stack. The program could not accommodate the request as described. Too many lists are active in the program at one time. This is a program logic error.Action: Report the problem to your Novell Authorized Reseller.PAGENUM=1146 ID="BP1140"25: The system could not pop a list from the stack because the list stack is empty.TEXTUTIL-Explanation: The program attempted to retrieve a list when none was saved. This is a program logic error.Action: Report the problem to your Novell Authorized Reseller.26: The system cannot display the utility header with the current date and time.TEXTUTIL-Explanation: The most likely cause of this error is a text string that is too long to display. This could result from messages expanding due to translation.Action: Report the problem to your Novell Authorized Reseller.28: The system could not allocate number bytes of additional memory.TEXTUTIL-Explanation: The workstation does not have sufficient memory to complete the attempted operation.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network.29: File name could not be opened.TEXTUTIL-Explanation: The user may not have access rights to the file, or the problem could indicate a corrupted file or a hardware failure.Action: Try one or more of the following:MARK=BULLETMake sure the file is flagged properly.If the user has a corrupted file, replace it if possible.Find out if other users and workstations are experiencing the same problem. If so, report it to your Novell Authorized Reseller.If the problem persists and is isolated to this workstation, check the hardware and cabling. Contact your Novell Authorized Reseller.30: File name could not be closed.TEXTUTIL-Explanation: The user may not have access rights to the file, or the problem could indicate a corrupted file or a hardware failure.Action: Try one or more of the following:MARK=BULLETMake sure the file is flagged properly.If the user has a corrupted file, replace it if possible.PAGENUM=1147 ID="BP1141"Find out if other users and workstations are experiencing the same problem. If so, report it to your Novell Authorized Reseller.If the problem persists and is isolated to this workstation, check the hardware and cabling. Contact your Novell Authorized Reseller..31: File name should have had number bytes written to it.TEXTUTIL-Explanation: The user may not have access rights to the file, or the problem could indicate a corrupted file or a hardware failure.Action: Try one or more of the following:MARK=BULLETMake sure the file is flagged properly.If the user has a corrupted file, replace it if possible.Find out if other users and workstations are experiencing the same problem. If so, report it to your Novell Authorized Reseller.32: The system could not write to file name. The write request was for number bytes.TEXTUTIL-Explanation: The user may not have access rights to the file, or the problem could indicate a corrupted file or a hardware failure.Action: Try one or more of the following:MARK=BULLETMake sure the file is flagged properly.If the user has a corrupted file, replace it if possible.Find out if other users and workstations are experiencing the same problem. If so, report it to your Novell Authorized Reseller.33: The first element of the list could not be obtained because the list is empty.TEXTUTIL-Explanation: The program expected an active list and there was none. This is a program logic error.Action: Report the problem to your Novell Authorized Reseller.PAGENUM=1148 ID="BP1142"35: The current list cannot be restored with list buffer number number because the buffer number is invalid.TEXTUTIL-Explanation: An internal system error probably has occurred.Action: Restart the workstation. If the problem persists, notify your Novell Authorized Reseller.36: The current list cannot be saved because the list save buffer number number is invalid.TEXTUTIL-Explanation: An internal system error probably has occurred.Action: Restart the workstation. If the problem persists, notify your Novell Authorized Reseller.37: A section of memory that was previously allocated could not be freed.TEXTUTIL-Explanation: An internal system error probably has occurred.Action: Restart the workstation. If the problem persists, notify your Novell Authorized Reseller.38: The bindery is locked. Normally the bindery is only locked if the supervisor is backing up volume SYS:. No information can be obtained until the supervisor unlocks the bindery.TEXTUTIL-Explanation: This is a temporary inconvenience.Action: Wait a few minutes and try again.39: Server name does not respond.TEXTUTIL-Explanation: Either the user is not attached to the server, or the server is down or malfunctioning.Action: Make sure the user is attached to the server, and try again. Make sure the server is running and functioning properly.40: Server name is not connected.TEXTUTIL-Explanation: The most likely explanation is that the workstation is not attached to this server. This could be a cabling problem.Action: Check the cabling, or make sure the workstation is attached to the server, and try again.PAGENUM=1149 ID="BP1143"41: Your station is already attached to the maximum number of servers allowed. You must detach from at least one server before you can attach to server name.TEXTUTIL-Explanation: The user has tried to attach to more servers than the user is allowed to.Action: Detach from at least one server before attempting to attach to the new server.42: Server name does not have any free connection slots. Another user must detach from it before you can attach to it.TEXTUTIL-Explanation: The server indicated in the message does not have any free connection slots.Action: Make sure another user detaches from the server before this user attempts to attach to it.43: You are already attached to server name.TEXTUTIL-Explanation: The user tried to attach to a server the user is already attached to.Action: None. This message is for information only..65: The system could not write the information to bindery object name property name.TEXTUTIL-Explanation: An internal system error probably has occurred.Action: Restart the workstation. If the problem persists, notify your Novell Authorized Reseller.69: The portal information cannot be obtained because no portal is currently selected.TEXTUTIL-Explanation: The program expected an active portal when there was none. This is a program logic error.Action: Report the problem to your Novell Authorized Reseller.70: File name could not be created.TEXTUTIL-Explanation: An internal system error probably has occurred.Action: Restart the workstation. If the problem persists, contact your Novell Authorized Reseller..72: Either the string passed to EditPortalString was longer than the maximum length allowed, or the string was not properly initialized.TEXTUTIL-Explanation: This is probably an internal program logic error, though it could be caused by message expansion during translation.Action: Report the problem to your Novell Authorized Reseller.PAGENUM=1150 ID="BP1144"76: The system could not change the file attributes of file name. The mode was number.TEXTUTIL-Explanation: An internal system error probably has occurred.Action: Restart the workstation. If the problem persists, contact your Novell Authorized Reseller.79: The procedure EditText failed because the default text was longer than the maximum length allowed.TEXTUTIL-Explanation: This is probably an internal program logic error, though it could be caused by message expansion during translation.Action: Report the problem to your Novell Authorized Reseller.82: The paste buffer is empty. TEXTUTIL-Explanation: The user tried to retrieve a data block from the paste buffer, but nothing was in the buffer.Action: None. This message is for information only.83: The text buffer is full. TEXTUTIL-Explanation: The text block the user marked is too large to hold in the text buffer.Action: Mark and process several smaller text blocks instead of trying to process a single large block.85: The marked block is too big for the available memory.TEXTUTIL-Explanation: The text block the user marked is too large to hold in the workstation's memory.Action: Mark and process several smaller text blocks instead of trying to process a single large block.88: Dynamic message number number could not be set because no dynamic message pointer for that number exists.TEXTUTIL-Explanation: A bad parameter was passed to the call. This is an internal program logic error.Action: Report the problem to a Novell Authorized Reseller.90: The name of the server at connection slot number could not be obtained.TEXTUTIL-Explanation: An internal system error probably has occurred.Action: Restart the workstation. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=1151 ID="BP1145"91: The system could not locate the Help Librarian data file name and will not be able to provide help for this utility. TEXTUTIL-Explanation: The version of the Help file may be outdated or corrupt, the search drive may be incorrect, or the workstation may have a connection problem.Action: If the file is in the proper search path and is a current version, try replacing it with a backup. Make sure the workstation is connected to the network. Try again. If the problem persists, contact your Novell Authorized Reseller.92: The system could not read the Help Librarian data file name and will not be able to provide help for this utility. TEXTUTIL-Explanation: The version of the Help file may be outdated or corrupt, the search drive may be incorrect, or the workstation may have a connection problem.Action: If the file is in the proper search path and is a current version, try replacing it with a backup. Make sure the workstation is connected to the network. Try again. If the problem persists, contact your Novell Authorized Reseller.93: The system is using an invalid version of the Help Librarian data file name and will not be able to provide help for this utility. TEXTUTIL-Explanation: An outdated version of the Help file is in the search path.Action: Replace the outdated file with a current version.95: The text is too long to fit in the current portal.TEXTUTIL-Explanation: This is probably an internal program logic error, though it could be caused by message expansion from translation.Action: Report the problem to your Novell Authorized Reseller.96: No portal is currently selected to display the text.TEXTUTIL-Explanation: The program expected an active portal when there was none. This is a program logic error.Action: Report the problem to your Novell Authorized Reseller.108: No server is attached. TEXTUTIL-Explanation: The user tried to execute a command on a server other than the default server, but was not attached to that server. The user must be attached to a server before he or she can use it.Action: Do one or both of the following:PAGENUM=1152 ID="BP1146"MARK=BULLETUse the WHOAMI utility to list the servers to which the user is logged in or attached; then specify one of these servers when the user executes the utility. To see server attachments, use the /B option (syntax: SERVER /B).Use the LOGIN utility to attach to the desired server; then map a drive to the server and use the new drive mapping in the command. Be sure to use the /NS option to attach; otherwise, the user will lose the default option.109: A read error occurred during attempt to read the overlay file name_RUN.OVL. TEXTUTIL-Explanation: The user may be using an outdated or corrupted version of the overlay file, the search drive may be incorrect, or the workstation may have a connection problem.Action: If the file is in the proper search path and is a current version, try replacing it with a backup. Make sure the workstation is connected to the network. Try again. If the problem persists, contact your Novell Authorized Reseller.110: The overlay file name_RUN.OVL is the wrong version for this utility. TEXTUTIL-Explanation: An outdated version of the Help file is in the search path.Action: Replace the outdated file with a current version.114: The system called GetError, but the specified procedure has been deleted.TEXTUTIL-Explanation: The most likely cause of this problem is an outdated or corrupted version of the error file TEXUTIL.IDX. Another possibility is hardware problems.Action: Get a new version of the error file. If the problem persists, check the hardware and cabling. If the problem persists, contact your Novell Authorized Reseller.180: The system called GetListIndex with element name, but that element is not found in the currently selected list.TEXTUTIL-Explanation: The list processing functions are out of sync. This error is usually caused by a program logic problem.Action: Report the problem to your Novell Authorized Reseller.181: AlignChangedList was called with the element name, but that element was not found in the currently selected list.TEXTUTIL-Explanation: The list processing functions are out of sync. This error is usually caused by an internal program logic error.Action: Report the problem to your Novell Authorized Reseller.PAGENUM=1153 ID="BP1147"182: AlignListDisplay was called with the element name, but that element was not found in the currently selected list. TEXTUTIL-Explanation: The list processing functions are out of sync. This error is usually caused by an internal program logic error.Action: Report the problem to your Novell Authorized Reseller.183: File name could not be found.TEXTUTIL-Explanation: The user may have specified an invalid filename, or an internal system error may have occurred.Action: Try again using a valid filename. If the problem persists, contact your Novell Authorized Reseller.187: The system called PushHelpContext to push context number number onto the stack, but the help context stack is already full.TEXTUTIL-Explanation: An internal system error probably has occurred.Action: Restart the workstation. If the problem persists, contact your Novell Authorized Reseller.188: You cannot return to a previous Help context at this point because no previous Help context is left on the stack.TEXTUTIL-Explanation: The user was already at the front of the Help context stack. An internal system error probably has occurred.Action: Restart the workstation. If the problem persists, contact your Novell Authorized Reseller.189: The Help context could not be set to number number, because only number Help contexts are defined. Help context numbers are zero-based.TEXTUTIL-Explanation: The program passed an invalid number to either the PushHelpContext() or SetHelpContext() function. This problem is usually caused by an internal program logic error. However, it could be caused by an outdated or corrupted Help file.Action: Make sure the version of the Help file is correct. If it is, report the problem to your Novell Authorized Reseller.197: Connection information could not be obtained about connection number number.TEXTUTIL-Explanation: An internal system error probably has occurred.Action: Restart the workstation. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=1154 ID="BP1148"198: The palette stack is full.TEXTUTIL-Explanation: Too many calls were made to the PushPalette() function without making any calls to PopPalette(). This error is usually an internal program logic error.Action: Report the problem to your Novell Authorized Reseller.199: The palette stack is empty.TEXTUTIL-Explanation: A call was made to the PopPalette() function without a corresponding call to PushPalette(). This error is usually an internal program logic error.Action: Report the problem to your Novell Authorized Reseller.202: The message queue is full.TEXTUTIL-Explanation: The message queue is full.Action: None. This message is for information only.203: There is either a lack of dynamic workspace or an I/O failure.TEXTUTIL-Explanation: Either the workstation needs more memory, or an internal system error has occurred.Action: To resolve workstation memory errors, see "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network.205: Directory name cannot be deleted because the directory is currently being used by another station.TEXTUTIL-Explanation: The user cannot delete this directory while another workstation is using it.Action: Wait until the directory is free; then try again. You may want to check to make sure you should delete the directory.207: The object password could not be changed.TEXTUTIL-Explanation: An internal system error may have occurred.Action: Continue if possible. If not, restart the workstation. If the problem persists, contact your Novell Authorized Reseller.209: A temporary drive handle could not be created.TEXTUTIL-Explanation: An internal system error probably has occurred. Another possibility is that the workstation does not have enough memory available to complete the operation.Action: To resolve workstation memory errors, see "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network.PAGENUM=1155 ID="BP1149"210: The drive handle could not be deallocated.TEXTUTIL-Explanation: An internal system error probably has occurred.Action: Restart the workstation. If the problem persists, contact your Novell Authorized Reseller.211: File name could not be deleted because the file is either in use or queued to be printed.TEXTUTIL-Explanation: The user cannot delete a file when it is in use or in a print queue.Action: Wait until the file is no longer being used; then try again.212: The specified drive is invalid.TEXTUTIL-Explanation: The specified drive is invalid.Action: Make sure that the user specifies a valid drive.213: The specified directory cannot be found.TEXTUTIL-Explanation: Either the user specified an invalid directory name, or an internal system error has occurred.Action: Make sure the directory name is valid; then try again. If the problem persists, contact your Novell Authorized Reseller.214: Server name cannot be found.TEXTUTIL-Explanation: One of the following probably occurred:MARK=BULLETThe user specified an invalid server name.The server may be down or offline.An internal system error has occurred.Action: Make sure that the user is connected to the server, the name specified is valid, and the server is operating properly; then try again. If the problem persists, contact your Novell Authorized Reseller.217: Information about the preferred server could not be obtained.TEXTUTIL-Explanation: An internal system error probably has occurred.Action: Restart the workstation. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=1156 ID="BP1150"218: The system could not get the directory trustee paths and the access level of object ID value on volume number.TEXTUTIL-Explanation: An internal system error probably has occurred.Action: Restart the workstation. If the problem persists, contact your Novell Authorized Reseller.219: The specified drive handle is invalid.TEXTUTIL-Explanation: An internal system error probably has occurred.Action: Restart the workstation. If the problem persists, contact your Novell Authorized Reseller.221: The specified server name is not attached.TEXTUTIL-Explanation: The user has specified a server that cannot be found. The user may not be attached to the server, the server may be offline, or the user may have typed the server name incorrectly.Action: Make sure the server is attached and operating properly; then try again, using the correct server name.222: File name cannot be found.TEXTUTIL-Explanation: An internal system error probably has occurred.Action: Restart the workstation. If the problem persists, contact your Novell Authorized Reseller.223: You do not have rights to change the mode of file name.TEXTUTIL-Explanation: NetWare's rights security system controls which directories, subdirectories, and files a user can access and what the user is allowed to do with them.Action: Obtain the necessary rights to complete this task.224: You do not have rights to create the directory name.TEXTUTIL-Explanation: NetWare's rights security system controls which directories, subdirectories, and files a user can access and what the user is allowed to do with them.Action: Obtain the necessary rights to complete this task.PAGENUM=1157 ID="BP1151"225: Directory name already exists.TEXTUTIL-Explanation: The user attempted to give a directory a name already assigned to another directory.Action: Choose a different name for the directory.228: The system encountered invalid parameters.TEXTUTIL-Explanation: The utility could not set up a new drive path because invalid parameters were specified. The utility will attempt to continue.Action: If the user cannot continue, restart the workstation. If the problem persists, contact your Novell Authorized Reseller.229: The specified path is not locatable.TEXTUTIL-Explanation: The user may have specified an invalid path, or an internal system error may have occurred.Action: Make sure the path is valid. If the user cannot continue, restart the workstation.230: The specified drive in path path is not a local drive.TEXTUTIL-Explanation: The drive assigned to this path must be a local (non-network) drive.Action: Try again, using a local drive.231: The target and the path are separate local drives.TEXTUTIL-Explanation: The specified target is on a different local drive from the path specified.Action: Make sure the target and source path are on the same local drive.233: The specified volume cannot be found.TEXTUTIL-Explanation: The user may have specified an invalid path, or an internal system error may have occurred.Action: Make sure the volume exists and is on the path the user specified. If so, restart the workstation. If the problem persists, contact your Novell Authorized Reseller.234: The DOS environment could not be found.TEXTUTIL-Explanation: An internal system error probably has occurred.Action: Restart the workstation. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=1158 ID="BP1152"235: Environment variable variable could not be found in the DOS environment.TEXTUTIL-Explanation: An internal system error probably has occurred.Action: Restart the workstation. If the problem persists, contact your Novell Authorized Reseller.236: No error was returned from this function call.TEXTUTIL-Explanation: An internal system error probably has occurred. This message often is associated with a call to get volume information when a volume number is given.Action: If necessary, restart the workstation. If the problem persists, contact your Novell Authorized Reseller.237: Connection number number is invalid.TEXTUTIL-Explanation: The user specified an invalid connection number.Action: Give the user a list of valid connection numbers.238: The new environment is larger than the maximum size available. The new variable is string.TEXTUTIL-Explanation: The user specified an environment size that was too large. The program has assigned a size within the acceptable range.Action: None. This message is for information only.239: Specified server in path path cannot be found.TEXTUTIL-Explanation: The user may have typed the path or server name incorrectly.Action: Try again, making sure the path and server name are correct.240: The specified server in path path is not attached.TEXTUTIL-Explanation: The user either is not attached to the specified server, the server is offline, or the server is not functioning properly.Action: Attach to the server. Check the hardware and cabling.242: Object ID value could not be found in the server bindery.TEXTUTIL-Explanation: The user may have specified an invalid object ID, or an internal error may have occurred.Action: Try again, making sure to use a valid ID.PAGENUM=1159 ID="BP1153"243: The name of object ID value could not be obtained.TEXTUTIL-Explanation: An internal system error probably has occurred.Action: Restart the workstation. If the problem persists, contact your Novell Authorized Reseller.244: The new property could not be added to bindery object name. The new property was name.TEXTUTIL-Explanation: An internal system error probably has occurred.Action: Restart the workstation. If the problem persists, contact your Novell Authorized Reseller.245: Additional memory cannot be allocated for the extra element name in the current list.TEXTUTIL-Explanation: The workstation does not have sufficient memory to add additional objects to the list.Action: To resolve workstation memory errors, see "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network.248: Additional memory cannot be allocated for an extra field in the current form.TEXTUTIL-Explanation: The workstation does not have enough memory to complete this operation.Action: To resolve workstation memory errors, see "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network.249: Trustee ID value could not be added to the specified directory.TEXTUTIL-Explanation: An internal system error probably has occurred.Action: Restart the workstation. If the problem persists, contact your Novell Authorized Reseller.250: Trustee ID value could not be deleted from the specified directory.TEXTUTIL-Explanation: An internal system error probably has occurred.Action: Restart the workstation. If the problem persists, contact your Novell Authorized Reseller.251: The specified directory could not be scanned for its trustees.TEXTUTIL-Explanation: An internal system error probably has occurred.Action: Restart the workstation. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=1160 ID="BP1154"253: An error occurred while file name was being copied to file name. Number bytes of the requested number bytes were copied.TEXTUTIL-Explanation: An internal system error probably has occurred.Action: Restart the workstation. If the problem persists, contact your Novell Authorized Reseller.256: File name could not be renamed to name because the specified path does not exist.TEXTUTIL-Explanation: The user attempted to rename a file to a path that does not exist.Action: Rename the file to an existing path.257: File name could not be renamed to name because a file with the same name already exists.TEXTUTIL-Explanation: The user attempted to rename a file using a name that already exists.Action: Rename the file with a different name.258: File name could not be renamed to name because the file is currently being used.TEXTUTIL-Explanation: The user attempted to rename a file that is currently being used.Action: Wait until the file is not longer being used; then rename the file.259: File name could not be renamed to name because the directory handle was invalid.TEXTUTIL-Explanation: An internal system error has occurred.Action: Restart the workstation. If the problem persists, contact your Novell Authorized Reseller.260: File name could not be renamed to name because the new file name is illegal.TEXTUTIL-Explanation: The user may have tried to give the file a name reserved by DOS or one that contains control characters (such as * and ?).Action: Give the file a valid name.261: File name could not be renamed to name because this station has no file rename privileges in the specified directory.TEXTUTIL-Explanation: NetWare's rights security system controls which directories, subdirectories, and files a user can access and what the user is allowed to do with them.Action: Obtain the necessary rights to complete this task.PAGENUM=1161 ID="BP1155"262: File name could not be renamed to name because the server is out of dynamic workspace.TEXTUTIL-Explanation: The server does not have enough memory.Action: To resolve server memory errors, see "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.272: The specified path does not exist.TEXTUTIL-Explanation: The path the user specified does not exist.Action: Make sure that the user specifies an existing path.321: The system could not unlink file name because the file was not found.TEXTUTIL-Explanation: An internal system error probably has occurred.Action: Restart the workstation. If the problem persists, contact your Novell Authorized Reseller.322: The system could not unlink file name because the specified path was not found.TEXTUTIL-Explanation: An internal system error has occurred.Action: Restart the workstation. If the problem persists, contact your Novell Authorized Reseller.323: The system could not unlink file name because access was denied.TEXTUTIL-Explanation: NetWare's rights security system controls which directories, subdirectories, and files a user can access and what the user is allowed to do with them.Action: Obtain the necessary rights to complete this task.334: File name could not be closed because the specified file handle is invalid.TEXTUTIL-Explanation: An internal system error probably has occurred.Action: Restart the workstation. If the problem persists, contact your Novell Authorized Reseller.337: File name could not be created because the specified directory could not be found.TEXTUTIL-Explanation: The user specified an invalid path when the user tried to create the file.Action: Type a valid path.PAGENUM=1162 ID="BP1156"338: File name could not be created because too many files are open.TEXTUTIL-Explanation: The number of open files allowed on the system has been exceeded.Action: Either close one or more open files, or wait until another user closes a file; then try again.339: File name could not be created because access was denied.TEXTUTIL-Explanation: NetWare's rights security system controls which directories, subdirectories, and files a user can access and what the user is allowed to do with them.Action: Obtain the necessary rights to complete this task.340: File name could not be opened because the specified files could not be found.TEXTUTIL-Explanation: The user may have specified an invalid filename or mistyped the path. Another possibility is that an internal system error has occurred.Action: Try again, making sure the filename and path are valid and typed correctly. If the problem persists, contact your Novell Authorized Reseller.341: File name could not be opened because the specified directory could not be found.TEXTUTIL-Explanation: The user may have specified an invalid filename or mistyped the path. Another possibility is that an internal system error has occurred.Action: Try again, making sure the filename and path are valid and typed correctly. If the problem persists, contact your Novell Authorized Reseller.342: File name could not be opened because too many files are already open.TEXTUTIL-Explanation: The number of open files allowed on the system has been exceeded.Action: Either close one or more open files, or wait until another user closes a file; then try again.343: File name could not be opened because access was denied.TEXTUTIL-Explanation: NetWare's rights security system controls which directories, subdirectories, and files a user can access and what the user is allowed to do with them.Action: Obtain the necessary rights to complete this task.344: File name could not be opened because the specified access code is invalid.TEXTUTIL-Explanation: The user specified an invalid access code.Action: Use a valid access code.PAGENUM=1163 ID="BP1157"345: File name could not be read because access was denied. The read request was for number bytes.TEXTUTIL-Explanation: NetWare's rights security system controls which directories, subdirectories, and files a user can access and what the user is allowed to do with them.Action: Obtain the necessary rights to complete this task.346: File name could not be read because the specified file handle was invalid. The read request was for number bytes.TEXTUTIL-Explanation: An internal system error probably has occurred.Action: Restart the workstation.If the problem persists, contact your Novell Authorized Reseller.347: Directory name could not be created because the specified path was not found.TEXTUTIL-Explanation: The user may have mistyped the path. Another possibility is that an internal system error has occurred.Action: Try again, making sure the path is valid and typed correctly. If the problem persists, contact your Novell Authorized Reseller.348: Directory name could not be created because access was denied.TEXTUTIL-Explanation: NetWare's rights security system controls which directories, subdirectories, and files a user can access and what the user is allowed to do with them.Action: Obtain the necessary rights to complete this task.349: The system could not write to file name because access was denied. The write request was for number bytes.TEXTUTIL-Explanation: NetWare's rights security system controls which directories, subdirectories, and files a user can access and what the user is allowed to do with them.Action: Obtain the necessary rights to complete this task.350: The system could not write to file name because the specified file handle was invalid. The write request was for number bytes.TEXTUTIL-Explanation: An internal system error probably has occurred.Action: Restart the workstation. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=1164 ID="BP1158"354: The combined width of the program header and the version number is greater than 34. This means that the header will be overwritten by the date and time for certain days in certain months. Shorten the header message.TEXTUTIL-Explanation: The text string is too wide to fit, possibly as a result of expansion during translation. (No more than 34 characters are allowed for the program name and version in the header.)Action: Report the problem to your Novell Authorized Reseller.385: The new bindery object name could not be created. The maximum number of bindery objects specified during installation has been reached. You must increase the number of bindery objects available on this server.TEXTUTIL-Explanation: The new bindery object indicated in the message could not be created because the maximum number of bindery objects has been reached.Action: Modify the configuration file to allow more bindery objects on the server.415: File pattern path_string cannot be erased because some of the files in the directory are currently being used by another station.TEXTUTIL-Explanation: The user cannot delete files that are being used by another user.Action: Wait until all the files are closed; then try again.416: The server does not have enough memory to complete the request.TEXTUTIL-Action: To resolve server memory errors, see "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.417: Either the file with the specified file handle could not be closed, or the bindery failed.TEXTUTIL-Explanation: An internal system error probably has occurred.Action: Restart the workstation. Novell Authorized Reseller418: The file was successfully closed, but the queue job could not be started.TEXTUTIL-Explanation: An internal system error probably has occurred.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.421: Error number occurred during attempt to get a directory path from a directory handle.TEXTUTIL-Explanation: An internal system error probably has occurred.Action: Restart the workstation. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=1165 ID="BP1159"425: Create Queue was passed an invalid queue name (name).TEXTUTIL-Explanation: An internal system error probably has occurred.Action: Restart the workstation. If the problem persists, contact your Novell Authorized Reseller.533: The Unicode files cannot be found.TEXTUTIL-Action: See message IDREF="FM62778""973: The Unicode table files cannot be found in the NLS directory or in the search path. Code page: number Country: number" in Appendix C.541: The specified volume does not exist.TEXTUTIL-Explanation: The user specified an invalid volume name.Action: Try again, using a valid volume name.555: The system could not get physical volume information for volume object name. TEXTUTIL-Explanation: An internal error prevented the program from getting the volume information.Action: Restart the utility and try again. If the problem persists, contact your Novell Authorized Reseller.561: The system was not able to allocate a buffer for the current operation. TEXTUTIL-Explanation: The most likely explanation is that the workstation does not have enough memory.Action: To resolve workstation memory errors, see "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network.562: The system was not able to read the volume objects in the current context. TEXTUTIL-Explanation: The database may be corrupt, the search drive may be incorrect, or the workstation may have a connection problem.Action: If the database is in the proper search path and is a current version, try replacing it with a backup. Make sure the workstation is connected to the network. Try again. If the problem persists, contact your Novell Authorized Reseller.563: The system was not able to retrieve a count of volume objects in the current context. TEXTUTIL-Explanation: An internal error prevented the program from getting the volume information.Action: Restart the utility and try again. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=1166 ID="BP1160"564: The system was not able to read the name of a volume object in the current context. TEXTUTIL-Explanation: The database may be corrupt, the search drive may be incorrect, or the workstation may have a connection problem.Action: If the database is in the proper search path and is a current version, try replacing it with a backup. Make sure the workstation is connected to the network. Try again. If the problem persists, contact your Novell Authorized Reseller.565: The current context has not been set properly. TEXTUTIL-Explanation: Either the user typed in the Directory Services object name incorrectly, or the workstation does not have enough memory to set up the context.Action: Make sure the object name is typed correctly. (Use NETADMIN to verify the correct name.) To resolve workstation memory errors, see "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network.566: The system was not able to set the current context. TEXTUTIL-Explanation: Either the user typed in the Directory Services object name incorrectly or the workstation does not have enough memory to set up the context.Action: Make sure the object name is typed correctly. (Use NETADMIN to verify the correct name.) To resolve workstation memory errors, see "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network.567: The system was not able to get a connection number to access volume object name.TEXTUTIL-Explanation: The database may be corrupted, the search drive may be incorrect, or the workstation may have a connection problem.Action: If the database is in the proper search path and is a current version, try replacing it with a backup. Make sure the workstation is connected to the network. Try again. If the problem persists, contact your Novell Authorized Reseller.568: The system was not able to get a connection ID for server name. TEXTUTIL-Explanation: For some unexpected reason, this utility could not obtain information about a particular server. No other information is available.Action: Try issuing the command again from a different drive. If the problem persists, contact your Novell Authorized Reseller.569: An invalid volume object string was entered. TEXTUTIL-Explanation: The volume object name the user entered is invalid.Action: Make sure the user is specifying a valid volume object name.PAGENUM=1167 ID="BP1161"572: The system could not reset the context after escaping from the Browse option. TEXTUTIL-Explanation: This may be an internal program.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.574: The system could not create a portal in which to display the function key help line. TEXTUTIL-Explanation: This error could indicate lack of workstation memory or an internal problem in the program.Action: To resolve workstation memory errors, see "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network.575: The system could not create a portal in which to display information area text. TEXTUTIL-Explanation: This error could indicate lack of workstation memory or an internal problem in the program.Action: To resolve workstation memory errors, see "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network.576: An incorrect version of the system help file SYS$HELP.HEP was found. The correct version is version. System help will be disabled. TEXTUTIL-Explanation: When the system tried to initialize the SYS$HELP.HEP file, it could not find a correct version of the file within the existing search drives. A file was found, but it was an incorrect version. The following areas were searched:MARK=BULLETThe current directory.The NWLANGUAGE environment variable directory. If the NWLANGUAGE variable is set, it should contain a directory name or names which specify a language (for example, ENGLISH or FRENCH). The files are searched for in a subdirectory of the NLS directory as specified by the NWLANGUAGE variable. The NLS directory in this instance is itself a subdirectory of the load directory. (The load directory contains the current utility's EXE file.)The load directory (the directory containing the current utility's EXE file). This is normally the PUBLIC directory.The PATH and DPATH (for OS/2 only) environment variables. These environment variables may be found either in the user's login script or in the AUTOEXEC.BAT file.The first directory found under the child NLS subdirectory of the load directory. PAGENUM=1168 ID="BP1162"The first directory found under the sibling NLS subdirectory of the load directory.Action: Find a current version of the system help file and either copy it to a directory that is mapped to an existing search drive, or map a search drive to the file.577: The message file found utility_name.MSG is an incorrect version. The correct version is version. See your network supervisor for assistance.TEXTUTIL-Action: See message IDREF="FM91957""998: The message file found (utility_name.MSG) is an incorrect version. The correct version is number. See your network supervisor for assistance." in Appendix C.578: The help file found (name.HEP) is an incorrect version. The correct version is version. Program help will be disabled. TEXTUTIL-Explanation: When the utility tried to initialize the utility_name.HEP file, it could not find a correct version of the file within the existing search drives. A file was found, but it was an incorrect version. The following areas were searched:MARK=BULLETThe current directory.The NWLANGUAGE environment variable directory. If the NWLANGUAGE variable is set, it should contain a directory name or names which specify a language (for example, ENGLISH or FRENCH). The files are searched for in a subdirectory of the NLS directory as specified by the NWLANGUAGE variable. The NLS directory in this instance is itself a subdirectory of the load directory. (The load directory contains the current utility's EXE file.)The load directory (the directory containing the current utility's EXE file). This is normally the PUBLIC directory.The PATH and DPATH (for OS/2 only) environment variables. These environment variables may be found either in the user's login script or in the AUTOEXEC.BAT file.The directories found under the child NLS subdirectory of the load directory. The directories found under the sibling NLS subdirectory of the load directory.Action: Find a current version of the help file and either copy it to a directory that is mapped to an existing search drive, or map a search drive to the file.PAGENUM=1169 ID="BP1163"588: The system was unable to parse the specified path. TEXTUTIL-Explanation: The program could not find the directory path because the user either specified a directory path that does not exist or mistyped the directory path.Action: Use the FILER utility to examine the directory. Type the directory path correctly. The correct syntax is as follows:FORMAT="LINESPECIFIC"MOREINFO="NONE"Server\volume:directory\subdirectory\file  or FORMAT="LINESPECIFIC"MOREINFO="NONE"Drive:directory\subdirectory\file The user can use the MAP command or the NETUSER utility to map a network drive to a directory; then the user can specify the drive, rather than the directory path, in the command. 589: The system received an invalid path for the current server mode. TEXTUTIL-Explanation: This is probably an internal error in the program.Action: Try again. If the problem persists, contact your Novell Authorized Reseller.590: An error occurred while attempting to build a class list. It is likely that the workstation is out of memory. TEXTUTIL-Explanation: The workstation does not have enough memory.Action: To resolve workstation memory errors, see "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network.591: The path must contain a full drive specification, including a ":". TEXTUTIL-Explanation: The user specified an incomplete drive designation.Action: Specify a complete designation. Be sure the drive name is followed by a colon (:).592: Directory_name is part of the current tree. TEXTUTIL-Explanation: The user tried to add a directory name to the tree, but a directory with that name is already in the tree.Action: If the user is trying to add a directory that is already in the tree, no action is necessary. Otherwise, assign a different name to the directory the user wants to add.PAGENUM=1170 ID="BP1164"593: The system could not read the network address for directory_name. TEXTUTIL-Explanation: The database may be corrupt, the search drive may be incorrect, or the workstation may have a connection problem.Action: If the database is in the proper search path and is a current version, try replacing it with a backup. Make sure the workstation is connected to the network. Try again. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=1171 ID="BP1165"TIMESYNC48: Cannot initialize time synchronization.TIMESYNCExplanation: Time synchronization cannot be initialized, possibly due to insufficient memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.49: Cannot start time synchronization.TIMESYNCExplanation: Time synchronization cannot be initialized, possibly due to insufficient memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.51: Cannot allocate settable parameters tag.TIMESYNCExplanation: Time synchronization cannot be initialized, possibly due to insufficient memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.53: Cannot allocate alloc tag.TIMESYNCExplanation: Time synchronization cannot be initialized, possibly due to insufficient memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.55: Cannot allocate NCP resource tag.TIMESYNCExplanation: Time synchronization cannot be initialized, possibly due to insufficient memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.57: Cannot allocate process tag.TIMESYNCExplanation: Time synchronization cannot be initialized, possibly due to insufficient memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.PAGENUM=1172 ID="BP1166"59: Cannot allocate event tag.TIMESYNCExplanation: Time synchronization cannot be initialized, possibly due to insufficient memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.60: Cannot parse load command line arguments.TIMESYNCExplanation: One of the following probably accounts for this error:MARK=BULLETYour server does not have enough memory available.The syntax in the command line is invalid. You may have made a typing error or used illegal characters.Action: Make sure the syntax in your command line is valid. If it is, make more memory available. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.61: Cannot initialize global information.TIMESYNCExplanation: Your server does not have enough memory available.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.62: Cannot hook TimeSync NCP verb.TIMESYNCExplanation: The program cannot get a resource. Someone is already running a version of TIMESYNC.NLM that is interfering with the current NLM program.Action: Find out who is running the interfering NLM program and unload it. If this is not the problem, check your server's memory. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.63: Couldn't allocate main stack.TIMESYNCExplanation: Your server does not have enough memory available.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.65: Couldn't create main process.TIMESYNCExplanation: Your server does not have enough memory available.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.PAGENUM=1173 ID="BP1167"72: Time synchronization has been lost after number successful polling loops.TIMESYNCExplanation: Time synchronization was lost for some unexplained reason. This is normally not a problem and the system will reestablish synchronization. However, if the problem occurs frequently, you may have a hardware or network problem.Action: Try the following:MARK=BULLETCheck for recent time changes or configuration changes that may have caused this problem.Check the "Synchronization Radius" parameter and make sure it is not unreasonably small. A practical limit is 1000 milliseconds (1 second).You may be experiencing a hardware or network problem. See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.73: Unrecognized command line parameter: parameter.TIMESYNCExplanation: You entered an invalid parameter in the command line.Action: Try again, making sure you are using correct syntax.77: Unrecognized parameter in configuration file: string.TIMESYNCExplanation: You entered an invalid parameter in the TIMESYNC.CFG file.Action: Try again, making sure you are using correct syntax.92: Primary, reference and single servers should not follow a secondary server. This server polled: server_name. The time exchange was ignored.TIMESYNCExplanation: This error is caused by incorrect custom configuration of a Time Source List. A Single Reference, Primary, or Reference server was instructed to synchronize to a Secondary server. This error only results from a custom configuration; it cannot occur when SAP is used.Action: Check the "Time Source List" in the TIMESYNC.CFG file for each Primary and Reference server. The order of servers in the list determines the polling order. Secondary servers should never be listed.114: Synchronization Radius less than number will prevent synchronization.TIMESYNCPAGENUM=1174 ID="BP1168"Explanation: The "Synchronization Radius" parameter is set to a value lower than the current correction floor setting for the TIMESYNC.NLM. The default synchronization radius is 2000 milliseconds; the default correction floor setting is 1 millisecond. (The correction floor parameter can be changed, though normally it should not be.)Action: Set the Synchronization Radius parameter to a value higher than the correction floor setting. A value of 1000-2000 milliseconds (1-2 seconds) or higher is usually adequate.129: Synchronization Radius less than number will prevent synchronization.TIMESYNCExplanation: The Synchronization Radius parameter is set to a value lower than the current correction floor setting for the TIMESYNC.NLM. The default synchronization radius is 2000 milliseconds; the default correction floor setting is 1 millisecond. (The correction floor parameter can be changed, though normally it should not be.)Action: Set the Synchronization Radius parameter to a value higher than the correction floor setting. A value of 1000-2000 milliseconds (1-2 seconds) or higher is usually adequate.133: Cannot allocate timer tag.TIMESYNCExplanation: Your server probably does not have enough available memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.137: SINGLE servers are incompatible with REFERENCE and PRIMARY servers and should not follow secondary servers. This server polled: "server_name." The time exchange was ignored!TIMESYNCExplanation: A Single Reference server should not exist in an environment that includes a Reference or Primary server. Action: Check the "Time Source List" in the TIMESYNC.CFG file for both the named server and the server reporting the error. Single servers do not need a "Time Source List." Secondary servers should never be in a "Time Source List."138: Time synchronization has been established.TIMESYNCExplanation: This message appears right after you load TIMESYNC.NLM or after you reestablish synchronization.Action: If the time period between when you lost synchronization and when it was reestablished is no more than a few minutes, no action is needed. If, however, the gap is significant (more than 15 minutes), use standard troubleshooting techniques to make sure that you don't have a hardware problem. "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network.150: Cannot allocate SAP socket tag.TIMESYNCExplanation: Your server probably does not have enough available memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.PAGENUM=1175 ID="BP1169"151: Cannot open SAP socket.TIMESYNCExplanation: The operating system has no more sockets to allocate. You are probably trying to run more processes on a single server than is practical.Action: To alleviate the problem temporarily, unload any unneeded NLM programs that require SAP sockets. To prevent future occurrences of the problem, you should probably distribute your network services over more than a single server.PAGENUM=1176 ID="BP1170"TLITLI, or Transport Level Interface, is a UNIX-based interface that provides basic end-to-end data transfer support needed by software applications and higher level protocols. It hides the topology and characteristics of the underlying network from users. It defines a set of services common to different protocol suites so that data can be ported across a variety of transport providers. TLI supports the International Standards Organization (ISO) protocols, TCP/IP, XNS, and SNA.All TLI messages are generated by a specific application. The messages listed here are called from the TLI library of function calls and are always followed by an application-specific message. If you need further information to resolve the problem, contact your application's vendor or a Novell Authorized Reseller.2: No error was specified.TLIExplanation: Either an error occurred that did not set the t_errno function to a specific error value, or an error has not yet occurred.Action: Notify your application's vendor or developer.3: Insufficient permission.TLIExplanation: A function has been called that is not allowed.Action: If you have access to developer documentation, look up the platform-specific restrictions and options for the underlying protocol and operating system being used. Otherwise, notify your application's vendor or developer.4: Incorrect transport address format.TLIExplanation: The application has called a function by passing an address that contains an incorrect format or illegal information.Action: If you have access to developer documentation, look up the platform-specific restrictions and options for the underlying protocol being used. Otherwise, notify your application's vendor or developer.5:Illegal amount of data.TLIExplanation: The amount of data used was not within the range set by the transport provider.Action: If you have access to developer documentation, look up the platform-specific restrictions for the minimum and maximum amount of data that can be sent. Otherwise, notify your application's vendor or developer.PAGENUM=1177 ID="BP1171"6: File descriptor does not refer to a transport endpoint.TLIExplanation: The file descriptor that was passed to the function is either invalid or has not been properly opened.Action: Notify your application's vendor or developer.7:Iincorrect flags.TLIExplanation: An invalid flag was specified.Action: Notify your application's vendor or developer.8: Incorrect transport options.TLIExplanation: The user or application does not have permission to accept a connection on the responding transport endpoint or to use the specified options.Action: Notify your application's vendor or developer.9:Iincorrect sequence number.TLIExplanation: The sequence number specified did not match the sequence number expected when the connection was being either established or rejected.Action: Notify your application's vendor or developer.10: Buffer size insufficient.TLIExplanation: A function has been called with a buffer of insufficient size to return protocol information.Action: If you have access to developer documentation, look up platform-specific protocol requirements of the system to determine a valid buffer size. Otherwise, notify your application's vendor or developer.11: Cannot send message.TLIExplanation: An unidentified error has prevented the message from being sent.Action: Notify your application's vendor or developer.12: An asynchronous event has occurred.TLIExplanation: In the process of calling a function, an asynchronous event has occurred on the endpoint. The t_look function can be called to determine what event took place.Action: Notify your application's vendor or developer.PAGENUM=1178 ID="BP1172"13: Transport provider could not allocate an address.TLIExplanation: The specified protocol address was in an incorrect format, contained illegal information, or was already being used. No dynamic addresses remain.Action: If you have access to developer documentation, look up platform-specific protocol restrictions on address format. Otherwise, notify your application's vendor or developer.14: No data is available.TLIExplanation: The function has been called on an endpoint where no data is available.Action: Notify your application's vendor or developer.15: No orderly release indication is available.TLIExplanation: A t_rcvrel function has been called when no orderly release indication has arrived from the other endpoint.Action: Notify your application's vendor or developer.16: Function not supported by the transport.TLIExplanation: The function is not supported by the underlying transport provider.Action: Notify your application's vendor or developer.17: Primitive issued in the wrong sequence.TLIExplanation: The function has been called in an improper state.Action: Notify your application's vendor or developer.18: State is changing.TLIExplanation: The transport provider is undergoing a transient state change.Action: Notify your application's vendor or developer.19:A system error occurred.TLIExplanation: A system error occurred during the execution of the function.Action: Notify your application's vendor or developer.20: No unitdata error indication is available.TLIExplanation: An error function was used by the application when no error condition existed.Action: Notify your application's vendor or developer.PAGENUM=1179 ID="BP1173"21: No disconnect indication is available.TLIExplanation: No disconnect indication currently exists on the specified transport endpoint.Action: Notify your application's vendor or developer.22: Unsupported struct-type requested.TLIExplanation: The structure specified in the t_alloc function is not supported.Action: Notify your application's vendor or developer.23:Iinvalid transport provider name.TLIExplanation: The transport protocol specified when the t_open function is not available.Action: Make sure you have loaded all of the protocols required by the application. If the problem persists, notify your application's vendor or developer.24: Qlen is zero.TLIExplanation: The argument "qlen" of the endpoint referenced by fd is zero. The application is trying to function as a server after initializing itself as a client.Action: Notify your application's vendor or developer.25: Address in use.TLIExplanation: The transport provider could not allocate the specified address because it is currently being used.Action: Specify an address that is not in use.57: Unable to Register TLI with CLIB; TLI cannot load successfully.TLIExplanation: This is a fatal error.Action: Contact your Novell Authorized Reseller.62: The internal consistency check on the TLI error message table has determined that the table is not large enough to hold all TLI error messages; TLI cannot load successfully.TLIExplanation: This is a fatal error.Action: Contact your Novell Authorized Reseller.PAGENUM=1180 ID="BP1174"TOKENDMA-NW025: You cannot load MSM31X on a NetWare 3.10 server.TOKENDMA-NWExplanation: You attempted to load MSM31X.NLM on a NetWare 3.10 server. MSM31X.NLM will run only on a NetWare 3.11 server.Action: Either load a version of the Media Support Module (MSM) that will run on a NetWare 3.10 server, or upgrade your server to NetWare 3.11. For information on MSM, see "BOOK="cncptenu" COLLECTION="nw41"Media Support Module (MSM)" in Concepts.026: On a NetWare 3.11 server, you must load LSLENH.NLM before you load MSM31X.NLM.TOKENDMA-NWExplanation: The Link Support Layer (LSL) and Media Support Module (MSM) have been loaded on a NetWare 3.11 server. An attempt was made to load LSLENH.NLM. You cannot load LSLENH.NLM once the MSM has been loaded. (LSLENH.NLM adds enhancement to the LSL.)Action: Unload MSM31X.NLM; then load LSLENH.NLM. Once the LSLENH.NLM has been loaded, load MSM31X.NLM again. For information on LSL and MSM, see "BOOK="cncptenu" COLLECTION="nw41"Link Support Layer (LSL)" and "BOOK="cncptenu" COLLECTION="nw41"Link Support Layer (LSL)" in Concepts.050: [ISA bus | Microchannel] The board cannot be found.TOKENDMA-NWExplanation: If you are using an ISA bus network board, the network board was not found due to one or more of the following conditions: MARK=BULLETThe network board is not present in the machine. The network board settings are not the defaults, and they are not defined in the NET.CFG file.Another network board is using the same hardware settings as this network board.The network board is bad.Action: Do one or more of the following:MARK=BULLETMake sure the network board is properly seated into the slot. If DIP switch settings are not the defaults, make sure that they match the settings in the NET.CFG file. PAGENUM=1181 ID="BP1175"If you are not using the NET.CFG file, make sure the DIP switch settings are set to the defaults. If other network boards are using the same hardware settings, change the settings and try to reload the driver.Replace the bad network board with one that you know is good.Explanation: If you are using a microchannel network board, either the network board is not in the machine, or the network board's configuration could not be obtained.Action: Do one of the following:MARK=BULLETMake sure the network board is properly seated into a slot.Insert the network board into a slot, and run the CLASS=DISKReference diskette to install it.067: The group bit in the node address override was cleared.TOKENDMA-NWExplanation: You entered a node address with the Group address bit set; the Topology Specific Module (TSM) cleared it. For more information about TSM, see "BOOK="cncptenu" COLLECTION="nw41"Topology Specific Module (TSM)" in Concepts.Action: None. This message is for information only.068: The local bit in the node address override was set.TOKENDMA-NWExplanation: You entered a node address without the local bit being set; the Topology Specific Module (TSM) set it. For more information about TSM, see "BOOK="cncptenu" COLLECTION="nw41"Topology Specific Module (TSM)" in Concepts.Action: None. This message is for information only.071: The matching virtual adapter could not be found.TOKENDMA-NWExplanation: A new frame was being added to an existing network board, but the Media Support Module (MSM) could not locate a previous network board to link it with.Action: Obtain the most current version of MSM.NLM. For more information about TSM, see "BOOK="cncptenu" COLLECTION="nw41"Topology Specific Module (TSM)" in Concepts.072: A resource tag is unavailable.TOKENDMA-NWExplanation: The server may not have enough available memory. NetWare cannot allocate memory for a resource tag.Action: Free up memory by unloading nonessential NLM programs from the server.PAGENUM=1182 ID="BP1176"073: Unable to allocate memory.TOKENDMA-NWExplanation: The server may not have enough available memory. NetWare cannot allocate memory for the LAN driver.Action: Free up memory by unloading nonessential NLM programs from the server.074: The hardware interrupt cannot be set.TOKENDMA-NWExplanation: NetWare could not set the hardware interrupt that the LAN driver registered. The LAN driver must have changed information in the configuration table (IntNumber, SharingFlags) after the hardware options were registered.Action: Make sure that interrupt setting on the board matches the setting in the AUTOEXEC.NCF file. For information on the AUTOEXEC.NCF file, see "BOOK="superenu" COLLECTION="nw41"Maintaining the NetWare Server" in Supervising the Network.075: The MLID cannot be registered with the LSL.TOKENDMA-NWExplanation: The LAN driver's Link Support Layer (LSL) ran out of logical boards, or it could not allocate memory for its internal structures. For more information about LSL, see "BOOK="cncptenu" COLLECTION="nw41"Link Support Layer (LSL)" in Concepts.Action: Unload nonessential LAN drivers that are consuming large numbers of logical boards, or free up memory by unloading nonessential NLM programs.076: The polling procedure cannot be added.TOKENDMA-NWExplanation: Too many polling processes are registered with the operating system.Action: Unload nonessential NLM programs that may be using a polling procedure.077: The event notification routine cannot be registered.TOKENDMA-NWExplanation: The server may not have enough available memory. NetWare cannot allocate memory for internal structures related to event notification. Action: Free up memory by unloading nonessential NLM programs from the server.079: The MLID did not initialize MSMTxFreeCount.TOKENDMA-NWExplanation: The .LAN file is either outdated or corrupted.Action: Obtain a new .LAN file.082: The node address cannot be set.TOKENDMA-NWExplanation: Unable to locate node address in the network board's ROM space.Action: Replace the network board with one that you know is good.PAGENUM=1183 ID="BP1177"084: Couldn't allocate memory below the 16 Megabyte boundary.TOKENDMA-NWExplanation: NetWare ran out of memory buffers from the pool below 16 megabytes.Action: Set reserved buffers below 16 MB (in STARTUP.NCF) to a higher number. For information on the STARTUP.NCF file, see "BOOK="superenu" COLLECTION="nw41"Maintaining the NetWare Server" in Supervising the Network.086: The driver parameter block is too small.TOKENDMA-NWExplanation: The .LAN file is designed to run with an older version of the MSM.NLM.Action: Obtain a newer version of the .LAN file or an older version of the MSM.NLM.087: The media parameter block is too small.TOKENDMA-NWExplanation: The topology NLM program is designed to run with an older version of the MSM.NLM.Action: Obtain a newer version of the topology NLM program or an older version of the MSM.NLM.091: The hardware configuration conflicts.TOKENDMA-NWExplanation: Another hardware resource is being used, which the LAN driver is trying to register.Action: Change the hardware configuration of the network board or of the conflicting device.092: Cannot schedule AES without an HSM routine.TOKENDMA-NWExplanation: The LAN driver is either outdated or corrupted.Action: Obtain a new .LAN file.093: Cannot schedule interrupt time call back without an HSM routine.TOKENDMA-NWExplanation: The LAN driver is either outdated or corrupted.Action: Obtain a new .LAN file.094: Cannot set hardware interrupt without an HSM routine.TOKENDMA-NWExplanation: The LAN driver is either outdated or corrupted.Action: Obtain a new .LAN file.PAGENUM=1184 ID="BP1178"095: Cannot add polling without an HSM routine.TOKENDMA-NWExplanation: The LAN driver is either outdated or corrupted.Action: Obtain a new .LAN file.201-Adapter 1: DIR.OPEN.ADAPTER error code = error_bit_number. Trying again.TOKENDMA-NWExplanation: The network board cannot be opened for operation.Action: Replace the network board with one you know is good.207: Initialization error = error_bit_number.TOKENDMA-NWExplanation: The network board did not initialize properly after being reset.Action: Replace the network board with one that you know is good. 233-Adapter 1-Board 1: The adapter detected a duplicate station during the insertion process. Error code = bit_number.TOKENDMA-NWExplanation: Another network board is using the same node address.Action: Use a different node address.234-Adapter 1-Board 1: The adapter received a Remove MAC Frame during the insertion process. Error code = bit_number.TOKENDMA-NWExplanation: The network board could not access the network because another network board has forced it off due to protocol incompatibilities.Action: Replace the network board with one you know is good.235-Adapter 1-Board 1: The adapter cable was disconnected during the insertion process. Error code = bit_number.TOKENDMA-NWExplanation: The network board could not access the network because the cable was disconnected.Action: Securely fasten the cable links, and reboot the workstation.236-Adapter 1: The ring was beaconing during the insertion process. Error code = bit_number.TOKENDMA-NWExplanation: The network board could not access the network because it is set at the wrong data rate.Action: Set the correct network board data rate.PAGENUM=1185 ID="BP1179"237-Adapter 1-Board 1: The adapter is beaconing. Ring status = bit_number.TOKENDMA-NWExplanation: The ring has detected a network board that is trying to access the network with the wrong data rate.Action: Find out which network board in the ring is set up at the wrong data rate, and correct it.238-Adapter 1-Board 1: The adapter check caused the adapter to deregister. Error code = error_bit_number.TOKENDMA-NWExplanation: An Adapter Check error was issued by the network board, which caused the driver to reset the network board.Action: If error persists, replace the network board with one that you know is good.239-Adapter 1-Board 1: Cable is disconnected at the board. The board is resetting. Ring status = bit_number.TOKENDMA-NWExplanation: The cable was disconnected at the network board.Action: Securely fasten the cable to the network board.240-Adapter 1-Board 1: Cable is disconnected at the MAU. The board is resetting. Ring status = bit_number.TOKENDMA-NWExplanation: Cable was disconnected at the Medium Access Unit (MAU).Action: Securely fasten the cable onto the MAU.241-Adapter 1-Board 1: The Auto Removal process reset the adapter. Ring status = bit_number.TOKENDMA-NWExplanation: The network board removed itself from the ring due to internal errors. The driver will reset the network board and continue.Action: None. This message is for information only.242-Adapter 1-Board 1: The Remove MAC Frame process shut down the adapter. Ring status = bit_number.TOKENDMA-NWExplanation: The network board removed itself from the ring as requested by another network board.Action: Replace the network board with one that you know is good.PAGENUM=1186 ID="BP1180"243-Adapter 1-Board 1: The adapter alert condition was corrected.TOKENDMA-NWExplanation: The previous alert condition has been corrected.Action: None. This message is for information only.244: The adapter's microcode is not loaded.TOKENDMA-NWExplanation: The network board's microcode has not been loaded since the hardware was powered up.Action: Load the microcode at the DOS prompt using the download utility.245: The adapter cannot handle memory above 16 MB. Use the "BELOW 16" keyword when you load the driver.TOKENDMA-NWExplanation: The host contained over 16 megabytes of memory and the BELOW 16 keyword was not included in the command line to signal the driver to allocate only buffers below 16 MB. The default size of the memory pool below 16 MB is sixteen 4 KB buffers (64 KB). Action: Use the 16 BELOW keyword to enable allocation of memory below 16 megabytes. To increase the number of buffers below 16 MB, add the following command to the STARTUP.NCF file:FORMAT="LINESPECIFIC"MOREINFO="NONE"Set reserved buffers below 16 meg = 64 This will increase the pool size to 256 KB, which should be enough memory for the driver's data spaces and spare ECBs.PAGENUM=1187 ID="BP1181"TOKEN-NW025: You cannot load MSM31X on a NetWare 3.10 server.TOKEN-NWExplanation: You attempted to load MSM31X.NLM on a NetWare 3.1 server. MSM31X.NLM will run only on a NetWare 3.11 server.Action: Either load a version of the Media Support Module (MSM) that will run on a NetWare 3.1 server, or upgrade your server to NetWare 3.11. F or more information about MSM, see "BOOK="cncptenu" COLLECTION="nw41"Media Support Module (MSM)" in Concepts.026: On a NetWare 3.11 server, you must load LSLENH.NLM before you load MSM31X.NLM.TOKEN-NWExplanation: The Link Support Layer (LSL) and Media Support Module (MSM) have been loaded on a NetWare 3.11 server. You attempted to load LSLENH.NLM. You cannot load LSLENH.NLM once the MSM has been loaded. (LSLENH.NLM adds enhancement to the LSL.)Action: Unload MSM31X.NLM; then load LSLENH.NLM. Once LSLENH.NLM has been loaded, load MSM31X.NLM again. For more information about LSL and MSM, see "BOOK="cncptenu" COLLECTION="nw41"Link Support Layer (LSL)" and "BOOK="cncptenu" COLLECTION="nw41"Media Support Module (MSM)"in Concepts.050: [ISA bus | Microchannel] The board cannot be found.TOKEN-NWExplanation: The ISA bus network board was not found due to one or more of the following conditions: MARK=BULLETThe network board is not present in the machine. The network board settings are not the defaults, and they are not defined in the NET.CFG file.Another network board is using the same hardware settings as this network board.The network board is bad.Action: Do one or more of the following:MARK=BULLETMake sure the network board is properly seated into the slot. If hardware settings are not the defaults, make sure they match the settings in the NET.CFG file. PAGENUM=1188 ID="BP1182"If you are not using the NET.CFG file, make sure the hardware settings are set to the defaults. If other network boards are using the same hardware settings, change the settings and try to reload the driver.Replace the bad network board with one that you know is good.Explanation: The microchannel network board is not in the machine, or the board's configuration could not be obtained.Action: Do one of the following:MARK=BULLETMake sure the network board is properly seated into a slot.Insert the network board into a slot, and use the CLASS=DISKReference diskette to install it.067: The group bit in the node address override was cleared.TOKEN-NWExplanation: You entered a node address with the Group address bit set; the Topology Specific Module (TSM) cleared it. For more information about TSM, see "BOOK="cncptenu" COLLECTION="nw41"Topology Specific Module (TSM)" in Concepts.Action: None. This message is for information only.068: The local bit in the node address override was set.TOKEN-NWExplanation: You entered a node address without the local bit being set; the Topology Specific Module (TSM) set it. For more information about TSM, see "BOOK="cncptenu" COLLECTION="nw41"Topology Specific Module (TSM)" in Concepts.Action: None. This message is for information only.071: The matching virtual adapter could not be found.TOKEN-NWExplanation: A new frame was being added to an existing network board, but the Media Support Module (MSM) could not locate a previous network board to link it with.Action: Obtain the most current version of MSM.NLM. For more information about MSM, see "BOOK="cncptenu" COLLECTION="nw41"Topology Specific Module (TSM)" in Concepts.072: A resource tag is unavailable.TOKEN-NWExplanation: The server may not have enough available memory. NetWare cannot allocate memory for a resource tag.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.PAGENUM=1189 ID="BP1183"073: Unable to allocate memory.TOKEN-NWExplanation: The server may not have enough available memory. NetWare cannot allocate memory for the LAN driver.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.074: The hardware interrupt cannot be set.TOKEN-NWExplanation: NetWare could not set the hardware interrupt that the LAN driver registered. The LAN driver must have changed information in the configuration table (IntNumber, SharingFlags) after the hardware options were registered.Action: Check the interrupt setting on the board and make sure it matches the setting in the AUTOEXEC.NCF file. For more information about the AUTOEXEC.NCF file, see "BOOK="superenu" COLLECTION="nw41"Maintaining the NetWare Server" in Supervising the Network.075: The MLID cannot be registered with the LSL.TOKEN-NWExplanation: The LAN driver's Link Support Layer (LSL) ran out of logical boards, or it could not allocate memory for its internal structures. for more information about LSL, see "BOOK="cncptenu" COLLECTION="nw41"Link Support Layer (LSL)" in Concepts.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.076: The polling procedure cannot be added.TOKEN-NWExplanation: Too many polling processes are registered with the NetWare operating system.Action: Unload nonessential NLM programs that may be using a polling procedure.077: The event notification routine cannot be registered.TOKEN-NWExplanation: The server may not have enough available memory. NetWare cannot allocate memory for internal structures related to event notification. Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.079: The MLID did not initialize MSMTxFreeCount.TOKEN-NWExplanation: The LAN driver file is either outdated or corrupted.Action: Use a new LAN driver file.086: The driver parameter block is too small.TOKEN-NWExplanation: The LAN driver file is designed to run with an older version of the MSM.NLM.Action: Use a version of the LAN driver file that is compatible with the MSM.NLM.PAGENUM=1190 ID="BP1184"087: The media parameter block is too small.TOKEN-NWExplanation: The TOKEN-NW.NLM is designed to run with an older version of the MSM.NLM.Action: Use a version of the TOKEN-NW NLM that is compatible with the MSM.NLM or update the NSM.NLM.091: The hardware configuration conflicts.TOKEN-NWExplanation: The LAN driver is trying to register a hardware resource set on the network board that is already being used.Action: Change the hardware configuration of the network board or of the conflicting device.092: Cannot schedule AES without an HSM routine.TOKEN-NWExplanation: The LAN driver file is either outdated or corrupted.Action: Use a new LAN driver file.093: Cannot schedule interrupt time call back without an HSM routine.TOKEN-NWExplanation: The LAN driver file is either outdated or corrupted.Action: Use a new LAN driver file.094: Cannot set hardware interrupt without an HSM routine.TOKEN-NWExplanation: The LAN driver file is either outdated or corrupted.Action: Use a new LAN driver file.095: Cannot add polling without an HSM routine.TOKEN-NWExplanation: The LAN driver file is either outdated or corrupted.Action: Use a new LAN driver file.201-Adapter 1: DIR.OPEN.ADAPTER error code = error_bit_number. Trying again.TOKEN-NWExplanation: The network board cannot be opened for operation.Action: Replace the network board with one that you know is good.206: An interrupt failed to occur during initialization.TOKEN-NWExplanation: The network board never interrupted the host after it was reset.Action: Replace the network board with one that you know is good.PAGENUM=1191 ID="BP1185"226: The ROM and shared RAM address overlap. Please check the ROM switch settings and RAM address (MEM #2) in the NET.CFG file.TOKEN-NWExplanation: The shared RAM buffer and ROM buffer overlap.Action: Reconfigure the Token-Ring hardware. See the documentation that came with the network board.233-Adapter 1: The adapter detected a duplicate station during the insertion process. Error code = bit_number.TOKEN-NWExplanation: Another network board is using the same node address.Action: Use a different node address.234-Adapter 1-Board 1: The adapter received a Remove MAC Frame during the insertion process. Error code = bit_number.TOKEN-NWExplanation: The network board could not access the network because another network board has forced it off due to protocol incompatibilities.Action: Replace the network board with one that you know is good.235-Adapter 1-Board 1: The adapter cable was disconnected during the insertion process. Error code = bit_number.TOKEN-NWExplanation: The network board could not access the network because the cable was disconnected.Action: Securely fasten the cable links, reboot the workstation, and reload the driver.236-Adapter 1: The ring was beaconing during the insertion process. Error code = bit_number.TOKEN-NWExplanation: The network board could not access the network because it is set at the wrong data rate.Action: Set the correct network board data rate.237-Adapter 1-Board 1: The adapter is beaconing. Ring status = bit_number.TOKEN-NWExplanation: The ring has detected a network board that is trying to access the network with the wrong data rate.Action: Find out which network board in the ring is set up at the wrong data rate, and correct it.PAGENUM=1192 ID="BP1186"238-Adapter 1-Board 1: The adapter check caused the adapter to deregister. Error code = error_bit_number.TOKEN-NWExplanation: An adapter check error was issued by the network board, which caused the driver to reset the network board.Action: If the error persists, replace the network board with one that you know is good.239-Adapter 1-Board 1: Cable is disconnected at the board. The board is resetting. Ring status = bit_number.TOKEN-NWExplanation: The cable is disconnected from the network board.Action: Securely fasten the cable to the network board.240-Adapter 1-Board 1: Cable is disconnected at the MAU. The board is resetting. Ring status = bit_number.TOKEN-NWExplanation: The cable is disconnected from the Media Access Unit (MAU).Action: Securely fasten the cable to the MAU.241-Adapter 1-Board 1: The Auto Removal process reset the adapter. Ring status = bit_number.TOKEN-NWExplanation: The network board removed itself from the ring due to internal errors. The driver will reset the network board and continue.Action: None. This message is for information only.242-Adapter 1-Board 1: The Remove MAC Frame process shut down the adapter. Ring status = bit_number.TOKEN-NWExplanation: The network board removed itself from the ring as requested by another network board.Action: Replace the network board with one that you know is good.243-Adapter 1-Board 1: The adapter alert condition was corrected.TOKEN-NWExplanation: The previous network board alert condition has been corrected.Action: None. This message is for information only.PAGENUM=1193 ID="BP1187"TOKEN-OS2050: [ISA bus | Microchannel] The board cannot be found.TOKEN-OS2Explanation: If you are using an ISA bus network board, the network board was not found due to one or more of the following conditions: MARK=BULLETThe network board is not present in the machine. The network board settings are not the defaults, and they are not defined in the NET.CFG file.Another network board is using the same hardware settings as this network board.The network board is bad.Action: Do one or more of the following:MARK=BULLETMake sure the network board is properly seated into the slot. If DIP switch settings are not the defaults, make sure the settings match the settings in the NET.CFG file. If you are not using the NET.CFG file, make sure the DIP switch settings are set to the defaults. If other network boards are using the same hardware settings, change the settings and try to reload the driver.Replace the bad network board with one that you know is good.Explanation: If you are using a microchannel network board, the network board is not in the machine, or the network board's configuration could not be obtained.Action: Do one of the following:MARK=BULLETMake sure the network board is properly seated into a slot.Insert the network board into a slot, and run the CLASS=DISKReference diskette to install it.PAGENUM=1194 ID="BP1188"056: This interrupt is already used and cannot be shared.TOKEN-OS2Explanation: The selected interrupt is being used by another device, so it cannot be used for this network board.Action: If you are using a microchannel network board, run the CLASS=DISKReference diskette that came with the computer, and change the jumper setting on the network board to use a different interrupt. See the TOKEN hardware manual for information about jumper settings. Edit the NET.CFG file to reflect the correct interrupt level used by the network board. For information on the NET.CFG file, see "BOOK="ws_osenu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for OS/2 User Guide.If you are using an ISA Bus network board, change the DIP switch settings to specify a different interrupt; then edit the NET.CFG file to reflect the correct interrupt level used by the network board.204: The shared RAM is on an incorrect boundary.TOKEN-OS2Explanation: The shared RAM and the mapped memory I/O locations overlap.Action: See the hardware manual for your network board, and change the jumper settings to eliminate the memory conflict. 206: An interrupt failed to occur during initialization.TOKEN-OS2Explanation: Either the jumper settings are incorrect, or a hardware error has occurred.Action: See the TOKEN hardware manual for correct interrupt switch settings. If the settings are correct, replace the network board. 227: [ISA bus | Microchannel] Either the board was not found or the bus is unrecognizable.TOKEN-OS2Explanation: If you are using an ISA bus network board, the network board was not found due to one or more of the following conditions: MARK=BULLETThe network board is not present in the machine. The network board settings are not the defaults, and they are not defined in the NET.CFG file.Another network board is using the same hardware settings as this network board.The network board is bad.Action: Do one or more of the following:MARK=BULLETMake sure the network board is properly seated into the slot. PAGENUM=1195 ID="BP1189"If DIP switch settings are not the defaults, make sure that they match the settings in the NET.CFG file. If you are not using the NET.CFG file, make sure the DIP switch settings are set to the defaults. If other network boards are using the same hardware settings, change the settings and try to reload the driver.Replace the bad network board with one that you know is good.Explanation: If you are using a microchannel network board, either the network board is not in the machine, or the network board's configuration could not be obtained.Action: Do one of the following:MARK=BULLETMake sure the network board is properly seated into a slot.Insert the network board in a slot, and run the CLASS=DISKReference diskette to install it.232: Buffer memory failure.TOKEN-OS2Explanation: This a hardware error. The network board is defective.Action: Replace the network board.240: Invalid Node Override, Group Address bit was set now reset.TOKEN-OS2Explanation: The driver address specified in the NET.CFG file has the group bit set. Note: If no address is specified, the driver will use the default address assigned by the network board's manufacturer.Action: No action is necessary; the bit was cleared by the driver. However, to prevent this error message from being displayed every time the driver is loaded, edit the NET.CFG file and correct the node address override, as is shown in the following example:FORMAT="LINESPECIFIC"MOREINFO="NONE"LINK DRIVER TOKEN 
   NODE ADDRESS address For information about editing the NET.CFG file, see "BOOK="ws_osenu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for OS/2 User Guide.PAGENUM=1196 ID="BP1190"241: Invalid Node Override, Local Administrated bit was set now reset.TOKEN-OS2Explanation: The driver address specified in the NET.CFG file does not have the locally administered bit set. Note: If no address is specified, the driver will use the default address assigned by the network board's manufacturer.Action: No action is necessary; the bit was set by the driver. However, to prevent this error message from being displayed every time the driver is loaded, edit the NET.CFG file and correct the node address override, as is shown in the following example:FORMAT="LINESPECIFIC"MOREINFO="NONE"LINK DRIVER TOKEN 
   NODE ADDRESS address For information about editing the NET.CFG file, see "BOOK="ws_osenu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for OS/2 User Guide.PAGENUM=1197 ID="BP1191"TPING0: The load line is invalid. Example load line: `load tping host [packetsize [retrycount]]'.TPINGExplanation: Some portion of the load line was incorrect. Action: Compare the original load line with the example in the message and correct any mistakes. For information on TPING, see "BOOK="utlrfenu" COLLECTION="nw41"TPING" in Utilities Reference.1: Unable to send number byte packet. Error code: code.TPINGExplanation: The packet could not be sent from the server. The BSD socket "sendto" call failed. Action: This is usually a temporary condition. If the problem persists, contact your Novell Authorized Reseller. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 2: Host name unknown.TPINGExplanation: The indicated host could not be found in the HOSTS file. Action: Correct the hostname or add it to the HOSTS file, then try the load line again.3: The requested packet size is too large. A maximum of number bytes can be sent.TPINGExplanation: The indicated packet size specified on the load line is too large for this network. Action: Reduce the packet size specified on the load line to less than or equal to the given maximum. For information on TPING, see "BOOK="utlrfenu" COLLECTION="nw41"TPING" in Utilities Reference.4: Unable to allocate memory.TPINGExplanation: The server could not allocate enough memory to run TPING. Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. 5: Unable to open ICMP socket. Error code: code.TPINGExplanation: TPING could not establish its interface with the Internet Control Message Protocol (ICMP). The server could not allocate enough memory to run TPING. Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A.PAGENUM=1198 ID="BP1192"6: Receive error was encountered. Error code: code.TPINGExplanation: TPING could not receive a response from the host. This error is usually caused by an error in the BSD socket's "recvfrom" call. Action: This is usually a temporary condition. If the problem persists, contact your Novell Authorized Reseller. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A.7: Unexpected End Of File was received.TPINGExplanation: TPING encountered an End Of File when receiving data from the network.Action: Try the load line again. For information on TPING, see "BOOK="utlrfenu" COLLECTION="nw41"TPING" in Utilities Reference. If the problem persists, contact your Novell Authorized Reseller.8: IP_address|name is alive.TPINGExplanation: This is an informational message indicating that the TPING was successful. The indicated host responded as expected. Action: None. This message is for information only.9: Message table was not found.TPINGExplanation: TPING could not find the message table that it requires to put out informative messages. This usually happens when the server is low on memory. Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.10: IP_address|name does not respond. number packets have been sent, each number bytes long.TPINGExplanation: The specified host did not respond to the packets. Action: Make sure the IP address or name is correct, and try again. For information on TPING, see "BOOK="utlrfenu" COLLECTION="nw41"TPING" in Utilities Reference.PAGENUM=1199 ID="BP1193"TRAN1: The message file name is invalid. The program cannot be loaded.TRANExplanation: The .MSG file is invalid. This problem could be the result of a corrupted file, a bad translation, or an outdated file version.Action: Either update the .MSG file with a valid copy or delete the file. The DOS Requester will use the default messages that are bound to the binary files.5: Module1.VLM is not loaded. The module2.VLM file cannot be loaded before module1.VLM. Load the module1.VLM file first then try to load the module2.VLM file.TRANExplanation: The module2.VLM requires that the module1.VLM be loaded first. Either the current configuration has module1.VLM and module2.VLM loading out of order, or module1.VLM did not load successfully.Action: Make sure that module1.VLM is configured to load before module2.VLM. To do this, change the load order of the "VLM=" parameter in the NET.CFG file.7: In order to load the module3.VLM, one of the following VLMs must be loaded: module1.VLM, module2.VLM.TRANExplanation: The module3.VLM requires that module1.VLM or module2.VLM be first. Either the current configuration has module3.VLM loading before the modules in the module1.VLM or module2.VLM list, or module1.VLM or module2.VLM did not load successfully.Action: Make sure that module1.VLM or module2.VLM loads successfully before attempting to load module3.VLM.42: There is a missing or invalid value for `parameter' on line number of the configuration file. This entry will be ignored. Correct the line specified in the configuration file before continuing.TRANExplanation: The configuration file contains a configuration keyword that has an invalid parameter, or that does not specify a parameter. This invalid line will be ignored by the configuration process.Action: Because this line will be ignored, no action is required now. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message.PAGENUM=1200 ID="BP1194"43: There is a missing or invalid ON/OFF value for `parameter' on line number of the configuration file. This entry will be ignored. Correct the line specified in the configuration file before continuing.TRANExplanation: The configuration file contains a configuration keyword that is defined to use either an "ON" or "OFF" parameter, but a different parameter, or no parameter, has been specified. This invalid line will be ignored by the configuration process.Action: None. This message is for information only. The line will be ignored; however, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message.45: The parameter specified for the following option was out of range and has been adjusted.TRANExplanation: A configurable parameter has been configured too high or too low to be valid. The invalid parameter is specified on the line following the message.Action: Check and correct the parameter specified in the NET.CFG file. For more information about the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.PAGENUM=1201 ID="BP1195"TRXNET-DOS001: The LSL is not loaded.TRXNET-DOSExplanation: You must load the Link Support Layer (LSL) before loading the driver.Action: Load the LSL; then load the driver, as in the following example:FORMAT="LINESPECIFIC"MOREINFO="NONE"C:\NWCLIENT\LSL MOREINFO="NONE"<Enter> 
C:\NWCLIENT\TRXNET MOREINFO="NONE"<Enter> 002: The LSL has no room for a board using frame type.TRXNET-DOSExplanation: The Link Support Layer (LSL) is configured with resources for a set number of network boards. (The default is 4.) This number has been exceeded.Action: Edit the NET.CFG file, and add the MAX BOARDS keyword to reflect the number of network boards to be loaded, as in the following example: FORMAT="LINESPECIFIC"MOREINFO="NONE"LINK SUPPORT 
   MAX BOARDS 6 Unload the driver; then reload it as in the following example:FORMAT="LINESPECIFIC"MOREINFO="NONE"C:\NWCLIENT\TRXNET /u MOREINFO="NONE"<Enter> 
C:\NWCLIENT\TRXNET MOREINFO="NONE"<Enter> 003: Could not find TRXNET MLID to unload.TRXNET-DOSExplanation: The TRXNET driver is not loaded.Action: None. This message is for information only.004: A TSR is loaded above the TRXNET MLID.TRXNET-DOSExplanation: Another TSR (terminate-and-stay-resident) program was loaded after the TRXNET driver.Action: The drivers must be unloaded in reverse order, as follows:FORMAT="LINESPECIFIC"MOREINFO="NONE"C:\NWCLIENT\NETX /u MOREINFO="NONE"<Enter> 
C:\NWCLIENT\IPXODI /u MOREINFO="NONE"<Enter> 
C:\NWCLIENT\TRXNET /u MOREINFO="NONE"<Enter> 
PAGENUM=1202 ID="BP1196"Unload the TSRs; then try to unload the TRXNET driver. If you wish, you can force the TRXNET driver to unload from the command line by using the /F switch after the driver name, as follows:FORMAT="LINESPECIFIC"MOREINFO="NONE"C:\NWCLIENT\TRXNET /f MOREINFO="NONE"<Enter> Use caution when using the /F switch because it could cause the system to hang.005: TRXNET MLID could not be unloaded; the operation was aborted.TRXNET-DOSExplanation: The TRXNET driver could not be shut down and unregistered; consequently, it cannot be unloaded.Action: To unload the driver, reboot the system.006: The adapter did not initialize. TRXNET did not load.TRXNET-DOSExplanation: The TRXNET driver encountered an error while loading.Action: Corrective action can vary. See the preceding driver-specific message on the screen for specific information about the error that occurred.007: You need another MLID section heading in the NET.CFG file in order to load the MLID again. TRXNET-DOSExplanation: The driver cannot be loaded consecutively unless you edit the configuration parameters and add a section heading for each instance in the NET.CFG file.Action: Unload the TRXNET driver. Edit/create the NET.CFG file and add a Link Driver section heading for each time the driver is to be loaded; then reload the driver. For more information about the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.008: A NET.CFG is required to load the MLID again.TRXNET-DOSExplanation: The driver cannot be loaded unless you create a NET.CFG file. A Link Driver section heading must be edited into the NET.CFG file for each time the driver is to be loaded.Action: Unload the TRXNET driver. Edit/create the NET.CFG file and add a Link Driver section heading for each time the driver is to be loaded. For more information about the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.PAGENUM=1203 ID="BP1197"009: The NET.CFG entry has been ignored.TRXNET-DOSExplanation: The driver cannot be loaded consecutively unless you create a NET.CFG file each time.Action: Unload the TRXNET driver. Edit/create the NET.CFG file and add a Link Driver section heading for each time the driver is to be loaded. For more information about the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.011: The MLID does not support frame type. The protocol keyword has been ignored.TRXNET-DOSExplanation: An unsupported or incorrectly typed frame type has been specified with the protocol keyword.Action: Check the contents of the NET.CFG file, and verify the frame type assigned under the PROTOCOL keyword is valid. For more information about the NET.CFG file and PROTOCOL keywords, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.012: The protocol keyword must have a frame type. Entry ignored.TRXNET-DOSExplanation: The PROTOCOL keyword entry is incomplete.Action: Correct the protocol entry in the NET.CFG file. The proper syntax for the protocol keyword is as follows:FORMAT="LINESPECIFIC"MOREINFO="NONE"PROTOCOL TRXNE hex_protocol_ID frame_type For information on PROTOCOL keywords, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.013: The MLID could not register Protocol ID number for protocol stack name for frame type type.TRXNET-DOSExplanation: The Link Support Layer (LSL) is configured with resources for a set number of Protocol Identifiers. (The default is 4.) This number has been exceeded.Action: Edit the NET.CFG file, and add the MAX STACKS keyword to reflect the number of network boards to be loaded, as in the following example:FORMAT="LINESPECIFIC"MOREINFO="NONE"LINK SUPPORT 
   MAX STACKS 6 Unload the driver; then reload it as in the following example:FORMAT="LINESPECIFIC"MOREINFO="NONE"C:\NWCLIENT\TRXNET /u MOREINFO="NONE"<Enter> 
C:\NWCLIENT\LSL /u MOREINFO="NONE"<Enter> 
PAGENUM=1204 ID="BP1198"C:\NWCLIENT\LSL MOREINFO="NONE"<Enter> 
C:\NWCLIENT\TRXNETMOREINFO="NONE" <Enter> 014: This version of the LSL is not supported.TRXNET-DOSExplanation: The driver you are using supports only Link Support Layer (LSL) versions later than 1.0.Action: Unload the LSL and replace it with a newer version.015: The frame type is already active for frame type.TRXNET-DOSExplanation: The frame type is already loaded, and it cannot be loaded repeatedly.Action: Edit the NET.CFG file to load the frame type only once for a given network board. For information on frame types, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.016: The node address was incorrectly specified in the NET.CFG file.TRXNET-DOSExplanation: The node address override in the NET.CFG file is too long.Action: Edit the NET.CFG file and correct the node address. The node address must be less than or equal to 12 hex digits. For information on the node address override, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.017: An invalid keyword was specified in NET.CFG on line number.TRXNET-DOSExplanation: The key word on the line indicated was not recognized.Action: Edit the NET.CFG file and correct the spelling of the keyword. For information on valid keywords, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.018: The frame type specified in the NET.CFG is not supported.TRXNET-DOSExplanation: The frame type specified with the FRAME keyword is not supported by the driver.Action: Edit the NET.CFG file and fix frame type. For information on supported frame types, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.PAGENUM=1205 ID="BP1199"019: An invalid TRXNET node address is specified in NET.CFG. The MLID modified the incorrect address bits.TRXNET-DOSExplanation: The node address specified in the NET.CFG file has set reserved bits.Action: Edit the NET.CFG file and correct the node address. For information on node addresses, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.050: [ISA bus] The board cannot be found.TRXNET-DOSExplanation: If you are using an ISA bus network board, the network board was not found due to one or more of the following conditions: MARK=BULLETThe network board is not present in the machine. The network board settings are not the defaults, and they are not defined in the NET.CFG file.Another network board is using the same hardware settings as this network board.The network board is bad.Action: Do one or more of the following:MARK=BULLETMake sure the network board is properly seated into the slot. If the jumper settings are not the defaults, make sure that they match the settings in the NET.CFG file. If you are not using the NET.CFG file, make sure the jumper settings are set to the defaults. If other network boards are using the same hardware settings, change the settings and try to reload the driver.Replace the bad network board with one that you know is good.050: [Microchannel] The board cannot be found.TRXNET-DOSExplanation: If you are using a microchannel network board, the network board is not in the machine, or the network board's configuration could not be obtained.Action: Do one of the following:MARK=BULLETMake sure the network board is properly seated into a slot.PAGENUM=1206 ID="BP1200"Insert the network board into a slot, and run the CLASS=DISKReference diskette to install it.054: The board did not respond to the initialization command.TRXNET-DOSExplanation: A hardware error has occurred.Action: Power down the system; then reboot it. If the network board still does not respond, replace it with one that you know is good.065: Board cannot be found at slot/IO port. (Please check SLOT and PORT values in the NET.CFG.)TRXNET-DOSExplanation: The network board cannot be found in the slot specified in the NET.CFG file.Action: If you are using an ISA Bus network board, check the slot number and the I/O address in the NET.CFG file. For more information about the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.If you are using a microchannel network board, do one or more of the following:MARK=BULLETCorrect the slot number in the NET.CFG file to match the slot where the network board is physically located. For more information about the NET.CFG file, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.Move the network board to the slot specified in the NET.CFG file; then run the CLASS=DISKReference diskette to install the network board.Note: If no slot is specified in the NET.CFG file, the driver will search all slots for the network board. If more than one network board is in the machine, the slots must be specified in the NET.CFG file.PAGENUM=1207 ID="BP1201"TRXNET-NW025: You cannot load MSM31X on a NetWare 3.10 server.TRXNET-NWExplanation: You attempted to load MSM31X.NLM on a NetWare 3.10 server. MSM31X.NLM will run only on a NetWare 3.11 server.Action: Either load a version of the Media Support Module (MSM) that will run on a NetWare 3.10 server, or upgrade your server to NetWare 3.11. For information on MSM, see "BOOK="cncptenu" COLLECTION="nw41"Media Support Module (MSM)" in Concepts.026: On a NetWare 3.11 server, you must load LSLENH.NLM before you load MSM31X.NLM.TRXNET-NWExplanation: The Link Support Layer (LSL) and Media Support Module (MSM) have been loaded on a NetWare 3.11 server. An attempt was made to load LSLENH.NLM. You cannot load LSLENH.NLM once the MSM has been loaded. (LSLENH.NLM adds enhancement to the LSL.)Action: Unload MSM31X.NLM; then load LSLENH.NLM. Once the LSLENH.NLM has been loaded, load MSM31X.NLM again. For information on LSL and MSM, see "BOOK="cncptenu" COLLECTION="nw41"Link Support Layer (LSL)" and "BOOK="cncptenu" COLLECTION="nw41"Media Support Module (MSM)"in Concepts.050: [ISA bus | Microchannel] The board cannot be found.TRXNET-NWExplanation: If you are using an ISA bus network board, the network board was not found due to one or more of the following conditions: MARK=BULLETThe network board is not present in the machine. The network board settings are not the defaults, and they are not defined in the NET.CFG file.Another network board is using the same hardware settings as this network board.The network board is bad.Action: Do one or more of the following:MARK=BULLETMake sure the network board is properly seated into the slot. If the jumper settings are not the defaults, make sure that they match the settings in the NET.CFG file. PAGENUM=1208 ID="BP1202"If you are not using the NET.CFG file, make sure the jumper settings are set to the defaults. If other network boards are using the same hardware settings, change the settings and try to reload the driver.Replace the bad network board with one that you know is good.Explanation: If you are using a microchannel network board, the network board is not in the machine, or the network board's configuration could not be obtained.Action: Do one of the following:MARK=BULLETMake sure the network board is properly seated into a slot.Insert the network board into a slot, and run the CLASS=DISKReference diskette to install it.058: The board did not respond.TRXNET-NWExplanation: The network board did not respond to a command.Action: Make sure the network board is properly seated and the cabling is secure. You may need to replace the network board with one that you know is good.072: A resource tag is unavailable.TRXNET-NWExplanation: The server may not have enough available memory. NetWare cannot allocate memory for a resource tag.Action: Free up memory by unloading unneeded NLM programs from the server.073: Unable to allocate memory.TRXNET-NWExplanation: The server may not have enough available memory. NetWare cannot allocate memory for the LAN driver.Action: Free up memory by unloading unneeded NLM programs or TSR (terminate-and-stay-resident) programs.079: The MLID did not initialize MSMTxFreeCount.TRXNET-NWExplanation: The .LAN file is either outdated or corrupted.Action: Obtain a new .LAN file.PAGENUM=1209 ID="BP1203"091: The hardware configuration conflicts.TRXNET-NWExplanation: Another hardware resource is being used, which the LAN driver is trying to register.Action: Change the hardware configuration of the network board or of the conflicting device.125: The TSM's version number does not match the version of MSM.NLM.TRXNET-NWExplanation: You are using incompatible versions of RXNET.TSM and MSM.NLM.Action: If you do not have the most recent version of each of these modules, contact your Novell Authorized Reseller. After loading the updated modules, try the operation again.PAGENUM=1210 ID="BP1204"TRXNET-OS2001: The LSL is not loaded.TRXNET-OS2Explanation: The Link Support Layer (LSL) module must be loaded before you can install the driver.Action: Edit the CONFIG.SYS file to load the LSL before the LAN driver, as in the following example:FORMAT="LINESPECIFIC"MOREINFO="NONE"DEVICE=C:\NETWARE\LSL.SYS 
DEVICE=C:\NETWARE\TRXNET.SYS 021: Could not add MLID Protocol ID.TRXNET-OS2Explanation: The Link Support Layer (LSL) is configured with resources for four Protocol Identifiers. This number has been exceeded.Action: None. This message is for information only.022: Could not allocate memory. Virtual board did not load.TRXNET-OS2Explanation: The system cannot allocate enough memory to load another network board.Action: Do one of the following:MARK=BULLETInstall more system memory in the machine.Edit the CONFIG.SYS file, and remove any unneeded drivers.050: [ISA bus | Microchannel] The board cannot be found.TRXNET-OS2Explanation: If you are using an ISA bus network board, the network board was not found due to one or more of the following conditions: MARK=BULLETThe network board is not present in the machine. The network board settings are not the defaults, and they are not defined in the NET.CFG file.Another network board is using the same hardware settings as this network board.The network board is bad.Action: Do one or more of the following:PAGENUM=1211 ID="BP1205"MARK=BULLETMake sure the network board is properly seated into the slot. If the jumper settings are not the defaults, make sure that they match the settings in the NET.CFG file. If you are not using the NET.CFG file, make sure the jumper settings are set to the defaults. If other network boards are using the same hardware settings, change the settings and try to reload the driver.Replace the bad network board with one that you know is good.Explanation: If you are using a microchannel network board, the network board is not in the machine, or the network board's configuration could not be obtained.Action: Do one of the following:MARK=BULLETMake sure the network board is properly seated into a slot.Insert the network board into a slot, and run the CLASS=DISKReference diskette to install it.054: The board did not respond to the initialization command.TRXNET-OS2Explanation: The network board may be bad.Action: Try rebooting the machine. If the message appears again, replace the network board with one that you know is good.056: This interrupt is already used and cannot be shared.TRXNET-OS2Explanation: The selected interrupt is being used by another device, so it cannot be used for this network board.Action: If you are using a microchannel network board, run the CLASS=DISKReference diskette that came with the computer, and change the jumper setting on the network board to use a different interrupt. See the EXOS hardware manual for information on jumper settings. Edit the NET.CFG file to reflect the correct interrupt level used by the network board. For information on the NET.CFG file, see "BOOK="ws_osenu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for OS/2 User Guide.If you are using an ISA Bus network board, change the jumper setting to specify a different interrupt; then edit the NET.CFG file to reflect the correct interrupt level used by the network board.PAGENUM=1212 ID="BP1206"061: The NET.CFG file contains an invalid IRQ selection.TRXNET-OS2Explanation: An interrupt setting is incorrect.Action: Change your interrupt setting in the NET.CFG file. For information on the NET.CFG file, see "BOOK="ws_osenu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for OS/2 User Guide.062: The NET.CFG file contains invalid port selection.TRXNET-OS2Explanation: The port address setting is incorrect.Action: Change your port address setting in the NET.CFG file. For information on the NET.CFG file, see "BOOK="ws_osenu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for OS/2 User Guide.063: The NET.CFG file contains an invalid shared RAM segment entry.TRXNET-OS2Explanation: This is a memory error.Action: Change your memory setting in the NET.CFG file. For information on the NET.CFG file, see "BOOK="ws_osenu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for OS/2 User Guide.PAGENUM=1213 ID="BP1207"TSA4001: The bindery cannot be opened. Error code: code. TSA400Explanation: After backup or restore, the bindery must be opened; however, it cannot be opened.Action: Make sure the user has Supervisor or equivalent user access rights. Make sure the correct volume is in use. Make sure volume SYS: is mounted. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 2: The bindery cannot be closed. Error code: code.TSA400Explanation: Before backup or restore, the bindery must be closed; however, it cannot be closed.Action: Make sure the user has Supervisor or equivalent user access rights. Make sure the correct volume is in use. Make sure volume SYS: is mounted. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 3: The bindery cannot be closed because you are not a Supervisor.TSA400Explanation: Before backup or restore, the bindery must be closed; however, it cannot be closed.Action: Make sure the user has Supervisor or equivalent user access rights.10: The data stream format for name is incorrect. Error code: code.TSA400Explanation: The media cannot be read. This could be a problem with your backup device.Action: Make sure the backup device is functioning properly. If it is, make sure that your media is SMS-compatible. Try again. If the problem persists, contact your Novell Authorized Reseller. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 41: An internal error has occurred. The program cannot push directory name.TSA400Explanation: The program could not add the directory to a list.Action: Increase the available memory. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. Verify the number of open files and directories. Make sure the user has appropriate user access rights.PAGENUM=1214 ID="BP1208"42: This program cannot get the name space entry name for data_set_name in the type name space.TSA400Explanation: The program could not find the file or directory name in the requested name space.Action: Make sure the indicated name space type is valid and that it is supported on the target volume. Make sure the data set name is valid for the specified name space. Make sure the name space support NLM programs are loaded.43: Error code getting name space specific information size for data_set_name in the name_space name space.TSA400Explanation: The program could not read the name-space-specific information for the file or directory.Action: Make sure the indicated name space type is valid and supported on the target volume. Make sure the data set name is valid for the specified name space. Make sure the name space support NLM programs are loaded. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 45: Error code occurred during the program's attempt to get the entry index for data_set. TSA400Explanation: The program could not get the file system entry index for the requested file or directory.Action: Make sure the indicated name space type is valid and supported on the target volume. Make sure the data set name is valid for the specified name space. Make sure the name space support NLM programs are loaded. Make sure the user has appropriate user access rights. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 46: Error code occurred when the program attempted to read extended attributes for data_set.TSA400Explanation: The program could not read the extended attributes for the requested file or directory.Action: Make sure the indicated name space type is valid and supported on the target volume. Make sure the data set name is valid for the specified name space. Make sure that name space support NLM programs are loaded. Make sure the user has appropriate user access rights. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. PAGENUM=1215 ID="BP1209"47: The original access date for file name cannot be reset. The access date will be changed to today's date.TSA400Explanation: TSA400 could not reset the access date for the file or directory. The file system will show the current time as the last access time.Action: None. This message is for information only. However, this error will affect future file system searches based on access date.48: Invalid data (an unexpected bindery trailer) was found.TSA400Explanation: TSA400 received an unexpected data object (a bindery trailer) from the SMS engine. This object was either out of sequence or was redundant. This error is probably due to a malfunctioning media or storage device.Action: Make sure the media and storage devices are operating properly.49: This program cannot create directory name. Error code: code.TSA400Explanation: TSA400 cannot create the requested directory.Action: Make sure a valid path (including volume name) is specified. Make sure the user has appropriate user access rights. Make sure the volume has enough disk space. If the problem persists, contact your Novell Authorized Reseller. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 51: Invalid data (no data stream trailer) was found for data_stream_name.TSA400Explanation: TSA400 received an unexpected data sequence from the SMS engine (a missing data stream trailer). End of data stream is assumed. This error is probably due to a malfunctioning media or storage device.Action: Make sure the media and storage devices are operating properly.52: Invalid data (an unexpected directory trailer) was found.TSA400Explanation: TSA400 received an unexpected data object (a bindery trailer) from the SMS engine. This object was either out of sequence or was redundant. This error is probably due to a malfunctioning media or storage device.Action: Make sure the media and storage devices are operating properly.53: This program cannot allocate a directory handle for directory_name.TSA400Explanation: The program could not allocate a directory handle to the requested directory.PAGENUM=1216 ID="BP1210"Action: Make sure the directory name is valid for the specified name space. Make sure a valid path (including volume name) is specified. Make sure the user has appropriate user access rights. Increase the available memory. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.54: File name was restored but could not be closed. Error code code was returned. The file may be corrupted.TSA400Explanation: The open file could not be closed. (The error code may give more specific information.) Because the file could not be closed, it may not be complete on the disk.Action: Verify the file contents. Make sure the user has appropriate user access rights. Make sure the file is not in exclusive use by another process. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 55: File name cannot be created. Error code: code.TSA400Explanation: The requested file cannot be created.Action: Make sure the filename is valid for the requested name space. Make sure the user has appropriate user access rights. Verify the number of currently open files. Make sure a valid path (including volume name) is specified. Make sure the volume has enough disk space. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 56: File name cannot be replaced.TSA400Explanation: The specified file exists but could not be opened for overwrite.Action: Make sure the user has appropriate user access rights. Make sure the file is not in exclusive use by another process.57: Invalid data (an unexpected file trailer) was found.TSA400Explanation: The program received a file trailer record before the complete file had been received. The file may be truncated or corrupted.Action: Verify the file's contents. Check the backup log for an error on this file. Make sure the media and storage devices are operating properly.58: This program cannot write file name. Error code: code.TSA400Explanation: An error occurred when the program attempted to write the file. Action: Make sure the user has appropriate user access rights. Make sure the volume has not been dismounted. Make sure the file is not in exclusive use by another process. If the problem persists, contact your Novell Authorized Reseller. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. PAGENUM=1217 ID="BP1211"59: An internal error has occurred. This program cannot get the field for field_name. Error code: code.TSA400Explanation: TSA400 encountered an error while attempting to read the next data field to process.Action: Contact your Novell Authorized Reseller. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 60: Trustee name cannot be added to file/directory_name. Error code: code.TSA400Explanation: The requested Trustee cannot be added to the specified file or directory.Action: If this is the case, do the following:MARK=BULLETMake sure the Trustee name is a valid Directory object. Make sure the file exists and the filename is valid for the specified name space type.Make sure the file or directory exists and is valid in the specified name space.Make sure the user has appropriate user access rights.For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 61: File name may be corrupted. An invalid CRC was received.TSA400Explanation: The cycle redundancy check (CRC) calculated on the file data does not match the CRC value calculated at the time of backup and stored on the media. The file may be corrupted, or the media or storage device may be malfunctioning.Action: Make sure the file contents are not corrupted. Make sure the media and storage devices are operating properly.62: Corrupted data was found after data_set_name.TSA400Explanation: The program still has data for the file or directory after a valid trailer record was processed because the file did not restore well.Action: Try restoring the file again. If the error continues, the data set may be corrupted. Make sure the media and storage devices are operating properly.63: The data set type is invalid.TSA400Explanation: TSA400 received an unknown data set type identifier. This data set will not be processed.Action: Make sure the media and storage devices are operating properly.PAGENUM=1218 ID="BP1212"64: An invalid data marker was found. File name may be corrupted.TSA400Explanation: An invalid data stream was found following a valid data stream trailer record.Action: Verify the contents of the file or directory. Make sure the media and storage devices are operating properly.65: The extended attributes format for data_set_name is invalid. Error code: code.TSA400Explanation: The extended attribute format for the file or directory is in an invalid sequence. The extended attributes may not be correct.Action: Verify the extended attributes for the data set. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 66: An invalid path data_set_path was specified. A full path is required.TSA400Explanation: The data set path could not be located or was incomplete. Action: Make sure the data set path is valid for the specified name space type. A full path requires a path from the server volume.67: An invalid path was specified. The volume does not exist: name.TSA400Explanation: The specified path contains a nonexistent volume.Action: Make sure the volume name is correct and that it includes a colon after the volume name. Make sure the user has appropriate user access rights..68: The program cannot set directory characteristics for directory_name.TSA400Explanation: The program could not set the directory attributes for the directory.Action:  Make sure the user has appropriate user access rights. Make sure the directory attributes are valid. Make sure to use a valid directory name for a directory that exists.69: The program cannot set file characteristics for filename. Error code: code.TSA400Explanation: The program cannot set the requested file attributes on the specified file.Action: Make sure the file attributes requested are valid and the file exists. Make sure the user has appropriate user access rights. Make sure the filename is valid for the specified name space type. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. PAGENUM=1219 ID="BP1213"70: The Macintosh name space is not supported. This information will not be restored.TSA400Explanation: The Macintosh name space is not supported on the target volume, so Macintosh-specific information will not be restored.Action: If Macintosh information is desired, do one of the following:MARK=BULLETStop the restore, enable Macintosh support for the target volume, and load Macintosh name space support modules.Restore to a volume in which Macintosh name space is supported.71: Beginning and ending FIDs for data_set_name do not match.TSA400Explanation: The closing FID for the file or directory does not match the opening FID. The data set may be corrupted.Action: Check your hardware devices and retry the data set. If the same errors occurs, the data is probably unrecognizable.72: Invalid data (an unexpected volume trailer) was found.TSA400Explanation: TSA400 read a volume trailer record before the end of the current data set. The current data set may be corrupted.Action: Check your hardware devices and retry the data set. If the same errors occurs, the data is probably unrecognizable.73: User name (ID number) cannot be added to volume name. Error code: code.TSA400Explanation: The requested user cannot be added as a user because of space restrictions on the volume.Action: Make sure the volume exists and the user has proper user access rights. Make sure the user is a valid Directory object. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 74: An internal error has occurred. Some trustees may not be restored for data_set_name.TSA400Explanation: Trustee information expected next in the data stream was not found.Action: Make sure the correct trustees were restored for the data set. If not, correct the trustee list as necessary.PAGENUM=1220 ID="BP1214"75: Trustee name was not restored for data_set_name, because the trustee IDs are different.TSA400Explanation: This error may happen when the same username exists on two different servers or when the users have different directory IDs. Action: At the end of the restore session, set the appropriate trustee information using NETADMIN, NWADMIN, or FILER.76: The volume restrictions data set format for data_set_name is invalid. Error code: code.TSA400Explanation: TSA400 found the volume restrictions name and the ID to be out of sequence in the data stream. Processing will continue.Action: At the end of the restore session, verify the volume restrictions are correct. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 77: The trustee data set format for object_name is invalid. Error code: code.TSA400Explanation: TSA400 found the trustee name and the ID to be out of sequence in the data stream. Processing will continue.Action: At the end of the restore session, verify the trustee information is correct. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 78: An internal error has occurred. Volume restrictions cannot be found for data_set_name.TSA400Explanation: TSA400 expected Volume Restrictions to be next in the data stream, but did not find them. Processing will continue.Action: At the end of the restore session, verify the volume restrictions are correct. Make sure that you are using a valid volume name and that you have proper access rights.79: The extended attributes for file name were not restored. Error code: code.TSA400Explanation: The extended attributes were not restored.Action: For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 80: Invalid data stream name name was found for file name.TSA400Explanation: An unknown or unsupported data stream (file or directory) header name was found. This data stream will not be restored.Action: Make sure the file has been restored correctly and the correct number of data streams was restored.PAGENUM=1221 ID="BP1215"81: Data set data_set_name may be corrupted. An invalid CRC was received.TSA400Explanation: The cycle redundancy check (CRC) in the data stream is invalid; the data may not be valid.Action: Try again. If the error continues, check the file or directory for internal errors.88: The NFS name space is not supported. This information will not be restored.TSA400Explanation: This file or directory contains information specific to NFS that will not be restored.Action: If NFS information is required, restore to a volume with NFS support or load NFS support on the selected volume. If the NFS information is not needed, continue the restore session.89: The full paths data set format is invalid. Error code: code.TSA400Explanation: An invalid full path was detected by TSA400.Action: Make sure the full path is specified; it must contain volume, directory, filename, and file separators for the specified name space. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 90: The type name space is not supported.TSA400Explanation: The specified name space type is invalid, or not supported on this volume.Action: Specify a valid name space type. If necessary, load name space support for the specified volume.91: Error code occurred while the program attempted to set the type name space name for data_set_name.TSA400Explanation: TSA400 could not set the name space name for the indicated name space type.Action: Make sure the name space name and name space type are valid. If the problem persists, contact your Novell Authorized Reseller. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. PAGENUM=1222 ID="BP1216"92: Error code occurred while the program was scanning for extended attributes for data_set_name.TSA400Explanation: An error occurred when the program attempted to read the extended attributes (EA) for the indicated file or directory. The extended attributes will not be backed up for this data set.Action: Make sure that you are using a valid data set name. Make sure the user has appropriate user access rights. Make sure the extended attributes are not corrupted. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 93: A buffer underflow occurred during the program's attempt to get the extended attribute value for data_set_name. Error code: code.TSA400Explanation: TSA400 received an end-of-data error before the correct number of bytes was read.Action: Make sure the extended attributes and the data set's data are not corrupted. If the problem persists, contact your Novell Authorized Reseller. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 94: Error code occurred while the program attempted to scan information that is specific to the name_space_name name space of data_set_name.TSA400Explanation: The name-space-specific information for the indicated data set cannot be read.Action: Make sure the specified name space support modules are loaded and volume support for the name space is enabled. Make sure you are using a valid data set name. Make sure the user has appropriate user access rights. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 95: An NFS hard link collision occurred while restoring data_set_name. The hard links cannot be restored.TSA400Explanation: NFS hard links for the file or directory conflict with existing hard links. The restore session cannot be completed.Action: Exit and try the operation again.96: An error occurred while the program attempted to restore name-space-specific information for data_set_name in the data_set_name name space. Error code: code.TSA400Explanation: Name space information for the file or directory cannot be restored.Action: Make sure the specified name space type is supported on the target volume. Make sure the user has appropriate user access rights. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. PAGENUM=1223 ID="BP1217"108: Directory entry information for data_set_name cannot be scanned.TSA400Explanation: The program could not scan the directory for the indicated data set.Action: Make sure a valid path (including volume name) is specified. Make sure the user has appropriate user access rights.109: An internal error has occurred: buffer state problem number number.TSA400Explanation: An internal error has occurred in the data buffer. Processing will continue; however, the data may be corrupted.Action: Repeat the session to make sure the data is not corrupted.110: This program cannot delete existing extended attributes for data_set_name. Error code: code.TSA400Explanation: The program cannot delete the extended attributes for the indicated data set.Action: Make sure the user has appropriate user access rights. Make sure the file is not in exclusive use by another process. After the restore session, check the integrity of the extended attributes and correct or change them if necessary. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 111: The TSA and responder versions are incompatible.TSA400Explanation: The SMS modules are from incompatible versions.Action: Replace SMS modules as necessary to obtain compatible versions.256: Access has been denied. An invalid username or authentication was used.TSA400Explanation: An invalid authentication has occurred.Action: Try again. Make sure the username and password are correct.257: This program cannot get the Directory object name.TSA400Explanation: The name specified is not a valid or known name.Action: Verify the name; then try again.258: This program has encountered a buffer underflow and cannot get the entire field.TSA400Explanation: TSA400 received an end-of-data error before the correct number of bytes were read. The data may be corrupted.Action: Make sure the data is correct. Repeat the session if necessary.PAGENUM=1224 ID="BP1218"259: This program cannot allocate a directory handle.TSA400Explanation: The program could not allocate a directory handle.Action: Make sure you have specified a valid directory path for the desired name space. Make sure the user has appropriate user access rights.260: The bindery cannot be closed.TSA400Explanation: The bindery cannot be closed.Action: Make sure that you have Supervisor rights to the server. Make sure the bindery is not being used.261: This program cannot create a directory entry.TSA400Explanation: The program could not create the specified directory entry.Action: Make sure that you have specified a valid directory path for the name space. Make sure the user has appropriate user access rights.262: This program cannot create a file.TSA400Explanation: The program could not create the specified file.Action: Make sure that you have specified a valid directory path for the name space. Make sure the user has appropriate user access rights.263: This data set name is already in use.TSA400Explanation: TSA400 cannot overwrite the existing data set because the data set is being used.Action: Change the SBACKUP selection to "Overwrite parent/child," or change the destination path.264: The data set was excluded by the selection list.TSA400Explanation: The specified file or directory was excluded by the selection criteria.Action: Change the selection criteria in SBACKUP.270: This program cannot delete a data set.TSA400Explanation: The specified data set could not be deleted.Action: Make sure a valid data set name was specified. Make sure the user has appropriate user access rights. Make sure the file is not in exclusive use by another process.PAGENUM=1225 ID="BP1219"272: The program was processing a record or subrecord and did not find the Trailer field.TSA400Explanation: Your data has been corrupted; the trailer field of a record is missing.Action: Clean the tape heads and check the hardware; then try again. If the problem persists, contact your Novell Authorized Reseller.273: This program cannot get the Directory object name.TSA400Explanation: The specified object was not found in the bindery.Action: Make sure a valid bindery object was specified. Make sure the user has appropriate user access rights.274: This program cannot get the data stream name.TSA400Explanation: The program could not read the requested data stream name.Action: Make sure a valid data set name for the name space was specified. Make sure name space is supported on the volume. Make sure the user has appropriate user access rights.275: This program cannot get the entry index.TSA400Explanation: The program could not get an entry index for the requested file or directory.Action: Make sure a valid data set name for the name space was specified. Make sure name space is supported on the volume. Make sure the user has appropriate user access rights.276: This program cannot get the name space entry name.TSA400Explanation: The program could not read the name space entry name for the requested file or directory.Action: Make sure a valid data set name for the name space was specified. Make sure name space is supported on the volume. Make sure the user has appropriate user access rights.277: This program cannot get the name space size information.TSA400Explanation: The program could not read the name space information size.Action: Make a valid data set name for the name space was specified. Make sure name space is supported on the volume. 278: This program cannot get the NetWare server information.TSA400Explanation: TSA400 could not read the server information.Action: Make sure the server's NetWare operating system version matches the TSA400 version in use.PAGENUM=1226 ID="BP1220"279: This program cannot get the volume-supported name space information.TSA400Explanation: The program could not read the list of supported name spaces for the requested volume.Action: Make sure a valid volume name was specified. Make sure the volume is mounted. Make sure the user has appropriate user access rights.280: An invalid connection handle was passed.TSA400Explanation: Your connection may no longer be valid.Action: Make sure the workstation is connected to the network.282: The data set handle is invalid.TSA400Explanation: The data set may not exist.Action: Verify the data set exists.283: The data set name is invalid.TSA400Explanation: An invalid file or directory name was specified.Action: Specify a valid data set name for the specified name space.284: An invalid data stream was found for data_set_name, data set type type.TSA400Explanation: The data stream specified is invalid for the indicated data set and type.Action: Specify a valid data stream type. Make sure the requested name space is supported on this volume.285: The handle tag is invalid or the pointer is null.TSA400Explanation: This handle is not valid.Action: None. This message is for information only.286: Message number is invalid.TSA400Explanation: An invalid message number was detected.Action: None. This message is for information only.287: The name space type does not exist or is invalid.TSA400Explanation: An invalid name space type was specified.Action: Specify a valid name space type, and make sure support for the specified name space type is loaded on the specified volume.PAGENUM=1227 ID="BP1221"288: The object ID or name that was backed up does not match the current object ID or name.TSA400Explanation: The object ID or name for the restore does not match the object ID or name for the backup. Restore is probably being performed on a different server than the server that was used for the backup. This results in an object on both servers with a different ID.Action: None. This message is for information only.289: The Open mode option is out of range (less than 0 or greater than 23).TSA400Explanation: An invalid open mode option was specified.Action: Specify a range within allowable parameters.290: One or more of the parameters is null or invalid.TSA400Explanation: Invalid parameters were specified.Action: Replace any null or invalid parameters.291: An invalid path was used.TSA400Explanation: The path is invalid for the specified name space.Action: Make sure the path is valid for the specified name space. Make sure the user has appropriate user access rights.292: The scan type is out of range (less than 0 or greater than 31).TSA400Explanation: An invalid scan type was specified.Action: Correct the scan type and try again.294: The selection type is out of range (less than 0 or greater than 31).TSA400Explanation: An invalid selection type was specified.Action: Correct the selection type and try again.295: The sequence number is invalid.TSA400Explanation: An invalid sequence number was specified.Action: Correct the sequence number and try again.PAGENUM=1228 ID="BP1222"296: This login attempt has been denied.TSA400Explanation: The login attempt failed.Action: Make sure a valid username and password for the selected server is specified; then try again.297: This logout attempt cannot be completed.TSA400Explanation: The logout attempt failed.Action: Make sure no work is in progress; then try again.298: The name space path has not been updated.TSA400Explanation: A valid path was not found in the path list for the selected name space.Action: Make sure a valid DOS path exists; then try again.300: The connection is invalid or does not exist.TSA400Explanation: The old connection is invalid or no connection has been established.Action: Reestablish the connection and proceed.303: Either no more entries are in the list or the name space type does not exist.TSA400Action: None. This message is for information only.304: You do not have the Search right on client service.TSA400Explanation: TSA400 could not scan the client file system because of a rights violation.Action: Try one or more of the following:MARK=BULLETChange to another server or volume where you have the Search right.Log in as another user who does have the Search right.Grant the user appropriate access rights.305: No such property exists.TSA400Explanation: An invalid property was specified.Action: Make sure the property you want is valid; then try again.PAGENUM=1229 ID="BP1223"306: A data stream cannot be opened.TSA400Explanation: The program cannot open the specified data stream.Action: Make sure that you are using a valid data stream name and the data stream exists. Make sure the user has appropriate user access rights.307: A file cannot be opened.TSA400Explanation: The program cannot open the specified file.Action: Make sure that you are using a valid filename and the file exists. Make sure the user has appropriate user access rights.308: The Open option is not used.TSA400Explanation: The Open option mode type string is not being used.Action: None. This message is for information only. However, you may want to add the mode type string (for example, NO_DATA_STREAMS_STR).309: A file or directory cannot be restored. You are out of disk space.TSA400Explanation: Restore cannot continue until you add more disk space.Action: Do one or both of the following:MARK=BULLETRestore to another volume with sufficient space.Increase the available disk space on the volume. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Disk Space Problems" in Supervising the Network.310: Either the server is out of memory or memory allocation failed.TSA400Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.311: A UINT64 value has overflowed.TSA400Explanation: A number overflow has occurred. The number is too large for the UINT64 type variable. This error is probably caused by invalid or corrupted data.Action: Contact your Novell Authorized Reseller.312: The extended attributes cannot be read.TSA400Explanation: The extended attributes for a file cannot be read.Action: Make sure a valid file is specified. Make sure the user has appropriate user access rights.PAGENUM=1230 ID="BP1224"313: A file cannot be read.TSA400Explanation: The file may be corrupted.Action: Try the operation again. If the problem persists, contact your Novell Authorized Reseller.314: Either no resource name can be found or all resource names have been found.TSA400Explanation: The Scan Target Service Resource function has found all resources, or no resources were found.Action: If you are expecting a resource list, make sure the data set sequence is correct. Then try again.315: The program's attempt to scan failed, probably because an invalid path was specified.TSA400Explanation: An invalid path was specified.Action: Specify a valid path for the requested name space. Make sure the user has appropriate user access rights.316: The program cannot scan file entry information.TSA400Explanation: File scan failed.Action: Specify a valid filename for the requested name space. Make sure the user has appropriate user access rights.318: Information applicable to a specific name space cannot be scanned.TSA400Action: Make sure that you have specified a valid name space and that name space support is loaded on the selected volume.319: The program cannot scan for trustees.TSA400Explanation: TSA400 could not scan for a trustee list.Action: Make sure the user has appropriate user access rights. Make sure the entry index is valid; then try again.320: This scan type is not used.TSA400Explanation: An invalid or unused scan type was specified.Action: Specify a valid scan type and try again.PAGENUM=1231 ID="BP1225"321: This selection type is not used.TSA400Explanation: An invalid or unused selection type was specified.Action: Specify a valid scan type and try again.322: The program cannot set file information.TSA400Explanation: The program cannot set file information.Action: Make sure the user has appropriate user access rights. Make sure the information to be set is valid.323: The transport mechanism has failed.TSA400Explanation: The intermodule communication layer has failed.Action: Reestablish the LAN communication between machines. 324: The read/write request exceeds 128 KB.TSA400Explanation: An intermodule communication request exceeds the 128 KB limit.Action: Restructure the read/write request into pieces of 128 KB or smaller.325: An invalid or inactive TSA was specified.TSA400Explanation: A TSA (Target Service Agent) was specified that cannot be found.Action: Make sure the TSA you want is valid and active. If it is not loaded, load it and try again.326: The requested function is not supported by this TSA.TSA400Explanation: The requested function is not supported on the selected TSA (Target Service Agent).Action: Request a valid function, or select another TSA that supports the requested function.328: The program cannot write extended attribute (value).TSA400Explanation: The program could not write the extended attribute(s).Action: Make sure the extended attribute(s) is valid and the file or directory is valid. Make sure sufficient extended attribute space is on the volume. Make sure the user has appropriate user access rights.PAGENUM=1232 ID="BP1226"329: An error occurred while the program attempted to write to a file. The full request could not be written.TSA400Explanation: You may not have enough disk space, or the file may be corrupted.Action: Do one or more of the following:MARK=BULLETCheck the contents of the file; it may be corrupted.Increase the available disk space on the volume. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Disk Space Problems" in Supervising the Network.330: An error occurred while the program attempted to write to a file. TSA400Explanation: You may not have enough disk space, or the file may be corrupted.Action: Do one or more of the following:MARK=BULLETCheck the contents of the file; it may be corrupted.Increase the available disk space on the volume. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Disk Space Problems" in Supervising the Network.PAGENUM=1233 ID="BP1227"TSADOS1: The bindery cannot be opened. Error code: code. TSADOSExplanation: After backup or restore, the bindery must be opened; however, it cannot be opened.Action: Make sure the user has Supervisor or equivalent user access rights. Make sure the correct volume is in use. Make sure volume SYS: is mounted. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 2: The bindery cannot be closed. Error code: code.TSADOSExplanation: Before backup or restore, the bindery must be closed; however, it cannot be closed.Action: Make sure the user has Supervisor or equivalent user access rights. Make sure the correct volume is in use. Make sure volume SYS: is mounted. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 3: The bindery cannot be closed because you are not a Supervisor.TSADOSExplanation: Before backup or restore, the bindery must be closed; however, it cannot be closed.Action: Make sure the user has Supervisor or equivalent user access rights.10: The data stream format for name is incorrect. Error code: code.TSADOSExplanation: The media cannot be read. This could be a problem with your backup device.Action: Make sure the backup device is functioning properly. If it is, make sure that your media is SMS-compatible. Try again. If the problem persists, contact your Novell Authorized Reseller. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 41: An internal error has occurred. The program cannot push directory name.TSADOSExplanation: The program could not add the directory to a list.Action: Increase the available memory. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. Verify the number of open files and directories. Make sure the user has appropriate user access rights.PAGENUM=1234 ID="BP1228"42: This program cannot get the name space entry name for data_set_name in the type name space.TSADOSExplanation: The program could not find the file or directory name in the requested name space.Action: Make sure the indicated name space type is valid and that it is supported on the target volume. Make sure the data set name is valid for the specified name space. Make sure the name space support NLM programs are loaded.43: Error code getting name space specific information size for data_set_name in the name_space name space.TSADOSExplanation: The program could not read the name-space-specific information for the file or directory.Action: Make sure the indicated name space type is valid and supported on the target volume. Make sure the data set name is valid for the specified name space. Make sure the name space support NLM programs are loaded. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 45: Error code occurred during the program's attempt to get the entry index for data_set. TSADOSExplanation: The program could not get the file system entry index for the requested file or directory.Action: Make sure the indicated name space type is valid and supported on the target volume. Make sure the data set name is valid for the specified name space. Make sure the name space support NLM programs are loaded. Make sure the user has appropriate user access rights. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 46: Error code occurred when the program attempted to read extended attributes for data_set.TSADOSExplanation: The program could not read the extended attributes for the requested file or directory.Action: Make sure the indicated name space type is valid and supported on the target volume. Make sure the data set name is valid for the specified name space. Make sure that name space support NLM programs are loaded. Make sure the user has appropriate user access rights. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. PAGENUM=1235 ID="BP1229"47: The original access date for file name cannot be reset. The access date will be changed to today's date.TSADOSExplanation: TSADOS could not reset the access date for the file or directory. The file system will show the current time as the last access time.Action: None. This message is for information only. However, this error will affect future file system searches based on access date.48: Invalid data (an unexpected bindery trailer) was found.TSADOSExplanation: TSADOS received an unexpected data object (a bindery trailer) from the SMS engine. This object was either out of sequence or was redundant. This error is probably due to a malfunctioning media or storage device.Action: Make sure the media and storage devices are operating properly.49: This program cannot create directory name. Error code: code.TSADOSExplanation: TSADOS cannot create the requested directory.Action: Make sure a valid path (including volume name) is specified. Make sure the user has appropriate user access rights. Make sure the volume has enough disk space. If the problem persists, contact your Novell Authorized Reseller. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 51: Invalid data (no data stream trailer) was found for data_stream_name.TSADOSExplanation: TSADOS received an unexpected data sequence from the SMS engine (a missing data stream trailer). End of data stream is assumed. This error is probably due to a malfunctioning media or storage device.Action: Make sure the media and storage devices are operating properly.52: Invalid data (an unexpected directory trailer) was found.TSADOSExplanation: TSADOS received an unexpected data object (a bindery trailer) from the SMS engine. This object was either out of sequence or was redundant. This error is probably due to a malfunctioning media or storage device.Action: Make sure the media and storage devices are operating properly.53: This program cannot allocate a directory handle for directory_name.TSADOSExplanation: The program could not allocate a directory handle to the requested directory.PAGENUM=1236 ID="BP1230"Action: Make sure the directory name is valid for the specified name space. Make sure a valid path (including volume name) is specified. Make sure the user has appropriate user access rights. Increase the available memory. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.54: File name was restored but could not be closed. Error code code was returned. The file may be corrupted.TSADOSExplanation: The open file could not be closed. (The error code may give more specific information.) Because the file could not be closed, it may not be complete on the disk.Action: Verify the file contents. Make sure the user has appropriate user access rights. Make sure the file is not in exclusive use by another process. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 55: File name cannot be created. Error code: code.TSADOSExplanation: The requested file cannot be created.Action: Make sure the filename is valid for the requested name space. Make sure the user has appropriate user access rights. Verify the number of currently open files. Make sure a valid path (including volume name) is specified. Make sure the volume has enough disk space. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 56: File name cannot be replaced.TSADOSExplanation: The specified file exists but could not be opened for overwrite.Action: Make sure the user has appropriate user access rights. Make sure the file is not in exclusive use by another process.57: Invalid data (an unexpected file trailer) was found.TSADOSExplanation: The program received a file trailer record before the complete file had been received. The file may be truncated or corrupted.Action: Verify the file's contents. Check the backup log for an error on this file. Make sure the media and storage devices are operating properly.58: This program cannot write file name. Error code: code.TSADOSExplanation: An error occurred when the program attempted to write the file. Action: Make sure the user has appropriate user access rights. Make sure the volume has not been dismounted. Make sure the file is not in exclusive use by another process. If the problem persists, contact your Novell Authorized Reseller. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. PAGENUM=1237 ID="BP1231"59: An internal error has occurred. This program cannot get the field for field_name. Error code: code.TSADOSExplanation: TSADOS encountered an error while attempting to read the next data field to process.Action: Contact your Novell Authorized Reseller. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 60: Trustee name cannot be added to file/directory_name. Error code: code.TSADOSExplanation: The requested Trustee cannot be added to the specified file or directory.Action: If this is the case, do the following:MARK=BULLETMake sure the Trustee name is a valid Directory object. Make sure the file exists and the filename is valid for the specified name space type.Make sure the file or directory exists and is valid in the specified name space.Make sure the user has appropriate user access rights.For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 61: File name may be corrupted. An invalid CRC was received.TSADOSExplanation: The cycle redundancy check (CRC) calculated on the file data does not match the CRC value calculated at the time of backup and stored on the media. The file may be corrupted, or the media or storage device may be malfunctioning.Action: Make sure the file contents are not corrupted. Make sure the media and storage devices are operating properly.62: Corrupted data was found after data_set_name.TSADOSExplanation: The program still has data for the file or directory after a valid trailer record was processed because the file did not restore well.Action: Try restoring the file again. If the error continues, the data set may be corrupted. Make sure the media and storage devices are operating properly.63: The data set type is invalid.TSADOSExplanation: TSADOS received an unknown data set type identifier. This data set will not be processed.Action: Make sure the media and storage devices are operating properly.PAGENUM=1238 ID="BP1232"64: An invalid data marker was found. File name may be corrupted.TSADOSExplanation: An invalid data stream was found following a valid data stream trailer record.Action: Verify the contents of the file or directory. Make sure the media and storage devices are operating properly.65: The extended attributes format for data_set_name is invalid. Error code: code.TSADOSExplanation: The extended attribute format for the file or directory is in an invalid sequence. The extended attributes may not be correct.Action: Verify the extended attributes for the data set. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 66: An invalid path data_set_path was specified. A full path is required.TSADOSExplanation: The data set path could not be located or was incomplete. Action: Make sure the data set path is valid for the specified name space type. A full path requires a path from the server volume.67: An invalid path was specified. The volume does not exist: name.TSADOSExplanation: The specified path contains a nonexistent volume.Action: Make sure the volume name is correct and that it includes a colon after the volume name. Make sure the user has appropriate user access rights..68: The program cannot set directory characteristics for directory_name.TSADOSExplanation: The program could not set the directory attributes for the directory.Action:  Make sure the user has appropriate user access rights. Make sure the directory attributes are valid. Make sure to use a valid directory name for a directory that exists.69: The program cannot set file characteristics for filename. Error code: code.TSADOSExplanation: The program cannot set the requested file attributes on the specified file.Action: Make sure the file attributes requested are valid and the file exists. Make sure the user has appropriate user access rights. Make sure the filename is valid for the specified name space type. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. PAGENUM=1239 ID="BP1233"70: The Macintosh name space is not supported. This information will not be restored.TSADOSExplanation: The Macintosh name space is not supported on the target volume, so Macintosh-specific information will not be restored.Action: If Macintosh information is desired, do one of the following:MARK=BULLETStop the restore, enable Macintosh support for the target volume, and load Macintosh name space support modules.Restore to a volume in which Macintosh name space is supported.71: Beginning and ending FIDs for data_set_name do not match.TSADOSExplanation: The closing FID for the file or directory does not match the opening FID. The data set may be corrupted.Action: Check your hardware devices and retry the data set. If the same errors occurs, the data is probably unrecognizable.72: Invalid data (an unexpected volume trailer) was found.TSADOSExplanation: TSADOS read a volume trailer record before the end of the current data set. The current data set may be corrupted.Action: Check your hardware devices and retry the data set. If the same errors occurs, the data is probably unrecognizable.73: User name (ID number) cannot be added to volume name. Error code: code.TSADOSExplanation: The requested user cannot be added as a user because of space restrictions on the volume.Action: Make sure the volume exists and the user has proper user access rights. Make sure the user is a valid Directory object. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 74: An internal error has occurred. Some trustees may not be restored for data_set_name.TSADOSExplanation: Trustee information expected next in the data stream was not found.Action: Make sure the correct trustees were restored for the data set. If not, correct the trustee list as necessary.PAGENUM=1240 ID="BP1234"75: Trustee name was not restored for data_set_name, because the trustee IDs are different.TSADOSExplanation: This error may happen when the same username exists on two different servers or when the users have different directory IDs. Action: At the end of the restore session, set the appropriate trustee information using NETADMIN, NWADMIN, or FILER.76: The volume restrictions data set format for data_set_name is invalid. Error code: code.TSADOSExplanation: TSADOS found the volume restrictions name and the ID to be out of sequence in the data stream. Processing will continue.Action: At the end of the restore session, verify the volume restrictions are correct. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 77: The trustee data set format for object_name is invalid. Error code: code.TSADOSExplanation: TSADOS found the trustee name and the ID to be out of sequence in the data stream. Processing will continue.Action: At the end of the restore session, verify the trustee information is correct. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 78: An internal error has occurred. Volume restrictions cannot be found for data_set_name.TSADOSExplanation: TSADOS expected Volume Restrictions to be next in the data stream, but did not find them. Processing will continue.Action: At the end of the restore session, verify the volume restrictions are correct. Make sure that you are using a valid volume name and that you have proper access rights.79: The extended attributes for file name were not restored. Error code: code.TSADOSExplanation: The extended attributes were not restored.Action: For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 80: Invalid data stream name name was found for file name.TSADOSExplanation: An unknown or unsupported data stream (file or directory) header name was found. This data stream will not be restored.Action: Make sure the file has been restored correctly and the correct number of data streams was restored.PAGENUM=1241 ID="BP1235"81: Data set data_set_name may be corrupted. An invalid CRC was received.TSADOSExplanation: The cycle redundancy check (CRC) in the data stream is invalid; the data may not be valid.Action: Try again. If the error continues, check the file or directory for internal errors.88: The NFS name space is not supported. This information will not be restored.TSADOSExplanation: This file or directory contains information specific to NFS that will not be restored.Action: If NFS information is required, restore to a volume with NFS support or load NFS support on the selected volume. If the NFS information is not needed, continue the restore session.89: The full paths data set format is invalid. Error code: code.TSADOSExplanation: An invalid full path was detected by TSADOS.Action: Make sure the full path is specified; it must contain volume, directory, filename, and file separators for the specified name space. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 90: The type name space is not supported.TSADOSExplanation: The specified name space type is invalid, or not supported on this volume.Action: Specify a valid name space type. If necessary, load name space support for the specified volume.91: Error code occurred while the program attempted to set the type name space name for data_set_name.TSADOSExplanation: TSADOS could not set the name space name for the indicated name space type.Action: Make sure the name space name and name space type are valid. If the problem persists, contact your Novell Authorized Reseller. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. PAGENUM=1242 ID="BP1236"92: Error code occurred while the program was scanning for extended attributes for data_set_name.TSADOSExplanation: An error occurred when the program attempted to read the extended attributes (EA) for the indicated file or directory. The extended attributes will not be backed up for this data set.Action: Make sure that you are using a valid data set name. Make sure the user has appropriate user access rights. Make sure the extended attributes are not corrupted. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 93: A buffer underflow occurred during the program's attempt to get the extended attribute value for data_set_name. Error code: code.TSADOSExplanation: TSADOS received an end-of-data error before the correct number of bytes was read.Action: Make sure the extended attributes and the data set's data are not corrupted. If the problem persists, contact your Novell Authorized Reseller. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 94: Error code occurred while the program attempted to scan information that is specific to the name_space_name name space of data_set_name.TSADOSExplanation: The name-space-specific information for the indicated data set cannot be read.Action: Make sure the specified name space support modules are loaded and volume support for the name space is enabled. Make sure you are using a valid data set name. Make sure the user has appropriate user access rights. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 95: An NFS hard link collision occurred while restoring data_set_name. The hard links cannot be restored.TSADOSExplanation: NFS hard links for the file or directory conflict with existing hard links. The restore session cannot be completed.Action: Exit and try the operation again.96: An error occurred while the program attempted to restore name-space-specific information for data_set_name in the data_set_name name space. Error code: code.TSADOSExplanation: Name space information for the file or directory cannot be restored.Action: Make sure the specified name space type is supported on the target volume. Make sure the user has appropriate user access rights. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. PAGENUM=1243 ID="BP1237"108: Directory entry information for data_set_name cannot be scanned.TSADOSExplanation: The program could not scan the directory for the indicated data set.Action: Make sure a valid path (including volume name) is specified. Make sure the user has appropriate user access rights.109: An internal error has occurred: buffer state problem number number.TSADOSExplanation: An internal error has occurred in the data buffer. Processing will continue; however, the data may be corrupted.Action: Repeat the session to make sure the data is not corrupted.110: This program cannot delete existing extended attributes for data_set_name. Error code: code.TSADOSExplanation: The program cannot delete the extended attributes for the indicated data set.Action: Make sure the user has appropriate user access rights. Make sure the file is not in exclusive use by another process. After the restore session, check the integrity of the extended attributes and correct or change them if necessary. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. 111: The TSA and responder versions are incompatible.TSADOSExplanation: The SMS modules are from incompatible versions.Action: Replace SMS modules as necessary to obtain compatible versions.256: Access has been denied. An invalid username or authentication was used.TSADOSExplanation: An invalid authentication has occurred.Action: Try again. Make sure the username and password are correct.257: This program cannot get the Directory object name.TSADOSExplanation: The name specified is not a valid or known name.Action: Verify the name; then try again.258: This program has encountered a buffer underflow and cannot get the entire field.TSADOSExplanation: TSADOS received an end-of-data error before the correct number of bytes were read. The data may be corrupted.Action: Make sure the data is correct. Repeat the session if necessary.PAGENUM=1244 ID="BP1238"259: This program cannot allocate a directory handle.TSADOSExplanation: The program could not allocate a directory handle.Action: Make sure you have specified a valid directory path for the desired name space. Make sure the user has appropriate user access rights.260: The bindery cannot be closed.TSADOSExplanation: The bindery cannot be closed.Action: Make sure that you have Supervisor rights to the server. Make sure the bindery is not being used.261: This program cannot create a directory entry.TSADOSExplanation: The program could not create the specified directory entry.Action: Make sure that you have specified a valid directory path for the name space. Make sure the user has appropriate user access rights.262: This program cannot create a file.TSADOSExplanation: The program could not create the specified file.Action: Make sure that you have specified a valid directory path for the name space. Make sure the user has appropriate user access rights.263: This data set name is already in use.TSADOSExplanation: TSADOS cannot overwrite the existing data set because the data set is being used.Action: Change the SBACKUP selection to "Overwrite parent/child," or change the destination path.264: The data set was excluded by the selection list.TSADOSExplanation: The specified file or directory was excluded by the selection criteria.Action: Change the selection criteria in SBACKUP.270: This program cannot delete a data set.TSADOSExplanation: The specified data set could not be deleted.Action: Make sure a valid data set name was specified. Make sure the user has appropriate user access rights. Make sure the file is not in exclusive use by another process.PAGENUM=1245 ID="BP1239"272: The program was processing a record or subrecord and did not find the Trailer field.TSADOSExplanation: Your data has been corrupted; the trailer field of a record is missing.Action: Clean the tape heads and check the hardware; then try again. If the problem persists, contact your Novell Authorized Reseller.273: This program cannot get the Directory object name.TSADOSExplanation: The specified object was not found in the bindery.Action: Make sure a valid bindery object was specified. Make sure the user has appropriate user access rights.274: This program cannot get the data stream name.TSADOSExplanation: The program could not read the requested data stream name.Action: Make sure a valid data set name for the name space was specified. Make sure name space is supported on the volume. Make sure the user has appropriate user access rights.275: This program cannot get the entry index.TSADOSExplanation: The program could not get an entry index for the requested file or directory.Action: Make sure a valid data set name for the name space was specified. Make sure name space is supported on the volume. Make sure the user has appropriate user access rights.276: This program cannot get the name space entry name.TSADOSExplanation: The program could not read the name space entry name for the requested file or directory.Action: Make sure a valid data set name for the name space was specified. Make sure name space is supported on the volume. Make sure the user has appropriate user access rights.277: This program cannot get the name space size information.TSADOSExplanation: The program could not read the name space information size.Action: Make a valid data set name for the name space was specified. Make sure name space is supported on the volume. 278: This program cannot get the NetWare server information.TSADOSExplanation: TSADOS could not read the server information.Action: Make sure the server's NetWare operating system version matches the TSADOS version in use.PAGENUM=1246 ID="BP1240"279: This program cannot get the volume-supported name space information.TSADOSExplanation: The program could not read the list of supported name spaces for the requested volume.Action: Make sure a valid volume name was specified. Make sure the volume is mounted. Make sure the user has appropriate user access rights.280: An invalid connection handle was passed.TSADOSExplanation: Your connection may no longer be valid.Action: Make sure the workstation is connected to the network.282: The data set handle is invalid.TSADOSExplanation: The data set may not exist.Action: Verify the data set exists.283: The data set name is invalid.TSADOSExplanation: An invalid file or directory name was specified.Action: Specify a valid data set name for the specified name space.284: An invalid data stream was found for data_set_name, data set type type.TSADOSExplanation: The data stream specified is invalid for the indicated data set and type.Action: Specify a valid data stream type. Make sure the requested name space is supported on this volume.285: The handle tag is invalid or the pointer is null.TSADOSExplanation: This handle is not valid.Action: None. This message is for information only.286: Message number is invalid.TSADOSExplanation: An invalid message number was detected.Action: None. This message is for information only.287: The name space type does not exist or is invalid.TSADOSExplanation: An invalid name space type was specified.Action: Specify a valid name space type, and make sure support for the specified name space type is loaded on the specified volume.PAGENUM=1247 ID="BP1241"288: The object ID or name that was backed up does not match the current object ID or name.TSADOSExplanation: The object ID or name for the restore does not match the object ID or name for the backup. Restore is probably being performed on a different server than the server that was used for the backup. This results in an object on both servers with a different ID.Action: None. This message is for information only.289: The Open mode option is out of range (less than 0 or greater than 23).TSADOSExplanation: An invalid open mode option was specified.Action: Specify a range within allowable parameters.290: One or more of the parameters is null or invalid.TSADOSExplanation: Invalid parameters were specified.Action: Replace any null or invalid parameters.291: An invalid path was used.TSADOSExplanation: The path is invalid for the specified name space.Action: Make sure the path is valid for the specified name space. Make sure the user has appropriate user access rights.292: The scan type is out of range (less than 0 or greater than 31).TSADOSExplanation: An invalid scan type was specified.Action: Correct the scan type and try again.294: The selection type is out of range (less than 0 or greater than 31).TSADOSExplanation: An invalid selection type was specified.Action: Correct the selection type and try again.295: The sequence number is invalid.TSADOSExplanation: An invalid sequence number was specified.Action: Correct the sequence number and try again.PAGENUM=1248 ID="BP1242"296: This login attempt has been denied.TSADOSExplanation: The login attempt failed.Action: Make sure a valid username and password for the selected server is specified; then try again.297: This logout attempt cannot be completed.TSADOSExplanation: The logout attempt failed.Action: Make sure no work is in progress; then try again.298: The name space path has not been updated.TSADOSExplanation: A valid path was not found in the path list for the selected name space.Action: Make sure a valid DOS path exists; then try again.300: The connection is invalid or does not exist.TSADOSExplanation: The old connection is invalid or no connection has been established.Action: Reestablish the connection and proceed.303: Either no more entries are in the list or the name space type does not exist.TSADOSAction: None. This message is for information only.304: You do not have the Search right on client service.TSADOSExplanation: TSADOS could not scan the client file system because of a rights violation.Action: Try one or more of the following:MARK=BULLETChange to another server or volume where you have the Search right.Log in as another user who does have the Search right.Grant the user appropriate access rights.305: No such property exists.TSADOSExplanation: An invalid property was specified.Action: Make sure the property you want is valid; then try again.PAGENUM=1249 ID="BP1243"306: A data stream cannot be opened.TSADOSExplanation: The program cannot open the specified data stream.Action: Make sure that you are using a valid data stream name and the data stream exists. Make sure the user has appropriate user access rights.307: A file cannot be opened.TSADOSExplanation: The program cannot open the specified file.Action: Make sure that you are using a valid filename and the file exists. Make sure the user has appropriate user access rights.308: The Open option is not used.TSADOSExplanation: The Open option mode type string is not being used.Action: None. This message is for information only. However, you may want to add the mode type string (for example, NO_DATA_STREAMS_STR).309: A file or directory cannot be restored. You are out of disk space.TSADOSExplanation: Restore cannot continue until you add more disk space.Action: Do one or both of the following:MARK=BULLETRestore to another volume with sufficient space.Increase the available disk space on the volume. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Disk Space Problems" in Supervising the Network.310: Either the server is out of memory or memory allocation failed.TSADOSAction: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.311: A UINT64 value has overflowed.TSADOSExplanation: A number overflow has occurred. The number is too large for the UINT64 type variable. This error is probably caused by invalid or corrupted data.Action: Contact your Novell Authorized Reseller.312: The extended attributes cannot be read.TSADOSExplanation: The extended attributes for a file cannot be read.Action: Make sure a valid file is specified. Make sure the user has appropriate user access rights.PAGENUM=1250 ID="BP1244"313: A file cannot be read.TSADOSExplanation: The file may be corrupted.Action: Try the operation again. If the problem persists, contact your Novell Authorized Reseller.314: Either no resource name can be found or all resource names have been found.TSADOSExplanation: The Scan Target Service Resource function has found all resources, or no resources were found.Action: If you are expecting a resource list, make sure the data set sequence is correct. Then try again.315: The program's attempt to scan failed, probably because an invalid path was specified.TSADOSExplanation: An invalid path was specified.Action: Specify a valid path for the requested name space. Make sure the user has appropriate user access rights.316: The program cannot scan file entry information.TSADOSExplanation: File scan failed.Action: Specify a valid filename for the requested name space. Make sure the user has appropriate user access rights.318: Information applicable to a specific name space cannot be scanned.TSADOSAction: Make sure that you have specified a valid name space and that name space support is loaded on the selected volume.319: The program cannot scan for trustees.TSADOSExplanation: TSADOS could not scan for a trustee list.Action: Make sure the user has appropriate user access rights. Make sure the entry index is valid; then try again.320: This scan type is not used.TSADOSExplanation: An invalid or unused scan type was specified.Action: Specify a valid scan type and try again.PAGENUM=1251 ID="BP1245"321: This selection type is not used.TSADOSExplanation: An invalid or unused selection type was specified.Action: Specify a valid scan type and try again.322: The program cannot set file information.TSADOSExplanation: The program cannot set file information.Action: Make sure the user has appropriate user access rights. Make sure the information to be set is valid.323: The transport mechanism has failed.TSADOSExplanation: The intermodule communication layer has failed.Action: Reestablish the LAN communication between machines. 324: The read/write request exceeds 128 KB.TSADOSExplanation: An intermodule communication request exceeds the 128KB limit.Action: Restructure the read/write request into pieces of 128 KB or smaller.325: An invalid or inactive TSA was specified.TSADOSExplanation: A TSA (Target Service Agent) was specified that cannot be found.Action: Make sure the TSA you want is valid and active. If it is not loaded, load it and try again.326: The requested function is not supported by this TSA.TSADOSExplanation: The requested function is not supported on the selected TSA (Target Service Agent).Action: Request a valid function, or select another TSA that supports the requested function.328: The program cannot write extended attribute (value).TSADOSExplanation: The program could not write the extended attribute(s).Action: Make sure the extended attribute(s) is valid and the file or directory is valid. Make sure sufficient extended attribute space is on the volume. Make sure the user has appropriate user access rights.PAGENUM=1252 ID="BP1246"329: An error occurred while the program attempted to write to a file. The full request could not be written.TSADOSExplanation: You may not have enough disk space, or the file may be corrupted.Action: Do one or more of the following:MARK=BULLETCheck the contents of the file; it may be corrupted.Increase the available disk space on the volume. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Disk Space Problems" in Supervising the Network.330: An error occurred while the program attempted to write to a file. TSADOSExplanation: You may not have enough disk space, or the file may be corrupted.Action: Do one or more of the following:MARK=BULLETCheck the contents of the file; it may be corrupted.Increase the available disk space on the volume. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Disk Space Problems" in Supervising the Network.PAGENUM=1253 ID="BP1247"TSANDS256: Access has been denied. An invalid username or authentication was used.TSANDSExplanation: An invalid authentication occurred.Action: Make sure the username and password are correct. Try again.257: This program cannot get the Directory object name.TSANDSExplanation: The object name specified is not a valid or known name.Action: Verify the name. Try again.258: This program has encountered a buffer underflow and cannot get the entire field.TSANDSExplanation: The program received an end-of-data error before the correct number of bytes were read. The data may be corrupted.Action: Make sure the data is correct. Repeat the session if necessary.259: This program cannot allocate a directory handle.TSANDSExplanation: The program could not allocate a directory handle.Action: Make sure a valid path for the desired name space type is specified. Make sure the user has appropriate user access rights.260: The bindery cannot be closed.TSANDSExplanation: The program could not close the bindery.Action: Make sure the user has Supervisor or equivalent user access rights. Make sure the bindery is not being used.261: This program cannot create a directory entry.TSANDSExplanation: The program could not create the specified directory entry.Action: Make sure a valid path for the desired name space type is specified. Make sure the user has appropriate user access rights.262: This program cannot create a file.TSANDSExplanation: The program could not create the specified file.Action: Make sure a valid path for the desired name space type is specified. Make sure the user has appropriate user access rights.PAGENUM=1254 ID="BP1248"263: This data set name is already in use.TSANDSExplanation: TSANDS cannot overwrite the existing data set because the data set is being used.Action: Change the SBACKUP selection to "Overwrite parent/child," or change the destination path.264: The data set was excluded by the selection list.TSANDSExplanation: The specified data set (file or directory) was excluded by the selection criteria.Action: Change the selection criteria in SBACKUP.270: This program cannot delete a data set.TSANDSExplanation: The specified data set could not be deleted.Action: Make sure a valid data set name for the name space type is specified. Make sure the user has appropriate user access rights. Make sure the file is not in exclusive use by another process.272: The program was processing a record or subrecord and did not find the Trailer field.TSANDSExplanation: Your data has been corrupted; the trailer field of a record is missing.Action: Clean your tape heads and check your hardware. Try again. If the problem persists, contact your Novell Authorized Reseller.273: This program cannot get the Directory object name.TSANDSExplanation: The specified object was not found in the bindery.Action: Make sure that you have specified a valid bindery object. Make sure the user has appropriate user access rights.274: This program cannot get the data stream name.TSANDSExplanation: The program could not read the requested data stream name.Action: Make sure the name space type is supported on the specified volume. Make sure a valid data set name for the name space type is specified. Make sure the user has appropriate user access rights.PAGENUM=1255 ID="BP1249"275: This program cannot get the entry index.TSANDSExplanation: TSANDS could not get an entry index for the requested data set (file or directory).Action: Make sure the name space type is supported on the specified volume. Make sure a valid data set name for the name space type is specified. Make sure the user has appropriate user access rights.276: This program cannot get the name space entry name.TSANDSExplanation: TSANDS could not read the name space entry name for the requested data set (file or directory).Action: Make sure the name space type is supported on the specified volume. Make sure a valid data set name for the name space type is specified. Make sure the user has appropriate user access rights.277: This program cannot get the name space size information.TSANDSExplanation: TSANDS could not read the name space information size.Action: Make sure the name space type is supported on the specified volume. Make sure a valid data set name for the name space type is specified. Make sure the user has appropriate user access rights.278: This program cannot get the NetWare server information.TSANDSExplanation: TSANDS could not read the server information.Action: Make sure the TSANDS version is compatible with the server's NetWare OS version.279: This program cannot get the volume-supported name space information.TSANDSExplanation: TSANDS could not read the list of supported name spaces for the requested volume.Action: Make sure the name space type is supported on the specified volume. Make sure a valid data set name for the name space type is specified. Make sure the user has appropriate user access rights.280: An invalid connection handle was passed.TSANDSExplanation: Your network connection may no longer be valid.Action: Make sure the workstation is connected to the network. Try again.PAGENUM=1256 ID="BP1250"282: The data set handle is invalid.TSANDSExplanation: The data set may not exist.Action: Verify the data set exists.283: The data set name is invalid.TSANDSExplanation: An invalid data set (file or directory) name was specified.Action: Make sure a valid data set name for the name space type is specified.284: An invalid data stream was found for data_set_name, data set type type.TSANDSExplanation: A data stream is invalid for the indicated data set and type.Action: Specify a valid data stream type. Make sure the name space type is supported on the specified volume.285: The handle tag is invalid or the pointer is null.TSANDSExplanation: This handle is not valid.Action: None. This message is for information only.286: Message number is invalid.TSANDSExplanation: An invalid message number was detected.Action: None. This message is for information only.287: The name space type does not exist or is invalid.TSANDSExplanation: An invalid name space type was specified.Action: Make sure a valid name space type is specified.288: The object ID or name that was backed up does not match the current object ID or name.TSANDSExplanation: The object ID or name for the restore does not match the object ID or name for the backup. Restore is probably being performed on a different server than the server that was used for the backup. This results in an object on both servers with a different ID.Action: None. This message is for information only.289: The Open mode option is out of range (less than 0 or greater than 23).TSANDSExplanation: An invalid open mode option was specified.Action: Specify a range within allowable parameters.PAGENUM=1257 ID="BP1251"290: One or more of the parameters is null or invalid.TSANDSExplanation: Invalid parameters were specified.Action: Check the parameters and replace any null or invalid ones.291: An invalid path was used.TSANDSExplanation: The path is invalid for the specified name space.Action: Make sure a valid path for the desired name space type is specified. Make sure the user has appropriate user access rights.292: The scan type is out of range (less than 0 or greater than 31).TSANDSExplanation: An invalid scan type was specified.Action: Correct the scan type and try again.294: The selection type is out of range (less than 0 or greater than 31).TSANDSExplanation: An invalid selection type was specified.Action: Correct the selection type and try again.295: The sequence number is invalid.TSANDSExplanation: An invalid sequence number was specified.Action: Correct the sequence number and try again.296: This login attempt has been denied.TSANDSExplanation: The login attempt failed.Action: Make sure the username and password are correct. Try again.297: This logout attempt cannot be completed.TSANDSExplanation: The logout attempt failed.Action: Make sure that you have no work in progress. Try again.298: The name space path has not been updated.TSANDSExplanation: A valid path was not found in the path list for the selected name space.Action: Make sure a valid path for the desired name space type is specified. Try again.PAGENUM=1258 ID="BP1252"300: The connection is invalid or does not exist.TSANDSExplanation: No connection has been established, or the old connection is invalid.Action: Reestablish the connection. Try again.303: Either no more entries are in the list or the name space type does not exist.TSANDSExplanation: This informational message is recorded in the error log file.Action: None. This message is for information only.304: You do not have the Search right on client service.TSANDSExplanation: TSANDS could not scan the client file system because of a rights violation.Action: Try one or more of the following:MARK=BULLETChange to another server or volume where you have the Search right.Log in as another user who does have the Search right.Make sure the user has appropriate user access rights.305: No such property exists.TSANDSExplanation: An invalid property was specified.Action: Make sure the property you want is valid. Try again.306: A data stream cannot be opened.TSANDSExplanation: The program cannot open the specified data stream.Action: Make sure the data stream exists and the data stream name is valid. Make sure the user has appropriate user access rights.307: A file cannot be opened.TSANDSExplanation: The program cannot open the specified file.Action: Make sure the file exists and the filename is valid. Make sure the user has appropriate user access rights.308: The Open option is not used.TSANDSExplanation: The "Open" option mode type string is not being used.Action: None. This message is for information only. However, you may want to add the mode type string (for example, NO_DATA_STREAMS_STR).PAGENUM=1259 ID="BP1253"309: A file or directory cannot be restored. You are out of disk space.TSANDSExplanation: The restore session cannot continue until you add more disk space.Action: Do one or more of the following:MARK=BULLETIncrease the available disk space on the volume. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Disk Space Problems" in Supervising the Network.Restore to another volume with enough disk space.310: Either the server is out of memory or memory allocation failed.TSANDSExplanation: You are out of server memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.311: A UINT64 value has overflowed.TSANDSExplanation: A number overflow has occurred because the number is too large for the UINT64 type variable. This error is probably caused by invalid or corrupted data.Action: Contact your Novell Authorized Reseller.312: The extended attributes cannot be read.TSANDSExplanation: The extended attributes for a file cannot be read.Action: Make sure the file exists and the filename is valid. Make sure the user has appropriate user access rights.313: A file cannot be read.TSANDSExplanation: The cause for this error is unknown. The file may be corrupted.Action: Try the operation again. If the problem persists, contact your Novell Authorized Reseller.314: Either no resource name can be found or all resource names have been found.TSANDSExplanation: The Scan Target Service Resource function has found all resources, or no resources were found.Action: If you are expecting a resource list, make sure the data set sequence is correct. Try again.PAGENUM=1260 ID="BP1254"315: The program's attempt to scan failed, probably because an invalid path was specified.TSANDSExplanation: An invalid path was specified.Action: Make sure a valid path for the desired name space type is specified. Make sure the user has appropriate user access rights.316: The program cannot scan file entry information.TSANDSExplanation: A file scan failed.Action: Make sure a valid filename for the requested name space type is specified. Make sure the user has appropriate user access rights.318: Information applicable to a specific name space cannot be scanned.TSANDSExplanation: Information applicable to a specific name space cannot be scanned.Action: Make sure a valid name space type is specified. Make sure the name space type is supported on the specified volume.319: The program cannot scan for trustees.TSANDSExplanation: TSANDS could not scan for a trustee list.Action: Make sure the user has appropriate user access rights. Make sure that your entry index is valid. Try again.320: This scan type is not used.TSANDSExplanation: An invalid or unused scan type was specified.Action: Specify a valid scan type. Try again.321: This selection type is not used.TSANDSExplanation: An invalid or unused selection type was specified.Action: Specify a valid selection type. Try again.322: The program cannot set file information.TSANDSExplanation: The program cannot set file information.Action: Make sure the user has appropriate user access rights. Make sure the information to be set is valid.PAGENUM=1261 ID="BP1255"323: The transport mechanism has failed.TSANDSExplanation: The intermodule communication layer has failed.Action: Check the LAN communication between machines and reestablish the connection.324: The read/write request exceeds 128 KB.TSANDSExplanation: An intermodule communication request exceeds the 128 KB limit.Action: Restructure the read/write request into pieces of 128 KB or smaller.325: An invalid or inactive TSA was specified.TSANDSExplanation: The TSA (Target Service Agent) that was specified cannot be found.Action: Make sure the TSA you want is valid and active. If the TSA is not loaded, load it and try again.326: The requested function is not supported by this TSA.TSANDSExplanation: The requested function is not supported on the selected TSA (Target Service Agent).Action: Request a valid function, or select another TSA that supports the requested function.328: The program cannot write extended attribute (value).TSANDSExplanation: The program could not write the extended attribute.Action: Make sure the extended attribute is valid and the data set (file or directory) is valid. Make sure the user has appropriate user access rights.329: An error occurred while the program attempted to write to a file. The full request could not be written.TSANDSExplanation: You may not have enough disk space, or the file may be corrupted.Action: Do one or more of the following:MARK=BULLETCheck the contents of the file; it may be corrupted.Increase the available disk space on the volume. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Disk Space Problems" in Supervising the Network.PAGENUM=1262 ID="BP1256"330: An error occurred while the program attempted to write to a file. TSANDSExplanation: You may not have enough disk space, or the file may be corrupted.Action: Do one or more of the following:MARK=BULLETCheck the contents of the file; it may be corrupted.Increase the available disk space on the volume. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Disk Space Problems" in Supervising the Network.PAGENUM=1263 ID="BP1257"TSAOS2256: Invalid username or authentication.TSAOS2Explanation: An invalid authentication has occurred.Action: Make sure the username and password are correct. Then retry the operation.257: Unable to get bindery object name.TSAOS2Explanation: The bindery object name specified is not a valid or known name.Action: Verify the name; then retry the operation.258: Buffer underflow, unable to get entire field.TSAOS2Explanation: TSAOS2 received an end-of-data error before the correct number of bytes were read. The data may be corrupted.Action: Make sure the data is correct. If necessary, repeat the session.259: Cannot allocate a directory handle.TSAOS2Explanation: TSAOS2 could not allocate a directory handle.Action: Make sure a valid path for the desired name space type is specified. Make sure the user has appropriate user access rights. For more information on rights, see "BOOK="cncptenu" COLLECTION="nw41"Rights" in Concepts.260: Cannot close the bindery.TSAOS2Explanation: The bindery cannot be closed.Action: Make sure the user has Supervisor or equivalent user access rights. Make sure the bindery is not being used.261: Cannot create a directory entry.TSAOS2Explanation: TSAOS2 could not create the specified directory entry.Action: Make sure a valid path for the desired name space type is specified. Make sure the user has appropriate user access rights.262: Cannot create a file.TSAOS2Explanation: TSAOS2 could not create the specified file.Action: Make sure a valid path for the desired name space type is specified. Make sure the user has appropriate user access rights.PAGENUM=1264 ID="BP1258"263: Data set name is already in use.TSAOS2Explanation: TSAOS2 could not overwrite the existing data set because the data set is being used.Action: Change the SBACKUP selection to "Overwrite parent/child," or change the destination path.264: The data set was excluded by the Selection List.TSAOS2Explanation: The specified data set (file or directory) was excluded by the selection criteria.Action: Change the selection criteria in SBACKUP.265: Cannot open an execute only file.TSAOS2Explanation: TSAOS2 could not open an execute-only file.Action: None. This message is for information only. These files will not be backed up.266: Data set is currently in use and cannot be accessed at this time.TSAOS2Explanation: The data set is in use, and TSAOS2 could not access it.Action: Retry the operation later.267: The target data set is newer than the one on the media, the data set will not be restored.TSAOS2Explanation: A mode update was specified; only newer files are restored.Action: None. This message is for information only.268: Attempt to open a data set when one is open or to alter a scan when a data set is open.TSAOS2Explanation: An attempt to open or alter an open data set failed. This is an implementation error.Action: Notify the third-party engine developer.269: No data sets found.TSAOS2Explanation: TSAOS2 could not locate a data set, because the specified path does not exist or was typed incorrectly.Action: Specify a valid data path.PAGENUM=1265 ID="BP1259"270: Error deleting data set.TSAOS2Explanation: The specified data set could not be deleted.Action: Make sure a valid data set name for the name space type is specified. Make sure the user has appropriate user access rights. Make sure the file is not in exclusive use by another process.271: Processing a Record/Subrecord and didn't find the HEADER Field.TSAOS2Explanation: The program was processing a record or a subrecord and did not find the header field of a record, indicating that the data has been corrupted.Action: Clean the tape heads and check the hardware; then retry the operation. If the problem persists, contact your Novell Authorized Reseller.272: Processing a Record/Subrecord and didn't find the TRAILER Field.TSAOS2Explanation: The program was processing a record or a subrecord and did not find the trailer field of a record, indicating that the data has been corrupted.Action: Clean the tape heads and check the hardware; then retry the operation. If the problem persists, contact your Novell Authorized Reseller.273: Unable to get bindery object name.TSAOS2Explanation: The specified object was not found in the bindery.Action: Make sure a valid bindery object was specified. Make sure the user has appropriate user access rights.274: Unable to get data stream name.TSAOS2Explanation: TSAOS2 could not read the requested data stream name.Action: Make sure a valid data set name for the name space type is specified. Make sure the name space type is supported on the specified volume. Make sure the user has appropriate user access rights.275: Unable to get the entry index.TSAOS2Explanation: TSAOS2 could not get an entry index for the requested data set (file or directory).Action: Make sure a valid data set name for the name space type is specified. Make sure the name space type is supported on the specified volume. Make sure the user has appropriate user access rights.PAGENUM=1266 ID="BP1260"276: Unable to get name space entry name.TSAOS2Explanation: TSAOS2 could not read the name space entry name for the requested data set (file or directory).Action: Make sure a valid data set name for the name space type is specified. Make sure the name space type is supported on the specified volume. Make sure the user has appropriate user access rights.277: Unable to get name space size information.TSAOS2Explanation: TSAOS2 could not read the name space information size.Action: Make sure a valid data set name for the name space type is specified. Make sure the name space type is supported on the specified volume. Make sure the user has appropriate user access rights.278: Unable to get file server information.TSAOS2Explanation: TSAOS2 could not read the server information.Action: Make sure the server's NetWare operating system's version matches the TSAOS2 version in use.279: Unable to get volume supported name space information.TSAOS2Explanation: TSAOS2 could not read the list of supported name spaces for the requested volume.Action: Make sure a valid volume name is specified. Make sure the volume is mounted. Make sure the user has appropriate user access rights.280: An invalid connection handle was passed.TSAOS2Explanation: The user's workstation connection may no longer be valid.Action: Make sure the workstation is connected to the network.281: Invalid Data Set data.TSAOS2Explanation: The data set (directory or file) may not exist.Action: Make sure the data set exists.282: Data set handle is invalid.TSAOS2Explanation: The data set (directory or file) may not exist.Action: Make sure the data set exists.PAGENUM=1267 ID="BP1261"283: Data set name is invalid.TSAOS2Explanation: An invalid data set (file or directory) name was specified.Action: Specify a valid data set name for the specified name space.284: Data set type is invalid.TSAOS2Explanation: A data stream is invalid for the data set and type.Action: Specify a valid data stream type. Make sure the name space type is supported on the specified volume.285: Handle is tagged INVALID or ptr is NIL.TSAOS2Explanation: The handle specified is not valid.Action: Notify the third-party engine developer.286: Message number is invalid.TSAOS2Explanation: An invalid message number was detected.Action: Make sure the TSARC.DLL is the correct version.287: The name space type does not exist or is invalid.TSAOS2Explanation: An invalid name space type was specified.Action: Make sure a valid name space type is specified. Make sure the name space type is supported on the specified volume.288: The object ID/name backed up doesn't match the current object ID/name.TSAOS2Explanation: The object ID or name for the restore does not match the object ID or name for the backup. Restore is probably being performed on a different server than the server that was used for the backup. This results in an object on both servers with a different ID.Action: None. This message is for information only.289: Open mode option is out of range (less than 0 or greater than 23).TSAOS2Explanation: An invalid open mode option was specified.Action: Specify a range within the allowed parameters.290: One or more of the parameters is NULL or invalid.TSAOS2Explanation: Null or invalid parameters were specified.Action: Check the parameters and replace any null or invalid ones.PAGENUM=1268 ID="BP1262"291: An invalid path was used.TSAOS2Explanation: The path is invalid for the specified name space.Action: Make sure a valid path for the desired name space type is specified. Make sure the user has appropriate user access rights.292: Scan type is out of range (less than 0 or greater than 31).TSAOS2Explanation: An invalid scan type was specified.Action: Notify the third-party engine developer.293: An invalid selection list entry was passed.TSAOS2Explanation: An invalid selection list entry was specified.Action: Specify a selection list entry within the allowed parameters; then retry the operation.294: Selection type is out of range (less than 0 or greater than 31).TSAOS2Explanation: An invalid selection type range was specified.Action: Notify the third-party engine developer.295: The sequence number is invalid.TSAOS2Explanation: An invalid sequence number was specified.Action: Correct the sequence number; then retry the operation.296: Login denied.TSAOS2Explanation: The login attempt failed. An invalid username or password may have been typed.Action: Make sure the username and password are correct. Then retry the operation.297: Unable to logout.TSAOS2Explanation: The logout attempt failed.Action: Make sure no work is in progress; then retry the operation.298: The name space path has not been updated.TSAOS2Explanation: A valid path was not found in the path list for the selected name space.Action: Make sure a valid path (including volume name) is specified. Then retry the operation.PAGENUM=1269 ID="BP1263"299: The specified server is unable to service the request at this time.TSAOS2Explanation: The server for TSAOS2 is not available.Action: Make sure the server is operating and available on the network. Or, specify a different server in the TSAOS2.CFG file.300: Connection is invalid or does not exist.TSAOS2Explanation: No connection has been established, or the old connection is invalid.Action: Reestablish the connection and proceed.301: No more data exists.TSAOS2Explanation: No additional Target Service Names exist.Action: None. This message is for information only.302: There are no more data sets to be scanned.TSAOS2Explanation: The scan is complete.Action: None. This message is for information only.303: No more entries in list or name space type does not exist.TSAOS2Explanation:  The data or name does not contain a DOS or OS/2 name.Action: Restore the data to a server.304: No search privileges on client service.TSAOS2Explanation: TSAOS2 could not scan the client file system because of a rights violation.Action: Do one of the following actions:MARK=BULLETIf appropriate, make sure the user has appropriate user access rights.Have the user change to another server or volume where the user has the Search right. Have the user log in as another user who does have the Search right. 305: No such property.TSAOS2Explanation: An invalid property was specified.Action: Specify a valid property; then retry the operation.PAGENUM=1270 ID="BP1264"306: Unable to open a data stream.TSAOS2Explanation: TSAOS2 could not open the specified data stream.Action: Make sure the data stream exists and the data stream name is valid. Make sure the user has appropriate user access rights.307: Can't open a file.TSAOS2Explanation: TSAOS2 could not open the specified file.Action: Make sure the file exists and the filename is valid. Make sure the user has appropriate user access rights.308: Open mode option is not used.TSAOS2Explanation: The Open mode option type string is not supported by the TSAOS2.Action: None. This message is for information only.309: Can't restore, out of disk space.TSAOS2Explanation: The restore session cannot continue until more disk space is added.Action: For information on adding disk space, see "BOOK="superenu" COLLECTION="nw41"Resolving Server Disk Space Problems" in Supervising the Network.310: Server out of memory or memory allocation failed.TSAOS2Explanation: The server may not have enough available memory.Action: For information on adding memory to the server, see "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.311: A UINT64 value has overflowed.TSAOS2Explanation: A number overflow has occurred. The number is too large for the UINT64 type variable. This error is probably caused by invalid or corrupted data.Action: Contact your Novell Authorized Reseller.312: Unable to read extended attributes.TSAOS2Explanation: The extended attributes for a file cannot be read.Action: Make sure a valid file was specified. Make sure the user has appropriate user access rights.PAGENUM=1271 ID="BP1265"313: Error reading file.TSAOS2Explanation: The cause for this error is unknown. The file may be corrupted.Action: Retry the operation. If the problem persists, contact your Novell Authorized Reseller.314: No resource name is found or all resource names have been found.TSAOS2Explanation: The Scan Target Service Resource function has found all resources, or no resources were found.Action: If you are expecting a resource list, make sure the data set sequence is correct. Then retry the operation.315: Scan failed, probably due to an invalid path.TSAOS2Explanation: An invalid path was specified.Action: Specify a valid path for the requested name space. Make sure the user has appropriate user access rights.316: Unable to scan file entry information.TSAOS2Explanation: The file scan failed.Action: Make sure a valid filename for the requested name space type is specified. Make sure the user has appropriate user access rights.317: Cannot alter resource list while scans are in progress.TSAOS2Explanation: NWSMTS cannot build a resource list during an NWSMTS Scan Target Service Resource List operation. This is an implementation error.Action: Notify the third-party engine developer.318: Unable to scan name space specific information.TSAOS2Explanation: Information applicable to a specific name space cannot be scanned.Action: Make sure a valid name space type is specified. Make sure the name space type is supported on the specified volume.319: Unable to scan for trustees.TSAOS2Explanation: TSAOS2 could not scan for a trustee list.Action: Make sure the user has appropriate user access rights. Make sure that your entry index is valid; then retry the operation.PAGENUM=1272 ID="BP1266"320: Scan type is not used.TSAOS2Explanation: An unused scan type was specified.Action: None. This message is for information only..321: Selection type is not used.TSAOS2Explanation: An unused selection type was specified.Action: None. This message is for information only.322: Unable to set file information.TSAOS2Explanation: TSAOS2 cannot set file information.Action: Make sure the user has appropriate user access rights. Make sure the information to be set is valid.323: The transport mechanism has failed.TSAOS2Explanation: The inter-module communication layer has failed.Action: Check the LAN communications between machines, then reregister and reestablish the connection.324: The read/write request exceeds 128K.TSAOS2Explanation: An inter-module communication request exceeds the 128 KB limit.Action: Notify the third-party engine developer.325: Invalid or inactive TSA specified.TSAOS2Explanation: A Target Service Agent (TSA) was specified that cannot be found.Action: Make sure the TSA you want is valid and active. If the TSA is not loaded, load it and retry the operation.326: The requested function is not supported by this TSA.TSAOS2Explanation: The requested function is not supported on the selected Target Service Agent (TSA).Action: Request a valid function, or select another TSA that supports the requested function.327: A valid parent handle is created.TSAOS2Action: None. This message is for information only.PAGENUM=1273 ID="BP1267"328: Unable to write extended attribute (value).TSAOS2Explanation: TSAOS2 could not write an extended attribute.Action: Make sure that extended attributes and the data sets (files or directories) are valid. Make sure the user has appropriate user access rights.329: Error writing to a file, didn't write full request.TSAOS2Explanation:  An error occurred while the program attempted to write to a file. The full request could not be written. The file may be corrupted, or enough disk space may not be available to write the file.Action: Make sure the contents of the file are not corrupted. If the disk space is low, see "BOOK="superenu" COLLECTION="nw41"Resolving Server Disk Space Problems" in Supervising the Network.330: Error writing to a file.TSAOS2Explanation: An error occurred while the TSAOS2 program attempted to write to a file. The file may be corrupted, or there may not be enough available disk space.Action: Make sure the contents of the file are not corrupted. If the disk space is low, see "BOOK="superenu" COLLECTION="nw41"Resolving Server Disk Space Problems" in Supervising the Network. 331: Indicates reconnection requirement.TSAOS2Explanation: The Transport Level Interface (TLI) transport has failed.Action: Reconnect the TSAOS2 to the server, and reconnect the engine to the TSA. Then run the job again.PAGENUM=1274 ID="BP1268"TSASMS1: TSASMS ERROR: Unable to unload TSASMS. TSASMS was not found in memory.TSASMSExplanation:   The command line option to unload TSASMS.COM from the workstation was used before TSASMS.COM was loaded or after it removed itself from memory because of a termination of the communication link with WSMAN.NLM.Action: None. This message is for information only.2: TSASMS ERROR: Unable to load TSASMS. TSASMS is already loaded in memory.TSASMSExplanation:   TSASMS.COM may not be loaded more than once on the workstation. TSASMS.COM is still loaded in memory.Action:  Before starting TSASMS.COM again, unload TSASMS.COM using the /U option.3: TSASMS ERROR: Unable to load TSASMS. TSASMS may not be loaded from inside Windows.TSASMSExplanation:   When starting to load the TSASMS.COM in memory, it detected Microsoft Windows running. TSASMS.COM must be loaded before Windows is started.Action:  Unload Windows, load TSASMS, then restart Windows.4: TSASMS ERROR: Unable to load TSASMS. TSASMS may not be loaded if DOS is in a task-switching mode.TSASMSExplanation:   When starting to load TSASMS.COM, it detected that a DOS task-switcher is loaded. TSASMS.COM must be loaded before any task-switching programs.Action:  Unload the task-switcher, load TSASMS.COM, then restart the task-switcher.5: TSASMS ERROR: Unable to load TSASMS. TSASMS may not be loaded if DOS version is less than 3.30.TSASMSExplanation:   TSASMS.COM uses DOS functions that are available only in DOS versions 3.30 and newer.Action: Upgrade the DOS workstation to DOS version 3.30 or newer.6: TSASMS ERROR: Must use NET.CFG or command line parameters.TSASMSExplanation:   No copy of NET.CFG file was found, and no command line options were used. TSASMS.COM must have information from one of these sources to load and function.Action: Use command line parameters, or add a "NetWare DOS TSA" section to the NET.CFG file with appropriate parameters.PAGENUM=1275 ID="BP1269"7: TSASMS ERROR: Can't read NET.CFG and no command line parameters were used.TSASMSExplanation:   No copy of NET.CFG file could be opened or the read of the NET.CFG file failed, and no command line options were used. TSASMS.COM must have information from one of these sources to load and function.Action: Use command line parameters, or add a "NetWare DOS TSA" section to the NET.CFG file with appropriate parameters.8: TSASMS ERROR: There are no usable parameters in net.cfg or on the command line.TSASMSExplanation:   No valid parameters were found in the NET.CFG file, and no valid command line options were used. TSASMS.COM must have information from one of these sources to load and function.Action: Use command line parameters, or add a "NetWare DOS TSA" section to the NET.CFG file with appropriate parameters.9: TSASMS Warning: Must enter at least 1 drive letter.TSASMSExplanation:   At least one valid disk drive letter must be specified.Action: Review the available drive letters on the workstation. Note: Drive letters for TSASMS do not include a colon.10: TSASMS Warning: Need to use either Password or Trust option.TSASMSExplanation:   The Password (/P=password) or Trust (/T) option must be used for connection.Action: Add the Password (/P=) or Trust (/T) option to the command line of the NET.CFG file.11: TSASMS ERROR: Unable to load TSASMS. Novell NetWare has not been found.TSASMSExplanation:   The Novell DOS Client software (ODI drivers and DOS shell or VLM programs) is not loaded on the workstation.Action: Load the client software before loading the TSASMS.12: TSASMS ERROR: Unable to load TSASMS. Novell File server and TSA could not be located.TSASMSExplanation:   The server specified did not respond, or it does not have WSMAN.NLM loaded.Action: Make sure the server name specified is correct. Make sure the server is operating and available on the network. Make sure the WSMAN.NLM is loaded on the specified server.PAGENUM=1276 ID="BP1270"13: TSASMS ERROR: Unable to load TSASMS. Error opening SPX Socket.TSASMSExplanation:   TSASMS failed to open a communication socket on the workstation.Action: Make sure the workstation network client software is loaded and enough memory is available. See "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network.14: TSASMS ERROR: Unable to load TSASMS. Memory Allocation Error on Server.TSASMSExplanation:   Memory could not be allocated on the specified server to complete the communication.Action: Make more memory available on the server, or specify a different server. See "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network.15: TSASMS ERROR: Unable to load TSASMS. Server User Limit Has Been Exceeded.TSASMSExplanation:   WSMAN.NLM on the specified server has the maximum number of workstation connections currently in use.Action: Specify a different server, or remove some of the registered workstations for this server.16: TSASMS ERROR: Unable to load TSASMS. Unable to locate Server or unable to communicate with Server.TSASMSExplanation:   The server specified did not respond, or the server does not have WSMAN.NLM loaded.Action: Make sure the server name specified is correct. Make sure the server is operating and available on the network. Make sure the WSMAN.NLM is loaded on the specified server.17: TSASMS ERROR: Unable to load TSASMS. Unable to initialize communications with server.TSASMSExplanation:   The server specified did not respond, or the server does not have WSMAN.NLM loaded.Action: Make sure the server name specified is correct. Make sure the server is operating and available on the network. Make sure the WSMAN.NLM is loaded on the specified server.18: TSASMS ERROR in parameter specification:TSASMSExplanation:   One or more of the parameters on the command line or in the NET.CFG file are invalid.Action: Check parameters specified on the command line or in the NET.CFG file, and correct the invalid parameter.PAGENUM=1277 ID="BP1271"19: TSASMS ERROR: Invalid buffer size. Buffer size must be between 1 and 30 buffers.TSASMSExplanation:   The buffer size specified on the command line or in the NET.CFG file is invalid. Only values 1 to 30 are valid for the /B or Disk Buffers option.Action: Check the value specified on the command line or in NET.CFG file, and specify a value within the valid range.20: TSASMS ERROR: Invalid disk drive specifiedTSASMSExplanation: The disk drive specified on the command line or in the NET.CFG file is invalid.Action: Review the available disk drives and correct the drive specified on the command line or in the NET.CFG file.21: TSASMS ERROR: No valid DOS drive letters have been specified.TSASMSExplanation:   One or more of the specified workstation disk drive letters are not in use. No disk drive is available for that letter.Action: Review available disk drives on the workstation and correct the drive specified on the command line or in the NET.CFG file.22: TSASMS ERROR: Workstation name too long.TSASMSExplanation:   The specified workstation name is greater than 48 characters.Action: Shorten the specified workstation name to be within 48 characters.23: TSASMS ERROR: Password too long.TSASMSExplanation:   The password specified is greater than 10 characters.Action: Shorten the specified password to 10 or less characters, or use the Trust option.24: TSASMS ERROR: Server name too long.TSASMSExplanation:   The specified server name is greater than 48 characters.Action: Shorten the specified server name to be within 48 characters.25: TSASMS ERROR: Invalid stack size. Stack size must be between 512 and 4096 bytes.TSASMSExplanation:    The stack size option specified is not within the allowed size parameters.Action: Specify a value between 512 and 4096 inclusive.PAGENUM=1278 ID="BP1272"26: TSASMS ERROR: Invalid command letter.TSASMSExplanation:   The command line contains an invalid option letter.Action: Make sure to specify a valid command letter on the command line.PAGENUM=1279 ID="BP1273"TUI6: Caller uses NUT version hexidecimal_number, but TUI uses version hexidecimal_number.TUIExplanation: A utility requesting TUI services is expecting a level of NUT services different from that provided by TUI.NLM. TUI will continue, but all required services may not be available.Action: If no further errors occur, no action is required. However, you should upgrade the TUI.NLM, NWSNUT.NLM, NUT.NLM, and the utility's NLM file to the latest version on the server displaying this error. 8: Could not get enough resources to support TUI.TUIExplanation: The server is very low on available memory. TUI services will not be available to the requesting utility. Action: Increase the available memory. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. Reload the utility when more memory is available. 9: NUT Initialization failed: error_code.TUIExplanation: : TUI could not complete NUT initialization for the utility requesting TUI services. The server is low on available memory or an internal error occurred.Action: Use MONITOR or NWADMIN to determine the resource usage in the server displaying this error message. If resources are low, see "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network. Reload the utility when more memory is available.PAGENUM=1280 ID="BP1274"UIMPORTUIMPORT allows a supervisor or administrator to load user objects into the Directory tree from an ASCII import file. This file can be created by most database programs or by any method that can create a comma-separated ASCII file.100: The control file cannot be found: (name)UIMPORTExplanation: UIMPORT requires a file specifying control parameters. That file cannot be found.Action: Create the necessary control file. For information about UIMPORT, see "BOOK="utlrfenu" COLLECTION="nw41"UIMPORT" in Utilities Reference.110: The specified data file cannot be found: nameUIMPORTExplanation: UIMPORT requires a file containing the extracted data that is to be imported. That file cannot be found.Action: Create the necessary data file. For information about UIMPORT, see "BOOK="utlrfenu" COLLECTION="nw41"UIMPORT" in Utilities Reference.120: The control file contains an invalid section header: invalid_header.UIMPORTExplanation: An invalid header was specified in the control file.Action: Specify a valid header. For information about UIMPORT, see "BOOK="utlrfenu" COLLECTION="nw41"UIMPORT" in Utilities Reference.130: The "Import Control" section contains an invalid statement: statement.UIMPORTExplanation: An invalid control parameter was specified in the control file.Action: Specify a valid control parameter. For information about UIMPORT, see "BOOK="utlrfenu" COLLECTION="nw41"UIMPORT" in Utilities Reference.132: The "Fields" section contains an invalid field definition: code.UIMPORTExplanation: An invalid NetWare Directory Services property was specified in the control file.Action: Specify a valid property. For information about UIMPORT, see "BOOK="utlrfenu" COLLECTION="nw41"UIMPORT" in Utilities Reference. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. PAGENUM=1281 ID="BP1275"141: You did not specify a field for "CN."UIMPORTExplanation: A Common Name (CN) property was not specified. This property is mandatory.Action: Specify a Common Name property. For information about UIMPORT, see "BOOK="utlrfenu" COLLECTION="nw41"UIMPORT" in Utilities Reference.142: You did not specify a field for "Surname."UIMPORTExplanation: A Surname property was not specified. This property is mandatory.Action: Specify a Surname property. For information about UIMPORT, see "BOOK="utlrfenu" COLLECTION="nw41"UIMPORT" in Utilities Reference.150: More fields were expected in this record: record_name.UIMPORTExplanation: The control file specified more fields than are contained in the data record.Action: Modify the data file or the control file so that they match. For information about UIMPORT, see "BOOK="utlrfenu" COLLECTION="nw41"UIMPORT" in Utilities Reference.151: There are more fields in this record than expected. The remaining fields will be ignored: record_name.UIMPORTExplanation: The data record had more fields than expected by the control file.Action: Modify the data record or the control file so that they match. For information about UIMPORT, see "BOOK="utlrfenu" COLLECTION="nw41"UIMPORT" in Utilities Reference.215: The context you are trying to change to is invalid.UIMPORTExplanation: The context that was entered does not exist, or the context was entered incorrectly.Action: Specify a valid context. Also make sure that it is spelled correctly. For information about UIMPORT, see "BOOK="utlrfenu" COLLECTION="nw41"UIMPORT" in Utilities Reference.220: An error occurred during UIMPORT's attempt to create the context.UIMPORTExplanation: An invalid context was specified, or an internal system error has occurred.Action: Specify a valid context; then try the operation again. Also be sure that no associated problems have occurred (such as the network going down, a connection being lost, or previous errors having occurred and been ignored). If the problem persists, contact your Novell Authorized Reseller.PAGENUM=1282 ID="BP1276"260: An internal system error occurred during UIMPORT's attempt to canonicalize the context. Error code: code.UIMPORTExplanation: An internal system error has probably occurred.Action: Try the operation again. Also make sure that no associated problems have occurred (such as the network going down, a connection being lost, or previous errors having occurred and been ignored). For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.300: An error occurred when the shell name context was read. Error code: code.UIMPORTExplanation: An internal system error has probably occurred.Action: Try the operation again. Also make sure that no associated problems have occurred (such as the network going down, a connection being lost, or previous errors having occurred and been ignored). For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.301: Volume name has no host resource property and can't be used.UIMPORTAction: Set the host resource property for the volume. For information about UIMPORT, see "BOOK="utlrfenu" COLLECTION="nw41"UIMPORT" in Utilities Reference.302: Path name does not exist.UIMPORTAction: Make sure the user specified a valid path. For information about UIMPORT, see "BOOK="utlrfenu" COLLECTION="nw41"UIMPORT" in Utilities Reference.303: You don't have access to path name. Error code: codeUIMPORTAction: If appropriate, grant the user rights to the specified path. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. For information about UIMPORT, see "BOOK="utlrfenu" COLLECTION="nw41"UIMPORT" in Utilities Reference.304: An error occurred trying to determine your access level to path name. Error code: code.UIMPORTExplanation: An internal system error occurred.Action: Make sure the user has appropriate user access rights. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. For information about UIMPORT, see "BOOK="utlrfenu" COLLECTION="nw41"UIMPORT" in Utilities Reference.PAGENUM=1283 ID="BP1277"305: The utility can't create path name. Error code: codeUIMPORTExplanation: An internal system error probably occurred, or an invalid directory was specified.Action: Make sure the user specified a valid directory. Make sure the user has the appropriate rights to create the specified directory. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. For information about UIMPORT, see "BOOK="utlrfenu" COLLECTION="nw41"UIMPORT" in Utilities Reference.306: The utility can't delete path name. Error code: codeUIMPORTExplanation: An internal system error has probably occurred, or an invalid directory was specified.Action: Make sure the user specified a valid directory. Make sure the user has the appropriate rights to delete the specified directory. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. For information about UIMPORT, see "BOOK="utlrfenu" COLLECTION="nw41"UIMPORT" in Utilities Reference.307: Path name on volume name for user name can't be created.UIMPORTExplanation: An internal system error has probably occurred, or an invalid parameters were specified.Action: Make sure the user specified a valid directory, volume, and user name. If appropriate, make sure the user has rights to create the specified directory. For information about UIMPORT, see "BOOK="utlrfenu" COLLECTION="nw41"UIMPORT" in Utilities Reference.308: This utility can't grant rights to path name for user name.UIMPORTExplanation: An internal system error has probably occurred, or an invalid parameters specified.Action: Make sure the user specified a valid directory, volume, and user name. If appropriate, make sure the user has the appropriate rights to the specified directory for performing the specified task. For information about UIMPORT, see "BOOK="utlrfenu" COLLECTION="nw41"UIMPORT" in Utilities Reference.309: This utility can't modify object name. Error code: codeUIMPORTExplanation: An internal system error has probably occurred, or an invalid object name was specified.Action: Make sure the user specified a valid object name. If appropriate, make sure the user has the appropriate rights to verify the validity of properties being modified. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. For information about UIMPORT, see "BOOK="utlrfenu" COLLECTION="nw41"UIMPORT" in Utilities Reference.PAGENUM=1284 ID="BP1278"310: The utility can't create the mailbox directories for user name and mailbox ID name.UIMPORTExplanation: An internal system error has probably occurred, or an invalid user or mailbox ID was specified.Action: Make sure the user specified is valid. Make sure the specified mailbox ID is valid. Make sure the user has the appropriate rights to perform the specified task. For information about UIMPORT, see "BOOK="utlrfenu" COLLECTION="nw41"UIMPORT" in Utilities Reference.311: Home and mail directories can't be on a server in the current tree. Server Name: nameUIMPORTAction: Make sure the home and mail directories are not in the current tree. For information about UIMPORT, see "BOOK="utlrfenu" COLLECTION="nw41"UIMPORT" in Utilities Reference.312: There is not enough memory to update the mailbox information. User: name Mailbox location: location Mailbox ID: nameUIMPORTAction: Make sure the server has enough memory. See "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network. For information about UIMPORT, see "BOOK="utlrfenu" COLLECTION="nw41"UIMPORT" in Utilities Reference.313: The mailbox location can't be set for user name since messaging server name is either: 1. Not a messaging server 2. Is not found. 3. Does not have a messaging database location property.UIMPORTAction: Make sure the server specified is a valid server, a messaging server, and that it has a messaging database location property. For information about UIMPORT, see "BOOK="utlrfenu" COLLECTION="nw41"UIMPORT" in Utilities Reference.314: The Foreign Email Address is incorrect. The format is tttt:aaaaa where t is the type, and a is the address. The incorrect Email Address value is: address_valueUIMPORTAction: Correct the Foreign Email Address. For information about UIMPORT, see "BOOK="utlrfenu" COLLECTION="nw41"UIMPORT" in Utilities Reference.314: The Foreign Email Alias is incorrect. The format is tttt:aaaaa where t is the type and a is the address. The incorrect alias is alias_valueUIMPORTAction: Correct the Foreign Email Alias. For information about UIMPORT, see "BOOK="utlrfenu" COLLECTION="nw41"UIMPORT" in Utilities Reference.PAGENUM=1285 ID="BP1279"315: You can't modify the password of user name.UIMPORTAction: Do not try to modify the specified user's password. For information about UIMPORT, see "BOOK="utlrfenu" COLLECTION="nw41"UIMPORT" in Utilities Reference.403: Cannot add a duplicate value to this user. NWDSModifyObject error: code. User: name Attribute: name.UIMPORTExplanation: An internal system error has probably occurred.Action: Try the operation again. Make sure that no associated problems have occurred (such as the network going down, a connection being lost, or previous errors having occurred and been ignored). For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.404: An error occurred attempting to write the path property. The volume object may not exist. Volume: nameUIMPORTAction: Make sure the volume exists. For information about UIMPORT, see "BOOK="utlrfenu" COLLECTION="nw41"UIMPORT" in Utilities Reference.707: The program cannot read the login script file. File name: name.UIMPORTExplanation: An internal system error has probably occurred.Action: Try the operation again. Make sure that no associated problems have occurred (such as the network going down, a connection being lost, or previous errors having occurred and been ignored). For information about UIMPORT, see "BOOK="utlrfenu" COLLECTION="nw41"UIMPORT" in Utilities Reference. If the problem persists, contact your Novell Authorized Reseller.708: The program cannot read the login script.UIMPORTExplanation: An internal system error has probably occurred, or the login script specified was invalid or mistyped.Action: Make sure the login script name is valid and typed correctly; then try the operation again. Make sure that no associated problems have occurred (such as the network going down, a connection being lost, or previous errors having occurred and been ignored). For information about UIMPORT, see "BOOK="utlrfenu" COLLECTION="nw41"UIMPORT" in Utilities Reference. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=1286 ID="BP1280"709: The program cannot read the login script file.UIMPORTExplanation: An internal system error has probably occurred, or the login script specified was invalid or mistyped.Action: Make sure the login script name is valid and typed correctly; then try the operation again. Also make sure that no associated problems have occurred (such as the network going down, a connection being lost, or previous errors having occurred and been ignored). For information about UIMPORT, see "BOOK="utlrfenu" COLLECTION="nw41"UIMPORT" in Utilities Reference. If the problem persists, contact your Novell Authorized Reseller.710: The program cannot add the Login Script property. Error code: code.UIMPORTExplanation: An internal system error has probably occurred.Action: Try the operation again. Make sure that no associated problems have occurred (such as the network going down, a connection being lost, or previous errors having occurred and been ignored). For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. For information about UIMPORT, see "BOOK="utlrfenu" COLLECTION="nw41"UIMPORT" in Utilities Reference. If the problem persists, contact your Novell Authorized Reseller.712: The program cannot write the Login Script.UIMPORTExplanation: An internal system error has probably occurred, or the user may not have the appropriate rights to write to the login script.Action: Try the operation again. If appropriate, make sure the user has the appropriate rights to write to the login script. Make sure that no associated problems have occurred (such as the network going down, a connection being lost, or previous errors having occurred and been ignored). If the problem persists, contact your Novell Authorized Reseller.718: The program cannot copy the USER_TEMPLATE to a new user. Error code: code.UIMPORTExplanation: An internal system error has probably occurred.Action: Try the operation again. Make sure that no associated problems have occurred (such as the network going down, a connection being lost, or previous errors having occurred and been ignored). For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=1287 ID="BP1281"720: The user does not exist. You cannot create this user with the Update Only import mode. User: nameUIMPORTExplanation: The "U" Update Only import mode cannot create a user.Action: Select the "C" (Create Only) or "B" (Both) import mode. Then try again. For information about UIMPORT, see "BOOK="utlrfenu" COLLECTION="nw41"UIMPORT" in Utilities Reference.722: The user already exists. You cannot update this user with the Create Only import mode. User: name.UIMPORTExplanation: The "C" (Create Only) import mode cannot update a user.Action: Select the "U" (Update Only) or "B" (Both) import mode. Then try again. For information about UIMPORT, see "BOOK="utlrfenu" COLLECTION="nw41"UIMPORT" in Utilities Reference.724: You cannot update an object that is not a user. Object name: name.UIMPORTExplanation: An object has been chosen that is not a user.Action: Use UIMPORT with user objects only. For information about UIMPORT, see "BOOK="utlrfenu" COLLECTION="nw41"UIMPORT" in Utilities Reference.726: The user you selected to remove does not exist. User: name.UIMPORTExplanation: An invalid username was specified.Action: Make sure that the username is valid. For information about UIMPORT, see "BOOK="utlrfenu" COLLECTION="nw41"UIMPORT" in Utilities Reference.727: User name was not removed. Error code: codeUIMPORTAction: Make sure the user has the appropriate rights to perform the specified task. For information about UIMPORT, see "BOOK="utlrfenu" COLLECTION="nw41"UIMPORT" in Utilities Reference728: The home directory path name specified contains illegal characters.UIMPORTExplanation: The home directory path specified in the control file contains characters that are not allowed by the file system.Action: Modify the home directory path control parameter in the control file. For information about UIMPORT, see "BOOK="utlrfenu" COLLECTION="nw41"UIMPORT" in Utilities Reference.PAGENUM=1288 ID="BP1282"730: The directory user's_home_object already exists.UIMPORTExplanation: UIMPORT tried to create a home directory that has already been created.Action: Make sure that the username and directory path are correct. For information about UIMPORT, see "BOOK="utlrfenu" COLLECTION="nw41"UIMPORT" in Utilities Reference. If the problem persists, contact your Novell Authorized Reseller.732: This utility was unable to create the new path specified_home_directory. DOS Error code: code.UIMPORTExplanation: A new home directory path could not be created. The reason is unknown; it could be an internal program error.Action: Make sure the user has Supervisor or Create rights. Also specified the correct path in the control file. Then try again. For information about UIMPORT, see "BOOK="utlrfenu" COLLECTION="nw41"UIMPORT" in Utilities Reference. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.734: You do not have sufficient rights to create the directory.UIMPORTExplanation: The user does not have the necessary rights to create the directory.Action: Make sure the user has appropriate user access rights. For information about UIMPORT, see "BOOK="utlrfenu" COLLECTION="nw41"UIMPORT" in Utilities Reference.736: The specified volume does not exist: name.UIMPORTExplanation: A volume that does not exist was specified when trying to add a trustee to a directory. Action: Modify the Volume control parameter in the control file. For information about UIMPORT, see "BOOK="utlrfenu" COLLECTION="nw41"UIMPORT" in Utilities Reference.738: You do not have sufficient rights to modify this user.UIMPORTExplanation: The user does not have the appropriate rights to modify the specified user.Action: Make sure the user has appropriate user access rights. For information about UIMPORT, see "BOOK="utlrfenu" COLLECTION="nw41"UIMPORT" in Utilities Reference.PAGENUM=1289 ID="BP1283"740: This utility cannot change the membership list. Error code: code.UIMPORTExplanation: The membership list could not be changed. The reason is unknown; it could be an internal program error.Action: Make sure that the group exists and that the user has necessary rights to change the membership list. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.742: An error occurred while adding the username to the Group member property. Error code: code.UIMPORTExplanation: An error occurred when UIMPORT tried to add a username to a group member property. This could be an internal error.Action: If the problem persists, contact your Novell Authorized Reseller.744: This utility could not create all properties associated with this user.UIMPORTExplanation: UIMPORT was unable to create all the properties desired for this user. The reason is unknown; it could be an internal error.Action: If the problem persists, contact your Novell Authorized Reseller.745: Error modifying the group membership property for user name. Group name may not exist.UIMPORTAction: Make sure the user has the appropriate rights to perform the specified task. For information about UIMPORT, see "BOOK="utlrfenu" COLLECTION="nw41"UIMPORT" in Utilities Reference.750: You must be supervisor equivalent to modify volume space restrictions on volume name.UIMPORTAction: If appropriate, make the user Supervisor equivalent. For information about UIMPORT, see "BOOK="utlrfenu" COLLECTION="nw41"UIMPORT" in Utilities Reference.760: An error occurred attempting to modify the volume restrictions. Error code: codeUIMPORTAction: Make sure the user has the appropriate rights to perform the specified task. For information about UIMPORT, see "BOOK="utlrfenu" COLLECTION="nw41"UIMPORT" in Utilities Reference. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A.PAGENUM=1290 ID="BP1284"765: An error occurred attempting to get your effective rights for object name. Error code: codeUIMPORTAction: Make sure the user has the appropriate rights to perform the specified task. Make sure the specified user name is a valid user. For information about UIMPORT, see "BOOK="utlrfenu" COLLECTION="nw41"UIMPORT" in Utilities Reference. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A.770: Volume name on server name is not in your DS tree. You can't set volume restrictions with this utility on a pre-4.0 server.UIMPORTAction: Make sure the user is trying to perform the specified task on a NetWare 4.x server. Make sure the volume and server are valid in the specified NetWare Directory Services tree. For information about UIMPORT, see "BOOK="utlrfenu" COLLECTION="nw41"UIMPORT" in Utilities Reference.775: Volume name is not on server name.UIMPORTAction: Make sure the specified volume name is a valid volume on the specified server. For information about UIMPORT, see "BOOK="utlrfenu" COLLECTION="nw41"UIMPORT" in Utilities Reference.780: This utility can't attach to the server associated with volume name.UIMPORTAction: Make sure the specified volume name is a valid volume on the specified server. Make sure the user has the appropriate rights to attach to the server. For information about UIMPORT, see "BOOK="utlrfenu" COLLECTION="nw41"UIMPORT" in Utilities Reference.785: An error occurred attempting to get the volume number for volume name on server name. Error code: codeUIMPORTExplanation: An internal error probably occurred.Action: Make sure the specified server and volume are valid. For information about UIMPORT, see "BOOK="utlrfenu" COLLECTION="nw41"UIMPORT" in Utilities Reference.790: An error occurred in NWDSWhoAmI. Error code: codeUIMPORTAction: See message IDREF="FM92553""991: An error occurred in function_name. Error code: code." in Appendix C.PAGENUM=1291 ID="BP1285"800: This utility cannot allocate sufficient memory for the Directory Services buffer.UIMPORTExplanation: The computer does not have enough memory available to complete the user import operation.Explanation: See "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network. For information about UIMPORT, see "BOOK="utlrfenu" COLLECTION="nw41"UIMPORT" in Utilities Reference.822: An error occurred in NWDSPutAttrVal. Error code: code.UIMPORTExplanation: An internal system error has probably occurred.Action: Try the operation again. Make sure that no associated problems have occurred (such as the network going down, a connection being lost, or previous errors having occurred and been ignored). For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A. If the problem persists, contact your Novell Authorized Reseller.826: The VLMs are not loaded.UIMPORTExplanation: The computer cannot execute this import utility until the VLM files are loaded.Action: Reboot the computer and load the VLM files. Then try again.828: You have added a value for the password expiration interval which is less than 1 or greater than 365. This may cause login problems when the password expiration time expires. A value of 40 has been added to the password expiration interval property.UIMPORTAction: Make sure to enter a value for this property between 1 and 365. For information about UIMPORT, see "BOOK="utlrfenu" COLLECTION="nw41"UIMPORT" in Utilities Reference.900: An internal application error has occurred. Error code: codeUIMPORTAction: See message IDREF="FM92553""991: An error occurred in function_name. Error code: code." in Appendix C.906: The Unicode files cannot be found.UIMPORTAction: See message IDREF="FM62778""973: The Unicode table files cannot be found in the NLS directory or in the search path. Code page: number Country: number" in Appendix C.907: The SCHEMA.XLT file can't be found.UIMPORTAction: See message IDREF="FM48610""907: This utility cannot open the translation table SCHEMA.XLT." in Appendix C.PAGENUM=1292 ID="BP1286"908: The SCHEMA.XLT file is an incorrect format and can't be used.UIMPORTAction: Copy a correct version of the SCHEMA.XLT file into the PUBLIC directory.909: The SCHEMA.XLT file is an incorrect version. Version number is required.UIMPORTAction: Copy a correct version of the SCHEMA.XLT file into the PUBLIC directory.920: This utility was unable to allocate <number> bytes of memory.UIMPORTAction: See message IDREF="FM30331""920: This utility was unable to allocate number bytes of memory." in Appendix C.923: An unexpected error has occurred. Error code: <code>.UIMPORTAction: See message IDREF="FM30182""923: An unexpected error has occurred. Error code: code." in Appendix C.970: The attempt to open the Unicode table files failed.UIMPORTAction: See message IDREF="FM15675""970: The attempt to open the Unicode table files failed." in Appendix C.971: The workstation does not have enough memory to load the Unicode table files.UIMPORTAction: See message IDREF="FM55341""971: The workstation does not have enough memory to load the Unicode table files." in Appendix C.972: Access to the Unicode table files was denied.UIMPORTAction: See message IDREF="FM90152""972: Access to the Unicode table files was denied." in Appendix C.973: The Unicode table files cannot be found in the NLS directory or in the search path. Code page: <number>  Country:  <number>UIMPORTAction: See message IDREF="FM62778""973: The Unicode table files cannot be found in the NLS directory or in the search path. Code page: number Country: number" in Appendix C.974: The Unicode table files are corrupt.UIMPORTAction: See message IDREF="FM63405""974: The Unicode table files are corrupt." in Appendix C.975: The Unicode table files cannot be opened because there are already too many open files. Close some files or modify your CONFIG.SYS file.UIMPORTAction: See message IDREF="FM49793""975: The Unicode table files cannot be opened because there are already too many open files. Close some files or modify your CONFIG.SYS file." in Appendix C.PAGENUM=1293 ID="BP1287"991: An error occurred in NWDSOpen Stream. The login script cannot be opened. Error code: code.UIMPORTAction: See message IDREF="FM92553""991: An error occurred in function_name. Error code: code." in Appendix C.991: An error occurred in NWDSModifyObject. Error code: code. User: name Attribute: value Value: valueUIMPORTAction: See message IDREF="FM92553""991: An error occurred in function_name. Error code: code." in Appendix C.991: An error occurred in NWDSMapNameToID. This may mean that the skulker has not put object name on server name yet. Error code: code.UIMPORTAction: See message IDREF="FM92553""991: An error occurred in function_name. Error code: code." in Appendix C.991: An error occurred in NWDSSetContext. The user does not have a DS connection. Error code: code.UIMPORTAction: See message IDREF="FM92553""991: An error occurred in function_name. Error code: code." in Appendix C.991: An error occurred in <function_name>. Error code: <code>.UIMPORTAction: See message IDREF="FM92553""991: An error occurred in function_name. Error code: code." in Appendix C.998: The message file found (<utility_name>.MSG) is an incorrect version. The correct version is <number>. See your network supervisor for assistance.UIMPORTAction: See message IDREF="FM91957""998: The message file found (utility_name.MSG) is an incorrect version. The correct version is number. See your network supervisor for assistance." in Appendix C.999: The message file for this utility cannot be found.UIMPORTAction: See message IDREF="FM69424""999: The message file for this utility cannot be found." in Appendix C.PAGENUM=1294 ID="BP1288"UPS1: Unable to get resource tags.UPSExplanation: A memory allocation error occurred during initialization of the UPS NLM program.Action: Try loading again. If the problem persists, see "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.2: Hardware driver must be loaded before uninterruptible power supply will be activated.UPSExplanation: A mismatch exists between the UPS and the UPS driver. The UPS cannot use the built-in drivers, or the wrong external driver was loaded.Action: Load the correct external UPS hardware driver, or unload the UPS NLM program and reload with the correct UPS type specified on the command line (for example, type=DCB). For information, see "BOOK="utlrfenu" COLLECTION="nw41"UPS" in Utilities Reference.3: Attempt to load hardware driver failed. You must manually load a hardware driver before uninterruptible power supply will be activated.UPSExplanation: The UPS hardware driver failed. This problem could result from having the wrong type of hardware driver or from using invalid configuration options for the hardware driver being specified.Action: Unload the UPS NLM program, and reload it with the correct type of hardware drivers and with the correct configuration parameters. For information, see "BOOK="utlrfenu" COLLECTION="nw41"UPS" in Utilities Reference.4: Another driver is already registered for the uninterruptible power supply.UPSExplanation: An external driver was just loaded to control the UPS hardware, but another driver was previously loaded or assigned to control the UPS hardware.Action: If the correct type of driver was selected, or if the correct driver was previously loaded, no action is required. If not, unload the loaded driver or UPS NLM program and try the operation again, specifying the correct type of UPS hardware and the correct configuration parameters. For information, see "BOOK="utlrfenu" COLLECTION="nw41"UPS" in Utilities Reference.5: Unable to open parameter screen.UPSExplanation: A memory allocation error occurred during initialization of the UPS NLM program.Action: Try loading again. If the problem persists, see "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.PAGENUM=1295 ID="BP1289"6: The uninterruptible power supply port you specified is invalid.UPSExplanation: The specified port configuration parameter is invalid, or the hardware is not configured to use the port specified.Action: Try again using the correct port configuration parameter. For information, see "BOOK="utlrfenu" COLLECTION="nw41"UPS" in Utilities Reference.7: Unable to register uninterruptible power supply hardware.UPSExplanation: The call to the operating system to register the hardware port address failed. The most common cause is that some other device is already registered for that address.Action: Determine whether any other hardware address is conflicting with the UPS address. If so, bring the server down and reconfigure the UPS monitoring hardware to use a different port address; then try loading the UPS NLM program again.8: Hardware driver is not loaded.UPSExplanation: This message is issued when the UPS STATUS or the UPS Time Utilities are used and no UPS hardware driver is loaded.Action: Load the UPS hardware driver. Or, unload the UPS NLM program, then reload it specifying the correct TYPE parameter. For information about UPS, see "BOOK="utlrfenu" COLLECTION="nw41"UPS" in Utilities Reference.9: Commercial power was off during uninterruptible power supply (UPS) installation. Check your commercial power lines or the UPS.UPSExplanation: When the UPS monitor was first loaded, it detected that normal power was already missing. The server is running on power from the battery.Action: Make sure the main power is, in fact, missing. If normal power is present, the UPS is not operating properly or the UPS is configured incorrectly (sometimes a jumper is used to set commercial power detection to positive logic or negative logic).10: Uninterruptible power supply battery is low. Repair or replace the battery.UPSExplanation: When the UPS monitor was first loaded, the battery low signal was detected. This usually means that the battery is getting weak (hence the suggestion to repair or replace the battery) or possibly that the battery has run down (power was lost and the server ran on power from the battery for a while) and has not yet had time to recharge.Action: If the battery has not simply been discharged and not yet recharged, the battery is probably going bad and needs to be serviced.PAGENUM=1296 ID="BP1290"11: Uninterruptible power supply (UPS) hardware configuration error was detected. Check for errors in your UPS hardware configuration settings.UPSExplanation: When the UPS monitor was first loaded, the hardware reported conflicting error states. The hardware board is not configured properly, or the UPS is reporting incorrect information.Action: Make sure the board is configured properly. If the problem persists, the UPS may need to be replaced.12: Commercial power has failed. Server name is running on battery power. The server will stay up for number minutes. Prepare users to log out.UPSExplanation: The main commercial power has failed, and the server is now running on power from the battery in the UPS. The UPS battery is good for the specified number of minutes. If commercial power is not restored in that amount of time, the server will be automatically shut down to prevent data loss.Action: None. This message is for information only. Users should save their files and log out to prevent possible data loss.13: Server name on battery power. number minutes of power remaining.UPSExplanation: This message is broadcast to all logged-in users when the UPS detects that commercial power is lost. This message is sent to workstations at the same time the previous message (message 12) is sent to the console.Action: None. This message is for information only. Users should save their files and log out to prevent possible data loss.14: Battery discharge time has almost expired. The file server will be shut down in one minute unless commercial power is restored.UPSExplanation: Commercial power has been lost, and the battery is gave up as well. The server is going down unless the commercial power is restored within the next minute.Action: Users should save their files and log out to prevent possible data loss.15: Battery power exhausted for server name. Log out!UPSExplanation: This message is sent to all logged-in users at the same time that the previous message (message 14) is sent to the console.Action: Users should save their files and log out now.PAGENUM=1297 ID="BP1291"16: Status cannot be read from uninterruptible power supply device.UPSExplanation: The current status of the UPS cannot be obtained. This occurs only if something is wrong with the UPS.Action: Have the UPS checked and repaired.17: Battery low on server name. Repair or replace.UPSExplanation: This message is sent to both the console and all logged-in users if commercial power is present but the low-battery signal is detected anyway.Action: Repair or replace the battery.18: Uninterruptible power supply mouse port could not be initialized.UPSExplanation: If the UPS is connected to the mouse port (typically only on a PS/2) and the mouse port could not be initialized properly, this message is sent to the console.Action: Try the operation again. If the problem persists, check the UPS configuration and the mouse port itself for proper operation.19: Uninterruptible power supply is shutting down server name. Commercial power has failed and the battery is too low.UPSExplanation: When the UPS monitor detects that commercial power has failed, it checks the battery to make sure it can run the server for at least some minimum amount of time. This message occurs when the UPS battery is almost depleted and is unable to sustain any extended server operation. In this situation, the server is being shut down immediately.Action: Make sure that the UPS has time to recharge (typically one to three hours). If the problem persists, have the UPS repaired or replaced.20: The battery power for server name is charging. The status is no longer low.UPSExplanation: Previously, the power state of the UPS battery was low, but the battery has recharged enough to no longer be low.Action: None. This message is for information only. The UPS is working correctly.21: The battery power for server name is complete.UPSExplanation: Previously, the power state of the UPS battery was charging, but the battery is now charged. The defined charge time has been reached.Action: None. This message is for information only. The UPS is working correctly.PAGENUM=1298 ID="BP1292"22: Commercial power restored for server name.UPSExplanation: Previously, the UPS was on battery power, but it is now on commercial power.Action: None. This message is for information only. The UPS is working correctly.PAGENUM=1299 ID="BP1293"VLM1: The message file name is invalid. The program cannot be loaded.VLMExplanation: The .MSG file is invalid. This problem could be the result of a corrupted file, a bad translation, or an outdated file version.Action: Update the .MSG file with a valid copy, or delete the file. The DOS Requester will use the default messages that are bound to the binary files.8: The VLM.EXE file is already loaded. VLM.EXE cannot be reloaded. If you want to load VLM.EXE with a different configuration, unload VLM.EXE first with the /U parameter and then try loading the VLM.EXE file.VLMExplanation: The VLM.EXE file is already loaded into memory. There cannot be two copies of the VLM.EXE file loaded in memory at one time.Action: If the VLM.EXE file is being reloaded in an attempt to reconfigure the VLMs already loaded, unload VLM.EXE using the /U parameter; then reload VLM.EXE.9: The VLM.EXE file is testing the VLMs.VLMExplanation: This message is used to show the progress the VLM.EXE file is making in configuring the VLMs to be loaded. Because this process can take a few seconds, the progress is displayed using a period (.) to indicate each VLM being tested.Action: None. This message is for information only.10: The conventional memory block for the EMS stack cannot be resized. The VLM.EXE file cannot be loaded. DOS memory is probably corrupted. Reboot your computer and then try to load the VLM.EXE again.VLMExplanation: This error indicates that the DOS memory chain has been corrupted.Action: Because this error indicates that the DOS memory chain has been corrupted, it is unsafe to continue operating the computer. The best solution is to reboot the computer; then try to load the VLM.EXE.PAGENUM=1300 ID="BP1294"11: There is insufficient memory to load the VLMs. The VLM.EXE file cannot be loaded. Reconfigure the VLMs to be loaded in the NET.CFG file and then try to load the VLM.EXE file.VLMExplanation: The VLM.EXE file can use expanded memory (EMS), extended memory (XMS), or conventional memory. This message indicates that there is not enough of any one of these to support the VLMs to be loaded.Action: Increase the available memory. (This includes expanded memory and extended memory.) Some memory managers provide dynamic memory pools by converting extended memory to expanded memory or vice versa. Other memory managers require you to configure the amount and type of memory desired. In either case, make sure enough memory of one type is available to support the VLM programs to be loaded or reduce the number of VLM programs to be loaded. You can do this by using the "VLM= statement" in the NET.CFG file or by renaming the VLM programs that are not desired.15: An invalid command line parameter was specified.VLMExplanation: The VLM.EXE file was loaded with an invalid command line parameter.Action: Run the VLM.EXE file with the /? parameter (for example: VLM /?) to display the valid parameters; then load the VLM.EXE file with a valid command line parameter.16: The VLM.EXE file version is currently loaded.VLMExplanation: This message is displayed during the VLM.EXE file diagnostics display. (The diagnostics display is accessed by running VLM.EXE with the /D parameter.) This message indicates that the VLM.EXE file of the given version is currently loaded into memory.Action: None. This message is for information only.17: The VLM.EXE file is not currently loaded.VLMExplanation: This message is displayed during the VLM.EXE file diagnostics display. (The diagnostics display is accessed by running VLM.EXE with the /D parameter.) This message indicates that the VLM.EXE file is not currently loaded into memory.Action: None. This message is for information only.30: A task switcher has been detected in memory. The VLM.EXE file cannot be loaded under a task switcher. Exit the task switcher; then try again.VLMExplanation: The DOS Requester cannot function properly when loaded after a task switcher. A task switcher has been loaded. (Task switchers include DR DOS TaskMax, MS DOS 5.0 DOSSHELL, and MS Windows 3.1 in standard mode.)Action: Exit the task switcher before loading the DOS Requester.PAGENUM=1301 ID="BP1295"31: Network error on server name. Check network cabling or server status.VLMExplanation: This is a critical communications error between the workstation and the file server. This error may also appear as "General failure on device NETWORK." A communications error can be caused by a hardware or software failure.Action: Make sure the network cable is connected properly and the file server is operating. If the problem persists, contact your Novell Authorized Reseller.32: The VLM.EXE file is not loaded. VLM.EXE cannot be unloaded.VLMExplanation: An attempt was made to unload the VLM.EXE file using the /U parameter. This message indicates that the VLM.EXE file is not currently loaded in memory.Action: None. This message is for information only.33: The loaded VLM.EXE file has a different version. VLM.EXE cannot be unloaded. Make sure the VLM.EXE file you are using has the same version number and then try to unload VLM.EXE.VLMExplanation: An attempt was made to unload the VLM.EXE file using the /U parameter. This message indicates that the version of the VLM.EXE file that is currently loaded in memory is not the same version as the one being used to unload VLM.EXE. This is unsafe and is therefore not allowed by the VLM.EXE file.Action: Unload VLM.EXE from the computer's memory using the same version that was used to load the VLM.EXE to memory. If you can not unload the VLM.EXE from memory, you can remove it (and all other programs in memory) by rebooting the computer.34: The loaded VLM.EXE file indicates it is unsafe to execute an unload for VLM number number. VLM.EXE will not be unloaded. Unload all memory resident programs (TSRs) that were loaded after the VLM.EXE file and then try to unload VLM.EXE.VLMExplanation: An attempt was made to unload the VLM.EXE file using the /U parameter. This message indicates that the loaded VLM.EXE file did not unload. This usually is caused by interrupts being used after the VLM.EXE file was loaded. Another possible cause is that a VLM program is in an unsafe state to unload.Action: Unload all the TSR (terminate-and-stay-resident) programs that were loaded after the VLM.EXE file; then try to unload VLM.EXE. Make sure all loaded VLM programs are in a safe state for unloading.36: The VLM.EXE file cannot use expanded memory (EMS). VLM.EXE will use an alternate memory scheme.VLMPAGENUM=1302 ID="BP1296"Explanation: An attempt was made to load the VLM.EXE file in expanded memory (EMS) using the /ME parameter. This message indicates that no LIM EMS 4.0 expanded memory manager is present or that not enough expanded memory is available to load the VLM programs. The VLM.EXE file will attempt to use an alternate type of memory, extended memory (XMS) or conventional memory, before failing to load.Action: None. The VLM.EXE file will try to use an alternate memory type. To avoid this message the next time the VLM.EXE file is loaded, make sure an expanded memory manager is loaded with enough memory to support the VLM programs desired or do not specify the /ME parameter when loading VLM.EXE.37: The VLM.EXE file is using expanded memory (EMS).VLMExplanation: This message indicates that the VLM.EXE file will be loading the VLM programs into expanded memory (EMS).Action: None. This message is for information only.38: The VLM.EXE file cannot use extended memory (XMS). VLM.EXE will use an alternate memory scheme.VLMExplanation: An attempt was made to load the VLM.EXE file in extended memory (XMS) using the /MX parameter. This message indicates that no XMS 2.0 extended memory manager is present, or not enough extended memory is available to load the VLM programs. The VLM.EXE file will attempt to use an alternate type of memory, expanded memory (EMS) or conventional memory, before failing to load.Action: None. The VLM.EXE file will try to use an alternate memory type. To avoid this message the next time the VLM.EXE file is loaded, make sure an extended memory manager is loaded with enough memory to support the VLM programs desired or do not specify the /MX parameter when loading VLM.EXE.39: The VLM.EXE file is using extended memory (XMS).VLMExplanation: This message indicates that the VLM.EXE file will be loading the VLM programs into extended memory (XMS).Action: None. This message is for information only.40: The VLM.EXE file cannot use conventional memory. VLM.EXE will use an alternate memory scheme.VLMExplanation: An attempt was made to load the VLM.EXE file in conventional memory using the /MC parameter. This message indicates that not enough conventional memory is available to load the VLM programs. The VLM.EXE file will attempt to use an alternate type of memory, expanded memory (EMS) or extended memory (XMS), before failing to load.Action: None. The VLM.EXE file will try to use an alternate memory type. To avoid this message the next time the VLM.EXE file is loaded, make sure enough conventional memory is available to support the VLM programs desired or do not specify the /MC parameter when loading VLM.EXE.PAGENUM=1303 ID="BP1297"41: The VLM.EXE file is using conventional memory.VLMExplanation: This message indicates that the VLM.EXE file will be loading the VLM programs into conventional memory.Action: None. This message is for information only.42: There is a missing or invalid value for `parameter' on line number of the configuration file. This entry will be ignored. Correct the line specified in the configuration file before continuing.VLMExplanation: The configuration file contains a configuration keyword that has an invalid parameter or that does not specify a parameter. This invalid line will be ignored by the configuration process.Action: None. This line will be ignored. To avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the message.43: There is a missing or invalid ON/OFF value for `parameter' on line number of the configuration file. This entry will be ignored. Correct the line specified in the configuration file before continuing.VLMExplanation: The configuration file contains a configuration keyword that is defined to use an "ON" or "OFF" parameter, but a different parameter or no parameter has been specified. This invalid line will be ignored by the configuration process.Action: None. This line will be ignored. To avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the message.44: There is an invalid string length specified for `parameter' on line number of the configuration file. This entry will be ignored. Correct the line specified in the configuration file before continuing.VLMExplanation: The configuration file contains a configuration keyword that is defined to use a string of a specified minimum and/or maximum length; but a string has been entered that does not fit the specified limits. This invalid line will be ignored by the configuration process.Action: None. This line will be ignored. To avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the message.PAGENUM=1304 ID="BP1298"45: The parameter specified for the following option was out of range and has been adjusted.VLMExplanation: A configurable parameter has been configured too high or too low to be valid. The parameter is specified on the line following the message.Action: Correct the parameter specified in the NET.CFG file. For information on NET.CFG parameters, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.46: A duplicate VLM ID was found during VLM load test. The file will not be loaded. Check the VLM= and USE DEFAULTS= parameter specified in the NET.CFG file before continuing.VLMExplanation: The VLM programs for the DOS Requester have been improperly configured to include two VLM programs with the same VLM ID. This can be caused by including a VLM program twice in the "VLM=" list or by a VLM program that has attempted to reuse a VLM ID assigned to a different VLM program.Action: Make sure no duplicates of the VLM= list are in the NET.CFG file. Make sure the "USE DEFAULTS=" parameter is set to "OFF" in the NET.CFG file. For information on NET.CFG parameters, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.47: A file server could not be found. Check the network cabling and the server's status before continuing.VLMExplanation: No file server was found when attempting to build an initial connection. This could be caused by one of the following: an improperly configured network board, an improperly configured IPX, a disconnected network cable, or an attempt to load the DOS Requester before a file server has been initialized.Action: Try one or more of the following:MARK=BULLETMake sure the network board is properly configured by checking the network board's settings and the NET.CFG file settings. For information on NET.CFG parameters, see "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference" in NetWare Client for DOS and MS Windows Technical Reference.Make sure the IPX is configured to be bound properly to the correct LAN driver.Check the network cabling.Make sure a server is up and running before attempting to load the DOS Requester.Note: If the server has not been loaded properly, attempting to access an invalid drive from the workstation will attempt to build an initial connection again.PAGENUM=1305 ID="BP1299"48: The preferred connection could not be established. Check the PREFERRED SERVER and PREFERRED TREE statements specified in the NET.CFG file. Also check the server's status before continuing.VLMExplanation: An attempt was made to connect to a specific Directory tree or server. This attempt failed. The server or tree is not operating at this time, or in the preferred server case, it may be unknown by the initial server's bindery.Action: Make sure the spelling of the preferred server or tree is correct. Make sure the server and tree is operating. Finally, make sure no restrictions have been made at the server to isolate the server from the network.60: There is an unrecognized entry `entry' on line number of the configuration file. This entry will be ignored. Correct the line specified in the configuration file before continuing.VLMExplanation: The configuration file contains a configuration keyword under a header where it does not belong. This invalid line will be ignored by the configuration process.Action: This line will be ignored. To avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the message.PAGENUM=1306 ID="BP1300"VREPAIR10: Unable to get resource tags.VREPAIRExplanation: There is not enough server memory available to run VREPAIR.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.11: Unable to open VREPAIR status screen.VREPAIRExplanation: There is not enough server memory available to run VREPAIR.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.12: Unable to open VREPAIR error screen.VREPAIRExplanation: There is not enough server memory available to run VREPAIR.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.14: Unable to allocate memory for VREPAIR process stack.VREPAIRExplanation: There is not enough server memory available to run VREPAIR.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.208: Error writing to error log file name. Message: "message" not written to file. Error log file closed.VREPAIRExplanation: VREPAIR was unable to write a message to the log file. This is usually caused by a failure of the log file's disk media (for example, removing the floppy diskette) or by running out of space on the log file's media.Action: If you want a log file, then stop VREPAIR using the F1 option, fix the media problem, and then run VREPAIR again. VREPAIR will continue to repair the volume if you do nothing.209: Error writing to error log file name. Error log file closed.VREPAIRExplanation: VREPAIR was unable to write a message to the log file. This is usually caused by a failure of the log file's disk media (for example, removing the floppy diskette) or by running out of space on the log file's media.Action: If you want a log file, then stop VREPAIR using the F1 option, fix the media problem, and then run VREPAIR again. VREPAIR will continue to repair the volume if you do nothing.PAGENUM=1307 ID="BP1301"279: Unable to allocate memory to read mirror FAT block sequence number.VREPAIRExplanation: VREPAIR needs more memory to complete the volume repair.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.301: Unable to allocate memory to record needed FAT entry correction. Try using the Save Changes Immediately option.VREPAIRExplanation: VREPAIR needs more memory to complete the volume repair.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.302: Unable to allocate memory to record needed FAT entry correction.VREPAIRExplanation: VREPAIR needs more memory to complete the volume repair.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.304: Unable to allocate memory to record needed FAT entry correction. Try using the Save Changes Immediately option.VREPAIRExplanation: VREPAIR needs more memory to complete the volume repair.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.305: Unable to allocate memory to record needed FAT entry correction.VREPAIRExplanation: VREPAIR needs more memory to complete the volume repair.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.425: Unable to get enough memory to set up directory cache buffers.VREPAIRExplanation: VREPAIR needs more memory to complete the volume repair.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.427: Unable to get enough memory to set up directory hash tables.VREPAIRExplanation: VREPAIR needs more memory to complete the volume repair.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.441: Unable to allocate memory to record needed directory entry correction. Try using the Write Changes Immediately To Disk option.VREPAIRExplanation: VREPAIR needs more memory to complete the volume repair.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.PAGENUM=1308 ID="BP1302"442: Unable to allocate memory to record needed directory entry correction.VREPAIRExplanation: VREPAIR needs more memory to complete the volume repair.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.444: Unable to allocate memory to record needed directory entry correction. Try using the Write Changes Immediately To Disk option.VREPAIRExplanation: VREPAIR needs more memory to complete the volume repair.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.462: This VREPAIR is not compatible with this OS.VREPAIRExplanation: This VREPAIR version is not compatible with the current NetWare operating system. As changes are made to the NetWare file system, you must change VREPAIR.Action: Load a version of VREPAIR that is compatible with the operating system.677: More than 999,999 new directory names have been generated.VREPAIRExplanation: During the process of volume repair, VREPAIR sometimes needs to generate a new unique name for files and directories that have invalid or conflicting names. This error occurs when VREPAIR has run out of unique names for use during volume repair. The problem occurs only when the volume is badly damaged.Action: If the volume is this badly damaged, try restoring it from a backup. If you do not have a backup, then try using a volume editor and rename the files manually.713: More than 999,999 new file names have been generated.VREPAIRExplanation: During the process of volume repair, VREPAIR sometimes needs to generate a new unique name for files and directories that have invalid or conflicting names. This error occurs when VREPAIR has run out of unique names for use during volume repair. The problem occurs only when the volume is badly damaged.Action: If the volume is this badly damaged, try restoring it from a backup. If you do not have a backup, then try using a volume editor and rename the files manually.ID="FM17531"766: Unable to read directory entry number which was previously read.VREPAIRExplanation: Volume data that VREPAIR previously read is currently not available. This problem is usually caused by a major hardware failure.Action: Try to get the disk hardware back in working condition. See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network. Then run VREPAIR again.PAGENUM=1309 ID="BP1303"767: Unable to read directory entry number which was previously read.VREPAIRAction: See message IDREF="FM17531""766: Unable to read directory entry number which was previously read."768: Unable to read directory entry number which was previously read.VREPAIRAction: See message IDREF="FM17531""766: Unable to read directory entry number which was previously read."769: Trustee entry was not found in directory trustee chain as expected.VREPAIRExplanation: Volume data that VREPAIR previously read is currently not available. This problem is usually caused by a major hardware failure.Action: Try to get the disk hardware back in working condition. See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network. Then run VREPAIR again.770: Unable to read directory entry number which was previously read.VREPAIRExplanation: Volume data that VREPAIR previously read is currently not available. This problem is usually caused by a major hardware failure.Action: Try to get the disk hardware back in working condition. See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network. Then run VREPAIR again.771: Trustee entry was not found in file trustee chain as expected.VREPAIRExplanation: Volume data that VREPAIR previously read is currently not available. This problem is usually caused by a major hardware failure.Action: Try to get the disk hardware back in working condition. See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network. Then run VREPAIR again.810: The name space list for entry number could not be corrected. To complete repairs, save changes and run VREPAIR again.VREPAIRExplanation: The name space list for an entry could not be repaired. VREPAIR needs to start over to correct the problem.Action: Save the changes you have made so far; then run VREPAIR again.828: Unable to allocate memory to record needed directory corrections. Try using the Write Changes Immediately To Disk option.VREPAIRExplanation: VREPAIR needs more memory to complete the volume repair.Action: Increase the available memory. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.PAGENUM=1310 ID="BP1304"829: Unable to allocate memory to record needed directory corrections.VREPAIRExplanation: VREPAIR needs more memory to complete the volume repair.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.831: Unable to allocate memory to record needed directory corrections. Try using the Write Changes Immediately To Disk option.VREPAIRExplanation: VREPAIR needs more memory to complete the volume repair.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.845: More than 999,999 new MAC names have been generated.VREPAIRExplanation: During the process of volume repair, VREPAIR sometimes needs to generate a new unique name for files and directories that have invalid or conflicting names. This error occurs when VREPAIR has run out of unique names for use during volume repair. The problem occurs only when the volume is badly damaged.Action: If the volume is this badly damaged, try restoring it from a backup. If you do not have a backup, then try using a volume editor and rename the files manually.849: More than 999,999 new OS/2 names have been generated.VREPAIRExplanation: During the process of volume repair, VREPAIR sometimes needs to generate a new unique name for files and directories that have invalid or conflicting names. This error occurs when VREPAIR has run out of unique names for use during volume repair. The problem occurs only when the volume is badly damaged.Action: If the volume is this badly damaged, try restoring it from a backup. If you do not have a backup, then try using a volume editor and rename the files manually.871: Unable to read directory entry number which was previously read.VREPAIRExplanation: Volume data that VREPAIR previously read is currently not available. This problem is usually caused by a major hardware failure.Action: Try to get the disk hardware back in working condition. See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network. Then run VREPAIR again.PAGENUM=1311 ID="BP1305"WHOAMI100: Control characters are not allowed in the command line.WHOAMIExplanation: Control characters (characters that are pressed in combination with the MOREINFO="NONE"<Ctrl> key) are invalid command line parameters.Action: Retype the command. For information about WHOAMI, see "BOOK="utlrfenu" COLLECTION="nw41"WHOAMI" in Utilities Reference.230: An error occurred during WHOAMI's attempt to get the connection status.WHOAMIExplanation: If the user is not on a NetWare 4 server, or if NetWare Directory Services is not present, WHOAMI cannot get the connection status of the connections the user is currently attached to.Action: Try WHOAMI again. If the problem persists, contact your Novell Authorized Reseller.240: An error occurred during WHOAMI's attempt to get the server information.WHOAMIExplanation: WHOAMI was unable to find out how many volumes this server can support. WHOAMI has terminated.Action: Try WHOAMI again. If the problem persists, contact your Novell Authorized Reseller.250: An error occurred during WHOAMI's attempt to get the effective rights for name.WHOAMIExplanation: WHOAMI was unable to get the effective rights for the user named in the message.Action: Try WHOAMI again. If the problem persists, contact your Novell Authorized Reseller.260: The total path length cannot exceed 256 characters (not including the server and volume names).WHOAMIExplanation: WHOAMI provides information about subdirectories that the user has access to. However, in this instance, the path searched was more than 256 characters long. WHOAMI will continue.Action: Specify a path of no more than 256 characters.270: You are not logged in or authenticated to an NDS server.WHOAMIAction: Make sure you log in to or authenticate to an NDS server.PAGENUM=1312 ID="BP1306"500: This utility was unable to allocate sufficient memory for the Directory Services attribute buffer.WHOAMIExplanation: The workstation does not have enough memory to run the utility.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network.510: This utility was unable to allocate sufficient memory for the Directory Services object information buffer.WHOAMIExplanation: The workstation does not have enough memory to run the utility.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network.520: An error occurred during attempt to initialize the Directory Services request buffer.WHOAMIExplanation: WHOAMI was unable to initialize a request buffer for use in a later call. WHOAMI has terminated.Action: Try WHOAMI again. If the problem persists, contact your Novell Authorized Reseller.530: An error occurred during attempt to put an attribute into the request buffer.WHOAMIExplanation: WHOAMI was unable to put NetWare Directory Services attributes into a buffer and has terminated.Action: Try WHOAMI again. If the problem persists, contact your Novell Authorized Reseller.560: An error has occurred during WHOAMI's attempt to retrieve the NDS object name.WHOAMIExplanation: WHOAMI was unable to retrieve a NetWare Directory Services object's common name and has terminated. WHOAMI will continue.Action: Make sure the object name specified is correct. Try WHOAMI again. If the problem persists, contact your Novell Authorized Reseller.900: An internal application error code has occurred.WHOAMIAction: None. This message is for information only.901: You are not attached to the specified server.WHOAMIAction: See message IDREF="FM84261""901: You are not attached to the specified server." in Appendix C.902: You are not attached to any servers.WHOAMIAction: See message IDREF="FM84261""901: You are not attached to the specified server." in Appendix C.PAGENUM=1313 ID="BP1307"903: The command line syntax is invalid.WHOAMIAction: See message IDREF="FM18860""903: The command line syntax is invalid." in Appendix C.917: This utility was unable to set the context.WHOAMIAction: See message IDREF="FM32126""917: This utility was unable to set the context." in Appendix C.919: This utility could not find a network connection.WHOAMIAction: See message IDREF="FM68419""919: This utility could not create a connection list. Error code." in Appendix C.920: This utility was unable to allocate <number> bytes of memory.WHOAMIAction: See message IDREF="FM30331""920: This utility was unable to allocate number bytes of memory." in Appendix C.970: The attempt to open the Unicode table files failed.WHOAMIAction: See message IDREF="FM15675""970: The attempt to open the Unicode table files failed." in Appendix C.971: The workstation does not have enough memory to load the Unicode table files.WHOAMIAction: See message IDREF="FM55341""971: The workstation does not have enough memory to load the Unicode table files." in Appendix C.972: Access to the Unicode table files was denied.WHOAMIAction: See message IDREF="FM90152""972: Access to the Unicode table files was denied." in Appendix C.973: The Unicode table files cannot be found in the NLS directory or in the search path. Code page: <number>  Country:  <number>WHOAMIAction: See message IDREF="FM62778""973: The Unicode table files cannot be found in the NLS directory or in the search path. Code page: number Country: number" in Appendix C.974: The Unicode table files are corrupt.WHOAMIAction: See message IDREF="FM63405""974: The Unicode table files are corrupt." in Appendix C.975: The Unicode table files cannot be opened because there are already too many open files. Close some files or modify your CONFIG.SYS file.WHOAMIAction: See message IDREF="FM49793""975: The Unicode table files cannot be opened because there are already too many open files. Close some files or modify your CONFIG.SYS file." in Appendix C.PAGENUM=1314 ID="BP1308"998: The message file found (<utility_name>.MSG) is an incorrect version. The correct version is <number>. See your network supervisor for assistance.WHOAMIAction: See message IDREF="FM91957""998: The message file found (utility_name.MSG) is an incorrect version. The correct version is number. See your network supervisor for assistance." in Appendix C.999: The message file for this utility cannot be found.WHOAMIAction: See message IDREF="FM69424""999: The message file for this utility cannot be found." in Appendix C.PAGENUM=1315 ID="BP1309"WSUPDATE001: You cannot enter both a volume or drive and the /ALL or /LOCAL option. Command line is: command.WSUPDATEExplanation: The user cannot copy to a specified drive and then specify all drives.Action: Copy to a specific drive or to all drives.005: This utility cannot create the context.WSUPDATEExplanation: The workstation may not have enough available memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network.007: This utility cannot get the context.WSUPDATEExplanation: The user is not connected to a NetWare Directory Services server.Action: Use LOGIN to attach to a NetWare Directory Services server; then retry the operation.010: This utility cannot interpret command: command which is in the configuration file: name.WSUPDATEExplanation: An invalid command was entered in the configuration file.Action: Correct the command in the configuration file. To access online help information, type "WSUPDATE /?", or see "BOOK="utlrfenu" COLLECTION="nw41"WSUPDATE" in Utilities Reference.020: The command is in the configuration file name.WSUPDATEExplanation: This message is associated with another error. A command entered on the command line is already found in the configuration file.Action: To access online help information, type "WSUPDATE /?", or see "BOOK="utlrfenu" COLLECTION="nw41"WSUPDATE" in Utilities Reference.024: The configuration filename is too long.WSUPDATEExplanation: More than eight characters were used for the configuration filename, or more than three characters were used for the extension.Action: Make sure the name is no longer than eight characters, and that the extension is no longer than three characters. To access online help information, type "WSUPDATE /?", or see "BOOK="utlrfenu" COLLECTION="nw41"WSUPDATE" in Utilities Reference.PAGENUM=1316 ID="BP1310"030: Available disk space is insufficient to copy the new file.WSUPDATEExplanation: The area into which the file was being copied is out of disk space.Action: Do one or both of the following:MARK=BULLETIf the disk space is restricted, increase the amount of disk space that can be used.If no disk space is remaining, remove old or unused files from the volume.035: Control characters cannot be used in the command parameters.WSUPDATEExplanation: Control characters (characters that are pressed in combination with the MOREINFO="NONE"<Ctrl> key) are invalid command line parameters.Action: Retype the command without the control characters. To access online help information, type "WSUPDATE /?", or see "BOOK="utlrfenu" COLLECTION="nw41"WSUPDATE" in Utilities Reference.040: The existing rename file cannot be deleted.WSUPDATEExplanation: One of the following problems could be keeping the file from being copied over:MARK=BULLETThe file has the Copy Inhibit or Delete Inhibit bit set.The user does not have the appropriate rights to rename the file.Action: Make sure the user the appropriate rights to delete the file.050: Access rights to the destination file cannot be changed. File: nameWSUPDATEExplanation: The user does not have rights to change the file attributes from Read Only to Read Write.Action: If appropriate, grant the user the appropriate rights, or change the file's attributes.060: The file mode for the destination file cannot be found. File: nameWSUPDATEExplanation: WSUPDATE could not get the attributes for the destination file.Action: Make sure the file is in the correct path and that the user has rights; then retry the operation.065: The destination path is too long.WSUPDATEExplanation: The workstation operating system cannot handle the length of the given path.Action: Shorten the destination path; then retry the operation.PAGENUM=1317 ID="BP1311"070: The destination file is set to Read Only and cannot be changed. File: nameWSUPDATEExplanation: The destination file is marked Read Only.Action: If appropriate, change the file's attributes using FLAG, or override the Read Only attribute using the WSUPDATE /O option.100: The source file's date and time were not found.WSUPDATEExplanation: WSUPDATE could not get the date and time of the file, probably because the user does not have the Access right.Action: Make sure the file is in the specified area. Make sure the user has appropriate user access rights.110: You have entered an incorrect file name.WSUPDATEExplanation: Control characters (characters that are pressed in combination with the MOREINFO="NONE"<Ctrl> key) are invalid command line parameters.Action: Rename the file without using control characters. To access online help information, type "WSUPDATE /?", or see "BOOK="utlrfenu" COLLECTION="nw41"WSUPDATE" in Utilities Reference.115: The command-line options cannot be understood. Command: commandWSUPDATEExplanation: Invalid options were specified on the command line.Action: Enter the command correctly. To access online help information, type "WSUPDATE /?", or see "BOOK="utlrfenu" COLLECTION="nw41"WSUPDATE" in Utilities Reference.116: You can't enter both the /N and the /ALL, /Local or /S options. Command line is: commandWSUPDATEExplanation: Invalid options were specified on the command line.Action: Enter the command correctly. To access online help information, type "WSUPDATE /?", or see "BOOK="utlrfenu" COLLECTION="nw41"WSUPDATE" in Utilities Reference.120: The source file cannot be found. File: nameWSUPDATEExplanation: The specified source file was not found.Action: Find the desired source file; then retry the operation. To access online help information, type "WSUPDATE /?", or see "BOOK="utlrfenu" COLLECTION="nw41"WSUPDATE" in Utilities Reference.PAGENUM=1318 ID="BP1312"125: The log filename is too long.WSUPDATEExplanation: The log filename is too long for the workstation's operating system.Action: Determine the acceptable length of filenames for the operating system, shorten the log filename to proper length, then retry the operation. To access online help information, type "WSUPDATE /?", or see "BOOK="utlrfenu" COLLECTION="nw41"WSUPDATE" in Utilities Reference.127: An invalid number of parameters was specified. To get help, type WSUPDATE /?WSUPDATEExplanation: The command line contains an invalid number of parameters.Action: Type the command correctly. To access online help information, type "WSUPDATE /?", or see "BOOK="utlrfenu" COLLECTION="nw41"WSUPDATE" in Utilities Reference.140: Multiple configuration files cannot be entered in the same command.WSUPDATEExplanation: Only one configuration file can be specified at a time.Action: Specify only one configuration file. To access online help information, type "WSUPDATE /?", or see "BOOK="utlrfenu" COLLECTION="nw41"WSUPDATE" in Utilities Reference.160: The destination path cannot be interpreted. WSUPDATEExplanation: The destination path was not in a valid format.Action: Use the correct syntax, for example:FORMAT="LINESPECIFIC"MOREINFO="NONE"volume_object:path server/volume:
path To access online help information, type "WSUPDATE /?", or see "BOOK="utlrfenu" COLLECTION="nw41"WSUPDATE" in Utilities Reference.165: Available memory is insufficient to continue the program.WSUPDATEExplanation: The workstation needs more memory to load WSUPDATE.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network.167: You must attach to server name before continuing.WSUPDATEExplanation: The server specified is not part of the connection list.Action: Use FILER to attach to the desired server; then retry the operation.PAGENUM=1319 ID="BP1313"170: The configuration file cannot be opened. File: nameWSUPDATEExplanation: Someone is using this file, or the file does not exist.Action: Make sure the file exists, and that no one else is using it; then retry the operation.180: The destination file cannot be opened. File: nameWSUPDATEExplanation: Someone is using this file, or the file does not exist.Action: Make sure the file exists, and that no one else is using it; then retry the operation.190: The log file cannot be opened. File: nameWSUPDATEExplanation: Someone is using this file, or the file does not exist.Action: Make sure the file exists, and that no one else is using it; then retry the operation.200: The source file cannot be opened. File: nameWSUPDATEExplanation: Someone is using this file, or the file does not exist.Action: Make sure the file exists, and that no one else is using it; then retry the operation.208: The backup file for the CONFIG.SYS file can't be opened. File: nameWSUPDATEExplanation: Someone is using this file, or the file does not exist.Action: Make sure the file exists, and that no one else is using it; then retry the operation.210: A line in the configuration file was too long: string.WSUPDATEExplanation: The indicated line is too long for the workstation's operating system.Action: Determine the acceptable line length for the operating system, and shorten the line; then retry the operation.220: The new filename cannot be the same as the source filename.WSUPDATEExplanation: The destination file and the source file cannot have the same name.Action: Give the destination file a different name. To access online help information, type "WSUPDATE /?", or see "BOOK="utlrfenu" COLLECTION="nw41"WSUPDATE" in Utilities Reference.PAGENUM=1320 ID="BP1314"230: The access rights for the renamed file cannot be changed. File: name.WSUPDATEExplanation: The specified file was not in the correct path, or WSUPDATE was unable to change the file attributes to Read Write.Action: Make sure the specified file is in the correct path; then retry the operation. If error recurs, make sure the user has the rights to access and change the file; then retry the operation.240: The destination file cannot be renamed. Error number: code. From path: path. To path: path.WSUPDATEExplanation: The destination file was not renamed because of an error.Action: Make sure the file attributes are flagged Read Write. Make sure the user has the appropriate rights to rename the file. For information about a specific error code, see IDREF="FM61529""Error Codes" in Appendix A.250: An error occurred during renaming. No copy was performed.WSUPDATEExplanation: When trying to rename the file, an error was encountered because WSUPDATE was unable to change the file attributes to Read Write.Action: Make sure the user has the appropriate rights to rename the file. Make sure the file is flagged Read Write.260: The destination file cannot be accessed. File: nameWSUPDATEExplanation: WSUPDATE was unable to access the destination file.Action: Make sure the destination file exists. Make sure the user has appropriate user access rights. Make sure the file is flagged Read Write.270: Available disk space is insufficient to rename or update the file.WSUPDATEExplanation: The workstation ran out of disk space while trying to update the file.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Disk Space Problems" in Supervising the Network.280: The access rights for renamed file cannot be restored. File: nameWSUPDATEExplanation: An error occurred when WSUPDATE tried to assign the file attributes to the renamed file.Action: Make sure the user has the appropriate rights to rename the file; then retry the operation.PAGENUM=1321 ID="BP1315"290: The specified file is Read Only and cannot be renamed. File: nameWSUPDATEExplanation: The attributes for the specified file are set to Read Only; therefore, the attributes could not be changed.Action: With the appropriate rights, use the /R option with WSUPDATE to rename the file with an .OLD extension and allow attributes for Read Only files to be changed.300: The date and time of the destination file cannot be set.WSUPDATEExplanation: The date and time of the destination file cannot be set.Action: Make sure the destination file exists. Make sure the destination file's name is typed correctly; then retry the operation.305: The source path is too long. WSUPDATEExplanation: The source path used is too long for the current workstation's operating system.Action: Determine the maximum length allowed for the source path by the workstation's operating system; then retry the operation. To access online help information, type "WSUPDATE /?", or see "BOOK="utlrfenu" COLLECTION="nw41"WSUPDATE" in Utilities Reference.322: You must specify a drive letter, a volume name, or the ALL or LOCAL option. Command line: command WSUPDATEExplanation: The destination drive or drives must be specified.Action: Specify the drive or drives in the command line. To access online help information, type "WSUPDATE /?", or see "BOOK="utlrfenu" COLLECTION="nw41"WSUPDATE" in Utilities Reference.325: The volume name is too long.WSUPDATEExplanation: The volume name specified is invalid because it is too long.Action: Shorten the volume name, and type the volume name correctly. To access online help information, type "WSUPDATE /?", or see "BOOK="utlrfenu" COLLECTION="nw41"WSUPDATE" in Utilities Reference.328: Volume name cannot be found.WSUPDATEExplanation: The specified volume does not exist, or the volume name was typed incorrectly.Action: Make sure a valid volume name is specified. Make sure the volume is mounted. Make sure the volume name is typed correctly.PAGENUM=1322 ID="BP1316"330: A wildcard character cannot be used in configuration filename. File: nameWSUPDATEExplanation: A control (wildcard) character was found in the configuration file.Action: Retype the destination path without using a wildcard character. To access online help information, type "WSUPDATE /?", or see "BOOK="utlrfenu" COLLECTION="nw41"WSUPDATE" in Utilities Reference.340: A wildcard character cannot be used in the destination path. Path: path Command line: numberWSUPDATEExplanation: A control (wildcard) character was found in the destination path.Action: Retype the destination path without using a wildcard character. To access online help information, type "WSUPDATE /?", or see "BOOK="utlrfenu" COLLECTION="nw41"WSUPDATE" in Utilities Reference.342: A wildcard character cannot be used in the destination filename. File: name Command line: number WSUPDATEExplanation: A control (wildcard) character was found in the destination filename.Action: Retype the destination filename without using a wildcard character. To access online help information, type "WSUPDATE /?", or see "BOOK="utlrfenu" COLLECTION="nw41"WSUPDATE" in Utilities Reference.344: A wildcard character cannot be used in the log filename. File: name. Command line: number. WSUPDATEExplanation: A control (wildcard) character was found in the log filename.Action: Retype the log filename without a using a wildcard character. To access online help information, type "WSUPDATE /?", or see "BOOK="utlrfenu" COLLECTION="nw41"WSUPDATE" in Utilities Reference.350: A wildcard character cannot be used in the source filename. File: name Command line: numberWSUPDATEExplanation: A control (wildcard) character was found in the source filename.Action: Retype the source filename without using a wildcard character. To access online help information, type "WSUPDATE /?", or see "BOOK="utlrfenu" COLLECTION="nw41"WSUPDATE" in Utilities Reference.360: An outdated file name was found in path.WSUPDATEExplanation:  In the directory shown in the message, an older file was found.Action: Replace the old file with a current file; then retry the operation.PAGENUM=1323 ID="BP1317"365: Cannot use the /r and /c options at the same time.WSUPDATEExplanation: The /R option renames a file and gives it an .OLD extension before copying the new file. The /C option copies the new file over the old one without creating a backup of the old file. These two options cannot be used at the same time.Action: Do not use the /R and /C option on a file at the same time.370: The source path cannot be interpreted.WSUPDATEExplanation: The source path cannot be interpreted.Action: Make sure the source path exists and that it was typed correctly. To access online help information, type "WSUPDATE /?", or see "BOOK="utlrfenu" COLLECTION="nw41"WSUPDATE" in Utilities Reference.400: An error occurred attempting to modify the CONFIG.SYS file. You should restore the file from CONFIG.VLMWSUPDATEExplanation: An error occurred while trying to modify the CONFIG.SYS file.Action: Restore the file from the backup CONFIG.VLM file.401: The destination path path could not be created.WSUPDATEExplanation: The path entered could not be created.Action: Make sure the path name is typed correctly and try again.900: An internal application error occurred. WSUPDATEExplanation: An unknown error has occurred.Action: Make sure the user has appropriate user access rights. Make sure the command was typed correctly. If the problem persists, contact your Novell Authorized Reseller.905: This utility was unable to initialize the country information.WSUPDATEAction: See message IDREF="FM55337""905: This utility was unable to initialize the country information." in Appendix C.906: The unicode files cannot be found.WSUPDATEAction: See message IDREF="FM78951""906: The Unicode files cannot be found." in Appendix C. 970: The attempt to open the Unicode table files failed.WSUPDATEAction: See message IDREF="FM15675""970: The attempt to open the Unicode table files failed." in Appendix C.PAGENUM=1324 ID="BP1318"971: The workstation does not have enough memory to load the Unicode table files.WSUPDATEAction: See message IDREF="FM55341""971: The workstation does not have enough memory to load the Unicode table files." in Appendix C.972: Access to the Unicode table files was denied.WSUPDATEAction: See message IDREF="FM90152""972: Access to the Unicode table files was denied." in Appendix C.973: The Unicode table files can't be found in the NLS directory or in the search drives.WSUPDATEAction: See message IDREF="FM62778""973: The Unicode table files cannot be found in the NLS directory or in the search path. Code page: number Country: number" in Appendix C.974: The Unicode table files are corrupt.WSUPDATEAction: See message IDREF="FM63405""974: The Unicode table files are corrupt." in Appendix C.975: The Unicode table files can't be opened because there are already too many open files. Close some files or modify your CONFIG.SYS file.WSUPDATEAction: See message IDREF="FM49793""975: The Unicode table files cannot be opened because there are already too many open files. Close some files or modify your CONFIG.SYS file." in Appendix C.998: The message file found was the incorrect version.WSUPDATEAction: See message IDREF="FM91957""998: The message file found (utility_name.MSG) is an incorrect version. The correct version is number. See your network supervisor for assistance." in Appendix C.PAGENUM=1325 ID="BP1319"WSUPGRDThe WSUPGRD messages numbered 200 and above may leave the workstation without a good LAN driver. If any of these messages appear, correct whatever caused the problem and restart WSUPGRD, or manually upgrade the workstation before it is turned off or rebooted. If the station's connection to the server has been lost, the upgrade will have to be performed manually from a floppy disk before the station can reattach to the network.100: The command line contains invalid parameter(s). No upgrade performed.WSUPGRDExplanation: Invalid parameters were found on the command line when trying to upgrade the workstation driver to an ODI driver.Action: Retype the command line using valid parameters.105: Program is unable to get the drive mapping to read DRVRXLAT.TXT. No upgrade performed.WSUPGRDExplanation: WSUPGRD needs one mappable drive, but all available drive letters are in use.Action: Delete a drive mapping and try again.110: Program is unable to open the old name's driver file. No upgrade performed.WSUPGRDExplanation: The DOSIPX driver has a name other than the one shown in the message, or the DOSIPX driver is not in the current directory.Action: Run WSUPGRD using the correct path and DOSIPX driver name.115: Configuration table could not be found in the name's driver file. No upgrade performed.WSUPGRDExplanation: WSUPGRD searched the specified file but could not find a master configuration table or the selected option table for one of the following reasons:MARK=BULLETThe specified file is not a DOSIPX driver.The DOSIPX driver's master configuration table does not have the proper signature.The hardware option tables do not immediately follow the master configuration table.The DOSIPX driver file is corrupted.Action: First reason: Run WSUPGRD again, using the correct path and DOSIPX driver name. Other reasons: Upgrade manually.PAGENUM=1326 ID="BP1320"120: Program is unable to find the ODI name driver file. No upgrade performed.WSUPGRDExplanation: The ODI driver file could not be found for one of the following reasons:MARK=BULLETThe specified ODI driver is not on the server.The DRVRXLAT.TXT entry for this driver is incorrect.The DRVRXLAT.TXT entry points to an ODI driver in an area in which the user does not have rights.Action: Correct the DRVRXLAT.TXT if needed, and verify that DOSODI drivers are in a directory to which users have rights.200: Program is unable to create the NET.CFG file. Upgrade cannot be completed. Do not turn off or reboot this station. Notify your system administrator of this message for further instructions.WSUPGRDExplanation: The disk being upgraded is full, write-protected, or corrupted.Action: Correct the problem and run WSUPGRD again.205: Program is unable to write to the NET.CFG file. Upgrade cannot be completed. Do not turn off or reboot this station. Notify your system administrator of this message for further instructions.WSUPGRDExplanation: The disk being upgraded is full or corrupted.Action: Correct the problem and run WSUPGRD again.210: Program is unable to close the NET.CFG file, probably due to insufficient disk space. Upgrade cannot be completed. Do not turn off or reboot this station. Notify your system administrator of this message for further instructions.WSUPGRDExplanation: WSUPGRD cannot do the final writes to (or cannot update and close the directory entry for) the NET.CFG file. The disk being upgraded is full or corrupted.Action: Correct the problem and run WSUPGRD again.220: Program is unable to open the LSL.COM file. Upgrade cannot be completed. Do not turn off or reboot this station. Notify your system administrator of this message for further instructions.WSUPGRDExplanation: The LSL.COM file could not be opened for one of the following reasons:MARK=BULLETLSL.COM is corrupted.PAGENUM=1327 ID="BP1321"LSL.COM is not on the server.LSL.COM is not in the correct subdirectory.The user does not have rights to LSL.COM.The workstation has lost its connection to the server.Action: Correct the problem and run WSUPGRD again. If the connection is lost, perform the upgrade manually from a floppy disk; then reattach the workstation to the server.225: Program is unable to create the LSL.COM file. Upgrade cannot be completed. Do not turn off or reboot this station. Notify your system administrator of this message for further instructions.WSUPGRDExplanation: The disk being upgraded is full, write-protected, or corrupted.Action: Correct the problem and run WSUPGRD again.230: Program is unable to read the LSL.COM file. Upgrade cannot be completed. Do not turn off or reboot this station. Notify your system administrator of this message for further instructions.WSUPGRDExplanation: The LSL.COM file cannot be read for one of the following reasons:MARK=BULLETLSL.COM is corrupted.The user doesn't have rights to LSL.COM.The workstation has lost its connection to the server.Action: Correct the problem and run WSUPGRD again. If the connection is lost, perform the upgrade manually from a floppy disk; then reattach the workstation to the server.235: Program is unable to write to the LSL.COM file. Upgrade cannot be completed. Do not turn off or reboot this station. Notify your system administrator of this message for further instructions.WSUPGRDExplanation: The disk being upgraded is full or corrupted.Action: Correct the problem and run WSUPGRD again.PAGENUM=1328 ID="BP1322"240: Program is unable to close the LSL.COM file, probably due to insufficient disk space. Upgrade cannot be completed. Do not turn off or reboot this station. Notify your system administrator of this message for further instructions.WSUPGRDExplanation: The disk being upgraded is full or corrupted.Action: Correct the problem and run WSUPGRD again.250: Program is unable to open the IPXODI.COM file. Upgrade cannot be completed. Do not turn off or reboot this station. Notify your system administrator of this message for further instructions.WSUPGRDExplanation: The IPXODI.COM cannot be opened for one of the following reasons:MARK=BULLETIPXODI.COM is corrupted.IPXODI.COM is not on the server.IPXODI.COM is not in the correct subdirectory.The user does not have rights to LSL.COM.The workstation has lost its connection to the server.Action: Correct the problem and run WSUPGRD again. If the connection is lost, perform the upgrade manually from a floppy disk; then reattach the workstation to the server.255: Program is unable to create the IPXODI.COM file. Upgrade cannot be completed. Do not turn off or reboot this station. Notify your system administrator of this message for further instructions.WSUPGRDExplanation: The disk being upgraded is full or corrupted.Action: Correct the problem and run WSUPGRD again.260: Program is unable to read the IPXODI.COM file. Upgrade cannot be completed. Do not turn off or reboot this station. Notify your system administrator of this message for further instructions.WSUPGRDExplanation: The IPXODI.COM cannot be opened for one of the following reasons:MARK=BULLETIPXODI.COM is corrupted.IPXODI.COM is not on the server.IPXODI.COM is not in the correct subdirectory.PAGENUM=1329 ID="BP1323"The user does not have rights to LSL.COM.The workstation has lost its connection to the server.Action: Correct the problem and run WSUPGRD again. If the connection is lost, perform the upgrade manually a from floppy disk; then reattach the workstation to the server.265: Program is unable to write to the IPXODI.COM file. Upgrade cannot be completed. Do not turn off or reboot this station. Notify your system administrator of this message for further instructions.WSUPGRDExplanation: The disk being upgraded is full or corrupted.Action: Correct the problem and run WSUPGRD again.270: Program is unable to close the IPXODI.COM file, probably due to insufficient disk space. Upgrade cannot be completed. Do not turn off or reboot this station. Notify your system administrator of this message for further instructions.WSUPGRDExplanation: The disk being upgraded is full or corrupted.Action: Correct the problem and run WSUPGRD again.280: Program is unable to open the ODI name driver file. Upgrade cannot be completed. Do not turn off or reboot this station. Notify your system administrator of this message for further instructions.WSUPGRDExplanation: The ODI driver file cannot be opened for one of the following reasons:MARK=BULLETIPXODI.COM is corrupted.IPXODI.COM is not on the server.IPXODI.COM is not in the correct subdirectory.The user does not have rights to LSL.COM.The workstation has lost its connection to the server.Action: Correct the problem and run WSUPGRD again. If the connection is lost, perform the upgrade manually from a floppy disk; then reattach the workstation to the server.PAGENUM=1330 ID="BP1324"285: Program is unable to create the new ODI name driver file. Upgrade cannot be completed Do not turn off or reboot this station. Notify your system administrator of this message for further instructions.WSUPGRDExplanation: The disk being upgraded is full or corrupted, or a write-protected file already exists with this name.Action: Correct the problem and run WSUPGRD again.290: Program is unable to read the ODI name driver file. Upgrade cannot be completed. Do not turn off or reboot this station. Notify your system administrator of this message for further instructions.WSUPGRDExplanation: The ODI driver file could not be read for one of the following reasons:MARK=BULLETThe ODI driver file is corrupted.The workstation has lost its connection to the server.Action: Correct the problem and run WSUPGRD again. If the connection is lost, perform the upgrade manually from a floppy disk; then reattach the workstation to the server.295: Program is unable to write to the new ODI name driver file. Upgrade cannot be completed. Do not turn off or reboot this station. Notify your system administrator of this message for further instructions.WSUPGRDExplanation: The disk being upgraded is full or corrupted.Action: Correct the problem and run WSUPGRD again.300: Program is unable to close the new ODI name driver file, probably due to insufficient disk space. Upgrade cannot be completed. Do not turn off or reboot this station. Notify your system administrator of this message for further instructions.WSUPGRDExplanation: The disk being upgraded is full or corrupted.Action: Correct the problem and run WSUPGRD again.310: Program is unable to create the NWSTART.BAT file. Upgrade cannot be completed. Do not turn off or reboot this station. Notify your system administrator of this message for further instructions.WSUPGRDExplanation: The disk being upgraded is full or corrupted.Action: Correct the problem and run WSUPGRD again.PAGENUM=1331 ID="BP1325"315: Program is unable to write to the NWSTART.BAT file. Upgrade cannot be completed. Do not turn off or reboot this station. Notify your system administrator of this message for further instructions.WSUPGRDExplanation: The disk being upgraded is full or corrupted.Action: Correct the problem and run WSUPGRD again.320: Program is unable to close the NWSTART.BAT file, probably due to insufficient disk space. Upgrade cannot be completed. Do not turn off or reboot this station. Notify your system administrator of this message for further instructions.WSUPGRDExplanation: The disk being upgraded is full or corrupted.Action: Correct the problem and run WSUPGRD again.330: Program is unable to open the AUTOEXEC.BAT file. Upgrade cannot be completed. Do not turn off or reboot this station. Notify your system administrator of this message for further instructions.WSUPGRDExplanation: The disk being upgraded is full or corrupted.Action: Correct the problem and run WSUPGRD again.335: Program is unable to create a new AUTOEXEC.BAT file. Upgrade cannot be completed. Do not turn off or reboot this station. Notify your system administrator of this message for further instructions.WSUPGRDExplanation: The disk being upgraded is full or corrupted.Action: Correct the problem and run WSUPGRD again.340: Program is unable to read the AUTOEXEC.BAT file. Upgrade cannot be completed. Do not turn off or reboot this station. Notify your system administrator of this message for further instructions.WSUPGRDExplanation: The file is corrupted.Action: Correct the problem and run WSUPGRD again.345: Program is unable to write to the new AUTOEXEC.BAT file. Upgrade cannot be completed. Do not turn off or reboot this station. Notify your system administrator of this message for further instructions.WSUPGRDExplanation: The disk being upgraded is full or corrupted.Action: Correct the problem and run WSUPGRD again.PAGENUM=1332 ID="BP1326"350: Program is unable to close the AUTOEXEC.BAT file, probably due to insufficient disk space. Upgrade cannot be completed. Do not turn off or reboot this station. Notify your system administrator of this message for further instructions.WSUPGRDExplanation: The disk being upgraded is full or corrupted.Action: Correct the problem and run WSUPGRD again.990: Unable to initialize; no upgrade performed.WSUPGRDExplanation: The disk being upgraded is full or corrupted.Action: Correct the problem and run WSUPGRD again.999: The message file for this utility cannot be found.WSUPGRDAction: See IDREF="FM69424""999: The message file for this utility cannot be found." in Appendix C.LABEL="A"PAGENUM=1333 ID="BP1327"ID="FM61529"Error CodesMany error codes display only a few digits of the hexadecimal error code. Often a number code is truncated to two digits, so it is not the actual decimal equivalent of the hexadecimal code.LABEL="1-1" PGWIDE=1 TOCENTRY="1" Error Codes Returned in NetWare 4 System MessagesCOLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="4*"COLNAME=3 COLWIDTH="24*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Hex.COLNAME=2 ROTATE="0" MOREROWS="0"NumberCOLNAME=3 ROTATE="0" MOREROWS="0"Description, Explanation, ActionVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"0000COLNAME=2 ROTATE="0" MOREROWS="0"decimal 64COLNAME=3 ROTATE="0" MOREROWS="0"Description: The print server completed the expected operation.Explanation: This is not an error.COLNAME=1 ROTATE="0" MOREROWS="0"000FCOLNAME=2 ROTATE="0" MOREROWS="0"decimal 255COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to use an invalid (undefined, unavailable, etc.) drive.COLNAME=1 ROTATE="0" MOREROWS="0"0040COLNAME=2 ROTATE="0" MOREROWS="0"decimal 64COLNAME=3 ROTATE="0" MOREROWS="0"Description: There are no available SPX connections for print services.COLNAME=1 ROTATE="0" MOREROWS="0"0041COLNAME=2 ROTATE="0" MOREROWS="0"decimal 65COLNAME=3 ROTATE="0" MOREROWS="0"Description: SPX has not been initialized for print services.COLNAME=1 ROTATE="0" MOREROWS="0"0042COLNAME=2 ROTATE="0" MOREROWS="0"decimal 66COLNAME=3 ROTATE="0" MOREROWS="0"Description: The specified PSERVER is invalid.COLNAME=1 ROTATE="0" MOREROWS="0"0043COLNAME=2 ROTATE="0" MOREROWS="0"decimal 67COLNAME=3 ROTATE="0" MOREROWS="0"Description: The server address cannot be obtained.COLNAME=1 ROTATE="0" MOREROWS="0"0045COLNAME=2 ROTATE="0" MOREROWS="0"decimal 69COLNAME=3 ROTATE="0" MOREROWS="0"Description: No IPX sockets are available.COLNAME=1 ROTATE="0" MOREROWS="0"0046COLNAME=2 ROTATE="0" MOREROWS="0"decimal 70COLNAME=3 ROTATE="0" MOREROWS="0"Description: You are already attached to a printer.COLNAME=1 ROTATE="0" MOREROWS="0"0047COLNAME=2 ROTATE="0" MOREROWS="0"decimal 71COLNAME=3 ROTATE="0" MOREROWS="0"Description: IPX is not initialized. COLNAME=1 ROTATE="0" MOREROWS="0"7770COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The version being used was the wrong one.COLNAME=1 ROTATE="0" MOREROWS="0"7771COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=3 ROTATE="0" MOREROWS="0"Description: The end of the scan list has been reached. There are no more entries.COLNAME=1 ROTATE="0" MOREROWS="0"7772COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: No more information can be added because no more disk space is in the network drive.Action: Free up some space or get more allocated.COLNAME=1 ROTATE="0" MOREROWS="0"7773COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The default was specified, but an error is in the database.COLNAME=1 ROTATE="0" MOREROWS="0"7774COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The libraries cannot find the database, or the user is not authorized to use the database.COLNAME=1 ROTATE="0" MOREROWS="0"7775COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user is not authorized to use the database, or a database problem exists.COLNAME=1 ROTATE="0" MOREROWS="0"7776COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user is not authorized to use the database, or a record problem exists.COLNAME=1 ROTATE="0" MOREROWS="0"7777COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user's workstation is out of disk space, or the user is not authorized to write to the database.Action: Try freeing up some space.COLNAME=1 ROTATE="0" MOREROWS="0"7778COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user's workstation is out of disk space, or the user is not authorized to write to the database record.Action: Try freeing up some space.COLNAME=1 ROTATE="0" MOREROWS="0"7779COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The database or the application has a problem.Action: You may need to contact the application vendor.COLNAME=1 ROTATE="0" MOREROWS="0"777ACOLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user requested information on an item that was not in the database. The item may have been deleted already or was never part of the list.COLNAME=1 ROTATE="0" MOREROWS="0"777BCOLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The PrintCon default entry has not been defined.Action: Define the PRINTCON default entry using the Set Default Job option.COLNAME=1 ROTATE="0" MOREROWS="0"777CCOLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user's workstation is out of RAM.Action: Increase RAM.COLNAME=1 ROTATE="0" MOREROWS="0"8800COLNAME=2 ROTATE="0" MOREROWS="0"0COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: One of the following reasons apply:MARK=BULLETYou are already attached to the server.A shell or VLM program error has occurred.This is not an error. The print server completed the expected operation. (0000)COLNAME=1 ROTATE="0" MOREROWS="0"8801COLNAME=2 ROTATE="0" MOREROWS="0"1COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: A request was attempted with an invalid or nonattached connection handle.COLNAME=1 ROTATE="0" MOREROWS="0"8802COLNAME=2 ROTATE="0" MOREROWS="0"2COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: OS/2 only (NOT USED)COLNAME=1 ROTATE="0" MOREROWS="0"8803COLNAME=2 ROTATE="0" MOREROWS="0"3COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: An attempt to map a drive was unsuccessful. It could not add a new current directory structure.COLNAME=1 ROTATE="0" MOREROWS="0"8804COLNAME=2 ROTATE="0" MOREROWS="0"4COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: An attempt was made to map a drive with an invalid path specification.COLNAME=1 ROTATE="0" MOREROWS="0"8805COLNAME=2 ROTATE="0" MOREROWS="0"5COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: An attempt to receive from the selected transport failed.COLNAME=1 ROTATE="0" MOREROWS="0"8806COLNAME=2 ROTATE="0" MOREROWS="0"6COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: A network send request was attempted, but a nonspecific network error occurred.COLNAME=1 ROTATE="0" MOREROWS="0"8807COLNAME=2 ROTATE="0" MOREROWS="0"7COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: A server request was attempted with an invalid server connection slot.COLNAME=1 ROTATE="0" MOREROWS="0"8808COLNAME=2 ROTATE="0" MOREROWS="0"8COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: An attempt was made to attach to a server with no connection slots available.COLNAME=1 ROTATE="0" MOREROWS="0"8809COLNAME=2 ROTATE="0" MOREROWS="0"9COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: An attempt to send on the selected transport failed.COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=3 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"880ACOLNAME=2 ROTATE="0" MOREROWS="0"10COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: An attempt was made to find a route to a server where no route exists.COLNAME=1 ROTATE="0" MOREROWS="0"880BCOLNAME=2 ROTATE="0" MOREROWS="0"11COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: An invalid local target was specified (for OS/2 only).COLNAME=1 ROTATE="0" MOREROWS="0"880CCOLNAME=2 ROTATE="0" MOREROWS="0"12COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: A request was attempted with too many request fragments specified.COLNAME=1 ROTATE="0" MOREROWS="0"880DCOLNAME=2 ROTATE="0" MOREROWS="0"13COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: Too many connections exist to fit in the list size specified.COLNAME=1 ROTATE="0" MOREROWS="0"880ECOLNAME=2 ROTATE="0" MOREROWS="0"14COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: An attempt was made to receive more data than the reply buffer had room for.COLNAME=1 ROTATE="0" MOREROWS="0"880FCOLNAME=2 ROTATE="0" MOREROWS="0"15COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: An attempt to get connection for a server failed. The workstation is not connected.COLNAME=1 ROTATE="0" MOREROWS="0"8810COLNAME=2 ROTATE="0" MOREROWS="0"16COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: No router was found (OS/2 only).COLNAME=1 ROTATE="0" MOREROWS="0"8811COLNAME=2 ROTATE="0" MOREROWS="0"17COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: A function call was tried to a nonexistent or illegal function.COLNAME=1 ROTATE="0" MOREROWS="0"8830COLNAME=2 ROTATE="0" MOREROWS="0"48COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: An internal server request was attempted across different server connections.COLNAME=1 ROTATE="0" MOREROWS="0"8831COLNAME=2 ROTATE="0" MOREROWS="0"49COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: An attempt was made to retrieve a default connection with no primary connection set.COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=3 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"8832COLNAME=2 ROTATE="0" MOREROWS="0"50COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: Capture information was requested on a port with no capture in progress.COLNAME=1 ROTATE="0" MOREROWS="0"8833COLNAME=2 ROTATE="0" MOREROWS="0"51COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The length that the caller requested was too large.COLNAME=1 ROTATE="0" MOREROWS="0"8834COLNAME=2 ROTATE="0" MOREROWS="0"52COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: No information for this error code is available.COLNAME=1 ROTATE="0" MOREROWS="0"8835COLNAME=2 ROTATE="0" MOREROWS="0"53COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: Capture was requested without a local print spooler installed.COLNAME=1 ROTATE="0" MOREROWS="0"8836COLNAME=2 ROTATE="0" MOREROWS="0"54COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: A function was attempted with an invalid function parameter specified.COLNAME=1 ROTATE="0" MOREROWS="0"8837COLNAME=2 ROTATE="0" MOREROWS="0"55COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: An attempt to open the configuration file failed (for OS/2 only).COLNAME=1 ROTATE="0" MOREROWS="0"8838COLNAME=2 ROTATE="0" MOREROWS="0"56COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: No configuration file can be found (for OS/2 only).COLNAME=1 ROTATE="0" MOREROWS="0"8839COLNAME=2 ROTATE="0" MOREROWS="0"57COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: An attempt to read a file failed (for OS/2 only).COLNAME=1 ROTATE="0" MOREROWS="0"883ACOLNAME=2 ROTATE="0" MOREROWS="0"58COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: A line in the configuration file is too long (for OS/2 only).COLNAME=1 ROTATE="0" MOREROWS="0"883BCOLNAME=2 ROTATE="0" MOREROWS="0"59COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: One or more lines in the configuration file were ignored (for OS/2 only).COLNAME=1 ROTATE="0" MOREROWS="0"883CCOLNAME=2 ROTATE="0" MOREROWS="0"60COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: A request was made with a parameter using a foreign resource.COLNAME=1 ROTATE="0" MOREROWS="0"883DCOLNAME=2 ROTATE="0" MOREROWS="0"61COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: No information for this error code is available (for OS/ 2 only).COLNAME=1 ROTATE="0" MOREROWS="0"883ECOLNAME=2 ROTATE="0" MOREROWS="0"62COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: An attempt was made to load the print spooler, but the print spooler was already installed.COLNAME=1 ROTATE="0" MOREROWS="0"883FCOLNAME=2 ROTATE="0" MOREROWS="0"63COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The system tried to allocate a connection handle, but no more local connection table entries were available.COLNAME=1 ROTATE="0" MOREROWS="0"8840(0040)COLNAME=2 ROTATE="0" MOREROWS="0"64COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The configuration section was not found (for OS/2 only). No available SPX connections are available for print services. COLNAME=1 ROTATE="0" MOREROWS="0"8841COLNAME=2 ROTATE="0" MOREROWS="0"65COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: One of the following reasons may apply:MARK=BULLETAn attempt was made to execute a function on a connection with an invalid transport selected.SPX has not been initialized for print services. (Actually hexadecimal 0041.)COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=3 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"8842COLNAME=2 ROTATE="0" MOREROWS="0"66COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: One of the following reasons may apply:MARK=BULLETA TDS tag is already in use (for OS/2 only).The specified PSERVER is invalid. (Actually hexadecimal 0042.)COLNAME=1 ROTATE="0" MOREROWS="0"8843COLNAME=2 ROTATE="0" MOREROWS="0"67COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: One of the following reasons may apply:MARK=BULLETThe computer does not have enough available RAM (for OS/2 only).The server address cannot be obtained. (Actually hexadecimal 0043.)COLNAME=1 ROTATE="0" MOREROWS="0"8844COLNAME=2 ROTATE="0" MOREROWS="0"68COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: A TDS function was attempted with an invalid tag.COLNAME=1 ROTATE="0" MOREROWS="0"8845COLNAME=2 ROTATE="0" MOREROWS="0"69COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: One of the following reasons may apply:MARK=BULLETA TDS write was tried to a buffer that exceeded the buffer's size.No IPX sockets are available. (Actually hexadecimal 0047.)COLNAME=1 ROTATE="0" MOREROWS="0"8846COLNAME=2 ROTATE="0" MOREROWS="0"70COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: One of the following reasons may apply:MARK=BULLETNo Directory Services connections exists.A request was tried to a busy, partially asynchronous function.You are already attached to a printer. (Actually hexadecimal 0047.)COLNAME=1 ROTATE="0" MOREROWS="0"8847COLNAME=2 ROTATE="0" MOREROWS="0"71COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: One of the following reasons may apply:MARK=BULLETThe attempt to connect failed to find any servers responding.IPX is not initialized. (Actually hexadecimal 0047.)COLNAME=1 ROTATE="0" MOREROWS="0"8848COLNAME=2 ROTATE="0" MOREROWS="0"72COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: An attempted function call was made to a nonexistent or not-loaded overlay.COLNAME=1 ROTATE="0" MOREROWS="0"8849COLNAME=2 ROTATE="0" MOREROWS="0"73COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: An attempt was made to map to a network drive that was already mapped.COLNAME=1 ROTATE="0" MOREROWS="0"884ACOLNAME=2 ROTATE="0" MOREROWS="0"74COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: An attempt was made to map to a local drive that was in use.COLNAME=1 ROTATE="0" MOREROWS="0"884BCOLNAME=2 ROTATE="0" MOREROWS="0"75COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: An attempt was made to map to the next available drive when no drive was available.COLNAME=1 ROTATE="0" MOREROWS="0"884CCOLNAME=2 ROTATE="0" MOREROWS="0"76COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The device was not redirected.COLNAME=1 ROTATE="0" MOREROWS="0"884DCOLNAME=2 ROTATE="0" MOREROWS="0"77COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The maximum number of files has been reached.COLNAME=1 ROTATE="0" MOREROWS="0"884ECOLNAME=2 ROTATE="0" MOREROWS="0"78COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: An attempted unload failed.COLNAME=1 ROTATE="0" MOREROWS="0"884FCOLNAME=2 ROTATE="0" MOREROWS="0"79COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: An attempt was made to reuse a connection entry that was already in use.COLNAME=1 ROTATE="0" MOREROWS="0"8850COLNAME=2 ROTATE="0" MOREROWS="0"80COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: An attempted request had too many reply fragments specified.COLNAME=1 ROTATE="0" MOREROWS="0"8851COLNAME=2 ROTATE="0" MOREROWS="0"81COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: An attempted request was made to add a name into the name table after the table was full.COLNAME=1 ROTATE="0" MOREROWS="0"8852COLNAME=2 ROTATE="0" MOREROWS="0"82COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: A listen was posted on an unopened socket.COLNAME=1 ROTATE="0" MOREROWS="0"8853COLNAME=2 ROTATE="0" MOREROWS="0"83COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: An attempted enhanced memory operation failed.COLNAME=1 ROTATE="0" MOREROWS="0"8854COLNAME=2 ROTATE="0" MOREROWS="0"84COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: An SFT III switch occurred during mid transfer.COLNAME=1 ROTATE="0" MOREROWS="0"8855COLNAME=2 ROTATE="0" MOREROWS="0"85COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: A preferred directory server was not established, but another directory server was returned.COLNAME=1 ROTATE="0" MOREROWS="0"8856COLNAME=2 ROTATE="0" MOREROWS="0"86COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The device is unknown.Action: Determine if the device is not used by the NetWare DOS Requester; pass to next redirector, if any.COLNAME=1 ROTATE="0" MOREROWS="0"88FFCOLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: An unknown error has occurred, or the shell or VLM program is not present.COLNAME=1 ROTATE="0" MOREROWS="0"8980COLNAME=2 ROTATE="0" MOREROWS="0"128COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to open or create a file that is already open.COLNAME=1 ROTATE="0" MOREROWS="0"8981COLNAME=2 ROTATE="0" MOREROWS="0"129COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: No more file handles are available; the network file handle table is full.COLNAME=1 ROTATE="0" MOREROWS="0"8982COLNAME=2 ROTATE="0" MOREROWS="0"130COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to open a file without the Open right.COLNAME=1 ROTATE="0" MOREROWS="0"8983COLNAME=2 ROTATE="0" MOREROWS="0"131COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: A hard disk input/output error occurred on a NetWare volume; a bad sector has been encountered and could be fatal.COLNAME=1 ROTATE="0" MOREROWS="0"8984COLNAME=2 ROTATE="0" MOREROWS="0"132COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to create a file without the Create right.COLNAME=1 ROTATE="0" MOREROWS="0"8985COLNAME=2 ROTATE="0" MOREROWS="0"133COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to create an already existing file without the Create/Delete rights.COLNAME=1 ROTATE="0" MOREROWS="0"8986COLNAME=2 ROTATE="0" MOREROWS="0"134COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to create a file with the same name as an already existing file with Read Only status.COLNAME=1 ROTATE="0" MOREROWS="0"8987COLNAME=2 ROTATE="0" MOREROWS="0"135COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to create a file using an ambiguous filename.COLNAME=1 ROTATE="0" MOREROWS="0"8988COLNAME=2 ROTATE="0" MOREROWS="0"136COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to close or perform I/O on a file with an invalid file handle (that is, trying to read from a file that has been closed).COLNAME=1 ROTATE="0" MOREROWS="0"8989COLNAME=2 ROTATE="0" MOREROWS="0"137COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to search a directory without search rights in that directory.COLNAME=1 ROTATE="0" MOREROWS="0"898ACOLNAME=2 ROTATE="0" MOREROWS="0"138COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to delete a file without file deletion privileges in that file's directory.COLNAME=1 ROTATE="0" MOREROWS="0"898BCOLNAME=2 ROTATE="0" MOREROWS="0"139COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to rename a file without renaming privileges in that file's directory.COLNAME=1 ROTATE="0" MOREROWS="0"898CCOLNAME=2 ROTATE="0" MOREROWS="0"140COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to modify a file without attribute modification privileges in that file's directory.COLNAME=1 ROTATE="0" MOREROWS="0"898DCOLNAME=2 ROTATE="0" MOREROWS="0"141COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to delete, rename, or set file attributes using an ambiguous filename while some of the files specified by the filename are in use by another workstation.COLNAME=1 ROTATE="0" MOREROWS="0"898ECOLNAME=2 ROTATE="0" MOREROWS="0"142COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to delete, rename, or set file attributes using a filename when the file or files specified by the filename are in use by another workstation.COLNAME=1 ROTATE="0" MOREROWS="0"898FCOLNAME=2 ROTATE="0" MOREROWS="0"143COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to delete, rename, or set file attributes using a filename when some of the files specified have Read Only status.COLNAME=1 ROTATE="0" MOREROWS="0"8990COLNAME=2 ROTATE="0" MOREROWS="0"144COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to delete, rename, or set file attributes using a filename when all the files specified have Read Only status.COLNAME=1 ROTATE="0" MOREROWS="0"8991COLNAME=2 ROTATE="0" MOREROWS="0"145COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to rename files when one or more files matching the new filename specification already exist.COLNAME=1 ROTATE="0" MOREROWS="0"8992COLNAME=2 ROTATE="0" MOREROWS="0"146COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to rename files when all the files matching the new filename specification already exist.COLNAME=1 ROTATE="0" MOREROWS="0"8993COLNAME=2 ROTATE="0" MOREROWS="0"147COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to read a file without Read privileges to that file.COLNAME=1 ROTATE="0" MOREROWS="0"8994COLNAME=2 ROTATE="0" MOREROWS="0"148COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to write to a file without Write privileges to that file, or the specified file has Read Only status.COLNAME=1 ROTATE="0" MOREROWS="0"8995COLNAME=2 ROTATE="0" MOREROWS="0"149COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to read or write to a detached file.COLNAME=1 ROTATE="0" MOREROWS="0"8996COLNAME=2 ROTATE="0" MOREROWS="0"150COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to write to a file server that does not have enough free dynamic memory to process the specified request.COLNAME=1 ROTATE="0" MOREROWS="0"8997COLNAME=2 ROTATE="0" MOREROWS="0"151COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The network operating system has determined that the network disk does not have enough space left for spool files.COLNAME=1 ROTATE="0" MOREROWS="0"8998COLNAME=2 ROTATE="0" MOREROWS="0"152COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The network operating system has tried to access a volume but cannot find the volume in the system definition files.COLNAME=1 ROTATE="0" MOREROWS="0"8999COLNAME=2 ROTATE="0" MOREROWS="0"153COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to write to a volume without available directory space.COLNAME=1 ROTATE="0" MOREROWS="0"899ACOLNAME=2 ROTATE="0" MOREROWS="0"154COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to rename across volumes (rename a file and move the renamed file from its current volume into another volume).Although the RENAME command may move the file between directories on the same volume, using RENAME to move a file between volumes is not allowed.COLNAME=1 ROTATE="0" MOREROWS="0"899BCOLNAME=2 ROTATE="0" MOREROWS="0"155COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to use an invalid directory handle. This occurs if the network has been brought down and brought back up, without rebooting the workstation.COLNAME=1 ROTATE="0" MOREROWS="0"899CCOLNAME=2 ROTATE="0" MOREROWS="0"156COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to access an invalid path.COLNAME=1 ROTATE="0" MOREROWS="0"899DCOLNAME=2 ROTATE="0" MOREROWS="0"157COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: No more directory handles are available; the directory handle table is full. Each user may have up to 255 directory handles.COLNAME=1 ROTATE="0" MOREROWS="0"899ECOLNAME=2 ROTATE="0" MOREROWS="0"158COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to create a file using invalid characters within the name of the file.COLNAME=1 ROTATE="0" MOREROWS="0"899FCOLNAME=2 ROTATE="0" MOREROWS="0"159COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to delete a directory that is being used by another workstation.COLNAME=1 ROTATE="0" MOREROWS="0"89A0COLNAME=2 ROTATE="0" MOREROWS="0"160COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to delete a directory that contains files or other directories.COLNAME=1 ROTATE="0" MOREROWS="0"89A1COLNAME=2 ROTATE="0" MOREROWS="0"161COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: A nonrecoverable I/O error has occurred on the disk in the directory area. This error has occurred in both copies of the directory and is fatal.COLNAME=1 ROTATE="0" MOREROWS="0"89A2COLNAME=2 ROTATE="0" MOREROWS="0"162COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to read a file where data is physically locked.COLNAME=1 ROTATE="0" MOREROWS="0"89C1COLNAME=2 ROTATE="0" MOREROWS="0"193COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to log in to an account with no credit available.COLNAME=1 ROTATE="0" MOREROWS="0"89C2COLNAME=2 ROTATE="0" MOREROWS="0"194COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to log in to an account with no credit available.COLNAME=1 ROTATE="0" MOREROWS="0"89C5COLNAME=2 ROTATE="0" MOREROWS="0"197COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to log in after the system had locked the account because of intruder detection.COLNAME=1 ROTATE="0" MOREROWS="0"89C6COLNAME=2 ROTATE="0" MOREROWS="0"198COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to use console privileges without operator privileges.COLNAME=1 ROTATE="0" MOREROWS="0"89D0COLNAME=2 ROTATE="0" MOREROWS="0"208COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: A queue I/O error occurred.COLNAME=1 ROTATE="0" MOREROWS="0"89D1COLNAME=2 ROTATE="0" MOREROWS="0"209COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: No queues are defined.COLNAME=1 ROTATE="0" MOREROWS="0"89D2COLNAME=2 ROTATE="0" MOREROWS="0"210COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: No queue server has been specified.COLNAME=1 ROTATE="0" MOREROWS="0"89D5COLNAME=2 ROTATE="0" MOREROWS="0"213COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: No jobs are in the queue.COLNAME=1 ROTATE="0" MOREROWS="0"89D6COLNAME=2 ROTATE="0" MOREROWS="0"214COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user does not have rights to this job in the queue.COLNAME=1 ROTATE="0" MOREROWS="0"89D7COLNAME=2 ROTATE="0" MOREROWS="0"215COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: One of the following reasons may apply:MARK=BULLETThe user tried to change a password to a previously used password when the unique requirement is specified for the account.The queue is in service at this time.COLNAME=1 ROTATE="0" MOREROWS="0"89D8COLNAME=2 ROTATE="0" MOREROWS="0"216COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: One of the following reasons may apply:MARK=BULLETThe queue is not active at this time.The user tried to change a password to a password with fewer characters than the required minimum specified for the account.COLNAME=1 ROTATE="0" MOREROWS="0"89D9COLNAME=2 ROTATE="0" MOREROWS="0"217COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: One of the following reasons may apply:MARK=BULLETThe queue station is not a server.The user tried to log in using an account that has limits on the number of concurrent connections and that number has been reached.COLNAME=1 ROTATE="0" MOREROWS="0"89DACOLNAME=2 ROTATE="0" MOREROWS="0"218COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: One of the following reasons may apply:MARK=BULLETThe queue has been halted.The user tried to log in during an unauthorized time of day specified for the account.COLNAME=1 ROTATE="0" MOREROWS="0"89DBCOLNAME=2 ROTATE="0" MOREROWS="0"219COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: This queue is already attached to the maximum number of servers allowed.COLNAME=1 ROTATE="0" MOREROWS="0"89DCCOLNAME=2 ROTATE="0" MOREROWS="0"220COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to log in using an account that has expired or has been disabled by the supervisor.COLNAME=1 ROTATE="0" MOREROWS="0"89DECOLNAME=2 ROTATE="0" MOREROWS="0"222COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to log in using an account password that has expired, and all grace logins have also expired.COLNAME=1 ROTATE="0" MOREROWS="0"89DFCOLNAME=2 ROTATE="0" MOREROWS="0"223COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to log in using an expired account password, but the login was allowed because the account had a grace login.COLNAME=1 ROTATE="0" MOREROWS="0"89E7COLNAME=2 ROTATE="0" MOREROWS="0"231COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: No more users exists.COLNAME=1 ROTATE="0" MOREROWS="0"89E8COLNAME=2 ROTATE="0" MOREROWS="0"232COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to use an item not associated with this property group or an item that has been deleted from this group.COLNAME=1 ROTATE="0" MOREROWS="0"89E9COLNAME=2 ROTATE="0" MOREROWS="0"233COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to add an object that already exists to a group property.COLNAME=1 ROTATE="0" MOREROWS="0"89EACOLNAME=2 ROTATE="0" MOREROWS="0"234COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to use an object that is not a member of the defined group property.COLNAME=1 ROTATE="0" MOREROWS="0"89EBCOLNAME=2 ROTATE="0" MOREROWS="0"235COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to use a nongroup property.COLNAME=1 ROTATE="0" MOREROWS="0"89ECCOLNAME=2 ROTATE="0" MOREROWS="0"236COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to use a nonexisting segment. Note that segments must be written sequentially when a property is first created, but may be read and written in any order after they already exist.COLNAME=1 ROTATE="0" MOREROWS="0"89EDCOLNAME=2 ROTATE="0" MOREROWS="0"237COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to create a property that already exists.COLNAME=1 ROTATE="0" MOREROWS="0"89EECOLNAME=2 ROTATE="0" MOREROWS="0"238COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to create an object that already exists.COLNAME=1 ROTATE="0" MOREROWS="0"89EFCOLNAME=2 ROTATE="0" MOREROWS="0"239COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: A request was made with an object or property name containing illegal characters. Illegal characters in names are control characters, the comma, colon, semicolon, slash, backslash, question mark, asterisk, and tilde.COLNAME=1 ROTATE="0" MOREROWS="0"89FCOLNAME=2 ROTATE="0" MOREROWS="0"240COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to use a wildcard character or wild object type in a call where wildcards are not allowed.COLNAME=1 ROTATE="0" MOREROWS="0"89F1COLNAME=2 ROTATE="0" MOREROWS="0"241COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to assign a security level of a bindery object or property to be higher than the user's security level. This would make the object or property inaccessible to the user.COLNAME=1 ROTATE="0" MOREROWS="0"89F3COLNAME=2 ROTATE="0" MOREROWS="0"243COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to rename an object without the necessary rights. Only the Supervisor can rename objects. Note that if the user does not have the rights to see that the object exists, then NCP_NO_SUCH_OBJECT is returned.COLNAME=1 ROTATE="0" MOREROWS="0"89F4COLNAME=2 ROTATE="0" MOREROWS="0"244COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to delete an object without the necessary rights to delete the object. Only the Supervisor can delete objects. Note that if the user does not have the right to see that the object exists, then NCP_NO_SUCH_OBJECT is returned.COLNAME=1 ROTATE="0" MOREROWS="0"89F5COLNAME=2 ROTATE="0" MOREROWS="0"245COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to create an object without the necessary security to create or change an object. Only Supervisors are allowed to create objects.COLNAME=1 ROTATE="0" MOREROWS="0"89F6COLNAME=2 ROTATE="0" MOREROWS="0"246COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to delete a property without the necessary property rights. Note that if the user does not have the proper rights to view the property, then NCP_NO_SUCH_PROPERTY is returned.COLNAME=1 ROTATE="0" MOREROWS="0"89F7COLNAME=2 ROTATE="0" MOREROWS="0"247COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: One of the following reasons may apply:MARK=BULLETThe target drive must be a local drive.The user tried to create a property without the necessary property rights for the object.COLNAME=1 ROTATE="0" MOREROWS="0"89F8COLNAME=2 ROTATE="0" MOREROWS="0"248COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user is already attached to the specified server.COLNAME=1 ROTATE="0" MOREROWS="0"89F9COLNAME=2 ROTATE="0" MOREROWS="0"249COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: One of the following reasons may apply:MARK=BULLETThe user tried to read without the necessary Read rights to access the property data.No connection slots are available.COLNAME=1 ROTATE="0" MOREROWS="0"89FACOLNAME=2 ROTATE="0" MOREROWS="0"250COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: One of the following reasons may apply:MARK=BULLETThe user tried to use an unknown path.No more server slots are available.COLNAME=1 ROTATE="0" MOREROWS="0"89FBCOLNAME=2 ROTATE="0" MOREROWS="0"251COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: One of the following reasons may apply:MARK=BULLETThe user tried to use a property that does not exist for the specified object.An attempt was made to use an invalid parameter (drive number, path, or flag value) during a set drive path call.COLNAME=1 ROTATE="0" MOREROWS="0"89FCCOLNAME=2 ROTATE="0" MOREROWS="0"252COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: One of the following reasons may apply:MARK=BULLETThe user tried to use a full message queue.The user tried to attach to a server using an invalid server name.COLNAME=1 ROTATE="0" MOREROWS="0"89FDCOLNAME=2 ROTATE="0" MOREROWS="0"253COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: One of the following reasons may apply:MARK=BULLETAn attempt was made to use a bad (undefined, unavailable, etc.) station number.The requesting packet did not have a 30 byte packet header as the first fragment, or its total length exceeded 576 characters.An unknown request was attempted.COLNAME=1 ROTATE="0" MOREROWS="0"89FECOLNAME=2 ROTATE="0" MOREROWS="0"254COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: One of the following reasons may apply:MARK=BULLETAn attempt was made to open a semaphore with an invalid semaphore name length. Semaphores use strings that are from 1 to 127 bytes long.An operation tried to use an unknown trustee.A failure occurred that was caused by the timeout limit expiring before the request was fulfilled.The user tried to log in when the supervisor has disabled logins from the console or the bindery was locked.An error occurred while spooling the directory.The user tried to use a locked directory.The user tried to use a server with a locked bindery.The user tried to use a bindery that is temporarily locked by the Supervisor.A packet cannot be delivered for any of the following possible reasons: (1) The destination node is on another network, and no router could be found with a path to the destination network.(2) The destination node address is on the local network, and the hardware detects that the destination node address is nonexistent or inactive. (3) The destination node is the same machine as the source node, and no pending listen request is on the destination socket number. (4) The destination socket number is not open.COLNAME=1 ROTATE="0" MOREROWS="0"89FFCOLNAME=2 ROTATE="0" MOREROWS="0"255COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: One of the following reasons may apply:MARK=BULLETNo files were found that matched the search specification.The user tried to use a drive with an invalid number.The program tried to open a semaphore with an invalid semaphore value. The semaphore value must be positive, and it must be initialized to a value from 0 to 127.The user tried to use a file with a bad (undefined, unavailable, etc.) name or extension.COLNAME=1 ROTATE="0" MOREROWS="0"89FF COLNAME=2 ROTATE="0" MOREROWS="0"255COLNAME=3 ROTATE="0" MOREROWS="0"(Continued)MARK=BULLETThe program tried to examine, wait for, or signal a semaphore with an invalid semaphore handle. The semaphore handle is obtained through the "open a semaphore" call.The program tried to find an unknown path during a "get full path" call.The user tried to use a queue with 99 entries in it. (99 is the maximum number of entries that can be placed in each print queue.)The user tried to use a bad (undefined, unavailable, etc.) printer.There are no outstanding NCP requests at the present time.The program tried to open a socket whose specified socket number is already open.An attempt was made to use an unfound object, or attempt to use a bad (undefined, unavailable, etc.) password. On a login call, this indicates the password was correct, but it has expired and all grace logins have been used up. On a change password call, it indicates that the old password given was correct, but the account is not allowed to change the password (typical of the GUEST account).No files were found that matched the search specification.An error occurred closing the file.The user tried to use a locked file.The program tried to use an invalid offset value during physical locking calls.The program tried to write beyond the end of the file or disk.A hardware failure occurred.The user tried to use an invalid (undefined, unavailable, etc.) drive. (000F)COLNAME=1 ROTATE="0" MOREROWS="0"0101COLNAME=2 ROTATE="0" MOREROWS="0"257COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The print server exceeded the maximum number of NetWare servers it is configured for. In NetWare bindery mode, the print server can be configured for no more than eight servers.COLNAME=1 ROTATE="0" MOREROWS="0"0102COLNAME=2 ROTATE="0" MOREROWS="0"258COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The name the user gave for the NetWare server does not exist, or the NetWare server the print server is attached to cannot recognize the other NetWare server.COLNAME=1 ROTATE="0" MOREROWS="0"0103COLNAME=2 ROTATE="0" MOREROWS="0"259COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The print server made a call made to the bindery but found the bindery locked.COLNAME=1 ROTATE="0" MOREROWS="0"0104COLNAME=2 ROTATE="0" MOREROWS="0"260COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The print server tried to log in to the NetWare server, but exceeded the maximum number of users that can log in at the same time. The number of users allowed depends on the NetWare version.COLNAME=1 ROTATE="0" MOREROWS="0"0105COLNAME=2 ROTATE="0" MOREROWS="0"261COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The NetWare server is not responding to a login attempt from the print server.COLNAME=1 ROTATE="0" MOREROWS="0"0106COLNAME=2 ROTATE="0" MOREROWS="0"262COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The print server login to the NetWare server failed, because the print server was already logged in to it.COLNAME=1 ROTATE="0" MOREROWS="0"0107COLNAME=2 ROTATE="0" MOREROWS="0"263COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: This is a generic return code for unknown errors that occur when the print server is trying to attach to the NetWare server.COLNAME=1 ROTATE="0" MOREROWS="0"0108COLNAME=2 ROTATE="0" MOREROWS="0"264COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: Although Accounting was activated, no account property was created for the print server.COLNAME=1 ROTATE="0" MOREROWS="0"0109COLNAME=2 ROTATE="0" MOREROWS="0"265COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The NetWare server sends this message when the print server cannot log in, because the print server has exceeded its account balance.COLNAME=1 ROTATE="0" MOREROWS="0"010ACOLNAME=2 ROTATE="0" MOREROWS="0"266COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The print server locks up when the intruder detection lock is set and the user exceeds the number of login tries.COLNAME=1 ROTATE="0" MOREROWS="0"010BCOLNAME=2 ROTATE="0" MOREROWS="0"267COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The print server login to the NetWare server failed, because it did not have a connection. This may happen if there are no available connections on the Netware Server. Check the number of connections and retry.COLNAME=1 ROTATE="0" MOREROWS="0"010CCOLNAME=2 ROTATE="0" MOREROWS="0"268COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: Although an account exists, it has been disabled.COLNAME=1 ROTATE="0" MOREROWS="0"010DCOLNAME=2 ROTATE="0" MOREROWS="0"269COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The times during which the print server can log in to the NetWare server have been restricted.COLNAME=1 ROTATE="0" MOREROWS="0"010ECOLNAME=2 ROTATE="0" MOREROWS="0"270COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The locations from which the print server can log in to the NetWare server have been restricted.COLNAME=1 ROTATE="0" MOREROWS="0"010FCOLNAME=2 ROTATE="0" MOREROWS="0"271COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The print server has reached the maximum number of grace logins allowed to change its password.COLNAME=1 ROTATE="0" MOREROWS="0"0110COLNAME=2 ROTATE="0" MOREROWS="0"272COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The network supervisor has disabled all print servers from logging in to the NetWare server.COLNAME=1 ROTATE="0" MOREROWS="0"0111COLNAME=2 ROTATE="0" MOREROWS="0"273COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The print server's name is not a valid account name.COLNAME=1 ROTATE="0" MOREROWS="0"0112COLNAME=2 ROTATE="0" MOREROWS="0"274COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The print server's password needs to be changed.COLNAME=1 ROTATE="0" MOREROWS="0"0113COLNAME=2 ROTATE="0" MOREROWS="0"275COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The print server is not able to log in to the specified NetWare server because the print server name is invalid or the password is invalid.COLNAME=1 ROTATE="0" MOREROWS="0"0114COLNAME=2 ROTATE="0" MOREROWS="0"276COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: This is a generic return code for unknown errors that occur when the print server is trying to log in to the NetWare server.COLNAME=1 ROTATE="0" MOREROWS="0"0115COLNAME=2 ROTATE="0" MOREROWS="0"277COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The printer is already installed.COLNAME=1 ROTATE="0" MOREROWS="0"0116COLNAME=2 ROTATE="0" MOREROWS="0"278COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The configuration file cannot be opened.COLNAME=1 ROTATE="0" MOREROWS="0"0117COLNAME=2 ROTATE="0" MOREROWS="0"279COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The configuration file cannot be read.COLNAME=1 ROTATE="0" MOREROWS="0"0118COLNAME=2 ROTATE="0" MOREROWS="0"280COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The printer type specified is not listed in the print server configuration files or is defined elsewhere.COLNAME=1 ROTATE="0" MOREROWS="0"0119COLNAME=2 ROTATE="0" MOREROWS="0"281COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The maximum number of forms has been exceeded.COLNAME=1 ROTATE="0" MOREROWS="0"011ACOLNAME=2 ROTATE="0" MOREROWS="0"282COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The specified print job does not exist.COLNAME=1 ROTATE="0" MOREROWS="0"011BCOLNAME=2 ROTATE="0" MOREROWS="0"283COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The printer specified is unknown.COLNAME=1 ROTATE="0" MOREROWS="0"011CCOLNAME=2 ROTATE="0" MOREROWS="0"284COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: A print services communications error occurred.COLNAME=1 ROTATE="0" MOREROWS="0"011DCOLNAME=2 ROTATE="0" MOREROWS="0"285COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The specified mode is not supported.COLNAME=1 ROTATE="0" MOREROWS="0"0200COLNAME=2 ROTATE="0" MOREROWS="0"512COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The queue that the print server is trying to attach to cannot be located. Verify the queue name.COLNAME=1 ROTATE="0" MOREROWS="0"0201COLNAME=2 ROTATE="0" MOREROWS="0"513COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The print server is not authorized to service the queue it needs to attach to.COLNAME=1 ROTATE="0" MOREROWS="0"0202COLNAME=2 ROTATE="0" MOREROWS="0"514COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The queue that the print server is trying to attach to was previously placed on hold.COLNAME=1 ROTATE="0" MOREROWS="0"0203COLNAME=2 ROTATE="0" MOREROWS="0"515COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: This is a generic return code for unknown errors that occur when the print server is trying to attach to a queue.COLNAME=1 ROTATE="0" MOREROWS="0"0204COLNAME=2 ROTATE="0" MOREROWS="0"516COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The number of queue servers that can attach to a queue was exceeded.COLNAME=1 ROTATE="0" MOREROWS="0"0300COLNAME=2 ROTATE="0" MOREROWS="0"768COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: An unrecognizable request was made.COLNAME=1 ROTATE="0" MOREROWS="0"0301COLNAME=2 ROTATE="0" MOREROWS="0"769COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The print server could not allocate sufficient memory to complete the request.COLNAME=1 ROTATE="0" MOREROWS="0"0302COLNAME=2 ROTATE="0" MOREROWS="0"770COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The specified printer is unrecognizable.COLNAME=1 ROTATE="0" MOREROWS="0"0303COLNAME=2 ROTATE="0" MOREROWS="0"771COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The function call contains unrecognizable parameters.COLNAME=1 ROTATE="0" MOREROWS="0"0304COLNAME=2 ROTATE="0" MOREROWS="0"772COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: You must pause the printer before giving this command, or wait until the job is completed.COLNAME=1 ROTATE="0" MOREROWS="0"0305COLNAME=2 ROTATE="0" MOREROWS="0"773COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: You can detach the print server from all NetWare servers, except the primary server.COLNAME=1 ROTATE="0" MOREROWS="0"0306COLNAME=2 ROTATE="0" MOREROWS="0"774COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The print server is going down. All commands will be ignored except for Cancel Down.COLNAME=1 ROTATE="0" MOREROWS="0"0307COLNAME=2 ROTATE="0" MOREROWS="0"775COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The command could not be completed because the printer is not connected.COLNAME=1 ROTATE="0" MOREROWS="0"0308COLNAME=2 ROTATE="0" MOREROWS="0"776COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The slot number you specified for the remote printer is already in use. You cannot attach the remote printer to the print server using this number.COLNAME=1 ROTATE="0" MOREROWS="0"0309COLNAME=2 ROTATE="0" MOREROWS="0"777COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: There were no active jobs when the command was issued.COLNAME=1 ROTATE="0" MOREROWS="0"030ACOLNAME=2 ROTATE="0" MOREROWS="0"778COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The print server is not attached to the specified NetWare server.COLNAME=1 ROTATE="0" MOREROWS="0"030BCOLNAME=2 ROTATE="0" MOREROWS="0"779COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The queue you tried to attach to is already on the list, or the user you tried to add to the notify list is already on the list.COLNAME=1 ROTATE="0" MOREROWS="0"030CCOLNAME=2 ROTATE="0" MOREROWS="0"780COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The print server is down.COLNAME=1 ROTATE="0" MOREROWS="0"030DCOLNAME=2 ROTATE="0" MOREROWS="0"781COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The queue you tried to change is not on the list, or the "notify user" you tried to change is not on the list.COLNAME=1 ROTATE="0" MOREROWS="0"030ECOLNAME=2 ROTATE="0" MOREROWS="0"782COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: You have insufficient rights to give this command.COLNAME=1 ROTATE="0" MOREROWS="0"030FCOLNAME=2 ROTATE="0" MOREROWS="0"783COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: An unsupported command was issued.COLNAME=1 ROTATE="0" MOREROWS="0"0400COLNAME=2 ROTATE="0" MOREROWS="0"1024COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The print server cannot verify the username used in the login to the print server.COLNAME=1 ROTATE="0" MOREROWS="0"0401COLNAME=2 ROTATE="0" MOREROWS="0"1025COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: One of the following reasons may apply:MARK=BULLETThe command you sent only applies to remote printers.No information is available.COLNAME=1 ROTATE="0" MOREROWS="0"0402COLNAME=2 ROTATE="0" MOREROWS="0"1026COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: No information for this error code is available.COLNAME=1 ROTATE="0" MOREROWS="0"0500COLNAME=2 ROTATE="0" MOREROWS="0"1280COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The XNP (extended network printer) is trying to attach to the print server before the print server is ready.COLNAME=1 ROTATE="0" MOREROWS="0"0501COLNAME=2 ROTATE="0" MOREROWS="0"1281COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The function call requires process switching, but it failed while performing the switching.COLNAME=1 ROTATE="0" MOREROWS="0"0502COLNAME=2 ROTATE="0" MOREROWS="0"1282COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The function call requires a job ID, but the job ID given is not valid.COLNAME=1 ROTATE="0" MOREROWS="0"0503COLNAME=2 ROTATE="0" MOREROWS="0"1283COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The message index points to a message file that does not exist.COLNAME=1 ROTATE="0" MOREROWS="0"0504COLNAME=2 ROTATE="0" MOREROWS="0"1284COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: A job request is outstanding. No more job requests are allowed until the current one is completed or cancelled.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFD45COLNAME=2 ROTATE="0" MOREROWS="0"-699COLNAME=3 ROTATE="0" MOREROWS="0"Description: Unknown.Explanation: An unrecoverable error has occurred and the operation cannot be completed. Action:Contact your Novell Authorized Reseller. COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFD54COLNAME=2 ROTATE="0" MOREROWS="0"-684COLNAME=3 ROTATE="0" MOREROWS="0"Description: Secure NCP violation.Explanation: No information for this error code is available.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFD55COLNAME=2 ROTATE="0" MOREROWS="0"-683COLNAME=3 ROTATE="0" MOREROWS="0"Description: Invalid API version.Explanation: An invalid application API is being used.Action: Update your software.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFD56COLNAME=2 ROTATE="0" MOREROWS="0"-682COLNAME=3 ROTATE="0" MOREROWS="0"Description: Auditing failed.Explanation: The auditing function failed.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFD57COLNAME=2 ROTATE="0" MOREROWS="0"-681COLNAME=3 ROTATE="0" MOREROWS="0"Description: Alias of an alias.Explanation: An attempt was made to use an alias of an alias.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFD58COLNAME=2 ROTATE="0" MOREROWS="0"-680COLNAME=3 ROTATE="0" MOREROWS="0"Description: An attempt was made to use a reference that is not a subordinate reference.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFD59COLNAME=2 ROTATE="0" MOREROWS="0"-679COLNAME=3 ROTATE="0" MOREROWS="0"Description: Partition already exists.Explanation: An attempt was made to create a partition that already exists.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFD5ACOLNAME=2 ROTATE="0" MOREROWS="0"-678COLNAME=3 ROTATE="0" MOREROWS="0"Description: Duplicate ACL.Explanation: No information for this error code is available.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFD5FCOLNAME=2 ROTATE="0" MOREROWS="0"-673COLNAME=3 ROTATE="0" MOREROWS="0"Description: Replica not on.Explanation: The replica is being created on a server. Until all the object information has been received on that server, the replica is "off" (not available for use by Directory clients).Action: Wait until the replica is created on the other server.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFD60COLNAME=2 ROTATE="0" MOREROWS="0"-672COLNAME=3 ROTATE="0" MOREROWS="0"Description: No access.Explanation: The client does not have the appropriate rights to perform the requested operation.Action: If appropriate, grant the client the appropriate rights to perform the requested operation.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFD61COLNAME=2 ROTATE="0" MOREROWS="0"-671COLNAME=3 ROTATE="0" MOREROWS="0"Description: No such parent.Explanation: A parent was specified that does not exist.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFD63COLNAME=2 ROTATE="0" MOREROWS="0"-669COLNAME=3 ROTATE="0" MOREROWS="0"Description: Failed authentication.Explanation: The Directory database is locked on the server. An invalid password was sent. Authentication failed.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFD64COLNAME=2 ROTATE="0" MOREROWS="0"-668COLNAME=3 ROTATE="0" MOREROWS="0"Description: Entry not container.Explanation: An illegal function was attempted on a leaf object.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFD65COLNAME=2 ROTATE="0" MOREROWS="0"-667COLNAME=3 ROTATE="0" MOREROWS="0"Description: Partition root.Explanation: The object being manipulated is the root of a Directory Services partition. This error appears most often when attempting to delete a container object that is a partition root.Action: Use the partition management tools to merge this partition into the parent partition.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFD67COLNAME=2 ROTATE="0" MOREROWS="0"-665COLNAME=3 ROTATE="0" MOREROWS="0"Description: New epoch.Explanation: This is an NDS time stamp error.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFD68COLNAME=2 ROTATE="0" MOREROWS="0"-664COLNAME=3 ROTATE="0" MOREROWS="0"Description: Old epoch.Explanation: This is an NDS time stamp error.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFD69COLNAME=2 ROTATE="0" MOREROWS="0"-663COLNAME=3 ROTATE="0" MOREROWS="0"Description: DS locked. Explanation: The Directory database is locked on the server.Action: If necessary, run SDREPAIR on the server.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFD6ACOLNAME=2 ROTATE="0" MOREROWS="0"-662COLNAME=3 ROTATE="0" MOREROWS="0"Description: DS volume IO failure.Explanation: An I/O failure occurred on the Directory Services volume.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFD6BCOLNAME=2 ROTATE="0" MOREROWS="0"-661COLNAME=3 ROTATE="0" MOREROWS="0"Description: DS volume not mounted.Explanation: The Directory Services volume is not mounted.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFD6CCOLNAME=2 ROTATE="0" MOREROWS="0"-660COLNAME=3 ROTATE="0" MOREROWS="0"Description: Record in use.Explanation: The requested record is already in use.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFD6DCOLNAME=2 ROTATE="0" MOREROWS="0"-659COLNAME=3 ROTATE="0" MOREROWS="0"Description: Time not synchronized.Explanation: NetWare Directory Services uses time stamps to determine the order of events that take place in the Directory. Time Synchronization Services has been implemented to maintain a consistent time across the network.Modification operations require the issuance of time stamp. If a replica on a server has issued a time stamp and the time on that server is set back, no further modification operations may take place until the time on the server moves past the last modification time on the partition. This applies only to operations that modify, not those that just read information.Action: Use Partition Manager's Rebuild Replicas to reset the time stamps to the current time and then wait for the replicas to synchronize. You may have to do this on a partition-by-partition basis.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFD6ECOLNAME=2 ROTATE="0" MOREROWS="0"-658COLNAME=3 ROTATE="0" MOREROWS="0"Description: Skulk in progress.Explanation: The function could not be completed because replica synchronization is in progress.Action: Wait awhile and try again.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFD6FCOLNAME=2 ROTATE="0" MOREROWS="0"-657COLNAME=3 ROTATE="0" MOREROWS="0"Description: Schema sync in progress.Explanation: The function could not be completed, because Directory synchronization is in progress. Action: Wait awhile and try again.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFD70COLNAME=2 ROTATE="0" MOREROWS="0"-656COLNAME=3 ROTATE="0" MOREROWS="0"Description: Crucial replica.Explanation: No information for this error code is available.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFD71COLNAME=2 ROTATE="0" MOREROWS="0"-655COLNAME=3 ROTATE="0" MOREROWS="0"Description: Multiple replicas.Explanation: No information for this error code is available.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFD72COLNAME=2 ROTATE="0" MOREROWS="0"-654COLNAME=3 ROTATE="0" MOREROWS="0"Description: Partition busy.Explanation: Another partition operation is taking place. For example, if a request has previously been issued to split a partition, a second request for a split (even at another point in the same partition) results in this error.Action: Wait for the previous partition operation to synchronize completely.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFD73COLNAME=2 ROTATE="0" MOREROWS="0"-653COLNAME=3 ROTATE="0" MOREROWS="0"Description: Duplicate optional.Explanation: An attempt was made to create an NDS definition for a class that contained a duplicate optional name.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFD74COLNAME=2 ROTATE="0" MOREROWS="0"-652COLNAME=3 ROTATE="0" MOREROWS="0"Description: Duplicate mandatory.Explanation: An attempt was made to create an NDS definition for a class that contained a duplicate mandatory name.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFD75COLNAME=2 ROTATE="0" MOREROWS="0"-651COLNAME=3 ROTATE="0" MOREROWS="0"Description: Ambiguous naming.Explanation: An attempt was made to create an NDS definition for a class that contained an ambiguous containment name.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFD76COLNAME=2 ROTATE="0" MOREROWS="0"-650COLNAME=3 ROTATE="0" MOREROWS="0"Description: Ambiguous containment.Explanation: An attempt was made to create an NDS definition for a class that contained an ambiguous containment rule.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFD77COLNAME=2 ROTATE="0" MOREROWS="0"-649COLNAME=3 ROTATE="0" MOREROWS="0"Description: Insufficient buffer.Explanation: The server ran out of memory.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFD78COLNAME=2 ROTATE="0" MOREROWS="0"-648COLNAME=3 ROTATE="0" MOREROWS="0"Description: Insufficient stack.Explanation: The server stack was not large enough.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFD79COLNAME=2 ROTATE="0" MOREROWS="0"-647COLNAME=3 ROTATE="0" MOREROWS="0"Description: Not Root partition.Explanation: An attempt was made to execute a function that is required on the root partition. The client did not pass in the root partition name, or the client tried to perform the function somewhere besides the root partition.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFD7ACOLNAME=2 ROTATE="0" MOREROWS="0"-646COLNAME=3 ROTATE="0" MOREROWS="0"Description: Bad naming attributes.Explanation: Invalid naming properties were used.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFD7BCOLNAME=2 ROTATE="0" MOREROWS="0"-645COLNAME=3 ROTATE="0" MOREROWS="0"Description: Class already exists.Explanation: The object Class being created already exists as a Class in the schema of the Directory. (See IDREF="FM35683""-604").Action: This error should only occur in a utility that updated the schema of the Directory. NetWare 4 does not include a utility to modify the schema. Determine the utility causing the error.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFD7CCOLNAME=2 ROTATE="0" MOREROWS="0"-644COLNAME=3 ROTATE="0" MOREROWS="0"Description: Schema is in use.Explanation: An attempt was made to delete an NDS configuration or structure (such as a container object) that still contains an object using that structure.Action: Delete the object or property then the structure.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFD7DCOLNAME=2 ROTATE="0" MOREROWS="0"-643COLNAME=3 ROTATE="0" MOREROWS="0"Description: Schema is nonremovable.Explanation: An attempt was made to delete an NDS structure or configuration.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFD7ECOLNAME=2 ROTATE="0" MOREROWS="0"-642COLNAME=3 ROTATE="0" MOREROWS="0"Description: Invalid iteration.Explanation: An iteration handle sent by a client workstation is invalid.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFD7FCOLNAME=2 ROTATE="0" MOREROWS="0"-641COLNAME=3 ROTATE="0" MOREROWS="0"Description: Invalid request.Explanation: The server did not understand the request. For example, a verb sent by a client workstation could be incorrect.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFD81COLNAME=2 ROTATE="0" MOREROWS="0"-639COLNAME=3 ROTATE="0" MOREROWS="0"Description: Incomplete authentication.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFD82COLNAME=2 ROTATE="0" MOREROWS="0"-638COLNAME=3 ROTATE="0" MOREROWS="0"Description: No character mapping.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFD83COLNAME=2 ROTATE="0" MOREROWS="0"-637COLNAME=3 ROTATE="0" MOREROWS="0"Description: Previous move in progress.Explanation: After an object has been moved from one context in the Directory to another, the Directory will not allow that object to be moved again until all replicas of that object have been updated. The length of time will vary depending on the size of the replica, the number of replicas, and the condition of the communication links between all the servers holding the replicas.Action: Leave the object in its current context until it can be moved again. This may require that the object be left in its new context for several minutes.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFD84COLNAME=2 ROTATE="0" MOREROWS="0"-636COLNAME=3 ROTATE="0" MOREROWS="0"Description: Unreachable server.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFD85COLNAME=2 ROTATE="0" MOREROWS="0"-635COLNAME=3 ROTATE="0" MOREROWS="0"Description: Remote failure.Explanation: To complete some operations, a server will need to contact another server. If this is not possible (due to a link being down, for example), this error is returned.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFD86COLNAME=2 ROTATE="0" MOREROWS="0"-634COLNAME=3 ROTATE="0" MOREROWS="0"Description: No referrals.Explanation: The server has no objects that match the request and has no referrals on which to search for the object.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFD87COLNAME=2 ROTATE="0" MOREROWS="0"-633COLNAME=3 ROTATE="0" MOREROWS="0"Description: Invalid entry for Root.Explanation: An invalid entry for the root was made.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFD88COLNAME=2 ROTATE="0" MOREROWS="0"-632COLNAME=3 ROTATE="0" MOREROWS="0"Description: System failure.Explanation: Unexpected results have occurred. For example, the client requested that the Directory return a network address attribute, and the Directory actually returned a public key attribute.This condition may be temporary. While the client usually returns errors in the -301 to -399 range, the client as well as the server returns this error during the authentication process.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFD89COLNAME=2 ROTATE="0" MOREROWS="0"-631COLNAME=3 ROTATE="0" MOREROWS="0"Description: Illegal replica type.Explanation: A replica needed to perform this function was not found. Typically you will receive this error when you attempt to set your bindery context at the server console and the server does not have a Read Write replica of the container you are attempting to reference in the bindery context.Action: Use Partition Manager to add a replica that includes the bindery context to that server.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFD8ACOLNAME=2 ROTATE="0" MOREROWS="0"-630COLNAME=3 ROTATE="0" MOREROWS="0"Description: Different tree.Explanation: No information for this error code is available.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFD8BCOLNAME=2 ROTATE="0" MOREROWS="0"-629COLNAME=3 ROTATE="0" MOREROWS="0"Description: Entry is not leaf.Explanation: The object being deleted or modified is not a leaf object. A container object that does not contain any objects is considered a leaf object, and therefore can be deleted.If you attempt to delete a container object that contains an object of any Class, the following error is returned. "The utility can't delete Object_Class=Object_name because it is not a leaf object." A container object that is a partition root cannot be deleted.Action: Delete all objects under the container object that is being deleted or modified. If the object is a partition root, merge the partition with the parent partition and then delete the object.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFD8CCOLNAME=2 ROTATE="0" MOREROWS="0"-628COLNAME=3 ROTATE="0" MOREROWS="0"Description: Object class violation.Explanation: An object class violation has occurred.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFD8DCOLNAME=2 ROTATE="0" MOREROWS="0"-627COLNAME=3 ROTATE="0" MOREROWS="0"Description: Can't remove naming value.Explanation: An attempt was made to delete the naming property. You must rename the object; then delete the property.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFD8ECOLNAME=2 ROTATE="0" MOREROWS="0"-626COLNAME=3 ROTATE="0" MOREROWS="0"Description: All referrals failed.Explanation: All referrals failed. The object could not be found. It is possible that the object exists, but the server could not communicate with the server holding a copy of the object. This error message is common when partition management is requested and events cannot occur because a server is inaccessible. This may be a temporary condition during partition functions.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFD8FCOLNAME=2 ROTATE="0" MOREROWS="0"-625COLNAME=3 ROTATE="0" MOREROWS="0"Description: Transport failure.Explanation: The server is unable to communicate across the network for one or more of the following reasons: a server is down, a bridge or other physical connection is down between servers, or a server cannot be found.Action: Check cabling and LAN communications. Check the server names and network addresses. Make sure that they have not changed since this server has been installed into the Directory. If they have, set them back to the original settings (if available) and see if the error goes away. After all the connections have been reestablished, this message may take up to 5 minutes to go away.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFD90COLNAME=2 ROTATE="0" MOREROWS="0"-624COLNAME=3 ROTATE="0" MOREROWS="0"Description: Replica already exists.Explanation: A replica of the specified partition already exists on the server. Action: Select a different server. A partition should have no more than seven or eight replicas.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFD91COLNAME=2 ROTATE="0" MOREROWS="0"-623COLNAME=3 ROTATE="0" MOREROWS="0"Description: Syntax invalid in name.Explanation: The syntax for the name provided is invalid.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFD92COLNAME=2 ROTATE="0" MOREROWS="0"-622COLNAME=3 ROTATE="0" MOREROWS="0"Description: Invalid transport.Explanation: The type of transport passed in to the server is not supported by the server.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFD93COLNAME=2 ROTATE="0" MOREROWS="0"-621COLNAME=3 ROTATE="0" MOREROWS="0"Description: Transactions disabled.Explanation: The Transaction Tracking Service (TTS) has been disabled for the sever on which the Directory operation is taking place. When TTS is disabled, Directory Services operations that require modifying the database on that server are disabled as well.Action: At the console prompt of the file server, type "ENABLE TTS". If TTS was disabled because volume SYS: is full, log in to the server and delete unnecessary files from volume SYS: and then type "ENABLE TTS" at the console.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFD94COLNAME=2 ROTATE="0" MOREROWS="0"-620COLNAME=3 ROTATE="0" MOREROWS="0"Description: Comparison failed.Explanation: A comparison of some kind failed.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFD95COLNAME=2 ROTATE="0" MOREROWS="0"-619COLNAME=3 ROTATE="0" MOREROWS="0"Description: Invalid comparison.Explanation: An attempt was made to (1) compare two properties that are not comparable or (2) use an invalid compare syntax.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFD96COLNAME=2 ROTATE="0" MOREROWS="0"-618COLNAME=3 ROTATE="0" MOREROWS="0"Description: Inconsistent database.Explanation: The server has detected an inconsistent database. Usually this means that the number of entries in a container does not match the number stored in the container's entry.Action: Run DSREPAIR.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFD97COLNAME=2 ROTATE="0" MOREROWS="0"-617COLNAME=3 ROTATE="0" MOREROWS="0"Description: Database format. Explanation: The database format is invalid.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFD98COLNAME=2 ROTATE="0" MOREROWS="0"-616COLNAME=3 ROTATE="0" MOREROWS="0"Description: Maximum entries exist.Explanation: The maximum entries (objects) exist in the Directory tree. The maximum number of objects that can be created in the Directory is FFFFFF (3 bits of FF), which equals 16,777,220 decimal.Action: For the current version of the Directory, you have reached the maximum number of objects that can be created. To continue, delete objects that are no longer needed.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFD99COLNAME=2 ROTATE="0" MOREROWS="0"-615COLNAME=3 ROTATE="0" MOREROWS="0"Description: Attribute already exists.Explanation: An attempt was made to add a property that already exists.Action: If the attribute is multivalued, just add the specified value to the existing property. If the property is single valued, delete the property and create it again with the new value.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFD9ACOLNAME=2 ROTATE="0" MOREROWS="0"-614COLNAME=3 ROTATE="0" MOREROWS="0"Description: Duplicate value.Explanation: An attempt was made to add a duplicate value to the specified property.Action: Enter a different value.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFD9BCOLNAME=2 ROTATE="0" MOREROWS="0"-613COLNAME=3 ROTATE="0" MOREROWS="0"Description: Syntax violation.Explanation: An attribute value being added to an object is incorrect. This error is most often encountered if that value is the name of another object and that does not exist.Action: For most cases, verify that the object name being added as a value is correct.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFD9CCOLNAME=2 ROTATE="0" MOREROWS="0"-612COLNAME=3 ROTATE="0" MOREROWS="0"Description: Can't have multiple values.Explanation: The specified property is single valued. All properties are single or multivalued. For example, the Group Membership property is multivalued. A user can be a member of multiple groups. the Group Membership property exists once and contains multiple group names (values).Action: For this property (information category in the utility), only one value (piece of information) can be supplied.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFD9DCOLNAME=2 ROTATE="0" MOREROWS="0"-611COLNAME=3 ROTATE="0" MOREROWS="0"Description: Illegal containment.Explanation: The containment rules of the Directory specify where an object class may appear in relation to other objects in the Directory tree. For example, the object Class Country can only be created at the top of the Directory, and the object Class User can only be created under Organizations and Organizational Units. The Schema enforces the containment rules for NetWare Directory Services.Action: Go to the appropriate container to create the object.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFD9ECOLNAME=2 ROTATE="0" MOREROWS="0"-610COLNAME=3 ROTATE="0" MOREROWS="0"Description: Illegal DS name.Explanation: Illegal Directory Names are those that are too long (more than 255 characters) or contain illegal character combinations. The "\" character can only be followed by a "." or "=" or "+" or "\".COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFD9FCOLNAME=2 ROTATE="0" MOREROWS="0"-609COLNAME=3 ROTATE="0" MOREROWS="0"Description: Missing mandatory.Explanation: One or more of the mandatory properties for the object being created is missing. Each object class in the Directory has a set of mandatory properties (properties that must contain a value before the object can be created). For example, a User object in the Directory is required to have a Common Name (CN) and a Surname. Without these properties, the object will not be created. A property exists only if there is a value specified for the given property.Action: Input the required information when creating the object.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFDA0COLNAME=2 ROTATE="0" MOREROWS="0"-608COLNAME=3 ROTATE="0" MOREROWS="0"Description: Illegal attribute.Explanation: An attempt was made to add a property that is illegal to an object. The NetWare Directory Services schema determines what properties can be inherited by an object class. (Refer to the NetWare Directory Services Schema documentation if available.)Action: You cannot add the specified property to the specified object.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFDA1COLNAME=2 ROTATE="0" MOREROWS="0"-607COLNAME=3 ROTATE="0" MOREROWS="0"Description: Not effective class.Explanation: This error indicates that the class being used to create the specified object is a noneffective class and cannot be used when creating an object. Two types of object classes exist in the Directory: effective and noneffective. All effective classes can be used when creating objects (the class being used to create the specified object is referred to as the "base class" of the object). Users is one example of an effective class. Noneffective classes are used as super classes to define information associated with various effective classes.Action: The standard Novell utilities that ship with NetWare 4 only allow effective classes to be used when creating objects. Find out what utility is being used to create the object. This utility is not following the rules of the specified object.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFDA2COLNAME=2 ROTATE="0" MOREROWS="0"-606COLNAME=3 ROTATE="0" MOREROWS="0"Description: Entry already exists.Explanation: An attempt was made to add an object at the same level as a preexisting object of the same name but not necessarily the same Class.Action: Specify a different name for the object being added or rename the existing object.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFDA3COLNAME=2 ROTATE="0" MOREROWS="0"-605COLNAME=3 ROTATE="0" MOREROWS="0"Description: No such partition.Explanation: A partition with the specified name does not exist. A partition in the directory is named by the root object of the specified partition. The very first partition in the Directory is [Root], which is the top of the directory.Action: Ensure that the partition name requested is valid and is a valid object name.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFDA4COLNAME=2 ROTATE="0" MOREROWS="0"ID="FM35683"-604COLNAME=3 ROTATE="0" MOREROWS="0"Description: No such class.Explanation: An object class that does not exist in the Directory is being referenced by a utility. Object class in NetWare Directory Services is similar to object type in the bindery. For example, object type 1 in the bindery is a user object; and in the Directory, the object Class is USER. The class indicates the kind of object to be created.Action: NetWare 4 utilities access only Novell's base schema that must be present for the Directory to operate. Determine what utility is being used to create the object. This utility is attempting to use an object class that is not defined in NetWare Directory Services. The shipping set of NetWare 4 utilities only displays valid object classes.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFDA5COLNAME=2 ROTATE="0" MOREROWS="0"-603COLNAME=3 ROTATE="0" MOREROWS="0"Description: No such attribute.Explanation: The requested property could not be found. In the Directory, if a property does not contain a value then the property does not exist for the specific object.Action: Ensure that the property being requested is a valid Directory Services property (check spelling and syntax). Use NLIST to determine if the property exists for the specified object. For example, NLIST user=username/d will show all properties and their values for the specified username. (Note: To see all of the properties associated to the object requires Supervisor rights to the object. Browse rights are given by default.)COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFDA6COLNAME=2 ROTATE="0" MOREROWS="0"-602COLNAME=3 ROTATE="0" MOREROWS="0"Description: No such value.Explanation: The requested property value could not be found.Action: Use NLIST to determine if the value exists for the specified property. If this error is encountered during the login or authentication process, this error usually means that either the user's or the server's public keys could not be located. If this is the case, regenerate the user's key pair by changing the password with utilities.An occurrence of this error during the synchronization process between servers means one of the public keys cannot be located or the replica lists of one of the servers contains inconsistent results. This error may be a temporary condition that exists due to the loosely consistent nature of NetWare Directory Services.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFDA7COLNAME=2 ROTATE="0" MOREROWS="0"-601COLNAME=3 ROTATE="0" MOREROWS="0"Description: No such entry.Explanation: The object name entered could not be found in the context specified. The name may have been mistyped. The workstation's context may be incorrect for the object being sought. The leading dots or trailing dots may have been used incorrectly.Action: Check the context specified for the object name entered. If the command line input was the object name, check the workstation's context. Make sure that it points to the correct level of the Directory tree for the object name specified. If the input includes the object's full or partial context, make sure that the leading and trailing dots are specified appropriately and the types are correct.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFEA3COLNAME=2 ROTATE="0" MOREROWS="0"-354COLNAME=3 ROTATE="0" MOREROWS="0"Description: An attempt was made to move an object to the same place in the Directory tree that it already occupies.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFEA3COLNAME=2 ROTATE="0" MOREROWS="0"-353COLNAME=3 ROTATE="0" MOREROWS="0"Description: The name passed in exceeded 256 characters.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFEA3COLNAME=2 ROTATE="0" MOREROWS="0"-352COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: On logout, the server logged out of the monitor connection. Subsequently, the program tried and failed to find a writable replica of that monitor connection's partition.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFEA3COLNAME=2 ROTATE="0" MOREROWS="0"-349COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The Unicode tables were already loaded when the program tried to load them again.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFEA4COLNAME=2 ROTATE="0" MOREROWS="0"-348COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The Unicode file could not be found in the defined search algorithm.Action: For more information, see message IDREF="FM62778""973: The Unicode table files cannot be found in the NLS directory or in the search path. Code page: number Country: number" in Appendix C"973: The Unicode table files cannot be found in the NLS directory or in the search path. Code page: number Country: number" in Appendix C.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFEA5COLNAME=2 ROTATE="0" MOREROWS="0"-347COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: This error probably occurred when the user tried to create a new class of object with a class name that exceeded 32 characters.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFEA6COLNAME=2 ROTATE="0" MOREROWS="0"-346COLNAME=3 ROTATE="0" MOREROWS="0"Description: A Unicode translation error occurred. Explanation: This is probably an internal program error. COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFEA8COLNAME=2 ROTATE="0" MOREROWS="0"-344COLNAME=3 ROTATE="0" MOREROWS="0"Description: The Tagged Data Store (TDS) is either not initialized or corrupted.Explanation: This usually occurs when the NWDS Login function was not first called.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFEA9COLNAME=2 ROTATE="0" MOREROWS="0"-343COLNAME=3 ROTATE="0" MOREROWS="0"Description: The attribute name exceeded 128 characters.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFEAACOLNAME=2 ROTATE="0" MOREROWS="0"-342COLNAME=3 ROTATE="0" MOREROWS="0"Description: An invalid Directory Services name was found.Explanation: One of the following reasons may apply:MARK=BULLETAn empty string passed in for a name Null pointerCOLNAME=1 ROTATE="0" MOREROWS="0"FFFFFEACCOLNAME=2 ROTATE="0" MOREROWS="0"-340COLNAME=3 ROTATE="0" MOREROWS="0"Description: A transport failure occurred.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFEB1COLNAME=2 ROTATE="0" MOREROWS="0"-335COLNAME=3 ROTATE="0" MOREROWS="0"Description: Multi-AVAs exist.Explanation: AVAs cannot contain the same type.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFEB2COLNAME=2 ROTATE="0" MOREROWS="0"-334COLNAME=3 ROTATE="0" MOREROWS="0"Description: The RDN exceeded 128 characters.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFEB3COLNAME=2 ROTATE="0" MOREROWS="0"-333COLNAME=3 ROTATE="0" MOREROWS="0"Description: An invalid iteration handle was found.Explanation: This is probably an internal program error.Action: COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFEB5COLNAME=2 ROTATE="0" MOREROWS="0"-331COLNAME=3 ROTATE="0" MOREROWS="0"Description: A Null pointer was found when a Real pointer was expected.Action: Do not use a Null pointer.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFEB6COLNAME=2 ROTATE="0" MOREROWS="0"-330COLNAME=3 ROTATE="0" MOREROWS="0"Description: The server returned an invalid response.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFEB7COLNAME=2 ROTATE="0" MOREROWS="0"-329COLNAME=3 ROTATE="0" MOREROWS="0"Description: The server returned an "infotype" parameter that did not agree with the infotype passed in.Explanation: This is an internal program error.Action: COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFEB8COLNAME=2 ROTATE="0" MOREROWS="0"-328COLNAME=3 ROTATE="0" MOREROWS="0"Description: The context could not be created.Explanation: This error most often occurs when the Unicode files are not loaded.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFEBBCOLNAME=2 ROTATE="0" MOREROWS="0"-325COLNAME=3 ROTATE="0" MOREROWS="0"Description: Invalid attribute syntax was passed in.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFEBCCOLNAME=2 ROTATE="0" MOREROWS="0"-324COLNAME=3 ROTATE="0" MOREROWS="0"Description: The program tried to pass in a replica type that was not a Master, Secondary, or Read Only.Explanation: This is probably an internal program error.Action: COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFEBDCOLNAME=2 ROTATE="0" MOREROWS="0"-323COLNAME=3 ROTATE="0" MOREROWS="0"Description: The program tried to call NWDSAllocBuf with a zero- length size.Explanation: This is probably an internal program error.Action: COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFEBECOLNAME=2 ROTATE="0" MOREROWS="0"-322COLNAME=3 ROTATE="0" MOREROWS="0"Description: An invalid iteration handle was found.Explanation: This is probably an internal program error.Action: COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFEBFCOLNAME=2 ROTATE="0" MOREROWS="0"-321COLNAME=3 ROTATE="0" MOREROWS="0"Description: An API call that takes a server name could not connect to the specified server.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFEC0COLNAME=2 ROTATE="0" MOREROWS="0"-320COLNAME=3 ROTATE="0" MOREROWS="0"Description: The program is trying to restore an object at the root.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFEC1COLNAME=2 ROTATE="0" MOREROWS="0"-319COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: This is an internal program error.Action:  COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFEC2COLNAME=2 ROTATE="0" MOREROWS="0"-318COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: Country name identifiers are only allowed one character.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFEC3COLNAME=2 ROTATE="0" MOREROWS="0"-317COLNAME=3 ROTATE="0" MOREROWS="0"Description: The AVA type is incorrect.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFEC4COLNAME=2 ROTATE="0" MOREROWS="0"-316COLNAME=3 ROTATE="0" MOREROWS="0"Description: Too many trailing delimiter dots occurred in the name.Explanation: Only three context levels and four trailing dots are allowed in a name.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFEC5COLNAME=2 ROTATE="0" MOREROWS="0"-315COLNAME=3 ROTATE="0" MOREROWS="0"Description: An RDN delimiter (.) was expected and not found while the name was being parsed.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFEC6COLNAME=2 ROTATE="0" MOREROWS="0"-314COLNAME=3 ROTATE="0" MOREROWS="0"Description: The program is trying to pass a NULL string for object name to the API call or trying to pass a name containing both leading and trailing dots.Action: COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFEC7COLNAME=2 ROTATE="0" MOREROWS="0"-313COLNAME=3 ROTATE="0" MOREROWS="0"Description: The program is trying to delete an empty filter. Explanation: This is an internal program error.Action: COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFEC8COLNAME=2 ROTATE="0" MOREROWS="0"-312COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The multi-AVA name being parsed may not be typed. Action: All AVAs must be typed or not typed. COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFEC9COLNAME=2 ROTATE="0" MOREROWS="0"-311COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The multi-AVA name being parsed must be typed.Action: All AVAs must be typed or not typed.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFECACOLNAME=2 ROTATE="0" MOREROWS="0"-310COLNAME=3 ROTATE="0" MOREROWS="0"Description: An equal sign is expected in the name.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFECBCOLNAME=2 ROTATE="0" MOREROWS="0"-309COLNAME=3 ROTATE="0" MOREROWS="0"Description: The name being parsed is not typed.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFECCCOLNAME=2 ROTATE="0" MOREROWS="0"-308COLNAME=3 ROTATE="0" MOREROWS="0"Description: The program initialized the buffer with a verb not associated with the API call.Explanation: This is an internal program error.Action: COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFECDCOLNAME=2 ROTATE="0" MOREROWS="0"-307COLNAME=3 ROTATE="0" MOREROWS="0"Action: The program tried to get data from an empty buffer.Explanation: This is an internal program error.Action: COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFECECOLNAME=2 ROTATE="0" MOREROWS="0"-306COLNAME=3 ROTATE="0" MOREROWS="0"Description: The program tried to pass a bad syntax ID.Explanation: This is an internal program error.Action: COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFECFCOLNAME=2 ROTATE="0" MOREROWS="0"-305COLNAME=3 ROTATE="0" MOREROWS="0"Description: The program passed an empty list (a null pointer) to NWDSPutAttrVal.Explanation: This is an internal program error.Action: COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFED0COLNAME=2 ROTATE="0" MOREROWS="0"-304COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The workstation does not have room to add data to an input buffer.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFED1COLNAME=2 ROTATE="0" MOREROWS="0"-303COLNAME=3 ROTATE="0" MOREROWS="0"Description: The program is trying to pass a bad context parameter to an NDS call.Explanation: This is an internal program error.Action: COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFED2COLNAME=2 ROTATE="0" MOREROWS="0"-302COLNAME=3 ROTATE="0" MOREROWS="0"Description: The program is trying to pass a bad key parameter for a context call.Explanation: This is an internal program error.Action: COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFED3COLNAME=2 ROTATE="0" MOREROWS="0"-301COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The client workstation does not have enough available memory.COLNAME=1 ROTATE="0" MOREROWS="0"FFF01COLNAME=2 ROTATE="0" MOREROWS="0"-255COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: One of the following reasons may apply:MARK=BULLETAn error occurred closing the file.A hardware failure occurred.The user tried to use a file with a bad (undefined, unavailable, etc.) name or extension.The program tried to write beyond the end of the file or disk.There are no spooled files.The user tried to use a bad (undefined, unavailable, etc.) printer.A parameter is invalid.No files were found that matched the search specification.The user does not have the rights to change trustees.The target station is not logged in.The target station is not accepting messages.No information is available.COLNAME=1 ROTATE="0" MOREROWS="0"FFF02COLNAME=2 ROTATE="0" MOREROWS="0"-254COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: One of the following reasons apply:MARK=BULLETThe user tried to use a bindery that is temporarily locked by the Supervisor.The user tried to use a locked directory.An error occurred during an attempt to delete a spool.An operation tried to use an unknown trustee.COLNAME=1 ROTATE="0" MOREROWS="0"FFF03COLNAME=2 ROTATE="0" MOREROWS="0"-253COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: An attempt was made to use a bad (undefined, unavailable, etc.) station number.COLNAME=1 ROTATE="0" MOREROWS="0"FFF04COLNAME=2 ROTATE="0" MOREROWS="0"-252COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to use a full message queue.COLNAME=1 ROTATE="0" MOREROWS="0"FFF05COLNAME=2 ROTATE="0" MOREROWS="0"-251COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: One of the following reasons apply:MARK=BULLETThe user tried to use a property that does not exist for the specified object.An attempt was made to use an invalid parameter (drive number, path, or flag value) during a set drive path call.COLNAME=1 ROTATE="0" MOREROWS="0"FFF06COLNAME=2 ROTATE="0" MOREROWS="0"-250COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to use an unknown path.COLNAME=1 ROTATE="0" MOREROWS="0"FFF07COLNAME=2 ROTATE="0" MOREROWS="0"-249COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to read without the necessary Read rights to access the property data.COLNAME=1 ROTATE="0" MOREROWS="0"FFF08COLNAME=2 ROTATE="0" MOREROWS="0"-248COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user does not have the rights to write the property.COLNAME=1 ROTATE="0" MOREROWS="0"FFF09COLNAME=2 ROTATE="0" MOREROWS="0"-247COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to create a property without the necessary property rights for the object.COLNAME=1 ROTATE="0" MOREROWS="0"FFF0ACOLNAME=2 ROTATE="0" MOREROWS="0"-246COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to delete a property without the necessary property rights. If the user does not have the proper rights to view the property, then NCP_NO_SUCH_PROPERTY is returned.COLNAME=1 ROTATE="0" MOREROWS="0"FFF0BCOLNAME=2 ROTATE="0" MOREROWS="0"-245COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to create an object without the necessary security to create or change an object. Only Supervisors are allowed to create objects.COLNAME=1 ROTATE="0" MOREROWS="0"FFF0CCOLNAME=2 ROTATE="0" MOREROWS="0"-244COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to delete an object without the necessary rights to delete the object. Only the Supervisor can delete objects. Note that if the user does not have the right to see that the object exists, then NCP_NO_SUCH_OBJECT is returned.COLNAME=1 ROTATE="0" MOREROWS="0"FFF0DCOLNAME=2 ROTATE="0" MOREROWS="0"-243COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to rename an object without the necessary rights. Only the Supervisor can rename objects. Note that if the user does not have the rights to see that the object exists, then NCP_NO_SUCH_OBJECT is returned.COLNAME=1 ROTATE="0" MOREROWS="0"FFF0ECOLNAME=2 ROTATE="0" MOREROWS="0"-242COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user does not have rights to read the object.COLNAME=1 ROTATE="0" MOREROWS="0"FFF0FCOLNAME=2 ROTATE="0" MOREROWS="0"-241COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to assign a security level of a bindery object or property to be higher than the user's security level. This would make the object or property inaccessible to the user.COLNAME=1 ROTATE="0" MOREROWS="0"FFF10COLNAME=2 ROTATE="0" MOREROWS="0"-240COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to use a wildcard character or wild object type in a call where wildcards are not allowed.COLNAME=1 ROTATE="0" MOREROWS="0"FFF11COLNAME=2 ROTATE="0" MOREROWS="0"-239COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: A request was made with an object or property name containing illegal characters. Illegal characters in names are control characters, the comma, colon, semicolon, slash, backslash, question mark, asterisk, and tilde.COLNAME=1 ROTATE="0" MOREROWS="0"FFF12COLNAME=2 ROTATE="0" MOREROWS="0"-238COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to create an object that already exists.COLNAME=1 ROTATE="0" MOREROWS="0"FFF13COLNAME=2 ROTATE="0" MOREROWS="0"-237COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to create a property that already exists.COLNAME=1 ROTATE="0" MOREROWS="0"FFF14COLNAME=2 ROTATE="0" MOREROWS="0"-236COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to use a nonexisting segment. Segments must be written sequentially when a property is first created, but may be read and written in any order after they already exist.COLNAME=1 ROTATE="0" MOREROWS="0"FFF15COLNAME=2 ROTATE="0" MOREROWS="0"-235COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to use a nongroup property.COLNAME=1 ROTATE="0" MOREROWS="0"FFF16COLNAME=2 ROTATE="0" MOREROWS="0"-234COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to use an object that is not a member of the defined group property.COLNAME=1 ROTATE="0" MOREROWS="0"FFF17COLNAME=2 ROTATE="0" MOREROWS="0"-233COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to add an object that already exists to a group property.COLNAME=1 ROTATE="0" MOREROWS="0"FFF18COLNAME=2 ROTATE="0" MOREROWS="0"-232COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to use an item not associated with this property group or an item that has been deleted from this group.COLNAME=1 ROTATE="0" MOREROWS="0"FFF20COLNAME=2 ROTATE="0" MOREROWS="0"-224COLNAME=3 ROTATE="0" MOREROWS="0"Description: No more login connections are available.COLNAME=1 ROTATE="0" MOREROWS="0"FFF21COLNAME=2 ROTATE="0" MOREROWS="0"-223COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to log in using an expired account password but the login was allowed because the account had a grace login.COLNAME=1 ROTATE="0" MOREROWS="0"FFF22COLNAME=2 ROTATE="0" MOREROWS="0"-222COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to log in using an account password that has expired and all grace logins have also expired.COLNAME=1 ROTATE="0" MOREROWS="0"FFF24COLNAME=2 ROTATE="0" MOREROWS="0"-220COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to log in using an account that has expired or has been disabled by the supervisor.COLNAME=1 ROTATE="0" MOREROWS="0"FFF25COLNAME=2 ROTATE="0" MOREROWS="0"-219COLNAME=3 ROTATE="0" MOREROWS="0"Description: This queue is already attached to the maximum number of servers allowed.Explanation: The user tried to log in from an unauthorized station using an account with limits to a specific network or station.COLNAME=1 ROTATE="0" MOREROWS="0"FFF26COLNAME=2 ROTATE="0" MOREROWS="0"-218COLNAME=3 ROTATE="0" MOREROWS="0"Description: The queue has been halted.Explanation: The user tried to log in during an unauthorized time of day specified for the account.COLNAME=1 ROTATE="0" MOREROWS="0"FFF27COLNAME=2 ROTATE="0" MOREROWS="0"-217COLNAME=3 ROTATE="0" MOREROWS="0"Description: The queue station is not a server.Explanation: The user tried to log in using an account that has limits on the number of concurrent connections, and that number has been reached.COLNAME=1 ROTATE="0" MOREROWS="0"FFF28COLNAME=2 ROTATE="0" MOREROWS="0"-216COLNAME=3 ROTATE="0" MOREROWS="0"Description: The queue is not active at this time.Explanation: The user tried to change a password to a password with fewer characters than the required minimum specified for the account.COLNAME=1 ROTATE="0" MOREROWS="0"FFF29COLNAME=2 ROTATE="0" MOREROWS="0"-215COLNAME=3 ROTATE="0" MOREROWS="0"Description: The queue is in service at this time.Explanation: The user tried to change a password to a previously used password when the unique password requirement is specified for the account.COLNAME=1 ROTATE="0" MOREROWS="0"FFF2ACOLNAME=2 ROTATE="0" MOREROWS="0"-214COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: No information for this error code is available.COLNAME=1 ROTATE="0" MOREROWS="0"FFF2BCOLNAME=2 ROTATE="0" MOREROWS="0"-213COLNAME=3 ROTATE="0" MOREROWS="0"Description: No jobs are in the queue.COLNAME=1 ROTATE="0" MOREROWS="0"FFF2ECOLNAME=2 ROTATE="0" MOREROWS="0"-210COLNAME=3 ROTATE="0" MOREROWS="0"Description: No queue server has been specified.COLNAME=1 ROTATE="0" MOREROWS="0"FFF2FCOLNAME=2 ROTATE="0" MOREROWS="0"-209COLNAME=3 ROTATE="0" MOREROWS="0"Description: No queues are defined.COLNAME=1 ROTATE="0" MOREROWS="0"FFF30COLNAME=2 ROTATE="0" MOREROWS="0"-208COLNAME=3 ROTATE="0" MOREROWS="0"Description: A queue I/O error occurred.COLNAME=1 ROTATE="0" MOREROWS="0"FFF3ACOLNAME=2 ROTATE="0" MOREROWS="0"-198COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to use console privileges without operator privileges.COLNAME=1 ROTATE="0" MOREROWS="0"FFF3BCOLNAME=2 ROTATE="0" MOREROWS="0"-197COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to log in after the system had locked the account because of intruder detection.COLNAME=1 ROTATE="0" MOREROWS="0"FFF3CCOLNAME=2 ROTATE="0" MOREROWS="0"-196COLNAME=3 ROTATE="0" MOREROWS="0"Description: Accounting has been disabled.COLNAME=1 ROTATE="0" MOREROWS="0"FFF3DCOLNAME=2 ROTATE="0" MOREROWS="0"-195COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: No information for this error code is available.COLNAME=1 ROTATE="0" MOREROWS="0"FFF3ECOLNAME=2 ROTATE="0" MOREROWS="0"-194COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to log in to an account with no credit available.COLNAME=1 ROTATE="0" MOREROWS="0"FFF3FCOLNAME=2 ROTATE="0" MOREROWS="0"-193COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to log in to an account with no credit available.COLNAME=1 ROTATE="0" MOREROWS="0"FFF40COLNAME=2 ROTATE="0" MOREROWS="0"-192COLNAME=3 ROTATE="0" MOREROWS="0"Description: The user has no accounting privileges.COLNAME=1 ROTATE="0" MOREROWS="0"FFF41COLNAME=2 ROTATE="0" MOREROWS="0"-191COLNAME=3 ROTATE="0" MOREROWS="0"Description: The name space name is invalid.COLNAME=1 ROTATE="0" MOREROWS="0"FFF42COLNAME=2 ROTATE="0" MOREROWS="0"-190COLNAME=3 ROTATE="0" MOREROWS="0"Description: Data streams are invalid.COLNAME=1 ROTATE="0" MOREROWS="0"FFF58COLNAME=2 ROTATE="0" MOREROWS="0"-168COLNAME=3 ROTATE="0" MOREROWS="0"Description: Access has been denied.COLNAME=1 ROTATE="0" MOREROWS="0"FFF59COLNAME=2 ROTATE="0" MOREROWS="0"-167COLNAME=3 ROTATE="0" MOREROWS="0"Description: An invalid resource tag was encountered.COLNAME=1 ROTATE="0" MOREROWS="0"FFF5ACOLNAME=2 ROTATE="0" MOREROWS="0"-166COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: No information for this error code is available.COLNAME=1 ROTATE="0" MOREROWS="0"FFF5BCOLNAME=2 ROTATE="0" MOREROWS="0"-165COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: No information for this error code is available.COLNAME=1 ROTATE="0" MOREROWS="0"FFF5CCOLNAME=2 ROTATE="0" MOREROWS="0"-164COLNAME=3 ROTATE="0" MOREROWS="0"Description: The user tried to rename a directory with an invalid name.COLNAME=1 ROTATE="0" MOREROWS="0"FFF5DCOLNAME=2 ROTATE="0" MOREROWS="0"-163COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: No information for this error code is available.COLNAME=1 ROTATE="0" MOREROWS="0"FFF5ECOLNAME=2 ROTATE="0" MOREROWS="0"-162COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to read a file where data is physically locked.COLNAME=1 ROTATE="0" MOREROWS="0"FFF5FCOLNAME=2 ROTATE="0" MOREROWS="0"-161COLNAME=3 ROTATE="0" MOREROWS="0"Description: A nonrecoverable I/O error has occurred on the disk in the directory area. This error has occurred in both copies of the directory and is fatal.COLNAME=1 ROTATE="0" MOREROWS="0"FFF60COLNAME=2 ROTATE="0" MOREROWS="0"-160COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to delete a directory that contains files or other directories.COLNAME=1 ROTATE="0" MOREROWS="0"FFF61COLNAME=2 ROTATE="0" MOREROWS="0"-159COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to delete a directory that is being used by another workstation.COLNAME=1 ROTATE="0" MOREROWS="0"FFF62COLNAME=2 ROTATE="0" MOREROWS="0"-158COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to create a file using invalid characters within the name of the file.COLNAME=1 ROTATE="0" MOREROWS="0"FFF63COLNAME=2 ROTATE="0" MOREROWS="0"-157COLNAME=3 ROTATE="0" MOREROWS="0"Description: No more directory handles are available; the directory handle table is full.Explanation: Each user may have up to 255 directory handles.COLNAME=1 ROTATE="0" MOREROWS="0"FFF64COLNAME=2 ROTATE="0" MOREROWS="0"-156COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: One of the following reasons apply:MARK=BULLETAn invalid extension was specified.The user tried to access an invalid path.COLNAME=1 ROTATE="0" MOREROWS="0"FFF65COLNAME=2 ROTATE="0" MOREROWS="0"-155COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to use an invalid directory handle. This occurs if the network has been brought down and brought back up without rebooting the workstation.COLNAME=1 ROTATE="0" MOREROWS="0"FFF66COLNAME=2 ROTATE="0" MOREROWS="0"-154COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to rename across volumes (rename a file and move the renamed file from its current volume into another volume). Although the RENAME command may move the file between directories on the same volume, using RENAME to move a file between volumes is not allowed.COLNAME=1 ROTATE="0" MOREROWS="0"FFF67COLNAME=2 ROTATE="0" MOREROWS="0"-153COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to write to a volume without available directory space.COLNAME=1 ROTATE="0" MOREROWS="0"FFF68COLNAME=2 ROTATE="0" MOREROWS="0"-152COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The network operating system has tried to access a volume but cannot find the volume in the system definition files.COLNAME=1 ROTATE="0" MOREROWS="0"FFF69COLNAME=2 ROTATE="0" MOREROWS="0"-151COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The network operating system has determined that the network disk does not have enough space left for spool files.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFF96COLNAME=2 ROTATE="0" MOREROWS="0"-150COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: One of the following reasons apply:MARK=BULLETThe user tried to write to a file server that does not have enough free dynamic memory to process this request.The specified target directory is not a subdirectory.COLNAME=1 ROTATE="0" MOREROWS="0"FFF6BCOLNAME=2 ROTATE="0" MOREROWS="0"-149COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to read or write to a detached file.COLNAME=1 ROTATE="0" MOREROWS="0"FFF6CCOLNAME=2 ROTATE="0" MOREROWS="0"-148COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to write to a file without Write privileges to that file, or the specified file has Read Only status.COLNAME=1 ROTATE="0" MOREROWS="0"FFF6DCOLNAME=2 ROTATE="0" MOREROWS="0"-147COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to read a file without Read privileges to that file.COLNAME=1 ROTATE="0" MOREROWS="0"FFF6ECOLNAME=2 ROTATE="0" MOREROWS="0"-146COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to rename files when all of the files matching the new filename specification already exist.COLNAME=1 ROTATE="0" MOREROWS="0"FFF6FCOLNAME=2 ROTATE="0" MOREROWS="0"-145COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to rename files when one or more files matching the new filename specification already exist.COLNAME=1 ROTATE="0" MOREROWS="0"FFF70COLNAME=2 ROTATE="0" MOREROWS="0"-144COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to delete, rename, or set file attributes using a filename when all of the files specified have Read Only status.COLNAME=1 ROTATE="0" MOREROWS="0"FFF71COLNAME=2 ROTATE="0" MOREROWS="0"-143COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to delete, rename, or set file attributes using a filename when some of the files specified have Read Only status.COLNAME=1 ROTATE="0" MOREROWS="0"FFF72COLNAME=2 ROTATE="0" MOREROWS="0"-142COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to delete, rename, or set file attributes using a filename when the file or files specified by the filename are in use by another workstation.COLNAME=1 ROTATE="0" MOREROWS="0"FFF73COLNAME=2 ROTATE="0" MOREROWS="0"-141COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to delete, rename, or set file attributes using an ambiguous filename while some of the files specified by the filename are in use by another workstation.COLNAME=1 ROTATE="0" MOREROWS="0"FFF74COLNAME=2 ROTATE="0" MOREROWS="0"-140COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to modify a file without attribute modification privileges in that file's directory.COLNAME=1 ROTATE="0" MOREROWS="0"FFF75COLNAME=2 ROTATE="0" MOREROWS="0"-139COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to rename a file without renaming privileges in that file's directory.COLNAME=1 ROTATE="0" MOREROWS="0"FFF76COLNAME=2 ROTATE="0" MOREROWS="0"-138COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to delete a file without file deletion privileges in that file's directory.COLNAME=1 ROTATE="0" MOREROWS="0"FFF77COLNAME=2 ROTATE="0" MOREROWS="0"-137COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to search a directory without Search rights in that directory.COLNAME=1 ROTATE="0" MOREROWS="0"FFF78COLNAME=2 ROTATE="0" MOREROWS="0"-136COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to close or perform I/O on a file with an invalid file handle (that is, the user tried to read from a file that has been closed).COLNAME=1 ROTATE="0" MOREROWS="0"FFF79COLNAME=2 ROTATE="0" MOREROWS="0"-135COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to create a file using an ambiguous filename.COLNAME=1 ROTATE="0" MOREROWS="0"FFF7ACOLNAME=2 ROTATE="0" MOREROWS="0"-134COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to create a file with the same name as an already existing file with Read Only status.COLNAME=1 ROTATE="0" MOREROWS="0"FFF7BCOLNAME=2 ROTATE="0" MOREROWS="0"-133COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to create an already existing file without the Create/Delete rights.COLNAME=1 ROTATE="0" MOREROWS="0"FFF7CCOLNAME=2 ROTATE="0" MOREROWS="0"-132COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to create a file without the Create right.COLNAME=1 ROTATE="0" MOREROWS="0"FFF7DCOLNAME=2 ROTATE="0" MOREROWS="0"-131COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: A hard disk input/output error occurred on a NetWare volume; a bad sector has been encountered and could be fatal.COLNAME=1 ROTATE="0" MOREROWS="0"FFF7ECOLNAME=2 ROTATE="0" MOREROWS="0"-130COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user tried to open a file without the Open right.COLNAME=1 ROTATE="0" MOREROWS="0"FFF7FCOLNAME=2 ROTATE="0" MOREROWS="0"-129COLNAME=3 ROTATE="0" MOREROWS="0"Description: No more file handles are available; the network file handle table is full.COLNAME=1 ROTATE="0" MOREROWS="0"FFF80COLNAME=2 ROTATE="0" MOREROWS="0"-128COLNAME=3 ROTATE="0" MOREROWS="0"Description: A lock attempt failed.COLNAME=1 ROTATE="0" MOREROWS="0"FFF81COLNAME=2 ROTATE="0" MOREROWS="0"-127COLNAME=3 ROTATE="0" MOREROWS="0"Description: A timeout occurred before a file was locked.COLNAME=1 ROTATE="0" MOREROWS="0"FFF82COLNAME=2 ROTATE="0" MOREROWS="0"-126COLNAME=3 ROTATE="0" MOREROWS="0"Description: The NCP subfunction size does not match the actual size of the data sent.COLNAME=1 ROTATE="0" MOREROWS="0"FFF83COLNAME=2 ROTATE="0" MOREROWS="0"-125COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The user is trying to log out of a connection he or she is not logged in to.COLNAME=1 ROTATE="0" MOREROWS="0"FFF84COLNAME=2 ROTATE="0" MOREROWS="0"-124COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The connection for a call has not been authenticated.COLNAME=1 ROTATE="0" MOREROWS="0"FFF85COLNAME=2 ROTATE="0" MOREROWS="0"-123COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: The connection is already logged in to the Directory.COLNAME=1 ROTATE="0" MOREROWS="0"FFF86COLNAME=2 ROTATE="0" MOREROWS="0"-122COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: An attempt was made to convert a connection to temporary that was already temporary.COLNAME=1 ROTATE="0" MOREROWS="0"FFF87COLNAME=2 ROTATE="0" MOREROWS="0"-121COLNAME=3 ROTATE="0" MOREROWS="0"Explanation: A request for items failed because the items could not be found, for example, during a bindery request.COLNAME=1 ROTATE="0" MOREROWS="0"FFF88COLNAME=2 ROTATE="0" MOREROWS="0"-120COLNAME=3 ROTATE="0" MOREROWS="0"Description: The volume flag has not been set.COLNAME=1 ROTATE="0" MOREROWS="0"FFF89COLNAME=2 ROTATE="0" MOREROWS="0"-119COLNAME=3 ROTATE="0" MOREROWS="0"Description: The data to be passed back is too large for the buffer that was declared.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFFFBCOLNAME=2 ROTATE="0" MOREROWS="0"-5COLNAME=3 ROTATE="0" MOREROWS="0"Description: An invalid request was made.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFCOLNAME=2 ROTATE="0" MOREROWS="0"-001COLNAME=3 ROTATE="0" MOREROWS="0"Description: The machine does not have sufficient disk space.COLNAME=1 ROTATE="0" MOREROWS="0"FFFFFFFFCOLNAME=2 ROTATE="0" MOREROWS="0"-1COLNAME=3 ROTATE="0" MOREROWS="0"Description: An unknown error has occurred.LABEL="B"PAGENUM=1385 ID="BP1328"ID="FM86922"MHS Error Reasons, Explanations, and ActionsThe following table is an alphabetical listing of each MHS_error_reason that may originate from the MHS, MHSCON, MSHDEINS, and MHSINS modules.The "Explanation" and "Action" columns occasionally provide more than one corrective action you can try. We suggest you base your actions on the task you were performing when the error occurred.COLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="7*"COLNAME=2 COLWIDTH="14*"COLNAME=3 COLWIDTH="14*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"ID="FM32805"MHS Error ReasonCOLNAME=2 ROTATE="0" MOREROWS="0"Explanation COLNAME=3 ROTATE="0" MOREROWS="0"ActionVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Argument list too bigCOLNAME=2 ROTATE="0" MOREROWS="0"Memory is corrupted, or a software malfunction occurred. COLNAME=3 ROTATE="0" MOREROWS="0"Bring down the server and bring it back up.COLNAME=1 ROTATE="0" MOREROWS="0"Bad addressCOLNAME=2 ROTATE="0" MOREROWS="0"Memory is corrupted, or a software malfunction occurred. COLNAME=3 ROTATE="0" MOREROWS="0"Bring down the server and bring it back up.COLNAME=1 ROTATE="0" MOREROWS="0"Bad file numberCOLNAME=2 ROTATE="0" MOREROWS="0"The disk is corrupted, or a software malfunction occurred.COLNAME=3 ROTATE="0" MOREROWS="0"Use VREPAIR to check the integrity of, and to repair, your NetWare file system.COLNAME=1 ROTATE="0" MOREROWS="0"Bad handle; file, screen, semaphore, etc.COLNAME=2 ROTATE="0" MOREROWS="0"Memory is corrupted, or a software malfunction occurred. COLNAME=3 ROTATE="0" MOREROWS="0"Bring down the server and bring it back up.COLNAME=1 ROTATE="0" MOREROWS="0"Cannot create message spool areaCOLNAME=2 ROTATE="0" MOREROWS="0"A message spool area creation failed. COLNAME=3 ROTATE="0" MOREROWS="0"Make sure the rights to the \MHS directory are appropriate.If the disk is full, free up disk space. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Disk Space Problems" in Supervising the Network.COLNAME=1 ROTATE="0" MOREROWS="0"Cannot read from message spool areaCOLNAME=2 ROTATE="0" MOREROWS="0"An attempt to read from a message spool area failed. COLNAME=3 ROTATE="0" MOREROWS="0"Make sure the access spool area file exists and that the rights to the \MHS directory are appropriate.Check for a hard disk error.COLNAME=1 ROTATE="0" MOREROWS="0"Cannot write to message spool areaCOLNAME=2 ROTATE="0" MOREROWS="0"A message spool area creation failed. COLNAME=3 ROTATE="0" MOREROWS="0"If the disk is full, free up disk space. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Disk Space Problems" in Supervising the Network.Make sure the \MHS\STORE\QUEUES directory exists.Make sure the access rights to the \MHS directory are appropriate.COLNAME=1 ROTATE="0" MOREROWS="0"Cross device linkCOLNAME=2 ROTATE="0" MOREROWS="0"An internal NetWare file system error occurred. COLNAME=3 ROTATE="0" MOREROWS="0"Use VREPAIR to check the integrity of, and to repair, your NetWare file system.COLNAME=1 ROTATE="0" MOREROWS="0"Device is fullCOLNAME=2 ROTATE="0" MOREROWS="0"The volume being accessed is out of disk space, or a "logjam" of messages is waiting to be delivered to servers that are inaccessible.COLNAME=3 ROTATE="0" MOREROWS="0"Free up disk space. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Disk Space Problems" in Supervising the Network.COLNAME=1 ROTATE="0" MOREROWS="0"Device is full No space is left on deviceCOLNAME=2 ROTATE="0" MOREROWS="0"The volume being accessed is out of disk space, or a "logjam" of messages is waiting to be delivered to servers that are inaccessible.COLNAME=3 ROTATE="0" MOREROWS="0"Free up disk space. See "BOOK="superenu" COLLECTION="nw41"Resolving Server Disk Space Problems" in Supervising the Network.COLNAME=1 ROTATE="0" MOREROWS="0"Distribution list was ALREADY expanded.COLNAME=2 ROTATE="0" MOREROWS="0"The MHS router found a distribution list as a recipient which had already been expanded once.This typically happens if you have two distribution lists that include each other as distribution lists, or if a message has two distribution lists as recipients and one of the distribution lists contains the other as a member.This is not necessarily an error, if this is what was intended. The MHS router subsystem will only expand a distribution list once. COLNAME=3 ROTATE="0" MOREROWS="0"Review your distribution list for the cases listed in the explanation.COLNAME=1 ROTATE="0" MOREROWS="0"Distribution list has no membersCOLNAME=2 ROTATE="0" MOREROWS="0"The MHS router found an empty distribution list.COLNAME=3 ROTATE="0" MOREROWS="0"Examine the distribution list in the NetWare Directory database to see if it has members. If not, add some members or delete the empty distribution list.Review the access rights to the Members attribute of the distribution list.Use DSREPAIR to check the integrity of, and to repair, your NetWare Directory database.COLNAME=1 ROTATE="0" MOREROWS="0"Expiration date expiredCOLNAME=2 ROTATE="0" MOREROWS="0"The expiration date specified by the originator was reached.COLNAME=3 ROTATE="0" MOREROWS="0"Possibly no action needs to be taken; the system will inform the originator if the appropriate report was requested.Make sure the mailbox ID and mailbox location of each recipient is correct.Make sure that the messaging server with the mailbox location is up and running.COLNAME=1 ROTATE="0" MOREROWS="0"Execution format errorCOLNAME=2 ROTATE="0" MOREROWS="0"Memory is corrupted, or a software malfunction occurred. COLNAME=3 ROTATE="0" MOREROWS="0"Bring down the server and bring it back up.COLNAME=1 ROTATE="0" MOREROWS="0"File already existsCOLNAME=2 ROTATE="0" MOREROWS="0"An incorrect assumption was made that a given file did not exist. This error should normally be for informational purposes; the system should be able to recover and proceed.COLNAME=3 ROTATE="0" MOREROWS="0"If this message appears to be related to some abnormal behavior, try to correct the problem.  If the problem persists, contact your Novell Authorized Reseller.COLNAME=1 ROTATE="0" MOREROWS="0"File table overflowCOLNAME=2 ROTATE="0" MOREROWS="0"An internal NetWare file system error occurred.COLNAME=3 ROTATE="0" MOREROWS="0"Use VREPAIR to check the integrity of, and to repair, your NetWare file system.Delete and purge any unnecessary files.COLNAME=1 ROTATE="0" MOREROWS="0"Internal errorCOLNAME=2 ROTATE="0" MOREROWS="0"An unusual NDS error occurred that is not mapped. An error number will display.COLNAME=3 ROTATE="0" MOREROWS="0"Review your NetWare Directory Services setup. Make sure all objects that you think exist really do. Review your partition replica setup. Review NetWare Directory Services access rights.Use DSREPAIR to check the integrity of, and to repair, the NetWare Directory database.Record the error number that is displayed. If the problem persist after all the other actions have been done,  to report the error number.COLNAME=1 ROTATE="0" MOREROWS="0"Invalid argumentCOLNAME=2 ROTATE="0" MOREROWS="0"Memory is corrupted, or a software malfunction occurred. COLNAME=3 ROTATE="0" MOREROWS="0"Bring down the server and bring it back up.COLNAME=1 ROTATE="0" MOREROWS="0"Invalid message spool contextCOLNAME=2 ROTATE="0" MOREROWS="0"Data passed to the message spooling area was not understood. Memory is corrupted, or a software malfunction occurred. COLNAME=3 ROTATE="0" MOREROWS="0"Unload and reload MHS, or bring down the server and bring it back up.If the problem persist after doing on of the previously specified tasks, the problem is most likely caused from malfunctioning software. Contact your Novell Authorized Reseller. COLNAME=1 ROTATE="0" MOREROWS="0"Illegal search operationCOLNAME=2 ROTATE="0" MOREROWS="0"A software malfunction occurred, most likely as part of the MHS user extract procedure. COLNAME=3 ROTATE="0" MOREROWS="0"Unload and reload MHS.COLNAME=1 ROTATE="0" MOREROWS="0"Message has timed outCOLNAME=2 ROTATE="0" MOREROWS="0"A message was not delivered within the configured time limit, so the message was rejected. COLNAME=3 ROTATE="0" MOREROWS="0"Verify that the mailbox ID and mailbox location of each recipient is correct.Make sure that the messaging server with the mailbox location is up and running. The system informs the originator if nondelivery notification was requested.COLNAME=1 ROTATE="0" MOREROWS="0"Message sender is invalidCOLNAME=2 ROTATE="0" MOREROWS="0"Sender validation is enabled, and someone other than owner of the file tried to send a message using a sender name.COLNAME=3 ROTATE="0" MOREROWS="0"Correct the "From" field so that it contains the appropriate sender's name and resubmit the message.COLNAME=1 ROTATE="0" MOREROWS="0"Message spool area already existsCOLNAME=2 ROTATE="0" MOREROWS="0"MHS tried to create a message spool area that already exists. Memory is corrupted, or a software malfunction occurred. COLNAME=3 ROTATE="0" MOREROWS="0"None. This message is for information only. If the problem persists, contact your Novell Authorized Reseller. COLNAME=1 ROTATE="0" MOREROWS="0"Message spool area contains no messagesCOLNAME=2 ROTATE="0" MOREROWS="0"MHS tried to retrieve a message from an empty spooling area.COLNAME=3 ROTATE="0" MOREROWS="0"None. This message is for information only. If the problem persists, unload and reload MHS.COLNAME=1 ROTATE="0" MOREROWS="0"Message spool area is lockedCOLNAME=2 ROTATE="0" MOREROWS="0"The MHS delivery module tried to claim a message spool area that was already claimed. COLNAME=3 ROTATE="0" MOREROWS="0"If the MHS delivery module is unable to deliver messages to the specified messaging server over a period of time, unload and reload MHS to clear the lock.COLNAME=1 ROTATE="0" MOREROWS="0"Message spool area message name foundCOLNAME=2 ROTATE="0" MOREROWS="0"The end of a message search has completed usually meaning that the message was already transferred or delivered.COLNAME=3 ROTATE="0" MOREROWS="0"None. This message is for information only. If the problem persists, contact your Novell Authorized Reseller.  COLNAME=1 ROTATE="0" MOREROWS="0"Message spool area not foundCOLNAME=2 ROTATE="0" MOREROWS="0"MHS tried to access a message spool area that no longer exists. COLNAME=3 ROTATE="0" MOREROWS="0"Check the message spool area \MHS\STORE\QUEUES to make sure that the spool area still exists. (Someone may have inadvertently deleted it.) Check the access rights to the \MHS directory.If the problem persists, unload and reload MHS.COLNAME=1 ROTATE="0" MOREROWS="0"Message transferred too many timesCOLNAME=2 ROTATE="0" MOREROWS="0"A message was transferred between too many messaging servers and was eventually discarded. A nondelivery notification was sent to the sender. Possibly MHS and a remote messaging service both indicate the other has the mailbox location.COLNAME=3 ROTATE="0" MOREROWS="0"Using , check the recipient's address of the message and the mailbox locations.COLNAME=1 ROTATE="0" MOREROWS="0"Message was badly formedCOLNAME=2 ROTATE="0" MOREROWS="0"An SMF-71 message did not follow SMF- 71 rules of construction. The system will send a bad message notification to the sender of the message, or to the network supervisor, if the sender is unavailable.COLNAME=3 ROTATE="0" MOREROWS="0"Check the recipient address in the message. Check the recipient's mailbox location in the NetWare Directory database, and on any other database where the recipients may have mailboxes. COLNAME=1 ROTATE="0" MOREROWS="0"Misc. temp I/O problemCOLNAME=2 ROTATE="0" MOREROWS="0"An error occurred while attempting to perform I/O functions, either across the network or locally. COLNAME=3 ROTATE="0" MOREROWS="0"None. This message is for information only.  Such errors are generally recovered from automatically.COLNAME=1 ROTATE="0" MOREROWS="0"Missing object attributeCOLNAME=2 ROTATE="0" MOREROWS="0"A NDS object attribute was not found in the database. COLNAME=3 ROTATE="0" MOREROWS="0"Make sure that the object attribute actually exists. Review NetWare Directory Services access rights.Use DSREPAIR to check the integrity of, and to repair, your NetWare Directory database.COLNAME=1 ROTATE="0" MOREROWS="0"No dataCOLNAME=2 ROTATE="0" MOREROWS="0"Memory is corrupted, or a software malfunction occurred.COLNAME=3 ROTATE="0" MOREROWS="0"Bring down the server and bring it back up.COLNAME=1 ROTATE="0" MOREROWS="0"No more messages in message spool areaCOLNAME=2 ROTATE="0" MOREROWS="0"MHS tried to retrieve a message from a spooling area that no longer exists.COLNAME=3 ROTATE="0" MOREROWS="0"Receiving this error occasionally is okay. If MHS cannot deliver messages to the specified messaging server over a period of time, repair the message database by unloading and reloading MHS using the -r option.COLNAME=1 ROTATE="0" MOREROWS="0"No space left on deviceCOLNAME=2 ROTATE="0" MOREROWS="0"No disk space is left on the volume that MHS is using to store messages.COLNAME=3 ROTATE="0" MOREROWS="0"Use VREPAIR to check the integrity of, and to repair, your NetWare file system.Delete and purge any unnecessary files.COLNAME=1 ROTATE="0" MOREROWS="0"No queue/file serverCOLNAME=2 ROTATE="0" MOREROWS="0"An internal NetWare file system error occurred.COLNAME=3 ROTATE="0" MOREROWS="0"Bring down the server and bring it back up. Use VREPAIR to check the integrity of, and to repair, your NetWare file system.COLNAME=1 ROTATE="0" MOREROWS="0"No such device or addressCOLNAME=2 ROTATE="0" MOREROWS="0"Memory is corrupted, or a software malfunction occurred.COLNAME=3 ROTATE="0" MOREROWS="0"Bring down the server and bring it back up.COLNAME=1 ROTATE="0" MOREROWS="0"No such file or directoryCOLNAME=2 ROTATE="0" MOREROWS="0"The file or directory does not exist. Possibly the directory was deleted. In some cases, this message would indicate normal behavior, such as when a message was accepted by the system before a user and associated user's mailbox was deleted.COLNAME=3 ROTATE="0" MOREROWS="0"If the directory is a mailbox that was moved, use MHSCON to verify the message. Review the mailbox location using NetWare Administrator.COLNAME=1 ROTATE="0" MOREROWS="0"Not a data messageCOLNAME=2 ROTATE="0" MOREROWS="0"Memory is corrupted, or a software malfunction occurred.COLNAME=3 ROTATE="0" MOREROWS="0"Bring down the server and bring it back up.COLNAME=1 ROTATE="0" MOREROWS="0"Not enough memoryCOLNAME=2 ROTATE="0" MOREROWS="0"Not enough memory exists to perform the operation being attempted. COLNAME=3 ROTATE="0" MOREROWS="0"Use MONITOR.NLM to find out where the memory is being used.See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.COLNAME=1 ROTATE="0" MOREROWS="0"Object not foundCOLNAME=2 ROTATE="0" MOREROWS="0"A NDS object was not found in the NetWare Directory database. COLNAME=3 ROTATE="0" MOREROWS="0"Make sure the object exists in the NetWare Directory database.Review your partition replica setup.Review NetWare Directory Services access rights.Use DSREPAIR to check the integrity of, and to repair, your NetWare Directory Services database.COLNAME=1 ROTATE="0" MOREROWS="0"Operation not supportedCOLNAME=2 ROTATE="0" MOREROWS="0"Memory is corrupted, or a software malfunction occurred. COLNAME=3 ROTATE="0" MOREROWS="0"Bring down the server and bring it back up.COLNAME=1 ROTATE="0" MOREROWS="0"Permission deniedCOLNAME=2 ROTATE="0" MOREROWS="0"You do not have rights to access a file or object, or the file is already open in an exclusive use mode, or security settings are configured improperly.COLNAME=3 ROTATE="0" MOREROWS="0"Review trustee assignment rights for the associated subdirectories to make sure they are all in order.Use MONITOR.NLM to determine if the file is already open.Review NetWare Directory Services Access Control List settings and security equivalence properties for messaging objects to make sure they are all in order.COLNAME=1 ROTATE="0" MOREROWS="0"Physical I/O errorCOLNAME=2 ROTATE="0" MOREROWS="0"The server has a hardware problem.COLNAME=3 ROTATE="0" MOREROWS="0"Bring down the server. Execute diagnostic software to attempt to determine the hardware problem. Correct the problem and bring the server back up.COLNAME=1 ROTATE="0" MOREROWS="0"Recipient address form is not recognizedCOLNAME=2 ROTATE="0" MOREROWS="0"A message included a recipient's name in an address form that is not is recognized by MHS. Possibly the address is not in SMF-71 compatible form, or the address may have been entered incorrectly.COLNAME=3 ROTATE="0" MOREROWS="0"Change the recipient's address to an SMF-71 compatible address and resubmit the message.Make sure the address is entered correctly.COLNAME=1 ROTATE="0" MOREROWS="0"Recipient has no mailbox IDCOLNAME=2 ROTATE="0" MOREROWS="0"The MHS router found a recipient with no mailbox ID defined. COLNAME=3 ROTATE="0" MOREROWS="0"Make sure the recipient has a mailbox ID in the NetWare Directory Services database.Review the access rights to the recipient's mailbox ID attribute.Use DSREPAIR to check the integrity of, and to repair, the NetWare Directory Services database.COLNAME=1 ROTATE="0" MOREROWS="0"Recipient has no mailbox locationCOLNAME=2 ROTATE="0" MOREROWS="0"The MHS router found a recipient with no mailbox location defined.COLNAME=3 ROTATE="0" MOREROWS="0"Make sure the recipient has a mailbox location in the NetWare Directory Services database.Review the access rights to the recipient's mailbox location attribute.Use DSREPAIR to check the integrity of, and to repair, your NetWare Directory database.COLNAME=1 ROTATE="0" MOREROWS="0"Recipient's mailbox location is unknownCOLNAME=2 ROTATE="0" MOREROWS="0"The MHS router found a recipient whose mailbox location exists on a messaging server that does not belong to the local Message Routing Group. This may not be an error, if the users mailbox exists on a foreign messaging server. Possibly the message will be handed to a gateway for delivery.COLNAME=3 ROTATE="0" MOREROWS="0"Make sure the proper gateway is installed and configured.Examine the recipient in the NetWare Directory Services database to see if the mailbox location is configured improperly.Use DSREPAIR to check the integrity of, and to repair, your NetWare Directory Services database.COLNAME=1 ROTATE="0" MOREROWS="0"Rename attempted across deviceCOLNAME=2 ROTATE="0" MOREROWS="0"Memory is corrupted, or a software malfunction occurred. COLNAME=3 ROTATE="0" MOREROWS="0"Bring down the server and bring it back up.COLNAME=1 ROTATE="0" MOREROWS="0"Resource deadlockCOLNAME=2 ROTATE="0" MOREROWS="0"Memory is corrupted, or a software malfunction occurred. COLNAME=3 ROTATE="0" MOREROWS="0"Bring down the server and bring it back up.COLNAME=1 ROTATE="0" MOREROWS="0"Resource temporarily unavailableCOLNAME=2 ROTATE="0" MOREROWS="0"An attempt was made to access a file that was temporarily unavailable.COLNAME=3 ROTATE="0" MOREROWS="0"Use MONITOR.NLM to determine which resource is unavailable, and take the appropriate action.Clean up deadlocked resources by bringing down the server and bringing it back up.COLNAME=1 ROTATE="0" MOREROWS="0"Resource in useCOLNAME=2 ROTATE="0" MOREROWS="0"An attempt was made to access a file that is already in use or unavailable. COLNAME=3 ROTATE="0" MOREROWS="0"None. This message is for information only. The system should be able to recover and proceed.COLNAME=1 ROTATE="0" MOREROWS="0"Resources (may be permanently) unavailableCOLNAME=2 ROTATE="0" MOREROWS="0"An attempt was made to access a file that is unavailable.COLNAME=3 ROTATE="0" MOREROWS="0"Use MONITOR.NLM to determine which resource is unavailable. If you can determine which resource is unavailable take the appropriate action.Clean up deadlocked resources by bringing down the server and bringing it back up.COLNAME=1 ROTATE="0" MOREROWS="0"Screen I/O attempted when no screensCOLNAME=2 ROTATE="0" MOREROWS="0"Memory is corrupted, or a software malfunction occurred. COLNAME=3 ROTATE="0" MOREROWS="0"Bring down the server and bring it back up.COLNAME=1 ROTATE="0" MOREROWS="0"Server error; out of memory, I/O, etc.COLNAME=2 ROTATE="0" MOREROWS="0"An internal NetWare file system error occurred. COLNAME=3 ROTATE="0" MOREROWS="0"Bring down the server and bring it back up.Use MONITOR.NLM to find out where the memory is being used.See "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.COLNAME=1 ROTATE="0" MOREROWS="0"Share mode is unknownCOLNAME=2 ROTATE="0" MOREROWS="0"Corruption or a software malfunction probably occurred. COLNAME=3 ROTATE="0" MOREROWS="0"Bring down the server and bring it back up.COLNAME=1 ROTATE="0" MOREROWS="0"Streams not loadedCOLNAME=2 ROTATE="0" MOREROWS="0"STREAMS.NLM is not loaded.COLNAME=3 ROTATE="0" MOREROWS="0"Load STREAMS.NLM.COLNAME=1 ROTATE="0" MOREROWS="0"Temp files not available or file table overflow or too many open filesCOLNAME=2 ROTATE="0" MOREROWS="0"The system cannot create new files because too many files already exist.COLNAME=3 ROTATE="0" MOREROWS="0"See "BOOK="superenu" COLLECTION="nw41"Resolving Server Disk Space Problems" in Supervising the Network.Use MONITOR.NLM to find how many files are open and who has them. Try to get users to close the open files.You may need to add more memory to your server; see "BOOK="superenu" COLLECTION="nw41"Resolving Server Memory Problems" in Supervising the Network.COLNAME=1 ROTATE="0" MOREROWS="0"Too many filesCOLNAME=2 ROTATE="0" MOREROWS="0"Too many files already exist on the NetWare volume, and new files cannot be created.COLNAME=3 ROTATE="0" MOREROWS="0"Use VREPAIR to check the integrity of, and to repair, your NetWare file system.Delete and purge any unnecessary files.COLNAME=1 ROTATE="0" MOREROWS="0"Transaction restartedCOLNAME=2 ROTATE="0" MOREROWS="0"Memory is corrupted, or a software malfunction occurred. COLNAME=3 ROTATE="0" MOREROWS="0"Bring down the server and bring it back up.COLNAME=1 ROTATE="0" MOREROWS="0"Unable to create a unique message spool area nameCOLNAME=2 ROTATE="0" MOREROWS="0"Spool area names for remote servers are generated by using the first seven characters of the common name. If more than one server has the same seven characters in their names, then the message spool creation process increments a number as part of the name and tries again. After approximately 3,000 attempts, it gives up. COLNAME=3 ROTATE="0" MOREROWS="0"Make sure the first seven characters in the name of your message servers are unique.COLNAME=1 ROTATE="0" MOREROWS="0"Unload, disable, no flowCOLNAME=2 ROTATE="0" MOREROWS="0"Message processing in the system is halted temporarily. This could be because the system is unloading, the network supervisor has disabled parts of the system, or memory or volume space is near capacity. COLNAME=3 ROTATE="0" MOREROWS="0"If the message appears because the system is unloading, no action needs to be taken.If parts of the system have been disabled, enable them before resuming normal services.If the system is not being unloaded or if no parts of the system are disabled, free up volume space or make more memory available.COLNAME=1 ROTATE="0" MOREROWS="0"Value was truncatedCOLNAME=2 ROTATE="0" MOREROWS="0"A message header value probably exceeded its maximum limit, so the value was truncated.This is usually caused by the application that generated the message. MHS will still attempt to deliver the message.COLNAME=3 ROTATE="0" MOREROWS="0"If the message is a nondelivery message, review the referenced message. Correct the header field to make it a legal SMS message, then resend the message.COLNAME=1 ROTATE="0" MOREROWS="0"Wrong kind of operation for this objectCOLNAME=2 ROTATE="0" MOREROWS="0"Memory is corrupted, or a software malfunction occurred. COLNAME=3 ROTATE="0" MOREROWS="0"Bring down the server and bring it back up.LABEL="C"PAGENUM=1397 ID="BP1A"ID="FM74346"Workstation Error MessagesThe following error messages are common to most workstation utilities:ID="FM81494"900: The default server cannot be found.Explanation: This utility was unable to get the connection ID for the default server. The shell may have timed out.Action: Try the operation again. Make sure that the network hasn't gone down, the connection hasn't been lost, or other errors have not been ignored. See "BOOK="superenu" COLLECTION="nw41"Troubleshooting Hardware and Network Problems" in Supervising the Network. If the problem persists, contact your Novell Authorized Reseller.ID="FM84261"901: You are not attached to the specified server.Explanation: You tried to execute a command on a server other than the default server, but The user is not attached to that server. The user must be attached to a server before you can use it.Action: Do one or both of the following:MARK=BULLETAt the prompt, type "WHOAMI /B" to list the servers that the user account is logged in to or attached to. Then specify a path to the utility on the appropriate server.Use the LOGIN utility to attach to the desired server; then map a drive to the server and use the new drive mapping in the command. Use the /NS option to attach; otherwise, you will lose the default option.ID="FM18860"903: The command line syntax is invalid.Explanation: The format of the command was incorrect.Action: Make sure the syntax, path, and optional parameters are correct. Use the online help screens to view the correct command line syntax.ID="FM42246"904: The server name is invalid.Explanation: An invalid character was used in the server name, or the server does not exist.Action: Make sure that there are no invalid characters used in the server name, or use NLIST to find the server desired. For example:PAGENUM=1398 ID="BP2A"MOREINFO="NONE"NLIST MY_SERVERThen try the command again.ID="FM55337"905: This utility was unable to initialize the country information.Explanation: This utility was unable to get the country information from the workstation. This error is returned when the workstation's operating system configuration is not correct. Action: Make sure that the workstation's operating system configuration is correct. ID="FM78951"906: The Unicode files cannot be found.Explanation: The Unicode files for the current language code page and country cannot be found.Action: Verify that the Unicode files for the current code page and country are located in the SYS:PUBLIC\NLS directory.ID="FM48610"907: This utility cannot open the translation table SCHEMA.XLT.Explanation: In the DOS, Windows, and OS/2 environments, the program searches the following areas for the translation files. MARK=BULLETThe current directory.The load directory (the directory containing the current utility's EXE file). This is usually the PUBLIC directory.The NLS directory that is located within the load directory (the directory containing the current utility's EXE file). If the Unicode files are not found in the NLS directory within the load file, the program searches the NLS directory that is a sibling of the load directory (that is, at the same level as the load directory). Note: The NWLanguage environment variable does not apply here.The PATH and DPATH (for OS/2 only) environment variables. These environment variables may be found in either the user's login script or AUTOEXEC.BAT file.Action: Make sure these files are loaded into the PUBLIC directory and that the workstation has a search drive mapped to the PUBLIC directory; then try the operation again. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=1399 ID="BP3A"ID="FM51165"908: The specified path is invalid.Explanation: The operating system could not find the directory path. The specified directory path does not exist or you mistyped the directory path.Action: Use the FILER utility to examine the directory. Type the directory path correctly. You can also use the MAP command or the NETUSER utility to map a network drive to a directory; then specify the drive, rather than the directory path, in the command. ID="FM28663"909: You are not mapped to the specified drive.Explanation: You specified either a local hard disk or a network drive that has not been defined.Action: Use the MAP command or the NETUSER utility to view the workstation's network drive mappings. If necessary, map a drive to the directory; then retry the command.ID="FM47164"910: This utility was unable to parse the specified path.Explanation: The program could not find the directory path. Either the specified a directory path does not exist, or you mistyped the directory path.Action: Use the FILER utility to examine the directory. Type the directory path correctly. The correct syntax is as follows:FORMAT="LINESPECIFIC"MOREINFO="NONE" server\volume:directory\subdirectory\files  or FORMAT="LINESPECIFIC"MOREINFO="NONE" drive_letter:directory\subdirectory\files You can also use the MAP command or the NETUSER utility to map a network drive to a directory; then you can specify the drive, rather than the directory path, in the command. ID="FM53981"911: Directory Services is not active at this time.Explanation: This error is probably caused by one of the following:MARK=BULLETYou attempted a NetWare Directory Services request on a non-NetWare Directory Services server.You do not have a NetWare Directory Services connection.Action: Make sure that NetWare Directory Services is active on the server. Also make sure that the workstation shell has NetWare Directory Services support.PAGENUM=1400 ID="BP4A"ID="FM74299"912: The specified file cannot be found.Explanation: You specified an invalid filename, or the file is not part of the path.Action: Make sure that the file is part of the path and that you typed the filename correctly.ID="FM19478"913: The specified directory cannot be found.Explanation: You specified an invalid directory name, or the directory is not part of the path.Action: Make sure that the directory is part of the path and that you typed the directory name correctly.ID="FM82066"914: The specified file or directory cannot be found.Explanation: You specified an invalid filename or directory name, or the file or directory is not part of the path.Action: Make sure that the file or directory is part of the path and that you typed the filename or directory name correctly.ID="FM46881"915: The specified volume does not exist.Explanation: The volume in the specified path is not valid.Action: Use FILER to make sure this is a valid volume. Make sure the volume is mounted.ID="FM77950"916: This utility only supports 25 levels of directories.Explanation: This utility supports only 25 levels of directories.Action: Limit the network directories to 25 levels.ID="FM32126"917: This utility was unable to set the context.Explanation: You typed in the NetWare Directory Services object name incorrectly, or the workstation does not have enough memory to set up the context.Action: Make sure that you have typed the object name correctly. (You can use NETADMIN to verify the correct name.) Increase the available memory. See "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network.ID="FM25772"918: This utility was unable to get connection information.  Error code: <code>.Explanation: For some unexpected reason, this utility was unable to obtain information about a particular server. No other information is available.Action: Issue the command again from a different drive. If you want specific information on the error code returned, contact your Novell Authorized Reseller.PAGENUM=1401 ID="BP5A"ID="FM68419"919: This utility could not create a connection list.  Error <code>.Explanation: The utility failed in its attempt to create a list of all the connections to which the workstation is currently attached. The error code identifies a specific reason for the failure. Action: To get more information on the error code see, IDREF="FM61529""Error Codes" in Appendix A, then look up the error code. If you need more information, contact your Novell Authorized Reseller.ID="FM30331"920: This utility was unable to allocate <number> bytes of memory.Explanation: During its processing, the utility attempted to allocate more memory. No additional memory was available; therefore, the program was unable to allocate the specified number of bytes.Action: See "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network.ID="FM49837"921: Either the supervisor has locked the bindery or volume SYS: is not mounted.Explanation: The supervisor has locked the bindery or the volume SYS: is not mounted.Action: Make sure that volume SYS: is mounted. (Type "VOLUMES" at the server console to determine if the volume SYS: has been mounted.) If volume SYS: is mounted, make sure that the bindery is not closed.ID="FM41618"922: Intruder detection lockout has disabled this account.Explanation: You or someone else has tried to log in to the account without supplying the correct password within the allowed number of login attempts. The network supervisor can limit any account on the server to a specific number of login attempts to protect the account from intrusion by unauthorized persons. You cannot use the account until it is reopened by the network supervisor.Action: Contact the network supervisor to enable the account, or wait a specified period of time for the account to become enabled again (default: 15 minutes).ID="FM30182"923: An unexpected error has occurred. Error code: <code>.Explanation: An unexpected error occurred. No other information is available.Action: Try the operation again. If the error persists, contact your Novell Authorized Reseller to get specifics on the error returned.ID="FM81823"924: All drives are in use.Explanation: Every drive from Z: down to the local drives is in use; this utility cannot map any more drives.Action: Delete a drive using the MAP DEL command.PAGENUM=1402 ID="BP6A"ID="FM67645"925: The server specified is a Personal NetWare server. You cannot attach to a Personal NetWare server with this utility. Use the Personal NetWare utilities to access this connection.Explanation: This utility is not compatible with a Personal NetWare server.Action: Use the corresponding Personal NetWare utility.ID="FM15675"970: The attempt to open the Unicode table files failed.Explanation: The Unicode table files could not be opened for an unknown reason. The cause of the error is probably other than those listed in messages 971 through 975.Action:  Try the following:MARK=BULLETClose files you do not need to have open at the present time.Free up memory on the workstation. See "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network.Make sure the user has rights to access the directory where the Unicode table are kept.Make sure the directory where the Unicode files are kept is in the search path.Make sure the Unicode files are the most current version and are not corrupted.If after doing all the listed actions the problem still persists, contact your Novell Authorized Reseller.ID="FM55341"971: The workstation does not have enough memory to load the Unicode table files.Explanation: During its processing, this utility needed more memory and attempted to allocate more. No more available memory is available.Action: Increase the available memory. See "BOOK="superenu" COLLECTION="nw41"Resolving Workstation Memory Problems" in Supervising the Network.ID="FM90152"972: Access to the Unicode table files was denied.Explanation: You do not have sufficient rights to open and read the Unicode files.Action: Ask the network supervisor to grant you the necessary rights.PAGENUM=1403 ID="BP7A"ID="FM62778"973: The Unicode table files cannot be found in the NLS directory or in the search path. Code page: <number>  Country:  <number> Explanation: The file extension shown in parentheses represents the country code the workstation is using which is set in CONFIG.SYS. For example, *.001 is US English. The country code may be different from the one shown here. In the DOS, Windows, and OS/2 environments, the program searches the following areas for the Unicode files:MARK=BULLETThe current directory (for DOS and OS/2 environments) or the Windows directory.The load directory (the directory containing the current utility's .EXE file). Normally this will be the PUBLIC directory.The NLS directory that is located within the load directory (the directory containing the current utility's .EXE file). If the Unicode files are not found in the NLS directory within the load directory, the program searches the NLS directory that is a sibling of the load directory (that is, at the same level as the load directory). Note: The NWLanguage environment variable does not apply here.The PATH and DPATH (for OS/2 only) environment variables. These environment variables may be found either in the user's login script or in the AUTOEXEC.BAT file.The following four files must be in one of these locations of the user's search drive, or this error message is displayed:FORMAT="LINESPECIFIC"MOREINFO="NONE"code_page_UNI. country_id 
UNI_
code_page.
country_id 
UNI_MON.
country_id 
UNI_COL.
country_id Action: Make sure that these four files are loaded into the PUBLIC directory and that you have a search drive mapped to PUBLIC; then try the operation again. If you have a search drive mapped to PUBLIC and the files still cannot be found there or in any other locations listed, use the NPATH utility to determine the Unicode files required for the workstation and their location. If the problem persists, contact your Novell Authorized Reseller.ID="FM63405"974: The Unicode table files are corrupt.Explanation: The Unicode files are not the correct version or they are corrupt.Action: Ask the network supervisor to provide a current, uncorrupted copy of the files.PAGENUM=1404 ID="BP8A"ID="FM49793"975: The Unicode table files cannot be opened because there are already too many open files. Close some files or modify your CONFIG.SYS file.Explanation: This utility came up in NetWare Directory Services mode but failed to open the Unicode table files. Too many files are already open.Action: Close any files you do not need to have open or modify the CONFIG.SYS file to increment the number that "Files" is set to. For example, change "files=20" to "files=30."990: Unable to initialize; no upgrade performed.Explanation: The disk being upgraded is full or corrupted.Action: Correct the problem and run WSUPGRD again.ID="FM92553"991: An error occurred in <function_name>. Error code: <code>.Explanation: An unexpected error has occurred. Action: For more information on the error code, see IDREF="FM61529""Error Codes" in Appendix A. Retry the operation a couple of times. Also be sure no associated problems have occurred (such as the network going down, a connection being lost, or previous errors having occurred and been ignored). If the problem persists, contact your Novell Authorized Reseller.ID="FM91957"998: The message file found (<utility_name>.MSG) is an incorrect version. The correct version is <number>. See your network supervisor for assistance.Explanation: When the utility tried to initialize the utility_name.MSG file, it was unable to find a correct version of the file within the existing search drives. A file was found, but it was an incorrect version. The following areas were searched:MARK=BULLETThe current directory.The NWLANGUAGE environment variable directory. If the NWLANGUAGE variable is set, it should contain a directory name or names which specify a language (for example, ENGLISH or FRENCH). The files are searched for in a child directory of the NLS directory as specified by the NWLANGUAGE variable. The NLS directory in this instance is itself a child directory of the load directory. (The load directory contains the current utility's .EXE file.)The load directory (the directory containing the current utility's .EXE file). This is normally the PUBLIC directory.The PATH and DPATH (for OS/2 only) environment variables. These environment variables may be found either in the user's login script or in the AUTOEXEC.BAT file.The directories found under the child NLS subdirectory of the load directory. PAGENUM=1405 ID="BP9A"The directories found under the sibling NLS subdirectory of the load directory.Action: Find a current version of the message file and either copy it to a directory that is mapped to an existing search drive, or map a search drive to the file.ID="FM69424"999: The message file for this utility cannot be found.Explanation: When the utility tried to initialize the utility_name.MSG file, it was unable to find the file within the existing search drives. The following areas were searched:MARK=BULLETThe current directory.The NWLANGUAGE environment variable directory. If the NWLANGUAGE variable is set, it should contain a directory name or names which specify a language (for example, ENGLISH or FRENCH). The files are searched for in a child directory of the NLS directory as specified by the NWLANGUAGE variable. The NLS directory in this instance is itself a child directory of the load directory. (The load directory contains the current utility's .EXE file.)The load directory (the directory containing the current utility's .EXE file). This is normally the PUBLIC directory.The PATH and DPATH (for OS/2 only) environment variables. These environment variables may be found either in the user's login script or in the AUTOEXEC.BAT file.The directories found under the child NLS subdirectory of the load directory. The directories found under the sibling NLS subdirectory of the load directory.Action: Find a current version of the message file. Then, copy it to a directory that is mapped to an existing search drive, or map a search drive to the directory containing the file.