UI Translation

Exchange Server 2016

  1. The WebReady Document Viewing worker process didn't initialize. It will try again to initialize. Exception message: "%1". ...
  2. The WebReady Document Viewing worker process fails when it converts documents. Document information: User Display Name = ...
  3. The well-known object entry '{0}' already exists in attribute 'otherWellKnownObjects' on container object {1}. It may point ...
  4. The well-known object entry with the GUID "{0}", which is on the "{1}" container object's otherWellKnownObjects attribute, ...
  5. The well-known object entry {0} on the otherWellKnownObjects attribute in the container object {1} points to an invalid DN ...
  6. The Windows Cluster service has been manually disabled on '{0}'. However '{0}' is a member of a database availability group. ...
  7. The Windows Cluster service is currently installed and manually enabled on '{0}'. However, '{0}' is not a member of a database ...
  8. The Windows Failover Cluster service has been crashing {0} times for {1} hour(s) for a duration of {2} hours. The most recent ...
  9. The Windows Failover Cluster service has not been running for {0} minutes. A restart of the service was attempted 10 minutes ...
  10. The Windows Failover Cluster service is installed on this computer. The computer must not be a member of a cluster prior ...
  11. The Windows Installer (msiservice) service is either disabled or not installed on this computer. You must exit Setup, install ...
  12. The Windows Live ID {0} is already associated with another recipient {1}. A Windows Live ID can be associated with only one ...
  13. The Windows Management Instrumentation (WMI) service on server {0} isn't configured to start-up as the computer account (LocalSystem). ...
  14. The Windows Management Instrumentation (WMI) service on server {2} is not configured to start-up as the computer account ...
  15. The Windows PowerShell fan-in provider assembly "{0}" wasn't found. Make sure it's not manually deleted during the setup ...
  16. The Windows PowerShell runspace failed to open in server '%1', for service instance '%2', reported the following error: %3 ...
  17. The Windows PowerShell virtual directory application pool '{0}' doesn't exist in '{1}'. The configuration file may be corrupted. ...
  18. The Windows Remote Management WS-Management (winrm) service is either disabled or not installed on this computer. You must ...
  19. The WindowsLiveId property for account "{0}" can't be changed to "{1}" because domains "{2}" and "{3}" support a different ...
  20. The witness server and directory currently in use by database availability group '{0}' doesn't match the configured primary ...
  21. The wizard helps you collect organizational health data. The health data displays on the Organizational Health tab. Depending ...
  22. The working directory for the Microsoft Exchange Information Store service on server {2} cannot be verified. This can cause ...
  23. The World Wide Web (W3SVC) service is either disabled or not installed on this computer. You must exit Setup, install the ...
  24. The World Wide Web Publishing Service (W3SVC) isn't running on any Exchange servers in the site. If you want to connect to ...
  25. The World Wide Web Services component of the Microsoft Internet Information Services (IIS) is either not installed or disabled ...
  26. The Write DACL inherit (group) right for the Exchange Enterprise Servers group isn't configured at the root of your Active ...
  27. The Write DACL inherit (group) right for the Exchange Enterprise Servers group should be removed from the root of the domain. ...
  28. The Write DACL inherit (group) right for the Exchange Enterprise Servers group should be removed from the root of your Active ...
  29. The X.400 address defined in recipient policy '{0}' does not have a semicolon as the terminating character. This can cause ...
  30. The X.400 address defined in recipient policy '{3}' does not have a semicolon as the terminating character. This can cause ...
  31. The X.400 address for the site is required for this operation, but it has been removed from the site object. Use Raw Properties ...
  32. The X.400 address has an invalid country or region code. The country or region code must contain either 2 alphabetic characters ...
  33. The {0} app couldn't be updated. The app that's currently installed must be uninstalled before the updated app can be installed. ...
  34. The {0} cmdlet is version-specific. The version of the target Mailbox server is {1} . Run the {1} version of the {0} cmdlet. ...
  35. The {0} cmdlet will be removed in a future version of Exchange. Use the {1} cmdlet instead. If you have any scripts that ...
  36. The {0} command that you are trying to run, which is version {1}, requires that the target mailbox account is on a Mailbox ...
  37. The {0} domain can't be reached. Because of this, the Domain Admins group for the domain won't be granted permissions to ...
  38. The {0} health set has detected a problem on {1} beginning at {Monitor.FirstAlertObservedTime} (UTC). Error: {Probe.Error}. ...
  39. The {0} Health Set has detected a problem with {1} at {2}. Attempts to auto-recover from this condition have failed and requires ...
  40. The {0} Health Set has detected a problem with {1} at {2}. The availability is {3}. The Health Manager is reporting that ...
  41. The {0} Health Set has detected a problem with {1} at {2}. The Health Manager is reporting that {0}. Attempts to auto-recover ...
  42. The {0} Health Set has detected a problem with {1} at {2}. The Health Manager is reporting that {0}. Attempts to auto-recover ...
  43. The {0} Health Set has detected a problem with {1} at {2}. {3} failures were found. The Health Manager is reporting that ...
  44. The {0} Health Set has detected a problem with {1}. The Health Manager is reporting that {Probe.Error}. Please investigate. ...
  45. The {0} is connecting to {1} to check for updates. There may be updates to the tool, or there may be updates to the configuration ...
  46. The {0} is connecting to {1} to check for updates. There may be updates to the tool, or there may be updates to the configuration ...
  47. The {0} is verifying that you've got network connectivity and the permissions to access Active Directory. The tool needs ...
  48. The {0} management scope has the same RecipientRoot, RecipientFilter, ServerFilter, ScopeRestrictionType or Exclusive property ...
  49. The {0} management scope object is used by one or more management role assignments. You must have all of the associated management ...
  50. The {0} must have read access to Active Directory. By default the tool will use the currently logged-on account, and will ...
  51. The {0} process has crashed at least {1} times in last {2} minutes. Watson Message: {Probe.StateAttribute1}Inference Classification ...
  52. The {0} process has crashed at least {1} times in last {2} minutes. Watson Message: {Probe.StateAttribute1}Inference Training ...
  53. The {1} object '{3}' has the same '{4}' value ({5}) as another {1} object in the topology. This will cause network problems. ...
  54. The {1} object '{3}' has the same '{4}' value ({5}) with another {1} object in the topology. This may prevent the Microsoft ...
  55. The {1} path is located on the same drive as the system partition. This may cause store performance problems. The current ...
  56. The {1} path on server {2} is located on the same drive as the system partition. This may cause performance problems. Current ...
  57. The {1} plug-in for {0} is running on server {2}. Messages to remote domains and servers may back up in queues or users may ...
  58. The {4} application is installed on server {2}. This should only be used when troubleshooting Exchange mail flow problems. ...
  59. The {4} value for SMTP instance '{3}' on server {2} has been altered from its default of 0. This will cause mail flow problems ...
  60. The {Probe.ServiceName} health set has detected a problem and your immediate attention is required. The problem began at ...
  61. The {Probe.ServiceName} health set has detected a problem and your immediate attention is required. The problem begun at ...
  62. The {Probe.ServiceName} health set has detected a problem on {Probe.MachineName} beginning at {Monitor.FirstAlertObservedTime} ...
  63. The {Probe.ServiceName} health set has detected a problem on {Probe.MachineName} beginning at {Monitor.FirstAlertObservedTime} ...
  64. The {Probe.ServiceName} health set has detected a problem on {Probe.MachineName} beginning at {Monitor.FirstAlertObservedTime} ...
  65. The {Probe.ServiceName} health set has detected a problem that couldn't be resolved automatically beginning at {Monitor.FirstAlertObservedTime} ...
  66. There appears to be a problem with extended SMTP verb advertising for SMTP instance '{3}' on server {2}. This may cause message ...
  67. There appears to be zero recipient policies, or the 'Recipient Policies' container is missing from the organization. This ...
  68. There appears to be zero recipient policies, or the '{3}' container is missing from the organization. This can cause message ...
  69. There appears to be zero system policies, or the 'System Policies' container is missing from the organization. This can cause ...
  70. There appears to be zero system policies, or the '{3}' container is missing from the organization. This can cause message ...
  71. There are a total of {0} FailedAndSuspended database copies from multiple different volumes. This likely indicates that there ...
  72. There are attachments in the "Outlook Secure Temporary File". You may need to remove them if you run into attachment issues. ...
  73. There are circumstances where the replay service may automatically suspend a database copy and that copy can be safely resumed. ...
  74. There are insufficient resources to perform a database operation. The Microsoft Exchange Transport service is shutting down. ...
  75. There are locally federated domains that aren't present in the list of domains for the remote organization relationship object. ...
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)