As per Microsoft: This event indicates that the Lightweight Directory Access Protocol (LDAP) call resulted in an error as described by the error code/error message. The error message can vary. For example, it could say "Insufficient rights" or "No such Object" or "Attribute or value exists". See MSEX2K3DB
for more details on this event.
- Error: 20 - To resolve this issue, move the following groups to the default User container:
1. The Exchange Enterprise Servers group.
2. The Exchange Domain Servers group.
3. The Exchange Services group. See ME822927
for more details.
- Error code: 32 - See ME254030
- Error code: 32 = Insufficient rights - From a newsgroup post: "After a lot of headaches and conversations with MS on this, I finally got it resolved so I figured I would post for anyone else that may have the same problem in the future. It turns out the exchange domain servers group did not have full control over the recipient update service even though in exchange system manager I could change it to full control (when I did change it, it would snap back to special access after a few hours). Exchange system manager and the actual schema were not in sync. Per ME259221
, I had to add a registry entry to the RUS schema via ADSI Edit waited about an hour until it populated (and it only populated on one DC BTW) then within ADSI Edit granted the exchange domain servers full control of RUS and the errors disappeared".
- Error code: 35 - See ME839912
for a hotfix applicable to Microsoft Windows Server 2003.
From a newsgroup post: "I have created a case with Microsoft support and got an answer that we cannot apply a manually created Recipient Policy in a Mixed Mode environment. It is by design".