Parameters Show a Negative Number

The notification command is failing at the notification server.

Fix the notification command. Run the notification script from the command line using the PATROL default user account. If the script fails, determine why. Possible reasons could include:

• The script has a typo
• The script may be in the wrong directory
• The script may lack an exit statement

If the script runs correctly, verify that you have entered the correct script name in your PATROL KM for Event Management rule. If you update the script, you must restart the PATROL Agent for the change to be recognized. For more information, see Testing Notification Scripts.

The PATROL default account does not have the proper permissions to execute the script file.

Check the permissions on the script file.

The PATROL Agent on the notification server is not running.

Verify that the PATROL agent on the notification server is running.

The remote notification event did not reach the notification server.

Resolve connection problems. Verify whether you can ping the notification server from the remote agent. Use the same hostname specified during notification configuration. For more information about configuring remote agents, see Configuring Remote Agents.

The remote agent is configured incorrectly.

Verify the rules have correct values.

• /AS/EVENTSPRING/ alertSystem must be set to REMOTE.
• /AS/EVENTSPRING/ NOTIFICATION_SERVER1.defaultAccount rule exists at the remote agent. If this rule is not present, you need to specify the notification server as described in Configuring Remote Agents.