This message generates any of the following:
Reason:
The program Program-name called a non-Notification Manager service, and it received return code rc and error message error-text.
Action:
See the description for the message, xxxnnnny, where xxx is any message prefix, nnnn is the return code, and y is the message suffix. Follow the provided instructions.
Reason:
The Notification Manager program Program-name tried to send an acknowledgement to the CA Automation Point Merged Messages window, but it received return code rc from the ADDRESS AXC WTXC command.
Action:
See the description of the WTXC return code for more information.
Reason:
The Notification Manager program Program-name tried to send an acknowledgement to the CA NSM console, but it received return code rc from the ADDRESS TNG UNIWTO command.
Action:
See the description of the UNIWTO return code for more information.
Reason:
The Notification Manager program Program-name tried to use an ADDRESS AXC command, but it received return code rc from the command.
Action:
See the description of the AXC command return code for more information.
Reason:
The Notification Manager program Program-name tried to use an ADDRESS TNG command, but it received return code rc from the command.
Action:
See the description of the CA NSM command return code for more information.
Reason:
The specified subroutine was called with the incorrect number of arguments.
Action:
Contact CA Technical Support.
Reason:
Your Notification Manager voice groups are not configured properly.
Action:
Set up your voice groups using the Notification Voice Groups configuration utility, which is available from the CA Automation Point menu.
Reason:
Your Notification Manager voice groups are not configured properly.
Action:
Set up your voice groups using the Notification Voice Groups configuration utility, which is available from the CA Automation Point menu.
Reason:
Your Notification Manager voice groups are not configured properly.
Action:
Set up your voice groups using the Notification Voice Groups configuration utility, which is available from the CA Automation Point menu.
Reason:
Your VOX client is not configured properly.
Action:
Use the CA Automation Point Configuration Manager to configure your VOX client and notification server.
Reason:
Program Program-name called a non-Notification Manager service, and it received return code error-code and error message error-message.
Action:
See the description for the message, xxxnnnny, where xxx is any message prefix, nnnn is the return code, and y is the message suffix. Follow the provided instructions.
Reason:
The value of one or more user-supplied parameters is incorrect. The error-text explains the problem.
Action:
Specify a valid value.
Reason:
The Notification Manager method Program-name failed. The error-text explains the problem. A dump is sent to ASOTRACE.LOG.
Action:
Contact CA Technical Support and, if requested to do so, send in the ASOTRACE log files.
Reason:
Notification Manager called someone, but the call returned “Positive voice detection failed.” The error-text explains the problem. The call is considered to be a failure.
Action:
Determine whether there is a problem with your phone system.
Reason:
You specified invalid parameters or too few parameters. The error-text explains the problem.
Action:
Correct the parameters.
Reason:
Notification Manager successfully contacted someone, but the person did not respond to its queries. The error-text explains the problem.
Action:
Check your phone system.
Reason:
Notification Manager successfully contacted someone, but the person did not respond correctly to its queries. The error-text explains the problem.
Reason:
Speak to the person that Notification Manager contacted to determine why the person responded incorrectly.
Reason:
The user pressed the Ctrl-Break key combination in an attempt to stop the current notification request.
Action:
Avoid pressing this key combination.
Reason:
One or more methods were performed, but the methods failed to contact someone. The error-text explains the problem.
Action:
Change the time block definitions.
Reason:
No methods were performed due to the way the time blocks were specified. For example, if a contact method is not specified for Joe from 5 p.m. to 6 p.m. and Notification Manager tries to contact him during that time, it will not perform any methods. The error-text explains the problem.
Action:
Change the time block definitions.
|
Copyright © 2012 CA.
All rights reserved.
|
|