The message has exceeded the queue quota.

Details
Product: BizTalk Server
Event ID: 7433
Source: BizTalk Server 3.0
Version: 3.0.4604.0
Message: The message has exceeded the queue quota.
   
Explanation
The sent message was dropped by destination because it exceeded the quota of the destination MSMQ queue.
   
User Action
Verify the quota property for the destination queue. Check for total size of the messages that are in the queue.

Related:

The message was purged before reaching its destination queue.

Details
Product: BizTalk Server
Event ID: 7431
Source: BizTalk Server 3.0
Version: 3.0.4604.0
Message: The message was purged before reaching its destination queue.
   
Explanation
The sent message was purged from MSMQ queue before the message could reach the destination application.
   
User Action
No user action required.

Related:

The MSMQT subservice failed to start because Windows MSMQ service is running on the computer.

Details
Product: BizTalk Server
Event ID: 7425
Source: BizTalk Server 3.0
Version: 3.0.4604.0
Message: The MSMQT subservice failed to start because Windows MSMQ service is running on the computer.
   
Explanation
MSMQ (Windows service) cannot run in parallel with BizTalk Server on the same machine unless both MSMQ and BizTalk Server are configured specifically to work together. The configuration requires MSMQ and BizTalk to run on a separate IP address.
   
User Action
If your computer does not require MSMQ service, use Computer Management to disable the Message Queueing service for Windows. If you require MSMQ and BizTalk Server to work side by side, refer to the BizTalk Server 2004 documentation for instructions on co

Related:

A BizTalk subservice has failed while executing a service request.Subservice: %1Service request: %2

Details
Product: BizTalk Server
Event ID: 5442
Source: BizTalk Server 3.0
Version: 3.0.4604.0
Message: A BizTalk subservice has failed while executing a service request.Subservice: %1Service request: %2
   
Explanation
The NT service is divided into sub-services: MSMQ/t, XLANG/s, EPM, Tracking. Each of those sub-services needs to be started when the NT service starts and stopped when the NT service stopped. This message indicates that an error occurred in the starting/s
   
User Action
Check other messages in the event log for a reason for the failure and the user actions to troubleshoot the error.

Related:

MSMQT dll has failed to initialize.

Details
Product: BizTalk Server
Event ID: 7456
Source: BizTalk Server 3.0
Version: 3.0.4604.0
Message: MSMQT dll has failed to initialize.
   
Explanation
A MSMQT networking component failed to initialize.
   
User Action
Ensure that MSMQ ports 1801 and 3627 are available for BizTalk Server 2004.

Related:

Poison Count is %1 for the message with RecordID %2. The message has reached or exceeded the configured poison threshold of %3. After the Microsoft Exchange Transport service restarted, the message was moved to the poison message queue.

Details
Product: Exchange
Event ID: 10001
Source: MSExchangeTransport
Version: 8.0
Symbolic Name: MessageEnqueuedToPoisonQueue
Message: Poison Count is %1 for the message with RecordID %2. The message has reached or exceeded the configured poison threshold of %3. After the Microsoft Exchange Transport service restarted, the message was moved to the poison message queue.
   
Explanation

This Warning event indicates that the transport process detected a message that could harm a Microsoft® Exchange environment. That message was moved to the poison message queue.

The poison message queue is a persistent queue that isolates messages that are detected as potentially fatal to a computer that is running Exchange Server 2007. This queue is typically empty. If no such messages exist in the poison message queue, the queue does not appear in the queue viewing interfaces. For information about how to manage queues, see Managing the Queue Database.

   
User Action

No user action is required. However, we recommend that you contact Microsoft Product Support to report the potentially harmful message that Exchange detected. For more information about how to contact support, visit the Microsoft Help and Support Web site.

Note   Do not delete the poison message from the poison queue. Microsoft Product Support Services may have to examine the message.

If you are not already doing so, consider running the tools that Microsoft Exchange offers to help administrators analyze and troubleshoot their Exchange environment. These tools can help you make sure that your configuration is in line with Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. Go to the Toolbox node of the Exchange Management Console to run these tools now. For more information about these tools, see Toolbox in the Exchange Server 2007 Help.

Related: