UI Translation

Exchange Server 2007

  1. The value for the '{0}' counter on server {2} is greater than zero (average value is {3}) and it appears that '{4}' is failing ...
  2. The value for the '{4}' parameter on server {2} is low and could cause instability. Consider increasing the value to 31000 ...
  3. The value for the '{4}' registry entry is set to zero on server {2}. This can cause severe reliability issues and problems ...
  4. The value for the '{4}' registry entry is set to {9} on server {2}. This may cause excessive memory usage on the server. ...
  5. The value for the '{4}' registry entry is set too high on server {2}. This can cause mail flow problems. Default value: {8} ...
  6. The value for the '{4}' registry entry is set too low on server {2}. This can cause degraded database performance and mail ...
  7. The value for the '{4}' registry entry on server {2} does not match the name of the local computer ({1}). This may cause ...
  8. The value for the '{4}' registry entry on server {2} has changed. Default value: {8} seconds. Current value: {9} seconds. ...
  9. The value for the '{4}' registry entry on server {2} has changed. Default value: {9} minutes. Current value: {8} seconds. ...
  10. The value for the '{4}' registry entry on server {2} has changed. This value should only be changed on the advice of Microsoft ...
  11. The value for the Exchange Installable File System (IFS) '{4}' registry entry on server {2} has changed. Current value: {9}. ...
  12. The value for the Extensible Storage Engine (ESE) transaction log file size for storage group '{3}' on server {2} has changed. ...
  13. The value for the Extensible Storage Engine (ESE) transaction log file size has changed on server {2}. This configuration ...
  14. The value for the IMAP4 '{4}' registry entry is set higher than {8} bytes on server {2}. Communication errors may occur. ...
  15. The value for the IMAP4 '{4}' registry entry is set lower than {8} bytes on server {2}. Communication errors may occur. Current ...
  16. The value for the IMAP4 '{4}' registry entry on server {2} has changed. In some scenarios, this can increase performance. ...
  17. The value for the maximum Extensible Storage Engine (ESE) cache on server {2} has changed. Current maximum cache size is ...
  18. The value for the maximum number of databases per storage group on server {2} has changed. This configuration is not supported. ...
  19. The value for the maximum number of storage groups on server {2} has changed. This configuration is not supported. This server ...
  20. The value for the Microsoft Exchange Information Store '{4}' registry entry is less than {8} on server {2}. This configuration ...
  21. The value for the Microsoft Exchange Information Store '{4}' registry entry on server {2} has changed. Current value: {9}. ...
  22. The value for the Microsoft Exchange Information Store '{4}' registry entry on server {2} has changed. Default value {8}. ...
  23. The value for the Microsoft Exchange Information Store '{4}' registry entry on server {2} is less than {8}. This configuration ...
  24. The value for the Microsoft Exchange Information Store RPC '{4}' registry entry on server {2} is not set to {8}. This will ...
  25. The value for the Microsoft Exchange Site Replication Service '{4}' registry entry on server {2} has changed. Port value: ...
  26. The value for the Microsoft Exchange Site Replication Service '{4}' registry entry on server {2} is less than {8}. This configuration ...
  27. The value for the Microsoft Exchange System Attendant '{4} registry entry is less than {8} on server {2}. This configuration ...
  28. The value for the Microsoft Exchange System Attendant '{4}' registry entry is less than {8} on server {2}. This configuration ...
  29. The value for the Microsoft Exchange System Attendant '{4}' registry entry on server {2} has changed. Default value {8}. ...
  30. The value for the Microsoft Exchange System Attendant '{4}' registry entry on server {2} has changed. Default value: {8}. ...
  31. The value for the Microsoft Exchange System Attendant '{4}' registry entry on server {2} is less than {8}. This configuration ...
  32. The value for the minimum Extensible Storage Engine (ESE) cache on server {2} has changed. This configuration is not generally ...
  33. The value for the POP3 '{4}' registry entry is set higher than {8} bytes on server {2}. Communication errors may occur. Current ...
  34. The value for the POP3 '{4}' registry entry is set lower than {8} bytes on server {2}. Communication errors may occur. Current ...
  35. The value for the POP3 '{4}' registry entry on server {2} has changed. In some scenarios, this can increase performance. ...
  36. The value of the Windows Management Instrumentation (WMI) setting '{4}' on cluster node {2} differs from that on node {1} ...
  37. The value specified for the age at which old message tracking log files will be removed is not valid. The default value %1 ...
  38. The value {0} is an invalid NumberFormat specifier. It should be of the form " ]" where prefix is a string containing only ...
  39. The value {0} is an invalid NumberFormat specifier. It should be of the form " ]" where prefix is a string containing only ...
  40. The values that you specified for the Bindings and RemoteIPRanges parameters conflict with the settings on Receive connector ...
  41. The version data on the Exchange server '{0}' is invalid. Setup will treat the server as a pre-Exchange 2007 server. Message: ...
  42. The version of '{5}' installed on cluster node {2} may cause failures if mount points are created. If you intend to use mount ...
  43. The version of '{5}' installed on cluster node {2} may cause volume mount point failures. Review Microsoft Knowledge Base ...
  44. The version of '{5}' installed on server {2} can cause kernel memory allocation errors. An update is available from the vendor. ...
  45. The version of '{5}' installed on server {2} can cause working sets to be improperly trimmed when Terminal Services is used. ...
  46. The version of '{5}' installed on server {2} is incompatible with {0} and can cause disk errors. If you are experiencing ...
  47. The version of '{5}' installed on server {2} may cause connectivity issues in some networking configurations. Download and ...
  48. The version of '{5}' installed on server {2} may cause connectivity issues in some networking configurations. If you are ...
  49. The version of '{5}' installed on server {2} may cause mail flow issues with X.400 connectors resident on this server. If ...
  50. The version of '{5}' installed on this computer is not from Windows Server 2003 Service Pack 1 or later. Apply Service Pack ...
  51. The version of the Active Directory Connector (ADC) on server {2} is not compatible with the current Active Directory forest ...
  52. The version of the free/busy security descriptor obtained from mailbox {0} is not supported. The expected version is {1}; ...
  53. The version of the Microsoft Exchange Information Store service is incompatible with the version of the Exchange System Manager. ...
  54. The version of the Recipient Update Service on Exchange server {2} is not compatible with the current Active Directory forest ...
  55. The version of {5} installed on server {2} may cause high CPU utilization for the Inetinfo process when message tracking ...
  56. The version of {5} installed on server {2} may cause messages to public folders to queue before the hierarchy can replicate. ...
  57. The version of {5} installed on server {2} may cause the Inetinfo process to use 100% of CPU when Active Directory queries ...
  58. The version on the target node is not compatible with the version on the source node. The source ({0}) version is {1}, and ...
  59. The version store for this instance (%4) cannot grow because it is receiving Out-Of-Memory errors from the OS. It is likely ...
  60. The version store for this instance (%4) has reached its maximum size of %5Mb. It is likely that a long-running transaction ...
  61. The virtual directory "{0}" is not configured correctly. This server has the Mailbox server role installed, so HTTP compression ...
  62. The virtual memory necessary to run your Exchange server is fragmented in such a way that normal operation may begin to fail. ...
  63. The virtual memory necessary to run your Exchange server is fragmented in such a way that performance may be affected. It ...
  64. The VoIP platform encountered an exception %1 during the call with ID "%2". This exception occurred at the Microsoft Exchange ...
  65. The VoIPSecurity parameter cannot be changed on the dial plan. This dial plan is associated with one or more UM servers. ...
  66. The VoIPSecurity parameter on the dial plan cannot be set to SIPSecured. The address field "{0}" on IP gateway "{1}" is not ...
  67. The WebReady Document Viewing cache has reached its size limit. It may take several minutes for the temporary files to be ...
  68. The WebReady Document Viewing manager did not initialize. It will try again to initialize. If this problem continues, restart ...
  69. The WebReady Document Viewing manager failed to access the temporary folder. The value of the temporary folder is set by ...
  70. The WebReady Document Viewing service cannot convert the document because Microsoft Exchange is busy. Please try converting ...
  71. The WebReady Document Viewing service cannot convert the document you tried to view because it does not have the proper file ...
  72. The WebReady Document Viewing service has been disabled by the administrator for your organization. For more information, ...
  73. The WebReady Document Viewing service is not working correctly because an error occurred. Please contact technical support ...
  74. The WebReady Document Viewing worker application cannot be found. To correct this problem, reinstall Outlook Web Access. ...
  75. The WebReady Document Viewing worker application is not registered. To correct this problem, reinstall Outlook Web Access. ...
日本語
Japanese English
English (United States)