Traditional File Services error codes include the following:
0x890A NLM INVALID CONNECTION
Source:
Traditional File Services
0x8901 INSUFFICIENT SPACE
Source:
Traditional File Services
Explanation:
The station does not have sufficient disk space.
Source:
Traditional File Services
Source:
Traditional File Services
Explanation:
The data to be passed back is too large for the buffer that was declared.
Source:
Traditional File Services
Explanation:
The service requested is not available on the selected volume.
Source:
Traditional File Services
Explanation:
A request for items failed because the items could not be found, for example, during a bindery request.
Source:
Traditional File Services
Explanation:
An attempt was made to convert a connection to temporary that was already temporary.
0x897B CONN ALREADY LOGGED IN
Source:
Traditional File Services
Explanation:
The connection is already logged in to eDirectory™ or NDS®.
0x897C CONN NOT AUTHENTICATED
Source:
Traditional File Services
Explanation:
The connection for a call has not been authenticated.
0x897D CONN NOT LOGGED IN
Source:
Traditional File Services
Explanation:
An attempt was made to log out of a connection that the user was not logged in to.
0x897E NCP BOUNDARY CHECK FAILED
Source:
Traditional File Services
Explanation:
The NCP subfunction size does not match the actual size of the data sent.
Source:
Traditional File Services
Explanation:
A timeout occurred before a file was locked.
Source:
Traditional File Services
Explanation:
An attempt was made to open or create a file that is already open.
Source:
Traditional File Services
Explanation:
An attempt was made to open or create a file that is already open.
Source:
Traditional File Services
Explanation:
No more file handles are available. The network file handle table is full.
Source:
Traditional File Services
Explanation:
An attempt was made to open a file without the Open right.
Source:
Traditional File Services
Explanation:
A hard disk input/output error occurred on a NetWare® volume; a bad sector has been encountered and could be fatal.
0x8984 FILE NO CREATE PRIV
Source:
Traditional File Services
Explanation:
An attempt was made to create a file without the Create right.
0x8985 FILE NO CREATE DEL PRIV
Source:
Traditional File Services
Explanation:
An attempt was made to create an already existing file without the Create/Delete rights.
0x8986 DIR TARGET INVALID
Source:
Traditional File Services
0x8986 FILE EXISTS READ ONLY
Source:
Traditional File Services
Explanation:
An attempt was made to create a file with the same name as an already existing file with Read Only status.
0x8987 FILE WILD CARDS IN NAME
Source:
Traditional File Services
Explanation:
An attempt was made to create a file using an ambiguous filename.
0x8988 FILE INVALID HANDLE
Source:
Traditional File Services
Explanation:
An attempt was made to close or perform I/O on a file with an invalid file handle (that is, trying to read from a file that has been closed).
Source:
Traditional File Services
Explanation:
An attempt was made to search a directory without Scan rights in that directory.
Source:
Traditional File Services
Explanation:
An attempt was made to delete a file without file deletion privileges in that file’s directory.
0x898B FILE NO RENAME PRIV
Source:
Traditional File Services
Explanation:
An attempt was made to rename a file without renaming privileges in that file’s directory.
Source:
Traditional File Services
Explanation:
An attempt was made to modify a file without attribute modification privileges in that file’s directory.
Source:
Traditional File Services
Explanation:
An attempt was made to delete, rename, or set file attributes using an ambiguous filename while some of the files specified by the filename are in use by another workstation.
Source:
Traditional File Services
Explanation:
An attempt was made to delete, rename, or set file attributes using a filename when the file or files specified by the filename are in use by another workstation.
0x898F FILE SOME READ ONLY
Source:
Traditional File Services
Explanation:
An attempt was made to delete, rename, or set file attributes using a filename when some of the files specified have Read Only status.
0x8990 FILE NONE READ ONLY
Source:
Traditional File Services
Explanation:
An attempt was made to delete, rename, or set file attributes using a filename when all the files specified have Read Only status.
0x8991 FILE SOME RENAMED EXIST
Source:
Traditional File Services
Explanation:
An attempt was made to rename files when one or more files matching the new filename specification already exist.
0x8992 FILE NONE RENAMED EXIST
Source:
Traditional File Services
Explanation:
An attempt was made to rename files when all the files matching the new filename specification already exist.
Source:
Traditional File Services
Explanation:
An attempt was made to read a file without Read privileges to that file.
0x8994 FILE NO WRITE PRIV
Source:
Traditional File Services
Explanation:
An attempt was made to write to a file without Write privileges to that file, or the specified file has Read Only status.
Source:
Traditional File Services
Explanation:
An attempt was made to write to a file without Write privileges to that file, or the specified file has Read Only status.
Source:
Traditional File Services
Explanation:
An attempt was made to read or write to a detached file.
0x8996 SERVER OUT OF MEMORY
Source:
Traditional File Services
Explanation:
An attempt was made to write to a file server that does not have enough free dynamic memory to process the specified request.
0x8997 DISK NO SPOOL SPACE
Source:
Traditional File Services
Explanation:
The network operating system has determined that the network disk does not have enough space left for spool files.
Source:
Traditional File Services
Explanation:
The network operating system has tried to access a volume but cannot find the volume in the system definition files.
Possible Cause:
The server that the user or application is trying to connect to has gone down.
Action:
Wait for the server to come up, establish a connection, then try the task again.
Source:
Traditional File Services
Explanation:
An attempt was made to write to a volume without available directory space.
0x899A VOL RENAMING ACROSS
Source:
Traditional File Services
Explanation:
An attempt was made to rename across volumes (rename a file and move the renamed file from its current volume into another volume).
Although the rename command may move the file between directories on the same volume, using rename to move a file between volumes is not allowed.
Source:
Traditional File Services
Explanation:
An attempt was made to use an invalid directory handle. This occurs if the network has been brought down and brought back up, without rebooting the workstation.
0x899C INSUFFICIENT RIGHTS INVALID PATH
Source:
Traditional File Services
Explanation:
An attempt was made to access a path with invalid rights to the path or with and invalid path name.
Source:
Traditional File Services
Explanation:
An attempt was made to access an invalid path.
Source:
Traditional File Services
Source:
Traditional File Services
Explanation:
No more directory handles are available; the directory handle table is full. Each user may have up to 255 directory handles.
Source:
Traditional File Services
Explanation:
An attempt was made to create a file using invalid characters within the name of the file.
Action:
Enter the filename again using valid characters.
Source:
Traditional File Services
Explanation:
An attempt was made to delete a directory that is being used by another workstation.
Source:
Traditional File Services
Explanation:
An attempt was made to delete a directory that contains files or other directories.
Source:
Traditional File Services
Explanation:
A nonrecoverable I/O error has occurred on the disk in the directory area. This error has occurred in both copies of the directory and is fatal.
Source:
Traditional File Services
Explanation:
An attempt was made to read a file where data is physically locked.
0x89A3 TRANSACTION RESTARTED
Source:
Traditional File Services
Explanation:
Transaction tracking was restarted.
0x89A3 TTS RANSACTION RESTARTED
Source:
Traditional File Services
Explanation:
Transaction tracking already has been restarted.
0x89A3 TTS TRANSACTION RESTARTED
Source:
Traditional File Services
0x89A4 DIR RENAME INVALID
Source:
Traditional File Services
Explanation:
An attempt was made to rename a directory with an invalid name.
0x89A5 FILE OPENCREAT MODE INVALID
Source:
Traditional File Services
Source:
Traditional File Services
Explanation:
An attempt was made to access a file that was already in use.
0x89A7 RESOURCE TAG INVALID
Source:
Traditional File Services
Explanation:
An invalid resource tag was encountered.
Source:
Traditional File Services
Explanation:
Access has been denied.
0x89BE DATA STREAM INVALID
Source:
Traditional File Services
Explanation:
Data streams are invalid.
0x89BF NAME SPACE INVALID
Source:
Traditional File Services
Explanation:
An invalid name space was used.
Source:
Traditional File Services
Explanation:
The user has no accounting privileges.
0x89C1 ACCTING NO BALANCE
Source:
Traditional File Services
Explanation:
Attempt was made to log in by a bindery object without an accounting balance, and accounting is enabled.
Source:
Traditional File Services
Explanation:
An attempt was made to log in to an account with no credit available.
0x89C3 ACCTING TOO MANY HOLDS
Source:
Traditional File Services
Source:
Traditional File Services
Explanation:
Accounting has been disabled.
Source:
Traditional File Services
Explanation:
An attempt was made to log in after the system had locked the account because of intruder detection.
Source:
Traditional File Services
Explanation:
An attempt was made to use console privileges without operator privileges.
Source:
Traditional File Services
Explanation:
A queue I/O error occurred.
Source:
Traditional File Services
Explanation:
No queues are defined.
Source:
Traditional File Services
Explanation:
No queue server has been specified.
Source:
Traditional File Services
Source:
Traditional File Services
Explanation:
The queue is full.
Source:
Traditional File Services
Explanation:
No jobs are in the queue.
0x89D6 PASSWORD UNENCRYPTED
Source:
Traditional File Services
Source:
Traditional File Services
Explanation:
The user does not have rights to this job in the queue.
0x89D7 PASSWORD NOT UNIQUE
Source:
Traditional File Services
Explanation:
An attempt was made to change a password to a previously used password when the unique requirement is specified for the account.
Source:
Traditional File Services
Explanation:
The queue is in service at this time.
0x89D8 PASSWORD TOO SHORT
Source:
Traditional File Services
Explanation:
An attempt was made to change a password to a password with fewer characters than the required minimum specified for the account.
Action:
Make sure the password entered has the minimum characters specified for the account.
Source:
Traditional File Services
Explanation:
The queue is not active at this time.
0x89D9 LOGIN MAX EXCEEDED
Source:
Traditional File Services
Explanation:
An attempt was made to log in using an account that has limits on the number of concurrent connections and that number has been reached.
Source:
Traditional File Services
Explanation:
An attempt was made to log in using an account that has limits on the number of concurrent connectins and that number has been reached.
Source:
Traditional File Services
Explanation:
The queue station is not a server.
0x89DA LOGIN UNAUTHORIZED TIME
Source:
Traditional File Services
Explanation:
An attempt was made to log in during an unauthorized time of day specified for the account.
Source:
Traditional File Services
Explanation:
The queue has been halted.
0x89DB LOGIN UNAUTHORIZED STATION
Source:
Traditional File Services
Explanation:
An attempt was made to log into an unauthorized station.
Source:
Traditional File Services
Explanation:
This queue is already attached to the maximum number of servers allowed.
Source:
Traditional File Services
Explanation:
An attempt was made to log in using an account that has expired or has been disabled by the supervisor.
Source:
Traditional File Services
Explanation:
An attempt was made to log in using an account password that has expired, and all grace logins have also expired.
Source:
Traditional File Services
Explanation:
An attempt was made to log in using an expired account password, but the login was allowed because the account had a grace login.
0x89E0 LOGIN NO CONN AVAIL
Source:
Traditional File Services
Explanation:
No login connection is available.
Source:
Traditional File Services
Explanation:
No more users exists.
0x89E8 BIND NOT ITEM PROP
Source:
Traditional File Services
Explanation:
An attempt was made to use an item not associated with this property group or an item that has been deleted from this group.
0x89E8 BIND WRITE TO GROUP PROP
Source:
Traditional File Services
Explanation:
An attempt was made to use an item not associated with this property group or an item that has been deleted from this group.
0x89E9 BIND MEMBER ALREADY EXISTS
Source:
Traditional File Services
Explanation:
An attempt was made to add an object to a group property that already exists.
0x89EA BIND NO SUCH MEMBER
Source:
Traditional File Services
Explanation:
An attempt was made to use an object that is not a member of the defined group property.
0x89EB BIND NOT GROUP PROP
Source:
Traditional File Services
Explanation:
An attempt was made to use a nongroup property.
0x89EC BIND NO SUCH SEGMENT
Source:
Traditional File Services
Explanation:
An attempt was made to use a nonexisting segment. Note that segments must be written sequentially when a property is first created, but may be read and written in any order after they already exist.
0x89ED BIND PROP ALREADY EXISTS
Source:
Traditional File Services
Explanation:
An attempt was made to create a property that already exists.
0x89EE BIND OBJ ALREADY EXISTS
Source:
Traditional File Services
Explanation:
An attempt was made to create an object that already exists.
Source:
Traditional File Services
Explanation:
A request was made with an object or property name containing illegal characters. Illegal characters in names are control characters, the comma, colon, semicolon, slash, backslash, question mark, asterisk, and tilde.
Action:
Enter requests using valid characters.
0x89F0 BIND WILDCARD INVALID
Source:
Traditional File Services
Explanation:
An attempt was made to use a wildcard character or wild object type in a call where wildcards are not allowed.
0x89F1 BIND SECURITY INVALID
Source:
Traditional File Services
Explanation:
An attempt was made to assign a security level of a bindery object or property to be higher than the user’s security level. This would make the object or property inaccessible to the user.
0x89F2 BIND OBJ NO READ PRIV
Source:
Traditional File Services
Explanation:
An attempt to access object information or scan the object’s properties was made by a station without the necessary security to access this information or object’s properties.
0x89F3 BIND OBJ NO RENAME PRIV
Source:
Traditional File Services
Explanation:
An attempt was made to rename an object without the necessary rights. Only the Supervisor can rename objects. Note that if the user does not have the rights to see that the object exists, then NCP_No_Such_Object is returned.
0x89F4 BIND OBJ NO DELETE PRIV
Source:
Traditional File Services
Explanation:
An attempt was made to delete an object without the necessary rights to delete the object. Only the Supervisor can delete objects. Note that if the user does not have the right to see that the object exists, then NCP_No_Such_Object is returned.
0x89F5 BIND OBJ NO CREATE PRIV
Source:
Traditional File Services
Explanation:
An attempt was made to create an object without the necessary security to create or change an object. Only Supervisors are allowed to create objects.
0x89F6 BIND PROP NO DELETE PRIV
Source:
Traditional File Services
Explanation:
An attempt was made to delete a property without the necessary property rights. Note that if the user does not have the proper rights to view the property, then NCP_No_Such_Property is returned.
0x89F7 BIND PROP NO CREATE PRIV
Source:
Traditional File Services
Explanation:
An attempt was made to create a property without the necessary property rights for the object.
0x89F8 BIND PROP NO WRITE PRIV
Source:
Traditional File Services
0x89F9 BIND PROP NO READ PRIV
Source:
Traditional File Services
Explanation:
An attempt was made to read without the necessary Read rights to access the property data.
0x89F9 NO FREE CONN SLOTS
Source:
Traditional File Services
Explanation:
No connection slots are available.
0x89FA NO MORE SERVER SLOTS
Source:
Traditional File Services
Explanation:
No server slots are available.
Source:
Traditional File Services
Explanation:
An attempt was made to use an unknown path.
Source:
File Services
Explanation:
An attempt was made to use a property that does not exist for the specified object.
Source:
Traditional File Services
0x89FB PARAMETERS INVALID
Source:
Traditional File Services
Explanation:
An attempt was made to use an invalid parameter (drive number, path, or flag value) during a set drive path call.
Source:
Traditional File Services
Explanation:
An attempt was made to use an object that could not be found in the context specified.
0x89FC INET PACKET REQ CANCELED
Source:
Traditional File Services
Source:
Traditional File Services
Explanation:
An attempt was made to use a full message queue.
Source:
Traditional File Services
Explanation:
An attempt was made to attach to a server using an invalid server name.
Source:
Traditional File Services
Explanation:
An attempt was made to use a bad (undefined, unavailable, etc.) station number.
Source:
Traditional File Services
0x89FD PACKET LEN INVALID
Source:
Traditional File Services
Explanation:
The requesting packet did not have a 30 byte packet header as the first fragment, or its total length exceeded 576 characters.
Source:
Traditional File Services
Explanation:
An unknown request was attempted.
Source:
Traditional File Services
Explanation:
An attempt was made to use a server with a locked bindery.
Source:
Traditional File Services
Explanation:
An attempt was made to use a locked directory.
0x89FE LOGIN DISABLED BY SUPER
Source:
Traditional File Services
Explanation:
An attempt was made to log in when the supervisor has disabled logins from the console or the bindery was locked.
0x89FE PACKET NOT DELIVERABLE
Source:
Traditional File Services
Explanation:
A packet cannot be delivered for any of the following possible reasons:
-
The destination node is on another network, and no router could be found with a path to the destination network.
-
The destination node address is on the local network, and the hardware detects that the destination node address is nonexistent or inactive.
-
The destination node is the same machine as the source node, and no pending listen request is on the destination socket number.
-
The destination socket number is not open.
0x89FE SEM INVALID NAME LEN
Source:
Traditional File Services
Explanation:
An attempt was made to open a semaphore with an invalid semaphore name length. Semaphores use strings that are from 1 to 127 bytes long.
Source:
Traditional File Services
Source:
Traditional File Services
Explanation:
An error occurred while spooling the directory.
Source:
Traditional File Services
Explanation:
A failure occurred that was caused by the timeout limit expiring before the request was fulfilled.
Source:
Traditional File Services
Explanation:
An operation tried to use an unknown trustee.
Source:
Traditional File Services
Explanation:
The program tried to use an invalid offset value during physical locking calls.
Source:
Traditional File Services
Explanation:
An attempt was made to use a bad (undefined, unavailable, etc.) printer.
Source:
Traditional File Services
Explanation:
An attempt was made to use a drive with an invalid number.
Source:
Traditional File Services
Explanation:
A failure has occurred.
Source:
Traditional File Services
Explanation:
An error occurred closing the file.
Source:
Traditional File Services
Explanation:
An attempt was made to use a file with a bad (undefined, unavailable, etc.) name or extension.
Source:
Traditional File Services
Explanation:
An attempt was made to use a file with a bad (undefined, unavailable, etc.) name or extension.
Source:
Traditional File Services
Explanation:
A hardware failure occurred.
Source:
Traditional File Services
Explanation:
The program tried to write beyond the end of the file or disk.
Source:
Traditional File Services
Explanation:
An attempt was made to use a locked file.
0x89FF NO FILES FOUND ERROR
Source:
Traditional File Services
Explanation:
No files were found that matched the search specification.
0x89FF NO OBJ OR BAD PASSWORD
Source:
Traditional File Services
Explanation:
An attempt was made to use an unfound object, or attempt to use a bad (undefined, unavailable, etc.) password. On a login call, this indicates the password was correct, but it has expired and all grace logins have been used up. On a change password call, it indicates that the old password given was correct, but the account is not allowed to change the password (typical of the guest account).
0x89FF NO RESPONSE FROM SERVER
Source:
Traditional File Services
0x89FF PATH NOT LOCATABLE
Source:
Traditional File Services
Explanation:
The program tried to find an unknown path during a "get full path" call.
Source:
Traditional File Services
Explanation:
An attempt was made to use a queue with 99 entries in it. (99 is the maximum number of entries that can be placed in each print queue.)
0x89FF REQ NOT OUTSTANDING
Source:
Traditional File Services
Explanation:
No NCP requests are outstanding.
0x89FF SEM INVALID HANDLE
Source:
Traditional File Services
Explanation:
The program tried to examine, wait for, or signal a semaphore with an invalid semaphore handle. The semaphore handle is obtained through the "open a semaphore" call.
0x89FF SEM INVALID INIT VAL
Source:
Traditional File Services
Explanation:
The program tried to open a semaphore with an invalid semaphore value. The semaphore value must be positive, and it must be initialized to a value from 0 to 127.
0x89FF SOCKET ALREADY OPEN
Source:
Traditional File Services
Explanation:
The program tried to open a socket whose specified socket number is already open.