The Analog Networking Agent (ANA) is responsible for transferring messages to and from remote systems using the Enterprise Networking and AMIS protocols.
The Analog Networking Agent is actually referred to in all events and alarms as two separate agents. The name "Enterprise Networking Agent" is used when the ANA is transferring messages using the Enterprise Networking protocol. The name "AMIS Networking Agent" is used when transferring messages using the AMIS protocol.
Severity Major
Description An internal program error occurred. This is really a class of errors, and it typically indicates that an abnormal situation occurred during the execution of the program. This could be, for example: a missing file, an error in execution of some system operations, or memory not being in its expected state.
Impact This error can affect the operation of AMIS Networking and/or Enterprise Networking in many ways, the most serious of which is where the local system is not able to send or receive messages using both of these networking protocols.
Recovery Action This problem typically should not occur sporadically, and would likely continue occurring as long as the system is running. However, it may occur once only, and then not happen again. In such case, no action needs to be taken.
If the problem is re-occuring, reboot the system during off-peak hours.
If the problem still occurs after the reboot, contact your customer service representative.
Note that this problem should always be reported to your customer service representative.
Technical Support Action Perform the following:
1. Verify that all administrator actions have been performed.
2. Inspect the Instance field of this event. Based on this value, you may be able to ascertain where during program execution the error occurs, and determine the cause of the problem.
3. If you cannot resolve the problem based on this information, contact your product support representative.
Severity Major
Description An error occurred communicating with the MTA.
Impact The current message could not be delivered. This may also indicate that the MTA is down, in which case most future message deliveries will fail.
Recovery Action Perform the following:
On the server, from Control Panel, Services, verify that the MCE MTA Service is started.
If the MCE MTA Service is not started, start it at this time.
If the MCE MTA Service is already started, it may have been down and has already been restarted by the system. If this is the case, leave it started. However, if this alarm still occurs at a later time, you need to restart the MCE MTA Service manually.
Technical Support Action Not Applicable
Severity Major
Description An error occurred opening a system mailbox.
Impact A message could not be delivered. The system mailbox in question may also be in an incorrect state, which can stop some or all message delivery on the local system.
Recovery Action Perform the following:
If this problem is occurring often, you may have to reboot the system in the near future to clear the error condition.
Otherwise, reboot the system during off-peak hours.
Technical Support Action Perform the following:
1. Verify that all administrator actions have been performed.
2. On the server, from Control Panel, Services, restart the MCE MTA Service. (Do this only when there are no active sessions in the MTA's queues - this can be checked using the MTA Monitoring support tool.)
3. The mailbox being reported in the event may be corrupt. Using the Message Package support tool, open this mailbox. Then list all messages in the mailbox. Both operations should be successful.
4. Report the results of the above steps to your product support representative.
Severity Minor
Description The telephone connection was lost during a networking session. This could mean that the remote system disconnected the call or that the telephone network connection to the remote system was lost.
Impact The current call could not be completed. If the call was outbound, the local system will retry the call according to the scheduling parameters defined for the protocol used in this call (AMIS or Enterprise Networking). If the call was inbound, it is up to the remote system to perform any retries as needed.
Recovery Action This situation may occur during normal system operation and normally no actions need to be performed when it occurs. However, if this situation persists, it should be investigated as it could be a symptom of a larger problem. Perform the following:
Contact the administrator at the remote site to see if any events were reported by the remote system at the same time as the local system reported the disconnect errors.
If the events reported at the remote site indicate errors other than disconnect then the problem is likely on the remote system so attempt to determine the problem based on those events.
If the events reported at the remote site indicate disconnect errors, the problem may be the local system hardware or the telephone network path between the local and remote systems. If this is the case:
Reboot the local server during off-peak hours.
Verify that he hardware on the local and remote systems is working properly
Inspect the cabling on the local and remote systems including the AML link connections
If the problem still persists, contact your telephone network administrator and attempt to diagnose the problem.
Technical Support Action Verify that all administrator actions have been performed.
Attempt to find the location of the problem by inspecting the "Instance" field of the event.
If no solution can be found, contact customer support.
Severity Minor
Description A violation of the AMIS or Enterprise Networking protocol occurred during a networking session. In most cases this indicates a transient error such as a timeout during the session, incorrect data received (e.g. due to noisy telephone line), etc. However, if persistent, this could indicate that the protocols used at the local and remote systems are incompatible.
Impact If this event is not persistent, a message could not be delivered, and the system will re-attempt to send it. If this event is persistent, the protocols used by the local and remote systems may not match, and message transmission may not work between the two systems.
Recovery Action This situation may occur during normal system operation, and normally no actions need to be performed when it occurs. However, if this situation persists, it should be investigated, as it could be a symptom of a larger problem:
Contact the administrator of the remote system to verify that the local and remote systems use the same protocol (Enterprise Networking or AMIS) for sending messages to each other. If they do not match, correct this.
If the problem still occurs in a large volume, contact the administrator of the remote system to see if any events are reported by the remote system at the same time as the local system reported the protocol errors. If they exist, attempt to determine the cause of the problem based on those events.
If you have difficulty determining the problem, finding a solution, or completing any of the above steps, contact your customer service representative.
Technical Support Action Perform the following:
1. Verify that all administrator actions have been performed.
2. Determine the quality of the telephone connection between the local and remote systems. If the quality is poor (i.e. very noisy), this could be the cause of these errors, and should be corrected.
3. Attempt to find the location of the problem by inspecting the Instance field of the event.
4. If no solution can be found, contact your product support representative.
Severity Minor
Description A remote system encountered a condition that made continuing communication impossible.
Impact A message could not be transmitted to or from the local system. This is caused by an error condition at the remote system.
Recovery Action If this situation persists, contact the administrator of the remote system to determine why the remote system is aborting the session, using the events reported there.
Technical Support Action If this situation persists, contact the administrator of the remote system to determine why the remote system is aborting the session, using the events reported there.
Severity Major
Description The Initiating Passwords used by the local and remote sites when sending Enterprise Networking messages to each other do not match. This is a configuration error.
Impact Enterprise Networking messages cannot be transmitted successfully between the local and remote sites until this problem is corrected.
Recovery Action Contact the administrator of the remote site and inspect the Initiating Passwords that the local and remote sites use for sending Enterprise Networking messages to each other. Make sure the Initiating Passwords are the same.
Technical Support Action Not Applicable
Severity Major
Description The Responding Passwords used by the local and remote sites when sending Enterprise Networking messages to each other do not match. This is a configuration error.
Impact Enterprise Networking messages cannot be transmitted successfully between the local and remote sites until this problem is corrected.
Recovery Action Contact the administrator of the remote site and inspect the Responding Passwords that the local and remote sites use for sending Enterprise Networking messages to each other. Make sure the Responding Passwords are the same.
Technical Support Action Not Applicable
Severity Major
Description During an incoming Enterprise Networking session, an invalid local Enterprise site Id was received from a remote site. This means that the local site's Enterprise site Id that is defined on the remote site is incorrect.
Impact Enterprise Networking messages cannot be received successfully from the remote site until this problem is corrected.
Recovery Action Contact the administrator of the remote site and inspect the local site's Enterprise site Id defined on the remote site. Make sure it is the same as the actual local site's Enterprise site Id.
Technical Support Action Not Applicable
Severity Major
Description The networking protocols which the local and remote sites use for to send messages to each other do not match. This is a configuration error.
Impact Messages cannot be received successfully from this remote site until this problem is corrected. Messages also likely cannot be sent to this remote site until this correction is made.
Recovery Action Contact the administrator of the remote site and inspect the protocols that the local and remote sites use for sending messages to each other. Make sure the protocols are the same.
Technical Support Action Not Applicable
Severity Major
Description An error occurred reading the database. This can be a problem with reading specific data from the database, or with general database access. The latter is more serious.
Impact This event can indicate that AMIS and/or Enterprise Networking messages cannot be sent and/or received. It can also indicate that these messages cannot be send and/or received to or from a particular remote system. In the most serious case, this event indicates that the database has become inaccessible by the system, which makes the entire system inoperational.
Recovery Action Perform the following:
If other components are reporting the same problem, or if you do require the affected operations (for example, the sending of AMIS messages) to work immediately, reboot the system as soon as possible.
Otherwise, reboot the system during off-peak hours.
Technical Support Action Not Applicable
Severity Minor
Description A non-serious internal program error occurred and was ignored. This type of error does not stop the transmission of a message.
Impact Messages can still be transmitted, but not all supported features are available.
Recovery Action This problem typically should not occur sporadically, and would likely continue occuring as long as the system is running. However, it may occur once only, and then not happen again. In such case, no action needs to be taken.
If the problem is re-occuring, reboot the system during off-peak hours.
If the problem still occurs after the reboot, contact your customer service representative.
Technical Support Action Perform the following:
1. Verify that all administrator actions have been performed.
2. Inspect the Instance field of this event. Based on this value, you may be able to ascertain where during program execution the error occurs, and determine the cause of the problem.
3. If you cannot resolve the problem based on this information, contact your product support representative.
Severity Minor
Description Initiating and/or responding Enterprise password are incorrect.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Debug
Description Not Applicable
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Debug
Description Not Applicable
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Major
Description An error has occurred reading the message on disk.
Impact The message could not be delivered and will be returned to the sender with a Non-Delivery Notification. If this is occuring repeatedly, it can indicate a more serious problem, e.g.a faulty condition of the file system, hard drive, etc., in which case the impact could be much greater.
Recovery Action If the problem is occuring repeatedly, reboot the system during off-peak hours. If this does not resolve the problem, contact your customer service representative.
Technical Support Action Perform the following:
1. Verify that all administrator actions have been performed.
2. The message in question could be corrupt. Open the message using the Message Package support tool, and check if its contents are correct.
3. Attempt to find the location of the problem by inspecting the Instance field of the event.
4. Report your findings to your product support representative.
Severity Major
Description A message submitted for sending to remote site had invalid contents and could not be delivered.
Impact The message could not be delivered and will be returned to the sender with a Non-Delivery Notification. If this is occuring repeatedly, it can indicate a more serious problem, e.g.a faulty condition of the file system, hard drive, etc., in which case the impact could be much greater.
Recovery Action If the problem is occuring repeatedly, reboot the system during off-peak hours. If this does not resolve the problem, contact your customer service representative.
Technical Support Action Perform the following:
1. Verify that all administrator actions have been performed.
2. The message in question could be corrupt. Open the message using the Message Package support tool, and check if its contents are correct.
3. Attempt to find the location of the problem by inspecting the Instance field of the event.
4. Report your findings to your product support representative.
Severity Minor
Description A message that was submitted for transmission to remote system could not be sent using this networking protocol. This could mean that an end-user has sent an message with fax and/or text content to an Enterprise Networking or AMIS destination, or a message longer than 8 minutes to an AMIS destination. This could mean that the length of sender or recipient mailboxes in this message are not supported by this protocol. (e.g. AMIS supports mailboxes of maximum length of 16 digits, Enterprise Networking of length at most 18 digits.)
Impact The message is returned as an Non-Delivery Notification to the sender. The sender may attempt to forward this message to the same destination, which will result in another Non-Delivery Notification unless the protocol for this destination is changed.
Recovery Action Perform the following:
Make known to the end-users what features are and are not supported when sending messages to different remote sites.
You can also consider changing the protocol for the remote site for which this problem occurs.
If AMIS messages longer than 8 minutes are not being sent to the remote site, consider changing the protocol for this remote site to Enterprise Networking or VPIM, which support longer messages.
If text and/or fax cannot be sent to this remote site, consider changing the protocol for this remote site to VPIM, which supports voice, fax and text.
Technical Support Action Not Applicable
Severity Minor
Description Message contains an address with an invalid switch location or recipient.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Major
Description An error occurred opening the spoken name of the sender of a message. The message was sent without the sender's spoken name.
Impact A message was transmitted to a remote site but the sender's spoken name was not sent. The sender's spoken name stored at the remote site was therefore not updated and may not be recent, or may not exist at all.
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Minor
Description A problem occurred on a remote server, while it was preparing to receive a message sender's spoken name. The message was sent without the spoken name.
Impact The spoken name of the sender was not sent to the remote site and not updated on there. This may mean that the entire remote site will not accept spoken names, or that spoken names will be rejected only for messages sent by a particular local user.
Recovery Action If this problem occurred a few times only, it's possible that is has already been corrected at the remote site. Otherwise, if this problem is re-occuring, you may have to point this problem out to the remote site administrator.
Technical Support Action Not Applicable
Severity Minor
Description Remote site aborted the session from the local system because it received invalid data from the local site. In most cases, this is caused by noise on the telephone line causing data being sent to become corrupted. It may also indicate an inconsistent memory state of the local system.
Impact The message could not be delivered. If this problem is re-occuring, it may indicate that no Enterprise Networking or AMIS messages can be sent out.
Recovery Action If this problem occurs sporadically, it is most likely caused by a noisy telephone line, and normally no actions need to be performed when it occurs. However, if this situation persists, it should be investigated:
Test the telephone path from the local site to the remote site. (Simply place several telephone calls to all Connection DNs of the remote site and listen for any noise.) If the line is noisy, this is likely the cause of the problem, and should be corrected. (Contact your telephone network administrator to do this.)
If you don't notice any noise, there may be a inconsistent memory state on the local system. Reboot the local system during off-peak hours.
If you have difficulty determining the problem, finding a solution, or completing any of the above steps, contact your customer service representative.
Technical Support Action Perform the following actions
1. Verify that all administrator actions have been performed.
2. Attempt to find the location of the problem by inspecting the Instance field of the event.
3. If no solution can be found, contact your product support representative.
Severity Major
Description The remote system is not accepting the networking protocol used in this call (Enterprise Networking or AMIS).
Impact Messages cannot be sent to this remote system using this protocol.
Recovery Action This is a configuration error. Perform the following actions:
Determine the remote system in question from the event description. (The remote system is the first item following the Info: text in the event description.)
For Enterprise Networking and Integrated AMIS, the remote server is identified in the event description by its name. Verify that this remote server supports this protocol (e.g. by contacting the remote server administrator), and if not, change the protocol to one that is supported.
For Open AMIS, the remote system is identified in the event description by its System Access Number. Make sure that your local users do not send AMIS messages to this system, as it does not support AMIS.
Technical Support Action Not Applicable
Severity Major
Description A remote site rejected the Enterprise site ID sent to it from the local site, which means that a configuration mismatch between the local and remote sites exists.
Impact Messages cannot be sent to this remote site, and likely also cannot be received from this remote site.
Recovery Action Perform the following actions:
Check if the remote site also reported errors at the time of this event. If not, the local system is calling the wrong remote site. Make sure that the remote site defined on the local system has correct Connection DN(s).
Inspect the remote site defined on the local system, and make sure that it contains the actual Enterprise site Id of the remote site.
Contact the administrator of the remote site, inspect the local site defined on the remote system, and make sure that it contains the actual Enterprise site Id of the local site.
If the above steps still do not resolve the problem, contact your customer service representative.
Technical Support Action Perform the following actions:
1. Verify that all administrator actions have been performed.
2. Attempt to find the location of the problem by inspecting the Instance field of the event.
3. If no solution can be found, contact your customer service representative.
Severity Major
Description A remote system has rejected a message because it considered it too long.
Impact The message could not be delivered. Other messages of similar length will not be delivered.
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Minor
Description The remote system is not accepting networking calls. This typically indicates that the remote system administrator has temporarily disabled the receiving of networking messages, e.g. because the remote system disk is full.
Impact Messages will not be delivered to this remote system while it is not accepting networking calls.
Recovery Action Perform the following actions:
If this problem persists, contact the remote server administrator and find out the reason and duration of this situation.
If the duration is extensive, consider disabling the message transfer to this system (this applies to Enterprise Networking and Integrated AMIS servers). Also consider informing local users of this situation, so they won't send messages to this remote system unnecessarily.
Technical Support Action Not Applicable
Severity Minor
Description The remote system's disk is full.
Impact Messages cannot be sent to the remote system.
Recovery Action Perform the following actions:
If the problem is persisting, contact the remote system administrator and determine the expected duration of the disk full condition.
If the expected duration is long, consider informing the local users of this condition. If the remote system is defined in the local Messaging Network Configuration, also consider temporarily disabling message transfer to this system.
Technical Support Action Not Applicable
Severity Minor
Description Outbound networking call was not answered by a computer system. It may have been answered by a human being.
Impact A message could not be delivered. Transmission of messages to this destination may be suspended.
Recovery Action Perform the following actions:
If the remote system is defined in the local Messaging Network Configuration, verify that its configuration is correct, especially its Connection DN(s).
If the remote system is not defined in the local Messaging Network Configuration, further transmission of messages to this number will be suspended by the local system. Verify that the number is correct. (This number was entered by the end-user.) It is very likely incorrect, in which case, make sure local users enter remote system numbers correctly.
If you cannot determine the cause of the problem, contact your customer service representative.
Technical Support Action Perform the following actions:
1. Verify that all administrator actions have been performed.
2. If no solution can be found, contact your customer service representative.
Severity Minor
Description The local system was unable to start a networking session to a remote system.
Impact A message could not be delivered. In most cases, the delivery of this message will be retried by the local system and should succeed.
Recovery Action Normally, no action is required. However, if this problem persists, you must do the following:
If the remote system is defined in the local Messaging Network Configuration, verify that its configuration is correct, especially its Connection DN(s).
If the remote system is not defined in the local Messaging Network Configuration, verify that the number of the remote system is correct. (This number was entered by the end-user.)
Verify that the remote system is working and accepting networking calls. (Contact the remote system administrator if necessary.)
Verify that the telephone path from the local system to the remote system is working. To do this, place a call from a telephone set on the local system to the remote system number found in the event description. The call should be answered. If it is not answered, do the following:
Verify that the hardware on the local and remote systems is working properly.
Inspect the cabling on the local and remote systems, including the AML link connections.
If still without a solution, contact your telephone network administrator, and attempt to diagnose the problem with their help.
If you cannot determine the cause of the problem, contact your customer service representative.
Technical Support Action Perform the following actions:
1. Verify that all administrator actions have been performed.
2. If no solution can be found, contact your customer service representative.
Severity Major
Description No valid connection DN is available to call a remote messaging server.
Impact Calls cannot be placed to to this messaging server, and messages cannot be sent there. This problem may also be an indication of a more serious problem.
Recovery Action Perform the following actions:
On the local system, under Messaging Network Configuration, inspect the 3 connection DNs for this remote server. Make sure that at least 1 connection DN is defined, and everyl Connection DN defined is valid (i.e. only contains characters 0-9, *, and # for AMIS). If not change the incorrect connection DN(s).
If the DN(s) are correct, and the problem is still occuring, re-add the connection DN(s) already defined there.
If the problem still does not resolve, contact your customer service representatiave.
Technical Support Action Perform the following actions:
1. Verify that all administrator actions have been performed.
2. Inspect the database using Network Package to verify that a correct DN is stored there. If not, it needs to be changed, also using Network Package.
3. If this does not resolve the problem, contact your customer service representative.
Note: You should always contact your customer service representative when this problem occurs.
Severity Minor
Description The sender of an AMIS message does not have permission to send messages to this number. (The sender's Restriction/Permission Lists do not allow it.)
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Perform the following actions:
1. Check the sender's Mailbox Class and its AMIS Restriction/Permission Lists, and verify that the number is indeed restricted. If not, then there may be a problem with data consistency on the system.
2. Contact your customer service representative.
Severity Information
Description Inbound Enterprise Networking session was rejected because inbound Enterprise Networking was disabled.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Information
Description Inbound AMIS Networking session was rejected because inbound AMIS Networking was disabled.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Major
Description Inbound message rejected; the local system''s disk is full.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Minor
Description Incoming session rejected; the local system''s disk is almost full.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Minor
Description An address that was received in an Enterprise Networking message does not reside on a site and/or location known by the local system. Either the Enterprise site Id or Enterprise location Id (or both) indicated in the address are not defined in the local Messaging Network Configuration.
Impact If the Enterprise site ID specified in the description is the same as that of the local site, the message was rejected. Otherwise, the message was received and the address was written to the message as being at an unknown site.
Recovery Action The remote site's definition of the messaging network is different from that of the local site. For example, the remote site may exchange messages with a site that is not defined on the local system. This may be normal and expected operation, in which case no action needs to be taken.
However, if the Enterprise site ID specified in the description belongs to the local site, then the remote site's definition of the local site needs updating, as it is out of date. This applies specifically to the remote site's definition of the Enterprise location ids of the local site.
Otherwise, you may choose to change your Messaging Network Configuration to now contain the previously-unknown messaging server and/or switch location.
Technical Support Action Check that all administrator actions have been performed.
Severity Major
Description Local site aborted the session from the remote system because it received invalid data from the remote system. In most cases, this is caused by noise on the telephone line causing data being sent to become corrupted. It may also indicate an inconsistent memory state of the local or remote system.
Impact The message could not be received If this problem is re-occuring, it may indicate that no Enterprise Networking or AMIS messages can be received.
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Minor
Description Invalid data received but ignored. Continuing with session...
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Major
Description Inbound session rejected; invalid remote Enterprise site id.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Major
Description Error writing to a message.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Major
Description Error creating a message.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Major
Description Error deleting a message already submitted for local delivery.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Minor
Description Failed to set up inbound networking call from remote system.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Minor
Description No data received at the start of an incoming call.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Minor
Description Inbound session rejected; invalid data received at start of session. It is possible that callers are calling in onthe AMIS/EN SDN.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Minor
Description Inbound session rejected; invalid data received after the start of session.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Major
Description The database is full.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description Error event occurred.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description Internal error occurred.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description Item was not found.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description Internal error: invalid address list.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description Internal error: invalid message type.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description Internal error: invalid message body type.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description Internal error: file is already in use.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description Incorrect DN.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description Invalid address (e.g. address does not exist).
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description Invalid location (e.g. location does not exist).
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description Internal error occurred.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description Internal error: invalid message body position.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description Spoken name does not exist.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description The disk is full.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable