Exchange Server 2010
- The Mailbox Search Service is unavailable on server: '{0}'. Please make sure 'Microsoft Exchange Mailbox Assistants' is running ...
- The Mailbox server %1 that hosts the mailbox for mobile phone user %2 is running version %3]. Exchange ActiveSync only supports ...
- The Mailbox server %1 that hosts the mailbox for mobile phone user %2 is running version %3]. Exchange ActiveSync only supports ...
- The Mailbox server resource pool limit of %1 has been reached. This may be due to resources not being properly released after ...
- The Mailbox server role provides e-mail storage and advanced scheduling services. The Mailbox server role also includes public ...
- The mailbox specified, '{0}', isn't valid. Check to be sure the user exists and is UM-enabled in the same dial plan as this ...
- The mailbox store '{3}' on server {2} is {9} GB in size. Standard Editions of Microsoft Exchange Server 2003 Service Pack ...
- The mailbox store '{3}' on server {2} is {9} GB in size. Standard editions of Microsoft Exchange Server are limited to a ...
- The mailbox store '{3}' on server {2} is {9} GB in size. Standard Editions of Microsoft Exchange Server are limited to a ...
- The mailbox that you specified is connected to "{0}". Only disconnected mailboxes can be reconnected. Specified mailbox: ...
- The mailbox you requested couldn't be opened because no match was found for the address "{0}". Make sure the address is spelled ...
- The mailbox you specified couldn't be found. Close the dialog box and try to find the mailbox again. Make sure you've typed ...
- The mailbox you're trying to access isn't available. The host name entry should be in the format "http :// : ]/owa", but ...
- The mailbox {0} can't be one of the mailboxes that you search or the mailbox in which results are saved. Select a different ...
- The mailbox's dial plan in the source forest is of type '{0}'. However, the matching dial plan in the target forest is of ...
- The major version for routing group '{3}' appears to be changing very rapidly on server {2} ({9} version change(s) detected ...
- The major version for routing group '{3}' has been changed on server {2} while the tool was running. Latest major version ...
- The major version for routing group '{3}' may be changing rapidly on server {2} ({9} version change(s) detected over {8} ...
- The major version of the server is {0}. However, a Client Access server with the same major version as the Mailbox server, ...
- The managed folder assistant audit log is enabled, but the path to the audit log is missing in Active Directory. Current ...
- The managed folder assistant could not configure the audit log. It will stop processing the current database: '%1'. It will ...
- The managed folder assistant could not configure the audit log. It will stop processing the current database: '%1'. It will ...
- The Managed Folder Assistant detected a circular reference in Managed Content Settings in mailbox '{0}' that will enforce ...
- The managed folder assistant detected a cycle among the policies in mailbox %1 that will enforce retention by moving items ...
- The managed folder assistant detected a cycle among the policies in mailbox %1 that will enforce retention by moving items ...
- The managed folder assistant did not write to the audit log. It will stop processing the current database: '%1'. It will ...
- The managed folder assistant did not write to the audit log. It will stop processing the current database: '%1'. It will ...
- The managed folder assistant failed to provision mailbox %1 because of damaged data in Active Directory. Exception details: ...
- The managed folder assistant failed to provision mailbox %1 because of damaged data in Active Directory. Exception details: ...
- The managed folder assistant skipped processing all databases on the local server because it could not read the audit log ...
- The managed folder assistant skipped processing all databases on the local server because it could not read the audit log ...
- The managed folder assistant skipped processing all databases on the local server because the audit log is enabled but the ...
- The managed folder assistant skipped processing all databases on the local server because the audit log is enabled but the ...
- The managed folder assistant was unable to create the managed root folder %1 in mailbox %2 because the mailbox has several ...
- The managed folder assistant was unable to create the managed root folder %1 in mailbox %2 because the mailbox has several ...
- The managed folder assistant will not process mailboxes on this server because one or more managed folders in Active Directory ...
- The managed folder assistant will not process mailboxes on this server because one or more managed folders in Active Directory ...
- The managed folder mailbox policy '{0}' for the mailbox '{1}' is invalid because it is linked to more than one managed default ...
- The managed folder mailbox policy '{0}' is invalid because it is linked to more than one default managed folder of the same ...
- The ManagedContentSetting {0} was upgraded from {1}. The MessageClass on this ManagedContentSetting is now set to "*". Please ...
- The management role "{0}" can't be assigned to the role assignment policy because it isn't an end-user role. Only end-user ...
- The management role "{0}" couldn't be upgraded. Consider removing this role and associated role assignments when the entire ...
- The management role "{0}" couldn't be upgraded. Consider removing this role and associated role assignments when the entire ...
- The management role "{0}" couldn't be upgraded. Remove the role and associated role assignments using Active Directory tools ...
- The management role "{0}" couldn't be upgraded. Remove the role and associated role assignments using Active Directory tools ...
- The management role "{0}" is in the process of being deprecated. New role assignments referring this role aren't allowed. ...
- The management role 'Role Management' should be assigned (with a delegating role assignment) to one security group with members. ...
- The management role 'Role Management' should be assigned (with a regular role assignment) to one security group with members. ...
- The management role '{0}' can't be renamed to '{1}' because there is already a root role or Administrative role with the ...
- The management role assignment "{0}" couldn't be created. The role group "{1}" and its management role assignments have been ...
- The management role assignment "{0}" is invalid and can't be automatically upgraded. Consider removing this role assignment ...
- The management role assignment {0} is associated with a policy; however, its RoleAssigneeType isn't RoleAssignmentPolicy. ...
- The management role assignment {0} is associated with a policy; however, its RoleAssignmentDelegationType isn't Regular. ...
- The management role assignment {0} isn't associated with a management role. The management role might have been deleted. ...
- The management role assignment {0} isn't associated with a role group, assignment policy, user, or universal security group. ...
- The management role assignments "{0}" and "{1}" have conflicting domain or configuration scopes. The reason for this error ...
- The management role entry "{0}" is invalid for the current role. Only management roles of type '{1}' can contain {2} management ...
- The management role name "{0}" is invalid because it either contains commas or it's empty. Remove any commas that are in ...
- The MAPI interface for Active Directory is disabled on server {2}. Microsoft Office Outlook clients will not be able to contact ...
- The MAPI property type with property tag (0x{0:x4}) doesn't match the MAPI property type found for this property in the Active ...
- The masquerade domain '{1}' configured for SMTP virtual server '{3}' on server {2} is also defined as an SMTP address in ...
- The master category list can't be saved because it is too large: {0} bytes. The maximum allowed size is {1} bytes. Delete ...
- The MasterServerOrAvailabilityGroup property for database copy '{0}' contains an invalid value. This may be due to a corrupted ...
- The max hop count was exceeded for the message. This code may occur if a loop situation exists between a sending server and ...
- The Max number of retries to load resolver configuration data on startup has been reached. The Microsoft Exchange Transport ...
- The MaxDSNSize registry value has not been set on server {2}. Implementing this option can increase overall performance and ...
- The MaxFieldLength HTTP parameter on server {2} has not been set to 32768. In large environments, the absence of this value ...
- The maximum allowable incoming message size ({8} KB) does not match the outgoing size ({9} KB). These values should be the ...
- The maximum database cache size is {9} on server {2}. The recommended database cache size on Edge Transport servers that ...
- The maximum database cache size is {9} on server {2}. The recommended database cache size on Hub Transport servers that have ...
- The maximum download size per item for transport synchronization should be less than the maximum download size per connection. ...
- The maximum Extensible Storage Engine (ESE) cache on server {2} has been increased and may cause low virtual memory conditions. ...
- 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 ...