This topic provides guidelines for solving problems associated with:

  • Viewing or setting Message Queuing properties.

  • Accessing objects in Active Directory Domain Services (AD DS).

  • Using the snap-ins for Message Queuing.

What problem are you having?

I cannot find Message Queuing under Services and Applications in Computer Management.
  • Cause:  The Message Queuing service is not running.

  • Solution:  In the Computer Management console tree, under Services and Applications, click Services. In the details pane, under Name, right-click Message Queuing, and then click Start. Restart Computer Management on Windows® 7 by clicking Start, right-clicking Computer, and then clicking Manage. To restart Computer Management on Windows Server® 2008 R2, click Start, click Programs, click Administrative Tools, and then click Computer Management.

Changes I made do not show up in AD DS.
  • Cause:  Replication can delay information updates displayed in the snap-ins, so that changes you make using the snap-ins do not appear until replication occurs.

  • Solution:  Press F5 after making the change, or wait at least 15 minutes.

I cannot access the contents of a particular queue.
  • Cause:  You might not have the proper permissions for viewing the queue. By default, Message Queuing displays all queues that are viewable. However, you can view the contents of only those queues that you have proper permissions to open. Therefore, there might be public queues whose contents are not viewable in the snap-ins.

  • Solution:  Ensure that the Peek Message or Receive Message permissions for the queue are granted to you. To view the contents of a queue journal, you must have the Peek Journal permission granted for the queue. To read messages from a private queue, the remote Message Queuing application requires the Receive Message permission for that queue.

I cannot create queues.
  • Cause:  You might have insufficient permissions to perform this operation.

  • Solution:  Ensure that the Create Queue permissions are granted to you.

Messages can no longer be delivered to a particular computer or queue.
  • Cause:  The computer quota or the queue quota for the particular computer might have been exceeded.

    You can verify this in the following two ways:

    • By requesting negative acknowledgment (NACK) messages and checking their class. (This technique is applicable to the quotas of destination queues, not to computer quotas.)

    • By using performance counters to compare the queue or computer quota to the actual volume of messages.

  • Solution:  Process and remove messages from the applicable queues, or increase the appropriate quota value.

A test message cannot be sent to a particular queue.
  • Cause:  Test messages can be sent from the MMC snap-in only to test queues; these have a queue type ID of {55EE8F33-CCE9-11CF-B108-0020AFD61CE9}.

  • Solution:  Verify that the queue to which you want to send the test message has the correct queue type ID. Do not change a transactional queue or a queue requiring authentication to a test queue because any test messages sent will not be delivered to such a queue. You can send test messages programmatically to queues with any queue type ID.

I cannot access messaging files stored locally on disk.
  • Cause:  By default, only members of the Administrators group for the local computer have full access to all locally stored message files, log files, and local queue storage (LQS) files.

  • Solution:  Grant yourself administrative permissions for the computer, or add yourself to the local Administrators group.

Table Of Contents