Exchange Server 2016
- The user configuration name is invalid. The name must be fewer than 237 characters, can contain only the characters "A-Z", ...
- The user directory attributes, such as homeMDB or msExchHomeServerName, may be missing or corrupted. Troubleshooting: Verify ...
- The user federated domain '{0}' is defined in multiple remote organization relationships, including '{1}', which can lead ...
- The user hasn't logged on to mailbox '{0}' ('{1}'), so there is no data to return. After the user logs on, this warning will ...
- The user ID "{0}" was found but could't be resolved to a SID, domain\account, or canonical format. The user ID '{0}' will ...
- The user ID and federated identity don't match. If this account was created recently, the user has to sign in to update the ...
- The user name and password for this account are correct, but a connection can't be created to the account because it doesn't ...
- The user name and password for this account are correct, but a connection to the account can't be created because the account ...
- The user record already exists in Store. Possible reason - current session has MbxReadMode flag set to NoMbxRead. You need ...
- The user version for routing group '{3}' appears to be changing very rapidly on server {2} ({9} version change(s) detected ...
- The user version for routing group '{3}' has been changed on server {2} while the tool was running. Latest user version number: ...
- The user version for routing group '{3}' may be changing rapidly on server {2} ({9} version change(s) detected over {8} seconds). ...
- The user with extension '{0}' and dial plan '{1}' isn't UM-enabled, or is enabled for UM on a mailbox that isn't supported ...
- The user {0} couldn't be removed from the migration batch {1} in its current state. Please stop the batch and then try to ...
- The user {0} must be a member of a role group that is assigned the Case Management role before you can make them an eDiscovery ...
- The user's Exchange Server version is '{0}'. An archive mailbox can be connected to a user with mailboxes on Exchange 2010 ...
- The user's external email address isn't a valid SMTP address. Remote access to the mailbox or archive will be disabled. User: ...
- The user-specified domain controller {0} cannot be used because setup has determined that it must use the schema master domain ...
- The UseWindowsUserCredentials group policy registry value isn't correct. This can cause autodiscover issues. You can ignore ...
- The UseWindowsUserCredentials registry entry isn't correct. This can cause autodiscover issues. You can ignore this message ...
- The value "{0}" isn't a valid mailbox folder permission or role. The valid permissions include "ReadItems, CreateItems, EditOwnedItems, ...
- The value "{0}" of the IssuedTo parameter matches more than one certificate in the LocalMachine certificate store. You can ...
- The value "{0}" of the parameter SHA1Thumbprint isn't valid. No certificate could be found in the LocalMachine certificate ...
- The value "{0}" on the parameter SHA1Thumbprint is invalid. The expected format is 20 bytes in hexadecimal presentation optionally ...
- The value '{0}' specified for NotifyUser parameter should be vaild SMTP address or one of Owner, LastModifier, SiteAdmin. ...
- The value '{0}' supplied as a condition contains special characters (single quote, double quote, back quote) or variables ...
- The value for 'MaxMessageCount' on server {0} is less than 500 and may cause performance degradation for the scanning result ...
- The value for '{4}' is set to {9} bytes on server {2}. This can cause errors for users of Outlook Web Access. A minimum value ...
- The value for '{4}' on server {2} is less than {8} and may cause performance degradation for the scanning result thread. ...
- The value for '{4}' on server {2} is too low and may cause performance degradation. The current registry value is {9}. Based ...
- The value for configuration setting 'RestrictRemoteClients' on server {0} isn't correctly configured. Changing this value ...
- The value for configuration setting '{4}' for database '{3}' on server {2} has changed (default value: {7}). Current '{4}' ...
- The value for configuration setting '{4}' for database '{3}' on server {2} has changed (default value: {7}). This configuration ...
- The value for configuration setting '{4}' for database '{3}' on server {2} has changed (default: {7}). This configuration ...
- The value for configuration setting '{4}' for database '{3}' on server {2} has changed. This configuration is recommended ...
- The value for configuration setting '{4}' for object '{3}' on server {2} has changed. Default value: {8}. Current value: ...
- The value for configuration setting '{4}' for public database '{3}' on server {2} has changed. Default: {8} seconds. Current ...
- The value for configuration setting '{4}' for public folder database '{3}' on server {2} has changed. Current value: {9}. ...
- The value for configuration setting '{4}' for public store '{3}' on server {2} has changed. Default: {8} seconds. Current ...
- The value for configuration setting '{4}' for SMTP instance '{3}' on server {2} has changed. Default value: {8}. Current ...
- The value for configuration setting '{4}' on server {2} has changed. This can cause mail flow problems. Current value: {9}. ...
- The value for parameter {0} can only be specified when moving mailboxes between Exchange organizations and must be in a different ...
- The value for setting '{4}' has changed for display specifier '{3}'. This will modify the default behavior for generating ...
- The value for the 'Disable Session Limit' registry entry is set to {1} on server {0}. This may cause excessive memory usage ...
- The value for the 'DSA Computer' registry entry on server {0} doesn't match the name of the local computer ({1}). Configured ...
- The value for the 'DSA Computer' registry entry on server {0} matches the name of the local computer ({1}). Current value ...
- The value for the 'This Server' registry entry on server {0} doesn't match the name of the local computer. This may cause ...
- The value for the '{0}' counter on server {2} is greater than zero (average value is {3}) and it appears that '{4}' is failing ...
- The value for the '{4}' parameter on server {2} is low and could cause instability. Consider increasing the value to 31000 ...
- The value for the '{4}' registry entry is set to zero on server {2}. This can cause severe reliability issues and problems ...
- The value for the '{4}' registry entry is set to {9} on server {2}. This may cause excessive memory usage by MAPI clients ...
- The value for the '{4}' registry entry is set to {9} on server {2}. This may cause excessive memory usage on the server. ...
- The value for the '{4}' registry entry is set too high on server {2}. This can cause mail flow problems. Default value: {8} ...
- The value for the '{4}' registry entry is set too low on server {2}. This can cause degraded database performance and mail ...
- The value for the '{4}' registry entry on server {2} does not match the name of the local computer ({1}). This may cause ...
- The value for the '{4}' registry entry on server {2} has changed. Default value: {8} seconds. Current value: {9} seconds. ...
- The value for the '{4}' registry entry on server {2} has changed. Default value: {9} minutes. Current value: {8} seconds. ...
- The value for the '{4}' registry entry on server {2} has changed. This value should only be changed on the advice of Microsoft ...
- The value for the Exchange Information Store 'TCP/IP Port' registry entry on server {0} is greater than 5000. Current port ...
- The value for the Exchange Information Store 'TCP/IP Port' registry entry on server {0} is less than 5000. If the value is ...
- The value for the Exchange Installable File System (IFS) '{4}' registry entry on server {2} has changed. Current value: {9}. ...
- The value for the Extensible Storage Engine (ESE) transaction log file size for database '{3}' on server {2} changed. This ...
- The value for the Extensible Storage Engine (ESE) transaction log file size for storage group '{3}' on server {2} has changed. ...
- The value for the Extensible Storage Engine (ESE) transaction log file size for storage group '{3}' on server {2} has changed. ...
- The value for the Extensible Storage Engine (ESE) transaction log file size has changed on server {2}. This configuration ...
- The value for the IMAP4 '{4}' registry entry is set higher than {8} bytes on server {2}. Communication errors may occur. ...
- The value for the IMAP4 '{4}' registry entry is set lower than {8} bytes on server {2}. Communication errors may occur. Current ...
- The value for the IMAP4 '{4}' registry entry on server {2} has changed. In some scenarios, this can increase performance. ...
- The value for the maximum Extensible Storage Engine (ESE) cache on server {2} has changed. Current maximum cache size is ...
- The value for the maximum number of databases per storage group on server {2} has changed. This configuration is not supported. ...
- The value for the maximum number of storage groups on server {2} has changed. This configuration is not supported. This server ...
- The value for the Microsoft Exchange Information Store '{4}' registry entry on server {2} has changed. Current value: {9}. ...
- The value for the Microsoft Exchange Information Store '{4}' registry entry on server {2} is less than {8}. This configuration ...
- The value for the Microsoft Exchange Information Store RPC '{4}' registry entry on server {2} is not set to {8}. This will ...
- The value for the Microsoft Exchange Site Replication Service '{4}' registry entry on server {2} has changed. Port value: ...