|
Code
|
Class
|
Type
|
Description
|
|---|---|---|---|
|
21100
|
Communication
|
Warning
|
Illegal value value for configuration parameter parameter, using default.
An illegal value was given to the parameter parameter. The server will use a default value for this parameter.
|
|
21101
|
Communication
|
Warning
|
Invalid protocol definition protocol in configuration file.
The protocol is defined illegally in the configuration file. Check the syntax of the definition.
|
|
21300
|
Communication
|
Error
|
Protocol connect_string is not supported. Most likely the protocol name in the connect string is misspelled. Check the connect string.
|
|
21301
|
Communication
|
Error
|
Cannot load the dynamic link library library or one of its components.
The server was unable to load the dynamic link library or a component needed by this library. Check the existence of necessary libraries and components.
|
|
21302
|
Communication
|
Error
|
Wrong version of dynamic link library library.
The version of this library is wrong. Update this library to a newer version.
|
|
21303
|
Communication
|
Error
|
Network adapter card is missing or needed protocol software is not running. The network adapter card is missing or not functioning.
|
|
21304
|
Communication
|
Error
|
Out of protocol resources
The network protocol is out of resources. Increase the protocols’ resources in the operating system.
|
|
21305
|
Communication
|
Error
|
An empty or incomplete network name was specified.
The network name specified is not legal. Check the network name.
|
|
21306
|
Communication
|
Error
|
Server network name not found, connection failed.
The server was not found. 1) Check that the server is running. 2) Check that the network name is valid. 3) Check that the server is listening to the given network name. 4) Check that the TLS settings are correct.
|
|
21307
|
Communication
|
Error
|
Invalid connect info network name.
The network name given as the connect info is not legal. Check the network name.
|
|
21308
|
Communication
|
Error
|
Connection is broken (protocol read/write operation failed with code internal code).
The connection using the protocol is broken. Either a read or a write operation has failed with an internal error internal code.
|
|
21309
|
Communication
|
Error
|
Failed to accept a new client connection, out of protocol resources.
The server was not able to establish a new client connection. The protocol is out of resources. Increase the protocol’s resources in the operating system.
|
|
21310
|
Communication
|
Error
|
Failed to accept a new client connection, listening of network name interrupted.
The server was not able to establish a new client connection. The listening has been interrupted.
|
|
21311
|
Communication
|
Error
|
Failed to start a selecting thread for network name. A thread selection has failed for network name.
|
|
21312
|
Communication
|
Error
|
Listening info network name already specified for this server.
A network name has already been specified for this server. A server can not use a same network name more than once.
|
|
21313
|
Communication
|
Error
|
Already listening with the network name network name.
You have tried to add a network name to a server when it is already listening with that network name. A server can not use a same network name more than once.
|
|
21315
|
Communication
|
Error
|
Cannot start listening, invalid listening info network name.
The server can not start listening with the given listening info. The given network name is invalid. Check the syntax of the network name.
|
|
21316
|
Communication
|
Error
|
Cannot stop the listening of network name. There are clients connected.
You can not stop listening of this network name. There are clients connected to this server using this network name.
|
|
21317
|
Communication
|
Error
|
Failed to save the listen information into the configuration file.
The server failed to save this listening information to the configuration file. Check the file access rights and format of the configuration file.
|
|
21318
|
Communication
|
Error
|
Operation failed because of an unusual protocol return code code. Possible network error or TLS certificate verification error. Create connection again.
|
|
21319
|
Communication
|
Error
|
RPC request contained an illegal version number.
Either the message was corrupted or there may be a mismatch between server and client versions.
|
|
21320
|
Communication
|
Error
|
Called RPC service is not supported in the server.
There maybe a mismatch between server and client versions.
|
|
21321
|
Communication
|
Error
|
Protocol protocol is not valid, try using switch -a for specifying another adapter id instead of switch.
This is returned if the NetBIOS LAN adapter id given in listen/connect string is not valid.
|
|
21322
|
Communication
|
Error
|
The host machine given in connect info '%s' was not found.
This is returned in clients if the host machine name given in connect info is not valid.
|
|
21323
|
Communication
|
Error
|
Protocol protocol can not be used for listening in this environment.
This message is displayed if the server end communication using specified protocol is not supported.
|
|
21324
|
Communication
|
Error
|
The process does not have the privilege to create a mailbox.
|
|
21325
|
Communication
|
Error
|
Only one listening name is supported in this server.
|
|
21326
|
Communication
|
Error
|
Failed to establish an internal number socket connection code number.
solidDB® uses one connect socket for internal use. Creation of this socket has failed; the local loopback may not be working correctly.
|
|
21327
|
Communication
|
Error
|
Too many name resolver requests already in progress.
|
|
21328
|
Communication
|
Error
|
Timeout while resolving host name.
|
|
21329
|
Communication
|
Error
|
Timeout while connecting to host.
|
|
21330
|
Communication
|
Error
|
Failed to accept a new client connection, too many open files
|
|
21331
|
Communication
|
Error
|
Cannot load OpenSSL library
|