Microsoft-Windows-MSMQ-Events

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 {param1}: {param2}

Fields #

Description

The Message Queuing service started.

Message #

The Message Queuing service started.

Description

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

Message #

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

Description

The message file '{param1}' was successfully created.

Message #

The message file '{param1}' was successfully created.

Fields #

Description

The Message Queuing service successfully joined the computer's domain '{param1}'.

Message #

The Message Queuing service successfully joined the computer's domain '{param1}'.

Fields #

Description

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

Message #

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

Description

Message Queuing successfully moved to the {param1} domain.

Message #

Message Queuing successfully moved to the {param1} domain.

Fields #

Message #

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

Fields #

Description

Message Queuing Down-level Client Support started.

Message #

Message Queuing Down-level Client Support started.

Description

The Message Queuing service stopped.

Message #

The Message Queuing service stopped.

Description

Message Queuing is operating in Hardened mode.

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.

Description

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 #

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\{param1} registry value to one of the following valid IP addresses: {param2}.

Fields #

Description

Message Queuing Triggers started successfully.

Message #

Message Queuing Triggers started successfully.

Description

Message Queuing Triggers service stopped.

Message #

Message Queuing Triggers service stopped.

Description

The parameters of the rule {param1} with the ID {param2} are now valid. The rule was evaluated successfully; and the action defined by it was executed.

Message #

The parameters of the rule {param1} with the ID {param2} are now valid. The rule was evaluated successfully; and the action defined by it was executed.

Fields #

Description

The rules attached to the trigger {param1} with the ID {param2} are now valid. All the rules were evaluated successfully; and the actions defined by them were executed.

Message #

The rules attached to the trigger {param1} with the ID {param2} are now valid. All the rules were evaluated successfully; and the actions defined by them were executed.

Fields #

Message #

The Triggers service has been set to run under the Network Service account; but this setting will take effect only after the Triggers service is restarted.  If you want the Triggers service to continue to run under the Local Service account (the default for the previous version of Triggers); modify the logon settings  for the Triggers service in Computer Management.

Message #

Message Queuing will use the IP address {param1}. To use a different IP address; set the \HKLM\Software\Microsoft\MSMQ\Parameters\{param2} registry value to one of the following valid IP addresses: {param3}.

Fields #

Description

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

Message #

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

Description

The Message Queuing service deleted message '{param1}'. The message cannot be restored because the queue '{param2}' does not exist.

Message #

The Message Queuing service deleted message '{param1}'. The message cannot be restored because the queue '{param2}' does not exist.

Fields #

Description

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

Message #

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

Description

The Message Queuing down-level client support 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.

Description

The Message Queuing service cannot communicate with other computers; because the RPC interface cannot use the TCP/IP protocol. Error {param1}: {param2}.

Message #

The Message Queuing service cannot communicate with other computers; because the RPC interface cannot use the TCP/IP protocol. Error {param1}: {param2}

Fields #

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 {param1} seconds.

Fields #

Description

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 #

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.

Description

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

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.

Description

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 #

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.

Description

The mapping of the URL {param1} to the queue {param2} was ignored. This URL is already mapped to another queue.

Message #

The mapping of the URL {param1} to the queue {param2} was ignored. This URL is already mapped to another queue.

Fields #

Description

The mapping of the URL {param1} to the queue {param2} is ignored. This queue name is not a valid URL-style queue name.

Message #

The mapping of the URL {param1} to the queue {param2} is ignored. This queue name is not a valid URL-style queue name.

Fields #

Message #

Message Queuing Down-level Client Support failed to create the MSMQ Configuration (msmq) object with a given GUID for computer {param1}. 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.

Fields #

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 {param1} seconds. To change this setting; set \HKLM\Software\Microsoft\MSMQ\Parameters\Event2181 registry value to desired time in seconds.

Fields #

Message #

Storage quota exceeded for MSMQ queue {param1}. 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 {param2} seconds. To change this setting; set \HKLM\Software\Microsoft\MSMQ\Parameters\Event2182 registry value to desired time in seconds.

Fields #

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 {param1} seconds. To change this setting; set \HKLM\Software\Microsoft\MSMQ\Parameters\Event2183 registry value to desired time in seconds.

Fields #

Message #

Message Queuing could not resolve the name '{param1}' 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 {param2} seconds. To change this setting; set \HKLM\Software\Microsoft\MSMQ\Parameters\Event2184 registry value to desired time in seconds.

Fields #

Message #

A socket operation failed with error {param1}. Next hop address is {param2}. Message Queuing cannot send the message now; but it will retry to send the message. This event is logged at most once per {param3} seconds. To change this setting; set \HKLM\Software\Microsoft\MSMQ\Parameters\Event2185 registry value to desired time in seconds.

Fields #

Message #

Message Queuing could not establish connection to {param1}; 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 {param2} seconds. To change this setting; set \HKLM\Software\Microsoft\MSMQ\Parameters\Event2186 registry value to desired time in seconds.

Fields #

Message #

Message Queuing could not establish connection to {param1}; 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 {param2} seconds. To change this setting; set \HKLM\Software\Microsoft\MSMQ\Parameters\Event2187 registry value to desired time in seconds.

Fields #

Message #

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

Fields #

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 {param1} seconds. To change this setting; set \HKLM\Software\Microsoft\MSMQ\Parameters\Event2189 registry value to desired time in seconds.

Fields #

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 {param1} seconds. To change this setting; set \HKLM\Software\Microsoft\MSMQ\Parameters\Event2190 registry value to desired time in seconds.

Fields #

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 {param1} seconds. To change this setting; set \HKLM\Software\Microsoft\MSMQ\Parameters\Event2191 registry value to desired time in seconds.

Fields #

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 {param3} seconds. To change this setting; set \HKLM\Software\Microsoft\MSMQ\Parameters\Event2192 registry value to desired time in seconds. Error {param1}: {param2}

Fields #

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 {param1} seconds. To change this setting; set \HKLM\Software\Microsoft\MSMQ\Parameters\Event2193 registry value to desired time in seconds.

Fields #

Message #

Message Queuing could not authenticate a message sent to queue {param1}. 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 {param2} seconds. To change this setting; set \HKLM\Software\Microsoft\MSMQ\Parameters\Event2195 registry value to desired time in seconds.

Fields #

Message #

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

Fields #

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 {param1}: {param2}

Fields #

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 {param1}: {param2}

Fields #

Message #

The change for the Triggers service to run under the Network Service account will not take effect as long as the 'Allow service to interact with desktop' check box is selected.  To allow this change to take effect; clear the 'Allow service to interact with desktop' check box on the Log On page of the Properties dialog box for Message Queuing Triggers in Computer Management and restart the service.

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 {param3}. 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 {param4} seconds. To change this setting; set \HKLM\Software\Microsoft\MSMQ\Parameters\Event2253 registry value to desired time in seconds. Error {param1}: {param2}

Fields #

Message #

The message could not be moved to deadletter queue {param1}. 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 {param2} seconds. To change this setting; set \HKLM\Software\Microsoft\MSMQ\Parameters\Event2254 registry value to desired time in seconds.

Fields #

Message #

The message could not be moved to deadletter queue {param1}. 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 {param2} seconds. To change this setting; set \HKLM\Software\Microsoft\MSMQ\Parameters\Event2255 registry value to desired time in seconds.

Fields #

Message #

The message could not be moved to deadletter queue {param1}. 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 {param2} seconds. To change this setting; set \HKLM\Software\Microsoft\MSMQ\Parameters\Event2256 registry value to desired time in seconds.

Fields #

Description

The Message Queuing service cannot start. The registry value '\HKLM\SOFTWARE\Microsoft\MSMQ\Parameters\{param3}' cannot be retrieved from the local Windows Registry. Error {param1}: {param2}.

Message #

The Message Queuing service cannot start. The registry value '\HKLM\SOFTWARE\Microsoft\MSMQ\Parameters\{param3}' cannot be retrieved from the local Windows Registry. Error {param1}: {param2}

Fields #

Description

The Message Queuing service cannot start. The registry value '\HKLM\SOFTWARE\Microsoft\MSMQ\Parameters\{param3}' cannot be written to the local Windows Registry. Error {param1}: {param2}.

Message #

The Message Queuing service cannot start. The registry value '\HKLM\SOFTWARE\Microsoft\MSMQ\Parameters\{param3}' cannot be written to the local Windows Registry. Error {param1}: {param2}

Fields #

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 '{param1}' 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.

Fields #

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 {param1}: {param2}

Fields #

Description

The Message Queuing service cannot start. The internal private queue '{param3}' cannot be initialized. If the problem persists; reinstall Message Queuing. Error {param1}: {param2}.

Message #

The Message Queuing service cannot start. The internal private queue '{param3}' cannot be initialized. If the problem persists; reinstall Message Queuing. Error {param1}: {param2}

Fields #

Description

The Message Queuing service cannot start. The message store cannot be reloaded. Error {param1}: {param2}.

Message #

The Message Queuing service cannot start. The message store cannot be reloaded. Error {param1}: {param2}

Fields #

Description

The Message Queuing service cannot start. The Active Directory Domain Services interface cannot be initialized. Error {param1}: {param2}.

Message #

The Message Queuing service cannot start. The Active Directory Domain Services interface cannot be initialized. Error {param1}: {param2}

Fields #

Description

The Message Queuing service cannot start. A connection with the Distributed Transaction Coordinator cannot be established. Error {param1}: {param2}.

Message #

The Message Queuing service cannot start. A connection with the Distributed Transaction Coordinator cannot be established. Error {param1}: {param2}

Fields #

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.

Description

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 {param1}: {param2}.

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 {param1}: {param2}

Fields #

Description

The Message Queuing service cannot start. The local RPC interface cannot be initialized. Error {param1}: {param2}.

Message #

The Message Queuing service cannot start. The local RPC interface cannot be initialized. Error {param1}: {param2}

Fields #

Description

The transactions checkpoint file failed to initialize. The file MQTrans.lg1 or MQTrans.lg2 in the Msmq\Storage folder are corrupted or absent. Error {param1}: {param2}.

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 {param1}: {param2}

Fields #

Description

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

Message #

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

Description

The logger files cannot be initialized. The file QMLog in the Msmq\Storage folder is corrupted or absent. Error {param1}: {param2}.

Message #

The logger files cannot be initialized. The file QMLog in the Msmq\Storage folder is corrupted or absent. Error {param1}: {param2}

Fields #

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 {param1}: {param2}

Fields #

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 {param1}: {param2}

Fields #

Description

The Message Queuing service cannot start. The message file '{param3}' and the log file '{param4}' cannot be reloaded. Error {param1}: {param2}.

Message #

The Message Queuing service cannot start. The message file '{param3}' and the log file '{param4}' cannot be reloaded. Error {param1}: {param2}

Fields #

Description

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 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.

Description

The message file '{param1}' cannot be created. There is insufficient disk space or memory.

Message #

The message file '{param1}' cannot be created. There is insufficient disk space or memory.

Fields #

Description

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 #

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).

Description

The Message Queuing folder cannot be created.

Message #

The Message Queuing folder cannot be created.

Description

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

Message #

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

Description

Message Queuing was unable to create the msmq (MSMQ Configuration) object in Active Directory Domain Services. Error {param1}: {param2}.

Message #

Message Queuing was unable to create the msmq (MSMQ Configuration) object in Active Directory Domain Services. Error {param1}: {param2}

Fields #

Description

Message Queuing was unable to load Mqupgrd.dll. Error {param1}: {param2}.

Message #

Message Queuing was unable to load Mqupgrd.dll. Error {param1}: {param2}

Fields #

Description

Message Queuing was unable to find the address of MqCreateMsmqObj in Mqupgrd.dll. Error {param1}: {param2}.

Message #

Message Queuing was unable to find the address of MqCreateMsmqObj in Mqupgrd.dll. Error {param1}: {param2}

Fields #

Description

Message Queuing Setup cannot be completed.

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 {param1}: {param2}

Fields #

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.

Description

The Message Queuing service failed to join the computer's domain '{param3}'. Error {param1}: {param2}.

Message #

The Message Queuing service failed to join the computer's domain '{param3}'. Error {param1}: {param2}

Fields #

Description

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

Message #

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

Fields #

Description

The properties of the queue {param3} cannot be set. Copying the queue file {param4} to the temporary file {param5} returned error {param1}: {param2}.

Message #

The properties of the queue {param3} cannot be set. Copying the queue file {param4} to the temporary file {param5} returned error {param1}: {param2}

Fields #

Description

The properties of the queue {param3} cannot be set. Replacing the queue file {param4} with the temporary file {param5} returned error {param1}: {param2}.

Message #

The properties of the queue {param3} cannot be set. Replacing the queue file {param4} with the temporary file {param5} returned error {param1}: {param2}

Fields #

Description

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

Message #

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

Description

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 computer object for this computer was not found in Active Directory Domain Services; possibly because of Active Directory Domain Services replication delays.

Description

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

Message #

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

Description

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

Message #

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

Description

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 at the end of the domain controller demotion process.

Description

The Message Queuing directory service failed to update the directory service flag in Active Directory Domain Services during the domain controller promotion 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.

Description

Obsolete; kept for backward compatibility.

Message #

Obsolete; kept for backward compatibility

Description

A multicast listener initialization failed. The file '{param3}' may be corrupted. Error {param1}: {param2}.

Message #

A multicast listener initialization failed. The file '{param3}' may be corrupted. Error {param1}: {param2}

Fields #

Description

The Message Queuing service stopped monitoring the mapping folder {param3}. Error {param1}: {param2}.

Message #

The Message Queuing service stopped monitoring the mapping folder {param3}. Error {param1}: {param2}

Fields #

Description

The mapping file {param3} was ignored. Its content cannot be read. Error {param1}: {param2}.

Message #

The mapping file {param3} was ignored. Its content cannot be read. Error {param1}: {param2}

Fields #

Description

The mapping file {param1} was ignored because it was improperly formatted.

Message #

The mapping file {param1} was ignored because it was improperly formatted.

Fields #

Description

The queue cannot listen/bind to the multicast address {param3}. Error {param1}: {param2}.

Message #

The queue cannot listen/bind to the multicast address {param3}. Error {param1}: {param2}

Fields #

Message #

The Message Queuing service will not join the {param1} 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.

Fields #

Description

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

Message #

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

Fields #

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 {param1}: {param2}

Fields #

Message #

The local computer is a Message Queuing routing server that formerly belonged to the '{param1}' 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={param2};CN=computers;DC={param1};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={param2};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.

Fields #

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 {param1}; 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.

Fields #

Description

The Message Queuing service cannot communicate with other computers; because the select API for socket failed. Error {param1}: {param2}.

Message #

The Message Queuing service cannot communicate with other computers; because the select API for socket failed. Error {param1}: {param2}

Fields #

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.

Description

Message Queuing Triggers initialization failed. Error {param1}: {param2}.

Message #

Message Queuing Triggers initialization failed. Error {param1}: {param2}

Fields #

Message #

Message Queuing Triggers failed to create an instance of the Triggers Transactional object. As a result; no transactional retrieval triggers can be invoked. Mqgentr.dll may not be registered or may not exist in the %SystemRoot%\System32 folder. Error {param1}: {param2}

Fields #

Description

The trigger information cannot be retrieved from the trigger store in registry. At least one trigger is nonfunctional.

Message #

The trigger information cannot be retrieved from the trigger store in registry. At least one trigger is nonfunctional.

Description

The information for the attached rule cannot be retrieved from the trigger store for trigger {param1} (Trigger Name: {param2}). The trigger is nonfunctional.

Message #

The information for the attached rule cannot be retrieved from the trigger store for trigger {param1} (Trigger Name: {param2}). The trigger is nonfunctional.

Fields #

Message #

Opening the queue {param3} for peeking at or retrieving messages failed. Local users may not have been granted the Peek Message or Receive Message permission for this queue. The trigger {param4} is nonfunctional. Error {param1}: {param2}

Fields #

Message #

Opening an internal queue needed by the Triggers service failed. The account under which the Triggers service is running may not have permissions to open this queue; or the queue may have been deleted. To solve this problem; uninstall and reinstall the Triggers service. Error {param1}: {param2}

Fields #

Message #

An instance of a rule handler for the rule {param3} with the ID {param4} was not created. The rule cannot be evaluated and executed. The MSMQTriggerObjects.MSMQRuleHandler class may not be registered; or your System folder does not contain mqtrig.dll. Error {param1}: {param2}

Fields #

Message #

The action or a condition parameter for the rule {param3} with the ID {param4} was not parsed. The rule cannot be evaluated and executed. You can remove the rule entry from the Triggers registry and recreate it using local computer management. Error {param1}: {param2}

Fields #

Description

The action defined by the rule {param3} with the ID {param4} was not invoked. The COM object may not be registered; or the executable file may not exist in your path. Error {param1}: {param2}.

Message #

The action defined by the rule {param3} with the ID {param4} was not invoked. The COM object may not be registered; or the executable file may not exist in your path. Error {param1}: {param2}

Fields #

Message #

Rule evaluation or execution failed for the transactional trigger {param3} with the ID {param4}. A rule condition or action parameter may be invalid; or the COM object invoked may not be registered correctly. Error {param1}: {param2}

Fields #

Description

The queue {param1} was not found. It may have been deleted. The trigger {param2} associated with this queue is nonfunctional. Please use Computer Management to remove this trigger.

Message #

The queue {param1} was not found. It may have been deleted. The trigger {param2} associated with this queue is nonfunctional. Please use Computer Management to remove this trigger.

Fields #

Description

At least one of the required dependencies was not found. Please verify that MSMQ Triggers resources are dependent on Message Queue resources.

Message #

At least one of the required dependencies was not found. Please verify that MSMQ Triggers resources are dependent on Message Queue resources.

Description

Unable to update EventLog information in registry for '{param1}'.

Message #

Unable to update EventLog information in registry for '{param1}'.

Fields #

Description

The Triggers transactional component could not be registered in COM+. Error {param1}: {param2}.

Message #

The Triggers transactional component could not be registered in COM+. Error {param1}: {param2}

Fields #

Description

Retrieving messages from a queue located on a remote pre-Windows XP computer is not supported. All triggers associated with the queue {param1} are nonfunctional.

Message #

Retrieving messages from a queue located on a remote pre-Windows XP computer is not supported. All triggers associated with the queue {param1} are nonfunctional.

Fields #

Message #

The IP address {param1} specified in the \HKLM\Software\Microsoft\MSMQ\Parameters\{param2} registry value is not a valid IP address for this computer. The Message Queuing service will use the IP address {param3} instead. Please remove this registry value or set it to one of the following valid IP addresses: {param4}.

Fields #

Description

Message Queuing Triggers initialization failed to complete in the configured timeout..

Message #

Message Queuing Triggers initialization failed to complete in the configured timeout..