Number 176 May 31, 1988 Title: NetWare File Server Errors The following is a NetWare File Server Errors report for NetWare 86, NetWare 286 Version 2.0a and NetWare 68 Version 2.01. This report will assist you in determining the error being made, the cause and the possible solutions. This report will be updated as needed and updates will be sent via Technical Bulletins. NETWARE FILE SERVER ERRORS NetWare/86 & 286 Version 2.0a NetWare/68 Version 2.01 Last Update: January 30, 1987 INDEX TO NETWARE FILE SERVER ERRORS 286 detected a memory failure in Disk CoProcessor . . . . . . . . 1 A invalid message number was returned to the background cache write process. . . . . . . . . . . . . . . . . . . . . . . . 1 Abandon Error Report? . . . . . . . . . . . . . . . . . . . . . 1 Abandon Volume Mount? . . . . . . . . . . . . . . . . . . . . . . 2 Abend: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Allocated cache block not found in SectorIndex. . . . . . . . . . 2 Attempt to configure a non-existent disk. . . . . . . . . . . . . 3 Bad block returned via Free. . . . . . . . . . . . . . . . . . . . 3 Bad block returned via KFree. . . . . . . . . . . . . . . . . . . 4 BAD PACKET ENCOUNTERED . . . . . . . . . . . . . . . . . . . . . . 4 Bindery Object List Warning . . . . . . . . . . . . . . . . . . . 4 Bindery Property List Warning . . . . . . . . . . . . . . . . . . 5 Bound interrupt. . . . . . . . . . . . . . . . . . . . . . . . . . 5 Breakpoint interrupt. . . . . . . . . . . . . . . . . . . . . . . 5 Cache Block Not Released During FlushCache . . . . . . . . . . . . 6 CacheRelease on non-used cache buffer. . . . . . . . . . . . . . . 6 Check specific message no such message in kernel. . . . . . . . . 6 ClearFileStation with files open. . . . . . . . . . . . . . . . . 7 Configured printer not found. . . . . . . . . . . . . . . . . . . 7 Could not find the destination network in the Star driver router list. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 DeAllocate semaphore attempted on active semaphore in kernel. . . 8 DeAttachFile invalid file handle. . . . . . . . . . . . . . . . . 8 Destroy Process not processed in kernel. . . . . . . . . . . . . . 8 DetachFile invalid file handle. . . . . . . . . . . . . . . . . . 9 DIRECTORY ACCESS BY UNAUTHORIZED PROCESS . . . . . . . . . . . . . 9 Dirty cache block has no dirty bits set . . . . . . . . . . . . . 9 Disk already Mounted . . . . . . . . . . . . . . . . . . . . . . . 10 Disk CoProcessor got a premature interrupt. . . . . . . . . . . . 10 Disk CoProcessor had a memory failure. . . . . . . . . . . . . . . 10 Disk CoProcessor had a ROM checksum error. . . . . . . . . . . . . 10 Disk CoProcessor returned invalid error code from diagnostics. . . 11 Disk CoProcessor timed out performing diagnostics. . . . . . . . . 11 DISK NOT FORMATTED FOR NETWARE NETWORK . . . . . . . . . . . . . . 12 DISK NOT UPGRADED TO ADVANCED NETWARE . . . . . . . . . . . . . . 12 diskrelease call to illegal cache block. . . . . . . . . . . . . . 12 Divide overflow interrupt. . . . . . . . . . . . . . . . . . . . . 13 Double exception interrupt. . . . . . . . . . . . . . . . . . . . 13 Drive already Dismounted. . . . . . . . . . . . . . . . . . . . . 13 Dynamic memory not available for Star line nodes. . . . . . . . . 14 Error attempting to open the file. . . . . . . . . . . . . . . . . 14 Error configuring Disk CoProcessor. . . . . . . . . . . . . . . . 14 Error Reading Configuration Info from Removable Disk. . . . . . . 15 ERROR READING NETWARE CONFIGURATION INFORMATION . . . . . . . . . 15 Error resetting external disk controller. . . . . . . . . . . . . 15 Error resetting the PC/AT hard disk controller. . . . . . . . . . 15 ERROR--CANNOT OPEN BINDERY FILES. . . . . . . . . . . . . . . . . 16 ERROR: VOLUME VOLUMENAME ALREADY MOUNTED. . . . . . . . . . . . . 16 i FAT Write Error: copy = c FAT sector = ssss volume = . . . . . . 17 FATAL ERROR -- NOT ENOUGH MEMORY TO SUPPORT DISK DRIVES. . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Fatal File System Error: zero First or Current Cluster. . . . . . 17 File is empty. . . . . . . . . . . . . . . . . . . . . . . . . . . 18 File System internal error: zero First or Current Cluster. . . . . 18 FlushBuffer with a non-zero use count. . . . . . . . . . . . . . . 18 General protection interrupt. . . . . . . . . . . . . . . . . . . 19 Global Descriptor Table overflow...too many segments defined. . . 19 Illegal Drive Number Specified . . . . . . . . . . . . . . . . . . 20 Illegal Printer Rerouting. . . . . . . . . . . . . . . . . . . . . 20 Illegal Removable Disk Specification. . . . . . . . . . . . . . . 20 Illegal Sector Number to Cache. . . . . . . . . . . . . . . . . . 20 INT0 Detected interrupt. . . . . . . . . . . . . . . . . . . . . . 21 Invalid drive passed to disk process. . . . . . . . . . . . . . . 21 Invalid memory size parameter.$ . . . . . . . . . . . . . . . . . 21 Invalid number of FCBs requested from configuration information. . 22 Invalid op code interrupt. . . . . . . . . . . . . . . . . . . . . 22 Invalid printer definition table. Run INSTALL to fix it. . . . . 22 Invalid process id passed by interrupt procedure to kernel. . . . 23 Invalid semaphore number passed to kernel. . . . . . . . . . . . . 23 Invalid task state interrupt. . . . . . . . . . . . . . . . . . . 23 LinkTree invalid file handle. . . . . . . . . . . . . . . . . . . 24 Maximum number of network files configured to be open is invalid. 24 Memory not available for star router tables. . . . . . . . . . . . 24 Message sent to invalid process in kernel. . . . . . . . . . . . . 25 !!! MOUNT ERROR -- NO FREE DYNAMIC MEMORY !!! . . . . . . . . . . 25 NDetachFile invalid file handle. . . . . . . . . . . . . . . . . . 26 NetWare/286 requires running on a IBM PC/AT or equivalent. . . . . 26 Network Operating System software is not serialized for this hardware. . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Network Operating System software is not serialized for this network. . . . . . . . . . . . . . . . . . . . . . . . . . . 27 NextRemoveFile invalid file handle. . . . . . . . . . . . . . . . 27 NMI interrupt. . . . . . . . . . . . . . . . . . . . . . . . . . . 27 No cache blocks available for allocation. . . . . . . . . . . . . 28 No Dirty Bits Set On Dirty Block. . . . . . . . . . . . . . . . . 28 !!! No Dynamic Work Space Available !!! . . . . . . . . . . . . . 28 NO FREE SPACE TO VERIFY DIRECTORIES . . . . . . . . . . . . . . . 29 NO FREE SPACE TO VERIFY FAT TABLES . . . . . . . . . . . . . . . . 29 No LAN Processor Boards are responding. . . . . . . . . . . . . . 29 No message packets available in kernel. . . . . . . . . . . . . . 30 No PCBs available in kernel. . . . . . . . . . . . . . . . . . . . 30 NO PRE-FETCH FOR DIRECTORY WRITE REQUEST . . . . . . . . . . . . . 30 No semaphores available in kernel. . . . . . . . . . . . . . . . . 31 Not enough memory available for cache blocks. . . . . . . . . . . 31 Not enough memory available for locks work space. . . . . . . . . 31 NOT ENOUGH MEMORY FOR DISK FAT TABLES. . . . . . . . . . . . . . . 32 Not enough memory to cache volume nn. . . . . . . . . . . . . . . 32 NReAttachFile invalid file handle. . . . . . . . . . . . . . . . . 33 NRemoveStationFile invalid file handle. . . . . . . . . . . . . . 33 Operating System / Server Mismatch. . . . . . . . . . . . . . . . 33 ii Out of dynamic memory. . . . . . . . . . . . . . . . . . . . . . . 34 Out of memory...too many FCBs requested. . . . . . . . . . . . . . 34 Out of message packets in the Kernel . . . . . . . . . . . . . . . 34 Over 64K segment requested by AllocSeg. . . . . . . . . . . . . . 35 Printer nn not in system. . . . . . . . . . . . . . . . . . . . . 35 Processor extension not supported. . . . . . . . . . . . . . . . . 35 Processor extension overrun interrupt. . . . . . . . . . . . . . . 35 Removable Drive nn locked for use by station ss. . . . . . . . . . 36 RemoveFromSectorIndex called with invalid cache buffer. . . . . . 36 Reply requested to non-existent message in kernel. . . . . . . . . 36 ResetBeingUsed call to cache block not being used. . . . . . . . . 37 ResetBeingUsed called on unused cache buffer. . . . . . . . . . . 37 Segment not present interrupt. . . . . . . . . . . . . . . . . . . 37 Semaphore created with negative initial value in kernel. . . . . . 38 SetBeingUsed already being used in cache. . . . . . . . . . . . . 38 SetBeingUsed call to cache block already set. . . . . . . . . . . 38 SetBeingUsed out of semaphores. . . . . . . . . . . . . . . . . . 39 Single step interrupt. . . . . . . . . . . . . . . . . . . . . . . 39 ***** SPOOLER ERROR ***** . . . . . . . . . . . . . . . . . . . . 39 SPOOLER ERROR--PRINTER NOT FOUND . . . . . . . . . . . . . . . . . 40 Stack overflow detected by kernel. . . . . . . . . . . . . . . . . 40 Stack segment overrun interrupt. . . . . . . . . . . . . . . . . . 40 StationRemoveFile invalid file handle. . . . . . . . . . . . . . . 40 SYSTEM ERRORS RECORDED IN SUPERVISOR FILE SYS$LOG.ERR . . . . . . 41 The Server has been Shut Down. Please Re-Boot to Restart. . . . . 41 Time out error configuring Disk CoProcessor. . . . . . . . . . . . 41 Time out on the first Disk CoProcessor. . . . . . . . . . . . . . 42 Time out on the second Disk CoProcessor. . . . . . . . . . . . . . 42 Timer Process out of Control Blocks. . . . . . . . . . . . . . . . 42 Too large a message request sent to kernel. . . . . . . . . . . . 43 TOO MANY VOLUMES ON SYSTEM . . . . . . . . . . . . . . . . . . . . 43 ??? UNKNOWN COMMAND ??? . . . . . . . . . . . . . . . . . . . . . 43 Unknown Removable Type . . . . . . . . . . . . . . . . . . . . . . 44 !!! VOLUME MOUNT ERROR -- NO FREE ALLOCATION SPACE !!! . . . . . . 44 VOLUME VOLUMENAME MOUNTED. DISMOUNT VOLUME BEFORE REMOVING! . . . . . . . . . . . . . . . . . . . . . . 44 *** WARNING *** ACTIVE FILES OPEN ON VOLUME. DISMOUNT? . . . . . . . . . . . . . . . . . . . . . . . . . 44 *** WARNING *** ACTIVE FILES OPEN. HALT NETWORK? . . . . . . . . 45 WARNING -- CANNOT CREATE MESSAGE FILE!!! . . . . . . . . . . . . . 45 WARNING -- CANNOT CREATE SPOOL FILE!!! . . . . . . . . . . . . . . 45 *** WARNING *** Directory sector sss data mirror mismatch. . . . . 46 *** WARNING *** DISK READ ERROR. CANCEL MOUNT? . . . . . . . . 46 Warning: disk write error in file FILENAME.EXT . . . . . . . . . . 47 !!! WARNING !!! ERROR MOUNTING DRIVE xx OF CONTROLLER yy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 *** WARNING *** FAT Entry ssss marked bad in FILENAME.EXT . . . . 48 *** WARNING *** FAT Entry ssss Marked Used with no File. . . . . . 48 *** WARNING *** FAT Entry ssss multiple allocation in FILENAME.EXT . . . . . . . . . . . . . . . . . . . . . . . . 49 *** WARNING *** FAT Entry ssss out of bounds in FILENAME.EXT . . . 49 *** WARNING *** FAT Entry ssss out of order in FILENAME.EXT . . . 50 iii *** WARNING *** FAT Table sector sss data mirror mismatch. . . . . 50 WARNING: FATAL DIR ERROR ON VOL VOLUMENAME DIR SECTOR sss. . . . . . . . . . . . . . . . . . . . . . . . . . 51 WARNING: FATAL DIR ERROR ON VOL VOLUMENAME FAT SECTOR sss. . . . . . . . . . . . . . . . . . . . . . . . . . 51 WARNING: INSUFFICIENT MEMORY TO HASH ALL DIRECTORIES. . . . . . . 52 WARNING: INSUFFICIENT MEMORY TO HASH DIRECTORIES. . . . . . . . . 52 WARNING! LAN n DEAD. . . . . . . . . . . . . . . . . . . . . . . . 52 ** WARNING ** Sector sss DIR Table n Read Error on VOLUMENAME. . . . . . . . . . . . . . . . . . . . . . . . . . 52 ** WARNING ** Sector sss FAT Table n Read Error on VOLUMENAME. . . . . . . . . . . . . . . . . . . . . . . . . . 53 Write Error: dir = ssss file = FILENAME.EXT vol = VOLUMENAME . . 53 iv NETWARE FILE SERVER ERRORS NetWare/86 & 286 Version 2.0a NetWare/68 Version 2.01 286 detected a memory failure in Disk CoProcessor Occurs on: 286 only. This is an Abend error. Meaning: This error indicates that a memory failure was detected in the dual-ported static RAM on a Disk CoProcessor (DCB) board by the 286 CPU. When a server is booting, the 286 CPU performs a small memory test on the DCB RAM after the DCB has passed all of its internal self diagnostics. Cause: This error can be caused by poor connections between the DCB and the mother board, by poor power supply regulation, or by a memory failure on the DCB. Solution: Clean the connector on the DCB and reseat the card. Check the power supply to make sure that clean, properly regulated DC is reaching the DCB. Replace the DCB if necessary. A invalid message number was returned to the background cache write process. Occurs on: 86 and 286. This is an Abend error. Meaning: The background cache write process was passed a message number that was invalid. This is an internal consistency check and this error should never occur in NetWare. Cause: This error could be caused by a memory failure in the file server attributable to either a hardware failure or poor power line conditioning. A corrupt operating system file might also cause this error. Solution: Reboot the file server. If this error or other Abend errors occur repeatedly, reinstall the operating system and then check the file server's memory and power line conditioning. Abandon Error Report? Occurs on: 68, 86, and 286. Meaning: This message may appear after several of the other operating system error messages when the file server is booting. This query is directed at the server manager when the server begins detecting possible file and/or FAT table inconsistencies as it mounts a volume. This query allows the server manager to choose whether the server continues displaying all errors that it encounters or not. Solution: Responding to this query with a "Y" will cause the server to quit reporting directory or FAT inconsistencies and 1 will simply mount the volume attempting its own fixup. Typing an "N" or simply a carriage return will cause the server to continue to report errors as they are found while mounting the volume. The file server will automatically repair all "data mirror mismatch" errors as the files that have the errors are used and rewritten. For most other problems, run VREPAIR or reload the operating system and/or files from a backup. Abandon Volume Mount? Occurs on: 68, 86 and 286. Meaning: This message may appear after several of the other operating system error messages. Whenever a potentially serious error occurs, the server gives the system manager the option of abandoning the volume mount process. Abandoning a volume mount ensures that a volume with potentially grave errors will not be mounted and accessed by server users until after the manager takes appropriate steps to correct the errors and/or save valuable information in the volume. Solution: Typing a "Y" in answer to this question will cause the server to stop the volume mount process for this volume. The server will then continue to mount other volumes and to initialize itself. When the server comes up, any information on the damaged volume will not be available to server users. Typing an "N" in answer to this question will cause the server to continue the volume mount process taking as much corrective action as it can to rectify the problems encountered. The file server will automatically repair all "data mirror mismatch" errors as the files that have the errors are used and rewritten. For most other problems, run VREPAIR or reload the operating system and/or files from a backup. Abend: Occurs on: 68, 86, and 286. Meaning: If the operating system encounters a fatal situation where continued processing would cause further damage to the system, the operating system halts the processor and displays the corresponding Abend (ABnormal END) message. Many Abend errors are the results of failed internal consistency checks that the operating system makes to ensure the integrity of the data involved. These consistency checks are always made immediately before performing critical operations. Abend errors are always fatal and always halt the file server. Solution: SEE THE SPECIFIC MESSAGE FOLLOWING "Abend:" Allocated cache block not found in SectorIndex. Occurs on: 68 only. This is an Abend error. 2 Meaning: This error means that the NetWare operating system Cache Buffer Manager was told to remove a sector from the cache memory sector index that was not there. This is an internal consistency check and the error should never occur. Cause: This error could be caused by a memory failure in the file server attributable to either a hardware failure or poor power line conditioning. A corrupt operating system file might also cause this error. Solution: Reboot the file server. If this error or other Abend errors occur repeatedly, reinstall the operating system and then check the file server's memory and power line conditioning. Attempt to configure a non-existent disk. Occurs on: 86 and 286. This is an Abend error. Meaning: The operating system attempted to configure and utilize a disk that is not attached to the system. Cause: This error is caused by physically removing a drive from the file server and not telling the operating system that it is no longer available with the INSTALL utility. This error could also be generated if the configuration set with the DISKSET (286 only) utility does not correspond to that set with INSTALL. DISKSET programs the EEPROM on the Disk CoProcessor Board for the drive configuration. INSTALL sets up the operating system for the specific drive configuration. These two configurations must agree. Solution: Whenever the disk configuration is physically changed, the operating system needs to be told by running the INSTALL utility. If the system has a Disk CoProcessor Board installed, the DISKSET utility must also be run and the settings must agree with both the physical disk configuration and the parameters set with the INSTALL utility. Bad block returned via Free. Occurs on: 68, 86, and 286. This is an Abend error. Meaning: A block of memory was returned by a process to the DGROUP memory segment to be reused. This error occurs if the address of the returned block of memory overlaps with a portion of memory that was not allocated. This is an internal consistency check and should never occur. Cause: This error could be caused by a memory failure in the file server attributable to either a hardware failure or poor power line conditioning. A corrupt operating system file might also cause this error. Solution: Reboot the file server. If this error or other Abend errors occur repeatedly, reinstall the operating system and 3 then check the file server's memory and power line conditioning. Bad block returned via KFree. Occurs on: 86 and 286. This is an Abend error. Meaning: A block of memory was returned by a process to the file lock memory segment to be reused. This error occurs if the address of the returned block of memory overlaps with a portion of memory that was not allocated. This is an internal consistency check and should never occur. Cause: This error could be caused by a memory failure in the file server attributable to either a hardware failure or poor power line conditioning. A corrupt operating system file might also cause this error. Solution: Reboot the file server. If this error or other Abend errors occur repeatedly, reinstall the operating system and then check the file server's memory and power line conditioning. BAD PACKET ENCOUNTERED Occurs on: 68, 86, and 286. Meaning: This message will be displayed on the server console if the console is in TRACK ON mode and if a bad router packet is received. This is not a fatal error. Cause: This error condition is usually caused by transmission problems over the cables or through the network interface cards. Improper cable type, improper cable termination and extended cable lengths can all cause packets to be lost or distorted. Solution: Check cable types, cable termination, and cable lengths. If none of these seem to be causing the problem, check the interface cards. If several servers are connected together through a large internetwork, the entire network may need to be checked out. Bindery Object List Warning Occurs on: 68, 86, and 286. Meaning: This error occurs only on boot up of the file server and indicates that the operating system has detected possible corruption in the Object List in the bindery files. This is only a warning of possible contamination and is not a fatal error. Cause: The Bindery files might be corrupted if the server was halted suddenly by a hardware or power failure or by bringing down the network without the DOWN command. 4 Solution: After the file server has completed booting, attempt to access the problems with the bindery. If the bindery has been badly damaged, use the BINDFIX utility to repair it. If necessary, restore the bindery files from a backup. Bindery Property List Warning Occurs on: 68, 86, and 286. Meaning: This error occurs only on boot up of the file server and indicates that the operating system has detected possible corruption in the Property List in the bindery files. This is only a warning of possible contamination and is not a fatal error. Cause: The Bindery files might be corrupted if the server was halted suddenly by a hardware or power failure or by bringing down the network without the DOWN command. Solution: After the file server has completed booting, attempt to access the problems with the bindery. If the bindery has been badly damaged, use the BINDFIX utility to repair it. If necessary, restore the bindery files from a backup. Bound interrupt. Occurs on: 286 only. This is an Abend error. Meaning: This is interrupt 5 in the 286 CPU and is generated if the CPU detects an operand outside of predefined values. This interrupt should never occur in NetWare. Cause: This error could be caused by a memory failure in the file server could be attributable to either a hardware failure or poor power line conditioning. A corrupt operating system file might also cause this error. Solution: Reboot the file server. If this error or other interrupt errors occur repeatedly, reinstall the operating system and then check the file server's memory and power line conditioning. Breakpoint interrupt. Occurs on: 286 only. This is an Abend error. Meaning: This is interrupt 3 in the 286 CPU and is generated by executing a breakpoint instruction for debug purposes. The NetWare operating system does not contain any breakpoint instructions and therefore, this interrupt should never occur. Cause: This error could be caused by a memory failure in the file server could be attributable to either a hardware failure or poor power line conditioning. A corrupt operating system file might also cause this error. Solution: Reboot the file server. If this error or other interrupt errors occur repeatedly, reinstall the operating system and 5 then check the file server's memory and power line conditioning. Cache Block Not Released During FlushCache Occurs on: 68 only. This is an Abend error. Meaning: A cache block that was to be flushed (written back to disk) by the "FlushCache" routine was still in use. This error is the result of a failed internal consistency check and should never occur in NetWare. Cause: This error could be caused by a memory failure in the file server attributable to either a hardware failure or poor power line conditioning. A corrupt operating system file might also cause this error. Solution: Reboot the file server. If this error or other Abend errors occur repeatedly, reinstall the operating system and then check the file server's memory and power line conditioning. CacheRelease on non-used cache buffer. Occurs on: 86 and 286. This is an Abend error. Meaning: A process attempted to release a cache buffer that has never been flagged for use in the "CacheRelease" routine. This error is the result of a failed internal consistency check and should never occur in NetWare. Cause: This error could be caused by a memory failure in the file server and could be attributable to either a hardware failure or poor power line conditioning. A corrupt operating system file might also cause this error. Solution: Reboot the file server. If this error or other Abend errors occur repeatedly, reinstall the operating system and then check the file server's memory and power line conditioning. Check specific message no such message in kernel. Occurs on: 86 and 286. This is an Abend error. Meaning: A process sent an invalid message to another process in the multi-tasking kernel. This error should never occur in NetWare. Cause: This error could be caused by a memory failure in the file server and could be attributable to either a hardware failure or poor power line conditioning. A corrupt operating system file might also cause this error. Solution: Reboot the file server. If this error or other Abend errors occur repeatedly, reinstall the operating system and then check the file server's memory and power line conditioning. 6 ClearFileStation with files open. Occurs on: 68, 86, and 286. This is an Abend error. Meaning: This error is the result of a failed internal consistency check and should never occur. This error is generated in the file handling routines in the operating system. Cause: This error could be caused by a memory failure in the file server and could be attributable to either a hardware failure or poor power line conditioning. A corrupt operating system file might also cause this error. Solution: Reboot the file server. If this error or other Abend errors occur repeatedly, reinstall the operating system and then check the file server's memory and power line conditioning. Configured printer not found. Occurs on: 86 and 286. Meaning: This error is displayed on the server console as the server boots if it cannot access the communication port assigned to a printer that is configured on the system. This is not a fatal error and the server will continue to come up. Cause: This error could be caused by a bad or missing communications port. This error could also be caused by a printer configuration that has been INSTALLed that does not agree with the present file server hardware configuration. Solution: Ensure that the file server has all of the communication ports installed that are configured for printers in the operating system. If a communication port has been removed from the file server, run the INSTALL utility and remove the printer that was using that port from the operating system. If the communications port is installed in the file server and you still get this error, check and repair or replace the port. Could not find the destination network in the Star driver router list. Occurs on: 68 only. This is an Abend error. Meaning: This error is generated in the router when it cannot find the destination network of a packet in its star driver router list. This error is the result of a failed internal consistency check and should never occur. Cause: This error could be caused by a memory failure in the file server and could be attributable to either a hardware failure or poor power line conditioning. A corrupt operating system file might also cause this error. Solution: Reboot the file server. If this error or other Abend errors occur repeatedly, reinstall the operating system and 7 then check the file server's memory and power line conditioning. DeAllocate semaphore attempted on active semaphore in kernel. Occurs on: 86 and 286. This is an Abend error. Meaning: The multi-tasking kernel attempted to deallocate a semaphore that was no longer needed and found that it was still active. This error is the result of a failed internal consistency check and should never occur in NetWare. Cause: This error could be caused by a memory failure in the file server and could be attributable to either a hardware failure or poor power line conditioning. A corrupt operating system file might also cause this error. Solution: Reboot the file server. If this error or other Abend errors occur repeatedly, reinstall the operating system and then check the file server's memory and power line conditioning. DeAttachFile invalid file handle. Occurs on: 68 only. This is an Abend error. Meaning: This error is generated in the file handling routines in the operating system if they encounter an invalid file handle. This error is the result of a failed internal consistency check and should never occur. Cause: This error could be caused by a memory failure in the file server and could be attributable to either a hardware failure or poor power line conditioning. A corrupt operating system file might also cause this error. Solution: Reboot the file server. If this error or other Abend errors occur repeatedly, reinstall the operating system and then check the file server's memory and power line conditioning. Destroy Process not processed in kernel. Occurs on: 86 and 286. This is an Abend error. Meaning: This error is generated by the multi-tasking kernel if it attempts to destroy a process that either does not exist or that is still actively processing information. This error is the result of a failed internal consistency check and should never occur in NetWare. Cause: This error could be caused by a memory failure in the file server and could be attributable to either a hardware failure or poor power line conditioning. A corrupt operating system file might also cause this error. Solution: Reboot the file server. If this error or other Abend errors occur repeatedly, reinstall the operating system and 8 then check the file server's memory and power line conditioning. DetachFile invalid file handle. Occurs on: 68 only. This is an Abend error. Meaning: This error is generated in the file handling routines in the operating system if they encounter an invalid file handle. This error is the result of a failed internal consistency check and should never occur. Cause: This error could be caused by a memory failure in the file server and could be attributable to either a hardware failure or poor power line conditioning. A corrupt operating system file might also cause this error. Solution: Reboot the file server. If this error or other Abend errors occur repeatedly, reinstall the operating system and then check the file server's memory and power line conditioning. DIRECTORY ACCESS BY UNAUTHORIZED PROCESS Occurs on: 68, 86, and 286. This is an Abend error. Meaning: This error results from a failed internal consistency check. A process in the multi-tasking kernel attempted to access a directory entry that it was not authorized to access. This error should never occur in NetWare. Cause: This error could be caused by a memory failure in the file server and could be attributable to either a hardware failure or poor power line conditioning. A corrupt operating system file might also cause this error. Solution: Reboot the file server. If this error or other Abend errors occur repeatedly, reinstall the operating system and then check the file server's memory and power line conditioning. Dirty cache block has no dirty bits set Occurs on: 86 and 286. This is an Abend error. Meaning: The process in the multi-tasking kernel that writes a modified (dirty) block in cache memory back onto the disk was notified that a dirty block existed but the process could not locate it. This error is the result of a failed internal consistency check and should never occur in NetWare. Cause: This error could be caused by a memory failure in the file server and could be attributable to either a hardware failure or poor power line conditioning. A corrupt operating system file might also cause this error. Solution: Reboot the file server. If this error or other Abend errors occur repeatedly, reinstall the operating system and 9 then check the file server's memory and power line conditioning. Disk already Mounted Occurs on: 68, 86, and 286. Meaning: This error indicates the removable disk that was being mounted with the MOUNT command is already mounted. This is not a fatal error. Solution: If the disk needs to be changed, DISMOUNT the prior removable disk before inserting and MOUNTing the new disk. Disk CoProcessor got a premature interrupt. Occurs on: 286 only. This is an Abend error. Meaning: When the Disk CoProcessor Board (DCB) completes a request made to it by the 286 CPU, it sets a flag in its internal dual-ported RAM and then sends an interrupt request to the CPU. When the CPU receives the interrupt request, it accesses the flag from the DCB's memory and checks it as an internal consistency check. If the flag is not valid, the file server generates this error message. This is a fatal error and it usually means that the memory on the DCB has failed or been overwritten. Cause: The most probable causes for this condition are power or hardware failures. Also, this error could occur if other cards installed in the file server are using the same IRQ line. Solution: Power off and then back on the file server. If the error continues to occur, check to make sure that no other cards in the file server are using the same IRQ lines as the DCBs. Then check the line power to the file server and try replacing the Disk CoProcessor Boards. Disk CoProcessor had a memory failure. Occurs on: 286 only. This is an Abend error. Meaning: This error indicates that a memory failure was detected in the dual-ported static RAM on a Disk CoProcessor (DCB) board by the DCB self diagnostics. As a file server boots, NetWare commands the DCB to perform its internal self diagnostics before the drives are brought online. Cause: This error can be caused by poor connections between the DCB and the mother board, by poor power supply regulation, or by a memory or other hardware failure on the DCB. Solution: Clean the connector on the DCB and reseat the card. Check the power supply to make sure that clean, properly regulated DC is reaching the DCB. Replace the DCB if necessary. Disk CoProcessor had a ROM checksum error. 10 Occurs on: 286 only. This is an Abend error. Meaning: This error indicates that the contents of ROM on a Disk CoProcessor Board (DCB) did not match its checksum when the DCB performed its internal self diagnostics. As a file server boots, NetWare commands the DCB to perform its internal self diagnostics before the drives are brought online. Cause: This error can be caused by poor connections between the DCB and the mother board, by poor power supply regulation, or by a ROM or other hardware failure on the DCB. Solution: Clean the connector on the DCB and reseat the card. Reseat and check the EPROM on the DCB for bent pins. Check the power supply to make sure that clean, properly regulated DC is reaching the DCB. Replace the DCB if necessary. Disk CoProcessor returned invalid error code from diagnostics. Occurs on: 286 only. This is an Abend error. Meaning: As a file server boots, NetWare commands the Disk CoProcessor Boards (DCB) to perform their internal self diagnostics before the drives are brought online. This error indicates that an invalid error return code was returned from the DCB to the 286 CPU. Cause: This error can be caused by poor connections between the DCB and the mother board, by improper SCSI bus termination, by poor power supply regulation, or by a hardware failure on the DCB. Solution: Clean the connector on the DCB and reseat the card. Check to make sure that the SCSI bus is properly terminated. A terminating resistor pack should be installed only on the last controller physically connected to the SCSI bus. Check the power supply to make sure that clean, properly regulated DC power is reaching the DCB. Replace the DCB if necessary. Disk CoProcessor timed out performing diagnostics. Occurs on: 286 only. This is an Abend error. Meaning: As a file server boots, NetWare commands the Disk CoProcessor Boards (DCB) to perform their internal self diagnostics before the drives are brought online. This error indicates that no response was received from a DCB within a specific amount of time after it was sent the command to perform its internal diagnostics. Cause: This error can be caused by poor connections between the DCB and the mother board, by poor power supply regulation, or by a hardware failure on the DCB. On older revision DCBs, this error might appear if no controllers and/or drives are connected to the DCB. 11 Solution: Clean the connector on the DCB and reseat the card. Check the power supply to make sure that clean, properly regulated DC is reaching the DCB. On older DCB's, ensure that at least one controller with a drive is connected. Replace the DCB if necessary. DISK NOT FORMATTED FOR NETWARE NETWORK Occurs on: 68, 86, and 286. Meaning: This error indicates that the disk the file server is attempting to mount has not been formatted to NetWare. This error is not fatal and will not halt the operation of the file server unless this is the first disk on the system. Cause: The disk has not been COMPSURFed. As COMPSURF completes the formatting of a disk, it writes special information onto the disk indicating that the disk is NetWare compatible. This error could also occur if track 0 of the disk has been damaged or overwritten. Solution: To correct this problem, run the COMPSURF utility on the disk and then run the INSTALL utility. If the error was caused by a track 0 problem, any files that were on the disk will have to be restored from a backup after running COMPSURF and INSTALL. If the drive does not pass COMPSURF, you will need to replace the drive. DISK NOT UPGRADED TO ADVANCED NETWARE Occurs on: 68, 86 and 286. This is an Abend error. Cause: This error occurs when a file server is attempting to mount a drive utilizing Advanced NetWare and the drive was originally installed with a version of NetWare prior to Advanced NetWare 1.0. This error could also occur if track 0 of the disk has been damaged or overwritten. Solution: If you do not want to upgrade the disk to Advanced NetWare, you will need to boot the file server with an earlier version of NetWare. If you want to upgrade the file server to Advanced NetWare, you will need to run the UPGRADE utility found on the INSTALL diskette of Advanced NetWare. This utility should be run only once for each disk that is to be upgraded. If the disk has been previously operating under Advanced NetWare, then track 0 has probably been damaged or overwritten. In this case, you will have to run COMPSURF on the disk. All files on the disk will have to be restored from a backup after running COMPSURF. diskrelease call to illegal cache block. Occurs on: 68 only. This is an Abend error. Meaning: This error is the result of a failed internal consistency 12 check in the caching routines and should never occur in NetWare. Cause: This error could be caused by a memory failure in the file server and could be attributable to either a hardware failure or poor power line conditioning. A corrupt operating system file might also cause this error. Solution: Reboot the file server. If this error or other Abend errors occur repeatedly, reinstall the operating system and then check the file server's memory and power line conditioning. Divide overflow interrupt. Occurs on: 286 only. This is an Abend error. Meaning: This is interrupt 0 in the 286 CPU and it is generated by the CPU if the quotient of a division instruction would be too large to be represented or if the divisor is 0. This interrupt should never occur in NetWare and will generate a fatal abend error. Cause: This error could be caused by a memory failure in the file server and could be attributable to either a hardware failure or poor power line conditioning. A corrupt operating system file might also cause this error. Solution: Reboot the file server. If this error or other interrupt errors occur repeatedly, reinstall the operating system and then check the file server's memory and power line conditioning. Double exception interrupt. Occurs on: 286 only. This is an Abend error. Meaning: This is interrupt 8 in the 286 CPU and it is generated by the CPU if two separate memory protection violations occur during the execution of a single instruction. This interrupt should never occur in NetWare. Cause: This error could be caused by a memory failure in the file server and could be attributable to either a hardware failure or poor power line conditioning. A corrupt operating system file might also cause this error. Solution: Reboot the file server. If this error or other interrupt errors occur repeatedly, reinstall the operating system and then check the file server's memory and power line conditioning. Drive already Dismounted. Occurs on: 68, 86, and 286. Meaning: This error indicates that the removable disk that was 13 being dismounted with the DISMOUNT command is already dismounted. This is not a fatal error. Solution: If the disk needs to be changed, DISMOUNT the prior removable disk and then insert and MOUNT the new disk. Dynamic memory not available for Star line nodes. Occurs on: 68 only. This is an Abend error. Meaning: This error occurs if the file server does not have enough available dynamic memory for Star line nodes. Cause: File server does not have enough dynamic memory available to it. This error could also be generated as a result of a failure in high memory which would cause the file server to think that it has less memory installed. Solution: Run SYSED and increase the amount of dynamic memory available for use by the server. Test the memory to ensure that it is good. If necessary, add more memory to the file server. Error attempting to open the file. Occurs on: 68, 86, and 286. This is a spooler error. Meaning: This message will be PRINTED (on a printer, not on the server console) along with a banner page if the print spooler cannot open the file to be printed when it attempts to send the file to the printer. This is not a fatal error. Cause: This error usually occurs because the file is locked for use by some station when the printer attempts to open it. Solution: Send the report to the spooler again and keep all workstations from accessing the file until after it prints. Error configuring Disk CoProcessor. Occurs on: 286 only. This is an Abend error. Meaning: This error occurs when the SCSI device driver programs a Disk CoProcessor Board (DCB) and the DCB returns an error status after attempting to configure itself. When the DCB attempts to configure itself, it may try to access each of the disks that should be connected to it. If it cannot access these disks properly for any reason, the DCB will return an error status to the driver, which in turn would generate this error message. Cause: This error is usually caused by a hardware problem with a drive, a controller or the interface cables. Since the DCB has passed its self-diagnostics previous to being programmed, the DCB should be O.K. Solution: Check all of the drives, controllers and disk interface 14 cables connected to the file server. Repair or replace any that are suspected of causing this error. Error Reading Configuration Info from Removable Disk. Occurs on: 68, 86, and 286. Meaning: This error will be displayed if the server cannot read from track 0 of a removable volume to get the disk configuration tables. This is not a fatal error but the removable disk will not be mounted. Cause: This error occurs if the disk is not formatted for NetWare or not configured properly, if the disk related hardware is not working properly, or if a disk error is encountered on track 0 of the removable disk. Solution: Use the SYSED utility to check the disk and related hardware and to verify the installation information. If the disk has not been formatted for NetWare or if a disk error has been encountered, run the COMPSURF utility. Use the INSTALL utility to reinstall the operating system and then restore the files from a backup if required. ERROR READING NETWARE CONFIGURATION INFORMATION Occurs on: 68, 86, and 286. This is an Abend error. Meaning: This error will be displayed if the server cannot read from track 0 of the SYS: volume to get the disk configuration tables. This is a fatal error. Cause: This error occurs if the disk is not configured correctly, if the disk related hardware is not working properly, or if a bad sector on track 0 of the disk is encountered. Solution: Use the SYSED utility to check the disk and verify the installation information. If a disk error has been encountered, run the COMPSURF utility. Repair or replace any disk related hardware that may not be working properly. Reinstall the operating system and/or restore the files from a backup if required. Error resetting external disk controller. Occurs on: 86 only. This is an Abend error. Meaning: The NetWare operating system attempted to reset the external disk controller three times without success. Cause: This error could be caused by loose or bad connections or a bad disk controller. Solution: Make sure that the disk cables are good and are connected properly. Reseat the disk controller board. If none of these work, try swapping the disk controller board. Error resetting the PC/AT hard disk controller. 15 Occurs on: 286 only. This is an Abend error. Meaning: The NetWare operating system attempted to reset the PC/AT hard disk controller three times without success. Cause: This error could be caused by loose or bad connections or a bad disk controller. Solution: Make sure that the disk cables are good and are connected properly. Reseat the disk controller board. If none of these work, try swapping the disk controller board. ERROR--CANNOT OPEN BINDERY FILES. Occurs on: 68, 86, and 286. Meaning: When the file server boots, it attempts to locate the bindery files. If it cannot find the bindery files, the file server will attempt to create them. This error occurs if the file server cannot create new bindery files after it has failed to locate any existing bindery files. Cause: This error indicates that there are no bindery files on the SYS: volume. If they should exist, this error indicates potentially serious problems with the files on the file server. Since the system is attempting to create the bindery files and cannot the SYS: volume may have a full directory or be out of available disk space. This error may also occur if the file server does not have enough memory to support the amount of disk space that is attached to it. Solution: Use the VREPAIR utility to check and repair any problems with the files on the file server. If the SYS: volume directory is full, use the INSTALL utility to expand it. If the file server does not have enough memory to support the amount of disk space being used, add more memory to the file server. If the volume is out of available disk space, it will have to be reinitialized and reINSTALLed. The files on the server can then be reloaded from a current backup. ERROR: VOLUME VOLUMENAME ALREADY MOUNTED. Occurs on: 68, 86, and 286. Meaning: This error occurs when the file server attempts to mount a volume that has the same name as another volume that is already mounted. "VOLUMENAME" is the name of the volume that the server is attempting to mount. This is not a fatal error. Cause: This error could occur if mounting a removable volume that has the same name as a volume that is already mounted on the system. This error could also occur if disk subsystems are interchanged between file servers and a volume on one of the disk subsystems has the same name as another volume connected to the same file server. 16 Solution: Ensure that every volume that is used on a file server has its own unique volume name. Use the INSTALL (86 or 286) or the SYSED (68) utility to change the name of a volume that is the same as another volume. FAT Write Error: copy = c FAT sector = ssss volume = VOLUMENAME Occurs on: 68, 86, and 286. Meaning: This error indicates that the read-after-write verification of a FAT sector write failed. Two copies of the FAT are stored on the disk. "c" is the copy number (0=primary, 1=secondary or mirror), "ssss" is the sector number and "VOLUMENAME" is the name of the volume on which the error occurred. This error will never occur if HOTFIX is activated on the disk. HOTFIX will automatically redirect the bad sector to an alternate good sector on the disk and rewrite the data. This is not a fatal error and the file server will continue normal operation. Cause: This error could be caused by a location on the disk that has gone bad and can no longer correctly retain data. This error could also be caused by faulty electronics on the Disk CoProcessor Board (DCB), the disk controller or the hard disk itself. Solution: Use the VREPAIR utility to diagnose and repair any problems with the disk. Verify that the disk related hardware is working properly. FATAL ERROR -- NOT ENOUGH MEMORY TO SUPPORT DISK DRIVES. Occurs on: 68 only. This is an Abend error. Meaning: This will be displayed when after setting up its internal tables the file server does not have enough memory left to cache the File Allocation Tables for all of the mounted disk volumes. The file server must have 1 kilobyte of memory for each megabyte of disk storage in which to cache the FAT tables for all mounted volumes. Cause: This error may be caused by attempting to mount more disk space than the amount of memory that is in the file server will support. This error may also occur if a high bank of memory failed in the file server, causing it to run with less than its normal amount of memory. Solution: Check the memory in the file server to insure that it is good. Run SYSED and decrease the amount of disk storage that is to be mounted by eliminating a volume or volumes or add additional memory to the file server. If the recommended amount of disk storage is exceeded, then the amount of disk storage must be reduced. Fatal File System Error: zero First or Current Cluster. Occurs on: 68, 86, and 286. This is an Abend error. 17 Meaning: This error would be generated when a process in the operating system attempts to extend an existing file and finds that the first or the current cluster number is zero. A file's first and current cluster numbers point to the physical area on the disk that the file is located in. These numbers can never be zero. This is a consistency check to ensure the integrity of the file before the file is extended. The occurrence of this error indicates that the file is potentially severely corrupted. Cause: This error could be caused by a memory failure in the file server and could be attributable to either a hardware failure or poor power line conditioning. This could also be caused by a problem with the disk or related hardware. Solution: Reboot the file server. Check the file server's memory and power line conditioning. Check the disk and related hardware. File is empty. Occurs on: 68, 86, and 286. This is a Spooler error. Meaning: This message will be PRINTED (on a printer, not on the server console) along with a banner page if the print spooler attempts to print an empty file that was sent to the queue. This just notifies the user that the selected report did not print because it had no information in it. This is not a fatal error. File System internal error: zero First or Current Cluster. Occurs on: 68 only. This is an Abend error. Meaning: This error would be generated when the operating system attempts allocate space on the disk and finds that the first or the current cluster number is zero. A file's first and current cluster numbers point to the physical area on the disk that the file is located in. These numbers can never be zero. This is a consistency check to ensure the integrity of the disk. The occurrence of this error indicates that the volume is potentially corrupted. Cause: This error could be caused by a memory failure in the file server and could be attributable to either a hardware failure or poor power line conditioning. This could also be caused by a problem with the disk or related hardware. Solution: Reboot the file server. Check the file server's memory and power line conditioning. Check the disk and related hardware. FlushBuffer with a non-zero use count. Occurs on: 86 and 286. This is an Abend error. Meaning: This error is generated if the operating system caching routines attempt to flush a buffer that is still in use. This 18 error is the result of a failed internal consistency check and should never occur. Cause: This error could be caused by a memory failure in the file server and could be attributable to either a hardware failure or poor power line conditioning. A corrupt operating system file might also cause this error. Solution: Reboot the file server. If this error or other Abend errors occur repeatedly, reinstall the operating system and then check the file server's memory and power line conditioning. General protection interrupt. Occurs on: 286 only. This is an Abend error. Meaning: This is interrupt 13 in the 286 CPU and it is generated by the CPU when memory protection violations occur that are not specifically handled by interrupts 9-12. For example, attempting to write to a segment that has been defined as read-only will generate this interrupt. This interrupt should never occur in NetWare and will generate a fatal abend error. This error usually indicates that the CPU's registers and/or the file server's memory has been severely altered. Cause: This error can be caused by just about anything including both hardware and software. The most probable cause of such an error would be a memory failure in the file server attributable to either a hardware failure or poor power line conditioning. A corrupt operating system file might also cause this error. On older 286 systems with early versions of NetWare, this error would occur when the file server's memory was over 4 MB or when the cache block size was set to under 4096. Solution: Reboot the file server. If this error or other interrupt errors occur repeatedly, reinstall the operating system and then check the file server's memory and power line conditioning. Attempt to narrow the problem down to hardware or software. Try replacing the interface cards, adding more memory, slowing the clock rate down, or reconfiguring the operating system. On older systems, decrease the amount of memory in the file server to a level below 4 MB and/or increase the cache block size to at least 4096 using the INSTALL utility. If neither of these work, you may need to upgrade the operating system. Global Descriptor Table overflow...too many segments defined. Occurs on: 286 only. This is an Abend error. Meaning: The operating system attempted to define too many memory segments in the Global Descriptor Table for the 286 CPU. This error should never occur in NetWare. 19 Cause: This error could be caused by a memory failure in the file server and could be attributable to either a hardware failure or poor power line conditioning. A corrupt operating system file might also cause this error. Solution: Reboot the file server. If this error or other Abend errors occur repeatedly, reinstall the operating system and then check the file server's memory and power line conditioning. Illegal Drive Number Specified Occurs on: 68, 86, and 286. Meaning: This error is displayed on the file server console when attempting to MOUNT a drive number that is not defined in the server. This is not a fatal error and will not affect the operation of the file server. Solution: Attempt to only MOUNT volumes that have been defined in the file server with the INSTALL utility. Illegal Printer Rerouting. Occurs on: 68, 86, and 286. Meaning: This error is displayed on the file server console when attempting to use the "REROUTE PRINTER" console command to reroute print jobs to a printer that is not defined on the server. This is not a fatal error and will not affect the operation of the file server. Solution: Attempt to only reroute printers to other printers that are defined on the file server. Illegal Removable Disk Specification. Occurs on: 68, 86, and 286. Meaning: This error is displayed on the file server console when attempting to DISMOUNT a drive that is not defined as a removable volume in the server. This is not a fatal error and will not affect the operation of the file server. Solution: Attempt to only DISMOUNT volumes that are specified as removable volumes in the system. Illegal Sector Number to Cache. Occurs on: 68 only. This is an Abend error. Meaning: The Cache manager in the multi-tasking kernel attempted to read and cache a sector of disk that does not exist. The sector number does not exist because it is higher than the number of logical sectors on that particular disk. This error is the result of a failed internal consistency check and should never occur in NetWare. 20 Cause: This error could be caused by a memory failure in the file server and could be attributable to either a hardware failure or poor power line conditioning. A corrupt operating system file might also cause this error. Solution: Reboot the file server. If this error or other Abend errors occur repeatedly, reinstall the operating system and then check the file server's memory and power line conditioning. INT0 Detected interrupt. Occurs on: 286 only. This is an Abend error. Meaning: This is interrupt 4 in the 286 CPU and it is generated by the CPU if the overflow flag is set when a INT0 instruction is executed. This interrupt should never occur in NetWare. Cause: This error could be caused by a memory failure in the file server and could be attributable to either a hardware failure or poor power line conditioning. A corrupt operating system file might also cause this error. Solution: Reboot the file server. If this error or other interrupt errors occur repeatedly, reinstall the operating system and then check the file server's memory and power line conditioning. Invalid drive passed to disk process. Occurs on: 86 and 286. This is an Abend error. Meaning: This error indicates that a command to access the disk specified a drive that is not on the system. This is a fatal error. This error is generated by a failed internal consistency check and should never occur. Cause: This error could be caused by a memory failure in the file server and could be attributable to either a hardware failure or poor power line conditioning. A corrupt operating system file might also cause this error. Solution: Reboot the file server. If this error or other Abend errors occur repeatedly, reinstall the operating system and then check the file server's memory and power line conditioning. Invalid memory size parameter.$ Occurs on: 86 only. Meaning: This error is generated by NetWare/86 when the operating system detects less than 384k of memory in the file server. This is a fatal error and will halt the server. Cause: The file server does not have enough memory. This error may also occur if there is a hardware failure in the server's 21 high memory. This will make the server to appear to have less memory than it really has. Solution: Install more memory in the file server so that it has at least 384k. If the server has over 384k of memory installed and continues to generate this error, check to see that the memory is good. Invalid number of FCBs requested from configuration information. Occurs on: 86 and 286. This is an Abend error. Meaning: This error occurs when a file server is booting up and as it sets up the File Control Block (FCB) storage area in memory, it finds that the number of FCBs to be requested is invalid. If the maximum number of files that can be open simultaneously is set to less than 20 or greater than 1000, then this error will be generated. This is an internal consistency check and the error should never occur. Cause: The most probable causes of this error condition is a bad copy of the operating system or a hardware failure in the disk, disk controller, Disk CoProcessor Board (DCB) or memory. Solution: Use the INSTALL utility to change the maximum number of files that can be open simultaneously to a value between 20 and 1000 and then reboot the file server. If this error still occurs, recopy the operating system back onto the hard disk and then reboot. If this or other mysterious errors continue to appear, check or replace the memory and/or the disk related hardware in the file server. Invalid op code interrupt. Occurs on: 286 only. This is an Abend error. Meaning: This is interrupt 6 in the 286 CPU and is generated by the CPU if it attempts to execute an undefined instruction opcode. This interrupt should never occur in NetWare. Cause: This error could be caused by a memory failure in the file server and could be attributable to either a hardware failure or poor power line conditioning. A corrupt operating system file might also cause this error. Solution: Reboot the file server. If this error or other interrupt errors occur repeatedly, reinstall the operating system and then check the file server's memory and power line conditioning. Invalid printer definition table. Run INSTALL to fix it. Occurs on: 86 and 286. This is an Abend error. Meaning: This error occurs on bootup of the file server if the printer definition table is corrupted or missing. This error is an internal consistency check and should not occur. 22 Cause: This error could be caused by a memory failure in the file server and could be attributable to either a hardware failure or poor power line conditioning. A corrupt operating system file might also cause this error. Solution: Run the INSTALL utility and set up the printer definitions again. Reboot the file server. If this error or other Abend errors occur repeatedly, reinstall the operating system and then check the file server's memory and power line conditioning. Invalid process id passed by interrupt procedure to kernel. Occurs on: 86 and 286. This is an Abend error. Meaning: An interrupt procedure passed a message to a process that was not defined in the multi-tasking kernel. This error should never occur in NetWare. Cause: This error could be caused by a memory failure in the file server and could be attributable to either a hardware failure or poor power line conditioning. A corrupt operating system file might also cause this error. Solution: Reboot the file server. If this error or other interrupt errors occur repeatedly, reinstall the operating system and then check the file server's memory and power line conditioning. Invalid semaphore number passed to kernel. Occurs on: 86 and 286. This is an Abend error. Meaning: This error is generated by the multi-tasking kernel and indicates that the system attempted to utilize a semaphore number that was invalid. Cause: This error is usually caused by a memory overflow in the file server. This error could also be caused by a memory failure in the file server and could be attributable to either a hardware failure or poor power line conditioning. A corrupt operating system file might also cause this error. Solution: To eliminate this problem, reconfigure the network to have less files open concurrently or add more memory to the file server. If this error or other Abend errors occur repeatedly, reinstall the operating system and then check the file server's memory and power line conditioning. Invalid task state interrupt. Occurs on: 286 only. This is an Abend error. Meaning: This is interrupt 10 in the 286 CPU and it is generated by the CPU if the new Task Switch Segment pointed to by the Task Gate is invalid during a task switch. This interrupt should never occur in NetWare. 23 Cause: This error could be caused by a memory failure in the file server and could be attributable to either a hardware failure or poor power line conditioning. A corrupt operating system file might also cause this error. Solution: Reboot the file server. If this error or other interrupt errors occur repeatedly, reinstall the operating system and then check the file server's memory and power line conditioning. LinkTree invalid file handle. Occurs on: 68, 86, and 286. This is an Abend error. Meaning: This error is generated in the file handling routines in the operating system if they encounter an invalid file handle. This error is the result of a failed internal consistency check and should never occur. Cause: This error could be caused by a memory failure in the file server and could be attributable to either a hardware failure or poor power line conditioning. A corrupt operating system file might also cause this error. Solution: Reboot the file server. If this error or other Abend errors occur repeatedly, reinstall the operating system and then check the file server's memory and power line conditioning. Maximum number of network files configured to be open is invalid. Occurs on: 68 only. This is an Abend error. Meaning: This error occurs when a file server is booting up and as it sets up the File Control Block (FCB) storage area in memory, it finds that the number of FCBs to be requested is invalid. If the maximum number of files that can be open simultaneously is less than 50 or greater than 4000, then this error will be generated. This error is the result of a failed internal consistency check and should never occur. Cause: The most probable causes of this error condition is a bad copy of the operating system or a hardware failure in the disk, disk controller, Disk CoProcessor Board (DCB) or memory. Solution: Use the SYSED utility to change the maximum number of files that can be open simultaneously to a value between 50 and 4000 and then reboot the file server. If this error still occurs, recopy the operating system back onto the hard disk and then reboot. If this or other mysterious errors continue to appear, check or replace the memory and/or the disk related hardware in the file server. Memory not available for star router tables. 24 Occurs on: 68 only. This is an Abend error. Meaning: This error message occurs when the file server does not have enough free dynamic memory to set up additional router tables. Cause: This error could be generated if the file server does not have enough free dynamic memory available to it. It could also be generated as a result of a failure in high memory, causing the file server to think that it has less memory installed. Solution: Run SYSED and increase the amount of dynamic memory available for use by the server. Test the memory to ensure that it is good. If necessary, add more memory to the file server. Message sent to invalid process in kernel. Occurs on: 86 and 286. This is an Abend error. Meaning: An internal message was sent to a process that does not exist in the multi-tasking kernel. Either the message is incorrect or the process is not activated and should be. This error should never occur in NetWare. Cause: This error could be caused by a memory failure in the file server and could be attributable to either a hardware failure or poor power line conditioning. A corrupt operating system file might also cause this error. Solution: Reboot the file server. If this error or other Abend errors occur repeatedly, reinstall the operating system and then check the file server's memory and power line conditioning. !!! MOUNT ERROR -- NO FREE DYNAMIC MEMORY !!! Occurs on: 68, 86, and 286. Meaning: File server could not mount a removable volume because there was no free dynamic memory to create a buffer for it. This is not a fatal error. Cause: File server does not have enough dynamic memory available to it. This error could also be generated by a failure in high memory which would cause the file server to think that it has less memory installed. Solution: If using a 68B server, run SYSED and increase the amount of dynamic memory available for use by the server. Test the memory to ensure that it is good. If necessary, add more memory to the file server. If using other than a 68B server, check that the memory is good. If no problems are found, add more memory to the file server. 25 NDetachFile invalid file handle. Occurs on: 86 and 286. This is an Abend error. Meaning: This error is generated in the file handling routines in the operating system if they encounter an invalid file handle. This error is the result of a failed internal consistency check and should never occur. Cause: This error could be caused by a memory failure in the file server and could be attributable to either a hardware failure or poor power line conditioning. A corrupt operating system file might also cause this error. Solution: Reboot the file server. If this error or other Abend errors occur repeatedly, reinstall the operating system and then check the file server's memory and power line conditioning. NetWare/286 requires running on a IBM PC/AT or equivalent. Occurs on: 286 only. Meaning: When NetWare/286 attempts to boot on a file server, it first checks the system's ROM BIOS to verify that the server is IBM PC/AT compatible. This error is displayed if it is not an IBM PC/AT or compatible. This is a fatal error and will halt the file server. Cause: This error is caused by not using an IBM PC/AT compatible system or if the ROM BIOS has been changed or has become defective. Solution: Use an IBM PC/AT or a Novell approved compatible file server. If the system is AT compatible, check the ROM BIOS to make sure that it is seated properly without any bent pins, that it is not corrupted, and that it is exactly IBM PC/AT compatible. Network Operating System software is not serialized for this hardware. Occurs on: 286 only. This is an Abend error. Meaning: The NetWare operating system serial number and the hardware serial number of the Novell key card or Disk Coprocessor Board (DCB) do not correspond to each other. Cause: The file server that NetWare is being installed on must have a key card or a DCB with the same serial number as the operating system. Solution: Ensure that the file server has a key card or a DCB installed in it that has the same serial number as the software that is being installed on it. If this error occurs on a 286 system containing a DCB but without a disk subsystem such that you are effectively using the DCB as a key card, the file server cannot read the serial number off of the DCB. This 26 error can be resolved by adding a disk subsystem or by the following modification: Jumper pins 23 and 25 together on the 50 pin connector of the Disk Coprocessor Board so that it appears to have a disk connected to it. The server will then be able to read the serial number correctly. Network Operating System software is not serialized for this network. Occurs on: 86 only. This is an Abend error. Meaning: The NetWare operating system serial number and the hardware serial number of the Novell key card do not correspond to each other. Cause: The file server that NetWare is being installed on must have a Novell key card with the same serial number as the operating system. Solution: Ensure that the file server has a key card installed in it that has the same serial number as the software that is being installed on it. NextRemoveFile invalid file handle. Occurs on: 68, 86, and 286. This is an Abend error. Meaning: This error is generated in the file handling routines in the operating system if they encounter an invalid file handle. This error is the result of a failed internal consistency check and should never occur. Cause: This error could be caused by a memory failure in the file server and could be attributable to either a hardware failure or poor power line conditioning. A corrupt operating system file might also cause this error. Solution: Reboot the file server. If this error or other Abend errors occur repeatedly, reinstall the operating system and then check the file server's memory and power line conditioning. NMI interrupt. Occurs on: 286 only. This is an Abend error. Meaning: The Non-Maskable Interrupt (NMI) is interrupt 2 in the 286 CPU. This error will occur if the 286 CPU receives a pulse on its NMI line but is unable to identify the source of it. This interrupt should never occur in NetWare. Cause: This error is most often caused by incorrectly configuring the cards in the file server such that I/O and/or memory conflicts occur. See Technical Bulletin #140. The I/O base address 340H cannot be used because the DCB uses it. A second DCB utilizes I/O base address 348H. A memory address of E000H or above cannot be used on any 286 machine. 27 Solution: Eliminate I/O and memory conflicts by reconfiguring the boards in the file server. See Technical Bulletin #140. No cache blocks available for allocation. Occurs on: 68 only. This is an Abend error. Meaning: File server could not allocate any cache blocks because there was no free dynamic memory. Cause: File server does not have enough dynamic memory available to it to support the amount of disk storage that is connected to the server. This error could also be generated as a result of a failure in high memory which would cause the file server to think that it has less memory installed. Solution: Test the memory to ensure that it is good. If necessary, add more memory to the file server. No Dirty Bits Set On Dirty Block. Occurs on: 68 only. This is an Abend error. Meaning: The process in the multi-tasking kernel that writes a modified (dirty) block in cache memory back onto the disk was notified that a dirty block existed but the process could not locate it. This error is the result of a failed internal consistency check and should never occur in NetWare. Cause: This error could be caused by a memory failure in the file server and could be attributable to either a hardware failure or poor power line conditioning. A corrupt operating system file might also cause this error. Solution: Reboot the file server. If this error or other Abend errors occur repeatedly, reinstall the operating system and then check the file server's memory and power line conditioning. !!! No Dynamic Work Space Available !!! Occurs on: 68, 86, and 286. Meaning: File server did not have enough unused memory space to use as buffer space for a printer. This is not a fatal error. Cause: File server does not have enough dynamic memory available to it. This error could also be generated as a result of a failure in high memory which would cause the file server to think that it has less memory installed. Solution: If using a 68B server, run SYSED and increase the amount of dynamic memory available for use by the server. Test the memory to ensure that it is good. If necessary, add more memory to the file server. If using other than a 68B server, check that the memory is 28 good. If no problems are found, add more memory to the file server. NO FREE SPACE TO VERIFY DIRECTORIES Occurs on: 68, 86, and 286. Meaning: This error occurs if the booting file server does not have enough available dynamic memory to compare the two copies of the directory on a volume to ensure that they are the same. This is not a fatal error and the server will continue to boot as normal except that there is no guarantee that the primary and secondary (mirror) directories match. Cause: File server does not have enough dynamic memory available to it. This error could also be generated as a result of a failure in high memory which would cause the file server to think that it has less memory installed. Solution: If using a 68B server, run SYSED and increase the amount of dynamic memory available for use by the server. Test the memory to ensure that it is good. If necessary, add more memory to the file server. If using other than a 68B server, check that the memory is good. If no problems are found, add more memory to the file server. NO FREE SPACE TO VERIFY FAT TABLES Occurs on: 68, 86, and 286. Meaning: This error occurs if the booting file server does not have enough available dynamic memory to compare the two copies of the FAT tables on a volume to ensure that they are the same. This is not a fatal error and the server will continue to boot as normal except that there is no guarantee that the primary and secondary (mirror) FAT tables match. Cause: File server does not have enough dynamic memory available to it. This error could also be generated as a result of a failure in high memory which would cause the file server to think that it has less memory installed. Solution: If using a 68B server, run SYSED and increase the amount of dynamic memory available for use by the server. Test the memory to ensure that it is good. If necessary, add more memory to the file server. If using other than a 68B server, check that the memory is good. If no problems are found, add more memory to the file server. No LAN Processor Boards are responding. Occurs on: 68 only. This is an Abend error. 29 Meaning: This error indicates that the 68B file server could not access any LAN processor boards as it was trying to boot up. Cause: This error could be caused by not having any LAN processor boards in the file server or if the server could not communicate with any LAN processor boards due to bad connections or bad boards. Solution: Ensure that the file server has at least one LAN processor board installed and that it is connected properly. Reseat the Lan processor boards and replace them if necessary. No message packets available in kernel. Occurs on: 86 and 286. This is an Abend error. Meaning: A process attempted to allocate a message packet in which to send a message to another process and there were no more available message packets in the multi-tasking kernel. This error should never occur in NetWare. Cause: This error could be caused by a memory failure in the file server and could be attributable to either a hardware failure or poor power line conditioning. A corrupt operating system file might also cause this error. Solution: Reboot the file server. If this error or other Abend errors occur repeatedly, reinstall the operating system and then check the file server's memory and power line conditioning. No PCBs available in kernel. Occurs on: 86 and 286. This is an Abend error. Meaning: The operating system attempted to start a new process in the multi-tasking kernel and could not because there were no more Process Control Blocks (PCBs) available. This error should never occur in NetWare. Cause: This error could be caused by a memory failure in the file server and could be attributable to either a hardware failure or poor power line conditioning. A corrupt operating system file might also cause this error. Solution: Reboot the file server. If this error or other Abend errors occur repeatedly, reinstall the operating system and then check the file server's memory and power line conditioning. NO PRE-FETCH FOR DIRECTORY WRITE REQUEST Occurs on: 68, 86, and 286. This is an Abend error. Meaning: A process in the multi-tasking kernel attempted to write a directory entry that had not been previously read. This 30 error should never occur in NetWare. This error results from a failed internal consistency check. Cause: This error could be caused by a memory failure in the file server and could be attributable to either a hardware failure or poor power line conditioning. A corrupt operating system file might also cause this error. Solution: Reboot the file server. If this error or other Abend errors occur repeatedly, reinstall the operating system and then check the file server's memory and power line conditioning. No semaphores available in kernel. Occurs on: 86 and 286. This is an Abend error. Meaning: A process attempted to allocate a semaphore in the multi-tasking kernel and there were none available. This error should never occur in NetWare. Cause: This error could be caused by a memory failure in the file server and could be attributable to either a hardware failure or poor power line conditioning. A corrupt operating system file might also cause this error. Solution: Reboot the file server. If this error or other Abend errors occur repeatedly, reinstall the operating system and then check the file server's memory and power line conditioning. Not enough memory available for cache blocks. Occurs on: 86 and 286. This is an Abend error. Meaning: The file server required more memory for caching than was available. 4 kilobytes of Cache memory is required for each volume directory block that is cached and a minimum of an additional 8 blocks of cache memory are required for file caching. Cause: The file server does not have enough dynamic memory available to it. This error could also be generated as a result of a failure in high memory which would cause the file server to think that it has less memory installed. Solution: First, check that the file server's memory is good. If no problems are found, then add more memory to the file server. Not enough memory available for locks work space. Occurs on: 86 and 286. This is an Abend error. Meaning: This error indicates that the file server required more memory for file locking work space than was available. The file server requires 2 kilobytes plus 100 bytes for each file that can be potentially opened on the server. The maximum 31 amount of memory that can be consumed by the NetWare File Locking System is 64 kilobytes. Cause: The file server does not have enough dynamic memory available to it. This error could also be generated as a result of a failure in high memory which would cause the file server to think that it has less memory installed. Solution: First, check that the file server's memory is good. If no problems are found, then add more memory to the file server. NOT ENOUGH MEMORY FOR DISK FAT TABLES. Occurs on: 86 and 286. This is an Abend error. Meaning: This error indicates that the file server required more memory to store the File Allocation Tables (FAT) for all mounted disk volumes than was available. NetWare requires 1 kilobyte of memory for each megabyte of mounted disk space for storing the FAT. Cause: The file server does not have enough dynamic memory available to it or the server is attempting to mount more disk space (volumes) than it can support with the memory that it has. This error could also be generated as a result of a failure in high memory which would cause the file server to think that it has less memory installed. Solution: Make sure that the file server has plenty of memory available for FAT storage in addition to the memory used by other portions of NetWare. Check that the file server's memory is good. If no problems are found, then add more memory to the file server. Not enough memory to cache volume nn. Occurs on: 68, 86, and 286. Meaning: This error indicates that the file server did not have enough available memory in which to cache the full directory of volume number "nn". To cache a directory, NetWare requires 4 kilobytes of memory for each directory block (32 bytes per directory entry) on the volume. This is not a fatal error and the file server will continue to run although it may be slower because the volume's directory is not cached. Cause: The file server does not have enough dynamic memory available to it or the server is attempting to mount more disk space (volumes) than it can support with the memory that it has. This error could also be generated as a result of a failure in high memory which would cause the file server to think that it has less memory installed. Solution: Make sure that the file server has plenty of memory available for directory caching in addition to the memory used by other portions of NetWare. Check that the file server's 32 memory is good. If no problems are found, then add more memory to the file server. NReAttachFile invalid file handle. Occurs on: 86 and 286. This is an Abend error. Meaning: This error is generated in the file handling routines in the operating system if they encounter an invalid file handle. This error is the result of a failed internal consistency check and should never occur. Cause: This error could be caused by a memory failure in the file server and could be attributable to either a hardware failure or poor power line conditioning. A corrupt operating system file might also cause this error. Solution: Reboot the file server. If this error or other Abend errors occur repeatedly, reinstall the operating system and then check the file server's memory and power line conditioning. NRemoveStationFile invalid file handle. Occurs on: 86 and 286. This is an Abend error. Meaning: This error is generated in the file handling routines in the operating system if they encounter an invalid file handle. This error is the result of a failed internal consistency check and should never occur. Cause: This error could be caused by a memory failure in the file server and could be attributable to either a hardware failure or poor power line conditioning. A corrupt operating system file might also cause this error. Solution: Reboot the file server. If this error or other Abend errors occur repeatedly, reinstall the operating system and then check the file server's memory and power line conditioning. Operating System / Server Mismatch. Occurs on: 286 only. This is an Abend error. Meaning: This error occurs if the operating system that is being used does not conform to the hardware that it is being used on. Cause: The standard release of NetWare/286 does not work on the 286A or the 286B file servers and will give this error. The 286A and 286B servers require NetWare/286a. Solution: Install NetWare/286a on the file server in place of standard NetWare/286. Both the 286A and 286B file servers will be able to use standard NetWare/286 in all future software versions. 33 Out of dynamic memory. Occurs on: 68 only. Meaning: This error message occurs when the file server does not have enough free dynamic memory. Cause: File server does not have enough dynamic memory available to it. This error could also be generated as a result of a failure in high memory which would cause the file server to think that it has less memory installed. Solution: Run SYSED and increase the amount of dynamic memory available for use by the server. Test the memory to ensure that it is good. If necessary, add more memory to the file server. Out of memory...too many FCBs requested. Occurs on: 86 and 286. This is an Abend error. Meaning: This error is generated when the file server does not have enough available memory in which to store the maximum number of File Control Blocks (FCBs) that the Network was configured for. The operating system requires 40 bytes of memory space for each file that is open simultaneously in the network. The maximum number of FCBs that you can have is 1000. Cause: The file server is configured to have more files open simultaneously than the amount of memory in the server can support. This error could also be generated as a result of a failure in high memory which would cause the file server to think that it has less memory installed. Solution: Check to make sure that the file server's memory is good and that it is all being used by the server. If possible, use the INSTALL utility to reduce the maximum number of files that can be open simultaneously. At the minimum, you should allow for 5 files per workstation attached to the network. If required, add more memory to the file server. Out of message packets in the Kernel Occurs on: 68 only. This is an Abend error. Meaning: A process attempted to allocate a message packet in which to send a message to another process and there were no more message packets available in the multi-tasking kernel. This error should never occur in NetWare. Cause: This error could be caused by a memory failure in the file server and could be attributable to either a hardware failure or poor power line conditioning. A corrupt operating system file might also cause this error. Solution: Reboot the file server. If this error or other Abend errors occur repeatedly, reinstall the operating system and 34 then check the file server's memory and power line conditioning. Over 64K segment requested by AllocSeg. Occurs on: 286 only. This is an Abend error. Meaning: The "AllocSeg" routine was called by a process to allocate a segment of memory for the 286 CPU that was larger than the 64 kilobyte limit that can be allocated. This error should never occur in NetWare. Cause: This error could be caused by a memory failure in the file server and could be attributable to either a hardware failure or poor power line conditioning. A corrupt operating system file might also cause this error. Solution: Reboot the file server. If this error or other Abend errors occur repeatedly, reinstall the operating system and then check the file server's memory and power line conditioning. Printer nn not in system. Occurs on: 68, 86, and 286. Meaning: This message displays on the server console if attempting to display the printer queue using the QUEUE command for a printer that is not installed on the system. "nn" is the printer number that is not on the system. This is not a fatal error. Solution: Check to make sure that printer "nn" should be on the system. If it should be, use the INSTALL program to put it on the system. Processor extension not supported. Occurs on: 286 only. This is an Abend error. Meaning: This is interrupt 7 in the 286 CPU and it is generated by the CPU if a processor extension, such as a 80287 numerical processor is not present when an instruction calls for it. This interrupt should never occur in NetWare. Cause: This error could be caused by a memory failure in the file server and could be attributable to either a hardware failure or poor power line conditioning. A corrupt operating system file might also cause this error. Solution: Reboot the file server. If this error or other interrupt errors occur repeatedly, reinstall the operating system and then check the file server's memory and power line conditioning. Processor extension overrun interrupt. Occurs on: 286 only. This is an Abend error. 35 Meaning: This is interrupt 9 in the 286 CPU and it is generated by the CPU if a processor extension, such as a 80287 numerical processor attempts to overrun the boundaries of a segment. This interrupt should never occur in NetWare. Cause: This error could be caused by a memory failure in the file server and could be attributable to either a hardware failure or poor power line conditioning. A corrupt operating system file might also cause this error. Solution: Reboot the file server. If this error or other interrupt errors occur repeatedly, reinstall the operating system and then check the file server's memory and power line conditioning. Removable Drive nn locked for use by station ss. Occurs on: 68, 86, and 286. Meaning: This error occurs when attempting to DISMOUNT removable disk number "nn" and station number "ss" still has the disk locked for use. This is not a fatal error. Solution: Have station number "ss" close all files that it may have open on the removable disk. Then attempt to DISMOUNT the removable disk again. RemoveFromSectorIndex called with invalid cache buffer. Occurs on: 86 and 286. This is an Abend error. Meaning: This error means that the NetWare operating system Cache Buffer Manager was told to remove a sector from the cache memory that was not stored there. This is an internal consistency check and the error should never occur. Cause: This error could be caused by a memory failure in the file server and could be attributable to either a hardware failure or poor power line conditioning. A corrupt operating system file might also cause this error. Solution: Reboot the file server. If this error or other Abend errors occur repeatedly, reinstall the operating system and then check the file server's memory and power line conditioning. Reply requested to non-existent message in kernel. Occurs on: 86 and 286. This is an Abend error. Meaning: This error is generated in the multi-tasking kernel when a process attempts to reply to a message that does not belong to it. This error is the result of a failed internal consistency check and should never occur. Cause: This error could be caused by a memory failure in the file server and could be attributable to either a hardware failure 36 or poor power line conditioning. A corrupt operating system file might also cause this error. Solution: Reboot the file server. If this error or other Abend errors occur repeatedly, reinstall the operating system and then check the file server's memory and power line conditioning. ResetBeingUsed call to cache block not being used. Occurs on: 68 only. This is an Abend error. Meaning: A cache block that had been in use was returned for reuse and the Cache Manager found that it had never been allocated. This error is the result of a failed internal consistency check and should never occur in NetWare. Cause: This error could be caused by a memory failure in the file server and could be attributable to either a hardware failure or poor power line conditioning. A corrupt operating system file might also cause this error. Solution: Reboot the file server. If this error or other Abend errors occur repeatedly, reinstall the operating system and then check the file server's memory and power line conditioning. ResetBeingUsed called on unused cache buffer. Occurs on: 86 and 286. This is an Abend error. Meaning: A cache block that had been in use was returned for reuse and the Cache Manager found that it had never been allocated. This error is the result of a failed internal consistency check and should never occur in NetWare. Cause: This error could be caused by a memory failure in the file server and could be attributable to either a hardware failure or poor power line conditioning. A corrupt operating system file might also cause this error. Solution: Reboot the file server. If this error or other Abend errors occur repeatedly, reinstall the operating system and then check the file server's memory and power line conditioning. Segment not present interrupt. Occurs on: 286 only. This is an Abend error. Meaning: This is interrupt 11 in the 286 CPU and it is generated by the CPU if it attempts to load a segment that is not defined in the segment table. This interrupt should never occur in NetWare. Cause: This error could be caused by a memory failure in the file server and could be attributable to either a hardware failure 37 or poor power line conditioning. A corrupt operating system file might also cause this error. Solution: Reboot the file server. If this error or other interrupt errors occur repeatedly, reinstall the operating system and then check the file server's memory and power line conditioning. Semaphore created with negative initial value in kernel. Occurs on: 86 and 286. This is an Abend error. Meaning: The multi-tasking kernel was asked to create a semaphore with a negative initial value. This error is the result of a failed internal consistency check and should never occur in NetWare. Cause: This error could be caused by a memory failure in the file server and could be attributable to either a hardware failure or poor power line conditioning. A corrupt operating system file might also cause this error. Solution: Reboot the file server. If this error or other Abend errors occur repeatedly, reinstall the operating system and then check the file server's memory and power line conditioning. SetBeingUsed already being used in cache. Occurs on: 86 and 286. This is an Abend error. Meaning: An available cache block that was to be set for use by the Cache Manager was already set as being in use. This error is the result of a failed internal consistency check and should never occur in NetWare. Cause: This error could be caused by a memory failure in the file server and could be attributable to either a hardware failure or poor power line conditioning. A corrupt operating system file might also cause this error. Solution: Reboot the file server. If this error or other Abend errors occur repeatedly, reinstall the operating system and then check the file server's memory and power line conditioning. SetBeingUsed call to cache block already set. Occurs on: 68 only. This is an Abend error. Meaning: An available cache block that was to be set for use by the Cache Manager was already set as being in use. This error is the result of a failed internal consistency check and should never occur in NetWare. Cause: This error could be caused by a memory failure in the file server and could be attributable to either a hardware failure 38 or poor power line conditioning. A corrupt operating system file might also cause this error. Solution: Reboot the file server. If this error or other Abend errors occur repeatedly, reinstall the operating system and then check the file server's memory and power line conditioning. SetBeingUsed out of semaphores. Occurs on: 68 only. This is an Abend error. Meaning: An available cache block was set for use by the Cache Manager but then could not be used because the multi-user kernel was out of available semaphores. This error should never occur in NetWare. Cause: This error could be caused by a memory failure in the file server and could be attributable to either a hardware failure or poor power line conditioning. A corrupt operating system file might also cause this error. Solution: Reboot the file server. If this error or other Abend errors occur repeatedly, reinstall the operating system and then check the file server's memory and power line conditioning. Single step interrupt. Occurs on: 286 only. This is an Abend error. Meaning: This is interrupt 1 in the 286 CPU and is generated by the CPU if placed in single step mode for debug purposes. When placed in single step mode, this interrupt is generated after each individual instruction is executed. This interrupt should never occur in NetWare. Cause: This error could be caused by a memory failure in the file server and could be attributable to either a hardware failure or poor power line conditioning. A corrupt operating system file might also cause this error. Solution: Reboot the file server. If this error or other interrupt errors occur repeatedly, reinstall the operating system and then check the file server's memory and power line conditioning. ***** SPOOLER ERROR ***** Occurs on: 68, 86, and 286. Meaning: This error PRINTS (on a printer, not on a server console) along with a banner page and a specific error message such as "Error attempting to open the file" or "File is empty." This is not a fatal error. Cause and Solution: See the specific error message that prints out on the banner page. 39 SPOOLER ERROR--PRINTER NOT FOUND Occurs on: 68, 86, and 286. This is an Abend error. Meaning: When the print spool software is first activated as a task within the internetwork, the file server performs an internal software check. This error indicates that the spooler process cannot find a corresponding software print driver. Cause: This does NOT have anything to do with printer hardware. This error comes from an internal software consistency check and should "never occur". Solution: If this error occurs, please contact Novell and inform them of the error, along with as much information about the circumstances that generated the error as you can get. Stack overflow detected by kernel. Occurs on: 86 and 286. This is an Abend error. Meaning: This error is generated by the multi-tasking kernel when it checks the memory stack used by a completed process and the process utilized too much stack memory. Cause: This error is usually generated by a memory overflow. It can also be caused by using an invalid device driver or a modified type table. Solution: Check to make sure that the proper device driver and/or type table is being used. To free up additional memory for stack use, run the INSTALL utility and reconfigure the network to have less files open concurrently. Stack segment overrun interrupt. Occurs on: 286 only. This is an Abend error. Meaning: This is interrupt 12 in the 286 CPU and it is generated by the CPU if the stack attempts to overrun a memory segment. Cause: This error could be caused by a memory failure in the file server and could be attributable to either a hardware failure or poor power line conditioning. A corrupt operating system file might also cause this error. Solution: Reboot the file server. If this error or other interrupt errors occur repeatedly, reinstall the operating system and then check the file server's memory and power line conditioning. StationRemoveFile invalid file handle. Occurs on: 68 only. This is an Abend error. Meaning: This error is generated in the file handling routines in the operating system if they encounter an invalid file handle. 40 This error is the result of a failed internal consistency check and should never occur. Cause: This error could be caused by a memory failure in the file server and could be attributable to either a hardware failure or poor power line conditioning. A corrupt operating system file might also cause this error. Solution: Reboot the file server. If this error or other Abend errors occur repeatedly, reinstall the operating system and then check the file server's memory and power line conditioning. SYSTEM ERRORS RECORDED IN SUPERVISOR FILE SYS$LOG.ERR Occurs on: 68, 86, and 286. Cause: This message is written to the server console after completing the power-up volume mounting and testing if the server finds the file SYS$LOG.ERR in the SYS:SYSTEM area. This is just a reminder to the server manager that significant errors have occurred that he should be aware of. This is not a fatal error and does not affect the operation of the file server. Solution: The manager should type the contents of the file SYS$LOG.ERR from a workstation to see what has happened. Action should be taken to correct any errors recorded, and then the file may be deleted. The Server has been Shut Down. Please Re-Boot to Restart. Occurs on: 68, 86, and 286. Meaning: This message is displayed on the server console after a DOWN command has successfully shut down the server and updated all cache information to the server volumes. Solution: Re-Boot the server to bring the network back up. Time out error configuring Disk CoProcessor. Occurs on: 286 only. This is an Abend error. Meaning: This error occurs when the SCSI device driver attempts to program a Disk CoProcessor Board (DCB) and the DCB does not return a completion code within a specified amount of time. This usually means that the DCB and the 286 processor are not communicating properly. Cause: This error is usually caused by a hardware problem or a setup problem with a drive, a controller, the interface cables, or the DCB. Solution: Check to make sure that the DCB's interrupt line (IRQ) settings do not conflict with other cards installed in the server. If two DCBs are installed in the file server, make sure that they are configured for separate channels. Check 41 all of the drives, controllers, disk interface cables and DCBs connected to the file server. Repair or replace any that are suspected of causing this error. The DCB has passed its internal diagnostics check if the software has gotten to this error message. Therefore, if the problem is on the DCB, it may not be easy to troubleshoot. Time out on the first Disk CoProcessor. Occurs on: 286 only. This is an Abend error. Meaning: This error occurs when the SCSI device driver attempts to access a channel one Disk CoProcessor Board (DCB) and the DCB does not respond within a specified amount of time. Cause: This error is usually caused by a hardware problem or a setup problem with a drive, a controller, the interface cables, or the DCB. Solution: Check to make sure that the DCB's interrupt line (IRQ) settings do not conflict with other cards installed in the server. If two DCBs are installed in the file server, make sure that they are configured for separate channels. Check all of the drives, controllers, disk interface cables and DCBs connected to the file server. Repair or replace any that are suspected of causing this error. If the software has gotten to this error message, the DCB has previously passed its internal diagnostics check. Therefore, if the problem is on the DCB, it may not be easy to troubleshoot. Time out on the second Disk CoProcessor. Occurs on: 286 only. This is an Abend error. Meaning: This error occurs when the SCSI device driver attempts to access a channel two Disk CoProcessor Board (DCB) and the DCB does not respond within a specified amount of time. Cause: This error is usually caused by a hardware problem or a setup problem with a drive, a controller, the interface cables, or the DCB. Solution: Check to make sure that the DCB's interrupt line (IRQ) settings do not conflict with other cards installed in the server. Make sure that a channel one DCB is installed in the file server along with the channel two DCB. Check all of the drives, controllers, disk interface cables and DCBs connected to the file server. Repair or replace any that are suspected of causing this error. If the software has gotten to this error message, the DCB has previously passed its internal diagnostics check. Therefore, if the problem is on the DCB, it may not be easy to troubleshoot. Timer Process out of Control Blocks. Occurs on: 68, 86, and 286. This is an Abend error. 42 Meaning: The timer process in the operating system has no more control blocks available in which to start and control another timed event. This error is the result of a failed internal consistency check and should never occur. Cause: This error could be caused by a memory failure in the file server and could be attributable to either a hardware failure or poor power line conditioning. A corrupt operating system file might also cause this error. Solution: Reboot the file server. If this error or other Abend errors occur repeatedly, reinstall the operating system and then check the file server's memory and power line conditioning. Too large a message request sent to kernel. Occurs on: 86 and 286. This is an Abend error. Meaning: This error occurs if a message request is sent to the multi-tasking kernel that is too long. This error is the result of a failed internal consistency check and should never occur. Cause: This error could be caused by a memory failure in the file server and could be attributable to either a hardware failure or poor power line conditioning. A corrupt operating system file might also cause this error. Solution: Reboot the file server. If this error or other Abend errors occur repeatedly, reinstall the operating system and then check the file server's memory and power line conditioning. TOO MANY VOLUMES ON SYSTEM Occurs on: 68, 86, and 286. This is an Abend error. Meaning: The file server attempted to mount more volumes than it could support. A file server can only support up to 32 volumes providing that it has the memory to cache the directories and FATs for each one. Cause: The file server was setup to mount more than 32 volumes. Solution: Use the INSTALL (86 & 286) or the SYSED (68) utility to reduce the number of volumes that the file server will mount to less than 32. If required, decrease the number of volumes by increasing the amount of disk space on each volume. It is strongly recommended that only one volume be assigned per physical disk. This allows the maximum number of physical disks possible to be used on the server. ??? UNKNOWN COMMAND ??? Occurs on: 68, 86, and 286. Cause: This error will display on the console of the file server if 43 the command being entered is not valid or if the spelling or syntax of the command is incorrect. This is not a fatal error. Solution: Enter the proper command with the appropriate spelling and syntax. Refer to the NetWare "Console Reference" manual for proper command usage and syntax. Unknown Removable Type Occurs on: 68, 86, and 286. Meaning: This error is generated when the file server attempts to MOUNT a removable drive that is undefined in the Removable Type Tables. This is not a fatal error. Cause: The removable drive being used is not defined in the version of NetWare that is being used. Solution: Use a removable drive that is recommended by Novell for use with NetWare. !!! VOLUME MOUNT ERROR -- NO FREE ALLOCATION SPACE !!! Occurs on: 68, 86, and 286. Meaning: File server could not mount a volume because there was no free memory to add the volume name to the Volume Name Table. This is not a fatal error. Cause: File server does not have enough dynamic memory available to it. This error could also be generated as a result of a failure in high memory which would cause the file server to think that it has less memory installed. Solution: If using a 68B server, run SYSED and increase the amount of dynamic memory available for use by the server. Test the memory to ensure that it is good. If necessary, add more memory to the file server. If using other than a 68B server, check that the memory is good. If no problems are found, add more memory to the file server. VOLUME VOLUMENAME MOUNTED. DISMOUNT VOLUME BEFORE REMOVING! Occurs on: 68, 86, and 286. Cause: Attempted to remove a mounted removable volume from the file server without first dismounting the volume. This is not a fatal error. Solution: Perform the DISMOUNT command on the file server monitor before removing the volume. *** WARNING *** ACTIVE FILES OPEN ON VOLUME. DISMOUNT? Occurs on: 68, 86, and 286. 44 Cause: This message occurs when attempting to DISMOUNT a removable volume and at least one work station connected to the file server still has open files on that volume. Solution: Answer "no" to the question and then have all of the workstations close all files on that volume before attempting to DISMOUNT the volume again. If a workstation has somehow "crashed", use the CLEAR STATION command on the station to close that workstation's files. Answering "yes" to "DISMOUNT?" will close all files such that their format will be intact and DISMOUNT the volume regardless. However, if the station was in the middle of a transaction or a file update, the files could be saved with incorrect data. *** WARNING *** ACTIVE FILES OPEN. HALT NETWORK? Occurs on: 68, 86, and 286. Cause: This message occurs when attempting to DOWN a file server and at least one work station connected to the server still has open files. Solution: Answer "no" to the question and then have the workstations all logout before attempting to DOWN the file server again. If a workstation has somehow "crashed", use the CLEAR STATION command on the station to close that workstation's files. Answering "yes" to "HALT NETWORK?" will close all files such that their format will be intact and DOWN the file server regardless. However, if the station was in the middle of a transaction or a file update, the files could be saved with incorrect data. WARNING -- CANNOT CREATE MESSAGE FILE!!! Occurs on: 68, 86, and 286. Meaning: This message is displayed if the server is unable to create the file where it stores messages being sent from one station to another via message pipes. This is not considered a fatal error, but station-to-station communication pipes will not work until the situation has been rectified and the server re- booted. Cause: This message is normally generated if there is insufficient work space on the SYS: volume or if there are insufficient free directory entries. Solution: Appropriate steps should be taken to free space on the SYS volume and/or create more free directory entries. The server should then be re-booted. WARNING -- CANNOT CREATE SPOOL FILE!!! Occurs on: 68, 86, and 286. Meaning: This message will be written to the server console if the server is unable to create the work file it needs for the print spool queues used for the various printers attached to the file 45 server. This is not a fatal error. However, if this error occurs, server print spooling will not work correctly until after some space has been made available on the SYS: volume and the server has been re-booted. Cause: This error is usually caused by not having enough available disk and directory space on volume SYS:. The file server needs a minimum of 2 to 3 MB of free workspace and 20 to 40 free directory entry slots in the SYS:SYSTEM area. Solution: Use the CHKVOL utility on a workstation attached to the server to check volume SYS:. Ensure that there is still disk space and directory space available for the server to work with. If the SYS: volume is full, then erase some of the files or move them to other volumes so that the server will have some workspace. If there is still space on the SYS: volume but there are no directory entries free, then run the INSTALL (86 or 286) or the SYSED (68) utility and increase the number of directory entries on the SYS: volume. *** WARNING *** Directory sector sss data mirror mismatch. Occurs on: 68, 86, and 286. Meaning: This message indicates that the primary and secondary (mirror) copies of directory sector "sss" do not match. This is not a fatal error. Cause: The most likely cause of this condition is that the server was suddenly stopped (by a power problem, hardware failure, etc.) between the time one sector was updated and the time its mirror was written. This error may also occur if the server is powered off without using the DOWN command at the console. Solution: This is not considered a fatal error. If a data mirror mismatch is detected, then the server will use the primary copy of the directory rather than the secondary copy. The primary copy is the one that is correct since it is written to disk first when a directory update occurs. The server does NOT automatically update the secondary copy to make it match the primary copy. Instead, both copies are left "as is". This condition will eventually clear itself if the volume is mounted and the server is run. While running, any update request to this directory sector will cause the mirrored sector to be updated to match the primary sector once again. *** WARNING *** DISK READ ERROR. CANCEL MOUNT? Occurs on: 68, 86, and 286. Meaning: This error is displayed if a disk read error occurs while reading in the directory of a volume during volume mount while bringing up a file server. Fixed volumes are always mounted automatically on system boot. Two copies of all directories are kept on each system volume. If a read failure 46 occurs on one copy, the server will automatically retry the read using the secondary (mirrored) directory. This error message will display only if a directory sector read failed on both directory copies. This is not a fatal error. Cause: This message might occur if the server was halted suddenly by a hardware or power failure or by bringing down the network without the DOWN command. Solution: The user may choose to cancel mounting of this volume (which would bring up the server running without the volume) or he may choose to allow the volume to continue mounting. In the latter case the server will continue as if the directory sector had contained no active file entries. This is not a fatal error, but it does signal significant problems in the directory area, and will probably be accompanied with many other error messages. The system manager should run VREPAIR on the volume to repair the bad sector before allowing the file server to be accessed. Warning: disk write error in file FILENAME.EXT Occurs on: 68, 86, and 286. Meaning: This error message will appear only on a WORKSTATION. This is the only operating system error message that does not appear on the file server console. This error indicates that the read-after-write verification of a hard disk write failed when the file server was attempting to write the file named "FILENAME.EXT" to disk. When ever the hard disk is written to, the data is immediately read back and verified to be the same as what was written. 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 is not a fatal error. This error will never occur if HOTFIX is activated on the disk. HOTFIX will automatically redirect the 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 could be caused by a location on the disk that has gone bad and can no longer retain data correctly. This error could also be caused by faulty electronics on the Disk CoProcessor Board (DCB), the disk controller or the hard disk itself. Solution: If the user is still in the application program when he receives this error on the workstation, he should attempt to save the file again under a different file name. The original file will be corrupt. The original file should not be erased because another disk write may try to utilize the same bad 47 area on the disk. Rename the file to a name that denotes 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. !!! WARNING !!! ERROR MOUNTING DRIVE xx OF CONTROLLER yy. Occurs on: 68, 86, and 286. Meaning: File server could not properly mount drive number "xx" attached to controller number "yy" because a disk error was encountered when it attempted to read the hard disk. This is not a fatal error. Cause: If the hard disk drive is new, it may not have been formatted. May also have been caused by a disk error or a problem with the controller. Solution: If the drive is new, COMPSURF it before attempting to bring up the server again. Otherwise, check out the disk and the controller. *** WARNING *** FAT Entry ssss marked bad in FILENAME.EXT Occurs on: 68, 86, and 286. Meaning: This error message is displayed when a file link list is linked to a physical sector which has been marked as bad in the FAT Table. "ssss" is the FAT entry number and "FILENAME.EXT" is the name of the affected file. The server automatically truncates the file so that it will not extend into the bad disk area. This truncation is done in the internal server tables and is NOT immediately written to disk. This is not a fatal error. Cause: The most probable cause for FAT Entry errors is a power or hardware failure, or by bringing down the network without the DOWN command. Solution: The VREPAIR utility may be used to verify and repair the problem. Do not use the outdated VOLFIX command. If a good backup of the file exists, or if the file is not important, then erasing and restoring the file will also fix the problem. *** WARNING *** FAT Entry ssss Marked Used with no File. Occurs on: 68, 86, and 286. Meaning: This error indicates that a FAT table entry shows that a disk block is allocated to a file but no file is linked to that disk block. "ssss" indicates the FAT entry number that is bad. The server displays this message and then automatically deallocates the block in its internal memory tables. The change will be updated back on to the disk when the block is re-allocated for another file. This is not a fatal error. 48 Cause: This message might occur if the server was halted suddenly by a hardware or power failure or by bringing down the network without the DOWN command. Solution: Since the server automatically deallocates the block and repairs itself, you can safely ignore this error message and it will eventually go away. *** WARNING *** FAT Entry ssss multiple allocation in FILENAME.EXT Occurs on: 68, 86, and 286. Meaning: The FAT table entries show that two different files claim to be using the same physical disk area. "ssss" indicates the FAT table entry number that is in question. "FILENAME.EXT" is the file name of the SECOND file that claims the disk space. Since a physical disk area can contain only one set of information, this error indicates a fatal file contamination for at least one and possibly both of the files involved. When this error is detected, the server automatically truncates the second file so that it will no longer claim the disputed physical disk area. This change is made in memory but is NOT immediately updated to disk. This error is not considered a fatal mount error. The server will continue to mount the volume even after this error is discovered. Cause: This error may be caused by a power or hardware failure, or by bringing down the network without the DOWN command. Solution: The system manager may use VREPAIR to find the names of all files that claim the same physical area. He may then examine the area in question to determine which file's data is actually written there. After repairing the disk, any files that may have been unrecoverable may be restored from the current backup. A second option is to simply delete the file named in this error message if it is not important or if a current backup copy exists to restore the file back from. *** WARNING *** FAT Entry ssss out of bounds in FILENAME.EXT Occurs on: 68, 86, and 286. Meaning: This error indicates that a file's FAT table link that points to the next physical area the file occupies corresponds to a data block beyond the end of the physical disk. "ssss" corresponds to the FAT table entry number and "FILENAME.EXT" is the name of the file that has been affected. The server reports this error and treats it as a file link error by truncating the file. This is not a fatal error and volume mount will continue after encountering it. Cause: The most probable cause for FAT Entry errors is a power 49 or hardware failure, or by bringing down the network without the DOWN command. Solution: Since the file indicated in the error message has already been truncated automatically by the file server, the best way to correct the situation is to erase the file and restore it from a backup. *** WARNING *** FAT Entry ssss out of order in FILENAME.EXT Occurs on: 68, 86, and 286. Meaning: This error message indicates that the physical disk entries in a file's FAT table map are out of consecutive order. "ssss" is the FAT entry number that has the problem and "FILENAME.EXT" is the file corresponding to that FAT entry. The server keeps track of where (logically) in a file each physical disk block belongs, both by linkage order and by allocation number. This is done so that operating systems like CP/M and CO/M-86, which allow files to be created with large "holes" in them, will work correctly on the server. If a FAT order error is discovered, the server truncates the file and reports the problem. A FAT order error is assumed by the server to be a symptom of a FAT link error, where one file has been accidentally linked into the disk allocation list of a different file. This is not a fatal error and volume mount continues after reporting the error. Cause: The most probable cause for FAT Entry errors is a power or hardware failure, or by bringing down the network without the DOWN command. Solution: The user can run VREPAIR to help determine the problem and possibly repair it. If all else fails, the user will need to erase the file and restore it from a backup. *** WARNING *** FAT Table sector sss data mirror mismatch. Occurs on: 68, 86, and 286. Meaning: This message indicates that the primary and secondary (mirror) copies of FAT sector "sss" do not match. This is not a fatal error. Cause: This message might occur if the server was previously halted suddenly by a hardware or power failure or by bringing down the network without the DOWN command between the time one FAT table sector was updated and the time its mirror was written. Solution: If a data mirror mismatch is detected, then the server will use the primary copy of the information rather than the secondary copy since the primary copy is updated to disk first when a disk FAT write occurs. The server does NOT automatically make the mirror copy match the primary copy but leaves both sectors as they are. If the server is brought 50 up and left running, then any request to write to this FAT sector will cause the mirror FAT sector to be automatically updated to match the primary FAT table copy. WARNING: FATAL DIR ERROR ON VOL VOLUMENAME DIR SECTOR sss. Occurs on: 68, 86, and 286. Meaning: This error is displayed if a disk read error occurs while reading the directory of a volume in the file server. "sss" is the directory sector number in which the error occurred. Two copies of all directories are kept on each system volume. If a read failure occurs on one copy, the server will automatically retry the read using the secondary (mirrored) directory. This error message will display only if a directory sector read failed on both directory copies. This error will not halt the file server. Cause: This message might occur if the server was halted suddenly by a hardware or power failure or by bringing down the network without the DOWN command. Solution: The file server will continue to operate as if the directory sector had contained no active file entries. This is not a fatal error, but it does signal significant problems in the directory area, and will probably be accompanied with many other error messages. The system manager should run VREPAIR on the volume to repair the bad sectors before allowing the file server to be accessed. WARNING: FATAL DIR ERROR ON VOL VOLUMENAME FAT SECTOR sss. Occurs on: 68, 86, and 286. Meaning: This error is displayed if a disk read error occurs while reading the File Allocation Table (FAT) a volume in the file server. "sss" is the sector number in which the error occurred. Two copies of all FATs are kept on each system volume. If a read failure occurs on the primary copy, the server will automatically retry the read using the secondary (mirrored) FAT. This error message will display only if a FAT sector read failed on both copies. Cause: This message might occur if the server was halted suddenly by a hardware or power failure or by bringing down the network without the DOWN command. Solution: The file server will continue to operate as if the FAT sector had contained no active file entries. This is not a fatal error, but it does signal significant problems in the directory and FAT areas, and will probably be accompanied with many other error messages. The system manager should run VREPAIR on the volume to repair the bad sectors before allowing the file server to be accessed. 51 WARNING: INSUFFICIENT MEMORY TO HASH ALL DIRECTORIES. Occurs on: 68 only. SEE equivalent error on NetWare/86 and 286 below: "WARNING: INSUFFICIENT MEMORY TO HASH DIRECTORIES." WARNING: INSUFFICIENT MEMORY TO HASH DIRECTORIES. Occurs on: 86 and 286. Meaning: This error indicates that the file server did not have enough available memory in which to hash all of the directories of the mounted volumes. To hash a directory, NetWare requires 1 kilobyte of memory for each directory block (8 bytes per directory entry) on the volume. This is not a fatal error and the file server will continue to run although it may be slower because the volume's directory is not hashed. Cause: The file server does not have enough dynamic memory available to it or the server is attempting to mount more disk space (volumes) than it can support with the memory that it has. This error could also be generated as a result of a failure in high memory which would cause the file server to think that it has less memory installed. Solution: Make sure that the file server has plenty of memory available for directory caching in addition to the memory used by other portions of NetWare. Check that the file server's memory is good. If no problems are found, then add more memory to the file server. WARNING! LAN n DEAD. Occurs on: 68, 86, and 286. Meaning: This error occurs if the file server detects that it can no longer access the LAN interface card configured as LAN number "n". This error message is only a warning and it does not halt the file server. Cause: This error could be caused by faulty connections between the LAN card and the file server or the network. It can also be caused by a hardware failure on the LAN interface card. Solution: Reseat the LAN interface card in the file server and check the connection to the rest of the network. Replace the LAN interface card if necessary. ** WARNING ** Sector sss DIR Table n Read Error on VOLUMENAME. Occurs on: 68, 86, and 286. Meaning: Disk read error while reading a sector from the volume's directory. "sss" indicates the specific sector number that is faulty. "n" indicates which directory is faulty: 0 = primary directory, 1 = backup (mirror) directory. "VOLUMENAME" indicates the name of the volume where the error occurred. This is not a fatal error. 52 Cause: This message might occur if the server was halted suddenly by a hardware or power failure or by bringing down the network without the DOWN command. Solution: If a directory sector is found to be bad, the server will automatically switch to using the mirrored backup copy of the faulty sector. The system manager will then be prompted to choose whether or not to abandon the volume mount. This is not a fatal error. The server will continue to function correctly using the backup (mirror) directory sector unless that sector is also bad. However, the directory mirror will no longer function for this sector until the read error is corrected. The disk error can be corrected by using the VREPAIR utility which is available on Netwire. Do not use VOLFIX! ** WARNING ** Sector sss FAT Table n Read Error on VOLUMENAME. Occurs on: 68, 86, and 286. Meaning: Disk read error while reading a sector from the FAT table. "sss" indicates the specific sector number that is faulty. "n" indicates which FAT table is faulty: 0 = primary FAT table, 1 = backup (mirror) FAT table. "VOLUMENAME" indicates the name of the volume where the error occurred. This is not a fatal error. Cause: This message might occur if the server was halted suddenly by a hardware or power failure or by bringing down the network without the DOWN command. Solution: If a FAT table sector is found to be bad, the server will automatically switch to using the secondary backup copy of the faulty sector. The system manager will then be prompted to choose whether or not to abandon the volume mount. This is not a fatal error. The server will continue to function correctly using the backup FAT table sector unless that sector also goes bad. However, the FAT table mirror will no longer function for this sector until the read error is corrected. The disk error can be corrected by using VREPAIR which is available on Netwire. Do not use VOLFIX! Write Error: dir = ssss file = FILENAME.EXT vol = VOLUMENAME Occurs on: 68, 86, and 286. Meaning: This error indicates that the read-after-write verification of a hard disk write failed. When ever the hard disk is written to, the data is immediately read back and verified to be the same as what was written. "ssss" is the directory number, "FILENAME.EXT" is the name of the file that the data was being written in, and "VOLUMENAME" is the name of the volume on which the error occurred. This error will never occur if HOTFIX is activated on the disk. HOTFIX will automatically redirect the bad sector to an alternate good 53 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 could be caused by a location on the disk that has gone bad and can no longer retain data correctly. This error could also be caused by faulty electronics on the Disk CoProcessor Board (DCB), the disk controller or the hard disk itself. Solution: Use the VREPAIR utility to diagnose and repair any problems with the disk. Verify that the disk related hardware is working properly. 54