Exchange Server 2016
- The bulk e-mail address operation ran out of memory. E-mail addresses for display name '%1' (mailbox name '%2') were unchanged. ...
- The bulk e-mail address process completed. %1 recipients were scanned, %2 were successfully updated, %3 were unsuccessfully ...
- The cached Active Directory configuration is {0} old, which is older than the maximum allowed age of {1}. This could indicate ...
- The calendar configuration is corrupt and has been recreated. All previous settings have been erased. Please reconfigure ...
- The call for '%1' isn't supported on this server. The call was redirected to the Microsoft Exchange Unified Messaging service ...
- The call for user %1 in dial plan %2 was rejected. Reason: No Mailbox server could be found in the user's mailbox site %3 ...
- The call to Mailbox Search Service on server: '{0}' failed. Please restart 'Microsoft Exchange Mailbox Assistants' on the ...
- The call to Microsoft Exchange Active Directory Topology service on server '{0}' returned an unexpected error. Error details: ...
- The call with ID "%1" was disconnected by the Microsoft Exchange Unified Messaging service on the Mailbox server because ...
- The category of client experiencing the most latency is '{1}'. The value of the counter '{0}' is {2} ms. This category of ...
- The certificate associated with the given server can't be removed because removing it will cause the Microsoft Exchange Unified ...
- The certificate associated with the Mailbox server can't be removed because removing it will cause the Microsoft Exchange ...
- The certificate chain terminated in a root certification authority which is not trusted by the trust provider. The root certificate ...
- The certificate named '%1' in the Federation Trust '%2' is expired. Please review the Federation Trust properties and the ...
- The Certificate on Client Access Server {0} with Thumbprint {1} has either expired, or not yet active, please check the dates ...
- The certificate on Client Access Server {0} with thumbprint {1} is self-signed. Self-signed certificates aren't allowed for ...
- The certificate specified by the InstantMessagingCertificateThumbprint parameter of the Outlook Web App virtual directory ...
- The certificate specified by the InstantMessagingCertificateThumbprint parameter of the Outlook Web App virtual directory ...
- The certificate specified by the InstantMessagingCertificateThumbprint parameter of the Outlook Web App virtual directory ...
- The certificate specified by the InstantMessagingCertificateThumbprint parameter of the Outlook Web App virtual directory ...
- The certificate specified in the InstantMessagingCertificateThumbprint parameter of the Outlook Web App virtual directory ...
- The certificate used by the Microsoft Exchange Unified Messaging Call Router service will expire in "%1" days. No actions ...
- The certificate used by the Microsoft Exchange Unified Messaging Call Router service will expire in "%1" days. When the certificate ...
- The certificate with the subject '{0}' can't be used for SSL or TLS connections because the subject isn't a valid fully qualified ...
- The certificate with the thumbprint '{0}', which is specified on the UMCertificateThumbprint property of the '{1}' object, ...
- The certificate with thumbprint "{0}" uses a Cryptography API: Next Generation (CNG) service provider. Certificates that ...
- The certificate with thumbprint '{0}' can't be enabled for Microsoft Exchange Unified Messaging because it is currently set ...
- The certificate with thumbprint '{0}' can't be enabled for Microsoft Exchange Unified Messaging because the service is unavailable ...
- The certificate with thumbprint '{0}' can't be enabled for Microsoft Exchange Unified Messaging Call Router because it is ...
- The certificate with thumbprint '{0}' can't be enabled for the Microsoft Exchange Unified Messaging call router because the ...
- The character '{4}' isn't valid for file extensions. It was found in character {3} of "{2}" in element {1} of the {0} array. ...
- The characters '=',';' and ',' are not allowed in logged text, please replace by some other characters before pushing text ...
- The checkpoint file path for database '{1}' on server {0} ({2}) doesn't match the transaction log path ({3}). This issue ...
- The checkpoint file path for database '{1}' on server {0} ({2}) matches the transaction log path ({3}). This is a recommended ...
- The checkpoint file path for storage group '{3}' on server {2} ({5}) does not match the transaction log path ({1}). This ...
- The child process servermanagercmd.exe returned {0} while trying to add or remove the Windows Failover Clustering feature. ...
- The ChildObjectTypes parameter can only be specified when you specify the CreateChild or DeleteChild values for the AccessRights ...
- The chosen global catalog server is not running Windows Server 2003 Service Pack 1 or later in the local Active Directory ...
- The CIDR length "{0}" is invalid. An acceptable CIDR length is in the range 0, 32 for an IPv4 address and 0, 128 for an IPv6 ...
- The CIDR length {0} is greater than the maximum of 128 for an IPv6 address. An acceptable CIDR length is in the range 0, ...
- The CIDR length {0} is greater than the maximum of 32 for an IPv4 address. An acceptable CIDR length is in the range 0, 32 ...
- The classification rule collection payload failed to validate against its target schema. The following error is found on ...
- The Client Access server "%1" attempted to proxy Outlook Web App traffic for mailbox "%2". This failed because no Client ...
- The Client Access server cannot proxy the Exchange ActiveSync client request to the Exchange server %1. For this to work, ...
- The Client Access server doesn't have the InternalURL value set for the Microsoft-Server-ActiveSync virtual directory. This ...
- The Client Access server failed to exchange the required certificates with an IP gateway to enable Transport Layer Security ...
- The Client Access server is running the following version of Microsoft Exchange: {0}, but a Client Access server running ...
- The Client Access server isn't currently enabled and the Microsoft Exchange Unified Messaging call router can't listen on ...
- The Client Access server role is already installed on this server. Run Setup again and specify a server role that's not already ...
- The Client Access server version doesn't match the Mailbox server version of the resource that was being accessed. To determine ...
- The Client Access server was able to contact the Microsoft Exchange Unified Messaging service on Mailbox server '%1' for ...
- The Client Access server wasn't specified. You can use the UseAutodisoverForClientAccessServer parameter to use the Autodiscover ...
- The Client Access Server {0} does not have a Certificate that contains the On-premises Web Services External Url domain ({1}) ...
- The Client Access servers specified by the HybridConfiguration Active Directory object were not properly cleared during the ...
- The clock setting of this machine isn't synchronized with the clock setting of the Edge Transport server you are attempting ...
- The cluster group for database availability group '{0}' is missing. Please use the Set-DatabaseAvailabilityGroup cmdlet to ...
- The Cluster Network for this DAG has not been up for {0} minutes. The most recent probe failure message is: {Probe.Error} ...
- The Cluster service couldn't access the Microsoft Failover Cluster Virtual Miniport network adapter. Verify that other network ...
- The cluster service doesn't appear to be running on server {0}. Make sure that the server is operating and that services ...
- The cmdlet can't operate on the HybridConfiguration Active Directory object because the object was created with a newer version ...
- The cmdlet could not to be called under forest wide context. Please provide an organization parameter, specify organization ...
- The cmdlet extension agent configuration object for class factory "{1}" in assembly "{0}" is already defined in Active Directory. ...
- The cmdlet fails to find all the server information through pinging service providers or other topology discovery inside ...
- The cmdlet name should be in the format of "Cmdlet" or "Cmdlet,SnapIn". Neither the cmdlet name nor the snap-in name can ...
- The cmdlet running on "{0}" can't manipulate Alternate Service Accounts on "{1}". Run Connect-ExchangeServer "{1}" and retry ...
- The cmdlet will be performing GLS rollback for tenant {0} so that its AccountForest property will be changed from {1} to ...
- The cmdlet will be performing relocation rollback for tenant {0} from {2} while servicelet hasn't reached requested state ...
- The cmdlet you tried to run failed because your remote PowerShell session expired. Your session will be automatically reconnected ...
- The CNAME autodiscover record is setup in DNS and verified for {0}. Your organization can automatically configure Outlook. ...
- The CNAME autodiscover record isn't configured correctly in DNS. Your organization {0} can't automatically configure Outlook. ...
- The combination of ProgramId '{0}' and OfferId '{1}' represent pilot service plan which can be used to create shared configurations ...
- The combined processor time spent in the store.exe and inetinfo.exe is more than {8}%. This may result in mail delays. Actual ...
- The command failed when running as user '{0}'. Please contact your administrator to assign the appropriate role(s) to your ...
- The command you tried to run isn't currently allowed in your organization. To run this command, you first need to run the ...
- The comment cannot be set on this managed folder. Comments cannot be set on the Calendar, Contacts, Journal, Notes and Tasks ...