Message Queueing routing server is operating in workgroup mode.

Summary

The local computer is a Message Queuing routing server that formerly belonged to a domain and is now operating in workgroup mode. Other Message Queuing clients still regard this computer as a routing server and will try to route messages through this computer

Causes

Stale computer objects can cause the MSMQ Service to not operate properly. Deleting stale computer objects may solve this problem. However, deleting a computer object in Active Directory Domain Services (AD DS) can cause problems on the client computer. Before you delete a computer object, make sure that no services running on the client computer will be affected. In this case, deleting the Message Queuing Active Directory object will delete public queues on the computer.

This error might be caused by one of the following conditions:

• Stale Computer objects

• Configuration errors in the Directory Service Integration feature.

Resolutions

Stale computer objects

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

To delete stale computer objects:

• Click Start, point to Administrative Tools, right-click Active Directory Users and Computers, and then click Run as administrator.

• On the View menu, ensure that Users, Contacts, Groups and Computers as containers is selected and that Advanced Features is selected.

• Browse to the particular computer. Determine whether there are Message Queuing objects present under that computer.

• If there are Message Queuing objects and Message Queuing with Active Directory Integration is not installed on this particular computer, this object is stale. Delete that particular Message Queuing Active Directory object, and then restart the MSMQ Service or, if necessary, restart the computer.

Configuration errors in the Directory Service Integration feature.

You can confirm the presence of the Directory Service Integration feature by doing the following:

• Verify the registry key setting

• Verify that the computer is joined to the correct domain

• Verify Active Directory operation

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

Caution: Incorrectly editing the registry might severely damage your system. Before making changes to the registry, you should back up any valued data.

Verify the registry key setting

To verify the registry key setting:

• Open Registry Editor. To open Registry Editor, click Start. In the search box, type regedit, and then press ENTER.

• In Registry Editor, expand HKEY_LOCAL_MACHINE, expand SOFTWARE, expand Microsoft, expand MSMQ, and then click Setup.

• In the details pane, double-click msmq_ADIntegrated.

• Confirm that Value data is set to 1.

• Under MSMQ, expand Parameters.

• In the details pane, double-click Workgroup.

• Confirm that Value data is not set to 1.

Verify that the computer is joined to the correct domain

To verify that the computer is joined to the correct domain:

• Open Server Manager. To open Server Manager, click Start, point to Administrative Tools, and then click Server Manager.

• Confirm that the domain that is listed in Computer Information is the correct domain.

Verify Active Directory operation

You can confirm that Active Directory is operating correctly by verifying that the Public Queue feature is enabled in Message Queuing.

To verify that the Public Queue feature is enabled:

• Open the Computer Management snap-in. To open Computer Management, click Start. In the search box, type compmgmt.msc, and then press ENTER.

• Navigate to MSMQ.

• If the Public Queues folder exists and you can right-click the folder, Message Queuing is operating correctly in domain mode with Active Directory Integration.

• For further confirmation, run a test application that uses the Active Directory features that you require.

Additional

For more information, see Event ID 2169 ( http://technet.microsoft.com/en-us/library/dd337420(WS.10).aspx)