FileStore and Stacking FileStore servers have a facility for obtaining a report of error status,
using *Report or *FSReport respectively. This document outlines the
error codes you may receive.
Taken from the Econet Design and Installation Guide, June 1993.
Code Description FS area
----------------------------------------------------------
01 Frame size is too big System
02 Function code is zero System
03 Unknown entry reason System
04 Size too big (vector fetch) System
05 Insufficient space (vector fetch) System
06 Size of store requested = 0 (vector fetch) System
07 Unable to fetch big buffer System
08 Not a digit (interrupt fetch) System
09 Unable to open receive control block System
[Econet interface not fitted or is faulty]
0A Read bitmap error System
[reformat and reinstall from backups]
0B Writing to sector zero System
[reformat and reinstall from backups]
...
11 Unknown machine System
12 Too many users logged on System
13 Restart called twice from User Manager util User Table Manager
[try switching off and restarting]
14 Object not a directory System
15 User not logged on
16 A computer on the network is station num. 0 User Table Manager
...
21 Cannot find Password file Authentication Manager
[the server will not start without a password
file - try using a floppy disc with blank]
22 User identifier not found
23 Password incorrect
24 Insufficient privilege
25 Bad password
[does not start with a letter, or has
control characters within]
26 User ID already exists
27 Password file syntax error Authentication Manager
28 Password file full
29 $.Passwords has wrong type (ie, directory) Authentication Manager
[see information for error code 21]
...
31 Restart called twice and is a system error Store Data Manager
32 SIN = 0, usually from a corrupted disc Store Data Manager
[should not happen with Level3 software 1.06
or later]
33 REF COUNT = &FF Store Data Manager
[should not happen with Level3 software 1.06
or later]
34 REF COUNT = &00 Store Data Manager
[should not happen with Level3 software 1.06
or later]
35 Size of file too big or size is zero Store Data Manager
[you are trying to create a file > 16Mb]
36 Invalid window address Store Data Manager
[Password file should be a full number of
sectors (256bytes, 512bytes etc). This error
indicates it is a different size, like 123
bytes.]
37 No free cache descriptors, too many items Store Data Manager
38 Window reference count > 0 Store Data Manager
39 Big buffer already in use Store Data Manager
3A Invalid buffer address Store Data Manager
3B As for error number 33
3C Store deadlock - cache full Store Data Manager
[restart server and reduce the number of
subdirectories in $, and number of users
logged in.]
3D Arithmetic Overflow in TSTGAP Store Data Manager
...
41 CDIR too big Directory Manager
[max. space is 19 sectors, 255 entries]
42 Broken directory Directory Manager
[Reinitialise the disc]
43 Object not found
44 Object not a directory
45 Insufficient access
46 Wrong arguments to Set/Read Object Attrib. Directory Manager
[see page 37 in Econet User Guide]
47 Directory entry locked
48 -
49 Object in use (it is already open)
4A Directory not empty
[delete contents before deleting directory]
4B Types do not match
4C No write access (object is Read Only)
4D Maximum directory size reached
4E Client asks for too many entries Directory Manager
[you may need to update your NFS/ANFS software]
4F Bad argument to Examine (similar to error 46) Directory Manager
50 -
51 Disc number not found
52 Disc space exhausted
53 SIN not for start of chain Map Manager
[you may need to reformat if not fixable]
54 Disc not a file server disc Map Manager
55 Both sector maps corrupt Map Manager
[Level 2 only, and highly unlikely!]
56 Illegal drive number Map Manager
57 Map sequence numbers differ by one Map Manager
[you may need to reinitialise the disc]
58 Illegal object size Map Manager
[user specified size cannot be zero]
59 New map doesn't fit in old space Map Manager
[Level 2 only - insert correct size disc]
5A Disc of same name already in use! Map Manager
5B No more space in Map descriptors Map Manager
5C Insufficient user free space Map Manager
[delete old files or use *SETFREE]
...
61 RNDMAN restart called twice Random Table Manager
[server incorrectly started - restart]
62 Invalid handle Random Table Manager
63 Handle quota exhausted Random Table Manager
64 Handle table full Random Table Manager
[each user can have up to 8 handles (Lib, CSD,
$ and five open files), and the server can
have up to 255 active handles]
65 Object not open
66 Copy not for file objects Random Table Manager
67 Random table full Random Table Manager
[ask user to log off, increase number of
logons allowed, then restart server]
68 File already open (interlock)
69 Object not a file
[you are trying to load a directory]
6A End of file on reading
6B Insufficient access on opening a file for
reading or writing
6C Attempt to point outside of current file
6D Invalid arguments to RDSTAR Random Table Manager
[resent in correct form]
6E Object not open for update
6F GETBYTE trying to read a byte after the last
byte in the file
70 -
71 Invalid number of sectors Disc Manager
[very low-level...reformat disc]
72 Store address overflow Disc Manager
73 Accessing beyond end of file Disc Manager
74 Invalid SIN Disc Manager
[very low-level, means map is being
overwritten]
75 Disc protected Disc Manager
76 Disc error Disc Manager
...
83 Too much data sent from client Command Processor
[should use SAVE procedures in NFS/ANFS]
84 Wait times out Command Processor
[resend, if fails again - check hardware]
85 Invalid function code Command Processor
[file server only allows codes 0 to 32]
86 Bad *Access string
89 Bad file title (mismatched quotes) Command Processor
8A File too big (over 16Mb) Command Processor
8B -
8C Bad privilege letter Command Processor
(use W, R or L)
8D Excess data in PUTBYTES Command Processor
[see error code 83]
8E Bad information argument Command Processor
8F Bad argument to RDAR (Read Obj. Info.) Command Processor
90 Bad date and time Command Processor
[change server date and time]
...
A0 Line jammed
[continuous information on one of the data
lines; faulty interface on another machine
or faulty termination]
A1 Net error
[usually a cable fault or two machines with
the same number]
A2 Not listening
[the machine that the command was directed to
is not connected or otherwise unavailable]
A3 No clock
[Econet interface could not find a valid clock
signal]
A4 Bad transmit block
A5 No reply
[unspecified failure whilst communicating with
another station]
...
AC Bad user name in Password file Authentication Manager
[restore from backup, or reformat disc]
AD -
AE User not logged on Authentication Manager
[Use *I Am to log on!]
AF Types don't match Directory Manager
[usually when trying to save a file over a
directory of the same name, or vice versa]
...
B0 Renaming across two discs Command Processor
[cannot be done - use copy instead]
B1 UserID already in Password file Authentication Manager
[use a different username]
B2 Password file full Authentication Manager
[v1.06 or greater will automatically extend
the file until a maximum size of 64K
(2097 users!) is reached]
B3 Maximum directory size reached Directory Manager
[split directories or delete old entries]
B4 Directory not empty Directory Manager
[delete contents then directory]
B5 Trying to load a directory Command Processor
B6 Disc error on read/write Map Manager
[try restarting; if this fails, reformat]
B7 Attempt to point outside file Random Table Manager
B8 User table full - too many users User Manager
[restart with more users allowed to log on,
or log an existing user off]
B9 Syntax error in password Authentication Manager
[log on method incorrectly expressed, try again]
BA Insufficient privilege Authentication Manager
[user does not have supervisor privilege]
BB Incorrect Password Authentication Manager
[try again]
BC UserID not found Authentication Manager
[username not recognised]
BD Insufficient access (as for error BA) Dir. Man. / Cmd Proc. / Rand. Table Man.
BE Object not a directory Directory Manager
BF The machine is not in the file server's user User Manager
table
[terminal ID not recognised - log on properly]
C0 Handle quota exhausted Random Table Manager
[log of some users or restart specifying more
users allowed to log on]
C1 File not open for update Random Table Manager
[read only, or opened using OPENIN]
C2 Object in use (ie: open) Directory Manager
[usually occurs when a user opens a file and
another user tries to delete it]
C3 Directory entry locked Directory Manager
[L attribute has been set, use *Access to unlock]
...
C6 Disc space exhausted Map Manager
[delete old files]
C7 Unrecoverable disc error Disc Manager
[reformat]
C8 Disc number not found Map Manager
[Level 2 only, if number incorrect or size
incorrect]
C9 Disc protected Disc Manager
[disc write protect tab is in the active
position]
...
CC Invalid seperator in file title Directory Manager
[illegal characters in title string]
...
CF Invalid access string Command Processor
...
D4 File write only Random Table Manager
[file has write-only attributes or was not
opened for read access]
D5 Object not found Directory Manager
D6 Disc name not found Map Manager
[when using SDISC, could not recognise the
inserted disc - verify it is okay]
...
DE Invalid handle or 'Channel' error Random Table Manager
[occurs if NFS/ANFS workspace is corrupt, or
if machine is switched off and on again with
user logged on, or (if on a BBC B) the value
of PAGE is changed to &E00]
DF End of file Random Table Manager
...
F5 Internal bit map cache error
F6 Cached bit map holds no free sectors
F7 -
F8 Write error (data read <> data written)
F9 Attempting to zero an illegal amount of disc
FA Multiple block allocate failed
FB -
FC Single block allocate failed
FD Bad file name, string, et cetera
FE Bad command
FF -
For most of the errors, a 'fix' is to shutdown the server, switch it off, then restart it.
However, some errors are more involved and may require you to format the affected disc(s).
Errors that may require a reformat say so. If you know the structure of a Level3 disc,
you may be able to low-level edit it and not need to reformat/reinstall.Errors in the Command Processor or errors without an "Area" entry are usually warnings that can normally be handled by the server in conjunction with the network software in the client's machine (for example: Bad Password).