XADM: Error When Selecting Security Tab for Mailbox.

Last reviewed: April 3, 1997
Article ID: Q153394
The information in this article applies to:
  • Microsoft Exchange Server, version 4.0

SYMPTOMS

When you attempt to select the Security tab of the properties page for a Microsoft Exchange recipient in the Microsoft Exchange Administrator program, after properly configuring the Microsoft Exchange Key Management (KM) Server, the following error might appear:

   Stop:    The specified module could not be found.
   Microsoft Windows NT
   ID no: 0xc002007e

CAUSE

This error occurs because the Microsoft Exchange Administrator program cannot access Secadmin.dll. This file must be located in the <exchange_root>\bin directory and the error will be displayed if the file is not present or is damaged.

The KM Server Setup program will install a copy of Secadmin.dll in the \security\bin directory, however, the file is also copied the <exchange_root>\bin directory during the Microsoft Exchange Server installation and it must remain there for KM Server administration to function properly.

The error also shows when selecting the "Key Management Server Administrator" button from the "Security" tab in the Encryption object found under the Configuration container.

To solve the problem simply copy SECADMIN.DLL from the \security\bin directory into the <exchange_root>\bin directory.


Additional query words:
Keywords : kbusage XADM
Version : 4.0 5.0
Platform : WINDOWS
Issue type : kbprb


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: April 3, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.