Event ID - 2188

Event Id2188
SourceMSMQ
DescriptionMessage Queuing could not access Active Directory and failed to compute routing path for messages sent to queue %3. Messages will wait in the outgoing queue until connection with Active Directory is restored. This event is logged at most once per %4 seconds. To change this setting, set \HKLM\Software\Microsoft\MSMQ\Parameters\Event2188 registry value to desired time in seconds. Error %1: %2
Event InformationAccording to Microsoft :
Diagnose :
Message Queuing was not able to join the domain or MSMQ Routing failed because of domain connectivity issues. This error might be caused by one of the following conditions:
  • Stale objects in AD DS are preventing Message Queuing from joining the domain
Note : This procedure applies to Windows Server 2008 only.
To confirm the presence of stale computer objects:
  1. Click Start, point to Administrative Tools, right-click Active Directory Users and Computers,and then click Run as administrator.
  2. On the View menu, ensure that Users, Contacts, Groups and Computers as containers is selected and that Advanced Features is selected.
  3. Browse to the particular computer. Check whether there are Message Queuing objects present under that computer.
  4. If there are Message Queuing objects and Message Queuing with Active Directory integration is not installed on that particular computer, these objects are stale.
  5. If you determine that there are stale objects, see the section titled "Remove stale Active Directory objects."
  • The computer does not have connectivity and cannot join a domain
If your computer does not have network or domain connectivity, see the section titled "Contact Microsoft."
  • Appropriate permissions are needed to create and access objects
To confirm that the user who is installing Message Queuing is a domain user and is a member of the local administrator group:
  1. Open the Computer Management snap-in. To open Computer Management, click Start. In the search box, type compmgmt.msc, and then press ENTER.
  2. In the console tree, expand System Tools, and then expand Local Users and Groups.
  3. In the details pane, double-click Administrators, and then confirm that the user is member of this group.
  4. If you determine that the user does not have the appropriate permissions, see the section titled "Grant appropriate permissions."
Resolve
To resolve this issue :
Cause :
Active Directory Domain Services has stale objects
Resolution :
Remove stale Active Directory objects
Stale objects can prevent the MSMQ Service from operating properly. Deleting stale objects may solve this problem. However, deleting a computer object in Active Directory Domain Services can cause problems on the client computer. Before deleting the 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 that computer.
You must have the Active Directory services tools installed in Role Administration tools under Remote Server Administration.
To perform these procedures,must have membership in Administrators or must have been delegated the appropriate authority.
Confirm that Active Directory services and control components are installed
To confirm that Active Directory services and control components are installed properly:
  1. Click Start, point to Administrative Tools, right-click Active Directory Users and Computers,and then click Run as administrator.
  2. Confirm that the following Active Directory tools appear in the list:
    • Active Directory Domains and Trusts
    • Active Directory Sites and Services
    • Active Directory Users and Computers
Delete stale computer objects
To delete stale computer objects:
  1. Click Start, point to Administrative Tools, right-click Active Directory Users and Computers,and then click Run as administrator.
  2. On the View menu, ensure that Users, Contacts, Groups and Computers as containers is selected and that Advanced Features is selected.
  3. Browse to the particular computer. Check whether there are Message Queuing objects present under that computer.
  4. If there are Message Queuing objects and Message Queuing with Active Directory integration is not installed on that particular computer, these objects are stale. Delete the particular Message Queuing Active Directory object, and then restart the MSMQ Service or if necessary restart the computer.
Cause :
Appropriate permissions have not been granted
Resolution :
Grant appropriate permissions
Message Queuing may not be able to create Active Directory objects if the account it is running under does not have appropriate permissions. Check the following:
  1. Confirm that the user who is installing Message Queuing is a domain user as well as a member of the local administrators group.
  2. Confirm that the proper Active Directory service tools are installed.
  3. If the account is a domain user, contact your domain administrator to check privileges.
  4. If you have the appropriate permissions, grant the Message Queuing user account permission to modify child objects.
To perform these procedures, must have membership in Administrators or must have been delegated the appropriate authority.
  • Confirm that the user who is installing Message Queuing is a domain user and a member of local administrators group
  • Confirm that the proper Active Directory service tools are installed
  • Grant the Message Queuing user account permission to modify child objects
Cause :
The computer has no connectivity or is not joined to domain
Resolution :
Contact Microsoft
If possible, consult with your domain administrator by providing the error description in the event.
If you continue to get this error, note any details in the event message, and then contact Microsoft Customer Service and Support (CSS).
Verify :
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, must have membership in Administrators or must have been delegated the appropriate authority.
Caution : Incorrectly editing the registry might severely damage your system. Before making changes to the registry, should back up any valued data.
Reference LinksEvent ID 2188 from MSMQ

Catch threats immediately

We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.

See what we caught

Did this information help you to resolve the problem?

Yes: My problem was resolved.
No: The information was not helpful / Partially helpful.