The following table lists each logging code generated by the Email Binding Component and describes the cause of the log message along with the recommended action for you to take.
Logging Code |
Severity |
Message Text, Cause, and Action |
---|---|---|
EMAILBC-4001 |
Config |
PollerCount Value : [New='{0}', Old='{1}'] Cause: Action: |
EMAILBC-4002 |
Config |
ExchangeThreading Value : [New={0}, Old={1}] Cause: Action: |
EMAILBC-6001 |
Warning |
The WSDL message does not define corresponding part for input attribute {0}. An empty value is assumed. Cause: Action: |
EMAILBC-6002 |
Warning |
No "Subject" is specified. Cause: Action: |
EMAILBC-6003 |
Warning |
No "From" address is specified. Cause: Action: |
EMAILBC-6004 |
Warning |
Header "From" is not added because the value [{0}] does not represent valid address(es) Cause: Action: |
EMAILBC-6005 |
Warning |
No "To" address is specified. Cause: Action: |
EMAILBC-6006 |
Warning |
Recipient(s) is not added to "To" because the value [{0}] does not represent valid address(es) Cause: Action: |
EMAILBC-6007 |
Warning |
Recipient(s) is not added to "Cc" because the value [{0}] does not represent valid address(es) Cause: Action: |
EMAILBC-6008 |
Warning |
Recipient(s) is not added to "Bcc" because the value [{0}] does not represent valid address(es) Cause: Action: |
EMAILBC-6009 |
Warning |
Recipient(s) is not added to "newsgroups" because the value [{0}] does not represent valid address(es) Cause: Action: |
EMAILBC-6010 |
Warning |
The WSDL message does not define part: {0}. An empty value is assumed. Cause: Action: |
EMAILBC-6011 |
Warning |
No "Message body" is specified. Cause: Action: |
EMAILBC-6012 |
Warning |
Failed to embed/resolve src {0} image {1} Cause: Action: |
EMAILBC-6013 |
Warning |
The WSDL message does not define corresponding part for input attachment attribute {0}. An empty value is assumed. Cause: Action: |
EMAILBC-6014 |
Warning |
Redelivery option 'suspend' is not supported, if enabled, this will be handled like 'error' option Cause: Action: |
EMAILBC-7001 |
Severe |
EmailBCBootstrap installation MBean failed to initialize: {0} Cause: Action: |
EMAILBC-7002 |
Severe |
{0} does not support {1} exchange pattern Cause: Action: |
EMAILBC-7003 |
Severe |
Failed to complete exchange({0}) for endpoint({1}-{2}): {3} Cause: Action: |
EMAILBC-7004 |
Severe |
Error sending the message to the channel Cause: Action: |
EMAILBC-7005 |
Severe |
No folder with name "{0}" exists on the server Cause: Action: |
EMAILBC-7006 |
Severe |
Error retrieving emails Cause: Action: |
EMAILBC-7007 |
Severe |
Error while closing connection to the email folder/store Cause: Action: |
EMAILBC-7008 |
Severe |
Error marking message "{0}" as DONE Cause: Action: |
EMAILBC-7009 |
Severe |
Error marking message "{0}"as ERROR Cause: Action: |
EMAILBC-7010 |
Severe |
Failed to handle NM attachment [{0}]: {1} Cause: Action: |
EMAILBC-7011 |
Severe |
Attachment content is not specified. You can specify it by use of attribute {0} or {1}. Cause: Action: |
EMAILBC-7012 |
Severe |
Application Variables {0} are not defined but they are used in value [{1}]. Cause: Action: |
EMAILBC-7013 |
Severe |
Failed to create endpoint from EndpointInfo: {0}, and ServiceUnit: {1} Cause: Action: |
EMAILBC-7014 |
Severe |
Required field "{0}" is not specified, please specify value Cause: Action: |
EMAILBC-7015 |
Severe |
Invalid operation input definition in WSDL: {0}. It must be IMAPOperationInput or POP3OperationInput. Cause: Action: |
EMAILBC-7016 |
Severe |
Invalid attachment definition in WSDL: {0}. It must be IMAPAttachment or POP3Attachment. Cause: Action: |
EMAILBC-7017 |
Severe |
Invalid operation name: {0} for endpoint: {1} Cause: Action: |
EMAILBC-7018 |
Severe |
No binding input for operation: {0} Cause: Action: |
EMAILBC-7019 |
Severe |
No valid recipient address is specified for this email message. Cause: Action: |
EMAILBC-7020 |
Severe |
Invalid encoding style: [{0}] Cause: Action: |
EMAILBC-7021 |
Severe |
Invalid scheme "{0}": expected scheme is "{1}" Cause: Action: |
EMAILBC-7022 |
Severe |
IMAP address is missing, please specify the address in the wsdl. Service name: '{0}', Endpoint name : '{1}' Cause: Action: |
EMAILBC-7023 |
Severe |
IMAP Operation extensibility element is missing, please specify the imapoperation in the wsdl. Service name: '{0}', Endpoint name : '{1}' Cause: Action: |
EMAILBC-7024 |
Severe |
POP3 address is missing, please specify the address in the wsdl. Service name: '{0}', Endpoint name : '{1}' Cause: Action: |
EMAILBC-7025 |
Severe |
POP3 Operation extensibility element is missing, please specify the imapoperation in the wsdl. Service name: '{0}', Endpoint name : '{1}' Cause: Action: |
EMAILBC-7026 |
Severe |
SMTP address is missing, please specify the address in the wsdl. Service name: '{0}', Endpoint name : '{1}' Cause: Action: |
EMAILBC-7027 |
Severe |
SMTP Operation extensibility element is missing, please specify the imap operation in the wsdl. Service name: '{0}', Endpoint name : '{1}' Cause: Action: |
EMAILBC-7028 |
Severe |
Redelivery failed, DONE acknowledged: Message ID: {0} Cause: Action: |
EMAILBC-7029 |
Severe |
Redelivery failed, ERROR acknowledged: Message ID: {0} Cause: Action: |
EMAILBC-7031 |
Severe |
Cannot create the directory structure "{0}". Cause: Action: |