As per Microsoft: "This issue may occur if the Exchange Enterprise Servers security group does not have Manage auditing and security logs permissions on the domain controller. The Exchange Enterprise Servers group must have Manage auditing and security logs permissions on all the domain controllers in the domain". See ME328662
for more details.
, and MSEX2K3DB
for additional information on this event.
I was getting this error along with EventID 2102 and EventID 9154. I had two Exchange servers running. I had migrated mailboxes from the first to the second because of a hardware problem. Every time the first Exchange server would reboot, users would lose connection to the second Exchange server hosting the mailboxes. This was fixed by changing the Exchange server responsible for holding the Recipient Update Service to the second server.
Quick Fix - Reload DNS Zone information. This error occurs when DNS does not contain accurate Global Catalog server information. Make sure a GC server is available and listed in DNS. You may need to reload the DNS Zone if you have made recent Global Catalog changes, or if you have rebooted your server. Exchange 2000 needs to communicate with a Global Catalog and it does this through DNS.
This is caused either because there are no GC servers available or because there is no Recipient Update Service created in the domain where you installed Exchange 2000. See ME322801