| Previous | Next |
| COMADMIN_E_EVENTCLASS_CANT_BE_SUBSCRIBER | COMADMIN_E_BASE_PARTITION_ONLY |
COMADMIN_E_LIB_APP_PROXY_INCOMPATIBLE
COMADMIN_E_LIB_APP_PROXY_INCOMPATIBLE is the failure HRESULT 0x8011044F (signed decimal -2146368433, unsigned decimal 2148598863). Its severity bit is 1, facility is 17 (FACILITY_ITF), and the facility-specific code field is 0x044F.
COM+ application type and proxy compatibility: exact meaning of COMADMIN_E_LIB_APP_PROXY_INCOMPATIBLE
Library-application configuration is incompatible with application-proxy behavior. COM+ deployment detects a package or target combination that mixes in-process library semantics with remote proxy semantics.
AllStat records this condition as “Library applications and application proxies are incompatible”.
Where the result occurs
Library applications run in the creator process, server applications own a server process, and application proxies contain client-side remote registration; those roles are not interchangeable. In the specific case of this result, record source application type, proxy export/import path, activation setting, and intended client/server boundary.
Evidence to collect before repair
- Evidence for it should include application Activation/type property, captured before a repair changes state.
- Collect source server and client roles when diagnosing this result; without it the symbolic HRESULT is underdetermined.
- The result investigation needs proxy package provenance so the exact failing boundary remains reconstructable.
- preserve RemoteServerName and marshaling metadata; it anchors the failure to the real administration object.
Diagnostic sequence
- At the boundary, identify the actual server application.
- The next this result diagnostic action is to choose server activation when remote access is required.
- To isolate this result, export a proxy from the server application.
- remove stale incompatible client registration.
- At the boundary, test remote activation with the regenerated proxy.
Difference from nearby COMADMIN results
COMADMIN_E_CAN_NOT_START_APP also recognizes non-server types, but this value identifies the library/proxy combination specifically.
Retry and recovery
Use a server application for remote activation/proxy deployment or keep the library application local.
Practical administration scenario
A team exports registration for a library application and tries to install it as a remote application proxy.
Official Microsoft references
- Microsoft: COMADMIN error codes
- Microsoft: types of COM+ applications
- Microsoft: deploying application proxies
- Microsoft: ICOMAdminCatalog::ExportApplication
- Microsoft: configuring COM+ applications
Looking for a different code? Search another status or error code.