Error Code Reference Guide › Exchange Server Agent Log › Exchange 2003 ESA Log Codes (SMTP Event Sink)

Exchange 2003 ESA Log Codes (SMTP Event Sink)

The following are error and informational log codes for the Exchange Server 2003 ESA (SMTP Event Sink) log file. The log files are named WgnSmtpS_datestamp.log.

E1B03 (Error 6915)

<count> emails are outstanding in the Policy Engine Hub.

Reason:

The SMTP Event Sink is shutting down while some emails are still outstanding in the Policy Engine Hub. The processing of these emails has been abandoned.

W1B04 (Warning 6916)

Re-loading the pending email with subject '<subject>' failed, error <error description>.
The email will re-load as if it had just been submitted.

Reason:

If the Exchange server is restarted or reset, emails currently being processed by the agent (that is, pending emails) are restored to their pending state. If restoring the state of an email fails, this message is logged. The email is reprocessed by the agent as if it has just been submitted.

I1B05 (Informational 6917)

Blocked email with subject '<subject>'.

Reason:

The email identified was blocked.

E1B06 (Error 6918)

Failed to block email with subject '<subject>'.

Reason:

An error occurred when blocking (deleting) an email. This may be caused by an external program accessing the SMTP Server message pipeline.

I1B07 (Informational 6919)

Applying failure mode: Deleted email with subject '<subject>'.

Reason:

Informational message. The processing of the email failed. Because Failure Mode is set to ‘delete’, this message reports that the email was successfully deleted.

E1B08 (Error 6920)

Applying failure mode: Should have deleted the email, but failed. Subject '<subject>'.

Reason:

The processing of the email identified failed. Failure Mode is set to ‘delete’, but deleting the email failed.

E1B11 (Error 6929)

Failed to issue a warning for email with subject '<subject>', error <error description>.

Reason:

Applying policy to the email with subject <subject> generated a warning event. Sending the warning email to the sender failed. The reason for the failure is given in <error description>.

I1B12 (Informational 6930)

Applying failure mode: The email was allowed to go. Subject '<subject>'.

Reason:

Informational message. The processing of the email failed. Because Failure Mode is set to ‘allow’, this message reports that the email was allowed to go.

E1B13 (Error 6931)

Failed to create and populate the Wigan event for email with subject '<subject>', error <error description>.

Reason:

The agent could not create the data needed by the Policy Engine Hub to process the email identified. The reason for the failure is given in <error description>.

I1B14 (Informational 6932)

The number of pending warned emails has exceeded 80% of the maximum allowed by configuration (MaxPendingWarnings=<count>).
Emails already pending will start heeding their warning automatically if the maximum is reached.

Reason:

Informational message.

W1B15 (warning 6933)

The number of pending warned emails has exceeded the maximum allowed by configuration (MaxPendingWarnings=<count>).
Emails already pending have started heeding their warning automatically.

Reason:

Informational message.

E1B16 (Error 6934)

Failed to read the configuration, error <error description>.

Reason:

One or more configuration settings may be incorrect, or an internal error may have occurred. The <error description> provides details.

E1B29 (Error 6953)

Failed to query email event for email store interface, error <error description>.

Reason:

Internal error.

E1B2A (Error 6954)

Sending action email: Failed to create a new CDO message, error <error description>.

Reason:

The cause of the error is given in <error description>. This error was generated by a Microsoft interface called Collaboration Data Objects (CDO). This error may occur if CDO is not correctly installed, or if insufficient memory is available.

I1B2B (Informational 6955)

Applying failure mode: The email was marked and allowed to go. Subject '<subject>'.

Reason:

Informational message. The processing of the email failed. Because Failure Mode is set to 'mark', this message reports that the email was marked and allowed to go.

E1B30 (Error 6960)

Failed to save email contents to file '<filepath>', error <error description>.

Reason:

You have requested to save the contents of emails to EML or EVF files, a diagnostic facility. There was a Windows file system error, <error description>, creating or writing to one of these files.

E1B32 (Error 6962)

Policy Engine Hub not installed.

Reason:

The Policy Engine Hub is not installed, or not correctly installed.

E1B33 (Error 6963)

Failed to create Policy Engine Hub, error <error description>. Entering failure mode.

Reason:

The Policy Engine Hub failed to launch. The cause of the error is given in <error description>. The agent is entering Failure Mode.

E1B34 (Error 6964)

Failed to retrieve local computer name, error <error description>. Entering failure mode.

Reason:

Failed to retrieve the local computer name to configure the Policy Engine Hub. This error could be caused by an incorrect Windows Installation, or by low memory. The agent is entering Failure Mode.

E1B35 (Error 6965)

Failed to register with Policy Engine Hub, error <error description>. Entering failure mode.

Reason:

The agent failed to register with the Policy Engine Hub. The cause of the error is given in <error description>. The agent is entering Failure Mode.

I1B36 (Informational 6966)

Successfully connected to the Policy Engine Hub.

Reason:

Informational message.

E1B37 (Error 6967)

Failed to configure the Policy Engine Hub, error <error description>. Entering failure mode.

Reason:

The agent failed to configure the Policy Engine Hub. The cause of the error is given in <error description>. The agent is entering Failure Mode.

E1B38 (Error 6968)

Failed to retrieve message status, error <error description>.

Reason:

Unable to load the Message Status property from the email. The email may be corrupt.

E1B39 (Error 6969)

Failed to map message contents into memory, error <error description>.

Reason:

Unable to load the email into memory. There may be insufficient memory. The email may be corrupt. The Windows error details are given in <error description>.

E1B3A (Error 6970)

Sending action email: failed to get root Body Part interface for new message, error <error description>.

Reason:

The cause of the error is given in <error description>. This error was generated by a Microsoft interface. This error may occur if you are short of memory.

E1B3B (Error 6971)

Sending action email: failed to add Body Part to new message, error <error description>.

Reason:

The cause of the error is given in <error description>. This error was generated by a Microsoft interface. This error may occur if you are short of memory.

E1B3C (Error 6972)

Sending action email: failed to get Data Source interface for original email, error <error description>.

Reason:

The cause of the error is given in <error description>. This error was generated by a Microsoft interface. This error may occur if you are short of memory.

E1B3D (Error 6973)

Sending action email: failed to embed message, error <error description>.

Reason:

The cause of the error is given in <error description>. This error was generated by a Microsoft interface. This error may occur if you are short of memory.

W1B3E (Warning 6974)

Sending action email: error adding subject to message, error <error description>.

Reason:

The cause of the warning is given in <error description>. This error was generated by a Microsoft interface. This warning may occur if you are short of memory.

W1B3F (Warning 6975)

Sending action email: error setting DSN Option to 'Never', error <error description>.

Reason:

The cause of the warning is given in <error description>. This error was generated by a Microsoft interface. This warning may occur if you are short of memory.

I1B40 (Informational 6976)

Skipping email already processed with subject '<subject>'.

Reason:

Informational message. The email message was detected as already processed by a previous agent, and has been skipped.

E1B41 (Error 6977)

SMTP On Message Submission event cannot be processed asynchronously.

Reason:

Reason: Internal error.

E1B42 (Error 6978)

Failed to create email context object, error <error description>.

Reason:

The cause of the error is given in <error description>. This error may occur if you are short of memory.

E1B43 (Error 6979)

Failed to create email callback object, error <error description>.

Reason:

The cause of the error is given in <error description>. This error may occur if you are short of memory.

E1B44 (Error 6980)

Failed to create email additional info object, error <error description>.

Reason:

The cause of the error is given in <error description>. This error may occur if you are short of memory.

E1B45 (Error 6981)

Failed to pass email with subject '<subject>' to hub, error <error description>. Retrying.

Reason:

Informational message.

E1B46 (Error 6982)

Giving up on email with subject '<subject>' because the hub won't start.

Reason:

Informational message.

E1B47 (Error 6983)

Giving up on email with subject '<subject>' due to hub error <error description>.

Reason:

Informational message.

E1B48 (Error 6984)

Initialization failure. Failed to create a synchronization event, error <error description>.

Reason:

During initialization, the program requested a synchronization event from Windows. Windows returned error <error description>.

E1B49 (Error 6985)

Initialization failure. Failed to create registry parameters object, error <error description>.

Reason:

The cause of the initialization failure is given in <error description>. This error may occur if you are short of memory.

I1B50 (Informational 6992)

SMTP Sink started in <mode> mode.

Reason:

Informational message.

I1B51 (Informational 6993)

SMTP Sink stopped.

Reason:

Informational message.

E1B52 (Error 6994)

Action on email with subject '<subject>' - Failed to submit an email to send to '<to address>', subject '<subject>', error <error description>.

Reason:

The processing of the email identified by <subject> generated a CA DataMinder message. An error occurred trying to send the CA DataMinder message. The error is given in <error description>.

I1B53 (Informational 6995)

Action on email with subject '<subject>' - A notification email sent to '<to address>' is empty.

Reason:

Informational message. The processing of the email message identified by <subject> generated a CA DataMinder message. The CA DataMinder message is empty. This may be due to an incorrect policy configuration.

E1B54 (Error 6996)

Action on email with subject '<subject>' - Failed to build a email to send to '<to address>', subject '<subject>', error <error description>.

Reason:

The processing of the email identified by <subject> generated a CA DataMinder message. An error occurred during the building of the CA DataMinder message. The error is given in <error description>.

E1B72 (Error 7026)

Failed to initialize due to error <error description>.

Reason:

The agent failed to initialize. The cause of the initialization failure is given in <error description>. This error may occur if you are short of memory or have ran out of some system resources.

I1B73 (Informational 7027)

Reading the configuration parameters following the detection of a potential change.

Reason:

Informational message.

I1B74 (Informational 7028)

Integration is currently disabled.

Reason:

Informational message.

I1B75 (Informational 7029)

Integration has been enabled.

Reason:

Informational message.

I1B76 (Informational 7030)

Integration has been disabled.

Reason:

Informational message.

E1B77 (Error 7031)

The configuration is invalid. Integration is staying disabled.

Reason:

Informational message.

E1B78 (Error 7032)

The new configuration is invalid and has been discarded. Integration is staying enabled with the previous configuration.

Reason:

Informational message.

I1B79 (Informational 7033)

The configuration has changed. Integration is staying enabled and is now using this new configuration.

Reason:

Informational message.

I1B7A (Informational 7034)

The registry setting '<setting>' is not set. Using its default value <value>.

Reason:

Informational message.

W1B7C (Warning 7036)

The changed value of the registry setting '<setting>' will not be picked up until IIS is restarted.

Reason:

The value of the registry setting <setting> has been changed, but the changed value needs a restart of IIS to be picked up by the agent.

I1B7D (Informational 7037)

Progress Summary: Processed <count>. Captured <count>. Excluded <count>. Failed <count>. Interactive warn pending <count>.

Reason:

Informational message displaying counts of email messages.

I1B7E (Informational 7038)

Captured. Message: '<subject>'.

Reason:

Informational message. The email identified was captured.

I1B7F (Informational 7039)

Excluded. Message: '<subject>'. Reason: <reason description>.

Reason:

Informational message. The email message identified was excluded from policy processing. The cause of the exclusion is given in <reason description>.

E1B80 (Error 7040)

Failed. Message: '<subject>'. Reason: <reason description>.

Reason:

The processing of the email message identified failed. The cause of the failure is given in <reason description>.

E1B81 (Error 7041)

Domain Mapping: Conflict: The domain '<domain>' in '<organization1>' is already defined in '<organization2>'.

Reason:

A domain defined for an organization (organization1) is already defined for another organization (organization2). The same domain cannot be used for more than one organization.

I1B82 (Informational 7042)

Domain Mapping: The sender email address '<address>' does not map to a domain.

Reason:

Informational.