As per Microsoft: "Following are the possible causes:
1.This behavior can occur if a specific global catalog server has been specified by using the registry, and that server is unavailable.
2.Exchange cannot find details, address, or display templates because of an incorrect legacyExchangeDN value.
3.During an unsuccessful installation of, or removal of Exchange, orphaned Display-Templates were left in the following container: CN=LostAndFoundConfig, CN=Configuration, DC=Domain, DC=com".
See MSEX2K3DB for additional information about this event.
- Error code: 0x80040402 - See ME811813.
- Error code: 0x80004005 - See ME828101 for a hotfix. Also, check Error code 0x80004005 for more details.
- Error code: 0x80070008 - See ME893353 for a hotfix applicable to Microsoft Exchange Server 2003.
According to one user that managed to fix this problem: "All I did was reboot the Global Catalog Server (We only have one on our network). I had not rebooted it since the MSDN Exchange manual removal. And I had recently made it a Global Catalog Server about 4 days before without a reboot. I had to move the server to another rack, so I took it down for about 5 minutes, brought it back up and it worked. The global catalog server is not the Exchange box in my case."
MAPI may return a warning value (CdoW) or an error value (CdoE) to the CDO libraries. A warning signifies a partial success with possible unexpected results or side effects. An error indicates the call was not successful. All warning and error return codes are nonzero.