Exchange Server 2010

  1. The log file %4 is missing (error %5) and cannot be used. If this log file is required for recovery, a good copy of the log ...
  2. The log file %5 (generation %6) has damaged or invalid log (%7), ESE has removed the portion of log corrupted since these ...
  3. The log file %5 (generation %6) has damaged or invalid log (%7), ESE has removed the portion of log corrupted since these ...
  4. The log file sequence in "%1" has been halted due to a fatal error. No further updates are possible for the databases that ...
  5. The log file sequence in "%1" has been halted due to a fatal error. No further updates are possible for the databases that ...
  6. The log files %1 and %2 are not in a valid sequence. Log file replay cannot succeed if there are gaps in the sequence of ...
  7. The log files %1 and %2 are not in a valid sequence. Log file replay cannot succeed if there are gaps in the sequence of ...
  8. The log range read from file "%1" at offset %2 for %3 bytes failed verification due to a corrupted checksum log record. The ...
  9. The log range read from file "%1" at offset %2 for %3 bytes failed verification due to a corrupted checksum log record. The ...
  10. The log range read from file "%1" at offset %2 for %3 bytes failed verification due to a range checksum mismatch. The expected ...
  11. The log range read from file "%1" at offset %2 for %3 bytes failed verification due to a range checksum mismatch. The expected ...
  12. The log range read from the file "%4" at offset %5 for %6 bytes failed verification due to a corrupted checksum log record. ...
  13. The log range read from the file "%4" at offset %5 for %6 bytes failed verification due to a corrupted checksum log record. ...
  14. The log range read from the file "%4" at offset %5 for %6 bytes failed verification due to a range checksum mismatch. The ...
  15. The log range read from the file "%4" at offset %5 for %6 bytes failed verification due to a range checksum mismatch. The ...
  16. The log signature of the existing log file %1 doesn't match the log files from the backup set. Log file replay cannot succeed ...
  17. The log signature of the existing log file %1 doesn't match the log files from the backup set. Log file replay cannot succeed ...
  18. The log signature of the existing logfile %4 doesn't match the logfiles from the backup set. Logfile replay cannot succeed ...
  19. The log signature of the existing logfile %4 doesn't match the logfiles from the backup set. Logfile replay cannot succeed ...
  20. The log version stamp of log file %1 doesn't match the database engine version stamp. The log files may be the wrong version ...
  21. The log version stamp of log file %1 doesn't match the database engine version stamp. The log files may be the wrong version ...
  22. The log version stamp of logfile %4 does not match the database engine version stamp. The logfiles may be the wrong version ...
  23. The log version stamp of logfile %4 does not match the database engine version stamp. The logfiles may be the wrong version ...
  24. The LogFile parameter is used to specify the Exchange Setup log to open. If this parameter is not specified, the script will ...
  25. The logfile sequence in "%4" has been halted due to a fatal error. No further updates are possible for the databases that ...
  26. The logfile sequence in "%4" has been halted due to a fatal error. No further updates are possible for the databases that ...
  27. The logfiles %4 and %5 are not in a valid sequence. Logfile replay cannot succeed if there are gaps in the sequence of available ...
  28. The logfiles %4 and %5 are not in a valid sequence. Logfile replay cannot succeed if there are gaps in the sequence of available ...
  29. The long-term IDs of the folders with synchronized per-user read/unread information for the given public folder database ...
  30. The machine {0} is a member of cluster {1}, but it does not appear to be running (state = {2}). Try the -configurationonly ...
  31. The mail protocol was unable to handle one or more requests because they were unrecognized or invalid. Please notify your ...
  32. The mail protocol was unable to handle one or more requests because they were unrecognized or invalid. Please notify your ...
  33. The mailbox '%1' Recoverable Items size has exceeded the warning quota limit. Items were deleted from Recoverable Items folders ...
  34. The mailbox '%1' Recoverable Items size has exceeded the warning quota limit. Items were deleted from Recoverable Items folders ...
  35. The mailbox '%s' couldn't be moved because rules in the source mailbox's Inbox folder exceed 32KB. Please use parameter -IgnoreRuleLimitErrors ...
  36. The mailbox audit log search has timed out after '{0}' seconds. Please narrow the date range or reduce the number of mailboxes ...
  37. The mailbox database copy '{0}\{1}' has failed to update from server {2}. Do you want to clean up that update request now? ...
  38. The mailbox database copy '{0}\{1}' has recently been updated from server {2}. Do you want to clean up that update request ...
  39. The mailbox database copy '{0}\{1}' is currently being updated from server {2}, and another seed cannot be requested for ...
  40. The mailbox database that you specified already exists as a recovery mailbox database. You can't create a new mailbox database ...
  41. The mailbox database that you specified is already associated with a recovery mailbox database. Specified mailbox database: ...
  42. The mailbox for %1 (GUID %2) has exceeded the maximum Recoverable Items Quota. Items cannot be deleted from this mailbox. ...
  43. The mailbox for %1 (GUID %2) has exceeded the maximum Recoverable Items Quota. Items cannot be deleted from this mailbox. ...
  44. The mailbox for %1 (GUID %2) has exceeded the Recoverable Items Warning Quota. Please remove items from Recoverable Items ...
  45. The mailbox for %1 (GUID %2) has exceeded the Recoverable Items Warning Quota. Please remove items from Recoverable Items ...
  46. The mailbox for %1 has exceeded the maximum mailbox size. This mailbox cannot send or receive messages. Incoming messages ...
  47. The mailbox for %1 has exceeded the maximum mailbox size. This mailbox cannot send or receive messages. Incoming messages ...
  48. The mailbox for user %1 has been quarantined. Access to this mailbox will be restricted to administrative logons for the ...
  49. The mailbox for user %1 has been quarantined. Access to this mailbox will be restricted to administrative logons for the ...
  50. The mailbox GUID of an external system mailbox ('%1') does not match the information in the Active Directory for the mailbox. ...
  51. The mailbox GUID of an external system mailbox ('%1') does not match the information in the Active Directory for the mailbox. ...
  52. The mailbox has been moved but an unexpected error occurred while trying to apply policies or clean the source mailbox. Error: ...
  53. The mailbox of the authenticating user and the mailbox of the resource being accessed must have the same Mailbox server version. ...
  54. The mailbox of user {0} that is located on a server that is running version {1} can't be opened on a server that is running ...
  55. The Mailbox parameter is not supported for mailboxes with versions older than {0}. The version of the mailbox {1} is {2}. ...
  56. The mailbox plan "{0}" wasn't the only default mailbox plan in the current organization defined on the domain controller ...
  57. The mailbox policy '{0}' has users associated with it. If you remove the mailbox policy, none of these users will have an ...
  58. The mailbox policy '{0}' may have users associated with it. If you remove it, no mailbox policy will be associated with these ...
  59. The mailbox quota was exceeded while contacts were being saved to the mailbox. Please free up some space and try again. The ...
  60. The Mailbox Replication Proxy Service can't process this request because it has reached the maximum number of active MRS ...
  61. The Mailbox Replication service removed an orphaned move request. MDB GUID: %1 Mailbox GUID: %2 Mailbox identity: %3 Validation ...
  62. The Mailbox Replication service removed an orphaned move request. MDB GUID: %1 Mailbox GUID: %2 Mailbox identity: %3 Validation ...
  63. The Mailbox Replication service was unable to clean up the destination mailbox after the move was canceled. The error was ...
  64. The Mailbox Replication service was unable to clean up the destination mailbox after the move was canceled. The error was ...
  65. The Mailbox Replication service was unable to clean up the source mailbox after the move. The error was ignored. Mailbox ...
  66. The Mailbox Replication service was unable to clean up the source mailbox after the move. The error was ignored. Mailbox ...
  67. The Mailbox Replication service was unable to determine the list of mailbox databases hosted in the local Active Directory ...
  68. The Mailbox Replication service was unable to determine the list of mailbox databases hosted in the local Active Directory ...
  69. The Mailbox Replication service was unable to determine the set of active mailbox databases on a mailbox server. Mailbox ...
  70. The Mailbox Replication service was unable to determine the set of active mailbox databases on a mailbox server. Mailbox ...
  71. The Mailbox Replication service was unable to reset the source mailbox after the move was canceled. The error was ignored. ...
  72. The Mailbox Replication service was unable to reset the source mailbox after the move was canceled. The error was ignored. ...
  73. The Mailbox Replication service was unable to update Active Directory information for the source Mailbox at the end of the ...
  74. The Mailbox Replication service was unable to update Active Directory information for the source Mailbox at the end of the ...
  75. The mailbox search name {0} is not a unique search name. You must provide a unique mailbox search name. Wildcards are not ...