This documentation applies to the 8.0 version of Remedy Action Request System, which is in "End of Version Support." You will not be able to leave comments.

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

3000 to 3225 - BMC Remedy Distributed Server Option messages

The following table describes BMC Remedy Distributed Server Option messages and notifications: 

Number Description
3000 Note

If signal is 15: "AR System Distributed Server terminated by user or accidentally."

If signal is not 15 "AR System Distributed Server terminated unexpectedly." The server for the DSO process (arservdsd) was terminated by a signal. The number following this error denotes 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.

3001 Note

BMC Remedy AR System Distributed Server terminated — fatal error encountered.

A fatal error occurred in arservdsd, and the process was shut down. An associated error message contains details.

3002 Note

Entry pending transfer or update has been pending for longer than the specified retry timeout.

A request pending transfer or update was in the pending state for longer than the Maximum Time to Retry interval, which is specified in the Modify Distributed Mappings form or overridden in the distributed fields on the actual request. If the request has a Transfer or Update Status distributed field, the field is updated to the status Time-out. The request is removed from the pending list, and the operation is not performed.

3003 Note

Pending distributed operation canceled due to error.

An error occurred while the system tried to transfer or update a request. If a Transfer or Update Status field is on the request, the field is updated to the status Canceled. An associated error message contains details.

3004 Note

BMC Remedy AR System Server is not currently available — will retry connection.

The BMC Remedy AR System Distributed Server Option cannot connect to the BMC Remedy AR System server. The connection attempt is retried periodically for several minutes. If repeated connection attempts fail, an associated error message is generated and no further attempts are made.

3005 Note

BMC Remedy AR System Server is now available.

The BMC Remedy AR System Distributed Server Option was previously unable to connect to the BMC Remedy AR System server. A subsequent connection attempt succeeded.

This scenario is possible when the Distributed Server Option is started before the BMC Remedy AR System server is ready to accept connections.

3100 Error

This AR System is not licensed for the Distributed Server Option.

A license for the DSO process is required to use the distributed functionality of the system. arservdsd cannot be run unless the system is licensed for it. Contact your distributor for information about obtaining a DSO process license.

3101 Error

Failed to open the Distributed Server lock file ar.lck.390601.

BMC Remedy AR System DSO process (arservdsd) opens a lock file named ar.lck.390601 at startup. This file is used to prevent multiple copies of arservdsd from being started. An associated file system error message contains details. Fix the problem, and rerun the server.

3102 Error

An instance of the Distributed Server is already running.

A computer can run only one instance of the DSO process at a time. If another DSO process is running, no action is required. If another DSO process is not running, you probably encountered a known problem with the NFS lock manager on Oracle workstations--the lock manager sometimes keeps a lock running even when the process holding the lock is no longer running. If no arservdsd is running, delete the lock file to free the lock, and then restart arservdsd.

3103 Error

Memory allocation for the DSO process failed.

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

3106 Error

The server being accessed is not licensed for the Distributed Server Option.

The arservtcd process might be on a target server that is not licensed to use the DSO process or on a version 2.0 or earlier target server that does not interact with arservdsd.

3107 Error

No Distributed Mapping form could be found on the server.

A Distributed Mapping form is required for the system to support distributed operations. No form containing all the special reserved fields indicating it is a Distributed Mapping form could be found.

Load the Distributed Mapping form, and define the appropriate mappings.

3108 Error

Two forms contain all the reserved distributed mapping fields — delete one to continue.

The system found two forms containing the reserved distributed mapping fields. Delete one form, or change it so that it is not considered a Distributed Mapping form (remove fields in the 200 to 220 range). An associated error message identifies the forms.

3109 Error

No Distributed Pending form could be found on the server.

A Distributed Pending form is required for the system to support distributed operations. No form containing all the special reserved fields indicating it is a Distributed Pending form could be found.

Load the Distributed Pending form.

3110 Error

Two forms contain all the reserved distributed pending fields — delete one to continue.

The system found two forms containing the reserved distributed pending fields. Delete one form, or change it so that it is not considered a Distributed Pending form (remove fields in the 250 to 260 range). An associated error message identifies the forms.

3111 Error

The "From" form in mapping definition must be the source form in the attempted mapping.

The form defined as the From form does not match the form that is the source of this transfer. Typically, this error occurs when a mapping specified in a transfer operation on the current server differs from the same mapping on the original server.

3112 Error

The "From" server in mapping definition must be the source server in the attempted mapping.

The server defined as the From server does not match the server that is the source of this transfer. Typically, this error occurs when a mapping specified in a transfer operation on the current server differs from the same mapping on the original server.

3113 Error

The "To" form in mapping definition must be the target form in the attempted mapping.

The form defined as the To form does not match the form that is the target of this transfer. Typically, this error occurs when a mapping specified in a transfer operation on the current server differs from the same mapping on the original server.

3114 Error

The "To" server in mapping definition must be the target server in the attempted mapping.

The server defined as the To server does not match the server that is the target of this transfer. Typically, this error occurs when a mapping specified in a transfer operation on the current server differs from the same mapping on the original server.

3115 Error

Unrecognized pending request type.

A pending request with the pending operation tag set to an unrecognized value was found. This error should occur only if you manually added requests to the Distributed Pending form, which is a system form that should not be manually manipulated. If you made no manual requests to the Distributed Pending form and encounter this error, contact Customer Support.

3116 Error

Only the master copy of an entry can be transferred.

You can only transfer the master instance of a request. The system tried to transfer the specified request, but the Master Flag field on the request is set to No.

3117 Error

Update unsuccessful — "From" form or "From" Server field has no value.

The From Form and From Server fields contain information about the previous copy of this request (from where the request was transferred). If the Master Flag is set to Yes, the system expects a value in the From Form and the From Server fields. If you used the ardist program to change the Master Flag value manually, make sure that values are assigned for the From Form and the From Server fields (you can also use ardist to change these).

3118 Error

Failed to record a distributed command.

arserverd received a request to record a distributed command or encountered a situation in which it tried automatically to record a distributed command, and a failure occurred during recording. Thus, the distributed command was not performed. The attempted command is displayed in this message. An associated message contains details.

3119 Error

The transfer or update cannot be performed because transfer mapping is currently disabled.

A transfer was attempted with mapping defined in the To Mapping (or From Mapping for an update) field. The specified mapping is disabled, so the transfer or update cannot be performed.

3120 Error

The distributed operation failed because the additional information about the item to be deleted is missing.

The Distributed Delete operation requires information about the item being deleted. This information is stored with the pending operation. If you encounter this message, the required additional data is missing. Without this data, the operation cannot be performed. This error should occur only if you manually added requests to the Distributed Pending form, which is a system form that should not be manipulated manually. If you made no manual requests to the Distributed Pending form and you encounter this error, contact Customer Support.

3121 Error

Duplicate entry IDs are encountered during transfer for specified action "Create New" - target form is missing the required field — "From Request ID".

You tried to transfer a request to the target form with ownership transferred to the new request, thus creating a new request because of conflicting request IDs. The target form, however, does not have a From Request ID field, which is required for this action. The From Request ID field provides a place to store the original request ID so that the original can be updated when the copy changes.

3122 Error

The target record for a distributed process (Distributed-Transfer, Distributed-Update, Distributed-Return) no longer exists.

A filter invoked a distributed process (Distributed-Transfer, Distributed-Update, Distributed-Return) during the deletion of a request. If a delete operation is in progress, the distributed process waits for the operation to be completed. When a distributed process begins, the error is created--because the request against which the distributed process is run no longer exists. Remove or disable the filter attempting the distributed operation, or reset the filter so it does not execute on a delete operation.

3123 Error

Must map the Entry ID field to the target Entry ID field, or the From Entry ID field must be present on the target form.

You tried a distributed transfer operation to another form by using a custom mapping with a transfer mode of Data + Ownership, but you did not map the Request ID field on the source form to one of these fields on the target form:

  • Request ID
  • From Request ID

Fix the mapping, and retry the transfer.

3124 Error

Transfer with ownership requires that target form contain Master Flag field.

You tried a distributed transfer operation by using mapping to another form with a transfer mode of Data + Ownership, and the target form does not contain a Master Flag field. The target form (identified in the error) must contain a Master Flag field if ownership is being transferred.

3125 Error

Transfer with ownership requires that target form contain "From form" field.

You tried a distributed transfer operation by using a mapping to another form with a transfer mode of Data + Ownership, and the target form does not contain a From Form field. The target form (identified in the error) must contain a From Form field if ownership is being transferred.

3126 Error

Transfer with ownership requires that target form contain "From server" field.

You tried a distributed transfer operation using a mapping to another form with transfer mode of Data + Ownership, and the target form does not contain a From Server field. The target form (identified in the error) must contain a From Server field if ownership is being transferred.

3127 Error

Master Flag field is required on source form for transfer with ownership.

A distributed transfer operation was attempted that included a mapping to another form with a Data + Ownership transfer. The source form does not contain a Master Flag field. The source form (identified in the error) must contain a Master Flag field if ownership is being transferred.

3128 Error

The reserved distributed pool fields can only exist on one form - delete duplicate to continue.

The system found two forms containing the reserved distributed pool fields. Delete one of the forms. An associated error message identifies the forms.

3129 Error

No Distributed Pool form could be found on the server.

A Distributed Pool form is required for the system to support distributed operations. No form containing all the special reserved fields indicating it is a Distributed Pool form could be found.

3130 Error

No Pending Errors form could be found on the server.

A Distributed Pending Errors form is required for the system to log pending errors to that form. No form containing all the special reserved fields indicating it is a Distributed Pending Errors form could be found.

3131 Error

The reserved distributed pending errors fields can only exist on one form — delete duplicate to continue.

The system found two forms containing the reserved distributed pending errors fields. You must delete one form or change it so that it is not considered a Distributed Pending Errors form. An associated error message identifies the forms.

3132 Error

Two forms contain all the reserved distributed logical mapping fields — delete one to continue.

The system found two forms containing the reserved distributed logical mapping fields. Delete one form, or change it so that it not considered a Distributed Logical Mapping form (remove fields in the 290 to 292 range). An associated error message identifies the forms.

3133 Error

No Distributed Logical Mapping form could be found on the server.

A Distributed Logical Mapping form is required for the system to support logical name replacement functionality. No form containing all the special reserved fields indicating it is a Distributed Logical Mapping form could be found.

With this form, DSO continues to work without the logical name replacement functionality. Load the Distributed Logical Mapping form, and define the appropriate mappings.

3134 Error

Logical name %s is not found in logical mapping form.

DSO could not find the logical name in the Distributed Logical Mapping form. Load the Distributed Logical Mapping form, and define the appropriate mappings.

3194 Error

Illegal value specified for -m option — legal values are 0 (not master) and 1 (master).

The value specified for the -m argument was not 0 (not master) or 1 (master), as required. The field is a selection field and requires a numeric value. The value specified was either a character or an integer other than 0 or 1. Reissue the command, and specify a legal value for this argument.

3195 Error

Must specify the -e <entryID> option.

To denote the ID of the request (entry) to be modified, specify the -e argument.

3196 Error

Must specify the -s <formName> option.

To denote the name of the form to be modified, specify the -s argument.

3197 Error

Must specify the -x <serverName> option.

To denote the name of the AR System server containing the form to modify, specify the -x argument.

3198 Error

A value is missing for one of the arguments for the command line option.

You included an argument with no specific value on the ardist command line. Reissue the command with values assigned to all arguments.

3199 Error

Unrecognized command line argument.

The specified command-line argument is not recognized by ardist. See the BMC Remedy Distributed Server Option section for more information about valid command-line arguments. ardist cannot execute with invalid arguments specified.

3200 Error Invalid dynamic permission inheritance object property format.
3201 Error Object does not have a dynamic permission inheritance property.
3202 Error Field defined in dynamic permission inheritance property not found.
3203 Error Error parsing field pairs from dynamic permission inheritance property.
3225 Error Form does not allow non-admin to delete.

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