I renamed a file in my vault and now when I try to check out the file I get a error saying my filename or path is too long (More than 260 characters.) But when I counted the number of characters in my file it was less than 150. Any ideas what is going on. Thanks in advance.
Solved! Go to Solution.
Solved by Richard.Rankin. Go to Solution.
Hello
Well, I had the same problem.
But then I searched on the internet for a solution and I ran into
L
o
n
g
P
a
t
h
T
o
o
l.
It´s really effective and you can solve your problem in less than 2 minutes
How does the long path tool work on files that are already checked into Vault? I can't do anything with them.
you are trying so much long methods. it will cost your time and will create many other problems as well. simply try using Long Path Tool.
In your Simulation Settings for FEA, turn off the OLE links button. For already existing OLE links use the LINKS command (I think its on Manage or Tools Tab) to delete existing links from the file.
Do this in your templates so its always off.
Did you find this reply helpful ? If so please use the Accept as Solution or Kudos button below.
Mark Flayler - Engagement Engineer
IMAGINiT Manufacturing Solutions Blog: https://resources.imaginit.com/manufacturing-solutions-blog
Lets consider an example so that you understand; C:\oraclxe\app\oracle\diag\tnslr\user\listener\me.txt, In this "me" file will not be counted as 2 character but will be counted as number of characters in the path name. Its because the windows API has MAX_LENGTH of 255 characters only. Thats probably the answer to your problem. That was the reason, not to the solution. If you want to solve this you can try GS Richcopy 360. I am currently using this software and it has worked for me and my enterprise to solve all our problems related to file copying.
Thank you for the comments. Unfortunately we aren't copying files. We just have inventor 2018 open sometimes actively working sometimes not and it will crash. Seems to be randomly several times a day. It doesn't just crash inventor. Any other program you try to open gives the error path filename too long. Requires a reboot to get everything working again. After having Autodesk tech support, our reseller tech support, our normal IT tech support I built him a new computer which does the same thing and rules out it being a problem isolated to his PC. So I am just holding off on putting 2018 on any of the others computers right now. 2016/17 work fine. I did use the long path tool and made sure every file on his computer and the network was under the limit. This didn't help but as most of the tech support concluded they don't think it has anything to do with a file path length. If it does it has to be something temporary or something running in the background b/c he isn't actively doing anything when it crashes. Right now he just reboots when it crashes and we are hoping for a hotfix someday that will fix it. Once it is fixed I will update the rest of the users to 2018. At this time we have spent too much time and money spinning our wheels trying to fix something that is most likely a bug in the program.
Wow! This program is amazing! Pros -did work fast -deleted thousands of my long path files -tested on different platforms, worked everywhere Cons Amazing program Summary Long Path Tool rocks! Recommended! https://longpathtool.com/ |
Hi Reader,
This appears to be one of our most read threads with no "Accepted Solution".
Autodesk Support has helped a number of customers over the years with the information provided in this article.
There are a number of posts on this thread that suggests a third party tool may be able to help. Autodesk has not tested this tool nor can we recommend using it. To avoid future readers having to try untested and potentially untrustworthy software, please try the suggestions in the article first.
Also, see this Ideastation Post to submit an enhancement request.
Hello reader,
This is one of the most read threads on the Vault forums with no accepted solution.
Before trying the other suggestions in this post please look to this article.
Error: The specified path, file name, or both are too long.
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.- (TOM COX)
To deal with issues regarding specified path, file name, or both being too long, I would suggest you to try LongPathTool. It worked for me.