Exchange Server 2010
- The '{4}' attribute for mailbox store '{3}' on server {2} doesn't correspond to the hosting server. This situation will cause ...
- The '{4}' attribute for public folder database '{3}' on server {2} doesn't match the hosting server. This will cause reliability ...
- The '{4}' attribute for Recipient Update Service '{3}' contains data. The Recipient Update Service is currently processing ...
- The '{4}' attribute for Recipient Update Service '{3}' contains old data that was not fully processed. This data has existed ...
- The '{4}' attribute for the Exchange organization is not well-formed and may cause functionality problems. Current '{4}' ...
- The '{4}' attribute on server {2} is missing. This will cause 'Microsoft Exchange Information Store' service initialization ...
- The '{4}' binding for server {2} does not contain a fully-qualified domain name. This can cause service failures. Current ...
- The '{4}' binding for server {2} does not match the DNS resolved name. This can cause mail routing problems. Current '{7}' ...
- The '{4}' configuration parameter is set to {9} on server {2} (default is {8}). If set incorrectly, this value may cause ...
- The '{4}' configuration setting is enabled on server {2}. This setting will prevent users from accessing resources on this ...
- The '{4}' has changed from its default of '{7}' on server {2}. This may cause communication problems. Current value: {1}. ...
- The '{4}' HTTP parameter on server {2} is set to {9}. This may cause Outlook Web Access and Exchange ActiveSync connections ...
- The '{4}' HTTP parameter on server {2} is set to {9}. This may cause Outlook Web App and Exchange ActiveSync connections ...
- The '{4}' is set on server {2}. It is possible that either the Exchange or Outlook client is installed on the server. Current ...
- The '{4}' parameter is set to '{9}' on server {2}. This may cause synchronization errors for Exchange ActiveSync clients. ...
- The '{4}' property of SMTP instance '{3}' on server {2} is set to 'False'. Verify that this setting is not preventing internal ...
- The '{4}' queue on server {2} has messages addressed to global distribution group '{3}', while the topology appears to be ...
- The '{4}' registry entry for mailbox store '{3}' on server {2} contains data. This database has experienced problems with ...
- The '{4}' registry entry for public folder database '{3}' on server {2} contains data. This database has experienced problems ...
- The '{4}' service reported resource pressure state transition from '{1}' to '{2}' at {3} and logged the following statistics: ...
- The '{4}' service reports {1} MB free space in the transport database file '{5}' at {2}. There is no reason to reclaim this ...
- The '{4}' service reports {1} MB free space in the transport database file '{5}' at {2}. This free space can be reclaimed ...
- The '{4}' setting for database '{3}' on server {2} is set too high. This can cause excessive server load and client performance ...
- The '{4}' setting for database '{3}' on server {2} is set too low. This can cause excessive server load and client performance ...
- The '{4}' system environment variable on server {2} is different from the default value of {8}. The current value is: {9}. ...
- The '{4}' system environment variable on server {2} is less than {8}. It is recommended that this environment variable be ...
- The '{4}' value for ASP.NET configuration on server {2} is set to '0.0.0.0'. This can cause Microsoft Exchange System Attendant ...
- The '{4}' value for mailbox database '{3}' on server {2} is missing. This will cause offline address book errors for {9} ...
- The '{4}' value for public folder store '{3}' on server {2} is missing. This will cause public folder size discrepancies. ...
- The '{4}' value for SMTP instance '{3}' on server {2} has been altered from its default of 0. This will cause mail flow problems ...
- The '{4}' value for SMTP instance '{3}' on server {2} is greater than the global limit. This may cause oversized messages ...
- The '{4}' value for the Microsoft Exchange System Attendant service on server {2} is missing. This will cause reliability ...
- The '{4}' value for the registry key '{5}' is set to zero. This disables ISAPI caching which can cause system instability. ...
- The '{4}' value for the registry key '{5}' is set to zero. This disables ISAPI caching which can cause system instability. ...
- The '{4}' value is set on server {2} and may cause system instability. On 64-bit servers, it is recommended to leave this ...
- The '{5}' registry entry used by {0} is set on server {2} but {0} needs to be updated before this configuration setting will ...
- The '{5}' version on cluster node {2} differs from that on node {1} ({9} <> {8}). This may cause cluster failover problems. ...
- The -CleanUpInvalidAlternateServiceAccountCredentials and -RemoveAlternateServiceAccountCredentials parameters are mutually ...
- The .dll file required for e-mail address generation couldn't be opened for verification because it couldn't be found in ...
- The .edb file for mailbox database '{3}' on server {2} is being written to a non-NTFS partition. This configuration doesn't ...
- The .edb file for mailbox database '{3}' on server {2} is being written to an encrypted folder. Severe performance degradation ...
- The .edb file for public folder database '{3}' on server {2} is being written to a compressed folder. Severe performance ...
- The .edb file for public folder database '{3}' on server {2} is being written to a non-NTFS partition. This configuration ...
- The .edb file for public folder database '{3}' on server {2} is being written to an encrypted folder. Severe performance ...
- The .stm file for public folder database '{3}' on server {2} is being written to a compressed folder. Severe performance ...
- The .stm file for public folder database '{3}' on server {2} is being written to a non-NTFS partition. This configuration ...
- The .stm file for public folder database '{3}' on server {2} is being written to an encrypted folder. Severe performance ...
- The /3GB switch is not set. There is at least one occurrence of Event ID {9} in the application log of server {2} within ...
- The /Userva switch is not set properly. There is at least one occurrence of Event ID {9} in the application log of server ...
- The 32-bit ASP.NET is registered to IIS on {2}. This will cause an Outlook Web App access error. Run 'aspnet_regiis -r -enable' ...
- The A/V Authentication service running on an Edge server hasn't been specified. Using the Set-OrganizationConfig cmdlet, ...
- The ability to modify policies on this tab is a premium Exchange ActiveSync feature that requires an Exchange Enterprise ...
- The ability to modify policies on this tab is a premium Exchange ActiveSync feature that requires an Exchange Enterprise ...
- The accepted domain {0} is federated and cannot be removed. Please use Remove-FederatedDomain task to first remove this domain ...
- The access token used for Exchange impersonation includes the following SIDs: %4User: %1 %4Group: %2 %4Restricted Group: ...
- The access token used for Exchange impersonation includes the following SIDs: %4User: %1 %4Group: %2 %4Restricted Group: ...
- The account "%1" doesn't have the appropriate permissions to modify the Exchange ActiveSync service privileges. Please check ...
- The account "%1" doesn't have the appropriate permissions to modify the Exchange ActiveSync service privileges. Please check ...
- The account '%1' provided valid credentials, but it does not have submit permissions on SMTP Receive connector '%2'; failing ...
- The account '%1' provided valid credentials, but it does not have submit permissions on SMTP Receive connector '%2'; failing ...
- The account can't be verified because services are temporary unavailable or because of other temporary failures. Please try ...
- The account cannot be verified. This may be because some services are temporary unavailable or other temporary failures. ...
- The account name "{0}" can't be used for the Windows Live ID because it violates the naming policy. Choose another name or ...
- The account name "{0}" can't be used for the Windows Live ID because it violates the naming policy. Please choose another ...
- The account namespace is the federated domain used to construct a user identifier for the Microsoft Federation Gateway. Make ...
- The account namespace is the federated domain used to construct a user identifier for the Microsoft Federation Gateway. Make ...
- The account specified for the Microsoft Exchange Server Mailbox Manager Administrator is invalid. No mailboxes will be processed. ...
- The account specified for the Microsoft Exchange Server Mailbox Manager Administrator is invalid. No mailboxes will be processed. ...
- The AceType is of type {0}. The only supported values are AccessAllowed, AccessAllowedObject, AccessDenied, and AccessDeniedObject. ...
- The ACL of the temporary folder couldn't be set because the WebReady Document Viewing Manager doesn't have the permissions ...
- The ACL of the temporary folder couldn't be set because the WebReady Document Viewing Manager doesn't have the permissions ...
- The ActingAs parameter is required to determine the requested configuration when retrieving any non-Unified Messaging configuration. ...
- The action '{1}', '{2}', can't be performed on the object '{0}' because the object is being synchronized from your on-premises ...
- The action '{1}', '{2}', can't be performed on the user '{0}'. Your Microsoft Exchange Online license doesn't permit you ...
- The action '{1}', '{2}', may not be performed on the management role group '{0}' with capablity '{3}'. Membership of a partner ...