New Participant

Answered

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

Forum|Forum|15 years ago
October 1, 2010
56 replies
429646 views

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.

Problem or error

This topic has been closed for replies.

Correct answer Jeff-Adobe

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).

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

Show previous replies

BREE315

New Participant

Have you found a resolution to this??

I read through the answers but nothing seems to be working for me.

"Could not save as copy because write access was not granted"

rataosinho

New Participant

Hey guys, how are you?

I'm still experiencing this problem pertinent.

Any application that tries to save the shared directory on my server, it generates the error permission.

I've tried changing the communication protocol for this function, because the OSX10.9 SMBv2 uses by default and that generates this bug as described in this article (http://cammodude.blogspot.com.br/2013/10/os-x-109-mavericks-workaround-for-smb.html).

I saw a guy comment about disable function SMBv2 and v3 directly on windows server (http://support.microsoft.com/kb/2696547). I am setting this test on a lab, return if you have news.

Finally, someone successfully to solve this problem? Any news from Apple?

Any help or solution would make me happy.

Good luck to all!

Evil_Lair

Participating Frequently

Just another follow up for my situation; I've since moved to a new Mac Pro with 10.9 and have not once seen the problem come up. I'm using all the same exact software from my old machine, the only difference being Mac OS 10.6 vs 10.9.

However I have had a new problem arise but it isn't anywhere near as severe an issue. Now sometimes when I save a file on the server I get this message: "The disk copy of "filename.psd" was changed since you last opened or saved it. Do you want to save anyway?"

I know for a fact I am the only person accessing that file, and it comes up when I'm saving multiple times a session with the file open, even just a few minutes apart. I'll see if 10.9.3 fixes it.

LarryK_95

Inspiring

Another small update: using 10.9.3 on a new Mac Pro and Photoshop CC 2014 I had this pop up again. It's only happened once but the problem is apparently still lurking.

hilarykl

New Participant

My daughter has lost all her final versions of work for her exam

She has photoshop 11, back up on external hard drive and two systems on two separate laptops, windows 7 which she reverted to when photoshop kept closing in new windows 8

we re-installed photoshop twice

we have windows defender virus check

she pressed save and save as as she went along

half the files from two days of work disappeared

we tried to get them back and simply clicking save deleted another file in front of our eyes

the lock sign has spontaneously appeared on some

the technical expert from the university has tried to get them and unable to, we have used special soft ware to look in temporary, temporary deleted, recycle, deleted/deleted

she has some print outs to scan in and size up for some of the projects but obviously its poor quality

some other students on her course have suffered similar loss

This is as serious problem and they are doing all nighters to try and recover from to get in for deadline, despite worried parents saying not t do so!

Is any one at all able to help

Any thoughts welcome

Anonymous

I can faithfully re-produce this error with One Mac opening a network folder either SMB or AFP.

This issue ONLY occurs in PHOTOSHOP no other products case this error.

ADOBE please advise ????

Title

Adobe files cannot write to server in OSX when Finder icon Preview is on

Description

Problem Description: Finder reports "Access not Granted" when saving files from Adobe Server.

Steps to Reproduce:Open a new PSD file save to server while in Finder you have the same folder.

Actual Result: File is deleted from Server and Open file has to Save as.

Expected Result:You should be able to save photoshop files on the Server without it deleting files.

Any Workarounds:
Turning off Finder "Show Icon Preview" and "Preview Column" reduces the amount of time Photoshop deletes the file.

Test Configuration

My Hardware and Environment details:
Apple OS X 10.6 - 10.9
CS 5
CS 6
CC

Anonymous

I got over this problem by installing Tuxera NTFS for Mac

Pauline Oliver

Anonymous

Hi Pauline

Are you saving to a Network or External Disk?

Regards

Matt

kellyjdrummer3

Participating Frequently

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.

yet another ben

Participating Frequently

Ok, I can 100% reproduce the problem

Here's the pattern I've found:

1. We have a network share in our studio using AFP protocol

2. A coworker creates a photoshop file

3. I then either open - or copy then open - that file.

4. If i then save the file again from Photoshop, I get the dreaded

Could not save “blablabla.psd” because write access was not granted.

and the original file is gone from the filesystem.

5. but only if that file's preview is currently displayed in my Finder's window.

If I click away from the file so that the preview is not visible then it works fine, or if I use a different finder view that doesn't have previews, like the List view, then it is also fine. As soon as I switch back to having the file's preview visible then it happens again.

Additional notes:

* If I manage to go past the step 4 and save successfully (by clicking away from the preview or using a different view), then I can switch back to the preview mode again and no further problem occurs.

* There is no issues if I'm editing one of my own files

So Adobe, is there anything else I can do to help (logs, tracing or what-not) since I can reproduce it at will?

Configuration is:

* Photoshop CS 5 12.1 (has been reported by others with 5.5)

* Lion Client 10.7.3

* Lion Server 10.7.4

* AFP Share with working ACL layer on top (User based permissions, full control)

the_brunerd

New Participant

yet another ben,

There a couple things you can do to get some data on what is happening:

1. Run fs_usage to get the file system calls as they are happening

Run it from the Terminal when you are done with the operation Ctrl-C will stop output

This first one might be a bit noisy but will get everything (-w is for Wide so nothing is truncated)

sudo fs_usage -w -f filesys

This one will only spit out lines containing Phtoshop (case insensitive) but who knows might miss some other interaction with Finder:

sudo fs_usage -w -f filesys | grep -i Photoshop

It'd be best if you can quit all other apps so the file system calls are only from Finder and Photoshop

2. You could also try Activity Monitor in Applications/Utilities, find Photoshop in the process list, double click to get info on the process, there is a Sample button that will do a call graph of all function calls by Photoshop for about 10 seconds after you press it, click it then quickly do the save operation. The data might be interesting to see here, however will probably be quite lengthy so a zip of the files is probably better than a long post

3. Once you have this data, and you done a great job with steps to repeat is file this bug as quickly as possible with Apple and then try and get as many other people to file it, start a campaign!

To file a bug report with Apple you register as a developer (free), here's all the info:

https://developer.apple.com/support/resources/bug-reporting.html

ALSO post the same bug report at Open Radar, this has the affect of getting it noticed and others can also light a fire under Apple to fix it:

http://openradar.appspot.com

Apple's Bug Reporter is sort of a "black hole" in that you can't see if there are similar bugs that have been filed, and they don't always give you feedback, sometimes a "Duplicate Bug" or asking for more info, so that's why Adobe can't comment, because they probably don't have any info on the status of the bug either (although techinically a bug report is under NDA). Apple always contends that its the volume of reports that matter and that will get its attention. 10.7.5 will probably be the last 10.7 release and it's in its 2nd beta so this really is the last hope of getting it fixed in 10.7! Otherwise if they do fix it, it will be in 10.8, just as Adobe has perhaps fixed it, but only for CS6 (not CS 5.5), so if you want it fixed without requiring an update of either OS or CS, file that bug and publicize it. I found a nasty Finder ACL duplication bug and was actually able to get it fixed in 10.6.8, even though it was fixed in 10.7, because I made a stink in my blog, had others mention it in theirs, filed a bug with Apple and open radar as well, so it can be done! Hope you can do the same! Good luck!

Joel Bruner

aka brunerd

stuarta99

Participating Frequently

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.

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

photosbyoz

New Participant

Provlem solved for us today if anyone is still looking.

We had the same issue working on an iMac connected to a Windows file server. The issue was magically fixed when I joined the iMac to the windows domain. It would appear that photoshop is opening the file using the local user permissions as opposed to the remote user permissions used to connect to the server. When the file is saved, photoshop deletes the file, as stated above, but then can't write the new file to the server as the local permissions do not have permission to write to the server.

I don't know if this is the same issue on xserve, but I am guessing that the core of the problem is the same.

Good Luck

ssprengel

Inspiring

You can move your Preferences window down on your computer by using the keyboard:

Alt-Space -> M ( -> down-arrow multiple times) -> Enter

MChapman1977

New Participant

For info, my company is primarily PC based with a small percentage of Mac and PC designers to support the rest of the business.

We have a mix of different age Macs, iMacs and MacBooks all running either 10.6 or 10.7 with CS5.

The network share is a NetApp vFiler system and we connect using SMB to ensure the Macs and PC's can connect.

We have no specialised software either on the vFiler or Macs to handle the Macs.

We are experiencing the 'access not granted' issue while trying to save photoshop files and after finding this thread (as someone said it's a goldmine for google search results) I decided I would post my thoughts so here goes:

I agree with Chris that this isn't an Adobe bug as such . We've been running 10.6.8 with CS5 for a while now and had no issues, since upgrading a few machines to 10.7 though the save issue is occuring - that suggests to me that the software isn't causing the issue, but the OS is.

The people running 10.7 are now opening the file, saving locally and copying back to the server.

I've tried making sure that the save preview setting and finder preview panes are turned off, but this hasn't helped.

Thankfully we don't seem to be losing files - I assume this is because Photoshop is bringing up the error message.

We are also running the PC version of CS5 and these users aren't having any such issues saving to the same server - Now I know this thread is about the Mac version of Photoshop, but I'm sure Adobe don't re-invent the wheel when writing their software so even though the language may be different (?) the processes will be the same - again to me this points to an OS issue.

However I do think that Adobe need to work more closely and push Apple harder to get this resolved because the length of time this has been going on simply isn't good enough and as Chris pointed out, "customers don't have visibility into Apple's bug system"

I believe this needs to be Adobe because should we as end users report this to Apple, they'll no doubt tell us this is an Adobe issue.

Until this issue is resolved though, I still don't understand why Photoshop can't be changed to use the same save mechanism as Illustrator, even as an option we can set. We don't have any issues saving Illustrator files and my users would report if they had lost data - believe me. I know that you want to perform your safe save, but it doesn't seem to be working for a good number of people out there and these people are your bread and butter.

Additionally for Chris

Has anyone tested to see if this is just the OS API taking longer to report a successful save and PS timing out? Just a thought.

You keep telling us that you can't replicate these issues in house, would you be able to let us know what your in house setup is? Someone out there may be able to replicate it and run some further testing.

I'm actually supposed to be upgrading our Macs to Lion this weekend. If this goes ahead I know will get some stick over this issue and saying that it's a problem with Adobe and Apple isn't going to appease my users, or their managers.

I am running tests today to see if 10.7.2 works and if so then we'll roll this out instead of 10.7.3 but I am not hopeful.

The other test I am going to try is installing a demo of DAVE and seeing if this makes any difference to the process.

I'll let you know how this goes.

Matt

Chris Cox

Legend

I can say that we are working as closely with Apple as Apple will let us work on these issues.

Meanwhile we are actively investigating workarounds to avoid the problem.

We can't use the unsafe mechanisms of other apps.

But we can improve the situation, and think we have in CS6.

>> Has anyone tested to see if this is just the OS API taking longer to report a successful save and PS timing out? Just a thought.

We're pretty confident that it is not a timeout, but a failure to move or copy files as the APIs are supposed to.

In house setup: those change day to day, we have hundreds of machines just on this floor, of all varieties. We've tried every combination we can think of. Somewhere, there is some triggering factor that just isn't obivious.

And you really want 10.7.3 - Apple fixed a LOT of bugs in the latest dot.

Kurt Lang

Known Participant

I've been watching and reading this thread closely for a few months now. We have a small in home business and turned an older Core Duo 2 iMac into a file server running Snow Leopard Server. That's when we ran into the .afpdeleted and write access not granted errors.

This even after having Apple help us set up a share point (they recommend never sharing the drive itself) and making sure the users have full read/write access to that share point. Didn't matter. Still got access errors (didn't have permission to write a file) and .afpdeleted errors. Which made zero sense since Photoshop would throw out either error on a file you've saved with Command+S a few times already with no issue, then all of the sudden you don't have permission to save the same file you've had open all along.

With either issue (.afpdeleted or no permission), the file gets deleted off the server (REALLY stupid!) and you have to remember to save it again immediately.

Running Photoshop configured this way, we never see the .afpDeleted error. This is a good workaround, and would also seem to be fairly conclusive proof that Photoshop is doing something wrong.

The fault could also be Snow Leopard Server, with QuickTime at the server failing to generate a preview, which in turn causes a file creation error.

May I make an observation, but requiring a major update to squash these bugs is a bit harsh.

Not harsh at all, in my opinion. That seems to be Apple's MO lately. They find the problem, but rather than fixing the issue in the current OS, they force you to upgrade to get the fix.

And you really want 10.7.3 - Apple fixed a LOT of bugs in the latest dot.

Not sure if Chris meant the client OS, or the server. Either way, my whole reason for this post is to note that we upgraded the server to Lion 10.7.3. The default came up as a stand alone server rather than open directory. I thought, heck, I'll just try it that first. I set up our share point and assigned our only two users (both on Mac Pros running Snow Leopard 10.6.8) full read/write access.

Now, it's only been up for a week so far, but we haven't seen a single .afpdeleted or no permission error since. It's also a very simple setup for a small business that may not be a feasible fix for a larger company. Who knows, it may have also worked to change SL Server to stand alone rather than open directory. But I'm not going to restore SL Server just to check that. I'll give it at least a couple of more weeks and report on if the problem seems to really be gone.

Dovahkiin27

Participating Frequently

So this issues of 'afpDeletedxxxxxxxxxxx' and 'Write access was not granted' in Photoshop are now happening in my environment. The users (about 20) have worked off of a Mac Server for 10+ years using Quark, InDesgin, Photoshop, you name it and have never had any issues until the past month or so. While I understand Adobe's stance on not working off of a server, I have been put in a tough as the system that worked for 10 years suddenly is not longer working consistently. Try telling someone they have to change the way they have been working for 10 years with no problems until now? No one is going to like that.

Here is a little info about the setup and troublehsooting I have tried

• 2 Mac Pro Servers running 10.6.8 - 1 is an OD master, the other is a OD replica which exists only in case of a disaster. The OD Master replicates its data 4 times a day to the OD replica using Carbon Copy Cloner. (The replication process has been in place and untouched for 3 years now) (I know when CCC runs and users have reported the saving issue at times that match up with CCC and times that do not. I even disabled the replication for a day and it still happened)

• The deisgners are all on Mac Pros purchased within the last three years and all are running 10.6.8 and CS5.5. As I said the connect via the built in AFP using their Open Directory Credentials using the Open Directory Authentication Attribute. All the designers have an internal drive dedicated to Time Machine. I have disabled Time Machine and the issue still happens.

• The designers are very careful about accessing each others files. Are the designer's project folders are color coded to alert other designers to stay out. Other designer's browsing the directory is not the cause.

• There has been no major change in software or hardware in the last 6 months so I cannot attribute that to the file saving issue.

When stuff was changed

CS5.5 and 10.6.8 Deployed in June 2011

OD Master Replaced (Xserve -> Mac Pro) in March 2011

3 New Mac Pros deployed in September 2011

If anyone could shed any light on this issue I cannot tell you how much I would appreciate it. I can upload logs if requested. The next step I am likely to take is to bind all the machines to the OD master and implement Kerberos, futile? Or a good idea?

Anonymous

There's only one workaround that I have found, and it's a pain. You have to go into Show View Options (Command J) and turn off the preview column.

It's a workaround that I found here with a full explaination of the issue: http://support.grouplogic.com/?p=1664

It works for me, but it's a pain because I have to hit the space bar to view previews, rather than having the finder present one to me. Slower, but safer.

Anonymous

Hi Gary,

As an addendum to your mail, we have run some reasonably extensive testing turning off the Finder preview options, but always seem to start seeing the problem again eventually. I would also add that these previews are written to the resource fork (._MyFile.jpg in the same directory for a file named MyFile.jpg) rather than the actual file and should not therefore hold any write lock over the original file.

However, in the last week or so, we seem to be seeing some success (fingers and toes crossed) with turning off the three preview options in Photoshop's own preferences as per the attached image. We've only been running with these off for a short time so no guarantees, but we can only hope.

Adobe Take Note: This would seem to indicate that your software may be holding a write lock on the file in order to write the preview. Please could you examine this section of your code to see if a resolution can be found here?

Dan

Show more replies

Title

Description

Test Configuration

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded