FIX: The Message Queuing service unexpectedly quits and event IDs 7034 and 4355 are logged in Windows Server 2003 (890746)



The information in this article applies to:

  • Microsoft Message Queuing 3.0, when used with:
    • Microsoft Windows Server 2003, Standard Edition
    • Microsoft Windows Server 2003, Enterprise Edition

SYMPTOMS

On a computer that is running Microsoft Windows Server 2003, the Microsoft Message Queuing service may unexpectedly quit. In this scenario, both the following error events are logged: Event Source: Service Control Manager
Event Category: None
Event ID: 7034
Date: Date
Time: Time
Type: Error
User: N/A
Computer: ComputerName
Description: The Message Queuing service terminated unexpectedly. It has done this 1 time(s). Event Source: MSDTC
Event Category: SVC
Event ID: 4355
Date: Date
Time: Time
Type: Error
User: N/A
Computer: ComputerName
Description: An MS DTC component has generated an exception. Error Specifics: The process '%WINDIR%\system32\mqsvc.exe' hit an exception in a MSDTC related component. The following exception (C0000005) was generated at 0x615AA6BE, Pid:2268. The process is being terminated.
Additional information useful in a debugger:
You can do '.exr 0x2c8f1a8' to display the exception record.
You can do '.cxr 0x2c8f1c4' to display the context at the time of the exception.

MQQM!QMMain(int,unsigned short const * * const) + 0x242ba
MQQM!QMMain(int,unsigned short const * * const) + 0x24f1a
MQQM!QMMain(int,unsigned short const * * const) + 0x24f46
MSDTCPRX!CTmProxyCore::CreateInstance(class CTmProxyCore * *,struct IUnknown *) + 0x15f1
MSDTCPRX!CTmProxyCore::CreateInstance(class CTmProxyCore * *,struct IUnknown *) + 0x366c
MSDTCPRX!JoinDtcEx(unsigned short *) + 0xc1ae
MSDTCPRX!JoinDtcEx(unsigned short *) + 0xc7d5
MSDTCPRX!JoinDtcEx(unsigned short *) + 0x2ef4
MSDTCPRX!JoinDtcEx(unsigned short *) + 0x30ee + 0x2070070

CAUSE

This problem may occur when multiple threads use the same Microsoft Distributed Transaction Coordinator (MSDTC) ITransaction transaction object. In this scenario, some threads might use this object before the object is initialized. Therefore, an access violation error occurs in the Message Queuing service.

RESOLUTION

Hotfix information

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 Windows Server 2003 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 telephone numbers and information about support costs, visit the following Microsoft Web site: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

No prerequisites are required to install this hotfix.

Restart requirement

You must restart your computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix 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
   ----------------------------------------------------------
   21-Dec-2004  23:29  5.2.1731.242      77,312  Mqac.sys
   22-Dec-2004  00:31  5.2.1731.242     146,432  Mqad.dll         
   22-Dec-2004  00:31  5.2.1731.242     192,000  Mqads.dll        
   21-Dec-2004  23:30  5.2.1731.242      28,160  Mqbkup.exe       
   22-Dec-2004  00:31  5.2.1731.242       9,728  Mqcertui.dll     
   22-Dec-2004  00:31  5.2.1731.242      31,232  Mqdbodbc.dll     
   22-Dec-2004  00:31  5.2.1731.242      47,616  Mqdscli.dll      
   22-Dec-2004  00:31  5.2.1731.242      48,128  Mqdssrv.dll      
   22-Dec-2004  00:31  5.2.1731.242      44,544  Mqgentr.dll      
   22-Dec-2004  00:31  5.2.1731.242      28,160  Mqise.dll        
   22-Dec-2004  00:31  2001.12.4720.23   71,680  Mqlogmgr.dll     
   21-Dec-2004  23:30  5.2.1731.242      39,424  Mqmig.exe        
   21-Dec-2004  21:31  5.2.1731.242     220,160  Mqmigrat.dll     
   22-Dec-2004  00:31  5.2.1731.242     230,400  Mqoa.dll         
   22-Dec-2004  00:31  5.2.1731.242      15,872  Mqperf.dll       
   22-Dec-2004  00:31  5.2.1731.242     778,752  Mqqm.dll         
   22-Dec-2004  00:31  5.2.1731.242     169,472  Mqrt.dll         
   22-Dec-2004  00:31  5.2.1731.242     117,248  Mqrtdep.dll      
   22-Dec-2004  00:31  5.2.1731.242     133,632  Mqsec.dll        
   22-Dec-2004  00:31  5.2.1731.242     508,928  Mqsnap.dll       
   22-Dec-2004  00:31  5.2.1731.242      50,176  Mqupgrd.dll      
   22-Dec-2004  00:31  5.2.1731.242     421,888  Mqutil.dll       

STATUS

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

MORE INFORMATION

For additional 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/1/2006
Keywords:kbBug kbfix kbWinServ2003preSP1fix kbHotfixServer kbQFE KB890746 kbAudDeveloper