List of all BMC Remedy ARS errors

All BMC Remedy AR Server messages with detailed description and developers comments.

All message types:

Selected Auto Dataset is not among the ones selected for this activity

Master Dataset must be specified if AutoDataset is specified for an Activity.

"If you specify a value for Auto Dataset, then you have to specify value for Master Dataset as well."

Please enter a value for Next Job Name.

"Please enter a value for Next Dataset Name."

Please enter values for Dataset1 and Dataset2.

"Please enter values for Dataset1 and Dataset2."

"Please enter all required fields."

Activity Type must be specified for an Activity.

Activity Status must be specified for an Activity.

Activity Sequence must be specified for an Activity.

On Error Continue cannot be empty for an Activity.

Namespace must be specified for an Activity.

Activity Name must be specified for an Activity.

Force Attribute Merge cannot be empty for an Activity.

Explicit Flag cannot be empty for an Activity.

Skip Auto-Identify of Master cannot be empty for an Activity.

Algorithm cannot be empty for an Activity

"Pick a valid Class Name"

"Please choose a Namespace and Class Name"

"Please choose a Namespace."

"Please choose instances that belong to two different Datasets."

"Please choose instances that belong to two different Datasets."

You must provide an Activity Name before selecting Namespaces.

You must provide a Group Name before selecting Namespaces.

The value(s) for the Dataset ID, Dataset Name is not unique.

"Dataset is required for an Merge Precedence Set".

"Merge Precedence Set is required for an Merge Precedence Set".

"Order is required for an Merge Precedence Set".

Name must be specified.

You must specify a Dataset MRG Precedence value for Merge Activities

You must specify a Dataset MRG Precedence value for Merge Activities

Namespace must be specified before adding identify rules.

Job Name must be specified for a Job.

Dataset Name must be specified for a Job.

Group Type must be specified.

Please enter value for Target Dataset

"Please give values to all required fields."

"Please give values to all required fields."

Specify values for the required fields: Product Categorization Tier 1, Product Categorization Tier 2, Product Categorization Tier 3, Product Name, Manufacturer, Suite Definition, Origin, Status-PDC, and Product Type.

Please do enter the Mandatory fields 'Product Model/Version', 'Requires Contract' and 'Model/Version State'.

Specify a value for the required field: Patch Last Build ID.

The Signature ID $420000012$ you specified does not exist.

The Company $1000000001$ you specified does not exist.

A Product with a Product Catalog Key of $420000006$ has been created.

The combination of Approved Flag and Blacklisted Flag values you specified is invalid.

Record saved successfully.

The Patch and Company association has been created.

The Version and Company association has been created.

Select a Company value.

The associated Versions for the product $240001002$ and company $1000000001$ are also set with Hide = $420000019$.

The associated Versions for the product $240001002$ and company $1000000001$ are also set with Blacklisted = $420000112$.

The associated Versions for the product $240001002$ and company $1000000001$ are also set with Approved = $420000109$.

Specify values for the required fields: ProductKey and SignatureId.

Specify values for the required fields: Logical Data Group, Version, and Attachment.

Select the Product or Model Version to delete

Select the Product, Model Version, or Patch to delete.

Select a Product Catalog View.

The combination of Selection Type, Selection Code, and Locale values already exists. Please select different values for these fields.

You have not selected any product. Select the product for which you want to perform the action and click Perform.

You have not selected any version. Select the version for which you want to perform the action and click Perform.

You have selected multiple products. Select only one product and click View.

You have not selected any product. Select the product for which you want to view the details and click View.

You have selected multiple versions. Select only one version and click View.

You have not selected any version. Select the version for which you want to view the details and click View.

You have not selected any Action. Select the action from Select Action drop down and then click Perform.

Specify values for the required Version status flags.

Specify values for the required Patch status flags.

Specify a value for the required field Product Type.

The Signature $420000012$ has been saved.

This Model/Version already exists. Please verify the following field values and try again: Product Model/Version, Operating System, Platform, VersionMajor, Version Minor, Version Maintenance and Version Build.

This record already exists for company $1000000001$. Please verify or reselect your field entries and try again

The combination of SignatureID, Logical Data Group, and Version you specified already exists. Please select different values for these fields.

Also setting Normalized flag = $420000110$ for the associated versions of product $240001002$ and company $1000000001$.

Setting Life cycle status flag = $420000138$ for the associated versions of product $240001002$ and company $1000000001$.

Also setting Managed flag = $420000111$ for the associated versions of product $240001002$ and company $1000000001$.

The signature $420000012$ is associated with the Product Key $301316700$. You must delete the corresponding product association from Signature Product Association before you delete the signature.

Duplicate File entries for same product and version not allowed

You need to be a part of Atrium Foundation Admin group to create a product entry.

Product $420000518$ has been created as Alias of Existing Product $420000573$ successfully.

Manufacturer $420000519$ has been created as Alias of Existing Manufacturer $420000574$ successfully.

Manufacturer $420000517$ has been successfully added as Alias of $240001003$ to Normalization Alias form

Product $420000516$ has been successfully added as Alias of $240001002$ to Normalization Alias form

The product $240001002$ has been successfully updated.

Alias $420000616$ of manufacturer $420000619$ has been successfully created

Alias $420000616$ of product $420000618$ has been successfully created.

AliasName is required field

Product having status "Enabled" cannot be deleted. Only Offline products can be deleted

Offline product cannot be made Alias of another product.

An entry with the product name does not exists. Please create an alias of existing product.

An entry with the manufacturer name does not exists. Please enter a different manufacturer name.

Alias $420000616$ successfully updated

User $420000656$ does not have permissions for company $301389298$

Cannot create alias of same product name $420000618$.

Cannot create alias of same manufacturer name $420000619$.

Cannot associate same alias to multiple products.

Cannot associate same alias to multiple manufacturers.

Product type $420000649$ of "$420000518$" does not match Product Type $420000553$ of selected product "$420000548$"

User $420000656$ does not have permissions for company $420000202$

Discovered product - $420000518$ will be made an alias of product - $420000548$ .

Discovered manufacturer $420000519$ will be made an alias of manufacturer - $420000549$ .

Please select the Person entry to delete in the People table, then click on the [Delete] button again.

Please select a People Relationship entry in the table above and an Relationship Action, from the menu provided, to perform on the selected entry. Thenclick on the [Execute] button again.

$10007399$ has been made an Associate Member of the Support Group.

You cannot create a Weak Reference with that Cardinality

You must provide ID Values for a Custom Selection

Invalid field ID. Field ID is too large.

Please specify Data Type.

Please specify Data Type.

Please specify Data Type.

Please specify Data Type.

'Namespace' and 'Class Name' must be entered before you can add/search attributes.

There is already an existing class with class name '$490001100$' in the namespace '$400109900$'. Please specifiy a different class name.

Invalid superclass. Class '$400103900$' is a final class and cannot be used as a superclass.

Namespace and Class Name are required fields. Please fill in a value before saving.

Class 1, Class 2, Role 1, Role 2 and Cardinality are required fields for relationship classes. Please fill in these values before saving.

Please fill in the Class Type field.

This attribute is already part of the Index.

Please enter the Index Name first.

There is already an index by the name of: $400111200$. Please use a different name.

Duplicate Field ID '$400004800$' for attribute '$400009700$'.

Data Type and Attribute Name must be specified.

Invalid Field ID for attribute '$400009700$'. Field IDs below 100 are reserved for Core fields.

Invalid Default Value for selection field.

There is already an existing class with class name '$490001100$' in the namespace '$400109900$'. Please specify a different class name.

This is an invalid combination of the Abstract and Final field.

Please select an Attribute from Class 1 and Class 2.

Invalid data type mismatch. You can only map Attributes with the same data type.

Attribute '$400009700$' has been saved.

An attribute with that name already exists

Select a Relationship to be deleted.

Spaces are not allowed in the Attribute Name Field.

Spaces are not allowed in the Class Name Field.

Spaces are not allowed in the Superclass Field.

The following instance has been successfully created: Instance Name: $200000020$ Class Form: $-5$

Default value is out of range

Default value must be selected from Default Value Menu values for $400104700$ fields

A report already exists with this name. Specify a different name in the Name field.

Specify a new report name.

If you close the report designer now, your changes will not be saved. Do you wish to continue?

Select a report type.

You did not specify a form. In the Form field, select the form to use for the report.

You did not specify a report name. In the Name field, specify a report name.

Form does not exist.

To access the AR System Report Console, you must use a browser. For browser login information, contact your administrator.

To access the AR System Report Console, you must use BMC Remedy Mid Tier 7.6.00 or later. The current mid tier version is midTierVersion.

The report name is too long. Enter a report name of 128 characters or fewer.

The Change Management user needs to have the following permission: AR Administrator, General Access, Unrestricted Access and Change Master.

The Incident Management user needs to have the following permission: AR Administrator, General Access, Unrestricted Access and Incident Master.

The Login specified for the Remedy Incident Management AR Login is invalid.

Top