FTP logging cannot display the physical path for any FTP command issued by users of an IIS FTP server

Applies to: Internet Information Services 8.5Internet Information Services 8.0Windows 8


FTP logging cannot display the physical path for any FTP command issued by users of an Internet Information Services (IIS) FTP server. This behavior makes it difficult to debug the FTP server issues especially in multi-tenant scenarios for different problems including security and access failures.


This behavior occurs because the physical path is not available as a field for logging while setting up FTP Server logging.


After you apply this hotfix, you can specify the physical path as a field when you set up logging for an IIS FTP server for debugging. To do this, follow these steps:
  1. Run Inetmgr.exe to start the Internet Information Services (IIS) Manager.
  2. Select the Computer node in the navigation pane's tree view control.
  3. Double-click the Configuration Editor icon in the Management pane to open the Configuration Editor page.
  4. Select system.applicationHost/sites in the Section: drop-down combo box.
  5. Select the Collectionname and then click the ellipsis () button, click ftpServer\logFile\logExtFileFlags and then click one of the following:
    • To select the PhysicalPath for all sites, select siteDefaults\ftpServer\logFile\logExtFileFlags.
    • To select a specific site, select the site by Instance ID. 
Note This same process can be made from system.ftpServer\log\centralLogFile\logExtFileFlags for the FTP server level.

Hotfix information

A supported hotfix is available from Microsoft Support. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, go to the following Microsoft website: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.


To apply this hotfix, you must be running one of the following operating systems:

  • Windows 8
  • Windows Server 2012
  • Windows 8.1
  • Windows Server 2012 R2

Additionally, you must first install update 2919355 on Windows 8.1 or Windows Server 2012 R2.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any previously released hotfix.


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

More Information

The ability to log the physical path is provided to ease debugging problems by FTP Server administrators and should be disabled after the debugging is finished. Failure to do this makes the FTP server unusable and may cause other issues generally if the hotfix is uninstalled from the computer. For FTP server administrators to take advantage of physical path logging capabilities, this hotfix updates the schema that the applicationHost.config file on the computer validates the settings against. Removal of the hotfix will restore the FTP configuration schema to the version before the update. This makes any configuration changes that takes advantage of the new physical path field invalid.


Learn about the terminology that Microsoft uses to describe software updates.