What does HRESULT 0xC0AAB133 (IMAPI_E_INCOMPATIBLE_PREVIOUS_SESSION) mean?

 
Previous Next
IMAPI_E_DATA_TOO_BIG IMAPI_E_STASHFILE_OPEN_FAILURE

IMAPI_E_INCOMPATIBLE_PREVIOUS_SESSION

IMAPI_E_INCOMPATIBLE_PREVIOUS_SESSION belongs to the IMAPI2FS multisession workflow. Microsoft documents it for previous-session import and for changing FileSystemsToCreate after a session has been imported. The imported file-system layout and the layout IMAPI would generate for the new session must remain compatible.

Compare imported and requested file-system layouts

  • Record which file system was imported from the previous session and the current FileSystemsToCreate value.
  • Capture whether output-format settings were changed before or after ImportFileSystem or ImportSpecificFileSystem.
  • Recreate the image with compatible settings rather than retrying import against the same conflicting configuration.

This is not a read error from the disc. IMAPI may successfully recognize and import the previous session, then reject a layout change that cannot be extended safely. Multisession code should establish the intended output file-system set before import and preserve it unless the API explicitly allows a compatible transition. The exact imported file system and requested result formats are the key diagnostic data.

ImportFileSystem · ImportSpecificFileSystem · FileSystemsToCreate


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