This documentation applies to the 8.1 version of Remedy Action Request System, which is in "End of Version Support."

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

Error messages 801 to 900

Number Description

801 Note

AR System TC server terminated — fatal error encountered.

802 Note

BMC Remedy AR System server terminated unexpectedly — restarting.

The server detected that one of the child processes it is responsible for terminated. The name of the process being restarted is reported in an associated message.

The server process relaunches the server that shut down.

803 Note

AR System server terminated unexpectedly — restarting.

804 Note

AR System TC server restarting.

840 Error

Error while opening the AR System TC server lock file.

841 Error

Another copy of the TC server is already running.

842 Error

Not enough memory to process the call from the client.

The system encountered an error during a call to allocate space. The failure occurred on the server during processing of a call from the client. In general, this error occurs when too many processes are running or when some processes have grown to occupy most or all available memory on the server. Recover the memory by shutting down unneeded processes or by restarting processes that have been running for a while.

843 Error

Unable to launch the child process.

A failure occurred while the system tried to launch a child process. An associated message provides details. The child process was not launched. Fix the problem, and retry the operation.

844 Error

Unable to launch the child process.

A failure occurred while the system tried to launch a child process. An associated message provides details. The child process was not launched. Fix the problem, and retry the operation.

845 Error

Unable to start this server after 4 tries within 30 seconds — abandoning attempt.

The server process tried to launch a child process more than four times within 30 seconds. The name of the child process that was not restarted is identified in an associated message. Because this process continues to fail, the server stops trying to launch the process and removes it.

846 Error

Exception occurred while handling previous exception.

847 Error

A failure occurred while the system tried to wait for a status change.

A failure occurred while the system tried to wait for a status change. An associated message provides details. This is an internal error.

848 Error

Unable to start any servers — TC server will be shut down.

849 Error

Unable to create the pipe.

850 Error

Unable to open the pipe.

851 Error

Unable to read from the pipe.

855 Error

Failed to lock arservftd process, it is held by another process.

The work file must be locked by the arservftd process but is being held by another process.

856 Error

Pending list lock file does not exist.

The arservftd process cannot release the work file, because the file does not exist.

857 Error

Unable to add note about the field updated due to the failure of opening the pending list indexing file.

A full text search (FTS)-enabled field was updated. The file holding the list of fields that have indexing pending could not be opened when you tried to add a note about the updated field. An associated error message provides details.

858 Error

Unable to add note about the field updated due to the failure of writing to the pending list indexing file.

A full text search (FTS)-enabled field was updated. The file holding the list of fields that have indexing pending could not be written to when you tried to add a note about the updated field. An associated error message provides details.

859 Error

Unable to add note about the field updated due to the failure of locating the record associated with the updated field.

A full text search (FTS)-enabled field was updated. The file holding the list of fields that have indexing pending could not be written to when you tried to add a note about the updated field because the record associated with the updated field was not found. An associated error message provides details.

860 Error

Unable to add note about the field updated due to the failure to truncate the file holding the indexing pending list.

A full text search (FTS)-enabled field was updated. The file holding the list of fields that have indexing pending could not be truncated when you tried to add a note about the updated field. An associated error message provides details.

861 Error

Failed to delete unneeded entries while reindexing the pending list.

During a reindex operation, an error occurred while the system tried to purge the list of pending changes. An associated error message provides details.

862 Error

Too few arguments for the full text indexer process.

You did not provided the minimum set of arguments required by the full text search (FTS) indexer process (arservftd). See Performing searches with FTS.

863 Error

Too many arguments for the full text indexer process.

You exceeded the limit of arguments allowed by the full text search (FTS) indexer process (arservftd). See Performing searches with FTS.

864 Error

Invalid action for full text index process.

One of the arguments for the full text search (FTS) indexer process (arservftd) indicates the action for the program to take. The supplied action code is not recognized. See Performing searches with FTS.

865 Error

Full text indexer process terminated by user or a system error.

The server for the full text search (FTS) search feature (arservftd) was terminated by a signal. The number following this error is the signal that was received.

If the signal is 15, restart the server and continue to work. The process was stopped either accidently or intentionally by a user in your environment.

If the signal is a number other than 15 or is one you sent directly to the process, contact Customer Support for assistance in determining the cause of the problem. The server most likely shut down due to a bug in the system.

866 Error

Another instance of the full text indexer process is already running.

Only one instance of the full text search (FTS) indexer process can be run on any given computer. Determine whether a copy of arservftd is already running. If so, no action is required.

867 Error

A form ID or name, a field ID, and a Request ID are all required for this operation. One or more of these values is missing.

When specifying an operation against a specific request, you must supply a form ID or name, a field ID, and a Request ID. One or more of these values is missing. For more information, see the C API Reference .

868 Error

Too many arguments specified for the "optimize" argument.

The optimize argument was specified for the full text search (FTS) indexer process. A limited number of arguments is allowed when this option is specified. In this case, one or more of the arguments that are not allowed were specified. For more information, see the C API Reference .

869 Error

Too many arguments specified for the "retry" argument.

The retry argument was specified for the full text search (FTS) indexer process. A limited number of arguments is allowed when this option is specified. In this case, one or more of the arguments that are not allowed were specified. For more information, see the C API Reference .

874 Error

A required parameter is null or invalid.

875 Error

FTS Service could not complete the requested operation.

881 Error

Image definition is missing.

A file specified as holding the definition of an image does not contain an image definition. This error is usually caused by a manual deletion of the contents of a structure file. If the file was deleted, restore it from a backup.

882 Error

The specified image could not be found.

The specified image is not in the AR System database. An operation was attempted against the wrong server, or no image is defined by that name. Change to the correct server or specify an existing image.

883 Error

Duplicate image name.

The specified image is already in the AR System database. Choose a different name for the image, or rename the existing image.

884 Error

No image specified.

No image content has been specified for the image being created or updated. This argument is required when creating or updating an image object.

885 Error

No image type specified.

No image type, such as jpg or bmp, has been specified for the image being created or updated. This argument is required when creating or updating an image object.

897 Error

Maximum number of client transactions already in use.

898 Error

Transaction handle supplied is invalid.

899 Error

Cannot begin transaction because a transaction is already open.

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Comments