Microsoft KB Archive/811307

= Message Queuing Triggers Event ID 65508 =

Article ID: 811307

Article Last Modified on 2/19/2007

-

APPLIES TO


 * Microsoft Message Queuing 2.0

-





SYMPTOMS
When Microsoft Message Queuing Triggers is monitoring a remote queue, and if Microsoft Message Queuing (also known as MSMQ) 2.0 on the remote machine is restarted, you may receive the following error message:

Event Type: Error

Event Source: MSMQ Triggers

Event Category: TrigServ

Event ID: 65508

Date: 11/14/2002

Time: 4:25:51 PM

User: N/A

Computer: ComputerName

Description: The description for Event ID (65508) in Source (MSMQ Triggers) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: GetQueueCompleteion status has completed without an IO packet, and with an unknown Overlapped HRESULT of (0). Interpreting this as an error...



CAUSE
The queue handle that is used by Message Queuing Triggers is not valid and will not retry receive requests after the restart.



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

To resolve this problem immediately, download the fix by clicking the download link later in this article or contact Microsoft Product Support Services to obtain the fix. 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;EN-US;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. Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

The following file is available for download from the Microsoft Download Center:

The English version of this fix contains files with the following file attributes. 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 --  11-Dec-2002  08:55  1.1.3.0       98,396  Setupextended.dll 11-Dec-2002 08:55               360,508  Trigadm.exe 11-Dec-2002 08:55  1.1.0.22      77,881  Trigmon.exe 11-Dec-2002 08:54  1.1.0.22     368,702  Trigobjs.dll 11-Dec-2002 08:54  1.1.0.22     323,646  Trigserv.exe 11-Dec-2002 08:55  1.1.0.22     536,634  Trigsnap.dll 11-Dec-2002 08:55                   986  Trigsnap.exp 11-Dec-2002 08:55                 2,616  Trigsnap.lib 11-Dec-2002 08:55  1.1.0.22     122,969  Uninst.dll



WORKAROUND
Restart the MSMQ Triggers service.

Additional query words: MQ_ERROR_QUEUE_NOT_AVAILABLE MQ_ERROR_REMOTE_MACHINE_NOT_AVAILABLE.



To enable Message Queuing triggers to refresh remote queue handles, change the following registry value from 0 to 1 or any positive number. The registry value is created the first time that version 22 of the MSMQ Triggers service is started. It is disabled by default.

HKEY_LOCAL_MACHINE\software\microsoft\msmq\Triggers\RemoteQueueRefreshFrequency

This value defines how frequently the Message Queuing Trigger service refreshes remote handles, in minutes. Therefore, 1 means refresh every one minute; 2 means refresh once every two minutes, and so on.

Note: all admin operations (add trigger, add rule, and so on) are blocked while refreshing the remote handles. The refresh operation may take a long time if remote computers are not available.

Build 22 of Message Queuing Triggers also contains a fix that changes how the trigger service accesses the registry on the local machine. In earlier versions, the Trigger service always used the RegConnectRegistry function to access the local registry. This function requires the Remote Registry service, which was not desireable for some users. Now, the trigger service uses RegOpenKey when accessing the local registry.

Keywords: kbdownload kbqfe KB811307

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.