Participant

質問

Having mac users with issues working directly off of SMB and AFP share with photoshop.

Forum|Forum|4 years ago
August 12, 2021
返信数 8.
12511 ビュー

Having mac users with issues working directly off of SMB and AFP share with photoshop. Using the latest photoshop 22.4.3 and mac os 11.4 with all m1 macbook pros with a supported Ethernet adapters or via wifi so the network is not really the issue. Also this error does not come up with windows 10 on the same nas and network. Getting a Could not complete request because of a disk error. So We have a Synology NAS with the latest firmware and SMB 3 /2 as well as AFP shares have been enabled. I have verified that the mac’s in question were all running on smb 2 / 3 or afp when the error occurred. It is also intermittent and does not seem to matter what protocol is running. The issue is the user will get a disk error trying to open some files sometimes off the nas directly. If the file is copied locally it works fine however. Verified it is not a permissions issue as the same files open sometimes. Are network share not supported to be used directly in photoshop ?

macOS

R

Rusty23213440pksy

Participant

I am also having this trouble. Very frustrating. Looks like it's been going on for years. What did all of you end up doing??

We have about 10 computers (older macs and a few pc's). And our 2 newly purchased Mac Mini M2 are the only ones giving us trouble staying connected to our Synology Nas. I've tried wifi and hardwired.

It disconnects when I try to save a file from Adobe Illustrator (which is the software I use everyday), or sometimes when I try to open a file.

jane-e

Community Expert

It disconnects when I try to save a file from Adobe Illustrator (which is the software I use everyday), or sometimes when I try to open a file.
By @Rusty23213440pksy

Adobe does not support saving directly to or opening directly from a NAS due to the many configurations. See the link here (also posted earlier in this thread with a screenshot) for details.

https://helpx.adobe.com/photoshop/kb/networks-removable-media-photoshop.html

It's a best practice to use Adobe's recommended workflow.

Recommended Workflow

"Technical Support strongly recommends working in Photoshop directly on the local hard disk. To prevent data loss, save files to your hard disk first. Then transfer them to the network or removable drive in the Finder or in Windows Explorer. To retrieve files, copy them in the Finder or in Windows Explorer from the network or removable drive to your hard disk. You can then open the files in Photoshop. This workflow avoids problems that occur when network system setups or removable media device drivers are incompatible with the operating system or Photoshop."

Jane

D

Darthsaiyan

Participating Frequently

That's just a lazy way out of saying "we know we can't code if our lives depended on it, so we'll tell you to change your 15-20 year old habit of doing things instead."

ABSOLUTELY Appaling way of treating customers. I've used NASes for over 15 years now, NEVER had a single problem before the introduction of these new M1-2-3 chips... so don't tell us to change our workflow, FIX THE DAMN bug in your code.

My 2 cents, getting annoyed with Adobe, Photoshop is crashgate, and when it crashes.
You want proof that Adobe programmers are incompetent?

Anything you import in your sessions, styles, brushes... name it... if the app crashes AFTER you've done that. These saves aren't kept. WHY? Why not save the state of your styles, brushes and other parameteres the MOMENT you import them?

You wanna know why? Cause they don't know what code is, even if it hit them in the face. Photoshop is based on 30yo code... it doesn't scale well to new advances like a ton of cores, simply cause at one point it should have been rewritten from scratch. But hey, that costs money, and dev that actually can code, so let's run instead off of code that wasn't all that stable to begin with 30 years ago, and keep making the app less and less reliable.

What else? Zoom tools will stop working randomly and turn to selection only. Keyboard shortcuts work randomly anyway, you bress B for brush, it highlights the brush visually, but the moment you click, you're back on your previous tool. It's HILARIOUS how buggy this app is, the more updates, the WORST it gets.

Just my 2 cents,
Do with them what you will, you always do anyway!

Chris

B

BCampioni

Participant

Guys... look what a bizzarre solution for this. I have been suffering with this issue in my office since I get a mac mini M1 in 2020.

If you change the icons visualization on macOS, the file will open without the error message. I mean, I always browsed in finder viewing my files as collums, but I noticed if I change to icons or list mode, the file will magically open.

L

Lumigraphics

Legend

This has been an issue since Classic MacOS days. Working off a server works... until it doesn't. There are too many variables with network configuration, server software, client versions, etc for this to be bulletproof.

I get it- I have a Windows PC with Bridge and Photoshop open on my desk next to a MacBook Pro with a flyer I'm working on in Illustrator, with Windows servers. I know the rules for working cross-platform but I'm still careful to work locally most of the time, and to save often to avoid data loss.

NB, colourmanagement

Community Expert

Hi, is it ONLY Photoshop?

It seems like this might be an issue best explored with Apple support,

it's very good, they call you back and can be super helpful

I hope this helps
neil barstow, colourmanagement net :: adobe forum volunteer:: co-author: 'getting colour right'
google me "neil barstow colourmanagement" for lots of free articles on colour management

fionab1933282

Participant

I'm here so I am obviously experiencing the same issue 😕😕

M1 connected to Synology NAS using SMB3. I can easily open a file from the NAS. When saving (save as) back over the same file all is well until trying to open the file again, with the 'you can't open... file locked.. blah blah' message.

I agree with JJung Photography that selecting the same file and another allows the file to open. Selecting the one offending file again returns the same error.

The only thing I have found that stops the issue is using SMB1. This is terrible as it is slow and image previews are non-existent, but it works.

I also noticed that when saving using SMB2/3 a temp file appears and disappears in the NAS folder. When using SMB1 it does not.

My thinking has been that the cache relating to SMB2/3 is holding onto the temp file and seeing the file as locked. This may be ignorant on my behalf, but a thought.

I'd be keen for anyone with a bit more knowledge on this to pitch in. Working locally is a ridiculous solution... we're not animals.

I

IngmarHansen

Participant

It is super annoying and we have this issue in our studio around 20 times a day. Everything was working smoothly (and still is on Intel Mac systems) until the day we switched to M1 Macbook Pro and Mac Studio. What always happens when the issue occurs ist that two MacOS services are crashing – com.apple.appkit.xpc.openAndSavelPanel.Service and QuickLookUIservice. When manually closing these two services in the activity monitor the system freezes, the finder crashes and the networt connection resets after a few minutes. It looks like there is some kind of permission error between these processes.

JJung Photography

Known Participant

Having the same issue here with Photoshop.

My only workaround I've found is if I open multiple files into Photoshop suddenly it'll open them vs give me one of two errors.

Would be nice if Adobe could make.an official response by now and sticky it as a known issue they're working on with workarounds? 🤔 🤔

Also the fact they're trying to say avoid using NAS is ridiculous. It worked flawlessly previously and I've never ran into any issues.

matt chew

Participant

Hi all. I've stumbled across this problem with one of the Mac's in our studio. It's the only one having the issue (out of ten M1's) and I've found some "band aid" fixes so far. We currently work off a server that has been set to smb. If the problem mac creates a photoshop file, saves it to the server, closes the file and then tries to re-open it then it shows the error message and cannot open. So what I have found so far is that photoshop won't open the file if Finder shows it with a "preview" (e.g gallery view in finder) BUT will open if I don't show a preview (e.g list view in finder). The problem M1 mac can open any file another computer creates and has no issues with other peoples files.

We've also found that switching to afp protocols has fixed the issue, but we prefer not to work in that format as it creates other issues.

F

flipdesign

Known Participant

True, not just an M1 issue, as I'm pretty sure I had this issue many weeks ago when still on 2017 iMac core i7. But this issue may have only started with Monterey.

D

DesignCoup

Participant

My office is running 5 Intel MacBook Pros that work fine.

It's the two new M1 MacBook Pros that are having this exact same issue.

I have tested this exhaustively and can confirm the issue does not exist on *our* Intel Macs.

J

Jeffrey Bodine

Participant

I do not beleive this is just releated to Apple M1. I think this is a Monteray issue, launch agent/daemon or mdworker. When I have console open and the logs running I see messages with these in it when I crash. I am on a 27in iMac and when working in InDesign or Acrobat my AFP connection to my Synology will just drop and crash my whole system. I have to use the power button to turn it off and restart. I have a ticket open with Synology and they told me some settings to try but it hasn't made a difference. They keep telling me not to use AFP but SMB is just really slow on my Synology. Just beach balls. But, this is also happening on 2 other Macs at my company that are running Big Sur.

philippl49897675

Participant

It is. Our 5k iMac from 2019 can run everything fine with the latest updated from adobe/apple.

But with our new M1 iMacs, as soon I try to place objects like PDF or AI with several pages/art boards and try to import them, nearly every time the spinning wheel from apple appears and won't stop until I get disconnected from our server (nas/synology-afp).
Meanwhile, that loading-freeze while bring the iMac to a near complete standstill. You can interact with software like chrome, but everything that has a file open from the server won't open.

I'm not a lot to play around with different settings on our server to test different settings, but it appears that many people have this problem.

Deactivating the image preview and switching to the list view in the finder seems to help so far.
But when you're in any adobe software and want to import files through the software, you can't deactivate the preview from the Finder.

Kevin Stohlmeyer

Community Expert

Hi @philippl49897675 agree with everything you've noted - it has gotten worse over the years with Apple mainly due to the Finder aggressive permissions when accessing remotely (server, etc). The only bulletproof solution is to either drag local, which is not an ideal workflow for most, or invest in a DAM system to allow users to check-in/out locally and preserve file integrity. There are a lot of solutions out there that integrate quite well with Creative Cloud and make life a whole lot easier. We switched 7 years ago and have never looked back.

D

Darthsaiyan

Participating Frequently

If they have Apple Silicon search no longer, M1 + Synology (or any other NAS I tested three! even built a couple of VMs with NAS distros to see if it was a Synology issue, it IS NOT, it's an Adobe issue with Apple Silicon). I've lost days trying to make this work, I've lost all faith in this company. They're lucky after 25 years of using toshop I can't afford the time and effort needed to use something else. Oh and let's not even bring the "we're striking 3D off" and if your file opens up as a black screen cause of that, tough luck... great job on backward compatibility guys. I gave the 3D options a tries for a couple of years, now if I want to open older files I need to have 2 versions of Photoshop running... thanks!

I apologize for my elevated temperament, but when you'll have lost weeks of your time literaly just trying to OPEN files, perhaps you'll have an inkling as to why I feel the way I do.

ryancmiles

Participant

Have you found ANY workaround for this? I just purchased a $3000 MacBook Pro M1 and I'm running into the exact same problems you are. It's beyond frustrating. I even had Adobe support takeover my screen for a 1.5 hour support session and they simply couldn't fix it and said to contact Synology and Apple.

jane-e

Community Expert

@ryancmiles wrote:

Have you found ANY workaround for this?

Does Adobe's recommended workflow work for you?

https://helpx.adobe.com/photoshop/kb/networks-removable-media-photoshop.html

S_Gans

Community Expert

Adobe STRONGLY recommends working with only local files, both on MacOS and Windows. I can't answer for why it does well on your Windows setup, but please refer to this article to learn more: https://helpx.adobe.com/photoshop/kb/networks-removable-media-photoshop.html

Adobe Community Expert / Adobe Certified Instructor

D

Darthsaiyan

Participating Frequently

I'm having the same issue and I've tried everything... M1 + NAS is a no go with Photoshop... it's totally random, some files will open, then will give a disk error, one day will open, the next day doesn't...

This "answer" is unacceptable, we don't care what Adobe recommends, I recommend they learn to code and fix their bugs instead of recommending workflows that may not work for certain pros.

Some people NEED to work off their NAS, so please Adobe, fix this, and fix this NOW (I've already informed support back in March 2021 and they told me they were aware of the issue and a fix was coming... we're november and still this problem lingers).

If anyone has find a way to fix this, please let me know as I have lost all faith that Adobe cares about their paying customers, if this issue isn't affecting a large amount of users, they'll never EVER fix it.

D

Darthsaiyan

Participating Frequently

I should add that this is affecting M1 macs only, so it IS a bug... no issues whatsoever on Intel Macs, and no issues whatsoever on Winblows machines.

サインアップ

ソーシャルログイン

コミュニティへログイン

ソーシャルログイン

ファイルをウイルススキャンする。

このファイルはダウンロードできません