Making Additional Customizations › Set Up Application Mapping › Import Application Mapping Rules › Error Messages for Importing Rules

Error Messages for Importing Rules

This topic describes some of the error messages that may be displayed. When importing is complete, the command returns error messages for any failed imports, then lists the fields for the failed rules.

If the rule import file contains column definition errors, the import operation fails. If the file contains errors in rule definitions, the import operation skips each faulty rule and continues with the next rule.

Notes about the Description field:

• All of the rule fields must be populated with values except the optional Description (desc) field. The rule line must include the comma for the desc field, however.
• If Description field values contain internal commas, the rule import fails. The import utility does not support commas inside Description values.

A column named 'XXX' already belongs to this DataTable

The import file contains a duplicate of the column named in the error message. The column name is shown in place of 'XXX'.

Troubleshooting: Delete the duplicated column. Follow the format in the appropriate example file as described in Import Custom Application Mapping Rules.

An invalid ApplicationMapping

One of the following problems occurred while you were updating existing rules:

• The import file specifies the appID of the original rule incorrectly.
• The specified appID corresponds to a rule that has been deleted.

Troubleshooting: Verify that the appID is entered correctly and that its rule still exists. You can export the current rules to a .csv file as described in Import Application Mapping Rule Updates. The export file includes the appIDs for all of the current rules.

Application Mapping object is not valid: An existing record is already in use

Both of the following conditions were met:

• You are using the file format for importing a new rule.
• One of the rule definitions in the import file has the same field values as an existing rule.

Troubleshooting: If this error occurs rarely, you may want to edit the rules individually on the Application Definitions page. To update a group of existing rules by using the racmd command, use the import file format that is described in Import Application Mapping Rule Updates.

Application Mapping object is not valid: An invalid protocol was entered

The import file may have a misspelled column name or may include an invalid column. This error may also occur if a rule has an invalid value for a required field (a field other than desc).

Troubleshooting: Verify that the following elements are correct in the import file:

• Field values: Rule definitions have supported field values. The values are entered correctly.
• Format: The correct columns are included in the file. The column names are spelled correctly.

Application Mapping object is not valid: IP cannot be blank

The error may occur if either of the following conditions is met:

• An NBAR2 rule is missing the NBAR2 application ID value.
• A Host (server) rule is missing the server IP address value.

Troubleshooting: Add the missing value to the rule definition.

Application Mapping object is not valid: Mask must be between 0 and 32

The Subnet rule has an unsupported Mask value.

Troubleshooting: Specify a Mask value between 0 and 32.

Application Mapping object is not valid: ToS must be between 0 and 255

The All (ToS) rule has an unsupported ToS value.

Troubleshooting: Specify a ToS value between 0 (all ToS) and 255.

Error: Missing parameter name from -params list

The rule has no specified value for one of the required fields.

Troubleshooting: Verify that all of the required field values are included. All field values are required except for desc.

To display help for the command, enter:

setapplicationmapping