FIX: Message Queuing generates an access violation in Windows 2000 Server (892046)



The information in this article applies to:

  • Microsoft Message Queuing 2.0

SYMPTOMS

In Microsoft Windows 2000 Server, Microsoft Message Queuing Trigger Service may generate an access violation, and an event ID error message that is similar to the following may be logged in the event log:
Event Type: Error
Event Source: MSMQ Triggers
Event Category: (1)
Event ID: 64635
Date: 11/28/2004
Time: 4:27:10 AM
User: N/A
Computer: MSMQTRIGSERVER
Description: The following information is part of the event: InvokeMSMQRuleHandlers() has caught an unidentified exception. Unable to determine if the rule has been fired.

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 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     
   --------------------------------------------------------
   29-Dec-2004  14:20  2.4.1.0         4,538,260  Msmqtriggers.exe  
   29-Dec-2004  14:19  1.1.3.0           110,684  Setupextended.dll  
   29-Dec-2004  14:19                    376,892  Trigadm.exe      
   29-Dec-2004  14:19  1.1.0.27           77,881  Trigmon.exe      
   29-Dec-2004  14:19  1.1.0.27          360,510  Trigobjs.dll     
   29-Dec-2004  14:19  1.1.0.27          311,358  Trigserv.exe     
   29-Dec-2004  14:19  1.1.0.27          536,634  Trigsnap.dll     
   29-Dec-2004  14:19                        986  Trigsnap.exp
   29-Dec-2004  14:19                      2,616  Trigsnap.lib
   29-Dec-2004  14:19  1.1.0.27          139,353  Uninst.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

Stack Output
2095f3cc 100292fb trigobjs!__sbh_free_block+0xb2
2095f3dc 1002516a trigobjs!free+0x23
2095f3e4 10018280 trigobjs!operator delete+0x9
2095f3f4 10013835 trigobjs!std::allocator<_bstr_t>::deallocate+0x10
2095f408 10017e55 trigobjs!std::list<unsigned short *,std::allocator<unsigned short *> >::_Freenode+0x15
2095f424 100131f8 trigobjs!std::list<CRuntimeRuleInfo *,std::allocator<CRuntimeRuleInfo *> >::erase+0x95
2095f458 10009efe trigobjs!CStringTokens::~CStringTokens+0xb0
2095f480 1001e12b trigobjs!CMSMQRuleHandler::~CMSMQRuleHandler+0x95
2095f498 1001d1af trigobjs!ATL::CComObject<CMSMQRuleHandler>::~CComObject<CMSMQRuleHandler>+0x6b
2095f4a4 1001e1b6 trigobjs!ATL::CComObject<CMSMQRuleHandler>::`scalar deleting destructor'+0xf
2095f4c0 0040ec2d trigobjs!ATL::CComObject<CMSMQRuleHandler>::Release+0x36
2095f4cc 0040e914 trigserv!ATL::AtlComPtrAssign+0x2d
2095f4e0 0040df37 trigserv!ATL::CComPtr<IUnknown>::operator=+0x14
2095f874 0040d1e6 trigserv!CTriggerMonitor::InvokeMSMQRuleHandlers+0xc34
2095fcd0 0040c90d trigserv!CTriggerMonitor::ProcessReceivedMsgEvent+0x213
2095ff34 00409fde trigserv!CTriggerMonitor::Run+0x20f
2095ff74 0040a1d8 trigserv!CThread::Execute+0xe1
2095ff80 00425817 trigserv!CThread::ThreadProc+0x12
2095ffb4 7c4e987c trigserv!_beginthreadex+0xca
2095ffec 00000000 KERNEL32!BaseThreadStart+0x52

Modification Type:MinorLast Reviewed:6/1/2006
Keywords:kbBug kbfix kbWin2000preSP5fix kbHotfixServer kbQFE KB892046 kbAudEndUser