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.

3300 to 3349 - BMC Remedy Data Import event messages

The following table describes BMC Remedy Data Import event messages and notifications:

Number Description
3300 Error

No Alert Events form could be found on the server.

The server could not locate a form containing the reserved alert events field.

3301 Error

The reserved alert event fields exist on multiple forms. They are only allowed to exist on one form.

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

3302 Error

Problem encountered during creation of the Alert Events form.

The server could not successfully import the Alert Events form at startup. An associated error message contains details.

3303 Error

Must be AR_NOTIFIER user to perform this operation.

The server does not allow the removal of the Alert Events form or its reserved fields.

3314 Error

Failed to connect with alert client.

A sockets error occurred while the system tried to establish communication with an alert client. Turn on alert logging to view a trace of the communication activity.

3315 Error

Attempt to communicate with alert client timed out.

An attempted communication with an alert client did not succeed within the configured time period. Turn on alert logging to view a trace of the communication activity.

3316 Error

Failed to load the alert cleanup escalation.

The server could not successfully import the CleanupAlertEvents escalation at startup. An associated error message contains details.

3317 Error

Invalid alert message format.

A failure occurred while the system tried to decode an alert message sent from the server to an alert client, indicating a data transmission error.

3318 Error

Attempt to communicate with alert client failed because the required port is in use by another process.

When attempting to send an alert to a client, the BMC Remedy AR System server encountered a socket address that the system was still using. This can occur on a system that is not releasing address/port combinations in a timely manner. Turn on alert logging for more information about the server actions taken.

3320 Error

The reserved server group fields can only exist on one form — delete duplicates on other forms to continue.

The system found two forms containing the reserved server group fields, which qualifies both forms as the BMC Remedy AR System Server Group Operation Ranking form. Delete one of the forms. An associated error message identifies the forms.

3321 Error

No server group operation ranking form could be found on the server.

An error occurred during the automatic creation of the BMC Remedy AR System Server Group Operation Ranking form. Contact your BMC Remedy AR System administrator.

3322 Error

Unrecognized server group operation encountered in the ranking form.

A server group operation was found that the BMC Remedy AR System server does not recognize. Use only the supplied operation names.

3323 Error

Creation of the server group operation ranking form failed.

The BMC Remedy AR System Server Group Operation Ranking form definition could not be imported. Check the server error log for the cause of the problem.

3324 Error

This configuration setting is not allowed when the server is a member of a server group.

The setting of the configuration item is not allowed because it conflicts with server group operation management. Do not set the configuration item while the server is a member of a server group.

3325 Error

Unable to send a server group related signal to another server.

The BMC Remedy AR System server could not successfully run a signaling process. Make sure the arsignal utility program is in the BMC Remedy AR System directory.

3326 Error

Unable to find a server group entry for this server.

An error occurred during the creation of a server group entry in a data dictionary table. Contact your BMC Remedy AR System administrator.

3327 Warning

Check interval cannot be less than 30 seconds. A 30-second value is set by the system.

A value of less than 30 seconds was specified for the check interval. You cannot set the check interval to a value of less than 30 seconds.

3328 Error

Unable to launch an agent process to communicate with an external program.

AR System was unable launch an agent process to communicate with an external program. Make sure that the specified program is in the AR System server's directory, or if the operation is not appropriate in the current environment, remove the ranking entry for the corresponding operation from the AR System Server Group Operation Ranking form. Two restarts of the server might be required to prevent the error from being reported when the operation is removed from the ranking form.

3329 Error

A floating license without server group tag cannot be used in a server group. This floating license is ignored.

The BMC Remedy AR System server encountered a floating license definition that was ignored because a server running as a member of a server group accepts only licenses that have a server group tag. Replace the license definition with a license that has a server group tag.

3330 Error {{A floating license with server group tag cannot be used on a stand-alone server. This floating license is ignored. The BMC Remedy AR System server encountered a floating license definition that was ignored because an BMC Remedy AR System server not running as a member of a server group accepts only licenses that do not have a server group tag. Replace the license definition with a license that does not have a server group tag.
3331 Error

A floating license with a different server group tag cannot be used on this server group. This floating license is ignored.

The BMC Remedy AR System server encountered a floating license definition that was ignored because an BMC Remedy AR System server running as a member of a server group accepts only floating licenses that have the same server group tag. Make sure that all floating license definitions have the same server group tag.

3332 Warning

The change of this setting will only take effect after AR System server restart.

The Server Group Member option was changed and the new value does not take effect immediately. The BMC Remedy AR System server must be restarted for the setting to take effect.

3333 Error

Invalid or missing server group operation definition. Contact your AR System administrator.

An internal table containing server group operation definitions has an invalid entry or is missing an expected entry. Contact your BMC Remedy AR System administrator.

3334 Error

Invalid or missing server group license entry. Contact your AR System administrator.

An internal table containing server group license entries has an invalid entry or is missing an expected entry. Contact your BMC Remedy AR System administrator.

3335 Warning

The Check Interval setting change will only take effect after all servers in the group are restarted.

This is a warning that BMC Remedy AR System must be restarted on all servers in the server group before a change in how often the server communicates with other servers in the group takes effect.

3336 Warning

Duplicate server group ranking value encountered in the ranking form -- ordering cannot be guaranteed.

A duplicate server group operation ranking was encountered during loading of the ranking data. The name of the operation is supplied as appended text. The ordering of duplicate values is not guaranteed to be consistent, therefore you should change the ranking values to be unique.

3340 Error

Unable to start the arsignald process.

Server group error indicating that the AR System server was unable to start the arsignald process. Arsignald is a small process, managed by the AR System server, that is used for communication between members of a server group. This error is typically caused by the executable file not being in the same directory as the AR System server executable (possibly as an installation error). Make sure that the arsignald executable is in the AR System server installation directory. If this does not resolve the problem, make sure the AR System server has permission to run the arsignald executable.

3341 Error

Not enough memory to create arsignald start up info.

Indicates that the AR System server was unable to start the arsignald process because it was unable to allocate memory for the required start up information. Although this is not a fatal server error, it is unlikely that the server will successfully start up when memory cannot be allocated. Give the server more memory.

3342 Error

Unable to write to arsignal daemon.

Indicates that the AR System server was unable to issue a command to the arsignald process. This error is caused by a broken communication pipe between the AR System server and arsignald, possibly caused by arsignald being killed or crashing. The situation should be corrected automatically, because the AR System server attempts to restart arsignald if it detects a communications problem.

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