| Previous | Next |
| IMAPI_E_ITEM_NOT_FOUND | IMAPI_E_DIR_NOT_FOUND |
IMAPI_E_FILE_NOT_FOUND
IMAPI_E_FILE_NOT_FOUND identifies a failed file-specific lookup inside IMAPI2FS. It should be distinguished from IMAPI_E_ITEM_NOT_FOUND, which is generic, and IMAPI_E_NOT_FILE, where an item exists but has the wrong type. The distinction helps narrow whether the path is missing or occupied by a directory.
Check path existence and type as two separate questions
- Resolve the parent directory and enumerate the child name expected by the caller.
- Record whether the image content came from direct adds, a bulk tree operation, or previous-session import.
- Preserve case and the exact image path used by the failing operation.
Do not automatically recreate the file from the host source without checking why the image entry disappeared. A prior Remove, rollback, import collision, or failed tree addition may be the real cause. If the application stores IFsiItem references across hierarchy changes, verify that its cached path assumptions still match the current image. The source tree and image hierarchy are related but are not the same namespace.
IFsiDirectoryItem · get_Item · AddFile
Looking for a different code? Search another status or error code.