Errors when managing an Exchange 2000 mailbox using the NetIQ Administration MMC interface (NETIQKB1674)

  • 7701674
  • 02-Feb-2007
  • 27-Jun-2007

Resolution

fact
Directory and Resource Administrator 6.30

fact
Directory and Resource Administrator 6.30 SP1

fact
Directory and Resource Administrator 6.30.01

fact
Directory and Resource Administrator 6.40

symptom
Errors when managing an Exchange 2000 mailbox using the NetIQ Administration MMC interface

symptom
When attempting to create or clone an Exchange 2000 mailbox using the NetIQ Administration MMC interface the following error message is received:


'Error saving the changes to the mailbox: The Exchange server cannot complete the requested action.'

When attempting to modify an Exchange 2000 mailbox using the NetIQ Administration MMC interface the following error message is received:


'There is no object found.'

The following information is logged in the Application log on the Directory and Resource Administrator server:


'E21720: An error occurred while cloning mailbox (ldap_path): [DAPIWrite] The following error was encountered when attempting to generate or validate e-mail addresses for userid. The binding handle is invalid.'

cause
The above error messages are due to an incompatibility between Microsoft Exchange 5.x and Exchange 2000 versions DAPI.DLL file.

The Exchange 2000 CD provides the option to install the Exchange 5.5 Management tools. If you choose this option, the Exchange 2000 version of the dynamic-link libraries (DLLs) for the Directory Application Programming Interface (DAPI) version 6.0.4417 are installed. This version of the DAPI DLLs is not supported programmatically against an Exchange 5.x Server. If you use DAPI to access an Exchange 5.x directory, you should use the DAPI DLLs that ship with Exchange 5.x.

fix
To resolve this problem, install the latest service pack for Microsoft Exchange 2000 Server on the Directory and Resource Administrator server.

For additional information, please see Microsoft Knowledge Base article Q280136.

note
Microsoft has confirmed this to be a bug in Exchange 2000. This issue was first corrected in Microsoft Exchange 2000 Server Service Pack 1.

Additional Information

Formerly known as NETIQKB1674

Feedback service temporarily unavailable. For content questions or problems, please contact Support.