This documentation applies to the 8.1 version of Remedy Action Request System, which is in "End of Version Support."

To view the latest version, select the version from the Product version menu.

Error messages 400 to 500

Number Description
400 Error

The file specified for a form does not hold a form definition.

The file that was expected to hold the definition of a form does not hold a form definition or is incorrectly formatted. The error is usually caused by a manual change to one or more BMC Remedy AR System database definition files. If you manually changed a file, the change is invalid. If you did not change a file, this is an unexpected error.

401 Error

Form definition in the source file is invalid.

The file contains a form definition, but it is not the expected form definition. The error is usually caused by a manual change to one or more BMC Remedy AR System database definition files. If you manually changed a file, the change is invalid.

402 Error

Incorrect format in the definition file.

A format error was detected in a definition file. This error is usually caused by a manual change to one or more BMC Remedy AR System database definition files. The error message contains the error. If you manually changed a file, the change is invalid.

403 Error

The form definition file field count does not match number of fields in the file.

The number of fields defined for the form does not match the count in the form header definition. This error is usually caused by a manual change to one or more of BMC Remedy AR System database definition files. If you manually changed a file, the change is invalid. If you did not change a file, this is an unexpected error.

404 Error

Field ID is in the core field range but is not a defined core field.

A field ID in the core range was found, but this is not one of the defined core fields. The ID is, therefore, an illegal ID and cannot be used.

405 Error

A core definition from the definition file is incorrect.

The definition of one of the core fields is inconsistent with the rules defined for that core field. This error is usually caused by a manual change to the form definition file. If the definition file was changed, the change is invalid.

406 Error

One of the core fields is missing from the form file definition.

The form definition being loaded is missing one or more of the required core fields. These fields must be present as part of the definition of the form. You may or may not use them, but they must be present. This error is usually caused by a manual change to the form definition file. If the definition file was changed, the change is invalid.

407 Error

Duplicate field/VUI ID in the form definition.

The form definition contains a duplicate definition for one or more fields. A field or VUI ID must be unique within a form. This error is usually caused by a manual change to the form definition file. If the definition file was changed, the change is invalid.

408 Error

Selection data type requires a selection specification.

All fields with a Selection data type must define a list of one or more values that define the selection for that field. A definition was found without that selection definition. This error is usually caused by a manual change to the definition. If the definition was changed, the change is invalid.

409 Error

No definition is in the file.

The structure file does not contain definitions. This error is usually caused by a manual deletion of the contents of a structure file. If the file was deleted, it must be restored from a backup.

410 Error

The filter definition cannot be found in the specified file.

A file specified as holding the definition of a filter does not contain a filter definition. This error is usually caused by a manual deletion of the contents of a structure file. If the file was deleted, it must be restored from a backup.

411 Error The command definition cannot be found in the specified file.
412 Error

The import file is in an incorrect format.

The import file contains data that is not part of a legal structure definition supported by BMC Remedy AR System. Remove the definition file of all lines that are not part of a legal definition, and then retry the import operation.

413 Error

The Active link definition cannot be found in the specified file.

A file specified as holding the definition of an active link does not contain the definition. This error is usually caused by a manual deletion of the contents of a structure file. If the file was deleted, it must be restored from a backup.

414 Error

The character menu definition cannot be found in the specified file.

A file specified as holding the definition of a character menu does not contain the definition. This error is usually caused by a manual deletion of the contents of a structure file. If the file was deleted, it must be restored from a backup.

415 Error

The escalation definition cannot be found in the specified file.

A file specified as holding the definition of an escalation does not contain the definition. This error is usually caused by a manual deletion of the contents of a structure file. If the file was deleted, it must be restored from a backup.

416 Error

The distributed mapping definition cannot be found in the specified file.

A file specified as holding the definition of a distributed mapping does not contain the definition. This error is usually caused by a manual deletion of the contents of a structure file. If the file was deleted, it must be restored from a backup.

417 Error

The group name is not a defined group.

The system was translating the contents of a group (for example, from the Group List [field ID 104], Assignee Group [field ID 112], or a dynamic field) from a text string into the internal format of a sequence of IDs. The operation was occurring during the processing of a filter or escalation. During the conversion, an error occurred. The likely cause of the failure is that the system encounters a name that is not a defined group.

418 Error

Incomplete join form definition.

During import, a form defined itself as a join form. However, one or more key pieces of information (such as the type of join or the primary or secondary form) are missing. The join form definition depends on complete information about the join, so it cannot be created.

419 Error

Incomplete view form definition.

During import, a form defined itself as a view form. However, one or more key pieces of information (such as the table being referenced) are missing. The view form definition depends on complete information about the view, so it cannot be created.

420 Error

Invalid field type.

With a join or view form, the field type specified in the field definition for a data field is not appropriate for that form type. For example, if the form is a join form, all data fields must be defined with a field type indicating that they are a join field because no base data fields exist when you are working with a join form.

421 Error

Incomplete field mapping definition.

The field mapping of this join or view form is not consistent with the type of the form.

422 Error

Unrecognized escalation action type.

The type of the action attached to the escalation is outside the allowed range of types.

423 Error

The container definition cannot be found in the specified file.

The file contains a container definition, but it is not the expected definition. Make sure that you did not change the name of the file prior to import.

424 Error

Push fields actions that affect entries in other forms can only affect forms on the same server in a filter/escalation.

In filters and escalations, you cannot use a Push Fields action to push values to forms residing on different servers. For more information about Push Fields actions, filters, and escalations, see Push Fields action.

429 Error

The VUI definition can not be found in the specified file.

The import file does not hold a view definition.

430 Error

Field ID exceeds the maximum allowed value.

The value supplied for the field identifier exceeds the maximum allowed value. Specify a value less than or equal to 2147483647.

431 Error

Field of this type cannot be included in a multi-column index.

A multi-column index was specified that includes a field type that is not allowed, such as a currency field. Remove any fields that are not allowed from the index specification

432 Error

Currency field has too many functional currencies to allow indexing.

A currency field selected for indexing has too many functional currencies to index each column without exceeding the index limit of 16. Do not index the field, or remove some functional currencies from the field definition.

433 Error

Not a lock block definition.

The definition file is invalid. It is possibly corrupted. Verify the validity of the export definition file and re-export it if necessary.

434 Error

An invalid or a corrupt lock block definition was skipped.

A portion of the definition file was skipped because it is invalid or corrupted. Verify the validity of the export definition file and re-export it if necessary.

435 Error

Administrative operations must be enabled before you can modify this server setting.

Administrative operations are disabled. Administrative operations must be enabled before you can modify this server setting.

436 Error

Invalid format for server information setting.

The input value for this server setting is invalid. Verify that the input value for this server setting is the correct type and is properly formatted.

437 Error

The form data definition cannot be found in the specified file.

The import file does not hold a form definition.

438 Error

Cache reload failure.

Indicates that a SQL error occurred during a certain stage of the AR System server initialization. After the server cache has been loaded, patches can be provided to correct database problems. This message indicates that an error occurred during the post-cache upgrade. Contact Customer Support.

439 Error

Error changing field column length; ensure no existing data in the field exceeds the requested length before retrying.

<form name > (<field id >) <old length > to <new field length >

For example;

Error changing field column length; ensure no existing data in the field exceeds the requested length before retrying (ARERR 439)

TestColLength (536870913) 25 to 35

Where:

TestColLength is the form name.

536870913 is the field id.

25 is the old length.

35 is the new length.

441 Error

Invalid array index, out of range.

The array index given to the AR System API is out of range for the specified array. Re-try the call with a proper index value.

442 Error

The required API input argument is empty.

Supply a value for the input argument to the AR System API.

444 Error Could not resolve the JNI class.
445 Error Could not resolve the JNI method.
446 Error

Changing the field option of the field is not allowed.

You tried to modify a field option, but this option cannot be modified.

447 Error

Server information associated with this tag has an invalid value.

The AR System server configuration setting for the specified tag includes a value that is outside the range of valid values or that is NULL for a non-NULL configuration. The error message provides information about the valid values. Fix the invalid value in the AR System Administration: Server Information form (recommended) or in the server configuration file, and then retry the operation.

448 Error

File size limit exceeded.

The maximum log file size of 2GB was reached for the specified log file. Reset the log file before reaching the limit or configure the log file to be circular.

450 Warning

Cannot find the report definition file.

The operation will continue without the file identified. When creating or updating an active link, a macro action or else definition contains a reference to a report file that does not exist. The active link is created or updated without the file. If it is replayed, the user receives a warning about the missing file. Locate the expected file, and put it in the proper location; then, reselect the macro in the action, and update the active link definition to have the file included in the active link.

451 Warning

Report definition file failed to load into server. The operation will continue without this file.

While trying to read a report file referenced in a macro definition embedded in the active link definition being created or modified, the system encountered an error, and the report file was not retrieved. The operation continues without the report file. The file is not saved as part of the definition.

452 Note

Could not find or read the optional license tags file.

BMC Remedy AR System cannot locate the arsystem.tag file. This file is used by applications to manage application licensing requirements. The tags file may not be present if no application has installed it.

460 Error

Audit Configuration information cannot be found in the ar.conf/ar.cfg file.

Application auditing was enabled, and the system tried to load configuration information for the application auditing but could not locate it in the configuration file. Contact Customer Support.

461 Error

The AR Server version does not match the Lite license AR Server version included with the licensed application.

BMC Remedy AR System on the server containing the application was updated to a different version. The licensed application is supported only on the version of BMC Remedy AR System included with the application. Install the BMC Remedy AR System included with the licensed application.

462 Error

The form is not a member of a Lite licensed application.

A form was added to a licensed application that does not support added forms. You cannot add forms to this application.

463 Error

Cannot create a form in a Lite licensed AR Server.

You tried to create a form on a BMC Remedy AR System server that was installed with an application that does not support added forms. You cannot add forms on this BMC Remedy AR System server.

464 Error

Cannot change the form name in a Lite licensed AR Server.

You tried to change the name of a form on an BMC Remedy AR System server that was installed with an application that does not support changing the names of forms. You cannot change the name of a form on this BMC Remedy AR System server.

465 Error

Cannot change the form mapping criteria in a Lite licensed AR Server.

You cannot change the join criteria of a join form or the properties of a join, vendor, or view form on this BMC Remedy AR System server.

466 Error

Invalid or pre 6.0 AR Server license file.

The license file is corrupted, formatted incorrectly, or from a version of BMC Remedy AR System prior to 6.0. Do not edit the license file. Contact Customer Support.

467 Error

AR Server license import option can only be 0 or 1.

Specify 0 or 1 for the license import option. For more information, see the C API Reference .

468 Error

Error reading license cache table.

An error occurred in loading data from the license_cache table in the AR System database.

469 Warning

Warning, this key is not valid for this server.

This warning indicates that the entered key is not valid for the AR System server on which it was entered. If the server is in a server group, the key might be valid for one of the other servers in the group. In that case, ignore the warning. If this warning appears on a single server, a problem exists with the license entry. Check the fields of the key for leading or trailing spaces, and make sure that the correct Host ID was used when the key was generated.

470 Error

User Cache utilities are disabled.

The arcache utility was run on an AR System server that is configured to disallow the arcache utility.

474 Warning

No licenses in supplied file.

Indicates that the file supplied during an ARImportLicense() API call does not contain valid licenses. Supply the correct file name.

475 Error

Too few arguments specified for upgrade program.

The program that upgrades the database structure to the current structure requires more arguments than you specified. The upgrade program is run automatically as part of the installation operation. You need not run this program.

476 Error

Too many arguments specified for upgrade program.

The program that upgrades the database structure to the current structure requires fewer arguments than you specified. The upgrade program is run automatically as part of the installation operation. You need not run this program.

477 Error

Oracle 8.0 is no longer supported by upgrade.

The program that updates the database structure to the current structure no longer supports version 8.0 of the Oracle® database. Upgrade to Oracle 8i or higher.

478 Error

This 6.3 Unicode database is not yet ready for upgrade. Please contact Customer Service for details on how to prepare your database before attempting an upgrade to a 7.0 Unicode database.

When upgrading an AR System 6.3 Unicode server to an AR System 7.0 or later Unicode server, you must first run a utility that prepares the database for this upgrade. If the utility has not been run, the installer generates this error.

479 Warning

The temporary column control.unicode63handled, created for upgrading the 6.3 Unicode database to a 7.0 database, could not be deleted. Please delete this column manually.

When upgrading a previous installation to AR System 7.0 or later, the installer creates temporary tables to allow it to move and transform data types. After this data move is completed, the installer attempts to delete these columns. If the delete fails, this error is generated.

480 Error

Status History field is not supported on View forms.

You cannot create a Status History field on a view form.

481 Error

Requested database table not found. Please check the spelling (table name is case-sensitive).

The correct column information (for example, the right number of columns) for the external schema was not retrieved.

482 Error

This View Form contains empty Request IDs. Ensure that the key field is set to a non-null, unique column to avoid data corruption.

You cannot search the database for the entry ID in a view form if its value is NULL.

483 Note

Please restart the AR System Server for the changes to take effect.

Restart AR System.

485 Error

The reservedIdOKList parameter in the ARCreateMultipleFields() API function is blank. This parameter must be either "Yes" or "No" or "1" or "0".

The reservedIdOKList parameter in the ARCreateMultipleFields() API function was supplied as a null pointer. This parameter must be supplied with a pointer to an ARBooleanList.

486 Error

The list parameter does not have the same item count as in the Field ID list.

A list parameter supplied in an ARCreateMultipleFields() or ARSetMultipleFields() API call does not have the same number of elements as the fieldIdList parameter. All list parameters that are supplied must have the same number of elements.

487 Error Set field status list cannot be empty. The setFieldStatusList parameter in the ARSetMultipleFields() API function was supplied as a null pointer. This parameter must be supplied with a pointer to an ARStatusListList.
488 Error

Field creation error occurred at the indicated list position.

An error occurred during one of the individual field creations for an ARCreateMultipleFields() API call. The specific error is reported as an item in the status list. This error supplies appended text containing the zero based list position of the field the error occurred on. For example, if the appended text is 2, the error occurred on the third field in the field list.

489 Error

At least one set field failed in a multi-field operation.

At least one error occurred during the operation of the ARSetMultipleFields() API call. If this error is returned, the setFieldStatusList parameter supplies the details of the individual field failures.

490 Error

Invalid preference server option, out of range.

Check preference server settings and make any necessary corrections.

500 Error

Failure while trying to open the flat file database data file.

Check the Server-directory setting.

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Comments