Natural System Error Messages 1900-1949

NAT1900: Couldn"t create a connection point (SOCKET code :1:).

Text

Couldn"t create a connection point. (SOCKET code :1:).

Explanation

The socket function "socket" failed to execute because
 - No more socket descriptors are available
 - No buffer space is available
 - The network subsystem or the associated service provider
   has failed

Action

check your system for 1) socket descriptors already in use
2) enough buffer space 3) correctly installed network system

NAT1901: Couldn"t bind to a connection point (SOCKET code :1:).

Text

Couldn"t bind to a connection point (SOCKET code :1:).

Explanation

The socket function "bind" failed to execute because
 - The network subsystem has failed
 - Not enough buffers available, too many connections

Action

check your system for
 - correctly installed network system
 - enough buffer space

NAT1902: Socket error :1: : Couldn"t resolve service port.

Text	TODO
Explanation	TODO
Action	TODO

NAT1903: Couldn"t connect to remote debugging service (SOCKET code :1:).

Text

Couldn"t connect to remote debugging service (SOCKET code :1:).

Explanation

Natural cannot create a connection to the remote debugging service
because of one of the following reasons:
  - the specified remote debugging node is not accessible
  - the remote debugging service is not active
  - the used port id does not match the port of the remote
    debugging service
  - the remote debugging service did not initialise correctly
Check that
  - the NT machine where the remote debugging service
    is running is accessible (e.g. via the "ping" command)
  - the remote debugging service is installed and
    running
  - the port used to install the service (default=2500)
    matches the port number specified in the RDPORT parameter

Action

    matches the port number specified in the RDPORT parameter
  - the remote debugging service initialised correctly
    (take a look at NT"s event viewer for any remote debugging
    service related error entry)

NAT1904: The node name :1: could not be resolved (SOCKET code :2:).

Text

The node name :1: could not be resolved ( SOCKET code :2: ).

Explanation

the node name where the remote debugging service is supposed
to run could not be resolved

Action

check that the specified node name is available in the network system

NAT1905: Remote Debugging: Error while receiving data (SOCKET code :1:).

Text	Remote Debugging: Error while receiving data (SOCKET code :1:).
Explanation	The connection between Natural and the remote debugging service has been broken.
Action	Set up debugging session again.

NAT1906: Remote debugging: Error while sending data (SOCKET code :1:).

Text	Remote debugging: Error while sending data (SOCKET code :1:).
Explanation	The connection between Natural and the remote debugging service has been broken.
Action	Set up debugging session again.

NAT1907: Establishing a local debugging session failed.

Text	Establishing a local debugging session failed.
Explanation	This platform does not provide a Natural Debugger
Action	Use Natural"s remote debugging facility to debug the application.