| Previous | Next |
| MSG_CI_MASTER_MERGE_CANT_START | QUTIL_E_INVALID_CODEPAGE |
MSG_CI_MASTER_MERGE_CANT_RESTART
MSG_CI_MASTER_MERGE_CANT_RESTART belongs to the recovery path after a merge interruption. Unlike a cannot-start event, this code implies that a previous merge existed and the service attempted to resume it.
Reconstruct the earlier abort and restart chain
- Find the preceding abort event for the same catalog and retain its nested error.
- Capture the new restart error and compare it with catalog consistency, low-disk, and component-corruption events.
- Do not assume a checkpoint is usable merely because one was written; catalog or storage state can change before the restart attempt.
Master-merge checkpoint documentation explains that checkpoints limit the amount of work redone after a pause. A restart failure therefore deserves a chronology that includes the initial merge, pause, any service or disk event, and the attempted resume. If the catalog later resets, preserve this sequence first. It can distinguish a transient resource problem from persistent catalog state that prevents recovery of interrupted merge work.
Master merge checkpoints · Merging indexes · Full-text catalog components
Looking for a different code? Search another status or error code.