This documentation supports the 9.0 version of Remedy Action Request System.

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

Error messages 8800 to 8899

Number Description
8800 Error

The specified container owner name is incorrect.

This is likely caused by a programming error, for example, in an incorrect API program.

8801 Error

The value of the specified reference is empty.

This is likely caused by a programming error, for example, in an incorrect API program.

8802 Error

The label of the specified reference is empty.

This is likely caused by a programming error, for example, in an incorrect API program.

8803 Error

The description of the specified reference is empty.

This is likely caused by a programming error, for example, in an incorrect API program.

8804 Error

The specified container does not exist.

This is likely caused by a programming error, for example, in an incorrect API program. You might also see this if an Open Window active link action tries to open a form from a different server and a different application name.

8805 Error

You do not have access to the specified container.

You do not have permission to access this container. Contact your BMC Remedy AR System administrator for assistance.

8806 Error

The specified container is missing.

A parameter is required, but the value passed is either NULL or an empty string. Load this parameter with the name of the form you want to reference.

8807 Error Unable to open the specified container.
8809 Error

Illegal container type.

You tried to define a container owner object that is not a supported container type. Supported container types include:

  • ARCON_GUIDE
  • ARCON_FILTER_GUIDE
  • ARCON_APP
  • ARCON_PACK
  • ARCON_WEBSERVICE

Supported container owners are:

  • ARCONOWNER_NONE (container is globally owned)
  • ARCONOWNER_SCHEMA
8810 Error

The specified container already exists.

Enter a different name for the container.

8811 Error

No name was specified for the owning object.

No owner name was specified. Typically, this occurs when a definition file you try to import contains an error.

8812 Error

Container cannot be owned by this type of object.

This is likely caused by a programming error, for example, in an incorrect API program.

8814 Error No container ID for the container.
8815 Error Missing or invalid container definition file.
8816 Error

Illegal reference type.

This is likely caused by a programming error, for example, in an incorrect API program in which the reference list is invalid.

8817 Error

The value of the external reference has an invalid format.

This is likely caused by a programming error, for example, in an incorrect API program.

8818 Error

The container is not supported by the server.

This is likely caused by old server containers.

8819 Error Application owner does not match what's defined in the schema.
8821 Error

Computed Group Cannot have Overlay. Setting Overlay Group to Null.

Do not assign an overlay to a computed group. If you assign an overlay to a computed group, the ARERR 8821 error occurs and the computed group is saved with Overlay Group as NULL in the AR System server.

During an upgrade, if a Computed Group exists with an Overlay Group, it is ignored and considered as NULL by the AR System server.

8830 Note

Object cannot be locked.

One of more objects being exported cannot be locked. Object locking is not supported for DSO or flashboards objects. Contact Customer Support for assistance, if necessary.

8831 Warning

Locking level cannot be decreased.

A locked object can be exported only at the same lock level or a higher lock level. Contact Customer Support for assistance, if necessary.

8832 Error

Unknown object lock level specified.

Specify one of the following lock levels:

  • AR_LOCK_TYPE_NONE (0)
  • AR_LOCK_TYPE_READONLY (1)
  • AR_LOCK_TYPE_HIDDEN (2)

This error can be encountered only through an API program.

8833 Warning

Lock key cannot be changed, so the existing key will be kept.

A locked object can only be exported with the same lock key. Changing the lock key is not allowed.

8834 Error

Lock information mismatch.

Locking properties of the object do not match the locking properties of the lock group. The definition file is possibly corrupted. Contact Customer Support.

8835 Error

Unable to load object lock information into cache.

A system error occurred. Contact Customer Support.

8836 Error

Specified lock block cannot be found.

A noncritical error occurred in the server cache. Restart the BMC Remedy AR System server.

8837 Note

End of file reached.

An unexpected end of file occurred during file processing.

8838 Warning

No information is returned for the hidden locked object.

Information is not returned for hidden locked objects.

8839 Error

Cannot delete a locked object — must override to delete.

You cannot delete just this locked object. You must delete the group of objects that have the locked key. To delete all objects in the lock group, use the AR_LOCK_BLOCK_DELETE option. This error is encountered only through an API program.

8840 Warning

Attempt to modify a locked object — inappropriate changes are discarded.

You tried to modify an object that has a read-only lock, such as by adding a form to a read-only filter. You cannot modify a locked object.

8841 Error

Safeguard mismatch - potentially corrupted form.

A system error occurred. The object is possibly corrupted. The form might have been modified at the database level. Contact Customer Support.

8842 Error

Safeguard mismatch - potentially corrupted container.

A system error occurred. The object is possibly corrupted. The container, such as a guide, an application, or a packing list, might have been modified at the database level. Contact Customer Support.

8843 Error

Safeguard mismatch - potentially corrupted active link.

A system error occurred. The object is possibly corrupted. The active link might have been modified at the database level. Contact Customer Support.

8844 Error

Safeguard mismatch - potentially corrupted filter.

A system error occurred. The object is possibly corrupted. The filter might have been modified at the database level. Contact Customer Support.

8845 Error

Safeguard mismatch - potentially corrupted escalation.

A system error occurred. The object is possibly corrupted. The escalation might have been modified at the database level. Contact Customer Support.

8846 Error

Safeguard mismatch - potentially corrupted menu.

A system error occurred. The object is possibly corrupted. The menu might have been modified at the database level. Contact Customer Support.

8847 Error

Field creation not allowed on a locked form.

You cannot create fields on a locked form.

8848 Error

Field deletion not allowed on a locked form.

You cannot delete fields on a locked form.

8849 Warning

Setting object lock information is disallowed at this time.

During set or create operations, locked object properties are not expected. Export the object as locked.

8850 Error

A lock block must be exported entirely in xml or entirely in def format.

In a single export call, all objects must be exported in the same format, which can be .xml or .def.

8851 Warning

Setting BSM tag disallowed.

This action is for internal use only.

8852 Error

Server setting out of range.

Check server settings and make any necessary corrections.

8853 Error

Invalid locale info supplied.

This error occurs when you use the API to send initialized locale information in ARControlStruct. Review your program and make sure the correct ARControlStruct parameter is passed.

8854 Warning

Child entries are not processed.

An XML Service Entry does not support processing of multiple entries. If the input XML document holds multiple entries when executing an OpService web service operation, the XML Service Entry will process only the first entry, Child entries will not be considered. This warning indicates that the operation is successful but that the child entries are not considered.

8855 Error

Safeguard mismatch - potentially corrupted image.

A system error occurred. The object is possibly corrupted. The image might have been modified at the database level. Contact Customer Support.

8856 Error

An overlay and its corresponding overlaid object cannot belong to the same overlay group.

BMC Remedy AR System supports only one overlay group (group ID 1). All overlay and custom objects must belong to that group. Because of this limitation, you cannot create an overlay of an overlay or a custom object. The new overlay would have to be assigned to a different overlay group, but BMC Remedy AR System does not permit that. 

8857 Error

Creating overlay is not supported for the type of object specified.

You tried to create an overlay for a type of object that does not support overlays. Overlays can be created for active links, active link guides, escalations, filters, filter guides, forms, views, fields, images, local applications, menus, packing lists, and web services. Overlays cannot be created for custom objects, deployable applications, overlaid objects, and overlay objects.

Note: DSO mappings, DSO pools, flashboards, skins, and templates are stored as data in a form. They are not AR System objects. Therefore, you cannot use overlays to customize them.

8858 Error

__C and __O are system reserved suffix and cannot be added manually.

You tried to include one of the following strings in the name of an object:

  • __c (reserved for future use)
  • __o (reserved for overlay object names)

AR System automatically adds those strings to custom or overlay object names. You cannot manually add them to the names of other types of objects.

8859 Error

Invalid operation on overlay or overlaid object.

You tried to perform an operation that is not permitted on an overlay or overlaid object. In Best Practice Customization mode, AR System restricts the operations that can be performed on objects to ensure that you perform only changes that will be preserved during application upgrades. To perform the operation on an AR System origin object, switch to Base Development mode.

Note: Base Development mode gives you unrestricted access to create, modify, and delete AR System origin objects, such as out-of-the-box application objects, but your changes might not survive upgrades.

8860 Error

The Group ID for Overlay and custom objects can only be 0 (does not belong to an overlay group) or 1 (belongs to the overlay group).

The specified overlay group is not supported by the server. In release 7.6.04, BMC Remedy AR System supports only one overlay group, overlay (group ID 1), which is a predefined level 1 group. Therefore, all overlay and custom objects are automatically assigned to it. If an operation requires you to specify an overlay group, provide one of the following values:

  • 0 (does not belong to an overlay group)
  • 1 (belongs to the overlay group)

For information about specifying design time and runtime overlay groups, see the following variable descriptions for the ARSetSessionConfiguration function:

  • AR_SESS_CONTROL_PROP_DESIGN_OVERLAYGROUP
  • AR_SESS_CONTROL_PROP_API_OVERLAYGROUP
8861 Error

Base and overlay object should be of same type.

When converting an origin object to custom make sure that their types match. Otherwise, the ARCreateOverlayFromObject API call returns this error.

8863 Error

Before creating an overlay of a field or a form view, you must create an overlay of the object's associated form.

Before creating an overlay of a field or a view, you must create an overlay of the object's associated form.

8864 Error

Invalid value for overlay property.

You are not permitted to assign the value that you specified to the property of an overlay object. In Best Practice Customization mode, AR System restricts the values that can be assigned to properties to ensure that you perform only changes that will be preserved during application upgrades. To assign this property value to an AR System origin object, switch to Base Development mode.

Warning: Base Development mode gives you unrestricted access to create, modify, and delete AR System origin objects, such as out-of-the-box application objects, but your changes might not survive upgrades.

8865 Error

Field/View overlay and the associated base form overlay must be in the same overlay group.

You tried to assign a field or a view to a different overlay group from the group to which its associated overlay form belongs to. Field and views must belong to the same overlay group that their associated overlay form belongs to.

8866 Error

Audit/Archive form overlay and the associated base form overlay must be in the same overlay group.

You tried to assign an overlay audit or archive form to a different overlay group from the group to which the form's associated overlay origin form belongs. An overlay audit or archive form must belong to the same overlay group to which its overlaid origin form belongs.

8867 Error

Unable to find overlay for specified overlaid object.

When you make a change on an overlaid object that should reflect on its overlay, the AR System server searches for that overlay. If the overlay is not found, BMC Remedy AR System returns this error. The occurrence of this error indicates that form definitions in the database, the server cache, or both were corrupted.

8868 Error

Field overlay and the associated view overlay must be in the same overlay group.

You tried to assign an overlay field to a different overlay group from the group to which the field's associated overlay view belongs. An overlay field must belong to the same overlay group to which its overlay view belongs.

8869 Error

To convert custom field to overlay, field ID of custom and base must be the same.

The ARCreateOverlayFromObject API call returns this error when you try to convert custom fields to overlays. Make sure that the custom field's ID is the same as the field ID of the origin field that you want it to overlay.

Note: This operation is allowed only for special fields.

8870 Error

To convert custom field to overlay, custom form name and the base form name must be the same.

The ARCreateOverlayFromObject API call returns this error when you try to convert custom fields to overlays. Make sure that the name of custom form (that contains the field you want to overlay) matches that of the origin form.

Note: This operation is allowed only for special fields.

8871 Error

Field must be of custom type on given form.

To convert a field to overlay, it must be a custom field. If the Best Practice Conversion utility encounters a non-custom field to be converted to overlay, it returns this error.

8872 Error

Unable to find the overlaid object.

The AR System server returns this error if the overlaid object is not found in the following situations:

  • While loading overlay object information.
  • When overlay objects need access to overlaid objects.

This error indicates a problem with object definitions.

8873 Error

Renaming of overlay object is not allowed.

You cannot rename overlay objects. Instead, you can create a matching object with the new name in either of the following ways:

  • In Best Practice Customization mode, use the Save As command to make a copy of the overlay object and give the new custom object the name.
  • In Base Development mode, rename the corresponding overlaid object. AR System automatically updates the name of the overlay object to match the overlaid object's new name.
8874 Error

Object is not a valid custom object, hence cannot be converted to base.

BMC Remedy AR System allows only converting a custom object to an origin object. If the object you selected for conversion to origin is not a custom object, BMC Remedy Developer Studio displays this error. Select only a custom object to convert to origin.

8875 Error

Audit or archive form must be custom for the specified overlay form.

When enabling an overlay or custom form for auditing or archiving, if the audit or archive form that you specify already exists, it must be a custom form with the same overlay group. Otherwise, BMC Remedy Developer Studio displays this error. To proceed, specify a custom audit or archive form that belongs to the same overlay group, or specify a new form name.

8876 Error

The object is either custom or overlay object and converting it to custom or overlay in same overlay group is not allowed.

BMC Remedy AR System only allows converting an origin object, or an overlay or custom object of a different overlay group, to overlay or custom. If you select a non-origin object and try to convert it to an overlay or custom object with the same overlay group, BMC Remedy Developer Studio displays this error. To proceed, specify a different overlay group than that of the currently selected object. BMC Remedy AR System does not allow converting an overlay or custom object further to overlay or custom. If you select an overlay or custom object and try to convert it to overlay or custom, BMC Remedy Developer Studio displays this error. Select only an origin object to convert to overlay or custom.

8877 Error

No permission to access object in base mode.

If a user is configured to work only in the overlay mode, the user cannot modify the base object.

8878 Error

No permission to access object in overlay mode.

If a user is configured to work only in the base mode, the user cannot modify the overlay or custom object.

8879 Error Base object and custom object names are same. Conversion of custom to overlay is not allowed.
8887 Error

Data operations are not allowed in Full Mode.

If an API user is in full development mode, data operations are not allowed. The user needs to perform these operations either in Base Development mode or overlay mode.

Was this page helpful? Yes No Submitting... Thank you

Comments