| Previous | Next |
| COMADMIN_E_USER_IN_SET | COMADMIN_E_CANTRECYCLESERVICEAPPS |
COMADMIN_E_CANTRECYCLELIBRARYAPPS
Why library applications have no independent recycle operation: exact meaning of COMADMIN_E_CANTRECYCLELIBRARYAPPS
COM+ refused to recycle a library application. Library components load into the creator’s process, so COM+ does not own a separate application server process that it can gracefully replace.
The Windows SDK describes the condition as “Library applications may not be recycled.”
Where the result occurs
The result is returned by recycle administration after resolving the application type. Recycling is a server-process lifecycle feature; library applications inherit the hosting process lifecycle and relevant pool/recycle behavior.
Evidence to collect before changing the catalog
- AppID, activation type, live process ownership, and component host process.
- the application-instance IDs passed to RecycleApplicationInstances.
- configuration/deployment history showing application-type changes.
- Component Services tracking data and the client process that loaded the library component.
Typical cause branches
- automation selected a library application by name without checking activation type.
- an application was converted from server to library but an old recycle task still targets it.
- a generic operations tool assumes every COM+ application maps to Dllhost.
- the intended server application was confused with a library application of a similar name.
Diagnostic sequence
- repopulate Applications and confirm the target by AppID.
- Identify the real host process and its owning service/application.
- remove invalid recycle policies or monitoring actions for library applications.
- Use the host’s supported restart lifecycle when operationally justified.
- consider a server application only when isolation and managed lifecycle are actual requirements.
Practical administration scenario
A maintenance job enumerates all COM+ applications and issues recycle requests indiscriminately; the library application returns this HRESULT while server applications recycle normally.
Retry and recovery
The same recycle call will remain unsupported while the application is a library application. Recovery means controlling the host or redesigning the hosting mode, not waiting.
Difference from nearby COMADMIN results
COMADMIN_E_CANTRECYCLESERVICEAPPS rejects recycling for Windows-service hosting; COMADMIN_E_APP_NOT_RUNNING concerns absence of a live server instance. This code follows directly from library in-process hosting.
What this HRESULT does not establish
Do not kill an arbitrary client process merely because this HRESULT is returned. First identify which process hosts the library component and whether restarting it is safe.
Developer and operations guidance
Capture AppID, application type, hosting PID/process owner, recycle target variant, configuration revision, and the maintenance policy that selected the application.
Official Microsoft references
Looking for a different code? Search another status or error code.