XFOR: File Not Found Error After Upgrading to IIS 4.0

Last reviewed: November 17, 1998
Article ID: Q193927


The information in this article applies to:
  • Microsoft Internet Information Server version 4.0
IMPORTANT: This article contains information about editing the registry. Before you edit the registry, make sure you understand how to restore it if a problem occurs. For information about how to do this, view the "Restoring the Registry" Help topic in Regedit.exe or the "Restoring a Registry Key" Help topic in Regedt32.exe.

SYMPTOMS

When you upgrade from Microsoft Internet Information Server (IIS) version 2.0 to version 4.0 from the Windows NT Option Pack, you may receive one (or both) of the following errors in the event log:

   The Microsoft SMTP Service failed to start due to the following
   error: The system could not find the file specified

   The Microsoft NNTP Service failed to start due to the following
   error: The system cannot find the file specified.

You will receive the above errors if you did the following:
  • Installed IIS 2.0 and placed the executable files in a location other than the <WINDIR>\System32\Inetsrv directory.
  • Upgraded to IIS 4.0 and added the SMTP and/or NNTP service(s).

CAUSE

When the SMTP and NNTP services are installed from IIS 4.0, the executables for the services are copied to the <WINDIR>\System32\Inetsrv directory. The registry entries for the services (SMTP and NNTP) are also set to point to the <WINDIR>\System32\Inetsrv directory. If you specified a different location (for example d:\Inetsrv) for the IIS 2.0 executables, then when the services attempt to start, the files needed to start the services (like Inetinfo.exe) are not located in the <WINDIR>\System32\Inetsrv directory.

RESOLUTION

To resolve this problem, copy the files from the <WINDIR>\System32\Inetsrv directory to the <root>\Inetsrv directory (the original IIS 2.0 default directory). You MUST also change the registry settings for the SMTP and/or NNTP service(s).

WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.

For information about how to edit the registry, view the "Changing Keys And Values" Help topic in Registry Editor (Regedit.exe) or the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe. Note that you should back up the registry before you edit it. If you are running Windows NT, you should also update your Emergency Repair Disk (ERD).

  1. Start Registry Editor (Regedt32.exe).

  2. Locate the ImagePath value under the following key in the registry:

          HKEY_LOCAL_MACHINE\System\CurrentControlSet\
          Services\<Service>
    

    where <service> is either SMTPSVC or NNTPSVC depending on which service is causing the error.

    NOTE: The above registry key is one path; it has been wrapped for readability.

  3. On the Edit menu, click String, type the path to the correct location of Inetinfo.exe (where you installed IIS 2.0), and then click OK.

  4. Quit Registry Editor.

STATUS

Microsoft has confirmed this to be a problem in Internet Information Server version 4.0.


Additional query words: xfor install
Version : WINNT:4.0
Platform : winnt
Issue type : kbbug
Solution Type : kbpending


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