These are the Client Services error codes included in this section:
Source:
Client Services
Explanation:
An attempt was made to use an invalid (undefined or unavailable) DOS drive.
Source:
Client Services
Explanation:
A VLM error has occurred.
Source:
Client Services
Explanation:
The user is already attached to the server.
Source:
Client Services
Explanation:
An attempt by an application to request a connection failed. If a connection is closed, it becomes invalid.
Possible Cause:
The connection handle that is being used by the requesting application no longer refers to a given connection slot in the requester’s connection table. In this case, the application, such as an executable file or driver, might be out of date.
Possible Cause:
An application might request that a connection be closed without any regard to other applications that point to the open connection.
Action:
Try the task again. If the error persists, contact the developer of the application for the latest version of the application.
Possible Cause:
The server ran out of connections.
Action:
To free a connection, have a user who is connected to the server log out. Or, to increase the number of connections allowed for that server, go to a workstation where a user is connected to the server and has Supervisor rights, and increase the number of connnections allowed.
Possible Cause:
The software might not allow more connections for the client. For example, in some of the NetWare® 3.12 utilities, like MAP and CAPTURE, this error will be returned if the workstation is attached to 9 or more servers. In NetWare 3.12, these utilities were designed to provide functionality for only 8 servers.
Action:
If you desire to increase the number of connections that a workstation can have, use a version of the software that will allow more connections. The utilities in NetWare 4 and later versions allow this number of connections.
Possible Cause:
The connection might have been closed at the server, such as by an administrator clearing a connection using MONITOR.
Action:
If desired, have the user log in again to the network.
Source:
Client Services
Explanation:
The drive is in use. (OS2 only, not used)
Source:
Client Services
Explanation:
An attempt to map a drive was unsucessful. It could not add a new current directory structure.
Source:
Client Services
Explanation:
An attempt was made to map a drive with an invalid path specification.
Source:
Client Services
Explanation:
An attempt to receive from the selected transport failed.
Possible Cause:
The network is no longer transmitting over the specified transport (IP or IPX).
Action:
Make sure the application’s connection to the network is working and try the action again.
Source:
Client Services
Explanation:
A network send request was attempted, but a nonspecific error occurred.
Source:
Client Services
Explanation:
A server request was attempted with an invalid server connection slot.
Source:
Client Services
Explanation:
An attempt was made to attach to a server with no connection slots available.
Source:
Client Services
Explanation:
An attempt to send on the selected transport failed.
Source:
Client Services
Explanation:
An attempt was made to find a route to a server where no route exists.
Source:
Client Services
Explanation:
An invalid local target was specified (for OS/2* only).
0x880C REQ TOO MANY REQ FRAGS
Source:
Client Services
Explanation:
A request was attempted with too many request fragments specified.
0x880D CONN LIST OVERFLOW
Source:
Client Services
Explanation:
Too many connections exist to fit in the list size specified.
Source:
Client Services
Explanation:
An attempt was made to receive more data than the reply buffer had room for.
Source:
Client Services
Explanation:
An attempt to get connection for a server failed. The workstation is not connected.
Source:
Client Services
Explanation:
No router was found (OS/2 only).
Source:
Client Services
Explanation:
A function call was tried to a nonexistent or illegal function.
Source:
Client Services
Explanation:
A Large Internet Packet (LIP) resize error occurred.
0x8813 INVALID DIR HANDLE
Source:
Client Services
0x8813 UNSUPPORTED NAME FORMAT TYP
Source:
Client Services
0x8814 HANDLE ALREADY LICENSED
Source:
Client Services
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.
0x8814 OUT OF CLIENT MEMORY
Source:
Client Services
Explanation:
The client is out of memory.
0x8815 HANDLE ALREADY UNLICENSED
Source:
Client Services
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.
Source:
Client Services
Explanation:
An attempt was made to specify a path that NetWare does not recognize.
0x8816 INVALID NCP PACKET LENGTH
Source:
Client Services
Explanation:
The NCP packet length is invalid.
0x8816 PATH IS PRINT DEVICE
Source:
Client Services
Explanation:
An attempt was made to write to a path that is a print device.
0x8817 PATH IS EXCLUDED DEVICE
Source:
Client Services
Explanation:
An attempt was made to specify a path to a device that is excluded.
0x8817 SETTING UP TIMEOUT
Source:
Client Services
Source:
Client Services
Explanation:
An attempt was made to access a path that is invalid.
Source:
Client Services
Explanation:
The device is not the same.
0x8819 SERVER CONNECTION LOST
Source:
Client Services
0x881B INVALID SEARCH HANDLE
Source:
Client Services
0x881B INVALID SERVICE REQUEST
Source:
Client Services
Explanation:
The service request is invalid.
0x881C INVALID DEVICE HANDLE
Source:
Client Services
0x881C INVALID TASK NUMBER
Source:
Client Services
Explanation:
The task number is invalid.
0x881D INVALID MESSAGE LENGTH
Source:
Client Services
Explanation:
The message length is invalid.
0x881D INVALID SEM HANDLE
Source:
Client Services
Source:
Client Services
Explanation:
An Equal Access (EA) scan is done.
0x881E INVALID CFG HANDLE
Source:
Client Services
0x881F BAD CONNECTION NUMBER
Source:
Client Services
Explanation:
An attempt has been made to connect to a server with a bad connection number.
0x881F INVALID MOD HANDLE
Source:
Client Services
0x8820 MULT TREES NOT SUPPORTED
Source:
Client Services
Explanation:
Multiple trees are not supported.
0x8821 INVALID DEVICE INDEX
Source:
Client Services
0x8822 INVALID CONN HANDLE
Source:
Client Services
Explanation:
An invalid CONN handle was issued.
0x8824 INVALID PDEVICE HANDLE
Source:
Client Services
0x8825 INVALID JOB HANDLE
Source:
Client Services
0x8826 INVALID ELEMENT ID
Source:
Client Services
Source:
Client Services
Explanation:
An alias is not found.
0x8828 RESOURCE SUSPENDED
Source:
Client Services
Explanation:
The resource is suspended.
0x8829 INVALID QUEUE SPECIFIED
Source:
Client Services
0x882A DEVICE ALREADY OPEN
Source:
Client Services
Explanation:
The device is already open.
Source:
Client Services
Explanation:
The job is already open.
0x882C QUEUE NAME ID MISMATCH
Source:
Client Services
Explanation:
The queue name has a mismatched ID.
0x882D JOB ALREADY STARTED
Source:
Client Services
Explanation:
The job already has been started.
0x882E SPECT DAA TYPE NOT SUPPORTED
Source:
Client Services
Explanation:
The specified Data Access Arrangement (DAA) type is not supported.
0x882F INVALID ENVIR HANDLE
Source:
Client Services
Source:
Client Services
Explanation:
An internal server request was attempted across different server connections.
0x8831 CONN PRIMARY NOT SET
Source:
Client Services
Explanation:
An attempt was made to retrieve a default connection with no primary connection set.
Source:
Client Services
Explanation:
A keyword is not found.
0x8832 PRN CAPTURE NOT IN PROGRESS
Source:
Client Services
Explanation:
Capture information was requested on a port with no capture in progress.
0x8833 BUFFER INVALID LEN
Source:
Client Services
Explanation:
The length that the caller requested was too large.
0x8835 PRN NO LOCAL SPOOLER
Source:
Client Services
Explanation:
Capture was requested without a local print spooler installed.
Source:
Client Services
Explanation:
A function was attempted with an invalid function parameter specified.
Source:
Client Services
Explanation:
An attempt to open the configuration file failed (for OS/2 only).
Source:
Client Services
Explanation:
No configuration file can be found (for OS/2 only).
Source:
Client Services
Explanation:
An attempt to read a file failed (for OS/2 only).
Source:
Client Services
Explanation:
A line in the configuration file is too long (for OS/2 only).
Source:
Client Services
Explanation:
One or more lines in the configuration file were ignored (for OS/2 only).
0x883C RESOURCE NOT OWNED
Source:
Client Services
Explanation:
A request was made with a parameter using a foreign resource.
Source:
Client Services
Explanation:
No information for this error code is available (for OS/2 only).
0x883E PRN SPOOLER INSTALLED
Source:
Client Services
Explanation:
An attempt was made to load the print spooler, but the print spooler was already installed.
Source:
Client Services
Explanation:
The system tried to allocate a connection handle, but no more local connection table entries were available.
0x8840 CFG SECTION NOT FOUND
Source:
Client Services
Explanation:
The configuration section was not found (for OS/2 only).
Source:
Client Services
Explanation:
An attempt was made to execute a function on a connection with an invalid transport selected.
Source:
Client Services
Explanation:
A Tagged Data Store (TDS) tag is already in use (for OS/2 only).
Source:
Client Services
Explanation:
The computer does not have enough available RAM (for OS/2 only).
Source:
Client Services
Explanation:
A Tagged Data Store (TDS) function was attempted with an invalid tag.
0x8845 TDS WRITE TRUNCATED
Source:
Client Services
Explanation:
A Tagged Data Store (TDS) write was tried to a buffer that exceeded the buffer’s size.
Source:
Client Services
Explanation:
No eDirectory or NDS connections exists.
Source:
Client Services
Explanation:
A request was tried to a busy, partially asynchronous function.
Source:
Client Services
Explanation:
The attempt to connect failed to find any servers responding.
Source:
Client Services
Explanation:
An attempted function call was made to a nonexistent or not-loaded overlay.
0x8849 DRIVE ALREADY MAPPED
Source:
Client Services
Explanation:
An attempt was made to map to a network drive that was already mapped.
0x884A DRIVE LOCAL IN USE
Source:
Client Services
Explanation:
An attempt was made to map to a local drive that was in use.
0x884B DRIVE NONE AVAILABLE
Source:
Client Services
Explanation:
An attempt was made to map to the next available drive when no drive was available.
0x884C DEVICE NOT REDIRECTED
Source:
Client Services
Explanation:
The device was not redirected.
Source:
Client Services
Explanation:
The maximum number of files has been reached.
Source:
Client Services
Explanation:
An attempted unload failed.
Source:
Client Services
Explanation:
An attempt was made to reuse a connection entry that was already in use.
0x8850 REQ TOO MANY REP FRAGS
Source:
Client Services
Explanation:
An attempted request had too many reply fragments specified.
Source:
Client Services
Explanation:
An attempted request was made to add a name into the name table after the table was full.
Source:
Client Services
Explanation:
A listen was posted on an unopened socket.
Source:
Client Services
Explanation:
An attempted enhanced memory operation failed.
Source:
Client Services
Explanation:
An SFT III switch occurred during mid transfer.
0x8855 DS PREFERRED NOT FOUND
Source:
Client Services
Explanation:
A preferred directory server was not established, but another directory server was returned.
0x8856 DEVICE NOT RECOGNIZED
Source:
Client Services
Explanation:
The device is unknown.
Action:
Determine if the device is not used by the NetWare DOS Requester™; pass to next redirector, if any.
0x8859 DS PREFERRED NOT SPECIFIED
Source:
Client Services
Explanation:
A preferred directory server was not specified.
Source:
Client Services
Explanation:
A requester failure has occurred.
0x885A SOCKET OPEN FAILED
Source:
Client Services
0x885B RESOURCE ACCESS DENIED
Source:
Client Services
Explanation:
Access to the resource is denied.
0x8861 SIGNATURE LEVEL CONFLICT
Source:
Client Services
Source:
Client Services
Explanation:
An attempt was made to remove a lock, but no lock was found.
Source:
Client Services
Explanation:
The lock table is full.
0x8864 INVALID MATCH DATA
Source:
Client Services
Explanation:
The match data is invalid.
Source:
Client Services
Explanation:
The match failed.
0x8867 INSUFFICIENT RESOURCES
Source:
Client Services
Explanation:
The resources are insufficient to perform the requested operation.
0x8868 STRING TRANSLATION
Source:
Client Services
Source:
Client Services
Explanation:
An access violation has occurred.
Source:
Client Services
Explanation:
The level is invalid.
0x886D INVALID NAME FORMAT
Source:
Client Services
Explanation:
The name format is invalid.
Source:
Client Services
Explanation:
An attempt was made to access an object, but the object was not found.
0x8870 UNSUPPORTED TRAN TYPE
Source:
Client Services
0x8871 INVALID STRING TYPE
Source:
Client Services
Explanation:
The string type is invalid.
Source:
Client Services
Explanation:
The owner is invalid.
0x8873 UNSUPPORTED AUTHENTICATOR
Source:
Client Services
Explanation:
The authenticator is unsupported.
Source:
Client Services
Explanation:
The I/O is pending.
0x8875 INVALID DRIVE NUMBER
Source:
Client Services
Explanation:
The drive number is invalid.
0x8880 SVC ALREADY REGISTERED
Source:
Client Services
Explanation:
The session for the Switched Virtual Circuit (SVC) is already registered.
Source:
Client Services
Explanation:
The SVC registry is full.
0x8882 SVC NOT REGISTERED
Source:
Client Services
Explanation:
The SVC is not registered.
Source:
Client Services
Explanation:
No resources are available.
0x8884 RESOLVE SVC FAILED
Source:
Client Services
Explanation:
An attempt to resolve the transport type or name failed.
Possible Cause:
The transport type used by the application is not supported.
Action:
Use only a supported transport type. The supported transport type is IPX. IP only will not be available until future versions of NetWare are released.
Possible Cause:
The tree or server name requested by the application was not found.
Action:
Verify that the tree or server name is requested is correct and try the task again.
Possible Cause:
The user attempting the task is not authenticated to the eDirectory or NDS tree.
Action:
Make sure the user is authenticated to the eDirectory or NDS tree and try the task again.
Source:
Client Services
Explanation:
The connection failed.
0x8886 PROTOCOL NOT BOUND
Source:
Client Services
Explanation:
The protocol is not bound.
0x8887 AUTHENTICATION FAILED
Source:
Client Services
Explanation:
The authentication failed.
0x8888 INVALID AUTHEN HANDLE
Source:
Client Services
Explanation:
The authentication handle is invalid.
0x8889 AUTHEN HANDLE ALREADY EXISTS
Source:
Client Services
Explanation:
An authentication handle already exists.
0x8890 DIFF OBJECT ALREADY AUTHEN
Source:
Client Services
Explanation:
Connections in Client 32™ are global. If an object (user or otherwise) is logged in or authenticated to a domain (bindery or eDirectory or NDS tree), an attempt to log in to the same domain as a different object will result in this error.
Possible Cause:
An application attempted to authenticate a different object or user on an existing authenticated connection.
Action:
Log the user out then have them log in again. If the error persists, contact the developer of the application.
Some cases have been reported with remote connections being unable to authenticate caused by a conflict with the dsapi.nlm. Upgrading to a later version of this NetWare Loadable Module™ (NLM™) program has solved the problem.
0x8891 REQUEST NOT SERVICEABLE
Source:
Client Services
Explanation:
The requester is not serviceable.
0x8892 AUTO RECONNECT SO REBUILD
Source:
Client Services
0x8893 AUTO RECONNECT RETRY REQUEST
Source:
Client Services
0x8894 ASYNC REQUEST IN USE
Source:
Client Services
0x8895 ASYNC REQUEST CANCELED
Source:
Client Services
0x8896 SESS SVC ALREADY REGISTERED
Source:
Client Services
Explanation:
The session for the SVC is already registered.
0x8897 SESS SVC NOT REGISTERED
Source:
Client Services
Explanation:
The session for the SVC is not registered.
0x8899 PREVIOUSLY AUTHENTICATED
Source:
Client Services
0x889A RESOLVE SVC PARTIAL
Source:
Client Services
Explanation:
An attempt to resolve the SVC is partial.
Possible Cause:
When using ConsoleOne™ 1.2d or later, this error might occur if one of the following occurs:
-
The tree name has an underscore in it.
-
The tree name has fewer than four characters.
-
The organization and the tree have the same name.
NOTE:Because of the Federated tree feature, only DNS qualified characters will work in the tree name.
Action:
Rename the tree with the correct syntax.
0x889B NO DEFAULT SPECIFIED
Source:
Client Services
Explanation:
No default was specified.
0x889C HOOK REQUEST NOT HANDLED
Source:
Client Services
0x889E AUTO RECONNECT SO IGNORE
Source:
Client Services
0x889F ASYNC REQUEST NOT IN USE
Source:
Client Services
0x88A0 AUTO RECONNECT FAILURE
Source:
Client Services
Explanation:
An auto reconnect failure occurred.
0x88A1 ERROR ABORT APPLICATION
Source:
Client Services
Explanation:
An application was aborted due to a network error.
0x88A2 ERROR SUSPEND APPLICATION
Source:
Client Services
Explanation:
An application was suspended due to a network error.
0x88A3 ERROR ABORTED PROCESS GROUP
Source:
Client Services
Explanation:
A process group was aborted due to a network error.
0x88A5 ERROR PASSWORD HAS EXPIRED
Source:
Client Services
Explanation:
The user’s password has expired.
0x88A6 ERROR NETWORK INACTIVE
Source:
Client Services
Explanation:
The network is inactive.
Source:
Client Services
Explanation:
An unknown error has occurred, or the shell or VLM program is not present.