Database '{0}' on server '{1}' cannot be mounted due to a previous error: {2} If you have addressed the underlying problem, or if you have decided to attempt to mount the database despite this error, the mount operation may be attempted by using the '-Force' parameter of the Mount-Database cmdlet.
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}, ...