| Previous | Next |
| IMAPI_E_FILE_SYSTEM_FEATURE_NOT_SUPPORTED | IMAPI_E_IMPORT_SEEK_FAILURE |
IMAPI_E_IMPORT_TYPE_COLLISION_FILE_EXISTS_AS_DIRECTORY
IMAPI_E_IMPORT_TYPE_COLLISION_FILE_EXISTS_AS_DIRECTORY is a hierarchy type collision during filesystem import. The source session contains a file at a path where the current in-memory IFileSystemImage hierarchy already has a directory. IMAPI retains existing in-memory items during ordinary name collisions, but a file-versus-directory type conflict cannot be merged as one object.
Compare the pre-import tree with the source path
- Log the full conflicting path and the filesystem being imported.
- Inspect content added to
RootbeforeImportFileSystem; the destination directory may have been created by application code. - Resolve the naming/type conflict before retrying instead of deleting unrelated imported content.
This code is the mirror image of IMAPI_E_IMPORT_TYPE_COLLISION_DIRECTORY_EXISTS_AS_FILE. The direction matters because it identifies which type already exists in memory. Import order is therefore diagnostically significant: if the application prepopulates the image before importing a previous session, it should validate path types against the disc layout or intentionally choose different destination names.
ImportFileSystem · IFileSystemImage · Creating a multisession disc
Looking for a different code? Search another status or error code.