Event ID 2168 — Message Queuing Clustering

Updated: December 3, 2008

Applies To: Windows Server 2008 R2

Clustering makes it possible for Message Queuing to operate as one instance across multiple operating systems so that Message Queuing can fail-over from one computer to another and provide high availability.

Event Details

Product: Windows Operating System
ID: 2168
Source: MSMQ
Version: 6.1
Message: <p>The Message Queuing service resource cannot bind to the cluster IP address. Error %1: %2</p>


Restart the MSMQ Service

The MSMQ Service on the physical node must be cluster aware. If the service is not cluster aware, this prevents the Message Queuing resource from coming online on this node.

This problem can occur if the MSMQ Service running on the physical node was started before the computer became a member of the server cluster. As a result, the MSMQ 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 perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

Restart the MSMQ Service

To restart the MSMQ Service:

  1. Open the Services snap-in. To open Services, click Start. In the search box, type services.msc, and then press ENTER.
  2. Right-click the Message Queuing service, and then click Restart. You must restart all the dependent services, as well.


You can use Failover Cluster Management to determine whether the Message Queuing cluster resource is online, or you can use the Cluster.exe tool to determine whether Windows Failover Clustering is installed and running.

Message Queuing Clustering

Message Queuing