The Unified Messaging server did not register for directory change notifications on the UM AutoAttendant container. The Unified Messaging server will retry this operation after %1 minutes. Additional information: “%2”

Details
Product: Exchange
Event ID: 1122
Source: MSExchange Unified Messaging
Version: 8.0
Symbolic Name: UnabletoRegisterForAutoAttendantADNotifications
Message: The Unified Messaging server did not register for directory change notifications on the UM AutoAttendant container. The Unified Messaging server will retry this operation after %1 minutes. Additional information: “%2”
   
Explanation

This Warning event indicates that Unified Messaging (UM) worker process is not able to register the UM IPGateway container for the Active Directory® change notification request during the startup of the UM worker process. Active Directory change notification is used to notify the server when a change is detected within the registered Active Directory container. In addition, when this event occurs, the server may not be aware when other IP/VoIP gateways are added or removed from the Active Directory. This event may be caused by network connectivity issues between domain controllers and the computer that has the Unified Messaging server role installed.

   
User Action

To resolve this warning, do one or more of the following:

  • Use the Ping or PathPing command-line tools to test basic connectivity. Use Ping to isolate network hardware problems and incompatible configurations. Use PathPing to detect packet loss over multiple-hop trips. For more information, see Microsoft Knowledge Base article 325487, How to troubleshoot network connectivity problems.

  • Review the Application log and System log for network card–related events or connectivity-related events. Check the Application log for MSExchangeADAccess and MSExchange Topology events. Use the information in those events to determine the root cause of this warning.

  • Check to see whether other computers that use the same default gateway and are plugged into the same hub or switch have also experienced connectivity problems. If the other computers connected to the same default gateway have not experienced network connectivity problems, the problem may be caused by a network adapter issue on a single computer. If this is the case, try to resolve this issue by doing one or more of the following:

    • Replace the network adapter with a network adapter that has been tested and proven reliable.

    • Update the driver for the network adapter driver to the latest version.

    • Replace the network cable between the failing system and the hub or switch.

  • Check the settings on the network adapter and uplink hardware. The uplink hardware is the hub or switch that is used by the computer that has the Unified Messaging server role installed. Make sure that all network hardware is correctly configured by doing the following:

    • Make sure that the speed and duplex level settings are the same on all network hardware.

    • If the media type is set to autosense, autosensing, autodetect, or Auto Select, make sure that all components are autosensing correctly.

If you are not already doing so, consider running the tools that Microsoft Exchange offers to help administrators analyze and troubleshoot their Exchange environment. These tools can help you make sure that your configuration is in line with Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. Go to the Toolbox node of the Exchange Management Console to run these tools now. For more information about these tools, see Toolbox in the Exchange Server 2007 Help.

Related:

Leave a Reply