What does HRESULT 0xC0AAB113 (IMAPI_E_NO_UNIQUE_NAME) mean?

IMAPI_E_NO_UNIQUE_NAME

IMAPI_E_NO_UNIQUE_NAME is more specific than a direct duplicate-name collision. IMAPI2FS can adapt names to the selected output file systems, but a requested item may map to a name that cannot be made unique within the constraints of a particular file-system representation. This is especially relevant when one image targets multiple file systems with different naming rules.

Compare source names with their file-system-specific representations

• Record FileSystemsToCreate and the original destination name.
• Inspect sibling names that may normalize, truncate, or otherwise map to the same representable name.
• Do not solve the issue only for Joliet or UDF if the same image also includes ISO 9660.

The error can arise even when the original Unicode strings are distinct. A robust image builder performs deterministic naming before insertion and checks collisions under every selected output format. Random retry loops can still collide and make the resulting disc layout unpredictable. When preserving original names is mandatory, choose an output file-system set whose naming capabilities match the data instead of forcing incompatible compatibility targets.

FileSystemsToCreate · IFsiDirectoryItem::Add · FsiFileSystems

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