Exchange Server 2010

  1. The Exchange Server User Monitor (ExMon) RPC data indicates that the user '{3}' is performing online operations of type MAPI ...
  2. The Exchange Server User Monitor (ExMon) RPC data indicates that the user '{3}' is performing synchronization operations ...
  3. The Exchange Server User Monitor (ExMon) RPC data indicates that the user '{3}' may be building new views, which is causing ...
  4. The Exchange server {2} wasn't found in Active Directory on server {1}. Please provide the CMS name for the Exchange server. ...
  5. The Exchange store %1 has unlimited storage capacity. The current physical size of this database (the .edb file) is %3 GB. ...
  6. The Exchange store %1 has unlimited storage capacity. The current physical size of this database (the .edb file) is %3 GB. ...
  7. The Exchange store %1 is limited to %2 GB. The current physical size of this database (the .edb file) is %3 GB. If the physical ...
  8. The Exchange store %1 is limited to %2 GB. The current physical size of this database (the .edb file) is %3 GB. If the physical ...
  9. The Exchange transport on server {2} will not expand membership of distribution groups when checking restrictions. This configuration ...
  10. The Exchange UMIPGateway objects weren't created. Please verify that you're a member of the Organization Management role ...
  11. The Exchange Virtual Server can not be upgraded by the Cluster Administrator tool on this computer. To upgrade this Exchange ...
  12. The Exchange Virtual Server can not be upgraded on this cluster node. To upgrade this Exchange Virtual Server, take the System ...
  13. The executable file "{0}" for the UM worker process doesn't exist. To resolve this issue, copy the executable file located ...
  14. The executable file "{0}" for the UM worker process doesn't exist. To resolve this issue, copy the executable file located ...
  15. The executable files for all the transport event sinks found in the metabase of server {2} are identified and found on disk. ...
  16. The execution time of agent '%1' exceeded %2 milliseconds while handling event '%3' for message with InternetMessageId: '%4'. ...
  17. The execution time of agent '%1' exceeded %2 milliseconds while handling event '%3' for message with InternetMessageId: '%4'. ...
  18. The existence of the junk e-mail rule for mailbox %1 can't be confirmed. If the junk e-mail rule doesn't exist, unsafe messages ...
  19. The existence of the junk e-mail rule for mailbox %1 can't be confirmed. If the junk e-mail rule doesn't exist, unsafe messages ...
  20. The existing cmdlet extension agent's configuration is invalid. There are two cmdlet extension agents that share the same ...
  21. The existing cmdlet extension agents configuration is invalid because cmdlet extension agents "{1}" and "{2}" share the same ...
  22. The existing trusted publishing domain (TPD) named "{0}" came from a different source than the TPD you are trying to import. ...
  23. The ExistingResponse property was not stamped on virtual directory '{1}' on '{0}'. The return code is {2}. The error message ...
  24. The ExMon trace was captured for {1} seconds. Since it is normal for some users to use large amounts of CPU for periods of ...
  25. The expiration date for the rule has to be later than or the same as the current date. Please update the date and try again. ...
  26. The EXPR section, which typically specifies external settings required by ExRCA, wasn't found in the Autodiscover response. ...
  27. The extension is invalid or not supported. LDAP_MATCHING_RULE_BIT_AND(1.2.840.113556.1.4.803) and LDAP_MATCHING_RULE_BIT_OR(1.2.840.113556.1.4.804) ...
  28. The extension management pack with the ID '{0}' wasn't found on Operations Manager Root Management Server '{1}'. The extension ...
  29. The Extensions folder in the ILM installation directory can't be found. Verify that the folder wasn't renamed after the ILM ...
  30. The external e-mail address can't be changed because it's the primary SMTP address. Promote another SMTP address to primary ...
  31. The external identity mapping in mailbox '{0}' stored as entry {1} appears to have currupted its SID. Stored SID is {2} and ...
  32. The ExternalLicensingEnabled parameter can't be set to true because the organization isn't federated with the Microsoft Federation ...
  33. The federation certificate %1 has expired. Renew the certificate to ensure proper functionality of federation trust services. ...
  34. The federation certificate %1 has expired. Renew the certificate to ensure proper functionality of federation trust services. ...
  35. The federation certificate %1 will expire in less than 15 days. Renew the certificate soon to ensure proper functionality ...
  36. The federation certificate %1 will expire in less than 15 days. Renew the certificate soon to ensure proper functionality ...
  37. The Federation certificate with thumbprint "{0}" must have a unique Subject Key Identifier. The Subject Key Identifier "{2}" ...
  38. The Federation mailbox is misconfigured for this organization. Remote mailbox access will be disabled until this is resolved. ...
  39. The Federation mailbox is misconfigured for this organization. Remote mailbox access will be disabled until this is resolved. ...
  40. The Federation Metadata URL must specify an absolute path to the federation metadata document. No relative URL is allowed. ...
  41. The federation trust doesn't contain the same certificates published by the security token service in its federation metadata. ...
  42. The federation trust has changed to prepare for the usage of a new certificate for Federation. You should update all TXT ...
  43. The federation trust has changed to prepare for the usage of a new certificate for Federation. You should update all TXT ...
  44. The federation trust has changed to use a new certificate for Federation. You should update all TXT proof-of-ownership records ...
  45. The field %s contains an embedded null character. Data loss will occur if this value is translated to text. Do you want to ...
  46. The field %s contains an embedded null character. Data loss will occur if this value is translated to text. Do you want to ...
  47. The file "{0}" couldn't be found. You have to deploy this assembly again or disable the cmdlet extension agent that refers ...
  48. The file %4 is missing and could not be backed-up. For more information, click http://www.microsoft.com/contentredirect.asp. ...
  49. The file %4 is missing and could not be backed-up. For more information, click http://www.microsoft.com/contentredirect.asp. ...
  50. The file %s is in use by another application. Setup can't determine which application(s) or service(s) is using this file, ...
  51. The file '[2]' cannot be installed because the file cannot be found in cabinet file '[3]'. This could indicate a network ...
  52. The file '{0}' isn't in the correct format for custom greetings. The file format must be 'PCM/16bit/8Khz/Mono', because there ...
  53. The file CTL3D32.DLL on your computer is obsolete. Delete this file and then reinstall it from your Windows distribution ...
  54. The file name that was supplied isn't valid. The file name must not be an absolute or relative path and should have a .wma ...
  55. The file name wasn't detected because there are some invalid characters in "{1}", the alias of mailbox {0}. Please provide ...
  56. The file version of '%1' installed on the local server is not current. Looking at servers in the site for a current version. ...
  57. The file version of '%1' installed on the local server is not current. Looking at servers in the site for a current version. ...
  58. The file version of '%1' installed on the local server is not current. Unable to locate a correct version on any server in ...
  59. The file version of '%1' installed on the local server is not current. Unable to locate a correct version on any server in ...
  60. The file you are installing is older than the file it will replace. Do you want to continue installing and remove the existing ...
  61. The first argument in SipCultureInfo.CreateInstance should be a System.Globalization.CultureInfo object, not a derivative. ...
  62. The first Exchange Mailbox server installation in an Exchange 2000 or Exchange 2003 organization requires that you enable ...
  63. The flags of some items cannot be changed. Setting flags might not be supported for these items, or you might not have permission ...
  64. The flags of the items cannot be changed. Setting flags might not be supported for these items, or you might not have permission ...
  65. The folder could not be deleted. This may have occurred because the folder has already been moved or deleted by another user. ...
  66. The folder could not be moved or copied. This may have occurred because you don't have appropriate permission for the folder, ...
  67. The folder couldn't be deleted. This may have occurred because a folder with the same name already exists in the Deleted ...
  68. The folder identity of the public folder to operate against. If none is specified, then all the folders in the hierarchy ...
  69. The folder name can be modified only for a Managed Custom Folder. You cannot modify the folder name for managed default folder. ...
  70. The folder path specified in the URL doesn't point to an existing folder. Or, you may not have sufficient permissions to ...
  71. The FolderType attribute on the managed folder {0} has changed in the Active Directory. The folder type changed from {1} ...
  72. The following applications are using files that need to be updated by this setup. Close these applications and then click ...
  73. The following authentication methods are enabled, but they aren't allowed authentication methods for this service. Methods: ...
  74. The following categories of clients have latencies greater than the threshold value of {2} ms: {1}, as reported by the performance ...
  75. The following custom prompt files were not found for UM dial plan "%1": "%2". If new custom prompt files have been published ...