UI Translation

Exchange Server 2007

  1. The background scan of the transport queue database has been stopped. %1 message(s) found so far. There may be other messages ...
  2. The background scanning progress value under the registry key '%1' is invalid. The error code is %2. Background scanning ...
  3. The backup database %4 must be a multiple of 4 KB. For more information, click http://www.microsoft.com/contentredirect.asp. ...
  4. The backup has been stopped because it was halted by the client or the connection with the client failed. For more information, ...
  5. The backup has been stopped prematurely (possibly because the instance is terminating). For more information, click http ...
  6. The backup procedure has been successfully completed. For more information, click http://www.microsoft.com/contentredirect.asp. ...
  7. The basic input/output system (BIOS) on server {2} (model {0}) requires an update. Data corruption may result if the BIOS ...
  8. The bootstrap account specified in the subscription file indicates it will expire in the next 5 minutes. To ensure proper ...
  9. The build version on the target node is not compatible with the clustered mailbox server (CMS) version. The CMS resource ...
  10. The bulk e-mail address operation ran out of memory. E-mail addresses for display name '%1' (mailbox name '%2') were unchanged. ...
  11. The cabinet file '[2]' required for this installation is corrupt and cannot be used. This could indicate a network error, ...
  12. The calendar configuration is corrupt and has been recreated. All previous settings have been erased. Please reconfigure ...
  13. The calendaring agent cannot bind to the appointment with the subject "%1" in mailbox %2 because the appointment is missing ...
  14. The calendaring agent could not publish the free/busy information for "%1" because it failed reading the registry with error: ...
  15. The calendaring agent did bind to the appointment with the subject "%1" in mailbox %2, but the appointment is missing an ...
  16. The CAS-to-CAS Proxy request failed because the request format was either malformed or the request had a corrupted SID header. ...
  17. The certificate for the URL {0} is incorrect. For SSL to work it needs to have a subject of {1}, instead the subject was ...
  18. The certificate that is used to establish secure communication with an IP/VoIP gateway using Transport Layer Security (TLS) ...
  19. The character '{4}' is invalid for file extensions. It was found in character {3} of "{2}" in element {1} of the {0} array. ...
  20. The checkpoint file path for storage group '{3}' on server {2} ({5}) does not match the transaction log path ({1}). This ...
  21. 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 ...
  22. The CIDR length {0} is greater than the maximum of 128 for an IPv6 address. An acceptable CIDR length is in the range 0, ...
  23. 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 ...
  24. The Client Access server role cannot be upgraded. Remove the current role using Control Panel, then install the newer version ...
  25. The Client Access server role enables clients to connect to their Exchange mailbox through Outlook Web Access, POP, IMAP, ...
  26. The client operation failed because the application tried to pass one or more flags that the Microsoft Exchange Address Book ...
  27. The client operation failed because Unicode was requested, but the Microsoft Exchange Address Book does not support Unicode ...
  28. The cluster continuous replication configuration for storage group {0} failed to create an invalid directory with path {1}. ...
  29. The cluster continuous replication configuration for storage group {0} failed to remove log file {1} with exception message ...
  30. The cluster service account '{0}' does not have sufficient permissions to bring the Exchange Information Store online. The ...
  31. The cluster service account '{0}' does not have sufficient permissions to create a computer account. The account must have ...
  32. The Clustered Mailbox role provides high availability, redundant e-mail storage, and advanced scheduling services for mailbox-enabled ...
  33. The clustered mailbox server '{0}' did not complete its startup (online) transition. Review the event log to identify the ...
  34. The Clustered Mailbox Server provides highly available, redundant e-mail storage and advanced scheduling services for Microsoft ...
  35. The clustered mailbox server's group '{0}' was found; however, it is not a valid clustered mailbox server. Verify you specified ...
  36. The clustered mailbox server's specified IP address ({0}) could not be used because it is already in use. Please re-run setup ...
  37. The combined processor time spent in the store.exe and inetinfo.exe is more than {8}%. This may result in mail delays. Actual ...
  38. The comment cannot be set on this managed folder. Comments cannot be set on the Calendar, Contacts, Journal, Notes and Tasks ...
  39. The computer account "%s" is not a member of the group "%s". When you are using an account that has been delegated the Full ...
  40. The computer account '{0}' was created on the domain controller '{1}', but has not replicated to the desired domain controller ...
  41. The computer account for Active Directory server {2} does not appear to contain the fully-qualified domain name of the Active ...
  42. The computer account for Active Directory server {2} does not appear to contain the fully-qualified domain name of the Active ...
  43. The computer account for Active Directory server {2} does not appear to contain the NetBIOS name of the Active Directory ...
  44. The computer account for Active Directory server {2} does not appear to contain the NetBIOS name of the Active Directory ...
  45. The computer account for Exchange server {2} does not appear to contain the fully-qualified domain name of Exchange SMTP ...
  46. The computer account for Exchange server {2} does not appear to contain the fully-qualified domain name of Exchange SMTP ...
  47. The computer account for Exchange server {2} does not appear to contain the fully-qualified domain name of the Exchange server ...
  48. The computer account for Exchange server {2} does not appear to contain the fully-qualified domain name of the Exchange server ...
  49. The computer account for Exchange server {2} does not appear to contain the fully-qualified domain name of the Exchange server ...
  50. The computer account for Exchange server {2} does not appear to contain the fully-qualified domain name of the Exchange server ...
  51. The computer account for Exchange server {2} does not appear to contain the NetBIOS name of the Exchange server for the '{3}' ...
  52. The computer account for Exchange server {2} does not appear to contain the NetBIOS name of the Exchange server for the '{3}' ...
  53. The computer account for Exchange server {2} does not appear to contain the NetBIOS name of the Exchange server for the '{3}' ...
  54. The computer account for Exchange server {2} does not appear to contain the NetBIOS name of the Exchange server for the '{3}' ...
  55. The computer account for the network name '{0}' was created on the domain controller '{1}'. Now checking on domain controller ...
  56. The computer account for the network name '{0}' was found on the domain controller '{1}', after approximately {2} seconds. ...
  57. The computer name specified is a simple name. Please use a fully-qualified domain name system name (for example, "server.domain.contoso.com" ...
  58. The configuration name is not valid. It may contain characters that are not supported. Use a string that contains only ASCII ...
  59. The configuration of one of the SMTP Receive connectors is invalid. The configuration change will be ignored. The description ...
  60. The configuration type used is not supported by current configuration object. ConfigType(defined) = {0}, ConfigType(used) ...
  61. The configured proxy URL '{0}' does not specify that Secure Sockets Layer (SSL) be used. The use of SSL is only supported ...
  62. The configured server role is invalid for this service. The Microsoft Exchange Transport Log Search service can only run ...
  63. The connection between the Client Access server and Mailbox server "%1" failed. If this event is logged infrequently or only ...
  64. The connection from IP address %1 is being dropped. The rate of connections from this IP address has exceeded the configured ...
  65. The connection from IP address %1 is being dropped. The rate of message submissions from this IP address has exceeded the ...
  66. The connection has been dropped between servers. This code may be caused by transient network issues or servers that are ...
  67. The connection to mailbox "%1" on Mailbox server "%2" failed. Examine the event log of Mailbox server "%2". More information ...
  68. The connection to secure domain '%1' on connector '%2' failed because Transport Layer Security (TLS) negotiation was unsuccessful. ...
  69. The connection to secure domain '%1' on Send connector '%2' failed because Transport Layer Security (TLS) negotiation failed ...
  70. The connector (GUID: {1}) found in the link state information maintained by server {2} cannot be resolved to an object in ...
  71. The connector (GUID: {1}) found in the link state information maintained by server {2} was successfully resolved to the connector ...
  72. The container or group referred to by the well-known GUID '{0}' could not be found on the domain controller {1}. Retry in ...
  73. The content cannot be displayed because the sender of this message used S/MIME to encrypt the content, or signed it with ...
  74. The content filter acts on messages according to their spam confidence level (SCL) rating and the following SCL thresholds ...
  75. The Content Filtering feature filters junk e-mail by using a probability-based algorithm that can learn what is and what ...
日本語
Japanese English
English (United States)