Error messages 8000 to 8500 - Documentation for BMC Helix Innovation Suite 23.3
Elijah King
Published Apr 07, 2026
The error handler cannot be found on this server.
The specified error handler does not exist in the AR System database. You attempted an operation against the wrong server, or no workflow object is defined by that name.
Change to the correct server, or specify the correct name.
The error handler name cannot exceed 254 characters.
The name of an error handler is limited to 254 characters.
Filter error handlers exceeded the maximum number of levels.Could not locate error handler in schema workflow list.
For an error handler to function, it must be associated with the same schemas as the parent workflow object. The parent workflow object is the workflow that has been designed to invoke an error handler when an error occurs. This error will occur if AR System server encounters a defined error handler that is not associated with the schema related to the parent workflow object.
An error handler cannot use itself as its own error handler.
To avoid recursive operations, a workflow object must not refer to itself as its own error handler.
The context for the called filter is missing.
Internal AR System server error. Contact Customer Support.
One or more entries matched filter conditions -- your current setting considered any match as an error.
A match for a Push filed filter action is considered as an error.
Some of the fields and/or workflow in this form are not supported in this version of the client.
When you retrieve a list of field definitions for a form, a failure occurred in the destination structure while filtering certain field IDs such as attachment fields.
The copy operation is not successful because of permission issues.
An owned container cannot have a list of subadministrator groups. The list is disregarded.
An owned container cannot have a list of subadministrator groups. The list is disregarded.
Floating License Timeout change will only take effect after server restart.
The number of hours for the Write Floating License Timeout was changed in the Timeouts tab of the Server Info window. These server configuration settings do not take effect until the server is stopped and restarted.
Full Text floating license timeout change will only take effect after server restart.
The number of hours for the Full Text Search Floating License Timeout was changed in the Timeouts tab of the Server Info window. These server configuration settings do not take effect until the server is stopped and restarted.
Referenced character menu cannot be found.
The character menu listed in the message is referenced in a container, but it no longer exists.
Create the character menu or remove the reference from the container.
The system cannot recognize some characters. Unrecognized characters are ignored.
The server parsed the data you specified, but at least one additional character could not be interpreted.
Extraneous characters are ignored.
Index length longer than 255 bytes may not work on all databases.
The operation proceeds. However, some database products do not support indexes exceeding 255 bytes in length.
For more information, consult your database product documentation.
Request to not fire filter workflow on merge was ignored because user is not an administrator.The RPC socket number specified is not one of the legal values (0, 390600, 390621 - 390634, 390636 - 390669, 390680 - 390694).
When connecting the client to AR System server, you set the RPC socket number to a value outside the legal range. The legal ranges of values are:
- 0
- 390600
- 390621 to 390634
- 390636 to 390669
- 390680 to 390694
The RPC port specified is not one of the legal values (0, 1 - 65535).
When connecting the client to AR System server, you set the TCP/IP port to a value outside the legal range. The legal range of values are 0 and 1 to 65535.
The server's RPC version is not supported.
An error occurred during an attempt to create an RPC connection because this version of AR System server is no longer supported.
To continue, upgrade to a later version of AR System.
RPC control failed to set non-blocking I/O mode. Continuing in blocked I/O mode.
The RPC-Non-Blocking-IO parameter was set in the AR System configuration file, but the AR System server continues in blocking mode.
For more information, see Configuration settings N-R
Port is busy — check with netstat to view ports in use.
This message appears when a server is started on a port that is in use.
The Server Version Control Reservation fields can only exist on one form.The data entered is invalid. The Server Version Control Reservation mode can only be 0 for disabled mode or 10 for enabled mode.
Specify a value of 0 or 10. Verify the Object Reservation option on the Version Control tab of the AR System Administration: Server Information form.
The requested object is reserved by another user.The operation failed because another user has reserved the form.The operation failed because another user has reserved the filter.The operation failed because another user has reserved the active link.The operation failed because another user has reserved the character menu.The operation failed because another user has reserved the escalation.The operation failed because another user has reserved the container.The operation failed because another user has reserved the application.The operation failed because another user has reserved the image.The operation failed because another user has reserved the dependent join form.The operation failed because another user has reserved the related filter.The operation failed because another user has reserved the related active link.The operation failed because another user has reserved the related escalation.The operation failed because another user has reserved the related container.The operation failed because another user has reserved the related application.The object cannot be reserved because it does not exist on the server. You must save an object on the server before you can reserve it.Version control object modification log mode must be either 0 for disabled mode or 10 for enabled mode.
Specify a value of 0 or 10. Verify the Object Modification Log option on the Version Control tab of the AR System Administration: Server Information form.
The Server Version Control Task fields can only exist on one form.The Server Version Control Object Modification Log fields can only exist on one form.The operation succeeded, but all or some of the corresponding log entries were not added to the AR System Version Control: Object Modification Log form.
The operation succeeded, but logging failed.
The Defintion Files option on the Version control tab must be either 0 for save and 10 for not save.
Specify a value of 0 or 10. Verify the Definition Files option on the Version Control tab of the AR System Administration: Server Information form.
The Server Version Control Label fields can only exist on one form.The Server Version Control Labeled Object fields can only exist on one form.The operation succeeded, but label was not created to the AR System Version Control: Label form.The operation succeeded, but all or some of the corresponding labeled object entries were not added to the AR System Version Control: Labeled Object form.The operation failed because the form object is already reserved.The operation failed because the filter object is already reserved.The operation failed because the active link object is already reserved.The operation failed because the character menu object is already reserved.The operation failed because the escalation object is already reserved.The operation failed because the container object is already reserved.The operation failed because the application object is already reserved.The operation failed because the image object is already reserved.The operation failed because the dependent join form object is already reserved.The operation failed because the related filter object is already reserved.The operation failed because the related active link object is already reserved.The operation failed because the related escalation object is already reserved.The operation failed because the related container object is already reserved.The operation failed because the related application object is already reserved.Task not found.Duplicate task.Checkpoint not found.Duplicate checkpoint.Task creation failed.Checkpoint creation failed.Cannot delete open task.Permission denied because the user is not the task owner.The number of rows exceeded the maximum allowed limit of 999.
You tried to set the number of rows for a character field in Developer Studio to less than 999.
Please select a source code control provider application.
In the Server Information form's Source Control tab, you clicked the Browse button, but no source control provider was selected in the Provider Name field. Before you click the Browse button, install a source control system and select it from the Provider Name list.
