This documentation supports the 20.02 version of Remedy Action Request (AR) System.

To view an earlier version, select the version from the Product version menu.


Error messages 5201 to 5391

Oops, it seems that you need to place a table or a macro generating a table within the Table Filter macro.

The table is being loaded. Please wait for a bit ...

NumberDescription
5201 Error

The label <guideLabel> is already being used in the guide. The label must be unique.

Labels in guides must be unique. Rename the label, providing a name that has not yet been used in the guide.

5202 ErrorNo primary field is defined for form <formName>.
5203 Error

Specified primary field ID does not exist on the form <formName>.

Specified primary field ID does not exist on the form.

5204 Error

Unable to locate form <formName>.

The form does not exist on the AR System server.

5205 Error

Unable to locate field <fieldName> on form <formName>.

The listed field could not be found on the listed form. It might have been deleted from the form.

5206 Error

The parent form is missing from the web services field map for <fieldName>.

The parent form is missing from the web services field map for fieldName.

5207 Error

The Change Field menu <menuName> is empty or invalid.

The Change Field menu is empty or invalid.

5208 ErrorMinutes value must be between 0-59.
5209 ErrorMissing hour information. Hours must be specified.
5210 ErrorMissing weekday information. A weekday or day in the month must be specified.
5211 Error

The escalation time interval cannot be 0.

The escalation time interval is set to 0.

5212 Error

With the Escalation Time Execution option, Run By = Time, and Time is not entered.

With the Escalation Time Execution option, Run By = Time, and Time is not entered.

5213 Error

The Cross-Reference Action in the Notify filter must have a reference field specified.

When creating a Notify filter action, you did not select the reference field required when the notification Mechanism is Cross-Reference. To continue, select a reference field.

5214 ErrorThe Selected Fields option must have a field specified.
5215 Error

SQL Set Fields action must have a SQL command specified.

To save a SQL Set Fields action, specify a SQL command. This is not validated but cannot be left blank. To continue, enter a SQL command.

5216 ErrorUnable to convert the operations XML document.
5217 Error

Unable to convert the input mapping XML document.

The mapping XML might be corrupted.

5218 Error

Unable to convert the output mapping XML document.

The mapping XML might be corrupted.

5219 ErrorUnable to parse the XML document. <errorNumber>.
5220 Error

Workflow must have at least one IF action.

No If actions are defined for the filter, escalation, or active link. Specify at least one If action.

5221 Error

<fieldType> Field <fieldName> has a minimum width greater than the maximum width.

A composite field embedded in another composite field with the Fill layout has a Minimum Width and a Maximum Width property. The Minimum Width value should not be greater than the Maximum Width value. Specify a minimum width that is less than or equal to the maximum width.

5222 Error

<fieldType> Field <fieldName> has a minimum height greater than the maximum height.

A composite field embedded in another composite field with the Fill layout has a Minimum Height and a Maximum Height property. The Minimum Height value should not be greater than the Maximum Height value. Specify a minimum height that is less than or equal to the maximum height.

5223 Note

BMC Remedy Action Request System is ready for use or evaluation without purchasing or activating an authorization key. For unlimited capabilities, contact your sales representative or visit www.bmc.com. Server: <serverName>.

This version of BMC Remedy AR System has a maximum limit of 2000 requests per database table, includes a maximum of three fixed licenses, and is configured for each client to access a maximum of one server. To obtain a version of AR System without these limitations, contact your BMC sales representative or an authorized reseller, or visit http://www.bmc.com.

5224 Error

Forms cannot be moved from <serverNameA> to <serverNameB>.

An attempt was made to drag a form from AR System server A to an application on AR System server B. This is not allowed.

5225 ErrorForm already exists on <applicationName> application.
5226 Error

The field type <fieldType> of Field <fieldName> does not match the field type of the base field.

A table column field is mapped to a remote field of a different type. For example, a column field with a type of char is using a remote button field.

5227 ErrorCreating field is not allowed in Tab Order Increment on Click mode.
5228 Error

<fieldType fieldType> contains an invalid form name. Provide a correct remote form name.

The remote form name is empty, or the specified form does not exist on the AR System server.

5229 Error

<fieldType fieldName> is linked to an unreachable AR System server <serverName>.

A network connection cannot be established to the BMC Remedy AR System server. For troubleshooting steps, see error message 90.

5230 Warning

Selecting the override loop option could cause an infinite loop in the system.

By shutting down loop protection, you run the risk of creating infinite loops and overwriting the original record in a distributed transfer operation or a distributed return operation. Save the filter or escalation only if you are understand the risk in what you are doing.

5231 Warning<filePath> does not exist. The Log to File action will create the file.
5232 WarningZ order for <fieldType> field <fieldName> has been modified to fix duplicate Z order.
5233 ErrorCore fields: <fieldNames> can not be deleted.
5234 ErrorYou cannot move a panel to its current parent.
5235 ErrorData fields cannot be added to audit forms.
5236 WarningZ order for <fieldType> field <fieldName> has been modified to make it consecutive with other fields.
5237 Error{0} with this name {1} already exists. Choose a new name.
5238 Error

target field <fieldName> cannot be empty.

Set Field actions and Service action assignments need an assignment value for each field added in mapping.

5239 Error

Port not defined for operation: <operationName>.

WSDL operation in a web service is missing a port.

5240 Error

Operation names must be unique. There is a duplicate operation: <operationName> in the Operations List.

You created a duplicate operation name in the Operations List. Operation names must be unique.

5241 Error

Invalid operation name operationName conflicts with output top level parent name for operation: <operationName>.

Internal operations are saved with the suffix Response. Therefore, avoid using Response as a suffix in the name of an operation. For example, this error occurs if an operation named WSDLNameResponse is used when an operation named WSDLName already exists.

5242 ErrorLabel <label> cannot be empty. Specify a label name.
5243 Error

Duplicate file names were found in the current directory. The duplicate files were not added.

The file name being added already exists in the current directory.

5244 ErrorVendor form table <tableName> does not have any available columns.
5245 Error

The web service Publishing Location must end with the web service name.

The web service location must end with the web service name.

5246 Error

The web service Publishing Location must be a non-empty string.

The web service location must be a non-empty string.

5247 NoteInvalid Web Services Publishing Location has been updated with correct name.
5248 ErrorFollowing Column fields for <tableFieldType tableFieldName> do not have referenced fields <columnFieldNames> on the current form. Press OK to delete.
5249 Error

The view <viewName> specified in the active link <activeLinkName> does not exist on Form <formName>.

When you created an Open Window action, the form view that you selected was not found on the AR System server. Accordingly, the view used in the action is the default administrator view. To verify that the view you want to use exists, open the form in BMC Remedy Developer Studio.

5250 ErrorExporting flashboard objects in XML is not supported. Selected flashboard objects will not be exported.
5251 ErrorYour changes cannot be saved because <objectName> is reserved by user <userName>.
5252 Error

Unable to display image. It does not appear to be a supported image format.

The image cannot be displayed. Valid file types for images are BMP, DIB, GIF, JPEG, JPG, and PNG.

5253 Error

Unable to display background image. It does not appear to be a supported image format.

The background image cannot be displayed. Valid file types for images are BMP, DIB, GIF, JPEG, JPG, and PNG.

5254 Warning

Changing the form might make existing actions invalid. Check existing actions.

When modifying an active link or filter, you changed which form controls the active link or filter. Active links and filters can be attached to multiple forms. Verify your actions after you change the form in an active link or filter.

5255 Error

Cannot add a submenu because a menu in a character menu cannot have more than 99 submenus.

The character menu definition contains too many items on one level of the menu tree. AR System allows a maximum of 99 items on a menu level. Use multilevel menus to split large menus into multiple smaller and more manageable menus.

5256 NoteNo allowable currency type has been specified. All currency types are now allowed.
5257 ErrorCannot connect to server: serverName because its version is version. Only servers that are 7.0 or later versions are supported.
5258 WarningSearch was aborted by the user. The results list might not be complete.
5259 Warning

Search did not match any objects.

When the system searched for an object, no results were returned. Objects might have been deleted, or their names might have been modified. Deleted objects do not appear even if the database is not synchronized.

5260 ErrorWeb Services Publishing location contains 'public' within the URL, but permissions have not been set to public for <webServiceName>.
5261 Error

A panel or a page cannot be moved to its child page holder.

A panel or a page cannot be moved to its child page holder.

5262 ErrorError connecting to BMC Atrium Orchestrator server. Reason: <errorNumber>.
5263 Error

Closing current editor due to resource error. <errorNumber>.

This is an internal error.

5264 Error

You cannot add a method here. The type is incompatible.

When you nest a method, the parent method's return must be one of the following types: IDispatch, VARIANT, or Compatible. If it is not one of these types, this error is returned.

5265 Error

A valid Web Services Port has not been selected.

Select a valid web services port.

5266 Error

A valid Web Services Operation has not been selected.

Select a valid web services operation.

5267 Error

A valid Operation has not been selected.

Select a valid operation.

5268 Error

A valid Configuration Name has not been selected.

Select a valid configuration name.

5269 Error

A valid Process has not been selected.

Select a valid process name.

5270 Error

A valid Web Services File has not been selected.

Select a valid web services file.

5271 Error

Column <columnName> used by Field <fieldName> is already referenced by another field.

In the View form, <columnName> in the Column property of <fieldName> is already used in another field. Use another available <columnName>.

5272 ErrorUnable to add an active link without primary form. Select a primary form.
5273 WarningLayout style for panel <panelLabel> is changed from XY to Fill.
5274 Error

An integer field is needed on the primary form for this operation.

An Execution Order From Field Value option cannot be used in a Goto action if the primary form does not have an integer field. Add an integer field to the primary form.

5275 Error

The configuration name <name> does not exist in the AR System Orchestrator Configuration form.

The entry might have been deleted from the form.

5276 Error

<fieldType> Field <fieldName> cannot refer to Column <databaseColumnName> of type databaseColumnType.

The <fieldType> must match the <databaseColumnType>.

5277 Error

The named menu <menuName> referenced by <fieldName> is not found.

The menu might have been deleted.

5278 ErrorOutput Mapping to a static value is not allowed for mapping item <value>.
5279 ErrorErrors were encountered while accessing the file: <fileName>.
5280 Error

Cannot create new object because application <applicationName> is reserved by another user <user>.

Object reservation is in use on the server, and you tried to create an object in an application reserved by another user. Wait until the reserved application is released. Alternatively, create the object outside the application by using the All Objects node in the BMC Remedy AR System Navigator. Add the object to the application when the application is no longer reserved.

5281 Error

You cannot create an Attachment Pool field in a view form.

You cannot create an Attachment Pool field in a view form.

5282 ErrorFilter cannot be added without a primary form. Select one primary form.
5283 ErrorSome Columns do not have matching Data Field in the Form: formName. They will be deleted. Press OK to delete.
5284 ErrorThe file <fileName> has an unsupported file extension. The supported extensions are .ARX, .CSV, .REP or .XML.
5285 Error

Number of selection values listed in this dialog box does not match the number of selection values in field ID <fieldID> on form ID <formID>.

Make sure the number of images and alternative texts correspond to the correct selection values.

5286 ErrorImage <imageName> is missing from the server. Select a different image in column columnName.
5287 ErrorImage imageName in column <columnName> exceeds the maximum recommended size (32 x 32 pixels).
5288 ErrorImages in column <columnName> are different sizes. To make the table more readable, select images that are the same size.
5289 ErrorPlease enter a valid Label Name.
5290 ErrorThe field <fieldName> referred in Table Field <fieldName> cannot be found on the base form <formName>. Save this form to fix this issue.
5291 ErrorNo Mid Tier information is provided for AR System server : <serverName>. Enter Mid Tier Information in the Preferences.
5292 ErrorError displaying preview for form : <formName>.
5293 Error

Right-aligned field has negative X value: <fieldName>.

When the Layout Style property of a form or panel is set to XY and a field's Alignment property is set to Right, the field's X property, which specifies the number of pixels between the field and the right side of the form or panel, must be a positive integer.

5294 ErrorCannot create label <labelName>.
5295 ErrorCannot edit label <labelName>.
5296 Warning

Label <labelName> created successfully. <number> objects labeled. Any objects that do not have a baseline were not labeled.

If an object does not have at least one entry ("a baseline") in the BMC Remedy AR System Version Control: Object Modification Log form, BMC Remedy AR System cannot add a version control label to it. To add an entry for an object to that form, enable the object modification log and then create, modify, delete, or import the object. For more information, see Version control in BMC Remedy AR System

5297 ErrorError in retrieving objects for label <labelName>.
5298 ErrorBecause <fieldName> Field <fieldID> uses the advanced rich text property, the field must contain at least 10 rows.
5299 ErrorBecause <fieldName> Field <fieldID> uses the advanced rich text property, the field must have at least 500 pt width.
5300 Warning

Label name cannot be blank.

The item has both a label name and a label description. You specified the label description, but you did not specify the label name. If you specify the description, also specify the name.

5301 ErrorTask name cannot be blank.
5302 ErrorFile name already exists. Choose a new name.
5303 ErrorNo definition (.def) files for the specified objects are attached to the object modification log. In the Version Control tab on the AR System Administration: Server Information form, verify that the Save Definition Files option is selected.
5304 ErrorThere are no Attachment Pool Fields available for selection. Create a new one.
5305 ErrorAttachment pool field <fieldName> for the Rich Text field <fieldName> was deleted.
5306 ErrorAttachment pool field <fieldName> for the Rich Text field <fieldName> should not be visible.
5307 NoteObjects exported successfully.
5308 ErrorThe object is not reserved or is reserved by another user. Save As with same name is not allowed.
5309 WarningGroup having ID: <groupID> does not exist on the server. This group has been removed from the permission list.
5310 ErrorApplication <applicationName>, specified for Integration Workflow property, does not exists.
5311 NoteZ order for <fieldName> field <fieldID> has been modified to set it within acceptable limits.
5312 Error 5317 Error

<nameOfOperation> operation not allowed on specified object. <reasonOperationIsNotAllowed>.

The change that you tried to perform is not permitted in Best Practice Customization mode because it might not be preserved if the application is upgraded.

5318 Error

Fields on View <nameOfView> has invalid Z order. Overlay of View required to modify it.

When a form is opened in BMC Remedy Developer Studio, corrupt display properties (such as incorrect Z-order, missing menus, and missing labels) are typically fixed. In Best Practice Customization mode, however, such errors in non-overlay form views are not fixed.

Instead, you must create an overlay of the form view that contains the invalid Z-order and then fix the Z-order in that overlay.

5319 Error

Field <nameOfField> has missing layout information. Overlay of View required to modify it.

When a form is opened in BMC Remedy Developer Studio, corrupt display properties (such as incorrect Z-order, missing menus, and missing labels) are typically fixed. In Best Practice Customization mode, however, such errors in non-overlay form views are not fixed.

Instead, you must create an overlay of the form view that contains the specified field and then add the missing information to that overlay.

5321 Error

View <nameOfView> has no label. Overlay of View required to modify it.

When a form is opened in BMC Remedy Developer Studio, corrupt display properties (such as incorrect Z-order, missing menus, and missing labels) are typically fixed. In Best Practice Customization mode, however, such errors in non-overlay form views are not fixed.

Instead, you must create an overlay of the form view whose label is missing and then add a label to that overlay.

5322 Error

Can not use Form <nameOfForm> as remote form because it does not contain fields referred by columns or cell fields in the overlaid form.

In an overlay of a list view, tree view, or cell-based table field, you cannot remove the columns or fields in a cell that exist in the overlaid form, but you can add columns or cell fields. The new columns or cell fields do not have to come from the same form that the columns or cell fields in the overlaid table came from (that is, you can specify a new remote form in the Tree/Table Property or Remote/Local Fields dialog box). But the new remote form must contain fields whose IDs match the field IDs of all the existing columns or cell fields in the overlaid table.

The new remote form that you specified does not contain fields whose IDs match the field IDs of all the existing columns or cell fields in the overlaid table. Specify a remote form that does contain the required IDs.

5323 Error

Creating new object is not allowed in Best Practice Customization Mode since AR System Server version is less than 7.6.04. Please use Base Development Mode to create new objects.

To create objects in Best Practice Customization mode, you must first install AR System server 7.6.04 or later. To create objects in your current system, switch to Base Development mode.

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

5324 Error

Creating <objectType> is not allowed in Best Practice Customization Mode. Please use Full Development Mode to create new <objectType>.

You cannot create the specified type of object in Best Practice Customization mode. To create that type of object, you must switch to Base Development mode.

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

5327 Error

Only custom fields can be added from a base form to an Overlay join form.

You cannot add an origin field from a primary or secondary form to an overlay join form. You can add only custom fields from the primary or secondary form to the overlay join form.

To create custom fields on the primary and secondary forms, you must create an overlay of those forms in Best Practice Customization mode and then add the custom fields to the overlay.

5328 Error

The objectType ' <objectName> ' has an open editor. Overlay cannot be created for objects that are currently opened in editor.

BMC Remedy AR System does not allow you to create an overlay of an object that is open in the editor. Close the relevant editor (save your changes if necessary) and then create the overlay.

5331 Error

Cannot switch to Base Development mode. You are part of the Overlay group on one or more of servers that you are logged into.

5347 Error
Invalid Archive to Form value.<archiveFormName>

This error occurs when you create an Archive form and change the form’s properties without naming the form. To avoid such errors, save the archive form and give appropriate name to the form before changing the properties.

5354 Error

<Property name> can not be empty.

The specified property of an association cannot be empty.
5355 Error

PKFK Field mapping: Empty mapping field for field <fieldName>.

Mapping for the specified field is empty.
5356 Error

Forms under Association to Follow For Archive section will not be archived because they have no archive definition.

5357 Error

<objectType> <objectType> does not exist on server <serverName>.

Object of the specified server does not exist on the server . You cannot reconcile it.
5358 Error

Old Definition source server is not specified in Settings.

5359 Error

Old Definition source server is not connected. Please login to server <serverName>.

Old Definition source server is not connected. Please log in to server.
5360 Error

Differences List for <objectName> is already open. If you want to view the updated list for reconciliation, close and reopen it.

Differences List is already open. If you want to view the updated list for reconciliation, close and reopen it.
5361 Error

Cannot reconcile because overlay of the object is deleted from the server.

5375 Error

The duration for keeping data for a Flashboard variable before it expires must be an Integer.

The expiry schedule for collecting data in a Flashboards variable when one of the expiry options is chosen was incompletely specified. The amount to keep data before it expires must be an Integer.

5376 ErrorPie charts cannot be selected for History or Summary display type.
5377 ErrorGroup access is not defined — only an administrator has access to this flashboard.
5378 ErrorGroup access is not defined — only an administrator has access to this variable.
5379 Error

The threshold value must be greater than zero.

Specify a value that is greater than zero for the threshold value.

5380 Error

The threshold value must be a non-negative integer.

Specify a non-negative integer for the threshold value.

5381 Error

Specified alarm variable does not exist on the AR System for the alarm to monitor.

Specify a variable that exists on the AR System server for the alarm to monitor.

5382 Error

Specified alarm name does not exist on the AR System for the alarm to monitor.

Specify an alarm name that exists on the AR System server.

5384 Error

The alarm cannot be saved. Correct the following errors.

See the following messages for the errors to correct.

5385 Error

The alarm variable was not specified, or the specified variable name is invalid.

Specify a variable that exists on the AR System server for the alarm to monitor.

5389 Error

The specified alarm trigger cannot be found.

Specify a trigger that exists on the AR System server for the alarm.

5390 Error

A user and a message must be specified for the alarm notification.

Specify a user and a message for the alarm notification.

5391 ErrorVariable <variableName> does not exist. It will be removed from Variables in next save.


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

Comments