Error codes

Error codes

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 function entry reason code	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 Either no Econet interface is installed, or the interface is faulty.	System
0A	Read bitmap error The disc contains a 'bitmap' marking where directories start, this is corrupted. You will probably need to reformat and reinstall from your backups.	System
0B	Writing to sector zero Usually caused by disc corruption. You will probably need to reformat and reinstall from your backups.	System
...
11	Unknown machine	System
12	Too many users logged on	System
13	Restart called twice from User Manager util Restart from 'cold' by switching off and back on again.	User Table Manager
14	Object not a directory	System
15	User not logged on	?
16	A computer on the network is station number 0 This is not valid, find the computer and reconfigure it to have a station number in the range 1-254 that doesn't conflict with another station.	User Table Manager
...
21	Cannot find Password file The server cannot start without the "$.Passwords" file. Recovering a harddisc which has had its password file deleted can be tricky. Perhaps easier is to start up in maintenance mode (flap open) and format a floppy disc - which will put in place an empty password file so the server will be able to start, though I do not know if you will be able to access the harddisc without logging in, which won't be possible if there is no password file... see the problem?	Authentication Manager
22	User identifier not found	?
23	Password incorrect	?
24	Insufficient privilege	?
25	Bad password Password does not start with a letter, or has control characters within.	?
26	User ID already exists	?
27	Password file syntax error	Auth. Mgr
28	Password file full	?
29	$.Passwords has wrong type (ie, directory). The server cannot start without a password file. In this case, the object exists, but it is a directory! Refer to the notes for error 21.	Authentication Manager
...
31	Restart called twice and is a system error	Str Dat Mgr
32	SIN = 0, usually from a corrupted disc [should not occur with Level3 v1.06 or later]	Store Data Manager
33	REF COUNT = &FF [should not occur with Level3 v1.06 or later]	Store Data Manager
34	REF COUNT = &00 [should not occur with Level3 v1.06 or later]	Store Data Manager
35	Size of file too big or size is zero You are trying to create a file larger then 16Mb.	Store Data Manager
36	Invalid window address The password file should be a full number of sectors (256 bytes, 512 bytes etc). This error indicates it is a different size, like 123 bytes; usually caused by crappy user editor software (or really amateur hacking) that writes back the user data but omits the padding.	Str Dat Mgr
37	No free cache descriptors, too many items	Str Dat Mgr
38	Window reference count > 0	Str Dat Mgr
39	Big buffer already in use	Str Dat Mgr
3A	Invalid buffer address	Str Dat Mgr
3B	As for error number 33.
3C	Store deadlock - cache full Restart the server and reduce the number of subdirectories in $, and number of users that can be logged in at any one time. Essentially, there is not enough memory to keep track of 'x' users and 'y' items in the disc root directory.	Store Data Manager
3D	Arithmetic Overflow in TSTGAP	Str Dat Mgr
...
41	CDIR too big The maximum directory space is 19 sectors, which can hold up to 255 entries.	Directory Manager
42	Broken directory This is usually caused by a loss of power while writing to the disc; you may have experienced similar with your RISC OS machine? The easy fix is to reinitialise the disc and restore from backups. The harder fix is to directly edit the disc structure - which is not exactly pleasant!	Directory Manager
43	Object not found	?
44	Object not a directory	?
45	Insufficient access	?
46	Wrong arguments to Set/Read Object Attrib.	Dir Mgr
47	Directory entry locked	?
48	-
49	Object in use (it is already open)	?
4A	Directory not empty Delete contents of directory, then delete the 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 When cataloguing a directory, the (A)NFS requests information on the directory, which the server duly sends, only there turn out to be more requests than the client can fit into its buffer. It is possible that you may need to update your (A)NFS software.	Directory Manager
4F	Bad argument to Examine	Dir Mgr
50	-
51	Disc number not found	?
52	Disc space exhausted	?
53	SIN not for start of chain The System Internal Number for a file points to a location on the disc that is not the start of the file or directory. You may be able to edit the disc. Failing this, you will probably need to reformat and reinstall.	Map Manager
54	Disc not a file server disc Could be a corrupted disc. Mostl likely to be an ADFS or MS-DOS disc inserted by mistake.	Map Manager
55	Both sector maps corrupt [Level2 only, and quite unlikely]	Map Manager
56	Illegal drive number	Map Mgr
57	Map sequence numbers differ by > 1 This should not occur unless a corruption occurs part way through updating the sector map. You may need to reinitialise the disc and restore from backups.	Map Manager
58	Illegal object size (i.e. zero)	Map Mgr
59	New map doesn't fit in old space [Level 2 only - insert correct discs before starting the server]	Map Manager
5A	Disc of same name already in use! You can't have discs with the same name - how will the server (or the clients) tell them apart?	Map Manager
5B	No more space in Map descriptors	Map Mgr
5C	Insufficient user free space The server offers accounting to stop users filling up the disc to the detriment of other users. The user must either delete old files, or the administrator must use the *SetFree command to allow more space for the user.	Map Manager
...
61	RNDMAN restart called twice	Map Mgr
62	Invalid handle	RndTab Mgr
63	Handle quota exhausted	RndTab Mgr
64	Handle table full The server can cope with a maximum of 255 'handles', which keep track of users and what they are doing. Each currently logged on user can have up to eight handles, which are usually assigned as 'library', 'current directory', 'root directory', and up to five open files.	Random Table Manager
65	Object not open	RndTab Mgr
66	Copy not for file objects	RndTab Mgr
67	Random table full Ask all users to log off, then increase the number of users that may log in concurrently.	Random Table Manager
68	File already open (interlock)	RndTab Mgr
69	Object not a file You are trying to load a filename which is actually a directory.	Random Table Manager
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	RndTab Mgr
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 Very low level problem - reformat the disc and reinstall from backups.	Disc Manager
72	Store address overflow	Disc Mgr
73	Accessing beyond end of file	Disc Mgr
74	Invalid SIN (protected area) Very low level problem, map is being overwritten - reformat and reinstall.	Disc Manager
75	Disc protected	Disc Mgr
76	Disc error (faulty sector, etc)	Disc Mgr
...
83	Too much data sent from client	CmdProc
84	Wait times out Receiver waiting for data not sent. Try again. If fault persists, check hardware.	Command Processor
85	Invalid function code The server only supports function codes 0 to 32. Most likely you are trying to use Level 4 specific software with the older server?	Command Processor
86	Bad *Access string	CmdProc
...
89	Bad file title (mismatched quotes)	CmdProc
8A	File too big (over 16Mb) The usual cause is bad maths when calculating PTR# values. You (or user) should delete the affected file and try again after checking their source code thoroughly.	Command Processor
8B	-
8C	Bad privilege letter (not 'W', 'R', or 'L')	CmdProc
8D	Excess data in PUTBYTES	CmdProc
8E	Bad information argument	CmdProc
8F	Bad argument to RDAR (Read Obj. Info.)	CmdProc
90	Bad date and time Ensure the server's date and time settings are correct.	Command Processor
...
A0	Line jammed There is continuous information on the data lines; either the network is severely laden or (more usually) there is a faulty interface or terminator.	?
A1	Net error This is usually caused by two machines having the same station number, or by a cabling fault.	?
A2	Not listening The machine that is being contacted did not respond. Usual case (station) is that it has crashed, or is switched off. Usual case (server) is that it is in management mode and is doing something to which it cannot respond right now (i.e. formatting a floppy disc).	?
A3	No clock No clock signal could be detected. Is the station plugged into the network?	?
A4	Bad transmit block	?
A5	No reply Unspecified failure whilst communicating with another station - check what the error message is on the other station.	?
...
AC	Bad user name in Password file Restore password file from backup. If you have none, you may need to reformat the disc.	Authentication Manager
AD	-
AE	User not logged on	Auth Man
AF	Types don't match This usually when trying to save a file over a directory of the same name, or vice versa.	Directory Manager
B0	Renaming across two discs This cannot be done - use copy instead.	Command Processor
B1	UserID already in Password file	Auth Mgr
B2	Password file full Server v1.06 or greater will automatically extend the file until a maximum size of 64K (or 2097 users!) is reached.	Authentication Manager
B3	Maximum directory size reached Directories are 19 entries (2 sectors) by default, and will automatically extend until 255 entries have been reached. Delete some old entries. You may wish, afterwards, to create some subdirectories.	Directory Manager
B4	Directory not empty	Dir Mgr
B5	Trying to load a directory	Cmd Proc
B6	Disc error on read/write Possible disc corruption. Restart the server and verify the disc. If it fails verification, it will need to be reformatted.	Map Manager
B7	Attempt to point outside file	RndTab Mgr
B8	User table full - too many users Restart with more users allowed to log on, or log off some existing users. If your habit is to 'restart' the client terminals by using a big switch on the wall, don't!. Ensure everybody has logged off before committing the heinous act of power cycling...	User Manager
B9	Syntax error in password	Auth Mgr
BA	Insufficient privilege	Auth Mgr
BB	Incorrect Password	Auth Mgr
BC	UserID not found	Auth Mgr
BD	Insufficient access	Various
BE	Object not a directory	Dir Mgr
BF	The machine is not in the file server's user table Log on properly...	User Manager
C0	Handle quota exhausted	RndTab Mgr
C1	File not open for update	RndTab Mgr
C2	Object in use (i.e. file open)	Dir Mgr
C3	Directory entry locked	Dir Mgr
...
C6	Disc space exhausted (disc full)	Map Manager
C7	Unrecoverable disc error You'll need to do the old reformat-and-reinstall routine...	Disc Manager
C8	Disc number not found [Level 2 only, if number incorrect or size incorrect]	Map Manager
C9	Disc protected	Disc Mgr
...
CC	Invalid separator in file title	Dir Mgr
...
CF	Invalid access string	Cmd Proc
...
D4	File write only	RndTab Mgr
D5	Object not found	Dir Mgr
D6	Disc name not found When using SDISC, could not recognise the inserted disc - verify it is okay.	Map Manager
...
DE	Invalid handle or 'Channel' error This 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.	Random Table Manager
DF	End of file	RndTab Mgr
...
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	-

Observations

A number of other errors are fairly generic user errors - for example "File write only" if the user attempts to OPENIN a file that does not have read access.

For many of the more critical errors, the cause is often a power glitch (or screwing around in the server's memory with Prot off), and the suggested 'fix' is to shutdown the server, switch it off, and then restart it.

Some errors are more important and more involved, and may require you to format the affected disc(s). Errors that may require a reformat generally say so. If you know the structure of the disc, you may be able to low-level edit it and not need to reformat/reinstall.
While it may seem that there are a depressing number of errors that could require a reformat, I feel I should point out that these sorts of errors affect most disc systems - a power loss while writing to disc can cause all sorts of havoc. Why do you think versions of Win32 automatically kick-start "Scandisk" when they detect the system was not correctly shut down... a problem mitigated considerably by modern discs having considerable write caching.

Note that there are some obvious potential incompatibilities. For example, if the user file can hold a maximum of two thousand potential users, and the root directory can hold up to 255 entries - that leaves one and three-quarter thousand users unable to have a URD...

Finally, there also appears to be some duplication of errors. For example "Disc protected is error &75 and error &C9.