At '%8' the Automatic Reseed Manager attempted to promote active database '%1' copy to requiring a seed to a spare volume. ...

Exchange Server 2016

At '%8' the Automatic Reseed Manager attempted to promote active database '%1' copy to requiring a seed to a spare volume. For more details about the in-place reseed failure, consult the Microsoft-Exchange-HighAvailability/Seeding event log on the server for related events. Service recovery was attempted by failover to another copy. Failover was unsuccessful in restoring the service because: %7.

Reason for failure escalation: %13

At '%8' the active copy of database '%1' on this server could not initialize a critical replication component. The failover ... At '%8' the active copy of database '%1' on this server could not initialize a critical replication component. The failover ... At '%8' the active copy of database '%1' on this server failed due to a bitlocker-locked volume. A successful failover restored ... At '%8' the active copy of database '%1' on this server failed due to a bitlocker-locked volume. The attempt to failover ... At '%8' the Automatic Reseed Manager attempted to promote active database '%1' copy to requiring a seed to a spare volume. ... At '%8' the Automatic Reseed Manager attempted to promote passive database '%1' copy to requiring a seed to a spare volume. ... At '%8' the Automatic Reseed Manager promoted active database '%1' copy to requiring a seed to a spare volume. For more details ... At '%8' the Automatic Reseed Manager promoted passive database '%1' copy to requiring a seed to a spare volume. For more ... At '%8' the copy of '%1' on this server experienced an error that requires it be reseeded. For more detail about this failure, ...