Event ID 2256 — Message Queuing Operation
Updated: December 3, 2008
Applies To: Windows Server 2008 R2
Message Queuing operation provides message authentication, message encryption, dead-letter queues, security settings, and other basic features. If Message Queuing has problems with any of these features, proper Message Queuing operation may suffer.
|Product:||Windows Operating System|
|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.|
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.
For more information about creating queues, see Create Queues (http://go.microsoft.com/fwlink/?LinkId=104735).
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:
- Open the Services snap-in. To open Services, click Start. In the search box, type services.msc, and then press ENTER.
- Locate the Message Queuing service, and confirm that the value in the Status column is Started.