Enable long file path for OneDrive for Business
My 1GB of storage part of my Office 365 Business subscription is more or less useless because I get the "File name too long" issue with most of my files.
The following request is now closed as completed but I have voted on it with OneDrive for Business in mind (and I'm sure a lot of other other users did!).
So, OneDrive for Business users, make your voice heard and vote for this!
You can now use much longer paths with OneDrive for Business and Team sites! You can read more about it here: https://techcommunity.microsoft.com/t5/SharePoint-Blog/New-support-for-and-in-SharePoint-Online-and-OneDrive-for/ba-p/60357. Thanks for the feedback!
minarul sk commented
Good i like this service
[Deleted User] commented
I don't understand why Microsoft releases critical features for non-paying users BEFORE they release them for paying ones. Seems like the paying users are the 2nd class citizens here.
Philip O'Reilly commented
just about to move my files from dropbox to onedrive and notice errors for long file names, and they weren't too long. Also noticed you couldn't right click to share files/folders like dropbox on mac. Switching back to dropbox as onedrive useless for my business needs
Mike Hansen commented
I have exactly the same problem. I want to sync a local NAS to OneDrive for business but the URL to the root of the drive location is 115 characters long, almost HALF the total number allowed.
The net effect is that I cannot sync move that 43,000 files (of a total of 161,000) and almost 1800 folders (of a total of 18,800).
Bottom line: OneDrive is useless to me.
So f***ing ridiculous... Excuse my french, but I still can't believe it
Mario P. commented
Has anyone of you try to use the "Easy fix" tool to help in renaming files and folders to prepare or fix the naming of items in a local folder or OneDrive for Business folder.
(Always test it out in Lab Environment to make sure you get the results needed in production)
Some people, including some MVP's say the 260 (or 250 or 255) character limit is in fact a Windows limitation. Other sources, like Wikipedia, say that the Windows kernel and NTFS allow up to 32,767 characters. I can't judge, so when I got to talk with a software developer on a party a few months ago I asked his opinion: "It's not a Windows limitation, it's a Win32 API limitation. The Win32 API is not the way to develop software in the 21rst century" Again, I'm only quoting.
What I can judge about: all Office 365 users I know only use the synchronized SharePoint and OneDrive folders in Windows Explorer. Those folders look the same as the My Documents folder or that share on a local Windows server, so they expect to have the same option for path length AND allowed characters. Between us: if the max path length wil only be 2,000 characters instead of 32,767 they will probably never notice in our lifetime...
Bill G commented
I have already brought this up with Microsoft numerous times.
OneDrive Personal even has a 450~ character filesize limit. mapped drives still have no solution for extended filesize.
Welcome to 2016 Microsoft. Leaders of Cloud technologies.
Yo, Admin or whoever reads this bog. I just faced this issue today. I cant believe that dropbox, a non professional app for storing in the cloud CAN work with long paths, and Onedrive FOR BUSINESS. FOR BUSSINESS BUSSSSSSSSIIIIIIIIIIIIIIINNNNNNNNNNNNEEEEEEESSSSSSSSSSSSSSSSS cannot do it.... Very very frustrating.
I will use one-drive like dropbox for temporary transfer or use of files and single folders, but it is not possible to put my file structure up there due to the restriction of path character length. Nested folders make this impossible to do. Please fix this problem.
Yeah, we'd really appreciate this feature getting included in a very soon next release. Assuming this is a client-side dependency, I'd assume folks need to plan on pushing/upgrading their desktops to the new client. So, with this request is also 'what are the requirements and steps for to accept this enhancement?'. Just trying to level-set on the overall intrusiveness and, especially if folks are still using groove.exe.
Number one priority for me as well. I make manual backups of my website using FTP and the paths are often very long, so this results in massive amounts of errors. Also, when syncing manually using e.g. Windows Explorer, the error message when the path is too long has no good option for me, either retry (which will accomplish nothing new), 'Close' which will unlink my OneDrive for business account! There should be an ignore/cancel button or something, perhaps something you can consider. thanks.
Pretty much a repeat of all below but just transferred over to onedrive from another cloud storage. Estimated it should be sign up for trial, download software, show it where to sync and go but had the file name too long error. Onedrive would not start synchronising any folders or files until it had scanned every file. After 2-3 hours I of renaming files and folders I started to question whether it was worth the transition. It took a total of 7 hours to rename all relevant documents to be shorter than 250. FYI - Longpathtool really helped me shorten this process. Now I've been uploading, started really well for the first couple of hours but now down to approx 100kbps on a 5GB up line.
This needs to be fixed it's absolutely ridiculous, the lack of support for long files names means the only option is to use something other than one drive for business. It would be cool if there was a rename option or skip option when it finds a file that is too long but all you give me is open location, try again or exit, so I'm supposed to fix this for 1000+ files before opening one drive??? What a joke!
@Jason Moore: while you are thinking about it, can you think a bit harder then you did with the "personal" onedrive and not just extend path-names to 340 characters but maybe unlimited or 32k for example?
Also, when this is achieved (probably in 8 months from here), please refrain from announcing it like "BOOM! We did it again"
Kevin Ohlsson commented
Enable this for personal accounts as well.
Rick Stockton commented
I just got some great technical advise from Microsoft on this: Here's what I did:
1.) Got into my Office365 Admin and change my company name to a [much shorter] acronym.
2.) Exit OneDrive on my PC. [Right-click OneDrive icon; Exit]
3.) Log out of Office365 portal.
3.) Sign back in to OneDrive on my PC.
4.) The OneDrive sync folder now uses the acronym instead of the old long company name.
4a.) OneDrive now syncs all of the files from the cloud down to the new location on the PC.
5.) Got back into my Office365 Admin and changed my company name back to the [and much longer] full company name.
I rebooted, and the change appears to be persistent, but I will have to repeat this procedure should I choose to 'Exit' OneDrive.
It's worth it, though, and I love it.
Is there any way to subscribe to this enhancement request? We cannot proceed with OneDrive until this issue is resolved.
Dimitar Stoyanov commented
Guys from Microsoft. Your service is just useless with these funny 250 characters limitation. Are you even realizing how embaracing this should be? Whoever did the product management, coding or whatever... should rip-off his diploma - if any.
Unfortunately I am obliged to work with it in my organization and I have to live through the nightmare you created every day. This is the least FRUSTRATING, HILARIOUS, MAKES ME CRY, RIDICULOUS, IDBMFE (I Don't Believe My F**** Eyes).
Of course you don't care, because you've already sold your 365 bundles to the big corps, closed the deal and the little tiny real users will have to suck it off now. Who cares! Your Sales Dpt? our Corp IT directors who signed the deal? No. Nobody cares now...
Hope you can sleep at night!!! I can't!!!
Kris Esplin commented
I am having multiple 'OneDrive folder has stopped sycning' errors due to overly long file paths. I have attempted to fix, but to no avail... Please fix this issue so we can upload directories from the preview version of OneDriveforBusiness that did not seem to have this problem. Very frustrating, Microsoft.