Database size monitor for database '{0}' may have failed to take appropriate provisioning action (setting IsExcludedFromProvisioning). Please investigate further and take appropriate recovery actions based on the values of database size and any error below. Diagnostic Command: {1} Command to get all unhealthy Database Size Monitors: {2} Database Size: {{Monitor.StateAttribute3}} Maximum allowed Database Size: {{Monitor.StateAttribute4}} Disk Capacity: {{Monitor.StateAttribute2}} IsExcludedFromProvisioning: {{Probe.StateAttribute2}} Error: {{Monitor.Exception}}
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 ...
Database: %1 Mailbox Server: %2 Attempts to copy the log files from the source server are taking longer than usual because ...
Database: %1 Mailbox server: %2 Attempts to copy the log files from the source server weren't successful because the database ...