"550 File not Found" error on FTP in IIS

Windows Server Windows Server 2019
1

So, I’m using FTP server (integrated in IIS) on windows server 2019. The problem is FTP in IIS gives “550 File not Found”, without concluding what is the reason behind it. How can I find out what is happening? Thank you for your input in advance!

1 Like
2

Hi @Hector,

Firstly, let’s get a quick idea on the FTP 550 error.

The 5xx error falls under the permanent negative completion reply status of the FTP server. And, it means that the FTP server did not accept the command and the requested action did not take place. Further more, x5x error denotes File system errors in FTP server.
Overall, the 550 error means the file was not found or there are access restrictions for the file.

Now, let’s see the top causes for the error.

  • Incorrect path
  • Permission problem
  • Wrong mount point

Please refer this article for a clear explanation on the above-mentioned causes and with a fix. FTP 550 No such file or directory- Here’s the quick fix

3

550 error means that the file or folder do not exist.

Following are the things one should verify to fix above error.

  1. Make sure that Document Controller have access to file

  2. Verify FTP authentication issue, FTP configuration and availability of computer in Work Group

  3. Make sure that file is available to particular FTP site location and user can access it.

4

Hey there!
Check the information in this link
It shows many situations why this happens
https://kb.globalscape.com/Knowledgebase/10305/550-Permission-Denied-or-No-such-file-or-folder

5

The “550 File not Found” error in IIS FTP often occurs due to incorrect file paths, permissions, or configurations. Here’s a detailed solution to resolve the issue:

1. Verify File Path

  • Check that the file or folder exists in the specified path.
  • Ensure the file name and path are correct in your FTP client, including case sensitivity.

2. Check Folder and File Permissions

  • Navigate to the folder in IIS.
  • Right-click and select Properties > Security tab.
  • Ensure the user (e.g., IUSR, NETWORK SERVICE, or custom FTP user) has Read and Execute permissions.

3. Verify FTP User’s Configuration

  • Ensure the FTP account has access to the correct directory.
  • Check the home directory settings in IIS FTP configuration:
    • Go to IIS Manager > Select your FTP site > FTP User Isolation.
    • Ensure the user is directed to the correct physical path.

4. Check IIS FTP Authorisation Rules

  • Open IIS Manager > Your FTP site > FTP Authorisation Rules.
  • Ensure there is an appropriate rule for the user or group allowing Read or Write (if uploading).

5. Enable Directory Browsing

  • If you’re accessing folders, enable directory browsing:
    • In IIS Manager, go to the site > Directory Browsing > Enable it.

6. Firewall and NAT Settings

  • Verify that the firewall or NAT settings allow passive FTP connections.
  • Ensure that the ports are open and correctly configured.

7. Enable Logging for Troubleshooting

  • Enable FTP logging:
    • Open IIS Manager > Your FTP site > FTP Logging.
    • Analyse logs for details about failed requests.

8. Ensure Correct Mount Points for Remote Folders

  • If you are mapping remote drives or folders, verify that they are correctly mounted and accessible to the IIS service.

9. Check Binding Configurations

  • Go to IIS Manager > Your FTP site > Bindings.
  • Ensure bindings match the IP address and port used by the client.

10. Restart IIS

  • After making changes, restart IIS:

    Copy code

       iisreset

By systematically addressing these areas, you should resolve the “550 File not Found” error. If the problem persists, reviewing IIS and FTP logs will provide specific clues for further troubleshooting.