Exchange Server 2010

  1. The bulk e-mail address operation ran out of memory. E-mail addresses for display name '%1' (mailbox name '%2') were unchanged. ...
  2. The bulk e-mail address process completed. %1 recipients were scanned, %2 were successfully updated, %3 were unsuccessfully ...
  3. The bulk e-mail address process completed. %1 recipients were scanned, %2 were successfully updated, %3 were unsuccessfully ...
  4. The BytesToSkip for the Outlook 2007 meeting change highlight feature should be either 0 or 4, but the recurrence property ...
  5. The cabinet file '[2]' required for this installation is corrupted and cannot be used. This could indicate a network error, ...
  6. The calendar configuration is corrupt and has been recreated. All previous settings have been erased. Please reconfigure ...
  7. The call for '%1' isn't supported on this server. The call was redirected to Unified Messaging server '%2'. The caller ID ...
  8. The call for '%1' isn't supported on this server. The call was redirected to Unified Messaging server '%2'. The caller ID ...
  9. The call for user %1 in dial plan %2 was rejected. Reason: No Unified Messaging server could be found in the user's mailbox ...
  10. The call for user %1 in dial plan %2 was rejected. Reason: No Unified Messaging server could be found in the user's mailbox ...
  11. The call to Mailbox Search Service on server: '{0}' failed. Please restart 'Microsoft Exchange Mailbox Assistants' on the ...
  12. The caller or your organization's policy required the voice message to be protected, but protection couldn't be applied. ...
  13. The category of client experiencing the most latency is '{1}'. The value of the counter '{0}' is {2} ms. This category of ...
  14. The certificate associated with the Unified Messaging server can't be removed because removing it will cause the Microsoft ...
  15. The certificate chain couldn't be built. You may be missing required intermediate certificates. For more information, see ...
  16. The certificate chain terminated in a root certification authority which is not trusted by the trust provider. The root certificate ...
  17. The certificate for the URL {0} is incorrect. For SSL to work, the certificate needs to have a subject of {1}, instead the ...
  18. The certificate is only trusted on Windows Mobile 5.0 with the Messaging and Security Feature Pack and later versions. Windows ...
  19. The certificate is only trusted on Windows Mobile 6.0 and later versions. Devices running Windows Mobile 5.0 and 5.0 with ...
  20. The certificate named '%1' in the Federation Trust '%2' is expired. Please review the Federation Trust properties and the ...
  21. The certificate named '%1' in the Federation Trust '%2' is expired. Please review the Federation Trust properties and the ...
  22. The certificate specified by the InstantMessagingCertificateThumbprint parameter of the Outlook Web App virtual directory ...
  23. The certificate specified by the InstantMessagingCertificateThumbprint parameter of the Outlook Web App virtual directory ...
  24. The certificate specified by the InstantMessagingCertificateThumbprint parameter of the Outlook Web App virtual directory ...
  25. The certificate specified by the InstantMessagingCertificateThumbprint parameter of the Outlook Web App virtual directory ...
  26. The certificate specified by the InstantMessagingCertificateThumbprint parameter of the Outlook Web App virtual directory ...
  27. The certificate specified by the InstantMessagingCertificateThumbprint parameter of the Outlook Web App virtual directory ...
  28. The certificate specified by the InstantMessagingCertificateThumbprint parameter of the Outlook Web App virtual directory ...
  29. The certificate specified by the InstantMessagingCertificateThumbprint parameter of the Outlook Web App virtual directory ...
  30. The certificate specified in the InstantMessagingCertificateThumbprint parameter of the Outlook Web App virtual directory ...
  31. The certificate specified in the InstantMessagingCertificateThumbprint parameter of the Outlook Web App virtual directory ...
  32. The certificate with the subject '{0}' can't be used for SSL or TLS connections because the subject isn't a valid fully qualified ...
  33. The certificate with thumbprint "{0}" uses a Cryptography API: Next Generation (CNG) service provider. Certificates that ...
  34. The certificate with thumbprint '{0}' can't be enabled for Microsoft Exchange Unified Messaging because it is currently set ...
  35. The certificate with thumbprint '{0}' can't be enabled for Microsoft Exchange Unified Messaging because Unified Messaging ...
  36. The certificate with thumbprint '{0}' specified on the UMCertificateThumbprint property of the UMServer object is an expired ...
  37. The character '{4}' isn't valid for file extensions. It was found in character {3} of "{2}" in element {1} of the {0} array. ...
  38. The checkpoint file path for storage group '{3}' on server {2} ({5}) does not match the transaction log path ({1}). This ...
  39. The ChildObjectTypes parameter can only be specified when you specify the CreateChild or DeleteChild values for the AccessRights ...
  40. 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 ...
  41. The CIDR length {0} is greater than the maximum of 128 for an IPv6 address. An acceptable CIDR length is in the range 0, ...
  42. 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 ...
  43. The Client Access server "%1" attempted to proxy Outlook Web App traffic for mailbox "%2". This failed because no Client ...
  44. The Client Access server "%1" attempted to proxy Outlook Web App traffic for mailbox "%2". This failed because no Client ...
  45. The Client Access server cannot proxy the Exchange ActiveSync client request to the Exchange server %1. For this to work, ...
  46. The Client Access server cannot proxy the Exchange ActiveSync client request to the Exchange server %1. For this to work, ...
  47. The Client Access server doesn't have the InternalURL value set for the Microsoft-Server-ActiveSync virtual directory. This ...
  48. The Client Access server doesn't have the InternalURL value set for the Microsoft-Server-ActiveSync virtual directory. This ...
  49. The Client Access server is running the following version of Microsoft Exchange: {0}, but a Client Access server running ...
  50. The Client Access server role cannot be upgraded. Remove the current role using 'Add or Remove Programs' in the Control Panel, ...
  51. The Client Access server role enables clients to connect to their Exchange mailbox through Outlook Web App, POP, IMAP, or ...
  52. The Client Access server version doesn't match the Mailbox server version of the resource that was being accessed. To determine ...
  53. The Client Access server wasn't specified. You can use the UseAutodisoverForClientAccessServer parameter to use the Autodiscover ...
  54. The Client Access server {0} requires the proxy to use HTTPS, but the service URL uses HTTP. Set the registry key AllowProxyingWithoutSsl ...
  55. The client and server versions aren't compatible. The client protocol version is older than the version required by the server. ...
  56. The client operation failed because the application tried to pass one or more flags that the Microsoft Exchange Address Book ...
  57. The client operation failed because Unicode was requested, but the Microsoft Exchange Address Book does not support Unicode ...
  58. The Client Performance Report uses data reported by Outlook 2003 and newer clients to the Exchange server to provide insight ...
  59. The clock setting of this machine isn't synchronized with the clock setting of the Edge Transport server you are attempting ...
  60. The closed campus policy blocks any external e-mail traffic, except for the external domains or internal groups that have ...
  61. The cloud-based service failed to detect connection settings using Autodiscover. Please specify the connection settings manually ...
  62. The cluster group for database availability group '{0}' is missing. Please use the Set-DatabaseAvailabilityGroup cmdlet to ...
  63. The Cluster service couldn't access the Microsoft Failover Cluster Virtual Miniport network adapter. Verify that other network ...
  64. The cluster service doesn't appear to be running on server {0}. Make sure that the server is operating and that services ...
  65. The cmdlet extension agent configuration object for class factory "{1}" in assembly "{0}" is already defined in Active Directory. ...
  66. The cmdlet fails to find all the server information through pinging service providers or other topology discovery inside ...
  67. The cmdlet name should be in the format of "Cmdlet" or "Cmdlet,SnapIn". Neither the cmdlet name nor the snap-in name can ...
  68. The cmdlet running on "{0}" can't manipulate Alternate Service Accounts on "{1}". Run Connect-ExchangeServer "{1}" and retry ...
  69. The cmdlet you tried to run failed because your remote PowerShell session expired. Your session will be automatically reconnected ...
  70. The combined processor time spent in the store.exe and inetinfo.exe is more than {8}%. This may result in mail delays. Actual ...
  71. The command failed when running as user '{0}'. Please contact your administrator to assign the appropriate role(s) to your ...
  72. The comment cannot be set on this managed folder. Comments cannot be set on the Calendar, Contacts, Journal, Notes and Tasks ...
  73. The compliance label you selected couldn't be set because Information Rights Management has been disabled in Outlook Web ...
  74. The compliance label you selected couldn't be set because the Rights Management server is unavailable. Please try again in ...
  75. The compliance label you selected couldn't be set. It's possible the compliance label has been removed or you don't have ...