I've been having this issue off an on for about a year, I have found that if you trash the com.adobe.Photoshop.plist file in the user's library, the issue goes away. Put the bad .plist back in the user's Library folder, user can't save.
Chris, I am not sure how this is a bug in Apple's server API if trashing Photoshop's .plist resolves the issue, if only temporarily. Any insight would be greatly appreciated here.
I will report back how long this remedy lasts for.
Photoshop only writes 2 values into the plist file (language and memory percentage) -- all the rest is OS variables.
If what you report is correct, then it would have to be an OS bug.
And the cases we've seen have been due to known bugs in file servers, or a known bug in the OS file APIs when saving to a file server.
This is all that is contained in the plist from Photoshop. The same user is also having a nasty issue with InDesign where oddly enough, removing the InDesgin .plist file resolves the issue.
Also, the saving issue appears to be user specific as fast user switching to another local account on the machine does not reproduce the issue. Sure enough, switch back the to the user account with the issue and the user can no longer save. This with the removal of the .plist from the user library really points this to something wrong in the user Library, not the server
Hopefully this is somehow helpful
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<string>/Volumes/SERVERSHARENAME/•• JOBS - Creative ••</string>
The only Photoshop values in there are "uiLanguageKey CS5.1" (sets the UI language) and "oldPaletteFontTypeKey CS5.1" (which I think is ignored). Both are default values, and neither have anything to do with files or saving.
The NS values are OS supplied. I don't know why they might affect file saving except for the "NSNavLastRootDirectory" which tells the OS where to default the save dialog the next time it is opened. I wonder if the OS has problems with the folder name (hypens and spaces)?
Chris Cox wrote:
I wonder if the OS has problems with the folder name (hypens and spaces)?
I was going to suggest the •• characters myself. What are those? They're hex code 95 from what I can see.
On the Mac they are bullets, pressing alt + 8 will get you one, and no one else is reporting issues (about 20 other desginers). For the user who has the issues, we have reinstaled CS 5.5, performed an archive and install and wiped his machine building it back up from scratch. The only way we can consistently resolve the issue is to delete the .plist. Deleting the .plist is only a temporrary solution sometimes the issue returns a couple days later, sometimes a few weeks. Something must be struggling to read that .plist consistently.
Atleast we have somewhat of a solution
Photoshop reads the plist only during launch (before reading preferences, because we need to configure the language early).
So my guess it that it is some OS component reading it.
Try working in another directory (with a normal name, no spaces, no punctuation) and see what happens.
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.
* 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?
* 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)
That particular problem we think we have a handle on (or at least have documented the bug well enough that Apple should be able to fix it).
We tried some work arounds for it in CS6 (to avoid deleting files and recover more gracefully).
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:
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:
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!
All solutions, theories or speculations about a fix are a complete waste of time. I do find it entertaining to read some of them, but a total waste of effort on everyone's part. There is no .plist file to delete or preference to tweak. This is an Adobe problem with how Photoshop opens files from a network drive and a problem that came with the latest Creative Suite 5.5 version. I have been using Photoshop for 20 years and have been working directly from an Apple server over a network for the last 10, and NEVER had a problem until I upgraded to Creative Suite 5.5.
Everyone should do themselves a favor and stop trying to come up with a fix. It's Adobe's problem, not Apple's. Apple may have changed the way it communicates from a Mac to a Server but Adobe must adapt to it. Adobe knows that the bulk of Photoshop users are on a Mac, so they need to get over themselves and fix their product.
For those just checking in, here is a horribly un-technical explanation of the problem and a work-around.
Photoshop opens a file into your RAM. The file that is left behind is an empty shell with all but a few bits of data left in it, one of them being the file size and modification stamp. When you or another network user clicks a file, especially in column view, Apple's OS generates a preview. This preview changes the resource data of the empty file that Photoshop leaves behind, and when you attempt to save the file, Photoshop freaks out and provides you with the error and ultimately nukes said empty file from the server, leaving only the RAM version. You can hit save again and re-save the file, but sometimes that isn't done and the file is lost.
The solution, TURN OFF THE PREVIEW COLUMN. By turning off Apple's ability to generate a preview, you are effectively solving the problem. Yes, I admit it's annoying and somewhat difficult to work with, but that's the way it has to be for now. To turn off the preview, go to 'Show View Options' under the 'View' menu and uncheck the 'Show Preview Column' check box. This will disable the preview for the file when in column view, thus preventing other network users or even yourself from creating a preview of an open Photoshop file.
This solution has eliminated all errors for my company, as it's pretty rare to have two people attempt to preview or open the same Photoshop file, so for us, this issue is resolved until Adobe fixes the issue for real.
Noel Carboni wrote:
Photoshop opens a file into your RAM. The file that is left behind is an empty shell with all but a few bits of data left in it,
That is absolutely incorrect.
I did say that this was horribly un-technical. I'm a designer, not a software engineer.
No worries, but oversimplifying something to the point where it's actually wrong doesn't really help even non-technical people.
I don't claim to understand the Apple bug that causes this problem, but I do know that just opening a file in Photoshop does NOTHING to the original file, even though the file contents are loaded into a document in RAM.
Gary - one person had a problem related to the open/save dialog and possibly the plist file, hence the discussion a few days ago.
Others have problems related to Finder and other processes holding onto the files.
And others still seem to run into the MacOS file system bug when saving to file servers without other obvious processes accessing the files.
None of these are Photoshop bugs.
Adobe can work around Apple's bugs sometimes, but Apple is responsible for fixing Apple's bugs.
Many times, Apple's bugs are in low level parts of the OS that cannot be worked around.
>> Photoshop opens a file into your RAM...
That entire paragraph is incorrect. Really, really, seriously incorrect.
Photoshop just reads the file, and does not modify it in any way when reading it. Your file is only modified when writing over the file, and that is the time when the OS file system bug causes problems on file servers. Photoshop CS6 tries to work around this and make sure that your original file remains intact despite the file system errors (which we can't entirely avoid).
>> The solution, TURN OFF THE PREVIEW COLUMN.
No, that is incorrect.
That will reduce the occurrance, but not solve the underlying file system problem.
Other users can be browsing the folder, the OS can be generating thumbnails or metadata, or other system activity can still trigger the file system problem.
>> the bulk of Photoshop users are on a Mac,
That is also quite incorrect.
I can verify that turning off desktop previews is not the issue. It doesn't matter if you're in icon, list or column view. Turning desktop previews on or off has no effect on how frequently the permissions or .afpdeleted errors occur. They remain pretty much the same.
I did try out the idea that maybe a space in the server name (the share point name) was possibly an issue. I changed the name of the share point from Server Files to ServerFiles. Believe it or not, just doing this has drastically cut down how often we see either of these errors. So far, only once since changing the name, whereas it used to happen at least a dozen times a day.
This using Lion Server, 10.7.4. Can't check to see if is has any effect on Snow Leopard Server.
I have the previews turned off and have for over 3 months, and I haven't had this issue since. It may not be the ultimate cause of the issue, but it does prevent me from getting the error and potentially losing files.
I have this same problem (just upgraded from CS5 to CS6) but I'm on a solitary Mac at home, no server, no shared files, no source control, just a standard home network. Save-as does not work, flattening does not work, in fact nothing I tried works. I continually get the "can't save this file because write access was not granted" error message. CS5 worked fine. My next step will be to open a support ticket.
Until I can figure this out, I won't be able to use PS CS6 at all. What's up with this?
Hi Chris. I think I may have this figured out. My first hint was in this thread (see my last post in that thread). Reinstalling the OS after the Adobe suite fixed the issue with capturing video. It was after that when I realized the .afpdeleted issue also disappeared. As did desktop icons not being created.
What it appears to be is that the installation of any Adobe suite (or single app) is damaging something related to QuickTime. Only a reinstall of the OS fixes it. I waited quite a while to post this as I was trying to test as much as possible, but the results bear it out.
What I did was use a spare partition to install various versions of OS X, the CS5 Creative Suite, CS5.5 Production Suite, CS6 Master Collection and CS6 Photoshop by itself (from a stand alone package). Yes, I spent days of testing on this. In all cases, I first erased the target drive and installed either Snow Leopard, Lion or Mountain Lion. I then applied all available updates. So we're talking squeaky clean OS. Using various apps supplied with OS X, I could not get it to fault on creating icons either on a local drive or our server.
I then installed one of the CS items mentioned above and any of its updates. Immediately afterwards, icons would not be created for all files; a QuickTime function. As before, permission and .afpdeleted messages occasionally appeared while using Photoshop, which deletes the active image from the server. All on a completely, cleanly reinstalled drive. The fix is to reinstall the OS and its updates after installing any of the Adobe packages. The .afpdeleted messages are gone, and icons are always created.
This is completely repeatable with Snow Leopard, Lion and Mountain using any of the Adobe packages mentioned. Install the Adobe software, errors return. Reinstall the OS, errors are gone. There is one that doesn't go away depending on what Adobe software you install. You also cannot fix this by simply reinstalling the stand alone QuickTime software update. So it goes like this:
Any version of OS X (10.6.x through 10.8.x) and any CS5 or CS5.5 suite: The .afpdeleted messages are gone. Icons are always correctly created. Permissions errors which delete the file being saved still occur, so this has to be related to the Adobe software somehow.
Any version of OS X (10.6.x through 10.8.x) and any CS6 software: The .afpdeleted and permissions errors are gone. I've been working this way in Snow Leopard with the CS6 Master Collection for about three weeks now, and haven't seen these messages once! The only one that pops up occasionally is Photoshop telling me that the file has been changed since the last save, do you still want to save the file? Well, of course. That was me who did the last save.
In short, it appears to be all related to QuickTime being broken by the installation of the Adobe apps. At least for the .afpdeleted and icon issues. Permissions errors remain a problem with the CS5 and CS5.5 apps.
>> Permissions errors which delete the file being saved still occur, so this has to be related to the Adobe software somehow.
That is a known Apple file system bug related to the resource fork.
So is the .afpdeleted message.
Also, icons being created for files is not part of QuickTime, but part of the OS metadata parsing -- seperate components. The OS only calls QuickTime for icons if the file is a video file.
We'll investigate -- but we're pretty careful about what we write, and not to touch the OS components.
Kurt Lang wrote:
The only one that pops up occasionally is Photoshop telling me that the file has been changed since the last save, do you still want to save the file? Well, of course. That was me who did the last save.
My understanding is that this means some part of the OS has modified the file since the last save YOU did, which is alarming (and it says that OSX is pretty cavalier about touching users' files). But apparently that's been tracked down to leaving a Finder window open showing the file you're editing while you're editing it. See if closing whatever Finder window you have open eliminates those.
Sorry, but I respectfully disagree. I erased a drive 12 times and installed one OS, and one Adobe package to test each combination without attempting to uninstall anything in between. The results are perfectly repeatable. Install the Adobe software, icons break and .afpdeleted issues are introduced. Reinstall the OS after the Adobe software, and it's fixed.
Interesting, Noel. But that one doesn't concern me since there's only two of us on the server at any time (small company ) and I know I'm the only one working on that image. Mostly though, it's not a critical error since that one doesn't cause a file to be deleted, just makes you say, "Huh?".
I can understand Chris' position. I'm sure he and Adobe's engineers have grappled with this until they're sick to death of it. But 12 times with the same result sure points to something.
I should clarify "broken icons". By that, when they aren't working correctly, about one in every thirty saves of a file out of Photoshop will not get an image thumbnail. It will instead have a generic Photoshop icon for a .psd, .tif or whatever. You can usually resave the file and then it will get a thumbnail desktop image. After reinstalling the OS, this issue stops.
I've worked on hundreds of images the past few weeks, saving mostly to our server (running Lion 10.7.4) and to the local drive. Every file gets a thumbnail icon. With CS6, I have yet to see another .afpdeleted or permissions denied message, which as everyone knows results in the file being deleted from the server.
I purposely waited to post my findings because I didn't want to throw it out on the first try without seeing if different versions of OS X or Adobe packages behaved differently. Chris may of course be also quite correct that QuickTime isn't directly the issue. I've just read in the past (long ago) that it was QuickTime's job to created the desktop thumbnail image. That and the obvious fix it had (seemingly) directly related to QuickTime in the issue I was having in Premiere Pro.
Don't anyone get me wrong. I love Adobe's software and make a pretty good living with it. As I noted in the Premiere Pro thread, Adobe's suite is everything Apple's editing software hopes to be when it grows up. When I switched from the Final Cut Studio software to the Adobe Production Suite, the output quality and overall easier use of Adobe's software was so drastically better, I wish I had started with it.
My purpose is to help find a solution to this issue, not berate Adobe.
>> With CS6, I have yet to see another .afpdeleted or permissions denied message, which as everyone knows results in the file being deleted from the server.
Yeah, we've been trying to work around the known OS bugs and add more safety and error handling to our code. But Apple added yet another server related bug in 10.8.
QuickTime was used as a file translater back in the OS 9 days, and maybe even early OS X. But I don't think that's been the case for many years.
As I said: we'll investigate, but I'm really not sure how what you describe could be possible. It's almost like the OS changes behavior when Adobe apps are installed, despire our attempts to not mess with the OS.
But Apple added yet another server related bug in 10.8.
Surprise, surprise! Glad we can't even take our iMac being used as the server past 10.7.x, I might have been tempted to update it.
QuickTime was used as a file translator back in the OS 9 days, and maybe even early OS X. But I don't think that's been the case for many years.
Ah! So it has changed since then. Well, I did say I read that a long time ago.
As I said: we'll investigate, but I'm really not sure how what you describe could be possible. It's almost like the OS changes behavior when Adobe apps are installed, despite our attempts to not mess with the OS.
Yes, it's definitely weird, but also very repeatable. Who knows, the installation of the Adobe apps may be unintentionally doing something as simple as altering the permissions of an OS component that causes the problem, and Disk Utility's Repair Permissions doesn't set it back. Wish I had the ability to look deeper, but I can only report the cause and effect I observed.
Since you have been so meticulous in your installations - how about doing it one more time?
This time however run logGen before and after, it will create a text file of all files accessed, created, and modified
This might shed light on what files are being modified outside /Applications/Adobe* and /Library/Application Support/ Adobe, etc...
(although from my experience I haven't seen CSx go into /System, they do put stuff in /Library: LaunchDaemons, LaunchAgents, ScriptingAdditions, PDF Services, Logs/Adobe, Preferences/Fonts, and Automator)
Like Chris said, Quicktime doesn't handle Icon creation, if anything that's a function of Finder (or Desktop Services) writing to the resource fork of a file if that folder has "show icon preview" turned on, that setting is written to the infamous .DS_Store files. I could see a conflict there, if Finder is attempting to read and write to the resource fork of a file while it is being written to by an Adobe app that is also trying to write an icon preview to the resource fork.
Anyway maybe give logGen a shot and see what you get?
Haha! If I had know about that little utility, I would have already done it. Not sure when I'll get my next chance to play with this, but it shouldn't be long. I'll erase and install Snow Leopard and its updates, then do a baseline log. Follow that by installing the CS6 Master Collection and its updates (I won't bother to activate it), then do a comparison log. Finally, reinstall SL and its updates and do a second comparison log.
Done. Actually, I skipped the log between the initial install of SL and CS6 since the only thing we were really interested in were files that changed again after reinstalling the OS. To make sure checksum values wouldn't be changed by installing things in a different order, when I reinstalled SL, I applied all updates in exactly the same order as the initial install.
No surprise, there's a lot of cache data that was either changed or new. Also a lot of installation receipts. But that's also really nothing since the OS tosses or updates a lot of that stuff on a reinstall. Doesn't mean a whole lot to me otherwise looking through the change log, but here's the text file for anyone who's interested. A very small .zip file will download when you click on the link. The only thing it contains is the .txt file.
Interesting that ColorSync is creating temporary profiles on your system: /Library/ColorSync/Profiles/Displays/CG243W-000015C3-0000-2090-0000-0 00070C82400.icc
Do you have a display calibrator that changes the profile all the time (like huey's in response to ambient light changes)?
I see an Apple updater writing a lot.
But Adobe's just writing GLSL temp files, and a few logs (/private/tmp/)
The updater or OS do update some cache files (/Library/Caches/com.apple.Components2.LocalCache.QuickTimeComponents , /System/Library/Caches/com.apple.Components2.SystemCache.QuickTimeCom ponents)
And the updater or OS reset a lot of plist files, and /var/db files that I don't know the purpose of.
What is interesting is /private/var/folders/CX/CXfEN29QGWq+RcH2FgSVik+++TI/-Caches-/com.appl e.QuickLook.thumbnailcache/
But is that from thumbnails being added, or the OS resetting the database?
I wonder if some of the thumbnail issues could be due to a corrupt SQLlite database for the thumbnails?
I am a hopeless non-techie but I have to look up this error since I had to have a new hard drive fitted to my MacBook Pro. As I had to re upload my PS which was CS4 extended I updated to CS6 on line with Adobe. I was unable to save any jpg or ps images on my external hard drive I just had the error message as mentioned.
I downloadedTuxera NTFS for Mac trial version and everything worked as it should. That has now run out and I will have to pay for it. So before paying out for something that I should not have to buy I scoured the net once more and came upon this conversation.
I found that I could not follow instructions to go to View-turn off preview but found similar in Bridge under Window then unticked Preview Panel. I proceeded to save both types of files to the external drive. I then decided to join this forum to add my piece of knowledge. I was then asked by Adobe to install an update to join. Since I have done this turning off the Preview Panel is not helping and I am getting the error message once more.
So my question is: What does Tuxera NTFS know that all you high tech and Adobe do not know?
PAULINE OLIVER wrote:
What does Tuxera NTFS know that all you high tech and Adobe do not know?
According to its web page it knows how to write Windows NTFS formatted disks from a Mac. Is that what format your external disk is?
Thank you Noel for such a prompt reply. I would not have known if it is or not. All I know is that I had no trouble saving to it before the new hard drive installation/ upgraded PS. So by what you are saying if I formatted my ex.HD it would save to it ok? If so why has it changed?
I'm not saying anything - I asked you a question. Be aware that formatting a disk risks losing all data stored on that disk, so don't do anything without being sure of what you're doing.
Since Tuxera NTFS knows how to access NTFS volumes, it may be that your external HD is NTFS formatted. You need to check.
Did you format the disk at some point while running Tuxera NTFS?
I know some external hard drives come from the store formatted for use with Windows, since the PC market is larger than Mac. You really need to educate yourself a little bit on how to manage disks and data, since I'm sure that with the right formatting and permissions Macs can in general access external hard drives without a 3rd party program like Tuxera NTFS.
Unfortunately, while knowledgeable about computers I'm not a Mac expert, so the detail on how to do that is beyond my ability to advise. Hopefully someone familiar with OSX and exactly what to look for will wade in here and advise you how to check what format your hard drive is, and possibly also how to check your permissions settings.