Exporting to PNG file on network drive doesn't work
There appears to be a bug when exporting PNG files to network mapped drives in Mac OS X 10.13.4 (Darwin) Adobe InDesign 2018 (latest version).
This is in a domain environment using domain credentials. You export the file as PNG and it doesn't appear in the folder as expected. If I export to desktop it works fine, if I copy it from desktop to the share it copies fine. Just cannot export directly.
Jack
shared this idea
Hello,
Can you confirm the InDesign version you are using? Is it 2018.1 or 2018?
I assume the path to which you are trying to export the PNG is /Volumes/Shares/011 Changed Information/002 Changed Information/00617 Changed Information/Changed/ ?
Is this drive mounted via SMB?
Is it a NAS server?
7 comments
-
Bec
commented
I am having this same issue.
I am using Indd CC 2019 on a mac.
does anyone have a solution to this. It's very frustrating exporting to my desktop and moving to the folder on my hard drive -
Cole
commented
InDesign fails to export image files to a server location. No slashes in the file name. Export to Desktop works fine, export the same file to a server folder and nothing happens after dialogue box disappears.
This needs some sort of error or alert...or they could make it work correctly.
-
James
commented
Having the same issue. Export JPEG works fine onto desktop but not to network drive. Using Illustrator CC
-
Mayura
commented
Can somebody respond to this below bug.
Its been 9 months since it was reported. -
Jack
commented
We have tried just now to change to SMB v1 and it worked temporarily the first time, but now it's not exporting again.
-
Jack
commented
It's Adobe InDesign CC 2018 version 13100
Yes that is the path, Yes it is mounted via SmbFS (SMBv2)
It's a file share on a file server (Windows Server 2016 Standard) -
Jack
commented
Dtruss gives the following information open("/Volumes/Shares/011 Changed Information/002 Changed Information/00617 Changed Information/Changed/test.png\0", 0x25, 0x64D7A8) = -1 Err#2
I cannot find any further information in logs or debug output, if I remount the drives it fixed it once but it isn't working again after remapping drives.