Select the product you need help with

FIX: MSMQ ActiveX Receive Fails Due To Bad SenderID Length

Article ID: 241765

This article was previously published under Q241765

Symptoms

An application receiving a message using the Microsoft Message Queue (MSMQ) ActiveX interface fails with the following error:

MQ_ERROR_SENDERID_BUFFER_TOO_SMALL

Back to the top | Give Feedback

Cause

The MSMQ ActiveX Receive method was coded for a maximum buffer of 32 bytes for the senderid property. This may be too small in some cases.

Back to the top | Give Feedback

When using the MSMQ ActiveX Receive, this error is no longer returned from the MQReceiveMessage in the ActiveX component. Instead, the senderid property buffer is automatically increased until the receive is satisfied. To resolve this problem, obtain the latest service pack for Windows NT 4.0 or the individual software update. For information on obtaining the latest service pack, please go to:

Windows Service Pack Center
(http://windows.microsoft.com/en-US/windows/downloads/service-packs)
-or-
152734
(http://support.microsoft.com/kb/152734/EN-US/ )
how to obtain the latest windows nt 4.0 service pack

For information on obtaining the individual software update, contact Microsoft Product Support Services. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:

http://support.microsoft.com/contactus/?ws=support

(http://support.microsoft.com/contactus/?ws=support)

Windows NT Server 4.0, Terminal Server Edition

To resolve this problem, obtain the latest service pack for Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

152734

(http://support.microsoft.com/kb/152734/EN-US/ )

How to Obtain the Latest Windows NT 4.0 Service Pack

Back to the top | Give Feedback

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

This problem was first corrected in Windows NT Server version 4.0, Terminal Server Edition Service Pack 6.

Back to the top | Give Feedback