The log copier couldn't initialize because it tried to start copying from log generation {1} but source server '{0}' only has logs starting at generation {2}. The source server may be truncating logs in which case the operation can be retried again later.
The location of the page file, SMTP server, TEMP or TMP directory may contribute to a performance bottleneck. If there is ...
The location that you specified for the transaction log files is invalid. Verify that the directory exists and that there ...
The log copier could not verify log divergence at generation '{0}'. The active server was '{1}'. An exception was encountered: ...
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 ...