UI Translation

Exchange Server 2016

  1. The database engine log disk is full. Deleting logfiles to recover disk space may make your database unstartable if the database ...
  2. The database engine log disk is full. Deleting logfiles to recover disk space may make your database unstartable if the database ...
  3. The database engine lost one bad data record. It is highly recommended that an application-level integrity check of the database ...
  4. The database engine lost one bad data record. It is highly recommended that an application-level integrity check of the database ...
  5. The database engine lost one or more bad columns of data in one record. It is highly recommended that an application-level ...
  6. The database engine lost one or more bad columns of data in one record. It is highly recommended that an application-level ...
  7. The database engine lost one page of bad data. It is highly recommended that an application-level integrity check of the ...
  8. The database engine lost one page of bad data. It is highly recommended that an application-level integrity check of the ...
  9. The database engine lost one table called %1. It is highly recommended that an application-level integrity check of the database ...
  10. The database engine lost one table called %4. It is highly recommended that an application-level integrity check of the database ...
  11. The database engine repaired corruption on page %1 of database '%2'. Although the corruption has been repaired, the source ...
  12. The database engine repaired corruption on page %4 of database '%5'. Although the corruption has been repaired, the source ...
  13. The database engine repaired corruption on pages %1 - %2 of database '%3'. Although the corruption has been repaired, the ...
  14. The database engine repaired corruption on pages %4 - %5 of database '%6'. Although the corruption has been repaired, the ...
  15. The database engine updated %1 index entries in database %2 because of a change in the NLS version. This message is informational ...
  16. The database engine updated %4 index entries in database %5 because of a change in the NLS version. This message is informational ...
  17. The database engine was unable to updated index entries in database %5 because the database is read-only. For more information, ...
  18. The database file %2 for %1 is missing. Re-seeding of this database is now required. Use the Update-MailboxDatabaseCopy cmdlet ...
  19. The database file for mailbox database '{3}' on Exchange server {2} appears to be stored on a network share. This isn't recommended ...
  20. The database file for public folder database '{3}' on Exchange server {2} appears to be stored on a network share. This isn't ...
  21. The database files are not on the same volume as the log files. Automatic Reseed is only supported for databases where logs ...
  22. The database files for mailbox store '{3}' on server {2} appear to be located on the same disk volume as the transaction ...
  23. The database latency troubleshooter detected high RPC Average latencies for database %1 and found a unique mailbox to be ...
  24. The database latency troubleshooter detected high RPC Average latencies for database %1 but found insufficient mailboxes ...
  25. The database latency troubleshooter detected high RPC Average latencies for database %1 but was unable to determine a cause. ...
  26. The database latency troubleshooter detected that disk latencies are abnormal for database %1. You need to replace the disk. ...
  27. The database latency troubleshooter detected that the current latency for database %1 appears high, but the current load ...
  28. The database latency troubleshooter detected that the current latency of %1 ms for database %2 is within the threshold of ...
  29. The database latency troubleshooter detected that the DSAccess Active Call Count is abnormal for database %1. This may be ...
  30. The database latency troubleshooter detected that the DSAccess Average Latency is abnormal for database %1. This may be due ...
  31. The database latency troubleshooter identified a problem with user %1 on database %2 due to unusual activity in the mailbox. ...
  32. The database latency troubleshooter quarantined user %1 on database %2 due to unusual activity in the mailbox. If the problem ...
  33. The database management scope {0} won't be applied to the role assignment for the management role {1} because this role has ...
  34. The database object '{0}' in Active Directory has been corrupted and is in an inconsistent state, with no copies configured ...
  35. The database object '{0}' in Active Directory has been corrupted and is in an inconsistent state. Unable to find any server ...
  36. The database page read from the file "%1" at offset %2 (database page %5) for %3 bytes failed verification because it contains ...
  37. The database page read from the file "%1" at offset %2 (database page %5) for %3 bytes failed verification due to a lost ...
  38. The database page read from the file "%1" at offset %2 (database page %5) for %3 bytes failed verification due to a persisted ...
  39. The database page read from the file "%1" at offset %2 (database page %5) for %3 bytes failed verification. Bit %4 was corrupted ...
  40. The database page read from the file "%1" at offset %2 (database page %6) for %3 bytes failed verification. Bit %5 was corrupted ...
  41. The database page read from the file "%1" at offset %2 (database page %7) for %3 bytes failed verification due to a page ...
  42. The database page read from the file "%1" at offset %2 for %3 bytes failed verification due to a page number mismatch. The ...
  43. The database page read from the file "%4" at offset %5 (database page %10) for %6 bytes failed verification due to a page ...
  44. The database page read from the file "%4" at offset %5 (database page %8) for %6 bytes failed verification because it contains ...
  45. The database page read from the file "%4" at offset %5 (database page %8) for %6 bytes failed verification due to a lost ...
  46. The database page read from the file "%4" at offset %5 (database page %8) for %6 bytes failed verification due to a persisted ...
  47. The database page read from the file "%4" at offset %5 (database page %8) for %6 bytes failed verification. Bit %7 was corrupted ...
  48. The database page read from the file "%4" at offset %5 (database page %9) for %6 bytes failed verification. Bit %8 was corrupted ...
  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 '%1' at offset %2 (database page %3) 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 redundancy alert condition is being suppressed for database '{0}'. Reason: All remote RPCs to retrieve the copy ...
  53. The database redundancy alert condition is being suppressed for database '{0}'. Reason: At least one copy status entry of ...
  54. The database signature does not match the log signature for database %4. For more information, click http://www.microsoft.com/contentredirect.asp. ...
  55. The database space troubleshooter detected a low space condition on volume %1 for database %2. Provisioning for this database ...
  56. The database space troubleshooter finished on volume %1 for database %2. No problems were detected. EDB free space (drive ...
  57. The database space troubleshooter finished on volume %1 for database %2. The database is over the expected threshold and ...
  58. The database space troubleshooter finished on volume %1 for database %2. The database is over the expected threshold, but ...
  59. The database space troubleshooter finished on volume %1 for database %2. The database is over the expected threshold. Users ...
  60. The database space troubleshooter has detected a critically low space condition on volume %1 for database %2. Provisioning ...
  61. The database that you specified, {0}, appears more than once, Provide a unique database name in the WritableDatabaseObject ...
  62. The database to be accessed from the server is not mounted or is not available. See the inner exception for more information. ...
  63. The database was already active on server '{0}'. The Third Party Replication vendor must specify a different server name ...
  64. The database was not in the dismounted state. The Third Party Replication vendor must use either the dismount-database task ...
  65. The database watermark(s) for database {1} are below the age threshold of {2} minute(s) on server {0}. The last event counter: ...
  66. The databases have not been restored to this machine. You cannot restore an incremental backupuntil a full backup has been ...
  67. The DC passed to -DomainController parameter is non-authoritative DC for tenant relocation data. Only the authoritative DC ...
  68. The decision from the moderator cannot be retrieved because the moderator made the decision before the mailbox server {0} ...
  69. The dedicated heartbeat connection on cluster {2} is not set to priority {8}. Use the 'Cluster Administrator' program to ...
  70. The default HTTP binding for site '{1}' is missing, or has been configured with a different host name. This can cause the ...
  71. The default installation path is invalid. If you are attempting an upgrade from a previous version of Exchange, ensure that ...
  72. The default public folder hierarchy for the organization is already provisioned and cannot be changed. In order to update ...
  73. The default role assignment policy, {0}, can't be removed. You need to set another policy as the default to be able to remove ...
  74. The default scope restriction for the "{0}" role assignment can't be calculated because the current user has delegating role ...
  75. The default sharing policy can't be removed. First choose another policy to be the default sharing policy, and then remove ...
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)