Error messages 9901 to 9994

Internal API call failed.

An internal system error occurred. Retry the operation.

Illegal command line parameter.

A program was called with a command-line parameter that cannot be used; it might not be legal for this program or it might not be legal in combination with other parameters. Check the documentation to verify that your parameters are legal and can be used together.

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

The count for Base and Custom form types should match the number of fields defined for the form in the field table. The count for an Overlay form should match the number of fields in the corresponding base form plus the number of custom fields defined for the overlay.

For more information on correcting the issue, see Knowledge Base article ID 000097106.

Join form Audit cannot be enabled unless the base forms have audit enabled.

Enable auditing for the base forms and retry the operation.

The same Log Key cannot be applied to more than one field in a schema.

Specify a unique log key for each field.

There are incorrect number of reserved fields in the Archive or Audit form.

Choose one of the following options to correct the problem:

• Make sure that the main form is linked to the correct archive/audit form.
• Set archive/audit to none in the main form, correct the problem, and enable archive/audit again.
• Choose a new name for the archive/audit form, and BMC Remedy AR System automatically creates a form.

The Archive or Audit form is already in use by another form.

To correct the problem, see error message 9925.

The number of data fields in the main form should be less than or equal to the data fields in the Archive or Audit form.

To correct the problem, see error message 9925.

The data types of the data fields in the Source and Archive/Audit form do not match.

To correct the problem, see error message 9925.

Field is missing from the Archive/Audit form.

To correct the problem, see error message 9925.

Cannot import only Audit form. Either the Main form by itself or both Main and Audit can be imported.

You cannot import only the source form. You can import the main form alone or the main form and the corresponding archive/audit form.

Qualification cannot contain EXTERNAL references.

The audit qualification cannot have external references.

Archive or Audit form not found. Archive or Audit will be disabled.

This warning is received when a form with audit or archive enabled is imported from a file and the audit or archive form is not on the AR System server. For example, if you are importing a form named "form_audit" that has audit enabled, and a form with the same name is not on the AR System server, audit is disabled on the imported form.

You cannot disable the audit on this form until you disable the audit on dependent form.

The form for which you are disabling audit has a dependent form on which audit is enabled. For example, if you have a join form that has audit enabled, audit on the base forms cannot be disabled. First disable audit on the dependent (join) forms, and then disable audit on the base forms.

You cannot enable the audit on this form until you enable the audit on base forms.

The form for which you are enabling audit has a base form on which audit is disabled. For example, if you have a base form that has audit disabled, audit on the dependent forms cannot be enabled. First enable audit on the base forms, and then enable audit on the dependent forms.

Fields in the range 5000 to 5999 are reserved for Audit use.

The field IDs in the range 5000 to 5999 are used by the system for audit purpose.

Can not set information field in archive policy.

There are information fields on the archive policy that show data from the archive definition. You cannot update the values of the information fields.

The field used for age qualification does not exist or is of not valid type. Only Date/Time fields are allowed in age qualification.

For a form archive definition, the field defined for age qualification either does not exist or is not of the type Data/Time field.

Time-out during plug-in call--the request has been accepted by the plug-in server, but the plug-in has not yet responded.

The plug-in did not respond to a call within the time period specified in the AR System server configuration file (ar.conf on UNIX; ar.cfg on Windows). To determine the cause of the error, check the AR System server's API log (by default, arapi.log). To avoid such errors in the future:

• Increase the plug-in time-out settings in the AR System server configuration file:
  • Filter-Api-Timeout — Specifies the time in which AR filter plug-in servers must respond to a call before an error is returned. The default is 40 seconds, but it can be as long as 300 seconds (5 minutes).
  • Server-Plugin-Default-Timeout — Specifies the time in which ARDBC plug-in servers must respond to a call before an error is returned. The default is 60 seconds, but it can be as long as 600 seconds (10 minutes). For more information, see Configuration settings S-Z.
• Make sure the AR System server has a sufficient number of server threads. The default number is often inadequate. For example, some plug-ins loop back to the server twice during a call, requiring two server threads for one call. The threads also must often support concurrent plug-in calls. In addition, if you increase the plug-in call time-out settings, the length of time a server thread is held for a plug-in call might increase. To increase the number of threads dedicated to plug-ins, use the Plugin-ARDBC-Threads, Plugin-AREA-Threads, and Plugin-Filter-API-Threads options in the AR System server configuration file (see Updating configuration settings by using the AR System Configuration Generic UI form).

Operation not allowed on this form.

You get this error if you try to create or modify an entry externally on the system forms,whose entries are created or modified by using a background process that is internal to AR Server. Examples of such forms are RLS Migration Pending and AR System:RLS Autodiscovery.

The input provided for calculating the next recurrence is bad.

An internal error occurred. Check the arerror.log file.

The date calculated is invalid or a bad date format. Please make sure the date format is in the ARServer's date format and separator.

Check the date and make any necessary corrections.

Type of recurrence requested is invalid.

Valid recurrence types are Yearly, Monthly, Weekly, Daily, and Special Dates.

Month of year selected is invalid.

Enter a month value between 1 and 12.

Week of Month selected is invalid.

Enter a week value from 1 to 5.

Day of Month selected is invalid.

Enter a day value from 1 to 31.

Hours of day selected is invalid.

Each element in the HoursOfDay array cannot be greater than 1.

Day of the week selected is invalid.

Each element in the daysOfWeek array cannot be greater than 1.

The date is out of range of the 1970 - 2038 allowed by the OS.

The year of the calculated recurrence date is outside of the range allowed by the operating system.

The recurrence date is not valid for this month. Skipping to next recurrence.

Using the recurrence provided, the date obtained is not valid for this month. The next recurring value will be tried.

Recurrence of type Specific Dates has no dates.

Make sure the dates are in the server's date and separator format. Separate dates with semicolons, for example, 12/24/07;12/25/07.

Cannot find respective System Log Form.

The log form is missing or corrupted. Import the LogForm.def file from the C:\Program Files\BMC Software\AR System\Arserver\systemforms\en folder, using the overwrite option if the form exists but is corrupted.

There is no recursion qualifier specified in the Recursive Query.

The ARGetListEntryWithMultiSchemaFields function tried to perform a recursive query, but it failed because the recursion qualifier (recursionQual) was not specified. For more information, see these topics in Structures for ARGetListEntryWithMultiSchemaFields and BMC Remedy AR System C API functions:

• ARGetListEntryWithMultiSchemaFields function
• ARMultiSchemaQueryFromList structure
• ARMultiSchemaRecursiveQueryStruct structure

Wrong schema type specified for a query form list item in the Recursive Query.

The ARGetListEntryWithMultiSchemaFields function tried to perform a recursive query, but it failed because one or more of the items in the query from list (queryFromList) of the recursive query structure were not of the type AR_MULTI_SCHEMA_SCHEMA_NAME. All the items in the list should be of that type.

For more information, see these topics in Structures for ARGetListEntryWithMultiSchemaFields and BMC Remedy AR System C API functions:

• ARGetListEntryWithMultiSchemaFields function
• ARMultiSchemaQueryFromList structure
• ARMultiSchemaRecursiveQueryStruct structure

Can not specify more than one Recursive Query.

The ARGetListEntryWithMultiSchemaFields function tried to perform a dynamic join, but it failed because more than one recursive query was included in its query from list (queryFromList). The query from list can contain only one item of the recursive query type.

For more information, see these topics in Structures for ARGetListEntryWithMultiSchemaFields and BMC Remedy AR System C API functions:

• ARGetListEntryWithMultiSchemaFields function
• ARMultiSchemaQueryFromList structure
• ARMultiSchemaQueryFromStruct structure

Can specify fields from only one schema in the Recursive Query fields list.

The ARGetListEntryWithMultiSchemaFields function tried to perform a recursive query, but it failed because the fields that the recursive query was instructed to retrieve were on more than one form. All the fields must be on the form designated by the recursive schema alias (recursiveSchemaAlias).

For more information, see these topics in Structures for ARGetListEntryWithMultiSchemaFields and BMC Remedy AR System C API functions:

• ARGetListEntryWithMultiSchemaFields function
• ARMultiSchemaQueryFromList structure
• ARMultiSchemaRecursiveQueryStruct structure

Wrong recursive schema specified in the Recursive Query.

The ARGetListEntryWithMultiSchemaFields function tried to perform a recursive query, but it failed because the recursive schema alias (recursiveSchemaAlias) does not match any alias or schema (form) in the recursive query's query from list (queryFromList).

For more information, see these topics in Structures for ARGetListEntryWithMultiSchemaFields and BMC Remedy AR System C API functions:

• ARGetListEntryWithMultiSchemaFields function
• ARMultiSchemaQueryFromList structure
• ARMultiSchemaRecursiveQueryStruct structure

Wrong or missing join type.

The ARGetListEntryWithMultiSchemaFields function tried to perform a dynamic join, but it failed because the join type (joinType) of one of the items in the function's query from list (queryFromList) is either invalid or not specified. Use one of these integers to specify the joinType:

• 0 – AR_MULTI_SCHEMA_JOIN_INNER (Inner join)
• 1 — AR_MULTI_SCHEMA_JOIN_LEFT (Left outer join)
• 2 — AR_MULTI_SCHEMA_JOIN_RIGHT (Right outer join)

For more information, see these topics in Structures for ARGetListEntryWithMultiSchemaFields and BMC Remedy AR System C API functions:

• ARGetListEntryWithMultiSchemaFields function
• ARMultiSchemaQueryFromList structure
• ARMultiSchemaQueryFromStruct structure

Wrong query type specified for an item in the query form list.

A call to the ARGetListEntryWithMultiSchemaFields function failed because one or more of the items in the function's query from list (queryFromList) is of the wrong type. These are the valid item types:

• Form = 0 (AR_MULTI_SCHEMA_SCHEMA_NAME)
• Recursive query = 2 (AR_MULTI_SCHEMA_RECURSIVE_QUERY) Verify the type and retry the operation.

For more information, see these topics in Structures for ARGetListEntryWithMultiSchemaFields and BMC Remedy AR System C API functions:

• ARGetListEntryWithMultiSchemaFields function
• ARMultiSchemaQueryFromList structure
• ARMultiSchemaQueryFromStruct structure

Schema alias associated with the field is not valid.

A call to the ARGetListEntryWithMultiSchemaFields function failed because the alias (queryFromAlias) of the form or recursive query associated with one of the fields specified in the call is either empty or exceeds the maximum length (AR_MAX_NAME_SIZE, 254 characters). Verify the alias and retry the operation. Character strings must be terminated by a 0.

For more information, see these topics in Structures for ARGetListEntryWithMultiSchemaFields and BMC Remedy AR System C API functions:

• ARGetListEntryWithMultiSchemaFields function
• ARMultiSchemaQueryFromList structure
• ARMultiSchemaQueryFromStruct structure

RegularQuery parameter cannot be empty.

The RegularQuery parameter of the getListEntryObjects function (Java API) is NULL. Provide a valid instance of the RegularQuery object and retry the operation.

For more information, see these:

• ARGetListEntryWithMultiSchemaFields, which includes information about the ARGetListEntryWithMultiSchemaFields function and its Java class diagram
• Java API online documentation located at ARSystemServerInstallDir\ARserver\api\javaplugins\arpluginsdoc<VerNum>.jar

The list of query sources cannot be empty.

The RegularQuery parameter of the getListEntryObjects function (Java API) contains a list of the query sources that is either NULL or empty. Ensure that the list has at least one element. For more information, see these documents:

• ARGetListEntryWithMultiSchemaFields, which includes information about the ARGetListEntryWithMultiSchemaFields function and its Java class diagram
• Java API online documentation located at ARSystemServerInstallDir\ARserver\api\javaplugins\arpluginsdoc<VerNum>.jar

Join qualifier is specified but join source is not valid.

One or more of the query source objects (IQuerySource) in the RegularQuery parameter of the getListEntryObjects function (Java API) contains a join qualification but does not specify a query source object to join with (getJoinedWith element). Ensure sure that the object specified in that element is valid.

For more information, see these documents:

• ARGetListEntryWithMultiSchemaFields, which includes information about the ARGetListEntryWithMultiSchemaFields function and its Java class diagram
• Java API online documentation located at ARSystemServerInstallDir\ARserver\api\javaplugins\arpluginsdoc<VerNum>.jar

Field definition not valid.

The definition of a field specified within a call to the getListEntryObjects function (Java API) is invalid. Either the field source object is NULL, or the field ID is less than 0. For more information, see these documents:

• ARGetListEntryWithMultiSchemaFields, which includes information about the ARGetListEntryWithMultiSchemaFields function and its Java class diagram
• Java API online documentation located at ARSystemServerInstallDir\ARserver\api\javaplugins\arpluginsdoc<VerNum>.jar

Recursive query cannot be empty.

The ARGetListEntryWithMultiSchemaFields function tried to perform a recursive query, but it failed because although the recursive query type is specified in the function's query from list (queryFromList), the recursive query structure is missing.

For more information, see these topics in Structures for ARGetListEntryWithMultiSchemaFields and BMC Remedy AR System C API functions:

• ARGetListEntryWithMultiSchemaFields function
• ARMultiSchemaQueryFromList structure
• ARMultiSchemaRecursiveQueryStruct structure

The list of the query fields must contain at least one regular field you have permission to.

A call to the ARGetListEntryWithMultiSchemaFields function failed because the user issuing the call did not have permission to any of the fields in the function's getListFields parameter. To enable the function to return data, give the user permission to at least one field in that parameter. To return all matching requests, give the user permission to all fields in that parameter. For more information, see ARGetListEntryWithMultiSchemaFields.

The ValueSetQuery property can only have one field.

A call to the getListEntryObjects function (Java API) failed because the list of fields in the ValueSetQuery object contains more than one field. Fix this error and retry the operation. For more information, see these topics:

• ARGetListEntryWithMultiSchemaFields, which includes information about the ARGetListEntryWithMultiSchemaFields function and its Java class diagram
• Java API online documentation located at ARSystemServerInstallDir\ARserver\api\javaplugins\arpluginsdoc<VerNum>.jar

Invalid join qualifier for this join form.

A call to the ARGetListEntryWithMultiSchemaFields function failed because the join criteria for one of the forms in the function's query from list (queryFromList) did not reference a field in the preceding item in the list. Review the fieldId element in the join criteria (ARMultiSchemaQualifierStruct) and retry the operation.

For more information, see these topics in ARGetListEntryWithMultiSchemaFields and BMC Remedy AR System C API functions:

• ARGetListEntryWithMultiSchemaFields function
• ARMultiSchemaQueryFromStruct structure
• ARMultiSchemaQualifierStruct structure

Dialog forms not allowed in a dynamic query.

A call to the ARGetListEntryWithMultiSchemaFields function failed because the function's queryFromList parameter contains a display-only form, such as a dialog box.

For more information, see these topics in Structures for ARGetListEntryWithMultiSchemaFields and BMC Remedy AR System C API functions:

• ARGetListEntryWithMultiSchemaFields function
• ARMultiSchemaQueryFromStruct structure
• ARMultiSchemaQualifierStruct structure

Join qualifier not allowed for the first query source in the list.

A call to the ARGetListEntryWithMultiSchemaFields function failed because the first item in the function's query from list (queryFromList) contained join criteria (joinType and joinQual). Specify join criteria in the second item and each item thereafter to define the join with the previous item. Do not specify the join criteria in the first item in the list. Review the join criteria and retry the operation.

For more information, see these topics in Structures for ARGetListEntryWithMultiSchemaFields and BMC Remedy AR System C API functions:

• ARGetListEntryWithMultiSchemaFields function
• ARMultiSchemaQueryFromList structure
• ARMultiSchemaQueryFromStruct structure

Diary field or long char field not allowed in join criterion.

An API call to one of the following functions failed because the join criteria associated with the function contains a diary field or a long character field:

• ARGetListEntryWithFields — Remove these field types from the predefined join criteria in the BMC Remedy AR System join form specified by the function's schema argument.
• ARGetListEntryWithMultiSchemaFields — Remove these field types from the join criteria (joinQual) of the items in the function's query from list (queryFromList).