AAM Tab
The following table details possible messages that the Auto Alarm Manager may display during its operation, and lists potential solutions to the problem that the messages convey. These messages appear in the top half of the AAM tab in the Mission Control window.
Troubleshooting Auto Alarm Manager Messages in Mission Control
Message Solution
Cannot find the phone book entry The primary or secondary contact specified in the SCU is not defined in the RAS phone book. Create a phone book entry for each contact before continuing. Refer to your Microsoft manuals for instructions.
Hardware failure in port or attached device
The Auto Alarm Manager cannot communicate with the local modem. Verify that the cable connection between the modem and the computer is secure. If the problem
persists, try a different cable or modem.
Cannot detect carrier The Auto Alarm Manager could not establish a connection to the Receiving node. Make sure the RAS server is running. Also make sure the local modem detects a dial tone when it dials the primary or secondary contact.
ERROR_INTERACTIVE_MODE Do the following:
1. Select the phone book entry you want to edit.
2. From the Remote Access dialog box, click Edit. Click Advanced. If the Basic button appears, proceed to the next step.
3. Click Modem.
4. Clear the Enter Modem Commands Manually check box.
5. Close all open dialog boxes and exit the Remote Access program. The next time the Auto Alarm Manager dials, you should not receive an error.
Testing the connection...
Connection BAD After establishing RAS and iFIX connections, the Auto Alarm Manager on the Sending node sent a test message to the Receiving node and did not get a response. Make sure that Auto Alarm Manager is running on the Receiving node. If it is not, start it.
The account does not have remote
access permission The currently logged in user or the name of the user account specified in the Advanced Send Alarm Settings dialog box does not have the necessary rights to dial into
Troubleshooting Auto Alarm Manager Messages in Mission Control
Message Solution
the RAS server. Use the RAS Administrator program on the server node to grant dial-in rights to the necessary users.
All AAM session attempts failed The Auto Alarm Manager could not communicate with the Auto Alarm Manager on the remote node. Make sure the following conditions exist:
• The names of the primary and secondary contacts match the names of remote nodes associated with each RAS phone book entry. If they do not, edit the entries. Refer to your Microsoft manuals for more information.
• The Auto Alarm Manager is started with the correct command line parameter on the Sending and Receiving nodes. Use the /c parameter on the Sending node and the /s parameter on the
Receiving node. Refer to the Implementing Alarms and Messages e-book for more information.
• The Sending and Receiving nodes are not on the same LAN.
Error 1311 setting emergency tag The Auto Alarm Manager could not set the specified Emergency tag configured in the SCU. Some of the reasons for this could be:
• The specified TAG does not exist in the database.
• The specified NODE does not exist or is not reachable.
Error 1311 setting receive tag The Auto Alarm Manager could not set the specified Receive tag configured in the SCU. Some of the reasons for this could be:
• The specified TAG does not exist in the database.
• The specified NODE does not exist or is not reachable.
Disable tag can't be read The Auto Alarm Manager could not read the specified Disable tag configured in the SCU. Some of the reasons for this could be:
• The specified TAG does not exist in the database.
• The specified NODE does not exist or is not
Troubleshooting Auto Alarm Manager Messages in Mission Control
Message Solution
reachable.
If you get this error, the AAM will keep running, and it cannot be disabled.
NOTES:
• The AAMTCP.exe can only read from or write to a database tag on a local iFIX node. You cannot read or write to remote nodes. In other words, you cannot disable the Auto Alarm Manager from a tag on a remote node; it will always be running.
• You cannot set an Emergency tag or Receive tag on a remote node. It has to be on the same (local) node which the AAMTCP.exe is running on.
• You cannot acknowledge an alarm that comes from a remote node. For the alarm to be
acknowledged, it has to be from the same (local) node that the AAMTCP.exe is running on. If it is not, the alarm will still be sent to the Receiver node, but will not be acknowledged by the Sender node.
SQL Tab
You can display the setup and status of iFIX ODBC in Mission Control. Each status field is described in the following table.
System Task Status Codes Status Code Description
Alarm adi Displays the enabled alarm areas.
Debug adi Displays the enabled debug areas.
Alarm screen Indicates whether alarm messages are sent to the SQL task.
Yes = send messages; No = send no messages.
Debug
screen Indicates whether debug messages are sent to the SQL task.
Yes = send messages; No = send no messages.
Sql cmd tbl Name of the SQL Library Table.
System Task Status Codes Status Code Description
Sql err tbl Name of the SQL Error Log Table.
Sql cmd dbid Name of the Database Identifier specified in the SCU's SQL Task Configuration.
Prim file Primary back-up file.
Second. file Secondary back-up file.
Login delay Number of seconds to wait before attempting to login once a connection is lost. The default is 300 seconds.
Max sqlcmd Maximum SQL command length.
Nodename Name of the local node.
Current
status Identifies the status of the SQL task. This field can display whether the SQL task is logged onto one or several relational databases.
Caching
status Status of SQL caching.