Microsoft-Windows-MSMQ

265 events across 3 channels

EventTitleChannelSample
1Message with ID MessageIDGUID\MessageIDIdentity was put into queue QueueName.End2EndN
1Message with ID MessageIDGUID\MessageIDIdentity was put into queueOperationalN
2Message receivedEnd2EndN
2Message receivedOperationalN
3Message sent over networkEnd2EndN
3Message sent over networkOperationalN
4Message came over networkEnd2EndN
4Message came over networkOperationalN
5Message with ID MessageIDGUID\MessageIDIdentity was sent to queue QueueName.End2EndN
5Message with ID MessageIDGUID\MessageIDIdentity was sent to queueOperationalN
2000The Message Queuing service cannot startOperationalN
2001The Message Queuing service cannot startOperationalN
2015The Message Queuing service is not online with Active Directory Domain ServicesOperationalN
2016The Message Queuing service is not online with Active Directory Domain Services, …OperationalN
2020The Message Queuing service cannot startOperationalN
2023The Message Queuing service cannot startOperationalN
2024The Message Queuing serivce performance counter data are not availableOperationalN
2028The Message Queuing service startedApplicationY
2028The Message Queuing service startedOperationalY
2035The Message Queuing service cannot startOperationalN
2043The Message Queuing service deleted message 'param1'OperationalN
2044The Message Queuing service has insufficient privileges to create audit log …OperationalN
2045The Message Queuing down-level client support service has insufficient …OperationalN
2047The Message Queuing service cannot startOperationalN
2048The server cannot support the automatic recognition of sites and connected …OperationalN
2049A multicast listener received a request with headers size exceeding the …OperationalN
2050A multicast listener received a request with content-length header size of …OperationalN
2051The Message Queuing service rejected a request since the deserialization hit the …OperationalN
2052The request's deserialization led to a stack overflow exception in the Message …OperationalN
2053The incoming sequences checkpoint file failed to initializeOperationalN
2054The Message Queuing service rejected an attempt to create a queue because the …OperationalN
2055The Message Queuing service session cleanup is taking longer than expectedOperationalN
2059The Message Queuing service cannot communicate with other computers, because the …OperationalN
2060The Message Queuing service is online with Active Directory Domain Services and …OperationalN
2061The Message Queuing service cannot startOperationalN
2064The transactions checkpoint file failed to initializeOperationalN
2068The list of Message Queuing servers with directory service functionality in the …OperationalN
2076The logger files cannot be initializedOperationalN
2078The Message Queuing service cannot startOperationalN
2079The Message Queuing service cannot startOperationalN
2083The Message Queuing service cannot startOperationalN
2084The Message Queuing service cannot start because a queue is in an inconsistent …OperationalN
2085The message file 'param1' cannot be createdOperationalN
2086The message file 'param1' was successfully createdOperationalN
2087The Client Access License (CAL) limit was reachedOperationalN
2095Since an MSMQ 1OperationalN
2096The Message Queuing folder cannot be createdOperationalN
2097The Message Queuing registry values cannot be read (the registry is probably …OperationalN
2116Message Queuing was unable to create the msmq (MSMQ Configuration) object in …OperationalN
2117Message Queuing was unable to load MqupgrdOperationalN
2118Message Queuing was unable to find the address of MqCreateMsmqObj in MqupgrdOperationalN
2119Message Queuing Setup cannot be completedOperationalN
2120The Message Queuing service was unable to obtain the properties of the msmq …OperationalN
2122This domain controller is not trusted for delegationOperationalN
2123The Message Queuing server cannot determine if the local domain controller is …OperationalN
2124The Message Queuing service failed to join the computer's domain 'param3'OperationalN
2125The Message Queuing service successfully joined the computer's domain 'param1'OperationalN
2126Message Queuing left the domain and is now operating in workgroup modeOperationalN
2127Message Queuing objects cannot move automatically between domains (param1)OperationalN
2134Message Queuing successfully moved to the param1 domainOperationalN
2135The computer belongs to the param1 domainOperationalN
2139Message Queuing detected a problem with the local domain controllerOperationalN
2140This server was unable to resolve the IP addresses of other routing serversOperationalN
2141The properties of the queue param3 cannot be setOperationalN
2142The properties of the queue param3 cannot be setOperationalN
2143The Microsoft Distributed Transaction Coordinator (DTC) failedOperationalN
2144There is an inconsistency between the actual network addresses and the addresses …OperationalN
2145The computer object for this computer was not found in Active Directory Domain …OperationalN
2147The service cannot start due to insufficient disk space or memoryOperationalN
2148The service cannot start due to its failure to connect to its device driverOperationalN
2149The Message Queuing directory service failed to update the directory service …OperationalN
2150The Message Queuing directory service failed to update the directory service …OperationalN
2151Obsolete, kept for backward compatibilityOperationalN
2152The Message Queuing directory service is not running as a local systemOperationalN
2153Message Queuing Down-level Client Support cannot startOperationalN
2154A multicast listener initialization failedOperationalN
2155The Message Queuing service stopped monitoring the mapping folderOperationalN
2156The mapping file param3 was ignoredOperationalN
2157The mapping of the URL param1 to the queue param2 was ignoredOperationalN
2158The mapping file param1 was ignored because it was improperly formattedOperationalN
2159Message Queuing Down-level Client Support startedOperationalN
2160The queue cannot listen/bind to the multicast addressOperationalN
2161The mapping of the URL param1 to the queue param2 is ignoredOperationalN
2162Message Queuing Down-level Client Support failed to create the MSMQ …OperationalN
2163The Message Queuing service stoppedOperationalN
2164The Message Queuing service will not join the param1 domainOperationalN
2165The sites where the computer resides cannot be resolvedOperationalN
2166The Message Queuing service cannot join the 'param1' Windows NT 4OperationalN
2167Message Queuing is operating in Hardened modeOperationalN
2168The Message Queuing service resource cannot bind to the cluster IP addressOperationalN
2169The local computer is a Message Queuing routing server that formerly belonged to …OperationalN
2170Message Queuing failed to bind to port 1801OperationalN
2171Message Queuing cannot bind to UDP port 3527OperationalN
2172The MsmqServices object is configured with weakened security to support MSMQ 1OperationalN
2173The MsmqServices object is configured with default securityOperationalN
2174Message Queuing Down-level Client Support cannot operate in mixed modeOperationalN
2175Message Queuing will use an encryption key with an effective length of 40 bits …OperationalN
2176Message Queuing found multiple IP addresses for the local computerOperationalN
2177The Message Queuing service rejects incoming messages when it is unable to check …OperationalN
2181Message Queuing cannot establish new connections to this computer because …OperationalN
2182Storage quota exceeded for MSMQ queueOperationalN
2183Machine MSMQ storage quota was exceeded or there is insufficient disk spaceOperationalN
2184Message Queuing could not resolve the name 'param1' to an IP addressOperationalN
2185A socket operation failed with errorOperationalN
2186Message Queuing could not establish connection to param1, because the connection …OperationalN
2187Message Queuing could not establish connection to param1, because connection was …OperationalN
2188Message Queuing could not access Active Directory Domain Services and failed to …OperationalN
2189Message Queuing failed to send a message due to low memoryOperationalN
2190Message Queuing could not complete SSL negotiation with the remote computerOperationalN
2191Message Queuing could not validate server certificate in HTTPS scenario because …OperationalN
2192Message Queuing could not establish SSL connection with the recipient computer …OperationalN
2193Message Queuing could not establish SSL connection with the recipient computer …OperationalN
2194The Message Queuing service cannot communicate with other computers, because the …OperationalN
2195Message Queuing could not authenticate a message sent to queueOperationalN
2196Message Queuing failed to verify digital signature of a message sent to queueOperationalN
2197Message Queuing failed to listen on the IPv6 protocolOperationalN
2198Message Queuing failed to listen on the IPv4 protocolOperationalN
2199Message Queuing Service failed to listen on both IPv4 and IPv6 protocolOperationalN
2220The IP address param1 specified in the …OperationalN
2221Message Queuing will use the IP addressOperationalN
2224The MSMQ VSS Writer object cannot be createdOperationalN
2225The MSMQ VSS Writer failed to register with the VSSOperationalN
2226The MSMQ VSS Writer failed to identify itselfOperationalN
2227Backup failed during eventOperationalN
2228Restore failed during eventOperationalN
2229The MSMQ VSS Writer failed to handle the restore located at 'param3'OperationalN
2230A backup (components: param1) was completed successfullyOperationalN
2231A restore was completed successfullyOperationalN
2232The restore located at 'param1' was handled successfullyOperationalN
2233The MSMQ VSS Writer is disabled through the registry settingOperationalN
2234The restore located at 'param1' is invalidOperationalN
2250Message Queuing will not be able to accept messages temporarily because system …OperationalN
2251Message Queuing will not be able to accept messages temporarily because system …OperationalN
2252Message Queuing is resuming accepting messages because the system memory usage …OperationalN
2253The message could not be moved to deadletter queueOperationalN
2254The message could not be moved to deadletter queueOperationalN
2255The message could not be moved to deadletter queueOperationalN
2256The message could not be moved to deadletter queueOperationalN
1073743848The Message Queuing serivce performance counter data are not available.OperationalN
1073743852The Message Queuing service started.OperationalY
1073743884The Message Queuing service is online with Active Directory Domain Services and …OperationalN
1073743910The message file 'param1' was successfully created.OperationalN
1073743949The Message Queuing service successfully joined the computer's domain 'param1'.OperationalN
1073743950Message Queuing left the domain and is now operating in workgroup mode.OperationalN
1073743958Message Queuing successfully moved to the param1 domain.OperationalN
1073743959The computer belongs to the param1 domain.OperationalN
1073743983Message Queuing Down-level Client Support started.OperationalN
1073743987The Message Queuing service stopped.OperationalN
1073743991Message Queuing is operating in Hardened mode.OperationalN
1073743996The MsmqServices object is configured with weakened security to support MSMQ 1.OperationalN
1073743997The MsmqServices object is configured with default security.OperationalN
1073744000Message Queuing found multiple IP addresses for the local computer.OperationalN
1073744045Message Queuing will use the IP address param1.OperationalN
1073744054A backup (components: param1) was completed successfully.OperationalN
1073744055A restore was completed successfully.OperationalN
1073744056The restore located at 'param1' was handled successfully.OperationalN
1073744057The MSMQ VSS Writer is disabled through the registry setting.OperationalN
1073744076Message Queuing is resuming accepting messages because the system memory usage …OperationalN
2147485691The Message Queuing service deleted message 'param1'.OperationalN
2147485692The Message Queuing service has insufficient privileges to create audit log …OperationalN
2147485693The Message Queuing down-level client support service has insufficient …OperationalN
2147485703The Message Queuing service session cleanup is taking longer than expected.OperationalN
2147485707The Message Queuing service cannot communicate with other computers, because the …OperationalN
2147485735The Client Access License (CAL) limit was reached.OperationalN
2147485771The Message Queuing server cannot determine if the local domain controller is …OperationalN
2147485787Message Queuing detected a problem with the local domain controller.OperationalN
2147485788This server was unable to resolve the IP addresses of other routing servers.OperationalN
2147485792There is an inconsistency between the actual network addresses and the addresses …OperationalN
2147485800The Message Queuing directory service is not running as a local system.OperationalN
2147485801Message Queuing Down-level Client Support cannot start.OperationalN
2147485805The mapping of the URL param1 to the queue param2 was ignored.OperationalN
2147485809The mapping of the URL param1 to the queue param2 is ignored.OperationalN
2147485810Message Queuing Down-level Client Support failed to create the MSMQ …OperationalN
2147485813The sites where the computer resides cannot be resolved.OperationalN
2147485819Message Queuing cannot bind to UDP port 3527.OperationalN
2147485823Message Queuing will use an encryption key with an effective length of 40 bits …OperationalN
2147485829Message Queuing cannot establish new connections to this computer because …OperationalN
2147485830Storage quota exceeded for MSMQ queue param1.OperationalN
2147485831Machine MSMQ storage quota was exceeded or there is insufficient disk space.OperationalN
2147485832Message Queuing could not resolve the name 'param1' to an IP address.OperationalN
2147485833A socket operation failed with error param1.OperationalN
2147485834Message Queuing could not establish connection to param1, because the connection …OperationalN
2147485835Message Queuing could not establish connection to param1, because connection was …OperationalN
2147485836Message Queuing could not access Active Directory Domain Services and failed to …OperationalN
2147485837Message Queuing failed to send a message due to low memory.OperationalN
2147485838Message Queuing could not complete SSL negotiation with the remote computer.OperationalN
2147485839Message Queuing could not validate server certificate in HTTPS scenario because …OperationalN
2147485840Message Queuing could not establish SSL connection with the recipient computer …OperationalN
2147485841Message Queuing could not establish SSL connection with the recipient computer …OperationalN
2147485843Message Queuing could not authenticate a message sent to queue param1.OperationalN
2147485844Message Queuing failed to verify digital signature of a message sent to queue …OperationalN
2147485845Message Queuing failed to listen on the IPv6 protocol.OperationalN
2147485846Message Queuing failed to listen on the IPv4 protocol.OperationalN
2147485872The MSMQ VSS Writer object cannot be created.OperationalN
2147485873The MSMQ VSS Writer failed to register with the VSS.OperationalN
2147485898Message Queuing will not be able to accept messages temporarily because system …OperationalN
2147485899Message Queuing will not be able to accept messages temporarily because system …OperationalN
2147485901The message could not be moved to deadletter queue param3.OperationalN
2147485902The message could not be moved to deadletter queue param1.OperationalN
2147485903The message could not be moved to deadletter queue param1.OperationalN
2147485904The message could not be moved to deadletter queue param1.OperationalN
3221227472The Message Queuing service cannot start.OperationalN
3221227473The Message Queuing service cannot start.OperationalN
3221227487The Message Queuing service is not online with Active Directory Domain Services.OperationalN
3221227488The Message Queuing service is not online with Active Directory Domain Services, …OperationalN
3221227492The Message Queuing service cannot start.OperationalN
3221227495The Message Queuing service cannot start.OperationalN
3221227507The Message Queuing service cannot start.OperationalN
3221227519The Message Queuing service cannot start.OperationalN
3221227520The server cannot support the automatic recognition of sites and connected …OperationalN
3221227521A multicast listener received a request with headers size exceeding the …OperationalN
3221227522A multicast listener received a request with content-length header size of '%1' …OperationalN
3221227523The Message Queuing service rejected a request since the deserialization hit the …OperationalN
3221227524The request's deserialization led to a stack overflow exception in the Message …OperationalN
3221227525The incoming sequences checkpoint file failed to initialize.OperationalN
3221227526The Message Queuing service rejected an attempt to create a queue because the …OperationalN
3221227533The Message Queuing service cannot start.OperationalN
3221227536The transactions checkpoint file failed to initialize.OperationalN
3221227540The list of Message Queuing servers with directory service functionality in the …OperationalN
3221227548The logger files cannot be initialized.OperationalN
3221227550The Message Queuing service cannot start.OperationalN
3221227551The Message Queuing service cannot start.OperationalN
3221227555The Message Queuing service cannot start.OperationalN
3221227556The Message Queuing service cannot start because a queue is in an inconsistent …OperationalN
3221227557The message file 'param1' cannot be created.OperationalN
3221227567Since an MSMQ 1.OperationalN
3221227568The Message Queuing folder cannot be created.OperationalN
3221227569The Message Queuing registry values cannot be read (the registry is probably …OperationalN
3221227588Message Queuing was unable to create the msmq (MSMQ Configuration) object in …OperationalN
3221227589Message Queuing was unable to load Mqupgrd.OperationalN
3221227590Message Queuing was unable to find the address of MqCreateMsmqObj in Mqupgrd.OperationalN
3221227591Message Queuing Setup cannot be completed.OperationalN
3221227592The Message Queuing service was unable to obtain the properties of the msmq …OperationalN
3221227594This domain controller is not trusted for delegation.OperationalN
3221227596The Message Queuing service failed to join the computer's domain 'param3'.OperationalN
3221227599Message Queuing objects cannot move automatically between domains.OperationalN
3221227613The properties of the queue param3 cannot be set.OperationalN
3221227614The properties of the queue param3 cannot be set.OperationalN
3221227615The Microsoft Distributed Transaction Coordinator (DTC) failed.OperationalN
3221227617The computer object for this computer was not found in Active Directory Domain …OperationalN
3221227619The service cannot start due to insufficient disk space or memory.OperationalN
3221227620The service cannot start due to its failure to connect to its device driver.OperationalN
3221227621The Message Queuing directory service failed to update the directory service …OperationalN
3221227622The Message Queuing directory service failed to update the directory service …OperationalN
3221227623Obsolete, kept for backward compatibilityOperationalN
3221227626A multicast listener initialization failed.OperationalN
3221227627The Message Queuing service stopped monitoring the mapping folder param3.OperationalN
3221227628The mapping file param3 was ignored.OperationalN
3221227630The mapping file param1 was ignored because it was improperly formatted.OperationalN
3221227632The queue cannot listen/bind to the multicast address param3.OperationalN
3221227636The Message Queuing service will not join the param1 domain.OperationalN
3221227638The Message Queuing service cannot join the 'param1' Windows NT 4.OperationalN
3221227640The Message Queuing service resource cannot bind to the cluster IP address.OperationalN
3221227641The local computer is a Message Queuing routing server that formerly belonged to …OperationalN
3221227642Message Queuing failed to bind to port 1801.OperationalN
3221227646Message Queuing Down-level Client Support cannot operate in mixed mode.OperationalN
3221227649The Message Queuing service rejects incoming messages when it is unable to check …OperationalN
3221227666The Message Queuing service cannot communicate with other computers, because the …OperationalN
3221227671Message Queuing Service failed to listen on both IPv4 and IPv6 protocol.OperationalN
3221227692The IP address param1 specified in the …OperationalN
3221227698The MSMQ VSS Writer failed to identify itself.OperationalN
3221227699Backup failed during event param3.OperationalN
3221227700Restore failed during event param3.OperationalN
3221227701The MSMQ VSS Writer failed to handle the restore located at 'param3'.OperationalN
3221227706The restore located at 'param1' is invalid.OperationalN

Event ID 1: Message with ID MessageIDGUID\MessageIDIdentity was put into queue QueueName.

#
Provider
Microsoft-Windows-MSMQ
Channel
End2End
Opcode
Info

Description

Message with ID MessageIDGUID\MessageIDIdentity was put into queue QueueName.

Message #

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

Fields #

NameDescription
MessageIDGUID GUID
MessageIDIdentity UInt32
QueueName UnicodeString

Event ID 1: Message with ID MessageIDGUID\MessageIDIdentity was put into queue

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational
Opcode
Info

Description

Message with ID \ was put into queue.

Fields #

NameDescription
MessageIDGUID GUID
MessageIDIdentity UInt32
QueueName UnicodeString

Event ID 2: Message received

#
Provider
Microsoft-Windows-MSMQ
Channel
End2End
Opcode
Info

Description

Message received.

Message #

Message received

Event ID 2: Message received

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational
Opcode
Info

Description

Message received.

Event ID 3: Message sent over network

#
Provider
Microsoft-Windows-MSMQ
Channel
End2End
Opcode
Info

Description

Message sent over network.

Message #

Message sent over network

Event ID 3: Message sent over network

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational
Opcode
Info

Description

Message sent over network.

Event ID 4: Message came over network

#
Provider
Microsoft-Windows-MSMQ
Channel
End2End
Opcode
Info

Description

Message came over network.

Message #

Message came over network

Event ID 4: Message came over network

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational
Opcode
Info

Description

Message came over network.

Event ID 5: Message with ID MessageIDGUID\MessageIDIdentity was sent to queue QueueName.

#
Provider
Microsoft-Windows-MSMQ
Channel
End2End
Opcode
Info

Description

Message with ID MessageIDGUID\MessageIDIdentity was sent to queue QueueName.

Message #

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

Fields #

NameDescription
MessageIDGUID GUID
MessageIDIdentity UInt32
QueueName UnicodeString

Event ID 5: Message with ID MessageIDGUID\MessageIDIdentity was sent to queue

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational
Opcode
Info

Description

Message with ID \ was sent to queue.

Fields #

NameDescription
MessageIDGUID GUID
MessageIDIdentity UInt32
QueueName UnicodeString

Event ID 2000: The Message Queuing service cannot start

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Fields #

NameDescription
param1 UnicodeString
param2 UnicodeString
param3 UnicodeString

Event ID 2001: The Message Queuing service cannot start

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Fields #

NameDescription
param1 UnicodeString
param2 UnicodeString
param3 UnicodeString

Event ID 2015: The Message Queuing service is not online with Active Directory Domain Services

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Fields #

NameDescription
param1 UnicodeString

Event ID 2016: The Message Queuing service is not online with Active Directory Domain Services, since the service properties cannot be retrieved or set

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Fields #

NameDescription
param1 UnicodeString
param2 UnicodeString

Event ID 2020: The Message Queuing service cannot start

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Fields #

NameDescription
param1 UnicodeString
param2 UnicodeString
param3 UnicodeString

Event ID 2023: The Message Queuing service cannot start

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Fields #

NameDescription
param1 UnicodeString
param2 UnicodeString

Event ID 2024: The Message Queuing serivce performance counter data are not available

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Fields #

NameDescription
param1 UnicodeString
param2 UnicodeString

Event ID 2028: The Message Queuing service started

#
Provider
Microsoft-Windows-MSMQ
Channel
Application
Level
Informational

Example Event #

{
  "system": {
    "provider": "Microsoft-Windows-MSMQ",
    "guid": "{ce18af71-5efd-4f5a-9bd5-635e34632f69}",
    "event_source_name": "MSMQ",
    "event_id": 2028,
    "version": 0,
    "level": 4,
    "task": 0,
    "opcode": 0,
    "keywords": 36028797018963968,
    "time_created": "2026-03-13T20:00:50.493281+00:00",
    "event_record_id": 3678,
    "correlation": {},
    "execution": {
      "process_id": 0,
      "thread_id": 0
    },
    "channel": "Application",
    "computer": "LAB-DC01.ludus.domain",
    "security": {
      "user_id": ""
    }
  },
  "event_data": {},
  "message": ""
}

Event ID 2028: The Message Queuing service started

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational
Level
4

Example Event #

{
  "system": {
    "provider": "Microsoft-Windows-MSMQ",
    "event_id": 2028,
    "level": 4,
    "task": 0,
    "opcode": 0,
    "time_created": "2026-03-13T20:00:50.4932819+00:00",
    "computer": "JD-DC01-2022.ludus.domain",
    "channel": "Application"
  },
  "event_data": {}
}

Event ID 2035: The Message Queuing service cannot start

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Fields #

NameDescription
param1 UnicodeString
param2 UnicodeString

Event ID 2043: The Message Queuing service deleted message 'param1'

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Fields #

NameDescription
param1 UnicodeString
param2 UnicodeString

Event ID 2044: The Message Queuing service has insufficient privileges to create audit log messages

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Event ID 2045: The Message Queuing down-level client support service has insufficient privileges to create audit log messages

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Event ID 2047: The Message Queuing service cannot start

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Fields #

NameDescription
param1 UnicodeString
param2 UnicodeString

Event ID 2048: The server cannot support the automatic recognition of sites and connected networks for down-level clients

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Event ID 2049: A multicast listener received a request with headers size exceeding the configured max size of 'MaxHeaderSize'

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Fields #

NameDescription
MaxHeaderSize UnicodeString
Frequency UnicodeString

Event ID 2050: A multicast listener received a request with content-length header size of 'ReqBodySize' that exceeds the configured max size of 'MaxBodySize'

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Fields #

NameDescription
ReqBodySize UnicodeString
MaxBodySize UnicodeString
Frequency UnicodeString

Event ID 2051: The Message Queuing service rejected a request since the deserialization hit the maximum allowed xml depth of 'MaxXmlDepth'

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Fields #

NameDescription
MaxXmlDepth UnicodeString
Frequency UnicodeString

Event ID 2052: The request's deserialization led to a stack overflow exception in the Message Queuing service

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Fields #

NameDescription
MaxXmlDepth UnicodeString

Event ID 2053: The incoming sequences checkpoint file failed to initialize

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Fields #

NameDescription
param1 UnicodeString
param2 UnicodeString

Event ID 2054: The Message Queuing service rejected an attempt to create a queue because the total number of queues has reached the maximum allowed limit of 'QueueCountLimit' This limit can be increased by creati...

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Fields #

NameDescription
QueueCountLimit UnicodeString

Event ID 2055: The Message Queuing service session cleanup is taking longer than expected

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Fields #

NameDescription
QueueCountLimit UnicodeString

Event ID 2059: The Message Queuing service cannot communicate with other computers, because the RPC interface cannot use the TCP/IP protocol

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Fields #

NameDescription
param1 UnicodeString
param2 UnicodeString

Event ID 2060: The Message Queuing service is online with Active Directory Domain Services and fully operational

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Event ID 2061: The Message Queuing service cannot start

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Fields #

NameDescription
param1 UnicodeString
param2 UnicodeString

Event ID 2064: The transactions checkpoint file failed to initialize

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Fields #

NameDescription
param1 UnicodeString
param2 UnicodeString

Event ID 2068: The list of Message Queuing servers with directory service functionality in the Windows registry is empty

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Event ID 2076: The logger files cannot be initialized

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Fields #

NameDescription
param1 UnicodeString
param2 UnicodeString

Event ID 2078: The Message Queuing service cannot start

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Fields #

NameDescription
param1 UnicodeString
param2 UnicodeString

Event ID 2079: The Message Queuing service cannot start

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Fields #

NameDescription
param1 UnicodeString
param2 UnicodeString

Event ID 2083: The Message Queuing service cannot start

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Fields #

NameDescription
param1 UnicodeString
param2 UnicodeString
param3 UnicodeString
param4 UnicodeString

Event ID 2084: The Message Queuing service cannot start because a queue is in an inconsistent state

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Event ID 2085: The message file 'param1' cannot be created

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Fields #

NameDescription
param1 UnicodeString

Event ID 2086: The message file 'param1' was successfully created

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Fields #

NameDescription
param1 UnicodeString

Event ID 2087: The Client Access License (CAL) limit was reached

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Fields #

NameDescription
param1 UnicodeString

Event ID 2095: Since an MSMQ 1

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Event ID 2096: The Message Queuing folder cannot be created

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Event ID 2097: The Message Queuing registry values cannot be read (the registry is probably corrupted)

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Event ID 2116: Message Queuing was unable to create the msmq (MSMQ Configuration) object in Active Directory Domain Services

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Fields #

NameDescription
param1 UnicodeString
param2 UnicodeString

Event ID 2117: Message Queuing was unable to load Mqupgrd

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Fields #

NameDescription
param1 UnicodeString
param2 UnicodeString

Event ID 2118: Message Queuing was unable to find the address of MqCreateMsmqObj in Mqupgrd

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Fields #

NameDescription
param1 UnicodeString
param2 UnicodeString

Event ID 2119: Message Queuing Setup cannot be completed

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Event ID 2120: The Message Queuing service was unable to obtain the properties of the msmq (MSMQ Configuration) object from Active Directory Domain Services

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Fields #

NameDescription
param1 UnicodeString
param2 UnicodeString

Event ID 2122: This domain controller is not trusted for delegation

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Event ID 2123: The Message Queuing server cannot determine if the local domain controller is trusted for delegation

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Event ID 2124: The Message Queuing service failed to join the computer's domain 'param3'

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Fields #

NameDescription
param1 UnicodeString
param2 UnicodeString
param3 UnicodeString

Event ID 2125: The Message Queuing service successfully joined the computer's domain 'param1'

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Fields #

NameDescription
param1 UnicodeString

Event ID 2126: Message Queuing left the domain and is now operating in workgroup mode

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Event ID 2127: Message Queuing objects cannot move automatically between domains (param1)

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Fields #

NameDescription
param1 UnicodeString

Event ID 2134: Message Queuing successfully moved to the param1 domain

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Fields #

NameDescription
param1 UnicodeString

Event ID 2135: The computer belongs to the param1 domain

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Fields #

NameDescription
param1 UnicodeString
param2 UnicodeString

Event ID 2139: Message Queuing detected a problem with the local domain controller

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Event ID 2140: This server was unable to resolve the IP addresses of other routing servers

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Event ID 2141: The properties of the queue param3 cannot be set

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Fields #

NameDescription
param1 UnicodeString
param2 UnicodeString
param3 UnicodeString
param4 UnicodeString
param5 UnicodeString

Event ID 2142: The properties of the queue param3 cannot be set

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Fields #

NameDescription
param1 UnicodeString
param2 UnicodeString
param3 UnicodeString
param4 UnicodeString
param5 UnicodeString

Event ID 2143: The Microsoft Distributed Transaction Coordinator (DTC) failed

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Event ID 2144: There is an inconsistency between the actual network addresses and the addresses that are listed on other Message Queuing servers for this computer

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Event ID 2145: The computer object for this computer was not found in Active Directory Domain Services, possibly because of Active Directory Domain Services replication delays

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Event ID 2147: The service cannot start due to insufficient disk space or memory

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Event ID 2148: The service cannot start due to its failure to connect to its device driver

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Event ID 2149: 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

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

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

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Event ID 2151: Obsolete, kept for backward compatibility

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Event ID 2152: The Message Queuing directory service is not running as a local system

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Event ID 2153: Message Queuing Down-level Client Support cannot start

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Event ID 2154: A multicast listener initialization failed

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Fields #

NameDescription
param1 UnicodeString
param2 UnicodeString
param3 UnicodeString

Event ID 2155: The Message Queuing service stopped monitoring the mapping folder

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Fields #

NameDescription
param1 UnicodeString
param2 UnicodeString
param3 UnicodeString

Event ID 2156: The mapping file param3 was ignored

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Fields #

NameDescription
param1 UnicodeString
param2 UnicodeString
param3 UnicodeString

Event ID 2157: The mapping of the URL param1 to the queue param2 was ignored

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Fields #

NameDescription
param1 UnicodeString
param2 UnicodeString

Event ID 2158: The mapping file param1 was ignored because it was improperly formatted

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Fields #

NameDescription
param1 UnicodeString

Event ID 2159: Message Queuing Down-level Client Support started

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Event ID 2160: The queue cannot listen/bind to the multicast address

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Fields #

NameDescription
param1 UnicodeString
param2 UnicodeString
param3 UnicodeString

Event ID 2161: The mapping of the URL param1 to the queue param2 is ignored

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Fields #

NameDescription
param1 UnicodeString
param2 UnicodeString

Event ID 2162: Message Queuing Down-level Client Support failed to create the MSMQ Configuration (msmq) object with a given GUID for computer

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Fields #

NameDescription
param1 UnicodeString

Event ID 2163: The Message Queuing service stopped

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Event ID 2164: The Message Queuing service will not join the param1 domain

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Fields #

NameDescription
param1 UnicodeString

Event ID 2165: The sites where the computer resides cannot be resolved

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Event ID 2166: The Message Queuing service cannot join the 'param1' Windows NT 4

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Fields #

NameDescription
param1 UnicodeString

Event ID 2167: Message Queuing is operating in Hardened mode

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Event ID 2168: The Message Queuing service resource cannot bind to the cluster IP address

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Fields #

NameDescription
param1 UnicodeString
param2 UnicodeString

Event ID 2169: The local computer is a Message Queuing routing server that formerly belonged to the 'param1' domain and is now operating in workgroup mode

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Fields #

NameDescription
param1 UnicodeString
param2 UnicodeString

Event ID 2170: Message Queuing failed to bind to port 1801

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Event ID 2171: Message Queuing cannot bind to UDP port 3527

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Event ID 2172: The MsmqServices object is configured with weakened security to support MSMQ 1

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Event ID 2173: The MsmqServices object is configured with default security

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Event ID 2174: Message Queuing Down-level Client Support cannot operate in mixed mode

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Event ID 2175: Message Queuing will use an encryption key with an effective length of 40 bits when sending messages encrypted with the RC2 encryption algorithm

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Event ID 2176: Message Queuing found multiple IP addresses for the local computer

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Fields #

NameDescription
param1 UnicodeString
param2 UnicodeString

Event ID 2177: 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

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Fields #

NameDescription
param1 UnicodeString

Event ID 2181: Message Queuing cannot establish new connections to this computer because connection limit was reached

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Fields #

NameDescription
param1 UnicodeString

Event ID 2182: Storage quota exceeded for MSMQ queue

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Fields #

NameDescription
param1 UnicodeString
param2 UnicodeString

Event ID 2183: Machine MSMQ storage quota was exceeded or there is insufficient disk space

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Fields #

NameDescription
param1 UnicodeString

Event ID 2184: Message Queuing could not resolve the name 'param1' to an IP address

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Fields #

NameDescription
param1 UnicodeString
param2 UnicodeString

Event ID 2185: A socket operation failed with error

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Fields #

NameDescription
param1 UnicodeString
param2 UnicodeString
param3 UnicodeString

Event ID 2186: Message Queuing could not establish connection to param1, because the connection limit for this computer was reached

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Fields #

NameDescription
param1 UnicodeString
param2 UnicodeString

Event ID 2187: Message Queuing could not establish connection to param1, because connection was refused by the recipient computer

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Fields #

NameDescription
param1 UnicodeString
param2 UnicodeString

Event ID 2188: Message Queuing could not access Active Directory Domain Services and failed to compute routing path for messages sent to queue

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Fields #

NameDescription
param1 UnicodeString
param2 UnicodeString
param3 UnicodeString
param4 UnicodeString

Event ID 2189: Message Queuing failed to send a message due to low memory

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Fields #

NameDescription
param1 UnicodeString

Event ID 2190: Message Queuing could not complete SSL negotiation with the remote computer

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Fields #

NameDescription
param1 UnicodeString

Event ID 2191: Message Queuing could not validate server certificate in HTTPS scenario because the certificate was found in disallowed store

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Fields #

NameDescription
param1 UnicodeString

Event ID 2192: 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

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Fields #

NameDescription
param1 UnicodeString
param2 UnicodeString
param3 UnicodeString

Event ID 2193: 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 cert...

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Fields #

NameDescription
param1 UnicodeString

Event ID 2194: The Message Queuing service cannot communicate with other computers, because the select API for socket failed

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Fields #

NameDescription
param1 UnicodeString
param2 UnicodeString

Event ID 2195: Message Queuing could not authenticate a message sent to queue

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Fields #

NameDescription
param1 UnicodeString
param2 UnicodeString

Event ID 2196: Message Queuing failed to verify digital signature of a message sent to queue

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Fields #

NameDescription
param1 UnicodeString
param2 UnicodeString

Event ID 2197: Message Queuing failed to listen on the IPv6 protocol

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Fields #

NameDescription
param1 UnicodeString
param2 UnicodeString

Event ID 2198: Message Queuing failed to listen on the IPv4 protocol

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Fields #

NameDescription
param1 UnicodeString
param2 UnicodeString

Event ID 2199: Message Queuing Service failed to listen on both IPv4 and IPv6 protocol

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Event ID 2220: The IP address param1 specified in the \HKLM\Software\Microsoft\MSMQ\Parameters\param2 registry value is not a valid IP address for this computer

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Fields #

NameDescription
param1 UnicodeString
param2 UnicodeString
param3 UnicodeString
param4 UnicodeString

Event ID 2221: Message Queuing will use the IP address

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Fields #

NameDescription
param1 UnicodeString
param2 UnicodeString
param3 UnicodeString

Event ID 2224: The MSMQ VSS Writer object cannot be created

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Fields #

NameDescription
param1 UnicodeString
param2 UnicodeString

Event ID 2225: The MSMQ VSS Writer failed to register with the VSS

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Fields #

NameDescription
param1 UnicodeString
param2 UnicodeString

Event ID 2226: The MSMQ VSS Writer failed to identify itself

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Fields #

NameDescription
param1 UnicodeString
param2 UnicodeString

Event ID 2227: Backup failed during event

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Fields #

NameDescription
param1 UnicodeString
param2 UnicodeString
param3 UnicodeString

Event ID 2228: Restore failed during event

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Fields #

NameDescription
param1 UnicodeString
param2 UnicodeString
param3 UnicodeString

Event ID 2229: The MSMQ VSS Writer failed to handle the restore located at 'param3'

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Fields #

NameDescription
param1 UnicodeString
param2 UnicodeString
param3 UnicodeString

Event ID 2230: A backup (components: param1) was completed successfully

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Fields #

NameDescription
param1 UnicodeString

Event ID 2231: A restore was completed successfully

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Event ID 2232: The restore located at 'param1' was handled successfully

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Fields #

NameDescription
param1 UnicodeString
param2 UnicodeString

Event ID 2233: The MSMQ VSS Writer is disabled through the registry setting

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Event ID 2234: The restore located at 'param1' is invalid

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Fields #

NameDescription
param1 UnicodeString
param2 UnicodeString

Event ID 2250: Message Queuing will not be able to accept messages temporarily because system paged pool is low

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Event ID 2251: Message Queuing will not be able to accept messages temporarily because system commit is low

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Event ID 2252: Message Queuing is resuming accepting messages because the system memory usage has normalized

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Event ID 2253: The message could not be moved to deadletter queue

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Fields #

NameDescription
param1 UnicodeString
param2 UnicodeString
param3 UnicodeString
param4 UnicodeString

Event ID 2254: The message could not be moved to deadletter queue

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Fields #

NameDescription
param1 UnicodeString
param2 UnicodeString

Event ID 2255: The message could not be moved to deadletter queue

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Fields #

NameDescription
param1 UnicodeString
param2 UnicodeString

Event ID 2256: The message could not be moved to deadletter queue

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Fields #

NameDescription
param1 UnicodeString
param2 UnicodeString

Event ID 1073743848: The Message Queuing serivce performance counter data are not available.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

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

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

Fields #

NameDescription
param1
param2

Event ID 1073743852: The Message Queuing service started.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational
Level
4

Description

The Message Queuing service started.

Message #

The Message Queuing service started.

Example Event #

{
  "system": {
    "provider": "Microsoft-Windows-MSMQ",
    "event_id": 2028,
    "level": 4,
    "task": 0,
    "opcode": 0,
    "time_created": "2026-03-13T20:00:50.4932819+00:00",
    "computer": "JD-DC01-2022.ludus.domain",
    "channel": "Application"
  },
  "event_data": {}
}

Event ID 1073743884: The Message Queuing service is online with Active Directory Domain Services and fully operational.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

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.

Event ID 1073743910: The message file 'param1' was successfully created.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

The message file 'param1' was successfully created.

Message #

The message file '%1' was successfully created.

Fields #

NameDescription
param1

Event ID 1073743949: The Message Queuing service successfully joined the computer's domain 'param1'.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

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

Message #

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

Fields #

NameDescription
param1

Event ID 1073743950: Message Queuing left the domain and is now operating in workgroup mode.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

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.

Event ID 1073743958: Message Queuing successfully moved to the param1 domain.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

Message Queuing successfully moved to the domain.

Message #

Message Queuing successfully moved to the %1 domain.

Fields #

NameDescription
param1

Event ID 1073743959: The computer belongs to the param1 domain.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

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.

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.

Fields #

NameDescription
param1
param2

Event ID 1073743983: Message Queuing Down-level Client Support started.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

Message Queuing Down-level Client Support started.

Message #

Message Queuing Down-level Client Support started.

Event ID 1073743987: The Message Queuing service stopped.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

The Message Queuing service stopped.

Message #

The Message Queuing service stopped.

Event ID 1073743991: Message Queuing is operating in Hardened mode.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

Message Queuing is operating in Hardened mode.

Message #

Message Queuing is operating in Hardened mode.

Event ID 1073743996: The MsmqServices object is configured with weakened security to support MSMQ 1.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

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

Event ID 1073743997: The MsmqServices object is configured with default security.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

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.

Event ID 1073744000: Message Queuing found multiple IP addresses for the local computer.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

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.

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

Fields #

NameDescription
param1
param2

Event ID 1073744045: Message Queuing will use the IP address param1.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

Message Queuing will use the IP address . To use a different IP address, set the \HKLM\Software\Microsoft\MSMQ\Parameters\ registry value to one of the following valid IP addresses: !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!.

Fields #

NameDescription
param1
param2
param3

Event ID 1073744054: A backup (components: param1) was completed successfully.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

A backup (components: ) was completed successfully.

Message #

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

Fields #

NameDescription
param1

Event ID 1073744055: A restore was completed successfully.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

A restore was completed successfully.

Message #

A restore was completed successfully.

Event ID 1073744056: The restore located at 'param1' was handled successfully.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

The restore located at 'param1' was handled successfully. Restored components are param2.

Message #

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

Fields #

NameDescription
param1
param2

Event ID 1073744057: The MSMQ VSS Writer is disabled through the registry setting.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

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 #

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.

Event ID 1073744076: Message Queuing is resuming accepting messages because the system memory usage has normalized.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

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.

Event ID 2147485691: The Message Queuing service deleted message 'param1'.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

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 '%1'. The message cannot be restored because the queue '%2' does not exist.

Fields #

NameDescription
param1
param2

Event ID 2147485692: The Message Queuing service has insufficient privileges to create audit log messages.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

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.

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

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

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.

Event ID 2147485703: The Message Queuing service session cleanup is taking longer than expected.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

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.

Event ID 2147485707: The Message Queuing service cannot communicate with other computers, because the RPC interface cannot use the TCP/IP protocol.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

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

Message #

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

Fields #

NameDescription
param1
param2

Event ID 2147485735: The Client Access License (CAL) limit was reached.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

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.

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.

Fields #

NameDescription
param1

Event ID 2147485771: The Message Queuing server cannot determine if the local domain controller is trusted for delegation.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

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.

Event ID 2147485787: Message Queuing detected a problem with the local domain controller.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

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 #

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.

Event ID 2147485788: This server was unable to resolve the IP addresses of other routing servers.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

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.

Event ID 2147485792: There is an inconsistency between the actual network addresses and the addresses that are listed on other Message Queuing servers for this computer.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

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 #

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.

Event ID 2147485800: The Message Queuing directory service is not running as a local system.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

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.

Event ID 2147485801: Message Queuing Down-level Client Support cannot start.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

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 #

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.

Event ID 2147485805: The mapping of the URL param1 to the queue param2 was ignored.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

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

Message #

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

Fields #

NameDescription
param1
param2

Event ID 2147485809: The mapping of the URL param1 to the queue param2 is ignored.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

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

Message #

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

Fields #

NameDescription
param1
param2

Event ID 2147485810: Message Queuing Down-level Client Support failed to create the MSMQ Configuration (msmq) object with a given GUID for computer param1.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

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.

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.

Fields #

NameDescription
param1

Event ID 2147485813: The sites where the computer resides cannot be resolved.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

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 #

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.

Event ID 2147485819: Message Queuing cannot bind to UDP port 3527.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

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

Event ID 2147485823: Message Queuing will use an encryption key with an effective length of 40 bits when sending messages encrypted with the RC2 encryption algorithm.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

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

Event ID 2147485829: Message Queuing cannot establish new connections to this computer because connection limit was reached.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

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.

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.

Fields #

NameDescription
param1

Event ID 2147485830: Storage quota exceeded for MSMQ queue param1.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

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.

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.

Fields #

NameDescription
param1
param2

Event ID 2147485831: Machine MSMQ storage quota was exceeded or there is insufficient disk space.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

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.

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.

Fields #

NameDescription
param1

Event ID 2147485832: Message Queuing could not resolve the name 'param1' to an IP address.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

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.

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.

Fields #

NameDescription
param1
param2

Event ID 2147485833: A socket operation failed with error param1.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

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.

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.

Fields #

NameDescription
param1
param2
param3

Event ID 2147485834: Message Queuing could not establish connection to param1, because the connection limit for this computer was reached.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

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.

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.

Fields #

NameDescription
param1
param2

Event ID 2147485835: Message Queuing could not establish connection to param1, because connection was refused by the recipient computer.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

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.

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.

Fields #

NameDescription
param1
param2

Event ID 2147485836: Message Queuing could not access Active Directory Domain Services and failed to compute routing path for messages sent to queue param3.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

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

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

Fields #

NameDescription
param1
param2
param3
param4

Event ID 2147485837: Message Queuing failed to send a message due to low memory.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

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.

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.

Fields #

NameDescription
param1

Event ID 2147485838: Message Queuing could not complete SSL negotiation with the remote computer.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

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.

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.

Fields #

NameDescription
param1

Event ID 2147485839: Message Queuing could not validate server certificate in HTTPS scenario because the certificate was found in disallowed store.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

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.

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.

Fields #

NameDescription
param1

Event ID 2147485840: Message Queuing could not establish SSL connection with the recipient computer because a trust chain from the server certificate to a trusted Certi...

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

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

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

Fields #

NameDescription
param1
param2
param3

Event ID 2147485841: Message Queuing could not establish SSL connection with the recipient computer because the computer name specified in the HTTP queue format name do...

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

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.

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.

Fields #

NameDescription
param1

Event ID 2147485843: Message Queuing could not authenticate a message sent to queue param1.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

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.

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.

Fields #

NameDescription
param1
param2

Event ID 2147485844: Message Queuing failed to verify digital signature of a message sent to queue param1.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

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.

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.

Fields #

NameDescription
param1
param2

Event ID 2147485845: Message Queuing failed to listen on the IPv6 protocol.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

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

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

Fields #

NameDescription
param1
param2

Event ID 2147485846: Message Queuing failed to listen on the IPv4 protocol.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

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

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

Fields #

NameDescription
param1
param2

Event ID 2147485872: The MSMQ VSS Writer object cannot be created.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

The MSMQ VSS Writer object cannot be created. Error : .

Message #

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

Fields #

NameDescription
param1
param2

Event ID 2147485873: The MSMQ VSS Writer failed to register with the VSS.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

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

Message #

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

Fields #

NameDescription
param1
param2

Event ID 2147485898: Message Queuing will not be able to accept messages temporarily because system paged pool is low.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

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

Event ID 2147485899: Message Queuing will not be able to accept messages temporarily because system commit is low.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

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 #

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.

Event ID 2147485901: The message could not be moved to deadletter queue param3.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

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

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

Fields #

NameDescription
param1
param2
param3
param4

Event ID 2147485902: The message could not be moved to deadletter queue param1.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

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.

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.

Fields #

NameDescription
param1
param2

Event ID 2147485903: The message could not be moved to deadletter queue param1.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

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.

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.

Fields #

NameDescription
param1
param2

Event ID 2147485904: The message could not be moved to deadletter queue param1.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

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.

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.

Fields #

NameDescription
param1
param2

Event ID 3221227472: The Message Queuing service cannot start.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

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

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

Fields #

NameDescription
param1
param2
param3

Event ID 3221227473: The Message Queuing service cannot start.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

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

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

Fields #

NameDescription
param1
param2
param3

Event ID 3221227487: The Message Queuing service is not online with Active Directory Domain Services.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

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.

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.

Fields #

NameDescription
param1

Event ID 3221227488: The Message Queuing service is not online with Active Directory Domain Services, since the service properties cannot be retrieved or set.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

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

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

Fields #

NameDescription
param1
param2

Event ID 3221227492: The Message Queuing service cannot start.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

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 '%3' cannot be initialized. If the problem persists, reinstall Message Queuing. Error %1: %2

Fields #

NameDescription
param1
param2
param3

Event ID 3221227495: The Message Queuing service cannot start.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

The Message Queuing service cannot start. The message store cannot be reloaded. Error.

Message #

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

Fields #

NameDescription
param1
param2

Event ID 3221227507: The Message Queuing service cannot start.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

The Message Queuing service cannot start. The Active Directory Domain Services interface cannot be initialized. Error.

Message #

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

Fields #

NameDescription
param1
param2

Event ID 3221227519: The Message Queuing service cannot start.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

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

Message #

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

Fields #

NameDescription
param1
param2

Event ID 3221227520: The server cannot support the automatic recognition of sites and connected networks for down-level clients.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

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 #

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.

Event ID 3221227521: A multicast listener received a request with headers size exceeding the configured max size of '%1'.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

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.

Event ID 3221227522: A multicast listener received a request with content-length header size of '%1' that exceeds the configured max size of '%2'.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

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.

Event ID 3221227523: The Message Queuing service rejected a request since the deserialization hit the maximum allowed xml depth of '%1'.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

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.

Event ID 3221227524: The request's deserialization led to a stack overflow exception in the Message Queuing service.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

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.

Event ID 3221227525: The incoming sequences checkpoint file failed to initialize.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

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.

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

Fields #

NameDescription
param1
param2

Event ID 3221227526: 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' ...

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

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.

Event ID 3221227533: The Message Queuing service cannot start.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

The Message Queuing service cannot start. The local RPC interface cannot be initialized. Error.

Message #

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

Fields #

NameDescription
param1
param2

Event ID 3221227536: The transactions checkpoint file failed to initialize.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

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.

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

Fields #

NameDescription
param1
param2

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

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

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.

Event ID 3221227548: The logger files cannot be initialized.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

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

Message #

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

Fields #

NameDescription
param1
param2

Event ID 3221227550: The Message Queuing service cannot start.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

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

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

Fields #

NameDescription
param1
param2

Event ID 3221227551: The Message Queuing service cannot start.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

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

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

Fields #

NameDescription
param1
param2

Event ID 3221227555: The Message Queuing service cannot start.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

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 '%3' and the log file '%4' cannot be reloaded. Error %1: %2

Fields #

NameDescription
param1
param2
param3
param4

Event ID 3221227556: The Message Queuing service cannot start because a queue is in an inconsistent state.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

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.

Event ID 3221227557: The message file 'param1' cannot be created.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

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

Message #

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

Fields #

NameDescription
param1

Event ID 3221227567: Since an MSMQ 1.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

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

Event ID 3221227568: The Message Queuing folder cannot be created.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

The Message Queuing folder cannot be created.

Message #

The Message Queuing folder cannot be created.

Event ID 3221227569: The Message Queuing registry values cannot be read (the registry is probably corrupted).

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

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

Event ID 3221227588: Message Queuing was unable to create the msmq (MSMQ Configuration) object in Active Directory Domain Services.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

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

Message #

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

Fields #

NameDescription
param1
param2

Event ID 3221227589: Message Queuing was unable to load Mqupgrd.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

Message Queuing was unable to load Mqupgrd.dll. Error.

Message #

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

Fields #

NameDescription
param1
param2

Event ID 3221227590: Message Queuing was unable to find the address of MqCreateMsmqObj in Mqupgrd.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

Message Queuing was unable to find the address of MqCreateMsmqObj in Mqupgrd.dll. Error.

Message #

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

Fields #

NameDescription
param1
param2

Event ID 3221227591: Message Queuing Setup cannot be completed.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

Message Queuing Setup cannot be completed.

Message #

Message Queuing Setup cannot be completed.

Event ID 3221227592: The Message Queuing service was unable to obtain the properties of the msmq (MSMQ Configuration) object from Active Directory Domain Services.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

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

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

Fields #

NameDescription
param1
param2

Event ID 3221227594: This domain controller is not trusted for delegation.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

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 #

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.

Event ID 3221227596: The Message Queuing service failed to join the computer's domain 'param3'.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

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 '%3'. Error %1: %2

Fields #

NameDescription
param1
param2
param3

Event ID 3221227599: Message Queuing objects cannot move automatically between domains.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

Message Queuing objects cannot move automatically between domains (). 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 (%1). You must either run the MoveTree utility or first uninstall Message Queuing and then reinstall it in the new domain.

Fields #

NameDescription
param1

Event ID 3221227613: The properties of the queue param3 cannot be set.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

The properties of the queue cannot be set. Copying the queue file to the temporary file returned error.

Message #

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

Fields #

NameDescription
param1
param2
param3
param4
param5

Event ID 3221227614: The properties of the queue param3 cannot be set.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

The properties of the queue cannot be set. Replacing the queue file with the temporary file returned error.

Message #

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

Fields #

NameDescription
param1
param2
param3
param4
param5

Event ID 3221227615: The Microsoft Distributed Transaction Coordinator (DTC) failed.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

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.

Event ID 3221227617: The computer object for this computer was not found in Active Directory Domain Services, possibly because of Active Directory Domain Services repli...

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

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.

Event ID 3221227619: The service cannot start due to insufficient disk space or memory.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

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

Message #

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

Event ID 3221227620: The service cannot start due to its failure to connect to its device driver.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

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.

Event ID 3221227621: The Message Queuing directory service failed to update the directory service flag in Active Directory Domain Services at the end of the domain cont...

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

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.

Event ID 3221227622: The Message Queuing directory service failed to update the directory service flag in Active Directory Domain Services during the domain controller ...

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

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.

Event ID 3221227623: Obsolete, kept for backward compatibility

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

Obsolete, kept for backward compatibility.

Message #

Obsolete, kept for backward compatibility

Event ID 3221227626: A multicast listener initialization failed.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

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

Message #

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

Fields #

NameDescription
param1
param2
param3

Event ID 3221227627: The Message Queuing service stopped monitoring the mapping folder param3.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

The Message Queuing service stopped monitoring the mapping folder . Error.

Message #

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

Fields #

NameDescription
param1
param2
param3

Event ID 3221227628: The mapping file param3 was ignored.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

The mapping file was ignored. Its content cannot be read. Error.

Message #

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

Fields #

NameDescription
param1
param2
param3

Event ID 3221227630: The mapping file param1 was ignored because it was improperly formatted.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

The mapping file was ignored because it was improperly formatted.

Message #

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

Fields #

NameDescription
param1

Event ID 3221227632: The queue cannot listen/bind to the multicast address param3.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

The queue cannot listen/bind to the multicast address . Error.

Message #

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

Fields #

NameDescription
param1
param2
param3

Event ID 3221227636: The Message Queuing service will not join the param1 domain.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

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.

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.

Fields #

NameDescription
param1

Event ID 3221227638: The Message Queuing service cannot join the 'param1' Windows NT 4.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

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 '%1' Windows NT 4.0 domain. The Active Directory Domain Services Integration subcomponent was therefore removed.

Fields #

NameDescription
param1

Event ID 3221227640: The Message Queuing service resource cannot bind to the cluster IP address.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

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

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

Fields #

NameDescription
param1
param2

Event ID 3221227641: The local computer is a Message Queuing routing server that formerly belonged to the 'param1' domain and is now operating in workgroup mode.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

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.

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.

Fields #

NameDescription
param1
param2

Event ID 3221227642: Message Queuing failed to bind to port 1801.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

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

Event ID 3221227646: Message Queuing Down-level Client Support cannot operate in mixed mode.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

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 #

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.

Event ID 3221227649: The Message Queuing service rejects incoming messages when it is unable to check whether the sender is allowed access to the queue for sending mess...

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

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.

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.

Fields #

NameDescription
param1

Event ID 3221227666: The Message Queuing service cannot communicate with other computers, because the select API for socket failed.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

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

Message #

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

Fields #

NameDescription
param1
param2

Event ID 3221227671: Message Queuing Service failed to listen on both IPv4 and IPv6 protocol.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

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 #

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.

Event ID 3221227692: The IP address param1 specified in the \HKLM\Software\Microsoft\MSMQ\Parameters\param2 registry value is not a valid IP address for this computer.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

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.

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

Fields #

NameDescription
param1
param2
param3
param4

Event ID 3221227698: The MSMQ VSS Writer failed to identify itself.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

The MSMQ VSS Writer failed to identify itself. Error : .

Message #

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

Fields #

NameDescription
param1
param2

Event ID 3221227699: Backup failed during event param3.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

Backup failed during event . Error : .

Message #

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

Fields #

NameDescription
param1
param2
param3

Event ID 3221227700: Restore failed during event param3.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

Restore failed during event . Error : . 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 #

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.

Fields #

NameDescription
param1
param2
param3

Event ID 3221227701: The MSMQ VSS Writer failed to handle the restore located at 'param3'.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

The MSMQ VSS Writer failed to handle the restore located at 'param3'. Error param1: param2.

Message #

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

Fields #

NameDescription
param1
param2
param3

Event ID 3221227706: The restore located at 'param1' is invalid.

#
Provider
Microsoft-Windows-MSMQ
Channel
Operational

Description

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

Message #

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

Fields #

NameDescription
param1
param2

Provenance

Where this provider's schema came from, and which Windows build it was observed on. Windows can change a provider's event schema between builds, so use this to judge whether it matches the build you collect from.

ETW provider GUID ce18af71-5efd-4f5a-9bd5-635e34632f69

Defined in mqutil.dll, which carries the event manifest.

Observed on:

  • WS2022-20348.4893, schema read from the registered manifest, binary version 10.0.20348.3207, captured 2026-06-02

Downloads