Copyright: (c) Copyright 1994-1996, Novell, Inc.


-001  FFFFFFFFF  INSUFFICIENT SPACE

Explanation

The station does not have sufficient disk space.

Action

See Reporting Error Code Problems to Novell.


-119  FFFFFFF89  BUFFER TOO SMALL

Explanation

The data to be passed back is too large for the buffer that was declared.

Action

See Reporting Error Code Problems to Novell.


-120  FFFFFFF88  VOLUME FLAG NOT SET

Explanation

The volume flag has not been set.

Action

See Reporting Error Code Problems to Novell.


-121  FFFFFFF87  NO ITEMS FOUND

Explanation

A request for items failed because the items could not be found, for example, during a bindery request.

Action

See Reporting Error Code Problems to Novell.


-122  FFFFFFF86  CONN ALREADY TEMPORARY

Explanation

An attempt was made to convert a connection to temporary that was already temporary.

Action

See Reporting Error Code Problems to Novell.


-123  FFFFFFF85  CONN ALREADY LOGGED IN

Explanation

The connection is already logged in to the Directory.

Action

See Reporting Error Code Problems to Novell.


-124  FFFFFFF84  CONN NOT AUTHENTICATED

Explanation

The connection for a call has not been authenticated.

Action

See Reporting Error Code Problems to Novell.


-125  FFFFFFF83  CONN NOT LOGGED IN

Explanation

An attempt was made to log out of a connection that the user was not logged in to.

Action

See Reporting Error Code Problems to Novell.


-126  FFFFFFF82  NCP BOUNDARY CHECK FAILED

Explanation

The NCP subfunction size does not match the actual size of the data sent.

Action

See Reporting Error Code Problems to Novell.


-127  FFFFFFF81  LOCK WAITING

Explanation

A timeout occurred before a file was locked.

Action

See Reporting Error Code Problems to Novell.


-128  FFFFFFF80  LOCK FAIL

Explanation

An attempt was made to open or create a file that is already open.

Action

See Reporting Error Code Problems to Novell.


-129  FFFFFFF7F  OUT OF HANDLES

Explanation

No more file handles are available or the network file handle table is full.

Action

See Reporting Error Code Problems to Novell.


-130  FFFFFFF7E  NO OPEN PRIVILEGE

Explanation

An attempt was made to open a file without the Open right.

Action

See Reporting Error Code Problems to Novell.


-131  FFFFFFF7D  HARD IO ERROR

Explanation

A hard disk input/output error occurred on a NetWare* volume; a bad sector has been encountered and could be fatal.

Action

See Reporting Error Code Problems to Novell.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


-132  FFFFFFF7C  NO CREATE PRIVILEGE

Explanation

An attempt was made to create a file without the Create right.

Action

See Reporting Error Code Problems to Novell.


-133  FFFFFFF7B  NO CREATE DELETE PRIV

Explanation

An attempt was made to create an already existing file without the Create/Delete rights.

Action

See Reporting Error Code Problems to Novell.


-134  FFFFFFF7A  R O CREATE FILE

Explanation

An attempt was made to create a file with the same name as an already existing file with Read Only status.

Action

See Reporting Error Code Problems to Novell.


-135  FFFFFFF79  CREATE FILE INVALID NAME

Explanation

An attempt was made to create a file using an ambiguous filename.

Action

See Reporting Error Code Problems to Novell.


-136  FFFFFFF78  INVALID FILE HANDLE

Explanation

An attempt was made to close or perform I/O on a file with an invalid file handle (that is, an attempt was made to read from a file that has been closed).

Action

See Reporting Error Code Problems to Novell.


-137  FFFFFFF77  NO SEARCH PRIVILEGE

Explanation

An attempt was made to search a directory without Search rights in that directory.

Action

See Reporting Error Code Problems to Novell.


-138  FFFFFFF76  NO DELETE PRIVILEGE

Explanation

An attempt was made to delete a file without file deletion privileges in that file's directory.

Action

See Reporting Error Code Problems to Novell.


-139  FFFFFFF75  NO RENAME PRIVILEGE

Explanation

An attempt was made to rename a file without renaming privileges in that file's directory.

Action

See Reporting Error Code Problems to Novell.


-140  FFFFFFF74  NO SET PRIVILEGE

Explanation

An attempt was made to modify a file without attribute modification privileges in that file's directory.

Action

See Reporting Error Code Problems to Novell.


-141  FFFFFFF73  SOME FILES IN USE

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.

Action

See Reporting Error Code Problems to Novell.


-142  FFFFFFF72  ALL FILES IN USE

Explanation

An attempt was made to delete, rename, or set file attributes using a filename when the file or files specified by the filename were in use by another workstation.

Action

See Reporting Error Code Problems to Novell.


-143  FFFFFFF71  SOME READ ONLY

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.

Action

See Reporting Error Code Problems to Novell.


-144  FFFFFFF70  ALL READ ONLY

Explanation

An attempt was made to delete, rename, or set file attributes using a filename when all of the files specified have Read Only status.

Action

See Reporting Error Code Problems to Novell.


-145  FFFFFFF6F  SOME NAMES EXIST

Explanation

An attempt was made to rename files when one or more files matching the new filename specification already exist.

Action

See Reporting Error Code Problems to Novell.


-146  FFFFFFF6E  ALL NAMES EXIST

Explanation

An attempt was made to rename files when all of the files matching the new filename specification already exist.

Action

See Reporting Error Code Problems to Novell.


-147  FFFFFFF6D  NO READ PRIVILEGE

Explanation

An attempt was made to read a file without Read privileges to that file.

Action

See Reporting Error Code Problems to Novell.


-148  FFFFFFF6C  NO WRITE PRIVILEGE

Explanation

An attempt was made to write to a file without Write privileges to that file, or the specified file has Read Only status.

Action

See Reporting Error Code Problems to Novell.


-149  FFFFFFF6B  FILE DETACHED

Explanation

An attempt was made to read or write to a detached file.

Action

See Reporting Error Code Problems to Novell.


-150  FFFFFFF6A  INSUFFICIENT MEMORY

Explanation

An attempt was made to write to a file server that does not have enough free dynamic memory to process this request.

Action

See Reporting Error Code Problems to Novell.


-150  FFFFFFF6A  NO ALLOC SPACE

Explanation

An attempt was made to write to a file server that does not have enough free dynamic memory to process this request.

Action

See Reporting Error Code Problems to Novell.


-150  FFFFFFF6A  TARGET NOT A SUBDIR

Explanation

The specified target directory is not a subdirectory.

Action

See Reporting Error Code Problems to Novell.


-150  Multiple causes

Explanation

NetWare could not identify the exact cause of this error.

Possible causes for this error are

INSUFFICIENT MEMORY

NO ALLOC SPACE

TARGET NOT A SUBDIR


-151  FFFFFFF69  NO SPOOL SPACE

Explanation

The network operating system has determined that the network disk does not have enough space left for spool files.

Action

See Reporting Error Code Problems to Novell.


-152  FFFFFFF68  INVALID VOLUME

Explanation

The network operating system has tried to access a volume but cannot find the volume in the system definition files.

Action

See Reporting Error Code Problems to Novell.


-153  FFFFFFF67  DIRECTORY FULL

Explanation

An attempt was made to write to a volume without available directory space.

Action

See Reporting Error Code Problems to Novell.


-154  FFFFFFF66  RENAME ACROSS VOLUME

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.

Action

See Reporting Error Code Problems to Novell.


-155  FFFFFFF65  BAD DIR HANDLE

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.

Action

See Reporting Error Code Problems to Novell.


-156  FFFFFFF64  INVALID PATH

Explanation

An attempt was made to access an invalid path.

Action

See Reporting Error Code Problems to Novell.


-156  FFFFFFF64  NO SUCH EXTENSION

Explanation

An invalid extension was specified.

Action

See Reporting Error Code Problems to Novell.


-156  Multiple causes

Explanation

NetWare could not identify the exact cause of this error.

Possible causes for this error are

INVALID PATH

NO SUCH EXTENSION


-157  FFFFFFF63  NO DIR HANDLES

Explanation

No more directory handles are available; the directory handle table is full. Each user may have up to 255 directory handles.

Action

See Reporting Error Code Problems to Novell.


-158  FFFFFFF62  BAD FILE NAME

Explanation

An attempt was made to create a file using invalid characters within the name of the file. Illegal characters in names are control characters, the comma, colon, semicolon, slash, backslash, question mark, asterisk, and tilde.

Action

Try making the request again using valid characters in the file name.


-159  FFFFFFF61  DIRECTORY ACTIVE

Explanation

An attempt was made to delete a directory that is being used by another workstation.

Action

See Reporting Error Code Problems to Novell.


-160  FFFFFFF60  DIRECTORY NOT EMPTY

Explanation

An attempt was made to delete a directory that contains files or other directories.

Action

See Reporting Error Code Problems to Novell.


-161  FFFFFFF5F  DIRECTORY IO ERROR

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.

Action

See Reporting Error Code Problems to Novell.


-162  FFFFFFF5E  IO LOCKED

Explanation

An attempt was made to read a file where data is physically locked.

Action

See Reporting Error Code Problems to Novell.


-163  FFFFFFF5D  TRANSACTION RESTARTED

Action

See Reporting Error Code Problems to Novell.


-164  FFFFFFF5C  RENAME DIR INVALID

Explanation

An attempt was made to rename a directory with an invalid name.

Action

See Reporting Error Code Problems to Novell.


-165  FFFFFFF5B  INVALID OPENCREATE MODE

Explanation

An invalid opencreate mode was encountered.

Action

See Reporting Error Code Problems to Novell.


-166  FFFFFFF5A  ALREADY IN USE

Explanation

An attempt was made to access a file that was already in use.

Action

See Reporting Error Code Problems to Novell.


-167  FFFFFFF59  INVALID RESOURCE TAG

Explanation

An invalid resource tag was encountered.

Action

See Reporting Error Code Problems to Novell.


-168  FFFFFFF58  ACCESS DENIED

Explanation

Access has been denied.

Action

See Reporting Error Code Problems to Novell.


-190  FFFFFFF42  INVALID DATA STREAM

Explanation

Data streams are invalid.

Action

See Reporting Error Code Problems to Novell.


-191  FFFFFFF41  INVALID NAME SPACE

Explanation

An invalid name space was used.

Action

See Reporting Error Code Problems to Novell.


-192  FFFFFFF40  NO ACCOUNTING PRIVILEGES
-192  FFFFFFFF40  NO ACCOUNTING PRIVILEGES

Explanation

The user has no accounting privileges.

Action

See Reporting Error Code Problems to Novell.


-193  FFFFFFF3F  NO ACCOUNT BALANCE

Explanation

Attempt was made to log in by a bindery object without an accounting balance, and accounting is enabled.

Action

See Reporting Error Code Problems to Novell.


-194  FFFFFFF3E  CREDIT LIMIT EXCEEDED

Explanation

An attempt was made to log in to an account with no credit available.

Action

See Reporting Error Code Problems to Novell.


-195  FFFFFFF3D  TOO MANY HOLDS

Action

See Reporting Error Code Problems to Novell.


-196  FFFFFFF3C  ACCOUNTING DISABLED

Explanation

Accounting has been disabled.

Action

See Reporting Error Code Problems to Novell.


-197  FFFFFFF3B  LOGIN LOCKOUT

Explanation

An attempt was made to log in after the system had locked the account because of intruder detection.

Action

See Reporting Error Code Problems to Novell.


-198  FFFFFFF3A  NO CONSOLE RIGHTS

Explanation

An attempt was made to use console privileges without operator privileges.

Action

See Reporting Error Code Problems to Novell.


-208  FFFFFFF30  Q IO FAILURE

Explanation

A queue I/O error occurred.

Action

See Reporting Error Code Problems to Novell.


-209  FFFFFFF2F  NO QUEUE

Explanation

No queues are defined.

Action

See Reporting Error Code Problems to Novell.


-210  FFFFFFF2E  NO Q SERVER

Explanation

No queue server has been specified.

Action

See Reporting Error Code Problems to Novell.


-211 FFFFFFF2D  NO Q RIGHTS

Explanation

An attempt was made to use the queue with no access privileges.

Action

See Reporting Error Code Problems to Novell.


-212  FFFFFFF2C  Q FULL

Explanation

The queue is full.

Action

See Reporting Error Code Problems to Novell.


-213  FFFFFFF2B  NO Q JOB

Explanation

No jobs are in the queue.

Action

See Reporting Error Code Problems to Novell.


-214  FFFFFFF2A  NO Q JOB RIGHTS

Explanation

An attempt was made to access the a job in the queue with no queue privileges.

Action

See Reporting Error Code Problems to Novell.


-214  Multiple causes

Explanation

NetWare could not identify the exact cause of this error.

Possible causes for this error are

NO Q JOB RIGHTS

UNENCRYPTED NOT ALLOWED


-214 FFFFFFF2A  UNENCRYPTED NOT ALLOWED

Action

See Reporting Error Code Problems to Novell.


-215  FFFFFFF29  DUPLICATE PASSWORD

Explanation

An attempt was made to change a password to a previously used password when the unique password requirement is specified for the account.

Action

See Reporting Error Code Problems to Novell.


-215  FFFFFFF29  Q IN SERVICE

Explanation

The queue is in service at this time.

Action

See Reporting Error Code Problems to Novell.


-215  Multiple causes

Explanation

NetWare could not identify the exact cause of this error.

Possible causes for this error are

DUPLICATE PASSWORD

Q IN SERVICE


-216  FFFFFFF28  PASSWORD TOO SHORT

Explanation

An attempt was made to change a password to a password with fewer characters than the required minimum specified for the account.

Action

Reenter the password using at least the minimum amount of required characters.


-216  FFFFFFF28  Q NOT ACTIVE

Explanation

An attempt was made to access a queue that is not active.

Action

See Reporting Error Code Problems to Novell.


-216  Multiple causes

Explanation

NetWare could not identify the exact cause of this error.

Possible causes for this error are

PASSWORD TOO SHORT

Q NOT ACTIVE


-217  FFFFFFF27  MAXIMUM LOGINS EXCEEDED

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.

Action

See Reporting Error Code Problems to Novell.


-217  FFFFFFF27  Q STN NOT SERVER

Explanation

The queue station is not a server.

Action

See Reporting Error Code Problems to Novell.


-217  Multiple causes

Explanation

NetWare could not identify the exact cause of this error.

Possible causes for this error are

MAXIMUM LOGINS EXCEEDED

Q STN NOT SERVER


-218  FFFFFFF26  BAD LOGIN TIME

Explanation

An attempt was made to log in during an unauthorized time of day specified for the account.

Action

See Reporting Error Code Problems to Novell.


-218  FFFFFFF26  Q HALTED

Explanation

The queue has been halted.

Action

See Reporting Error Code Problems to Novell.


-218  Multiple causes

Explanation

NetWare could not identify the exact cause of this error.

Possible causes for this error are

BAD LOGIN TIME

Q HALTED


-219  FFFFFFF25  NODE ADDRESS VIOLATION

Explanation

An attempt to log in was made from an unauthorized station using an account with limits to a specific network and or station.

Action

See Reporting Error Code Problems to Novell.


-219  Multiple causes

Explanation

NetWare could not identify the exact cause of this error.

Possible causes for this error are

NODE ADDRESS VIOLATION

Q MAX SERVERS


-219 FFFFFFF25  Q MAX SERVERS

Explanation

This queue is already attached to the maximum number of servers allowed.

Action

See Reporting Error Code Problems to Novell.


-220  FFFFFFF24  LOG ACCOUNT EXPIRED

Explanation

An attempt was made by a station to log in using an account that has expired or has been disabled by the Supervisor.

Action

See Reporting Error Code Problems to Novell.


-222  FFFFFFF22  BAD PASSWORD

Explanation

An attempt was made to log in using an account password that has expired and all grace logins have also expired.

Action

See Reporting Error Code Problems to Novell.


-223  FFFFFFF21  PASSWORD EXPIRED

Explanation

An attempt was made by a station to log in using an expired account password but the login was allowed because the account had a grace login.

Action

See Reporting Error Code Problems to Novell.


-224  FFFFFFF20  NO LOGIN CONN AVAILABLE

Explanation

An attempt was made by a station to login when no login connections were available.

Action

See Reporting Error Code Problems to Novell.


-232  FFFFFFF18  WRITE TO GROUP PROPERTY

Explanation

An attempt was made by a station to write a data segment to a group property using the call to write a property value.

Action

See Reporting Error Code Problems to Novell.


-233  FFFFFFF17  MEMBER ALREADY EXISTS

Explanation

An attempt was made by a station to redundantly add an object to a group property.

Action

See Reporting Error Code Problems to Novell.


-234  FFFFFFF16  NO SUCH MEMBER

Explanation

An attempt was made by a station to use an object that is not a member of the defined group property.

Action

See Reporting Error Code Problems to Novell.


-235  FFFFFFF15  PROPERTY NOT GROUP

Explanation

An attempt was made by a station to use a nongroup property.

Action

See Reporting Error Code Problems to Novell.


-236  FFFFFFF14  NO SUCH VALUE SET

Explanation

An attempt was made by a station to use a nonexistent segment. Segments must be written sequentially when a property is first created, but can be read and written in any order after they already exist.

Action

See Reporting Error Code Problems to Novell.


-237  FFFFFFF13  PROPERTY ALREADY EXISTS

Explanation

An attempt was made by a station to create a property that already exists.

Action

See Reporting Error Code Problems to Novell.


-238  FFFFFFF12  OBJECT ALREADY EXISTS

Explanation

An attempt was made by a station to create an object that already exists.

Action

See Reporting Error Code Problems to Novell.


-239  FFFFFFF11  ILLEGAL NAME

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

Try making the request again using valid characters.


-240  FFFFFFF10  ILLEGAL WILDCARD

Explanation

An attempt was made to use a wildcard character or wild object type in a call where wildcards are not allowed.

Action

See Reporting Error Code Problems to Novell.


-241  FFFFFFF0F  BINDERY SECURITY

Explanation

An attempt to assign a security level of a bindery object or property to be higher than the user's security level was made. This would make the object or property inaccessible to the user.

Action

See Reporting Error Code Problems to Novell.


-242  FFFFFFF0E  NO OBJECT READ RIGHTS

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.

Action

See Reporting Error Code Problems to Novell.


-243  FFFFFFF0D  NO OBJECT RENAME RIGHTS

Explanation

An attempt to rename an object was made by a station without the necessary security to rename an object. Only the Supervisor object can rename objects. If a station does not even have the proper security to see that the object exists, then NCP_NO_SUCH_OBJECT is returned.

Action

See Reporting Error Code Problems to Novell.


-244  FFFFFFF0C  NO OBJECT DELETE RIGHTS

Explanation

An attempt to delete an object was made by a station without the necessary security to delete the object. Only the Supervisor object can delete objects. If a station does not even have the proper security to see that the object exists, then NCP_NO_SUCH_OBJECT is returned.

Action

See Reporting Error Code Problems to Novell.


-245  FFFFFFF0B  NO OBJECT CREATE RIGHTS

Explanation

An attempt to create an object was made by a station without the necessary security to create or change an object. Only the Supervisor object is allowed to create objects.

Action

See Reporting Error Code Problems to Novell.


-246  FFFFFFF0A  NO PROPERTY DELETE RIGHTS

Explanation

An attempt to delete a property was made by a station without the necessary security privilege to delete a  property from the give object. If the station does not have the proper security to see that the property exists, then NCP_NO_SUCH_PROPERTY is returned.

Action

See Reporting Error Code Problems to Novell.


-247  FFFFFFF09  NO PROPERTY CREATE RIGHTS

Explanation

An attempt to create a property was made by a station without the necessary security to create or change a property for the object.

Action

See Reporting Error Code Problems to Novell.


-248  FFFFFFF08  NO PROPERTY WRITE RIGHTS

Explanation

An attempt to write was made by a station without the necessary write security to access the property data.

Action

See Reporting Error Code Problems to Novell.


-249  FFFFFFF07  NO PROPERTY READ RIGHTS

Explanation

An attempt to read was made by a station without the necessary read security to access the property data.

Action

See Reporting Error Code Problems to Novell.


-250  FFFFFFF06  TEMP REMAP

Explanation

An attempt was made to use an unknown path.

Action

See Reporting Error Code Problems to Novell.


-251  FFFFFFF05  NO SUCH PROPERTY

Explanation

An attempt was made to use a property that does not exist for the specified object.

Action

See Reporting Error Code Problems to Novell.


-251  FFFFFFF05  UNKNOWN REQUEST

Explanation

An attempt was made to use an invalid parameter (drive number, path, or flag value) during a set drive path call.

Action

See Reporting Error Code Problems to Novell.


-251  Multiple causes

Explanation

NetWare could not identify the exact cause of this error.

Possible causes for this error are

NO SUCH PROPERTY

UNKNOWN REQUEST


-252  FFFFFFF04  MESSAGE QUEUE FULL

Explanation

An attempt was made to use a full message queue.

Action

See Reporting Error Code Problems to Novell.


-252  FFFFFFF04  NO SUCH OBJECT

Explanation

An attempt was made to use an object that doesn't exist, or the calling station does not have the proper security to access the object. The object name and type must both match for the object to be found.

Action

See Reporting Error Code Problems to Novell.


-252  FFFFFFF04  TARGET ALREADY HAS MSG

Explanation

The message recipient already has a message waiting.

Action

See Reporting Error Code Problems to Novell.


-252  Multiple causes

Explanation

NetWare could not identify the exact cause of this error.

Possible causes for this error are

MESSAGE QUEUE FULL

NO SUCH OBJECT

TARGET ALREADY HAS MSG


-253  FFFFFFF03  BAD STATION NUMBER

Explanation

An attempt was made to use a bad (undefined, unavailable, etc.) station number.

Action

See Reporting Error Code Problems to Novell.


-254  FFFFFFF02  BINDERY LOCKED

Explanation

An attempt was made to use a bindery that is temporarily locked by the Supervisor.

Action

See Reporting Error Code Problems to Novell.


-254  FFFFFFF02  DIR LOCKED

Explanation

An attempt was made to use a locked directory.

Action

See Reporting Error Code Problems to Novell.


-254  FFFFFFF02  SPOOL DELETE

Explanation

An error occurred during an attempt to delete a spool.

Action

See Reporting Error Code Problems to Novell.


-254  FFFFFFF02  TRUSTEE NOT FOUND

Explanation

An operation tried to use an unknown trustee.

Action

See Reporting Error Code Problems to Novell.


-254  Multiple causes

Explanation

NetWare could not identify the exact cause of this error.

Possible causes for this error are

BINDERY LOCKED

DIR LOCKED

SPOOL DELETE

TRUSTEE NOT FOUND


-255  FFFFFFF01  BAD PARAMETER

Explanation

An invalid parameter was used.

Action

See Reporting Error Code Problems to Novell.


-255  FFFFFFF01  BAD SPOOL PRINTER

Explanation

An attempt was made to use a bad (undefined, unavailable, etc.) printer.

Action

See Reporting Error Code Problems to Novell.


-255  FFFFFFF01  CLOSE FCB

Explanation

An error occurred closing the file.

Action

See Reporting Error Code Problems to Novell.


-255  FFFFFFF01  ERR OF SOME SORT

EXPLANATION

An internal error that has not been identified by Novell has occurred.

Action

See Reporting Error Code Problems to Novell.


-255  FFFFFFF01  FILE EXISTS

Explanation

An attempt was made to create a file that already exists.

Action

See Reporting Error Code Problems to Novell.


-255  FFFFFFF01  FILE NAME

Explanation

An attempt was made to use a file with a bad (undefined, unavailable, etc.) name or extension.

Action

See Reporting Error Code Problems to Novell.


-255  FFFFFFF01  HARD FAILURE

Explanation

A hardware failure occurred.

Action

See Reporting Error Code Problems to Novell.


-255  FFFFFFF01  IO BOUND

Explanation

The program tried to write beyond the end of the file or disk.

Action

See Reporting Error Code Problems to Novell.


-255  FFFFFFF01  MUST FORCE DOWN

Action

See Reporting Error Code Problems to Novell.


-255  FFFFFFF01  NO FILES FOUND

Explanation

No files were found that matched the search specification.

Action

See Reporting Error Code Problems to Novell.


-255  FFFFFFF01  NO SPOOL FILE

Explanation

There are no spooled files.

Action

See Reporting Error Code Problems to Novell.


-255  FFFFFFF01  NO TRUSTEE CHANGE PRIV

Explanation

The user does not have the rights to change trustees.

Action

See Reporting Error Code Problems to Novell.


-255  FFFFFFF01  TARGET NOT ACCEPTING MSGS

Explanation

The target station is not accepting messages.

Action

See Reporting Error Code Problems to Novell.


-255  FFFFFFF01  TARGET NOT LOGGED IN

Explanation

The target station is not logged in.

Action

See Reporting Error Code Problems to Novell.


-255  Multiple causes

Explanation

NetWare could not identify the exact cause of this error.

Possible causes for this error are

BAD PARAMETER

BAD SPOOL PRINTER

CLOSE FCB

ERR OF SOME SORT

FILE EXISTS

FILE NAME

HARD FAILURE

IO BOUND

MUST FORCE DOWN

NO FILES FOUND

NO SPOOL FILE

NO TRUSTEE CHANGE PRIV

TARGET NOT ACCEPTING MSGS

TARGET NOT LOGGED IN


-301  FFFFFFED3  NOT ENOUGH MEMORY

Explanation

The client workstation does not have enough available memory.

Action

See Reporting Error Code Problems to Novell.


-302  FFFFFFED2  BAD KEY

Explanation

The program is trying to pass a bad key parameter for a context call. This is an internal program error.

Action

See Reporting Error Code Problems to Novell.


-303  FFFFFFED1  BAD CONTEXT

Explanation

The program is trying to pass a bad context parameter to an NDS call. This is an internal program error.

Action

See Reporting Error Code Problems to Novell.


-304  FFFFFFED0  BUFFER FULL

Explanation

The workstation does not have room to add data to an input buffer.

Action

See Reporting Error Code Problems to Novell.


-305  FFFFFFECF  LIST EMPTY

Explanation

The program passed an empty list (a null pointer) to NWDSPutAttrVal. This is an internal program error.

Action

See Reporting Error Code Problems to Novell.


-306  FFFFFFECE  BAD SYNTAX

Explanation

The program tried to pass an ID that had an invalid syntax. This is an internal program error.

Action

See Reporting Error Code Problems to Novell.


-307  FFFFFFECD  BUFFER EMPTY

Explanation

The program tried to get data from an empty buffer. This is an internal program error.

Action

See Reporting Error Code Problems to Novell.


-308  FFFFFFECC  BAD VERB

Explanation

The program initialized the buffer with a verb not associated with the API. This is an internal program error.

Action

See Reporting Error Code Problems to Novell.


-309  FFFFFFECB  EXPECTED IDENTIFIER

Explanation

The name being parsed is not typed.

Action

See Reporting Error Code Problems to Novell.


-310  FFFFFFECA  EXPECTED EQUALS

Explanation

An equal sign is expected in the name.

Action

See Reporting Error Code Problems to Novell.


-311  FFFFFFEC9  ATTR TYPE EXPECTED

Explanation

The multi-AVA name being parsed must be typed.

Action

All AVAs must be typed or not typed.


-312  FFFFFFEC8  ATTR TYPE NOT EXPECTED

Explanation

The multi-AVA name being parsed might not be typed.

Action

All AVAs must be typed or not typed.


-313  FFFFFFEC7  FILTER TREE EMPTY

Explanation

The program is trying to delete an empty filter. This is an internal program error.

Action

See Reporting Error Code Problems to Novell.


-314  FFFFFFEC6  INVALID OBJECT NAME

Explanation

The program is trying to pass a NULL string for object name to the API call or trying to pass a name containing both leading and trailing dots.

Action

See Reporting Error Code Problems to Novell.


-315  FFFFFFEC6  EXPECTED RDN DELIMITER

Explanation

An RDN delimiter (.) was expected and not found while the name was being parsed.

Action

See Reporting Error Code Problems to Novell.


-316  FFFFFFEC5  TOO MANY TOKENS

Explanation

Too many trailing delimiter dots occurred in the name. Only three context levels and four trailing dots are allowed in a name.

Action

See Reporting Error Code Problems to Novell.


-317  FFFFFFEC3  INCONSISTENT MULTIAVA

Explanation

The AVA type is incorrect.

Action

See Reporting Error Code Problems to Novell.


-318  FFFFFFEC2  COUNTRY NAME TOO LONG

Explanation

Country name identifiers are only allowed one character.

Action

See Reporting Error Code Problems to Novell.


-319  FFFFFFEC1  SYSTEM ERROR

Explanation

This is an internal program error.

Action

See Reporting Error Code Problems to Novell.


-320  FFFFFFEC0  CANT ADD ROOT

Explanation

The program is trying to restore an object at the root.

Action

See Reporting Error Code Problems to Novell.


-321  FFFFFFEBF  UNABLE TO ATTACH

Explanation

An attempt to connect to a server failed.

Action

See Reporting Error Code Problems to Novell.


-322  FFFFFFEBE  INVALID HANDLE

Explanation

An invalid iteration handle was found. This is probably an internal program error.

Action

See Reporting Error Code Problems to Novell.


-323  FFFFFFEBD  BUFFER ZERO LENGTH

Explanation

The program tried to call NWDS AllocBuf with a zero-length size. This is probably an internal program error.

Action

See Reporting Error Code Problems to Novell.


-324  FFFFFFEBC  INVALID REPLICA TYPE

Explanation

The program tried to pass in a replica type that was not a Master, Secondary, or Read Only. This is probably an internal program error.

Action

See Reporting Error Code Problems to Novell.


-325  FFFFFFEBB  INVALID ATTR SYNTAX

Explanation

An invalid attribute syntax was passed in.

Action

See Reporting Error Code Problems to Novell.


-326  FFFFFFEBA  INVALID FILTER SYNTAX

Explanation

An invalid filter syntax was passed in.

Action

See Reporting Error Code Problems to Novell.


-328  FFFFFFEB8  CONTEXT CREATION

Explanation

The context could not be created. This error occurs

Most often when the Unicode files are not loaded.

When NDS* Manager is running on Windows** 95** and the maximum number of context handles in use has been reached.

Note: Windows 95 only allows 16 context handles per process.  Windows 3x allows 48 total handles system-wide. Therefore, you might see this error in Windows 3x, but will most likely see it in Windows 95.

Action

Make sure the Unicode files are loaded.

If you are using NDS Manager, do the following actions in order:

1.	Close some of your NDS Manager windows and retry the operation.

2.	If you are using Window 3x, and the first action does not work, close any unnecessary applications and retry the operation.

3.	If step 1 or 2 does not work, shut down the workstation and bring it back up.


-329  FFFFFFEB7  INVALID UNION TAG

Explanation

The server returned an "infotype" parameter that did not agree with the infotype passed in. This is an internal program error.

Action

See Reporting Error Code Problems to Novell.


-330  FFFFFFEB6  INVALID SERVER RESPONSE

Explanation

The server returned an invalid response.

Action

See Reporting Error Code Problems to Novell.


-331  FFFFFFEB5  NULL POINTER

Explanation

A null pointer was found when a Real pointer was expected.

Action

Do not use a null pointer.


-332  FFFFFFEB5  NO SERVER FOUND

Explanation

The attempt to connect failed to find any servers responding.

Action

See Reporting Error Code Problems to Novell.


-333  FFFFFFEB3  NO CONNECTION

Explanation

An invalid iteration handle was found. This is probably an internal program error.

Action

See Reporting Error Code Problems to Novell.


-334  FFFFFFEB2  RDN TOO LONG

Explanation

The Relative Distingushed Name (RDN) exceeded 128 characters.

Action

See Reporting Error Code Problems to Novell.


-335  FFFFFFEB1  DUPLICATE TYPE

Explanation

Multi-AVAs exist. AVAs cannot contain the same type.

Action

See Reporting Error Code Problems to Novell.


-336  FFFFFFEB0  DATA STORE FAILURE

Explanation

A data storage failure occurred.

Action

See Reporting Error Code Problems to Novell.


-337  FFFFFFEAF  NOT LOGGED IN

Action

See Reporting Error Code Problems to Novell.


-338  FFFFFFEAE  INVALID PASSWORD CHARS

Explanation

Illegal characters were used when assigning the password. Illegal characters in names are control characters, the comma, colon, semicolon, slash, backslash, question mark, asterisk, and tilde.

Action

Try assigning the password again using valid characters.


-339  FFFFFFEAD  FAILED SERVER AUTHENT

Action

See Reporting Error Code Problems to Novell.


-340  FFFFFFEAC  TRANSPORT

Explanation

A transport failure occurred.

Action

See Reporting Error Code Problems to Novell.


-341  FFFFFFEAB  NO SUCH SYNTAX

Action

See Reporting Error Code Problems to Novell.


-342  FFFFFFEAA  INVALID DS NAME

Explanation

An invalid NetWare* Directory Services* name was found.

This error might occur by either of the following two reasons:

An empty string was passed in for a name

Null pointer

Action

See Reporting Error Code Problems to Novell.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


-343  FFFFFFEA9  ATTR NAME TOO LONG

Explanation

The attribute name exceeded 128 characters.

Action

See Reporting Error Code Problems to Novell.


-344  FFFFFFEA8  INVALID TDS

Explanation

The Tagged Data Store (TDS) is not initialized or is corrupted. This usually occurs when the NWDS Login function was not called first.

Action

See Reporting Error Code Problems to Novell.


-345  FFFFFFEA7  INVALID DS VERSION

Action

See Reporting Error Code Problems to Novell.


-346  FFFFFFEA6  UNICODE TRANSLATION

Explanation

A Unicode translation error occurred. This is probably an internal program error.

Action

See Reporting Error Code Problems to Novell.


-347  FFFFFFEAS  SCHEMA NAME TOO LONG

Explanation

This error probably occurred when the user tried to create a new class of object with a class name that exceeded 32 characters.

Action

See Reporting Error Code Problems to Novell.


-348  FFFFFFEA4  UNICODE FILE NOT FOUND

Explanation

The Unicode file could not be found in the defined search algorithm.

The file extension shown in parentheses represents the country code the workstation is using, which is set in CONFIG.SYS. For example, *.001 is US English. The country code may be different from the one shown here.

In the DOS, Windows, and OS/2 environments, the program searches the following areas for the Unicode files:

The current directory (for DOS and OS/2 environments) or the Windows directory.

The load directory (the directory containing the current utility’s .EXE file). Normally this will be the PUBLIC directory.

The NLS directory that is located within the load directory (the directory containing the current utility’s .EXE file). If the Unicode files are not found in the NLS directory within the load directory, the program searches the NLS directory that is a sibling of the load directory (that is, at the same level as the load directory). Note: The NWLanguage environment variable does not apply here.

The PATH and DPATH (for OS/2 only) environment variables. These environment variables may be found either in the user’s login script or in the AUTOEXEC.BAT file.

The following four files must be in one of these locations of the user’s search drive, or this error message is displayed:

code_page_UNI. country_id

UNI_code_page.country_id

UNI_MON.country_id

UNI_COL.country_id

Action

Make sure that these four files are loaded into the PUBLIC directory and that you have a search drive mapped to PUBLIC; then try the operation again. If you have a search drive mapped to PUBLIC and the files still cannot be found there or in any other locations listed, use the NPATH utility to determine the Unicode files required for the workstation and their location. If the problem persists, contact a NetWare support provider.


-349  FFFFFFEA3  UNICODE ALREADY LOADED

Explanation

The Unicode tables were already loaded when the program tried to load them again.

Action

See Reporting Error Code Problems to Novell.


-350  FFFFFFEA2  NOT CONTEXT OWNER

Action

See Reporting Error Code Problems to Novell.


-351  FFFFFFEA1  ATTEMPT TO AUTHENTICATE 0

Action

See Reporting Error Code Problems to Novell.


-352  FFFFFFEA0  NO WRITABLE REPLICAS

Explanation

On logout, the server logged out of the monitor connection. Subsequently, the program tried and failed to find a writable replica of that monitor connection's partition.

Action

See Reporting Error Code Problems to Novell.


-353  FFFFFFE9F  DN TOO LONG

Explanation

The name passed in exceeded 256 characters.

Action

See Reporting Error Code Problems to Novell.


-354  FFFFFFE9E  RENAME NOT ALLOWED

Explanation

An attempt was made to move an object to the same place in the Directory tree that it already occupies.

Action

See Reporting Error Code Problems to Novell.


-489  FFFFFFE17  UNI ALREADY LOADED

Explanation

When an application tried to load the Unicode tables, they were already loaded.

Action

See Reporting Error Code Problems to Novell.


-490  FFFFFFE16  UNI  FUTURE OPCODE

Explanation

The Unicode rule table has unimplimented rules.

Action

See Reporting Error Code Problems to Novell.


-491  FFFFFFE15  UNI NO SUCH FILE

Explanation

No such Unicode file or directory exists.

Action

See Reporting Error Code Problems to Novell.


-492  FFFFFFE14  UNI TOO MANY FILES

Explanation

Too many Unicode files are already open.

Action

See Reporting Error Code Problems to Novell.


-493  FFFFFFE13  UNI NO PERMISSION

Explanation

An attempt was made to open a Unicode file to which the user does not have sufficient rights.

Action

If appropriate, give the user the rights necessary to open the Unicode files.


-494  FFFFFFE12  UNI NO MEMORY

Explanation

The workstation does not have enough memory to load the Unicode table files.

Action

Increase the memory available to the workstation. See "Resolving Workstation Memory Problems" in Supervising the Network.


-495  FFFFFFE11  UNI LOAD FAILED

Explanation

An attempt to load the Unicode rule table files failed.

Action

See Reporting Error Code Problems to Novell.


-496  FFFFFFE10  UNI HANDLE BAD

Explanation

An attempt was made to use the Unicode Rule tables, but its handle was bad.

Action

See Reporting Error Code Problems to Novell.


-497  FFFFFFE0F  UNI HANDLE MISMATCH

Explanation

The handle for the rule table does not the match operation being attempted.

Action

See Reporting Error Code Problems to Novell.


-498  FFFFFFE0E  UNI RULES CORRUPT

Explanation

The Unicode Rule table files are not the correct version or they are corrupt.

Action

Obtain a new copy of the Unicode files. Then retry the operation.


-499  FFFFFFE0D  UNI NO DEFAULT

Explanation

A default directory for the Unicode files does not exist.

Action

See Reporting Error Code Problems to Novell.


-500  FFFFFFE0C  UNI INSUFFICIENT BUFFER

Explanation

The buffer is insufficient to load the Unicode files.

Action

See Reporting Error Code Problems to Novell.


-501  FFFFFFE0B  UNI OPEN FAILED

Explanation

The Unicode table files could not be opened for an unknown reason.

Action

Try the following

Close files you do not need to have open at the present time.

Free up memory on the workstation. See "Resolving Workstation Memory Problems" in Supervising the Network.

Make sure the user has rights to access the directory where the Unicode table files are kept.

Make sure the directory where the Unicode files are kept is in the search path.

Make sure the Unicode files are the most current version and are not corrupted.

If after doing all the listed actions the problem still persists, contact a NetWare support provider.


-502  FFFFFFE0A  UNI NO LOAD DIR

Explanation

The load directory for the Unicode file could not be determined.

Action

See Reporting Error Code Problems to Novell.


-503  FFFFFFE09  UNI BAD FILE HANDLE

Explanation

The file handle is bad for the Unicode files.

Action

See Reporting Error Code Problems to Novell.


-504  FFFFFFE08  UNI READ FAILED
-504  FFFFFE08  UNI READ FAILED

Explanation

The files could not be read for the Unicode rule table.

Action

See Reporting Error Code Problems to Novell.


-505  FFFFFFE07  UNI TRANS CORRUPT
-505  FFFFFE07  UNI TRANS CORRUPT

Explanation

The translator is corrupt for the Unicode files.

Action

See Reporting Error Code Problems to Novell.


-601  FFFFFFDA7  NO SUCH ENTRY

Explanation

The object name entered could not be found in the context specified. The object name might be mistyped. The context for the workstation might be incorrect for the object being sought. The leading dots or trailing dots might be used incorrectly.

If this error displays while running DSTRACE on the server or while viewing Partition Continuity in NDS Manager, it usually means that an entry is missing from the entry record table on the source server.

It is common to get this error on a NetWare 4.0x server when trying to delete bindery-type objects through NetWare Administrator or the NetWare 4.02 version of NETADMIN.

Action

Client: Check the context specified for the object name entered. If the command line input was the object name, check the workstation's context. Make sure that it points to the correct level of the Directory tree for the object name specified. If the input includes the object's full or partial context, make sure that the leading and trailing dots are specified appropriately and the types are correct.

To delete bindery-type objects from a NetWare 4.0x server, use the NetWare 4.01 version of NETADMIN. In NetWare 4.1 (or later versions), you should not have to delete bindery-type objects.

You can use the Partition Continuity feature of NDS Manager to evaluate the partition for synchronization errors. NDS Manager has several repair functions that allow you to correct synchronization errors without having to run DSREPAIR from the server.

Note: Using the Send Updates option or the Receive Updates option might create high levels of network traffic.

If Partition Continuity shows no errors besides -601, use NDS Manager to send updates from a replica that does not have the error, or receive updates on the replica with the error. Send Updates and Receive Updates are available from the Tree view, the list of Partitions and Servers, and the Partition Continuity view in NDS Manager.

Server: Identify which object is returning the -601 error. To do this, set the SET DSTRACE=+SYNC command on both the source and the target server and on any other servers in the replica list.

If the object is not a server, try deleting it.

If the object with the error is a server object, see if DSTRACE returns any other errors besides -601. Address those errors, if any.

Note: Using the Send All Objects option or the Receive All Objects option might create high levels of network traffic.

If no additional errors are displayed, use the Send All Objects option or Receive All Objects option in DSREPAIR to update replicas of a partition on the servers holding replicas.


-602  FFFFFFDA6  NO SUCH VALUE

Explanation

The requested property value could not be found. If this error is encountered during the login or authentication process, this error usually means that the user's or the server's public keys could not be located. If this is the case, regenerate the user's key pair by changing the password with utilities.

An occurrence of this error during the synchronization process between servers means one of the public keys cannot be located or the replica lists of one of the servers contains inconsistent results. This error might be a temporary condition that exists due to the loosely consistent nature of NetWare* Directory Services*.

Action

Determine whether the value exists for the specified attribute using NLIST.

If either of these messages is displayed without an error code, do the following action that is applicable to the error displayed: Error unable to communicate, or Error sending updates.

Error unable to communicate

Check to see if a problem exists with the object. To do this, use DSTRACE and the SET DSTRACE=+SYNC command.

This problem might be related to the public key or the remote ID number. Verify that all remote server ID numbers are valid.

To do this, run the Verify Remote Server IDs option from the Partition Continuity view in NDS Manager (on the client) or DSREPAIR (on the server).

If the -602 or -603 error codes are returned, rerun the Verify Remote Server IDs option.

If error codes -602 or -603 are returned again, contact a NetWare support provider for support.

Be aware, however, that a public key cannot be repaired unless there is at least one server in the tree authenticating to the target server. The server that is able to successfully authenticate to the target server must also have a real copy of the target server object.

This means that the server must have a replica (other than a subordinate reference replica) of the partition holding the target server object. If only two servers are in the tree, remove the target server from the tree and reinstall it.

Error sending updates

Check to see if a problem exists with the object. To do this, use DSTRACE and the SET DSTRACE=+SYNC command.

If an error exists, try deleting the object in question.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


-603  FFFFFFDA5  NO SUCH ATTRIBUTE

Explanation

The requested attribute could not be found. In the Directory, if an attribute does not contain a value then the attribute does not exist for the specific object. The error occurs sometimes when users try to edit properties that are grayed out in the utilities. Properties that are grayed out are not supported by the current Directory Schema.

This error can also occur when problems with schema synchronization occur in a mixed tree (NetWare 4.0x and other NetWare* 4 servers in the same tree). This error is basically the same as a -602 error except that a -602 error is returned for a multi-valued property and a -603 is for a single-valued property.

Action

Client: Ensure that the attribute being requested is a valid NDS* attribute (check spelling and syntax). To determine whether the attribute exists for the specified object, use NLIST. For example, NLIST user=username /d will show all attributes and their values for the specified username.

To see all of the attributes associated with the object, you must have the Supervisor right to the object. The Browse right is given by default.

Server: If either of these messages is displayed without an error code, do the following action that is applicable to the error displayed: Error unable to communicate, or Error sending updates.

Error unable to communicate

Check to see if a problem exists with the object. To do this, use DSTRACE and the SET DSTRACE=+SYNC command.

This problem might be related to the public key or the remote ID number.

Verify that all remote server ID numbers are valid. To do this, run the Verify Remote Server IDs option from the Partition Continuity view in NDS Manager (on the client) or DSREPAIR (on the server).

If the -602 or -603 error codes are returned, rerun the Verify Remote Server IDs option.

If error codes -602 or -603 are returned again, contact a NetWare support provider for support.

Be aware, however, that a public key cannot be repaired unless there is at least one server in the tree authenticating to the target server. The server that is able to successfully authenticate to the target server must also have a real copy of the target server object. This means that the server must have a replica (other than a subordinate reference replica) of the partition holding the target server object. If only two servers are in the tree, remove the target server from the tree and reinstall it.

Error sending updates

Check to see if a problem exists with the object. To do this, use DSTRACE and the SET DSTRACE=+SYNC command.

If an error exists, try deleting the object in question.

If a mix of NetWare 4.x servers exists in the tree or if a NetWare 4.1 (or later version) server was installed then uninstalled in a NetWare 4.0x  tree, the problem might be caused by a schema problem. Run the Global Schema Update option in DSREPAIR on a NetWare 4.1 (or later version) server.

If no NetWare 4.1 (or later version) servers are installed in the tree, or if the Global Schema Update option does not fix the problem, shut down the server holding the master replica of the partition returning the error, and then bring it back up. Upon start-up, the server forces a schema update and this will usually correct a schema problem.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


-604  FFFFFFDA4  NO SUCH CLASS

Explanation

A utility is trying to reference an object class that does not exist in the Directory. An NDS object class is similar to the bindery's object type. For example, object type 1 in the bindery is a user object. In NDS that object class is User. The class indicates the kind of entry to be created.

Action

NetWare 4.0x  utilities access only NetWare's base schema, which must be present for the Directory to operate. Determine what utility is being used to create the object. This utility is trying to use an object class that is currently not defined in the Directory database. NetWare 4.0x  utilities only display valid object classes.

NetWare 4.1 (or later versions) allows the schema to be extended, so this error in NetWare 4.1 (or later versions) might point to schema synchronization problems.


-605  FFFFFFDA3  NO SUCH PARTITION

Explanation

A partition with the specified name does not exist. A partition in the Directory is named by the root object of the specified partition. The very first partition in the Directory is (Root) named by the tree name, which appears at the top of the directory.

Action

Ensure that the partition name requested is valid and is a valid object name.


-606  FFFFFFDA2  ENTRY ALREADY EXISTS

Explanation

An attempt was made to add an object at the same level as a preexisting object of the same name but not necessarily the same class.

Action

Specify a different name for the object being added or rename the existing object.


-607  FFFFFFDA1  NOT EFFECTIVE CLASS

Explanation

This error indicates that a noneffective class is being used to create the specified entry.

Noneffective classes cannot be used to create an entry. NetWare* Directory Services* (NDS) has two types of object classes: effective and noneffective. You can use all effective classes to create entries. (The base class of the object class is the class used to create the entry.) The class Users is one example of an effective class. You can use noneffective classes as super classes. These classes define information associated with various effective classes.

Action

The standard NetWare utilities that ship with NetWare 4.x  only allow effective classes to be used when creating objects. Find out what utility is being used to create the object. This utility is not following the rules of the specified object.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


-608  FFFFFFDA0  ILLEGAL ATTRIBUTE

Explanation

An attempt was made to add an attribute that is illegal to an object. The NetWare* Directory Services* (NDS) schema determines what attributes can be inherited by an object class. (Refer to the NetWare Directory Services Schema documentation, if it is available.)

This error can also occur in a mixed tree environment where both NetWare 4.0x  and NetWare 4.1 (or later version) servers exist or in an upgraded tree that has servers with an incorrect schema.

Action

Client: Use the Partition Continuity feature of NDS* Manager to detect whether any partitions in your Directory tree are returning errors.

Server: To resolve the problem, do the following action that applies:

Check to see if a problem exists with the object. To do this, use DSTRACE and the SET DSTRACE=+SYNC command.

If an error exists, try deleting the object in question.

If the object that has errors is a Server object, use NDS Manager to delete it. To delete objects besides Server objects, use NetWare Administrator.

If the problem is only on one server, use NDS Manager and run the Receive Updates option on the server with the error.

If errors were detected on a Server object, try running the Repair Local Database option from the Partition Continuity view in NDS Manager to remove the illegal attribute from that server. You can also repair local database using DSREPAIR.

If a mix of NetWare 4.x  servers exists in the tree or if a NetWare 4.1 (or later version) server was installed and then uninstalled in a NetWare 4.0x  tree, the error code might be due to a schema problem. Run the Global Schema Update option in DSREPAIR on a NetWare 4.1 (or later version) server.

If no NetWare 4.1 (or later version) servers are installed in the tree, or if the Global Schema Update option does not fix the problem, shut down the server holding the master replica of the partition returning the error, and then bring it back up. Upon starting up, the server forces a schema update, and this will usually correct a schema problem.

If the problem persists, contact a NetWare support provider.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


-609  FFFFFFD9F  MISSING MANDATORY

Explanation

One or more of the mandatory attributes for the object being created is missing. Each object class in the Directory has a set of mandatory attributes (attributes that must contain a value before the object can be created). For example, a User object in the Directory is required to have a Common Name (CN) and a Surname. Without these attributes, the object will not be created. An attribute exists only if there is a value specified for the given attribute.

This error can also occur in a mixed tree environment where both NetWare* 4.0x  and NetWare 4.1 (or later version) servers exist or in an upgraded tree that has servers with an incorrect schema.

Action

Client: You cannot add the specified attribute to the specified object.

Server: To solve the problem, do the action that applies:

Check to see if a problem exists with the object. To do this, use DSTRACE and the SET DSTRACE=+SYNC command.

If an error exists, try deleting the object in question.

If a mix of NetWare 4.x  servers exists in the tree, or if a NetWare 4.1 (or later version) server was installed and then uninstalled in a NetWare 4.0x  tree, the problem might be caused by a schema problem. Run the Global Schema Update option in DSREPAIR on a NetWare 4.1 (or later version) server.

If no NetWare 4.1 (or later version) servers are installed in the tree, or if the Global Schema Update option does not fix the problem, shut down the server holding the master replica of the partition returning the error, and then bring it back up. Upon starting up, the server forces a schema update, and this will usually correct a schema problem.

If the problem persists, contact a NetWare support provider.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


-610  FFFFFFD9E  ILLEGAL DS NAME

Explanation

Illegal NDS name. Illegal Directory names are those which are too long (more than 255 characters) or contain illegal character combinations. The "\" character can only be followed by

.

=

+

\

Action

Avoid using illegal characters or reduce the number of characters in the object's name.


-611  FFFFFFD9D  ILLEGAL CONTAINMENT

Explanation

The containment rules of the Directory specify where an object class might appear in relation to other objects in the Directory tree. An attempt to create an object violated these containment rules. For example, the object class Country can only be created at the top of the Directory, the object class User can only be created under Organization object containers and Organizational Unit object containers. The Schema enforces the containment rules for NetWare* Directory Services* (NDS).

This error might appear in NDS* Manager when moving a partition.

Action

Go to the appropriate container to create the object.

If the error occurs when moving a partition, check the containment rules for the partition root object.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


-612  FFFFFFD9C  CANT HAVE MULTIPLE VALUES

Explanation

The specified property is single valued. All properties are single or multi-valued. For example, the Group Membership property is multi-valued. A user can be a member of multiple groups. The Group Membership property exists once and contains multiple group names (values).

Action

For this property (information category in the utility) only one value (piece of information) can be supplied.


-613  FFFFFFD9B  SYNTAX VIOLATION

Explanation

This error occurs most often when an attribute value being added to an object is incorrect or when the value is pointing to an object that does not exist in the tree.

Action

Client: Verify that the object name being added as a value is correct.

Explanation

The error might also occur when a bindery-type object (usually created by a third-party program) becomes corrupt.

Action

If the -613 errors are on these types of objects, delete all objects created by the program, and then reinstall the program.

Explanation

This error is also seen during the install or upgrade to NetWare* 4.1 (or later versions).

Action

Client: If you are installing or upgrading to NetWare 4.1 (or later versions), run Partition Continuity in NDS Manager to view any synchronization errors on the partition that you are installing the server into. Using NDS Manager, run Repair Local Database on the server holding the master replica of the partition.

Server: If a new NetWare 4.1 (or later version) server hangs during installation while copying over the existing Directory objects, run DSTRACE on the server holding the master replica of the partition that you are installing the server into, by setting the SET DSTRACE=+SYNC command.

If an error exists, run DSREPAIR on the master.

If the problem still exists, run the SET DSTRACE=+SYNC command to find the object returning the error and check the description field (and any other field which accepts a string) for any unusual ASCII characters. Correct the corruption or delete the object, and the replica should complete copying to the new server.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


-614  FFFFFFD9A  DUPLICATE VALUE

Explanation

An attempt was made to add a duplicate value to the specified property.

Action

Enter a different value.


-615  FFFFFFD99  ATTRIBUTE ALREADY EXISTS

Explanation

An attempt was made to add an attribute that already exists.

Action

If the attribute is multi-valued, just add the specified value to the existing attribute.

If the attribute is single-valued, you will need to delete the attribute in order to create it again with the new value.


-616  FFFFFFD98  MAXIMUM ENTRIES EXIST

Explanation

The maximum entries (objects) exist in the Directory tree. The maximum number of objects that can be created in the Directory is FFFFFF (3 bits of FF), which equals 16,777,220 decimal.

Action

For the current version of the Directory, you have reached the maximum number of objects that can be created. To continue, delete objects that are no longer needed.


-617  FFFFFFD97  DATABASE FORMAT

Explanation

The database format is invalid.

Action

Client: From the Partition Continuity view in NDS* Manager, run Repair Local Database. If you run this option from the client, you might not need to run DSREPAIR from the server.

Server: Run DSREPAIR once. If this error persists after running DSREPAIR the first time, contact a NetWare* support provider.

Warning: By running DSREPAIR a second time, the original.OLD database files will be overwritten and it might not be possible to restore their former Directory Information Base (DIB).

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


-618  FFFFFFD96  INCONSISTENT DATABASE

Explanation

The server has detected an inconsistent database. Usually this means that the number of entries in a container does not match the number stored in the container's entry. When this error occurs during synchronization, the target server has a corrupted database.

Action

From the Partition Continuity view in NDS* Manager, run Repair Local Database on the target server. If you would rather work from the server console, run DSREPAIR once.

Warning: By running DSREPAIR a second time, the original.OLD database files will be overwritten and it might not be possible to restore their former Directory Information Base (DIB).

If this error persists after running DSREPAIR the first time, contact a NetWare support provider.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


-619  FFFFFFD95  INVALID COMPARISON

Explanation

An attempt was made to compare two properties that are not comparable or to use an invalid compare syntax.

Action

Check the syntax and verify that the properties are comparable.


-620  FFFFFFD94  COMPARISON FAILED

Explanation

A comparison of some kind failed.

Action

From the Partition Continuity view in NDS* Manager, run Repair Local Database on the target server. If you would rather work from the server console, run DSREPAIR once. If this error persists after running DSREPAIR the first time, contact a NetWare* support provider.

Warning: By running DSREPAIR a second time, the original.OLD database files will be overwritten and it might not be possible to restore their former Directory Information Base (DIB).

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


-621  FFFFFFD93  TRANSACTIONS DISABLED

Explanation

This error indicates that Transaction Tracking (TTS) has been disabled for the server on which the Directory operation is taking place. When TTS is disabled, Directory operations that require modifying the database on that server are disabled as well.

Action

At the console prompt of the server, type "ENABLE TTS". If TTS was disabled because volume SYS: is full, log in to the server and delete unnecessary files from volume SYS:, and then type ENABLE TTS at the console.

If you are unable to log in to the file server, try running VREPAIR on volume SYS: and selecting the Purge Deleted Files option from the VREPAIR menu. If there still is not enough space, put another drive into the server and span the volume SYS: across both drives to give volume SYS: more space.


-622  FFFFFFD92  INVALID TRANSPORT

Explanation

The type of transport passed in to the server is not supported by the server.

Action

Select a supported transport type and retry the operation.


-623  FFFFFFD91  SYNTAX INVALID IN NAME

Explanation

The syntax for the name provided is invalid.

Action

Reenter the name with the correct syntax.


-624  FFFFFFD90  REPLICA ALREADY EXISTS

Explanation

A replica of the specified partition already exists on the server.

Action

Select a different server. It is recommended that a partition should have no more than seven or eight replicas.


-625  FFFFFFD8F  TRANSPORT FAILURE

Explanation

The server is unable to communicate across the network. This error is almost always LAN-related.

This error usually occurs for one or more of the following reasons:

A server is down.

A bridge or other physical connection is down between servers.

A server cannot be found.

Occasionally the error might occur for one of the following reasons:.

A change to the server's name

A move of the server's object

A change to the internal IPX number

This error might also be seen when trying to communicate with servers that have databases that are locked by utilities such as NDS Manager, Install Maintenance Mode DSDUMP, or DSREPAIR.

Action

Perform some or all of the following actions until the error code disappears:

Check for SAP filtering of the DS SAP types of 26B and 278. Check cabling, the LAN card, and the LAN driver. Ensure that workstations can connect to the target server through RCONSOLE.

Ensure that the server can communicate with the target server. To verify whether they are communicating, type DISPLAY SERVERS on the source server.

Determine whether other servers are returning the -625 error for the same target server.

Ensure that the workstations can attach and log in to the target server from the same segment as the source server.

Flag all servers as UP by typing RESET ROUTERS, and then setting the SET DSTRACE=*U command at the source server. Then retry communicating with them.

At a client workstation, view the Partition Continuity screen in NDS Manager. If every source has an error on one target, and that target server is unable to connect as a source, check to see whether that server is down or whether its NDS database is locked.

Try to correct the internal IPX number on the target server.

To do this from a client workstation, select the source server in the Partition Continuity screen in NDS Manager. Then from the Repair menu, choose Repair Network Addresses.

To do this from the server, run DSREPAIR and select the Repair Network Addresses option on the source server.


-626  FFFFFFD8E  ALL REFERRALS FAILED

Explanation

The object could not be found. It is possible that the object exists, but the server could not communicate with the server holding a copy of the object. This error message is common when partition management is requested and events cannot occur because a server is inaccessible. This might be a temporary condition during partition functions.

Action

Perform all or some of the following actions until the error disappears:

From the Partition Continuity screen in NDS* Manager, run the Repair Network Addresses or Verify Remote Server IDs option. If you prefer to work from the server console, run the Repair Network Addresses option and Verify Remote Server ID Numbers option in DSREPAIR.

From the Partition Continuity screen in NDS Manager, verify that there is one master replica (in each row) for the partition in question.

Check the replica states and make sure they are all "ON."

Resolve whatever problems you find in the DSREPAIR.LOG file.

Run the DISPLAY SERVERS command and see whether the tree name is present. If not, check issues related to the -625 errors (including SAP filtering).

If creation time stamps are invalid, run the Check External References in NetWare* 4.1 (or later version) of DSREPAIR (under Advanced Option) to eliminate the problem.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


-627  FFFFFFD8D  CANT REMOVE NAMING VALUE

Explanation

An attempt was made to delete the naming property.

Action

Rename the object; then delete the property.


-628  FFFFFFD8C  OBJECT CLASS VIOLATION

Explanation

An object class violation has occurred. This violation might be caused by either of the following two reasons:

The objects on the source server are unknown but the object on the target server are correct.

A schema synchronization problem has occurred.

Action

If the error occurs when the objects on the source server are unknown but the objects on the target server are correct, do the following:

1.	Isolate the corrupted replica. You can do this by locking the databases with DSREPAIR, then running NETADMIN or NetWare* Administrator to view the objects.

2.	Make sure the master replica is not corrupted. If the master replica is not corrupted, delete the corrupted replica and add it back again using NDS* Manager.

If the master replica is corrupted, use NDS Manager to change the type of an uncorrupted replica to master (which automatically changes the old master to read/write).

If the error seems to be caused by a schema synchronization problem, do the following:

1.	Run the Global Schema Update option in DSREPAIR on a NetWare 4.1 (or later version) server.

2.	If no NetWare 4.1 (or later version) servers are in the tree, or if the Global Schema Update option does not fix the problem, shut down the server that has the master replica of the partition returning the error, and then bring it back up.

Upon starting up, the server will force a schema update, and the update will usually correct a schema problem.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


-629  FFFFFFD8B  ENTRY IS NOT LEAF

Explanation

The object being deleted or modified is not a leaf object. A container object that does not contain any objects is considered a leaf object, and therefore can be deleted. If you attempt to delete a container object that contains an object of any class, the following error will be returned: The utility can't delete Object Class=Object_name because it is not a leaf object. A container object that is a partition root cannot be deleted.

Action

Delete all objects under the container object that is being deleted or modified. If the object is a partition root, merge the partition with the parent partition using NDS* Manager, and then delete the object using NetWare* Administrator.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


-630  FFFFFFD8A  DIFFERENT TREE

Explanation

Different tree.

Action

Make sure you are performing operations on the correct Directory tree for the objects.


-631  FFFFFFD89  ILLEGAL REPLICA TYPE

Explanation

A replica needed to perform this function was not found. Typically you will receive this error when you attempt to set your bindery context at the server console and the server does not have a read/write replica of the container you are trying to reference in the bindery context.

Action

Use NDS Manager to add a replica that includes the bindery context to that server. Bindery context requires a writable replica (either a read/write or a master replica) in order to be set.

Verify that the server has a writable replica of the partition containing the container to which you are trying to set the bindery context.


-632  FFFFFFD88  SYSTEM FAILURE

Explanation

Unexpected results have occurred. For example, perhaps the client requested that the Directory return a network address attribute and the Directory actually returned a public key attribute. This condition might be temporary. While the client usually returns errors in the -301 to -399 range, the client as well as the server returns this error during the authentication process.

When a server returns a -632 during synchronization, it might occur because authentication could not complete due to an error in the public key, such as the key being corrupted (not the right format).

This error can also be returned by DSTRACE when the server is unable to open the local database. However, -632 is just a general error which means that the process being attempted failed. This also might be because the server or servers being contacted were busy or down, or because the source server could not authenticate to them.

After upgrading a server, the NDS* might be unable to open the database.

Action

Perform the following steps:

1.	From the client, use NDS Manager to view the Partition Continuity screen, or from the server set the SET DSTRACE=ON command, and then set the SET DSTRACE=+MISC command.

2.	Dismount and remount the volume SYS:.

3.	Check the DSTRACE screen and confirm that a -632 error is returned when NDS tries to open the database. If a -632 error is returned, the database is corrupted. Remove NDS from the server and reinstall from another replica in the tree or, if in a single server environment, from backup.

4.	Verify that all remote server ID numbers are valid. To do this, run the Verify Remote Server IDs option from the Partition Continuity view in NDS Manager (on the client) or DSREPAIR (on the server).

If the -602 or -603 error codes are returned, rerun the Verify Remote Server IDs option. If error codes -602 or -603 are returned again, contact a NetWare* support provider.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


-633  FFFFFFD87  INVALID ENTRY FOR ROOT

Explanation

An attempt was made to restore or move an object that is flagged as a partition root, but whose base class is not a container, or perform a split at an object whose base class is not a container.

Action

From the client, use the Partition Continuity feature in NDS* Manager to run Repair Local Database. Or, from the server, run DSREPAIR.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


-634  FFFFFFD86  NO REFERRALS

Explanation

The target server does not have a copy of what the source server is requesting. In other words, the source server has no objects that match the request and has no referrals on which to search for the object.

Action

This is not a serious error; it is just a response. This error will usually resolve itself.


-635  FFFFFFD85  REMOTE FAILURE

Explanation

This error might be caused because

The target server does not have the correct information about the source server. Not having the correct information is often caused by a problem with local to remote ID numbers or the Server object.

The source server is unable to contact another server needed to complete the operation for reason such as, a link or server being down.

For example, if you do a Receive Updates in DSREPAIR and the server with the master replica is down, this error will be returned.

Action

If you suspect that the target server does not have the correct information, do the following:

Verify that all remote server ID numbers are valid. To do this, run the Verify Remote Server IDs option from the Partition Continuity view in NDS* Manager (on the client) or DSREPAIR (on the server).

If the -602 or -603 error codes are returned, rerun the Verify Remote Server IDs option.

If error codes -602 or -603 are returned again, contact a NetWare* support provider.

If you suspect that the source server is unable to contact another server needed to complete the operation, do the following:

Check for and resolve all  -625 errors first.

Make sure all servers needed to complete an operation are up and communicating to each other.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


-636  FFFFFFD84  UNREACHABLE SERVER

Explanation

The server is unreachable. This error is almost always LAN-related. Occasionally a change of the server's name, a move of the server object, or a change to the internal IPX number can also cause this error. This error might also be seen when trying to communicate with servers that have databases that are locked utilities such as DSDUMP, DSMAINT, or DSREPAIR.

Action

Perform some or all of the following actions until the error codes disappear:

Check for SAP filtering of the DS SAP types of 26B and 278. Check cabling, the LAN card, and the LAN driver. Ensure that workstations can RCONSOLE to the target server.

Check to see whether the server can communicate with the target server. To do this, type DISPLAY SERVERS on the source server.

Determine whether other servers are returning the -625 error for the same target server.

Ensure that workstations can attach and log in to the target server from the same segment as the source server.

Flag all servers as UP by typing RESET ROUTERS, and then setting the SET DSTRACE=*U command at the source server. Then retry communicating with them.

Check the internal IPX number of the target server. To do this, run DSREPAIR with the option to repair network addresses on the source server.


-637  FFFFFFD83  PREVIOUS MOVE IN PROGRESS

Explanation

After an object has been moved from one context in the Directory tree to another, the Directory database will not allow that object to be moved again until all replicas of that object have been updated. The length of time will vary depending on the size of the replica, the number of replicas, and the condition of the communication links between all the servers holding the replicas.

This error can be caused by a moved object which lost the original object (the primary obituary) or by a broken partition.

Action

Leave the object in its current context until it can be moved again. This might require that the object be left in its new context for several minutes.

If the object still cannot be moved, load the NetWare* 4.1 (or later version) DSREPAIR with the "-m" parameter, and then run the Repair Local Database option.

If you are using a NetWare 4.0x  DSREPAIR, use the LOAD DSREPAIR -A command, then choose Select Options. Toggle A until it reads Find obituaries for move and move-inhibit.

Then, view the DSREPAIR.LOG file, which will display objects that have moved obituaries. Verify that the problem objects and all their attributes have successfully moved to the new location by running NetWare Administrator or NETADMIN and viewing the objects.

If the problem objects have moved successfully, load the NetWare 4.1 (or later version) DSREPAIR with the "-MR" parameters. If you are using a NetWare 4.0x DSREPAIR, use the LOAD DSREPAIR -A command, then choose Select Options. Toggle A until it reads Purge obituaries for move and move-inhibit which will then delete the move obituaries for those problem objects.

Verify that the purger ran successfully. To do this, use SET DSTRACE=+J and SET DSTRACE=*F commands.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


-638  FFFFFFD82  NO CHARACTER MAPPING

Explanation

No characters are mapped.

Action

Retry the operation, or contact a NetWare* support provider.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


-639  FFFFFFD81  INCOMPLETE AUTHENTICATION

Explanation

Authentication was incomplete.

Action

Retry the operation, or contact a NetWare* support provider.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


-640  FFFFFFD80  INVALID CERTIFICATE

Explanation

The server did not understand the request. For example, a request sent by a client workstation could be incorrect. This error can be caused by a non-synchronized schema.

Action

Run the Global Schema Update option in the NetWare* 4.1 (or later version) DSREPAIR. This error can also be a response error. Check for errors on the target server first, and resolve any errors you find.


-641  FFFFFFD7F  INVALID REQUEST

Explanation

The server did not understand the request. For example, a client workstation could have sent an incorrect call. This error could also be a response error or be caused by a non-synchronized schema.

Action

If a reponse error is suspected, check for errors on the target server first, and resolve any errors you find.

If a non-synchronized schema is suspected, run the Global Schema Update option in the NetWare* 4.1 (or later version) DSREPAIR.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


-642  FFFFFFD7E  INVALID ITERATION

Explanation

A client workstation sent an invalid iteration handle.

Action

See Reporting Error Code Problems to Novell.


-643  FFFFFFD7D  SCHEMA IS NONREMOVABLE

Explanation

An attempt was made to delete a NetWare* Directory Services* (NDS) structure or configuration.

Action

First delete the object or property; then delete the structure. If the error persists, contact a NetWare* support provider.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


-644  FFFFFFD7C  SCHEMA IS IN USE

Explanation

An attempt was made to delete a NetWare* Directory Services* (NDS) configuration or structure (such as a container object) that still contains an object using that structure.

Action

First delete the object or property; then delete the structure.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


-645  FFFFFFD7B  CLASS ALREADY EXISTS

Explanation

This error indicates that the object class being created already exists as a class in the schema of the Directory. See also error code -604.

Action

This error should only occur in a utility that updates the schema of the Directory database.

Determine which utility is causing the error.


-646  FFFFFFD7A  BAD NAMING ATTRIBUTES

Explanation

Invalid naming attributes were used.

Action

Use a different set of characters. If the error persists, contact a NetWare* support provider.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


-647  FFFFFFD79  NOT ROOT PARTITION

Explanation

An attempt was made to execute a function that is required on the root partition. The client did not pass in the root partition name, or the client tried to perform the function somewhere besides the root partition.

Action

Retry the operation. If the error persists, contact a NetWare* support provider.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


-648  FFFFFFD78  INSUFFICIENT STACK

Explanation

The server stack was not large enough.

Action

Increase the stack size on the server in question.


-649  FFFFFFD77  INSUFFICIENT BUFFER

Explanation

The server ran out of memory. The operating system will self-correct this error.

Action

Wait for the operating system to self-correct the error. See "Resolving Server Memory Problems" in Supervising the Network.


-650  FFFFFFD76  AMBIGUOUS CONTAINMENT

Explanation

An attempt was made to create an NDS* definition for a class that contained an ambiguous containment rule. This error can be caused by a non-synchronized schema. This error can also be a response error.

Action

Check for errors on the target server first, and resolve any errors found. If the error still occurs, run the Global Schema Update option in the NetWare* 4.1 (or later version) of DSREPAIR.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


-651  FFFFFFD75  AMBIGUOUS NAMING

Explanation

An attempt was made to create an NDS* definition for a class that contained an ambiguous containment name. This error can be a response error. This error can also be caused by a non-synchronized schema.

Action

Check for errors on the target server first, and resolve any errors found. If the error still occurs, run the Global Schema Update option in the NetWare* 4.1 (or later version) of DSREPAIR.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


-652  FFFFFFD74  DUPLICATE MANDATORY

Explanation

An attempt was made to create an NDS* definition for a class that contained a duplicate mandatory name. This error can be a response error. This error can also be caused by a non-synchronized schema.

Action

Check for errors on the target server first, and resolve any errors found. If the error still occurs, run the Global Schema Update option in the NetWare* 4.1 (or later version) of DSREPAIR.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


-653  FFFFFFD73  DUPLICATE OPTIONAL

Explanation

An attempt was made to create an NDS* definition for a class that contained a duplicate optional name. This error can be a response error. This error can also be caused by a non-synchronized schema.

Action

Check for errors on the target server first, and resolve any errors found. If the error still occurs, run the Global Schema Update option in the NetWare* 4.1 (or later version) of DSREPAIR.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


-654  FFFFFFD72  PARTITION BUSY

Explanation

Another partition operation is currently taking place. For example, if a request has previously been issued to split a partition, a second request for a split (even at another point in the same partition) will result in this error.

Action

Wait. This is a normal error immediately after a partition operation has been initiated.

If this error persists, check to see whether this error indicates that the target server does not recognize a replica of the partition on the source server.

Confirm this through the Partition Continuity screen of NDS* Manager, or through the DSREPAIR.LOG, or by watching DSTRACE.

If the partition remains busy for more than a few hours, try running PTEST on NetWare* 4.x  servers. Or on NetWare 4.1 (or later version) servers, abort the partition operation on the source server by choosing the Abort Partition Operation option in NDS Manager.

You can also remove the source server from the tree, or contact a NetWare support provider.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


-655  FFFFFFD71  MULTIPLE REPLICAS

Explanation

This is an internal error that appears as a result of a programming error, and not as a system inconsistency.

Action

Retry the operation. If the error persists, contact a NetWare* support provider.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


-656  FFFFFFD70  CRUCIAL REPLICA

Explanation

An attempt was made to perform one of the following illegal operations on a master replica:

Remove the master replica

Change the master replica's replica type (This operation can be done only by changing the replica type of another server's replica to the master, which will indirectly force the master to become a read/write.)

Request that the master replica receive all updates from the master

This error can also be caused by trying to add a replica to the server where the master of that replica already exists.

Action

Retry the operation. If the error persists, contact a NetWare* support provider.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


-657  FFFFFFD6F  SCHEMA SYNC IN PROGRESS

Explanation

The function could not be completed because Directory synchronization is in progress.

Action

Wait for synchronization to complete and try again.


-658  FFFFFFD6E  SKULK IN PROGRESS

Explanation

The function could not be completed because replica synchronization is in progress.

Action

Wait for synchronization to complete and try again.


-659  FFFFFFD6D  TIME NOT SYNCHRONIZED

Explanation

NetWare* Directory Services* uses time stamps to determine the order of events that take place in the Directory. Time Synchronization services have been implemented to maintain a consistent time across the network.

Modification operations require the issuance of a time stamp. If a replica on a server has issued a time stamp and the time on that server is set back, in NetWare 4.0x  no further modification operations can take place until the time on the server moves past the last modification time on the partition. This applies only to operations that modify, not those that just read information. In other words, users will be able to log in to the Directory tree, but no objects can be edited through the utilities.

In NetWare 4.1 (or later versions), the Directory database issues synthetic time stamps on objects to allow them to be modified, yet will still not allow illegal time stamps. The server console will display a synthetic time error when the server time is behind the NDS time.

Action

Warning: If the master copy was corrupt in any way, that corruption will be dispersed to the other replicas when a Repair Time Stamps or Receive Updates action is performed Repair Time Stamps and Receive Updates can also cause considerable traffic on the network. You might have to do this on a partition by partition basis.

Check DSTRACE for other errors first and resolve any errors you find. Then use the Repair Time stamps option in DSREPAIR. This option resets the time stamps to the current server time.

You can also use NDS Manager to perform Receive Updates on the server with the problem. This will delete all objects on the target server and recreate them from the master.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


-660  FFFFFFD6C  RECORD IN USE

Explanation

The requested record is already in use.

Action

Wait a until the record is available and try again.


-661  FFFFFFD6B  DS VOLUME NOT MOUNTED

Explanation

The NetWare* Directory Services* (NDS) volume is not mounted.

Action

Mount the volume SYS:, and retry the operation.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


-662  FFFFFFD6A  DS VOLUME IO FAILURE

Explanation

An I/O failure occurred on the NetWare* Directory Services* (NDS) volume.

Action

Identify the source of the problem; then retry the operation.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


-663  FFFFFFD69  DS LOCKED

Explanation

The Directory database is locked on the server. This error will be seen in DSTRACE when the source server is trying to synchronize with a target server that has a locked database.

On the server with the locked database, no activity will be in the DSTRACE screen.

This error occurs when

DSREPAIR is loaded on the on the server is performing an operation that has locked the Directory database.

DSDUMP has the Directory database locked.

The hard drive on the server is starting to fail.

A new 4.02 server install does not complete properly.

The server receives an error trying to open the Directory when mounting the volume SYS:.

Action

From the client, check to see whether DSREPAIR is loaded by going to the Partition Continuity screen in NDS Manager. From the Partition Continuity screen, run Repair Local Database.  At this point, if DSREPAIR is loaded, Partition Continuity will ask whether you want to unload DSREPAIR to perform the Repair Local Database option.

If DSREPAIR is not loaded, load DSREPAIR. If DSREPAIR is loaded, run the Repair Local Database option once. If the error persists after running DSREPAIR the first time, contact a NetWare support provider. If Repair Local Database is run a second time, the original.OLD database files will be overwritten and it might not be possible to restore their former Directory Information Base (DIB).

If running Repair Local Database does not fix the problem, try bringing down the server and bringing it back up again. If running Repair Local Database and bringing down the server do not fix this error, the server might need to be removed from the tree.

If this is a new server with no replicas on it, remove NDS from the server. If you do not want to remove NDS from the server, contact a NetWare support provider for alternative solutions.

Warning: If you remove NDS from a NetWare 4.01 server, you will lose trustee assignments. The trustee assignments are backed up for a NetWare 4.02 or NetWare 4.1 (or later version) server during removal of NDS.

When NDS is locked, the normal removal of NDS on a NetWare 4.02 server might not complete properly. You might need to load INSTALL with the -DSREMOVE switch, and then try to remove NDS through INSTALL.

Using the -DSREMOVE switch will most likely return an error stating that it was unable to remove NDS, but the removal will be performed anyway. To verify that the removal was performed, load INSTALL using the -DSREMOVE switch again and try removing NDS a second time. The DSI module should report that NDS was already removed from the server.

Warning: Do not use the -DSREMOVE switch unless the normal removal process does not work. The -DSREMOVE switch ignores errors and warnings and might not perform all the steps necessary to do a clean removal.

Warning: If you remove NDS from a NetWare 4.01 server, you will lose trustee assignments. The trustee assignments are backed up for a NetWare 4.02 or NetWare 4.1 (or later version) server during removal of NDS.


-664  FFFFFFD68  OLD EPOCH

Explanation

A NetWare* Directory Services* (NDS) time stamp error has occurred. It occurs when the Creation Time attribute for a given partition is not updated with the new, correct time.

An epoch is another name for partition.

Action

Repair the Local Database.

Two ways to do this are

From the Partition Continuity screen in NDS* Manager, run the Repair Local Database option.

From the server console, run DSREPAIR.


-665  FFFFFFD67  NEW EPOCH

Explanation

This is a NetWare* Directory Services* (NDS) time stamp error. It occurs when the Creation Time attribute for a given partition is not updated with the new, correct time.

An epoch is another name for partition.

Action

Repair the Local Database.

Two ways to do this are

From the Partition Continuity screen in NDS Manager, run the Repair Local Database option.

From the server console, run DSREPAIR.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


-666  FFFFFFD66  INCOMPATIBLE DS VERSION

Explanation

This error might occur if

You are performing operations requiring the same schema and the servers involved have dissimilar schema.

For example, when a partition operation is requested, NDS* Manager returns this error if the server with the master replica is running NetWare* 4.1 (or later versions) while other servers in the replica list are running NetWare 4.0x. Servers holding subordinate reference replicas with a dissimilar schema also generate this error.

Important: The version of NetWare Directory Services* (NDS) that shipped with NetWare 4.11 will not synchronize with NDS versions before 4.89.

NDS synchronization has been restricted using the Set NDS Synchronization Restrictions parameter at the server.

When running DSREPAIR for NetWare 4.1 (or later versions) and a remote to local ID check is being done.

Action

If the server holding the master replica is a NetWare 4.1 (or later version) server, most partition operations that involve updating replicas on NetWare 4.0x servers cannot be completed.

To be able to complete the partition operations, upgrade the NetWare 4.0x servers in the replica list to NetWare 4.1 (or later versions).

Note: If the master replica is on a NetWare 4.02 server, you will not have this problem.

If this error is seen in DSREPAIR during a remote to local ID check, perform the SET DSTRACE=!V command on the NetWare 4.1 (or later version) server. This resets a list that is maintained for restricting use of certain versions of NDS.

Make sure the SET NDS Synchronization Restrictions parameter has been used as explained in the "NetWare Directory Services Parameters" section of Utilities Reference.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


-667  FFFFFFD65  PARTITION ROOT

Explanation

This error indicates that the object being manipulated is the root of a Directory Services partition.

This error most commonly appears when trying to delete a container object that is a partition root.

This error might also occur during synchronization when a subordinate reference replica should exist and does not, or should not exist and does, or when a server has an incorrect partition entry.

Action

Although you cannot delete a container object that is a partition root, you can use NDS Manager to merge the partition into the parent partition.

If a subordinate reference replica exists when it should not, then from the Partition Continuity screen in NDS Manager, run the Repair Local Database option.


-668  FFFFFFD64  ENTRY NOT CONTAINER

Explanation

An illegal function was attempted on a leaf object.

Action

Retry the operation with legal functions.


-669  FFFFFFD63  FAILED AUTHENTICATION

Explanation

An invalid password was used or authentication failed. This error also occurs when one server tries to synchronize with another one and the target server's database is locked. This error commonly occurs when problems exist with the remote ID or the public key.

Action

Run the Verify Remote Server IDs option from the Partition Continuity screen in NDS* Manager, or from the server console using DSREPAIR, on the source server and all other servers in the replica list. If errors occur in the DSREPAIR.LOG file, rerun the Verify Remote Server IDs option in NDS Manager or DSREPAIR on every server in the replica list. This should correct a problem with the remote ID being incorrect.

The other scenario is when the source server is using or looking at the wrong public key (the key is the right format, but is for the wrong object). If the problem is the public key, then do one of the following:

If the source server has a master replica, read/write replica, or read-only replica of the target server object, then ensure that all other servers in the replica list are able to authenticate to the target server.

Note: Using the Send All Objects option generates a high level of network traffic.

If another server can authenticate, then do a Send All Objects from the correct server, or Receive All Objects on the target server (but only if the server with the correct copy has the master replica).

Make sure that you do not send copies containing incorrect public keys.

If no servers can authenticate to the target server, remove NDS from the target server and reinstall it back into the tree, or contact a NetWare* support provider.

If the source server has a subordinate reference replica, or if no replica of the partition containing the target server object exists, then the external reference to that object needs to be backlinked again. Contact a NetWare support provider.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


-670  FFFFFFD62  INVALID CONTEXT

Explanation

An invalid context was used to reference an object.

Action

Determine the appropriate context for the object, and retry the operation.


-671  FFFFFFD61  NO SUCH PARENT

Explanation

A parent object was specified that does not exist.

Action

Run DSREPAIR. If the error persists, contact a NetWare* support provider.


-672  FFFFFFD60  NO ACCESS

Explanation

The client does not have sufficient rights to complete the requested operation. For servers, this error in DSTRACE means that the replica list for the target server does not match the replica list for the source server.

Action

Compare the replica ring information for all the servers in the replica list by viewing the Partition Continuity of the partition in NDS* Manager. Or, from the server console, use the Display Replica Information option in DSREPAIR.

If you confirm that the target server does not have the source server in its replica list, then remove NDS from the target server, or contact a NetWare* support provider.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


-673  FFFFFFD5F  REPLICA NOT ON

Explanation

The replica has an operation in progress and is in an intermediate state. Until all the object information has been received on that server, the replica is not on, meaning that the replica is not available to Directory clients.

Action

Wait. If the replica does not appear to be completing the operation, identify the error that is preventing the replica from turning "ON," and then correct that error. Or contact a NetWare* support provider.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


-674  FFFFFFD5E  INVALID NAME SERVICE

Explanation

NetWare* Directory Services* (NDS) does not support the name server that you are using. This is an internal error caused by the client's management of the context.

Action

See Reporting Error Code Problems to Novell.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


-675  FFFFFFD5D  INVALID TASK

Explanation

An invalid NDS operation was performed. This is an internal error caused by the client's management of the context.

Action

See Reporting Error Code Problems to Novell.


-676  FFFFFFD5C  INVALID CONN HANDLE

Explanation

An invalid CONN handle was issued. This is an internal error caused by the client's management of the context.

Action

See Reporting Error Code Problems to Novell.


-677  FFFFFFD5B  INVALID IDENTITY

Explanation

An invalid object identity was received. This is an internal error caused by the client's management of the context.

Action

See Reporting Error Code Problems to Novell.


-678  FFFFFFD5A  DUPLICATE ACL

Explanation

An ACL for the object already exists. This usually happens only while merging a tree. The error indicates that the context is invalid.

Action

Open and close the Directory database. The error should resolve itself.


-679  FFFFFFD59  PARTITION ALREADY EXISTS

Explanation

An attempt was made to create a partition that already exists.

Action

Create a new partition with a different name.


-680  FFFFFFD58  TRANSPORT MODIFIED

Explanation

An attempt was made to use a reference that is not a subordinate reference.

Action

See Reporting Error Code Problems to Novell.


-681  FFFFFFD57  ALIAS OF AN ALIAS

Explanation

An attempt was made to use an alias of an alias.

Action

Identify the target object and create a new Alias object.


-682  FFFFFFD56  AUDITING FAILED

Explanation

The auditing function failed.

Action

See Reporting Error Code Problems to Novell.


-683  FFFFFFD55  INVALID API VERSION

Explanation

An invalid application API is being used.

Action

Update software to conform with the latest API set.


-684  FFFFFFD54  SECURE NCP VIOLATION

Explanation

An attempt was made to forge an NCP packet signature on a server that has packet signing ON. The server expected to receive a signed packet from a client and did not receive one.

Action

Identify the application that is submitting the packet and disable the application.


-685  FFFFFFD53  MOVE IN PROGRESS

Explanation

The replica is in the process of being moved to another server. Until all the object information has been received on that server, the replica is locked.

Action

Wait. If the replica does not appear to be completing the operation, identify the error that is preventing the replica from completing the "move" operation, and then correct that error. Or contact a NetWare* support provider.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


-686  FFFFFFD52  NOT LEAF PARTITION

Explanation

A subtree can be moved only if it is a leaf partition.

Action

Using the Tree View in NDS* Manager, make sure no partitions are subordinate to the one being moved. If subordinate partitions are in the tree, use NDS Manger to merge them with the partition you want to move. The partitions can be made subordinate partitions again after the Move Partition operation is complete.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


-687  FFFFFFD51  CANNOT ABORT

Explanation

This error occurs when you try to abort one of the following options:

Changing the replica type when the state of the replica does not display in NDS Manager (or DSTRACE) that the replica type is changing or that the change is not in an initial state.

Splitting a partition when the state of the replica does not display in NDS Manager (or DSTRACE) that the partition is splitting or that the split is not in an initial state.

Joining partitions when the state of the parent partition does not display in NDS Manager (or DSTRACE) that the partition is in the joining state with the partition in the request.

Moving a subtree when the move has proceeded past the initial move subtree state.

Action

Wait for the operation to complete. Then reverse the operation.


-688  FFFFFFD50  CACHE OVERFLOW

Explanation

A cache overflow was experienced on the target server.

Action

See Reporting Error Code Problems to Novell.


-689  FFFFFFD4F  INVALID SUBORDINATE COUNT

Explanation

This error indicates an inconsistent entry.

Action

Client:

From the Partition Continuity screen in NDS Manager, run Repair Local Database.

Server:

From the server console, run DSREPAIR.


-690  FFFFFFD4E  INVALID RDN

Explanation

This error indicates an inconsistent entry.

Action

Client:

From the Partition Continuity screen in NDS* Manager, run the Repair Local Database option.

Server:

From the server console, run DSREPAIR.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


-691  FFFFFFD4D  MOD TIME NOT CURRENT

Explanation

This error indicates an inconsistent entry.

Action

Client:	From the Partition Continuity screen in NDS Manager, run Repair Local Database.

Server: From the server console, run DSREPAIR.


-692  FFFFFFD4C  INCORRECT BASE CLASS

Explanation

This error indicates an inconsistent entry.

Action

From the Partition Continuity screen in NDS Manager, run the Repair Local Database option. Or, from the server console, run DSREPAIR.


-693  FFFFFFD4B  MISSING REFERENCE

Explanation

A required reference is missing from the object. This error is frequently seen in the NetWare* 4.1 (or later version) utilities when trying to delete an object with a creation time stamp value of zero.

Action

From the Partition Continuity screen in NDS* Manager, run the Repair Local Database option. Or, from the server console, run DSREPAIR.

This will give objects with missing creation time stamps a valid time stamp. If the object continues to give a -693 error during deletion, then there is still a server in that partition's replica list with a creation time stamp of zero for that object. Run Repair Local Database in NDS Manager, or from the server console, run DSREPAIR on each server in that partition's replica list.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


-694  FFFFFFD4A  LOST ENTRY

Explanation

NetWare* Directory Services* (NDS) cannot update an entry that has not yet been received as a new entry.

Action

See Reporting Error Code Problems to Novell.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


-695  FFFFFFD49  AGENT ALREADY REGISTERED

Explanation

NDS cannot update an entry that has not yet been received as a new entry.

Action

See Reporting Error Code Problems to Novell.


-696  FFFFFFD48  DS LOADER BUSY

Explanation

NDS cannot update an entry that has not yet been received as a new entry.

Action

See Reporting Error Code Problems to Novell.


-697  FFFFFFD47  DS CANNOT RELOAD

Explanation

The DS.NLM program cannot reload on the target server, possibly because there is not enough memory on the server.

Action

If this error occurs while performing NDS Version Update in NDS* Manager, do the following:

1.	Make a backup of SYS:SYSTEM.

2.	Copy a new DS.NLM program to the SYS:SYSTEM directory.

3.	Unload and reload DS.NLM program.

If the problem persists, contact a NetWare* support provider.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


-698  FFFFFFD46  REPLICA IN SKULK

Explanation

A server is currently synchronizing with another server in the replica ring. The replica is busy skulking and no other replica processes will be done until the skulk has completed.

Action

Usually this error will occur as a normal part of a partition operation and will resolve itself. If this error does not go away, check for other errors that might be preventing the partition operation from completing successfully. Remember that the master replica is controlling all partition operations.


-699  FFFFFFD45  FATAL

Explanation

An unrecoverable error has occurred and the operation cannot be completed. This error can be caused by a variety of problems.

Action

Go to the target server and look for a response TRACE error (turn off the DSTRACE filters by using a setting like FFFF6FF7 or 8164B19 in NetWare* 4.0x or an 8164b91 in NetWare 4.1 or later versions).

Sometimes you will see an error without an error code (such as "skulk lost entry") that can also be important. Resolve the error on the target server. Treat a "skulk lost entry" error the same as a -601 error.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


-700  FFFFFFD44  OBSOLETE API

Explanation

The client made a request that is no longer supported by NetWare* Directory Services* (NDS).

Action

Obtain an updated version of the program that is compatible with the current version of NDS*.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


-701  FFFFFFD43  SYNCHRONIZATION DISABLED

Explanation

Schema synchronization has been disabled by an API (or DSTRACE = !S0) call.

Action

Enable schema synchronization through the API or by using the command, SET DSTRACE = !S1.


-702  FFFFFFD42  INVALID PARAMETER

Explanation

An invalid parameter was passed to an internal NetWare* Directory Services* (NDS) function.

Action

Retry the operation.

If it fails again, the Directory Information Base (DIB) might be corrupted. In this case, from the Partition Continuity screen in NDS* Manager, run the Repair Local Database option. Or, from the server console, run DSREPAIR.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


-703  FFFFFFD41  DUPLICATE TEMPLATE

Explanation

A server using NDS 4.02 or earlier versions might have tried to synchronize duplicate ACL templates.

Action

See Reporting Error Code Problems to Novell.


-704  FFFFFFD40  NO MASTER REPLICA

Explanation

This message is currently not used.

Action

See Reporting Error Code Problems to Novell.


-705  FFFFFFD3F  DUPLICATE CONTAINMENT

Explanation

Schema synchronization from a server with NDS 4.02 or earlier might have tried to add containment for a class that already exists.

Action

See Reporting Error Code Problems to Novell.


-706  FFFFFFD3E  NOT SIBLING

Explanation

NetWare* Directory Services* (NDS) tried to merge two entries that are not siblings (do not have the same parent container). The client API might have passed an incorrect parameter.

Action

Specify the correct parameters (in this case, the Entry IDs) in the DSAMergeEntries API.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


-707  FFFFFFD3D  INVALID SIGNATURE

Explanation

An invalid signature was received.

Action

See Reporting Error Code Problems to Novell.


-708  FFFFFFD3C  INVALID RESPONSE

Explanation

An invalid response was received.

Action

See Reporting Error Code Problems to Novell.


-709  FFFFFFD3B  INSUFFICIENT SOCKETS

Explanation

Insufficient sockets are available.

Action

See Reporting Error Code Problems to Novell.


-710  FFFFFFD3A  DATABASE READ FAIL

Explanation

An attempt to read the database failed.

Action

See Reporting Error Code Problems to Novell.


-711  FFFFFFD39  INVALID CODE PAGE

Explanation

An invalid code page exists.

Action

See Reporting Error Code Problems to Novell.


-712  FFFFFFD38  INVALID ESCAPE CHAR

Explanation

Invalid escape characters exist.

Action

See Reporting Error Code Problems to Novell.


-713  FFFFFFD37  INVALID DELIMITERS

Explanation

Invalid delimiters exist.

Action

See Reporting Error Code Problems to Novell.


-714  FFFFFFD36  NOT IMPLEMENTED

Explanation

The operation was not implemented.

Action

See Reporting Error Code Problems to Novell.


-715  FFFFFFD35  CHECKSUM FAILURE

Explanation

A checksum failure occurred.

Action

See Reporting Error Code Problems to Novell.


-716  FFFFFFD34  CHECKSUMMING NOT SUPPORTED

Explanation

Checksumming is not supported.

Action

See Reporting Error Code Problems to Novell.


-717  FFFFFFD33  CRC FAILURE

Explanation

A failure of the Cyclical Redundancy Check (CRC) occurred.

Action

See Reporting Error Code Problems to Novell.


0x000F  DOS INVALID DRIVE

Explanation

An attempt was made to use an invalid (undefined or unavailable) DOS drive.

Action

See Reporting Error Code Problems to Novell.


0x8800  ALREADY ATTACHED

Explanation

The user is already attached to the server.

Action

See Reporting Error Code Problems to Novell.


0x8800  Multiple causes

Explanation

NetWare could not identify the exact cause of this error.

Possible causes for this error are

ALREADY ATTACHED

VLM ERROR


0x8800  VLM ERROR

Explanation

A VLM error has occurred.

Action

See Reporting Error Code Problems to Novell.


0x8801  CONN INVALID

Explanation

A request was attempted with an invalid or nonattached connection handle.

Action

See Reporting Error Code Problems to Novell.


0x8802  DRIVE IN USE

Explanation

The drive is in use. (OS2 only, not used)

Action

See Reporting Error Code Problems to Novell.


0x8803  DRIVE CANNOT MAP

Explanation

An attempt to map a drive was unsucessful. It could not add a new current directory structure.

Action

See Reporting Error Code Problems to Novell.


0x8804  DRIVE BAD PATH

Explanation

An attempt was made to map a drive with an invalid path specification.

Action

See Reporting Error Code Problems to Novell.


0x8805  NET RECEIVE

Explanation

An attempt to receive from the selected transport failed.

Action

See Reporting Error Code Problems to Novell.


0x8806  NET UNKNOWN

Explanation

A network send request was attempted, but a nonspecific error occurred.

Action

See Reporting Error Code Problems to Novell.


0x8807  SERVER BAD SLOT

Explanation

A server request was attempted with an invalid server connection slot.

Action

See Reporting Error Code Problems to Novell.


0x8808  SERVER NO SLOTS

Explanation

An attempt was made to attach to a server with no connection slots available.

Action

See Reporting Error Code Problems to Novell.


0x8809  NET SEND

Explanation

An attempt to send on the selected transport failed.

Action

See Reporting Error Code Problems to Novell.


0x880A  SERVER NO ROUTE

Explanation

An attempt was made to find a route to a server where no route exists.

Action

See Reporting Error Code Problems to Novell.


0x880B  BAD LOCAL TARGET

Explanation

An invalid local target was specified (for OS/2 only).

Action

See Reporting Error Code Problems to Novell.


0x880C  REQ TOO MANY REQ FRAGS

Explanation

A request was attempted with too many request fragments specified.

Action

See Reporting Error Code Problems to Novell.


0x880D  CONN LIST OVERFLOW

Explanation

Too many connections exist to fit in the list size specified.

Action

See Reporting Error Code Problems to Novell.


0x880E  BUFFER OVERFLOW

Explanation

An attempt was made to receive more data than the reply buffer had room for.

Action

See Reporting Error Code Problems to Novell.


0x880F  SERVER NO CONN

Explanation

An attempt to get connection for a server failed. The workstation is not connected.

Action

See Reporting Error Code Problems to Novell.


0x8810  NO ROUTER FOUND

Explanation

No router was found (OS/2 only).

Action

See Reporting Error Code Problems to Novell.


0x8811  FUNCTION INVALID

Explanation

A function call was tried to a nonexistent or illegal function.

Action

See Reporting Error Code Problems to Novell.


0x8812  LIP RESIZE ERROR

Explanation

A Large Internet Packet (LIP) resize error occurred.

Action

See Reporting Error Code Problems to Novell.


0x8812  Multiple causes

Explanation

NetWare could not identify the exact cause of this error.

Possible causes for this error are

LIP RESIZE ERROR

SCAN COMPLETE


0x8812  SCAN COMPLETE

Action

See Reporting Error Code Problems to Novell.


0x8813  INVALID DIR HANDLE

Action

See Reporting Error Code Problems to Novell.


0x8813  Multiple causes

Explanation

NetWare could not identify the exact cause of this error.

Possible causes for this error are

INVALID DIR HANDLE

UNSUPPORTED NAME FORMAT TYP


0x8813  UNSUPPORTED NAME FORMAT TYP

Action

See Reporting Error Code Problems to Novell.


0x8814  HANDLE ALREADY LICENSED

Explanation

An application attempted to license a connection that was already licensed. An application can only license or unlicense a connection once without getting an error.

Action

See Reporting Error Code Problems to Novell.


0x8814  Multiple causes

Explanation

NetWare could not identify the exact cause of this error.

Possible causes for this error are

HANDLE ALREADY LICENSED

OUT OF CLIENT MEMORY


0x8814  OUT OF CLIENT MEMORY

Explanation

The client is out of memory.

Action

See Reporting Error Code Problems to Novell.


0x8815  HANDLE ALREADY UNLICENSED

Explanation

An application attempted to unlicense a connection that was already unlicensed. An application can only license or unlicense a connection once without getting an error.

Action

See Reporting Error Code Problems to Novell.


0x8815  Multiple causes

Explanation

NetWare could not identify the exact cause of this error.

Possible causes for this error are

HANDLE ALREADY UNLICENSED

PATH NOT OURS


0x8815  PATH NOT OURS

Explanation

An attempt was made to specify a path that NetWare* does not recognize.

Action

See Reporting Error Code Problems to Novell.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


0x8816  INVALID NCP PACKET LENGTH

Explanation

The NCP packet length is invalid.

Action

See Reporting Error Code Problems to Novell.


0x8816  Multiple causes

Explanation

NetWare could not identify the exact cause of this error.

Possible causes for this error are

INVALID NCP PACKET LENGTH

PATH IS PRINT DEVICE


0x8816  PATH IS PRINT DEVICE

Explanation

An attempt was made to write to a path that is a print device.

Action

See Reporting Error Code Problems to Novell.


0x8817  Multiple causes

Explanation

NetWare could not identify the exact cause of this error.

Possible causes for this error are

PATH IS EXCLUDED DEVICE

SETTING UP TIMEOUT


0x8817  PATH IS EXCLUDED DEVICE

Explanation

An attempt was made to specify a path to a device that is excluded.

Action

See Reporting Error Code Problems to Novell.


0x8817  SETTING UP TIMEOUT

Action

See Reporting Error Code Problems to Novell.


0x8818  Multiple causes

Explanation

NetWare could not identify the exact cause of this error.

Possible causes for this error are

PATH IS INVALID

SETTING SIGNALS


0x8818  PATH IS INVALID

Explanation

An attempt was made to access a path that is invalid.

Action

See Reporting Error Code Problems to Novell.


0x8818  SETTING SIGNALS

Action

See Reporting Error Code Problems to Novell.


0x8819  Multiple causes

Explanation

NetWare could not identify the exact cause of this error.

Possible causes for this error are

NOT SAME DEVICE

SERVER CONNECTION LOST


0x8819  NOT SAME DEVICE

Explanation

The device is not the same.

Action

See Reporting Error Code Problems to Novell.


0x8819  SERVER CONNECTION LOST

Action

See Reporting Error Code Problems to Novell.


0x881A  OUT OF HEAP SPACE

Action

See Reporting Error Code Problems to Novell.


0x881B  INVALID SEARCH HANDLE

Action

See Reporting Error Code Problems to Novell.


0x881B  INVALID SERVICE REQUEST

Explanation

The service request is invalid.

Action

See Reporting Error Code Problems to Novell.


0x881B  Multiple causes

Explanation

NetWare could not identify the exact cause of this error.

Possible causes for this error are

INVALID SEARCH HANDLE

INVALID SERVICE REQUEST


0x881C  INVALID DEVICE HANDLE

Action

See Reporting Error Code Problems to Novell.


0x881C  INVALID TASK NUMBER

Explanation

The task number is invalid.

Action

See Reporting Error Code Problems to Novell.


0x881C  Multiple causes

Explanation

NetWare could not identify the exact cause of this error.

Possible causes for this error are

INVALID DEVICE HANDLE

INVALID TASK NUMBER


0x881D  INVALID MESSAGE LENGTH

Explanation

The message length is invalid.

Action

See Reporting Error Code Problems to Novell.


0x881D  INVALID SEM HANDLE

Action

See Reporting Error Code Problems to Novell.


0x881D  Multiple causes

Explanation

NetWare could not identify the exact cause of this error.

Possible causes for this error are

INVALID MESSAGE LENGTH

INVALID SEM HANDLE


0x881E  EA SCAN DONE

Explanation

An Equal Access (EA) scan is done.

Action

See Reporting Error Code Problems to Novell.


0x881E  INVALID CFG HANDLE

Action

See Reporting Error Code Problems to Novell.


0x881E  Multiple causes

Explanation

NetWare could not identify the exact cause of this error.

Possible causes for this error are

EA SCAN DONE

INVALID CFG HANDLE


0x881F  BAD CONNECTION NUMBER

Explanation

An attempt has been made to connect to a server with a bad connection number.

Action

See Reporting Error Code Problems to Novell.


0x881F  INVALID MOD HANDLE

Action

See Reporting Error Code Problems to Novell.


0x881F  Multiple causes

Explanation

NetWare could not identify the exact cause of this error.

Possible causes for this error are

BAD CONNECTION NUMBER

INVALID MOD HANDLE


0x8820  ASYN FIRST PASS

Action

See Reporting Error Code Problems to Novell.


0x8820  MULT TREES NOT SUPPORTED

Explanation

Multiple trees are not supported.

Action

See Reporting Error Code Problems to Novell.


0x8820  Multiple causes

Explanation

NetWare could not identify the exact cause of this error.

Possible causes for this error are

ASYN FIRST PASS

MULT TREES NOT SUPPORTED


0x8821  INVALID DEVICE INDEX

Action

See Reporting Error Code Problems to Novell.


0x8822  INVALID CONN HANDLE

Explanation

An invalid CONN handle was issued.

Action

See Reporting Error Code Problems to Novell.


0x8823  INVALID QUEUE ID

Action

See Reporting Error Code Problems to Novell.


0x8824  INVALID PDEVICE HANDLE

Action

See Reporting Error Code Problems to Novell.


0x8825  INVALID JOB HANDLE

Action

See Reporting Error Code Problems to Novell.


0x8826  INVALID ELEMENT ID

Action

See Reporting Error Code Problems to Novell.


0x8827  ALIAS NOT FOUND

Explanation

An alias is not found.

Action

See Reporting Error Code Problems to Novell.


0x8828  RESOURCE SUSPENDED

Explanation

The resource is suspended.

Action

See Reporting Error Code Problems to Novell.


0x8829  INVALID QUEUE SPECIFIED

Action

See Reporting Error Code Problems to Novell.


0x882A  DEVICE ALREADY OPEN

Explanation

The device is already open.

Action

See Reporting Error Code Problems to Novell.


0x882B  JOB ALREADY OPEN

Explanation

The job is already open.

Action

See Reporting Error Code Problems to Novell.


0x882C  QUEUE NAME ID MISMATCH

Explanation

The queue name has a mismatched ID.

Action

See Reporting Error Code Problems to Novell.


0x882D  JOB ALREADY STARTED

Explanation

The job already has been started.

Action

See Reporting Error Code Problems to Novell.


0x882E  SPECT DAA TYPE NOT SUPPORTED

Explanation

The specified Data Access Arrangement (DAA) type is not supported.

Action

See Reporting Error Code Problems to Novell.


0x882F  INVALID ENVIR HANDLE

Action

See Reporting Error Code Problems to Novell.


0x8830  CONN NOT SAME

Explanation

An internal server request was attempted across different server connections.

Action

See Reporting Error Code Problems to Novell.


0x8831  CONN PRIMARY NOT SET

Explanation

An attempt was made to retrieve a default connection with no primary connection set.

Action

See Reporting Error Code Problems to Novell.


0x8832  KEYWORD NOT FOUND

Explanation

A keyword is not found.

Action

See Reporting Error Code Problems to Novell.


0x8832  Multiple causes

Explanation

NetWare could not identify the exact cause of this error.

Possible causes for this error are

KEYWORD NOT FOUND

PRN CAPTURE NOT IN PROGRESS


0x8832  PRN CAPTURE NOT IN PROGRESS

Explanation

Capture information was requested on a port with no capture in progress.

Action

See Reporting Error Code Problems to Novell.


0x8833  BUFFER INVALID LEN

Explanation

The length that the caller requested was too large.

Action

See Reporting Error Code Problems to Novell.


0x8834  USER NO NAME

Action

See Reporting Error Code Problems to Novell.


0x8835  PRN NO LOCAL SPOOLER

Explanation

Capture was requested without a local print spooler installed.

Action

See Reporting Error Code Problems to Novell.


0x8836  PARAM INVALID

Explanation

A function was attempted with an invalid function parameter specified.

Action

See Reporting Error Code Problems to Novell.


0x8837  CFG OPEN FAILED

Explanation

An attempt to open the configuration file failed (for OS/2 only).

Action

See Reporting Error Code Problems to Novell.


0x8838  CFG NO FILE

Explanation

No configuration file can be found (for OS/2 only).

Action

See Reporting Error Code Problems to Novell.


0x8839  CFG READ FAILED

Explanation

An attempt to read a file failed (for OS/2 only).

Action

See Reporting Error Code Problems to Novell.


0x883A  CFG LINE TOO LONG

Explanation

A line in the configuration file is too long (for OS/2 only).

Action

See Reporting Error Code Problems to Novell.


0x883B  CFG LINES IGNORED

Explanation

One or more lines in the configuration file were ignored (for OS/2 only).

Action

See Reporting Error Code Problems to Novell.


0x883C  RESOURCE NOT OWNED

Explanation

A request was made with a parameter using a foreign resource.

Action

See Reporting Error Code Problems to Novell.


0x883D  DAEMON INSTALLED

Explanation

No information for this error code is available (for OS/2 only).

Action

See Reporting Error Code Problems to Novell.


0x883E  PRN SPOOLER INSTALLED

Explanation

An attempt was made to load the print spooler, but the print spooler was already installed.

Action

See Reporting Error Code Problems to Novell.


0x883F  CONN TABLE FULL

Explanation

The system tried to allocate a connection handle, but no more local connection table entries were available.

Action

See Reporting Error Code Problems to Novell.


0x8840  CFG SECTION NOT FOUND

Explanation

The configuration section was not found (for OS/2 only).

Action

See Reporting Error Code Problems to Novell.


0x8841  TRAN INVALID TYPE

Explanation

An attempt was made to execute a function on a connection with an invalid transport selected.

Action

See Reporting Error Code Problems to Novell.


0x8842  TDS TAG IN USE

Explanation

A Tagged Data Store (TDS) tag is already in use (for OS/2 only).

Action

See Reporting Error Code Problems to Novell.


0x8843  TDS OUT OF MEMORY

Explanation

The computer does not have enough available RAM (for OS/2 only).

Action

See Reporting Error Code Problems to Novell.


0x8844  TDS INVALID TAG

Explanation

A Tagged Data Store (TDS) function was attempted with an invalid tag.

Action

See Reporting Error Code Problems to Novell.


0x8845  TDS WRITE TRUNCATED

Explanation

A Tagged Data Store (TDS) write was tried to a buffer that exceeded the buffer's size.

Action

See Reporting Error Code Problems to Novell.


0x8846  DS NO CONN

Explanation

No NetWare* Directory Services* (NDS) connections exists.

Action

See Reporting Error Code Problems to Novell.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


0x8846  Multiple causes

Explanation

NetWare could not identify the exact cause of this error.

Possible causes for this error are

DS NO CONN

SERVICE BUSY


0x8846  SERVICE BUSY

Explanation

A request was tried to a busy, partially asynchronous function.

Action

See Reporting Error Code Problems to Novell.


0x8847  SERVER NOT FOUND

Explanation

The attempt to connect failed to find any servers responding.

Action

See Reporting Error Code Problems to Novell.


0x8848  VLM INVALID

Explanation

An attempted function call was made to a nonexistent or not-loaded overlay.

Action

See Reporting Error Code Problems to Novell.


0x8849  DRIVE ALREADY MAPPED

Explanation

An attempt was made to map to a network drive that was already mapped.

Action

See Reporting Error Code Problems to Novell.


0x884A  DRIVE LOCAL IN USE

Explanation

An attempt was made to map to a local drive that was in use.

Action

See Reporting Error Code Problems to Novell.


0x884B  DRIVE NONE AVAILABLE

Explanation

An attempt was made to map to the next available drive when no drive was available.

Action

See Reporting Error Code Problems to Novell.


0x884C  DEVICE NOT REDIRECTED

Explanation

The device was not redirected.

Action

See Reporting Error Code Problems to Novell.


0x884D  FILE MAX REACHED

Explanation

The maximum number of files has been reached.

Action

See Reporting Error Code Problems to Novell.


0x884E  UNLOAD FAILED

Explanation

An attempted unload failed.

Action

See Reporting Error Code Problems to Novell.


0x884F  CONN IN USE

Explanation

An attempt was made to reuse a connection entry that was already in use.

Action

See Reporting Error Code Problems to Novell.


0x8850  REQ TOO MANY REP FRAGS

Explanation

An attempted request had too many reply fragments specified.

Action

See Reporting Error Code Problems to Novell.


0x8851  NAME TABLE FULL

Explanation

An attempted request was made to add a name into the name table after the table was full.

Action

See Reporting Error Code Problems to Novell.


0x8852  SOCKET NOT OPEN

Explanation

A listen was posted on an unopened socket.

Action

See Reporting Error Code Problems to Novell.


0x8853  MEMORY MGR ERROR

Explanation

An attempted enhanced memory operation failed.

Action

See Reporting Error Code Problems to Novell.


0x8854  SFT3 ERROR

Explanation

An SFT III switch occurred during mid transfer.

Action

See Reporting Error Code Problems to Novell.


0x8855  DS PREFERRED NOT FOUND

Explanation

A preferred directory server was not established, but another directory server was returned.

Action

See Reporting Error Code Problems to Novell.


0x8856  DEVICE NOT RECOGNIZED

Explanation

The device is unknown.

Action

Determine if the device is not used by the NetWare* DOS Requester; pass to next redirector, if any.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


0x8857  NET INVALID TYPE

Action

See Reporting Error Code Problems to Novell.


0x8858  FILE OPEN FAILED

Action

See Reporting Error Code Problems to Novell.


0x8859  DS PREFERRED NOT SPECIFIED

Explanation

A preferred directory server was not specified.

Action

See Reporting Error Code Problems to Novell.


0x885A  Multiple causes

Explanation

NetWare could not identify the exact cause of this error.

Possible causes for this error are

REQUESTER FAILURE

SOCKET OPEN FAILED


0x885A  REQUESTER FAILURE

Explanation

A requester failure has occurred.

Action

See Reporting Error Code Problems to Novell.


0x885A  SOCKET OPEN FAILED

Action

See Reporting Error Code Problems to Novell.


0x885B  RESOURCE ACCESS DENIED

Explanation

Access to the resource is denied.

Action

See Reporting Error Code Problems to Novell.


0x8861  SIGNATURE LEVEL CONFLICT

Action

See Reporting Error Code Problems to Novell.


0x8862  NO LOCK FOUND

Explanation

An attempt was made to remove a lock, but no lock was found.

Action

See Reporting Error Code Problems to Novell.


0x8863  LOCK TABLE FULL

Explanation

The lock table is full.

Action

See Reporting Error Code Problems to Novell.


0x8864  INVALID MATCH DATA

Explanation

The match data is invalid.

Action

See Reporting Error Code Problems to Novell.


0x8865  MATCH FAILED

Explanation

The match failed.

Action

See Reporting Error Code Problems to Novell.


0x8866  NO MORE ENTRIES

Action

See Reporting Error Code Problems to Novell.


0x8867  INSUFFICIENT RESOURCES

Explanation

The resources are insufficient to perform the requested operation.

Action

See Reporting Error Code Problems to Novell.


0x8867  INSUFFICIENT SPACE

Explanation

The station does not have sufficient disk space.

Action

See Reporting Error Code Problems to Novell.


0x8868  STRING TRANSLATION

Action

See Reporting Error Code Problems to Novell.


0x8869  ACCESS VIOLATION

Explanation

An access violation has occurred.

Action

See Reporting Error Code Problems to Novell.


0x886A  NOT AUTHENTICATED

Action

See Reporting Error Code Problems to Novell.


0x886B  INVALID LEVEL

Explanation

The level is invalid.

Action

See Reporting Error Code Problems to Novell.


0x886C  RESOURCE LOCK

Action

See Reporting Error Code Problems to Novell.


0x886D  INVALID NAME FORMAT

Explanation

The name format is invalid.

Action

See Reporting Error Code Problems to Novell.


0x886E  OBJECT EXISTS

Action

See Reporting Error Code Problems to Novell.


0x886E  UNSUPPORTED AUTHENTICATOR

Action

See Reporting Error Code Problems to Novell.


0x886F  OBJECT NOT FOUND

Explanation

An attempt was made to access an object, but the object was not found.

Action

See Reporting Error Code Problems to Novell.


0x8870  UNSUPPORTED TRAN TYPE

Action

See Reporting Error Code Problems to Novell.


0x8871  INVALID STRING TYPE

Explanation

The string type is invalid.

Action

See Reporting Error Code Problems to Novell.


0x8872  INVALID OWNER

Explanation

The owner is invalid.

Action

See Reporting Error Code Problems to Novell.


0x8874  IO PENDING

Explanation

The I/O is pending.

Action

See Reporting Error Code Problems to Novell.


0x8875  INVALID DRIVE NUMBER

Explanation

The drive number is invalid.

Action

See Reporting Error Code Problems to Novell.


0x8880  SVC ALREADY REGISTERED

Explanation

The session for the Switched Virtual Circuit (SVC) is already registered.

Action

See Reporting Error Code Problems to Novell.


0x8881  SVC REGISTRY FULL

Explanation

The Switched Virtual Circuit (SVC) registry is full.

Action

See Reporting Error Code Problems to Novell.


0x8882  SVC NOT REGISTERED

Explanation

The Switched Virtual Circuit (SVC) is not registered.

Action

See Reporting Error Code Problems to Novell.


0x8883  OUT OF RESOURCES

Explanation

No resources are available.

Action

See Reporting Error Code Problems to Novell.


0x8884  RESOLVE SVC FAILED

Explanation

An attempt to resolve the Switched Virtual Circuit (SVC) failed.

Action

See Reporting Error Code Problems to Novell.


0x8885  CONNECT FAILED

Explanation

The connection failed.

Action

See Reporting Error Code Problems to Novell.


0x8886  PROTOCOL NOT BOUND

Explanation

The protocol is not bound.

Action

See Reporting Error Code Problems to Novell.


0x8887  AUTHENTICATION FAILED

Action

See Reporting Error Code Problems to Novell.


0x8888  INVALID AUTHEN HANDLE

Action

See Reporting Error Code Problems to Novell.


0x8889  AUTHEN HANDLE ALREADY EXISTS

Explanation

An authentication handle already exists.

Action

See Reporting Error Code Problems to Novell.


0x8890  DIFF OBJECT ALREADY AUTHEN

Action

See Reporting Error Code Problems to Novell.


0x8891  REQUEST NOT SERVICEABLE

Explanation

The requester is not serviceable.

Action

See Reporting Error Code Problems to Novell.


0x8892  AUTO RECONNECT SO REBUILD

Action

See Reporting Error Code Problems to Novell.


0x8893  AUTO RECONNECT RETRY REQUEST

Action

See Reporting Error Code Problems to Novell.


0x8894  ASYNC REQUEST IN USE

Action

See Reporting Error Code Problems to Novell.


0x8895  ASYNC REQUEST CANCELED

Action

See Reporting Error Code Problems to Novell.


0x8896  SESS SVC ALREADY REGISTERED

Explanation

The session for the Switched Virtual Circuit (SVC) is already registered.

Action

See Reporting Error Code Problems to Novell.


0x8897  SESS SVC NOT REGISTERED

Explanation

The session for the Switched Virtual Circuit (SVC) is not registered.

Action

See Reporting Error Code Problems to Novell.


0x8899  PREVIOUSLY AUTHENTICATED

Action

See Reporting Error Code Problems to Novell.


0x889A  RESOLVE SVC PARTIAL

Explanation

An attempt to resolve the Switched Virtual Circuit (SVC) is partial.

Action

See Reporting Error Code Problems to Novell.


0x889B  NO DEFAULT SPECIFIED

Explanation

No default was specified.

Action

See Reporting Error Code Problems to Novell.


0x889C  HOOK REQUEST NOT HANDLED

Action

See Reporting Error Code Problems to Novell.


0x889D  HOOK REQUEST BUSY

Action

See Reporting Error Code Problems to Novell.


0x889E  AUTO RECONNECT SO IGNORE

Action

See Reporting Error Code Problems to Novell.


0x889F  ASYNC REQUEST NOT IN USE

Action

See Reporting Error Code Problems to Novell.


0x88A0  AUTO RECONNECT FAILURE

Explanation

An auto reconnect failure occurred.

Action

See Reporting Error Code Problems to Novell.


0x88A1  ERROR ABORT APPLICATION

Explanation

An application was aborted due to a network error.

Action

See Reporting Error Code Problems to Novell.


0x88A2  ERROR SUSPEND APPLICATION

Explanation

An application was suspended due to a network error.

Action

See Reporting Error Code Problems to Novell.


0x88A3  ERROR ABORTED PROCESS GROUP

Explanation

A process group was aborted due to a network error.

Action

See Reporting Error Code Problems to Novell.


0x88A5  ERROR PASSWORD HAS EXPIRED

Explanation

The user's password has expired.

Action

See Reporting Error Code Problems to Novell.


0x88A6  ERROR NETWORK INACTIVE

Explanation

The network is inactive.

Action

See Reporting Error Code Problems to Novell.


0x88FF  REQUESTER FAILURE

Explanation

 An unknown error has occurred, or the shell or VLM program is not present.

Action

See Reporting Error Code Problems to Novell.


0x8977  BUFFER TOO SMALL

Explanation

The data to be passed back is too large for the buffer that was declared.

Action

See Reporting Error Code Problems to Novell.


0x8978  VOL FLAG NOT SET

Explanation

The volume flag has not been set.

Action

See Reporting Error Code Problems to Novell.


0x8979  NO ITEMS FOUND

Explanation

A request for items failed because the items could not be found, for example, during a bindery request.

Action

See Reporting Error Code Problems to Novell.


0x897A  CONN ALREADY TEMP

Explanation

An attempt was made to convert a connection to temporary that was already temporary.

Action

See Reporting Error Code Problems to Novell.


0x897B  CONN ALREADY LOGGED IN

Explanation

The connection is already logged in to the Directory.

Action

See Reporting Error Code Problems to Novell.


0x897C  CONN NOT AUTHENTICATED

Explanation

The connection for a call has not been authenticated.

Action

See Reporting Error Code Problems to Novell.


0x897D  CONN NOT LOGGED IN

Explanation

An attempt was made to log out of a connection that the user was not logged in to.

Action

See Reporting Error Code Problems to Novell.


0x897E  NCP BOUNDARY CHECK FAILED

Explanation

The NCP subfunction size does not match the actual size of the data sent.

Action

See Reporting Error Code Problems to Novell.


0x897F  LOCK WAITING

Explanation

A timeout occurred before a file was locked.

Action

See Reporting Error Code Problems to Novell.


0x8980  FILE IN USE

Explanation

An attempt was made to open or create a file that is already open.

Action

See Reporting Error Code Problems to Novell.


0x8980  LOCK FAIL

Explanation

An attempt was made to open or create a file that is already open.

Action

See Reporting Error Code Problems to Novell.


0x8980  Multiple causes

Explanation

NetWare could not identify the exact cause of this error.

Possible causes for this error are

FILE IN USE

LOCK FAIL


0x8981  FILE NO HANDLES

Explanation

No more file handles are available; the network file handle table is full.

Action

See Reporting Error Code Problems to Novell.


0x8982  FILE NO OPEN PRIV

Explanation

An attempt was made to open a file without the Open right.

Action

See Reporting Error Code Problems to Novell.


0x8983  DISK IO ERROR

Explanation

A hard disk input/output error occurred on a NetWare* volume; a bad sector has been encountered and could be fatal.

Action

See Reporting Error Code Problems to Novell.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


0x8984  FILE NO CREATE PRIV

Explanation

An attempt was made to create a file without the Create right.

Action

See Reporting Error Code Problems to Novell.


0x8985  FILE NO CREATE DEL PRIV

Explanation

An attempt was made to create an already existing file without the Create/Delete rights.

Action

See Reporting Error Code Problems to Novell.


0x8986  DIR TARGET INVALID

Action

See Reporting Error Code Problems to Novell.


0x8986  FILE EXISTS READ ONLY

Explanation

An attempt was made to create a file with the same name as an already existing file with Read Only status.

Action

See Reporting Error Code Problems to Novell.


0x8986  Multiple causes

Explanation

NetWare could not identify the exact cause of this error.

Possible causes for this error are

DIR TARGET INVALID

FILE EXISTS READ ONLY


0x8987  FILE WILD CARDS IN NAME

Explanation

An attempt was made to create a file using an ambiguous filename.

Action

See Reporting Error Code Problems to Novell.


0x8988  FILE INVALID HANDLE

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).

Action

See Reporting Error Code Problems to Novell.


0x8989  FILE NO SRCH PRIV

Explanation

An attempt was made to search a directory without search rights in that directory.

Action

See Reporting Error Code Problems to Novell.


0x898A  FILE NO DEL PRIV

Explanation

An attempt was made to delete a file without file deletion privileges in that file's directory.

Action

See Reporting Error Code Problems to Novell.


0x898B  FILE NO RENAME PRIV

Explanation

An attempt was made to rename a file without renaming privileges in that file's directory.

Action

See Reporting Error Code Problems to Novell.


0x898C  FILE NO MOD PRIV

Explanation

An attempt was made to modify a file without attribute modification privileges in that file's directory.

Action

See Reporting Error Code Problems to Novell.


0x898D  FILE SOME IN USE

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.

Action

See Reporting Error Code Problems to Novell.


0x898E  FILE NONE IN USE

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.

Action

See Reporting Error Code Problems to Novell.


0x898F  FILE SOME READ ONLY

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.

Action

See Reporting Error Code Problems to Novell.


0x8990  FILE NONE READ ONLY

Explanation

An attempt was made to delete, rename, or set file attributes using a filename when all the files specified have Read Only status.

Action

See Reporting Error Code Problems to Novell.


0x8991  FILE SOME RENAMED EXIST

Explanation

An attempt was made to rename files when one or more files matching the new filename specification already exist.

Action

See Reporting Error Code Problems to Novell.


0x8992  FILE NONE RENAMED EXIST

Explanation

An attempt was made to rename files when all the files matching the new filename specification already exist.

Action

See Reporting Error Code Problems to Novell.


0x8993  FILE NO READ PRIV

Explanation

An attempt was made to read a file without Read privileges to that file.

Action

See Reporting Error Code Problems to Novell.


0x8994  FILE NO WRITE PRIV

Explanation

An attempt was made to write to a file without Write privileges to that file, or the specified file has Read Only status.

Action

See Reporting Error Code Problems to Novell.


0x8994  FILE READ ONLY

Explanation

An attempt was made to write to a file without Write privileges to that file, or the specified file has Read Only status.

Action

See Reporting Error Code Problems to Novell.


0x8994  Multiple causes

Explanation

NetWare could not identify the exact cause of this error.

Possible causes for this error are

FILE NO WRITE PRIV

FILE READ ONLY


0x8995  FILE DETACHED

Explanation

An attempt was made to read or write to a detached file.

Action

See Reporting Error Code Problems to Novell.


0x8996  SERVER OUT OF MEMORY

Explanation

An attempt was made to write to a file server that does not have enough free dynamic memory to process the specified request.

Action

See Reporting Error Code Problems to Novell.


0x8997  DISK NO SPOOL SPACE

Explanation

The network operating system has determined that the network disk does not have enough space left for spool files.

Action

See Reporting Error Code Problems to Novell.


0x8998  VOL INVALID

Explanation

The network operating system has tried to access a volume but cannot find the volume in the system definition files.

Action

See Reporting Error Code Problems to Novell.


0x8999  DIR FULL

Explanation

An attempt was made to write to a volume without available directory space.

Action

See Reporting Error Code Problems to Novell.


0x899A  VOL RENAMING ACROSS

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.

Action

See Reporting Error Code Problems to Novell.


0x899B  DIRHANDLE INVALID

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.

Action

See Reporting Error Code Problems to Novell.


0x899C  Multiple causes

Explanation

NetWare could not identify the exact cause of this error.

Possible causes for this error are

PATH INVALID

TRUSTEES NO MORE


0x899C  PATH INVALID

Explanation

An attempt was made to access an invalid path.

Action

See Reporting Error Code Problems to Novell.


0x899C  TRUSTEES NO MORE

Action

See Reporting Error Code Problems to Novell.


0x899D  DIRHANDLE NO MORE

Explanation

No more directory handles are available; the directory handle table is full. Each user may have up to 255 directory handles.

Action

See Reporting Error Code Problems to Novell.


0x899E  FILE NAME INVALID

Explanation

An attempt was made to create a file using invalid characters within the name of the file.

Action

Enter the file name again using valid characters.


0x899F  DIR ACTIVE

Explanation

An attempt was made to delete a directory that is being used by another workstation.

Action

See Reporting Error Code Problems to Novell.


0x89A0  DIR NOT EMPTY

Explanation

An attempt was made to delete a directory that contains files or other directories.

Action

See Reporting Error Code Problems to Novell.


0x89A1  DIR IO ERROR

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.

Action

See Reporting Error Code Problems to Novell.


0x89A2  FILE IO LOCKED

Explanation

An attempt was made to read a file where data is physically locked.

Action

See Reporting Error Code Problems to Novell.


0x89A3  Multiple causes

Explanation

NetWare could not identify the exact cause of this error.

Possible causes for this error are

TTS TRANSACTION RESTARTED

TRANSACTION RESTARTED

TTS RANSACTION RESTARTED


0x89A3  TRANSACTION RESTARTED

Explanation

Transaction tracking was restarted.

Action

See Reporting Error Code Problems to Novell.


0x89A3  TTS RANSACTION RESTARTED

Explanation

Transaction tracking already has been restarted.

Action

See Reporting Error Code Problems to Novell.


0x89A3  TTS TRANSACTION RESTARTED

Action

See Reporting Error Code Problems to Novell.


0x89A4  DIR RENAME INVALID

Explanation

An attempt was made to rename a directory with an invalid name.

Action

See Reporting Error Code Problems to Novell.


0x89A5  FILE OPENCREAT MODE INVALID

Action

See Reporting Error Code Problems to Novell.


0x89A6  ALREADY IN USE

Explanation

An attempt was made to access a file that was already in use.

Action

See Reporting Error Code Problems to Novell.


0x89A7  RESOURCE TAG INVALID

Explanation

An invalid resource tag was encountered.

Action

See Reporting Error Code Problems to Novell.


0x89A8  ACCESS DENIED

Explanation

Access has been denied.

Action

See Reporting Error Code Problems to Novell.


0x89BE  DATA STREAM INVALID

Explanation

Data streams are invalid.

Action

See Reporting Error Code Problems to Novell.


0x89BF  NAME SPACE INVALID

Explanation

An invalid name space was used.

Action

See Reporting Error Code Problems to Novell.


0x89C0  ACCTING NO PRIV

Explanation

The user has no accounting privileges.

Action

See Reporting Error Code Problems to Novell.


0x89C1  ACCTING NO BALANCE

Explanation

Attempt was made to log in by a bindery object without an accounting balance, and accounting is enabled.

Action

See Reporting Error Code Problems to Novell.


0x89C2  ACCTING NO CREDIT

Explanation

An attempt was made to log in to an account with no credit available.

Action

See Reporting Error Code Problems to Novell.


0x89C3  ACCTING TOO MANY HOLDS

Action

See Reporting Error Code Problems to Novell.


0x89C4  ACCTING DISABLED

Explanation

Accounting has been disabled.

Action

See Reporting Error Code Problems to Novell.


0x89C5  LOGIN LOCKOUT

Explanation

An attempt was made to log in after the system had locked the account because of intruder detection.

Action

See Reporting Error Code Problems to Novell.


0x89C6  CONSOLE NO PRIV

Explanation

An attempt was made to use console privileges without operator privileges.

Action

See Reporting Error Code Problems to Novell.


0x89D0  Q IO FAILURE

Explanation

A queue I/O error occurred.

Action

See Reporting Error Code Problems to Novell.


0x89D1  Q NONE

Explanation

No queues are defined.

Action

See Reporting Error Code Problems to Novell.


0x89D2  Q NO SERVER

Explanation

No queue server has been specified.

Action

See Reporting Error Code Problems to Novell.


0x89D3  Q NO RIGHTS

Action

See Reporting Error Code Problems to Novell.


0x89D4  Q FULL

Explanation

The queue is full.

Action

See Reporting Error Code Problems to Novell.


0x89D5  Q NO JOB

Explanation

No jobs are in the queue.

Action

See Reporting Error Code Problems to Novell.


0x89D6  Multiple causes

Explanation

NetWare could not identify the exact cause of this error.

Possible causes for this error are

PASSWORD UNENCRYPTED

Q NO JOB RIGHT


0x89D6  PASSWORD UNENCRYPTED

Action

See Reporting Error Code Problems to Novell.


0x89D6  Q NO JOB RIGHTS

Explanation

The user does not have rights to this job in the queue.

Action

See Reporting Error Code Problems to Novell.


0x89D7  Multiple causes

Explanation

NetWare could not identify the exact cause of this error.

Possible causes for this error are

PASSWORD NOT UNIQUE

Q IN SERVICE


0x89D7  PASSWORD NOT UNIQUE

Explanation

An attempt was made to change a password to a previously used password when the unique requirement is specified for the account.

Action

See Reporting Error Code Problems to Novell.


0x89D7  Q IN SERVICE

Explanation

The queue is in service at this time.

Action

See Reporting Error Code Problems to Novell.


0x89D8  Multiple causes

Explanation

NetWare could not identify the exact cause of this error.

Possible causes for this error are

PASSWORD TOO SHORT

Q NOT ACTIVE


0x89D8  PASSWORD TOO SHORT

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.


0x89D8  Q NOT ACTIVE

Explanation

The queue is not active at this time.

Action

See Reporting Error Code Problems to Novell.


0x89D9  LOGIN MAX EXCEEDED

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.

Action

See Reporting Error Code Problems to Novell.


0x89D9  LOGIN NO CONN

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.

Action

See Reporting Error Code Problems to Novell.


0x89D9  Multiple causes

Explanation

NetWare could not identify the exact cause of this error.

Possible causes for this error are

LOGIN MAX EXCEEDED

LOGIN NO CONN

Q STN NOT SERVER


0x89D9  Q STN NOT SERVER

Explanation

The queue station is not a server.

Action

See Reporting Error Code Problems to Novell.


0x89DA  LOGIN UNAUTHORIZED TIME

Explanation

An attempt was made to log in during an unauthorized time of day specified for the account.

Action

See Reporting Error Code Problems to Novell.


0x89DA  Multiple causes

Explanation

NetWare could not identify the exact cause of this error.

Possible causes for this error are

LOGIN UNAUTHORIZED TIME

Q HALTED


0x89DA  Q HALTED

Explanation

The queue has been halted.

Action

See Reporting Error Code Problems to Novell.


0x89DB  LOGIN UNAUTHORIZED STATION

Explanation

An attempt was made to log into an unauthorized station.

Action

See Reporting Error Code Problems to Novell.


0x89DB  Multiple causes

Explanation

NetWare could not identify the exact cause of this error.

Possible causes for this error are

LOGIN UNAUTHORIZED STATION

Q MAX SERVERS


0x89DB  Q MAX SERVERS

Explanation

This queue is already attached to the maximum number of servers allowed.

Action

See Reporting Error Code Problems to Novell.


0x89DC  ACCT DISABLED

Explanation

An attempt was made to log in using an account that has expired or has been disabled by the supervisor.

Action

See Reporting Error Code Problems to Novell.


0x89DE  PASSWORD INVALID

Explanation

An attempt was made to log in using an account password that has expired, and all grace logins have also expired.

Action

See Reporting Error Code Problems to Novell.


0x89DF  PASSWORD EXPIRED

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.

Action

See Reporting Error Code Problems to Novell.


0x89E0  LOGIN NO CONN AVAIL

Explanation

No login connection is available.

Action

See Reporting Error Code Problems to Novell.


0x89E7  E NO MORE USERS

Explanation

No more users exists.

Action

See Reporting Error Code Problems to Novell.


0x89E8  BIND NOT ITEM PROP

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.

Action

See Reporting Error Code Problems to Novell.


0x89E8  BIND WRITE TO GROUP PROP

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.

Action

See Reporting Error Code Problems to Novell.


0x89E8  Multiple causes

Explanation

NetWare could not identify the exact cause of this error.

Possible causes for this error are

BIND NOT ITEM PROP

BIND WRITE TO GROUP PROP


0x89E9  BIND MEMBER ALREADY EXISTS

Explanation

An attempt was made to add an object to a group property that already exists.

Action

See Reporting Error Code Problems to Novell.


0x89EA  BIND NO SUCH MEMBER

Explanation

An attempt was made to use an object that is not a member of the defined group property.

Action

See Reporting Error Code Problems to Novell.


0x89EB  BIND NOT GROUP PROP

Explanation

An attempt was made to use a nongroup property.

Action

See Reporting Error Code Problems to Novell.


0x89EC  BIND NO SUCH SEGMENT

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.

Action

See Reporting Error Code Problems to Novell.


0x89ED  BIND PROP ALREADY EXISTS

Explanation

An attempt was made to create a property that already exists.

Action

See Reporting Error Code Problems to Novell.


0x89EE  BIND OBJ ALREADY EXISTS

Explanation

An attempt was made to create an object that already exists.

Action

See Reporting Error Code Problems to Novell.


0x89EF  BIND NAME INVALID

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

Explanation

An attempt was made to use a wildcard character or wild object type in a call where wildcards are not allowed.

Action

See Reporting Error Code Problems to Novell.


0x89F1  BIND SECURITY INVALID

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.

Action

See Reporting Error Code Problems to Novell.


0x89F2  BIND OBJ NO READ PRIV

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.

Action

See Reporting Error Code Problems to Novell.


0x89F3  BIND OBJ NO RENAME PRIV

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.

Action

See Reporting Error Code Problems to Novell.


0x89F4  BIND OBJ NO DELETE PRIV

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.

Action

See Reporting Error Code Problems to Novell.


0x89F5  BIND OBJ NO CREATE PRIV

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.

Action

See Reporting Error Code Problems to Novell.


0x89F6  BIND PROP NO DELETE PRIV

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.

Action

See Reporting Error Code Problems to Novell.


0x89F7  BIND PROP NO CREATE PRIV

Explanation

An attempt was made to create a property without the necessary property rights for the object.

Action

See Reporting Error Code Problems to Novell.


0x89F8  BIND PROP NO WRITE PRIV

Action

See Reporting Error Code Problems to Novell.


0x89F9  BIND PROP NO READ PRIV

Explanation

An attempt was made to read without the necessary Read rights to access the property data.

Action

See Reporting Error Code Problems to Novell.


0x89F9  Multiple causes

Explanation

NetWare could not identify the exact cause of this error.

Possible causes for this error are

BIND PROP NO READ PRIV

NO FREE CONN SLOTS


0x89F9  NO FREE CONN SLOTS

Explanation

No connection slots are available.

Action

See Reporting Error Code Problems to Novell.


0x89FA  Multiple causes

Explanation

NetWare could not identify the exact cause of this error.

Possible causes for this error are

NO MORE SERVER SLOTS

TEMP REMAP ERROR


0x89FA  NO MORE SERVER SLOTS

Explanation

No server slots are available.

Action

See Reporting Error Code Problems to Novell.


0x89FA  TEMP REMAP ERROR

Explanation

An attempt was made to use an unknown path.

Action

See Reporting Error Code Problems to Novell.


0x89FB  BIND NO SUCH PROP

Explanation

An attempt was made to use a property that does not exist for the specified object.

Action

See Reporting Error Code Problems to Novell.


0x89FB  Multiple causes

Explanation

NetWare could not identify the exact cause of this error.

Possible causes for this error are

BIND NO SUCH PROP

NCP NOT SUPPORTED

PARAMETERS INVALID


0x89FB  NCP NOT SUPPORTED

Action

See Reporting Error Code Problems to Novell.


0x89FB  PARAMETERS INVALID

Explanation

An attempt was made to use an invalid parameter (drive number, path, or flag value) during a set drive path call.

Action

See Reporting Error Code Problems to Novell.


0x89FC  BIND NO SUCH OBJ

Explanation

An attempt was made to use an object that could not be found in the context specified.

Action

See Reporting Error Code Problems to Novell.


0x89FC  INET PACKET REQ CANCELED

Action

See Reporting Error Code Problems to Novell.


0x89FC  MSG Q FULL

Explanation

An attempt was made to use a full message queue.

Action

See Reporting Error Code Problems to Novell.


0x89FC  Multiple causes

Explanation

NetWare could not identify the exact cause of this error.

Possible causes for this error are

BIND NO SUCH OBJ

INET PACKET REQ CANCELED

MSG Q FULL

SERVER UNKNOWN


0x89FC  SERVER UNKNOWN

Explanation

An attempt was made to attach to a server using an invalid server name.

Action

See Reporting Error Code Problems to Novell.


0x89FD  CONN NUM INVALID

Explanation

An attempt was made to use a bad (undefined, unavailable, etc.) station number.

Action

See Reporting Error Code Problems to Novell.


0x89FD  LOCK COLLISION

Action

See Reporting Error Code Problems to Novell.


0x89FD  Multiple causes

Explanation

NetWare could not identify the exact cause of this error.

Possible causes for this error are

CONN NUM INVALID

LOCK COLLISION

PACKET LEN INVALID

UNKNOWN REQ


0x89FD  PACKET LEN INVALID

Explanation

The requesting packet did not have a 30 byte packet header as the first fragment, or its total length exceeded 576 characters.

Action

See Reporting Error Code Problems to Novell.


0x89FD  UNKNOWN REQ

Explanation

An unknown request was attempted.

Action

See Reporting Error Code Problems to Novell.


0x89FE  BIND LOCKED

Explanation

An attempt was made to use a server with a locked bindery.

Action

See Reporting Error Code Problems to Novell.


0x89FE  DIR LOCKED

Explanation

An attempt was made to use a locked directory.

Action

See Reporting Error Code Problems to Novell.


0x89FE  LOGIN DISABLED BY SUPER

Explanation

An attempt was made to log in when the supervisor has disabled logins from the console or the bindery was locked.

Action

See Reporting Error Code Problems to Novell.


0x89FE  Multiple causes

Explanation

NetWare could not identify the exact cause of this error.

Possible causes for this error are

BIND LOCKED

DIR LOCKED

LOGIN DISABLED BY SUPER

PACKET NOT DELIVERABLE

SEM INVALID NAME LEN

SOCKET TABLE FULL

SPOOL DIR ERROR

TIMEOUT FAILURE

TRUSTEE NOT FOUND


0x89FE  PACKET NOT DELIVERABLE

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.

Action

See Reporting Error Code Problems to Novell.


0x89FE  SEM INVALID NAME LEN

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.

Action

See Reporting Error Code Problems to Novell.


0x89FE  SOCKET TABLE FULL

Action

See Reporting Error Code Problems to Novell.


0x89FE  SPOOL DIR ERROR

Explanation

An error occurred while spooling the directory.

Action

See Reporting Error Code Problems to Novell.


0x89FE  TIMEOUT FAILURE

Explanation

A failure occurred that was caused by the timeout limit expiring before the request was fulfilled.

Action

See Reporting Error Code Problems to Novell.


0x89FE  TRUSTEE NOT FOUND

Explanation

An operation tried to use an unknown trustee.

Action

See Reporting Error Code Problems to Novell.


0x89FF  BAD RECORD OFFSET

Explanation

The program tried to use an invalid offset value during physical locking calls.

Action

See Reporting Error Code Problems to Novell.


0x89FF  BAD SPOOL PRINTER

Explanation

An attempt was made to use a bad (undefined, unavailable, etc.) printer.

Action

See Reporting Error Code Problems to Novell.


0x89FF  DRIVE INVALID NUM

Explanation

An attempt was made to use a drive with an invalid number.

Action

See Reporting Error Code Problems to Novell.


0x89FF  FAILURE

Explanation

A failure has occurred.

Action

See Reporting Error Code Problems to Novell.


0x89FF  FCB CLOSE

Explanation

An error occurred closing the file.

Action

See Reporting Error Code Problems to Novell.


0x89FF  FILE EXT

Explanation

An attempt was made to use a file with a bad (undefined, unavailable, etc.) name or extension.

Action

See Reporting Error Code Problems to Novell.


0x89FF  FILE NAME

Explanation

An attempt was made to use a file with a bad (undefined, unavailable, etc.) name or extension.

Action

See Reporting Error Code Problems to Novell.


0x89FF  HARD FAILURE

Explanation

A hardware failure occurred.

Action

See Reporting Error Code Problems to Novell.


0x89FF  IO BOUND

Explanation

The program tried to write beyond the end of the file or disk.

Action

See Reporting Error Code Problems to Novell.


0x89FF  LOCK ERROR

Explanation

An attempt was made to use a locked file.

Action

See Reporting Error Code Problems to Novell.


0x89FF  Multiple causes

Explanation

NetWare could not identify the exact cause of this error.

Possible causes for this error are

BAD RECORD OFFSET

BAD SPOOL PRINTER

DRIVE INVALID NUM

FAILURE

FCB CLOSE

FILE EXT

FILE NAME

HARD FAILURE

IO BOUND

LOCK ERROR

NO FILES FOUND ERROR

NO OBJ OR BAD PASSWORD

NO RESPONSE FROM SERVER

PATH NOT LOCATABLE

Q FULL ERROR

REQ NOT OUTSTANDING

SEM INVALID HANDLE

SEM INVALID INIT VAL

SOCKET ALREADY OPEN


0x89FF  NO FILES FOUND ERROR

Explanation

No files were found that matched the search specification.

Action

See Reporting Error Code Problems to Novell.


0x89FF  NO OBJ OR BAD PASSWORD

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).

Action

Make sure the user type the correct password.

If necessary, assign the user a new password.

If the error persist, see Reporting Error Code Problems to Novell.


0x89FF  NO RESPONSE FROM SERVER

Action

See Reporting Error Code Problems to Novell.


0x89FF  PATH NOT LOCATABLE

Explanation

The program tried to find an unknown path during a "get full path" call.

Action

See Reporting Error Code Problems to Novell.


0x89FF  Q FULL ERROR

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.)

Action

See Reporting Error Code Problems to Novell.


0x89FF  REQ NOT OUTSTANDING

Explanation

No NCP requests are outstanding.

Action

See Reporting Error Code Problems to Novell.


0x89FF  SEM INVALID HANDLE

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.

Action

See Reporting Error Code Problems to Novell.


0x89FF  SEM INVALID INIT VAL

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.

Action

See Reporting Error Code Problems to Novell.


0x89FF  SOCKET ALREADY OPEN

Explanation

The program tried to open a socket whose specified socket number is already open.

Action

See Reporting Error Code Problems to Novell.


Authentication Keys

NetWare 4 authentication uses a Public Key Encryption system that is virtually unbreakable. It consists of a private key and a public key. The keys are strings of numbers used in complex mathematical functions.

The workstation uses a private key to encode messages sent to the NetWare server. The server then uses a public key to decode the messages. The server knows that the workstation sent it because the workstation's private key is required to encode the message.

Neither the two keys nor the user's password are ever sent across the network.


File System Error Codes

Overview

0x000F  DOS INVALID DRIVE

0x8800  ALREADY ATTACHED

0x8800  VLM ERROR

0x8801  CONN INVALID

0x8802  DRIVE IN USE

0x8803  DRIVE CANNOT MAP

0x8804  DRIVE BAD PATH

0x8805  NET RECEIVE

0x8806  NET UNKNOWN

0x8807  SERVER BAD SLOT

0x8808  SERVER NO SLOTS

0x8809  NET SEND

0x880A  SERVER NO ROUTE

0x880B  BAD LOCAL TARGET

0x880C  REQ TOO MANY REQ FRAGS

0x880D  CONN LIST OVERFLOW

0x880E  BUFFER OVERFLOW

0x880F  SERVER NO CONN

0x8810  NO ROUTER FOUND

0x8811  FUNCTION INVALID

0x8812  LIP RESIZE ERROR

0x8812  SCAN COMPLETE

0x8813  INVALID DIR HANDLE

0x8813  UNSUPPORTED NAME FORMAT TYP

0x8814  HANDLE ALREADY LICENSED

0x8814  OUT OF CLIENT MEMORY

0x8815  HANDLE ALREADY UNLICENSED

0x8815  PATH NOT OURS

0x8816  INVALID NCP PACKET LENGTH

0x8816  PATH IS PRINT DEVICE

0x8817  PATH IS EXCLUDED DEVICE

0x8817  SETTING UP TIMEOUT

0x8818  PATH IS INVALID

0x8818  SETTING SIGNALS

0x8819  NOT SAME DEVICE

0x8819  SERVER CONNECTION LOST

0x881A  OUT OF HEAP SPACE

0x881B  INVALID SEARCH HANDLE

0x881B  INVALID SERVICE REQUEST

0x881C  INVALID DEVICE HANDLE

0x881C  INVALID TASK NUMBER

0x881D  INVALID MESSAGE LENGTH

0x881D  INVALID SEM HANDLE

0x881E  EA SCAN DONE

0x881E  INVALID CFG HANDLE

0x881F  BAD CONNECTION NUMBER

0x881F  INVALID MOD HANDLE

0x8820  ASYN FIRST PASS

0x8820  MULT TREES NOT SUPPORTED

0x8821  INVALID DEVICE INDEX

0x8822  INVALID CONN HANDLE

0x8823  INVALID QUEUE ID

0x8824  INVALID PDEVICE HANDLE

0x8825  INVALID JOB HANDLE

0x8826  INVALID ELEMENT ID

0x8827  ALIAS NOT FOUND

0x8828  RESOURCE SUSPENDED

0x8829  INVALID QUEUE SPECIFIED

0x882A  DEVICE ALREADY OPEN

0x882B  JOB ALREADY OPEN

0x882C  QUEUE NAME ID MISMATCH

0x882D  JOB ALREADY STARTED

0x882E  SPECT DAA TYPE NOT SUPPORTED

0x882F  INVALID ENVIR HANDLE

0x8830  CONN NOT SAME

0x8831  CONN PRIMARY NOT SET

0x8832  KEYWORD NOT FOUND

0x8832  PRN CAPTURE NOT IN PROGRESS

0x8833  BUFFER INVALID LEN

0x8834  USER NO NAME

0x8835  PRN NO LOCAL SPOOLER

0x8836  PARAM INVALID

0x8837  CFG OPEN FAILED

0x8838  CFG NO FILE

0x8839  CFG READ FAILED

0x883A  CFG LINE TOO LONG

0x883B  CFG LINES IGNORED

0x883C  RESOURCE NOT OWNED

0x883D  DAEMON INSTALLED

0x883E  PRN SPOOLER INSTALLED

0x883F  CONN TABLE FULL

0x8840  CFG SECTION NOT FOUND

0x8841  TRAN INVALID TYPE

0x8842  TDS TAG IN USE

0x8843  TDS OUT OF MEMORY

0x8844  TDS INVALID TAG

0x8845  TDS WRITE TRUNCATED

0x8846  DS NO CONN

0x8846  SERVICE BUSY

0x8847  SERVER NOT FOUND

0x8848  VLM INVALID

0x8849  DRIVE ALREADY MAPPED

0x884A  DRIVE LOCAL IN USE

0x884B  DRIVE NONE AVAILABLE

0x884C  DEVICE NOT REDIRECTED

0x884D  FILE MAX REACHED

0x884E  UNLOAD FAILED

0x884F  CONN IN USE

0x8850  REQ TOO MANY REP FRAGS

0x8851  NAME TABLE FULL

0x8852  SOCKET NOT OPEN

0x8853  MEMORY MGR ERROR

0x8854  SFT3 ERROR

0x8855  DS PREFERRED NOT FOUND

0x8856  DEVICE NOT RECOGNIZED

0x8857  NET INVALID TYPE

0x8858  FILE OPEN FAILED

0x8859  DS PREFERRED NOT SPECIFIED

0x885A  REQUESTER FAILURE

0x885A  SOCKET OPEN FAILED

0x885B  RESOURCE ACCESS DENIED

0x8861  SIGNATURE LEVEL CONFLICT

0x8862  NO LOCK FOUND

0x8863  LOCK TABLE FULL

0x8864  INVALID MATCH DATA

0x8865  MATCH FAILED

0x8866  NO MORE ENTRIES

0x8867  INSUFFICIENT RESOURCES

0x8867  INSUFFICIENT SPACE

0x8868  STRING TRANSLATION

0x8869  ACCESS VIOLATION

0x886A  NOT AUTHENTICATED

0x886B  INVALID LEVEL

0x886C  RESOURCE LOCK

0x886D  INVALID NAME FORMAT

0x886E  UNSUPPORTED AUTHENTICATOR

0x8874  IO PENDING

0x8875  INVALID DRIVE NUMBER

0x8880  SVC ALREADY REGISTERED

0x8881  SVC REGISTRY FULL

0x8882  SVC NOT REGISTERED

0x8883  OUT OF RESOURCES

0x8884  RESOLVE SVC FAILED

0x8885  CONNECT FAILED

0x8886  PROTOCOL NOT BOUND

0x8887  AUTHENTICATION FAILED

0x8888  INVALID AUTHEN HANDLE

0x8889  AUTHEN HANDLE ALREADY EXISTS

0x8890  DIFF OBJECT ALREADY AUTHEN

0x8891  REQUEST NOT SERVICEABLE

0x8892  AUTO RECONNECT SO REBUILD

0x8893  AUTO RECONNECT RETRY REQUEST

0x8894  ASYNC REQUEST IN USE

0x8895  ASYNC REQUEST CANCELED

0x8896  SESS SVC ALREADY REGISTERED

0x8897  SESS SVC NOT REGISTERED

0x8899  PREVIOUSLY AUTHENTICATED

0x889A  RESOLVE SVC PARTIAL

0x889B  NO DEFAULT SPECIFIED

0x889C  HOOK REQUEST NOT HANDLED

0x889D  HOOK REQUEST BUSY

0x889E  AUTO RECONNECT SO IGNORE

0x889F  ASYNC REQUEST NOT IN USE

0x88A0  AUTO RECONNECT FAILURE

0x88A1  ERROR ABORT APPLICATION

0x88A2  ERROR SUSPEND APPLICATION

0x88A3  ERROR ABORTED PROCESS GROUP

0x88A5  ERROR PASSWORD HAS EXPIRED

0x88A6  ERROR NETWORK INACTIVE

0x88FF  REQUESTER FAILURE

0x8977  BUFFER TOO SMALL

0x8978  VOL FLAG NOT SET

0x8979  NO ITEMS FOUND

0x897A  CONN ALREADY TEMP

0x897B  CONN ALREADY LOGGED IN

0x897C  CONN NOT AUTHENTICATED

0x897D  CONN NOT LOGGED IN

0x897E  NCP BOUNDARY CHECK FAILED

0x897F  LOCK WAITING

0x8980  FILE IN USE

0x8980  LOCK FAIL

0x8981  FILE NO HANDLES

0x8982  FILE NO OPEN PRIV

0x8983  DISK IO ERROR

0x8984  FILE NO CREATE PRIV

0x8985  FILE NO CREATE DEL PRIV

0x8986  DIR TARGET INVALID

0x8986  FILE EXISTS READ ONLY

0x8987  FILE WILD CARDS IN NAME

0x8988  FILE INVALID HANDLE

0x8989  FILE NO SRCH PRIV

0x898A  FILE NO DEL PRIV

0x898B  FILE NO RENAME PRIV

0x898C  FILE NO MOD PRIV

0x898D  FILE SOME IN USE

0x898E  FILE NONE IN USE

0x898F  FILE SOME READ ONLY

0x8990  FILE NONE READ ONLY

0x8991  FILE SOME RENAMED EXIST

0x8992  FILE NONE RENAMED EXIST

0x8993  FILE NO READ PRIV

0x8994  FILE NO WRITE PRIV

0x8994  FILE READ ONLY

0x8995  FILE DETACHED

0x8996  SERVER OUT OF MEMORY

0x8997  DISK NO SPOOL SPACE

0x8998  VOL INVALID

0x8999  DIR FULL

0x899A  VOL RENAMING ACROSS

0x899B  DIRHANDLE INVALID

0x899C  PATH INVALID

0x899C  TRUSTEES NO MORE

0x899D  DIRHANDLE NO MORE

0x899E  FILE NAME INVALID

0x899F  DIR ACTIVE

0x89A0  DIR NOT EMPTY

0x89A1  DIR IO ERROR

0x89A2  FILE IO LOCKED

0x89A3  TTS TRANSACTION RESTARTED

0x89A3  TRANSACTION RESTARTED

0x89A3  TTS RANSACTION RESTARTED

0x89A4  DIR RENAME INVALID

0x89A5  FILE OPENCREAT MODE INVALID

0x89A6  ALREADY IN USE

0x89A7  RESOURCE TAG INVALID

0x89A8  ACCESS DENIED

0x89BE  DATA STREAM INVALID

0x89BF  NAME SPACE INVALID

0x89C0  ACCTING NO PRIV

0x89C1  ACCTING NO BALANCE

0x89C2  ACCTING NO CREDIT

0x89C3  ACCTING TOO MANY HOLDS

0x89C4  ACCTING DISABLED

0x89C5  LOGIN LOCKOUT

0x89C6  CONSOLE NO PRIV

0x89D0  Q IO FAILURE

0x89D1  Q NONE

0x89D2  Q NO SERVER

0x89D3  Q NO RIGHTS

0x89D4  Q FULL

0x89D5  Q NO JOB

0x89D6  PASSWORD UNENCRYPTED

0x89D6  Q NO JOB RIGHTS

0x89D7  PASSWORD NOT UNIQUE

0x89D7  Q IN SERVICE

0x89D8  PASSWORD TOO SHORT

0x89D8  Q NOT ACTIVE

0x89D9  LOGIN MAX EXCEEDED

0x89D9  LOGIN NO CONN

0x89D9  Q STN NOT SERVER

0x89DA  LOGIN UNAUTHORIZED TIME

0x89DA  Q HALTED

0x89DB  LOGIN UNAUTHORIZED STATION

0x89DB  Q MAX SERVERS

0x89DC  ACCT DISABLED

0x89DE  PASSWORD INVALID

0x89DF  PASSWORD EXPIRED

0x89E0  LOGIN NO CONN AVAIL

0x89E7  E NO MORE USERS

0x89E8  BIND NOT ITEM PROP

0x89E8  BIND WRITE TO GROUP PROP

0x89E9  BIND MEMBER ALREADY EXISTS

0x89EA  BIND NO SUCH MEMBER

0x89EB  BIND NOT GROUP PROP

0x89EC  BIND NO SUCH SEGMENT

0x89ED  BIND PROP ALREADY EXISTS

0x89EE  BIND OBJ ALREADY EXISTS

0x89EF  BIND NAME INVALID

0x89F0  BIND WILDCARD INVALID

0x89F1  BIND SECURITY INVALID

0x89F2  BIND OBJ NO READ PRIV

0x89F3  BIND OBJ NO RENAME PRIV

0x89F4  BIND OBJ NO DELETE PRIV

0x89F5  BIND OBJ NO CREATE PRIV

0x89F6  BIND PROP NO DELETE PRIV

0x89F7  BIND PROP NO CREATE PRIV

0x89F8  BIND PROP NO WRITE PRIV

0x89F9  BIND PROP NO READ PRIV

0x89F9  NO FREE CONN SLOTS

0x89FA  NO MORE SERVER SLOTS

0x89FA  TEMP REMAP ERROR

0x89FB  BIND NO SUCH PROP

0x89FB  NCP NOT SUPPORTED

0x89FB  PARAMETERS INVALID

0x89FC  BIND NO SUCH OBJ

0x89FC  INET PACKET REQ CANCELED

0x89FC  MSG Q FULL

0x89FC  SERVER UNKNOWN

0x89FD  CONN NUM INVALID

0x89FD  LOCK COLLISION

0x89FD  PACKET LEN INVALID

0x89FD  UNKNOWN REQ

0x89FE  BIND LOCKED

0x89FE  DIR LOCKED

0x89FE  LOGIN DISABLED BY SUPER

0x89FE  PACKET NOT DELIVERABLE

0x89FE  SEM INVALID NAME LEN

0x89FE  SOCKET TABLE FULL

0x89FE  SPOOL DIR ERROR

0x89FE  TIMEOUT FAILURE

0x89FE  TRUSTEE NOT FOUND

0x89FF  BAD RECORD OFFSET

0x89FF  BAD SPOOL PRINTER

0x89FF  DRIVE INVALID NUM

0x89FF  FAILURE

0x89FF  FCB CLOSE

0x89FF  FILE EXT

0x89FF  FILE NAME

0x89FF  HARD FAILURE

0x89FF  IO BOUND

0x89FF  LOCK ERROR

0x89FF  NO FILES FOUND ERROR

0x89FF  NO OBJ OR BAD PASSWORD

0x89FF  NO RESPONSE FROM SERVER

0x89FF  PATH NOT LOCATABLE

0x89FF  Q FULL ERROR

0x89FF  REQ NOT OUTSTANDING

0x89FF  SEM INVALID HANDLE

0x89FF  SEM INVALID INIT VAL

0x89FF  SOCKET ALREADY OPEN


How can I find information associated with an error code?

The topics in NetWare* Error Codes Help are organized by a decimal or hexadecimal code.

You can browse the navigation lists that are sorted numerically.

You can search for information by the error code number using  Search  in Windows** 3x or Find in Windows 95**.

Some error codes have several possible causes. While searching, if you see an error code with that is associated a topic Multiple Causes, choose this topic. This topic will list all the causes for that error code and link you to the associated topics with the explanations and actions for each cause.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Monitoring and Repairing NDS error codes
Monitoring and Repairing NDS Errors

NetWare* provides you with the following tools to monitor and repair error conditions with NetWare Directory Services* (NDS):

The NDS* Manager utility. Provides partitioning and replication services for the NDS database on a NetWare server. It also provides repair capabilities for repairing the database from a client workstation, which alleviates the network administrator's total dependence on working from the server console.

The DSREPAIR utility. Allows you to work from the server console to monitor and repair problems with the Directory database on a single-server basis. It does not correct problems on other servers from a single, centralized location. It must be run on each server that you want to correct Directory database errors on.

The DSTRACE utility. Allows you to work from the server console to diagnose NDS errors. These errors might appear when you are manipulating NDS objects with the administration utilities. NDS errors also show up on the DSTRACE screen.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


NDS Error Codes

Overview

-001  FFFFFFFFF  INSUFFICIENT SPACE

-119  FFFFFFF89  BUFFER TOO SMALL

-120  FFFFFFF88  VOLUME FLAG NOT SET

-121  FFFFFFF87  NO ITEMS FOUND

-122  FFFFFFF86  CONN ALREADY TEMPORARY

-123  FFFFFFF85  CONN ALREADY LOGGED IN

-124  FFFFFFF84  CONN NOT AUTHENTICATED

-125  FFFFFFF83  CONN NOT LOGGED IN

-126  FFFFFFF82  NCP BOUNDARY CHECK FAILED

-127  FFFFFFF81  LOCK WAITING

-128  FFFFFFF80  LOCK FAIL

-129  FFFFFFF7F  OUT OF HANDLES

-130  FFFFFFF7E  NO OPEN PRIVILEGE

-131  FFFFFFF7D  HARD IO ERROR

-132  FFFFFFF7C  NO CREATE PRIVILEGE

-133  FFFFFFF7B  NO CREATE DELETE PRIV

-134  FFFFFFF7A  R O CREATE FILE

-135  FFFFFFF79  CREATE FILE INVALID NAME

-136  FFFFFFF78  INVALID FILE HANDLE

-137  FFFFFFF77  NO SEARCH PRIVILEGE

-138  FFFFFFF76  NO DELETE PRIVILEGE

-139  FFFFFFF75  NO RENAME PRIVILEGE

-140  FFFFFFF74  NO SET PRIVILEGE

-141  FFFFFFF73  SOME FILES IN USE

-142  FFFFFFF72  ALL FILES IN USE

-143  FFFFFFF71  SOME READ ONLY

-144  FFFFFFF70  ALL READ ONLY

-145  FFFFFFF6F  SOME NAMES EXIST

-146  FFFFFFF6E  ALL NAMES EXIST

-147  FFFFFFF6D  NO READ PRIVILEGE

-148  FFFFFFF6C  NO WRITE PRIVILEGE

-149  FFFFFFF6B  FILE DETACHED

-150  FFFFFFF6A  INSUFFICIENT MEMORY

-150  FFFFFFF6A  NO ALLOC SPACE

-150  FFFFFFF6A  TARGET NOT A SUBDIR

-151  FFFFFFF69  NO SPOOL SPACE

-152  FFFFFFF68  INVALID VOLUME

-153  FFFFFFF67  DIRECTORY FULL

-154  FFFFFFF66  RENAME ACROSS VOLUME

-155  FFFFFFF65  BAD DIR HANDLE

-156  FFFFFFF64  INVALID PATH

-156  FFFFFFF64  NO SUCH EXTENSION

-157  FFFFFFF63  NO DIR HANDLES

-158  FFFFFFF62  BAD FILE NAME

-159  FFFFFFF61  DIRECTORY ACTIVE

-160  FFFFFFF60  DIRECTORY NOT EMPTY

-161  FFFFFFF5F  DIRECTORY IO ERROR

-162  FFFFFFF5E  IO LOCKED

-163  FFFFFFF5D  TRANSACTION RESTARTED

-164  FFFFFFF5C  RENAME DIR INVALID

-165  FFFFFFF5B  INVALID OPENCREATE MODE

-166  FFFFFFF5A  ALREADY IN USE

-167  FFFFFFF59  INVALID RESOURCE TAG

-168  FFFFFFF58  ACCESS DENIED

-190  FFFFFFF42  INVALID DATA STREAM

-191  FFFFFFF41  INVALID NAME SPACE

-192  FFFFFFF40  NO ACCOUNTING PRIVILEGES

-193  FFFFFFF3F  NO ACCOUNT BALANCE

-194  FFFFFFF3E  CREDIT LIMIT EXCEEDED

-195  FFFFFFF3D  TOO MANY HOLDS

-196  FFFFFFF3C  ACCOUNTING DISABLED

-197  FFFFFFF3B  LOGIN LOCKOUT

-198  FFFFFFF3A  NO CONSOLE RIGHTS

-208  FFFFFFF30  Q IO FAILURE

-209  FFFFFFF2F  NO QUEUE

-210  FFFFFFF2E  NO Q SERVER

-211  FFFFFFF2D  NO Q RIGHTS

-212  FFFFFFF2C  Q FULL

-213  FFFFFFF2B  NO Q JOB

-214  FFFFFFF2A  NO Q JOB RIGHTS

-214  FFFFFFF2A  UNENCRYPTED NOT ALLOWED

-215  FFFFFFF29  DUPLICATE PASSWORD

-215  FFFFFFF29  Q IN SERVICE

-216  FFFFFFF28  PASSWORD TOO SHORT

-216  FFFFFFF28  Q NOT ACTIVE

-217  FFFFFFF27  MAXIMUM LOGINS EXCEEDED

-217  FFFFFFF27  Q STN NOT SERVER

-218  FFFFFFF26  BAD LOGIN TIME

-218  FFFFFFF26  Q HALTED

-219  FFFFFFF25  NODE ADDRESS VIOLATION

-219  FFFFFFF25  Q MAX SERVERS

-220  FFFFFFF24  LOG ACCOUNT EXPIRED

-222  FFFFFFF22  BAD PASSWORD

-223  FFFFFFF21  PASSWORD EXPIRED

-224  FFFFFFF20  NO LOGIN CONN AVAILABLE

-232  FFFFFFF18  WRITE TO GROUP PROPERTY

-233  FFFFFFF17  MEMBER ALREADY EXISTS

-234  FFFFFFF16  NO SUCH MEMBER

-235  FFFFFFF15  PROPERTY NOT GROUP

-236  FFFFFFF14  NO SUCH VALUE SET

-237  FFFFFFF13  PROPERTY ALREADY EXISTS

-238  FFFFFFF12  OBJECT ALREADY EXISTS

-239  FFFFFFF11  ILLEGAL NAME

-240  FFFFFFF10  ILLEGAL WILDCARD

-241  FFFFFFF0F  BINDERY SECURITY

-242  FFFFFFF0E  NO OBJECT READ RIGHTS

-243  FFFFFFF0D  NO OBJECT RENAME RIGHTS

-244  FFFFFFF0C  NO OBJECT DELETE RIGHTS

-245  FFFFFFF0B  NO OBJECT CREATE RIGHTS

-246  FFFFFFF0A  NO PROPERTY DELETE RIGHTS

-247  FFFFFFF09  NO PROPERTY CREATE RIGHTS

-248  FFFFFFF08  NO PROPERTY WRITE RIGHTS

-249  FFFFFFF07  NO PROPERTY READ RIGHTS

-250  FFFFFFF06  TEMP REMAP

-251  FFFFFFF05  NO SUCH PROPERTY

-251  FFFFFFF05  UNKNOWN REQUEST

-252  FFFFFFF04  MESSAGE QUEUE FULL

-252  FFFFFFF04  NO SUCH OBJECT

-252  FFFFFFF04  TARGET ALREADY HAS MSG

-253  FFFFFFF03  BAD STATION NUMBER

-254  FFFFFFF02  BINDERY LOCKED

-254  FFFFFFF02  DIR LOCKED

-254  FFFFFFF02  SPOOL DELETE

-254  FFFFFFF02  TRUSTEE NOT FOUND

-255  FFFFFFF01  BAD PARAMETER

-255  FFFFFFF01  BAD SPOOL PRINTER

-255  FFFFFFF01  CLOSE FCB

-255  FFFFFFF01  ERR OF SOME SORT

-255  FFFFFFF01  FILE EXISTS

-255  FFFFFFF01  FILE NAME

-255  FFFFFFF01  HARD FAILURE

-255  FFFFFFF01  IO BOUND

-255  FFFFFFF01  MUST FORCE DOWN

-255  FFFFFFF01  NO FILES FOUND

-255  FFFFFFF01  NO SPOOL FILE

-255  FFFFFFF01  NO TRUSTEE CHANGE PRIV

-255  FFFFFFF01  TARGET NOT ACCEPTING MSGS

-255  FFFFFFF01  TARGET NOT LOGGED IN

-301  FFFFFFED3  NOT ENOUGH MEMORY

-302  FFFFFFED2  BAD KEY

-303  FFFFFFED1  BAD CONTEXT

-304  FFFFFFED0  BUFFER FULL

-305  FFFFFFECF  LIST EMPTY

-306  FFFFFFECE  BAD SYNTAX

-307  FFFFFFECD  BUFFER EMPTY

-308  FFFFFFECC  BAD VERB

-309  FFFFFFECB  EXPECTED IDENTIFIER

-310  FFFFFFECA  EXPECTED EQUALS

-311  FFFFFFEC9  ATTR TYPE EXPECTED

-312  FFFFFFEC8  ATTR TYPE NOT EXPECTED

-313  FFFFFFEC7  FILTER TREE EMPTY

-314  FFFFFFEC6  INVALID OBJECT NAME

-315  FFFFFFEC6  EXPECTED RDN DELIMITER

-316  FFFFFFEC5  TOO MANY TOKENS

-317  FFFFFFEC3  INCONSISTENT MULTIAVA

-318  FFFFFFEC2  COUNTRY NAME TOO LONG

-319  FFFFFFEC1  SYSTEM ERROR

-320  FFFFFFEC0  CANT ADD ROOT

-321  FFFFFFEBF  UNABLE TO ATTACH

-322  FFFFFFEBE  INVALID HANDLE

-323  FFFFFFEBD  BUFFER ZERO LENGTH

-324  FFFFFFEBC  INVALID REPLICA TYPE

-325  FFFFFFEBB  INVALID ATTR SYNTAX

-326  FFFFFFEBA  INVALID FILTER SYNTAX

-328  FFFFFFEB8  CONTEXT CREATION

-329  FFFFFFEB7  INVALID UNION TAG

-330  FFFFFFEB6  INVALID SERVER RESPONSE

-331  FFFFFFEB5  NULL POINTER

-332  FFFFFFEB5  NO SERVER FOUND

-333  FFFFFFEB3  NO CONNECTION

-334  FFFFFFEB2  RDN TOO LONG

-335  FFFFFFEB1  DUPLICATE TYPE

-336  FFFFFFEB0  DATA STORE FAILURE

-337  FFFFFFEAF  NOT LOGGED IN

-338  FFFFFFEAE  INVALID PASSWORD CHARS

-339  FFFFFFEAD  FAILED SERVER AUTHENT

-340  FFFFFFEAC  TRANSPORT

-341  FFFFFFEAB  NO SUCH SYNTAX

-342  FFFFFFEAA  INVALID DS NAME

-343  FFFFFFEA9  ATTR NAME TOO LONG

-344  FFFFFFEA8  INVALID TDS

-345  FFFFFFEA7  INVALID DS VERSION

-346  FFFFFFEA6  UNICODE TRANSLATION

-347  FFFFFFEAS  SCHEMA NAME TOO LONG

-348  FFFFFFEA4  UNICODE FILE NOT FOUND

-349  FFFFFFEA3  UNICODE ALREADY LOADED

-350  FFFFFFEA2  NOT CONTEXT OWNER

-351  FFFFFFEA1  ATTEMPT TO AUTHENTICATE 0

-352  FFFFFFEA0  NO WRITABLE REPLICAS

-353  FFFFFFE9F  DN TOO LONG

-354  FFFFFFE9E  RENAME NOT ALLOWED

-489  FFFFFFE17  UNI ALREADY LOADED

-490  FFFFFFE16  UNI  FUTURE OPCODE

-491  FFFFFFE15  UNI NO SUCH FILE

-492  FFFFFFE14  UNI TOO MANY FILES

-493  FFFFFFE13  UNI NO PERMISSION

-494  FFFFFFE12  UNI NO MEMORY

-495  FFFFFFE11  UNI LOAD FAILED

-496  FFFFFFE10  UNI HANDLE BAD

-497  FFFFFFE0F  UNI HANDLE MISMATCH

-498  FFFFFFE0E  UNI RULES CORRUPT

-499  FFFFFFE0D  UNI NO DEFAULT

-500  FFFFFFE0C  UNI INSUFFICIENT BUFFER

-501  FFFFFFE0B  UNI OPEN FAILED

-502  FFFFFFE0A  UNI NO LOAD DIR

-503  FFFFFFE09  UNI BAD FILE HANDLE

-504  FFFFFFE08  UNI READ FAILED

-505  FFFFFFE07  UNI TRANS CORRUPT

-601  FFFFFFDA7  NO SUCH ENTRY

-602  FFFFFFDA6  NO SUCH VALUE

-603  FFFFFFDA5  NO SUCH ATTRIBUTE

-604  FFFFFFDA4  NO SUCH CLASS

-605  FFFFFFDA3  NO SUCH PARTITION

-606  FFFFFFDA2  ENTRY ALREADY EXISTS

-607  FFFFFFDA1  NOT EFFECTIVE CLASS

-608  FFFFFFDA0  ILLEGAL ATTRIBUTE

-609  FFFFFFD9F  MISSING MANDATORY

-610  FFFFFFD9E  ILLEGAL DS NAME

-611  FFFFFFD9D  ILLEGAL CONTAINMENT

-612  FFFFFFD9C  CANT HAVE MULTIPLE VALUES

-613  FFFFFFD9B  SYNTAX VIOLATION

-614  FFFFFFD9A  DUPLICATE VALUE

-615  FFFFFFD99  ATTRIBUTE ALREADY EXISTS

-616  FFFFFFD98  MAXIMUM ENTRIES EXIST

-617  FFFFFFD97  DATABASE FORMAT

-618  FFFFFFD96  INCONSISTENT DATABASE

-619  FFFFFFD95  INVALID COMPARISON

-620  FFFFFFD94  COMPARISON FAILED

-621  FFFFFFD93  TRANSACTIONS DISABLED

-622  FFFFFFD92  INVALID TRANSPORT

-623  FFFFFFD91  SYNTAX INVALID IN NAME

-624  FFFFFFD90  REPLICA ALREADY EXISTS

-625  FFFFFFD8F  TRANSPORT FAILURE

-626  FFFFFFD8E  ALL REFERRALS FAILED

-627  FFFFFFD8D  CANT REMOVE NAMING VALUE

-628  FFFFFFD8C  OBJECT CLASS VIOLATION

-629  FFFFFFD8B  ENTRY IS NOT LEAF

-630  FFFFFFD8A  DIFFERENT TREE

-631  FFFFFFD89  ILLEGAL REPLICA TYPE

-632  FFFFFFD88  SYSTEM FAILURE

-633  FFFFFFD87  INVALID ENTRY FOR ROOT

-634  FFFFFFD86  NO REFERRALS

-635  FFFFFFD85  REMOTE FAILURE

-636  FFFFFFD84  UNREACHABLE SERVER

-637  FFFFFFD83  PREVIOUS MOVE IN PROGRESS

-638  FFFFFFD82  NO CHARACTER MAPPING

-639  FFFFFFD81  INCOMPLETE AUTHENTICATION

-640  FFFFFFD80  INVALID CERTIFICATE

-641  FFFFFFD7F  INVALID REQUEST

-642  FFFFFFD7E  INVALID ITERATION

-643  FFFFFFD7D  SCHEMA IS NONREMOVABLE

-644  FFFFFFD7C  SCHEMA IS IN USE

-645  FFFFFFD7B  CLASS ALREADY EXISTS

-646 F FFFFFD7A  BAD NAMING ATTRIBUTES

-647  FFFFFFD79  NOT ROOT PARTITION

-648  FFFFFFD78  INSUFFICIENT STACK

-649  FFFFFFD77  INSUFFICIENT BUFFER

-650  FFFFFFD76  AMBIGUOUS CONTAINMENT

-651  FFFFFFD75  AMBIGUOUS NAMING

-652  FFFFFFD74  DUPLICATE MANDATORY

-653  FFFFFFD73  DUPLICATE OPTIONAL

-654  FFFFFFD72  PARTITION BUSY

-655  FFFFFFD71  MULTIPLE REPLICAS

-656  FFFFFFD70  CRUCIAL REPLICA

-657  FFFFFFD6F  SCHEMA SYNC IN PROGRESS

-658  FFFFFFD6E  SKULK IN PROGRESS

-659  FFFFFFD6D  TIME NOT SYNCHRONIZED

-660  FFFFFFD6C  RECORD IN USE

-661  FFFFFFD6B  DS VOLUME NOT MOUNTED

-662  FFFFFFD6A  DS VOLUME IO FAILURE

-663  FFFFFFD69  DS LOCKED

-664  FFFFFFD68  OLD EPOCH

-665  FFFFFFD67  NEW EPOCH

-666  FFFFFFD66  INCOMPATIBLE DS VERSION

-667  FFFFFFD65  PARTITION ROOT

-668  FFFFFFD64  ENTRY NOT CONTAINER

-669  FFFFFFD63  FAILED AUTHENTICATION

-670  FFFFFFD62  INVALID CONTEXT

-671  FFFFFFD61  NO SUCH PARENT

-672  FFFFFFD60  NO ACCESS

-673  FFFFFFD5F  REPLICA NOT ON

-674  FFFFFFD5E  INVALID NAME SERVICE

-675  FFFFFFD5D  INVALID TASK

-676  FFFFFFD5C  INVALID CONN HANDLE

-677  FFFFFFD5B  INVALID IDENTITY

-678  FFFFFFD5A  DUPLICATE ACL

-679  FFFFFFD59  PARTITION ALREADY EXISTS

-680  FFFFFFD58  TRANSPORT MODIFIED

-681  FFFFFFD57  ALIAS OF AN ALIAS

-682  FFFFFFD56  AUDITING FAILED

-683  FFFFFFD55  INVALID API VERSION

-684  FFFFFFD54  SECURE NCP VIOLATION

-685  FFFFFFD53  MOVE IN PROGRESS

-686  FFFFFFD52  NOT LEAF PARTITION

-687  FFFFFFD51  CANNOT ABORT

-688  FFFFFFD50  CACHE OVERFLOW

-689  FFFFFFD4F  INVALID SUBORDINATE COUNT

-690  FFFFFFD4E  INVALID RDN

-691  FFFFFFD4D  MOD TIME NOT CURRENT

-692  FFFFFFD4C  INCORRECT BASE CLASS

-693  FFFFFFD4B  MISSING REFERENCE

-694  FFFFFFD4A  LOST ENTRY

-695  FFFFFFD49  AGENT ALREADY REGISTERED

-696  FFFFFFD48  DS LOADER BUSY

-697  FFFFFFD47  DS CANNOT RELOAD

-698  FFFFFFD46  REPLICA IN SKULK

-699  FFFFFFD45  FATAL

-700  FFFFFFD44  OBSOLETE API

-701  FFFFFFD43  SYNCHRONIZATION DISABLED

-702  FFFFFFD42  INVALID PARAMETER

-703  FFFFFFD41  DUPLICATE TEMPLATE

-704  FFFFFFD40  NO MASTER REPLICA

-705  FFFFFFD3F  DUPLICATE CONTAINMENT

-706  FFFFFFD3E  NOT SIBLING

-707  FFFFFFD3D  INVALID SIGNATURE

-708  FFFFFFD3C  INVALID RESPONSE

-709  FFFFFFD3B  INSUFFICIENT SOCKETS

-710  FFFFFFD3A  DATABASE READ FAIL

-711  FFFFFFD39  INVALID CODE PAGE

-712  FFFFFFD38  INVALID ESCAPE CHAR

-713  FFFFFFD37  INVALID DELIMITERS

-714  FFFFFFD36  NOT IMPLEMENTED

-715  FFFFFFD35  CHECKSUM FAILURE

-716  FFFFFFD34  CHECKSUMMING NOT SUPPORTED

-717  FFFFFFD33  CRC FAILURE


NetWare Error Codes

Overview

What is a NetWare Error Code?

How can I find information associated with an error code?

NetWare Directory Services Error Codes

Overview

List of Codes

List of Tools for Monitoring and Repairing NDS

File System Error Codes

Overview

List of Codes

Reference

Trademarks


Online Service, Internet

The Technical Support Database and NetWire* forum are available on the Internet. The Novell FTP sites support access through FTP, Gopher, and World Wide Web (WWW) systems. Over 9,000 documents exist on the WWW system for providing technical hints and information.

To access the Novell Internet FTP sites, log in as ANONYMOUS and use your E-mail address as your password. Contact one of the following site addresses:

In the United States: ftp.novell.com

In Germany: ftp.novell.de

In the United Kingdom: ftp.salford.ac.uk

In Canada: novell.nrc.ca

See public areas in these sites for possible listings of other sites' addresses.

To access the Novell Internet WWW sites, contact one of the following site addresses:

In the United States: www.novell.com or www.netware.com

In Germany: www.novell.de

See information areas in these sites for possible listings of other sites' addresses.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Online Service, NetWire forum on CompuServe

Using the NetWire* forum on the CompuServe** bulletin board is a fairly inexpensive way to get up-to-date advice and patches.

To open a CompuServe account, call one of the following numbers and ask for Representative 200. This identifies you as a Novell customer:

In the United States or Canada: 1-800-524-3388

In the United Kingdom: 0800-289-378

In Germany: 0130-37-32

In other European countries: 44-272-255-111

In locations other than the United States, Canada, or Europe, use the appropriate country code for the U.S. and call 614-457-0802.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Overview, File System Error Codes

This portion of the help lists NetWare* file system error codes. Use this information to manage file system problems when error conditions exist.

File system errors usually are displayed in hexadecimal values.

An application usually displays these error codes as part of a message.

For example:

918: This utility was unable to get connection information. Error code: 89FF.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Overview, NDS Error Codes

This portion of the help lists NetWare* Directory Services* (NDS) error codes. Use this information to manage your NDS* servers when error conditions exist.

NDS errors codes are usually displayed in decimal numbers. Sometimes an application displays these codes using hexadecimal values. Error code numbers can be categorized as follows:

Error Codes numbered -1 through -256 (or FFFF through FF01) represent errors from the file system, IPX, NCP, and other NetWare operating system services. These one-byte errors are mapped to -1 to -256 when returned through Directory Services.

Error Codes numbered -301 through -399 (or FED3 through FDA6) represent errors that originated in the NetWare Client library software that are returned through Directory Services.

Error codes numbered -601 through -799 (or FDA7 through F9FE) represent errors that originated in the Directory Services Agent software in the server that are returned through Directory Services.

Because the Directory database is designed as a loosely consistent database, temporary errors are normal. You should not be alarmed if NDS error conditions exist temporarily. However, some errors might persist until the error condition is resolved.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Reporting Error Code Problems to Novell

To improve the information Novell* has about resolving error code problems, we need to know when and how users are seeing them occur. Please help us gather this information by doing the following:

1.	Record the error number.

2. 	Record the circumstances in which the error occurred.

3. 	If you were able to resolve the error, record what you did to resolve the problem.

4. 	Report this information to Novell through E-mail. Send the E-mail to SYSMSG@Novell.com.

If you want an updated copy of the NetWare* Error Codes Help, type HELP in the subject line.

If you are unable to resolve the problem, please contact a NetWare support provider.

You may also obtain an updated copy of this file, NWEC.HLP,  from the following online services:

Internet

NetWire*

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Source Server, definition
Source Server

When running DSTRACE, this is the server where the DSTRACE error is displayed.

In NDS Manager, this is the server represented by a row on the Partition Continuity screen.


Synthetic Time

A type of time stamp used by NetWare Directory Services (NDS) to prevent objects from being timestamped incorrectly.

For example, if the time on the server is set back and it no longer matches the timestamp of the partition, then a synthetic timestamp is issued to NDS to prevent objects from being timestamped incorrectly.


Target Server, definition
Target Server

When running DSTRACE, this is the server whose name is listed in DSTRACE with the error message.

In NDS Manager, this is the server represented by a column on the Partition Continuity screen.


Trademarks

Copyright © 1994-1996, Novell, Inc.  All rights reserved.  Patent Pending.

Novell Trademarks

Client 32 is a trademark of Novell, Inc.

GroupWise is a trademark of Novell, Inc.

IPX (Internetwork Packet Exchange) is a trademark of Novell, Inc.

IPX/SPX is a trademark of Novell, Inc.

NetWare is a registered trademark of Novell, Inc. in the United States and other countries.

NetWare 3 is a trademark of Novell, Inc.

NetWare 4 is a trademark of Novell, Inc.

NetWare Client is a trademark of Novell, Inc.

NetWare Directory Services and NDS are trademarks of Novell, Inc.

NetWire is a registered service mark of Novell, Inc. in the United States and other countries.

Novell is a registered trademark of Novell, Inc. in the United States and other countries.

Novell Labs is a trademark of Novell, Inc.

Novell Network Registry is a service mark of Novell, Inc.

Transaction Tracking System and TTS are trademarks of Novell, Inc.

Third-Party Trademarks

AppleTalk is a registered trademark of Apple Computer, Inc.

ARCNet is a registered trademark of DataPoint Corporation.

COMPAQ is a registered trademark of Compaq Computer Corporation.

CompuServe is a registered trademark of CompuServe Incorporated.

DS Migrate is a trademark of Preferred Systems, Inc.

Excel is a trademark of Microsoft Corporation.

Hayes is a registered trademark of Hayes Microcomputer Products, Inc.

IBM is a registered trademark of International Business Machines Corporation.

Lotus Notes is a registered trademark of Lotus Development Corporation.

Macintosh is a registered trademark of Apple Computer, Inc.

NFS is a registered trademark of Sun Microsystems, Inc.

OS/2 is a registered trademark of International Business Machines Corporation.

PageMarq is a registered trademark of Compaq Computer Corporation.

PCL is a registered trademark of Hewlett-Packard Company.

PerfectOffice is a trademark of Corel Corporation Limited.

PostScript is a registered trademark of Adobe Systems Incorporated.

PowerPoint is a registered trademark of Microsoft Corporation.

Preferred Systems and PSI are trademarks of Preferred Systems, Inc.

Quattro Pro is a registered trademark of Corel Corporation Limited.

The Assistant is a  trademark of Preferred Systems, Inc.

UNIX is a registered trademark in the United States and other countries, licensed exclusively through X/Open Company, Ltd.

Windows is a registered trademark of Microsoft Corporation.

Windows 95 is a trademark of Microsoft Corporation.

Windows NT is a trademark of Microsoft Corporation.

WNIM is a registered trademark of Gateway Communications, Inc.

WordPerfect is a registered trademark of Corel Corporation Limited.

WordPerfect Presentations is a registered trademark of Corel Corporation Limited.


UNKNOWN ERROR

Explanation

An error has occurred that NetWare* is unable to identify.

Action

See Reporting Error Code Problems to Novell.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


What is a NetWare Error Code?

A NetWare* error code is a hexadecimal or decimal number that is usually displayed within an error message for an application. When an error code is displayed, it indicates that a software or hardware error has occurred that does not allow NetWare to continue processing.

Many error codes display only a few digits of the hexadecimal error code. Often a number code is truncated to two digits, so it is not the actual decimal equivalent of the hexadecimal code.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.