A Message Queuing trigger on Windows 7 or on Windows 2008 R2 stops processing messages after the Message Queuing service is restarted on the computer that hosts the message queue

Applies to: Windows 7Windows Server 2008 R2

Symptoms


Consider the following scenario:

  • You install Message Queuing on a computer that is running Windows 7 or Windows Server 2008 R2.
  • You create a Message Queuing trigger that associates with a remote public queue.
  • You create and attach a rule to the trigger. This rule makes the trigger start an executable file when a message arrives at the remote public queue.
  • You stop and restart the Message Queuing service on the computer that hosts the remote public queue.
In this scenario, the Message Queuing trigger does not start the executable file when a new message arrives at the remote queue.

Cause


The issue occurs because of a problem in the Message Queuing Triggers service. When the Message Queuing service is stopped on the computer that hosts the remote queue, the Message Queuing Triggers service retires the queue handle. However, the Message Queuing Triggers servicedoes not obtain a new queue handle when the Message Queuing service is restarted on the remote computer. Therefore, the trigger does not start the executable file when a message arrives at the remote queue.

Resolution


Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, your computer must be running Windows 7 or Windows Server 2008 R2. Additionally, you must install Message Queuing 5.0 on the computer.

Registry information

To use the hotfix in this package, you do not have to make any changes to the registry.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The English (United States) version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows 7 and Windows Server 2008 R2 file information notes
Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 7/Windows Server 2008 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2 and for Windows 7" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows 7
File nameFile versionFile sizeDateTimePlatform
Mqtgsvc.exe6.1.7600.20775126,46409-Aug-201004:17x86
Mqtgsvc.exe.cfgNot Applicable4110-Jun-200921:31Not Applicable
For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Mqtgsvc.exe6.1.7600.20775189,44009-Aug-201005:08x64
Mqtgsvc.exe.cfgNot Applicable4110-Jun-200920:49Not Applicable
For all supported IA-64-based versions of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Mqtgsvc.exe6.1.7600.20775397,82409-Aug-201003:56IA-64
Mqtgsvc.exe.cfgNot Applicable4110-Jun-200920:55Not Applicable

Workaround


Workaround for Windows 7 and for Windows Server 2008 R2

To work around this issue, restart the Message Queuing Triggers service.

Status


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

More Information


For more information about Message Queuing, visit the following Microsoft website:For more information about software update terminology, 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

Additional file information

Additional file information for Windows 7 and for Windows Server 2008 R2

Additional files for all supported x86-based versions of Windows 7
File nameUpdate.mum
File versionNot Applicable
File size1,617
Date (UTC)09-Aug-2010
Time (UTC)07:37
File nameX86_54a821a51b1ece5560f7dc4f0e3614dd_31bf3856ad364e35_6.1.7600.20775_none_96ec59e03fb562dd.manifest
File versionNot Applicable
File size709
Date (UTC)09-Aug-2010
Time (UTC)07:37
File nameX86_microsoft-windows-msmq-triggers-service_31bf3856ad364e35_6.1.7600.20775_none_28914c66376e4071.manifest
File versionNot Applicable
File size9,413
Date (UTC)09-Aug-2010
Time (UTC)04:54
Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File nameAmd64_4f970e3622a66494285d60794ddf34e4_31bf3856ad364e35_6.1.7600.20775_none_30de7a377ce12c81.manifest
File versionNot Applicable
File size713
Date (UTC)09-Aug-2010
Time (UTC)07:37
File nameAmd64_microsoft-windows-msmq-triggers-service_31bf3856ad364e35_6.1.7600.20775_none_84afe7e9efcbb1a7.manifest
File versionNot Applicable
File size9,419
Date (UTC)09-Aug-2010
Time (UTC)05:50
File nameUpdate.mum
File versionNot Applicable
File size1,828
Date (UTC)09-Aug-2010
Time (UTC)07:37
Additional files for all supported IA-64-based versions of Windows Server 2008 R2
File nameIa64_988356ccf0827918f8fa5fdfab2d2621_31bf3856ad364e35_6.1.7600.20775_none_dd01f13e14924180.manifest
File versionNot Applicable
File size711
Date (UTC)09-Aug-2010
Time (UTC)07:37
File nameIa64_microsoft-windows-msmq-triggers-service_31bf3856ad364e35_6.1.7600.20775_none_2892f05c376c496d.manifest
File versionNot Applicable
File size9,416
Date (UTC)09-Aug-2010
Time (UTC)05:39
File nameUpdate.mum
File versionNot Applicable
File size1,453
Date (UTC)09-Aug-2010
Time (UTC)07:37