| Previous | Next |
| COMADMIN_E_CAT_SERVERFAULT | COMQC_E_NO_QUEUEABLE_INTERFACES |
COMQC_E_APPLICATION_NOT_QUEUED
COMQC_E_APPLICATION_NOT_QUEUED means that the queue moniker targeted a COM+ application that is not marked to support queued activation.
The contract behind the HRESULT
Queued Components cross several independent layers: call recording, MSMQ transport, message authentication, listener playback, and execution of the business method. Message ID, queue format name, original sender, any mover or requeuer, and the COM+ application version are the keys that join those layers without treating every queue symptom as the same fault.
A queue can exist in MSMQ while the COM+ application is not configured as queued; both catalog and queue state matter.
Diagnostic worksheet
- COM+ application identity, QueuingEnabled/Listening state, CLSID, and queue moniker
- COM+ catalog export or Component Services settings
- Destination MSMQ queue and whether it was created for this application
- Client moniker parameters and server application name
Reproduce the condition safely
- Activate the component directly to verify ordinary COM registration.
- Enable queuing on a test copy of the COM+ application and compare.
- Enumerate the application queue and listener before sending a method call.
Closing the incident
Apply the smallest change that addresses the first rejected condition: Mark only the intended COM+ application as queued, create/associate its queue, and start listening under the correct identity.
Close the incident only when a queued call is recorded, delivered once to the intended application, and a nonqueued test application remains rejected.
Technical references
Looking for a different code? Search another status or error code.