Exchange Server 2016
- The maximum Extensible Storage Engine (ESE) cache on server {2} is set too high and is causing low virtual memory conditions. ...
- The maximum incoming message size is set too high. This can cause reliability problems. Current maximum message size is {9} ...
- The maximum incoming message size maybe set too low. An administrative error may have occurred. Current maximum message size ...
- The maximum incoming message size maybe set too low. An administrative error may have occurred. Maximum message size is {9} ...
- The maximum LDAP page size for the default query policy is set at a recommended level. The default of 1000 is recommended. ...
- The maximum LDAP page size for the default query policy is set too high and may cause performance problems. The default of ...
- The maximum LDAP page size for the default query policy is set too high. If this value is set too high, it can cause performance ...
- The maximum non-paged pool memory on server {2} is over the error threshold of {8} MB. System instability may occur. Current ...
- The maximum non-paged pool memory on server {2} is over the error threshold of {8} MB. This may cause system instability. ...
- The maximum non-paged pool memory on server {2} is over the warning threshold of {8} MB. System instability may occur. Current ...
- The maximum non-paged pool memory on server {2} is over the warning threshold of {8} MB. This may cause system instability. ...
- The maximum number of bytes that a Live Views web sandbox fetch (HTML, JSS, or CSS) can have in the transformation pipeline. ...
- The maximum number of cached views ('msExchMaxCachedViews') for database {3} on server {2} is set too low. This can cause ...
- The maximum number of cached views (msExchMaxCachedViews) for database {3} on server {2} is set too high. This can cause ...
- The maximum number of Extensible Storage Engine (ESE) open tables for storage group '{3}' on server {2} is hard-coded. This ...
- The maximum number of Html elements allowed in a web sandbox document. Each element includes a begin tag and a potentially ...
- The maximum number of incremental syncs, {0}, must be less than the maximum number of concurrent migrations, which is currently ...
- The maximum number of recipients of each type to return. The four types are: User, Contact, Group, and DynamicDistributionGroup. ...
- The maximum number of values that can be retrieved from a multi-valued attribute in a single LDAP query for policy '{3}' ...
- The maximum outgoing message size is set too high. This can cause reliability problems. Current maximum message size is {9} ...
- The maximum outgoing message size maybe set too low. An administrative error may have occurred. Current maximum message size ...
- The maximum outgoing message size maybe set too low. An administrative error may have occurred. Maximum message size is {9} ...
- The maximum value of '{0}' is {9}, which is greater than the threshold of {8}. The transaction log drive may be a bottleneck. ...
- The maximum {0} message size is set too low for your Exchange organization '{1}'. Current maximum message size is {2} KB. ...
- The maximum {0} message size isn't set correctly for your Exchange organization '{1}'. Improperly configuring your message ...
- The MaxRequestBytes HTTP parameter on server {0} hasn't been set to 32768. In large environments the absence of this value ...
- The MaxRequestBytes HTTP parameter on server {2} has not been set to 32768. In large environments the absence of this value ...
- The meeting is out of date. The calendar response couldn't be processed but a message with the response content was sent ...
- The meeting message couldn't be correlated because the target is a repeating master and the meeting message is an occurrence. ...
- The member "{1}" can't be removed from the "{0}" management role group. The "{0}" role group can't be empty because it holds ...
- The member "{1}" can't be removed from the "{0}" management role group. The "{0}" role group can't be empty, because it holds ...
- The member count "{0}" of the distribution group "{1}" from tenant "{2}" exceeds the threshold. It will be skipped for out-of-band ...
- The MemberDepartRestriction property value of group "{0}" is "ApprovalRequired", which is currently not supported. Only "Open" ...
- The membership depart restriction of the group "{0}" is set to closed because there is no arbitration mailbox within the ...
- The membership join restriction of the group "{0}" is set to closed because there is no arbitration mailbox within the organization ...
- The message classification settings couldn't be read from Active Directory for virtual directory "%1" under web site "%2". ...
- The message could not be received from domain-secured domain %1 because of a configuration error on Receive connector %2. ...
- The message expiration policy can't be retrieved because the approval process hasn't started. The ModeratedRecipient retention ...
- The message for user {0} will be deleted from the Microsoft Exchange Unified Messaging service message pipeline on the Mailbox ...
- The message in the queue has expired. The sending server tried to relay or deliver the message, but the action was not completed ...
- The message in the queue has expired. The sending server tried to relay or deliver the message, but the action was not completed ...
- The message in the queue has expired. The server responsible for sending the message tried to relay or deliver it, but the ...
- The message is longer than the limit for text messages set by your administrator. For assistance, please contact your email ...
- The message is too large for the local quota. For example, a remote Exchange user may have delivery restrictions set with ...
- The message rejection text and custom status code that you created are ignored because you have configured the policy to ...
- The message submitted by '{4}' to '{3}' appears to be stuck on Exchange gateway server {2}. Further analysis is necessary ...
- The message submitted by '{4}' to '{3}' appears to be stuck on non-gateway server {2}. Further analysis is necessary to determine ...
- The message submitted by '{4}' to '{3}' was routed outside the Exchange organization by server {2} whereas the specified ...
- The message submitted by '{4}' was delivered successfully to recipient '{3}'. It appears that this message was not addressed ...
- The message transfer agent (MTA) configuration parameter '{4}' on server {2} is set too low and may cause mail flow issues. ...
- The message transfer agent (MTA) diagnostic logging level on server {2} is greater than 5. As such, the service is in debugging ...
- The message transfer agent (MTA) diagnostic logging level on server {2} is set to a non-zero value. This level is used for ...
- The Message Waiting Indicator Assistant failed to deliver the MWI notification '%1/%2 (unread/read)' for the UM-enabled mailbox ...
- The Message Waiting Indicator Assistant was unable to obtain the MWI state for mailbox '%1' on database '%2'. You can safely ...
- The Message Waiting Indicator Assistant was unable to query the mailbox database '%1'. The MWI assistant will try to query ...
- The message was not delivered because of Administrator action through the queue viewer interface in Exchange System Manager. ...
- The message you tried to open is protected with Information Rights Management but it can't be viewed because it's corrupted. ...
- The message you tried to open is protected with Information Rights Management. Pre-licensing failed. Try opening the message ...
- The message you tried to open is protected with Information Rights Management. The Rights Management server isn't available ...
- The message you tried to open is protected with Information Rights Management. The RMS server isn't set up correctly. To ...
- The message you tried to open is protected with Information Rights Management. The sender didn't give you the rights necessary ...
- The messaging notifications payload size has grown too large for user "%1". The notifications infrastructure is either not ...
- The Microsoft Distributed Transaction Coordinator (MSDTC) resource appears to be missing from cluster server {2}. This may ...
- The Microsoft Distributed Transaction Coordinator (MSDTC) resource currently running on cluster node {2} is set to affect ...
- The Microsoft Exchange Active Directory Topology service on server {0} did not return any suitable domain controllers for ...
- The Microsoft Exchange Active Directory Topology service on server {0} did not return any suitable global catalog for forest ...
- The Microsoft Exchange Active Directory Topology service on server {2} is hard-coded to use the following Active Directory ...
- The Microsoft Exchange Address Book service couldn't find the local server object in Active Directory. The service will stop. ...
- The Microsoft Exchange Background Audit Search servicelet completed an Audit Log search. The host process ID is %1. The search ...
- The Microsoft Exchange Background Audit Search servicelet initiated an Audit Log search. The host process ID is %1. The search ...
- The Microsoft Exchange Chat resource is running on this node. You must failover the Microsoft Exchange Chat resource to at ...
- The Microsoft Exchange component specified is configured to use circular database logs.It cannot be backed up without a full ...
- The Microsoft Exchange DAG Management service provides storage management and database layout management functionality for ...
- The Microsoft Exchange Event service is running on server {2}. Exchange Server 2007 does not support this facility. This ...
- The Microsoft Exchange Forward Sync Service '%1' could not push data to Insights Engine as queue is full. Data will be dropped. ...