Photoshop CC: Cannot save anywhere but a local drive

  • 6
  • Problem
  • Updated 4 days ago
  • (Edited)
First let me start by saying, please don't tell me Photoshop and other Adobe apps don't officially support writing to a server. In our small business, and in those I worked for where they had lots of prepress technicians, working off of a server has been the norm for over 30 years.

I don't know if this affects Windows users, but I'm guessing not, given the results of hours of testing here.

There is a problem in Mojave. Or more specifically, Mojave and Adobe's apps.
No matter how you connect to any remote device, the Adobe apps will randomly (and often) say you can't save the file, or, write access was not granted. Doesn't matter if it's a server, or even just a shared folder on another Mac.

I had rather recently made Mojave my everyday OS on a 2010 Mac Pro. Saving files open in Photoshop back to the server was hit and miss. Mostly miss. I booted into High Sierra to see if that was the difference, rather than the server. Yes! The exact same, up-to-date version of Photoshop CC 2019 can save a file you're working on over and over without a single error message. But as soon as someone else logs into the server from a Mac running Mojave and opens a file with Photoshop or other Adobe app, the files of the folder that person is in get locked (or something). We cannot be in the same folder. Not even the Mac running High Sierra. As soon as the user with Mojave disconnects, all error messages go away for the High Sierra user.

Locked files (or whatever Adobe's apps, or Mojave are doing), don't just affect the other user, the problem also affects yourself. You can be the only person connected the server, and as long as you're booted to Mojave, you cannot work from the Adobe apps without getting messages that you can't save a file.

When these write errors occur, you end up with hidden junk files that get left behind in the folder. Depending on how you connected to the server, either .afp.deletedxxxx or .smb.deletedxxxx files. The xxxx being a number. These can accumulate by the dozens rather quickly, eating up lots of server space as they're the same size as the image you were working on. Some will be removed by the server when you dismount. Others you have to get rid of manually.

I don't know who's really to blame here, but since it seems to be only the Adobe apps that cause this issue while in Mojave, then I would say it's Adobe that has to figure out what their apps are doing wrong. From the messages you get, it would appear the Adobe apps aren't releasing files after completing a write. So the next time you try and do a save of your progress, it won't let you. Photoshop hasn't released the file, so neither can the server. Bingo, bango, bongo, you get write error messages. That's my guess, anyway.

Apple will also be getting this bug report. Mainly because testing points both ways. It could just as easily be Photoshop is releasing files after a write, but Mojave isn't. But from Mojave, I can be in Quark XPress, and literally any other non-Adobe app and write back to server all day long. It's only the Adobe apps that fail, and lock other users out of an entire folder. But at the same time, the exact same version of Photoshop CC has zero problems writing to the server in High Sierra or older OS. So then it appears Mojave is the problem.

One way or the other, the combination of Mojave and Photoshop CC makes it impossible to work directly off the server. You haver to copy files you're going to work on the desktop, then copy them back to the server when you're done. This is time consuming and almost makes having a server pointless.

Our new 2018 Mac Mini can of course only run Mojave, which makes it nearly impossible for us to work off the server together.

We've tried having the Mac running High Sierra connect to the server via AFP, and the mini as SMB, but that makes no difference. The main issue is if you're using the Adobe apps in Mojave, you literally cannot reliably save a file from within the app anywhere but to a local drive. Doesn't matter if anyone else is using the server. If you're in Mojave, you cannot write to any server or shared drive without experiencing write errors. Worse, just being connected affects everyone else whether the other Macs are using Mojave or not.

For the time being, I've gone back to High Sierra on the older Mac so at least I can write to the server without issue (when I'm the only one on it).
Photo of Kurt Lang

Kurt Lang

  • 28 Posts
  • 0 Reply Likes

Posted 6 months ago

  • 6
Photo of Zarushura

Zarushura

  • 5 Posts
  • 0 Reply Likes
Just ran into this problem today with my computer on High Sierra and another person who has upgraded to Mojave. We also have Synology Diskstation servers.
Photo of Kurt Lang

Kurt Lang

  • 25 Posts
  • 0 Reply Likes
Sorry to hear you've run into the same Mojave issue. You'll find that it doesn't have anything to do with the Synology server itself. You can set up a shared folder on your Mac, have a Mojave user log into it with your own full, admin credentials, and you'll have exactly the same write errors.
Photo of James Thibault

James Thibault

  • 2 Posts
  • 0 Reply Likes
I tested with PathFinder to replace OS X Finder, and the problem no longer exists.


James
Photo of Peter Reilly

Peter Reilly

  • 1 Post
  • 0 Reply Likes
I had the same issue, using Photoshop 2019 on a macOS 10.14.x iMac Pro, trying to save to a Western Digital MyCloud NAS.  (The NAS is brand new, and on the latest firmware.) When I used afp://10.0.66.20/ShareName it worked and saved as expected.  When I used SMB:// or CIFS:// it did not work.  BUENA SUERTE
Photo of KIRK FETZER

KIRK FETZER

  • 3 Posts
  • 0 Reply Likes
I've tested the workaround turning Preview off in the Finder windows when viewing in Column view and this workaround has worked for Mohave and High Sierra computers saving to QNAP NAS and Apple Server 10.13.

Even using the space bar to preview a file, causes the issue to return for that file, so really a clunky workaround, given it's photos we're talking about here. Not being able to quickly preview photo files in Finder is really a problem. Dragging a photo or folder of photos over my Adobe Bridge icon to preview them works as a bit of a replacement for Finder Preview.
Photo of Kurt Lang

Kurt Lang

  • 28 Posts
  • 0 Reply Likes
Yay! A solution.

Actually, Pierre Lepeer mentioned this a ways back, and we did try his suggestion. But at the time, it didn't help and we hadn't gone back to that possible solution for a while.
Well, somewhere within some point updates to the CC apps, Mojave and a very recent, large update to the Synology NAS, it now works!

I was experimenting again today, and noticed we no longer had any problem working out of the same folder with TIFFs, JPEGs and other file types. Only .psd images would continue to throw out write errors. So then I wondered why only that file type was different. Per Pierre's note:

Have you tested? In PS, go to Preferences, File Handling and in the dropdown menu Image Previews choose Never save.On our Macs (mojave), it solved the problem.

I went back into Photoshop's settings and once again turned that setting off:



All write errors stopped! And no leftover .afp.deletedxxx files.

Having thumbnails disabled is no big deal anyway. You still get a desktop icon and a preview of that image in the Open dialogue box. So it's no loss to have it off.

I wonder if it causes an error because, maybe, that check box is a leftover for the old thumbnail the Adobe apps used to write to the resource fork. As of CS6, the Adobe apps don't even write a resource fork, per Apple's instructions all the way back to Snow Leopard that the resource fork had been deprecated and all vendors were supposed to stop using it.
(Edited)
Photo of Grant Graham

Grant Graham

  • 5 Posts
  • 0 Reply Likes
Hi Kurt,
Just to confirm with your preferences in Photoshop - you only had to un-tick "Thumbnails" and you did not have to set Image Previews to "Never Save". So just disabling thumbnails was enough, is that correct?
Photo of Kurt Lang

Kurt Lang

  • 28 Posts
  • 0 Reply Likes
Correct. Only the Thumbnail option was turned off. Image Previews is left at Always Save.

It wasn't until we noticed TIFFs and JPEGs had no overlap problems when working out of the same folder that I read through this topic again to see if I had missed a tip entirely, or just needed to try them again.

This was really bugging us since our main client wants all of their files kept in .psd format, and that was our constant save issue if anyone using Mojave was in the same folder as anyone else.

Our mistake was misinterpreting some of the suggestions in this topic because there are numerous places in the OS called thumbnail, or preview. We had been turning off desktop previews/thumbnails in various places at the OS level, which didn't do anything. It wasn't until I re-read Pierre's reply and saw he was (obviously, too) talking about Photoshop's preferences. Not the Finder. As soon as we turned that check box off on all Macs, all write issues disappeared.

Since you can sometimes work out of the same folder for a few saves before getting the error, we kept at it with some test images in the same folder for about 15 minutes, making one small change after another and saving after each change. We were convinced the problem was solved after over a couple hundred save actions between us with .psd images without a single error message.
(Edited)
Photo of Grant Graham

Grant Graham

  • 5 Posts
  • 0 Reply Likes
Thanks for confirming that Kurt, we are testing that configuration and it seems to be working too so far. :-)
Photo of Kurt Lang

Kurt Lang

  • 28 Posts
  • 0 Reply Likes
Great to hear it appears to be consistent!

I never would have thought it would end up being a single check box in Photoshop. When you can work out of a folder by yourself with that check box on in any version of the Mac OS and have no errors, you just don't think Photoshop is the problem. It must be Mojave since that's the repeatable issue.

Is Mojave the issue in their somewhere? I still think so. This problem of being unable to work in the same folder didn't exist before then (for us). But again, Apple has long made it known to vendors the resource fork is dead, and that's where the specifically named Thumbnail images went. And if that's the case, why is that check box even in Photoshop's preferences yet?

We could go in circles all day making these types of assumptions. And that's all they are when we don't really know what's going on in the underlying code of the OS and Photoshop. I'm just glad (really glad), it turned out to be a simple solution.