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