could not save because write access was not granted (Mac OS)

[sean-gloss]

I keep getting the above error when working off of my xserve in photoshop. It is new in CS5 which we have recently upgraded to. Several people at my office are getting it. Sometimes it displays a random name with afp in front of it (I assume it is the temp name when photoshop is swapping out the new file for the old file.) It only seems to happen with psd and psb files. I have write access to the volume in question and it doesn't matter if I am the only one accessing the folder or not. I can save as and it seems to work; but it does delete the file.

Very frustrating. Anybody have any ideas? My IT guys are struggling with it, and one of them used to work on the Flash team as well as at Apple.

[stevelees-ramzwe]

Having read a fair chunk of this thread, it seems everyone is focused on this being a SERVER issue (and windows related), I am here to tell you it is not limited to those two factors.

Here is my setup:

iMac 27" Retina connected to a couple of LaCie Thunderbolt drives containing all of my work files.

Macbook Pro Retina that I connect to the two external LaCie drives mentioned above, (via Wireless network) which are connected to my iMac.

I have been using this setup for years, no Windows machines involved, and no servers involved. If I open a Photoshop file off the LaCie thunderbolt drive on my MacBook Pro, it simply will not save, saying I do not have write permissions.

The Facts:

1) I DO HAVE WRITE PERMISSIONS!

2) ALL DRIVES FORMATTED FOR MAC AND JOURNALED (No NTFS or FAT etc)

3) ALL OTHER FILE FORMATS OPEN AND SAVE FINE

Based on the facts above, this is an issue with PHOTOSHOP and nothing else. Nothing mentioned in this entire thread does anything to resolve the problem. I can not believe this problem has been around for so long and not been fixed.

I have no idea why I am suddenly having the problem as I did not prior to changing to the new iMac, which is when i 'think' it started. Surely SOMEONE at Adobe can resolve this???

[J453]

You may want to start a new thread if your issue is not server related.

What version of Photoshop are you using? (Is it up to date with all the available updates)

[stevelees-ramzwe]

I am using CS6 (13.0.6 x64). As far as I am aware, that is the latest version?

[J453]

If you're comfortable running a test, could you try running a trial of Photoshop CC 2014 on your system to see if you still get the same issue using the latest version?

[Brett N]

  Sorry, I'm joining this conversation late and I'm just working from your post above Steve, so excuse me if these questions and suggestions have already been covered. You mention that this problem only started when you moved to another Mac computer. Did this new computer have a different Mac OS version installed. I.e. did you go from 10.8.x to 10.10.x or something similar?

  When you open the file from the hard disk, are you going to the folder in Finder, double-clicking the file, and then working with Photoshop? As opposed to using File > Open in Photoshop. If so, could you try closing the Finder window where the file is when you go to save in Photoshop? I've seen an issue where the file is locked by Finder as it tries to generate a thumbnail. This locking of the file acts the same way as not having write permissions and will result in this error.

[stevelees-ramzwe]

Brett I went from 10.10.X to 10.10.X.   I just tried to open via Photoshop and with no finder window open, to save the file. Once again, write permissions error.

[stevelees-ramzwe]

I really, really do not want CC on my computer.

[Brett N]

I doubt the issue has anything at all to do with the version of Photoshop you have installed. But you could always test with CS6 to verify (you have access to this as part of as CC subscription: Creative Cloud Help | Download, install, update, or uninstall apps).

Would you like me to call you to work through this? Just send me an email with the best time to call and phone number: bnemecek {AT} adobe {DOT} com.

[stevelees-ramzwe]

Brett, I am NOT a CC subscriber, I own box versions of Adobe software.

I am heading out for the day now and will not be back until this afternoon, and really will not be free to do anything until about 8PM tonight (Sydney Australia time). IF that suits you then sure lets do it.

[Brett N]

That's a really long time from now (since it's only 10:30 a.m. your time). That means you won't be available until 2 a.m. my time, I'm afraid I'll still be asleep. What about latter in the day?

[stevelees-ramzwe]

I am free now if it suits Brett?

[Brett N]

Sorry, this post came in at 9 p.m. my time. I guess I'm getting old, but I was getting ready for bed by this time. I'd need more warning to meet this kind of time. Any openings today, over the next 8 or so hours?

[stevelees-ramzwe]

Brett two hours from NOW, could work.....heading out the door now, back soon.

[Brett N]

That works for me. Email me your phone number: bnemecek{AT}adobe{DOT}com.

[Chris Cox]

You don't have write permission somewhere necessary, otherwise the OS wouldn't be saying that you don't have permission (which Photoshop just relays to you).

We keep debugging this with customers, and have found only problems with drive and server permissions, plus a few OS bugs.

[stevelees-ramzwe]

All throughout this thread you (Adobe) keep saying it is a permissions issue - IT IS NOT - as stated by me and many others, ALL OTHER FILE FORMATS can read and write without issue - IT IS ONLY PHOTOSHOP that has the problem.

Unless PHOTOSHOP requires 'special' permissions that no other application requires, then it is time to find another response to the problem.

[Chris Cox]

It is a permissions issue, because the OS is saying that you do not have permission to write the file.

Photoshop is just passing along the error from the OS.

[Andre Schneider]

So Chris... As stevelees and many others (including me) have asked before, do you care to explain to us why is it that, being an OS problem, it only happens in Photoshop? If we save a file from InDesign, Word, Illustrator, FinalCut Pro, ANY OTHER SOFTWARE EXCEPT Photoshop it never gives us an error, NEITHER IT MAKES OUR FILE VANISH like Photoshop does. How do you explain that it's an OS problem BUT IT ONLY AFFECTS Photoshop?

[Chris Cox]

As we have already said, more than a few times: Photoshop does more error checking than most other applications, because we've seen so many odd errors in the past and don't want customers to lose files to those odd OS errors and minor system configuration mistakes.

If it was not a permissions error coming from the OS, then Photoshop would not be telling you that there was a permissions error.  But the OS says that there is a permissions error, and Photoshop informs the user about that error that it got from the OS.

And files vanishing is something else entirely - there was a MacOS bug like that, but we spent a lot of time figuring out how to work around it while waiting for Apple to fix the bug in the OS code.

Also, shouting is not helping.

[stevelees-ramzwe]

Chris, please understand, that we as users of your software, many of whom are probably like me, been paying for upgrades to Adobe software for many years, in my case over 20 years, so I have thousands and thousands of dollars invested in the software I use to make a living every day.

We as users are at the mercy of YOU, Adobe to solve issues relating to the software we have paid for. It is not unreasonable to expect that Adobe would do more than simply say that it is not a Photoshop problem. It IS a Photoshop problem regardless of where the cause may lay.

The fact is, YOUR software does NOT work as it should on the Mac OS X platform, and we have paid for software that should. As it stands right now, when ever I try to save it deletes the original file and then fails to write the new version.

You say Photoshop is simply relaying the message from OS X, we get that...but I put it to you this way, is OS X not simply responding to what PHOTOSHOP is trying to do?

YES it is. Given that it is ONLY Photoshop that is having this problem, and given that Photoshop is trying to save a file and sending OSX a command to do so, and that OSX is responding to what Photoshop is trying to do, it has to be a Photoshop problem. So please, stop with the 'it is not our problem' responses as it is insulting to say the least.

[Andre Schneider]

I'm sorry, I should have used bold instead. I wasn't shouting, I was trying to highlight what I was saying.

Once again, I don't believe what you are saying Chris. I'm sorry, but I don't. You can tell me as many times as you want this story, but when me, and everybody that works with me never, ever, in any time, have that problem in any other software that is not Photoshop, and that we never, ever, in any time have any "odd errors" with our files unless it's in Photoshop, I don't care what you say, I'm not going to believe that it's the OS' fault. Because your explanation doesn't make sense whatsoever. "Here, no other software gives you any problem, but it's the OS' fault". Sorry Chris, but that looks like politician talk to me. If it is really the ultra extra checking that Photoshop does when saving that gives us those problems, then why on earth do you guys at Adobe don't add that same triple checking (or whatever amount of checking it is) to the other Adobe products? Is InDesign files less worthy of not being lost than Photoshop files? Are Illustrator users time less valuable than Photoshop users so that they don't need the triple/quadruple checking on their files? And if indeed this amount of checking when writing a file so that "odd errors" don't occur, wouldn't it be obvious that we would see these "odd errors" every now and then when working with other software? How come nobody have those problems? How come nobody sees those "odd errors"? Are they like unicorns?

[handsontech]

Anyone have this symptom? (regarding saving in InDesign 2014)

Yosemite 10.10 Server, Macs on 10.10 as well...

SMB sharing ON/AFP ON, Macs cannot save to the shared volume…

SMB sharing OFF/AFP ON and they save just fine...

Problem is, PC's can't access the shared volumes with SMB off… Any thoughts?

[bretperry]

Yosemite uses smb3 by default.

I gather all your macs running Yosemite?

Are they using afp to connect? - Why not just connect them with smb which is faster than afp?

(smb will not enable Spotlight search on server - the only real downside of smb3)

Maybe you could enable smb1 (CIFS) on the server to connect older OSXes?

Bret Perry

The information in this email is confidential and may be legally privileged. It is intended solely for the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution, or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. If you have received this email in error, please notify us immediately by calling the Help Desk at 855-486-5519.

[handsontech]

All Macs are on Yosemite... All are new iMacs...

Server was upgraded (actually a clean install to a new volume) to Yosemite as well... The problem is that IF I have SMB active on the shared volumes InDesign will not save the changes to a file to the volume...  Even if the Macs are connected via SMB... Tried to connect them with CIFS but still had the same problem saving to the drives...

Tonight I'll turn AFP off, connect all Macs via CIFS and see what happens... Have not tried any testing with AFP turned off... Worth a shot...

[bretperry]

We have a Windows server and "no" issues saving InDesign files using smb, smb2, smb3 or afp thru ExtremeZ_IP on server from Yosemite or Mavericks Macs.

Could it be a problem with files being locked while live preview is trying to update? Or Spotlight?

(If so, turn off previews or use List view)

Bret Perry

Application Specialist/Studio Client Manager

The information in this email is confidential and may be legally privileged. It is intended solely for the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution, or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. If you have received this email in error, please notify us immediately by calling the Help Desk at 855-486-5519.