Exchange Server 2016
- Microsoft Exchange System Attendant does not have sufficient rights to read Exchange configuration objects in Active Directory. ...
- Microsoft Exchange System Attendant failed to add the local computer as a member of the DS group object '%1'. Please stop ...
- Microsoft Exchange System Attendant failed to read the membership of group '%1'. Error code '%2'. Please check whether the ...
- Microsoft Exchange System Attendant failed to read the membership of the universal security group '%1'; the error code was ...
- Microsoft Exchange System Attendant has detected a discrepancy in the published security data for Exchange server '%1'. This ...
- Microsoft Exchange System Attendant has detected that the local computer '%1' is not a member of group '%2'.System Attendant ...
- Microsoft Exchange System Attendant has detected that the password of the legacy Exchange service account has been modified. ...
- Microsoft Exchange System Attendant has detected that the system attendant object in the DS has been modified.System Attendant ...
- Microsoft Exchange System Attendant is querying for Outlook Anywhere back-ends to reset RPC Proxy Valid Ports. Config DC='%1' ...
- Microsoft Exchange System Attendant was unable to find the Exchange server object named '%1' in Active Directory. All known ...
- Microsoft Exchange Transport is rejecting message submissions because the available disk space has dropped below the configured ...
- Microsoft Exchange versions earlier than Exchange Server 2003 do not support Outlook Anywhere. The following servers cannot ...
- Microsoft Exchange versions earlier than Exchange Server 2013 do not support the Negotiate client authentication method. ...
- Microsoft Exchange VSS Writer failed with error %1 when collecting database information for '%2' in preparation for backup. ...
- Microsoft Exchange was unable to initialize the Content Filter agent. Check the access control lists (ACLs) on the files ...
- Microsoft Exchange was unable to initialize the Content Filter agent. It could not allocate sufficient memory for an internal ...
- Microsoft Exchange was unable to initialize the Content Filter agent. Notification of the file system change could not be ...
- Microsoft Filter Pack isn't installed on server {0}. The Microsoft Filter Pack is necessary to index and search Microsoft ...
- Microsoft Forefront Security 2010 for Exchange Server is running on Exchange server {0} with reverse DNS lookup enabled. ...
- Microsoft Forefront Security 2010 for Exchange Server is running on Exchange server {0} without reverse DNS lookup enabled. ...
- Microsoft Office 365 Best Practices Analyzer Beta 1.0 can allow you enter alternate credentials to run the on-premises checks. ...
- Modifying CompleteAfter within a short period of time before the original CompleteAfter may not take affect. Settings propagate ...
- Monitoring is not enabled for database {0}. Last reported monitoring (AutoDagExcludeFromMonitoring) state is {Probe.StateAttribute3} ...
- Monitoring item '{0}' of type '{1}' already has an override '{2}' applied for all target resources. Please remove the existing ...
- Monitoring item '{0}' of type '{1}' already has an override '{2}' applied for specific target resource(s). Please remove ...
- Monitoring item '{1}' of type '{2}' already has an override applied for Property '{0}'. Please remove the existing override ...
- More than 500 mailboxes in the entire forest have delivery restrictions set where at least one distribution group is used ...
- More than 8 logical processors exist on Exchange server {0}. If this server has more than 8 physical processors installed, ...
- More than 8 logical processors exist on Exchange server {2}. If this server has more than 8 physical processors installed, ...
- More than 8 processors were detected for the Exchange server {2}. If this server has more than 8 physical processors installed ...
- More than 8 processors were detected for the Exchange server {2}. If this server has more than 8 physical processors installed, ...
- More than 800 address lists exist in the organization '{0}'. If the Recipient Update Service is responsible for these, severe ...
- More than 800 address lists exist in the organization. If the Recipient Update Service is responsible for these, severe latencies ...
- More than 800 global address lists exist in the organization '{0}'. If the Recipient Update Service is responsible for these, ...
- More than 800 global address lists exist in the organization. If the Recipient Update Service is responsible for these, severe ...
- More than one accepted domain was found when searching for '{0}'. The following accepted domains were found: {1} and {2}. ...
- More than one Active Directory object is configured with the recipient address %1. Messages to this recipient will be deferred ...
- More than one administrator audit log configuration was found for the organization '{0}'. This may be caused by a replication ...
- More than one computer account in Active Directory has '{5}' set to '{3}'. This will result in Kerberos authentication failures ...
- More than one computer account in Active Directory has '{5}' set to '{3}'. This will result in Kerberos authentication failures ...
- More than one IIS Web service extension was found with the group ID {0} and the file {1}. Please remove the duplicate entries ...
- More than one mailbox plan is marked as default. Use Set-MailboxPlan to make sure that only one mailbox plan is marked as ...
- More than one network interface on server {0} has a default IP gateway listed. Communication errors may occur if these network ...
- More than one network interface on server {2} has a default IP gateway listed. Communication errors may occur if these network ...
- More than one organization mailbox was found that has 'UMDataStorage' capability: {0}, {1}. Only one organization mailbox ...
- More than one UM IP gateway object has been resolved to the same IP address. Modify the configuration so that each UM IP ...
- More than two connectors were found in ManagementAgent %1 for MetaVerse object %2. This could be because of invalid changes ...
- More than {0} results were found given the specified search criteria. Please have more restriction on your search criteria. ...
- More than {6}% of the messages in the '{4}' queue on server {2} appear to be addressed to distribution group '{3}'. The number ...
- More than {6}% of the messages in the '{4}' queue on server {2} appear to be addressed to server {1}. The number of such ...
- More than {6}% of the messages in the '{4}' queue on server {2} appear to be addressed to the mailbox store '{3}'. The number ...
- More than {6}% of the messages in the '{4}' queue on server {2} appear to be addressed to the public folder '{3}'. The number ...
- More than {6}% of the messages in the '{4}' queue on server {2} appear to be addressed to the public folder store '{3}'. ...
- More than {6}% of the messages in the '{4}' queue on server {2} appear to be addressed to user '{1}'. The number of such ...
- More than {8} Exchange mailbox stores exist in the organization. To avoid logon issues with Outlook Web Access, install the ...
- More than {8} Exchange servers exist in the organization. Exchange is limited to {1} total servers. Current number of Exchange ...
- More than {8} messaging connectors exist in the organization. This may cause additional load on Exchange and Active Directory ...
- Most common possible causes are 1)The message contains more than 250 attachments. More than 250 attachments cause the MAPI_E_TOO_BIG ...
- Most of the RPC load is in the category '{1}'. This category accounts for {2} RPC operations/second, out of the total rate ...
- Mount for database '{0}' failed due to timeout after {2} seconds on server '{1}'. Disk or controller issues may cause slow ...
- Mount point '{0}' on server {1} doesn't have a recommended amount of free disk space. Total: {2} GB of free space, which ...
- Move Collection Commands/sec is the number of MoveCollection commands that are processed each second. Clients that are running ...
- Move Collection Total is the total number of MoveCollections requests that have been processed since the service was started. ...
- Move for database '{0}' was suppressed because too many moves have happened recently. {1} moves have happened within {2}. ...
- Move for database '{0}' was suppressed due to a blackout between '{1}'UTC and '{2}'UTC. {3} previous moves have happened ...
- Move for mailbox '{0}' is stalled because DataMoveReplicationConstraint is not satisfied for the database '{1}' (agent {3}). ...
- Move for mailbox {0} has been postponed because the remote forest doesn't have enough resources to process the move. The ...
- Move Items Commands/sec is the number of MoveItems commands that are processed each second. Clients use this command to move ...
- Move request '{0}' is an offline mailbox move request. Only online mailbox move requests can be suspended automatically when ...
- Move-ActiveMailboxDatabase was called for server '{0}' with skip options, but ActivateOnServer is not specified (SkipClientExperienceChecks={1}, ...
- Move-DatabasePath is not allowed for replicated databases. For detailed steps to change the location of a replicated database, ...
- MoveFolder Average Response Time is the average elapsed time (in milliseconds) between the beginning and end of a MoveFolder ...
- MoveFolder Successful Requests is the total number of successful requests for the MoveFolder web method since the service ...
- MoveItem Average Response Time is the average elapsed time (in milliseconds) between the beginning and end of a MoveItem ...
- MoveItem Successful Requests is the total number of successful requests for the MoveItem web method since the service was ...