Upload failed path not found

[Fixed]: โ€œUpload failed path not foundโ€ or The specified path, file name, or both are too long error

No comments

Loading

In this โ€œupload failed path not foundโ€ troubleshooting article, we will learn how to fix โ€œUpload failed path not foundโ€ or The specified path, file name, or both are too long error

Issue description โ€“ scenario 1: Upload failed path not found

A couple of years back I was working on a big migration project where I was migrating more than 200 GB of data thru a third-party tool. Migration was failing again and again so it needed my constant monitoring. The 90 percent of error was โ€œThe specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 charactersโ€

But when we looked at the file path โ€“ it was within the given limit. So the error message was not correct.

Issue description โ€“ scenario 2: Upload failed path not found

In the recent past suddenly one of the department site users reported that suddenly they were not able to upload the files to the SharePoint library. They were getting the below error:

โ€œUpload failed: Path not foundโ€. Specified path not found on the server.

Solution: Upload failed path not found (the specified path file name or both are too long)

For the above two scenario problems, the solution is the same. For the particular content database, โ€œauto growโ€ size issue โ€“ Login to SQL server or ask your DB admin to check database auto-growth size settings.

Note:

  1. Change the maximum file size settings to โ€œUnlimitedโ€
  2. If you are good at handling the file growth size, go with it manually and choose the option โ€œLimited to (MB)โ€ and increase the value as per your need.
  3. This setting might get changed automatically over a period of time when the database size significantly grows โ€“ at least it happened with me โ€“ in my above scenario 1, even though I had set it to โ€œUnlimitedโ€ but automatically over a period of time when migration was in progress, it was changing back to โ€œLimited to(MB)โ€.
  4. So needs a database monitoring tool to maintain the database file size stable.

As an example, the sample screenshot is given below:

Upload failed path not found in SharePoint server

Summary: Upload failed path not found (the specified path file name or both are too long)

Thus, in this troubleshooting technique we have learned about how to fix the โ€œUpload failed: Path not foundโ€ or The specified path, file name, or both are too long error.

See Also: SharePoint Online Tutorial

You may also like the below SharePoint Online tutorials:

Download SharePoint Online PDF Book

Download SharePoint Online & Office 365 Administration eBook

Buy the premium version of SharePoint Online & Office 365 administration eBook from here:



Buy SharePoint Online & Office 365 Administration eBook


ย 

Get the free demo PDF eBook from here:

FREE DOWNLOAD

Send download link to:

Subscribe to get exclusive content and recommendations every month. You can unsubscribe anytime.

About Post Author


Discover more from Global SharePoint

Subscribe to get the latest posts sent to your email.

Do you have a better solution or question on this topic? Please leave a comment