The database was already active on server '{0}'. The Third Party Replication vendor must specify a different server name when changing the active server.
The database space troubleshooter finished on volume %1 for database %2. The database is over the expected threshold. Users ...
The database space troubleshooter has detected a critically low space condition on volume %1 for database %2. Provisioning ...
The database that you specified, {0}, appears more than once, Provide a unique database name in the WritableDatabaseObject ...
The database to be accessed from the server is not mounted or is not available. See the inner exception for more information. ...
The database was already active on server '{0}'. The Third Party Replication vendor must specify a different server name ...
The database was not in the dismounted state. The Third Party Replication vendor must use either the dismount-database task ...
The database was not mounted because configuration settings from the registry could not be copied. Please verify that the ...
The database was not mounted because it has experienced data loss as a result of a switchover or failover, and the attempt ...
The database wasn't mounted because it has experienced data loss as a result of the move or a failover that occurred. Check ...