PRB: Event 4214 When You Play COM+ Queued Component (269292)

SYMPTOMS

When you use COM+ Queued Components (QC), the following Application event log may appear on a server that has the COM+ version 1.0 Queued Application:

Event Type: Error
Event Source: COM+
Event Category: QC Listener
Event ID: 4214
Date: 7/21/2000
Time: 15:49:10
User: N/A
Computer: KINDRA
Description:
The QC Player detected an invalid QC message. The message will be moved to the deadqueue.
Unauthenticated
Server Application ID: {B374406D-0053-4657-BA7E-487F3EFA3FDF}
Server Application Name: QCTest2
Error Code = 0x8000ffff: Catastrophic failure
COM+ Services Internals Information:
File: .\lquereceive.cpp, Line: 1243

You may receive this error message on a server that has the COM+ version 1.5 Queued Application:

The authentication methods have changed in QC for COM+ 1.5. So the resolution part must be changed.

CAUSE

This error is logged each time the COM+ Queued Components listener tries to process a message under the following circumstances:

The message has not been signed. This occurs because the COM+ application proxy has an Authentication Level of None, or because AuthLevel=NONE is specified in the queue: moniker that was used to create the queued component.
The COM+ Queued Application requires authentication.

This error usually occurs because the Authentication Level on the COM+ Application was increased to a value higher than None after the application proxy was exported to the sending computer. QC uses authenticated messages with applications that have an Authentication Level other than None. You may also receive this error if you send unauthenticated messages when the application didn't require authentication.

RESOLUTION

If you require authentication, re-export the COM+ Application with the Authentication Level higher than None to the client computers.

If you do not require authentication, set the Authentication Level to None on the Security tab of the queued COM+ Application's property sheet.

MORE INFORMATION

Steps to Reproduce Behavior

Create a simple Queued Components application.
Set the Application's Authentication Level to None.
Export the application proxy to another computer.
Set the Authentication Level on the COM+ application to something higher than None. You receive the following error message:
Warning
If you save these changes and you have already exported this queued application you must export it again. Otherwise, clients will send unauthenticated messages which will get rejected by the QC listener.
Invoke the Queued Component from the client computer.
After you start the COM+ application, you see the Application event log entry.

REFERENCES

For more information on COM+ Queued Components, see the following Web sites on the Microsoft Developer Network (MSDN):

MSDN: Queued Components
http://msdn.microsoft.com/library/psdk/cossdk/pgwritingcomponents_queuedcomponents_6ir7.htm

COM+ Application Guidelines for Visual Basic Development
http://msdn.microsoft.com/library/techart/complus.htm

MSMQ Message Authentication
http://msdn.microsoft.com/library/psdk/cossdk/pgservices_queuedcomponents_22su.htm