Article ID: 916699
Article Last Modified on 6/7/2007
APPLIES TO
- Microsoft Message Queuing 3.0
SYMPTOMS
When you use the HTTP protocol to send a message to a server that is running Microsoft Message Queuing 3.0, the message may not be delivered. When this problem occurs, the message will remain in the sending computer's queue and will eventually time-out. However, you will not receive an error message.
When this problem occurs, entries that resemble the following may be logged in the Message Queuing log:
CAUSE
This problem occurs when the Message Queuing ISAPI extension (Mqise.dll) tries to bind to the local Message Queuing service after the Message Queuing ISAPI extension receives a POST request that contains a Message Queuing message. The Message Queuing ISAPI extension cannot bind to the Message Queuing service when the server name is exactly 15 characters long. RPC exception 0x6a6 (RPC_S_INVALID_BINDING) occurs in the W3wp.exe process. However, the exception is handled. Therefore, you do not receive an error message.
Message Queuing resolves the server name by using the DNS host name. The Message Queuing ISAPI extension cannot bind to the Message Queuing service because the buffer that Message Queuing uses to resolve the server name is too small.
RESOLUTION
To resolve this problem, rename the server that is running Microsoft Message Queuing 3.0. Use a name that contains less than 15 characters.
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
MORE INFORMATION
Steps to reproduce the problem
- Rename the server that is running Message Queuing 3.0. Use a name that contains 15 characters.
- Restart the server.
- Install Message Queuing together with HTTP protocol support.
- Attach a debugger to the W3wp.exe process on the server. Have the debugger look for the following exception:
- Send a message from a remote computer that has Message Queuing.
Additional query words: MSMQ
Keywords: kbmsg kbbug kbtshoot kbprb KB916699
