Event ID 2171 — Message Queuing Connectivity

Applies To: Windows Server 2008 R2

Message Queuing relies on network connectivity for much of its functionality. If network connectivity is lost or compromised, messages may not be sent or delivered.

Event Details

Resolve

Free UDP port 3527 and restart the MSMQ Service

The Message Queuing internal ping mechanism uses User Datagram Protocol (UDP) port 3527 to establish network connections. Another process may be using this port. Message Queuing can continue to operate without using this port, but connection times will not be optimal. To optimize the establishment of connections, free port 3527, and then restart the MSMQ Service.

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

Free port 3527

Message Queuing must bind to port 3527 to function. Make sure that the port is free (no other programs are trying to use it) and try to start the MSMQ Service again after allowing time for the port to close.

If this problem occurs during setup, you must free the port and run Setup again.

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 Message Queuing, and then click Restart. You must restart all the dependent services, as well.

Verify

Confirm 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 confirm that the MSMQ Service is installed and running:

1. Open the Services snap-in. To open Services, click Start. In the search box, type services.msc, and then press ENTER.
2. Locate the Message Queuing service, and then confirm that the value in the Status column is Started.

Verify that the computer has connectivity to the network.

Related Management Information

Message Queuing Connectivity

Message Queuing