Issue description – scenario 1:
Couple of years back I was working in a big migration project where I was migrating more than 200 GB of data thru the 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:
In recent past suddenly one of the department site users reported that suddenly they were not able to upload the files in SharePoint library. They were getting the below error:
“Upload failed: Path not found”. Specified path not found on server.
For the above two scenario’s problem, the solution is 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.
- Change the maximum file size setting to “Unlimited”
- If you are good at handling the file growth size , go with 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 to “Unlimited” but automatically over a period of time when migration was in progress, it was changing back to “Limited to(MB)”.
- So needs database monitoring tool to maintain the database file size stable.
As an example , the sample screen shot is given below: