Troubleshoot Secure Email Alert Message

Available Languages

Download Options

  • PDF     (24.7 KB)
    View with Adobe Reader on a variety of devices
  • ePub     (81.3 KB)
    View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
  • Mobi (Kindle)     (66.9 KB)
    View on Kindle device or Kindle app on multiple devices
Updated:August 25, 2026
Document ID:222558

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Introduction

This document describes identifying, troubleshooting, and resolving the "An application fault occurred" error. 

Prerequisites

Requirements

Cisco recommends that you have a basic understanding of the Cisco Secure Email Gateway or Cisco Secure Email Cloud Gateway.

Components Used

This document is not restricted to specific software and hardware versions.

The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, ensure that you understand the potential impact of any command.

Background Information

This document also provides a more detailed overview of some common application faults.

An alert is received after a process crashes.

note-icon

Note: Most application faults are self-resolving and are safe to ignore; however, there are a few that require intervention in order to bring the device back to normal operation.  For example, the Aquarium.py screenLoop application faults are usually indicative of too many clicks within a short span inside the GUI and are safe to ignore.  If you are noticing strange behavior or other impact after receiving the error, then proceed to open up a Cisco TAC case for assistance using the Cisco Support Case Manager.

Common Application Faults

An additional context surrounding some existing application faults has been provided and the list is kept updated. If you believe that something can be added, then let us know.

[ENH] Option to suppress alert Critical: An application fault occurred Network communication error: Connection refused:

Critical: An application fault occurred: ('egg/command_client.py connect|145', "<class 'Commandment.CommunicationError'>", 'ironport.example.com: Network communication error: Connection refused', '[egg/omh.py queue_worker_thread|4211] [egg/omh.py process_item|5130] [egg/command_client.py quick_read_var_auto_level|712] [egg/command_client.py connect|145]') MID: XXXXXX

Application fault triggered by uppercase recipient address matching alias table domain context Cisco bug ID CSCws09183: 

Critical: An application fault occurred: ('egg/alias.py get|205', "<type 'exceptions.KeyError'>", "'NoReply_Cisco@cisco.example.com'", '[egg/smtp_server.py main|785] [egg/smtp_server.py cmd_rcpt|2024] [egg/injector.py enqueue_rcpt|1938] [egg/alias.py get|205]') MID: 1219

Related Information

Revision History

Revision Publish Date Comments
2.0
25-Aug-2026
Formatting, links
1.0
03-Nov-2024
Initial Release
TAC Authored

Contributed by Cisco Engineers

  • Dennis McCabe Jr
    Cisco Technical Leader

Was this Document Helpful?

FeedbackFeedback

Contact Cisco

This Document Applies to These Products