| Event Id | 2256 |
| Source | MSMQ |
| Description | 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. |
| Event Information | According to Microsoft : Cause : This event is logged when the message could not be moved to deadletter queue. Resolution : Make the per-app dead-letter queue transactional or the messages being sent to it nontransactional The dead-letter queue that is specified in the event is nontransactional, but there are transactional messages trying to go there. To allow messages to go to the dead-letter queue, recreate the dead-letter queue as a transactional queue, or if you have control over the messages that are being sent to the queue, ensure that the messages are nontransactional. To recreate the dead-letter queue as a transactional queue, create a new transactional queue with all the same properties as the original dead-letter queue, but make the new queue transactional. Verify : Verify that the MSMQ Service is installed and running. To perform this procedure, you must have membership in Administrators , or you must have been delegated the appropriate authority. To verify that the MSMQ Service is installed and running:
|
| Reference Links | Event ID 2256 from MSMQ |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.