What does HRESULT 0x80AA0A0A (E_IMAPI_RAW_IMAGE_TRACK_INDEX_TOO_CLOSE_TO_OTHER_INDEX) mean?

 
Previous Next
E_IMAPI_RAW_IMAGE_TRACK_INDEX_OFFSET_ZERO_CANNOT_BE_CLEARED ERROR_DBG_CREATE_PROCESS_FAILURE_LOCKDOWN

E_IMAPI_RAW_IMAGE_TRACK_INDEX_TOO_CLOSE_TO_OTHER_INDEX

E_IMAPI_RAW_IMAGE_TRACK_INDEX_TOO_CLOSE_TO_OTHER_INDEX is a spacing failure in the raw CD track index layout. Microsoft defines a minimum size of ten sectors between indexes. A proposed offset can therefore be unique and still be rejected because it is too near an existing boundary.

Validate sorted index spacing before applying the list

  • Enumerate current indexes and sort the requested offsets numerically for diagnostics.
  • Calculate the distance to the nearest previous and next index in sectors.
  • Keep offset zero/index 1 in the calculation; it is a fixed boundary that cannot be cleared.

Do not collapse this error into the “already exists” success status. An existing offset is idempotent; a different offset with a gap below ten sectors is invalid. When cue points come from time values, inspect the time-to-sector conversion and rounding rules, because two distinct timestamps can map to offsets that are closer than the raw image constraint permits. Changing recorder speed or media does not alter this image-layout rule.

Track indexes · Track information · IMAPI return values


Looking for a different code? Search another status or error code.