FIX: An access violation may occur when the Message Queuing 2.0 run time (Mqrt.dll) is loaded in a COM+ application (891874)


The information in this article applies to:

  • Microsoft Message Queuing 2.0, when used with:
    • Microsoft Windows 2000 Server

Notice

Important This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry

SYMPTOMS

An access violation may occur in the Microsoft Message Queuing 2.0 run time (Mqrt.dll) when the run time is loaded in a COM+ application on a Microsoft Windows 2000 Server-based computer. A message that is similar to the following is logged in the application event log:Event Type: Error
Event Source: COM+
Event Category: SVC
Event ID: 4194
Date: <Date>
Time: <Time>
User: N/A
Computer: <ComputerName>
Description: The description for Event ID ( 4194 ) in Source ( COM+ ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event:
Component Prog ID:
Server Application ID: {63A4AF4F-F47E-4660-9884-369387CBB71D}
Server Application Name: ServerApplicationName
The serious nature of this error has caused the process to terminate.
Exception: C0000005
Address: 0x77F88216
Call Stack: ,
ntdll!RtlpWaitForCriticalSection + 0x60
ntdll!NtCreateThread + 0xBE
MQRT!MQPathNameToFormatName + 0x39
MQOA + 0xD849 MQOA + 0xD7F7
ServerApplicationName + 0xD39C
OLEAUT32!DispCallFunc + 0x15D MSVBVM60!BASIC_CLASS_Invoke + 0x259 MSVBVM60!BASIC_CLASS_Invoke + 0x52 OLEAUT32!UserEXCEPINFO_free_local + 0x57D
+ 0x83D98780

CAUSE

This problem occurs because a thread can be assigned to multiple activities in COM+ applications. This behavior causes excessive Message Queuing API calls in a relatively short time. If the thread is reentered while previous activity is blocked, the Mqrt.dll run time stops responding.

RESOLUTION

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/default.aspx?scid=fh;[LN];CNTACTMS

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites

Microsoft Message Queuing 2.0.

Restart requirement

You must restart your computer if the files that are being updated are running when you apply this software update.

Hotfix replacement information

This hotfix does not replace any other software updates.

The English version of this fix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Date         Time   Version            Size    File name
--------------------------------------------------------------
03-Feb-2005  13:18  5.0.0.792         291,088  Mq1repl.dll      
22-Dec-2003  22:26  5.0.0.791          14,096  Mq1sync.exe      
25-Oct-2004  03:40  5.0.0.798          77,680  Mqac.sys
03-Feb-2005  13:18  5.0.0.791         217,360  Mqads.dll        
20-Sep-2003  19:23  5.0.0.761          25,360  Mqbkup.exe       
03-Feb-2005  13:18  5.0.0.779          50,448  Mqclus.dll       
03-Feb-2005  13:18  5.0.0.785          76,560  Mqdscli.dll      
03-Feb-2005  13:18  5.0.0.773          42,256  Mqdssrv.dll      
22-Dec-2003  22:26  5.0.0.791          98,064  Mqmig.exe        
03-Feb-2005  13:18  5.0.0.791         266,512  Mqmigrat.dll     
03-Feb-2005  13:18  5.0.0.793         222,480  Mqoa.dll         
03-Feb-2005  13:18  5.0.0.784          10,000  Mqperf.dll       
03-Feb-2005  13:18  5.0.0.798         438,544  Mqqm.dll         
03-Feb-2005  13:18  5.0.0.799         102,672  Mqrt.dll         
03-Feb-2005  13:18  5.0.0.776          70,928  Mqsec.dll        
03-Feb-2005  13:18  5.0.0.783         400,656  Mqsnap.dll       
03-Feb-2005  13:18  5.0.0.762          23,824  Mqupgrd.dll      
03-Feb-2005  13:18  5.0.0.798         110,864  Mqutil.dll       
03-Feb-2005  13:18  5.0.0.748          64,784  Msmq.cpl

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

WORKAROUND

To work around this problem, use one or both of the following methods.

Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
  • Change the COM+ object behavior to use the EmulateMTSBehaviour registry subkey, and switch to the MTS model. The MTS behavior is one activity per single-threaded apartment (STA) thread. To change this behavior, follow these steps:

    Note This method affects all COM+ applications that are running on the computer.
    1. Click Start, click Run, type regedit, and then click OK.
    2. Locate and then click the following key in the registry:

      HKEY_LOCAL_MACHINE\Software\Microsoft\COM3\STAThreadPool

    3. On the Edit menu, point to New, and then click DWORD .
    4. Type EmulateMTSBehavior, and then press ENTER.
    5. On the Edit menu, click Modify.
    6. Type 1, and then click OK.

      Note If you enter a value other than zero for the EmulateMTSBehavior value, the thread pool emulates the MTS behavior of one activity for each thread and 100 maximum threads for each package.
    7. Exit Registry Editor.
  • Set the COM+ application to run while it is idle instead of closing. By default, the COM+ application closes after the application has been idle for three minutes or more. The application could stop responding when it restarts after closing. To enable the application to run while it is idle, follow these steps:
    1. Click Start, click Settings, click Control Panel, and then click Administrative Tools.
    2. Double-click Component Services.
    3. In the left pane under Console Root, expand Component Services, expand Computers, expand My Computer, expand COM+ Applications, right-click the COM+ application that you are working with, and then click Properties.
    4. In the Properties dialog box, click the Advanced tab,
    5. Under Server Process Shutdown, click to select the Leave running when idle check box, and then click OK.

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

Modification Type:MinorLast Reviewed:6/2/2006
Keywords:kbfix kbbug kbQFE kbHotfixServer KB891874 kbAudDeveloper
©2004 Microsoft Corporation. All rights reserved.