XADM: Access Violation (0xc0000005) During Exchange Setup

 Last reviewed: March 3, 1998
Article ID: Q177762
The information in this article applies to:
  • Microsoft Exchange Server, version 5.5

SYMPTOMS

If you are installing Exchange Server version 5.5 on a computer with a 15- character NetBIOS machine name, the event service will send the following Dr. Watson error message at the end of Setup: 

   events.exe
   Exception: Access violation (0xc0000005), address 0x00405766
This error message will appear when Setup has finished and is starting the Exchange services, immediately before you are prompted to run the Optimizer Wizard or exit Setup.

WORKAROUND

The Microsoft Exchange Event Server generates the Dr. Watson error message only during Setup. After installation, you can manually start the service or allow Windows NT to automatically start the service after any subsequent restarts.

STATUS

Microsoft has confirmed this to be a problem in Microsoft Exchange Server version 5.5. A supported fix is now available, but has not been fully regression-tested and should be applied only to systems experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft recommends that you wait for the next Service Pack that contains this fix. Contact Microsoft Technical Support for more information. 

Keywords          : XADM kbbug5.50 kbusage
Version           : WINDOWS:5.5
Platform          : WINDOWS
Issue type        : kbbug
Solution Type     : kbfix

================================================================================

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: March 3, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.