| Previous | Next |
| MSG_CI_MASTER_MERGE_ABORTED | MSG_CI_CORRUPT_INDEX_COMPONENT |
MSG_CI_MASTER_MERGE_RESTARTED
MSG_CI_MASTER_MERGE_RESTARTED is a recovery/lifecycle event, not a new merge request. It should be correlated with the earlier abort for the same catalog and with any checkpoint or nested error information captured at the pause.
Measure whether the restarted merge makes forward progress
- Link the restart to the prior abort by catalog and time rather than counting both as independent merge jobs.
- Record how often the same merge restarts and whether free space or service state changes between attempts.
- Watch for a subsequent cannot-restart event or catalog consistency error if the restart never reaches a stable completion state.
Indexing Service documentation explains that merge checkpoints reduce the amount of new master-index work that must be redone after a pause. A restart can therefore be expected after a recoverable interruption. The concerning pattern is repeated restart without progress, especially with the same embedded error or low-disk condition. Diagnostic logs should retain the sequence start → abort → restart rather than flattening all merge events into generic indexing failures.
Master merge checkpoints · Merging indexes · Windows Search indexing
Looking for a different code? Search another status or error code.