Many Office 365 clients (and especially Excel) really don’t like long paths. The older the client, the worse the issues.
To find files over a certain path length in Office 365, I wrote a script a while back. This required manual perusal of the results and manual correction of the issues.
The new version of my script now features fully automatic discovery, a flexible editor and automatic correction of paths based on what you entered into the editor.
You can get the PowerShell script / editor from my git repository here.
Many thanks to CTS in their help me designing and testing this script!
How to use
- download the script and save it somewhere
- Copy the desired Sharepoint Library into a new Sharepoint Library and/or site
- Run the script only for that site or library by specifying the -specificSiteUrls or specificDocumentLibraries parameter
- do some corrections, commit them, check the results
- If satisfied, set permissions for your admin account on the actual production locations your wish to fix (script for Onedrive Mass Permissions here)
- Ensure no users have open files in the library
- Remove any non-standard characters from folder names (see script source, example code at the top)
- Please make sure you TEST this on a copy of your document library/sites before using the ‘commit’ option.
- Use at your own risk.
- I recommend turning on the Universal Audit log before usage.
I get the “You specified an empty CSV file! Try again without precreating the CSV file so this script can create it for you at the specified path.” although there is no csv file in the directory when i run the script ?
When finish gives me GUi with null examples, and with this error: Index operation failed; the array index evaluated to null
After my credentials windows open i type it always say some error:
Could not connect to SpO online, check your credentials
At C:\Users\se19138\Downloads\fix-filesWithLongPathsInOffice365.ps1:251 char:9
+ Throw “Could not connect to SpO online, check your credential …
Could you be a bit more specific towards this “.PARAMETER specificSiteUrls
“Comma seperated list of sites to process. If not specified ALL sites are processed (including Onedrive for Business and Microsoft Teams)”
I have tried different variations be is does not work, tried this
Nothing works here, so it would be great if you included an example just like specificDocumentLibraryUrls
[…] max path length tool has been […]
Thank you for this script. I was wondering if there is a way to only target the script for the specified URLs. I have added my specific site URLS but once the script starts and it recognizes them, the script continues to run discovery and then picks up my user’s personal OneDrive subsites. This then causes the script to get overwhelmed later on. Is this supposed to be happening?
Thank you in advanced.
Is it possible to use this to scan subsites? I have a subsite that does not include the /site/ portion. AKA https://Contoso.sharepoint.com/sites/testsite would be the general and the subsite is https://Constoso.sharepoint.com/subsite and is not being picked up in the scan but the other 50 sites in our collection are
[…] Max Path Length in Sharepoint Online, Onedrive for Business and Teams […]
[…] Max Path Length in Sharepoint Online, Onedrive for Business and Teams | Liebensraum […]