0% found this document useful (0 votes)
9 views

NetC Err

automation studio
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
9 views

NetC Err

automation studio
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 4

-1 SERVER NOT FOUND

The specified server does not exist.


-2 INVALID CONNECTION
A handle has been specified which is outside the legal range of
values.
-3 ALGORITHM NOT FOUND
There are no available licenses on the network with the specified
developer ID or algorithm.
-4 OUT OF HANDLES
All servers for this identifier are out of handles. Usually, this
means there are no available licenses on the network with the
specified developer ID or algorithm. It may also mean that the
handle limit configured for one or more servers is lower than the
sum of the limits of the attached keys. To correct this, restart
the server with the /H option.
-5 HANDLE ALREADY LOCKED
This key is already locked (by the same or another user).
-6 HANDLE LOCKED
Another user has placed a lock on the key (using Lock Key). Queries
from other users are inhibited until that lock is removed.
-7 INVALID FUNCTION
The specified function is not a valid NetSentinel interface
function.
-8 INVALID UNIT
The specified key is not connected to the server.
-9 RPC ERROR
A network error occurred. This may mean that the server you were
connected to is no longer reachable.
-10 ALGORITHM NOT FOUND
There are no available licenses on the network with the specified
developer ID or algorithm.
-11 OUT OF HANDLES
All available handles for this application have been used.
-12 NO NETSENTINEL SERVERS
No security servers can be found on this network.
-13 BAD HANDLE
The handle you specified is not assigned to any current license.
-14 NO MORE KEYS
No other NetSentinel keys with this developer ID or algorithm and a
free license can be found on the network.
-15 HANDLE LOCKED
Another user has placed a lock on the key (using Lock Key). Queries
from other users are inhibited until that lock is removed.
-16 HANDLE ALREADY LOCKED
The key is already locked (by the same or another user).
-17 SERVER DIED
The server to which you were connected failed to responde. It may be
disconnected from the network.
-18 SERVER PROTOCOL
The server does not support communications with your NetSentinel
user library (version mismatch).
-19 NETWORK INIT
An error occurred during network initialization.
-20 SERVER NOT FOUND
The specified server does not exist.
-21 CANNOT CONNECT
A network error occurred while trying to connect to the server.
-22 SERVER BUSY
All communication threads for the server are in use. This error is
returned only if you have specified non-blocking mode; by default,
a busy server is retried automatically.
-23 KEY REMOVED
The server has detected that your security key has been removed
from a parallel port and replaced by a different key.
-24 USER BUSY
The DLL is already processing a call with this user handle. This
error can occur if the "Yield To Windows" option is enabled using
the Set Rainbow Windows Parameters function.
-25 TASK TABLE FULL
The DLL is being used by too many applications.
-26 API ERROR
Either the department name is illegal or the max server number
is out of range.
-27 INVALID REQUEST
Incorrect parameters have been passed to Set Rainbow Library
Parameters.
-28 INVALID HANDLE TABLE REQ
The number of handles specified is smaller than the size of the
current table. The handle table can grow larger but never smaller.
-29 MEMORY ALLOCATION ERROR
A request to allocate memory from the operating system has failed.
-30 VERSION NOT SUPPORTED
The user loader you are using does not support the version of
linked-in NetSentinel code in your application.
-31 LOADER NOT INSTALLED
In the WATCOM interface (Loader version), the loader was not used
to load the client application.
-32 UNSUPPORTED PROTOCOL
The user library you are using does not support the specified
protocol.
-33 OPTION NOT AVAILABLE
You have called Access sub license with a session handle which
does not reference a NetSentinel-C key. Sub-licensing is only
supported on the NetSentinel-C.
-34 MAX LICENSE REACHED
You have attempted to open a sub-license at a time when all
sub-licenses are already in use.
-35 LICENSE TABLE FULL
The NetSentinel server's sub-license table is full. Re-start your
server using the /SL�:nnnnn command line option, where nnnnn is the
maximum number of sub-licenses you expect to be open by all users
at any one time (the default value is 256).
-36 KEY REMOVED
A key containing one of your currently open sub-licenses has been
removed.
-37 KEY CONTENT CHANGED
The sub-licensing configuration of one of your keys has been
changed. You must always bring down the security server before
changing the contents of a sub-licensing key.
-38 OUT OF RANGE
You have specified a sub-license number whose value is within
legal limits (0-56) but which is greater than the largest
sub-license number defined in any of your keys.
-39 NOT IN USE
You have attempted to close a sub-license which is not currently
open.
-40 INVALID ASLCMD
You have specified an invalid command code in Access sub license.
-41 RSP PTR NULL
You have supplied a null response buffer address (0000) in an
ASL_GET_INFO command.
-42 INVALID SUBLICENSE
You have specified a sub-license number greater than 56 in Access
sub license.
-43 FUNC NOT AVAIL LOCAL
The function specified is not valid for local mode.
-44 INIT THREAD ERROR
Initialization of user thread process failed. Virtual memory
may be running low. Freeing up virtual memory by shuting down
other tasks may resolve the error.
-45 INIT SEMAPHORE ERROR
Initialization of semaphore failed. Virtual memory may be running
low. Freeing up virtual memory by shuting down other task may
resolve the error.
-46 INIT PROTOCOL ERROR
Protocol failed to initialize. Either the entire transport or
part of the transport may be missing or is configured incorrectly.
-47 BAD HANDLE
The handle you specified is timed out or the handle value is
corrupted.
-48 GET LIB PARAMS ERROR
An general error occurred when calling Get Rainbow Library
Parameters. This may mean it failed to get the NetSentinel OS/2
system driver status.
-49 INVALID LIB PARAMS FUNC
The specified function is not a valid Get Rainbow Library
Parameters or Set Rainbow Library Parameters function.
-50 INVALID KEY TYPE
The specified key type was not NetSentinel-Pro nor NetSentinel-C.
-51 SET LIB PARAMS ERROR
An general error occurred when calling Set Rainbow Library
Parameters.
-52 DRIVER CONFIGURE ERROR
An error occurred while trying to configure the NetSentinel system
driver.
-53 GET DRIVER INFO ERR
Failed to get NetSentinel system driver information.
-54 INIT RDP ERR
An error occurred during NetSentinel system driver initialization.
-55 HANDLE NOT FOUND
The handle you specified is not assigned to any current license.
-56 TASK NOT FOUND
The current task/application cannot been found in NetSentinel task
table.
-57 BAD OFFSET
You have specified a handle greater than maximum number of licenses.
-58 KEY CORRUPTED
Found Invalid data in key.
-59 DRIVER READ ERROR
An error occurred while reading the key.
-896 / FC80
The NetSentinel-C may be in the middle of an operation and cannot
start another operation. Alternatively, there may not be a
NetSentinel-C attached to LPT1.
-897 / FC7F
The software is corrupted. Try reloading the software from the
release diskette. If the problem persists,contact Rainbow
Technologies.
-898 / FC7E
The software is corrupted. Try reloading the software from the
release diskette. If the problem persists, contact Rainbow
Technologies.
-899 / FC7D
Port LPT1 is malfunctioning, does not exist, or has had its
address removed by some other software. If the port cannot be
repaired, use a different computer.
-993 / FC1F
The requested command is not valid. Refer to the list of valid
commands provided in the Rainbow user's guide.
-994 / FC1E
No NetSentinel-C key can be detected. Make sure the key is securely
connected to port LPT1. Retry the operation in case there is a
hardware problem causing intermittent access failures.
-995 / FC1D
The requested command has one or more invalid parameters. Make sure
the parameters are in the correct order, that each parameter is
within the proper range, and that there are no extraneous
characters.
-997 / FC1B
You are trying to output to the key, but did not enter the correct
Read or Write password.

You might also like