Database schema version check monitor for one or more database(s) failed to take appropriate provisioning action. Please investigate further and take appropriate recovery actions based on the schema version and any error below. Diagnostic Command: {0} Command to get all unhealthy Database Schema Version Check Monitors: {1} Last Reported Database: {{Probe.StateAttribute1}} Database Schema Version: {{Probe.StateAttribute2}} Database Schema Version Threshold: {{Probe.StateAttribute3}} Recommended Action: {{Probe.StateAttribute4}} Error: {{Probe.Error}}
Database recovery stopped abruptly while redoing logfile %1 (%2,%3). The logs after this point may not be recognizable and ...
Database recovery stopped abruptly while redoing logfile %4 (%5,%6). The logs after this point may not be recognizable and ...
Database recovery/restore failed with unexpected error %4. For more information, click http://www.microsoft.com/contentredirect.asp. ...
Database RPC Latency Root Cause Responder successfully executed last time and found no issues, turning monitor green so responder ...
Database schema version check monitor for one or more database(s) failed to take appropriate provisioning action. Please ...
Database size monitor for database '{0}' may have failed to take appropriate provisioning action (setting IsExcludedFromProvisioning) ...
Database size monitor for database '{0}' may have failed to take appropriate provisioning action (setting IsExcludedFromProvisioning). ...
Database: %1 Mailbox Server: %2 A failover occurred and the database was forced to mount after waiting %5 seconds. The known ...
Database: %1 Mailbox server: %2 A Move-ActiveMailboxDatabase operation was requested with a MountDialOverride of %3. Database ...