-
280. Re: could not save because write access was not granted (Mac OS)
Simon Joh4nsson Apr 24, 2013 3:26 PM (in response to Chris Cox)Hi Chris,
I have reported an issue here (above). I have given you steps to reproduce the issue so your engineers can verify what is going on on a deeper level then either me or you can do.
Your honesty in simply blaming this issue on Apple's filesystem and/or "bugs in MacOS" is exactly the kind of response I was afraid I would get from you all along. First of all the issue I described is in regards to Xsan which is a StorNext based file system. Working on that causes dataloss for your photoshop customers. It is not even Apple's filesystem.
If the Xsan volume is *re-shared" over AFP we get other error messages (preventing save and therefore dataloss). Since those error messages are mentioned in this forum I posted the issue here.
Please just answer this:
If you took the time to test this (you need equpment for 10-20k USD for the Xsan setup, but I am sure you have a lab at your disposal) you can verify this issue as I have reported it. Do you understand that, from a customer point of view, whatever way you are saving from Photoshop that is running into whatever issue (Apple's or Adobes) could benefit from being changed to the way saving works in the other applications where saving does not cause any issues?
As you customer I do not care if it is an Apple bug causing the issue if you have the option to bypass the bug by fixing your software. Do you see where I am coming from?
(And by that I mean implement the same saving as in for example AE into PS)
"If you really want to see this fixed, please let Apple know that you don't like all the unfixed bugs in their filesystem/fileserver code."
I know that you want me to go to Apple with this, but I don't want them to change anything, they can't fix Photoshop for me, Adobe can. I want Adobe to change their code so that Photoshop saves like their other software does. Or at least take an issue with dataloss serious enough to attempt to reproduce the issue in-house and issue a statement to their customers.
I will give you an analogy:
If Photoshop is a car.
I have problems driving the car on a specific road.
You are telling me to go to the public transport office to have them fix the road.
But I am asking you to consider modifying the car so it can drive on the specific road (which your other cars already can).
Maybe I am not having the right expectations here. Is there another way for me to file a bug with you guys. Do you have a support team? Do they attempt to replicate issues and escalate them to your engineers? If so please let me know of that resource so I can help get this report to the right people...
-
281. Re: could not save because write access was not granted (Mac OS)
Chris Cox Apr 24, 2013 4:26 PM (in response to Simon Joh4nsson)We are identifying the bugs as being in MacOS because we have tested and found that the bugs are in MacOS, and because Apple has tested and identified the bugs in MacOS.
AGAIN: we are working around as many of the MacOS filesystem and fileserver bugs as we can.
We cannot fix Apple's bugs, we cannot fix third party fileserver bugs - but we are going out of our way to work around as many as possible.
This is not about fixing Photoshop - this is about parts of the OS (and sometimes fileserver code) not working correctly.
AND AGAIN: we are working around as many of the MacOS filesystem and fileserver bugs as we can.
Also, please take some time to read the credits on Photoshop.
-
282. Re: could not save because write access was not granted (Mac OS)
Simon Joh4nsson Apr 25, 2013 2:32 AM (in response to Chris Cox)Hi Chris,
I checked your CV already. I know that you are influential.
I already have raised this issue with Apple. The funny thing with raising issues with them is that, as an end customer, you get a reference number, you give the steps to reproduce and you feel taken cared of.
Or you file it as a bug so it goes directly to their engineering.
None of that means the issue will be fixed anytime soon of course, maybe Adobe has a closer releationship and can get engineering resources allocated for major issues like this though.
Raising an issue here with you I get the feeling that: you don't appreciate the issue being raised. You don't indicate you can attempt to replicate the issue. You don't give any indication you understand the severity of the issue. Instead of considering workarounds or thanking for feedback and log it as an enhancement request for the developer team, you simply write of this as "just another filessystem/OS bug we can't do anything about".
Maybe I have miss-read your replies. I understand your frustration about bugs outside of your controll. (But as I have repeatedly pointed out you could consider workaround this by changing your way of saving in Photoshop to me more like in your other apps.)
As creatives we are totally depending on your software products, so please don't turn into another Quark in regards to staying on top of your game, fixing issues and treating customers.
-
283. Re: could not save because write access was not granted (Mac OS)
Chris Cox Apr 25, 2013 10:55 AM (in response to Simon Joh4nsson)I am a senior engineer, and I tend to take care of the cases directly.
That's why you have gotten detailed replies instead of a case number and a brushoff.
How many times do I have to say that we have investigated these issues?
How many times do I have to say that we have found these issues to be due to bugs in MacOS code?
How many times do I have to say that Apple is fixing some of these bugs?
How many times do I have to say that we are working around as many of the Apple bugs as we can?
Are you not reading anything that I write?
AGAIN: Changing the way Photoshop saves to match other appplications would only accomplish one thing: you would lose more files without knowing about it. The OS bugs would still be there, you just wouldn't get the error notification when the OS hosed your files.
-
284. Re: could not save because write access was not granted (Mac OS)
Jeff-Adobe Apr 25, 2013 1:36 PM (in response to Simon Joh4nsson)Hi Simon,
Can you send me an email to jsass [at] adobe.com? I would like to get some more specific information around your server setup vs. what we have here in house.
Thanks,
Jeff Sass - Adobe Photoshop
-
285. Re: could not save because write access was not granted (Mac OS)
Simon Joh4nsson Apr 26, 2013 1:49 PM (in response to Chris Cox)Hi Criss,
I get what you write. I realize the issue may not be with you.
Sorry for talking past each other. If changing the code in PS to be more like other adobe apps is not an option I think only Apple can fix this particular issue we have isolated.
Might be worth a tech note from Adobe still since it is a pretty bad outcome of the issue as things are now that only seems to affect Photoshop and Xsan 3 customers.
As an end customer it's very easy to get the impression that this is a
Photoshop bug since the issue only occurs in Photoshop.
Once again if you want my help to isolate the effects of the issue I can help with access to our system to isolate.
I am sorry for my tone in last posts, issues like these are very frustrating but I should not let that frustration result in unfair comments here. (I would edit out the quark comment if I could).
-
286. Re: could not save because write access was not granted (Mac OS)
Jeff-Adobe Apr 26, 2013 2:32 PM (in response to Simon Joh4nsson)Hi Simon,
I have filed Adobe Photoshop bug 3550643 for this issue. I will continue to work with you offline on this and if we find a solution we can report back to this thread.
Thanks,
Jeff
-
287. Re: could not save because write access was not granted (Mac OS)
Chris Cox Apr 26, 2013 2:38 PM (in response to Simon Joh4nsson)Only Apple can really fix the underlying problems (or possibly the vendors behind XSan in your case).
But we are trying to work around as many of the issues as possible - not by failing to inform you of errors like other applications, but by checking for known problems and having fallback strategies (if that directory gives an error when it shouldn't, write somewhere else) or avoiding problematic APIs when necessary (if that server can't handle a certain operation (even if it is supposed to): then don't do that operation on that kind of server).
We really want network saving to work - we know it can when the OS, server and network are all working correctly.
But we've seen SO many issues with bad servers, bad networks, bad server administrators (Dilbert is an optimist), and unfortunately a lot of bugs in OS code (especially on MacOS)...
-
288. Re: could not save because write access was not granted (Mac OS)
PaulaBeaumont May 1, 2013 3:52 AM (in response to Chris Cox)Hi forgive a newbie butting in - but I have just changed fom a PC to IMAC, installed my CS4 extended edition, everything working fabulously untill I try and save an image I have just spent three hours manipulating. I get the same message as everyone else here "write access was not granted". I googled the issue and stumbled onto here. Now I am not technical at all, I'm a photographer that just manipulates images. I have tried reading through the 8 pages here - but kinda glazed over by page three - not a lot made much sense. But the gist that I am getting is that I can't do anything about this issue, you guys haven't found out how to work around this and I'm stuck with a mac that I can't use CS4 on?
Is that about right?
Thanks Paula
P.S - There's no server - just me and my new mac (that I would actually like to throw out the window at this moment in time!!)
-
289. Re: could not save because write access was not granted (Mac OS)
Andre Schneider May 1, 2013 4:44 AM (in response to PaulaBeaumont)Hi Paula,
A workaround is just saving as a different name. Just add a 1 or something at the end of the file name and save it and your work won't be wasted. Weird that this is happening on a local drive thou, I haven't seen this happen before.
Andre
-
290. Re: could not save because write access was not granted (Mac OS)
PaulaBeaumont May 1, 2013 4:52 AM (in response to Andre Schneider)Hi Andrea - thanks for the reply but I'd already tried that and nothing works. The only place it is letting me save anything to is a dropbox file - which will do for now but is a complete pain in the backside and adding loads of time to processing that I don't have and I have had to extend my dropbox space allowance so it's already cost me money!
Thanks
Paula
-
291. Re: could not save because write access was not granted (Mac OS)
Kurt Lang May 1, 2013 6:36 AM (in response to PaulaBeaumont)Where is the file being saved to? On the same partition as the OS and Photoshop, or a separate partition?
-
292. Re: could not save because write access was not granted (Mac OS)
PaulaBeaumont May 1, 2013 6:43 AM (in response to Kurt Lang)Sorry Kurt I don't know even what that means (sorry I did say I wasn't technical!) I am trying to save to a Toshiba external hard drive. I can use it in any other application on the mac and I use it on my home PC all the time. But I can not save from PS at all.
Thanks Paula
-
293. Re: could not save because write access was not granted (Mac OS)
Kurt Lang May 1, 2013 7:11 AM (in response to PaulaBeaumont)I am trying to save to a Toshiba external hard drive.
Actually, that's just the kind of info I was looking for.
OS X is built on top of UNIX, which is a permissions based OS. On the desktop, click on the icon of your external drive once to highlight it. Then press Command+I (or choose Get Info from the menu bar). You will see this (the name of the drive will of course be different):
If necessary, click on the arrow next to Sharing & Permissions so it looks like the image above. Click on the lock at the lower right. Your admin password box will appear. Type in your password and click OK. Now turn on the check box next to Ignore ownership on this volume. Close the Get Info box.
That's it. Now nothing on that drive is considered "owned". You won't see any more such messages about "write access was not granted".
-
295. Re: could not save because write access was not granted (Mac OS)
Andre Schneider May 1, 2013 7:34 AM (in response to PaulaBeaumont)Hi Paula,
Your drive is formatted as a NTFS drive (which is a file format that only Windows can read), that's why you're not being able to save to it. If you format it in pretty much any other file system existent you'll be able to save it normally. In the meantime, you can save the file on your desktop so that you don't have to use your Dropbox.
Andre
-
296. Re: could not save because write access was not granted (Mac OS)
Kurt Lang May 1, 2013 7:37 AM (in response to PaulaBeaumont)"You can only read" says it all. That's why you can't write anything to the drive.
The problem is it's formatted as NTFS (a Windows format). OS X can only read NTFS drives by default. There's a few things you can do to get around it.
The first issue is; does the drive need to be in NTFS format anymore? That is, do you still share it with a Windows computer? If not, then there's no need for the drive to be NTFS. If that's the case, do this:
1) Make a new folder on the OS X drive. Copy everything from the external drive to the new folder.
2) Use Disk Utility to erase the external drive as Mac OS Extended (Journaled).
3) Copy everything back to the newly Mac formatted drive.
4) Now use the instructions above to ignore permissions on the external drive.
If the drive must remain NTFS format for some reason, then you need to add third party software to OS X so it can write to an NTFS drive. Paragon NTFS is an excellent choice.
If you need to share the drive between Windows and OS X, but don't want to use such third party software, then reformat the drive as exFAT. OS X's Disk Utility can do that, but it doesn't always work well to do it from there. Take the drive back to a Windows computer. Copy all data off to another drive in Windows. Reformat the drive as exFAT, and then copy all data back. OS X can read and write exFAT without the need for any extra software.
Best choice though is to reformat the drive for the Mac, assuming you have no need to share it any further with a Windows computer.
-
297. Re: could not save because write access was not granted (Mac OS)
PaulaBeaumont May 1, 2013 7:45 AM (in response to Andre Schneider)Thanks Andre - I assume to format it I would lose the 11,000 photos on there? I need a new one soon anyway - can I format a new one so it wrks on both PC amd Mac?
Thanks again
-
298. Re: could not save because write access was not granted (Mac OS)
Andre Schneider May 1, 2013 7:56 AM (in response to PaulaBeaumont)Hi Paula,
You can do as Kurt suggested and copy everything to your Mac drive, format t and copy everything back, but if you need a new one anyway, you could leave this one as is and get a new one and format the new one for both Mac and Windows (following the steps that Kurt mentioned on his response).
Hope this helps!
Andre
-
299. Re: could not save because write access was not granted (Mac OS)
PaulaBeaumont May 1, 2013 9:12 AM (in response to Andre Schneider)Thanks guys - I really appreciate the time you've both taken to help me out. I do need the drive for both PC and Mac as I work Mac in the office and PC at home (yep crazy I know!) but hey not much I can do about that. It'a not far off full is this drive so I will format a new one for use on both machines.
Thanks again
Paula
-
300. Re: could not save because write access was not granted (Mac OS)
Kurt Lang May 1, 2013 9:28 AM (in response to PaulaBeaumont)Since you need to share between OS platforms, then you can format the new, larger drive as exFAT, or NTFS. If the latter, then you do need to purchase and install Paragon NTFS for Mac so it can write to the drive. There's also Tuxera NTFS, but Paragon's software is $11 cheaper.
-
301. Re: could not save because write access was not granted (Mac OS)
bretperry May 1, 2013 3:28 PM (in response to Kurt Lang)Yep, but if you go with FAT, you will be limited in file names, rather like "old" DOS-style short names--same as most Flash/Thumb drives which often are formatted FAT.
NTFS would probably be better but needs software for OSX.
Bret Perry
-
302. Re: could not save because write access was not granted (Mac OS)
Kurt Lang May 1, 2013 12:09 PM (in response to bretperry)Not FAT, exFAT. exFAT supports long file names and very large files.
The main disadvantage of exFAT is that Microsoft themselves still haven't released an official standard for it. Most likely the reason why it's still a bit flakey in both Windows and on the Mac.
For that reason alone, and along with your recommendation, I would much more strongly suggest PaulaBeaumont use NTFS for her external drive and install Paragon NTFS on her Mac.
-
303. Re: could not save because write access was not granted (Mac OS)
PaulaBeaumont May 2, 2013 1:12 AM (in response to Kurt Lang)Gosh this sounds complicated - can you not just buy a HD that is already formatted for use on both a Mac and a PC? Thank you for the replies.
Paula
-
304. Re: could not save because write access was not granted (Mac OS)
Kurt Lang May 2, 2013 5:57 AM (in response to PaulaBeaumont)can you not just buy a HD that is already formatted for use on both a Mac and a PC?
No. Each OS has its own proprietary file system. There is no uniform file system that works for both systems transparently.
The only way to have both on one drive is to partition the drive into two parts and format one as NTFS for Windows, and the other as HFS for the Mac. But then you'd still have the problem of the Mac not being able to write to the NTFS drive (without adding the OS X software mentioned above), and Windows would not be able to write or read the Mac partition.
Microsoft has never licensed the code for NTFS to anyone, and Apple holds an equally tight grip on HFS. The items you can install in OS X I've mentioned are reverse engineered products where the vendors figured out how to write to NTFS drives on their own.
Since Windows cannot in any way access a Mac HFS formatted drive, your best bet is to format the new external drive while attached to your Windows computer as NTFS. Then install either Paragon NTFS, or Tuxera NTFS on your Mac so it can both read and write the same drive as Windows. That's as close as you're going to get to a uniform file system. It's either that, or exFAT, which I'm not sure I would trust for saving critical work to.
Though if you'd rather do it the other way around, you can format the new drive as HFS+ (Mac OS Extended) and install MacDrive on your Windows computer. That will allow Windows to read and write a Mac formatted drive. The same people who make Paragon NTFS for Mac I linked to above, also make HFS+ for Windows; also for $20. Same thing for that title. You format the drive as HFS+ for the Mac and install HFS+ for Windows on your Windows computer so it can read and write Mac formatted drives.
-
305. Re: could not save because write access was not granted (Mac OS)
Andre Schneider May 2, 2013 6:39 AM (in response to Kurt Lang)Or, depending on what kind of files you have, if they're not that large, have it formatted as FAT so that you can read and write on both... The limit for FAT is 2Gb, right?
Andre
-
306. Re: could not save because write access was not granted (Mac OS)
Kurt Lang May 2, 2013 7:53 AM (in response to Andre Schneider)Or, depending on what kind of files you have, if they're not that large, have it formatted as FAT so that you can read and write on both... The limit for FAT is 2Gb, right?
Yes. 2 GB is the file size limit for FAT16 and FAT32 (4 GB on the same drives if you were using NT). Good source info at Microsoft. FAT16 and FAT32. FAT32 can theoretically handle an 8 TB drive, though any one partition can't be larger than 32 GB.
So FAT32 wouldn't be a terrible choice as long as no files exceeded 2 GB in size. Newer systems such as the Mac OS and later versions of Windows (7 or 8) can format a much larger drive than 32 GB as FAT32, but is very wasteful of disk space when done that way. FAT32 can still only allocate and access so many blocks, so you end up with huge block sizes on (example) a 1 TB drive. The waste comes from how all OS systems work. If when writing a file, even only 1 byte of data gets written to a block to complete a write, the rest of that block cannot be used for anything else. Multiply that by thousands of files ending their data in partially filled blocks and you end up with lots of empty, unusable disk space.
-
307. Re: could not save because write access was not granted (Mac OS)
PaulaBeaumont May 2, 2013 8:18 AM (in response to Kurt Lang)Wow - this is hurting my brain now!! ha ha - it doesn't take much! I'd never have a single file bigger than 2 gb - each photo file is about 20mb. So I think I have all this chaps - thanks very much! I maybe back when it's time to actually format the new ND tho!
Cheers Paula
-
308. Re: could not save because write access was not granted (Mac OS)
kellyjdrummer3 May 7, 2013 12:49 PM (in response to sean-gloss)I have been having this issue on a Macbook Pro 15" Retina since October 2012 when I took delivery of this machine. I use PSCS6 Extended and 4 external drives. After formatting all of them as exFAT, I have had no issues at all. None. It was just a last ditch attempt to do anything to change this issue and it worked.
Life is good again.
-
309. Re: could not save because write access was not granted (Mac OS)
Jeff-Adobe Jun 6, 2013 11:30 AM (in response to Simon Joh4nsson)Hi everyone,
The recent Mac OS X 10.8.4 released yesterday has specifically named the following fix:
- Resolves an issue saving files to an Xsan volume from certain applications
referenced from this Apple KB article. http://support.apple.com/kb/HT5730
If you are still experiencing this issue, please update to 10.8.4 and then re-test in your environment. Please let us know if you are still experiencing issues.
The KB article also mentions this fix:
- A fix for an issue that may prevent changes to files made over NFS from displaying
- A fix for an issue that may prevent documents from being saved to a server using SMB
In general this OS update has a number of network save fixes in it that we recommend users try out.
Thanks,
Jeff
-
310. Re: could not save because write access was not granted (Mac OS)
Evil Lair Jun 18, 2013 8:29 AM (in response to Jeff-Adobe)The 10.8.4 update hasn't helped eliminate the problem for our setup (running CS5). I don't know all the details of our server but I do know it's an older Xserve running 10.4, hosting through afp.
-
311. Re: could not save because write access was not granted (Mac OS)
Jeff-Adobe Jun 21, 2013 3:12 PM (in response to Evil Lair)I apologize that this issue is still reproducing for you under your setup. I will see if we can find an XServe server running 10.4 locally here at Adobe. That system isn't supported anymore from what I can determine so it might be challenging to reproduce this one but we will take a look. Thanks for the information.
-
312. Re: could not save because write access was not granted (Mac OS)
skynet-solutions Sep 4, 2013 10:04 AM (in response to Evil Lair)I have replicated and cured this issue for me and would like to share what I have found. I hope that this helps someone out there. Please click to link to read my blog post on this subject.
-
313. Re: could not save because write access was not granted (Mac OS)
LonDee3337 Oct 1, 2013 7:28 AM (in response to skynet-solutions)Thanks skynet-solutions. That's absolutely brilliant. You've solved it for me. I just have to remember to unselect the file in Finder and no more issues. Thanks for researching this.
-
314. Re: could not save because write access was not granted (Mac OS)
skynet-solutions Oct 1, 2013 8:13 AM (in response to LonDee3337)I knew when I found a solution to this particular problem many would benefit. I'm glad to know that it works for you too.
-
315. Re: could not save because write access was not granted (Mac OS)
kellyjdrummer3 Oct 1, 2013 9:01 AM (in response to skynet-solutions)Yes, Skynet-solutions, I employed that after seeing the post about the Preview Column solution on your blog. Although, I used that after a format to exFAT on four drives, which was the solution that worked for me. I posted that to your blog a month ago and you aknowledged it. I use both, but switch the Preview option as needed.
I don't work on a server system so I have a bit of freedom in how I deal with it. Formatting four external drives was a hassle as you can imagine. Ranging in size from 250g to 1tb. It took two days to sort, tranfer to and from all day.
Thanks for the solution, suggestion and help.
-
316. Re: could not save because write access was not granted (Mac OS)
Evil Lair Oct 1, 2013 12:49 PM (in response to skynet-solutions)I do keep lots of finder windows open that almost always includes the open files, but I never use column view so no preview action for me. Hopefully an impending move to a new server will clear it up.
-
317. Re: could not save because write access was not granted (Mac OS)
stuarta99 Nov 18, 2013 2:42 AM (in response to Evil Lair)Has anyone come across any other fixes for this. I've had the same issue with a new Mavericks user and found out that it's been happening for a while for a user on Mountain Lion, this is connected to a Win 2008 R2. On the Mavericks workstation I did ask the user to disable the preview which has resolved it, but not an ideal fix as they do use the preview option quite heavily.
Annoying to see this has been ongoing since 2011 in this thread but still doesn't appear to be any resolve
-
318. Re: could not save because write access was not granted (Mac OS)
LonDee3337 Nov 18, 2013 6:16 AM (in response to stuarta99)I haven't found another fix and I can confirm that it still happens in Mavericks. To be safe, I still always copy the file to my hard drive, work on it there, then copy back to the server when I'm done.
<begin rant>
As a side note, I've been an avid user of Apple and Adobe products for over two decades, and I can attest that both Adobe and Apple are arrogant companies and are as bad as the US congress when it comes to working with each other. The fact that Apple refuses to make any changes to fix this—or even acknowledge that it exists—proves that point. And just reading some of the responses from Adobe engineers in this forum shows how arrogant they are. But at least Adobe engineers read their own forum—Apple has a great user forum, but you'll never find an Apple employee answering questions there.
I don't care if it is a bug in Apple's OS, this doesn't appear in any other software that I own – it only happens in Adobe software. So if every other company out there can work around the bug, I don't know why Adobe can't.
In any case, we're all stuck with using the excellent workaround that Skynet-solutions came up with or just foregoing the use of Adobe products in the MacOS. I've chosen the latter for most of my work now. Why use expensive bloatware when smaller, more focused apps will do 90% of my work?
</end rant>
-
319. Re: could not save because write access was not granted (Mac OS)
kellyjdrummer3 Nov 18, 2013 6:43 AM (in response to LonDee3337)I'm in.
As a guy who works on my own, not on a server, I consider myself fortunate that I DON'T work in a server based environment. Formatting my four drives to exFAT was a pain, but pales compared to having to drag every project to a server just to commit it everytime.





