Exchange Server 2016
- The log copier couldn't continue processing because a gap in the log sequence has been detected. Source server '{0}' doesn't ...
- The log copier couldn't initialize because it tried to start copying from log generation {1} but source server '{0}' only ...
- The log copier determined log divergence at generation '{0}' is present between the local copy and the active on server '{1}'. ...
- The log copier for database '%1' detected that the end of log is changing from generation %2 to %3. This passive copy will ...
- The log copier for database '%1' has been disconnected for '%2'. This has exceeded the configured limit and the copy is being ...
- The log copier for database '%1' received an error from the source server '%2': %3 The copier will automatically retry after ...
- The log copier for database '%1' was unable to cleanly transition out of continuous replication-block mode. The transition ...
- The log copier was unable to communicate with server '%2'. The copy of database '%1' is in a disconnected state. The communication ...
- The log copier was unable to continue processing for database '%1' because an error occured on the target server: %2 The ...
- The log copier was unable to continue processing for database '%1' because the source server '%2' returned an error: %3 The ...
- The log copier was unable to continue processing for database '%1' because the source server '%2' returned an error: %3 The ...
- The log file %1 is damaged, invalid, or inaccessible (error %2) and cannot be used. If the log file cannot be found, the ...
- The log file %1 is damaged, invalid, or inaccessible (error %2) and cannot be used. If this log file is required for recovery, ...
- The log file %1 is missing (error %2) and cannot be used. If this log file is required for recovery, a good copy of the log ...
- The log file %2 (generation %3) has damaged or invalid log (%4), ESE has removed the portion of log corrupted since these ...
- The log file %4 is damaged, invalid, or inaccessible (error %5) and cannot be used. If the log file cannot be found, the ...
- The log file %4 is damaged, invalid, or inaccessible (error %5) and cannot be used. If this log file is required for recovery, ...
- The log file %4 is missing (error %5) and cannot be used. If this log file is required for recovery, a good copy of the log ...
- The log file %5 (generation %6) has damaged or invalid log (%7), ESE has removed the portion of log corrupted since these ...
- The log range read from the file "%1" at offset %2 for %3 bytes failed verification due to a corrupted checksum log record. ...
- The log range read from the file "%1" at offset %2 for %3 bytes failed verification due to a range checksum mismatch. The ...
- The log range read from the file "%4" at offset %5 for %6 bytes failed verification due to a corrupted checksum log record. ...
- The log range read from the file "%4" at offset %5 for %6 bytes failed verification due to a range checksum mismatch. The ...
- The log signature of the existing logfile %1 doesn't match the logfiles from the backup set. Logfile replay cannot succeed ...
- The log signature of the existing logfile %4 doesn't match the logfiles from the backup set. Logfile replay cannot succeed ...
- The log version stamp of logfile %1 does not match the database engine version stamp. The logfiles may be the wrong version ...
- The log version stamp of logfile %4 does not match the database engine version stamp. The logfiles may be the wrong version ...
- The logfile sequence in "%1" has been halted due to a fatal error. No further updates are possible for the databases that ...
- The logfile sequence in "%4" has been halted due to a fatal error. No further updates are possible for the databases that ...
- The logfiles %1 and %2 are not in a valid sequence. Logfile replay cannot succeed if there are gaps in the sequence of available ...
- The logfiles %4 and %5 are not in a valid sequence. Logfile replay cannot succeed if there are gaps in the sequence of available ...
- The LogFolderPath was expected to be '{1}' but was actually '{0}'. Automatic Reseed is only supported for databases that ...
- The logical and physical disk performance counters on server {0} are disabled. You can monitor the performance of your disks ...
- The LogOnly and DeleteContent switches cannot be used together. Before using the DeleteContent switch to delete messages, ...
- The Lync Server A/V Edge service wasn't able to open a port or allocate resources while attempting to establish a session. ...
- The machine {0} is a member of cluster {1}, but it does not appear to be running (state = {2}). Try the -configurationonly ...
- The mailbox "{0}" is about to be permanently deleted. All mailbox content such as emails, contacts, etc. will be irrecoverably ...
- The mailbox "{0}" is the primary public folder mailbox for the users. To remove this mailbox, first remove all other public ...
- The mailbox "{0}" is the primary public folder mailbox. To disable this mailbox, first disable all other public folder mailboxes. ...
- The mailbox %1 of tenant %2 is approaching the mailbox quota. Current Mailbox size (bytes) : '%3', Mailbox quota warning ...
- The mailbox '%1' Recoverable Items size has exceeded the warning quota limit. Items were deleted from Recoverable Items folders ...
- The mailbox '%1' Recoverable Items size has exceeded the warning quota limit. Oldest items were deleted from Recoverable ...
- The mailbox '{0}' can't be moved to mailbox database '{1}' because the provisioning attributes on the database don't satisfy ...
- The mailbox assistants process '{0}' has crashed at least {1} times in last {2}. Watson Message: {Probe.StateAttribute1} ...
- The mailbox assistants process '{0}' has crashed at least {1} times in last {2}. Watson Message: {Probe.StateAttribute1} ...
- The mailbox audit log search has timed out after '{0}' seconds. Please narrow the date range or reduce the number of mailboxes ...
- The Mailbox database "{0}" isn't on a server running Exchange 2013 or a later version. If you want to create or enable a ...
- The mailbox database '{1}' on server {0} hasn't been backed up in last {2} hours, LastFullBackup time:{3}, LastIncrementalBackup ...
- The mailbox database '{1}' on server {0} is configured to mount on startup of the Exchange Information Store service. If ...
- The mailbox database '{1}' on server {0} isn't configured to mount on startup of the Exchange Information Store service. ...
- The mailbox database '{1}' on server {0} was backed up in last {2} hours, LastFullBackup time:{3}, LastIncrementalBackup ...
- The mailbox database '{1}' on server {0} wasn't backed up in the last {2} hours, LastFullBackup time:{3}, LastIncrementalBackup ...
- The mailbox database '{3}' on server {2} is {9} GB in size. Standard editions of Microsoft Exchange Server 2003 Service Pack ...
- The mailbox database '{3}' on server {2} is {9} GB in size. Standard editions of Microsoft Exchange Server are limited to ...
- The mailbox database copy '{0}\{1}' has failed to update from server {2}. Do you want to clean up that update request now? ...
- The mailbox database copy '{0}\{1}' has recently been updated from server {2}. Seeding cannot be requested for the same database ...
- The mailbox database copy '{0}\{1}' is currently being updated from server {2}, and another seed cannot be requested for ...
- The mailbox database that you specified already exists as a recovery mailbox database. You can't create a new mailbox database ...
- The mailbox database that you specified is already associated with a recovery mailbox database. Specified mailbox database: ...
- The mailbox has been moved but an unexpected error occurred while trying to apply policies or clean the source mailbox. Error: ...
- The mailbox is not hosted in the current service location. Mailbox service location is {0}. User lookup can't be completed. ...
- The mailbox of the authenticating user and the mailbox of the resource being accessed must have the same Mailbox server version. ...
- The mailbox or SharePoint site may not exist. If this is incorrect, please contact Microsoft support. Otherwise, please remove ...
- The Mailbox parameter is not supported for mailboxes with versions older than {0}. The version of the mailbox {1} is {2}. ...
- The mailbox plan "{0}" wasn't the only default mailbox plan in the current organization defined on the domain controller ...
- The mailbox policy '{0}' has users associated with it. If you remove the mailbox policy, none of these users will have an ...
- The mailbox quota was exceeded while contacts were being saved to the mailbox. Please free up some space and try again. The ...
- The Mailbox Replication Proxy Service can't process this request because it has reached the maximum number of active MRS ...
- The Mailbox Replication Service could not connect to the remote server because the remote server encountered an internal ...
- The Mailbox Replication service removed an orphaned move request. MDB GUID: %1 Mailbox GUID: %2 Mailbox identity: %3 Validation ...
- The Mailbox Replication service was unable to clean up the destination mailbox after the move was canceled. The error was ...
- The Mailbox Replication service was unable to clean up the source mailbox after the move. The error was ignored. Mailbox ...
- The Mailbox Replication Service was unable to connect to the remote server using the credentials provided. Please check the ...
- The Mailbox Replication service was unable to determine the set of active mailbox databases on a mailbox server. Mailbox ...
- The Mailbox Replication service was unable to reset the source mailbox after the move was canceled. The error was ignored. ...