Exchange Server 2010

  1. Database %4: Page %5 failed verification due to a flush-order dependency mismatch. This page should have flushed before page ...
  2. Database %4: Page %5 failed verification due to a flush-order dependency mismatch. This page should have flushed before page ...
  3. Database %4: Page %5 failed verification due to a timestamp mismatch. The expected timestamp was %6 but the actual timestamp ...
  4. Database %4: Page %5 failed verification due to a timestamp mismatch. The expected timestamp was %6 but the actual timestamp ...
  5. Database %6: Index %4 of table %5 is corrupted (%7). For more information, click http://www.microsoft.com/contentredirect.asp. ...
  6. Database %6: Index %4 of table %5 is corrupted (%7). For more information, click http://www.microsoft.com/contentredirect.asp. ...
  7. Database '%1' has a schema version '%2' where the required version is '%3'. Move the database folder '%4' and the database ...
  8. Database '%1' has a schema version '%2' where the required version is '%3'. Move the database folder '%4' and the database ...
  9. Database '%1': A message was successfully delivered, but an error (%2) was encountered attempting to add an entry into the ...
  10. Database '%1': A message was successfully delivered, but an error (%2) was encountered attempting to add an entry into the ...
  11. Database '%1': A message with an expiration time was successfully delivered, but an error (%2) was encountered attempting ...
  12. Database '%1': A message with an expiration time was successfully delivered, but an error (%2) was encountered attempting ...
  13. Database '%1': Available B-Tree IDs (ObjectIDs) have almost been exhausted. Freed/unused B-Tree IDs may be reclaimed by performing ...
  14. Database '%1': Available B-Tree IDs (ObjectIDs) have almost been exhausted. Freed/unused B-Tree IDs may be reclaimed by performing ...
  15. Database '%1': Background clean-up skipped pages. The database may benefit from widening the online maintenance window during ...
  16. Database '%1': Background clean-up skipped pages. The database may benefit from widening the online maintenance window during ...
  17. Database '%1': Out of B-Tree IDs (ObjectIDs). Freed/unused B-Tree IDs may be reclaimed by performing an offline defragmentation ...
  18. Database '%1': Out of B-Tree IDs (ObjectIDs). Freed/unused B-Tree IDs may be reclaimed by performing an offline defragmentation ...
  19. Database '%1': The database engine has built an in-memory cache of %2 space tree nodes on a B-Tree (ObjectId: %3, PgnoRoot: ...
  20. Database '%1': The database engine has built an in-memory cache of %2 space tree nodes on a B-Tree (ObjectId: %3, PgnoRoot: ...
  21. Database '%1': The database engine lost unused pages %2-%3 while attempting space reclamation on a B-Tree (ObjectId %4). ...
  22. Database '%1': The database engine lost unused pages %2-%3 while attempting space reclamation on a B-Tree (ObjectId %4). ...
  23. Database '%1': The primary index '%2' of table '%3' may be corrupt. If there is no later event showing the index being rebuilt, ...
  24. Database '%1': The primary index '%2' of table '%3' may be corrupt. If there is no later event showing the index being rebuilt, ...
  25. Database '%1': The secondary index '%2' of table '%3' may be corrupt. If there is no later event showing the index being ...
  26. Database '%1': The secondary index '%2' of table '%3' may be corrupt. If there is no later event showing the index being ...
  27. Database '%1': The secondary index '%2' of table '%3' will be rebuilt as a precautionary measure after the Windows version ...
  28. Database '%1': The secondary index '%2' of table '%3' will be rebuilt as a precautionary measure after the Windows version ...
  29. Database '%1': While attempting to move to the next or previous node in a B-Tree, the database engine skipped over %4 non-visible ...
  30. Database '%1': While attempting to move to the next or previous node in a B-Tree, the database engine skipped over %4 non-visible ...
  31. Database '%1': While attempting to move to the next or previous node in a B-Tree, the database engine skipped over %4 non-visible ...
  32. Database '%1': While attempting to move to the next or previous node in a B-Tree, the database engine skipped over %4 non-visible ...
  33. Database '%4': Available B-Tree IDs (ObjectIDs) have almost been completely consumed. Freed/unused B-Tree IDs may be reclaimed ...
  34. Database '%4': Available B-Tree IDs (ObjectIDs) have almost been completely consumed. Freed/unused B-Tree IDs may be reclaimed ...
  35. Database '%4': Background clean-up skipped pages. The database may benefit from widening the online maintenance window during ...
  36. Database '%4': Background clean-up skipped pages. The database may benefit from widening the online maintenance window during ...
  37. Database '%4': Out of B-Tree IDs (ObjectIDs). Freed/unused B-Tree IDs may be reclaimed by performing an offline defragmentation ...
  38. Database '%4': Out of B-Tree IDs (ObjectIDs). Freed/unused B-Tree IDs may be reclaimed by performing an offline defragmentation ...
  39. Database '%4': The database engine has built an in-memory cache of %5 space tree nodes on a B-Tree (ObjectId: %6, PgnoRoot: ...
  40. Database '%4': The database engine has built an in-memory cache of %5 space tree nodes on a B-Tree (ObjectId: %6, PgnoRoot: ...
  41. Database '%4': The database engine lost unused pages %5-%6 while attempting space reclamation on a B-Tree (ObjectId %7). ...
  42. Database '%4': The database engine lost unused pages %5-%6 while attempting space reclamation on a B-Tree (ObjectId %7). ...
  43. Database '%4': The primary index '%5' of table '%6' may be corrupt. If there is no later event showing the index being rebuilt, ...
  44. Database '%4': The primary index '%5' of table '%6' may be corrupt. If there is no later event showing the index being rebuilt, ...
  45. Database '%4': The secondary index '%5' of table '%6' may be corrupt. If there is no later event showing the index being ...
  46. Database '%4': The secondary index '%5' of table '%6' may be corrupt. If there is no later event showing the index being ...
  47. Database '%4': The secondary index '%5' of table '%6' will be rebuilt as a precautionary measure after the Windows version ...
  48. Database '%4': The secondary index '%5' of table '%6' will be rebuilt as a precautionary measure after the Windows version ...
  49. Database '%4': While attempting to move to the next or previous node in a B-Tree, the database engine skipped over %7 non-visible ...
  50. Database '%4': While attempting to move to the next or previous node in a B-Tree, the database engine skipped over %7 non-visible ...
  51. Database '%4': While attempting to move to the next or previous node in a B-Tree, the database engine skipped over %7 non-visible ...
  52. Database '%4': While attempting to move to the next or previous node in a B-Tree, the database engine skipped over %7 non-visible ...
  53. Database '{0}' can't be mounted on server '{1}' due to a previous error: {2} Verify that the underlying cause of the error ...
  54. Database '{0}' is expected to be in a database availability group but the value for its MasterServerOrAvailabilityGroup property ...
  55. Database '{0}' isn't on an Exchange 2007 or later server. Please use Exchange System Manager in Exchange 2003 to manage servers ...
  56. Database '{0}' on Remote Continuous Replication source machine '{1}' has failed to mount after a failover or a handoff probably ...
  57. Database '{0}' on server '{1}' cannot be mounted due to a previous error: {2} If you have addressed the underlying problem, ...
  58. Database '{0}' was not mounted because either no possible host servers were in an activation-ready state, or there were no ...
  59. Database '{0}' was not moved because it has apparently already been moved away from original active server '{1}' to '{2}'. ...
  60. Database '{2}' CANNOT be moved to server '{3}' because it would cause the AD sites to become MORE unbalanced. AllowedMaxSiteDelta={4}, ...
  61. Database '{2}' CANNOT be moved to server '{3}' because it would cause the AD sites to become unbalanced. AllowedMaxSiteDelta={4}, ...
  62. Database '{3}' on server {2} accommodates {9} mailboxes. This database has not had a full online backup for {8} days. Last ...
  63. Database Availability Group '%2' member server '%1' is not completely started. Run Start-DatabaseAvailabilityGroup '%2' -MailboxServer ...
  64. Database Availability Group '%2' member server '%1' is not completely started. Run Start-DatabaseAvailabilityGroup '%2' -MailboxServer ...
  65. Database availability group '{0}' doesn't have a configured witness server and directory, even though its quorum model requires ...
  66. Database availability group '{0}' is empty. Operations on its networks aren't possible until at least one Mailbox server ...
  67. Database availability group '{0}' witness '{1}' isn't a valid path. Please use the Set-DatabaseAvailabilityGroup cmdlet to ...
  68. Database availability group '{0}' witness is in a failed state. The database availability group requires the witness server ...
  69. Database availability group server {0} cannot be removed from database availability group {1} since it is currently set for ...
  70. Database availability group {0} cannot be set into datacenter activation mode, since it contains fewer than two mailbox servers. ...
  71. Database Cache % Hit is the percentage of database file page requests that were fulfilled by the database cache without causing ...
  72. Database Cache Misses per second is the rate at which database file page requests were fulfilled by the database cache by ...
  73. Database Cache Misses per second is the rate at which database file page requests were fulfilled by the database cache by ...
  74. Database Cache Size (MB) is the amount of system memory (in megabytes) used by the database cache manager to hold commonly ...
  75. Database Cache Size (MB) is the amount of system memory (in megabytes) used by the database cache manager to hold commonly ...