UI Translation

Exchange Server 2007

  1. Table was marked as in use while releasing a database session on database "%4". Problem will automatically be fixed. Table ...
  2. Tag: {0} in the Sync request is not from the Contacts or Contacts2 namespace. Confirm that the tag you including is part ...
  3. Target node '{0}' is outside of Move-ClusteredMailboxServer criteria. Move-ClusteredMailboxServer will be blocked to prevent ...
  4. Target routing group %1 was not found for routing group connector %2 in routing tables with timestamp %3; skipping the connector. ...
  5. Task has copied current web distribution files for offline address book "{0}" to the target server. You can back up and remove ...
  6. Test mailbox does not reside on correct server. This may have occurred because the test user's mailbox was moved. User name: ...
  7. Testing {0} connectivity using the given mailbox credential by creating a mail with unique subject and delete the created ...
  8. Thank you for your participation in the Microsoft Exchange Server beta program. The license to use this beta version of the ...
  9. Thank you for your participation in the Microsoft Exchange Server beta program. Your license to use this beta version of ...
  10. Thank you for your submission. Please note that submissions to some folders or discussion groups are reviewed to determine ...
  11. The "Internet Information Services Snap-In" component of the Microsoft Internet Information Services (IIS) is either not ...
  12. The %1 attribute on the Information Store object in the Active Directory has been configured with a value of %2, which exceeds ...
  13. The '%s' service is in '%s' state. It is highly recommended to start this service before continuing this operation. Do you ...
  14. The 'Host' (A) record for server {2} cannot be retrieved from DNS server '{1}'. This can cause message routing delays and ...
  15. The 'Host' (A) record for server {2} could not be retrieved from DNS server {1}. This can cause mail routing delays and other ...
  16. The 'Local delivery' queue ({3}) on server {2} holds more than 100 messages. Source: '{4}'. Number of messages in the queue: ...
  17. The 'Local delivery' queue ({3}) on server {2} is frozen. Number of message(s) in the queue: {9}. This queue needs to be ...
  18. The 'Local delivery' queue ({3}) on server {2} is frozen. Source: '{4}'. Number of message(s) in the queue: {9}. This queue ...
  19. The 'Local delivery' queue ({3}) on server {2} is in retry status. Number of message(s) in the queue: {9}. Additional status ...
  20. The 'Local delivery' queue ({3}) on server {2} is in retry status. Source: '{4}'. Number of message(s) in the queue: {9}. ...
  21. The 'Messages awaiting directory lookup' queue ({3}) on server {2} holds more than 50 messages. Source: '{4}'. Number of ...
  22. The 'Messages awaiting directory lookup' queue ({3}) on server {2} is frozen. Source: '{4}'. Number of message(s) in the ...
  23. The 'Messages awaiting directory lookup' queue ({3}) on server {2} is in retry status. Source: '{4}'. Number of message(s) ...
  24. The 'Messages pending submission' queue ({3}) on server {2} holds more than 50 messages. Number of messages in the queue: ...
  25. The 'Messages pending submission' queue ({3}) on server {2} holds more than 50 messages. Source: '{4}'. Number of messages ...
  26. The 'Messages pending submission' queue ({3}) on server {2} is frozen. Number of message(s) in the queue: {9}. This queue ...
  27. The 'Messages pending submission' queue ({3}) on server {2} is frozen. Source: '{4}'. Number of message(s) in the queue: ...
  28. The 'Messages pending submission' queue ({3}) on server {2} is in retry status. Number of message(s) in the queue: {9}. Additional ...
  29. The 'Messages pending submission' queue ({3}) on server {2} is in retry status. Source: '{4}'. Number of message(s) in the ...
  30. The 'Messages waiting to be routed' queue ({3}) on server {2} holds more than 50 messages. Source: '{4}'. Number of messages ...
  31. The 'Messages waiting to be routed' queue ({3}) on server {2} is frozen. Source: '{4}'. Number of message(s) in the queue: ...
  32. The 'Messages waiting to be routed' queue ({3}) on server {2} is in retry status. Source: '{4}'. Number of message(s) in ...
  33. The 'Messages with an unreachable destination' queue ({3}) on server {2} holds one or more messages. Source: '{4}'. Number ...
  34. The 'Messages with an unreachable destination' queue ({3}) on server {2} is frozen. Source: '{4}'. Number of message(s) in ...
  35. The 'Messages with an unreachable destination' queue ({3}) on server {2} is in retry status. Source: '{4}'. Number of message(s) ...
  36. The 'MNSFileShare' path cannot be verified. This may be due to the current account not having access to the file share. Check ...
  37. The 'MNSFileShare' path exists but {9} node(s) exist in the cluster. The majority node set with file share witness facility ...
  38. The 'MX' record(s) of domain {1} are {4}, but the 'Host' records of the servers indicated by the 'MX' records cannot be obtained ...
  39. The 'Remote delivery' queue ({3}) on server {2} holds more than 100 messages. Source: '{4}'. Number of messages in the queue: ...
  40. The 'Remote delivery' queue ({3}) on server {2} is frozen. Number of message(s) in the queue: {9}. This queue needs to be ...
  41. The 'Remote delivery' queue ({3}) on server {2} is frozen. Source: '{4}'. Number of message(s) in the queue: {9}. This queue ...
  42. The 'Remote delivery' queue ({3}) on server {2} is in retry status. Number of message(s) in the queue: {9}. Last error information: ...
  43. The 'Remote delivery' queue ({3}) on server {2} is in retry status. Source: '{4}'. Number of message(s) in the queue: {9}. ...
  44. The 'Servers' container cannot be found for administrative group '{3}'. This may be causing backups in the queue. Check the ...
  45. The 'UseBasicAuthToBE' registry value is set to 1 on server {2}. This will allow the front-end server to use basic, rather ...
  46. The 'VM Largest Block Size' on server {2} is low and may cause reliability problems. Current largest block size is {9} MB. ...
  47. The 'VM Largest Block Size' on server {2} is reaching a critical level and may cause reliability problems. Current largest ...
  48. The '{0}' counter on server {2} is averaging more than {8}. This may indicate that server {2} is experiencing a performance ...
  49. The '{0}' service on server {2} is set to be started manually. The service should be set to 'Automatic' because Exchange ...
  50. The '{1}' class is not part of the '{4}' for group objects. This may cause Exchange server instability such as Recipient ...
  51. The '{1}' interval for database '{3}' on server {2} has been modified from default. This configuration is only recommended ...
  52. The '{1}' interval for database '{3}' on server {2} has been modified from default. This configuration is recommended only ...
  53. The '{1}' interval for database '{3}' on server {2} has been modified from default. This configuration is recommended only ...
  54. The '{1}' queue average length exceeds {8} messages and number of messages entering the '{1}' queue ({2}) is greater than ...
  55. The '{1}' value on Exchange cluster {2} is too small and may cause fail-over problems. The recommended value is 4194304 (4096 ...
  56. The '{4}' attribute for administrative group '{3}' does not match the parent organization. This may cause mail flow problems. ...
  57. The '{4}' attribute for administrative group '{3}' is not well-formed. This may cause mail flow problems. Current '{4}' value: ...
  58. The '{4}' attribute for Exchange server {2} does not match the parent administrative group. This will cause reliability problems. ...
  59. The '{4}' attribute for mailbox store '{3}' on server {2} does not correspond to the hosting server. This will cause reliability ...
  60. The '{4}' attribute for public store '{3}' on server {2} does not match the hosting server. This will cause reliability issues. ...
  61. The '{4}' attribute for Recipient Update Service '{3}' contains data. The Recipient Update Service is currently processing ...
  62. The '{4}' attribute for Recipient Update Service '{3}' contains old data that was not fully processed. This data has existed ...
  63. The '{4}' attribute for the Exchange organization is not well-formed and may cause functionality problems. Current '{4}' ...
  64. The '{4}' attribute value ({1}) for Accepted Domain '{0}' in Active Directory Application Mode (ADAM) instance on server ...
  65. The '{4}' binding for server {2} does not contain a fully-qualified domain name. This can cause service failures. Current ...
  66. The '{4}' binding for server {2} does not match the DNS resolved name. This can cause mail routing problems. Current '{7}' ...
  67. The '{4}' configuration parameter is set to {9} on server {2} (default is {8}). If set incorrectly, this value may cause ...
  68. The '{4}' configuration setting is enabled on server {2}. This setting will prevent users from accessing resources on this ...
  69. The '{4}' has changed from its default of '{7}' on server {2}. This may cause communication problems. Current value: {1}. ...
  70. The '{4}' HTTP parameter on server {2} is set to {9}. This may cause Outlook Web Access and Exchange ActiveSync connections ...
  71. The '{4}' is set on server {2}. It is possible that either the Exchange or Outlook client is installed on the server. Current ...
  72. The '{4}' parameter is set to '{9}' on server {2}. This may cause synchronization errors for Exchange ActiveSync clients. ...
  73. The '{4}' property of SMTP instance '{3}' on server {2} is set to 'False'. Verify that this setting is not preventing internal ...
  74. The '{4}' queue on server {2} has messages addressed to global distribution group '{3}', while the topology appears to be ...
  75. The '{4}' registry entry for mailbox store '{3}' on server {2} contains data. This database has experienced problems with ...
日本語
Japanese English
English (United States)