Date: November 16, 1987 Bulletin: 203 Title: NETWARE WORKSTATION SHELL ERRORS The following is a list explaining various NetWare workstation shell errors. NetWare is a registered trademark of Novell, Inc. NETWARE WORKSTATION SHELL ERRORS NetWare Version 2.0a Last Update: November 12, 1987 INDEX TO NETWARE WORKSTATION SHELL ERRORS A File Server could not be found................................. 1 Batteries are low. Server will go down in one minute............ 1 (CTRL-ENTER to clear)............................................ 1 Commercial power has been restored to server..................... 1 Invalid Parameter. Use "I" option to query shell type........... 2 Net Driver Crash: ......................... 2 NetWare Workstation Shell has already been loaded................ 2 Network Error: during . File = :................................ 3 Network Error on Server :..................... 7 Network Spooler Error: (probably out of space on SYS: volume).... 8 Not running on top of DOS version 2.x............................ 8 Not running on top of DOS version 3.x............................ 9 PIPE not found in transient portion of COMMAND.COM ** Program Aborted **.................................... 9 Shell Error: No active File Server attachments................... 9 The Network is inactive or you are not connected properly........ 9 Too many devices defined in DOS (over approximately 32) Device Table Overflow.................................... 10 Warning: disk write error in file FILENAME.EXT................... 10 You are on auxiliary power. Server will go down in nn minutes.... 11 NETWARE WORKSTATION SHELL ERRORS NetWare Version 2.0a A File Server could not be found. Meaning: This indicates that the shell could find no file server to attach to as it was being loaded and initialized. Cause: This message can be caused by a variety of problems that prevent the workstation from communicating with a file server as the shell is loaded. Bad or improperly configured shells or LAN interface cards can generate this error. Problems with the network, file servers, or the workstation's connection to the network can also cause this problem. Solution: Ensure that the LAN interface card in the file server is good and is jumpered correctly. Ensure that the shell is properly configured and linked to the correct LAN driver. Ensure that the workstation is properly connected to the network. Check to make sure that the rest of the network is up and functioning properly. Ensure that at least one active file server is connected to the network and that it is configured with an adequate number of router buffers. Batteries are low. Server will go down in one minute. Occurs only on servers with SFT II and TTS. Meaning: This message is displayed on all workstations attached to the server. The batteries of the UPS that the server is connected to are running low. The server will be shut down in one minute to prevent data loss unless normal AC power is restored. This is not a fatal error message but only a notice to the server users. This is one of the few error messages that is generated at the server and broadcast to all workstations. Cause: Normal AC power to the UPS has been disrupted and the UPS's batteries are nearly drained from providing backup power to the server. Solution: Logout all workstations immediately so that no data will be lost when the server is automatically DOWNed. Reboot the server when normal AC power is restored. (CTRL-ENTER to clear) Occurs on 68, 86, 286, ND286, SFT I, SFT II, and TTS. Meaning: This message appears on the bottom (25th line) of the screen when a message or broadcast from another user is received and displayed. Cause: Another station used the SEND command line utility or the BROADCAST or SEND console command to send a message. Solution: Pressing the ENTER key while holding down the CONTROL key will clear the message from the bottom of the screen. Commercial power has been restored to server. Occurs only on servers with SFT II and TTS. Meaning: This message is displayed on all workstations attached to the server. This message indicates to all users that are attached to the server that normal AC power has been restored to the UPS connected to the server and the server is no longer running on UPS battery backup. This is not an error message but only a system status report to the users. This is one of the few error messages that is generated at the server and broadcast to all workstations. Cause: The normal AC power has been disrupted and then restored. The UPS switched over to battery backup during the power disruption to continue to provide power to the server. The UPS has now switched back to normal AC power. Solution: No action is necessary. Invalid Parameter. Use "I" option to query shell type. Meaning and Cause: A user has attempted to enter an invalid parameter at the command line with the workstation shell COM filename. Solution: If the shell is to be loaded, no option parameters can be included with the shell name on the command line. If the user desires to query the shell type, the "I" option should be used after the shell name on the command line. No other option parameters are valid. Net Driver Crash: Meaning: This message indicates that the LAN driver linked to the shell has encountered an ABEND (ABnormal END) condition and has halted processing. An ABEND condition is one in which continued processing by the shell may cause further problems to the system. "Net Driver Crash" errors are always fatal and always halt the workstation. The is specific to the LAN driver linked with the shell and may give some indication of the cause of the problem. Cause: This error should never occur and is usually the result of a failed internal consistency check in the LAN driver. If this error is displayed, it means that an unrecoverable error condition has been encountered. Usually, this points to a hardware problem with the LAN interface card or to memory corruption in the workstation. Solution: Attempt to determine the possible cause from the displayed . Reboot the workstation. If the error occurs repeatedly, check for hardware problems in the LAN interface card and in the workstation. NetWare Workstation Shell has already been loaded. Meaning: This message indicates that the NetWare workstation shell can not be loaded on a workstation because a shell has already been loaded. It discovered that the shell prevents itself from being loaded more than once on a workstation. Cause: A NetWare shell is already loaded on this workstation. Solution: No action is necessary. The shell is already loaded and the user can now login. If a different shell must be loaded, the workstation must first be rebooted. Network Error: during . File = : Abort, Retry? or Abort, Retry, Fail? Meaning: This message indicates that the specified could not be performed because of the specified . The : specify the drive and filename on which the error condition occurred. If the is specified as "PUBLIC:," then the file is located on a search drive. Cause: A function call or DOS interrupt was called and the specified operation could not be performed. This error can be caused by many different situations. It could indicate problems in the file server setup and operation or in the applications programs being used. Solution: Press the "R" key to retry the operation. If the problem persists, look up the specific message below to help determine the actual cause and arrive at a solution of the problem. messages bad directory handle - The directory handle that was passed to the function call routine is invalid. This usually indicates a bug in the application program being run. file detached - A user has attempted to access a file which has previously been locked, used, and unlocked by the application program. However, the second time the file was not locked. Once locking is used on an opened file, it is necessary for locking to be used consistently thereafter when accessing the file. This error message usually indicates an application program bug! The code has locked a file in one place but neglected to lock the same file in another. file in use - The file specified in is locked for use by another process. This usually indicates that another workstation on the network is updating the same file. Wait until that workstation is finished and then try the operation again. File Server went down - This indicates that the file server went down while the specified operation was being processed. illegal completion code - The completion code returned from the indicated routine is invalid. This error is the result of a failed internal consistency check and should never occur. This error may result from intermixing different versions of the NetWare operating system, shell, and utilities. This error may also be caused by corrupted copies of the NetWare files. Use the INSTALL program to reinstall the NetWare operating system and utilities. Boot the workstation with another copy of the NetWare shell. invalid file handle - The file handle passed to the function call routine is invalid. This usually indicates a bug in the application program being run. IO attempted to physically locked area - A user has attempted to read or write to a location on the disk that is locked with a physical record or file lock. This usually indicates that another workstation has physically locked the location while it is using it. Wait until the other workstation is finished and then attempt the operation again. IO error in directory area - The network disk drive specified by has encountered an error while reading or writing the directory entry for the file named . This error usually indicates a hardware failure with the disk drive, the controller, or associated cables. IO error network disk - The network disk drive specified by has encountered an error while reading or writing the file named . This error usually indicates a hardware failure with the disk drive, the controller, or associated cables. no read privilege - A user who does not have the "Read" directory right has attempted to read the file named . Have the system supervisor use the SYSCON utility to assign the user "Read" trustee rights to the directory that contains the specified file. no write privilege or file read only - This message indicates two possible problems: 1) a user who does not have "Write" privileges in the file named has attempted to write to a file, or 2) the file has been flagged as a "Read Only" file. If the user does not have "Write" trustee right to the directory that contains the specified file, have the system supervisor assign the appropriate right with the SYSCON utility. Also ensure that the specified file has been flagged as a "Read/Write" file. out of directory handles - The file server has run out of available directory handles. The total number of file (or directory) handles can be increased by using the INSTALL utility to increase the Maximum number of open files on the server. out of disk space - This message indicates that the drive indicated by is out of available disk storage space. Additional disk storage space can be obtained by erasing files that are no longer needed, by replacing the disk drive with a larger unit, or by adding additional drives to the system. out of dynamic work space - This message indicates that the file server is out of dynamic memory work space. This error is caused by a failed internal consistency check and should never occur unless the NetWare operating system on the file server has become corrupt. Use the INSTALL program to reinstall the NetWare operating system file, NET$OS.EXE. out of file handles - The file server has run out of available file handles. The total number of file handles can be increased by using the INSTALL utility to increase the Maximum number of open files on the server. messages CHANGE FILE MODE - Change File Mode (CHMOD). Corresponds to DOS Function Call 43H. CHANGE THE CURRENT DIRECTORY - Change the Current Directory (CHDIR). Corresponds to DOS Function Call 3BH. CLOSE - Close a File. Corresponds to DOS Function Call 10H. CLOSE A FILE - Close a File Handle. Corresponds to DOS Function Call 3EH. CREATE - Create a File. Corresponds to DOS Function Call 16H. CREATE A FILE - Corresponds to DOS Function Calls 3CH. Can also be generated by DOS Function Call 3DH (Open a File). CREATE A SUBDIRECTORY - Create a Subdirectory (MKDIR). Corresponds to DOS Function Call 39H. CREATE NEW FILE - Corresponds to DOS Function Call 5BH. CREATE TEMP FILE - Create a Unique File. Corresponds to DOS Function Call 5AH. Can also be generated by DOS Function Call 3DH (Open A File). DELETE - Delete a File. Corresponds to DOS Function Call 13H. DELETE A FILE - Delete a File from a Specified Directory. Corresponds to DOS Function Call 41H. FIND FIRST MATCHING FILE - Find the First Matching File (FIND FIRST). Corresponds to DOS Function Call 4EH. FIND NEXT MATCHING FILE - Find the Next Matching File (FIND NEXT). Corresponds to DOS Function Call 4FH. GET CURRENT DIRECTORY - Corresponds to DOS Function Call 47H. GET SET A FILE DATE AND TIME - Get/Set a File's Date and Time. Corresponds to DOS Function Call 57H. IO CONTROL FOR DEVICES - I/O Control for Devices (IOCTL). Corresponds to DOS Function Call 44H. MOVE FILE POINTER - Move File Read Write Pointer (LSEEK). Corresponds to DOS Function Call 42H. OPEN - Open a File. Corresponds to DOS Function Call 0FH. OPEN A FILE - Corresponds to DOS Function Call 3DH. RANDOM BLOCK READ - Reads a Specified Number of Records from a File. Corresponds to DOS Function Call 27H. RANDOM BLOCK WRITE - Writes a Specified Number of Records to a File. Corresponds to DOS Function Call 28H. RANDOM READ - Reads a Specified Record from a File. Corresponds to DOS Function Call 21H. RANDOM WRITE - Writes a Specified Record to a File. Corresponds to DOS Function Call 22H. READ FROM A FILE - Read From a File or Device. Corresponds to DOS Function Call 3FH. REMOVE A SUBDIRECTORY - Remove a Subdirectory (RMDIR). Corresponds to DOS Function Call 3AH. RENAME - Rename a File. Corresponds to DOS Function Call 17H. RENAME A FILE - Corresponds to DOS Function Call 56H. SEARCH FIRST - Search for the First Matching Filename Entry in the Current Directory. Corresponds to DOS Function Call 11H. SEARCH NEXT - Search for the Next Matching Filename Entry in the Current Directory. Corresponds to DOS Function Call 12H. SEQUENTIAL READ - Sequentially Reads the Next Record from a File. Corresponds to DOS Function Call 14H. SEQUENTIAL WRITE - Sequentially Writes the Next Record to a File. Corresponds to DOS Function Call 15H. SET ATTRIBUTES - Network Environment Function 228: Set File Attributes (FCB). Corresponds to NetWare function call 228 (E4H). SPOOL LST: CATCH - NOT USED. UPDATE FILE SIZE - Network Environment Function 229: Update File Size (FCB). Corresponds to NetWare function call 229 (E5H). WRITE TO A FILE - Write to a File or Device. Corresponds to DOS Function Call 40H. Network Error on Server : Abort or Retry? Meaning: This message indicates that the specified network occurred during communication with the file server named . Cause: These errors are usually caused by improperly accessing the network. Several of these errors will never be seen and only exist for consistency checking of NetWare packets. The more common errors are usually caused by hardware problems on the network. Improper bus termination, exceeding maximum distance limitations, and broken or bad cables and connectors can all contribute to these errors. Solution: Press the "R" key to retry the operation. If the problem persists, look up the specific message below to help determine the actual cause and arrive at a solution of the problem. messages Attempted access to illegal or down server - A user has attempted to access the file server named and the server is down or the name is invalid. Ensure that the server's name is entered correctly and that it is up and attached to the network. Bad local network address. - This error message, which is no longer used, indicates that the local address being used to send a packet is bad. This message appears when a bad packet is received or workstation memory has become corrupted. Connection no longer valid. - The shell has sent a packet to a Server to which it is no longer connected. If the workstation looses connection to a file server to which it is attached for longer than about 10 minutes, the server's watchdog timer will invalidate the connection. The lost connection could be caused by a physical cable that is bad or unconnected, or by a router (a file server or bridge) that has gone down. If the workstation's physical connection is afterwards restored, the server no longer recognizes the connection and this message will be generated. Could not route to File Server. - This error message, which is no longer used, indicates that the network number being used to send a packet is bad. This message can be caused by receiving a bad packet or by corrupted workstation memory. Error locating router. - This error indicates that a route to the desired destination can not be found. When a network read or write error occurs and the retry option is selected, the shell will attempt to find an alternate route to the destination server. This error is displayed if the previously used route is now bad and no alternate route can be found. Error reading from network. - The workstation has encountered problems in attempting to receive and decode a NetWare packet. This error is usually caused by a hardware problem with the connections, cables, terminators, or the workstation LAN interface card. Error writing to network. - A workstation has encountered problems while attempting to format and send a NetWare packet. This error is usually caused by a hardware problem with the connections, cables, terminators, or the workstation LAN interface card. Reply invalid header. - A reply packet has been received from the file server but the IPX packet header checksum is invalid. This message can be caused by receiving a bad IPX packet or by corrupted workstation memory. Reply invalid sequence number. - A reply packet has been received from the file server but the packet header contains an invalid packet sequence number. This message can be caused by receiving a bad packet or by corrupted workstation memory. Reply invalid slot. - A reply packet has been received from the file server but the packet header contained an invalid slot number. This message can be caused by receiving a bad packet or by corrupted workstation memory. Reply packet lengths don't match. - A reply packet has been received from the file server but the actual length of the packet does not match the expected length stored in the packet's header. This message is no longer used. This message can only be caused by a failed internal consistency check probably caused by corrupted workstation memory. Unknown communications error code - The completion code returned in an ECB (Event Control Block) indicates an unknown communications error code. This message can only be caused by a failed internal consistency check probably caused by corrupted workstation memory. Network Spooler Error: (probably out of space on SYS: volume) Meaning: This message indicates that the network spooler encountered a fatal error and could no longer continue. Cause: The most common cause of this error is that the spooler has run out of available space on the SYS: volume in which to temporarily store the data to be printed. Solution: Free up space on the SYS: volume for the spooler by erasing or moving files from the volume. Also, ensure that the printer is online and running. Not running on top of DOS version 2.x. Meaning and Cause: This error message indicates that an attempt has been made to load the ANET2.COM shell onto a workstation that is not running DOS version 2.x. Solution: Use the correct shell for the version of DOS that you are using. If you are using DOS version 2.x, then load the ANET2.COM shell. If you are using DOS version 3.x, then load the ANET3.COM shell. Not running on top of DOS version 3.x. Meaning and Cause: This error message indicates that an attempt has been made to load the ANET3.COM shell onto a workstation that is not running DOS version 3.x. Solution: Use the correct shell for the version of DOS that you are using. If you are using DOS version 2.x, then load the ANET2.COM shell. If you are using DOS version 3.x, then load the ANET3.COM shell. PIPE not found in transient portion of COMMAND.COM. Meaning: This message indicates that the shell could not locate the filename used for DOS PIPE functions found in the transient portion of COMMAND.COM. The shell must find and change this name in order for piping to function properly on a file server. Cause: The most likely cause of this error message is a corrupted COMMAND.COM file or a corrupt NetWare shell file. Solution: Copy COMMAND.COM back onto your disk or diskettes. If this does not eliminate the problem, replace the NetWare shell file with a known good one. ** Program Aborted ** Meaning: This message indicates that the Abort option was selected after an error message was displayed with "Abort, Retry?" or "Abort, Retry, Fail?" The Abort operation causes the executing program to terminate and control to return to DOS. When "Abort" is chosen, the program being executed terminates and control returns to DOS. Shell Error: No active File Server attachments. Meaning: This message indicates that the workstation is no longer connected to any file server. Cause: This condition usually occurs when the server or servers to which a shell is attached (not necessarily logged into) go down, leaving the shell with no other file server attachments. Solution: Ensure that at least one file server is up and running on the network and then reboot the workstation. The Network is inactive or you are not connected properly. Meaning: This error will only occur as the shell is being loaded and initialized. This message is generated after the shell has successfully attached to the file server but is unable to complete its initialization process because it can no longer communicate with the file server. Cause: This error message can be caused by a bad or improper cable, terminator, or LAN interface card. Solution: Ensure that the cable connections are tight and that the LAN interface card is seated properly. Ensure that the cables and terminators are good and of the proper value. Also ensure that the correct shell and driver are being used and then attempt to load the shell again. Too many devices defined in DOS (over approximately 32)...Device Table Overflow. Meaning: This error message occurs while the shell is being loaded and indicates that the DOS device table is too full for the Network device could not be inserted into it as the shell was loaded. Cause: As the NetWare shell is loaded on top of DOS, it attempts to insert the Network device into the DOS device table. If the table is full (approximately 32 entries) then this error message is displayed and the shell is aborted. Solution: Remove some of the device drivers that are loaded in the CONFIG.SYS file. Then reboot the system and attempt to load the shell again. Warning: disk write error in file FILENAME.EXT Meaning: This is one of the few operating system error messages that is displayed at the workstation instead of the file server console. This error indicates that the read-after-write verification of a hard disk write failed when the file server attempted to write the file named "FILENAME.EXT" to disk. Whenever the hard disk is written to, the data is immediately read back and verified. If this error occurs, the file server console displays the corresponding error message: "Write Error: dir = SSSS file = FILENAME.EXT vol = VOLUMENAME." See the file server error message for more information. This error will never occur if Hot Fix is activated on the disk. Hot Fix will automatically redirect information sent to a bad sector to an alternate good sector on the disk and rewrite the data. This is not a fatal error but it does indicate that the noted file is corrupt on the disk. Cause: This error occurs when a disk location can no longer retain data accurately. This error can also be caused by faulty electronics in the file server's Disk Coprocessor Board (DCB), the disk controller, or even the hard disk drive itself. Solution: If the file is still open, attempt to save the file again under a different file name. The original file will be corrupt, but it should not be erased because another disk write may try to utilize the same bad area on the disk. Rename the corrupted file to a name that suggests that it is bad and discontinue using it. If the information in the file must be retrieved, attempt to copy it to another file. The VREPAIR utility may also be used on the file server to diagnose and repair file problems. You are on auxiliary power. Server will go down in nn minutes. Occurs only on servers with SFT II and TTS. Meaning: This message is displayed on all workstations attached to the server. This message indicates that the normal AC power has been disrupted and that file server is now running on auxiliary battery backup power. This message also indicates that the server will be shut down within the displayed number of minutes unless normal AC power is restored. This is not a fatal error message but only a warning to the users attached to the server. This is one of the few error messages that is generated at the server and broadcast to all workstations. Cause: Normal AC power has been disrupted and the file server is operating from UPS battery backup. Solution: No action is necessary. You will be notified again 1 minute before the server goes down or when normal power is restored.