Couldn't mount database "{0}" because at least one committed transaction log file appears to be missing. The log files may be recoverable from one of the database's continuous replication copies. If none of its copies has a valid copy of the log file, consider removing them with the Remove-MailboxDatabaseCopy cmdlet and then attempting the mount again. Error: {1}
Couldn't load the certificate from the local machine store based on the subject name specified by ClientCertificateSubjectName ...
Couldn't log on to the specified mail server because the server indicated the login for this account is temporarily restricted. ...
Couldn't look up the system mailbox or the server hosting the system mailbox for mdb '%1'. Last successful ping was '%2' ...
Couldn't look up the system mailbox or the server hosting the system mailbox for mdb '%1'. Last successful ping was '%2' ...
Couldn't mount database "{0}" because at least one committed transaction log file appears to be missing. The log files may ...
Couldn't move public folder database '{0}' into itself. Please select a target database that is different from the source ...
Couldn't preserve the mailbox signature for mailbox '{0}'. Outlook clients will need to restart to access the moved mailbox. ...
Couldn't remove the role assignment policy with the identity "{0}". There is at least one role assignment for this assignment ...
Couldn't resolve the user or group "{0}." If the user or group is a foreign forest principal, you must have either a two-way ...