Getting file name too long to save message

This problem has just started to happen and it is very strange. I am now unable to directly save files with long filenames into one particular folder on my main hard drive. When I try I get the following message: "Names longer than 31 characters are not supported on the destination volume." My hard drive is formatted as "Mac OS Extended". In the past I have saved many files with long names in this particular folder with no problem.


The strange thing is that I can save the file with the long filename onto my desktop and then move it into the folder that I can not save directly into.


I need some advice on how to troubleshoot this. All software is up to date. In these cases I have created the documents in Pages and tried to save as pdf.


Thanks for your help.

iMac (24-inch Mid 2007), OS X Mavericks (10.9.1)

Posted on Dec 22, 2013 4:46 AM

Reply
33 replies

Mar 13, 2014 10:51 AM in response to AndyT!

I've also experienced the problem when trying to save Thunderbird email attachments after upgrading to 10.9.


Possibly related to this Finder bug: I can no longer drag items from my Downloads stack in the Dock into another Finder window or even the Desktop. I can drag them to the Trash on the Dock, but nowhere else. This is incredibly annoying.


In general Finder seems to have become a hot mess in the Mavericks release. Better looking, but not someone you want to marry.

Mar 21, 2014 3:43 PM in response to ealondon

I just got two new Apple laptops: an Air (to use while my 6-month-old MacBook Pro was sick with blood-curdling slowness for two months) and a new MacBook Pro Retina to replace the sick one. While the Air doesn't have the 31 character problem, the MackBook Pro does: I cannot save a PDF from Chrome. If I try from Safari, it works. At least for now...

May 1, 2014 7:09 PM in response to bjkered

I ran diskutility to repair permission on my MBP and it fixed the problem.


I have two MBP (a year apart) with identical paths: one saves files file while the other intermittently has this problem. So: problem is not SSD-v-HD or application or file path.


During diskutil repairpermissions, the four thing that caught my eye was (the remaing two was printer.plist)

usr/lib/libruby.2.0.dylib

usr/lib/libruby.dylib

Applications/Safari.app/Contents/Resources/Safari.help/Contents/Resources/index. html

private/etc/aliases


Do not know if that's the culprit. Ran diskutil repairpermissions again: only the two libruby were not there in the fixed list. So, that' narrows it down. Maybe it depends on those apps who uses those ruby libaries?


tim

Dec 7, 2014 1:00 AM in response to timerinoz

not sure if that will help but just in case I've done check/repair permissions (diskutil repairPermissions disk1) as well and spotted this (apart from numerous cups/printer permissions issues)


User differs on "private/var/db/displaypolicyd"; should be 0; user is 244

Group differs on "private/var/db/displaypolicyd"; should be 0; group is 244

Repaired "private/var/db/displaypolicyd"


doesn't seem related though.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Getting file name too long to save message

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.