UI Translation

Exchange Server 2010

  1. The database engine stopped an instance. Use the error code listed in the associated event, ESE ID 104, to determine the ...
  2. The database engine successfully converted the database format. This is an Information event. No user action is required. ...
  3. The database engine updated %1 index entries in database %2 because of a change in the NLS version. This message is informational ...
  4. The database engine updated %1 index entries in database %2 because of a change in the NLS version. This message is informational ...
  5. The database engine updated %4 index entries in database %5 because of a change in the NLS version. This message is informational ...
  6. The database engine updated %4 index entries in database %5 because of a change in the NLS version. This message is informational ...
  7. The database engine was unable to updated index entries in database %5 because the database is read-only. For more information, ...
  8. The database engine was unable to updated index entries in database %5 because the database is read-only. For more information, ...
  9. The database file %2 for %1 is missing. Re-seeding of this database is now required. Use the Update-MailboxDatabaseCopy cmdlet ...
  10. The database file %2 for %1 is missing. Re-seeding of this database is now required. Use the Update-MailboxDatabaseCopy cmdlet ...
  11. The database file for mailbox database '{3}' on Exchange server {2} appears to be stored on a network share. This isn't recommended ...
  12. The database file for public folder database '{3}' on Exchange server {2} appears to be stored on a network share. This isn't ...
  13. The database files for mailbox store '{3}' on server {2} appear to be located on the same disk volume as the transaction ...
  14. The database files in this database were replaced with older versions by an offline restore. To use the restored files, open ...
  15. The database latency troubleshooter detected high RPC Average latencies for database %1 but was unable to determine a cause. ...
  16. The database latency troubleshooter detected that disk latencies are abnormal for database %1. You need to replace the disk. ...
  17. The database latency troubleshooter detected that DSAccess latencies are abnormal for database %1. This may be due to an ...
  18. The database latency troubleshooter detected that the current latency of %1 ms for database %2 is within the threshold of ...
  19. The database latency troubleshooter identified a problem with user %1 on database %2 due to unusual activity in the mailbox. ...
  20. The database latency troubleshooter quarantined user %1 on database %2 due to unusual activity in the mailbox. If the problem ...
  21. The database management scope {0} won't be applied to the management role assignment for the management role {1} because ...
  22. The database object '{0}' in Active Directory has been corrupted and is in an inconsistent state, with no copies configured ...
  23. The database object '{0}' in Active Directory has been corrupted and is in an inconsistent state. Unable to find any server ...
  24. The database page read from file "%1" at offset %2 (database page %5) for %3 bytes failed verification. Bit %4 was corrupted ...
  25. The database page read from file "%1" at offset %2 (database page %5) for %3 bytes failed verification. Bit %4 was corrupted ...
  26. The database page read from file "%1" at offset %2 (database page %7) for %3 bytes failed verification due to a page checksum ...
  27. The database page read from file "%1" at offset %2 (database page %7) for %3 bytes failed verification due to a page checksum ...
  28. The database page read from file "%1" at offset %2 for %3 bytes failed verification due to a page number mismatch. The expected ...
  29. The database page read from file "%1" at offset %2 for %3 bytes failed verification due to a page number mismatch. The expected ...
  30. The database page read from file '%1' at offset %2 (database page %3) failed verification due to a page checksum mismatch. ...
  31. The database page read from file '%1' at offset %2 (database page %3) failed verification due to a page checksum mismatch. ...
  32. The database page read from the file "%1" at offset %2 (database page %5) for %3 bytes failed verification because it contains ...
  33. The database page read from the file "%1" at offset %2 (database page %5) for %3 bytes failed verification because it contains ...
  34. The database page read from the file "%1" at offset %2 (database page %6) for %3 bytes failed verification. Bit %5 was corrupted ...
  35. The database page read from the file "%1" at offset %2 (database page %6) for %3 bytes failed verification. Bit %5 was corrupted ...
  36. The database page read from the file "%4" at offset %5 (database page %10) for %6 bytes failed verification due to a page ...
  37. The database page read from the file "%4" at offset %5 (database page %10) for %6 bytes failed verification due to a page ...
  38. The database page read from the file "%4" at offset %5 (database page %8) for %6 bytes failed verification because it contains ...
  39. The database page read from the file "%4" at offset %5 (database page %8) for %6 bytes failed verification because it contains ...
  40. The database page read from the file "%4" at offset %5 (database page %8) for %6 bytes failed verification due to a lost ...
  41. The database page read from the file "%4" at offset %5 (database page %8) for %6 bytes failed verification due to a lost ...
  42. The database page read from the file "%4" at offset %5 (database page %8) for %6 bytes failed verification due to a lost ...
  43. The database page read from the file "%4" at offset %5 (database page %8) for %6 bytes failed verification due to a lost ...
  44. The database page read from the file "%4" at offset %5 (database page %8) for %6 bytes failed verification. Bit %7 was corrupted ...
  45. The database page read from the file "%4" at offset %5 (database page %8) for %6 bytes failed verification. Bit %7 was corrupted ...
  46. The database page read from the file "%4" at offset %5 (database page %9) for %6 bytes failed verification. Bit %8 was corrupted ...
  47. The database page read from the file "%4" at offset %5 (database page %9) for %6 bytes failed verification. Bit %8 was corrupted ...
  48. The database page read from the file "%4" at offset %5 for %6 bytes failed verification due to a page number mismatch. The ...
  49. The database page read from the file "%4" at offset %5 for %6 bytes failed verification due to a page number mismatch. The ...
  50. The database page read from the file '%4' at offset %5 (database page %6) failed verification due to a page checksum mismatch. ...
  51. The database page read from the file '%4' at offset %5 (database page %6) failed verification due to a page checksum mismatch. ...
  52. The database signature does not match the log signature for database %4. For more information, click http://www.microsoft.com/contentredirect.asp. ...
  53. The database signature does not match the log signature for database %4. For more information, click http://www.microsoft.com/contentredirect.asp. ...
  54. The database space troubleshooter detected a low space condition on volume %1 for database %2. Provisioning for this database ...
  55. The database space troubleshooter finished on volume %1 for database %2. No problems were detected. EDB drive free space: ...
  56. The database space troubleshooter finished on volume %1 for database %2. The database is over the expected threshold and ...
  57. The database space troubleshooter finished on volume %1 for database %2. The database is over the expected threshold, but ...
  58. The database space troubleshooter finished on volume %1 for database %2. The database is over the expected threshold. Users ...
  59. The database space troubleshooter has detected a critically low space condition on volume %1 for database %2. Provisioning ...
  60. The database that you specified, {0}, appears more than once, Provide a unique database name in the WritableDatabaseObject ...
  61. The database to be accessed from the server is not mounted or is not available. See the inner exception for more information. ...
  62. The database was already active on server '{0}'. The Third Party Replication vendor must specify a different server name ...
  63. The database was not in the dismounted state. The Third Party Replication vendor must use either the dismount-database task ...
  64. The database was not mounted because configuration settings from the registry could not be copied. Please verify that the ...
  65. The database was not mounted because it has experienced data loss as a result of a switchover or failover, and the attempt ...
  66. The database wasn't mounted because it has experienced data loss as a result of the move or a failover that occurred. Check ...
  67. The databases have not been restored to this machine. You cannot restore an incremental backup until a full backup has been ...
  68. The databases have not been restored to this machine. You cannot restore an incremental backup until a full backup has been ...
  69. The decision from the moderator cannot be retrieved because the moderator made the decision before the mailbox server {0} ...
  70. The dedicated heartbeat connection on cluster {2} is not set to priority {8}. Use the 'Cluster Administrator' program to ...
  71. The default HTTP binding for site '{1}' is missing, or has been configured with a different host name. This can cause the ...
  72. The default installation path is invalid. If you are attempting an upgrade from a previous version of Exchange, ensure that ...
  73. The default mode is install. Specifying the /mode parameter is optional for initial installation of a language pack update. ...
  74. The default mode is install. Specifying the /mode parameter is optional for initial installation of a language pack update. ...
  75. The default role assignment policy can't be removed unless it is the last one. You need to specify another role assignment ...
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)