-
240. Re: could not save because write access was not granted (Mac OS)
PAULINE OLIVER Sep 8, 2012 10:17 AM (in response to Noel Carboni)No worries Noel I am not about to format my ex.HD as I have so much important data on it. I just cannot understand that it has been used with my Mac and PS4 extended with no problem until the upgrade to PS6 and a new MacBook hard drive.
Pauline
-
241. Re: could not save because write access was not granted (Mac OS)
conroy Sep 8, 2012 10:49 AM (in response to PAULINE OLIVER)Pauline, I'll assume that you maintain at least two backups of all valuable files on the drive. Are you aware that you can reformat the drive to an Apple file system and restore its files from one of your backups? Unless you need to write to that drive with a Windows computer then it would be better formatted with Apple's HFS+ Journaled file system.
-
242. Re: could not save because write access was not granted (Mac OS)
PAULINE OLIVER Sep 8, 2012 11:57 AM (in response to conroy)Thank you Conroy. Yes I do save and use from both formatts. Do you think it would be any good to phone Adobe next week?
-
243. Re: could not save because write access was not granted (Mac OS)
Kurt Lang Sep 8, 2012 12:15 PM (in response to PAULINE OLIVER)As Noel noted, Tuxera NTFS allows you to write to NTFS formatted drives. Something OS X cannot do by itself, it can only read. If your external drive is formatted for Mac, then Tuxera won't do anything for you regarding the drive.
By PS4, can I assume you mean PS CS4? Version 4 would be a very old version of Photoshop, which cannot run on any Intel based Mac under OS X. But yes, the issue of .afpdeleted and permissions denied messages appeared with CS5 and forward. That's why you don't see that behavior with CS4.
-
244. Re: could not save because write access was not granted (Mac OS)
Kurt Lang Sep 8, 2012 12:30 PM (in response to Chris Cox)Do you have a display calibrator that changes the profile all the time (like huey's in response to ambient light changes)?
I do use ColorNavigator, which is supplied with EIZO monitors, but I only create fixed profiles with it, and store them in the /Library/ColorSync/Profiles/ folder. The one you see in the Displays folder is the profile OS X automatically retrieves from the monitor's firmware. As I'm sure you know, you can't stop it from doing that, I just don't use them. Why they get these ridiculously long names, I couldn't tell you.
The updater or OS do update some cache files (/Library/Caches/com.apple.Components2.LocalCache.QuickTimeComponents , /System/Library/Caches/com.apple.Components2.SystemCache.QuickTimeComponents)
And the updater or OS reset a lot of plist files, and /var/db files that I don't know the purpose of.
I was looking for anything to do with QuickTime, also. They're both supposedly just cache files, but any trashed cache file, unless cleared, can cause problems every day it exists. Not sure why a reinstall of the OS would change them. Installing the CS6 suite changed them somehow, and the OS reinstall did something to change them again? Hard to say since cache files tend to change constantly by their very nature anyway.
Also noticed the seemingly unusual amount of updated .plist files. I was mostly surprised to see how many .plist files were in the hidden /private/var folder. Especially ones with names virtually identical to user account .plist files. Such as AddressBook.
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?
That is a great catch! I overlooked that one. You may be onto something there.
-
245. Re: could not save because write access was not granted (Mac OS)
conroy Sep 8, 2012 12:51 PM (in response to PAULINE OLIVER)PAULINE OLIVER wrote:
Thank you Conroy. Yes I do save and use from both formatts. Do you think it would be any good to phone Adobe next week?
Sorry, I've absolutely no idea whether a phone call to Adobe will help.
-
246. Re: could not save because write access was not granted (Mac OS)
Noel Carboni Sep 8, 2012 2:32 PM (in response to conroy)That was very nicely put, Conroy. I'm proud of you.
Based on recent anecdotal evidence of what other people are getting out of Adobe Customer Support, that is a VERY good question.
Pauline, you might want to consult with an Apple Genius. It sounds as if maybe you have problems more basic than Photoshop with your setup. You might just be able to take your external drive to an Apple Store, if taking all the computer hardware is unweildy. Disclaimer: The only thing I've been to an Apple Store and consulted with an Apple Genius for was a defective iPhone, which they fixed by replacing it, so I don't know whether they're really at IQ 140 or just have the tee shirt.
-Noel
-
247. Re: could not save because write access was not granted (Mac OS)
Chris Cox Sep 8, 2012 4:33 PM (in response to Noel Carboni)>> just have the tee shirt.
yeah, that.
-
248. Re: could not save because write access was not granted (Mac OS)
bretperry Sep 8, 2012 5:13 PM (in response to PAULINE OLIVER)Pauline,
You can use Disk Utility in Utilities folder of Applications folder to see how your drive is formatted. (look don't format
Open the Disk Utility program and select your hard drive on the left.
Your (formatted) drive will be the one that has it's usual name and is indented from the raw drive.
With your drive (name) selected, at the bottom it will say "Format:"
If it is NTFS, how odd. You must have had special software installed on your old Macs to write to that format.
If it is a Mac format, Mac Extended (journelled or not) it could be many things but likely permissions. Try repairing permissions then in Disk utility, but probably you will need to reset them further.
Try File… Get info on the drive or a folder on it and see if you have read/write permissions under "Sharing and Permissions" (click triangle to see if needed). If you have permissions, then it I something else.
If you don't have permissions, You can change permissions to yourself with Get Info or get an app for changing permissions to make it easier.
-
249. Re: could not save because write access was not granted (Mac OS)
Kurt Lang Sep 9, 2012 1:36 PM (in response to bretperry)To expand/add to bretperry's notes:
You don't need to launch Disk Utility to check a drive's format, though that does certainly work. Simpler is to just highlight the drive's icon on the desktop and press Command+I, or choose Get Info from the menu bar. It's format will be listed in the Get Info dialogue box, as show next:
In relation to that, I've never seen any need to have permissions on for either internal or external drives which are not the startup disk. At the bottom of the same Get Info box, click on the icon of the lock. Enter your admin password to allow changes to be made to permissions settings. Turn on the checkbox for, "Ignore ownership on this volume". Close the Get Info box. You'll never have a read/write problem again on that drive since nothing is treated as "owned".
-
250. Re: could not save because write access was not granted (Mac OS)
OneCustomerIT Nov 5, 2012 12:16 AM (in response to Kurt Lang)Hi all.
We have been hit by the same kind of issue while saving Photoshop or Indesign files onto NFS shares, NFS shares being stored on a NetApp storage bay. Both software throw an error saying there are insufficient privileges to save files. We've been able to nail down the issue.
The basic security model of UNIX boxes only allows the sole owner of a file to change it. Since only 3-4 people need to work on each other's files in our case, we didn't use ACL but used NFS sharing property all_squash (see http://www.troubleshooters.com/linux/nfs.htm ) so that the owner of files placed on the share are owned by the NFS anonymous user, access is restricted to the IP addresses of the relevant machines.
The "insufficient privileges" issue while saving files occurs systematically when NFS uid squashing is enabled on the NFS server. Without squashing Photoshop and Indesign both save their stuff without moaning. This issue hence boils down to either how these programs manage the save function or how the corresponding MacOS API works. This certainly has to do with either checking or forcing the owner of files while saving. The Preview mode has little to no influence.
We're currently trying ACLs on NFS shares to temporarily work around this major annoyance.
Hope this helps.
-
251. Re: could not save because write access was not granted (Mac OS)
Chris Cox Nov 6, 2012 12:12 AM (in response to OneCustomerIT)That does sound like an OS bug, where it is incorrectly reporting the permissions in that case.
Hmm, I bet it's one of the known OS bugs. Try turning off all thumbnails/icons in preferences (to eliminate resource fork writing) and try saving to the NFS volume.
-
252. Re: could not save because write access was not granted (Mac OS)
OrtisLaboratories Nov 6, 2012 2:39 AM (in response to Chris Cox)(Sorry for replying with a new account, the other one doesn't seem to work anymore.)
@Chris:
Fact is:
- without all_squash Photoshop actually saves files *even* with preview/icon/thumbnail enabled,
- with all_squash Photoshop throws this error message *even* with preview/icon/thumbnail disabled.
That's what I meant «the preview mode has little to no influence». Besides only Photoshop (and eventually InDesign) throw these errors (when saving onto NFS shares with UID squashing enabled). We've used a few other applications (like TextEdit or Finder, for instance) and no error occurs regardless of whether UID squashing is enabled or not.
-
253. Re: could not save because write access was not granted (Mac OS)
Chris Cox Nov 6, 2012 3:36 PM (in response to OrtisLaboratories)Hmm, the known permissions bugs were mostly resource related -- but there is another outstanding bug that fails to map ACLs to Carbon/Cocoa permissions correctly for all file forks, and I think it is NFS specific (at least according to what we've heard from Apple so far).
Photoshop does more error checking when saving - because we've seen so many problems in the past, and seen other apps fail to save correctly in the same situations. So we tend to catch these errors when other apps don't (and they will sometimes silently lose your file). We've been trying to work with Apple on these issues, but it has been difficult.
-
254. Re: could not save because write access was not granted (Mac OS)
OrtisLaboratories Nov 7, 2012 12:42 AM (in response to Chris Cox)Chris Cox wrote:
Photoshop does more error checking when saving - because we've seen so many problems in the past, and seen other apps fail to save correctly in the same situations. So we tend to catch these errors when other apps don't (and they will sometimes silently lose your file). We've been trying to work with Apple on these issues, but it has been difficult.
I think I understand the motivations just that in this case, our issue with UID squashing also results in losing the file. With UID squashing enabled, the program actually has write access to the resource, which is why it's so frustrating. It then zeroes the file and throws the error. This is as annoying as corrupting the file in the cases you referred to, I guess.
-
255. Re: could not save because write access was not granted (Mac OS)
KG Wong Dec 28, 2012 3:16 AM (in response to OrtisLaboratories)Hi all,
being following this thread since beginning and tried all suggested possible solutions but non of these solve this problem in my environment (see my environment below)
But my latest testing may have solve my problem of psd file open from network drive (being mounted using afp or smb) disappear after save action. All iMacs in my studio are installed with PS 5.1 and all of these iMacs have are showing the same if open psd from network drive, so all my testing are performed using PS 5.1 and all failed as expected. But recently i install one of the iMac with Photoshop 5 Extended, and suprisingly this problem solved (psd still there in network drive after saved). And i have been using the same psd in same network drive location for previous testings all failed but it is ok with PS 5 Extended. The very same psd if save using PS 5.1 standard, same problem happening again. Now i am trying to install PS 5 Extended into another iMac just to confirm.
This information might be useful for you guys too. As i understand the only different of PS standard and PS Extended is Extended support 3D creation and editing. Anyone can provide more in-depth explanation will be good.
Environment:
Client Machine
OS: OS X 10.7.5
Photoshop version: CS5 Extended
Network Drive
Type: Synology Diskstation DSM 3.1
Protocol: tried afp and sbm, all works if psd open using CS5 Extended
thanks
-
256. Re: could not save because write access was not granted (Mac OS)
Chris Cox Dec 28, 2012 10:13 AM (in response to KG Wong)Extended and Standard are the same app, and don't change the file save behavior in any way.
The only difference is that the extended serial number enables some additional features.
I think that we now have a good handle on the causes of these MacOS filesystem problems, and are testing workarounds to avoid those problems.
-
257. Re: could not save because write access was not granted (Mac OS)
KG Wong Dec 28, 2012 11:07 PM (in response to Chris Cox)Hi Chris,
thanks for replying. but strangely by using Extended version did solve my problem. will be great finally know that we got some workaround for this problem. hope the solution also applicable for PS 5 or 5.1.
-
258. Re: could not save because write access was not granted (Mac OS)
OrtisLaboratories Jan 3, 2013 12:54 PM (in response to Chris Cox)Further investigations, we've switched from NFS to CIFS and we're experiencing other issues. All boil down to using Adobe products on Mountain Lion. To summarize:
- NFS yields access and permissions errors.
- CIFS yields errors such as «Cannot save xxxxx.psd because of an unexpected end of file.» Worse: the file is truncated to zero byte length. If you exit Photoshop, the file is lost. The user must have the reflex to save *twice* to not lose her work!
All these issues occur when the following conditions are all met on remote shares:
- Adobe products (Photoshop, Indesign...)
- running on Mountain Lion (10.8.x)
- ownership on the remote share is forced (e.g. either with NFS id squashing or SAMBA server configuration options "force user" or "force group").
We have fallen back to using the above mentionned Adobe products on MacOS Lion (10.7.x) but not Mountain Lion (10.8.x).
I personally believe that is enough to qualify this annoyance "serious", right ?
-
259. Re: could not save because write access was not granted (Mac OS)
Chris Cox Jan 3, 2013 12:55 PM (in response to OrtisLaboratories)That does sound like you're hitting a couple of the known MacOS bugs with file servers.
We're still trying to work around them, and Apple is still trying to get some of their bugs fixed.
-
260. Re: could not save because write access was not granted (Mac OS)
maw2013 Jan 21, 2013 12:58 PM (in response to Chris Cox)I've started having this issue, too, with a new NFS export from a Linux server. My end users are in a mix of 10.6.8 and 10.7.5, and all are using CS5.
Here's what I've learned:
- We are exporting the share via NFS with ID squashing (UID 65534, GID 12 --aka Everyone on Macs).
- All other CS5 apps (including InDesign) do not exhibit this problem.
- Every other Mac app I've tried can write to the folder without a problem.
- Save for Web & Devices does not exhibit this problem, it can write to the same folder that the normal Save function cannot.
- It is entirely a problem with group permissions to the folder, or a specific file if Photoshop is trying to overwrite an existing file.
- Photoshop will not save a file if the user has read/write permissions, but the group only has read permissions.
- Photoshop will save to a file if the user and the group have read/write permissions.
- When Photoshop cannot write to the file, it will create a new 0-byte empty file with an April 8, 2037 6:53pm timestamp in its place, or delete the existing file.
- If I create (in Terminal) an empty filename.psd file (via touch) and then chmod that file to 664 (rw-rw-r--), Photoshop will overwrite that file, as it should. If that file has 644 permissions, Photoshop will not save over that file.
- Turning icon previews off in Finder preferences makes no difference.
- I have also tried this with CS5.5 (Photoshop 12.1) and CS6 (Photoshop 13.0) with the same results.
From reading this thread (from the start!), I've learned that Photoshop farms off the saving of the file to OS X, and that leads me to think that the OS X user that runs that saving process doesn't belong to the "everyone" group (GID: 12) on the Mac that the user using Photoshop belongs to.
Message was edited by: maw2013
-
261. Re: could not save because write access was not granted (Mac OS)
Chris Cox Jan 21, 2013 6:28 PM (in response to maw2013)We've been talking to Apple about this, and especially about the NFS issues -- they've found some of the causes (yay!), but we don't have any estimate for when a fix will be available.
Meantime we're continuing to investigate and test various workarounds.
-
262. Re: could not save because write access was not granted (Mac OS)
captain1944 Jan 27, 2013 11:30 AM (in response to Chris Cox)IN SUMMARY, if that is posible, what is the workaround fix? Is it to re-install mountain lion? If so, will this delete all of my files and applications or will it simply provide a new mountain lion? I have used cocktail to help, but now this fix has a short life so I would like a more permanent fix without having to rebuild my entire desktop. Thanks
-
263. Re: could not save because write access was not granted (Mac OS)
Chris Cox Jan 27, 2013 11:46 AM (in response to captain1944)As a programmer imagining all the ways the file system bugs could occur, I highly doubt that reinstalling the OS would change their behavior. But I don't know the exact nature of all the OS bugs, so I can't say for sure.
-
264. Re: could not save because write access was not granted (Mac OS)
captain1944 Jan 27, 2013 11:49 AM (in response to Chris Cox)thank you but is the the fix thathas been suggested?
-
265. Re: could not save because write access was not granted (Mac OS)
Chris Cox Jan 27, 2013 11:54 AM (in response to captain1944)The only OS reinstall advice I can find in this thread is for an unrelated problem (OS bug with thumbnails).
-
266. Re: could not save because write access was not granted (Mac OS)
captain1944 Jan 27, 2013 11:58 AM (in response to Chris Cox)so there is no other fix at this time?
-
267. Re: could not save because write access was not granted (Mac OS)
Chris Cox Jan 27, 2013 12:07 PM (in response to captain1944)Please read the thread. We're working on workarounds for Apple's bugs, and Apple is slowing identifying the cause of their filesystem bugs but we don't have an ETA for their fixes.
-
268. Re: could not save because write access was not granted (Mac OS)
PmgRWB Mar 4, 2013 7:07 AM (in response to Chris Cox)We are seeing similar issues, is there a bug ID number that we can link to on this with either Adobe/Apple support?
-
269. Re: could not save because write access was not granted (Mac OS)
Chris Cox Mar 4, 2013 11:28 AM (in response to PmgRWB)No, there is no single bug ID for this.
-
270. Re: could not save because write access was not granted (Mac OS)
Simon Joh4nsson Apr 23, 2013 5:29 AM (in response to Chris Cox)Hi there,
we have isolated a scenario that can result in dataloss or error messages mentioned in this thread.
Issue: Saving from Adobe Photoshop to Xsan 3.0 Volume or AFP re-share of Xsan volume causes error messages and dataloss.
Configuration:
Xsan 3.0 on servers running 10.8.3
Xsan volume with Native Extended Attributes enabled.
Clients running 10.8.3, Adobe CS6 Photoshop 13.0.4
Troubleshooting / steps to reproduce:
On Xsan clients (with Xsan 3 volume mounted):
- Save of new file from Photoshop results in error:
"Could not save “filename.psd” because of a disk error."
- Save of existing file results in no error dialog but file is removed from Xsan volume. (Ie. dataloss!)
On Clients connecting to AFP re-share of Xsan volume.
Creating new file works.
Modifying and saving the created file results in error:
"Could not save “filename.psd” because write access was not granted."
Clients can mount AFP share-points that are pointing to HFS+ volumes without any issues (which is great of course).
Workarounds:
On AFP clients:
1. Save as and rename each file you modify. (if modifying texture files or similar this is not viable due to re-linking hassle afterwards).
2. Save locally and copy file over to storage. (in this day and age this is not an acceptable workflow to suggest to clients, especially since all other Adobe apps does not experience this issue).
On Xsan clients:
1. Save locally and copy file over to storage. (in this day and age this is not an acceptable workflow to suggest to clients, especially since all other Adobe apps does not experience this issue).
Solution:
n/a?
Possibly downgrade OS on clients to 10.6 (but that leaves out newer Apple hardware)
Any ideas, suggestions, confirmation of being able to reproduce above would be greatly appreciated, this is a BIG issue for us.
Comments:
I do not really care about if this issue is Adobe's or Apple's. But since all the other CS6 applications works without any issues and this only happens with Photoshop it sure feels like it should be possible for Adobe to address this one way or another.
Since this is resulting in dataloss I also hope this will get the attention it deserves in regards to getting a fix.
Based on the history of Adobe releases it is reasonable to expect a new version of CS within the coming months. But even if it would be fixed in the next version of Photoshop it would be great to address this in Photoshop 13 as well.
-
271. Re: could not save because write access was not granted (Mac OS)
Simon Joh4nsson Apr 23, 2013 5:41 AM (in response to Simon Joh4nsson)Other sites referring to same issue as I outlined above:
-
272. Re: could not save because write access was not granted (Mac OS)
Chris Cox Apr 23, 2013 9:53 AM (in response to Simon Joh4nsson)Again, we are attempting to work around all the Apple filesystem bugs that we know about (and that's a disturbingly long list). But many of the workarounds are much more extensive than would be allowed in a dot release.
Apple is also working on fixes to some of those bugs, for future OS versions.
-
273. Re: could not save because write access was not granted (Mac OS)
Simon Joh4nsson Apr 23, 2013 10:43 AM (in response to Chris Cox)Hi Chris,
I have narrowed it down to Photoshop saving failing to work (or erasing file at attempt att save if on local Xsan volume) ONLY on Xsan 3.0 (so basically any Xsan client on 10.8, so basically all new machines from now on..)
Xsan 2.3 volumes (10.7) and earlier works fine.
As a workaround we will have to downgrade one Xsan client to 10.7 (Xsan 2.3) re-share that volume to all our other clients and disable Xsan on 8 clients until the issue is resolved.
It is great that you are trying to work around Apple filesystem bugs, especially since a lot of Pro customers using Adobe and potentially Xsan will be affected by them in general. However...
Since this does not appear to be an issue in any other Adobe product other than Photoshop the logical conclusion here is that it is not Apple's filesystem bugs causing this particular issue, but rather the way your software is written.
Have you checked / logged this in your own bug-tracking systems?
Can you reproduce the issue?
Adobes track record for fixing (or even supporting) basic saving to network / non-local storage is not great (just take the exporting larger than 4GB files to network share via Media Encoder as an example) so it would be great if Adobe could nail this particular issue before it becomes a larger one, as system admins in production houses over the world slowly migrate up their Xsan installations.
Let me know if I can provide any more info/details to help you get to the bottom of this.
-
274. Re: could not save because write access was not granted (Mac OS)
Chris Cox Apr 23, 2013 2:39 PM (in response to Simon Joh4nsson)That does sound like one of the bugs that we filed with Apple. I'm not sure of it's status.
No, the logical conclusion is usually that Photoshop does more error checking than most applications - so we catch a lot more OS errors (because we've seen so many and added additional error checking over the years).
And yes, we investigate all of these -- so far very, very few turn out to be our bugs, and almost all are reproduceable in other software once you know what is happening in the OS code.
-
275. Re: could not save because write access was not granted (Mac OS)
Simon Joh4nsson Apr 24, 2013 9:09 AM (in response to Chris Cox)Hi Chris,
so the added error checking in Photoshop (that is not added to Premiere, AE, Illustrator etc) is potentially causing dataloss on a StorNext compliant filesystem (Xsan). So the options are:
1. Go with added error checking in all apps if it is the way to go (and work with Apple to make sure your added security works).
2. Remove the "added error checking" from Photoshop since it causes issues compared to your "less safe" saving in other apps.
3. Do nothing, assume the issues are on the OS / Filesystem level and refer to Apple when your customers have issues.
1 feels far fetched, 2 is what I would like, 3 is what I fear will happen..
I don't intend to come of as a pessimist, but it is in your software this happens, you clearly have the solution in your other apps.
You most influential and important customers are the ones most lightly to work on shared storage in general and with your push into the video editing market potential Xsan customers must be a priority, so to get to the bottom of this feels like it should be a priority. As your customer I hope it is.
Once again, thanks for taking the time to reply and hopefully bring this forward internally.
-
276. Re: could not save because write access was not granted (Mac OS)
Chris Cox Apr 24, 2013 10:27 AM (in response to Simon Joh4nsson)No, the error checking is telling you about external problems that cause dataloss.
The error checking does not cause the problems, it just informs you about problems that already exist in your OS or fileserver.
Again, we have researched all the reported issues. Yes, Apple has a lot of filesystem/fileserver bugs.
No, the other apps are not a solution, they are just not noticing the problems with the OS and fileservers - so you silently lose data.
The extra error checking has been added to Photoshop because we have seen and debugged so many OS and fileserver bugs over the years, and don't want our customers to lose data if they can avoid it.
-
277. Re: could not save because write access was not granted (Mac OS)
Simon Joh4nsson Apr 24, 2013 1:07 PM (in response to Chris Cox)The irony here is of course that whatever error checking you have introduced in Photoshop, that you don't have in other apps, now is causing exactly what it was intended to resolve.
I understand that it can't be easy working with a 20+ year old filesystem like HFS that has been patched forever. And I am sure you are right that there are a lot of bugs. But in this particular case it is an issue causing dataloss. It is easy to reproduce. You have saving mechanisms in other apps that does not experience the issue.
Just to be clear, when you say:
"Again, we have researched all the reported issues."
Do you mean that you have verified *this* particular issue (Saving from Photoshop deletes file from storage if storage is an Xsan Volume mounted on an Xsan 3.0 client) and that you are isolating the best course of action to resolve it for your customers, or is that a generic answer you fall back on anytime anyone reports an issue that could be related to the OS or filesystem underneath your software?
If you have verified an issue that can cause dataloss for your customers are you considering making a tech note somewhere about it to help your customers prevent the dataloss they will definitely expereience if they update their existing Xsan infrastructure and clients?
-
278. Re: could not save because write access was not granted (Mac OS)
Chris Cox Apr 24, 2013 2:12 PM (in response to Simon Joh4nsson)I don't know what your *exact* issue is because I don't have your system.
We have spent a lot of time tracking down Apple's filesystem/fileserver bugs and working around as many of them as we can. I recall we have 3 or 4 bugs specific to XSAN, in addition to the generic remote file sharing bugs in MacOS, but I don't recall the details of every single bug in Apple's code.
The Photoshop code is not causing anything here - it is simply reporting the OS error to you.
The OS is causing the problem, Photoshop just passes along the message when the OS messes up.
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.





