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

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

Error messages 9101 to 9199

NumberDescription
9101 Error

The direct SQL and run process commands are valid only as server-side processes, not as client-side.

During import and export operations, the direct SQL and run process commands are valid only as server-side processes, not as client-side. In certain cases, the processes are exported as client-side processes.

9102 Error

Invalid Run Process or Direct SQL command.

An error occurred when the fully substituted command was returned from the database, for example, an invalid server-side Run Process command was returned. To continue, verify that the SQL command or Run Process command works from a command line.

9110 Error

Server does not have a valid host id. Please correct this error to enable licensing for this server.

The host ID you entered does not match the host ID in your license. Make sure that the host ID you entered is the one you supplied when you requested the license.

9130 Error

Error encountered while executing a Web Service.

This error message is generated by the Web Service plug-in whenever an error occurs during the execution of a Web Service.

Note: If you receive this error message while upgrading the BMC Remedy AR System server, you can ignore it. During the installation, this message is generated when Java 1.5 or 1.6 is used in both the old and new versions of the server. When the AR System server is restarted after the upgrade, this error message will not reappear.

9131 ErrorXML Output mapping cannot be empty.
9132 Error

The output default value of element does not match the input value.

In web services, a field in the output mapping is set to a default value, but the incoming value does not match it.

9141 ErrorConversion of timestamp to a string failed.
9142 ErrorConversion of time value to a string failed.
9143 ErrorConversion of a datetime string to timestamp failed.
9144 Error

Upgrade of system form failed because the definition file is not the required version.

At system startup, a system form was not upgraded because the expected version of the corresponding definition file was not in the expected location. Locate the updated version of the specified definition file and place it in the specified system form directory.

9145 Error

Upgrade of system form failed because the definition file is missing an expected field.

At system startup, a system form was not upgraded because the expected contents of the corresponding definition file were not in the file. This is an unexpected system error. Contact Customer Support.

9150 Error

Error while opening the armonitor lock file.

You cannot run multiple instances of armonitor from the same installation directory. However, you can run another instance of armonitor from a different installation directory. (UNIX only)

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

Comments