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

The registry stores information necessary to configure the system for applications and hardware devices. The registry also contains information that the OS continually references during operation.

Message Queuing (MSMQ) can be configured by setting registry information or by running the MSMQAdm utility.

Note:
You must configure MSMQ after you set the computer name and current time. The current time is used for generating the globally unique identifier (GUID). If the time is not set properly, more than one machine might be assigned the same GUID. For this reason, configuration does not proceed during the first cold boot. Instead, the user is responsible for the configuration.

The persistent state of MSMQ is a combination of information in the MSMQ registry key and the MSMQ base directory. The base registry key is HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSMQ\SimpleClient.

The following named values are for the base-registry MSMQ 7 configuration parameters.

Value : type Description

AllowResponse: REG_SZ

Default setting is "No."

If the value is "No", MSMQ sends the acknowledgment using the host name, such as www.adatum.com.

If the value is "Yes", MSMQ sends the acknowledgment using the IP address of the sender, such as 192.168.0.0.

Acknowledges the sender. MSMQ sends acknowledgements when the PROPID_M_ACKNOWLEDGE property is set.

BaseDir: REG_SZ

Default setting is "\Temp\MSMQ."

Directory used for queue information and message storage.

BinaryEnabled: REG_SZ

Default setting is "No."

You can set the value to "Yes" or "No."

If the value is "No", MSMQ receives incoming messages, but does not send outgoing messages.

If the value is "Yes", MSMQ supports the native MSMQ and the SOAP-based protocol.

Security Note:
Setting the value to "No" minimizes the risk of exposure by allowing only specific types of messages.
Note:
For example, if MSMQ is used in a private network, you can set BinaryEnabledto "Yes" to support native MSMQ and SOAP-based protocols.
Note:
If MSMQ is used in the Internet, you can set BinaryEnabledto "No" and SrmpEnabledto "Yes" to support only SOAP-base protocol.

CEStartAtBoot: REG_DWORD

Default setting is 1. Windows Embedded CE-specific entry.

If this value is 0, MSMQ will not start at boot time but can be started using the MSMQAdm utility.

CETrackNetwork: REG_SZ

Default setting is "Yes."

You can set the value to "Yes" or "No."

If the value is "Yes", MSMQ attempts to resend immediately after the network reconnects, instead of following the standard resend schedule.

DebugOutputChannels: REG_DWORD

Mask of the MSMQ debug output channels.

DebugOutputMask: REG_DWORD

Mask of the enabled debug zones.

DebugQueue: REG_SZ

Queue used to route debugging.

DefaultLocalQuota: REG_DWORD

Default value is 1024.

If this value is not present in the registry, the default incoming quota is 1024 kilobytes.

Incoming queue quota, in kilobytes.

DefaultQuota: DWORD

Default setting is 256.

If this value is not present in the registry, the default outgoing quota is 256 kilobytes.

Queue quota, in kilobytes, for message storage by a remote queue. The maximum default queue size and the size of output queues are expressed in kilobytes.

FSMaxTimeout: REG_DWORD

Time-out, in seconds, for an installable file system.

If the MSMQ base directory is not found on startup, MSMQ waits for this period of time, rechecking every second before failing.

HostName: REG_SZ

Default is not set in the registry.

Host name to override the machine's host name.

If this value is not present in the registry, information is queried dynamically from the network.

LanRetrySchedule: REG_DWORD

Default is not set in the registry.

If there are no network interfaces, the next attempt to connect is shifted by this value, in seconds, instead of the next-leg-of-connection schedule.

If 0, the existence of network interfaces is not checked and the connection schedule is followed.

LogSize: REG_DWORD

Size of the MSMQ log file.

MachineQuota: REG_DWORD

Default setting is 2048.

If this value is not present in the registry, the default machine quota is 2048 kilobytes.

Machine queue quota, in kilobytes.

MessageID: REG_DWORD

Current message identifier, accurate within 1,000 messages.

The MSMQ client sets this identifier for backup/restore purposes.

A user should not change it.

OrderAckScale: REG_DWORD

Default setting is 5.

Multiplier for transactional acknowledgement periods and time-outs.

OrderAckWindow: REG_DWORD

Number of packets sent per transactional queue until the transactional receipt arrives.

Changing this can cause severe repercussions.

OutFRSQueue: REG_SZ

Outgoing Falcon Routing Server (FRS) queue format name.

This name must be DIRECT.

If another name is used, you cannot configure the outgoing FRS queue.

PingPort: REG_DWORD

Default setting is 3527 by the registration utility.

Machine User Datagram Protocol (UDP) port that the MQPing service is monitoring. This ping port is set by the registration utility.

Do not change the ping port setting.

PingTimeout: REG_DWORD

Default is not set in the registry.

Time-out for response to MQPing.

If this value is 0, pinging is disabled and connections are attempted immediately.

Port: REG_DWORD

Default value is 1801.

Machine TCP/IP port that MSMQ is monitoring. This port is set to 1801 by the registration utility.

Do not change the port setting.

QueueManagerGUID: REG_BINARY

Default is not set in the registry.

GUID of the queue manager, which is used for session protocols between and desktop implementations.

RetrySchedule: REG_BINARY

Array of little-endian shorts, each containing a next-leg-of-connection schedule.

SrmpEnabled: REG_SZ

Default setting is "No", which disables SRMP.

You can set the value to "Yes" or "No".

If this value is "Yes", MSMQ supports the SOAP-based protocol.

Security Note:
Setting the value to "No" minimizes the risk of exposure by allowing only specific types of messages.
Note:
For example, if MSMQ is used in a private network, you can set BinaryEnabledto "Yes" to support native MSMQ and SOAP-based protocols.
Note:
If MSMQ is used in the Internet, you can set BinaryEnabledto "No" and SrmpEnabledto "Yes" to support only SOAP-base protocol.

UntrustedNetwork: REG_SZ

Default setting is "Yes", which indicates that the current network is untrusted.

You can set the value to "Yes" or "No".

Disables message routing.

Security Note:
This values allows you to selectively provide service to known networks, which minimizes security vulnerability.

The following registry entries provide resilience against dropped connections that can result from very slow wireless LANs.

Value Description

ConnectionTimeout: REG_DWORD

Time-out, in seconds, for a connection to complete.

IdleTimeout: REG_DWORD

Time interval, in seconds, before the connection closes because there is no incoming message.

MaxAckTimeout: REG_DWORD

Maximum negotiated time-out, in seconds, for receiving acknowledgement for session-level messages.

MinAckTimeout: REG_DWORD

Minimum negotiated time-out, in seconds, for receiving acknowledgement for session-level messages.

MinStoreAckTimeout: REG_DWORD

Minimum negotiated time-out, in seconds, for receiving acknowledgement for session-level reliable messages before they are stored.

The base registry key for SRMP is HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSMQ\SimpleClient\SRMP.

The following named value can be used for the base-registry SRMP configuration parameters.

Value Description

MaxPost: REG_DWORD

Default size is 131072 bytes.

Maximum size of the buffer, in bytes, that SrmpIsapi reads off the wire when processing SRMP messages over HTTP.

Messages over this size are rejected and a 413 – Request Entity Too Large is sent to the client.

See Also

Concepts

MSMQ Security

Other Resources

Message Queuing
Message Queuing

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.