Important:
This is retired content. This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.
A version of this page is also available for
4/8/2010

This property specifies a queue for receiving response messages returned from the receiving application.

Syntax 

HRESULT get_ResponseQueueInfo( 
  IMSQQueueInfo** 
ppinfoResponse 
);
HRESULT putref_ResponseQueueInfo( 
  IMSQQueueInfo* 
pinfoResponse
);

Parameters

ppinfoResponseor pinfoResponse

Queue information ( MSMQQueueInfo) object that represents the response queue.

Return Value

The following table describes the common return values.

Value Description

S_OK

Success

E_INVALIDARG

One or more arguments are invalid

E_NOTIMPL

The function contains no implementation

E_OUTOFMEMORY

Out of memory

Remarks

ResponseQueueInfois used to send the format name of another queue to the receiving application. Typically, this is done so the receiving application can send response messages back to the sending application.

Note:
The MSMQQueueInfoobject of a private queue (which is inaccessible otherwise) can also be sent using ResponseQueueInfo.

Messages returned to the response queue are application defined. The application must define what is in the messages as well as what is to be done when a message is received.

You can also set and retrieve the response queue when using Message Queuing function calls.

For information on See

Setting and retrieving the response queue using Message Queuing function calls

PROPID_M_RESP_QUEUE

Requirements

Header mqoai.h
Library mqoa.lib
Windows Embedded CE Windows CE .NET 4.0 and later
Windows Mobile Windows Mobile Version 5.0 and later

See Also

500 Internal Server Error

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at webmaster@systemmanager.forsenergy.ru to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.

Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.