UI Translation

Exchange Server 2007

  1. The Unified Messaging server could not obtain a DNS record for the following hosts: "%1". Verify that your UM IP gateway ...
  2. The Unified Messaging server detected corrupt user configuration data for user "%1". This data contains information such ...
  3. The Unified Messaging server encountered an error in the speech grammar filter list at line %1, character %2. The error is ...
  4. The Unified Messaging server encountered an error on the call with ID "%1" while trying to read from Active Directory. The ...
  5. The Unified Messaging server encountered an error when parsing a user interface configuration file. It found an unexpected ...
  6. The Unified Messaging server encountered an error when parsing a user interface configuration file. The prompt with ID "{0}" ...
  7. The Unified Messaging server encountered an error while parsing a user interface definition file. The action "{0}" has not ...
  8. The Unified Messaging server encountered an error while parsing the description of a speech user interface. The speech menu ...
  9. The Unified Messaging server encountered an error while processing the speech grammar filter list that is used for Automatic ...
  10. The Unified Messaging server failed to exchange the required certificates to enable Transport Layer Security (TLS) with an ...
  11. The Unified Messaging server failed to exchange the required certificates with an IP gateway to enable Transport Layer Security ...
  12. The Unified Messaging server failed to receive an incoming call for user "%1" during the call with ID "%2" because a Hub ...
  13. The Unified Messaging server failed to submit the message to the Hub Transport server using header file "%1". The header ...
  14. The Unified Messaging server has created a grammar file named "%1". The grammar file was then compiled into a file named ...
  15. The Unified Messaging server has encountered a data error while trying to read information is stored in Active Directory ...
  16. The Unified Messaging server has encountered an error while parsing a user interface configuration file. An expression was ...
  17. The Unified Messaging server has encountered an error while parsing a user interface configuration file. An unexpected token ...
  18. The Unified Messaging server has encountered an error while parsing a user interface configuration file. The activity ID ...
  19. The Unified Messaging server has encountered an error while parsing the user interface configuration file "{1}". A reference ...
  20. The Unified Messaging server has received a SIP header that is not valid from an incoming call with ID "%1". Header details ...
  21. The Unified Messaging server has received an inbound call that has an invalid extension "%1" for UM dial plan "%2". The call ...
  22. The Unified Messaging server has received both fax and audio media from "%1" for "%2" at number "%3". The fax contains %4 ...
  23. The Unified Messaging server has successfully generated a speech grammar file that includes the names of distribution lists. ...
  24. The Unified Messaging server has successfully received a fax from "%1" for "%2" at extension number "%3". The fax contains ...
  25. The Unified Messaging server is initiating an outgoing call. The calling party is "%1", the party being called is "%2", and ...
  26. The Unified Messaging server is transferring a call from "%1", with diversion "%2", to extension number "%3",. The call ID ...
  27. The Unified Messaging server received a Play on Phone request from "%1". The calling number "%2" is dialing "%3" using the ...
  28. The Unified Messaging server received a Play on Phone request from user "%1", but the telephone number "%2" cannot be dialed ...
  29. The Unified Messaging server received an incomplete extension for the call with ID "%1". The number of digits received was ...
  30. The Unified Messaging server role cannot be upgraded. Remove the current role using Control Panel, then install the newer ...
  31. The Unified Messaging Server Role provides connectivity between a corporate telephony system and Exchange server. Clients ...
  32. The Unified Messaging server successfully generated a speech grammar file that contains entries from the default Global Address ...
  33. The Unified Messaging server updated the custom prompt cache for UM auto attendant "%1". The name of the file that was updated ...
  34. The Unified Messaging server updated the custom prompt cache for UM dial plan "%1". The name of the file that was updated ...
  35. The Unified Messaging server was unable to create a message for the fax call with ID "%1". The following invalid media details ...
  36. The Unified Messaging server was unable to issue a Session Initiation Protocol (SIP) Option request to the IP/VoIP gateway ...
  37. The Unified Messaging server was unable to resolve the caller ID "%1" to a user in Active Directory or personal contact before ...
  38. The Unified Messaging server was unable to submit messages to a Hub Transport server because there is no Hub Transport server ...
  39. The Unified Messaging Service was unable to read the UM Worker Process retire time from the configuration data. The UM Worker ...
  40. The Unified Messaging Worker Process (UMWorkerProcess.exe) encountered an unhandled exception "%1" during an incoming call ...
  41. The Unified Messaging Worker Process has finished updating the speech grammar files for UM dial plans that are associated ...
  42. The Unified Messaging Worker Process has started grammar generation for Automatic Speech Recognition. The log file is "%1". ...
  43. The Unified Messaging Worker Process is attempting to recover from an exception "%1" that was encountered during a call with ...
  44. The Unified Messaging Worker Process was terminated because its startup time exceeded the configured maximum, %1 seconds. ...
  45. The Unified Messaging-enabled user "%1" is not configured to receive fax messages. The fax message that originated from phone ...
  46. The update was skipped. The site addressing portion of e-mail address '%1' for display name '%2' (mailbox name '%3') does ...
  47. The user "%1" modified a custom prompt for UM dial plan "%2". The custom prompt file name is "%3" and the custom prompt publishing ...
  48. The user "{0}" with the e-mail address "{1}" was not added to the speech grammar because the speech recognition service has ...
  49. The user '{0}' was issuing {1} MAPI operations per second, which is higher than expected. If a user is issuing more than ...
  50. The user '{3}' is causing high RPC load by MAPI operation "{4}". When a single MAPI operation type is responsible for a large ...
  51. The user account "{0}" to be linked has already been the master account of another linked mailbox "{1}", please specify a ...
  52. The user account for '%1' does not exist in the directory or is not enabled for Exchange e-mail. This mailbox has been removed ...
  53. The user account for '%1' does not exist in the directory or is not enabled for Exchange e-mail. This mailbox will be removed ...
  54. The user account for '%1' does not exist in the directory or is not enabled for Exchange mail. This mailbox will be removed ...
  55. The user account which was used to submit this request does not have the right to send mail on behalf of the specified sending ...
  56. The user directory attributes, such as homeMDB or msExchHomeServerName, may be missing or corrupted. Troubleshooting: Verify ...
  57. The user profile with display name %1 was not found in the Active Directory, but the time delay before it will be created ...
  58. The user version for routing group '{3}' appears to be changing very rapidly on server {2} ({9} version change(s) detected ...
  59. The user version for routing group '{3}' has been changed on server {2} while the tool was running. Latest user version number: ...
  60. The user version for routing group '{3}' may be changing rapidly on server {2} ({9} version change(s) detected over {8} seconds). ...
  61. The user, {0}, already has some of the permissions ({2}) specified to be added on the public folder {1}. You cannot add a ...
  62. The user, {0}, does not have some of the permissions ({2}) specified to be removed on the public folder {1}. You cannot remove ...
  63. The user-specified domain controller {0} cannot be used because setup has determined that it must use the schema master domain ...
  64. The value for '{4}' is set to {9} bytes on server {2}. This can cause errors for users of Outlook Web Access. A minimum value ...
  65. The value for '{4}' on server {2} is less than {8} and may cause performance degradation for the scanning result thread. ...
  66. The value for '{4}' on server {2} is too low and may cause performance degradation. The current registry value is {9}. Based ...
  67. The value for configuration setting '{4}' for database '{3}' on server {2} has changed (default value: {7}). This configuration ...
  68. The value for configuration setting '{4}' for database '{3}' on server {2} has changed (default: {7}). This configuration ...
  69. The value for configuration setting '{4}' for database '{3}' on server {2} has changed. This configuration is only recommended ...
  70. The value for configuration setting '{4}' for database '{3}' on server {2} has changed. This configuration is recommended ...
  71. The value for configuration setting '{4}' for object '{3}' on server {2} has changed. Default value: {8}. Current value: ...
  72. The value for configuration setting '{4}' for public store '{3}' on server {2} has changed. Default: {8} seconds. Current ...
  73. The value for configuration setting '{4}' for SMTP instance '{3}' on server {2} has changed. Default value: {8}. Current ...
  74. The value for configuration setting '{4}' on server {2} has changed. This can cause mail flow problems. Current value: {9}. ...
  75. The value for setting '{4}' has changed for display specifier '{3}'. This will modify the default behavior for generating ...
日本語
Japanese English
English (United States)