MSExchangeTransport 10001

PoisonMessage

Warning

%1 messages have reached or exceeded the configured poison threshold of %2. After the Microsoft Exchange Transport service restarted, these messages were moved to the poison message queue.

MSExchangeTransport 10003

PoisonMessage

Error

The transport process failed during message processing with the following call stack: %1.

MSExchangeTransport 10005

PoisonMessage

Error

The transport process couldn't load poison message information from the registry. Access to the registry failed with the following error: %1.

MSExchangeTransport 10004

PoisonMessage

Warning

The processing of Pickup file %1 caused the transport process to fail. Pickup file %1 will be renamed.

MSExchangeTransport 10006

PoisonMessage

Error

The transport process couldn't save poison message information to the registry. Access to the registry failed with the following error: %1.

MSExchangeTransport 10007

PoisonMessage

Error

The transport process couldn't remove poison message information from the registry. Access to the registry failed with the following error: %1.

MSExchangeTransport 1003

SmtpReceive

Error

The configuration of one of the SMTP Receive connectors is invalid. The configuration change will be ignored. The description of the configuration error is: %1.

MSExchangeTransport 1012

SmtpReceive

Warning

Receive connector %1: Authentication failures have exceeded the maximum of %2 for the connection from %3. Disconnecting.

MSExchangeTransport 1018

SmtpReceive

Warning

The account '%1' provided valid credentials, but it does not have submit permissions on SMTP Receive connector '%2'; failing authentication.

MSExchangeTransport 1020

SmtpReceive

Warning

The account '%1' provided valid credentials, but is not authorized to use the server; failing authentication.

MSExchangeTransport 1021

SmtpReceive

Warning

Receive connector %1 rejected an incoming connection from IP address %3. The maximum number of connections per source (%2) for this connector has been reached by this source IP address.

MSExchangeTransport 1022

SmtpReceive

Warning

Anti-spam agents are enabled, but the list of internal SMTP servers is empty. If there are any MTAs between this server and the Internet, populate this list by using the Set-TransportConfig cmdlet in the Exchange Management Shell.

MSExchangeTransport 1025

SmtpReceive

Error

SMTP rejected a (%4) mail from '%1' with '%2' connector and the user authenticated as '%3'. The Active Directory lookup for the sender address returned validation errors. %5

MSExchangeTransport 1028

SmtpReceive

Error

SMTP rejected a mail from '%1', sender '%4' on '%2' connector, and user authenticated as '%3'. The Active Directory directory service lookup for the FROM address returned the following error: %5

MSExchangeTransport 1034

SmtpReceive

Error

Initialization of inbound authentication failed with error %1 for Receive connector %2. The authentication mechanism is %3. The source IP address of the client who tried to authenticate to us is [%4].

MSExchangeTransport 1036

SmtpReceive

Error

Inbound direct trust authentication failed for certificate %1. The source IP address of the server that tried to authenticate to Microsoft Exchange is [%2]. Make sure EdgeSync is running properly.

MSExchangeTransport 11005

MessageSecurity

Error

Unable to validate the TLS certificate of the smart host for the connector %1. The certificate validation error for the certificate is %2. If the problem persists, contact the administrator of the smart host to resolve the problem.

MSExchangeTransport 11011

MessageSecurity

Error

A secure connection from domain-secured domain '%1' on connector '%2' failed to authenticate because validation of the Transport Layer Security (TLS) certificate failed with status '%3'. Contact the administrator of %1 to resolve the problem, or remove the domain from the domain-secured list.

MSExchangeTransport 11012

MessageSecurity

Error

A message from domain-secured domain '%1' on connector '%2' could not be authenticated because the server did not use Transport Layer Security (TLS). Contact the administrator for %1 to resolve the problem, or remove the domain from the domain-secured list.

MSExchangeTransport 11013

MessageSecurity

Error

The connection to secure domain '%1' on connector '%2' failed because Transport Layer Security (TLS) negotiation was unsuccessful. Error: '%3'. Please contact the administrator of %1 to resolve the problem.

MSExchangeTransport 11014

MessageSecurity

Error

A secure connection to domain secure domain '%1' on connector '%2' could not be established because TLS was not offered. Contact the administrator for %1 to resolve the problem or remove the domain from the domain-secured list.

MSExchangeTransport 11015

MessageSecurity

Error

A secure connection to domain secure domain '%1' on connector '%2' could not be established because TLS was not offered. Contact the administrator for %1 to resolve the problem or remove the domain from the domain-secured list.

MSExchangeTransport 11016

MessageSecurity

Error

Authentication of the connection to secure domain %1 failed because the Transport Layer Security (TLS) server certificate didn't contain the name of that domain. Either contact the administrator for domain %1 to resolve the problem with their certificate or remove the domain from the domain-secured list.

MSExchangeTransport 11017

MessageSecurity

Error

A message from domain-secured domain '%1' on connector '%2' failed to authenticate because no Transport Layer Security (TLS) certificate was supplied. Contact the administrator for %1 to resolve the problem, or remove the domain from the domain-secured list.

MSExchangeTransport 11018

MessageSecurity

Error

The message could not be received from domain-secured domain %1 because of a configuration error on Receive connector %2. You must set Transport Layer Security (TLS) as the authentication mechanism on the connector to receive messages from domain-secured domains.

MSExchangeTransport 11019

MessageSecurity

Error

The connection to secure domain '%1' on Send connector '%2' failed because Transport Layer Security (TLS) negotiation failed with response '%3'. Contact the administrator of secure domain '%1' to resolve the problem or remove the domain from the domain-secured list.

MSExchangeTransport 11020

MessageSecurity

Error

A secure connection to domain-secured domain '%1' on connector '%2' could not be established because the validation of the Transport Layer Security (TLS) certificate for %1 failed with status '%3. Contact the administrator of %1 to resolve the problem, or remove the domain from the domain-secured list.

MSExchangeTransport 12008

TransportService

Error

Microsoft Exchange couldn't read the Receive connector configuration. The service will be stopped.

MSExchangeTransport 12010

TransportService

Error

Microsoft Exchange couldn't load the Active Directory recipient cache performance counters %1.

MSExchangeTransport 12011

TransportService

Error

Microsoft Exchange couldn't register the service principal name %1: %2

MSExchangeTransport 12012

TransportService

Error

The internal transport certificate that is used for SMTP authentication by Microsoft Exchange could not be read from Active Directory. The certificate may be missing. If an existing certificate that matches the fully qualified domain name (FQDN) of the server is already installed, run the Enable-ExchangeCertificate cmdlet to publish this certificate to Active Directory. If a certificate for the FQDN of the server is not installed, create a certificate by running the New-ExchangeCertificate cmdlet for the FQDN of the server.

MSExchangeTransport 12013

TransportService

Error

Microsoft Exchange could not load the certificate with thumbprint of %1 from the personal store on the local computer. This certificate was configured for authentication with other Exchange servers. Mail flow to other Exchange servers could be affected by this error. If the certificate with this thumbprint still exists in the personal store, run Enable-ExchangeCertificate %1 -Services SMTP to resolve the issue. If the certificate does not exist in the personal store, restore it from backup by using the Import-ExchangeCertificate cmdlet, or create a new certificate for the FQDN or the server enabled for SMTP by running the following command: New-ExchangeCertificate -DomainName serverfqdn -Services SMTP.

MSExchangeTransport 12014

TransportService

Error

Microsoft Exchange could not find a certificate that contains the domain name %1 in the personal store on the local computer. Therefore, it is unable to support the STARTTLS SMTP verb for the connector %2 with a FQDN parameter of %1. If the connector's FQDN is not specified, the computer's FQDN is used. Verify the connector configuration and the installed certificates to make sure that there is a certificate with a domain name for that FQDN. If this certificate exists, run Enable-ExchangeCertificate -Services SMTP to make sure that the Microsoft Exchange Transport service has access to the certificate key.

MSExchangeTransport 12016

TransportService

Error

There is no valid SMTP Transport Layer Security (TLS) certificate for the FQDN of %1. The existing certificate for that FQDN has expired. The continued use of that FQDN will cause mail flow problems. A new certificate that contains the FQDN of %1 should be installed on this server as soon as possible. You can create a new certificate by using the New-ExchangeCertificate task.

MSExchangeTransport 12018

TransportService

Warning

The STARTTLS certificate will expire soon: subject: %1, thumbprint: %2, hours remaining: %3. Run the New-ExchangeCertificate cmdlet to create a new certificate.

MSExchangeTransport 12020

TransportService

Error

A secure connection to the domain %1 could not be established because the Transport Layer Security (TLS) certificate for the domain has expired. Contact the administrator for %1 to resolve the problem.

MSExchangeTransport 12021

TransportService

Warning

Microsoft Exchange detected a configuration change but couldn't read the updated Receive connector configuration. The configuration change will be ignored.

MSExchangeTransport 14001

Process

Error

The worker process with process ID %1 is not responding and will be forced to shut down.

MSExchangeTransport 14004

Process

Error

The worker process has failed to load application configuration file: %1.

MSExchangeTransport 15006

ResourceManager

Warning

Microsoft Exchange Transport is rejecting message submissions because the available disk space has dropped below the configured threshold.%1

MSExchangeTransport 15007

ResourceManager

Warning

The Microsoft Exchange Transport service is rejecting message submissions because the service continues to consume more memory than the configured threshold.%1.

MSExchangeTransport 16011

Configuration

Warning

MessageTrackingLog is enabled, but MessageTrackingLogPath is null. MessageTrackingLog will be disabled.

MSExchangeTransport 16013

Configuration

Warning

The SendProtocolLogPath parameter is set to $null. Setting the value of this parameter to $null disables protocol logging for all Send connectors on the server. No send protocol log is written.

MSExchangeTransport 16014

Configuration

Warning

The path to the protocol logging location for Receive connectors has not been set. Use the existing path.

MSExchangeTransport 16015

Configuration

Warning

The SendProtocolLogPath parameter is set to $null. Microsoft Exchange will continue to use the old location for protocol log storage.

MSExchangeTransport 16016

Configuration

Error

There is no default authoritative domain or the domain name is empty.

MSExchangeTransport 16017

Configuration

Error

Microsoft Exchange couldn't activate transport components because of the unexpected exception: %1.

MSExchangeTransport 16018

Configuration

Warning

A configuration update occurred but the internal %1 cache failed to load. Microsoft Exchange will retain the existing configuration. %2

MSExchangeTransport 16021

Configuration

Error

An accepted domain entry was damaged in Active Directory. Exchange is rejecting the configuration.

MSExchangeTransport 16023

Configuration

Error

Microsoft Exchange couldn't start transport agents. The Microsoft Exchange Transport service will be stopped. Exception details: %1 : %2.

MSExchangeTransport 16024

Configuration

Error

The data for an accepted domain entry included invalid data. Skipping record for %1.

MSExchangeTransport 16025

Configuration

Warning

No DNS servers could be retrieved from network adapter %1. Check if the computer is connected to a network and Get-NetworkConnectionInfo returns any results.

MSExchangeTransport 17001

Storage

Error

Column %3 in Extensible Storage Engine (ESE) table %2 from database %1 should contain data type %4, but instead it contains data type %5. The module that contains the database schema may have been updated and could be trying to open an older database. The old database must be removed before starting the Microsoft Exchange Transport service.

MSExchangeTransport 17002

Storage

Error

The non-nullable column %3 on the Extensible Storage Engine (ESE) table %2 from database %1 is part of the database schema but cannot be found in the actual database table. The module containing the database schema may have been updated and could be attempting to open an older database. The old database must be removed before starting the Exchange Server Transport service in Microsoft Exchange Server 2010.

MSExchangeTransport 17003

Storage

Error

%1: An operation has encountered a fatal error. The database may be corrupted. The Microsoft Exchange Transport service is shutting down. Manual database recovery or repair may be required. Exception details: %2

MSExchangeTransport 17004

Storage

Error

%1: An operation has encountered a fatal error. There wasn't enough disk space to complete the operation. The Microsoft Exchange Transport service is shutting down. The exception is %2.

MSExchangeTransport 17005

Storage

Error

%1: The database could not be opened because a log file is missing or corrupted. The Microsoft Exchange Transport service is shutting down. Manual database recovery or repair may be required. The exception is %2.

MSExchangeTransport 17006

Storage

Error

%1: The database could not be opened because the log file path that was supplied is invalid. The Microsoft Exchange Transport service is shutting down. The exception is %2.

MSExchangeTransport 17007

Storage

Error

%1: The database could not be opened because the database file does not match the log files. The Microsoft Exchange Transport service is shutting down. The exception is %2.

MSExchangeTransport 17011

Storage

Error

%1: The database could not be opened because the checkpoint file (.chk) is missing or corrupted. The Microsoft Exchange Transport service is shutting down. Manual database recovery or repair may be required. The exception is %2.

MSExchangeTransport 17101

Storage

Error

%1: MSExchangeTransport has detected a critical storage error but will not take any recovery actions. Manual actions should be taken to resolve issues encountered with this database (%2) and associated transaction logs (%3).

MSExchangeTransport 17102

Storage

Error

%1: MSExchangeTransport has detected a critical storage error and has taken an automated recovery action. This recovery action will not be repeated until the target folders are renamed or deleted. %2.

MSExchangeTransport 17104

Storage

Error

%1: MSExchangeTransport has detected a critical storage error but failed to complete the desired recovery action on %2 due to error %3.

MSExchangeTransport 17105

Storage

Warning

%1: MSExchangeTransport has detected a critical storage error and will now stop. The service attempted to update the registry key (%2) used to initiate automated recovery but failed with the following error: %3. Please make sure Network Service has Full Control to this registry key.

MSExchangeTransport 2000

SmtpSend

Warning

Send connector %1: A DNS failure occurred with the following diagnostic information %2.

MSExchangeTransport 2002

SmtpSend

Error

Send connector %1: an error occurred while connecting to %2.

MSExchangeTransport 2003

SmtpSend

Warning

Send connector %1 has failed to authenticate with %2. The response from the remote site is %3.

MSExchangeTransport 2006

SmtpSend

Warning

Send connector %1: the connection to %2 was disconnected by the remote server.

MSExchangeTransport 2011

SmtpSend

Error

A secure connection with Exchange server %1 could not be established because the protocol negotiation did not find a mutually supported hash algorithm. Modify the configuration of either %1 or this server so that one hash algorithm is supported by both servers.

MSExchangeTransport 2014

SmtpSend

Error

Failed to bind to SourceIPAddress '%1' configured on send connector '%2'.

MSExchangeTransport 2015

SmtpSend

Error

Send connector %1 couldn't connect to remote domain %2. The send connector requires Transport Layer Security (TLS) authentication, but is unable to establish TLS with the receiving server for the remote domain. Check this connector's authentication setting and the EHLO response from the remote server %3.

MSExchangeTransport 2016

SmtpSend

Error

An authentication credential initialization error %1 occurred with Send connector %2. The authentication mechanism used was %3. The name of the server that we were trying to authenticate to was %4. This server was using the name %5. Try reentering the credential. If the problem persists, contact Microsoft Support Services.

MSExchangeTransport 2017

SmtpSend

Error

Outbound authentication failed with error %1 for Send connector %2. The authentication mechanism is %3. The target is %4.

MSExchangeTransport 2018

SmtpSend

Error

Outbound direct trust authentication failed for certificate %1. The target IP address of the Exchange server that Microsoft Exchange tried to authenticate to is [%2]. Make sure EdgeSync is running properly.

MSExchangeTransport 2019

SmtpSend

Warning

Unable to transmit ORAR information to remote server '%1' over send connector '%2'. Message '%3' will not be delivered to recipient '%4'.

MSExchangeTransport 3004

Dsn

Error

The generation of the quarantine message may fail because of an error reading the spam quarantine mailbox configuration from the directory. The configuration data may be corrupt or the Active Directory directory service may be unreachable.

MSExchangeTransport 3005

Dsn

Error

An error caused by reading the SystemMessage configuration from the directory indicates that generation of delivery status notifications (DSNs) and storage quota is using out-of-date or incomplete message customizations. The configuration data may be corrupt, or the Active Directory directory service may be unreachable. The error was '%1'.

MSExchangeTransport 5001

Routing

Error

Microsoft Exchange couldn't load the routing performance counters: %1.

MSExchangeTransport 5002

Routing

Error

Microsoft Exchange couldn't load routing tables because the Active Directory directory service is unavailable. Microsoft Exchange will continue to use the existing routing table if one is available.

MSExchangeTransport 5003

Routing

Error

Microsoft Exchange couldn't load configuration information for routing. The process will block and retry the operation in %1 seconds.

MSExchangeTransport 5004

Routing

Error

Microsoft Exchange cannot obtain the fully qualified domain name (FQDN) of Exchange server %1 in routing tables with timestamp %2. Recipients will not be routed to this server.

MSExchangeTransport 5005

Routing

Error

The Active Directory site for Exchange server %1 was not determined in routing tables with timestamp %2. Recipients will not be routed to this server.

MSExchangeTransport 5006

Routing

Error

Cannot find route to Mailbox Server %1 for store %2 in routing tables with timestamp %3. Recipients will not be routed to this store.

MSExchangeTransport 5007

Routing

Error

The topology doesn't contain a route to Active Directory site %1 in routing tables with the timestamp %2. Recipients will not be routed to servers in this Active Directory site. Hub Transport server %3 is unreachable.

MSExchangeTransport 5008

Routing

Error

The topology does not contain any route to server %1 in Active Directory site %2 in routing tables with timestamp %3. Recipients will not be routed to this server.

MSExchangeTransport 5009

Routing

Warning

Microsoft Exchange cannot find the route to mailbox database %1 for public folder hierarchy %2 in routing tables with timestamp %3.

MSExchangeTransport 5010

Routing

Warning

No route has been created for public folder hierarchy %1 in routing tables with timestamp %2. Recipients will not be routed to this public folder. Check the routing logs for further information.

MSExchangeTransport 5011

Routing

Error

Source routing group %1 was not found for routing group connector %2 in routing tables with timestamp %3. Microsoft Exchange is skipping the connector.

MSExchangeTransport 5012

Routing

Error

Target routing group %1 was not found for routing group connector %2 in routing tables with timestamp %3; skipping the connector.

MSExchangeTransport 5013

Routing

Error

The routing group for Exchange server %1 was not determined in routing tables with timestamp %2. Recipients will not be routed to this server.

MSExchangeTransport 5014

Routing

Error

No source transport servers or home MTA server have been set for connector %1 in routing tables with timestamp %2. Ignoring the connector.

MSExchangeTransport 5015

Routing

Error

Microsoft Exchange cannot find a route to the source transport server or home MTA server %1 for connector %2 in routing tables with timestamp %3. Microsoft Exchange is ignoring the source transport server.

MSExchangeTransport 5016

Routing

Error

The Active Directory topology service could not discover any route to connector %1 in the routing tables with the timestamp %2. This connector will not be used.

MSExchangeTransport 5017

Routing

Error

Microsoft Exchange cannot find target bridgehead server %1 for routing group connector %2 in routing tables with timestamp %3. Microsoft Exchange is ignoring the target bridgehead server.

MSExchangeTransport 5018

Routing

Error

No target bridgehead servers were found for routing group connector %1 in routing tables with timestamp %2. Ignoring the routing group connector.

MSExchangeTransport 5019

Routing

Error

MSExchangeTransport found invalid smart hosts string %1 on SMTP connector %2 in routing tables with timestamp %3. MSExchangeTransport is ignoring the SMTP connector.

MSExchangeTransport 5020

Routing

Warning

The topology doesn't contain a route to Exchange 2000 Server or Exchange Server 2003 %1 in Routing Group %2 in routing tables with the timestamp %3.

MSExchangeTransport 5021

Routing

Error

The Exchange 2000 or Exchange 2003 server %1 was found in Exchange 2007 routing group %2 in routing tables with timestamp %3.

MSExchangeTransport 5023

Routing

Error

A transient configuration error was detected while the routing configuration was loading. Exception details: %1 : %2.

MSExchangeTransport 5024

Routing

Error

The maximum number of retries to load routing configuration data has been reached. The service will be stopped.

MSExchangeTransport 5025

Routing

Error

Non-SMTP address space '%1' was detected on the DNS SMTP connector '%2' in routing tables with timestamp %3. The address space is ignored on the connector because a non-delivery report (NDR) will be sent for the message or because the message will go to another connector. Exchange Server 2007 or Exchange 2010 tasks block this configuration. However, the connector may have been set up by Exchange Server 2003.

MSExchangeTransport 5026

Routing

Warning

Source servers belonging to different Active Directory sites were detected for connector '%1' in routing tables with timestamp %2. Only the closest site will be used and load-balancing will be affected.

MSExchangeTransport 5027

Routing

Error

Source routing group %1 was not found for the connector with connected routing groups %2 in routing tables with timestamp %3. Microsoft Exchange Transport is skipping the connector.

MSExchangeTransport 5028

Routing

Error

Source routing group %1 is the local routing group for a connector with connected routing groups %2 in routing tables with timestamp %3. Connectors with connected routing groups are only supported in routing groups with Exchange 2000 or Exchange 2003 servers.

MSExchangeTransport 5029

Routing

Error

Connected routing group %1 was not found for connector %2 in routing tables with timestamp %3.

MSExchangeTransport 5030

Routing

Error

Microsoft Exchange couldn't create routing table log file or directory %1. Exception details: %2 : %3.

MSExchangeTransport 5031

Routing

Error

Microsoft Exchange couldn't delete routing table log file %1. Exception details: %2 : %3.

MSExchangeTransport 5500

Logging

Warning

Transport pipeline tracing is active. This may degrade system performance.

MSExchangeTransport 7002

Components

Error

Database %1 is already in use. The service will be stopped. Exception details: %2

MSExchangeTransport 8004

RemoteDelivery

Error

A non-SMTP gateway connection failure occurred on connector %1. When writing to the drop directory %2, an I/O exception %3 occurred.

MSExchangeTransport 8005

RemoteDelivery

Error

A non-SMTP gateway connection failure occurred on connector %1. The drop directory quota limit of %2(MB) has been exceeded.

MSExchangeTransport 8007

RemoteDelivery

Error

Non-SMTP Gateway Connection Failure on Connector %1. The drop directory filename %2 exceeds the system-defined maximum length.

MSExchangeTransport 8008

RemoteDelivery

Error

A connection failure occurred on the foreign connector %1. The Drop directory %2 does not exist.

MSExchangeTransport 8009

RemoteDelivery

Error

Non-SMTP connector %1 failed because the Drop directory %2 does not have the correct access permissions. Change the access permissions for directory %2 or use another directory.

MSExchangeTransport 8010

RemoteDelivery

Error

A message with the Internal Message ID %1 was rejected by the remote server. This message will be deferred and retried because it was marked for retry if rejected. Other messages may also have encountered this error.

MSExchangeTransport 9002

Pickup

Error

The Pickup directory doesn't have the necessary Read permissions and Delete Subfolders and Files permissions for Pickup directory %1.

MSExchangeTransport 9003

Pickup

Warning

Read-only files have been found in the directory %1. Read-only files cannot be processed by the Pickup directory or the Replay directory. Please remove the read-only attributes or remove the read-only files.

MSExchangeTransport 9004

Pickup

Error

File(s) cannot be deleted from %1 by the Pickup directory. This may cause duplicate mail. Please verify that the Network Service account has "Delete Subfolders and Files" permission for this directory.

MSExchangeTransport 9005

Pickup

Error

The Pickup directory cannot submit the message because of database problems.

MSExchangeTransport 9006

Pickup

Error

The Microsoft Exchange Transport service failed to create the Pickup directory: %1. Pickup will not function until the directory is created. The detailed error is %2.

MSExchangeTransport 9007

Pickup

Error

File(s) cannot be opened or renamed in %1 by the Pickup directory. Some mail may not be processed by the Pickup directory. Please verify that the Network Service account has "Create Files" permission for this directory, and that files in the directory do not deny read access to the Network Service account.

MSExchangeTransport 9009

Pickup

Error

The Pickup directory doesn't have permissions to write the pickup location to registry (%1). Please make sure Network Service has Full Control to the registry location. The error was %2.

MSExchangeTransport 9010

Pickup

Error

At least one file in %1 can't be processed. These files have .bad extensions. Please look for .bad files, and make sure that their content is valid.

MSExchangeTransport 9201

Categorizer

Error

Transport agent (%1) running on the OnSubmittedMessage event did not handle a catchable exception: (%2).

MSExchangeTransport 9202

Categorizer

Error

Transport agent (%1) running on the OnRoutedMessage event did not handle a catchable exception: (%2).

MSExchangeTransport 9212

Categorizer

Error

Microsoft Exchange couldn't load the resolver performance counters: %1.

MSExchangeTransport 9213

Categorizer

Warning

A non-expirable message with the Internal Message ID %1 could not be categorized. This message may be a journal report or other system message. The message will remain in the queue until administrative action is taken to resolve the error. Other messages may also have encountered this error. To further diagnose the error, use the Queue Viewer or the Exchange Mail Flow Troubleshooter.

MSExchangeTransport 1009

SmtpReceive

Warning

Receive connector %1 rejected an incoming connection. The maximum number of connections (%2) for this connector has been reached.

MSExchangeTransport 18001

Agents

Error

Agent '%1' did not close the MIME stream after handling the %2 event for message with ID '%3'. The message has been rejected. Please report this problem to the agent vendor.

MSExchangeTransport 7007

Components

Information

Online defragmentation has completed for database %1. The database has %2 free bytes.

MSExchangeTransport 7006

Components

Information

Scheduled online defragmentation will start for database %1. The database has %2 free bytes.

MSExchangeTransport 7005

Components

Information

A new database file %1 has been created.

MSExchangeTransport 7004

Components

Information

The activation of all modules took longer than expected to complete. Total Load Time: %1 Total Start Time: %2 Load Time Breakdown: %3 Start Time Breakdown: %4.

MSExchangeTransport 2021

SmtpSend

Information

Unable to transmit RDST (Routing Destination) to remote server '%1' over send connector '%2'. Message '%3' will not be delivered to recipient '%4'.

MSExchangeTransport 2020

SmtpSend

Information

Unable to transmit long ORAR address '%1' to remote server '%2' over send connector '%3'. Message '%4' will not be delivered to recipient '%5'.

MSExchangeTransport 2007

SmtpSend

Information

Send connector %1 has initiated a new session to %2.

MSExchangeTransport 2005

SmtpSend

Information

Send connector %1: Errors occurred with the connection to %2. The connection was acknowledged with SMTP response %3.

MSExchangeTransport 2004

SmtpSend

Information

Send connector %1: Message delivery was not successful. The message with message ID %2 was acknowledged with SMTP response %3.

MSExchangeTransport 10002

PoisonMessage

Information

PoisonCount for the message with the record ID %1 has been incremented. The new value is %2.

MSExchangeTransport 1002

SmtpReceive

Information

The connectors have been configured.

MSExchangeTransport 1010

SmtpReceive

Error

Receive connector %1 rejected a message at SMTP end of data with %2.

MSExchangeTransport 1023

SmtpReceive

Error

SMTP rejected a message from '%1' with '%2' connector. The authenticated user '%3' doesn't have permission to submit e-mail messages to this server.

MSExchangeTransport 1024

SmtpReceive

Error

SMTP rejected a (%4) mail from '%1' with '%2' connector and user authenticated as '%3'. There was a transient Active Directory directory service exception thrown with the following information. %5.

MSExchangeTransport 1026

SmtpReceive

Error

SMTP rejected a (%4) mail from '%1' with '%2' connector. The user '%3' does not have permissions to send as this address.

MSExchangeTransport 1027

SmtpReceive

Error

SMTP rejected a mail from '%1', sender '%4' with '%2' connector and user authenticated as '%3'. The Active Directory lookup for the FROM address threw a transient Active Directory exception with the following information. %5

MSExchangeTransport 1029

SmtpReceive

Information

SMTP rejected a mail from '%1', sender '%4' with '%2' connector and user authenticated as '%3'. The sender does not have permissions to send on behalf of the FROM address.

MSExchangeTransport 1031

SmtpReceive

Error

The connection for user [%1] with IP address [%2] is being dropped. The rate of message submissions from this connection has exceeded the throttling policy of %3 per minute.

MSExchangeTransport 1033

SmtpReceive

Error

An exception was thrown while processing data from client IP address %1. The exception is %2.

MSExchangeTransport 1035

SmtpReceive

Error

Inbound authentication failed with error %1 for Receive connector %2. The authentication mechanism is %3. The source IP address of the client who tried to authenticate to Microsoft Exchange is [%4].

MSExchangeTransport 1037

SmtpReceive

Error

Failure occurred while trying to determine the Mailbox server for mailbox database [%1]. Message submission quota for user [%2] with IP address [%3] will not be enforced. Exception details: %4

MSExchangeTransport 1039

SmtpReceive

Error

SMTP rejected a message from '%1' on '%2' connector. The user was authenticated as '%3'. The Active Directory lookup returned the following error: %4.

MSExchangeTransport 11021

MessageSecurity

Warning

A secure connection to domain-secured domain '%1' on connector '%2' could not be established because the DomainSecureEnabled flag on the connector was not set. Set the DomainSecureEnabled flag or remove the domain '%1' from the domain-secured list.

MSExchangeTransport 11022

MessageSecurity

Error

Failed to confirm domain capabilities '%1' on connector '%2' because validation of the Transport Layer Security (TLS) certificate failed with status '%3'. Contact the administrator of '%4' to resolve the problem, or remove the domain from the TlsDomainCapabilities list of the Receive connector.

MSExchangeTransport 11023

MessageSecurity

Error

Connection to remote endpoint '%1 (%2)' for send connector '%3' is dropped because the server did not advertise the XOORG (Originator Organization) ESMTP protocol extension.

MSExchangeTransport 11024

MessageSecurity

Warning

Remote certificate with thumbprint '%1' contains '%2' subject alternative names and exceeds the limit of %3. Subject alternative names of this certificate will be ignored. The limit can be changed by adding/modifying the SubjectAlternativeNameLimit parameter in the EdgeTransport.exe.config file.

MSExchangeTransport 12002

TransportService

Information

A configuration update occurred.

MSExchangeTransport 12003

TransportService

Information

The configured server role is invalid for this process.

MSExchangeTransport 12009

TransportService

Error

Microsoft Exchange couldn't read the Receive connector configuration because the directory is unavailable. The service will be stopped.

MSExchangeTransport 12015

TransportService

Information

An internal transport certificate expired. Thumbprint:%1

MSExchangeTransport 12017

TransportService

Information

An internal transport certificate will expire soon. Thumbprint:%1, hours remaining: %2.

MSExchangeTransport 12019

TransportService

Information

The remote internal transport certificate expired. Certificate subject: %1.

MSExchangeTransport 12023

TransportService

Information

Microsoft Exchange could not load the certificate with thumbprint of %1 from the personal store on the local computer. This certificate was configured for authentication with other Exchange servers. Mail flow to other Exchange servers could be affected by this error. If the certificate with this thumbprint still exists in the personal store, run Enable-ExchangeCertificate %1 -Services SMTP to resolve the issue. If the certificate does not exist in the personal store, restore it from backup by using the Import-ExchangeCertificate cmdlet, or create a new certificate for the FQDN or the server enabled for SMTP by running the following command: New-ExchangeCertificate -DomainName serverfqdn -Services SMTP. Meanwhile, the certificate with thumbprint %2 is being used.

MSExchangeTransport 12024

TransportService

Information

Microsoft Exchange could not load the certificate with thumbprint of %1 from the personal store on the local computer. This certificate was configured for authentication with other Exchange servers. Mail flow to other Exchange servers could be affected by this error. If the certificate with this thumbprint still exists in the personal store, run Enable-ExchangeCertificate %1 -services SMTP to resolve the issue. If the certificate does not exist in the personal store, restore it from backup by using the Import-ExchangeCertificate cmdlet, or create a new certificate for the FQDN or the server enabled for SMTP by running the following command: New-ExchangeCertificate -DomainName serverfqdn -Services SMTP. Meanwhile, an ephemeral, self-signed certificate with thumbprint %2 is being used.

MSExchangeTransport 12025

TransportService

Warning

Transport service is disconnecting performance counters with process lifetime from their old process.

MSExchangeTransport 12026

TransportService

Error

Transport service failed to disconnect performance counters with process lifetime in category : %1 from their old process.

MSExchangeTransport 12028

TransportService

Warning

The process with processId %1 is holding the performance counter %2 from instance %3 and category %4 while running processes are: %5.

MSExchangeTransport 12029

TransportService

Information

The transport server is healthy for time: %1.

MSExchangeTransport 15004

ResourceManager

Warning

The resource pressure increased from %1 to %2.%3.

MSExchangeTransport 15005

ResourceManager

Information

The resource pressure decreased from %1 to %2.%3.

MSExchangeTransport 16012

Configuration

Warning

The path to the protocol logging location for Receive connectors has not been set. No protocol log for Receive connectors was written. The default location is C:\Program Files\Microsoft Exchange\TransportRoles\Logs\ProtocolLog\SmtpReceive.

MSExchangeTransport 16019

Configuration

Error

Active Directory directory service encountered an error for %1. Microsoft Exchange will retain the existing configuration, if available. Exception details: %2.

MSExchangeTransport 16022

Configuration

Information

A configuration update for %1 has successfully completed.

MSExchangeTransport 16026

Configuration

Information

Microsoft Exchange failed to query a network adapter to obtain the IP addresses assigned to it. Microsoft Exchange will continue to use previously loaded IP address information if available. The Microsoft Exchange Transport service will be stopped if this error occurred during service startup. Exception details: %1.

MSExchangeTransport 16027

Configuration

Information

The configuration for %1 has had to be forcibly loaded %2 time(s). There might be a problem with AD notifications.

MSExchangeTransport 16028

Configuration

Information

A forced configuration update for %1 has successfully completed. Object details from last notification based reload: %2. New details: %3.

MSExchangeTransport 17008

Storage

Information

The Microsoft Exchange Transport service has started the background scan of the queue database. All messages that have not yet been delivered will be loaded.

MSExchangeTransport 17009

Storage

Information

The background scan of the transport queue database has been stopped. %1 message(s) found so far. There may be other messages left in the database that have not yet been loaded.

MSExchangeTransport 17010

Storage

Information

The background scan of the transport queue database has completed. %1 message(s) were found.

MSExchangeTransport 17012

Storage

Error

%1: The database could not allocate memory. Please close some applications to make sure you have enough memory for Exchange Server. The exception is %2.

MSExchangeTransport 17013

Storage

Error

%1: The database could not be opened because there is another process using it. The Microsoft Exchange Transport service is shutting down. The exception is %2.

MSExchangeTransport 17014

Storage

Error

%1: The database could not be opened because there is no such database found. The Microsoft Exchange Transport service is shutting down. The exception is %2.

MSExchangeTransport 17015

Storage

Error

%1: The database could not be opened because it does not belong with the current set of log files. The Microsoft Exchange Transport service is shutting down. The exception is %2.

MSExchangeTransport 17016

Storage

Error

%1: An operation has encountered a fatal error. The database may be fragmented and manual offline defragmentation using ESEUTIL may be required. The Microsoft Exchange Transport service is shutting down. Exception details: %2

MSExchangeTransport 17017

Storage

Error

%1: Quota was exceeded while performing a database operation. The Microsoft Exchange Transport service is shutting down. Exception details: %2.

MSExchangeTransport 17018

Storage

Error

%1: There are insufficient resources to perform a database operation. The Microsoft Exchange Transport service is shutting down. Exception details: %2.

MSExchangeTransport 17019

Storage

Error

%1: A database operation has encountered an I/O error. The Microsoft Exchange Transport service is shutting down. Exception details: %2.

MSExchangeTransport 17020

Storage

Error

%1: A database operation has encountered a fatal error. The Microsoft Exchange Transport service is shutting down. Exception details: %2.

MSExchangeTransport 17021

Storage

Error

%1: Exchange couldn't open the database because it can't find a table. The Microsoft Exchange Transport service is shutting down. Exception details: %2.

MSExchangeTransport 17022

Storage

Error

%1: Exchange couldn't open the database because it can't find a file. The Microsoft Exchange Transport service is shutting down. Exception details: %2.

MSExchangeTransport 17023

Storage

Error

%1: The database could not be started because a critical database file has the read-only attribute set. The Microsoft Exchange Transport service is shutting down. Exception details: %2.

MSExchangeTransport 17103

Storage

Error

%1: MSExchangeTransport has detected a critical storage error and has taken an automated recovery action. %2.

MSExchangeTransport 17106

Storage

Information

%1: MSExchangeTransport has detected a critical storage error, updated the registry key (%2) and as a result, will attempt self-healing after process restart.

MSExchangeTransport 12022

TransportService

Information

The internal transport certificate that is used for SMTP authentication by Microsoft Exchange could not be read from Active Directory. The certificate may be corrupted. If an existing certificate that matches the fully qualified domain name (FQDN) of the server is already installed, run the Enable-ExchangeCertificate cmdlet to publish this certificate to Active Directory. If a certificate for the FQDN of the server is not installed, create an internal transport certificate by running the New-ExchangeCertificate cmdlet for the FQDN of the server.