| Text | SAGExt version incorrect. |
| Explanation | The SAGExt.DLL does not have the correct version. Entire Connection cannot be started. |
| Action | Repair your Entire Connection installation. |
| Text | OLE initialization failed. |
| Explanation | OLE initialization failed. Entire Connection cannot be started. |
| Action | Check your Windows system. Make sure that the OLE libraries have the correct version. |
| Text | Error on startup. |
| Explanation | Error on startup. Entire Connection cannot be started. |
| Action | Repair your Entire Connection installation. |
| Text | Initialization failed. |
| Explanation | The Entire Connection initialization failed. The parameters you passed are not valid. |
| Action | Correct the startup parameters and restart Entire Connection. |
| Text | Error starting Entire Connection. |
| Explanation | An unrecoverable error occurred while starting Entire Connection. |
| Action | Check your Entire Connection installation and configuration, and retry. |
| Text | Initialization failed. |
| Explanation | An unrecoverable error occurred while initializing Entire Connection. |
| Action | Check your Entire Connection installation and configuration, and retry. |
| Text | User properties record does not exist. |
| Explanation | You selected "Use Windows user name for logon" and "Create user properties automatically" in the "System Preferences and Settings" dialog box. The user properties record for Windows user-name does not exist. |
| Action | Select "Yes" if you want to create the user properties with the default values. Contact your Entire Connection administrator if you are not sure what to do. |
| Text | Unknown user name or password. |
| Explanation | Logon to Entire Connection failed. The user name or password entered is unknown to Entire Connection. |
| Action | Check and correct the user name and the password. |
| Text | Already logged on with this user name. |
| Explanation | You are already logged on with user-name to another Entire Connection terminal you started on the PC. You cannot run multiple Entire Connection terminals with different users logged on at the same time. |
| Action | Check the startup parameters and the setting of "Use Windows user name for logon" in the "System Preferences and Settings" dialog box. |
| Text | Error with user-defined menu. |
| Explanation | An error was detected in the definition of the user-defined menu. The menu you selected could not be displayed. |
| Action | Check the definitions of the menu in the Entire Connection Configuration Manager. |
| Text | No tasks and procedure files found. |
| Explanation | No tasks and no procedure files were found. There may be a problem with the share file or the procedure folder setting. |
| Action | Check the defined tasks and the procedure folder setting in the Entire Connection Configuration Manager. |
| Text | Error occurred in starting command, task or procedure file. |
| Explanation | The command, task or procedure file you wanted to execute could not be started. |
| Action | Check your Entire Connection installation and configuration, and retry. |
| Text | Canceling procedure has been rejected. |
| Explanation | Canceling procedure has been rejected. The Entire Connection system is instable. |
| Action | Check your Windows system for unusual high memory usage. Restart Entire Connection. |
| Text | Running procedure file has been rejected. |
| Explanation | Running the procedure file has been rejected. The Entire Connection system is instable. |
| Action | Check your Windows system for unusual high memory usage. Restart Entire Connection. |
| Text | Procedure debugger has nothing to run. |
| Explanation | You are in the procedure debugger but there are no procedure files or no more procedure commands to execute. |
| Action | Check and correct. |
| Text | Error opening session. |
| Explanation | Failed to open session. |
| Action | Check the session properties of the session you tried to open. |
| Text | Maximum number of concurrent open terminal windows has exceeded. |
| Explanation | The number of open terminal windows is limited in your user properties. The maximum number of concurrent open terminal windows has exceeded. No new terminal window could be opened. |
| Action | Close terminal windows that you do not need. Contact your Entire Connection system administrator if you need more concurrent open sessions. |
| Text | No sessions are currently defined. |
| Explanation | Failed to open session. No sessions are currently defined. |
| Action | Check your share file and create session properties for the hosts you want to use. |
| Text | The Configuration Manager was not found. |
| Explanation | Starting the Entire Connection Configuration Manager from the terminal window failed. The executable for the Configuration Manager (Pccadmin.exe) was not found. |
| Action | Repair your Entire Connection installation. |
| Text | The Configuration Manager cannot be started. |
| Explanation | The Configuration Manager cannot be started. There was an error with error-code error-code when starting the Entire Connection Configuration Manager. |
| Action | Check your Entire Connection installation and configuration, and retry. |
| Text | The Host Printer Manager was not found. |
| Explanation | Starting the Entire Connection Host Printer Manager failed. The executable for the Host Printer Manager (PccPLUMn.exe) was not found. |
| Action | Repair your Entire Connection installation. |
| Text | The Host Printer Manager cannot be started. |
| Explanation | The Host Printer Manager cannot be started. There was an error with error-code error-code when starting the Entire Connection Host Printer Manager. |
| Action | Check your Entire Connection installation and configuration, and retry. |
| Text | Error reading unattended workstation data. |
| Explanation | An error occurred while reading the scheduling data for the unattended workstation. Cannot enter unattended mode. |
| Action | Check your scheduling data for the unattended workstation. Check your hard disk. Restore your share file from a backup and retry. |
| Text | Error writing the unattended workstation scheduling data. |
| Explanation | An error occurred while writing the unattended workstation scheduling data to the share file. |
| Action | Check your hard disk. Restore your share file from a backup and retry. |
| Text | Missing ending quote in startup parameter. |
| Explanation | The startup parameter token has a beginning quote (" or '), but no ending quote (" or '). If you use quotes for string arguments, they must be paired. You have to use quotes for strings containing blanks. |
| Action | Check and correct. |
| Text | Error parsing startup parameters. |
| Explanation | An error occurred while parsing the startup parameters. |
| Action | Check and correct. |
| Text | Startup parameters too long. |
| Explanation | You entered too many characters for the startup parameters - the maximum length for all startup parameters is 192 characters. |
| Action | Check and correct. |
| Text | Internal error: No share file name passed. |
| Explanation | No share file name was passed to the loader routine. Internal error. Can only happen in the development environment. |
| Action | No action required. |
| Text | Error opening share file. |
| Explanation | Opening the share file name returned an error with error-code error-code. The error-code is the return code of the Open File function of Windows. Entire Connection cannot be started. |
| Action | Check your hard disk. Restore your share file from a backup and retry. |
| Text | SYSTEM properties record not found. |
| Explanation | The SYSTEM properties record was not found in share file name. Entire Connection cannot be started. |
| Action | Check your hard disk. Restore your share file from a backup and retry. |
| Text | Error reading share file. |
| Explanation | An error occurred while reading the share file name. Entire Connection cannot be started. |
| Action | Check your hard disk. Restore your share file from a backup and retry. |
| Text | Wrong share file version. |
| Explanation | The share file name is not compatible with the current version of Entire Connection. Entire Connection cannot be started. |
| Action | Check and correct. |
| Text | File is not an Entire Connection share file. |
| Explanation | The share file name is not an Entire Connection share file. |
| Action | Check and correct. |
| Text | WORD table missing. |
| Explanation | There is an error in the share file - the WORD table is missing. Entire Connection cannot be started. |
| Action | Restore your share file from a backup and retry. |
| Text | Terminal function code table missing. |
| Explanation | There is an error in the share file - the terminal function code table name is missing. Entire Connection cannot be started. |
| Action | Restore your share file from a backup and retry. |
| Text | Error opening table input file. |
| Explanation | An error occurred while opening the table input file name. This error can only occur in the development environment. |
| Action | No action required. |
| Text | Missing table name. |
| Explanation | The table name is missing in line number of the table input file name. This error can only occur in the development environment. |
| Action | No action required. |
| Text | Too many entries for the table. |
| Explanation | There is an error in the table input file name in line number - too many entries for the table. Only 16 entries per table are allowed. This error can only occur in the development environment. |
| Action | No action required. |
| Text | Token number error. |
| Explanation | There is an error in the table input file name in line number - incorrect number of tokens. There must be 18 hexadecimal tokens. This error can only occur in the development environment. |
| Action | No action required. |
| Text | Out of sequence. |
| Explanation | There is an error in the translation table input file name in line number - out of sequence. |
| Action | Check and correct. |
| Text | First token not equal to last token. |
| Explanation | There is an error in the translation table input file name in line number - the first token is not equal to the last token. |
| Action | Check and correct. |
| Text | Table incomplete. |
| Explanation | There is an error in the translation table input file name in line number - the table is incomplete. Rows 0 - F are required. |
| Action | Check and correct. |
| Text | Too many translation tables. |
| Explanation | There is an error in the translation table input file name in line number - too many translation tables defined. |
| Action | Check and correct. |
| Text | Error in input line. |
| Explanation | There is an error in the physical keyboard table input file name in line number. |
| Action | Check and correct. |
| Text | Missing lines in table NUMPAD. |
| Explanation | There is an error in the physical keyboard table input file - lines missing in table NUMPAD. |
| Action | Check and correct. |
| Text | Missing lines in table KEYTABLE. |
| Explanation | There is an error in the physical keyboard table input file - lines missing in table KEYTABLE. |
| Action | Check and correct. |
| Text | Too many lines in table KEYTABLE. |
| Explanation | There is an error in the physical keyboard table input file - too many lines in table KEYTABLE. |
| Action | Check and correct. |
| Text | Invalid table name. |
| Explanation | The table name name specified in the terminal function code table input file is not valid for this kind of table. Valid names are BS2, HLLAPI, N3270, VTXXX and VT_aaa, where aaa can be 1 to 28 characters long. |
| Action | Check and correct. |
| Text | No table name specified. |
| Explanation | There is an error in the terminal function code table input file name - no table name specified. |
| Action | Check and correct. |
| Text | Syntax error in command. |
| Explanation | There is a syntax error in the element token of the command in line line. This general message is used if a specific error message has not yet been implemented. It should only happen in the development environment. |
| Action | Report the error to your local Software AG support. |
| Text | Communication method not yet supported. |
| Explanation | The communication method specified in the session properties is not yet supported. This can only happen in a development test environment. |
| Action | No action required. |
| Text | Session not defined in the share file. |
| Explanation | An error occurred while reading the session data from the share file. |
| Action | Reorganize the share file with the Configuration Manager (go to the Tools menu and choose Reorganize Share File). If the error is still there, create the session again or use a backup copy of your share file. |
| Text | Data transfer has aborted. |
| Explanation | The Natural data transfer with Entire Connection has aborted. The previous error messages contain more details about the cause. |
| Action | If the data transfer has aborted because of an error, save the error trace file XFER_ERR.TRC from the log and trace directory, and report the error to your local Software AG support including the error trace file. |
| Text | The interface to the print service could not be opened. |
| Explanation | The associated printer session was not created. Printing to the associated printer session failed. |
| Action | Close the display session and open it again. If the error persists, report the error to your local Software AG support. |
| Text | Communication method not supported by terminal server. |
| Explanation | The communication method specified in the session you tried to open is not supported by the terminal server. Because of technical restrictions, the communication methods "HLLAPI" and "Serial VTxxx" cannot be used on a terminal server. |
| Action | Use a local installation if you want to use these communication methods. |
| Text | Communication method no longer supported. |
| Explanation | The communication method specified in the session you tried to open is no longer supported. |
| Action | Check the Entire Connection documentation, chapter Installation, Supported Communication Methods for alternative communication methods. |
| Text | Error text not found. |
| Explanation | The error text for the error number n could not be found. This should only happen during development. |
| Action | Report the error to your local Software AG support. |
| Text | File access error. |
| Explanation | An error occurred while accessing the file file. The operating system error-code was n. |
| Action | Check the operating system error-code for details. You find a list of the operating system error-codes in your operating system documentation. |
| Text | Internal error. |
| Explanation | Internal error while parsing the BS2000 9750 data stream. This can only happen in a development test environment. |
| Action | No action required. |
| Text | Internal error. |
| Explanation | Internal error in the command parser routine cp_subst. |
| Action | If the error persists, report the error to your local Software AG support. |
| Text | Internal error. |
| Explanation | Internal error in the routine cp_setke. |
| Action | If the error persists, report the error to your local Software AG support. |
| Text | Dynamic variables cannot be set. |
| Explanation | You cannot set a value for a dynamic variable. Dynamic variables start with an asterisk (*). |
| Action | See chapter Terminal Emulation, Procedure Files, Variables in Procedure Files in the Entire Connection documentation. |
| Text | Internal error. |
| Explanation | Internal error in the routine cp_value. |
| Action | If the error persists, report the error to your local Software AG support. |
| Text | Cannot not open audit log file. |
| Explanation | The audit log file file-name could not be created or opened. Possible reasons are a wrong setting for the user's log and trace directory or disk problems. |
| Action | Check the setting of the user's log and trace directory in the Configuration Manager, User Properties, Procedure dialog. |
| Text | Internal error - unknown command in pcode. |
| Explanation | Internal error in the routine cp_rout. |
| Action | If the error persists, report the error to your local Software AG support. |
| Text | Task does not exist. |
| Explanation | The task task-name was scheduled for execution but does not or no longer exist in the share file. |
| Action | Check the task definitions with the Entire Connection Configuration Manager. |
| Text | Internal error. |
| Explanation | Internal error in the routine js_exec. |
| Action | If the error persists, report the error to your local Software AG support. |
| Text | Internal error. |
| Explanation | Internal error in the routine js_exec. |
| Action | If the error persists, report the error to your local Software AG support. |
| Text | DOS task cannot be executed. |
| Explanation | The task task-name cannot be executed. In your user properties, DOS tasks are marked to be not allowed for you. The property to disallow DOS tasks is no longer supported since version 4 of Entire Connection. This error can only occur if you merged a version 3 share file containing tasks which use this property. |
| Action | Delete and then re-create the user properties with the current version of the Entire Connection Configuration Manager. |
| Text | Error starting task. |
| Explanation | An operating system error occurred when trying to start the Entire Connection task task-name with the program program-name |
| Action | Check the task definition. |
| Text | Task does not exist. |
| Explanation | The task task-name does not exist in the share file. |
| Action | Check the task name used and also the task definitions in the share file. |
| Text | Missing ending quotes in literal string. |
| Explanation | The string string in token n does not have ending quotes. Procedure file input arguments must have paired quotes. |
| Action | Correct error. |
| Text | Unknown dynamic variable. |
| Explanation | An unknown dynamic variable is used in the command. This should only happen in the development environment. |
| Action | Report the error to your local Software AG support. |
| Text | LocalLock failed. |
| Explanation | A memory request to the Windows operating system failed. The current Entire Connection operation failed. |
| Action | Stop Entire Connection, close other Windows applications, and then try again. |
| Text | No more tables available. |
| Explanation | The internal table manager of Entire Connection ran out of space. This should only happen in the development environment. |
| Action | Stop Entire Connection and retry. If the error persists, report the error to your local Software AG support. |
| Text | Unknown command or task. |
| Explanation | The command or task name in line n is unknown in Entire Connection. |
| Action | Specify a valid command. See the Entire Connection documentation for information on the commands. |
| Text | Operation could not be completed. |
| Explanation | You cannot modify session related variables from the command line. |
| Action | No action required. |
| Text | No command specified. |
| Explanation | A command containing only blanks was entered. |
| Action | Specify a valid command. |
| Text | Invalid file number in command. |
| Explanation | Invalid file number for command cmd in line n Valid file numbers are 1,2,3 or 4. See the Entire Connection documentation for information on the commands OPEN, CLOSE, READ and WRITE. |
| Action | Correct the command. |
| Text | OPEN requires a file name. |
| Explanation | The OPEN command in line n requires a file name. See the Entire Connection documentation for information on the command OPEN. |
| Action | Correct error. |
| Text | READ command requires global or local parameter variables. |
| Explanation | The READ command requires global or global parameter variables. You may use +PARM0 - +PARM9 and/or #PARM0 - #PARM9. See the Entire Connection documentation for information on the command READ. |
| Action | Correct error. |
| Text | Local variable may not be set at this time. |
| Explanation | A local procedure variable cannot be specified in the command line (using the SET command). Local variables can only be used in procedure files. See the Entire Connection documentation for information on the commands. |
| Action | Correct error. |
| Text | You cannot use a SET key command within a SET key command. |
| Explanation | You may not use a SET PCKEY/TEKEY command within a SET PCKEY/TEKEY command. |
| Action | Correct error. |
| Text | Too many parameters for the command. |
| Explanation | Too many parameters are given for the command cmd. For example, only 10 parameters are allowed for the command EXECUTE. |
| Action | Correct error. |
| Text | Wrong screen range in *SCREEN variable. |
| Explanation | The screen range given for the *SCREEN variable is less than the length of the compare string. For information on how to use the *SCREEN variable, see the documentation for the Entire Connection command IF. |
| Action | Correct error. |
| Text | Literal string does not have ending quotes. |
| Explanation | Literal string does not have ending quotes. Quoted strings must be paired. |
| Action | Correct error. |
| Text | NULL string not valid. |
| Explanation | An empty string (NULL string) is not valid in compare commands such as IF or WAITFOR. |
| Action | Correct error. |
| Text | Command TYPE not allowed. |
| Explanation | The TYPE command is not allowed in this statement. |
| Action | Remove the TYPE command from the statement. |
| Text | Invalid use of local variable. |
| Explanation | Invalid use of local variable. You cannot use a local variable with the commands CLOSE, INPUT, OPEN-I, OPEN-O, READ, SET PCFILE, WAITM and WRITE. |
| Action | Correct error. |
| Text | Unsupported key type in SET key_var statement. |
| Explanation | The key type used in the SET key_var statement is no longer supported. Valid key type for key_var is TEKEY. |
| Action | Correct error. |
| Text | TEKEY may not be set at this time. |
| Explanation | You cannot set a TEKEY at this time. |
| Action | Use the "Terminal Emulation Key Scheme" dialog box of the Entire Connection Configuration Manager. |
| Text | VTKEY may not be set at this time. |
| Explanation | You cannot set a VTKEY at this time. |
| Action | Modify the appropriate .key table file in the tables folder of your installation. Then use the "Terminal function code" dialog of the Entire Connection Configuration Manager to import the table. |
| Text | 3278KEY may not be set at this time. |
| Explanation | You cannot set a 3278KEY at this time. |
| Action | Modify the appropriate .key table file in the tables folder of your installation. Then use the "Terminal function code" dialog of the Entire Connection Configuration Manager to import the table. |
| Text | Only one *SCREEN variable allowed. |
| Explanation | Only one *SCREEN variable may be used in the command. |
| Action | Correct error. |
| Text | Invalid PCFILE number in SET PCFILE command. |
| Explanation | The file number specified in the SET PCFILE command is not valid. The file number must be an integer value in the range 1 - 32. |
| Action | Correct error. |
| Text | Invalid combination of parameters in SET PCFILE command. |
| Explanation | The parameters UP and REPORT cannot be combined in the SET PCFILE command. |
| Action | Correct error. |
| Text | *SCREEN variable cannot be used from the command line. |
| Explanation | The variable *SCREEN cannot be used from the command line. *SCREEN can be used from a procedure file. |
| Action | Correct error. |
| Text | Too many tokens after *SCREEN variable. |
| Explanation | No more tokens are allowed after *SCREEN format. For information on how to use the *SCREEN variable, see the Entire Connection documentation for information on the command IF. |
| Action | Correct error. |
| Text | Invalid value for MINUTE parameter. |
| Explanation | The value for the MINUTE parameter must be an integer value. |
| Action | Correct error. |
| Text | Number or variable expected. |
| Explanation | A number or variable was expected. You must use an integer or a variable that contains an integer. |
| Action | Correct error. |
| Text | PARITY keyword or variable expected. |
| Explanation | A PARITY keyword or variable was expected. You must use a PARITY keyword or a variable that contains an integer. |
| Action | Correct error. |
| Text | BINARY keyword or variable expected. |
| Explanation | A BINARY keyword or variable expected. You must use a BINARY keyword or a variable here. |
| Action | Correct error. |
| Text | String or variable expected. |
| Explanation | A string or variable expected was expected at the position n. You may use a quoted string or a variable. |
| Action | Correct error. |
| Text | Command expected. |
| Explanation | A command was expected at the position n. You can use any Entire Connection command except IF, IFNOT, WAITFOR. |
| Action | Correct error. |
| Text | Command expected. |
| Explanation | A command was expected at the position n. You can use any Entire Connection command here. |
| Action | Correct error. |
| Text | Command not valid here. |
| Explanation | Command cmd not valid here. This command cannot be used from the command line. |
| Action | Correct error. |
| Text | Syntax error. |
| Explanation | Syntax error in token n. No matching command or variable found. |
| Action | Correct error. |
| Text | System variable, global variable or local variable expected. |
| Explanation | The token at position n should be a system variable, a global variable or a local variable. |
| Action | Correct error. |
| Text | A label expected. |
| Explanation | The token at position n should be a label. |
| Action | Correct error. |
| Text | Invalid label. |
| Explanation | The label at position n is not valid. A label can't be greater then 12 characters. |
| Action | Correct error. |
| Text | Command expected. |
| Explanation | The token at position n should be a command. |
| Action | Correct error. |
| Text | TEKEY keyword expected. |
| Explanation | The TEKEY keyword is expected as token n. |
| Action | Correct error. |
| Text | Variables not allowed here. |
| Explanation | The token 3 in a SET TEKEY command must be a keyword for a key of the physical keyboard, for example, F1. |
| Action | Correct error. |
| Text | Keyword for key of physical keyboard expected. |
| Explanation | The token 3 in a SET PCKEY command must be a keyword for a key of the physical keyboard, for example, F1. |
| Action | Correct error. |
| Text | VT100 key expected. |
| Explanation | The token 3 in a SET VTKEY command must be the keyword for a VT100 key. Used in SET VTKEY commands in the terminal function code tables. |
| Action | Contact your local Software AG support for assistance to correct error. |
| Text | XCLOCK/KEYRESET keyword or TYPE keyword expected. |
| Explanation | An XCLOCK/KEYRESET keyword or TYPE keyword was expected but not found. Used in SET 3278KEY and SET VTKEY commands in the terminal function code tables. |
| Action | Contact your local Software AG support for assistance to correct error. |
| Text | Keyword for terminal emulation key expected. |
| Explanation | A keyword for a terminal emulation key was expected but not found. Used in SET 3278KEY and SET VTKEY commands in the terminal function code tables. |
| Action | Contact your local Software AG support for assistance to correct error. |
| Text | Keyword for PC key expected. |
| Explanation | A keyword for a PC key was expected but not found. Used in SET 3278KEY and SET VTKEY commands in the terminal function code tables. |
| Action | Contact your local Software AG support for assistance to correct error. |
| Text | Literal or keyword for a VT100 key expected. |
| Explanation | A literal or a keyword for a VT100 key was expected but not found. Used in SET VTKEY commands in the terminal function code tables. |
| Action | Contact your local Software AG support for assistance to correct error. |
| Text | Token not a keyword for a VT100 key. |
| Explanation | A keyword for a VT100 key was expected but not found. Used in SET VTKEY commands in the terminal function code tables. |
| Action | Contact your local Software AG support for assistance to correct error. |
| Text | Token not a literal, global variable, system variable or PC key. |
| Explanation | A literal, global variable, system variable, or PC key was expected but not found. Used in internal tables in SET key commands. |
| Action | Contact your local Software AG support for assistance to correct error. |
| Text | Token not a literal, global variable, system variable, or terminal emulation key. |
| Explanation | A literal, global variable, system variable, or terminal emulation key was expected but not found. Used in internal tables in SET key commands. |
| Action | Contact your local Software AG support for assistance to correct error. |
| Text | Global or local counter variable expected. |
| Explanation | A global or local counter variable is expected with a DECR and INCR command. See the Entire Connection documentation for information on the commands DECR and INCR. |
| Action | Correct error. |
| Text | Global or local variable expected. |
| Explanation | A global or local variable is expected with the RESETVAR command. See the Entire Connection documentation for information on the command RESETVAR. |
| Action | Correct error. |
| Text | Keyword GLOBALS or LOCALS expected. |
| Explanation | The keyword GLOBALS or LOCALS is expected with the SHIFT command. See the Entire Connection documentation for information on the command SHIFT. |
| Action | Correct error. |
| Text | Binary system variable expected. |
| Explanation | A binary system variable is expected with the TOGGLE command. See the Entire Connection documentation for information on the command TOGGLE. |
| Action | Correct error. |
| Text | *SCREEN format syntax error. |
| Explanation | *SCREEN format syntax error. A row, but no column is specified. |
| Action | Correct error. |
| Text | Literal or variable expected. |
| Explanation | A literal or variable is expected after token n. |
| Action | Correct error. |
| Text | Operator expected. |
| Explanation | An operator is expected after token n. |
| Action | Correct error. |
| Text | Operator expected. |
| Explanation | An operator is expected before token n. |
| Action | Correct error. |
| Text | Operator or command expected. |
| Explanation | An operator or command is expected after token n. |
| Action | Correct error. |
| Text | Literal or variable expected. |
| Explanation | A literal or variable is expected before token n. |
| Action | Correct error. |
| Text | Operator or command expected. |
| Explanation | An operator or command is expected as token n. |
| Action | Correct error. |
| Text | Operator not allowed with the IFNOT command. |
| Explanation | An operator is not allowed with the IFNOT command. See the Entire Connection documentation for information on the command IFNOT. |
| Action | Correct error. |
| Text | PCFILE number expected after SET PCFILE. |
| Explanation | A PCFILE number is expected after SET PCFILE. See the Entire Connection documentation for information on the command SET PCFILE. |
| Action | Correct error. |
| Text | DOWN or UP expected as next token. |
| Explanation | The keyword DOWN or UP is expected after SET PCFILE fnr. See the Entire Connection documentation for information on the command SET PCFILE. |
| Action | Correct error. |
| Text | DOWN or UP expected as next token. |
| Explanation | The keyword DOWN or UP is expected after SET PCFILE fnr. See the Entire Connection documentation for information on the command SET PCFILE. |
| Action | Correct error. |
| Text | DATA or REPORT expected as next token. |
| Explanation | The keyword DATA or REPORT is expected as next token in the SET PCFILE command. See the Entire Connection documentation for information on the command SET PCFILE. |
| Action | Correct error. |
| Text | DATA or REPORT expected as next token. |
| Explanation | The keyword DATA or REPORT is expected as next token in the SET PCFILE command. See the Entire Connection documentation for information on the command SET PCFILE. |
| Action | Correct error. |
| Text | DATA or REPORT expected as next token. |
| Explanation | The keyword DATA or REPORT is expected as next token in the SET PCFILE command. See the Entire Connection documentation for information on the command SET PCFILE. |
| Action | Correct error. |
| Text | File name expected as next token. |
| Explanation | A PC file name is expected as next token in the SET PCFILE command. See the Entire Connection documentation for information on the command SET PCFILE. |
| Action | Correct error. |
| Text | Invalid token in SET PCFILE command. |
| Explanation | An additional token was specified in the SET PCFILE command. No tokens are allowed behind the PCFILE parameter. See the Entire Connection documentation for information on the command SET PCFILE. |
| Action | Correct error. |
| Text | *SCREEN format required. |
| Explanation | To use the *SCREEN variable in a SET command, the full *SCREEN format must be specified; for example *SCREEN row col len. |
| Action | Correct error. |
| Text | *SCREEN format syntax error. |
| Explanation | The *SCREEN format is *SCREEN row col len. You can use an integer value, a local variable or a global variable for row, col and len. |
| Action | Correct error. |
| Text | Too many tokens in SET PCFILE command. |
| Explanation | An additional token was specified in the SET PCFILE command. No tokens are allowed behind the PCFILE parameter. See the Entire Connection documentation for information on the command SET PCFILE. |
| Action | Correct error. |
| Text | Global or local variable expected. |
| Explanation | A global or local variable is expected as parameter 1 in the INPUT command. See the Entire Connection documentation for information on the command INPUT. |
| Action | Correct error. |
| Text | Integer for length expected. |
| Explanation | An integer length value is expected as parameter 2 in the INPUT command. See the Entire Connection documentation for information on the command INPUT. |
| Action | Correct error. |
| Text | Parameter 3 or 4 in INPUT command not a literal or variable. |
| Explanation | A literal or variable is expected as parameter 3 and 4 in the INPUT command. See the Entire Connection documentation for information on the command INPUT. |
| Action | Correct error. |
| Text | Too many parameters in INPUT command. |
| Explanation | There are too many parameters in the INPUT command. See the Entire Connection documentation for information on the command INPUT. |
| Action | Correct error. |
| Text | Too many operands. |
| Explanation | There are too many operands in the command. Check the syntax for the command used. See the Entire Connection documentation for information on the commands. |
| Action | Correct error. |
| Text | Incomplete syntax. |
| Explanation | Parameters or operands are missing. Check the syntax for the command used. See the Entire Connection documentation for information on the commands. |
| Action | Correct error. |
| Text | Invalid BAUDRATE value. |
| Explanation | The value given for the system variable BAUDRATE is not valid. Valid values are 300, 1200, 2400, 4800, 9600, 14400, 19200, 28800, 38400, 57600, 115200. |
| Action | Correct error. |
| Text | Invalid BREAKMS value. |
| Explanation | The value given for the system variable BREAKMS is not valid. Valid values are 1 - 1000. |
| Action | Correct error. |
| Text | Invalid COMMPORT value. |
| Explanation | The value given for the system variable COMMPORT is not valid. Valid values are 1 - 4. |
| Action | Correct error. |
| Text | Invalid DATABITS value. |
| Explanation | The value given for the system variable DATABITS is not valid. Valid values are 7 and 8. |
| Action | Correct error. |
| Text | Invalid STOPBITS value. |
| Explanation | The value given for the system variable STOPBITS is not valid. Valid values are 1 and 2. |
| Action | Correct error. |
| Text | Invalid UPLDELAY value. |
| Explanation | The value given for the system variable UPLDELAY is not valid. Valid values are 0 - 3200. |
| Action | Correct error. |
| Text | Invalid UPLPSIZE value. |
| Explanation | The value given for the system variable UPLPSIZE is not valid. Valid values are 1 - 1920. Note: this System variable is deprecated with PCC453. |
| Action | Correct error. |
| Text | Invalid CURSOR value. |
| Explanation | The value given for the system variable CURSOR is not valid. Valid values are 0 - 4. |
| Action | Correct error. |
| Text | Invalid ECHO value. |
| Explanation | The value given for the system variable ECHO is not valid. Valid values are 0 - 100. |
| Action | Correct error. |
| Text | Invalid RESPONSE value. |
| Explanation | The value given for the system variable RESPONSE is not valid. Valid values are 1 - 2440. |
| Action | Correct error. |
| Text | Invalid AUTOLOCK value. |
| Explanation | The value given for the system variable AUTOLOCK is not valid. Valid values are 0 - 1440. |
| Action | Correct error. |
| Text | Internal error in a local variable. |
| Explanation | There was a problem while processing a local variable. |
| Action | If the error persists, contact your local Software AG support. |
| Text | Integer value is required. |
| Explanation | The variable used in this command must contain an integer value between 0 - 32767. |
| Action | Check variable usage and correct error. |
| Text | Invalid parity value in the variable. |
| Explanation | The variable used in this command must contain a valid parity value. Valid values are 1 and 2. |
| Action | Check variable usage and correct error. |
| Text | Binary keyword required after system variable. |
| Explanation | The value in the variable used to set the system variable must be a binary keyword such as ON or OFF. |
| Action | Check variable usage and correct error. |
| Text | Invalid *SCREEN format. |
| Explanation | The values in the variables for the *SCREEN format are not valid. |
| Action | Check variable usage and correct error. |
| Text | File does not exist. |
| Explanation | A "file not found" or "file read" error occurred for file file-name. |
| Action | Check whether the file exists. |
| Text | Procedure aborted by user. |
| Explanation | The procedure was aborted by the user. The command where it was aborted is in line number of the procedure file. |
| Action | No action required. |
| Text | Internal error while parsing the procedure file. |
| Explanation | An error occurred while parsing the procedure file. The internal memory was exceeded. |
| Action | If the error persists, contact your local Software AG support. |
| Text | Internal nest limit exceeded. |
| Explanation | The procedure was terminated because the internal nest limit was exceeded. You are only allowed to nest up to 7 procedure files. |
| Action | Reduce the number of nested procedure calls. |
| Text | Host system not responding. |
| Explanation | The procedure was terminated because the host system did not respond in the configured response time. |
| Action | Check the host connection. Use the Entire Connection Configuration Manager (Session Properties, Procedure dialog) to check the response time setting for the session. |
| Text | Invalid procedure file. Lines too long or binary data found. |
| Explanation | An error occurred while parsing the procedure file. Binary data were found in a line, or a line which is too long was found. The maximum length of a procedure file line is 192 characters. |
| Action | Correct error. |
| Text | SET TEKEY command cannot be completed. |
| Explanation | The SET TEKEY command in the procedure file cannot be completed. You must first open a session. |
| Action | Open a session and retry. |
| Text | Duplicate tag in procedure file. |
| Explanation | There is more than one tag with the same label in the procedure file. |
| Action | Correct error. |
| Text | LOOPCNT exceeded. |
| Explanation | The procedure terminated because the configured loop count was exceeded. The loop count is set in the Entire Connection Configuration Manager (User Properties, Procedure dialog). |
| Action | Correct procedure file or increase loop count value. |
| Text | Tag not found. |
| Explanation | The tag tag-label was not found in the procedure file. |
| Action | Correct error. |
| Text | DOS task not allowed. |
| Explanation | Procedure terminated when trying to execute a DOS task. In your user properties, DOS tasks are marked to be not allowed for you. The property to disallow DOS tasks is no longer supported since version 4 of Entire Connection. This error can only occur if you merged a version 3 share file containing tasks which use this property. |
| Action | Delete and then re-create the user properties with the current version of the Entire Connection Configuration Manager. |
| Text | DOS commands not allowed. |
| Explanation | Procedure terminated when trying to execute a DOS command. In your user properties, DOS commands are marked to be not allowed for you. The property to disallow DOS commands is no longer supported since version 4 of Entire Connection. This error can only occur if you merged a version 3 share file containing tasks which use this property. |
| Action | Delete and then re-create the user properties with the current version of the Entire Connection Configuration Manager. |
| Text | Too many nested PERFORM commands. |
| Explanation | Procedure terminated because there are too many nested PERFORM commands. You may only nest 8 PERFORM commands. |
| Action | Correct error. |
| Text | No active PERFORM command to which to return. |
| Explanation | Procedure terminated because a RETURN was to be executed but there is no active PERFORM command to which to return. |
| Action | Correct error. |
| Text | Cannot schedule more than 32 tasks in a procedure file. |
| Explanation | Procedure terminated because you tried to schedule more than 32 tasks. You can schedule up to 32 tasks in a procedure file. |
| Action | Correct error. |
| Text | Internal buffer overflow error. |
| Explanation | An internal buffer overflow error occurred in line n. The buffer size was exceeded. |
| Action | If the error persists, report the error to your local Software AG support. |
| Text | Invalid *SCREEN format. |
| Explanation | A runtime error occurred in line n because the *SCREEN parameters built from variables are not valid. See the Entire Connection documentation for information on the command IF for usage of the *SCREEN variable. |
| Action | Correct error. |
| Text | Nested TYPE command error. |
| Explanation | A runtime error occurred in a nested TYPE command. After the first TYPE, only TYPE commands are allowed. |
| Action | Correct error. |
| Text | Command REC_BUFF not valid for VT100 communication method. |
| Explanation | The command REC_BUFF cannot be used in a VT100 host session. |
| Action | Correct error. |
| Text | Command HOLD not valid for the communication method. |
| Explanation | The command HOLD is only valid in a VTxxx session. It is not supported in your current session. |
| Action | Correct error. |
| Text | Command SESSION not valid for the communication method. |
| Explanation | The command SESSION is only valid in an HLLAPI session. It is not supported in your current session. |
| Action | Correct error. |
| Text | No more HLLAPI sessions available. |
| Explanation | The command SESSION failed - no more HLLAPI sessions are available. |
| Action | Correct error. |
| Text | Command not allowed in a DOWNLOAD COMMAND SYNC statement. |
| Explanation | Several commands cannot be used in a DOWNLOAD COMMAND SYNC statement sent from Natural. See chapter Terminal Emulation, Data Transfer, DOWNLOAD Statement in the Entire Connection documentation. |
| Action | Correct error. |
| Text | Invalid command in DOWNLOAD COMMAND SYNC statement. |
| Explanation | A command was sent from Natural in a DOWNLOAD COMMAND SYNC statement while another command or procedure file was still being processed. Only the command SET PCFILE can be used in this situation. |
| Action | Correct error. |
| Text | Invalid value for MINUTE parameter. |
| Explanation | A runtime error occurred because the value for the MINUTE parameter taken from a variable was greater than 1440. |
| Action | Check the procedure file logic and correct the error. |
| Text | Message text too long. |
| Explanation | The message text given for the WAIT or WAITM command is too long. The message text must be less than 184 characters long. |
| Action | Correct error. |
| Text | Invalid value for MINUTE. |
| Explanation | A runtime error occurred because the value for the MINUTE parameter taken from a variable was not valid. The value for the MINUTES parameter must be between 1 and 1440. |
| Action | Correct error. |
| Text | Invalid value detected for date or time. |
| Explanation | An invalid value for date or time was detected in the ELAPSETIME command. |
| Action | Correct error. |
| Text | Invalid value detected for date or time. |
| Explanation | An invalid value for date or time was detected in the ELAPSETIME or WAITUNTIL command. |
| Action | Correct error. |
| Text | Invalid file number. |
| Explanation | A runtime error occurred because the file number in the SET PCFILE command is not valid. The file number must be an integer value in the range 1 - 32. |
| Action | Check the procedure file logic and correct the error. |
| Text | Invalid file name. |
| Explanation | A runtime error occurred because the file name in the SET PCFILE command is not valid. The file name must not contain keywords such as LPT1 or wildcard characters. |
| Action | Correct error. |
| Text | File name too long. |
| Explanation | A runtime error occurred because the file name in the SET PCFILE command is too long. Entire Connection file names can only be 268 characters long. |
| Action | Correct error. |
| Text | Invalid file name. |
| Explanation | A runtime error occurred because the file name in the SET PCFILE command is not valid. The special file name ~~RANDOM is only valid for downloads. |
| Action | Correct error. |
| Text | Internal error in SET PCFILE - No more tables. |
| Explanation | An internal error occurred when processing the SET PCFILE command - no more tables are available. |
| Action | If the error persists, report the error to your local Software AG support. |
| Text | Data missing in SET PCFILE. |
| Explanation | A runtime error occurred in the SET PCFILE x DOWN CONVERT command - not enough data specified. Required data are stylesheet type and stylesheet name. |
| Action | Correct error. |
| Text | Error in SET PCFILE: PCFILE length exceeded due to usage of environment variable. |
| Explanation | A runtime error occurred in the SET PCFILE command - the PCFILE length was exceeded due to usage of environment variable. By including the value of the environment variable, the maximum file name length of 512 characters was exceeded. |
| Action | Check if you can circumvent the problem by using a different length path or file name. |
| Text | Recursive key definition. |
| Explanation | A runtime error occurred in the SET TEKEY command. A recursive key definition was detected. |
| Action | Correct error. |
| Text | Integer value required. |
| Explanation | A runtime error occurred in the SET command - expected integer value here. Integer values must be between 0 - 32767. |
| Action | Correct error. |
| Text | Invalid use of local variable. |
| Explanation | Local variables cannot be used on the command line. Local variables are only valid when used in a procedure file. |
| Action | Correct error. |
| Text | Invalid length. |
| Explanation | A runtime error occurred in the INPUT or READ command. An invalid length was detected. The length in the INPUT command must be between 1 and 72. The length in the READ command must be less than 255. |
| Action | Correct error. |
| Text | Message missing in INPUT command. |
| Explanation | At least one message must be specified in the INPUT command. |
| Action | Correct error. |
| Text | DOSDIR not started. |
| Explanation | A runtime error occurred in the DOSDIR command. You must first start DOSDIR with a file parameter. Only subsequent DOSDIR commands can then be without parameters. |
| Action | Correct error. |
| Text | Invalid option in DOSDIR command. |
| Explanation | A runtime error occurred in the DOSDIR command - an invalid option was detected. Valid file attribute option values are A, D, H, R, S. |
| Action | Correct error. |
| Text | Invalid PRINTOPTION parameter. |
| Explanation | A runtime error occurred in the SET PRINTOPTION command - an invalid parameter was detected. See the Entire Connection documentation for all valid parameters of the PRINTOPTION system variable. |
| Action | Correct error. |
| Text | No current directory available for POPDIR. |
| Explanation | A runtime error occurred in the POPDIR command. You must use the PUSHDIR command before you can use the POPDIR command. |
| Action | Correct error. |
| Text | Invalid PUSHDIR command. |
| Explanation | A runtime error occurred in the PUSHDIR command. You are not allowed to save more than 8 directories with the PUSHDIR command. |
| Action | Correct error. |
| Text | DOSDIR not started - not allowed to PUSHDIR. |
| Explanation | A runtime error occurred in the PUSHDIR command. You must use the DOSDIR command before you can use the PUSHDIR command. |
| Action | Correct error. |
| Text | Invalid file number. |
| Explanation | A runtime error occurred in the OPEN, READ or WRITE command - invalid file number detected. The file number in the OPEN, READ or WRITE command must be 1, 2, 3 or 4. |
| Action | Correct error. |
| Text | Invalid file name in OPEN command. |
| Explanation | A runtime error occurred in the OPEN command - invalid file name detected. AUX and CON are not valid file names. |
| Action | Correct error. |
| Text | File number in use. |
| Explanation | A runtime error occurred in the OPEN command - there is an open file for the file number. You forgot to close the file before trying to use the file number again. |
| Action | Correct error. |
| Text | File already open. |
| Explanation | A runtime error occurred in the OPEN command - a file with the name name is already open. You may not open two files with the same name. |
| Action | Correct error. |
| Text | File not opened for output. |
| Explanation | A runtime error occurred in the WRITE command - file not opened for output. The file has been opened for input - writes are not allowed. |
| Action | Correct error. |
| Text | File not opened for input. |
| Explanation | A runtime error occurred in the READ command - file not opened for input. This file has been opened for output - reads are not allowed. |
| Action | Correct error. |
| Text | File number not opened. |
| Explanation | A runtime error occurred in the READ, WRITE or CLOSE command - file not opened. Before you can READ, WRITE or CLOSE a file, it must first be opened. |
| Action | Correct error. |
| Text | Error in WRITE command. |
| Explanation | A runtime error occurred in the WRITE command - error while writing to disk. |
| Action | Check whether the disk is full and whether you have privileges to write to the specified location. |
| Text | Error in READ command. |
| Explanation | A runtime error occurred in the READ command - error while reading from disk. |
| Action | Check whether you have privileges to read from the specified location. Check your hard disk. |
| Text | Error in OPEN command. |
| Explanation | A runtime error occurred in the OPEN command - the file could not be opened. |
| Action | Check whether you have privileges for the specified location. Check your hard disk. |
| Text | Error in CLOSE command. |
| Explanation | A runtime error occurred in the CLOSE command - the file could not be closed. |
| Action | Check your hard disk. |
| Text | TE task or EMULATE failed. |
| Explanation | A runtime error occurred in the EMULATE command or in the TE task - no default session specified. You must specify a default session in the user properties. |
| Action | Use the Entire Connection Configuration Manager to specify a default session in your user properties. |
| Text | Could not open a session. |
| Explanation | A runtime error occurred in a command which requires an open session. The command tried to open the default session. You must specify a default session in the user properties or first open a session using the CONNECT command. |
| Action | Correct error. |
| Text | Host session lost. |
| Explanation | A runtime error occurred in the WAITM command - host session lost. The host session was closed while the WAITM command was active. |
| Action | Check your host connection. |
| Text | Unable to open SSL connection. SSL_CTX_new failed. |
| Explanation | The SSL connection could not be opened because the function SSL_CTX_new failed. |
| Action | Check your SSL installation and configuration. If the error persists, report the error to your local Software AG support. |
| Text | Unable to open SSL connection. SSL_new failed. |
| Explanation | The SSL connection could not be opened because the function SSL_new failed. |
| Action | Check your SSL installation and configuration. If the error persists, report the error to your local Software AG support. |
| Text | Unable to open SSL connection. SSL_connect failed. |
| Explanation | The SSL connection could not be opened because the function SSL_connect failed. Error-code: error, IP address: IP-address, Port: port. |
| Action | Check the TCP/IP address and port in the SSL configuration. If the error persists, report the error to your local Software AG support. |
| Text | SSL_write failed. |
| Explanation | An error occurred while sending data to the host. Error-code: error. |
| Action | Check your SSL installation and configuration. If the error persists, report the error to your local Software AG support. |
| Text | SSL_read failed. |
| Explanation | An error occurred while reading data from the host. Error-code: error. |
| Action | Check your SSL installation and configuration. If the error persists, report the error to your local Software AG support. |
| Text | SSL connection aborted - could not read certificate file calist.pem. |
| Explanation | The SSL connection aborted because the certificate file calist.pem could not be read. |
| Action | Check your SSL configuration and make sure that the file calist.pem exists and can be read. |
| Text | Unable to open SSL connection. Random number generation failed. |
| Explanation | The SSL connection could not be opened because the generation of a random number failed. |
| Action | Check your SSL installation and configuration. If the error persists, report the error to your local Software AG support. |
| Text | SSL connection aborted - host name mismatch. |
| Explanation | The host name host is different from the name in the certificate: host. |
| Action | Check your SSL configuration and provide a valid certificate for the selected host. |
| Text | Unable to open SSL connection - could not read client certificate file. |
| Explanation | The SSL connection could not be opened because the client certificate file certificate-file could not be read. |
| Action | Check your SSL configuration and provide a valid client certificate. |
| Text | Unable to open SSL connection - could not read client private key file. |
| Explanation | The SSL connection could not be opened because the client private key file key-file could not be read. |
| Action | Check your SSL configuration and provide a valid client private key file. |
| Text | SSL connection aborted - host name not found in the certificate. |
| Explanation | The SSL connection aborted because the host name could not be found in the certificate. |
| Action | Check your SSL configuration and provide a valid certificate. |
| Text | Unable to open SSH connection. libssh2 initialization failed. |
| Explanation | The SSH connection could not be opened. The SSH library could not be initialized and returned an error error-code. |
| Action | Check your SSH installation and configuration. If the error persists, report the error to your local Software AG support. |
| Text | Unable to open SSH connection. Could not initialize an SSH session. |
| Explanation | The SSH connection could not be opened. The SSH session could not be initialized. |
| Action | Check your SSH installation and configuration. If the error persists, report the error to your local Software AG support. |
| Text | Unable to open SSH connection. Failed to establish SSH session. |
| Explanation | The SSH connection could not be opened. No SSH session could be established. |
| Action | Check your SSH installation and configuration. If the error persists, report the error to your local Software AG support. |
| Text | Unable to open SSH connection. "Password" authentication failed. |
| Explanation | The SSH connection could not be opened. The supplied values for user ID and password are not valid. |
| Action | Check and correct. |
| Text | Unable to open SSH connection. No supported authentication methods found. |
| Explanation | The SSH connection could not be opened. The host did not return an authentication method supported by Entire Connection. |
| Action | Check your host SSH installation and configuration. If the error persists, report the error to your local Software AG support. |
| Text | Unable to open SSH connection. "Keyboard-interactive" authentication method failed. |
| Explanation | The SSH connection could not be opened. The supplied values for user ID and password are not valid. The host returned an error error-code. |
| Action | Check and correct. |
| Text | Unable to open SSH connection. No authentication schemes received from host. |
| Explanation | The SSH connection could not be opened. The host did not return any authentication schemes. |
| Action | Check your host SSH installation and configuration. If the error persists, report the error to your local Software AG support. |
| Text | Unable to open SSH connection. Unable to open a session. |
| Explanation | The SSH connection could not be opened. The SSH session could not be opened. |
| Action | Check your SSH installation and configuration. If the error persists, report the error to your local Software AG support. |
| Text | Unable to open SSH connection. Failed to request pty. |
| Explanation | The SSH connection could not be opened. The function "request pty" returned an error error-code. |
| Action | Check your SSH installation and configuration. If the error persists, report the error to your local Software AG support. |
| Text | Unable to open SSH connection. Unable to request shell on allocated pty. |
| Explanation | The SSH connection could not be opened. The request of a shell on the allocated pty failed. |
| Action | Check your SSH installation and configuration. If the error persists, report the error to your local Software AG support. |
| Text | Unable to open SSH connection. Too many authentication failures. |
| Explanation | The SSH connection could not be opened. There were too many authentication failures for the user user-name. |
| Action | Check the supplied user credentials and try again. Note that you cannot change the user ID if you received an authentication error. In this case, you have to close and re-open the session and enter the correct user ID. |
| Text | Unable to open SSH connection. Error in "keyboard-interactive" authentication. |
| Explanation | The SSH connection could not be opened. The authentication by keyboard-interactive returned an error error-code. |
| Action | Check the supplied user credentials and try again. |
| Text | Opening of SSH connection canceled by user. |
| Explanation | The SSH connection was not be opened because the user pressed the Cancel button. |
| Action | No action required. |
| Text | Unable to open SSH connection. Internal error. |
| Explanation | The SSH connection could not be opened. An internal error occurred because a server interface was not available. |
| Action | Check your Entire Connection installation and configuration. If the error persists, report the error to your local Software AG support. |
| Text | Unable to open SSH connection. "Publickey" authentication failed. |
| Explanation | The SSH connection could not be opened. The authentication by public key failed. |
| Action | Check the supplied user credentials and the public and private keys and try again. Also check the host configuration for the "publickey" authentication. |
| Text | SSH_write failed. |
| Explanation | Error in the host communication. The data entered could not be sent to the host. The function SSH_write failed with error error-code. |
| Action | Check your SSH installation and configuration. If the error persists, report the error to your local Software AG support. |
| Text | The SSH key file must be located in the folder %LOCALAPPDATA%\Software AG\Entire Connection\certs. |
| Explanation | The private key file for the "publickey" authentication must be located in the folder %LOCALAPPDATA%\Software AG\Entire Connection\certs. |
| Action | Check and correct. |
| Text | SSH key file name too long. |
| Explanation | The file name of the private key file is too long. The maximum length is 47 characters. |
| Action | Check and correct. |
| Text | Fatal communication error. |
| Explanation | Error in the host communication. A timeout occurred in CallMethodToThread. Caller: name. |
| Action | Check your SSH installation and configuration. If the error persists, report the error to your local Software AG support. |
| Text | SSL connection aborted. Unable to get issuer certificate. |
| Explanation | The SSL connection aborted because the issuer certificate could not be found. This error occurs if the issuer certificate of an untrusted certificate cannot be found. |
| Action | Check your SSL configuration and provide a valid issuer certificate. |
| Text | SSL connection aborted - unable to get certificate CRL. |
| Explanation | The SSL connection aborted because the CRL of a certificate could not be found. |
| Action | Check your SSL configuration and provide a valid certificate. |
| Text | SSL connection aborted. Unable to decrypt certificate's signature. |
| Explanation | The SSL connection aborted because the signature could not be decrypted. This means that the actual signature value could not be determined rather than it not matching the expected value. This is only meaningful for RSA keys. |
| Action | Check your SSL configuration and provide a valid certificate. |
| Text | SSL connection aborted. Unable to decrypt CRL's signature. |
| Explanation | The SSL connection aborted because the CRL signature could not be decrypted. This means that the actual signature value could not be determined rather than it not matching the expected value. |
| Action | Check your SSL configuration and provide a valid certificate. |
| Text | SSL connection aborted. Unable to decode issuer public key. |
| Explanation | The SSL connection aborted because the public key in the certificate SubjectPublicKeyInfo could not be read. |
| Action | Check your SSL configuration and provide a valid certificate. |
| Text | SSL connection aborted. Certificate signature failure. |
| Explanation | The SSL connection aborted because the signature of the certificate is invalid. |
| Action | Check your SSL configuration and provide a valid certificate. |
| Text | SSL connection aborted. CRL signature failure. |
| Explanation | The SSL connection aborted because the CRL signature of the certificate is invalid. |
| Action | Check your SSL configuration and provide a valid certificate. |
| Text | SSL connection aborted. Certificate is not yet valid. |
| Explanation | The SSL connection aborted because the certificate is not yet valid. The notBefore date is after the current time. |
| Action | Check your SSL configuration and provide a valid certificate. |
| Text | SSL connection aborted. Certificate has expired. |
| Explanation | The SSL connection aborted because the certificate has expired. The notAfter date is before the current time. |
| Action | Check your SSL configuration and provide a valid certificate. |
| Text | SSL connection aborted. CRL is not yet valid. |
| Explanation | The SSL connection aborted because the certificate is not yet valid. The CRL is not yet valid. |
| Action | Check your SSL configuration and provide a valid certificate. |
| Text | SSL connection aborted. CRL has expired. |
| Explanation | The SSL connection aborted because the certificate is not valid. The CRL has expired. |
| Action | Check your SSL configuration and provide a valid certificate. |
| Text | SSL connection aborted. Format error in certificate's notBefore field. |
| Explanation | The SSL connection aborted because the certificate is not valid. The notBefore field of the certificate contains an invalid time. |
| Action | Check your SSL configuration and provide a valid certificate. |
| Text | SSL connection aborted. Format error in certificate's notAfter field. |
| Explanation | The SSL connection aborted because the certificate is not valid. The notAfter field of the contains an invalid time. |
| Action | Check your SSL configuration and provide a valid certificate. |
| Text | SSL connection aborted. Format error in CRL's lastUpdate field. |
| Explanation | The SSL connection aborted because the certificate is not valid. The lastUpdate field of the CRL contains an invalid time. |
| Action | Check your SSL configuration and provide a valid certificate. |
| Text | SSL connection aborted. Format error in CRL's nextUpdate field. |
| Explanation | The SSL connection aborted because the certificate is not valid. The nextUpdate field of the CRL contains an invalid time. |
| Action | Check your SSL configuration and provide a valid certificate. |
| Text | SSL connection aborted. Out of memory. |
| Explanation | The SSL connection aborted because an error occurred while trying to allocate memory. This should never happen. |
| Action | Check your PC hardware. |
| Text | SSL connection aborted. Untrusted self-signed certificate. |
| Explanation | The SSL connection aborted because the certificate is not valid. The passed certificate is self-signed and the same certificate cannot be found in the list of trusted certificates. |
| Action | Check your SSL configuration and provide a valid certificate. |
| Text | SSL connection aborted. Self signed-certificate in certificate chain. |
| Explanation | The SSL connection aborted because the certificate chain is not valid. The certificate chain could be built up using the untrusted certificates but the root could not be found locally. |
| Action | Check your SSL configuration and provide a valid certificate chain. |
| Text | SSL connection aborted. Unable to get local issuer certificate. |
| Explanation | The issuer certificate of a locally looked up certificate could not be found. This normally means that the list of trusted certificates is not complete. |
| Action | Check your SSL configuration and provide a valid issuer certificate. |
| Text | SSL connection aborted. Unable to verify the first certificate. |
| Explanation | The SSL connection aborted because the first certificate could not be verified. No signatures could be verified because the chain contains only one certificate and it is not self-signed. |
| Action | Check your SSL configuration and provide a valid certificate. |
| Text | SSL connection aborted. Certificate chain too long. |
| Explanation | The SSL connection aborted because the certificate chain is too long. The certificate chain length is greater than the supplied maximum depth. |
| Action | Check your SSL configuration and provide a valid certificate. |
| Text | SSL connection aborted. Certificate revoked. |
| Explanation | The SSL connection aborted because the certificate has been revoked. |
| Action | Check your SSL configuration and provide a valid certificate. |
| Text | SSL connection aborted. Invalid CA certificate. |
| Explanation | The SSL connection aborted because the CA certificate is not valid. The CA certificate is invalid. Either it is not a CA certificate or its extensions are not consistent with the supplied purpose. |
| Action | Check your SSL configuration and provide a valid CA certificate. |
| Text | SSL connection aborted. Path length constraint exceeded. |
| Explanation | The SSL connection aborted because the certificate is not valid. The basicConstraints path length parameter has been exceeded. |
| Action | Check your SSL configuration and provide a valid certificate. |
| Text | SSL connection aborted. Unsupported certificate purpose. |
| Explanation | The SSL connection aborted because the certificate is not valid. The supplied certificate cannot be used for the specified purpose. |
| Action | Check your SSL configuration and provide a valid certificate. |
| Text | SSL connection aborted. Certificate not trusted. |
| Explanation | The SSL connection aborted because the certificate is not valid. The root CA is not marked as trusted for the specified purpose. |
| Action | Check your SSL configuration and provide a valid CA certificate. |
| Text | SSL connection aborted. Certificate rejected. |
| Explanation | The SSL connection aborted because the certificate is not valid. The root CA is marked to reject the specified purpose. |
| Action | Check your SSL configuration and provide a valid certificate. |
| Text | SSL connection aborted. Subject issuer mismatch. |
| Explanation | The SSL connection aborted because the certificate is not valid. The current candidate issuer certificate was rejected because its subject name did not match the issuer name of the current certificate. The verification is done when the -issuer_checks option is set. |
| Action | Check your SSL configuration and provide a valid certificate. |
| Text | SSL connection aborted. Authority and subject key identifier mismatch. |
| Explanation | The SSL connection aborted because the certificate is not valid. The current candidate issuer certificate was rejected because its subject key identifier was present and did not match the authority key identifier of the current certificate. The verification is done when the -issuer_checks option is set. |
| Action | Check your SSL configuration and provide a valid certificate. |
| Text | SSL connection aborted. Authority and issuer serial number mismatch. |
| Explanation | The SSL connection aborted because the certificate is not valid. The current candidate issuer certificate was rejected because its issuer name and serial number was present and did not match the authority key identifier of the current certificate. The verification is done when the -issuer_checks option is set. |
| Action | Check your SSL configuration and provide a valid certificate. |
| Text | SSL connection aborted. Key usage does not include certificate signing. |
| Explanation | The SSL connection aborted because the certificate is not valid. The current candidate issuer certificate was rejected because its keyUsage extension does not permit certificate signing. |
| Action | Check your SSL configuration and provide a valid certificate. |
| Text | SSL connection aborted. Application verification failure. |
| Explanation | The SSL connection aborted because of an application-specific error. This should never happen. |
| Action | Check your SSL installation and configuration. If the error persists, report the error to your local Software AG support. |
| Text | Initialization of the selected communication method timed out. |
| Explanation | Failed to open session because there was no answer from the host within the specified maximum response time. |
| Action | Check your host connection and the session properties. Try to increase the "Open session timeout" parameter on the Terminal page of the session properties. |
| Text | Cannot execute procedure file at this time. |
| Explanation | The procedure file cannot be executed at this time. You are already nested in terminal emulation. This happens, for example, if a host command was executed from a procedure file, and the host response contains a command to start another procedure file. |
| Action | Check and correct your procedure file logic. |
| Text | Unable to disconnect - communication in progress. |
| Explanation | The DISCONNECT command cannot be executed because the current communication process has to finish first. |
| Action | Try again later. |
| Text | Unable to connect - communication in progress. |
| Explanation | The CONNECT command cannot be executed because the current communication process has to finish first. |
| Action | Try disconnecting first. |
| Text | Connect request failed - session not found. |
| Explanation | The session could not be opened because a session with the specified name could not be found in the share file for your user ID. |
| Action | Check whether the session exists in the share file. Check your procedure file. |
| Text | You are not allowed to enter terminal emulation at this time. |
| Explanation | You are not allowed to enter terminal emulation at this time because you are already in terminal emulation. |
| Action | End/exit the task you are currently running. Check your procedure file logic. |
| Text | Error loading communication DLL. |
| Explanation | Failed to open session because there was an error error-number while loading the communication DLL DLL-name. |
| Action | Check your Entire Connection installation. If the error persists, report the error to your local Software AG support. |
| Text | Start of the communication thread failed. |
| Explanation | Failed to open session because the communication thread could not be started. |
| Action | Check your PC system for unusual load. If the error persists, report the error to your local Software AG support. |
| Text | Error creating translation table. |
| Explanation | Failed to open session. The translation table for the code pages code-pages could not be created. |
| Action | Check your Entire Connection installation. If the error persists, report the error to your local Software AG support. |
| Text | Error loading WinSocket interface DLL. |
| Explanation | Failed to open session because the WinSocket interface could not be loaded. The function function-name could not be found in WS2_32.DLL. |
| Action | Check your PC system and the WinSocket installation. If the error persists, report the error to your local Software AG support. |
| Text | BS2000/975x communications initialization failed. |
| Explanation | Failed to open session. The BS2000/975x communication could not be started. The initial request could not be started. |
| Action | Check the BS2000 host connection. If the error persists, report the error to your local Software AG support. |
| Text | Error reading translation table from share file. |
| Explanation | Failed to open session. The translation table table-name could not be read from the share file. |
| Action | Check the national settings for the session. If the error persists, try restoring your share file from a backup and retry. |
| Text | Error returned from HLLAPI function "Query Sessions". |
| Explanation | Failed to open session - the HLLAPI function "Query Sessions" returned an error: error-code. |
| Action | Check your HLLAPI software installation. If the error persists, create a trace with your HLLAPI software, and report the error to your local Software AG support. |
| Text | HLLAPI function "Query Sessions" did not return any host screen sessions. |
| Explanation | Failed to open session - the HLLAPI function "Query Sessions" did not return any host screen sessions. |
| Action | Check and correct the session definitions in your HLLAPI software. |
| Text | Error from HLLAPI function "Connect to Presentation Space". |
| Explanation | Failed to open session - the HLLAPI function "Connect to Presentation Space" returned an error: error-code. |
| Action | Check your HLLAPI software installation. If the error persists, create a trace with your HLLAPI software, and report the error to your local Software AG support. |
| Text | Error returned from HLLAPI "put_key" function. |
| Explanation | Communication error - the HLLAPI function "put_key" returned an error: error-code. |
| Action | Check your HLLAPI software installation. If the error persists, create a trace with your HLLAPI software, and report the error to your local Software AG support. |
| Text | Error returned from HLLAPI "CopyPS2String" function. |
| Explanation | Communication error - the HLLAPI function "CopyPS2String" returned an error: error-code. |
| Action | Check your HLLAPI software installation. If the error persists, create a trace with your HLLAPI software, and report the error to your local Software AG support. |
| Text | Error returned from HLLAPI "Start_Host_Notification" function. |
| Explanation | Communication error - the HLLAPI function "Start_Host_Notification" returned an error: error-code. |
| Action | Check your HLLAPI software installation. If the error persists, create a trace with your HLLAPI software, and report the error to your local Software AG support. |
| Text | HLLAPI DLL could not be loaded. |
| Explanation | Failed to open session - the HLLAPI DLL DLL name could not be loaded. Error: error-code. |
| Action | Make sure that software providing the HLLAPI is installed and that it is in the PATH. If the error persists, report the error to your local Software AG support. |
| Text | HLLAPI function not found. |
| Explanation | Failed to open session - the HLLAPI function function-name was not found in the DLL DLL-name. |
| Action | Check your HLLAPI software installation and make sure that it is in the PATH. If the error persists, report the error to your local Software AG support. |
| Text | HLLAPI session no longer connected. |
| Explanation | Communication error - the HLLAPI session is no longer connected. |
| Action | Check your host connection. |
| Text | Error returned from HLLAPI function "CopyOIA" |
| Explanation | Communication error - the HLLAPI function "CopyOIA" returned an error: error-code. |
| Action | Check your HLLAPI software installation. |
| Text | HLLAPI is already connected to an Entire Connection terminal. |
| Explanation | Failed to open session - the HLLAPI interface is already connected to another Entire Connection terminal. |
| Action | Use the HLLAPI session in the other Entire Connection terminal. |
| Text | Error writing to the share file. |
| Explanation | An error occurred when writing to the Entire Connection share file. |
| Action | Check your disk space and whether you have permission to write to the location. Restore your share file from a backup and retry. |
| Text | Error reading from the share file. |
| Explanation | An error occurred when reading from the Entire Connection share file. |
| Action | Check your disk and whether you have permission to read from the location. Restore your share file from a backup and retry. |
| Text | CN01 PLEASE ENTER NET COMMAND. |
| Explanation | CN01 PLEASE ENTER NET COMMAND: help text for BS2000 init dialog. |
| Action | No action required. |
| Text | CN02 ERROR IN NET COMMAND; INVALID COMMAND SYNTAX. |
| Explanation | CN02 ERROR IN NET COMMAND; INVALID COMMAND SYNTAX - error message for BS2000 init dialog. |
| Action | Correct the BS2000 command. |
| Text | CN02 ERROR IN NET COMMAND; NO DEFAULT FOR PARTNER NAME. |
| Explanation | CN02 ERROR IN NET COMMAND; NO DEFAULT FOR PARTNER NAME - error message for BS2000 init dialog. |
| Action | Correct the BS2000 command. |
| Text | Connection refused by the communications partner. |
| Explanation | Failed to open session - the connection was refused by the communications partner. |
| Action | Check your communication settings or contact your network administrator. |
| Text | Error when processing "put_keystroke". |
| Explanation | A communication error occurred in the "put_keystroke" routine. |
| Action | Check your host connection. Close and re-open the session and try again. If the error persists, report the error to your local Software AG support. |
| Text | Error when processing "quit". |
| Explanation | A communication error occurred in the BS2000 "quit" routine. |
| Action | Check your host connection. Close and re-open the session and try again. If the error persists, report the error to your local Software AG support. |
| Text | Error when processing "ptast". |
| Explanation | A communication error occurred when sending a BS2000 P-key to the host. |
| Action | Check your host connection. Close and re-open the session and try again. If the error persists, report the error to your local Software AG support. |
| Text | CN06 REJECTED; MISSING APPLICATION NAME. |
| Explanation | CN06 REJECTED; MISSING APPLICATION NAME - error message for BS2000 init dialog. |
| Action | Correct the BS2000 command. |
| Text | CN06 REJECTED; APPLICATION NAME TOO LONG. |
| Explanation | CN06 REJECTED; APPLICATION NAME TOO LONG - error message for BS2000 init dialog. |
| Action | Correct the BS2000 command. |
| Text | CN06 REJECTED; CHECK CONNECTION PARAMETER. |
| Explanation | CN06 REJECTED; CHECK CONNECTION PARAMETER - error message for BS2000 init dialog. |
| Action | Correct the BS2000 command. |
| Text | CN07 DISCONNECTED; NO REASON SPECIFIED BY PARTNER. |
| Explanation | CN07 DISCONNECTED; NO REASON SPECIFIED BY PARTNER - error message for BS2000 init dialog. |
| Action | Correct the BS2000 command. |
| Text | Could not load translation table ASC2HEB. |
| Explanation | Failed to open session - could not load translation table ASC2HEB. This translation table is required if the option "Enable right-to-left support" is set in the Session Properties, National page. |
| Action | Import the missing table into the share file. See Configuration Manager, Tables, Translation Tables dialog. |
| Text | Unable to initialize communications from prodecure file. |
| Explanation | A command in a procedure file which requires a host session tried to open the default session. An error occurred while opening the session. |
| Action | Check the communication parameters for your default session. |
| Text | Command not valid for VTxxx communication methods. |
| Explanation | The command REC_BUFF is not supported with the VTxxx communication methods. |
| Action | Check and correct the procedure file. |
| Text | Command not supported with the current communication method. |
| Explanation | The command cmd is not supported with the current communication method. There are terminal commands which are only available with specific communication methods. |
| Action | Check and correct the command usage. |
| Text | Out of disk space. REC_SCR turned off. |
| Explanation | A screen trace could not be written to the disk because the disk is full. The screen trace was turned off. |
| Action | Check your hard disk for errors and for free disk space. |
| Text | Fatal disk error. REC_SCR turned off. |
| Explanation | A screen trace could not be written to the disk because of a write error. The screen trace was turned off. |
| Action | Check the "Log&Trace" parameter in the User Properties, Procedure page. Check whether you have privileges to write to this location. Check your hard disk for errors and for free disk space. |
| Text | Out of disk space. REC_BUF turned off. |
| Explanation | A buffer trace could not be written to the disk because the disk is full. The buffer trace was turned off. |
| Action | Check your hard disk for errors and for free disk space. |
| Text | Fatal disk error. REC_BUF turned off. |
| Explanation | A buffer trace could not be written to the disk because of a write error. The buffer trace was turned off. |
| Action | Check the "Log&Trace" parameter in the User Properties, Procedure page. Check whether you have privileges to write to this location. Check your hard disk. |
| Text | Out of disk space. REC_XFER turned off. |
| Explanation | A file transfer trace could not be written to the disk because the disk is full. The file transfer trace was turned off. |
| Action | Check your hard disk for errors and for free disk space. |
| Text | Fatal disk error. REC_XFER turned off. |
| Explanation | A file transfer trace could not be written to the disk because of a write error. The file transfer trace was turned off. |
| Action | Check the "Log&Trace" parameter in the User Properties, Procedure page. Check whether you have privileges to write to this location. Check your hard disk. |
| Text | Error parsing the 3270 data stream. |
| Explanation | The interpreter of the 3270 data stream was not able to parse successfully and reported an error: error. |
| Action | Check your session communication settings and the host connection. If the error persists, create a communication trace and report the error to your local Software AG support. To turn on the communication trace, enable the parameter "Enable communication trace" in the Test page of the session properties. |
| Text | Disk error initializing the monitor trace. |
| Explanation | The monitor trace file could not be initialized because of a disk write error. |
| Action | Check the "Log&Trace" parameter in the User Properties, Procedure page. Check whether you have privileges to write to this location. Check your hard disk. |
| Text | Open Socket failed. |
| Explanation | The Open Socket function returned an error: error-code. |
| Action | Check the communication settings for the session. Check your network connection or contact your network administrator. |
| Text | Error initializing the WinSocket interface. |
| Explanation | An error occurred while initializing the WinSocket interface. Error: error-code. |
| Action | Check your network connection or contact your network administrator. |
| Text | Connect failed. |
| Explanation | The Connect function returned an error: error-code. |
| Action | Check the communication settings for the session. Make sure that the host is running. |
| Text | Exceeded limit of tasks supported by the Windows Socket implementation. |
| Explanation | Host communication error. The number of tasks supported by the Windows Socket implementation has been exceeded. |
| Action | Check your PC for unusual load. Contact your network administrator. |
| Text | The underlying network subsystem is not ready for network communication. |
| Explanation | Host communication error. The underlying network subsystem is not ready for network communication. |
| Action | Contact your network administrator. |
| Text | An error occurred while attempting to receive data from the host. |
| Explanation | Host communication error with error-code error-code in receiving data from the host. |
| Action | Check your network connection or contact your network administrator. |
| Text | Error from function getaddrinfo. |
| Explanation | Host communication error. The function getaddrinfo returned an error: error-code. |
| Action | Check your network connection or contact your network administrator. |
| Text | Windows Socket DLL version out of range (WSAVERNOTSUPPORTED). |
| Explanation | The current Windows Socket implementation does not support the Windows Sockets specification version requested by the Entire Connection. |
| Action | Contact your PC administrator. |
| Text | Host not found (WSAHOST_NOT_FOUND). |
| Explanation | The host host-name was not found. The name you have used is not an official hostname or alias. |
| Action | Check the session properties or contact your network administrator. |
| Text | Host not found or server failure (WSATRY_AGAIN). |
| Explanation | Failed to open session with error WSATRY_AGAIN. This is usually a temporary error during the resolution of the host name and means that the local server did not receive a response from an authoritative server. |
| Action | Try again. |
| Text | Host name not found on the name server (WSANO_DATA). |
| Explanation | Failed to open session with error WSANO_DATA. The host name was not found on the name server (DNS). |
| Action | Check the session properties or contact your network administrator. |
| Text | Connection refused (WSAECONNREFUSED). |
| Explanation | Failed to open session with error WSAECONNREFUSED. The connection to the host was refused. No specific error was reported. |
| Action | Check the session properties or contact your network administrator. |
| Text | Socket type not supported (WSAESOCKTNOSUPPORT). |
| Explanation | Failed to open session with error WSAESOCKTNOSUPPORT. The type of socket requested by Entire Connection is not supported by the installed Windows Socket implementation. |
| Action | Check your Windows installation. Contact your PC administrator. |
| Text | The network subsystem or the associated service provider has failed (WSAENETDOWN). |
| Explanation | Failed to open session with error WSAENETDOWN. The network subsystem or the associated service provider has failed. |
| Action | Contact your network administrator. |
| Text | Address family not supported by the installed Windows sockets implementation. |
| Explanation | Failed to open session with error WSAEAFNOSUPPORT. The specified address family is not supported by the installed Windows sockets implementation. |
| Action | Check your Windows installation. Contact your PC administrator. |
| Text | No more socket descriptors available (WSAEMFILE). |
| Explanation | Failed to open session with error WSAEMFILE. No more socket descriptors available. |
| Action | Check your PC system for unusual high load or looping applications. |
| Text | Specified protocol not supported (WSAEPROTONOSUPPORT). |
| Explanation | Failed to open session with error WSAEPROTONOSUPPORT. The specified protocol is not supported by the installed Windows sockets implementation. |
| Action | Check your Windows installation. Contact your PC administrator. |
| Text | Not enough buffers available, too many connections (WSAENOBUFS). |
| Explanation | Failed to open session with error WSAENOBUFS. Not enough buffers available, too many connections. |
| Action | Check your PC system for unusual high number of TPC/IP connections. |
| Text | Socket already bound to an address (WSAEINVAL). |
| Explanation | Failed to open session with error WSAEINVAL. The socket is already bound to an address. |
| Action | Close and re-open the session and try again. If the error persists, report the error to your local Software AG support. |
| Text | Specified buffer not part of the application address space. |
| Explanation | TCP/IP communication error. The specified buffer is not part of the application address space. |
| Action | Close and re-open the session and try again. If the error persists, report the error to your local Software AG support. |
| Text | Connection broken due to the remote host resetting (WSAENETRESET). |
| Explanation | Communication error. The connection has been broken due to the remote host resetting. |
| Action | Check your host communication. |
| Text | Socket has been shut down (WSAESHUTDOWN). |
| Explanation | Communication error. The socket has already been shut down. |
| Action | Close and re-open the session and try again. If the error persists, report the error to your local Software AG support. |
| Text | Message size problem (WSAEMSGSIZE). |
| Explanation | Communication error. A message size problem occurred. |
| Action | Close and re-open the session and try again. If the error persists, report the error to your local Software AG support. |
| Text | Remote host cannot be reached (WSAEHOSTUNREACH). |
| Explanation | Failed to open session with error WSAEHOSTUNREACH. The remote host cannot be reached from this computer at this time. |
| Action | Check your host communication. |
| Text | Host connection aborted, reset or timed out. |
| Explanation | Communication error with WinSocket error error-code. The connection to the host was aborted, reset or timed out. |
| Action | Check your host communication. |
| Text | Received message size too large. |
| Explanation | The message size received from the host was too large to fit into the buffer and was truncated. |
| Action | Close and re-open the session and try again. If the error persists, report the error to your local Software AG support. |
| Text | Failed to open session with error WSAEACCES. |
| Explanation | Failed to open session. The requested address is a broadcast address, but the appropriate flag was not set. |
| Action | Check and correct the "Host name / IP address" parameter in the session properties. |
| Text | Failed to open session with error WSAEADDRNOTAVAIL. |
| Explanation | Failed to open session. The specified address is not available from the local machine. |
| Action | Check and correct the "Host name / IP address" parameter in the session properties. |
| Text | TCP/IP connection refused by host. |
| Explanation | Failed to open session - TCP/IP connection refused by the host you want to connect to. |
| Action | Contact your network administrator. |
| Text | Communication error in send routine. |
| Explanation | Communication error in the send routine - the specified buffer is not part of the application address space. |
| Action | Close and re-open the session, and try again. If the error persists, report the error to your local Software AG support. |
| Text | Communication error in ioctlsocket routine. |
| Explanation | Communication error in the ioctlsocket routine - the specified buffer is not part of the application address space. |
| Action | Close and re-open the session, and try again. If the error persists, report the error to your local Software AG support. |
| Text | Communication error in send routine. |
| Explanation | Communication error in the send routine - the socket is message oriented, and the message is larger than the maximum supported by the underlying transport. |
| Action | Close and re-open the session, and try again. If the error persists, report the error to your local Software AG support. |
| Text | Communication error in ioctlsocket routine. |
| Explanation | Communication error in the ioctlsocket routine - a blocking WinSock 1.1 call is in progress, or the service provider is still processing a callback function. |
| Action | Try again. |
| Text | Failed to open session. Socket request refused. |
| Explanation | The socket is defined as non-blocking, the call would block. So the request has been refused. |
| Action | Close and re-open the session, and try again. If the error persists, report the error to your local Software AG support. |
| Text | Winsock II interface function WSAEventSelect failed. |
| Explanation | The Winsock II interface function WSAEventSelect returned a WinSock error: error-code. |
| Action | Close and re-open the session, and try again. If the error persists, report the error to your local Software AG support. |
| Text | Failed to connect TCP/IP socket. |
| Explanation | The connect TCP/IP socket function failed. The host could not be connected with the given name and port. |
| Action | Check the host name and port number in the session settings. Check wether the host system is running. |
| Text | Send data to socket failed. |
| Explanation | The send data to socket function returned a WinSock error: error-code. |
| Action | Close and re-open the session, and try again. If the error persists, report the error to your local Software AG support. |
| Text | WinSocket returned an unspecific error. |
| Explanation | The call to the WinSocket interface returned an unspecific error. Failed to open session. |
| Action | Check your Windows WinSocket installation. Contact your network administrator. |
| Text | Invalid value in data type field of a TN3270E message header. |
| Explanation | An invalid value was found in the data type field of a the TN3270E message header. |
| Action | If the error persists, create a communication trace and report the error to your local Software AG support. To turn on the communication trace, enable the parameter Communication Traces in the Test page of the Session Properties. |
| Text | Invalid value in request flag field of a TN3270E message header. |
| Explanation | An invalid value was found in the request flag field of a TN3270E message header. |
| Action | If the error persists, create a communication trace and report the error to your local Software AG support. To turn on the communication trace, enable the parameter Communication Traces in the Test page of the Session Properties. |
| Text | Invalid value in response flag field of a TN3270E message header. |
| Explanation | An invalid value was found in the response flag field of a TN3270E message header. |
| Action | If the error persists, create a communication trace and report the error to your local Software AG support. To turn on the communication trace, enable the parameter Communication Traces in the Test page of the Session Properties. |
| Text | Invalid value in sequence number field of a TN3270E message header. |
| Explanation | An invalid value was found in the sequence number field of a TN3270E message header. |
| Action | If the error persists, create a communication trace and report the error to your local Software AG support. To turn on the communication trace, enable the parameter Communication Traces in the Test page of the Session Properties. |
| Text | Connection request to printer failed. |
| Explanation | The connection request to a specific printer failed because device-name is the partner to some terminal. |
| Action | Check the definition of the printer in the Telnet server configuration. |
| Text | Printer device already associated with another session. |
| Explanation | The requested printer device-name is already associated with another screen session. |
| Action | Check the definition of the printer in the Telnet server configuration. |
| Text | Association to a terminal device failed. |
| Explanation | Association to a terminal device failed because device-name is not a terminal. |
| Action | Check the definition of the printer in the Telnet server configuration. |
| Text | Device or resource name not known to the Telnet server. |
| Explanation | The device or resource name specified in the "TN3270E communication" dialog is not known to the Telnet server. |
| Action | Check the session settings in the Entire Connection Configuration Manager. |
| Text | Telnet server does not support the requested device type. |
| Explanation | The Telnet server does not support the requested device type device-type. |
| Action | Check the session settings in the Entire Connection Configuration Manager. Contact your Telnet server administrator. |
| Text | Incompatible device or resource name requested. |
| Explanation | The requested device or resource name is incompatible with the requested device type device-type. |
| Action | Check the session settings in the Entire Connection Configuration Manager. Contact your Telnet server administrator. |
| Text | Unknown error in device type or name processing. |
| Explanation | An unknown error in device type or name processing has occurred. |
| Action | If the error persists, create a communication trace and report the error to your local Software AG support. To turn on the communication trace, enable the parameter Communication Traces in the Test page of the Session Properties. |
| Text | Telnet server unable to satisfy client request. |
| Explanation | The Telnet server is unable to satisfy the type of request sent by the client. Possible reasons: a specific terminal or printer was requested but the Telnet server does not have any such pools of device names defined to it, or the "Associate to terminal" option was used but no partner printers are defined in the Telnet server. |
| Action | Check the settings in the Telnet server. Contact your Telnet server administrator. |
| Text | Unknown device type reject command. |
| Explanation | The device type was rejected by the host with an unknown device type reject command. |
| Action | If the error persists, create a communication trace and report the error to your local Software AG support. To turn on the communication trace, enable the parameter Communication Traces in the Test page of the Session Properties. |
| Text | No device name returned for requested device type. |
| Explanation | A TN3270E negotiation problem occurred. The Telnet server did not return a device name for device type device-type. |
| Action | Check the settings in the Telnet server. Contact your Telnet server administrator. |
| Text | Unexpected 3270 or SCS data from host. |
| Explanation | Entire Connection received 3270 or SCS data from the host but the session was not yet bound. |
| Action | If the error persists, create a communication trace and report the error to your local Software AG support. To turn on the communication trace, enable the parameter Communication Traces in the Test page of the Session Properties. |
| Text | Wrong host printer sessions returned. |
| Explanation | The Telnet server tried to open a TN3270 printer session. Entire Connection only supports TN3270E host printer sessions. |
| Action | Check the settings on the Telnet server. Contact your Telnet server administrator. |
| Text | Unexpected SCS data received. |
| Explanation | The Telnet server sent SCS data although SCS was not negotiated. |
| Action | If the error persists, create a communication trace and report the error to your local Software AG support. To turn on the communication trace, enable the parameter Communication Traces in the Test page of the Session Properties. |
| Text | Unexpected SNA bind received. |
| Explanation | The Telnet server sent a SNA bind image although bind-image was not negotiated. |
| Action | If the error persists, create a communication trace and report the error to your local Software AG support. To turn on the communication trace, enable the parameter Communication Traces in the Test page of the Session Properties. |
| Text | Unexpected SNA unbind received. |
| Explanation | The Telnet server sent a SNA unbind notification although bind-image was not negotiated. |
| Action | If the error persists, create a communication trace and report the error to your local Software AG support. To turn on the communication trace enable the parameter Communication Traces in the Test page of the Session Properties. |
| Text | Open of associated printer session failed. |
| Explanation | The associated printer session could not be opened. Your Telnet server only supports TN3270 sessions. Entire Connection only supports TN3270E host printer sessions. |
| Action | Check the settings in the Telnet server. Contact your Telnet server administrator. |
| Text | Open file parameter error. |
| Explanation | A parameter error was returned from the open file function for file-name. Open file failed. |
| Action | Check the file name and the parameters passed. |
| Text | File is write protected. |
| Explanation | Open file failed for file-name. The file is write-protected. Data transfer terminated abnormally. |
| Action | Check the file properties. |
| Text | Invalid field type in format record. |
| Explanation | The format record received from Natural contains an unknown or invalid field type. Data transfer terminated abnormally. |
| Action | If the error persists, create a file transfer trace and report the error to your local Software AG support. Press the CTRL+F to turn the file transfer trace on. An "X" at the end of the status line shows that the file transfer trace is enabled. Press CTRL+F again to turn the trace off. |
| Text | Data transfer terminated by user request. |
| Explanation | Data transfer terminated by user request. You have chosen the Cancel button while the data transfer was in progress. All currently running data transfers will be terminated. |
| Action | No action required. |
| Text | Data transfer buffer error. |
| Explanation | The data transfer buffer received from Natural is in error. Data transfer terminated abnormally. |
| Action | If the error persists, create a file transfer trace and report the error to your local Software AG support. Press CTRL+F to turn the file transfer trace on. An "X" at the end of the status line shows that the file transfer trace is enabled. Press CTRL+F again to turn the trace off. |
| Text | Disk space exceeded during download. |
| Explanation | Data transfer terminated abnormally, disk space exceeded. |
| Action | Check your hard disk for errors and for free disk space. |
| Text | Error uploading data from XML file. |
| Explanation | Uploading data from the XML file failed. An error occurred while parsing the data from XML to the Natural data record. Data transfer terminated abnormally. |
| Action | Check the XML file for errors. Check that the data in the XML file matches the Natural record. |
| Text | Missing <RECORD> tag. |
| Explanation | No <RECORD> tag was found in the XML file. Data transfer terminated abnormally. |
| Action | Check and correct the XML data file. |
| Text | Cannot open temporary file for XML upload failed. |
| Explanation | The temporary file name required for the XML data upload could not be opened. Data transfer terminated abnormally. |
| Action | Check your hard disk for errors and for free disk space. Check whether you have permissions to write to the location. |
| Text | Missing TEMP or TMP environment variable. |
| Explanation | The file transfer aborted because the TEMP and TMP environment variables are not set. Entire Connection needs a temporary file for the XML data upload. Data transfer terminated abnormally. |
| Action | Check the Windows TEMP and TMP environment variables. |
| Text | Open file for data transfer failed. |
| Explanation | Open file failed for file-name. The file name, directory name, or volume label syntax is incorrect. Data transfer terminated abnormally. |
| Action | Check and correct the supplied file name. |
| Text | Data type mismatch. |
| Explanation | The data format in the record record of the file to be uploaded does not match the record format specified in the Natural program. Data transfer terminated abnormally. |
| Action | Check the data in the input file. Check the field type specified in the Natural UPLOAD statement. |
| Text | Data length greater than field length. |
| Explanation | The data transfer function of Entire Connection detected that the data sent by Natural for a field exceeds the field length as specified in the field format. The excess data will be lost. |
| Action | Check the Natural download coding in the Natural program. |
| Text | File access error. |
| Explanation | Open file failed for file-name with access denied error. Data transfer terminated abnormally. |
| Action | Check whether you have the appropriate privileges for the file and the specified location. |
| Text | Error writing to file. |
| Explanation | An error occurred while writing to file-name. Data transfer terminated abnormally. |
| Action | Check your hard disk for errors and for free space. |
| Text | Invalid usage of reserved file name. |
| Explanation | "prn" and "lpt1" to "lpt3" are reserved names which cannot be used as file names for upload and download. Data transfer terminated abnormally. |
| Action | Supply a valid file name. |
| Text | DOWNLOAD REPORT or DOWNLOAD VARIABLE conversion error. |
| Explanation | DOWNLOAD REPORT or DOWNLOAD VARIABLE must be set to ASCII (.ncd or .ncc) format only. Download to file-name failed. Data transfer terminated abnormally. |
| Action | Choose a file extension for ASCII conversion, that is, .ncd or .ncc or any extension not associated with a format conversion in Entire Connection such as .txt. |
| Text | DOWNLOAD COMMAND string is too long. |
| Explanation | The command specified in the Natural DOWNLOAD COMMAND statement is too long. The maximum command length is 276 characters. The command will not be executed. |
| Action | Correct the Natural DOWNLOAD COMMAND statement in the Natural program. |
| Text | Error writing to printer. |
| Explanation | Download to printer failed. An error occurred while writing to the printer. Data transfer terminated abnormally. |
| Action | Check your printer and the printer settings of the PC. |
| Text | Internal error processing field names. |
| Explanation | Internal error while processing field names received from Natural. Data transfer terminated abnormally. |
| Action | If the error persists, create a file transfer trace and report the error to your local Software AG support. Press CTRL+F to turn the file transfer trace on. An "X" at the end of the status line shows that the file transfer trace is enabled. Press CTRL+F again to turn the trace off. |
| Text | Non-ASCII file specified for upload. |
| Explanation | You are attempting to upload a non-ASCII file. The file being uploaded contains binary zeros. Data transfer terminated abnormally. |
| Action | Check the file you want to upload. |
| Text | Unknown Lotus field type. |
| Explanation | Unknown Lotus field type field-type in the field field of the record record detected. Data transfer terminated abnormally. |
| Action | Check the Lotus data file. |
| Text | Buffer count is in error. |
| Explanation | Buffer count is in error. The data buffer received from Natural does not have the expected sequence number. Data transfer terminated abnormally. |
| Action | Check your host connection. If the error persists, create a file transfer trace and report the error to your local Software AG support. Press CTRL+F to turn the file transfer trace on. An "X" at the end of the status line shows that the file transfer trace is enabled. Press CTRL+F again to turn the trace off. |
| Text | Variable length data cannot be uploaded. |
| Explanation | Upload data to a Natural record defined as variable is not supported. Data transfer terminated abnormally. |
| Action | Check and correct the UPLOAD statement in the Natural program. |
| Text | Invalid data in response field. |
| Explanation | The data buffer received from Natural contains invalid data in the response field. Data transfer terminated abnormally. |
| Action | Check your host connection. If the error persists, create a file transfer trace and report the error to your local Software AG support. Press CTRL+F to turn the file transfer trace on. An "X" at the end of the status line shows that the file transfer trace is enabled. Press CTRL+F again to turn the trace off. |
| Text | Data transfer buffer out of sync. |
| Explanation | The data transfer buffer is out of sync. A header data buffer was expected, but the buffer received from Natural is a normal data buffer. Data transfer terminated abnormally. |
| Action | Check your host connection. If the error persists, create a file transfer trace and report the error to your local Software AG support. Press CTRL+F to turn the file transfer trace on. An "X" at the end of the status line shows that the file transfer trace is enabled. Press CTRL+F again to turn the trace off. |
| Text | Natural data transfer terminated abnormally. |
| Explanation | A fatal error occurred and the data transfer terminated. This message is displayed after a message showing the specific error has been displayed. |
| Action | See the action for the specific error which was displayed before. |
| Text | Buffer overrun during compression. |
| Explanation | Buffer overrun during compression. The size of the record in the Natural UPLOAD statement is greater than a data transfer buffer. This only works as long as the data can be compressed enough. |
| Action | Check the upload logic in the Natural program. Try using a bigger 3270 terminal model. |
| Text | Cannot download binary data to Excel application. |
| Explanation | You cannot download binary data to an Excel application. Data transfer terminated abnormally. |
| Action | Check and correct the DOWNLOAD statement in the Natural program. |
| Text | Unknown format detected. |
| Explanation | An unknown format was detected in the data buffer received from Natural. You may be using an older version of Entire Connection which does not support a data format supported by your newer Natural version. Data transfer terminated abnormally. |
| Action | Check your Entire Connection version. Make sure you are using the latest version. If the error persists, create a file transfer trace and report the error to your local Software AG support. Press CTRL+F to turn the file transfer trace on. An "X" at the end of the status line shows that the file transfer trace is enabled. Press CTRL+F again to turn the trace off. |
| Text | File not found. |
| Explanation | The file specified for upload could not be found. Data transfer terminated abnormally. |
| Action | Check and correct the file name. |
| Text | Too many open files. |
| Explanation | The file specified for upload could not be opened because there are too many open files on the PC. Data transfer terminated abnormally. |
| Action | Check why there are that many open files and close some files. |
| Text | File already in use. |
| Explanation | The file specified for upload could not be opened because the file has already been opened by another application. Data transfer terminated abnormally. |
| Action | Check which other application has opened the file and close it. |
| Text | Network busy. |
| Explanation | The file specified for upload could not be opened because your network is busy at this time. Data transfer terminated abnormally. |
| Action | Check your network connection and try again. |
| Text | Open file failure. |
| Explanation | The file specified could not be opened. The Windows CreateFile function returned an error: error-code. Data transfer terminated abnormally. |
| Action | Try again. If the error persists, report the error to your local Software AG support. |
| Text | Conversion to the selected format not yet supported. |
| Explanation | Conversion to the selected format is not yet supported. This should only happen in a development environment. Data transfer terminated abnormally. |
| Action | Try again. If the error persists, report the error to your local Software AG support. |
| Text | File path not found. |
| Explanation | The file specified could not be opened. An invalid drive or path was specified. Data transfer terminated abnormally. |
| Action | Check and correct the file name. |
| Text | Open printer failed. |
| Explanation | Download to printer failed because there was an error in the open printer function. Data transfer terminated abnormally. |
| Action | Check the selected printer. |
| Text | Not enough memory available for spooling. |
| Explanation | The Entire Connection host printer support could not be started because there was not enough memory available. |
| Action | Check your PC system for applications with unusually high memory usage. |
| Text | Empty file error. |
| Explanation | You are attempting to upload a file with length 0. Data transfer terminated abnormally. |
| Action | Check the file you want to upload. |
| Text | Binary data format cannot be used with this file type. |
| Explanation | The Natural data record contains a binary data field. However, the file type you selected does not allow binary data. Data transfer terminated abnormally. |
| Action | Choose a file type which supports binary data. |
| Text | Open printer failed. |
| Explanation | Printing to the host printer failed because the configured PC or network printer could not be opened. There was an error with error-code error-code from the Windows OpenPrinter function. |
| Action | Check your PC or network printer. |
| Text | Unable to spool print document to printer. |
| Explanation | Printing to the host printer failed. There was an error with error-code error-code from the Windows StartDocPrinter function. |
| Action | Check the printer setup in your Windows system. |
| Text | Error reading temporary print file. |
| Explanation | Printing to the host printer failed. There was an error with error-code error-code while reading from the temporary print file. |
| Action | Check your hard disk. |
| Text | Error writing data to printer. |
| Explanation | Printing to the host printer failed. There was an error with error-code error-code while writing to the local printer printer-name. |
| Action | Check the printer setup in your Windows system. |
| Text | Error closing printer. |
| Explanation | Printing to the host printer failed. The Windows ClosePrinter function returned an error: error-code. |
| Action | Check the printer setup in your Windows system. |
| Text | Error closing printer spooler. |
| Explanation | Printing to the host printer failed. The Windows EndDocPrinter function returned an error: error-code. |
| Action | Check the printer setup in your Windows system. |
| Text | Record length exceeds 32767 bytes. |
| Explanation | The record length of the record used in the Natural DOWNLOAD statement exceeds 32767 bytes. dBase and Lotus only support a maximum record length of 32767. |
| Action | Check and correct the DOWNLOAD statement in the Natural program. |
| Text | Record read mismatch. |
| Explanation | Record read from file does not match the record requested from Natural. Data transfer terminated abnormally. |
| Action | Check the file you want to upload. |
| Text | Too many fields for specified format. |
| Explanation | The number of fields in the Natural data transfer records is greater than the number of fields supported by the PC file data format. Data transfer terminated abnormally. |
| Action | Check and correct the data transfer statement in the Natural program. |
| Text | Alphanumeric fields with length greater than 253 not supported. |
| Explanation | The Natural data record contains an alphanumeric field with a length greater than 253. The PC file data format chosen, however, does not support alphanumeric fields with such a length. Data transfer terminated abnormally. |
| Action | Check and correct the data transfer statement in the Natural program. |
| Text | Record length for DOWNLOAD VARIABLE exceeds 32767 bytes. |
| Explanation | The data record used in the Natural DOWNLOAD VARIABLE statement exceeds the limit of 32767 bytes. Data transfer terminated abnormally. |
| Action | Check and correct the data transfer statement in the Natural program. |
| Text | Data formats X, Y and U not supported by the installed version. |
| Explanation | The Natural data record contains a BLOB (X), LOB (Y) or Unicode (U) field. This is not supported in the version of Entire Connection you are using. Data transfer terminated abnormally. |
| Action | Check your Entire Connection version. Make sure you are using the latest version. |
| Text | Insufficient memory available. |
| Explanation | Insufficient memory available. Data transfer terminated abnormally. |
| Action | Check your Windows system for unusually high memory usage. |
| Text | Too many fields of type U, X or Y. |
| Explanation | The Natural data record contains too many fields of the types BLOB (X), LOB (Y) or Unicode (U). Only up to 4000 fields of these types may be contained in one record. Data transfer terminated abnormally. |
| Action | Check and correct the data transfer statement in the Natural program. |
| Text | Unicode fields with length greater than 253 not supported in PC file format. |
| Explanation | The Natural data record contains a Unicode type field with a length greater than 253. The chosen PC file format (for example, XLS), however, does not support Unicode fields with a length greater than 253. Data transfer terminated abnormally. |
| Action | Check and correct the data transfer statement in the Natural program. |
| Text | Error parsing XML file for upload. |
| Explanation | An error in the XML data file was detected in line, column. |
| Action | Check and correct the XML data file you want to upload. |
| Text | Fatal error parsing XML file for upload. |
| Explanation | An fatal error in the XML data file was detected in line, column. |
| Action | Check and correct the XML data file you want to upload. |
| Text | Warning while uploading XML file. |
| Explanation | Warning for the XML data file in line line, column column. |
| Action | Check and correct the XML data file you want to upload. |
| Text | Error while uploading XML file. |
| Explanation | An error was detected in line line of the XML file you want to upload. Data transfer terminated abnormally. |
| Action | Check and correct the XML data file you want to upload. |
| Text | Error opening print data output file. |
| Explanation | Opening of the print data output file file-name failed with error error-code. The host print job failed. |
| Action | Check your hard disk for errors and for free disk space. |
| Text | Error closing print data output file. |
| Explanation | Closing of the print data output file file-name failed with error error-code. The host print job failed. |
| Action | Check your hard disk for errors and for free disk space. |
| Text | Error writing print data to output file. |
| Explanation | Writing the print data to the output file file-name failed with error error-code. The host print job failed. |
| Action | Check your hard disk for errors and for free disk space. |
| Text | Wrong host printer support print destination. |
| Explanation | The print destination setting in the host printer session properties is wrong. |
| Action | Check and correct the print destination setting in the host printer session properties. |
| Text | Host Printer Manager could not start user print program. |
| Explanation | The Host Printer Manager could not start a user-supplied print program. Windows returned an error: error-code. |
| Action | Check and correct the program name in the host printer session, Printer LU settings. |
| Text | Error opening temporary printer file. |
| Explanation | An error with error-code error-code was returned from the open file call for the temporary printer file file-name. |
| Action | Check your hard disk for errors and for free disk space. |
| Text | Natural UNIX data transfer could not be started. |
| Explanation | Natural UNIX data transfer could not be started. A network address or port setting conflict was detected on your computer. Additional information was written to the Windows event log. |
| Action | Check the Windows event log for additional information. If the error persists, report the error to your local Software AG support. |
| Text | Out of disk space. |
| Explanation | A disk space error was returned when writing to the file file-name. |
| Action | Check your hard disk for errors and for free disk space. |
| Text | Error opening output file. |
| Explanation | The file file-name could not be opened. |
| Action | Check the file name and path setting. |
| Text | Cannot allocate memory. |
| Explanation | A memory request to the Windows operating system failed. The current Entire Connection operation failed. |
| Action | Stop Entire Connection, close other Windows applications and then try again. |
| Text | Error creating NCF file. |
| Explanation | The creation of the data transfer format file file-name failed with error error-code. |
| Action | Check your hard disk for errors and for free disk space. |
| Text | Error creating Excel Automation Server. |
| Explanation | The Excel Automation Server could not be created. Data transfer from or to Excel format failed. |
| Action | Check your Windows setup. Check whether a version of Excel is installed which is supported by Entire Connection and make sure that it works. |
| Text | Error setting Excel worksheet name. |
| Explanation | An error occurred while setting the Excel worksheet name worksheet-name. Download to the Excel file failed. |
| Action | Check whether a version of Excel is installed which is supported by Entire Connection and make sure that it works. |
| Text | Error opening Excel workbook. |
| Explanation | An error occurred while opening the Excel workbook workbook-name. Upload from the Excel file failed. |
| Action | Check whether a version of Excel is installed which is supported by Entire Connection and make sure that it works. Check whether you can open the workbook in Excel. |
| Text | Error writing data to Excel file. |
| Explanation | An error occurred while writing the Natural field names to the Excel file. Download to the Excel file failed. |
| Action | Check whether a version of Excel is installed which is supported by Entire Connection and make sure that it works. |
| Text | Error saving Excel worksheet or workbook. |
| Explanation | An error occurred while writing the Excel worksheet or workbook to disk. Download to the Excel file failed. |
| Action | Check your hard disk for errors and for free disk space. |
| Text | Error reading Excel value. |
| Explanation | An error occurred while reading values from Excel. Upload from the Excel file failed. |
| Action | Check whether a version of Excel is installed which is supported by Entire Connection and make sure that it works. Check whether you can open the file in Excel. |
| Text | Error reading last Excel cell. |
| Explanation | An error occurred while reading a cell from Excel. Upload from the Excel file failed. |
| Action | Check whether a version of Excel is installed which is supported by Entire Connection and make sure that it works. Check whether you can open the file in Excel. |
| Text | Cannot convert variant data type. |
| Explanation | An error occurred while reading data from Excel in the convert variant data type function. Upload from the Excel file failed. |
| Action | Check whether a version of Excel is installed which is supported by Entire Connection and make sure that it works. Check whether you can open the file in Excel. |
| Text | Error closing workbook. |
| Explanation | An error occurred while closing the Excel workbook workbook-name. Data transfer to or from the Excel file failed. |
| Action | Check whether a version of Excel is installed which is supported by Entire Connection and make sure that it works. |
| Text | Error closing workbooks. |
| Explanation | An error occurred while closing the Excel workbooks. Data transfer to or from the Excel file failed. |
| Action | Check whether a version of Excel is installed which is supported by Entire Connection and make sure that it works. |
| Text | Error closing Excel Automation Server. |
| Explanation | An error occurred while closing the Excel Automation Server. Data transfer to or from the Excel file failed. |
| Action | Check whether a version of Excel is installed which is supported by Entire Connection and make sure that it works. |
| Text | Error retrieving decimal character from Excel Automation Server. |
| Explanation | An error occurred while retrieving the decimal character from the Excel Automation Server. Data transfer to or from the Excel file failed. |
| Action | Check whether a version of Excel is installed which is supported by Entire Connection and make sure that it works. |
| Text | Error retrieving thousands separator character from Excel Automation Server. |
| Explanation | An error occurred while retrieving the thousands separator character from the Excel Automation Server. Data transfer to or from the Excel file failed. |
| Action | Check whether a version of Excel is installed which is supported by Entire Connection and make sure that it works. |
| Text | Maximum number of rows per worksheet exceeded. |
| Explanation | Maximum number of rows per worksheet exceeded. The maximum number of rows per worksheet is limited. The limit depends on the Excel version. Download to the Excel file failed. |
| Action | Change the download logic in the Natural program. Check the Excel version and consider using a higher version. |
| Text | Maximum number of rows per worksheet exceeded. |
| Explanation | An Excel worksheet of version 7 can store the maximum number of 16384 rows. |
| Action | Change the download logic in the Natural program. Check the Excel version and consider using a higher version. |
| Text | Error writing header to the Multiplan file. |
| Explanation | An error occurred while writing the header to the Multiplan file file-name. Download to the Multiplan file failed. |
| Action | Check the file name and path setting. |
| Text | Error writing data to the Multiplan file. |
| Explanation | An error occurred while writing data to the Multiplan file file-name. Download to the Multiplan file failed. |
| Action | Check your hard disk for errors and for free disk space. |
| Text | Error writing trailer to the Multiplan file. |
| Explanation | An error occurred while writing the trailer to the Multiplan file file-name. Download to the Multiplan file failed. |
| Action | Check your hard disk for errors and for free disk space. |
| Text | No column labels in Excel worksheet. |
| Explanation | The option to use column labels is switched on but there are no column labels in the Excel worksheet. Upload from Excel file failed. |
| Action | Check and correct the option usage. |
| Text | Unexpected column labels in Excel worksheet. |
| Explanation | The option to use column labels is switched off but there are column labels in the Excel worksheet. Upload from Excel file failed. |
| Action | Check and correct the option usage. |
| Text | Error writing header to the dBase file. |
| Explanation | An error occurred while writing the header to the dBase file file-name. Download to the dBase file failed. |
| Action | Check the file name and path setting. |
| Text | Error writing data to a dBase file. |
| Explanation | An error occurred while writing data to the dBase file file-name. Download to the dBase file failed. |
| Action | Check your hard disk for errors and for free disk space. |
| Text | Error writing trailer to the dBase file. |
| Explanation | An error occurred while writing the trailer to the dBase file file-name. Download to the dBase file failed. |
| Action | Check your hard disk for errors and for free disk space. |
| Text | Error writing data to the NCD file. |
| Explanation | An error occurred while writing data to the file file-name. Download to NCD format failed. |
| Action | Check your hard disk for errors and for free disk space. |
| Text | Binary data will be written to the NCD file. |
| Explanation | Warning: Binary data will be written to the NCD file file-name. |
| Action | Check the data that are downloaded if binary data are allowed. |
| Text | Unicode data download to NCC file format not supported. |
| Explanation | Download of Unicode data to NCC file format is not supported by Entire Connection. Data transfer aborted. |
| Action | Choose a different data file format. |
| Text | Upload Unicode data from NCC file format not supported. |
| Explanation | Upload of Unicode data from a NCC file format is not supported by Entire Connection. Data transfer aborted. |
| Action | Check and change the UPLOAD statement in the Natural program. |
| Text | Download Unicode data to printer not supported. |
| Explanation | Download of Unicode data to a printer is not supported by Entire Connection. Data transfer aborted. |
| Action | Download to a file as intermediate step. Check and change the DOWNLOAD statement in the Natural program. |
| Text | Error writing header to the DIF file. |
| Explanation | An error occurred while writing the header to the DIF file file-name. Download to the DIF file failed. |
| Action | Check the file name and path setting. |
| Text | Error writing data to the DIF file. |
| Explanation | An error occurred while writing data to the DIF file file-name. Download to the DIF file failed. |
| Action | Check your hard disk for errors and for free disk space. |
| Text | Error writing trailer to the DIF file. |
| Explanation | An error occurred while writing the trailer to the DIF file file-name. Download to the DIF file failed. |
| Action | Check your hard disk for errors and for free disk space. |
| Text | Error writing header to the ENC file. |
| Explanation | An error occurred while writing the header to the ENC file file-name. Download to the ENC file failed. |
| Action | Check the file name and path setting. |
| Text | Error writing data to the ENC file. |
| Explanation | An error occurred while writing data to the ENC file file-name. Download to the ENC file failed. |
| Action | Check your hard disk for errors and for free disk space. |
| Text | Error writing trailer to the ENC file. |
| Explanation | An error occurred while writing the trailer to the ENC file file-name. Download to the ENC file failed. |
| Action | Check your hard disk for errors and for free disk space. |
| Text | Error writing header to the PRN file. |
| Explanation | An error occurred while writing the header to the PRN file file-name. Download to the PRN file failed. |
| Action | Check the file name and path setting. |
| Text | Error writing data to the PRN file. |
| Explanation | An error occurred while writing data to the PRN file file-name. Download to the PRN file failed. |
| Action | Check your hard disk for errors and for free disk space. |
| Text | Error writing trailer to the PRN file. |
| Explanation | An error occurred while writing the trailer to the PRN file file-name. Download to the PRN file failed. |
| Action | Check your hard disk for errors and for free disk space. |
| Text | No table found in this HTML file. |
| Explanation | An error was detected in the HTML file - no more table entries found. Upload from the HTML file failed. |
| Action | Check the HTML file you want to upload. |
| Text | HTML file character set not supported. |
| Explanation | The character set name used in the HTML file is not supported by Entire Connection. |
| Action | Save the file with another encoding and try again. |
| Text | No more table entries found in HTML file. |
| Explanation | An error was detected in the HTML file file-name - no more table entries found. Upload from the HTML file failed. |
| Action | Check the HTML file you want to upload. |
| Text | Failed to write trailer to the HTML file. |
| Explanation | An error occurred while writing the trailer to the HTML file file-name. Download to the HTML file failed. |
| Action | Check your hard disk for errors and for free disk space. |
| Text | Failed to write data to the HTML file. |
| Explanation | An error occurred while writing data to the HTML file file-name. Download to the HTML file failed. |
| Action | Check your hard disk for errors and for free disk space. |
| Text | Error writing header to the Lotus file. |
| Explanation | An error occurred while writing the header to the Lotus file file-name. Download to the Lotus file failed. |
| Action | Check the file name and path setting. |
| Text | Error writing data to the Lotus file. |
| Explanation | An error occurred while writing data to the Lotus file file-name. Download to the Lotus file failed. |
| Action | Check your hard disk for errors and for free disk space. |
| Text | Error writing trailer to the Lotus file. |
| Explanation | An error occurred while writing the trailer to the Lotus file file-name. Download to the Lotus file failed. |
| Action | Check your hard disk for errors and for free disk space. |
| Text | Error writing header to the XML file. |
| Explanation | An error occurred while writing the header to the XML file file-name. Download to the XML file failed. |
| Action | Check the file name and path setting. |
| Text | Error writing data to the XML file. |
| Explanation | An error occurred while writing data to the XML file file-name. Download to the XML file failed. |
| Action | Check your hard disk for errors and for free disk space. |
| Text | Error converting PRN file. |
| Explanation | Error converting PRN file. The field separator (comma) was not found. Upload from the PRN file failed. |
| Action | Check the PRN file you want to upload. |
| Text | Start of text field not found. |
| Explanation | Error in conversion. The start of the text field was not found; the beginning quotes are missing. Upload failed. |
| Action | Check and correct the file you want to upload. |
| Text | End of text field not found. |
| Explanation | Error in conversion. The end of the text field was not found; the ending quotes are missing. Upload failed. |
| Action | Check and correct the file you want to upload. |
| Text | Invalid format of number/decimal in input file. |
| Explanation | Error in conversion. An invalid format of a number/decimal was detected in the input file. Upload failed. |
| Action | Check and correct the file you want to upload. |
| Text | Invalid format of float in input file. |
| Explanation | Error in conversion. An invalid format of float was detected in the input file. Upload failed. |
| Action | Check and correct the file you want to upload. |
| Text | Missing leading minus, plus or blank for numeric or decimal in input file. |
| Explanation | Numeric or decimal values in NCD or DBF input files must have a leading blank, plus sign or minus sign. Upload failed. |
| Action | Check and correct the file you want to upload. |
| Text | Error converting input file. |
| Explanation | A fatal error occurred while converting the data from the input file format. Upload failed. |
| Action | Check and correct the file you want to upload. |
| Text | Upload of binary data of Unicode UTF-16 data not supported. |
| Explanation | There is a binary data field in the Natural UPLOAD statement. And you specified a UTF-16 coded file for upload. This is not supported by Entire Connection. Upload failed. |
| Action | Check and correct the input file. |
| Text | Cannot find online documentation folder. |
| Explanation | The folder for the online documentation could not be found. A folder named "doc" should exist either in ProgramData\Software AG\Entire Connection or in the folder which contains the Entire Connection executables. |
| Action | Check and correct your Entire Connection installation. |
| Text | Cannot find online documentation. |
| Explanation | The Entire Connection online documentation file PCCxxxyy.chm (were xxx is the version number, and yy is the language code) could not be found. |
| Action | Check and correct your Entire Connection installation. |
| Text | Cannot start online help. |
| Explanation | The Entire Connection online documentation could not be started. An error occurred while processing the help file. |
| Action | Check and correct your Entire Connection installation. |
| Text | Cannot display Software AG web pages. |
| Explanation | An error occurred while trying to display the Software AG web page in the internet browser. |
| Action | Check your browser and check the URL used. |
| Text | Error occurred in online help. |
| Explanation | An unknown error occurred in online help. |
| Action | Check and correct your Entire Connection installation. |
| Text | Could not delete object. |
| Explanation | Deletion failed for share file object object-name. |
| Action | Check whether you have the required privileges to delete objects from the share file. Check your hard disk for errors. |
| Text | Could not delete user properties record. |
| Explanation | The user properties record object-name in the share file could not be deleted. |
| Action | Check whether you have the required privileges to delete objects from the share file. Check your hard disk for errors. |
| Text | Could not delete user group record. |
| Explanation | The user group record object-name in the share file could not be deleted. |
| Action | Check whether you have the required privileges to delete objects from the share file. Check your hard disk for errors. |
| Text | Could not delete menu record. |
| Explanation | The menu record object-name in the share file could not be deleted. |
| Action | Check whether you have the required privileges to delete objects from the share file. Check your hard disk for errors. |
| Text | Could not delete task record. |
| Explanation | The task record object-name in the share file could not be deleted. |
| Action | Check whether you have the required privileges to delete objects from the share file. Check your hard disk for errors. |
| Text | Could not delete host session record. |
| Explanation | The host session record object-name in the share file could not be deleted. |
| Action | Check whether you have the required privileges to delete objects from the share file. Check your hard disk for errors. |
| Text | Could not delete host printer session record. |
| Explanation | The host printer session record object-name in the share file could not be deleted. |
| Action | Check whether you have the required privileges to delete objects from the share file. Check your hard disk for errors. |
| Text | Could not delete color scheme record. |
| Explanation | The color scheme record object-name in the share file could not be deleted. |
| Action | Check whether you have the required privileges to delete objects from the share file. Check your hard disk for errors. |
| Text | Could not delete key scheme record. |
| Explanation | The key scheme record object-name in the share file could not be deleted. |
| Action | Check whether you have the required privileges to delete objects from the share file. Check your hard disk for errors. |
| Text | Could not delete translation table record. |
| Explanation | The translation table record object-name in the share file could not be deleted. |
| Action | Check whether you have the required privileges to delete objects from the share file. Check your hard disk for errors. |
| Text | Could not delete physical keyboard table record. |
| Explanation | The physical keyboard table record object-name in the share file could not be deleted. |
| Action | Check whether you have the required privileges to delete objects from the share file. Check your hard disk for errors. |
| Text | Could not delete terminal function code table record. |
| Explanation | The terminal function code table record object-name in the share file could not be deleted. |
| Action | Check whether you have the required privileges to delete objects from the share file. Check your hard disk for errors. |
| Text | Could not rename user properties record. |
| Explanation | The user properties record object-name in the share file could not be renamed. |
| Action | Check whether you have write privileges for objects in the share file. Check your hard disk for errors. |
| Text | Could not rename user group record. |
| Explanation | The user group record object-name in the share file could not be renamed. |
| Action | Check whether you have write privileges for objects in the share file. Check your hard disk for errors. |
| Text | Could not rename menu record. |
| Explanation | The menu record object-name in the share file could not be renamed. |
| Action | Check whether you have write privileges for objects in the share file. Check your hard disk for errors. |
| Text | Could not rename task record. |
| Explanation | The task record object-name in the share file could not be renamed. |
| Action | Check whether you have write privileges for objects in the share file. Check your hard disk for errors. |
| Text | Could not rename host session record. |
| Explanation | The host session record object-name in the share file could not be renamed. |
| Action | Check whether you have write privileges for objects in the share file. Check your hard disk for errors. |
| Text | Could not rename host printer session record. |
| Explanation | The host printer session record object-name in the share file could not be renamed. |
| Action | Check whether you have write privileges for objects in the share file. Check your hard disk for errors. |
| Text | Could not rename color scheme record. |
| Explanation | The color scheme record object-name in the share file could not be renamed. |
| Action | Check whether you have write privileges for objects in the share file. Check your hard disk for errors. |
| Text | Could not rename key scheme record. |
| Explanation | The key record object-name in the share file could not be renamed. |
| Action | Check whether you have write privileges for objects in the share file. Check your hard disk for errors. |
| Text | Could not rename system object. |
| Explanation | The object object-name in the share file could not be renamed because it is a default system object. |
| Action | You cannot rename the default system objects. |
| Text | Could not create user properties record. |
| Explanation | The user properties record object-name could not be created in the share file. |
| Action | Check whether you have write privileges for objects in the share file. Check your hard disk for errors. |
| Text | Could not create user group record. |
| Explanation | The user group record object-name could not be created in the share file. |
| Action | Check whether you have write privileges for objects in the share file. Check your hard disk for errors. |
| Text | Could not create menu record. |
| Explanation | The menu record object-name could not be created in the share file. |
| Action | Check whether you have write privileges for objects in the share file. Check your hard disk for errors. |
| Text | Could not create task record. |
| Explanation | The task record object-name could not be created in the share file. |
| Action | Check whether you have write privileges for objects in the share file. Check your hard disk for errors. |
| Text | Could not create host session record. |
| Explanation | The host session record object-name could not be created in the share file. |
| Action | Check whether you have write privileges for objects in the share file. Check your hard disk for errors. |
| Text | Could not create host printer session record. |
| Explanation | The host printer session record object-name could not be created in the share file. |
| Action | Check whether you have write privileges for objects in the share file. Check your hard disk for errors. |
| Text | Could not create color scheme record. |
| Explanation | The color scheme record object-name could not be created in the share file. |
| Action | Check whether you have write privileges for objects in the share file. Check your hard disk for errors. |
| Text | Could not create key scheme record. |
| Explanation | The key scheme record object-name could not be created in the share file. |
| Action | Check whether you have write privileges for objects in the share file. Check your hard disk for errors. |
| Text | Could not duplicate user properties record. |
| Explanation | The user properties record object-name in the share file could not be duplicated. |
| Action | Check whether you have write privileges for objects in the share file. Check your hard disk for errors. |
| Text | Could not duplicate user group record. |
| Explanation | The user group record object-name in the share file could not be duplicated. |
| Action | Check whether you have write privileges for objects in the share file. Check your hard disk for errors. |
| Text | Could not duplicate menu record. |
| Explanation | The menu record object-name in the share file could not be duplicated. |
| Action | Check whether you have write privileges for objects in the share file. Check your hard disk for errors. |
| Text | Could not duplicate task record. |
| Explanation | The task record object-name in the share file could not be duplicated. |
| Action | Check whether you have write privileges for objects in the share file. Check your hard disk for errors. |
| Text | Could not duplicate host session record. |
| Explanation | The host session record object-name in the share file could not be duplicated. |
| Action | Check whether you have write privileges for objects in the share file. Check your hard disk for errors. |
| Text | Could not duplicate host printer session record. |
| Explanation | The host printer record object-name in the share file could not be duplicated. |
| Action | Check whether you have write privileges for objects in the share file. Check your hard disk for errors. |
| Text | Could not duplicate color scheme record. |
| Explanation | The color scheme record object-name in the share file could not be duplicated. |
| Action | Check whether you have write privileges for objects in the share file. Check your hard disk for errors. |
| Text | Could not duplicate key scheme record. |
| Explanation | The key scheme record object-name in the share file could not be duplicated. |
| Action | Check whether you have write privileges for objects in the share file. Check your hard disk for errors. |
| Text | Could not update system properties. |
| Explanation | The system properties record object-name in the share file could not be updated. |
| Action | Check whether you have write privileges for objects in the share file. Check your hard disk for errors |
| Text | Could not update user properties record. |
| Explanation | The user properties record object-name in the share file could not be updated. |
| Action | Check whether you have write privileges for objects in the share file. Check your hard disk for errors. |
| Text | Could not update user group record. |
| Explanation | The group record object-name in the share file could not be updated. |
| Action | Check whether you have write privileges for objects in the share file. Check your hard disk for errors. |
| Text | Could not update menu record. |
| Explanation | The menu record object-name in the share file could not be updated. |
| Action | Check whether you have write privileges for objects in the share file. Check your hard disk for errors. |
| Text | Could not update task record. |
| Explanation | The task record object-name in the share file could not be updated. |
| Action | Check whether you have write privileges for objects in the share file. Check your hard disk for errors. |
| Text | Could not update host session record. |
| Explanation | The host session record object-name in the share file could not be updated. |
| Action | Check whether you have write privileges for objects in the share file. Check your hard disk for errors. |
| Text | Could not update host printer session record. |
| Explanation | The host printer session record object-name in the share file could not be updated. |
| Action | Check whether you have write privileges for objects in the share file. Check your hard disk for errors. |
| Text | Could not update color scheme record. |
| Explanation | The color scheme record object-name in the share file could not be updated. |
| Action | Check whether you have write privileges for objects in the share file. Check your hard disk for errors. |
| Text | Could not update key scheme record. |
| Explanation | The key scheme record object-name in the share file could not be updated. |
| Action | Check whether you have write privileges for objects in the share file. Check your hard disk for errors. |
| Text | Fatal error writing key scheme to the share file. |
| Explanation | Fatal error writing key scheme object-name to the share file. |
| Action | Check your hard disk. Restore your share file from a backup and retry. |
| Text | Share file write-protected or locked. |
| Explanation | Share file is write-protected or locked. You can only list and view the share file objects. The commands Modify, Delete, Duplicate, New and Make Public cannot be used because they require write-access permission. |
| Action | Check with your system administrator if you need to write to the share file. |
| Text | Error removing the user's private objects. |
| Explanation | Deleting a user properties record partly failed. The user properties record was deleted, but an error occurred while deleting the user's private objects. Unreferenced objects which are not visible in the Configuration Manager remain in the share file. |
| Action | Check your hard disk for errors. Restore your share file from a backup and retry. |
| Text | Could not read user properties record. |
| Explanation | A fatal error occurred while reading the user properties for user user-name. |
| Action | Check your hard disk for errors. Restore your share file from a backup and retry. |
| Text | Invalid user ID. |
| Explanation | You entered an invalid user ID. The user ID can be 1 to 16 characters long and may contain embedded blanks. |
| Action | Check and correct the user ID. |
| Text | Invalid object name. |
| Explanation | You entered an invalid object name. The object name can be 1 to 32 characters long. |
| Action | Check and correct the object name. |
| Text | Passwords do not match. |
| Explanation | The passwords you entered in the "Password" and "Confirm Password" fields do not match. |
| Action | Check and correct the password. |
| Text | "Confirm Password" field is empty. |
| Explanation | You did not enter your password in the "Confirm Password" field. |
| Action | Confirm your password in this field. |
| Text | "Password" field is empty. |
| Explanation | You did not enter a password in the "Password" field. The password can be 1 to 16 characters long. |
| Action | Enter a valid password. |
| Text | Invalid embedded blanks in name. |
| Explanation | Embedded blanks are not allowed for this object name. |
| Action | Enter a valid name. |
| Text | Administrator user ID may not be deleted. |
| Explanation | The administrator's user ID may not be deleted. You can only modify or rename the administrator's user ID. |
| Action | No action required. |
| Text | No name specified. |
| Explanation | You must enter a name for the object. |
| Action | Enter a name. |
| Text | Invalid HLLAPI DLL name. |
| Explanation | You did not enter a HLLAPI DLL name or you entered an invalid name. The name may also contain path information. |
| Action | Enter a valid HLLAPI DLL name. |
| Text | Invalid HLLAPI entry name. |
| Explanation | You did not enter a HLLAPI entry function name or you entered an invalid name. |
| Action | Enter a valid HLLAPI entry function name. |
| Text | Object name too long. |
| Explanation | The name entered for the BS2000 P-key is too long. Maximum length is 16 characters. |
| Action | Enter a valid name. |
| Text | Name already in use. |
| Explanation | The name name you entered is already in use for an object of the current user. |
| Action | Choose a different name for this object. |
| Text | Invalid object name. |
| Explanation | You entered an invalid name for the object. The name can be 1 to 32 characters long and must not contain embedded blanks. |
| Action | Enter a valid name for the object. |
| Text | Invalid session name. |
| Explanation | You did not enter a session name. A session name can be 1 to 32 characters long. |
| Action | Enter a valid session name. |
| Text | Value entered is out of range. |
| Explanation | The value entered for the TCP/IP port is not valid. The valid value range is 0 to 9999. |
| Action | Enter a value within the specified range. |
| Text | Missing TCP/IP address or host name. |
| Explanation | You did not enter a TCP/IP address or host name. This field may not be blank. |
| Action | Enter a TCP/IP address or host name. |
| Text | Invalid character in BS2000 station name. |
| Explanation | An invalid character was found in the BS2000 name. The first character of this name must not be a number. |
| Action | Enter a correct BS2000 station name. |
| Text | Missing device name. |
| Explanation | Missing device name. The device name can be 1 to 8 characters long. |
| Action | Enter a device name. |
| Text | Invalid value for columns. |
| Explanation | The value for columns is not valid. The value range is 20 to 200 for TN3270 sessions, and 80 to 255 for VT sessions. |
| Action | Enter a valid value in the specified range. |
| Text | Invalid value for rows. |
| Explanation | The value for rows is not valid. The value range is 24 to 80 for TN3270 sessions, and 24 to 7380/columns for VT sessions. |
| Action | Enter a valid value in the specified range. |
| Text | Number of group links exceeded. |
| Explanation | Cannot add object to the group. The object is already linked to 32 other groups. It is not possible to link one object to more than 32 groups. |
| Action | Check your group design. |
| Text | Error deleting group link for objects. |
| Explanation | The group could be deleted, but an error occurred while deleting the group link in the objects. This leads to inconsistent data for the objects. |
| Action | Check your hard disk for errors. Restore your share file from a backup and retry. |
| Text | The group name is already in use. |
| Explanation | Cannot add the group group-name. The group name is already in use. |
| Action | Enter a different name for the group. |
| Text | Cannot delete or rename the group EVERYONE. |
| Explanation | The group EVERYONE is a required system group which must exist with this name. |
| Action | No action required. |
| Text | Could not read user properties record. |
| Explanation | A fatal error occurred while reading the user properties record for user user-name. |
| Action | Check your hard disk for errors. Restore your share file from a backup and retry. |
| Text | A public object with the name already exists. |
| Explanation | Cannot make the object public. A public object with the name already exists. |
| Action | Check the objects for data consistency. |
| Text | Could not make object public. |
| Explanation | Could not make the object public. An error with error-code error-code occurred. |
| Action | Check your hard disk for errors. Restore your share file from a backup and retry. |
| Text | Invalid task description. |
| Explanation | You must enter a valid task description. The description can be 1 to 62 characters long. |
| Action | Enter a valid task description. |
| Text | Cannot delete a Software AG task. |
| Explanation | Software AG tasks are required system tasks which cannot be deleted. |
| Action | No action required. |
| Text | Invalid program name for the task. |
| Explanation | You did not enter a valid program name for the program to be run by this task. |
| Action | Enter the name (and path) for the program to be run by this task. |
| Text | Task is in use as startup task or shutdown task. |
| Explanation | You are not allowed to rename or delete this task. This task is also your startup task or shutdown task. |
| Action | No action required. |
| Text | Invalid extension in task program name. |
| Explanation | The program name for the task does not have a valid extension. The program name must have an extension of .COM or .EXE . |
| Action | Check and correct the program name. |
| Text | Cannot delete object. |
| Explanation | You are not allowed to delete this object. The object is either a system object, or it is a public object and you are not logged in as administrator. |
| Action | Contact your administrator if you need to delete the object. |
| Text | Cannot duplicate Software AG task. |
| Explanation | You cannot duplicate a Software AG task. Software AG tasks are predefined tasks required by the system. |
| Action | No action required. |
| Text | Cannot rename object. |
| Explanation | You are not allowed to rename this object. The object is either a system object, or it is a public object and you are not logged in as administrator. |
| Action | Contact your administrator if you need to rename the object. |
| Text | Cannot modify private objects. |
| Explanation | You are not allowed to modify this object. This is a private object of a user and you are logged in as administrator. |
| Action | Contact the owner of the object if it needs to be modified. |
| Text | Cannot delete private objects. |
| Explanation | You are not allowed to delete this object. This is a private object of a user and you are logged in as administrator. |
| Action | Contact the owner of the object if it needs to be deleted. |
| Text | Cannot rename private objects. |
| Explanation | You are not allowed to rename this object. This is a private object of a user and you are logged in as administrator. |
| Action | Contact the owner of the object if it needs to be renamed. |
| Text | Cannot modify public objects. |
| Explanation | You are not allowed to modify this object. This is a public object and you are not logged in as administrator. |
| Action | Contact your administrator if you need to modify the object. You also can duplicate the object and then modify it as your private object. |
| Text | Invalid P-key name. |
| Explanation | You did not enter a valid name for the P-key. The name can be 1 to 16 characters long. |
| Action | Enter a valid name. |
| Text | Error reading the key definition details. |
| Explanation | An error occurred while reading the detailed commands used in the key definition. |
| Action | Restore your share file from a backup and retry. |
| Text | Error deleting scheme. |
| Explanation | An error occurred in the delete scheme function. The scheme could not be deleted. |
| Action | Check your hard disk for errors. Restore your share file from a backup and retry. |
| Text | Unable to create new scheme. |
| Explanation | An error occurred in the create scheme function. The scheme could not be created. |
| Action | Check your hard disk for errors. Restore your share file from a backup and retry. |
| Text | A scheme with this name already exists. |
| Explanation | The name you entered is already used by another scheme. |
| Action | Correct and enter a unique name. |
| Text | Error setting scheme for this session. |
| Explanation | An error occurred in the setting scheme function in the session properties. |
| Action | Check your hard disk for errors. Restore your share file from a backup and retry. |
| Text | No P-key schemes are currently defined. |
| Explanation | No BS2000 P-key schemes are defined in the share file. |
| Action | Currently there is no default BS2000 P-key scheme in the share file from the installation. You have to create your own P-key schemes. |
| Text | Error in P-key content. |
| Explanation | There is an error in the definition of the BS2000 P-key at the shown position. The element is not a valid 9750 terminal function. |
| Action | Check and correct the P-key definition. |
| Text | No color schemes currently defined. |
| Explanation | No color schemes are defined in the share file. This should never happen. |
| Action | Check your hard disk for errors. Restore your share file from a backup and retry. |
| Text | No valid key scheme selected. |
| Explanation | You did not select a key scheme or the selected scheme was not found in the share file. |
| Action | Select a valid scheme. Check your share file. |
| Text | No valid color scheme selected. |
| Explanation | You did not select a color scheme or the selected scheme was not found in the share file. |
| Action | Select a valid scheme. |
| Text | Same value for background and foreground colors. |
| Explanation | The settings for the background and foreground colors in the color scheme have the same value. No characters will be visible in the terminal emulation screen. |
| Action | Correct the color setting in the color scheme. |