The database copy was successfully suspended, but the ResumeBlocked state could not be set. Resuming this copy could be dangerous as there may be corruption on the passive copy.
The database copy was automatically suspended by the Automatic Reseed Manager after being in a 'Failed' state for a duration ...
The database copy was successfully suspended, but the InPlaceReseedBlocked state could not be set. In-place reseed (by the ...
The database copy was successfully suspended, but the ReseedBlocked state could not be set. Reseeding this copy could be ...
The database copy was successfully suspended, but the ResumeBlocked state could not be set because it is currently Seeding. ...
The database copy was successfully suspended, but the ResumeBlocked state could not be set. Resuming this copy could be dangerous ...
The database copy was successfully suspended, but the SuspendComment could not be set. Please retry the command to set SuspendComment ...
The database could not allocate memory. Please close some applications to make sure you have enough memory for Exchange Server. ...
The database could not be opened because a log file is missing or corrupted. The Microsoft Exchange Transport service is ...
The database could not be opened because it does not belong with the current set of log files. The Microsoft Exchange Transport ...