What does HRESULT 0x80110819 (COMADMIN_E_PARTITION_MSI_ONLY) mean?

 
Previous Next
COMADMIN_E_PARTITION_ACCESSDENIED COMADMIN_E_LEGACYCOMPS_NOT_ALLOWED_IN_1_0_FORMAT

COMADMIN_E_PARTITION_MSI_ONLY

COMADMIN_E_PARTITION_MSI_ONLY is the failure HRESULT 0x80110819 (signed decimal -2146367463, unsigned decimal 2148599833). Its severity bit is 1, facility is 17 (FACILITY_ITF), and the facility-specific code field is 0x0819.

Deployment format required for COM+ partitions: exact meaning of COMADMIN_E_PARTITION_MSI_ONLY

The installation source is not an Application File in MSI format, but the target is a COM+ partition that accepts only that package form. Direct component registration and ordinary non-partition application files do not satisfy this deployment contract.

AllStat records the Windows SDK description as “Only Application Files (*.MSI files) can be installed into partitions.”

Typical cause branches

  • InstallApplication was given a non-MSI export or a raw component DLL for a partition destination.
  • automation attempts ImportComponents where a partition-aware application package is required.
  • an exported proxy or legacy application file is mistaken for an installable partition package.
  • the path has an MSI extension but the content is not a valid COM+ application package.

Where COMADMIN_E_PARTITION_MSI_ONLY occurs

COM+ validates the package type and destination partition before committing application objects. The restriction supports a coherent, repeatable installation of application and component metadata within the partition.

Evidence to collect before changing the catalog

  • source path, file type, hash, signature, package database metadata, and export origin.
  • target partition ID and exact install method/options.
  • source application AppID, components, and export format/version.
  • Windows Installer log plus COM+ ErrorInfo and package-validation events.

Diagnostic sequence for COMADMIN_E_PARTITION_MSI_ONLY

  • preserve and identify the original artifact rather than renaming its extension.
  • export/build a supported MSI Application File from the authoritative COM+ application.
  • validate package integrity and target partition compatibility.
  • install through the documented COMAdmin/Windows Installer path.
  • repopulate the partition and verify application/component identities.

Difference from nearby COMADMIN results

COMADMIN_E_APP_FILE_VERSION concerns a readable application file with an unsupported version; this code rejects the deployment form for a partition. COMADMIN_E_LEGACYCOMPS_NOT_ALLOWED_IN_NONBASE_PARTITIONS concerns component type after packaging.

Retry and recovery

Retry only with a valid MSI application package. Copying DLLs or renaming another file to .msi cannot satisfy the package contract.

What this HRESULT does not establish

The HRESULT does not mean that Windows Installer is unavailable and does not prove the target partition is invalid. It identifies the allowed package form.

Practical administration scenario

A deployment attempts to import a component DLL directly into a tenant partition instead of installing the MSI produced by the COM+ export workflow.

Developer and operations guidance

Record partition ID, method, source path/hash, detected package type, MSI product/package codes when present, export source, and validation event.

Official Microsoft references for COMADMIN_E_PARTITION_MSI_ONLY

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