Notification Engine error messages


Common error messages found while using Notification Engine

Error

Description

140505

This Notification Engine error message indicates that the specified Subscription ID does not exist. This error can appear when you make a getNotifications call or attempt to unsubscribe from receiving the notifications using an invalid ID.

140506

This Notification Engine error message indicates that the client request cannot be completed because of one of the following reasons:

  • The query execution timed-out in the Action Request System or your database.
  • The load on the server is heavy.

    Let your system stabilize, and wait for the server load to lessen. If the problem persists, other applications (such as Mid Tier, CMDB Explorer, and so on) are likely to experience similar problems, and you might need to restart your Action Request System and Notification Engine computers. If the problem was caused by a Action Request System timeout, set the client timeout values on the ARServerUser object as follows:
    ar.setTimeoutLong(arg0);
    ar.setTimeoutNormal(arg0);
    ar.setTimeoutXLong(arg0);

140507

This Notification Engine error message indicates that the subscription request failed due to runtime exceptions. Try your subscription request again. If the problem persists, review the server log to investigate the problem.

140508

This Notification Engine error message indicates that the subscription request failed because the subscription query is taking too long to process.
Consider making your query into smaller, sub-queries to avoid timeouts during subscription and at run time. Once you have reduced the large query into smaller pieces, try your subscription request again. Additionally, you can set the client timeout values on the ARServerUser by using the following parameters:
ar.setTimeoutLong(arg0);
ar.setTimeoutNormal(arg0);
ar.setTimeoutXLong(arg0);

140509

This Notification Engine error message indicates that the query execution timed-out in the Action Request System or your database. Set the client timeout values on the ARServerUser object by using the following parameters:
ar.setTimeoutLong(arg0);
ar.setTimeoutNormal(arg0);
ar.setTimeoutXLong(arg0);

140510

This Notification Engine error message indicates that the Notification Engine plugin API timed out. To resolve this problem, increase the Filter API RPC Timeout setting:

  1. In Mid Tier, open the AR System Administration Console.
  2. Select System > General > Server Information.
  3. On the Server Information form, click the Timeouts tab.
  4. In the Filter API RPC Timeout (seconds) field, enter a higher timeout setting.

140511

This Notification Engine error message indicates that the password used to connect the Notification Engine plugin server to the AR System server is incorrect. If you change the Action Request System Application Service password, you must also change that password in the Notification Engine plugin configuration file. Because the password is encrypted, perform the following steps to ensure that the passwords for the Notification Engine plugin server and AR System server are the same:

  1. Open the Action Request System configuration file (ar.cfg on Microsoft Windows and ar.conf on UNIX) for editing.
  2. Copy the encrypted password of the Remedy-App-Service-Password line.
  3. Open the installationDirectory/AtriumCore/cmdb/plugins/shared/ pluginsvr_config.xml file for editing.
  4. In the <! – Plugin for Notification engine --> section, paste the encrypted password between the opening and closing <ar_system_password> tags.
  5. Save the pluginsvr_config.xml file.
  6. Restart the AR System server.

Related topic

Enabling plug-ins

Troubleshooting-the-Notification-plug-in

Enabling-logs-for-the-plug-ins-server

Configuring-core-CMDB-components-and-plug-ins

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*