| Previous | Next |
| COMADMIN_E_CAT_PARTITION_IN_USE | COMADMIN_E_CAT_IMPORTED_COMPONENTS_NOT_ALLOWED |
COMADMIN_E_FILE_PARTITION_DUPLICATE_FILES
COMADMIN_E_FILE_PARTITION_DUPLICATE_FILES is the failure HRESULT 0x8011045A (signed decimal -2146368422, unsigned decimal 2148598874). Its severity bit is 1, facility is 17 (FACILITY_ITF), and the facility-specific code field is 0x045A.
COM+ partition administration: exact meaning of COMADMIN_E_FILE_PARTITION_DUPLICATE_FILES
Partition export cannot proceed because components in the partition contain duplicate filenames. ExportPartition assembles files into one package namespace and detects name collisions.
AllStat records this condition as “The partition cannot be exported, because one or more components in the partition have the same file name”.
Where COMADMIN_E_FILE_PARTITION_DUPLICATE_FILES occurs
Partitions are logical containers with explicit IDs, names, user defaults, application contents, and platform enablement; operations must use the intended partition rather than assume a global namespace. In the specific case of COMADMIN_E_FILE_PARTITION_DUPLICATE_FILES, list every component file with full path, hash, owning application, and colliding basename.
Evidence to collect before repair
- For
COMADMIN_E_FILE_PARTITION_DUPLICATE_FILES, preserve full path, basename, hash, and owning CLSID for every collision; it anchors the failure to the real administration object. - Evidence for
COMADMIN_E_FILE_PARTITION_DUPLICATE_FILESshould include application and component membership within the partition, captured before a repair changes state. - Collect export destination and package layout when diagnosing
COMADMIN_E_FILE_PARTITION_DUPLICATE_FILES; without it the symbolic HRESULT is underdetermined. - The
COMADMIN_E_FILE_PARTITION_DUPLICATE_FILESinvestigation needs whether duplicate names represent identical or different bytes so the exact failing boundary remains reconstructable.
Diagnostic sequence for COMADMIN_E_FILE_PARTITION_DUPLICATE_FILES
- For
COMADMIN_E_FILE_PARTITION_DUPLICATE_FILES, produce a collision report by basename. - At the
COMADMIN_E_FILE_PARTITION_DUPLICATE_FILESboundary, determine whether binaries can be consolidated safely. - The next
COMADMIN_E_FILE_PARTITION_DUPLICATE_FILESdiagnostic action is to rename and rebuild distinct components when their bytes differ. - To isolate
COMADMIN_E_FILE_PARTITION_DUPLICATE_FILES, remove verified stale component entries through supported uninstall. - For
COMADMIN_E_FILE_PARTITION_DUPLICATE_FILES, re-export and validate that each package filename is unique.
Retry and recovery
Rename/repackage binaries with unique deployable filenames or separate applications before re-exporting.
Difference from nearby COMADMIN results
COMADMIN_E_CANTCOPYFILE is an I/O failure; this result is a deterministic package-name collision discovered before copying completes.
Practical administration scenario
Two applications in one partition use different DLLs both named Common.dll, preventing unambiguous export.
Official Microsoft references for COMADMIN_E_FILE_PARTITION_DUPLICATE_FILES
- Microsoft: COMADMIN error codes
- Microsoft: what COM+ partitions are
- Microsoft: managing local COM+ partitions
- Microsoft: ICOMAdminCatalog2
- Microsoft: the COM+ catalog
Looking for a different code? Search another status or error code.