![]()
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:
- Change the maximum file size settings to โUnlimitedโ
- 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.
- 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)โ.
- So needs a database monitoring tool to maintain the database file size stable.
As an example, the sample screenshot is given below:
![[Fixed]: "Upload failed path not found" or The specified path, file name, or both are too long error 3 Upload failed path not found in SharePoint server](https://i0.wp.com/global-sharepoint.com/wp-content/uploads/2019/08/1.1.jpg?resize=779%2C610&ssl=1)
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:
- Office 365: Getting started with SharePoint PnP PowerShell โ installation
- In 2 steps convert a classic SharePoint page to modern using PnP
- Office 365: Retrieve hub sites and associated sites using PnP Powershell
- Create a modern team site using PnP PowerShell in SharePoint
- In 4 steps access SharePoint online data using postman tool
- SharePoint admin center: Learn SharePoint online administration in an hour โ step by step
- SharePoint REST API: GET vs POST vs PUT vs DELETE vs PATCH
- Office 365: Understanding the hub site in SharePoint online
- Troubleshooting SharePoint Server
About Post Author
Discover more from Global SharePoint
Subscribe to get the latest posts sent to your email.
![[Fixed]: "Upload failed path not found" or The specified path, file name, or both are too long error 5 Buy SharePoint Online & Office 365 Administration eBook](https://i0.wp.com/global-sharepoint.com/wp-content/uploads/2021/04/Buy-SharePoint-Online-eBook-300x277.png?resize=300%2C277&ssl=1)