Find the file in Windows Explorer, or File Explorer as it’s called in Windows 10, click once on it, hit F2 to rename it, and change that silly filename to something more reasonable. It’s obvious who the offender is in this case. Maybe you have a filename that looks something like: C:\User\guymc\Documents\My Resumesresumewithanamesolongthatitcausesproblemsandbecomespartofsomeguysarticleonthewebhowdoyoulikemenow.docx
I've had to use this technique doing a massive robocopy between two servers when we realised that users had mapped drives quite deep in the folder structure, so they had been able to use 255 characters from there, but that exceeded the total file path length when accessed from the local drive root.If you’re fortunate, you’ll get the error and know exactly what file’s name is causing the issue. Remember, you don't have to share the folder containing the file necessarily, if it is already inside a shared folder you can just map through the share and the nested folders to a target folder near to the file and that works fine. (The "/persistent:no" means this won't survive the next reboot and confuse you later on.ĭon't forget to un-share your folder when done.) Assume you shared folder "foo" as "fooshare", then you could do net use x: \\mycomputername\fooshare\bar\folders /persistent:noĪnd the X: drive now points directly to the folder "folders" inside that share, so "x:\oldfiles\myoldfile.txt" is now pretty short. Now go to the shared folder or one inside it and share it, or use the command line as follows.
If you want, just allow modify rights only to your own account. Depending on your environment and paranoia level, allow everyone modify access to the share as long as the NTFS permissions are reasonably restrictive. Pre-requisite - the folder must be in a shared folder (which it may already be if it is on a server, which is where I have needed to do this), and if it is not already then pick a folder somewhere in the path and share it. Then map an arbitrary drive letter to somewhere along the path so that the first chunk of the path becomes only a few characters long. So you have c:\some\long\path.\and\foo\bar\folders\oldfiles\myoldfile.txt. A trick I have used to get round the "full path and filename" length limitation in order to move, copy or delete something is to shorten it by 'breaking in' halfway down (or more) using a mapped drive letter pointing to a folder way down the path.
0 kommentar(er)
