| Previous | Next |
| COMADMIN_E_APP_FILE_READFAIL | COMADMIN_E_BADPATH |
COMADMIN_E_APP_FILE_VERSION
COMADMIN_E_APP_FILE_VERSION is the failure HRESULT 0x80110409 (signed decimal -2146368503, unsigned decimal 2148598793). Its severity bit is 1, facility is 17 (FACILITY_ITF), and the facility-specific code field is 0x0409.
COM+ application package and file operation: exact meaning of COMADMIN_E_APP_FILE_VERSION
The application file uses a version that this COM+ installation does not accept. Package validation succeeds far enough to read format metadata and then rejects the declared version.
AllStat records this condition as “Invalid version number in application file”.
Where COMADMIN_E_APP_FILE_VERSION occurs
The HRESULT belongs to COM+ package/import/export processing; the package path, file bytes, deployment identity, and target catalog must be correlated before changing the system. In the specific case of COMADMIN_E_APP_FILE_VERSION, record source and destination Windows versions, export options, package hash, and whether compatibility format was selected.
Evidence to collect before repair
- For
COMADMIN_E_APP_FILE_VERSION, preserve exact source/destination paths and the caller identity; it anchors the failure to the real administration object. - Evidence for
COMADMIN_E_APP_FILE_VERSIONshould include file size, hash, version, signature, and timestamps, captured before a repair changes state. - Collect source and target Windows/COM+ versions when diagnosing
COMADMIN_E_APP_FILE_VERSION; without it the symbolic HRESULT is underdetermined. - The
COMADMIN_E_APP_FILE_VERSIONinvestigation needs underlying file-system or package-validation error from events so the exact failing boundary remains reconstructable.
Diagnostic sequence for COMADMIN_E_APP_FILE_VERSION
- For
COMADMIN_E_APP_FILE_VERSION, preserve the original package before attempting repair. - At the
COMADMIN_E_APP_FILE_VERSIONboundary, validate path access and package integrity under the actual identity. - The next
COMADMIN_E_APP_FILE_VERSIONdiagnostic action is to compare export options and target-platform support. - To isolate
COMADMIN_E_APP_FILE_VERSION, regenerate the package from a coherent source application when metadata is wrong. - For
COMADMIN_E_APP_FILE_VERSION, repeat the complete supported install/export operation and verify catalog state.
Retry and recovery
Re-export with a format supported by the target or deploy to a compatible platform; repeated installation of the same file is deterministic.
Difference from nearby COMADMIN results
COMADMIN_E_APP_FILE_READFAIL indicates unreadable content, whereas this code identifies a readable but unsupported application-file version.
Practical administration scenario
A package exported on a newer server is installed on an older host whose COM+ catalog cannot interpret the package version.
Official Microsoft references for COMADMIN_E_APP_FILE_VERSION
- Microsoft: COMADMIN error codes
- Microsoft: ICOMAdminCatalog::InstallApplication
- Microsoft: ICOMAdminCatalog::ExportApplication
- Microsoft: deploying COM+ applications
- Microsoft: the COM+ catalog
Looking for a different code? Search another status or error code.