Topic Last Modified: 2009-12-01

The Microsoft Exchange Server 2010 Management Pack for System Center Operations Manager monitors the Windows Application log on computers running Exchange 2010 and generates this alert when the events specified in the following Details table are logged.

To learn more about this alert, in Operations Manager, do one or more of the following:


Product Name


Product Version

14.0 (Exchange 2010)

Event ID


Event Source

MSExchange Messaging Policies

Alert Type


Rule Path

Microsoft Exchange Server/Exchange 2010/Hub Transport/Agents/Messaging Policies

Rule Name

Recipient(s) encountered with invalid master account SIDs.


This Warning event indicates that the Microsoft® Windows Right Management Services (RMS) Exchange agent, the Active Directory RMS Prelicensing agent, failed to retrieve the user information for the recipient from the Active Directory. The agent will not acquire a prelicense on behalf of the recipient. This event may be caused by one or more of the following:

  • The data returned by the Active Directory was corrupted. For example, the user account security identifier (SID) and the master account security identifier (SID) are both empty.

  • Network connectivity issues between the computer that has the agent installed and a domain controller.

The Active Directory RMS Prelicensing agent provides Microsoft Office Outlook® 2007, Outlook Web Access, and Outlook Anywhere users easier access to their RMS-protected messages. The Active Directory RMS Prelicensing agent lets your Exchange users secure RMS use licenses for e-mail messages and attachments and store the messages locally. This enhances the ease of working with those messages offline.

User Action

To resolve this error, consider the following:

  • If this event occurs infrequently, no user action is required.

  • If this occurs frequently, check network connectivity between the computer that is running agent and the domain controllers. 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.

For More Information

If you are not already doing so, consider running the Exchange tools created to help you analyze and troubleshoot your Exchange environment. These tools can help make sure that your configuration aligns with Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. To run these tools, go to the Toolbox node of the Exchange Management Console. To learn more about these tools, see Managing Tools in the Toolbox.