What does HRESULT 0xC0AAB10B (IMAPI_E_NOT_IN_FILE_SYSTEM) mean?

 
Previous Next
IMAPI_E_DIR_NOT_EMPTY IMAPI_E_INVALID_PATH

IMAPI_E_NOT_IN_FILE_SYSTEM

IMAPI_E_NOT_IN_FILE_SYSTEM identifies object membership rather than a host-filesystem lookup failure. IMAPI2FS lets applications create IFsiFileItem or IFsiDirectoryItem objects and later add them to the image hierarchy. Some operations are valid only after the item belongs to an IFileSystemImage tree.

Track item creation and attachment as separate lifecycle steps

  • Record where the item object was created and which directory was supposed to receive it.
  • Verify that Add completed successfully before invoking operations that require image membership.
  • Check that the item belongs to the same image object; do not mix detached items from different builders.

The corresponding source path may exist on disk and still be irrelevant. The HRESULT says the IMAPI item is not part of the image model. This matters for named-stream and directory operations that depend on parent/image context. Fix the object lifecycle by adding the item at the correct location, or operate on the item returned from the hierarchy after insertion rather than retaining a detached placeholder.

Add · CreateFileItem · CreateDirectoryItem


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