-
160. Re: could not save because write access was not granted (Mac OS)
Chris Cox Jan 27, 2012 4:44 PM (in response to mccolo)There are too many changes involved for a dot release, and this sort of thing needs a lot of testing. So it would have to wait for a major release.
-
161. Re: could not save because write access was not granted (Mac OS)
The Penguin of Doom Jan 30, 2012 3:15 AM (in response to Chris Cox)Chris Cox wrote:
I don't know why you don't see it. We can reproduce such problems fairly often in other apps (and it's annoying as @$%^@#%).
Chris,
Could you please explain which applications you are able to reproduce this in and how? Could you also explain the save process that Photoshop implements when including the writing of previews?
This would go a long way to helping us to understand the problem.
Many thanks
Dan
-
162. Re: could not save because write access was not granted (Mac OS)
Chris Cox Jan 30, 2012 11:09 AM (in response to The Penguin of Doom)We see the problem in most apps when saving to servers. It's worst in any app that writes to a resource fork.
And when Photoshop writes MacOS thumbnails, it writes them to the resource fork.
-
163. Re: could not save because write access was not granted (Mac OS)
The Penguin of Doom Jan 31, 2012 12:55 AM (in response to Chris Cox)Could you name a few please Chris? And the circumstances under which the errors occur so we can try to reproduce same here?
Could you also please detail the Photoshop save process?
-
164. Re: could not save because write access was not granted
LongScreenName Jan 31, 2012 9:12 AM (in response to Chris Cox)I just scanned one of our file servers and found 179 .afpDeleted files. Many come from Photoshop, but I also see Keynote, Excel and Powerpoint files. I wonder if this gave the users any trouble... or if they noticed missing data. This tends to back up Chris's point that other programs can emit silent errors.
-
165. Re: could not save because write access was not granted (Mac OS)
Andre Schneider Jan 31, 2012 9:29 AM (in response to LongScreenName)I'm pretty sure that if 179 files were lost, the users would have noticed and you would know. These errors were probably "auto-fixed" by the app that generated it or didn't cause a file to be lost (which is what bothers me most with CS5)
-
166. Re: could not save because write access was not granted (Mac OS)
JohnKGibson Feb 27, 2012 12:06 PM (in response to Chris Cox)Just happend to us again today.
Thanks GOODNESS I have DiskKeeper Undelte on my server system. I can go back into the recovery bin and pull out the .afpdeleted file and then rename it on the PC side for the user.
At least we have a safety net installed where we can catch these.
-
167. Re: could not save because write access was not granted (Mac OS)
Cat Killian Mar 22, 2012 5:24 AM (in response to Chris Cox)Chris,
Is Adobe any closer to fixing the "write access not granted" issue?
BTW, here is my work-around (let me know if you have a better one):
First "Save" or "Save As"....which initiates the error message (file gets deleted but document is still open)...
Second "Save" or "Save As" again. The second save does not collide with the temp file and the same file name can be used. This is good because Lightroom can still find it.
But...I should not be having to do this...it is frustrating, to say the least.
-
168. Re: could not save because write access was not granted (Mac OS)
The Penguin of Doom Mar 22, 2012 5:39 AM (in response to Cat Killian)I wanted to post this a while ago but thought it best to wait until we'd had a decent test period.
We have been running now for some time with Photoshop's thumbnail creation prefs switched off as below.
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.
We also found another that for some reason Photoshop decides occasionally to quietly reset these settings. Perhaps Adobe would care to look into this? Can't really blame this one on anyone else.
To remedy this, we run the following script periodically. We run it from Casper as a policy ()with some additional logic code that I'm happy to supply to anyone who wants it), but you could just as easily run it from launchd or a however you please.
I hope this helps everyone suffering out there
Dan
-- set up logging
global docPath
set docPath to (path to library folder from user domain) & "Logs:" as string
global theLogFile
global logString
-- check if photoshop is open
if appIsRunning("Adobe Photoshop CS5") then
tell application "Adobe Photoshop CS5"
--Change Photoshop thumbnail preferences to do with saving thumbnails while logging results
if image previews of settings = yes or image previews of settings = ask then
my writelog("Image previews are set to " & image previews of settings & ", setting to no")
set image previews of settings to no
else
my writelog("Image previews are set to " & image previews of settings & ", leaving alone")
end if
if icon preview of settings = true then
my writelog("Icon preview is set to " & icon preview of settings & ", setting to false")
set icon preview of settings to false
else
my writelog("Icon preview is set to " & icon preview of settings & ", leaving alone")
end if
if Mac OS thumbnail of settings = true then
my writelog("Mac OS thumbnails are set to " & Mac OS thumbnail of settings & ", setting to false")
set Mac OS thumbnail of settings to false
else
my writelog("Mac OS thumbnails are set to " & Mac OS thumbnail of settings & ", leaving alone")
end if
if Windows thumbnail of settings = true then
my writelog("Windows thumbnails are set to " & Windows thumbnail of settings & ", setting to false")
set Windows thumbnail of settings to false
else
my writelog("Windows thumbnails are set to " & Windows thumbnail of settings & ", leaving alone")
end if
end tell
end if
on appIsRunning(appName)
tell application "System Events"
set res to (name of every process) contains appName
return res
end tell
end appIsRunning
on writelog(stringToLog)
set logFilePath to docPath & "com.cp.photoshopresetprefs.log" as string
try
-- Check the file & path exists and are reachable by assigning an alias
set theLogFile to alias logFilePath
on error
-- Likely that the file doesn't exist yet, try touching it and re-assigning the alias
do shell script "touch " & quoted form of POSIX path of logFilePath
set theLogFile to alias logFilePath
end try
-- Make sure another app is not already holding a write-lock on the file by closing it first
try
set logfileRef to open for access theLogFile with write permission
on error errmsg number errnum
if errnum = -49 then
-- close the file
close access theLogFile
-- Try to open it again
set logfileRef to open for access theLogFile with write permission
end if
end try
set endOf to (get eof logfileRef)
set logString to (current date) & tab & stringToLog & return & return as string
write logString to logfileRef starting at (endOf)
close access logfileRef
end writelog
-
169. Re: could not save because write access was not granted (Mac OS)
Cat Killian Mar 22, 2012 6:35 AM (in response to The Penguin of Doom)The Penquin of Doom wrote:
"We have been running now for some time with Photoshop's thumbnail
creation prefs switched off as below....we never see the .afpDeleted
error."
Unfortunately, this workaround did not change the outcome for me. Here
are additional details which seem to contribute:
In my workflow, I always open images from Lightroom (3.6) and all my
images are on a server. Launching Photoshop 5 this way will always give
me the error and delete my file. I just did some experiments and I do NOT
get the error if I do either of two things...Either don't use the server,
or open files within photoshop using "file>open". I think the second
option will be an easier road for me to take.
-
170. Re: could not save because write access was not granted (Mac OS)
Chris Cox Mar 22, 2012 8:54 AM (in response to The Penguin of Doom)>> would also seem to be fairly conclusive proof that Photoshop is doing something wrong.
Or you found a way to avoid some of the problematic OS file system calls (mostly relating to resource forks).
Apple is investigating why their APIs fail on some file servers, while we have been working on ways to avoid the problems with the OS file APIs and do a better job of catching non-obvious errors from the file APIs. Photoshop CS6 includes our latest efforts, while we're still waiting for Apple.
>> We also found another that for some reason Photoshop decides occasionally to quietly reset these settings.
That should only be possible if the application preferences get reset.
-
171. Re: could not save because write access was not granted (Mac OS)
mccolo Mar 22, 2012 9:02 AM (in response to Chris Cox)THanks for the update Chris. I was planning on looking at the Beta and
trying it on some files.
-
172. Re: could not save because write access was not granted (Mac OS)
JohnKGibson Mar 22, 2012 9:02 AM (in response to Chris Cox)Chris,
May I make an observation, but requiring a major update to squash these bugs is a bit harsh. Luckily I have migraged our company to the Assurance program and so I will be rolling out CS 6 when I am fully happy with how it works with Lion.
I rarely install .0 versions of any software anymore, even Apple because of the various gotchas that I have lived through. Which means that at best I will be rolling it out 4 to 6 months after you have introduced so that the kinks can be worked out.
Look... I am aware that many companies have gone to the model were they squash bugs in major releases, but this bug really shouldn't wait for that.
John Gibson
-
173. Re: could not save because write access was not granted (Mac OS)
Chris Cox Mar 22, 2012 9:10 AM (in response to JohnKGibson)>> May I make an observation, but requiring a major update to squash these bugs is a bit harsh.
It should be a minor OS update, but we don't have a schedule from Apple yet on when the bugs will be fixed.
While we wait for Apple to fix the bugs, we're rolling out workarounds at our first opportunity, which is CS6.
-
174. Re: could not save because write access was not granted (Mac OS)
The Penguin of Doom Mar 22, 2012 9:29 AM (in response to Chris Cox)Chris Cox wrote:
Or you found a way to avoid some of the problematic OS file system calls (mostly relating to resource forks).
Apple is investigating why their APIs fail on some file servers, while we have been working on ways to avoid the problems with the OS file APIs and do a better job of catching non-obvious errors from the file APIs. Photoshop CS6 includes our latest efforts, while we're still waiting for Apple.
Which is great for us as we can get on with working.
It's a shame that you couldn't have told us about the resource forks earlier, that may have helped us find a workaround sooner. Generally speaking, regardless of who's fault it is, both you and Adobe have come across as somewhat unhelpful in this matter. Once again, and I'm sure others here would agree, I'm not bothered who's fault it is. We needed some help to find a workaround or solution, as you know the software better than us we asked you. Instead of help, what we got was finger pointing. This has helped no-one and comes across as poor customer service. I'm sorry to have to say this but it is true.
Chris Cox wrote:
That should only be possible if the application preferences get reset.
That's why I see it as an error. It occurs without the prefs being reset, all our other prefs remain intact as far as we can tell.
-
175. Re: could not save because write access was not granted (Mac OS)
Chris Cox Mar 22, 2012 9:46 AM (in response to The Penguin of Doom)>> That's why I see it as an error. It occurs without the prefs being reset, all our other prefs remain intact as far as we can tell.
That's weird. I don't see any code in Photoshop that could change that value without the user or an action/script changing the value.
But do try the CS6 beta and see if it's improved.
-
176. Re: could not save because write access was not granted (Mac OS)
The Penguin of Doom Mar 22, 2012 9:50 AM (in response to Chris Cox)Yeah we were a bit bugged out about it too. It definitely happens, but scratch disk settings for instance are left intact.
It's not down to the preference not being written to disk as we tried setting the pref, quitting, re-launching and checking to see it had taken which it had and then some time later (hours, days even a week or so) the pref had been reset.
Anyway, we've worked around.
-
177. Re: could not save because write access was not granted (Mac OS)
MChapman1977 Mar 23, 2012 4:16 AM (in response to sean-gloss)Hi
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
-
178. Re: could not save because write access was not granted (Mac OS)
Chris Cox Mar 23, 2012 2:02 PM (in response to MChapman1977)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.
-
179. Re: could not save because write access was not granted (Mac OS)
Kurt Lang Mar 28, 2012 9:26 AM (in response to Chris Cox)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.
-
180. Re: could not save because write access was not granted (Mac OS)
JohnKGibson Mar 28, 2012 10:00 AM (in response to Kurt Lang)Kurt,
My problem is that I don't have the flexability of going to server 10.7.3. We are running Windows 2008 with Extremez-IP and my clients are all running 10.6.8 except for two or three macbook airs that were purchased and couldn't be downgraded.
As a larger comapny, I have to evaluate how each OS update is going to affect our workflow, and the loss of Save As in Lion, along with how apple is handing the versioning, gives me pause and I have to see how it interacts with our server and software.
I tend to be about 1 major version of Mac OS behind Apple due to the fact that rolling out a new OS in a company enviornment isn't the simple idealistic thing that Apple believes it is. Point in fact is that Canon Inc. has finally released drivers for 10.7 for the Canon T1 Rips. These drivers are so primitive that they don't even have the ability to access the finishing attachments for the printers, so those of my users that are on 10.7 can't collate or staple.
Right now I am between a rock and freaking hard place, I can't update the OS because my drivers don't work, AND with 10.6.8 and Photoshop I get the deleted file bug that this thread is about.
BTW.. wanna know something more crazy???!! Only in Photoshop... get this... at some point when someone is working in a file, they do something, and the file is deleted and kicked out to my server, into my Diskkeeper Undelete folder (this piece of software has been my saving grace for years) the users can still get to the file via the "Open Recent" Drives me up the wall....
-
181. Re: could not save because write access was not granted (Mac OS)
Kurt Lang Mar 28, 2012 10:58 AM (in response to JohnKGibson)My problem is that I don't have the flexibility of going to server 10.7.3. We are running Windows 2008 with Extremez-IP...
Oh, no doubt Lion Server is not feasible for all situations. In Apple's usual mode of simplifying their software, they made Lion Server too simple. Which is why I noted: "It's also a very simple setup for a small business that may not be a feasible fix for a larger company." Lots of IT folks have been complaining about the loss of Extremez-IP support and other functions. LS works for me because our need is very simple. We run file sharing and the firewall, nothing else.
As a larger company, I have to evaluate how each OS update is going to affect our workflow, and the loss of Save As in Lion, along with how apple is handing the versioning, gives me pause and I have to see how it interacts with our server and software.
I do that here, also. I'm a rather long time member at Apple's forums, and it's almost comical. Every time a major version of OS X comes out, people are screaming that xxxx stopped working. They use their Mac for their business, and how are they supposed to get work done? Invariably, someone states the obvious. "Uh, you use your Mac for a living, and you jump on a point zero release of an OS without testing it, or have a backup you can restore to get back to your previous state?"
And don't even get me started on the insanity of Versions/Autosave/Duplicate. Absolutely the worst idea I have ever seen for a work OS. My Mac is NOT a gigantic iPad. I will save my data when I want to! Fortunately, so far, only Apple's own apps force the user to use the new paradigm. An app has to be written to use the new functions. And even then, it can be turned off with simple preferences. Note Open Office and Graphic Converter for examples. Why Apple chose not to make this an app by app, or global option defies logic.
Note to Chris Cox: Please, please, pleeeeaaase don't ever release Adobe's software without a way to disable this nonsense.
Right now I am between a rock and freaking hard place, I can't update the OS because my drivers don't work, AND with 10.6.8 and Photoshop I get the deleted file bug that this thread is about.
Yup. I thought my post may be helpful as I am still running 10.6.8 on both Mac Pros with CS 5.5. Only the server was upgraded to Lion and so far (knock on wood), the issue seems to have been solved.
Another one of those forced upgrade fixes is with fonts. I didn't even start using Snow Leopard on a day to day basis until 10.6.3, when they finally had most of the font bugs fixed. And they were awful! 10.6.4 really cleaned up all but one issue. And that was certain fonts with characters that didn't contain outlines, but instead referenced other characters within the font for their shapes. These fonts would show no character for those positions. The same fonts worked in Leopard and earlier, but Apple had to completely rewrite the font engine for Snow Leopard to make it 64 bit. So what happens? Apple finds the problem and fixes it in Lion. Do they apply the same fix to SL, even though they know what it is? NO!
-
182. Re: could not save because write access was not granted (Mac OS)
Cat Killian May 1, 2012 7:17 AM (in response to Chris Cox)I tried CS6 Beta and the issue is resolved. No longer getting the "could not save because write access was not granted" error.
-
183. Re: could not save because write access was not granted (Mac OS)
Chris Cox May 1, 2012 8:29 AM (in response to Cat Killian)Not resolved - it still happpens sometimes due to external factors, but we tried a couple of strategies to minimize it.
-
184. Re: could not save because write access was not granted (Mac OS)
carlsbadphotographer May 6, 2012 10:28 PM (in response to Chris Cox)So from what I can read above, I can not use my copy of Photoshop 5 on my iMac since I cannot find a way to save any changes I make. Is that correct? Which means I have wasted hundreds of dollars in buying Photoshop 5 for my iMac. So unless I am going to switch to a PC, I should not buy Adobe Photoshop for the Mac. Will you exchange my Mac copy for a PC copy of Photoshop 5 Extended? Seems silly but that seems to be the only option unless I want to have all the money invested just going to waste. I am serious about exchanging the product for a PC version. Can I do that? Thanks.
-
185. Re: could not save because write access was not granted (Mac OS)
Marian Driscoll May 7, 2012 2:40 PM (in response to carlsbadphotographer)carlsbadphotographer wrote:
So from what I can read above, I can not use my copy of Photoshop 5 on my iMac since I cannot find a way to save any changes I make. Is that correct?
No. That is not correct. The issue discussed above relates to saving to a network. You can still save files to your iMac.
If you want to move to Windows, you can contact Adobe Customer Service and ask for a 'crossgrade'.
-
187. Re: could not save because write access was not granted (Mac OS)
carlsbadphotographer May 7, 2012 4:40 PM (in response to Marian Driscoll)I am working on an individual iMac in my apartment. My photos were on an external drive. CS5 would not allow me to save the changes I made to the photos as discussed in this thread. I copied photos to the desktop and then made changes and was able to save the changes to the desktop. Why will CS5 not let me save directly to the hard drive where the photo originated, when that is where it opened the file from? Thanks.
-
188. Re: could not save because write access was not granted (Mac OS)
bretperry May 7, 2012 4:56 PM (in response to carlsbadphotographer)Is it just a normal Firewire or USB drive -- not connected by ethernet nor by wireless but only using a Firewire or USB cable?
If you are not using ethernet or wireless, are the permissions OK? -- do you have write permissions for the file on external?
-
189. Re: could not save because write access was not granted (Mac OS)
Chris Cox May 7, 2012 5:02 PM (in response to carlsbadphotographer)That sounds more like you just had a real permissions problem - not a mystery problem.
You can give yourself read/write permission on the drive, or ignore all permissions on the external drive.
-
190. Re: could not save because write access was not granted (Mac OS)
carlsbadphotographer May 7, 2012 5:07 PM (in response to bretperry)The drive is USB and connected by a cable. Where do I look for the permissions for ethernet or wireless and for permission to write for the file on the external?
Thanks.
-
191. Re: could not save because write access was not granted (Mac OS)
bretperry May 7, 2012 5:17 PM (in response to carlsbadphotographer)Click on the file on the external drive to select it and choose "get info" from the file menu, look under sharing and permissions (click little triangle to show sharing an permissions if needed) then make sure that YOU have read and write permission.
You should be able to click on the items in the Privelge column to select read & write for yourself. If it says you don't have permission to change the setting, then you may need to log in as an admin using an admin account (assuming You are not an admin).
-
192. Re: could not save because write access was not granted (Mac OS)
Kurt Lang May 8, 2012 5:25 AM (in response to carlsbadphotographer)USB and Ethernet have nothing to do with each other.
If you normally work off the external USB drive, and have no real reason to have permissions on it, do this:
Highlight the drive's icon on your desktop and press Command+I (Get Info). You will get this dialogue box:
Click the lock on the lower right. This will cause your admin password dialogue box to open. Enter your admin name and password. This will unlock the settings. Then you can put a check mark on the box at the bottom next to Ignore ownership on this volume. Close the Get Info box.
With no restrictions, you will never see another message about permissions on that drive.
-
193. Re: could not save because write access was not granted (Mac OS)
Marian Driscoll May 8, 2012 5:54 AM (in response to carlsbadphotographer)You should also check the format of the external drive. Unless you install MacFuse, Mac OS cannot write to NTFS drives. You can only access NTFS as read-only with a plain installation of OS X.
Have you ever been able to write to this external drive?
-
194. Re: could not save because write access was not granted (Mac OS)
eclectic4 May 16, 2012 7:27 AM (in response to Marian Driscoll)"Adobe specifically does not support saving over the network. Adobe has a product called Version Cue specifically for managing shared files and file versioning."
This has been our mantra to all of our Adobe CS customers. If you work directly off the server otherwise, this stuff will happen.
-
195. Re: could not save because write access was not granted (Mac OS)
photosbyoz May 24, 2012 12:21 PM (in response to sean-gloss)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
-
196. Re: could not save because write access was not granted (Mac OS)
ssprengel May 24, 2012 12:25 PM (in response to photosbyoz)You can move your Preferences window down on your computer by using the keyboard:
Alt-Space -> M ( -> down-arrow multiple times) -> Enter
-
197. Re: could not save because write access was not granted (Mac OS)
FramestoreLondon Jun 1, 2012 10:29 AM (in response to Chris Cox)First of all, I personally would like to thank Chris for his continual patience with this topic. Over the years, across different version and file servers (all of our servers are nfs automounts), we have intermittently seen file corruption and we all know how frustrating this can be, I believe Chris is as frustrated as us and putting this issue to bed would be fantastic for all. As Chris suggests this is an OS bug, I can understand how it can be incredible hard to work around this with an effective solution for a software provider. I would suggest that maybe the best solution would be a good check-in/check-out system inside of Photoshop and I'm not talking about one that file locks, this just unnecessarily complicates the situtation.
What I'm suggesting is PS having the ability to save the files locally for you and all subsequent file use and saving is handled locally. At some point, inside PS, you may choose to resubmit (copy the files back) to the server, keeping the local copies. So we no longer are working with a temporary local copies that are deleted immediately after a save, but actual visible copies. Preferences could allow for where to save the files and maybe even how long to keep these copies for. A failed submission back to server wouldn no longer matter; the user still has their local copy, untouched. The check-in/out system will track where files were opened and default to resubmit back to the same location.
With little effort, I can add another drive inside a Mac Pro to allow for multiple local copies with a retention period, but I can't repair a corrupt file.
We try to persuade our user base to manually do this process, but often the files wont get saved back for a day or two or they may ignore the advice as they want to make sure that the saved versions are always on the server and so work directly from the server. With a simple resubmission window, I could see our users regularly saving files back to servers and having a much happier experience overall, with minimal risk.
-
198. Re: could not save because write access was not granted (Mac OS)
bretperry Jun 1, 2012 10:46 AM (in response to FramestoreLondon)From what I've read, Photoshop CS6 has auto-recovery, so it does save a local copy of the file as backup, no?
-
199. Re: could not save because write access was not granted (Mac OS)
RigbyDesigns Jun 11, 2012 12:09 PM (in response to Chris Cox)I've been experiencing issues with saving some files to both a Mac Server (Lion) and a Windows 2008 server. AFP, SMB, ExtremeZ-IP (on Windows server) all do not resolve the "cannot write file" issue. I often have to save the file twice, with the file disappearing after the first failed attempt.
However, I did recently discover three things: 1) If i open a file from the "Open Recent" menu in Photoshop, and save the file after, there is no issue. 2) If I open a file from the FInder, but then close the finder window with the file I just opend, I can save the file. 3) If I turn off "Show preview column", I can save files with no issue.
This all sounds like its a Preview.app issue - or MacOS thumbnail/preview issues and saving over a network with Adobe causing a conflict. Can someone try this if they are experiencing the " Could not save because write access was not granted" issue and verify if this solves the write problem?







