This file contains brief explanations for all error messages that can appear as you're using Verastream Host Integrator. The messages are in numerical order.
The application may have to be reinstalled. Contact Attachmate Technical Support.
There was not enough system memory to execute the application.
The installation file has either been corrupted or could not be found.
Event handler names chosen by the user must conform to the rules of the respective programming language.
The arguments supplied to the application on the command line were invalid.
An internal error occurred during product initialization. Contact Attachmate Technical Support.
An internal error occurred during product initialization. Contact Attachmate Technical Support.
An internal error occurred during product initialization. Contact Attachmate Technical Support.
A file specified on the command line is either missing or invalid.
An internal error occurred during product initialization. Contact Attachmate Technical Support.
An internal error occurred during product initialization. Contact Attachmate Technical Support.
The IP address may be incorrectly specified in your hosts file. Contact Attachmate Technical Support.
The application is a time-limited version that has expired. Contact Attachmate Technical Support.
An unrecognized option was specified on the application command line.
An internal error occurred during product initialization. Contact Attachmate Technical Support.
An internal error occurred during product initialization. Contact Attachmate Technical Support.
Only one instance of the Host Integrator Server may be run on a given machine at one time.
The installation file has been corrupted. Reinstall Host Integrator.
An internal error occurred during product initialization. Contact Attachmate Technical Support.
The application you are attempting to start has an upper limit on the number of instances that can be run on a given machine at any one time.
The service you are attempting to start, requires a dedicated TCP listening port to be available. Currently this TCP port is in use by another program.
Contact Attachmate Technical Support.
Contact Attachmate Technical Support.
Another administrator is in configure mode. Only one webstation is allowed to configure the server at any one time. More information...
A communication error occurred between the Administrative WebStation and the Server. Log out and then log back into the Administrative WebStation.
The version of one or more models stored on the Server is different than the version currently active on the Server.
A Server trace file could not be created or an unrecognized file system error has occurred.
The specified file could not be found. Check the path and case of the file name.
The contents of the file cannot be read by Host Integrator. They may have been altered or corrupted.
The access permissions of the specified file do not allow the attempted operation.
You attempted to create a file that already exists.
Contact your system administrator.
You attempted to write to a read-only file.
The specified file name is invalid, or the file exists and is protected. Check the spelling of the path, and make sure the path exists.
The file name contains invalid characters, refers to a directory, or is an invalid file.
You must specify a valid filename.
Select a shorter filename.
The Server failed to start the domain server. This error could be due to excessive network traffic or low system resources. Contact Attachmate Technical Support.
The specified text was not recognized by the parser. Check the text for spelling, comma separation and string quoting accuracy.
The specified text was not recognized as a valid Host Integrator command.
The specified command requires more arguments than were supplied. Check the command syntax.
A numeric argument was expected. Check the command syntax.
The specified numeric argument was not within the range of accepted values.
A string delineated by double quotes is required for the command argument.
A string delineated by double quotes with the specified format is required for the command argument.
The closing quote for a string argument was not found.
The text supplied for the numeric argument does not identify a valid Host Integrator constant.
The Host Integrator constant supplied for the command argument is not valid for the command.
The specified file has either been corrupted or does not contain Host Integrator settings.
An unknown parser error occurred. Contact Attachmate Technical Support.
The string supplied for the argument is longer than the command allows.
The specified command is not valid within the context of the current command.
The specified command requires one or more arguments that were not supplied.
The folder specified when creating a shortcut to the saved model could not be created. Check the folder name and path.
The shortcut to the saved model could not be created. Check the shortcut and folder.
The user cancelled a command to wait for an event.
The specified multiple event expression was not satisfied within the timeout given in the WaitForMultipleEvents command.
Contact Attachmate Technical Support.
Some events have prerequisites that must be met before the event will be satisfied. This error message provides additional context for an event that timed out in the case that a prerequisite condition was not met.
In order to keep Host Integrator in sync with the host application, operations and scripts often use various event commands to wait for the host to finish data transfer. Examples include waiting for a string to appear on the screen, the cursor to enter a specific location, or the host to update a particular region of the screen. This error message indicates that one of these commands failed. This usually points to a flawed model or an unexpected response from the host.
When a connector sends terminal commands to directly to Host Integrator instead of executing operations, there is often a need to queue a command to wait for the current entity to change to make sure Host Integrator remains in sync with the host. If that request to wait for a change times out, this error message is returned.
The state of the Design Tool or Server prevents the specified command from being executed.
The state of the Design Tool or Server prevents the specified setting from being modified.
The request to wait for one of a list of entities to arrive waits for a period of time specified by the timeout parameter. This error means that the defined period of time elapsed without finding any of the desired entities.
The file has either been corrupted or does not contain Design Tool settings.
This error occurs when WaitForEntities is called without any entities in the string array. At least one entity must be listed in a valid request.
An invalid option was specified on the command line. Check the command line syntax for accuracy.
The specified setting cannot be directly modified by the user.
A client requested to attach to a model that is not supported by any Servers currently running in the domain. Verify that all Servers in the domain are running and that at least one of them supports the model requested.
A client requested to attach to a session from a pool that is not supported by any Server currently running in the domain. Verify that all Servers in the domain are running and that at least one of them supports the session pool requested.
The domain is operating at its maximum capacity. Contact your system administrator.
A client request for a persistent session contained an invalid or outdated session ID.
This error means the Verastream Host Integrator session tried to access data beyond the bounds of the screen buffer. This can result from a request with invalid position parameters or from an internal error. If the request that generated this error contains any terminal screen position parameters, verify that they are valid. Otherwise, contact Attachmate Technical Support.
This error occurs when a session fails to initialize in a timely manner. Detail the exact circumstances that generated this error and contact Attachmate Technical Support.
The model file may have been altered without using the Design Tool. On the Connection menu, click Session Setup to correct the terminal type and model ID.
An invalid keyboard key name was entered.
The keystroke entered is a reserved key stroke and cannot be mapped.
The keyboard name that was entered cannot be used with the current terminal type.
You need a mouse to use the options in this dialog box.
The keyboard name was not found. Contact Attachmate Technical Support.
An essential DLL could not be loaded. Reinstall Host Integrator.
An essential DLL is missing. Reinstall Host Integrator.
An essential DLL could not be loaded. Reinstall Host Integrator.
An essential DLL is missing. Reinstall Host Integrator.
Contact Attachmate Technical Support.
Please specify a valid host name or IP address for this session.
The specified error occurred during communication with the host. Contact your system administrator or Attachmate Technical Support for further assistance.
Contact Attachmate Technical Support.
Contact Attachmate Technical Support.
The trace file was not recorded properly or has been corrupted. Choose a different trace file or re-save the trace.
The file is not a host datacomm trace file, was not recorded properly, or has been corrupted. Choose a different trace file or re-save the trace.
The keyboard was not reset properly or the host system is slow or unresponsive.
The current session setup differs from the session setup used to record the trace file. On the Connection menu, click Session Setup to correct the terminal type, model ID, and transport type.
Disconnect from the host before attempting to play back the trace file.
To correct this error, change the record limit to a non-zero positive value, or elect to not limit the number of records.
Before leaving an entity, you must save or cancel any changes you have made.
The font name specified is not valid for the Design Tool. Select a different font.
The font size is too large for the display.
One or more commands are required for the item being configured.
The use of Any Row or Any Column is not allowed in the current context.
The name of the requested navigation destination could not be resolved. Check the destination's spelling and case.
No path could be found between the current location and the requested destination. This means there is no combination of operations marked as Use for Dynamic Traversal that can complete the requested traversal.
The requested navigation took longer than the model's global timeout. This could indicate a faulty operation, a circular path, or that the requested traversal takes longer than the model allows.
This error occurs when an attempt is made to load a Verastream model that is newer than the version of Verastream being used to load it.
An unsuccessful attempt was made to contact a VHI test server. This could mean that the server name or IP address is incorrect, or that the VHI test server is not currently running.
A pooled session was identified as a rogue session and suspended.
Before you delete this object, you must remove all its external references.
Before you delete this entity, you must use the Tables dialog box to choose a different home entity for the referencing table.
Before you delete this entity, you must use the Procedure Editor dialog box to remove it from the referencing procedure.
Before you delete this recordset, you must use the Procedure Editor dialog box to remove it from the referencing procedure.
Before you delete this recordset, you must use the Operation Edit dialog box to remove it from the referencing command list.
Before you delete this attribute, you must use the Procedure Editor dialog box to remove it from the referencing procedure.
Before you delete this operation, you must use the Procedure Editor dialog box to remove it from the referencing procedure.
Before you delete this procedure, you must use the Procedure Editor dialog box to remove it from the referencing procedure.
Before you delete this column, you must use the Procedure Editor dialog box to remove it from the referencing procedure.
Before you delete this filter parameter, you must use the Procedure Editor dialog box to remove it from the referencing procedure.
Before you delete this data parameter, you must use the Procedure Editor dialog box to remove it from the referencing procedure.
Before you delete this output parameter, you must use the Procedure Editor dialog box to remove it from the referencing procedure.
You may not Save As to overwrite the current model. Please use Save instead.
Log off and or disconnect from the host before attempting to open a new model or settings file.
Many types of requests require Host Integrator to move the terminal cursor into a specific location. These requests include navigation or operation execution that contain a MoveCursor command and a request to write attributes to the terminal screen. This error means that Host Integrator tried to move the cursor into the location specified, but the global move cursor timeout expired during a tab routine. If this error is seen intermittently, try increasing the global move cursor timeout setting from its default. A larger timeout interval will not detract from model performance unless the model relies on Verastream to tab backward and forward on the same terminal screen. This requirement can typically be avoided with careful model construction and/or use of the table interface.
Log off and or disconnect from the host before attempting to restore defaults.
Many types of requests require Host Integrator to move the terminal cursor into a specific location. These requests include navigation or operation execution that contain a MoveCursor command and a request to write attributes to the terminal screen. This error means that Host Integrator tried to move the cursor into the location specified using the default mechanisms built into the product, but was unable to do so. This is because the use of arrow keys is not permitted or was insufficient. The model will need to be modified to customize how Verastream moves the cursor on the terminal screen in question. More information... Note: If you are viewing this information in the Administrative WebStation help, search the Development Kit Reference for "Advanced Model Properties".
Many character mode hosts do not allow you to use the error keys to move the cursor. On these hosts, you must override the cursor movement by specifying a different command, such as a tab key. If such a command fails, this error message is logged. Additional error messages from the failed command may also be logged. Many requests have implied requirements to move the cursor, such as writing attributes data to the terminal. This error message can appear even when you have not explicitly requested a cursor movement.
An essential DLL could not be loaded. Reinstall Host Integrator.
Many types of requests require Host Integrator to move the terminal cursor into a specific location. These requests include navigation or operation execution that contain a MoveCursor command and a request to write attributes to the terminal screen. In some models, Host Integrator has to be given the valid locations for the cursor for each entity. This is done via tabstop definition. This error means that the current entity has tabstops defined, but Host Integrator was required to move the cursor to a place that was not defined as a tabstop. To resolve this problem, redefine an attribute's location, the supplemental tabstop definition, or both.
An essential DLL is missing. Reinstall Host Integrator.
Many types of requests require Host Integrator to move the terminal cursor into a specific location. These requests include navigation or operation execution that contain a MoveCursor command and a request to write attributes to the terminal screen. This error means that Host Integrator tried to move the cursor into the location specified, but was unable to do so. This could be because the use of arrow keys is not permitted and no alternative was provided in the model, or because Host Integrator was already past the location given and could not reverse directions. More information... Note: If you are viewing this information in the Administrative WebStation help, search the Development Kit Reference for "Advanced Model Properties".
An essential DLL could not be loaded. Reinstall Host Integrator.
An essential DLL is missing. Reinstall Host Integrator.
The timeout may be due to a slow host system, network problems, or a connection failure.
An internal error occurred during validation of a property sheet. Contact Attachmate Technical Support.
An internal error occurred during parsing of a property sheet. Contact Attachmate Technical Support.
An internal error occurred during validation of a property sheet. Contact Attachmate Technical Support.
An internal error occurred during validation of a property sheet. Contact Attachmate Technical Support.
An internal error occurred during validation of a property sheet. Contact Attachmate Technical Support.
An error occurred while trying to unserialize data from stream, please contact Attachmate Technical Support for assistance.
Contact Attachmate Technical Support.
Contact Attachmate Technical Support.
Contact Attachmate Technical Support.
The remote WCP object failed to send a response within specified time-out period. Check the remote object log for additional information. For example, the connector will wait 30 seconds (or different value specified with SetMethodTimeout) for a response from the VHI server. To determine the activity or errors, check the VHI server log.
Connection cannot be completed as the product version of this component is not allowed to connect to the remote component due to version limitation. Please contact Attachmate Technical Support for assistance.
The Server you are trying to connect to is not currently running or is shutting down.
Host Integrator received an event for a deleted socket.
The connection failed because the remote object did not send a handshake reply within specified time-out period.
A connection to the remote service cannot be made. Please verify that the services are running on the machine you are connecting to.
The service you are connecting to is no longer running. It is likely that it was removed because it timed out while waiting for client connection.
Contact Attachmate Technical Support.
Contact Attachmate Technical Support.
Contact Attachmate Technical Support.
Client applications on other machines cannot connect to the Host Integrator server if the machine name is mapped to the network loopback address (127.0.0.1). Usually this condition represents a network configuration error, but it may also occur when laptops or other DHCP clients are not connected to a network. The Host Integrator server will ignore this condition unless the environment variable VHI_IGNORELOOPBACKADDRESS is set to 0. For more information please contact Attachmate Technical Support.
Contact Attachmate Technical Support.
Your system is running low on memory.
Contact Attachmate Technical Support.
The service you are connecting to is shutting down. It is possible that the service was removed because it timed out while waiting for a connection.
A connection to the remote service cannot be made. Verify that the services are running on the machine you are connecting to.
Got a socket error, please contact Attachmate Technical Support for assistance.
It is possible that your system is running low on memory.
The connection to the remote object has been broken.
Contact Attachmate Technical Support.
Contact Attachmate Technical Support.
Cannot transmit data to the remote object. It has not finished processing data that was transmitted earlier.
Verify that you have specified a valid IP address.
A connection to the remote service cannot be made. Verify that the services are running on the machine you are connecting to.
Contact Attachmate Technical Support.
Contact Attachmate Technical Support.
Contact Attachmate Technical Support.
Verify that the name of the host or Server you are connecting to is correct.
Contact Attachmate Technical Support.
Contact Attachmate Technical Support.
The 3270 screen size requested by the host is invalid or is not supported. Connect to a different host resource or contact your host system administrator.
Enter a number within the range of allowed values.
An internal sequencing error has occurred, please contact Attachmate Technical Support.
Check the spelling and case of the path, and make sure the path exists on the Server.
An internal deployment error has occurred, please contact Attachmate Technical Support.
A model can be configured only once on a given Server.
Verify that the model file is stored in a directory which has the same name as the model. If the Server is running on a UNIX system, verify both the model name and letter case. More information...
Specify a different name for the new session pool.
A client requested to attach to a session with an invalid session pool name.
Enter a number within the range of allowed values.
Enter a number within the range of allowed values.
Verify that the model path and model still exist on the Server.
A change has been made to the specified model without using the Design Tool. Try reloading the model in the Design Tool, validate, and then save the model.
One or more classes identified as event handlers for objects within the model were not found when loading the model.
The session pool from which the session was requested has reached its maximum concurrent session count. Contact your system administrator.
The Server from which the session was requested has reached its maximum concurrent session count. Contact your system administrator.
Open the model with the Design Tool and use the model validator to determine the problem with the model. Once the problem is corrected, save the model.
The model variable list assigned to the session pool from which the session was requested does not have any available entries to be allocated to a new session. Contact your system administrator.
Specify a different name for the new model variable list.
If your host does not require unique values for the any of the model variables within a model variable list, you may not need a model variable list. Contact Attachmate Technical Support.
Model variable lists cannot contain duplicate variables since variables can only be given one value.
A duplicate value for a unique model variable in a model variable list was specified.
Only one value can be supplied for a model variable associated with a session pool.
When more than one model variable list is used for a session pool, the variables in each list cannot overlap. A model variable can only be assigned one value).
The model variable list specified for the given session pool does not exist. Either the name of the list has changed, or the list has been removed.
Each session in the session pool must obtain a unique entry from the model variable list. Either decrease the count of sessions in the pool or add more entries to the model variable list.
All model variables specified for a session pool must exist in the model associated with the pool. Check the variable's spelling and case.
All model variables in a model variable list specified for a session pool must exist in the model associated with the pool. Check the variable's spelling and case.
Check the entity's spelling and case.
A client provided a value for a model variable that does not exist in the model for the session. Check the variable's name and case.
A client did not provide enough entries in model variable list to satisfy the minimum number of sessions in the session pool.
Stop the current trace before you start tracing to a different file.
Check the trace file name and trace folder for write permissions and disk space.
The specified file could not be found or contains invalid trace configuration data.
An internal error occurred during validation of a property sheet. Contact Attachmate Technical Support.
An internal error occurred during validation of a property sheet. Contact Attachmate Technical Support.
An internal error occurred during validation of a property sheet. Contact Attachmate Technical Support.
An internal error occurred during validation of a property sheet. Contact Attachmate Technical Support.
An internal error occurred during validation of a property sheet. Contact Attachmate Technical Support.
An internal error occurred during validation of a property sheet. Contact Attachmate Technical Support.
An internal error occurred during validation of a property sheet. Contact Attachmate Technical Support.
An internal error occurred during validation of a property sheet. Contact Attachmate Technical Support.
An internal error occurred during validation of a property sheet. Contact Attachmate Technical Support.
An internal error occurred during validation of a property sheet. Contact Attachmate Technical Support.
A communication error occurred between the Administrative WebStation and the Server. Log out from the Administrative WebStation and then log back in.
Stop recording and either save or discard the operation.
There is a syntax error in the condition. Click here for details on condition and filter syntax. Note: If you are viewing this information in the Administrative WebStation help, search the Development Kit Reference for "Condition Edit", and then select Condition Edit/Filter String Edit Dialog Box in the results list.
There is a syntax error in the condition. Click here for details on condition and filter syntax. Note: If you are viewing this information in the Administrative WebStation help, search the Development Kit Reference for "Condition Edit", and then select Condition Edit/Filter String Edit Dialog Box in the results list.
There is a syntax error in the condition. Click here for details on condition and filter syntax. Note: If you are viewing this information in the Administrative WebStation help, search the Development Kit Reference for "Condition Edit", and then select Condition Edit/Filter String Edit Dialog Box in the results list.
The specified attribute does not exist on the current entity.
Your model file is corrupted. Contact Attachmate Technical Support.
The specified variable does not exist.
Your model file is corrupted. Contact Attachmate Technical Support.
The specified recordset does not exist on the current entity.
Your model file is corrupted. Contact Attachmate Technical Support.
The specified field does not exist on the current entity.
Your model file is corrupted. Contact Attachmate Technical Support.
The data types in the comparison do not match. Numbers cannot be compared to strings.
The number is too large.
Only numeric expressions can be used with operators "-", "*", and "/".
Check preceding errors for details.
The specified runtime exception (DSEXCEPTION) occurred in the AADS code. Contact Attachmate Technical Support.
The specified runtime exception (DSEXCEPTION1) occurred in the AADS code. Contact Attachmate Technical Support.
The specified runtime exception (DSEXCEPTION2) occurred in the AADS code. Contact Attachmate Technical Support.
Contact Attachmate Technical Support.
Another user is logged on to the Administrative WebStation in configure mode. Switch the other user to view mode and try again. More information...
The specified domain name is not in the current configuration. Switch to configuration mode and add the domain name.
The specified Server does not appear in the list of Servers registered with this Directory Service. Reinstall the Server and register it with this Directory Service.
None of the Servers in the specified domain are currently active.
You cannot add a Server to more than one domain.
Contact Attachmate Technical Support.
AADS initialization encountered an error.
When you enable security, you need to add at least one operating system group to the Administrator profile to enforce authentication on the next login. More information...
Unauthorized attempt to shut down AADS. Please use atstart to shut down AADS.
You cannot add a domain that already exists.
The specified Server is not a member of the domain. Switch to configure mode and add the Server to the domain.
Authorized shutdown for AADS in process.
The operating system does not recognize the user ID or password. Verify the user ID and password and try again.
The user ID is not a member of an operating system group associated with the specified security profile. Please add the user to the appropriate operating system group.
Contact Attachmate Technical Support.
The SSL connection has been interrupted, or has timed out. It is also possible that the SSL certificates do not match.More information...
Contact Attachmate Technical Support.
Contact Attachmate Technical Support.
Contact Attachmate Technical Support.
There may be an SSL certificate mismatch. More information....
FIPS capable SSL libraries may be missing. More information....
Contact Attachmate Technical Support.
Contact Attachmate Technical Support.
Contact Attachmate Technical Support.
Contact Attachmate Technical Support.
Contact Attachmate Technical Support.
Contact Attachmate Technical Support.
Contact Attachmate Technical Support.
The service you are connecting to is no longer running. It has probably timed out while waiting for a connection.
Contact Attachmate Technical Support.
Contact Attachmate Technical Support.
Contact Attachmate Technical Support.
The Host Integrator session has reached an undefined state. Request another session. This is usually an indication of an unexpected host response or a flawed model.
Position parameters must be AtCursor and Length, Offset and Length; or TopRow, LeftColumn, NbrRows, and NbrColumns.
The position parameters do not fall within the confines of the current terminal screen.
A request to write to a protected field has been received. This can happen directly or through an attribute or variable.
A request was made to read or write attributes that have not been defined on the entity.
Argument lists must contain unique names for each kind of model object. For example, you cannot pass two separate values for Attribute1 in the same SetAttributes() API call.
The name of a specified entity could not be resolved. Check the entity's spelling and case.
The name of a specified attribute could not be resolved. Check the attribute's spelling and case.
An offset falls outside the confines of the current terminal screen.
A valid model has not been loaded. Contact Attachmate Technical Support.
See the API help on meta-data requests for the valid options. If you have the Host Integrator Development Kit Online Reference installed, click here to link to the Host Integrator API documentation.
See the API help on meta-data requests for the valid options. If you have the Host Integrator Development Kit Online Reference installed, click here to link to the Host Integrator API documentation.
Either the session encountered a fatal exception or the model uses event handlers and the event handler engine has been disabled due to a communication error.
See the API help on meta-data requests for the valid options. If you have the Host Integrator Development Kit Online Reference installed, click here to link to the Host Integrator API documentation.
The name of a specified variable could not be resolved. Check the variable's spelling and case.
Argument lists must contain unique names for each kind of model object. For example, you cannot pass two separate values for Variable1 in the same SetVariables() API call.
Invalid data has been passed in earlier via a SetAttributesDelayed() method call on a connector. For example, the length of the data string may be too long.
The name of a specified recordset could not be resolved. Check the recordset's spelling and case.
On entities with more than one recordset, you must explicitly set the current recordset. This error may also appear if you try to perform a recordset command on an entity with no recordsets.
This error is usually generated when trying to perform an update or operation on a specific record in the recordset, but Host Integrator has not been given a record to treat as current. To resolve this problem, explicitly set the index to a valid value or fetch a record.
A model designer designates operations that implement the various scroll actions available on a recordset. However, not all recordsets can perform each kind of scroll. For example, some recordsets can move forward but not backwards. In that case, a request to PageUp will fail with this error.
Argument lists must contain unique names for each kind of model object. For example, you cannot pass two separate values for Field1 in the same UpdateRecord() API call.
The name of a specified field could not be resolved. Check the field name's spelling and case.
A request to alter the current record can use a search filter or a specific index, but not both.
The name of a specified pattern could not be resolved. Check the pattern name's spelling and case.
Unable to import model file from a previous version due to one or more errors. Contact Attachmate Technical Support.
A file required by the Administrative WebStation was not properly installed. Please uninstall and then reinstall the Administrative WebStation. If the problem persists, contact Attachmate Technical Support.
The Server could not establish a connection to AADS for user authorization. Check to see that AADS is running. Note: This error can also appear when AADS has been reinstalled. More information...
The Server could not establish a connection to AADS for registration. If this error occurs on startup, the Server will immediately shut down. Check to see if AADS is running.
The Server failed to register with AADS. Check to see if AADS is running.
The Server you selected is not running. Start the Server and try again.
Contact Attachmate Technical Support.
The Server you have selected is in a bad state and cannot switch to configure mode. Stop and then restart the server, and then try again.
The Server you have selected is in a bad state and cannot switch to view mode. Stop and then restart the server, and then try again.
Refresh the browser to get an updated Server status.
A given session can only be viewed by one window at a time.
The Administrative WebStation failed to complete the specified action. Try again. If the problem persists, stop and then restart the Administrative WebStation.
There are no more possible additions to this list.
A duplicate node was found. Refresh the browser and submit your changes again.
At least one model should be configured on the Server before creating a session pool.
Verify that your operating system group is in the Administrator profile, then save, logout, and log back in for correct authorization. More information...
The Server you selected is not running. Verify that the Server is running and then try again.
The Server Name that you entered already exists in the list of Directory Servers. Enter a different name or login with the existing Directory Server.
Enter a valid Directory Server name in the Server Name field.
Do not use <, > or & in your input field. Use <, > or & instead.
The session that you are viewing has ended on the Server. You cannot view this session anymore.
An internal error has occurred in the Administrative WebStation. Please document the steps leading to this problem and contact Attachmate Technical Support.
All defined model variables are already within the session pool.
Contact Attachmate Technical Support.
An internal communication error occurred. This error could be due to excessive network traffic or low system resources. Contact Attachmate Technical Support.
The Server is either being restarted or has shut down. Contact your system administrator.
An internal communication error occurred. This error could be due to excessive network traffic or low system resources. Contact Attachmate Technical Support.
Contact Attachmate Technical Support.
An internal communication error occurred. This error could be due to excessive network traffic or low system resources. Contact Attachmate Technical Support.
Contact Attachmate Technical Support.
An internal communication error occurred. This error could be due to excessive network traffic or low system resources. Contact Attachmate Technical Support.
Only model connections can be suspended.
An internal communication error occurred. This error could be due to excessive network traffic or low system resources. Contact Attachmate Technical Support.
The client was not able to gracefully close the connection.
An internal communication error occurred. This error could be due to excessive network traffic or low system resources. Contact Attachmate Technical Support.
When a client requests a connection to a model or session pool, the client has 60 seconds to bind to the host session. If the timeout elapses, the host session will terminate or return to the pool.
An internal communication error occurred. This error could be due to excessive network traffic or low system resources. Contact Attachmate Technical Support.
Verify the inactivity timeout configured on the Server or contact your system administrator.
An internal communication error occurred. This error could be due to excessive network traffic or low system resources. Contact Attachmate Technical Support.
When a model connection is suspended, a timeout must be provided by the client. This timeout determines how long the session will wait for a reconnect before self-terminating.
An internal communication error occurred. This error could be due to excessive network traffic or low system resources. Contact Attachmate Technical Support.
The Server could be running low on system resources. Try restarting the Server or contact Attachmate Technical Support.
An internal communication error occurred. This error could be due to excessive network traffic or low system resources. Contact Attachmate Technical Support.
The Server is configured for Administrative WebStation security, but the webstation did not provide a certificate. Log out and then log back into the Administrative WebStation.
An internal communication error occurred. This error could be due to excessive network traffic or low system resources. Contact Attachmate Technical Support.
Server security is enabled, but the client did not provide a password for authorization.
An internal communication error occurred. This error could be due to excessive network traffic or low system resources. Contact Attachmate Technical Support.
The user ID and password supplied by the client is invalid or the user does not have permission to connect to a host session.
An internal communication error occurred. This error could be due to excessive network traffic, low system resources, or one of the Servers in the domain shutting down unexpectedly. Contact Attachmate Technical Support.
An internal error occurred during security initialization. Contact Attachmate Technical Support.
An internal communication error occurred. This error could be due to excessive network traffic, low system resources, or one of the Servers in the domain shutting down unexpectedly. Contact Attachmate Technical Support.
The token provided by the webstation or AADS was not valid. You will get this error if you configured security profiles and turned on security for your server just now. You must first log out and log back in to get a new security token that is authorized to configured this server. If the problem persists even after you logout and log back in, contact Attachmate Technical Support.
Note: This error can occur if the system time does not match on the machines running AADS and the Server.
An internal communication error occurred. This error could be due to excessive network traffic, low system resources, or one of the Servers in the domain shutting down unexpectedly. Contact Attachmate Technical Support.
An internal communication error occurred. This error could be due to excessive network traffic or low system resources. Contact Attachmate Technical Support.
An internal communication error occurred. This error could be due to excessive network traffic or low system resources. Contact Attachmate Technical Support.
An internal communication error occurred. This error could be due to excessive network traffic or low system resources. Contact Attachmate Technical Support.
An internal communication error occurred. This error could be due to excessive network traffic or low system resources. Contact Attachmate Technical Support.
An internal communication error occurred. This error could be due to excessive network traffic or low system resources. Contact Attachmate Technical Support.
An internal communication error occurred. This error could be due to excessive network traffic or low system resources. Contact Attachmate Technical Support.
An internal communication error occurred. This error could be due to excessive network traffic or low system resources. Contact Attachmate Technical Support.
The user ID and password from a client could not be authorized due to communication problems with AADS. Check to see that AADS is running.
A host session encountered a fatal error. The Server will gracefully shut down and restart. Make a note of the circumstances that led to this error and contact Attachmate Technical Support.
An internal communication error occurred. This error could be due to excessive network traffic or low system resources. Contact Attachmate Technical Support.
The Server failed to start a new host session. This error could be due to excessive network traffic or low system resources. Contact Attachmate Technical Support.
An unauthorized connection to the server was attempted. You will get this error if you configured security profiles and turned on security for your server just now. You must first log out and log back in to get a new security token that is authorized to configured this server. If the problem persists even after you logout and log back in, contact Attachmate Technical Support.
Entities can have validation parameters such as cursor position, conditions, or patterns in addition to a signature. When an operation times out, if an entity's signature was found but it could not be validated, this error is generated in addition to the timeout error.
Operations can call other operations through the Navigate command, up to a maximum of 16 concurrent calls. This error indicates that an unexpected circular loop has occurred in operation execution.
When an error has occurred during an operation, no other operations can be started until the current operation is completed.
An operation was cancelled. Unless cancelled by the user in the Verastream Design Tool, this error should be accompanied by another message indicating source of cancellation and/or the command being executed when cancel was pressed.
Starting a dynamic traversal requires that the session be on a defined entity.
All navigation requests are filled by executing one or more operations marked as Use for Dynamic Traversal. If one of those operations fails, then the entire navigation request will fail.
A request to navigate between two entities by any available path often requires traversing through several intermediate entities. One of these intermediate navigations failed, causing an overall failure of the navigation request.
A request to navigate between two entities by any available path often requires traversing through several intermediate entities. This error indicates that an intermediate navigation was aborted because the overall navigation request timed out.
A developer can designate several kinds of conditions to check during an operation. These include required attribute inputs and a string condition expression. This error indicates that a CheckOperationConditions command failed. The error message should detail the type of condition failure. See the operation definition for a list of conditions. If the message seems incorrect, make sure the command is not positioned too early in the command list. It should be positioned after all attributes have been updated and immediately before the command(s) that cause the session to move off the starting entity.
All operations are composed primarily of commands that manipulate the terminal session. This error indicates that the operation failed because one of these constituent commands resulted in an error. In most cases, there should be additional error message(s) giving more specific information about the failed command.
Operations can designate intermediate destinations, or screens that may or may not be seen during operation execution. When such an entity is recognized, Host Integrator can be instructed by the model designer to execute additional commands to bypass the screen and reach the ultimate destination. This error indicates one of the commands associated with the listed intermediate destination failed. In most cases, there should be additional error message(s) giving more specific information about the command that failed.
An operation is given a specific amount of time to complete by the model designer. This error indicates that an operation took longer than the allowed amount of time, and the operation was therefore aborted.
An operation has a set of valid locations that can be recognized during execution. These are the primary destination, the set of alternate destinations, and the set of intermediate destinations. If any other defined location is found during the operation, this error will result. If the model designer wants to have Host Integrator ignore the entity and wait for another, then this entity should be added as an intermediate destination. If the entity constitutes a valid outcome of the operation, then it should be added as an alternate destination. The same rules apply to the origin as any other entity; if the first host update does not result in departure from the origin, the origin may need to be added as an intermediate destination.
The operation named in the request could not be found on the current entity. This could be because the operation is defined on a different entity, or the name could be misspelled or not have the correct case.
All operations are properties of an entity. In order to execute an operation, the session's current location must be on the operation's owning entity. This error indicates that the session is not currently on any entity.
The navigation was aborted because another operation that queued the request to navigate timed out. Check the error stack for a failed operation.
An operation can be called from another operation by use of the Navigate command. Under these conditions, if the calling operation times out or otherwise fails, then all child operations will report this error.
A model designer can designate a set of attributes on an entity as required inputs for an operation. This error means that Host Integrator detected a required attribute that was not updated by the time the CheckOperationConditions command was executed. Check the operation definition for a list of required attributes. If this message seems incorrect, the model designer needs to check that the CheckOperationConditions command is properly positioned after all attribute updates but before the command(s) that cause Host Integrator to leave the origin entity.
A model designer can define certain host conditions during an operation as errors. These include arrival at a certain entity or detection of a certain pattern on the screen. If a navigation or operation spawns a child operation via a Navigate command, and Host Integrator detects one of these model-defined error conditions in the parent operation, the child operation will abort and log this error message. There should be additional error messages from the parent operation indicating the exact error.
A model designer can define certain host conditions during an operation to be errors. One type of model-defined error is the detection of a pattern on the terminal screen. This message indicates that Host Integrator found an error pattern on the screen. The error message should include some model-defined text specifying the nature of the problem.
A model designer can define certain host conditions during an operation to be errors. One type of model-defined error is the recognition of a particular entity that is defined as an error state. This message indicates that Host Integrator detected such an error entity. The error message should include some model-defined text specifying the nature of the problem.
Two tables with the same name are not allowed. Change one of the table names in the Tables dialog box to correct the problem.
An error occurred while trying to obtain a shared memory resource on a Unix host. Contact Attachmate Technical Support.
Two columns with the same name in a table are not allowed. Change one of the column names in the Tables dialog box to correct the problem.
The model assumes any valid state left by an operation is intended. However, this error will be logged when a script returns from an operation and the terminal session is on an unknown screen because that is an invalid state. This can occur when an operation script completes while the terminal still has unprocessed host data waiting. If this error occurs intermittently or it otherwise appears this could be the problem, use WaitForEntities or CheckTerminal methods in a loop at the end of the script to let the terminal process the host data and arrive at a defined location.
Two procedures with the same name in a procedure are not allowed. Change one of the procedure names in the Tables dialog box to correct the problem.
If a script invoked to execute an operation returns an error, the operation will be aborted. See prior messages for details on the script error.
The specified column's minimum value is greater than its maximum value. Change either the min or max value in the Tables dialog box to correct the problem.
An operation is given a specific amount of time to complete by the model designer. If the operation is configured to expect a host response, it will wait up to this period of time for host data. This error indicates that an operation waited for the allotted amount of time for a host response but did not received one. If this operation is not expecting a host response, uncheck this option in the operation's configuration and use one or more wait commands to synchronize completion of the operation as needed.
The specified column's minimum length is greater than its maximum length. Change either the min or max length in the Tables dialog box to correct the problem.
Operation execution was halted because another model object, such as an event handler script, had its timeout expire. This error should be accompanied by another message indicating the source of the timeout.
The filter parameter is mapped to an output parameter of a different data type. This may cause data to be lost in the translation when the procedure is run.
This message indicates that some object in the model other than the operation itself reported an error. For example, if an entity arrival event handler throws an exception during an operation, this message is a likely result. See other error messages for details about what caused the operation to abort.
The filter parameter is marked as an input to the procedure but it is not used in the procedure. Click here for help on creating procedures and refer to the section that corresponds to the procedure's type. Note: If you are viewing this information in the Administrative WebStation help, search the Development Kit Reference for "Creating procedures".
A model designer can define certain host conditions during an operation to be errors. One type of model-defined error is the recognition of a particular entity that is defined as an error state. This message indicates that Host Integrator detected such an error entity but finds yet another entity has become current when the error message was constructed. This is usually the result of an entity arrival script on the error entity causing the host to move away from the error entity before Host Integrator can process the error.
The data parameter is marked as an input to the procedure but it is not used in the procedure. Click here for help on creating procedures and refer to the section that corresponds to the procedure's type. Note: If you are viewing this information in the Administrative WebStation help, search the Development Kit Reference for "Creating procedures".
An operation is given a specific amount of time to complete by the model designer. If the operation is configured to expect a host response and none of its destinations are also the origin, it will wait up to this period of time for host data that causes a departure from the origin entity. This error indicates that an operation waited for the allotted amount of time but did not received the expected data from the host. If this operation is not expecting a host response, uncheck this option in the operation's configuration and use one or more wait commands to synchronize completion of the operation as needed. If this operation can end on the origin entity, add that as a destination to the operation definition.
The output parameter is marked as an output of the procedure but it is not used in the procedure. Click here for help on creating procedures and refer to the section that corresponds to the procedure's type. Note: If you are viewing this information in the Administrative WebStation help, search the Development Kit Reference for "Creating procedures".
The model variable initialization dialog was cancelled, canceling the connection attempt.
No route was found between the two specified entities in the procedure. To create a route between the two entities either change an existing operation to default or add a new default operation.
No route was found between one of the procedure's last entities and the home entity of the model. A navigation route must exist for the procedure to execute on the server.
The primary destination of the operation is not a branch or error entity in the procedure. Add the entity as a branch or error entity in the Procedure Editor to correct the problem.
No route was found between the model's home entity and the procedure's starting entity. A navigation route must exist for the procedure to execute on the server.
The alternate destination of the operation is not a branch or error entity in the procedure. Add the entity as a branch or error entity in the Procedure Editor to correct the problem.
A compound procedure uses a procedure that cannot be executed due to unsatisfied input parameters.
The branch entity in the procedure is not a primary or alternate destination in the operation. Remove this branch entity in the Procedure Editor to correct this problem.
A procedure can only branch on a static path. Either delete the branches or change to a static path in the Procedure Editor to correct this problem.
The operation along the path requires the specified attributes to have values. Map input parameters to these attributes in the Procedure Editor or mark the attributes as not required in the operation.
A compound procedure uses a procedure that provides no additional information.
The Procedure Wizard could not find a route to this entity. To create a route to the entity, either change an existing operation to default or add a new default operation.
The output parameter is mapped to a field that is write-only. This will cause an error during execution of the procedure.
The maximum length of the column is greater than the length an attribute to which it is mapped. This could cause an error during execution of the procedure.
The input parameter is compared to a field that is write-only. This will cause an error during execution of the procedure.
The maximum length of the column is less than the length an attribute to which it is mapped. This could cause an error during execution of the procedure.
The input parameter is mapped to a field that is read-only. This will cause an error during execution of the procedure.
The input parameter is mapped to an attribute that is read-only. This will cause an error during execution of the procedure.
You cannot update a recordset in a procedure if the recordset does not support direct record update.
The output parameter is mapped to an attribute that is write-only. This will cause an error during execution of the procedure.
The input parameter is compared to an attribute that is write-only. This will cause an error during execution of the procedure.
You cannot insert into a recordset in a procedure if the recordset does not support insertion.
References to fields are not allowed in this operation. There are only two situations in which fields may be referenced in an operation used in a procedure. The first situation is for operations that lead away from an entity with a recordset marked as First Record Only. The second situation is for operations that lead away from a recordset. In all other circumstances there will be no current record in the recordset.
Your model file is corrupted. Contact Attachmate Technical Support for further assistance.
Your model file is corrupted. Contact Attachmate Technical Support.
Your model file is corrupted. Contact Attachmate Technical Support.
Your model file is corrupted. Contact Attachmate Technical Support.
Your model file is corrupted. Contact Attachmate Technical Support.
Before you delete this operation, you must go to the Destinations dialog on the Operation tab of the specified entity and remove it from the referencing operation.
Your model file is corrupted. Contact Attachmate Technical Support.
Your model file is corrupted. Contact Attachmate Technical Support.
Your model file is corrupted. Contact Attachmate Technical Support.
Your model file is corrupted. Contact Attachmate Technical Support.
Your model file is corrupted. Contact Attachmate Technical Support.
There is a syntax error in the SQL statement. Click here for details on SQL-92 syntax in Host Integrator. Note: If you are viewing this information in the Administrative WebStation help, search the Development Kit Reference for "SQL API overview".
There is a syntax error in the SQL statement. Click here for details on SQL-92 syntax in Host Integrator. Note: If you are viewing this information in the Administrative WebStation help, search the Development Kit Reference for "SQL API overview".
There is a syntax error in the SQL statement. Click here for details on SQL-92 syntax in Host Integrator. Note: If you are viewing this information in the Administrative WebStation help, search the Development Kit Reference for "SQL API overview".
The SQL keyword(s) specified in the error are not supported. Click here for details on SQL-92 syntax in Host Integrator. Note: If you are viewing this information in the Administrative WebStation help, search the Development Kit Reference for "SQL API overview".
GROUP BY and HAVING clauses are not supported. Click here for details on SQL-92 syntax in Host Integrator. Note: If you are viewing this information in the Administrative WebStation help, search the Development Kit Reference for "SQL API overview".
DEFAULT and NULL cannot be used for values in a SET clause. Click here for details on SQL-92 syntax in Host Integrator. Note: If you are viewing this information in the Administrative WebStation help, search the Development Kit Reference for "SQL API overview".
The quantifiers ALL, SOME and ANY are not supported in comparisons. Click here for details on SQL-92 syntax in Host Integrator. Note: If you are viewing this information in the Administrative WebStation help, search the Development Kit Reference for "SQL API overview".
DEFAULT and NULL cannot be used for values in a VALUES clause. Click here for details on SQL-92 syntax in Host Integrator. Note: If you are viewing this information in the Administrative WebStation help, search the Development Kit Reference for "SQL API overview".
Joins are not supported. Click here for details on SQL-92 syntax in Host Integrator. Note: If you are viewing this information in the Administrative WebStation help, search the Development Kit Reference for "SQL API overview".
Parameters are not supported. Click here for details on SQL-92 syntax in Host Integrator. Note: If you are viewing this information in the Administrative WebStation help, search the Development Kit Reference for "SQL API overview".
Sub queries are not supported. Click here for details on SQL-92 syntax in Host Integrator. Note: If you are viewing this information in the Administrative WebStation help, search the Development Kit Reference for "SQL API overview".
Table correlations unsupported. Click here for details on SQL-92 syntax in Host Integrator. Note: If you are viewing this information in the Administrative WebStation help, search the Development Kit Reference for "SQL API overview".
The specified table does not exist.
The specified column in the table does not exist.
The ORDER BY clause can only be used to sort by columns selected in the SELECT clause.
The column number in the ORDER BY clause is larger than the number of columns in the SELECT clause.
A column with the name exists in more than one table. Prefix the table name to resolve the ambiguity.
The data types in the comparison cannot be compared. Strings and numbers cannot be compared.
There is a mismatch between the number of elements being compared.
Only literal expressions are allowed.
Only boolean expressions are allowed.
Only numeric expressions are allowed.
Only string expressions are allowed.
Only scalar values are allowed.
The number is too large.
Data types in the assignment mismatch. Strings cannot be assigned to numeric columns and numbers cannot be assigned to string columns.
The number of columns in the row constructor does not match either the number of columns in the INSERT INTO clause or the number of columns in the table.
Multiple SQL statements are not supported.
Multiple tables are not allowed in the FROM clause.
The specified collating sequence is not recognized. The only recognized collating sequences are CASE_INSENSITIVE and CASE_SENSITIVE.
The COLLATE operator cannot be used on numeric values.
The strings in the comparison have conflicting collating sequences. Use COLLATE CASE_INSENSITIVE or COLLATE CASE_SENSITIVE to resolve the mismatch.
The strings cannot be concatenated because their explicit collating sequences conflict. Use COLLATE CASE_INSENSITIVE or COLLATE CASE_SENSITIVE to resolve the mismatch.
The SQL statement could not be resolved into a set of procedures. This means that no procedure(s) could be found that match the request SQL operation. Subsequent error messages will list the closest procedures, if any.
The specified table for the procedure does not exist.
The specified column for the procedure does not exist in the table.
The specified procedure does not exist in the table.
The specified filter parameter is a required input of the procedure but is not supplied. All required filter parameters must be supplied.
The specified data parameter is a required input of the procedure but is not supplied. All required data parameters must be supplied.
The specified column is not a filter input to the procedure but it was supplied.
The specified column is not a data input to the procedure but it was supplied.
The specified column is not an output parameter but it was requested.
The specified integer is out of range for the column.
The specified integer is too small for the column.
The specified integer is too large for the column.
The specified string is too long for the column.
The specified string is too short for the column.
The column only allows string values.
The column only allows integer values.
The column only allows float values.
No Select procedures have been defined for the table.
No Update procedures have been defined for the table.
No Insert procedures have been defined for the table.
No Delete procedures have been defined for the table.
This procedure matches the SQL statement's type, but it cannot be used because it lacks filter parameters that appear in the statement's WHERE clause.
This procedure matches the SQL statement's type, but it cannot be used because it requires filter parameters that do not appear in the statement's WHERE clause.
This procedure matches the SQL statement's type, but it cannot be used since multiple unequal values for the same filter parameter appear in the statement's WHERE clause.
This procedure matches the SQL statement's type, but it cannot be used because it lacks data parameters that appear in the statement's SET (UPDATE statements) or VALUES (INSERT statements) clauses.
This procedure matches the SQL statement's type, but it cannot be used because it requires data parameters that do not appear in the statement's SET (UPDATE statements) or INSERT INTO (INSERT statements) clauses.
This procedure matches the SQL statement's type, but it cannot be used because it does not have output parameters that appear in the statement's SELECT clause. If you are using "SELECT * FROM ..." then enable "Allow SQL SELECT statements to return a subset of columns when all columns are requested" on the table in the model.
Host Integrator cannot guarantee that duplicate records will not be returned by the set of procedures chosen. Either use SELECT DISTINCT or remove one or more OR's in the WHERE clause to correct this problem.
The specified procedure failed. Check preceding errors for details.
The procedure was cancelled before completing.
The procedure failed due to arrival at entity not specified in the procedure. To prevent this error, use the Procedure Editor to add the entity as a branch or error entity.
The procedure failed due to an operation failing. To prevent this error, correct the operation that failed.
The procedure failed due to arrival at an undefined entity. To prevent this error, create an entity and then use the Procedure Editor to add it as a branch or error entity.
The procedure failed due to an error reading from an attribute. Check preceding errors for details.
The procedure failed due to an error reading from a field. Check preceding errors for details.
The procedure failed due to an error writing to an attribute. Check preceding errors for details.
The procedure failed due to an error writing to a field. Check preceding errors for details.
This is a user-defined error. Check with the model designer for details.
Host Integrator was unable to find the synchronization record upon returning the entity with the recordset. Try using Previous Record as the synchronization option for the recordset in the procedure. The synchronization options for the recordset can be changed in the Procedure Editor.
No record matching could be found in the recordset. One record must be found when using the First Record Only option for the recordset in the procedure.
The procedure timed out.
The procedure failed because Host Integrator was unable to navigate to the procedure's starting entity.
Host Integrator failed to navigate back to the procedure's starting entity after a failed run.
Before you delete this attribute, you must remove it from the referencing command list.
Before you delete this attribute, you must use the Advanced Entity Properties dialog box to remove it from the entity validation.
Before you delete this attribute, you must go to the Operation tab and remove it from the referencing operation.
Before you delete this attribute, you must go to the Recordset tab and remove it from the referencing recordset.
Before you delete this attribute, you must go to the Operation tab of the specified entity and remove it from the referencing operation.
Before you delete this attribute, you must go to the Recordset tab and use the Recordset Termination Options dialog box to remove it from the referencing recordset.
Before you delete this attribute, you must go to the Recordset tab and use the Recordset Termination Options dialog box to remove it from the referencing recordset.
Before you delete this attribute, you must go to the Recordset tab and use the Recordset Termination Options dialog box to remove it from the referencing recordset.
Before you delete this event, you must go to the Operation tab, select the entity in the intermediate list of the Destinations dialog, and use the Command List Editor dialog box to remove it from the referencing command.
Before you delete this event, you must go to the Operation tab and use the Command List Editor dialog box to remove it from the referencing command.
Before you delete this event, you must remove the event from the command list in this model property.
Before you delete this entity, you must remove it from the referencing command list.
Before you delete this entity, you must go to the Operation tab and use the Operation Destinations dialog box to remove it from the referencing operation.
Before you delete this entity, you must use the Model Properties dialog box to choose a different home entity.
Before you delete this entity, you must use the Model Properties dialog box to choose a different Host Emulator Start entity.
Before you delete this entity, you must remove it from the referencing command list.
Before you delete this entity, you must go to the Operation tab and remove it from the referencing operation.
Before you delete this operation, you must use the Cursor tab to select a different operation to move the cursor.
Before you delete this operation, you must use the Advanced Entity Properties dialog box to choose a different keep-alive operation.
Before you delete this operation, you must go to the Recordset tab and remove it from the referencing recordset.
Before you delete this operation, you must go to the Attribute Operations tab and remove it from the referencing attribute.
Before you delete this pattern, you must go to the Attribute tab and remove it from the referencing attribute.
Before you delete this pattern, you must use the Advanced Entity Properties dialog box to remove it from the entity validation.
Before you delete this pattern, you must go to the Operation tab and remove it from the referencing operation.
Before you delete this pattern, you must go to the Recordset tab and remove it from the referencing recordset.
Before you delete this pattern, you must go to the Recordset tab and remove it from the referencing recordset columns.
Before you delete this pattern, you must go to the Recordset tab and remove it from the referencing recordset field.
Before you delete this pattern, you must go to the Recordset tab and remove it from the referencing recordset records.
Before you delete this pattern, you must go to the Recordset tab and use the Recordset Termination Options dialog box to remove it from the referencing recordset.
Before you delete this pattern, you must go to the Recordset tab and use the Recordset Termination Options dialog box to remove it from the referencing recordset.
Before you delete this pattern, you must go to the Recordset tab and use the Recordset Termination Options dialog box to remove it from the referencing recordset.
Before you delete this variable, you must go to the Attribute tab and remove it from the referencing attribute.
Before you delete this variable, you must remove it from the referencing command list.
Before you delete this variable, you must remove it from the referencing command list.
Before you delete this variable, you must remove it from the referencing command list.
Before you delete this variable, you must use the Advanced Entity Properties dialog box to remove it from the entity validation.
Before you delete this variable, you must go to the Operation tab and use the Operation Edit dialog box to remove it from the referencing operation.
Before you delete this variable, you must go to the Recordset tab and remove it from the referencing recordset.
Before you delete this variable, you must go to the Recordset tab and remove it from the referencing recordset field.
Before you delete this variable, you must go to the Recordset tab and use the Recordset Termination Options dialog box to remove it from the referencing recordset.
Before you delete this variable, you must go to the Recordset tab and use the Recordset Termination Options dialog box to remove it from the referencing recordset.
Before you delete this variable, you must go to the Recordset tab and use the Recordset Termination Options dialog box to remove it from the referencing recordset.
An invalid Property Sheet was found. Your model file is corrupted. Contact Attachmate Technical Support.
An invalid Property Sheet was found. Your model file is corrupted. Contact Attachmate Technical Support.
An invalid Property Sheet was found. Your model file is corrupted. Contact Attachmate Technical Support.
An invalid Property Sheet was found. Your model file is corrupted. Contact Attachmate Technical Support.
An invalid Property Sheet was found. Your model file is corrupted. Contact Attachmate Technical Support.
An invalid Property Sheet was found. Your model file is corrupted. Contact Attachmate Technical Support.
An invalid Property Sheet was found. Your model file is corrupted. Contact Attachmate Technical Support.
Your model file is corrupted. Contact Attachmate Technical Support.
Your model file is corrupted. Contact Attachmate Technical Support.
Your model file is corrupted. Contact Attachmate Technical Support.
Your model file is corrupted. Contact Attachmate Technical Support.
Your model file is corrupted. Contact Attachmate Technical Support.
Your model file is corrupted. Contact Attachmate Technical Support.
Your model file is corrupted. Contact Attachmate Technical Support.
Your model file is corrupted. Contact Attachmate Technical Support.
Your model file is corrupted. Contact Attachmate Technical Support.
Your model file is corrupted. Contact Attachmate Technical Support.
Your model file is corrupted. Contact Attachmate Technical Support.
Your model file is corrupted. Contact Attachmate Technical Support.
Your model file is corrupted. Contact Attachmate Technical Support.
Your model file is corrupted. Contact Attachmate Technical Support.
Your model file is corrupted. Contact Attachmate Technical Support.
Your model file is corrupted. Contact Attachmate Technical Support.
Make sure that the validation criteria are proper and correctly specified.
Your model file is corrupted. Contact Attachmate Technical Support.
Your model file is corrupted. Contact Attachmate Technical Support.
Your model file is corrupted. Contact Attachmate Technical Support.
Your model file is corrupted. Contact Attachmate Technical Support.
Your model file is corrupted. Contact Attachmate Technical Support.
Your model file is corrupted. Contact Attachmate Technical Support.
Your model file is corrupted. Contact Attachmate Technical Support.
An Entity requires at least one screen pattern so Host Integrator can recognize it.
Your model file is corrupted. Contact Attachmate Technical Support.
Your model file is corrupted. Contact Attachmate Technical Support.
Your model file is corrupted. Contact Attachmate Technical Support.
Your model file is corrupted. Contact Attachmate Technical Support.
Your model file is corrupted. Contact Attachmate Technical Support.
Your model file is corrupted. Contact Attachmate Technical Support.
Your model file is corrupted. Contact Attachmate Technical Support.
Your model file is corrupted. Contact Attachmate Technical Support.
Either the snapshot is out of date or the entity signature needs to be changed.
Your model file is corrupted. Contact Attachmate Technical Support.
Either the snapshot is out of date or patterns need to be added to make the entity signature unique.
Your model file is corrupted. Contact Attachmate Technical Support.
Your model file is corrupted. Contact Attachmate Technical Support.
Your model file is corrupted. Contact Attachmate Technical Support.
Your model file is corrupted. Contact Attachmate Technical Support.
Your model file is corrupted. Contact Attachmate Technical Support.
Your model file is corrupted. Contact Attachmate Technical Support.
Your model file is corrupted. Contact Attachmate Technical Support.
Your model file is corrupted. Contact Attachmate Technical Support.
Your model file is corrupted. Contact Attachmate Technical Support.
Your model file is corrupted. Contact Attachmate Technical Support.
Your model file is corrupted. Contact Attachmate Technical Support.
Your model file is corrupted. Contact Attachmate Technical Support.
If this entity is reached on the Server, the model must disconnect and reconnect to reach the home entity. This will degrade the Server's performance.
This design tool message is always accompanied by additional error messages given the reasons the name was rejected.
There is a small possibility that a multi-column recordset with column of differing widths has been incorrectly defined. If so, fetched data would be misaligned.
Object names must be at least one character long.
The specified character is not permitted to be the first character. In particular, a number as the first character can be misinterpreted, lead to the string being treated as a number instead of a string identifier.
No extended characters are permitted in object names.
Only alphanumeric characters, as defined by the system locale, and the underscore character are considered valid for use in an object name.
Object names must be between 1 and 128 characters in length, inclusive.
Verastream Host Integrator has only one reserved word: variables, in any letter case. Objects cannot be named with the word variables.
The security token supplied has a bad format (zero length). Contact Attachmate Technical Support.
Security token parsing error (NULLTOKENVERIFIER): Contact Attachmate Technical Support.
Security token parsing error (TOKENPARSING). You will get this error if you configured security profiles and turned on security for your server just now. You must first log out and log back in to get a new security token that is authorized to configured this server. If the problem persists even after you logout and log back in, contact Attachmate Technical Support.
Security token parsing error (UNSUPPORTEDSUBJECTTYPE): Contact Attachmate Technical Support.
Security token parsing error (SIGNATUREHASH): Contact Attachmate Technical Support.
Security token parsing error (INVALIDSIGNATUREISSUER): Contact Attachmate Technical Support.
Security token parsing error (UNSUPPORTEDSIGNATURETYPE): Contact Attachmate Technical Support.
Security token parsing error (INVALIDTOKEN): Contact Attachmate Technical Support.
Security token parsing error (SECCTXREADONLY): Contact Attachmate Technical Support.
Security token parsing error (TOKENDATEINVALID): Contact Attachmate Technical Support.
Note: This error can occur if the system time does not match on the machines running AADS and the Server.
Security token parsing error (NOSUBJECTINFO): Contact Attachmate Technical Support.
Security token parsing error (BADBINDING): Contact Attachmate Technical Support.
Your model file is corrupted. Contact Attachmate Technical Support.
During Model Elements import, you imported an object that had a reference to an object that you did not import. To resolve that reference, a placeholder was created. Please remove or rename this placeholder.
During Model Elements import, an existing object could not be removed because a reference to it still existed. To resolve that reference, a placeholder was created. Please remove or rename this placeholder.
You can only import model elements from models with the same Session Type (5250, 3720, HP, VT) as you are currently editing.
The host system may be unresponsive or Session Setup may be incorrect. On the Connection menu, click Session Setup and verify the session settings.
If a login command list is defined, the screen present at completion must be recognized as a defined entity. Otherwise, the initial host screen must be recognized. This error means that Host Integrator failed to recognize the screen. Possible explanations are the host application has changed, the login sequence was not completed successfully or differs based on the user, or the screen is just not defined in the model.
The login command list is executed on session connect in the Server or upon request in the Design Tool. This error is typically accompanied by another error specifying the exact command that failed. If the error is not reproducible using the Design Tool command debugger, Host Integrator might be getting ahead of the host. You may need to add additional wait commands prior to sending data.
The logout command list is executed when a Server session is being shut down, or upon request in the Design Tool. This error is typically accompanied by another error specifying the command that failed. If the error is not reproducible using the Design Tool command debugger, Host Integrator might be getting ahead of the host. You may need to add additional wait commands prior to sending data. Other problems could include failure to reach the start entity or the start entity being altered in a session pool to a screen not supported by the logout script.
The auto generation of tab stops failed because a duplicate tab stop was encountered. Define the tab stops manually instead.
During tab stop generation Host Integrator makes two passes and compares the results. This error occurs when the results of the second pass do not match the first pass. The results of the first pass are still used, but they may not be correct.
A request to move the cursor must always supply row and column values that are on the display screen. This error indicates the row and column pair do not constitute a valid screen location.
The most likely cause of this error is a move cursor command or API call in a cursor forward or backward override. This would result in infinite recursion and is therefore not permitted.
When using a cursor tab override, calling the default callback to move the cursor forward or backward must result in the cursor moving to a valid tabstop. This message is the result when a move cursor forward or backward default callback moves the cursor but the resulting location is not defined as a tabstop.
Any cursor default callback will stop if a system interrupt for a timeout, user cancellation in the Design Tool, or an error. Other error messages reported subsequent to this should provide information about what caused the cursor callback to halt.
Host Integrator is unable to initialize the Property Manager. Close the current Administrative WebStation browser session, then restart the Administrative WebStation on the machine where it is installed. Start a new Administrative WebStation browser session, and try again to logon to the Administrative WebStation.
Host Integrator is unable to initialize the Property Manager. Close the current Administrative WebStation browser session, then restart the Administrative WebStation on the machine where it is installed. Start a new Administrative WebStation browser session, and try again to logon to the Administrative WebStation.
The Administrative WebStation session has timed out because it has been inactive for 30 minutes. When the Administrative WebStation times out, it returns to the login panel. The timeout is configured on the web server running the Administrative WebStation. If you are using Tomcat, the web server included in Host Integrator, click here for information about modifying the timeout.
You have started more than one instance of the Administrative WebStation from a single browser session or have ended an Administrative WebStation session without first logging out. Each Administrative WebStation session must run in its own browser session; log out from all additional sessions. If you want to run multiple instances of the Administrative WebStation, start each session in its own browser window. If you continue to experience problems, close all browser sessions and then try to start an Administrative WebStation browser session.
A valid directory server has not been specified for this installation of the Administrative WebStation. On the Administrative WebStation Login panel, click the Directory Serv button to specify a directory server. More Information...
There is a problem with the currently selected directory server. Most likely the specified name is invalid or the directory server is not functioning. On the Administrative WebStation login page, click Directory Serv and verify that the specified directory server name is correct. If you continue to experience a problem, try stopping and then restarting the directory server.
Your model file is corrupted. Contact Attachmate Technical Support.
Your model file is corrupted. Contact Attachmate Technical Support.
The Host Emulator requires at least one trace (.hetrace) file per operation defined in the model. This error indicates that Host Integrator detected that the named operation does not have such a file or has the wrong number of files. To resolve this problem, either execute the operation with Host Emulator trace recording enabled or with the Host Emulator trace Overwrite property set. See the Host Emulator recording help for further information.
The host emulator requires at least one trace (.hetrace) file per operation defined in the model. This error indicates that Verastream Host Integrator detected that the named operation does not have such a file or has the wrong number of files. This can be rectified by either executing the operation with Host Emulator trace recording enabled or with the Host Emulator trace Overwrite property set.
The CheckOperationConditions command checks the status of the terminal screen for various model-defined properties. If the screen has already changed from the origin entity, Host Integrator will issue this error because it cannot check the conditions.
The CheckOperationConditions command was executed in the context of a command list such as login or logout. Remove the command from the command list.
The CheckOperationConditions command was executed in a context other than operations. Remove the command removed from the command list.
An internal error occurred. If the problem persists, contact Attachmate Technical Support.
To add a pattern/attribute to an entity, select a section of the host screen and then click New Pattern/Attribute on the Pattern/Attribute tab.
To add an attribute to an entity, select a text field on the host screen and click New Attribute on the Attribute tab.
Use the Operation Edit dialog box to edit the invalid command. In the Operation Edit dialog box, select a command and press F1 or click Command Help for detailed online help for that command.
Use the Condition Edit dialog box to create a condition.
To move a pattern from the Unused box to the Check box, use the right arrow button. The only patterns that will appear in the Unused box will be patterns that are not considered to be a part of the entity signature.
A tabstop in the list does not accurately reflect an attribute on the entity. Click Generate to identify the tabstop positions automatically.
Note: You must first configure a move cursor command list in the Advanced Model Properties dialog box.
Choose a different name for the logging directory.
To cancel the execution of a command list, click Cancel button in the Command List in Progress dialog box.
To select an operation to move the cursor forward, select the Move forward check box and then choose an operation. To select an operation to move the cursor backward, select the Move backward check box and follow the same procedure.
To add an operation to an entity, click New Operation on the Operation tab, choose an operation destination, and define a command list. Alternatively, if the Design Tool is set to generate operations automatically, an operation will be generated as you manually traverse to the selected entity.
Use the Signature Analyzer dialog box to identify pattern mismatches, then edit or delete the bad patterns on the Pattern tab. Alternatively, you can connect to the host, navigate to this entity, and click Update in the General tab of the Advanced Entity Properties dialog box to update the snapshot.
To create a snapshot for an entity, connect to the host, navigate to that entity, and click the Update button on the General tab of the Advanced Entity Properties dialog box.
Use the Signature Analyzer to compare the patterns of this entity with other entities in your host application model. Add one or more patterns on the Pattern tab to uniquely identify this entity.
An error occurred while attempting to update the current entity. Please document the sequence of events that led to this error, click Cancel on the entity window, save your work to a new file, and contact Attachmate Technical Support.
Choose a different name.
Choose an operation destination.
Use the Operation Edit dialog box to create an operation command list.
Enter a name.
To add a pattern to an entity, select a static section of the host screen and click New Pattern on the Pattern tab.
A pattern cannot be used for both entity signature and validation. To remove a pattern from the validation list, open the Advanced Entity Properties dialog box, go to the Validation tab, select that pattern, and click Remove.
To add a pattern to an entity, use the cursor to select a static section of the host screen and click the New Pattern button on the Pattern tab.
An error occurred while attempting to display a host screen. Please document the sequence of events that led to this error, exit Host Integrator, and contact Attachmate Technical Support.
Use the Test Recordset dialog box to test a data fetch of a recordset.
Note: Testing recordsets will only function while you are connected to a host.
To add an entity, traverse to a host screen and click New Entity on the entity window.
Choose a different name for the log file.
Choose one or more recordset termination criteria.
Select a section of recordset text in the host screen and click the Update button.
Select a section of the recordset in the host screen and click New Field.
Select the Read check box to make this field readable. Select the Write check box to make this field writable.
To add an operation to an entity, click New Operation on the Operation tab, choose an operation destination, and then define a command list.
Choose one or more pattern properties, for example text.
Enter text that appears on that area of the host screen.
A pattern cannot be used for both entity signature and operation error. To remove a pattern from the operation pattern list, go to the Conditions dialog for the operation.
Enter text to be returned on the host screen if unable to locate a relative attribute during fetch.
As long as a procedure is used in a compound procedure its type cannot be changed. If you want to change it you must first remove it from the compound procedure.
An error occurred while attempting to save the variables. Please document the sequence of events that led to this error, cancel the dialog box, save your work to a new file, and contact Attachmate Technical Support.
The recordset selection test failed. The selection operation did not reach an expected destination. Click the Operation tab and use the Operation Edit dialog box to edit the selection operation.
Select the Read check box to allow the variable to be readable. Select the Write check box to allow an API developer to change the value of this variable after it's been deployed to the Host Integrator Server. Select the Hidden check box to make the variable inaccessible to a developer via the model file after it's been deployed to the Host Integrator Server.
Enter a different number.
Enter a different number.
The minimum length must be smaller than the maximum. Enter a different number.
Enter a different number.
Enter a different number.
The minimum value must be smaller than the maximum. Enter a different number.
Click Yes to generate attributes automatically, No to cancel.
Click Yes to discard this operation, No to cancel.
The list of tabstops matches the list of tab keystrokes that stop at each attribute on the selected entity.
Click Yes to permanently delete the current entity, No to cancel.
Click Yes to use offline mode, No to cancel.
Click Yes to disconnect from the current session, No to cancel.
Click Yes to generate a unique name, No to cancel.
Click Yes to use the current operation when a dynamic traversal is requested and that traversal needs to jump from the current entity to an adjacent entity. Click No to cancel.
Click Yes to generate patterns automatically, No to cancel.
Click OK to have Host Integrator make each line a separate pattern. Click Cancel to return to the dialog box and adjust the pattern text to make all lines equal.
Click Yes to replace the existing command list, No to cancel.
Redefine the pattern so that the text and search region are the same size, or enable the "Search in extended region" option.
Click Yes to erase encrypted values for this variable, No to cancel.
Performed syntax checking of the expression. No errors found.
The procedure ran to completion successfully.
The procedure has no validation errors or warnings.
You cannot change a procedure's type without losing the entity and parameter mappings. Click Yes to change the type, No to cancel.
The parameter is mapped to an attribute, field, or another parameter. Removing the parameter from the procedure will also remove these mappings. Click Yes to remove the parameter, No to cancel.
Changing a procedure's home entity may break the procedure until it is re-edited. If you change a procedure's home entity you should check that each procedure's path is still correct in the Procedure Editor. Click Yes to change the home entity, No to cancel.
Click Yes to apply changes, No to cancel. Go to offline mode, use the Signature Analyzer dialog box to identify pattern mismatches, and then edit or delete the bad patterns on the Pattern tab.
The new local keyboard is substantially different. Click Yes to reset keyboard maps to defaults, No to cancel.
Click Yes to delete the entire command list, No to cancel.
A recordset field must be within a record of the recordset. To add a field to a recordset, select an area within the recordset on the terminal screen that contains specific data and click the New Field button. By default, a name and the start and end offsets of the field are provided by the Design Tool.
Use the Operation Edit dialog box to edit the invalid command. In the Operation Edit dialog box, select a command and press F1 or click Command Help for detailed online help for that command.
An error occurred while attempting to save a command. Please document the current command and argument values, cancel the dialog, save work to a new file, and contact Attachmate Technical Support.
Choose one or more filter options for recordset fetch termination.
A recordset field must be within a record of the recordset. To add a field to a recordset, select an area within the recordset on the terminal screen that contains specific data and click the New Field button. By default, a name and the start and end offsets of the field are provided by the Design Tool.
Click Yes to update the initial cursor position, No to cancel. Note: If you have configured any entity properties relative to a cursor position, these property coordinates will be automatically updated. Click Apply to save your changes or click Cancel to revert your initial cursor position back to its original state.
To move an attribute from the Unused box to the Return box, use the right arrow button.
To update the snapshot for an entity, connect to the host, navigate to that entity, and click the Update button on the General tab of the Advanced Entity Properties dialog box.
To use the 'End of screen is always a delimiter' option, you must go to the Recordset Options dialog and deselect the 'Host overlaps records across screens' option.
To use the 'Host overlaps records across screens' option, you must go to the Recordset/Layout tab and uncheck the 'End of screen is always a delimiter' box.
Use the Operation Edit dialog box to edit the command list. In the Operation Edit dialog box, select a command and press F1 or click Command Help for detailed online help for that command.
An error occurred while attempting to save a command. Please document the current command and argument values, cancel the dialog, save work to a new file, and contact Attachmate Technical Support.
Use the Operation Edit dialog box to edit the command list. In the Operation Edit dialog box, select a command and press F1 or click Command Help for detailed online help for that command.
Use the Operation Edit dialog box to edit the command list. In the Operation Edit dialog box, select a command and press F1 or click Command Help for detailed online help for that command.
Performed syntax checking of the expression. No errors found.
The model loaded into the Design Tool contained an invalid command in an operation. Please document the text that could not be parsed, and contact Attachmate Technical Support.
If the specified location is not relative to the cursor position, row and column parameters must be from 1 to the current screen height and width of the terminal display.
Click Yes to add a 'Navigate to the starting entity' command to the start of the logout command list, No to cancel.
The terminal screen has changed and does not match the current entity. Check the pattern definitions. Temporarily clear the Wait for cursor check box on the Validation tab of the Advanced Entity Properties dialog box. If you do not clear this check box, the screen snapshot will fail because the entity is set to match attributes according to cursor positioning and generating a tabstop changes the cursor position.
Logout command list must start at the home entity. If you experience any problems, press the Record button to record another command list from the home entity.
To add a pattern to an entity, use the cursor to select a static section of the host screen and click the New Pattern button on the Pattern tab.
Choose one from the pattern property combo box.
The Event Expression or Condition cannot be an empty string.
This line is discarded because it has no text.
Click Yes to overwrite existing library, No to cancel.
Each line of the pattern may not be wider than the pattern region. Redefine the pattern by either decreasing the width of the pattern text or increasing the width of the pattern region.
Click Yes to update the initial cursor position, No to cancel. Note: If you have configured any entity properties relative to a cursor position, these property coordinates will be automatically updated.
Click Yes to apply changes, No to cancel. More patterns should be added to make the screen signature unique.
In Windows NT, directories created with all capital letters are translated to mixed case. This can result in a mismatch between model folder names and their corresponding model file names. If you transfer model files to a Host Integrator Server running on a UNIX or Windows system, this situation could result in failure to find models.
The specified character is not allowed in model names.
In the Design Tool, you cannot close the Test Recordset dialog box while an operation is still executing. When you need to stop the operation, click Break.
Host Integrator was unable to set the requested index. The most likely reason is that the index is greater than the total number of records. This message will also be displayed when Host Integrator has no means to reach the index. For example, if the recordset has scrolled past the requested index and there is no PageUp or Home operation defined, Host Integrator cannot fulfill this request and will return this error.
No records were returned because the end of the recordset has been reached.
When saving a model in the design tool with the host emulator option turned on, Verastream Host Integrator will display this error if the model was saved but the required files for the host emulator were not. The most likely cause of this problem is the lack of all required trace (.hetrace) files in the model's Traces subdirectory. See the Host Emulator Traces Status dialog box for details.
When saving a model in the Design Tool with the Host Emulator option enabled, Host Integrator will display this error if the model was saved but the required files for the Host Emulator were not saved. This error appears because a required trace (.hetrace) file is missing in the model's Traces subdirectory. See the Host Emulator Traces Status panel for details.
Host Emulator traces are saved according to the number of AID keys in the operation. If there are fewer traces than AID keys, you most likely have an outdated Host Emulator trace for the given operation. Use the Overwrite traces feature for Host Emulator trace recording to rectify this situation.
This error usually results from a variable being marked as write-only. This may have been done to protect passwords or other sensitive data.
The variable is probably marked as read-only.
Some Host Integrator system settings, such as cryptographic certificates and keys, require that the data values assigned have a specific format.
Some Host Integrator system settings, such as UserID and Password, Device Name, and Port, are disabled after the session is connected to the host. This reflects the fact that the state at host connect is the only one of significance for these settings. If a variable is mapped to one of these system settings, writes to that variable will also be disabled.
During model execution Host Integrator was asked to write data from a variable to the terminal, but the specified variable has never been initialized with a valid value. This most often happens in the context of an operation.
If a variable is marked as needing initialization at host connect, the variable must be provided with a value either from the connector in the connect() method or from a model variable list created in the console. Host Integrator detected a failure to initialize such a variable.
Change the value of the variable to a unique value, or turn off the Unique checkbox for this variable.
Change the value of the variable to a unique value, or turn off the Unique checkbox for this variable.
A variable in the previously saved Model Variable List does not exist in the current model. The variable and its values have been discarded. If you wish to retain the entries for this model variable, you may cancel from the deployment options dialog after dismissing this error message, then redefine the model variable.
The home entity designated for the session pool which was previously saved in the deployment file no longer exists. The model home entity is being used as default. When you dismiss this error you can press Cancel to make no changes to your Deployment Package data, Clear to start fresh with no Deployment Package data, or edit and save your Deployment Package data.
The home entity designated for the session pool which was previously saved in the deployment file no longer exists. The model home entity is being used as default. When you dismiss this error you can press Cancel to make no changes to your Deployment Package data, Clear to start fresh with no Deployment Package data, or edit and save your Deployment Package data.
The home entity designated for the session pool which was previously saved in the deployment file no longer exists. The model home entity is being used as default. When you dismiss this error you can press Cancel to make no changes to your Deployment Package data, Clear to start fresh with no Deployment Package data, or edit and save your Deployment Package data.
For help with the validator, click here. Note: If you are viewing this information in the Administrative WebStation help, search the Development Kit Reference for "Validator".
Make sure the Host Integrator server is running and that the model has been successfully validated.
One or more error messages have been returned by the deployment tool, as the result of an attempt to deploy a model to the local server.
Change the value of the variable to a unique value, or turn off the Unique checkbox for this variable.
An object's location is calculated to be off the terminal screen.
A recordset operation failed.
Host Integrator tries to keep the current record in the recordset on the screen at all times using the Page Up and Page Down operations. This error indicates that Host Integrator failed to do so because either a recordset operation failed or a recordset operation is not defined.
An internal error has occurred. Contact Attachmate Technical Support.
Using the Line Up and Line Down operations, Host Integrator tried to set the host's current record to match the current record in the recordset. This error indicates that Host Integrator failed to do so because either a recordset operation failed or a recordset operation is not defined.
In order to perform a specific recordset operation, it must be defined under Recordset Operations in the Design Tool.
Host Integrator executed either the Line Up or Line Down operation expecting the host to change its current record, but the host's current record either did not change or did not change to the expected record.
This recordset operation cannot be performed in the current context. Typically this means a Page Up operation was attempted on the first page or a Page Down operation was attempted on the last page.
Host Integrator is unable to determine the host's current record using the model specified current record preferences.
The Recordset index cannot be set beyond the end of the recordset.
The current host record has been filtered out of the fetch. Thus the current record index for the recordset cannot be set at this record.
A recordset can support navigation by record selection. However, the model designer must map an operation on the entity to the Selection operation property of the recordset. An attempt to execute the selection operation without such a mapping will result in this error.
The recordset index is invalid.
Direct insertion of new records into a recordset is a feature that can be enabled and specified by the model designer as appropriate. If that feature is not enabled, a request to perform an insertion will be rejected with this error.
Direct updates of records in a recordset is a feature that can be enabled and specified by the model designer as appropriate. If that feature is not enabled, a request to perform an update will be rejected with this error.
The operation mapped as the Selection operation on the specified recordset failed. There should be information regarding the nature of the failure in additional error messages generated as part of the exception.
When searching for a record by filter, if no matching records were found between the starting point and the end of the recordset, Verastream Host Integrator will return this error.
This message error should be accompanied by additional error messages providing more details on the exact nature of the problem encountered.
This message error should be accompanied by additional error messages providing more details on the exact nature of the problem encountered.
One property of the direct record insertion feature is where to insert the new record. One option is to find the first blank record. If that option is selected and Verastream Host Integrator is unable to locate a blank record, this error will result.
One property of the direct record insertion feature is where to insert the new record. One option for the model designer is to specify a condition that matches the insertion record. If this option is selected and Verastream Host Integrator cannot find a matching record, this error will result.
The Recordset is empty.
The requested action assumes the context of the current entity. However, no recordset field by this name was found. Be sure the name is spelled correctly and with correct letter case.
A recordset field before write operation failed.
A recordset field auto-tab operation failed.
A recordset field after write operation failed.
The requested action assumes the context of the current entity. However, no recordset field by this name was found. Be sure the name is spelled correctly and with correct letter case.
The requested action assumes that the named recordset is the current recordset on the given entity.
A Host Integrator session attempted to send an event to the Log Manager without first initializing its connection to this subsystem.
You have not been granted permission to perform the requested operation.
A request sent to the Host Integrator Log Manager was incorrectly formed. Contact Attachmate Technical Support.
A Host Integrator process attempted to bind to a server's logger that is not currently active.
The currently configured logging directory contains corrupted message files. Try restarting the Log Manager or specifying a new directory for log messages.
The Host Integrator Log Manager is unable to use the currently configured directory to store log messages. Try specifying a new directory for log messages.
The Host Integrator Log Manager cannot access the files in the currently configured logging directory. Check the permissions on the directory and the files it contains.
The Host Integrator Log Manager is unable to establish a connection with the configured email server. Verify that your email notification settings are correct, the hostname can be resolved, and the email server is running on the specified port.
The currently configured email server refused to accept an email message from the Host Integrator Log Manager. Verify that the configured email server allows email messages to originate from this server's address.
A request was made to the Host Integrator Log Manager, but it does not recognize the request.
Contact Attachmate Technical Support.
The Host Integrator Server cannot connect to the Log Manager. Ensure the Host Integrator Log Manager is running on this host. The server will periodically retry connection attempts. If this error continues to occur, contact Attachmate Technical Support.
The Host Integrator log viewer cannot establish a connection to the requested Host Integrator Log Manager. Verify that the requested Log Manager is running.
Contact Attachmate Technical Support.
The specified directory cannot be used by the Host Integrator Log Manager. Verify that the directory exists on the server, and that the Log Manager has read and write permissions to access it.
Contact Attachmate Technical Support.
The Log Manager does not currently contain any entries to view for the selected server.
The type of message store requested is not known by the log viewer and cannot be opened on the server selected.
The cursor name specified during the creation of a new cursor is already in use on this connection. Try a different name or close the previous cursor.
The Host Integrator Log Manager does not recognize the query dialect used by this log viewer. Verify that you are using compatible versions.
A syntax error has been detected in the query string at the indicated position.
The Host Integrator Log Manager does not maintain a column with the indicated name.
The cursor specified is not currently open.
An attempt was made to perform an operation using two different SQL data types.
The Host Integrator Log Manager does not maintain a table with the indicated name.
A client attempted to access a message store that is not present on the selected server.
The specified command failed. There is usually some additional information the form of prior error messages or in the descriptive text to explain the failure. If not, consider the state of the terminal screen and the context of the command when trying to determine a cause.
Save the work to a new file and contact Attachmate Technical Support. If the model file has been edited outside the Design Tool, it may have been corrupted.
Save the work to a new file and contact Attachmate Technical Support. If the model file was edited outside the Design Tool, it may have been corrupted.
The specified command failed at the specified index of the command list. There should be some additional information the form of subsequent error messages to provide the context of the command list failure. There may also be a prior message indicating a more specific reason for failure.
When a script or operation is cancelled while a command is executing, Host Integrator will report the current command for informational purposes. If the system seems stalled during a command sequence, it is usually because the executing command is waiting for something the host is never going to do.
Once you have clicked cancel, you cannot queue any additional operations or scripts until the cancelled command set has been fully stopped. Wait for the prior operation or script to finish.
All objects in Verastream Host Integrator, including attributes, are referenced internally by a numeric identifier. If an attempt is made to access an attribute on the current entity with an invalid identifier, this error will be returned. If all requested attributes exist on the current entity, then the next most likely problem is a corrupt model. You will probably need to contact Attachmate Technical Support for assistance.
All objects in Verastream Host Integrator, including attributes, are referenced internally by a numeric identifier. If an attempt is made to access an attribute on the current entity with an invalid identifier, this error will be returned. If all requested attributes exist on the current entity, then the next most likely problem is a corrupt model. You will probably need to contact Attachmate Technical Support for assistance.
Each request to modify attributes must contain attributes from a single entity. Any request that contains attributes from more than one entity will cause this error to be generated.
Each attribute has a maximum length governed by the model and based on the properties of the terminal screen. This error indicates that the value string is too long for the attribute.
Verastream Host Integrator must move the cursor to the start of an attribute in order to write data into it. If the attempt to move the cursor into position fails, then Verastream Host Integrator will return this error. Possible problems include the model may needing to have cursor movement commands redefined, or the entity requiring additional tabstop definitions, or the terminal state preventing the cursor from being moved.
In IBM blockmode terminals and HP format mode screens, the user is only allowed to modify certain areas of the screen. If an attribute or recordset field is marked as writable but corresponds to a read-only (protected) area of the screen, Verastream Host Integrator will disallow access and return this error.
Some terminal screens can define fields to be numeric only. This error indicates an attempt to Write non-numeric text to one these fields.
The requested action assumes the context of the current entity. However, no attribute by this name was found. Be sure the name is spelled correctly and with correct letter case.
The model designer has marked this attribute as read only. No updates from operations or from a connector are permitted.
The model designer has marked this field as read only. No updates from operations or from a connector are permitted.
The model designer has marked this attribute as write only. No access from operations or from a connector are permitted. This is often done to prevent access to data such as passwords.
The model designer has marked this field as write only. No access from operations or from a connector are permitted. This is often done to prevent access to data such as passwords.
If the default cursor movement has been overridden and tabstops defined on the entity, each writable attribute must correspond to a tabstop. Otherwise, Verastream Host Integrator will be unable to position the cursor correctly and the write will fail. This error occurs when an attempt is made to write to an attribute that does not have a tabstop. The model designer should either add the appropriate tabstop or mark the attribute as read-only.
An attribute before write operation failed.
An attribute auto-tab operation failed.
An attribute after write operation failed.
This error indicates that a client or script tried to set delayed inputs on an entity which has the immediate arrival processing flag turned on. Use of this entity property is not compatible with delayed inputs. If dynamic data input is needed on arrival, try setting variable values and writing them to the terminal in an entity arrival event handler. In that event handler, be sure that the terminal prepared for input by using any needed wait commands (such as WaitForKeyboardUnlocked or WaitForDisplayScreen) in the arrival event) or the host session may stall or report errors due to illegal input.
A request was made on the Verastream model which requires the current terminal screen to be defined as an entity. If a client application receives this error, define and map an unrecognizedScreen event and save the contents of the terminal screen for analysis. If an event handler receives this error, capture the contents of the terminal screen in the exception processing code.
The GETOBJECTLOCATIONS_ command can only be successfully processed when a current Entity exists.
The GETOBJECTLOCATIONS_ command can only be successfully processed when a current Entity exists.
The OBJECTLOCATION_ Property Sheet is a vital element of the GETOBJECTLOCATIONS_ command. Without it, there is not reason for being.
The GETOBJECTLOCATIONS_ command can only be successfully processed on the following objects: Attributes, RecordSet Fields, Patterns, and RecordSets.
The Scroll Lock keyboard mode is used to stop terminal input under some conditions. This error message indicates that there is text on hold until Scroll Lock is turned off.
The host keyboard was not reset properly or the host system is slow or unresponsive.
The server name does not resolve to the ip address.
Contact Attachmate Technical Support.
Contact Attachmate Technical Support.
Contact Attachmate Technical Support.
User has not been authorized to lock configuration. More information...
Another user is logged on to the Administrative WebStation in configure mode. Switch the other user to view mode and try again. More information...
Unable to unlock configuration. More information...
Unable to find the server name in DNS.
The peer AADS initiating contact has not been registered with this AADS.
DirService rejecting configuration update from peer DirService.
DirService unable to authenticate peer AADS.
DirService unable to connect to or authenticate to peer AADS.
DirService unable to unregister primary AADS.
DirService unable to store properties file.
DirService unable to load properties file.
DirService detects error in ldap parameters.
DirService unable to obtain group information.
DirService: incorrect userid or password for Ldap administrator.
DirService: unable to contact peer AADS for initial configuration.
DirService: unable to restore configuration to prior state.
DirService: switching authentication modes requires turning off product security and clearing security profile groups.
DirService: Configuration changes rejected by peer AADS. Check log messages for rejection reasons.
DirService: unable to process X509 certificate.
DirService releasing configuration lock.
DirService: configuration not locked.
There is a syntax error in the event expression.
There is a syntax error in the event expression.
There is a syntax error in the event expression.
The specified event does not exist on the current entity or in the global events.
Your model file is corrupted. Contact Attachmate Technical Support.
One of the events specified as part of a WaitForMultipleEvents command could not be created.
One of the events specified as part of a WaitForMultipleEvents command had an error occur during its evaluation.
The region on the screen specified as part of a wait event is not a valid region.
The current entity used in the definition of a wait event is not a valid entity.
The location in the definition of a wait event is not a valid location.
The XML file you are trying to import has a syntax error.
See Documentation for required values for this XML node.
See Documentation for required values for this XML node.
See Documentation for valid values for this XML node.
Node has different child nodes depending whether its mode is rectangular or linear.
An internal error occurred while importing XML. Contact Attachmate Technical Support.
An internal error occurred while importing XML. Contact Attachmate Technical Support.
An internal error occurred while importing XML. Contact Attachmate Technical Support.
Node Id must take the format 'NodeName.#'.
A valid number is either an decimal integer or of the form 0X### for hex or 0### for octal.
See Documentation for valid values for this XML node.
An internal error occurred while importing XML. Contact Attachmate Technical Support.
RSRecordSize node with a PatternMarker containing PMNormal, PMNumeric, or PMAlpha requires StartColumn and EndColumn nodes.
StartColumn and EndColumn values must be between 1 and the record set width and StartColumn cannot be greater than EndColumn.
RSRecordSize node with a PatternMarker containing PMNormal, PMNumeric, or PMAlpha requires StartColumn and EndColumn nodes.
The specified numeric argument was not within the range of accepted values.
This design tool message is always accompanied by additional error messages given the reasons the name was rejected.
Each object in a list must have a unique name.
The id of an object should correspond to its node type.
Object idref's can only be of certain types.
Patterns used in validation must belong to the same entity as the validation node.
A pattern cannot be used for both entity signature and validation.
EndOfScreenIsDelimiter is in RSRecordSize and overlapsRecordsAcrossScreens is in RSScrollingBehavior.
Enter some text in this node.
Certain objects referred to by the idref must belong to the same root node as this node.
An internal error occurred while importing XML. Contact Attachmate Technical Support.
Bad Doctype.
Cannot import an XML model file without a model context. Please open an associated Model before importing the XML file
Property Sheets cannot have a property ID_ of 0x0.
WaitForMultipleEvents Command Item must contain one or more commands.
An internal error occurred while creating a Session View packet. Contact Attachmate Technical Support.
An internal error occurred while creating a Session View packet. Contact Attachmate Technical Support.
Before deleting the entity, you must go to the Events dialog and remove this event or change its parameters to no longer reference this entity.
Before deleting the attribute, you must go to the Events dialog and remove this event or change its parameters to no longer reference this object.
Before deleting the recordset, you must go to the Events dialog and remove this event or change its parameters to no longer reference this object.
Before deleting the recordset field, you must go to the Events dialog and remove this event or change its parameters to no longer reference this object.
Before accepting a global event definition, all of the event parameters must be properly specified.
The timeout may be due to a slow host system, network problems, or a connection failure.
The timeout may be due to a slow host system, network problems, or a connection failure.
The timeout may be due to a slow host system, network problems, or a connection failure.
See the help on resetting the script manager for troubleshooting information.
Please consult the Host Integrator server log for more information on the error that caused the script manager to fail.
Prior to initializing the script manager, a test connection is made to ensure that there is no script manager already running and that the TCP listening port for the server is not in use. The information obtained from the connection attempt suggests that there is a third-party application listening on the TCP port used by the script manager.
The Design Tool invokes Windows CreateProcess method with user-defined command lines. Check that any escape code substitution gave the desired result and that any applications referenced are on the system path.
An attempt to connect to the script manager failed.
An attempt to communication with script manager failed.
An attempt to communicate with the script manager failed because the script manager is offline. In the design tool the script manager can be restarted with the 'Reload Handlers' button on the toolbar. In the server the script manager will be restarted upon server restart.
An internal error occurred in the scripting runtime while processing a request. More information surrounding the fault can be found in via the tracing system.
The event in progress was aborted by the user or a failure to recover after a timeout.
An unhandled exception occurred in an event handler. See message contents for a description of the error.
An invalid value was returned from the specified event handler method.
A call to event resulted in an exception. See additional error messages for details.
An invalid parameter was passed to the specified event handler callback method.
A callback to the Host Integrator server from an event failed. See additional error messages for details.
An event handler was invoked recursively. An event handler for a given event object can not be invoked while is it already in progress.
An event callback method was invoked at an inappropriate time. If you have the Host Integrator Development Kit Online Reference installed, click here for more information about callback limitations.
An event handler failed to return its response before its configured timeout.
An attempt to communicate with the script manager timed out waiting for a connection.
The Design Tool requires the ability to write to files and folders within the model folder during model development. In the event that read-only access is encountered for any of these files or folders, the model will be opened in read-only mode.
The 'Model Load' event handler returned an error when activating the model. This event handler must succeed (if supplied) for the model to be available on the Host Integrator server.
An event handler has encountered a fatal error that has left the script manager in an unstable condition. The Host Integrator server will be shut down and restarted.
Changing the current entity while executing this event handler is not allowed.
Changing the current recordset while executing this event handler is not allowed.
An operation or procedure responsible for initiating an event has timed out, causing the need to interrupt the event handler.
The script manager process terminated unexpectedly. The Host Integrator server will be shut down and restarted.
This message should always be preceded by one or more other error messages with more specific information. The additional information could be derived from an exception thrown by the user's event handler code. Alternatively, the additional messages could be internal system errors such as the event handler could not be found or the handler time out expired.
This message should always be preceded by one or more other error messages with more specific information. The additional information could be derived from an exception thrown by the user's event handler code. Alternatively, the additional messages could be internal system errors such as the event handler could not be found or the handler time out expired.
Contact Attachmate Technical Support.
Contact Attachmate Technical Support.
Contact Attachmate Technical Support.
This message should always be preceded by one or more other error messages with more specific information. The additional information could be derived from an exception thrown by the user's event handler code. Alternatively, the additional messages could be internal system errors such as the event handler could not be found or the handler time out expired.
This message should always be preceded by one or more other error messages with more specific information. The additional information could be derived from an exception thrown by the user's event handler code. Alternatively, the additional messages could be internal system errors such as the event handler could not be found or the handler time out expired.
Field locations returned from the ParseRecord event must fall within the bounds of the parent record. Check your event handler to ensure that it is returning a valid location for this field.
Record locations returned from the ParseScreen event must fall within the bounds of the parent recordset. Check your event handler to ensure that it is returning a valid location for each record.
Check your event handler to ensure that it is returning a valid current host record index.
Record locations returned from the ParseScreen event must fall within the bounds of the parent recordset. Check your event handler to ensure that it is returning a valid location for each record.
A command or event handler callback was invoked at an inappropriate time. See the documentation on the command or event handler callback for details about when it can be called.
An attempt to communicate with the script manager was aborted.
The named event handler assigned to this object was not found in any of the event handler libraries.
The event handler assigned to this object implements the wrong type of events for that object.
The assigned event handler does not implement any events.
The unrecognized screen event is triggered at defined points when Verastream expects to see a defined entity but does not find one. Verastream will report an error if this condition is not corrected. This message indicates that, in addition to the error generated by the lack of a current entity, the unrecognized screen event also returned an exception of its own. The contents of the exception are shown at the end of this message.
The entity arrival event is triggered when Verastream initially detects a defined entity. There is no event that can be triggered during a system timeout, but entity arrival and departure events will be triggered as appropriate regardless of system error state. This message indicates that, in addition to the possible additional errors present, the entity arrival event returned an exception of its own. The contents of the exception are shown at the end of this message.
The entity departure event is triggered when Verastream initially detects a defined entity is no longer present. There is no event that can be triggered during a system timeout, but entity arrival and departure events will be triggered as appropriate regardless of system error state. This message indicates that, in addition to the possible additional errors present, the entity departure event returned an exception of its own. The contents of the exception are shown at the end of this message.
As part of an operation implemented by an event handler, a callback was made to wait for arrival. That request includes a timeout, and this error means that timeout expired before arrival was detected.
A scripted operation either explicitly called the WaitForArrival callback or it implicitly called that functionality by returning at a location that was not a valid destination. While WaitForArrival was processing, the user pressed cancel or some other object the system reported an error. Either condition results in WaitForArrival to be cancelled.
A scripted operation either explicitly called the WaitForArrival callback or it implicitly called that functionality by returning at a location that was not a valid destination. While WaitForArrival was processing, another object timed out or logged an error to cause an abort.
The script manager TCP port, used for debugging, must be a numeric value between 0 and 65535.
The password and confirm password strings must match.
An attempt to manipulate a scripted session has failed do to an invalid identifier.
Under some circumstances, the UnrecognizedScreen and EntityDeparture events can request an entity to be current even though Verastream does not recognize its signature patterns. However, the name provided does not match any defined entity. Check spelling and letter case.
An invalid parameter was passed to the specified method.
A call to the Host Integrator server from an event failed. See additional error messages for details.
An attribute's location is calculated to be off the terminal screen.
A recordset field's location is calculated to be off the terminal screen.
A recordset record's location is calculated to be off the terminal screen.
A recordset column's location is calculated to be off the terminal screen.
An object cannot be located on the screen, since the object to which it is relative could not be located.
An attribute could not be located on the screen, since the object to which it is relative could not be located.
A recordset field could not be located on the screen, since the object to which it is relative could not be located.
A recordset record could not be located on the screen, since the object to which it is relative could not be located.
A recordset column could not be located on the screen, since the object to which it is relative could not be located.
An internal communication error occurred. This error could be due to excessive network traffic or low system resources. Contact Attachmate Technical Support.
An internal communication error occurred. This error could be due to excessive network traffic or low system resources. Contact Attachmate Technical Support.
In order to connect to a model from a non-rejuvenation session, the model must have at least one entity defined.
A problem has occurred accessing previously stored deployment options for this model. Default settings for these options will be used.
The portion of the XML file referenced by this error does not match the schema definition.
Provides details of the XML error encountered.
The IP Address is badly formed
The Host Name has an illegal character
The Host Port Number should between 1 and 65535
The XML file referenced by this error is either not present or not well formed.
The portion of the XML file referenced by this error is not well formed.
This error describes an internal fault. Please contact Attachmate Technical Support for assistance.
The system cannot create a required COM object. This error typically occurs due to a corrupt installation.
The package or namespace contains invalid characters or reserved words
The class name contains invalid characters or is a reserved word
The class name is reserved and cannot be used for an event handler
Enter a valid model name
The model already exists
Enter a valid settings file name
Either the amount of time to wait was not long enough or the host was never going to send more data.
An error occurred in the API library. Specifics are detailed in the error text.
A user defined error. Specifics are detailed in the error text.
The process string event handler is not defined in the model. The process string API can only be used if this event handler is defined.
An error occurred while attempting to create a model debug report. This error only affects the generation of a model debug report for the session. Client requests will remain unaffected.
An error occurred while recording a model debug report. This error only affects the generation of a model debug report for the session. Client requests will remain unaffected.
Host Integrator was unable to move the generated model debug report to its storage location. This error only affects the generation of a model debug report for the session. Client requests will remain unaffected.
The temporary model debug file used by Host Integrator has been changed or deleted by a third party. This error only affects the generation of a model debug report for the session. Client requests will remain unaffected.
The specified file has either been corrupted or does not contain a Host Integrator debug report.
Use a more recent version of Host Integrator to open the specified file.
The opening of the model debug report was cancelled by the user.
The saving of the model debug report was cancelled by the user.
Close one or more model debug reports before attempting to open another report.
No message was found matching the search criteria.
The current model does not contain the specified object. Load the model that was used to generate the message store to avoid this error.
Find message was cancelled before a matching message was found.
A unique trailing escape sequence can not be found because the data does not end with an escape sequence.
The regular expression operator is unrecognized. The only valid operators are "m" and "s".
The regular expression operator is specified more than once.
The regular expression modifier is unrecognized. The only valid modifier is "i".
The regular expression modifier is specified more than once.
The regular expression contains an invalid collating element name.
The regular expression contains an invalid character class name.
The regular expression contains an invalid escaped character or trailing escape.
The expression contains an invalid back-reference.
The regular expression contains mismatched [ and ].
The regular expression contains mismatched ( and ).
The regular expression contains mismatched { and }.
The regular expression contains an invalid range in a {}.
The regular expression contains an invalid character range. For example [b-a].
One of *?+{ was not preceded by a valid regular expression.
The regular expression is too complex.
Insufficient memory to determine whether the regular expression could match.
A nested regular expression is uninitialized.
An attempt to create a variable-width look-behind assertion was detected.
VHI does not support encrypted private keys for use in secure host communications.
The provide private key does not match the certificate.
© 1999-2008 Attachmate Corporation. All rights reserved. Terms of Use.