kennethharder Posted March 14, 2016 Report Share Posted March 14, 2016 Hey! I cannot seem to undo my changes due to a file having a path that is too long. The problem is that I do not know which file it is.. I have tried turning on logging, however, that did not tell me either. Help Link to comment Share on other sites More sharing options...
manu Posted March 15, 2016 Report Share Posted March 15, 2016 Ouch! We have this issue pending to be fixed since long time ago. Can you try the undo changes operation from the command line? "cm unco --all" from the workspace root path will undo your pending changes and hopefully its output will reveal more info. Link to comment Share on other sites More sharing options...
hunterwyatt Posted March 24, 2016 Report Share Posted March 24, 2016 Use Long Path Tool, Long Path Tool can simplify and probably end your problems in unlocking, managing and renaming files that appear to have a long filename. Link to comment Share on other sites More sharing options...
Ronald87 Posted August 22, 2016 Report Share Posted August 22, 2016 Yep Long Path Tool worked for me good. thanks Link to comment Share on other sites More sharing options...
manu Posted August 23, 2016 Report Share Posted August 23, 2016 Thank you for the feedback! Link to comment Share on other sites More sharing options...
Sam Posted December 15, 2016 Report Share Posted December 15, 2016 Hello everybody, I also have this error, is there a way to know which is the path limit in plastic ? Can I increase that ? Thank you for help Link to comment Share on other sites More sharing options...
manu Posted December 19, 2016 Report Share Posted December 19, 2016 Hello Sam, if you are using Windows 10 you can get rid of the restriction following this guide: http://blog.plasticscm.com/2016/10/path-is-too-long-fixed-in-plastic-scm.html As Ronald87 said you can also use the "Long Path tool" in order to bypass the issue. Link to comment Share on other sites More sharing options...
liona1982 Posted March 24, 2017 Report Share Posted March 24, 2017 search google for Long Path Tool and it will resolve all of your problems Link to comment Share on other sites More sharing options...
Misieq Posted August 16, 2017 Report Share Posted August 16, 2017 Hello Sorry for digging out this old thread. Just short question - is problem with long paths solved also for Windows 7. By solved I mean is it possible to use long paths in Win7 (Long Path Tool to just rename is not enough). Link to comment Share on other sites More sharing options...
manu Posted August 16, 2017 Report Share Posted August 16, 2017 As far as I know it's not possible, you have to have win 10 and .NET 4.6.2. Link to comment Share on other sites More sharing options...
gkelly Posted November 1, 2017 Report Share Posted November 1, 2017 I just attempted the steps at http://blog.plasticscm.com/2016/10/path-is-too-long-fixed-in-plastic-scm.html and I am still getting the same error messages. I've attempted both via commandline and via the GUI, and both paths give me the same error message. I'm running on windows 10 (1709) with .NET 4.7.1 installed using Plastic 6.0.16.1644 PS C:\> cm mkwk wkdefault C:\tmp\4567890\1234567890\1234567890\1234567890\1234567890\1234567890\1234567890\1234567890\1234567890\1234567890\1234567890\1234567890\1234567890\1234567890\1234567890\1234567890\1234567890\1234567890\1234567890\1234567890\1234567890\1234567890\1234567890\hey Error: 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. PS C:\> UPDATE: So I did a little digging and found http://www.plasticscm.net/topic/20289-plastic-windows-and-long-path-names which might explain the problems I'm having. Has there been any traction on this? Link to comment Share on other sites More sharing options...
manu Posted November 2, 2017 Report Share Posted November 2, 2017 Hi @gkelly, I'm sorry but we didn't search for improvements from MS regarding the long path support. I'm not sure why some machines are not friendly with the workaround, on my machine, for example, works fine but on some others, like yours, doesn't. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.