Event ID 2251 — Message Queuing System Resources

Event ID 2251 — Message Queuing System Resources

Updated: January 31, 2008

Applies To: Windows Server 2008

Disk, memory, and system resources are assigned to Message Queuing. If these resources become limited, Message Queuing may not function as expected.

Event Details

Product: Windows Operating System
ID: 2251
Source: MSMQ
Version: 6.0
Symbolic Name: EVENT_WARN_LOW_COMMIT
Message: Message Queuing will not be able to accept messages temporarily because system commit is high.

No manual intervention is required at this stage. Once memory utilization has normalized, Message Queuing will automatically resume accepting messages.

Resolve
Monitor low system resources

Common system resources are almost fully consumed. Message Queuing will not operate properly until system resources are freed up. For more information about managing Message Queuing system resources, see Resource Management in MSMQ Applications (http://go.microsoft.com/fwlink/?LinkId=107361).

We recommend that you monitor the number of messages on your computer and processs these messages. If this issue is persistent, you may have to rearchitect your solution.

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To monitor Message Queuing with Performance Monitor:

  1. Open a command prompt. To open a command prompt, click Start. In the search box, type cmd, and then press ENTER.
  2. At the command prompt, type Perfmon, and then press ENTER.
  3. In the console tree, under Monitoring Tools, click Performance Monitor.
  4. Click the green plus sign to add a monitor.
  5. On the Add counters tab, in the Counters section, click MSMQ Service.
  6. Select the appropriate counters that you need.

Verify

Verify that there is sufficient available memory and disk space.

To perform these procedures, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To verify that there is enough available memory:

  1. Open Task Manager. To open Task Manager, right-click an empty space on the taskbar, and then click Task Manager.
  2. Click the Performance tab.
  3. Verify the CPU Usage is not 100%.

To verify that there is enough available disk space:

  1. Open Windows Explorer.
  2. Right-click the drive where Message Queuing is located, and then click Properties.
  3. Verify that there is available Free space.

Related Management Information

Message Queuing System Resources

Message Queuing

Related:

Directory operation (om_create) failed with error . [ ] (12)

Details
Product: Exchange
Event ID: 2251
Source: MSExchangeMTA
Version: 6.5.6940.0
Component: Microsoft Exchange Message Transfer Agent
Message: Directory operation (om_create) failed with error <error code>. [<value> <value> <value> <value>] (12)
   
Explanation
There is no historical information available to provide assistance on this event.
   
User Action
The diagnostics logging levels of the message transfer agent (MTA) interface and interoperability categories should be increased to create interoperability logs. These logs are text logs that consist of the binary contents of communication among MTAs in different sites, and between MTA and client applications within a site. They are stored in the \Exchsrvr\Mtadata directory. The current log is always named Bf0.log. Prior logs are named Bfx.log, where x increases as the age of the log increases.
To help Microsoft Product Support Services determine the problem, create log files. For more information, see Microsoft Knowledge Base articles 163032 and 168906.
To create Ap*.log files, in the Diagnostics Logging tab of the Server Properties dialog box, select MSExchangeMTA, and then set the logging level of the Interoperability and Interface categories to Maximum.
To create Bf*.log files, set the logging level of the Application Protocol Data Unit (APDU) and X.400 service categories to Maximum.
Save all MTA log files (mtadata\*.log), event viewer output, and database files. Contact Microsoft Product Support Services for assistance.

Related: