| Previous | Next |
| IMAPI_E_RESTRICTED_NAME_VIOLATION | IMAPI_E_NO_UNIQUE_NAME |
IMAPI_E_DUP_NAME
IMAPI_E_DUP_NAME reports a namespace collision in the IMAPI2FS image hierarchy. A directory item contains an enumerable set of child files and directories, and add operations cannot always create another child with the same destination name. The conflict is inside the image being built, which can differ from the layout of the host source tree.
Identify the existing destination item before retrying
- Resolve the name with
get_Itemin the destination directory and record whether it is a file or directory. - Trace whether the item came from an earlier
Add,AddFile,AddTree, or imported session. - Choose an explicit overwrite/merge strategy in application code rather than generating random suffixes after failure.
Tree import has documented collision behavior, while individual add operations expose duplicate-name errors. That difference matters when code mixes bulk and incremental insertion. Build a single policy for destination-name collisions and apply it before invoking the API. If uniqueness must be preserved across multiple output file systems, also inspect the file-system-specific name because different source names can map to an identical representable name.
IFsiDirectoryItem · Add · get_Item
Looking for a different code? Search another status or error code.