Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

FIX: Event ID: 4811 occurs when you try to start a queued COM+ application that has a long name and Microsoft Message Queuing is configured for Workgroup mode in Windows Server 2003


View products that this article applies to.

Symptoms

Consider the following scenario:
  • You have a Microsoft COM+ queued component application in Microsoft Windows Server 2003.
  • The COM+ queued component application has a long name.
  • Microsoft Message Queuing is configured for Workgroup mode (private queues).
In this scenario, the COM+ queued component application may not start. When this problem occurs, the following Error event is logged in the Application log:
Event Type: Error
Event Source: COM+
Event Category: (115)
Event ID: 4811
Date: Date
Time: Time
User: N/A
Computer: ComputerName
Description: An unexpected error was returned by Message Queuing API indicated. Unable to retrieve the associated error message text. Message Queuing API return values are defined in Platform SDK file MQ.H.MQOpenQueue

Server Application Name: ApplicationName
Error Code = 0xc00e0003 :
COM+ Services Internals Information:
File: d:\nt\com\complus\src\comsvcs\qc\msmqrt\msmqrt.cpp, Line: 331 Comsvcs.dll file version: ENU 2001.12.4720.2517 shp
Note The error code 0xc00e0003 corresponds to the MQ_ERROR_QUEUE_NOT_FOUND constant.

↑ Back to the top


Cause

This problem occurs because the FormatName property for the main queue in a COM+ queued component application is incorrectly truncated to 59 characters.

↑ Back to the top


Resolution

Service pack information

To resolve this problem, obtain the latest service pack for Windows Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
889100 How to obtain the latest service pack for Windows Server 2003

How to obtain the hotfix

This issue is fixed in the Windows Server 2003 Post-Service Pack 1 COM+ 1.5 Hotfix Package 9.

↑ Back to the top


Status

Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Windows Server 2003 Service Pack 2.

↑ Back to the top


More information

For more information, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
For more information about Workgroup mode in Microsoft Message Queuing, click the following article number to view the article in the Microsoft Knowledge Base:
884974 Information about Workgroup mode and about Domain mode in Microsoft Message Queuing
For more information about how to determine whether Microsoft Message Queuing is installed in Workgroup mode, click the following article number to view the article in the Microsoft Knowledge Base:
248500 How to determine if MSMQ 2.0 is installed in Workgroup or Domain mode

↑ Back to the top


Keywords: KB917399, kbwinserv2003presp2fix, kbqfe, kbfix, kbcomplusqc, kbwinserv2003sp2fix

↑ Back to the top

Article Info
Article ID : 917399
Revision : 3
Created on : 10/9/2011
Published on : 10/9/2011
Exists online : False
Views : 307