Skip to main content
Participant
December 5, 2023
Answered

Problem saving jpgs on shares - result 0KB jpgs

  • December 5, 2023
  • 1 reply
  • 1150 views

Hello

we have severall macOS Systems (Ventura and Sonoma) in our Windows AD environment. Each has the same problem saving JPGs from Photoshop to an network drive. Every jpg has only 0KB and is not usable. Of course saving locally works. Copy from local and paste to network share is working fine as well. I know Adobe is not intended to savo on network shares, but that far from any working reality. Any ideas what might be the problem an how to fix it?

 

Best Rgds

This topic has been closed for replies.
Correct answer Kevin Stohlmeyer

@100000Watt we too work on Macs with a Windows server. This is not a new overall issue but has gotten worse with the last several Mac OS releases. 

 

We always have our users save files local and then drag to the Windows server location. Saving directly causes so many issues (including the one you are reporting) with permissions and read/write speeds. Files end up locked "in use by another user" (which ends up being the Mac Finder), or corrupted files like you are seeing.

 

This will never be solved because everyone points a finger. This is why Photoshop's official stance is to not support working directly on remote locations (server, cloud, external drive) - there are too many variables that can affect it.

 

We ended up solving this issue by migrating to a DAM system that works natively on a Mac - users download or upload files to the DAM avoiding corruption and allowing users to work locally.

1 reply

kglad
Community Expert
Community Expert
December 5, 2023

are other apps able to save on your network drive? 

 

are other adobe apps able to save on your network drive?

Participant
December 5, 2023

All other Files from all other apps are saving just fine, onliy jpg and png from photoshop or illustrator are not saving correctly (save as, export, saving for web) 

Sometimes it even is like opening an existing jpg from the share lets to a 0KB file after opening it. Then we get this message (due to the fact, that it is only 0kb)

Kevin Stohlmeyer
Community Expert
Kevin StohlmeyerCommunity ExpertCorrect answer
Community Expert
December 5, 2023

@100000Watt we too work on Macs with a Windows server. This is not a new overall issue but has gotten worse with the last several Mac OS releases. 

 

We always have our users save files local and then drag to the Windows server location. Saving directly causes so many issues (including the one you are reporting) with permissions and read/write speeds. Files end up locked "in use by another user" (which ends up being the Mac Finder), or corrupted files like you are seeing.

 

This will never be solved because everyone points a finger. This is why Photoshop's official stance is to not support working directly on remote locations (server, cloud, external drive) - there are too many variables that can affect it.

 

We ended up solving this issue by migrating to a DAM system that works natively on a Mac - users download or upload files to the DAM avoiding corruption and allowing users to work locally.