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

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

Error messages 9700 to 9900

NumberDescription
9701 Error

The Currency form does not contain the correct number of required currency fields.

The Currency form does not contain the correct number of required currency fields.

9710 Error

Bulk entry transaction already in progress.

An attempt was made to initiate a bulk entry transaction when one was in progress.

9711 Error

No bulk entry transaction is in progress.

An attempt was made to end a bulk entry transaction when no transaction was in progress.

9712 Error

Invalid action type for end of bulk entry transaction.

The action type supplied for ending a bulk entry transaction was not one of the acceptable options. See the C API Reference for the list of acceptable values.

9713 Error

The attempted bulk entry transaction failed due to an error in one of the individual operations.

The attempted bulk entry transaction failed due to an error in one of the individual operations. Check the return list for more detailed information about the individual operation failure.

9720 ErrorThe updating of object relationship data through the AR System Object Relationships form is not allowed.
9730 ErrorThe updating of metadata through the Metadata view forms is not allowed.
9735 Error

Invalid full text scan information in form object properties.

An invalid combination of form object properties was provided for a form's full text scan information. Verify that interval or time properties were provided, but not both.

9750 Error

Error encountered while loading the shared library.

The BMC Remedy AR System Server could not load a shared extension library, such as the CMDB engine. Shared libraries are registered for loading in the ar.conf file. The server functions, but any functionality associated with the shared library is unavailable. The error message is written to the arerror.log file. Check the library paths specified in ar.conf. Make sure that the shared library and all dependent libraries are specified correctly, and restart the server.

9751 Error

The shared library identification is invalid or duplicate.

When a shared extension library is loaded, the AR System server invokes callback routines to identify the library to the server. This error occurs when the ar.conf file contains multiple registry entries for the same library or when the identification callback routine returns an error. The library is then unloaded from memory. The server continues to function, but any functionality associated with the shared library is unavailable. The error message is logged in the arerror.log file.

9752 Error

The shared library does not provide an Identification routine implementation.

When a shared extension library is loaded, the AR System server invokes callback routines to identify the library to the server. This error occurs when the server invokes a routine that is not implemented by the shared library. The library is then unloaded from memory. The server continues to function, but any functionality associated with the shared library is unavailable. The error message is logged in the arerror.log file.

9753 Error

The shared library is not loaded because it violates one of the prerequisites.

When a shared extension library is loaded, the AR System server invokes callback routines to identify the library to the server. This error occurs when the shared library does not implement a required routine. The library is then unloaded from memory. The server continues to function, but any functionality associated with the shared library is unavailable. The error message is logged in the arerror.log file.

9754 Error

The shared library has an invalid RPC program number.

The server loads a configuration management database (CMDB) shared library and assigns it a remote procedure call (RPC) identification number. The RPC number is returned by the library through a callback routine invoked by the server. In this case, the routine returned an invalid RPC value. To fix the problem, check the implementation of the callback routine and make any necessary corrections.

9755 Error

Error encountered while initializing (Initialization routine) the shared library.

On server startup, an initialization routine runs for all shared extension libraries that are loaded. The initialization routine returned an error, and the shared library was unloaded from memory. The server functions, but any functionality associated with the shared library is unavailable. To resolve the problem, check the implementation of the routine and make any necessary corrections.

9756 Error

This version of internal API is not supported by the server.

This is an internal error. A shared library tried to use an internal API exposed by AR Server, but the API version is incompatible with the AR Server version.

9757 ErrorInvalid call made from within filter context.
9758 Error

Invalid filter processing call made outside of filter context.

An internal error occurred because a filter workflow extension library was called by a filter action that does not have a filter context. Identify the user activity and workflow associated with the error, and then report it to Customer Support.

9759 Error

Extension library called with no filter context.

An extension library was called by a filter action that did not have a filter context. This is an internal error. Identify the user activity and workflow associated with the error, and then report it to Customer Support.

9760 Error

Workflow API function called from improper filter phase.

Error in the BMC Atrium CMDB extension library API. Contact Customer Support.

9761 Error

Unrecognized internal workflow API function.

Error in the BMC Atrium CMDB extension library API. Contact Customer Support.

9781 Error

Role name was not found. Verify that the role name is valid.

The server tried to resolve a role name to a role ID, but the role does not exist. Role names can be specified by a user or by workflow. Check the associated role name and make sure it is valid.

9782 ErrorInvalid role format: %s.
9800 Error

The reserved fields already exist on this email form.

Reserved fields are being created on the Email form that already exist on the form with the same field IDs.

9801 Error

Couldn't locate the Email form.

When an email message is sent to a specified user, this error message is returned if the server cannot find the Email Message, Email Attachments, or Email Association forms.

9802 Error

Email attachment mapping is invalid.

An internal system error occurred. Contact Customer Support.

9803 Error

Cannot locate mailbox.

Either no default mailbox is specified for an email notification, or the specified mailbox does not exist.

9804 Error

{{A required form for Email is missing. Server will attempt to import the form in place. Please verify the form gets imported or import it manually to ensure the Email Engine will work properly. formName. }}

The identified form is missing and must be imported if necessary.

9820 Error

Error opening license audit file.

The AR System server cannot open the file containing the license audit data. Each time an audit is run, AR System attempts to re-create the file if it is not found or inaccessible. This error can be caused by the AR System server not having read/write permission to the server log directory.

9821 Error

Error reading license audit file.

The AR System server received an error when attempting to read the license audit data file. This can be caused by the AR System server not having read/write permission to the server log directory.

9822 Error

Error writing license audit file.

The AR System server received an error when attempting to write to the license audit data file. This error can be caused by the AR System server not having read/write permission to the server log directory.

9823 Error

Corrupted license audit file.

The data in the license audit file is corrupt. The existing file is renamed and a new audit data file is created.

9824 Error

Unable to initialize license audit mutex.

An internal error occurred during the AR System server start up. Try restarting AR System. If restarting AR System does not fix the problem, contact Customer Support.

9828
Error

Invalid license limit configured

This errror can occur in the following scenarios:

  • While creating a new license, if the license is not part of the pricing model, which got encoded in the server license key.
  • While trying to update the license by increasing the number of licenses, which is not part of the pricing model.
9829
Error

Invalid license(s) assigned

This errror can occur in the following scenarios:

  • While trying to add/modify a user with bundled license type when legacy pricing model is configured.
  • While trying to add/modify a user with bundled license type with no bundled license.
  • While trying to add/modify a user with Read/Restricted Read type with application licenses.
  • While trying to add/modify a user with Fixed/Floating user license type with no application license and lwhen egacy pricing model is not configured.
  • While trying to add/modify a user with Fixed/Floating user license type with both application and bundled licenses present.
  • While trying to add/modify a user with both Fixed and Floating bundled license of same type.
  • While trying to add/modify a user with bundled license and its mapped granular license.
  • While trying to add/modify a user with application/bundled license that is not present in the pricing model mask.
  • While trying to add/modify a user with Floating user license and Fixed application license.
  • While trying to add/modify a user with bundled license type having bundled license from both pricing models.
  • While trying to add/modify a user with bundled license type having more than one 2015 Pricing Model bundled licenses.
  • While trying to add/modify a user with bundled license type and no bundled license is present.
9850 Error

You do not have application write license.

Either this user does not have an application write license for the application, or a floating license is unavailable for assigning. Contact your BMC Remedy AR System administrator.

9851 Error

No additional application fixed license for this type of license is available: licenseType.

No additional application fixed license for this type of license is available for assigning. Get more licenses if necessary.

9852 Warning

An Application fixed license of this type has been assigned to more users than the number of valid licenses you have: licenseType.

No more fixed licenses can be assigned until the number of fixed licenses is greater than the number of users who are assigned fixed licenses.

9853 Note

The following application fixed licenses have been returned to the system: licenseType.

A fixed license was returned to the system and is now available for assigning.

9854 Note

The following application fixed licenses have been granted: licenseType.

A fixed license was assigned.

9855 Note

The following write application token has become available and has been allocated to you -- access has been upgraded to write access.

A floating license was assigned for your use.

9856 Error

There is no such application user fixed license on the system: licenseType.

Either license information was entered incorrectly, or the fixed license does not exist. Contact Customer Support.

9857 Error

Application or Form already Licensable. Cannot modify or unlicense the Application or Form.

You cannot make an application license less restrictive. Contact Customer Support.

9858 Error

The application is not licensed.

Make sure that the application is a deployable application, not a local application. For information about local and deployable applications, see Deployable applications.

9859 Error

The license information provided for this form does not match that in owning application.

An internal system error occurred. Contact Customer Support.

9860 Error

The application license format is not valid.

License information might be entered incorrectly. Make sure that license names end with User Fixed or User Floating and that each license for a user is separated by a semicolon ( ; ).

9861 Error

The form is missing application licensing information.

An internal system error occurred. Contact Customer Support.

9862 Warning

No free application user floating write license are available. Currently accessing the application form in read-only mode. License will upgrade when one is available.

You have read-only access to the application. Try later to see whether a floating license becomes available, or contact your BMC Remedy AR System administrator.

9863 Warning

No license property can be set while creating a form.

License properties for a form cannot be set when a form is created. You can set the license properties after the form is created.

9864 Error

The Application or the Form cannot be made licensable. Only deployable applications can be made licensable. Also, Forms have to belong to deployable applications to be made licensable.

A local application cannot be made licensable. For information about local and deployable applications, see Deployable applications.

9870 ErrorEscalations must be disabled.
9871 Error

Execution terminated by workflow debugger.

A filter or escalation execution was terminated with a forced error from the workflow debugger.

9872 Error

Error in field value list (bad ID or datatype).

Adding a field or changing the data type is not permitted when setting the field value list during workflow debugging.

9873 Error

Command not valid at this time.

The workflow debugger command was issued at an incorrect time. For example, this error would result when you try to view the field-value list when the debug thread is idle (workflow is not executing) because no field-value list exists at that time. Issue the command when workflow is executing.

9874 Error

Invalid Breakpoint ID.

Breakpoints are identified by a numeric ID. This error typically indicates that the breakpoint specified in a command does not exist. For example, if you have only breakpoints 1, 2 and 3, and you issue a command to clear breakpoint 4, this message is issued. To see the list of valid breakpoints (including ID), issue the List Breakpoints or List Remote Breakpoints command.

9900 NoteExternal Logging Note.
Was this page helpful? Yes No Submitting... Thank you

Comments