none
HTTP/1.1 500 Internal server error when POSTing message to MSMQ RRS feed

  • Question

  • Windows Server 2003 - IIS6.0

    I have 2 private queues defined on the Win Server: RequestQueue and ResponseQueue. "MSMQ HTTP Support" is enabled on the server. 

    A client application is using Internet Messaging in MSMQ to directly place a message in the RequestQueue on the server.

    When the client application attempts to place the message in the queue, the server returns with 500 Internal Server Error.

    Using a sniffer -

    The client makes a TCP/IP connection with the server and sends the first frame:

    POST /msmq/private%24/requestqueue HTTP/1.1
    Host: ronr679
    Content-Type: multipart/related; boundary="MSMQ - SOAP boundary, 2088"; type=text/xml
    Content-Length: 1143
    SOAPAction: "MSMQMessage"
    Proxy-Accept: NonInteractiveClient

    The server responds to that first frame with with:

    HTTP/1.1 500 Internal server error
    Connection: close
    Date: Tue, 05 Oct 2010 22:19:57 GMT
    Server: Microsoft-IIS/6.0
    MicrosoftOfficeWebServer: 5.0_Pub
    X-Powered-By: ASP.NET
    Content-Length: 0
     

    There is a message on an MSMQ blog which describes my problem exactly:

    http://blogs.msdn.com/b/johnbreakwell/archive/2006/09/15/msmq-messages-using-http-just-won-t-get-delivered.aspx

    It points to an KB to solve the problem:

    http://support.microsoft.com/default.aspx?scid=kb;EN-US;916699 

    However my Win 2003 server name (I assume they are talking about the DNS name) is well under 15 characters so I don't think this is my problem.

    I think this is something related to the Message Queuing ISAPI extension (MQISE.dll) set up. In the MSMQ property | Virtual Directory tab | Configuration, I've got MQISE.DLL for the wildcard application map so I'm thinking that the POST would be processed.

    Is there some other MSMQ settings I am missing in setting up IIS to receive MSMQ messages over HTTP?

     

    Sunday, October 17, 2010 4:50 PM

All replies

  • Hi Ron,

    It's tricky to troubleshoot as the MQISE internal error logging (which would show you the answer) is in a binary log file that requires Microsoft PSS to format to text.

    Does normal non-HTTP MSMQ traffic work?

    Cheers

    John Breakwell

    Monday, October 18, 2010 12:21 PM