FIX: Message Queuing Trigger Passes a Message ID That Is Not Correct (828697)



The information in this article applies to:

  • Microsoft Message Queuing 2.0, when used with:
    • the operating system: Microsoft Windows 2000

SYMPTOMS

When you create a Microsoft Message Queuing (also known as MSMQ) trigger that invokes an executable file and passes the message ID to the executable file as a command-line parameter, the message ID string is set to a value that is not correct.

CAUSE

This problem occurs because the message ID is not converted to a string. Instead, it is passed as binary.

RESOLUTION

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem.

To resolve this problem, 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.

The English version of this hotfix has the file attributes (or later) 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     
-------------------------------------------------------------------
18-Sep-2003  	14:48	2.4.1.0    4,528,504      Msmqtriggers.exe
18-Sep-2003  	14:47                360,508      Trigadm.exe
18-Sep-2003  	14:47  	1.1.0.25      77,881      Trigmon.exe
18-Sep-2003  	14:46  	1.1.0.25     368,702      Trigobjs.dll
18-Sep-2003  	14:47  	1.1.0.25     323,646      Trigserv.exe
18-Sep-2003  	14:47  	1.1.0.25     536,634      Trigsnap.dll 


STATUS

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

Modification Type:MinorLast Reviewed:10/18/2005
Keywords:kbQFE kbMSMQ200fix kbTrigger kbfix kbbug KB828697 kbAudDeveloper