Error messages 601 to 700
The specified command-line argument is not a recognized argument for this program. Verify the definition of the program for information about the valid command-line arguments. The program does not execute with invalid arguments specified.
The command line has both a
Specify either the
A command-line argument is not appropriate for the operation being performed. Review the documentation of the command for details about the options allowed with each operation.
In User form, Allowed Client Types field only accepts integer values with delimiter ';'. Any non-integer value will throw the "ARERR 606" to the user.
A required option for the specified operation is missing. Supply all required options. Review the documentation for the command for details about the options required with each operation.
The specified option expects a value but none was specified. Supply an appropriate value.
The specified value is not one of the legal tags (
The server could not open the access control server cache file (
Dynamic groups are not permitted in the definition of a computed group.
The user specified as the administrator user to allow you to perform this command is not a recognized user in the system. Connect with a valid user with administrator access.
The value for the group type option must be an integer code 1 for a view group and 2 for a change group. The value specified is not one of these values. Re-enter the command, and specify an appropriate value.
The value for the license type option must be an integer code (0 = no license, 1 = fixed license, 2 = floating license). The value you specified is not one of these values. Re-enter the command, and specify an appropriate value.
The user trying to log in is not a registered user. Although the system was configured to allow guest users, the user is not allowed to log in as a guest user because the user name differs from a registered user.
An incorrect group ID value was specified for a dynamic group, or a group ID in the dynamic group range was specified for a regular group. Group IDs in the range from 60000 to 60999 must be used only for groups in the dynamic group category.
The computed group definition contains a circular reference. Remove the circular reference.
The syntax of the computed group qualification is incorrect. Make sure that the syntax is correct.
Computed group list contains invalid information.
The system found two forms containing the same open license tag specified in the change history. An associated error message identifies the forms.
The system encountered an error while trying to process the license tag file.
The system encountered an error while trying to prepare open write licensing. An associated error message contains details.
Make sure that your user name and password were entered correctly.
Consecutive login attempts failed because of invalid passwords. The AR System server administrator can configure the number of attempts to allow. To unlock your account, reset your password or contact your administrator.
To ensure that this error message appears instead of error 623, set the following parameters in the AR System Configuration Generic UI form.
A date in the holiday list of the Business Time Holiday form is not a legal date. Illegal dates are ignored and processing continues.
A time specified in the Business Time Workday form is invalid. Invalid times are treated as if no time was specified, and processing continues.
The system found two forms containing the reserved holiday fields. For business time processing to continue, delete one of the forms. An associated error message identifies the forms.
The system could not find a form with the specified reserved holiday fields on it. Business time processing involving holiday schedules cannot proceed without this form. During installation, a definition file with copies of the business time forms was placed on the server system. The Holiday form can be imported from that definition.
The tag included in this message was specified as a holiday tag on a business time calculation. However, this tag cannot be found in the Holiday form. Either correct the workflow to reference a legal tag, or add a new tag to the Holiday form.
The system found two forms containing the reserved workday fields. For business time processing to continue, delete one of the forms. An associated error message identifies the forms.
The system could not find a form with the specified reserved workday fields on it. Business time processing involving workday schedules cannot proceed without this form. During installation, a definition file with copies of the business time forms was placed on the server system. The Workday form can be imported from that definition.
The tag included in this message was specified as a workday tag on a business time calculation. However, this tag cannot be found in the Workday form. Either correct the workflow to reference a legal tag, or add a new tag to the Workday form.
The workday schedule does not contain any open hours. For a workday schedule to be valid, at least one minute during the week must be defined as open. Fix the definition to specify open times for the schedule.
The Business Time Segment form must be unique. You cannot have more than one copy of this form.
The shared library you are using for the catalog is old or corrupted.
You specified a time segment that does not exist in the Business Time Segment form. Make sure that the associated tag name is correct, or create another Time Segment.
The level parameter of the Application-Bus-Time2-Get-Free-Window command is out of range. Rerun the command, specifying a level of 1 to 1000.
The Business Segment-Entity Association form must be unique. You cannot have more than one copy of this form.
A Business Segment-Entity Association form was not found. This error can occur if the shared library you are using for the catalog is old or corrupted.
Level 1 and Level 2 Time segments are special time segments. Level 1 can only be Available and Level 2 can only be Unavailable.
For a recurrence time segment, the start time must be less than the end time.
The full text search (FTS) information for the specified tag represents a piece of information that has a data type different from the type specified in the update operation, or the value specified is out of the legal range of values for the FTS information setting. Retry the operation, specifying the correct data type for the value.
The data value specified for one of the full text search (FTS) values is an empty string. If a value is specified, it must have a legal value assigned. Omit this value from the Set operation, or supply a value.
You specified a code for a piece of full text search (FTS) information that was not recognized. Review the
The value you specified for the list of information to retrieve from the FTS value was
The server encountered an error while trying to connect to the full text search (FTS) database. An associated error message contains details. Fix the problem, and restart the server process.
This generic message indicates that an error occurred during a full text search (FTS) operation. An associated error message contains the full text of the error message from the FTS engine.
While performing a full text search (FTS) operation, an error occurred while reading from the FTS database. An associated message contains the full text of the error message from the FTS engine.
While the system tried to retrieve or set the Ignore Words list, an error occurred. An associated message contains the full text of the error message from the full text search (FTS) engine.
This error is often caused by a permission problem with the Ignore Words list file. Search the FTS home directory and index directory for a file named
While the system tried to update the Ignore Words list, an error occurred. An associated error message contains the full text of the error message from the full text search (FTS) engine.
An error occurred during an attempt to change the location of the full text search (FTS) index directory. An associated error message contains the full text of the error message from the FTS engine.
This error commonly occurs when the target location does not exist, does not have appropriate permissions, or does not have enough disk space for the existing FTS index.
The operation you attempted generates a full text search (FTS) command that is too large for the database to handle. Break the operation into smaller pieces. For example, if you are searching on many different fields that are FTS-enabled or you are issuing many different qualifications against a single FTS-enabled field, reduce the number of operations being performed. Consider using the accrue capability to combine searches for multiple values on the same field.
An error occurred during a full text search (FTS). An attempt was made to search on a field that is not a character, diary, or attachment field. This message indicates an error in the database structure tables. Contact Customer Support.
An attempt was made to retrieve or set information about the full text search (FTS) environment on the server, but no Full Text Search Option licenses are defined for the server. If you are not using the product's FTS capability, ignore this error. To use the FTS capability, obtain a license.
You tried to perform an operation that can only be performed when the full text search (FTS) state is set to Enabled. It is set to Disabled. To perform this operation, change the FTS state to Enabled, and retry.
You tried to perform an operation that can only be performed when the full text search (FTS) state is set to Disabled. It is set to Enabled. To perform this operation, change the FTS state to Disabled, and retry.
The full text search (FTS) operation failed because the search criteria had syntax errors. An associated error message contains complete information from the FTS engine. Contact Customer Support for assistance in resolving the error.
You tried to move the location of the full text search (FTS) index directory. The target directory already exists. To move the index directory, the directory you will be using cannot already exist. If the directory you specified is incorrect, change the name to the directory you want. If it is correct and an empty directory is in place, remove the directory and retry the operation.
The field you are performing the search on is a full text search (FTS) enabled field; however, the index does not exist on this field. Its creation is pending. It might take a few minutes or a few hours for the index to be created and put in place, depending on the amount of indexing pending.
For now, the system defaults to the search strategy supported by the underlying database. When the indexing is completed, the field will be available for full text searches again.
The indexer for running the Full Text Search indexing cannot be found.
The Status History field (core field ID 15) cannot be enabled for a full text search. You performed an operation that attempted to index this field.
The query compares two fields that involve full text indexed fields. The full text search capability does not support comparing two fields. The comparison will be made using the functionality of the database.
The attempted query involved a full text search (FTS) indexed field, and the search term matched too many words in the FTS dictionary.
You cannot use the API call
The value for the license type option must be an integer code (0 = no license, 1 = fixed license, 2 = floating license, or 3 = restricted read license). The value you specified is not one of these values. Re-enter the command, and specify an appropriate value.
A full text related operation was requested, but full text indexing is not enabled.
A search was requested using the special form-based search field in the qualification. To use this feature, you need a current license of the specified type, and you must enable full text searching.
If full text user licenses are on the system, the server tries to load the specified library. If the full text search engine is installed, it is installed incorrectly. If the full text search engine is not installed, install it to activate the full text search feature. If you do not want to use the full text feature, remove the full text user licenses or ignore the error message.
Due to the field length change, the corresponding full text index is being rebuilt.
The AR System search service is not available, so the search was performed against the database. Contact your AR System administrator.
An error occurred when the server attempted to initialize for full text search and did not find the required configuration values for collection directory and configuration directory. Use the BMC Remedy AR System Administration: Server Information form to configure locations for the full text search collection and configuration directories.
The full text search plug-in is not responding. Check with your AR System administrator to verify the status of the plug-in server.
A full text indexing scan for changes was defined for the current form. The form does not have a Last Modified Time field that can support a scan for entries updated since the last scan. Therefore, each scan performed on this form completely re-indexes the form.
Investigate whether you can add support for a Last Modified Time field to the form to provide more efficient indexing.
The table field qualification is not compatible with multi-form search indexing, so the field cannot be selected for indexing. Create a shadow table field with a simpler qualification that can be used for multi-form search indexing.
An attempt was made to create a form with fields reserved for the existing multi-form search system form. You cannot create a form with multi-form search fields.
At least one field in the forms being searched is in the process of being indexed which may effect the search results. A multi-form search is being conducted against indexes that are in the process of a bulk field update. Results might vary depending on the completion status of the operation.
A search term is required to perform a multi-form search. Specify at least one search term.
The form lists contains no indexed fields on which to search. Specify forms that provide fields to be searched.
An attempt was made to use the multi-form search feature without a full text system license. Obtain a system license for full text search before attempting to use the multi-form search feature.
An attempt was made to perform an update operation on the AR System Multi-Form Search form. No type of update is allowed through this form.
An attempt was made to perform an unsupported retrieval operation on the AR System Multi-Form Search form. The retrieval operation name is appended. This type of retrieval is not allowed through this form.
An attempt was made to designate a non-character field as a multi-form search category field. Only character fields may be designated as multi-form search category fields.
An attempt was made to designate a non-public field as a multi-form search category or title field. Only public fields may be designated as multi-form search category or title fields.
An attempt was made to designate a non-indexed field as a weighted relevancy field on a form. Only indexed fields may be designated as weighted relevancy fields on a form.
An attempt was made to specify a multi-form search category name that is already in use for the current form. Specify a different name that is not already in use as a category name on the current form.
An attempt was made to establish full text search properties on the AR System Multi-Form Search form. Full text search properties are not allowed on the AR System Multi-Form Search form.
The system failed to connect to the network management platform. An associated error message contains details. Fix the problem (for example, run the network manager if the manager is not running), and rerun the daemon.