Fields

Message

Message with ID %1\%2 was put into queue %3

Fields

Message

Message received

Message

Message sent over network

Message

Message came over network

Fields

Message

Message with ID %1\%2 was sent to queue %3

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Message

The Message Queuing serivce performance counter data are not available. The performance counter module failed to initialize. Please run 'lodctr.exe mqperf.ini' from the command console and restart the service, or contact Microsoft support. Error %1: %2

Message

The Message Queuing service started.

Message

The Message Queuing service is online with Active Directory Domain Services and fully operational.

Message

The message file '%1' was successfully created.

Message

The Message Queuing service successfully joined the computer's domain '%1'.

Message

Message Queuing left the domain and is now operating in workgroup mode.

Message

Message Queuing successfully moved to the %1 domain.

Message

The computer belongs to the %1 domain. It is recommended that you use the MoveTree utility to move the msmq (MSMQ Configuration) object of this computer from the %2 domain (its previous domain) to the current domain.

Message

Message Queuing Down-level Client Support started.

Message

The Message Queuing service stopped.

Message

Message Queuing is operating in Hardened mode.

Message

The MsmqServices object is configured with weakened security to support MSMQ 1.0 clients. With weakened security, the Message Queuing Down-level Client Support service will use its own rights (under the LocalSystem account on a domain controller) to view object properties, but it will not bypass the security restrictions on creating Message Queuing objects and setting their properties.

Message

The MsmqServices object is configured with default security. MSMQ 1.0 clients will not be able to query Active Directory Domain Services in this configuration.

Message

Message Queuing found multiple IP addresses for the local computer. Message Queuing will use the default IP address determined by the PGM driver for multicast messages. To use a different IP address, set the \HKLM\Software\Microsoft\MSMQ\Parameters\%1 registry value to one of the following valid IP addresses: %2!S!.

Message

Message Queuing will use the IP address %1. To use a different IP address, set the \HKLM\Software\Microsoft\MSMQ\Parameters\%2 registry value to one of the following valid IP addresses: %3!S!.

Message

A backup (components: %1) was completed successfully.

Message

A restore was completed successfully.

Message

The restore located at '%1' was handled successfully. Restored components are %2.

Message

The MSMQ VSS Writer is disabled through the registry setting. Backup and restore support is not available. To enable the writer, please delete registry value DisableMsmqVSSWriter or set it to 0.

Message

Message Queuing is resuming accepting messages because the system memory usage has normalized.

Message

The Message Queuing service deleted message '%1'. The message cannot be restored because the queue '%2' does not exist.

Message

The Message Queuing service has insufficient privileges to create audit log messages.

Message

The Message Queuing down-level client support service has insufficient privileges to create audit log messages.

Message

The Message Queuing service session cleanup is taking longer than expected. This indicates a potential DoS attack and an excessively high value configured for the QueueCountLimit DWORD registry value at HKLM\Software\Microsoft\MSMQ\Parameters\QueueCountLimit. The current value set for QueueCountLimit is '%1'. Consider setting it to a lower value to protect the service from DoS attacks.

Message

The Message Queuing service cannot communicate with other computers, because the RPC interface cannot use the TCP/IP protocol. Error %1: %2

Message

The Client Access License (CAL) limit was reached. This server is unable to serve more clients. This may lead to messaging performance degradation. See the Windows documentation for information on how to increase your client license limit. This event is logged no more than once per %1 seconds.

Message

The Message Queuing server cannot determine if the local domain controller is trusted for delegation. This may indicate a serious problem. For more information, see Help and Support Center.

Message

Message Queuing detected a problem with the local domain controller. Until the problem is resolved, Message Queuing will function unpredictably. Using Event Viewer, inspect the directory service, File Replication Service, and system logs to help identify the problem.

Message

This server was unable to resolve the IP addresses of other routing servers. Please check that all computers are registered in DNS.

Message

There is an inconsistency between the actual network addresses and the addresses that are listed on other Message Queuing servers for this computer. If this computer belongs to an MSMQ 1.0 site, you should use MSMQ Explorer on the local primary site controller (PSC) to manually update the addresses listed for this computer.

Message

The Message Queuing directory service is not running as a local system. To get the directory service functionality, you need to run as a local system.

Message

Message Queuing Down-level Client Support cannot start. This service can operate only on a domain controller. The service can be disabled by using Computer Management to change its startup type in the Properties dialog box from Automatic to Manual or Disabled.

Message

The mapping of the URL %1 to the queue %2 was ignored. This URL is already mapped to another queue.

Message

The mapping of the URL %1 to the queue %2 is ignored. This queue name is not a valid URL-style queue name.

Message

Message Queuing Down-level Client Support failed to create the MSMQ Configuration (msmq) object with a given GUID for computer %1. Creating MSMQ Configuration objects with given GUIDs may be required for Message Queuing clients during the setup of Windows NT 4.0 or Windows 9x computers and when a Windows 2000 computer joins a Windows Server 2003 (or later) domain. By default, an Active Directory Domain Services forest does not support adding an object with a supplied GUID. You can solve this problem by upgrading Message Queuing on the client computer to a version that does not require creating an object with a given GUID. There are also alternative solutions.

Message

The sites where the computer resides cannot be resolved. Check that the subnets in your network are configured correctly in Active Directory Domain Services and that each site is configured with the appropriate subnet.

Message

Message Queuing cannot bind to UDP port 3527. Message Queuing's internal ping mechanism uses this port to establish network connections. Another process may be using this port. Message Queuing can continue to operate without using this port, but connection times will not be optimal. To optimize the establishment of connections, free this port and restart Message Queuing.

Message

Message Queuing will use an encryption key with an effective length of 40 bits when sending messages encrypted with the RC2 encryption algorithm. To restore strong encryption, remove the registry value HKLM\Software\Microsoft\MSMQ\Parameters\Security\SendEnhRC2With40.

Message

Message Queuing cannot establish new connections to this computer because connection limit was reached.  There are too many computers attempting to send messages to or receive from this computer. This event is logged at most once per %1 seconds. To change this setting, set \HKLM\Software\Microsoft\MSMQ\Parameters\Event2181 registry value to desired time in seconds.

Message

Storage quota exceeded for MSMQ queue %1. No more messages can be stored in the queue.  You can increase a queue's storage quota by editing queue properties in Computer Management console. This event is logged at most once per %2 seconds. To change this setting, set \HKLM\Software\Microsoft\MSMQ\Parameters\Event2182 registry value to desired time in seconds.

Message

Machine MSMQ storage quota was exceeded or there is insufficient disk space. No more messages can be stored in user queues.  You can increase Message Queuing storage quota or purge unneeded messages by using Computer Management console. This event is logged at most once per %1 seconds. To change this setting, set \HKLM\Software\Microsoft\MSMQ\Parameters\Event2183 registry value to desired time in seconds.

Message

Message Queuing could not resolve the name '%1' to an IP address. Try to ping the recipient computer, and check this computer's DNS settings.  This event is logged at most once per %2 seconds. To change this setting, set \HKLM\Software\Microsoft\MSMQ\Parameters\Event2184 registry value to desired time in seconds.

Message

A socket operation failed with error %1. Next hop address is %2!S!. Message Queuing cannot send the message now, but it will retry to send the message. This event is logged at most once per %3 seconds. To change this setting, set \HKLM\Software\Microsoft\MSMQ\Parameters\Event2185 registry value to desired time in seconds.

Message

Message Queuing could not establish connection to %1, because the connection limit for this computer was reached. There too many computers trying to send to or receive messages from this computer. This event is logged at most once per %2 seconds. To change this setting, set \HKLM\Software\Microsoft\MSMQ\Parameters\Event2186 registry value to desired time in seconds.

Message

Message Queuing could not establish connection to %1, because connection was refused by the recipient computer.  It is possible that Client Access Licenses (CALs) are exhausted (if the recipient is a Windows Server), or connection limit has been reached (if the recipient is a Windows workstation). This event is logged at most once per %2 seconds. To change this setting, set \HKLM\Software\Microsoft\MSMQ\Parameters\Event2187 registry value to desired time in seconds.

Message

Message Queuing could not access Active Directory Domain Services and failed to compute routing path for messages sent to queue %3. Messages will wait in the outgoing queue until connection with Active Directory Domain Services is restored.  This event is logged at most once per %4 seconds. To change this setting, set \HKLM\Software\Microsoft\MSMQ\Parameters\Event2188 registry value to desired time in seconds. Error %1: %2

Message

Message Queuing failed to send a message due to low memory. Message Queuing will retry to send the message. This event is logged at most once per %1 seconds. To change this setting, set \HKLM\Software\Microsoft\MSMQ\Parameters\Event2189 registry value to desired time in seconds.

Message

Message Queuing could not complete SSL negotiation with the remote computer. It is possible that the server certificate is not properly installed, or that remote computer is not listening on port 443 (SSL). This event is logged at most once per %1 seconds. To change this setting, set \HKLM\Software\Microsoft\MSMQ\Parameters\Event2190 registry value to desired time in seconds.

Message

Message Queuing could not validate server certificate in HTTPS scenario because the certificate was found in disallowed store. This means the certificate cannot be trusted. This event is logged at most once per %1 seconds. To change this setting, set \HKLM\Software\Microsoft\MSMQ\Parameters\Event2191 registry value to desired time in seconds.

Message

Message Queuing could not establish SSL connection with the recipient computer because a trust chain from the server certificate to a trusted Certificate Authority certificate could not be established. This event is logged at most once per %3 seconds. To change this setting, set \HKLM\Software\Microsoft\MSMQ\Parameters\Event2192 registry value to desired time in seconds. Error %1: %2

Message

Message Queuing could not establish SSL connection with the recipient computer because the computer name specified in the HTTP queue format name does not match the name of the recipient server certificate. This event is logged at most once per %1 seconds. To change this setting, set \HKLM\Software\Microsoft\MSMQ\Parameters\Event2193 registry value to desired time in seconds.

Message

Message Queuing could not authenticate a message sent to queue %1. The message was rejected because the queue only accepts authenticated messages. It is possible that sender did not sign the message, or signed it with a self-signed certificate. A negative arrival acknowledgement will be sent if requested by the sender. This event is logged at most once per %2 seconds. To change this setting, set \HKLM\Software\Microsoft\MSMQ\Parameters\Event2195 registry value to desired time in seconds.

Message

Message Queuing failed to verify digital signature of a message sent to queue %1. The message was rejected. A negative arrival acknowledgement will be sent if requested by the sender. This event is logged at most once per %2 seconds. To change this setting, set \HKLM\Software\Microsoft\MSMQ\Parameters\Event2196 registry value to desired time in seconds.

Message

Message Queuing failed to listen on the IPv6 protocol. Messages will not be accepted on IPv6.  If you want Message Queuing to accept messages on IPv6 protocol, please verify that the IPv6 protocol is installed and operational (Restarting the machine is required). Error %1: %2

Message

Message Queuing failed to listen on the IPv4 protocol. Messages will not be accepted on IPv4.  If you want Message Queuing to accept messages on IPv4 protocol, please verify that the IPv4 protocol is installed and operational (Restarting the machine is required). Error %1: %2

Message

The MSMQ VSS Writer object cannot be created. Error %1: %2.

Message

The MSMQ VSS Writer failed to register with the VSS. Please make sure that the VSS is running. Error %1: %2.

Message

Message Queuing will not be able to accept messages temporarily because system paged pool is low. During this period, machine quota will be set to 0. No manual intervention is required at this stage. Once memory utilization has normalized, Message Queuing will automatically resume accepting messages.

Message

Message Queuing will not be able to accept messages temporarily because system commit is low. During this period, machine quota will be set to 0. No manual intervention is required at this stage. Once memory utilization has normalized, Message Queuing will automatically resume accepting messages.

Message

The message could not be moved to deadletter queue %3. Check that queue exists and users have permissions to send. The message was moved to the system transactional dead letter queue. This event is logged at most once per %4 seconds. To change this setting, set \HKLM\Software\Microsoft\MSMQ\Parameters\Event2253 registry value to desired time in seconds. Error %1: %2

Message

The message could not be moved to deadletter queue %1. The deadletter queue is authenticated and the authenticity of the message could not be verified. The message will be moved to the system transactional dead letter queue. This event is logged at most once per %2 seconds. To change this setting, set \HKLM\Software\Microsoft\MSMQ\Parameters\Event2254 registry value to desired time in seconds.

Message

The message could not be moved to deadletter queue %1. Deadletter queues should not require privacy of messages. The message will be moved to the system transactional dead letter queue. This event is logged at most once per %2 seconds. To change this setting, set \HKLM\Software\Microsoft\MSMQ\Parameters\Event2255 registry value to desired time in seconds.

Message

The message could not be moved to deadletter queue %1. The deadletter queue needs to be transactional. The message will be moved to the system transactional dead letter queue. This event is logged at most once per %2 seconds. To change this setting, set \HKLM\Software\Microsoft\MSMQ\Parameters\Event2256 registry value to desired time in seconds.

Message

The Message Queuing service cannot start. The registry value '\HKLM\SOFTWARE\Microsoft\MSMQ\Parameters\%3' cannot be retrieved from the local Windows Registry. Error %1: %2

Message

The Message Queuing service cannot start. The registry value '\HKLM\SOFTWARE\Microsoft\MSMQ\Parameters\%3' cannot be written to the local Windows Registry. Error %1: %2

Message

The Message Queuing service is not online with Active Directory Domain Services. The MSMQ Configuration object (msmq) ID stored in the registry value '\HKLM\SOFTWARE\Microsoft\MSMQ\Parameters\MachineCache\QMId' was found under the computer name '%1' in Active Directory Domain Services. Please relocate this MSMQ Configuration object under the local computer name in Active Directory Domain Services. The service attempts to locate a matching MSMQ Configuration object every few minutes.

Message

The Message Queuing service is not online with Active Directory Domain Services, since the service properties cannot be retrieved or set. The service will attempt to retrieve and set its properties in a few minutes. Error %1: %2

Message

The Message Queuing service cannot start. The internal private queue '%3' cannot be initialized. If the problem persists, reinstall Message Queuing. Error %1: %2

Message

The Message Queuing service cannot start. The message store cannot be reloaded. Error %1: %2

Message

The Message Queuing service cannot start. The Active Directory Domain Services interface cannot be initialized. Error %1: %2

Message

The Message Queuing service cannot start. A connection with the Distributed Transaction Coordinator cannot be established. Error %1: %2

Message

The server cannot support the automatic recognition of sites and connected networks for down-level clients.  The problem might be caused by Active Directory Domain Services replication delay. Please restart MQDS service after replication completed.

Message

A multicast listener received a request with headers size exceeding the configured max size of '%1'. As a result, the request has been rejected. If this is a legitimate request, increase the default limit by creating a DWORD registry key HKLM\Software\Microsoft\MSMQ\Parameters\MaxSRMPHeaderSize and setting it to a higher value. This event is logged at most once per %2 seconds. To change this setting, set \HKLM\Software\Microsoft\MSMQ\Parameters\Event2049 registry value to desired time in seconds.

Message

A multicast listener received a request with content-length header size of '%1' that exceeds the configured max size of '%2'. As a result, the request has been rejected. If this is a legitimate request, increase the default limit by creating a DWORD registry key HKLM\Software\Microsoft\MSMQ\Parameters\MaxSRMPBodySize and setting it to a higher value. This event is logged at most once per %3 seconds. To change this setting, set \HKLM\Software\Microsoft\MSMQ\Parameters\Event2050 registry value to desired time in seconds.

Message

The Message Queuing service rejected a request since the deserialization hit the maximum allowed xml depth of '%1'. This limit can be increased by creating a DWORD registry key HKLM\Software\Microsoft\MSMQ\Parameters\MaxXmlDepth and setting it to a higher value. Note that increasing the value could expose the service to potential DoS attacks. Watch for event ID 2052 as a sign of such attacks. This event is logged at most once per %2 seconds. To change this setting, set \HKLM\Software\Microsoft\MSMQ\Parameters\Event2051 registry value to desired time in seconds.

Message

The request's deserialization led to a stack overflow exception in the Message Queuing service. This indicates a potential DoS attack and an excessively high value configured for the MaxXmlDepth DWORD registry value at HKLM\Software\Microsoft\MSMQ\Parameters\MaxXmlDepth. The current value set for MaxXmlDepth is '%1'. Consider setting it to a lower value to prevent the service from consuming excessive memory.

Message

The incoming sequences checkpoint file failed to initialize. The file MQInSeqs.lg1 or MQInSeqs.lg2 in the Msmq\Storage folder is corrupted or absent. Error %1: %2

Message

The Message Queuing service rejected an attempt to create a queue because the total number of queues has reached the maximum allowed limit of '%1' This limit can be increased by creating a DWORD registry key HKLM\Software\Microsoft\MSMQ\Parameters\QueueCountLimit and setting it to a higher value. Note that increasing the value could expose the service to potential DoS attacks. Watch for event ID 2055 as a sign of such attacks.

Message

The Message Queuing service cannot start. The local RPC interface cannot be initialized. Error %1: %2

Message

The transactions checkpoint file failed to initialize. The file MQTrans.lg1 or MQTrans.lg2 in the Msmq\Storage folder are corrupted or absent. Error %1: %2

Message

The list of Message Queuing servers with directory service functionality in the Windows registry is empty.

Message

The logger files cannot be initialized. The file QMLog in the Msmq\Storage folder is corrupted or absent. Error %1: %2

Message

The Message Queuing service cannot start. The checkpoint files cannot be recovered. To start the Message Queuing service without losing consistency, you must correct or recover corrupted checkpoint and log files. To start the service for emergency use (with a potential loss of data consistency), delete the files QMLog, MQTrans.lg1, MQTrans.lg2, MQInSeqs.lg1, and MQInSeqs.lg2 from the Msmq\Storage folder and add the DWORD registry key HKLM\Software\Microsoft\MSMQ\Parameters\LogDataCreated with a value of 0. Error %1: %2

Message

The Message Queuing service cannot start. The log file cannot be recovered. To start the Message Queuing service without losing consistency, you must correct or recover corrupted checkpoint and log files. To start the service for emergency use (with a potential loss of data consistency), delete the files QMLog, MQTrans.lg1, MQTrans.lg2, MQInSeqs.lg1, and MQInSeqs.lg2 from the Msmq\Storage folder and add the DWORD registry key HKLM\Software\Microsoft\MSMQ\Parameters\LogDataCreated with a value of 0. Error %1: %2

Message

The Message Queuing service cannot start. The message file '%3' and the log file '%4' cannot be reloaded. Error %1: %2

Message

The Message Queuing service cannot start because a queue is in an inconsistent state. For more information, see Microsoft Knowledge Base article 827493 at support.microsoft.com.

Message

The message file '%1' cannot be created. There is insufficient disk space or memory.

Message

Since an MSMQ 1.0 primary site controller owns the queue, you must manually delete the queue from the MSMQ 1.0 site (use MSMQ Explorer running on an applicable the site controller).

Message

The Message Queuing folder cannot be created.

Message

The Message Queuing registry values cannot be read (the registry is probably corrupted).

Message

Message Queuing was unable to create the msmq (MSMQ Configuration) object in Active Directory Domain Services. Error %1: %2

Message

Message Queuing was unable to load Mqupgrd.dll. Error %1: %2

Message

Message Queuing was unable to find the address of MqCreateMsmqObj in Mqupgrd.dll. Error %1: %2

Message

Message Queuing Setup cannot be completed.

Message

The Message Queuing service was unable to obtain the properties of the msmq (MSMQ Configuration) object from Active Directory Domain Services. This may be caused by an Active Directory Domain Services replication delay. Please wait several minutes and then restart the Message Queuing service. Error %1: %2

Message

This domain controller is not trusted for delegation. Therefore, the Message Queuing server cannot run. See Help and Support Center for information about how to enable the "This computer is trusted for delegation" property.

Message

The Message Queuing service failed to join the computer's domain '%3'. Error %1: %2

Message

Message Queuing objects cannot move automatically between domains (%1). You must either run the MoveTree utility or first uninstall Message Queuing and then reinstall it in the new domain.

Message

The properties of the queue %3 cannot be set. Copying the queue file %4 to the temporary file %5 returned error %1: %2

Message

The properties of the queue %3 cannot be set. Replacing the queue file %4 with the temporary file %5 returned error %1: %2

Message

The Microsoft Distributed Transaction Coordinator (DTC) failed. The Message Queuing service cannot continue. Please restart the DTC and the Message Queuing service.

Message

The computer object for this computer was not found in Active Directory Domain Services, possibly because of Active Directory Domain Services replication delays.

Message

The service cannot start due to insufficient disk space or memory.

Message

The service cannot start due to its failure to connect to its device driver.

Message

The Message Queuing directory service failed to update the directory service flag in Active Directory Domain Services at the end of the domain controller demotion process.

Message

The Message Queuing directory service failed to update the directory service flag in Active Directory Domain Services during the domain controller promotion process.

Message

Obsolete, kept for backward compatibility

Message

A multicast listener initialization failed. The file '%3' may be corrupted. Error %1: %2

Message

The Message Queuing service stopped monitoring the mapping folder %3. Error %1: %2

Message

The mapping file %3 was ignored. Its content cannot be read. Error %1: %2

Message

The mapping file %1 was ignored because it was improperly formatted.

Message

The queue cannot listen/bind to the multicast address %3. Error %1: %2

Message

The Message Queuing service will not join the %1 domain. An MSMQ Configuration (msmq) object exists in the new domain with an ID differing from the service ID. Please delete the MSMQ Configuration object in the new domain, restart the Message Queuing service, and log on again.

Message

The Message Queuing service cannot join the '%1' Windows NT 4.0 domain. The Active Directory Domain Services Integration subcomponent was therefore removed.

Message

The Message Queuing service resource cannot bind to the cluster IP address. This prevents the Message Queuing resource from coming online on this node. One possible reason is that the Message Queuing service running on the physical node was started before the computer became a member of the server cluster. As a result, the Message Queuing service running on the physical node listens on all IP addresses of the computer and prevents the Message Queuing resource from listening on the cluster IP address. To solve this problem, restart the Message Queuing service on the physical node. Error %1: %2

Message

The local computer is a Message Queuing routing server that formerly belonged to the '%1' domain and is now operating in workgroup mode. Other Message Queuing clients still regard this computer as a routing server and will try to route messages through this computer. To solve this problem, you need to manually delete the Message Queuing objects for this computer in Active Directory Domain Services. Please delete the following two objects: 1) The msmq object under the computer object of this computer in the Computers container in the Active Directory Users and Computers snap-in: 'CN=msmq,CN=%2,CN=computers,DC=%1,DC=...' 2) The MSMQ Settings object under the server object for this computer in the Active Directory Sites and Services snap-in: 'CN=MSMQ Settings,CN=%2,CN=Servers,CN=<SiteName>,CN=Sites,CN=Configuration,DC=...' You also need to uninstall Routing Support and Down-level Client Support by using Server Role Manager.

Message

Message Queuing failed to bind to port 1801. The port may already be bound to another process. Make sure that the port is free and try to start Message Queuing again. If this problem arises during setup, you must free the port and run setup again.

Message

Message Queuing Down-level Client Support cannot operate in mixed mode. Mixed mode is a transient mode in which Message Queuing deployment is in the middle of migration from MQIS (for MSMQ 1.0) to Active Directory Domain Services. In this mode, some sites are still Windows NT 4.0 sites and are mastered by the PEC and PSCs. Mixed mode might require creating/deleting/updating objects that belong to Windows NT 4.0 sites. These operations are not supported by Message Queuing Down-level Client Support. After completing the migration of all Windows NT 4.0 sites to Active Directory Domain Services (migration of the PEC and all PSCs in Windows NT 4.0 sites), Message Queuing will no longer be in mixed mode.

Message

The Message Queuing service rejects incoming messages when it is unable to check whether the sender is allowed access to the queue for sending messages. In this case, the queue affected is %1, but note that an event might not be issued every time this problem occurs.
 To perform this access check, Message Queuing needs access to the TokenGroupsGlobalAndUniversal attribute of the sender's user object. Only users with domain administration permissions can add members to the Windows Authorization Access Group, which is allowed access to the TokenGroupsGlobalAndUniversal attribute, in one of two ways:
 1) For best security practice, add only the computer accounts that need access to the TokenGroupsGlobalAndUniversal attribute to the Windows Authorization Access Group. The domain administrator will repeat this operation for other Message Queuing computers that require the permission, manually adding the relevant accounts to the Windows Authorization Access Group.
 2) As a less secure practice, add the Authenticated Users group to the Windows Authorization Access group. This grants every authenticated user, including the Message Queuing service on any computer, access to the TokenGroupsGlobalAndUniversal attribute for all users, and requires no further manual administration.

Message

The Message Queuing service cannot communicate with other computers, because the select API for socket failed. Error %1: %2

Message

Message Queuing Service failed to listen on both IPv4 and IPv6 protocol. Messages will not be accepted from the network through TCP/IP protocols.  Messages addressed to this machine using TCP/IP protocols will not arrive but will accumulate in sender's outgoing queues.   Please fix the TCP/IP protocols issue and restart the computer.

Message

The IP address %1 specified in the \HKLM\Software\Microsoft\MSMQ\Parameters\%2 registry value is not a valid IP address for this computer. The Message Queuing service will use the IP address %3!S! instead. Please remove this registry value or set it to one of the following valid IP addresses: %4!S!.

Message

The MSMQ VSS Writer failed to identify itself. Error %1: %2.

Message

Backup failed during event %3. Error %1: %2.

Message

Restore failed during event %3. Error %1: %2. This can happen if the restore directories under the MSMQ root directory cannot be created, or the restore root directory cannot be written in registry.

Message

The MSMQ VSS Writer failed to handle the restore located at '%3'. Error %1: %2.

Message

The restore located at '%1' is invalid. Invalid components are %2. Please verify all required files are present in the correct directory.