| Event Id | 4808 |
| Source | COM+ |
| Description | "An unexpected error was returned by the Message Queuing API MQOpenQueue : The queue does not exist, or you do not have sufficient permissions to perform the operation. Server Application ID: Server Application Instance ID: Server Application Name: Error Code = 0xc00e0003 : COM+ Services Internals Information: File: Line: file version:" |
| Event Information | If a COM+ Queued Component (QC) Queue is deleted, any messages that are unprocessed and still in the queue at the time of deletion are placed in the transactional dead-letter message queue. If a client sends messages to the queue after it has been deleted, those messages are also placed in the transactional dead-letter message queue, and the client does not receive any error messages. Steps to Reproduce Behavior: 1. Create a simple COM+ component that takes a String as a parameter. 2. Install this Component into a COM+ Server application. 3. In the COM+ Server application properties, mark the component and the interface on the component as queued. 4. Create a client that will create the queued component, and call the simple method. 5. Run the client application, and call the method repeatedly. 6. In the MSMQ viewer, look at the messages for the queued component. Note that they are still waiting to be processed. 7. Delete this queue. Note that all of the messages are transferred to the transactional dead-letter queue. 8. Run the client again, and send many messages. Note that no errors are returned to the client and that all of the messages are transferred to the transactional dead-letter message queue. |
| Reference Links | INFO: What Happens When a COM+ Queued Component Queue Is Deleted |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.