XADM: Error 1075 During Setup of Exchange 4.0 on NT 4.0

Last reviewed: November 21, 1997
Article ID: Q164930

The information in this article applies to:

Microsoft Exchange Server, version 4.0

SYMPTOMS

When you install Microsoft Exchange Server 4.0 for the first time on a Windows NT Server 4.0 computer, after you type the Exchange Service Account, the following error message appears:

   Fail On Install Setup was unsuccessful a dependency service does
   not exist or has been marked for deletion.

If you look in Control Panel Services, you see that the Exchange services are there. However, when you try to start the Exchange Service Account service, the following error message appears:

   Error 1075: The dependency service does not exist or has been
   marked for deletion.

CAUSE

To determine the cause of this problem:

In Control Panel Network, click Service and see whether RPC CONFIGURATION is installed. If not, this is the cause. RPC must be installed for Exchange Server to work.
If RPC is installed, look in Control Panel Services and see whether you have both of the following:
```
    - Remote Procedure Call (RPC) Locator
    - Remote Procedure Call (RPC) Service
```

RESOLUTION

To resolve this problem:

In Control Panel Network, click Service and
Remove the RPC Configuration and then add it again.
Restart the server then restart Exchange Server.

Keywords          : XADM kbsetup kbtshoot kbusage
Version           : winnt:4.0
Platform          : winnt

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

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