UI Translation

Exchange Server 2016

  1. The Outlook Web App configuration settings couldn't be read and updated. Virtual directory: "%1". Web site: "%2". Error message: ...
  2. The Outlook Web App configuration settings couldn't be read and updated. Virtual directory: "%1". Web site: "%2". Error message: ...
  3. The Outlook Web App forms-based authentication Web service extension couldn't be found: module {1} GroupID {0} Run the u ...
  4. The Outlook Web App template file '{5}' on server {2} has a later build number than front-end servers in the administrative ...
  5. The OWACalendarAppPool request failed with the error below. Error Code: {Probe.StateAttribute4} Error Type: {Probe.StateAttribute5} ...
  6. The OWAEnabled property of mailbox '{0}' isn't in a consistent state. Reset the OWAEnabled property using the Set-CASMailbox ...
  7. The paging file size ({0}) is less than the physical memory size ({1}) plus 10 MB. It's recommended that the paging file ...
  8. The paging file size ({8}) is less than the physical memory size ({9}) plus 10 MB. It is recommended that the paging file ...
  9. The parameter %1 was not set to one value by the previous ESE application instance, but set to a different value from the ...
  10. The parameter %1 was not set via the previous ESE application instance, but is set in the current ESE application. This is ...
  11. The parameter %1 was set via the previous ESE application instance, but is not set in the current ESE application. This is ...
  12. The parameter %4 was attempted to be set to %5, but was overridden to %6 by the registry settings (at %7). For more information, ...
  13. The parameter %4 was not set to one value by the previous ESE application instance, but set to a different value from the ...
  14. The parameter %4 was not set via the previous ESE application instance, but is set in the current ESE application. This is ...
  15. The parameter %4 was read from the registry settings (at %7), but the ESE engine rejected the value %5 with err %6. For more ...
  16. The parameter %4 was set via the previous ESE application instance, but is not set in the current ESE application. This is ...
  17. The parameter '{0}' isn't currently allowed in your organization. To use this parameter, you first need to run the command: ...
  18. The parameter '{0}' length of '{1}' is too long. Shorten the length to less than or equal to '{2}' and then try the command ...
  19. The parameter name for the Live Views data hash which is used to verify the authenticity of the Live Views metadata in the ...
  20. The parameters 'ResetUrl', 'SearchableUrlEnabled', 'PublishDateRangeFrom', 'PublishDateRangeTo' or 'DetailLevel' cannot be ...
  21. The Parameters parameter is required. If you want to remove all the existing parameters for the specified management role ...
  22. The parameters passed to the cmdlet represent a federated account, which doesn't match the namespace state, which is managed. ...
  23. The parameters passed to the cmdlet represent a federated account, which doesn't match the tenant's service plan to support ...
  24. The parameters passed to the cmdlet represent a managed account, which doesn't match the namespace state, which is federated. ...
  25. The parameters passed to the cmdlet represent a managed account, which doesn't match the tenant's service plan to support ...
  26. The parent Legacy Exchange DN container value '%1' was not found during generation of the differential update file for offline ...
  27. The password for Windows LiveID is invalid. Try again using a password which has the same length as the original password. ...
  28. The patch page read from the file "%1" at offset %2 for %3 bytes failed verification due to a page checksum mismatch. The ...
  29. The patch page read from the file "%1" at offset %2 for %3 bytes failed verification due to a page number mismatch. The expected ...
  30. The patch page read from the file "%4" at offset %5 for %6 bytes failed verification due to a page checksum mismatch. The ...
  31. The patch page read from the file "%4" at offset %5 for %6 bytes failed verification due to a page number mismatch. The expected ...
  32. The path "{0}" doesn't exist on the remote server "{1}". The Microsoft Exchange File Distribution service will create it ...
  33. The path for the PowerShell virtual directory '{0}' has been changed to '{1}'. This can cause the Exchange Management Tools ...
  34. The path for the PowerShell virtual directory '{1}' has been changed to '{2}'. This can cause the Exchange Management Tools ...
  35. The path must reside on a local fixed disk. If operating on a cluster, it must reside on a disk shared by all physical nodes. ...
  36. The path of virtual directory '{3}' on server {2} doesn't match the 'folderPathName' or 'msExchDefaultDomain' attributes ...
  37. The path to the language pack bundle wasn't found or reachable. Setup can't continue. Please see the Setup log for for more ...
  38. The path to the language pack bundle wasn't found or reachable. Setup can't continue. See the Setup log for for more details. ...
  39. The path to the protocol logging location for Receive connectors has not been set. No protocol log for Receive connectors ...
  40. The people relevance feeder for mailbox %1 picked %2 sent items to process. Number of sent items successfully processed %3 ...
  41. The performance counter '%1' sustained a value of '%2', for the '%3' minute(s) interval starting at '%4'.%5 Trigger Name:%6. ...
  42. The performance data log file has been divided into 20-minute increments. Please select the time range in which the performance ...
  43. The periodic database shrink file operation finished successfully and shrunk the database file by %4 pages. For more information, ...
  44. The periodic database shrink file operation started. For more information, click http://www.microsoft.com/contentredirect.asp. ...
  45. The periodic database shrink file operation was not able to shrink the database file because there is not enough internal ...
  46. The periodic database shrink file operation was not able to shrink the database file because there is not enough internal ...
  47. The periodic database shrink file operation was not able to shrink the database file. Result %4. For more information, click ...
  48. The personal greeting is played to callers who request to leave a message when your extension is either busy or there is ...
  49. The personal greeting is played to callers who request to leave a message when your phone number is either busy or there ...
  50. The phone number for "{0}" is not in a standard international format. The following number is an example of the correct format: ...
  51. The phone number isn't in a standard international format. The following number is an example of the correct format: +1 (425) ...
  52. The phone number you entered, {0} , doesn't comply with the dialing restrictions configured by your voice mail administrator. ...
  53. The phone number {0} hasn't been set as your notification phone number. If you want to receive text messages on {0}, please ...
  54. The Pickup directory doesn't have permissions to write the pickup location to registry (%1). Please make sure Network Service ...
  55. The Pickup directory doesn't have the necessary Read permissions and Delete Subfolders and Files permissions for Pickup directory ...
  56. The pilot identifer "{0}" isn't a valid SIP address. The following is an example of a valid address: sip:[email protected]. ...
  57. The PIN you entered is not valid. Your PIN must contain only numbers, and must be at least {0} digits long. It cannot be ...
  58. The PIN you entered isn't valid. Your PIN must contain only numbers, and must be at least {0} digits long. It can't be the ...
  59. The Pointer (PTR) record {1} does not match any fully-qualified domain name of the SMTP instances on server {2}. This may ...
  60. The poison message component couldn't access the registry information. Locate the registry location and verify that the Network ...
  61. The poison message component couldn't access the registry information. Locate the registry location and verify that the Network ...
  62. The poison message component couldn't access the registry information. Verify that the Network Service account or the account ...
  63. The policy change has been saved, but deployment to '{0}' has been delayed by interim Office 365 datacenter issues. Please ...
  64. The Polling Interval specifies the frequency that this distribution point checks for updated OAB files. An interval of 0 ...
  65. The POP3 service failed to connect using SSL or TLS encryption. No valid certificate is configured to respond to SSL/TLS ...
  66. The port number specified for {0} does not match the port number specified for UnEncryptedOrTLSBindings/SSLBindings. {1} ...
  67. The port used by Active Directory Application Mode (ADAM) is configured correctly to block to outside access. ADAM is listening ...
  68. The port used by Active Directory Application Mode (ADAM) should be blocked to outside access. ADAM is listening on port ...
  69. The PowerShell virtual directory '{1}' has been configured to require SSL. This can cause the Exchange Management Tools to ...
  70. The PreferLocalXML value was found in the registry. This value is used by Autodiscover, but it can cause problems if your ...
  71. The prerequisite check that ensures access to the Microsoft download site will be bypassed according to the specified command-line ...
  72. The previous archive '{1}' of user '{0}' can't be found in the database. The recovery of the archive failed. This can occur ...
  73. The previous database '{1}' which stored the archive for user '{0}' is no longer available. The recovery of archive failed. ...
  74. The previous execution of the compliance search "{0}" either had too many errors or took place too long ago to be resumed. ...
  75. The previous execution of the compliance search action "{0}" either had too many errors or took place too long ago to be ...
Deutsch (Deutschland)
German (Germany) Español (España)
Spanish (Spain) Français (France)
French (France) italiano
Italian 日本語
Japanese 한국어
Korean Português
Portuguese Русский
Russian English
English (United States)