| Text | Connect to server ... port ... failed; socket code .... |
| Expl. |
A connection to the development server failed due to one of the following reasons: - A wrong development server name was specified. - The specified port ID does not match the port where the development server is listening. - The development server is not active. - The server machine hosting the development server is not active. |
| Actn. |
Check that the specified name matches the development server name, the development server is active, its port matches the specified port, and the server machine is accessible (e.g. via "ping" command). |
| Text | Protocol mismatch of Server Nat ... (...) and Nat Studio (...) |
| Expl. |
The protocol versions of the Natural Development Server and the Natural Studio do not match. Although the Natural Studio can run with servers using an older or newer version of the protocol, some functionality might not or only partly be supported. |
| Actn. |
Upgrade the Natural Development Server or the Natural Studio. |
| Text | Development server file for application ... not unique. |
| Expl. |
The specified development server file differs from the active development server file. All mapped applications have to use one common development server file. |
| Actn. |
Change the development server file for the current application. |
| Text | Connection to NDV server lost or network failure. |
| Expl. |
The remote Natural session or the Natural Development Server (NDV) has terminated abnormally, or a network failure has occurred. - Examine the NDV trace output for information on the connection termination. If NDV trace contains no such information, contact your network administrator. Try to remap the session to the server. - If the problem persists, check in the NDV server trace whether your buffer has arrived: - If data have arrived, check for error information in subsequent trace records. - If no data have arrived, contact your network administrator. |
| Actn. |
See explanation above. |
| Text | Command not applicable within the current context. |
| Expl. |
The issued command cannot be executed in the selected remote environment or application context. Possible reasons are: - The command is not available for the selected environment or application; e.g. the command "Connect" is issued for a compound application. - The command is not available for the current state of the selected environment or application; e.g. the command "Activate" is issued for a disconnected environment, although only connected environments can be activated. |
| Actn. |
Check whether all conditions for issuing the command are fulfilled. |
| Text | Command not supported by Natural Development Server. |
| Expl. |
The issued command is not supported by the protocol version of the Natural Development Server. |
| Actn. |
Upgrade the Natural Development Server. |
| Text | Invalid value specified. |
| Expl. |
The value which has been assigned to a property or was specified as method parameter is not allowed in this context. |
| Actn. |
Assign a valid attribute value, or use a valid method parameter. |
| Text | Natural ... cannot be used to access NDV server. |
| Expl. |
This Natural version is not capable of using the requested NDV server. |
| Actn. |
Upgrade Natural Studio. |
| Text | Environment name ... already exists. |
| Expl. |
The specified environment name is already used either by another mapped environment or by a mapped application. |
| Actn. |
Use a different name for the environment to be mapped. |
| Text | Function not available, because ... is not installed. |
| Expl. |
The required component must be installed in order to perform the function specified or to process the object specified. |
| Actn. |
Install component, or do not use this function. |
| Text | Remote Debug could not be started. |
| Expl. |
An internal error occurred which prevented the session for Remote Debug from being started. For details see the NDV trace, at least trace-level bit 15 should be activated. |
| Actn. |
Contact Software AG support. |
| Text | Internal error during Remote Debug, terminating. |
| Expl. |
The connection to Remote Debug could not be maintained because of internal errors. For details see the NDV trace, at least trace-level bit 15 should be activated. |
| Actn. |
Contact Software AG support. |
| Text | Parameter error in MAP/UNMAP command. |
| Expl. |
The MAP/UNMAP command cannot be performed, because the specified parameters are not correct. Possible errors are, for example: - Mandatory parameters of the MAP command are missing (for APPL= at least the application name has to be specified; for ENV= at least the server name and the port number have to be specified). - No parameters are specified for the UNMAP command, but the local environment is active. - The application/environment specified in the UNMAP command cannot be found. See the Natural system commands documentation for further information. |
| Actn. |
Correct the parameter specification. |
| Text | The debugger port is already in use. |
| Expl. |
The debugger port specified via the SPODDEBUGPORT parameter is already used by a different program. Therefore the remote connection to the Natural application could not be established. |
| Actn. |
Set the SPODDEBUGPORT parameter to a different value. Or set the SPODDEBUGPORT parameter to 0; Natural Studio will then automatically select a free port on the machine for debugging. |
| Text | ... locked by .... |
| Expl. |
No detailed explanation available. |
