Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
51

P: Issues exporting photos to a Network Drive

LEGEND ,
May 14, 2019 May 14, 2019

Since I upgraded to V8.3 of Lightroom Classic I can no longer export my files to our Synology Network System, I get the following error message "The specified folder in not writable"

After contacting support they were not able to resolve my issue, they maintained that it is a network issue on my side. I could not find any answers here or anywhere on the internet and decided to report this issue.

Because I share my processed photos with the rest of the office, my only solution was to un-install V8.3 and go back to V8.2.1, by doing that it resolved my problem.

So yes Adobe you have network issues in V8.3 as version 8.2.1 works perfectly when saving files to a network drive.

Bug Fixed
TOPICS
macOS , Windows
2.5K
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 2 Correct answers

Adobe Employee , May 29, 2019 May 29, 2019
Lightroom Classic 8.3.1 was released today and contains a fix for this issue. Please update to 8.3.1 and verify that you are no longer seeing the issue. Thank you!
Translate
Adobe Employee , May 22, 2019 May 22, 2019
Greetings all,

I wanted to give you an update on this issue. We've been able to identify a possible bug with regard to this issue. We are currently testing the fix with a few users to verify that it does cure the issue. At this time I do not have an ETA for a public-facing fix.

If your issue is with Export the workaround continues to be: https://helpx.adobe.com/lightroom-classic/kb/error_export_folder.html
If your issue is with Publish Services, the only workaround is to revert to version 8.2.1. 

Th...
Translate
replies 150 Replies 150
150 Comments
LEGEND ,
May 22, 2019 May 22, 2019
For the record, I'm having the same problem as everyone else, but I don't even know what a "Synology NAS" is.  I am trying to publish to a shared folder on a hard drive on another PC in my home network.  Until 8.3, this worked for years without a hitch.  The export workaround works for me, but it doesn't help publishing.  I can live without publish for awhile, so I'm not rolling back to 8.2.   

Also wanted to add that I can export OR publish to a local folder with no problem whatsoever.  Only the shared drive/folder on my other Windows 10 PC has the problem.  Thanks for the action on this!
Translate
Report
New Here ,
May 23, 2019 May 23, 2019
I am also having this problem exporting to my Synoloy NAS device trying to export images to the share on Windows 10.  Exporting on the local C: drive still works.  Really annoyed!!!
Translate
Report
New Here ,
May 25, 2019 May 25, 2019
I have the same issue, but it started during an export few pictures were already written to the NAS. The directory used for export is on Synology and has been used this way since 2013.... Rights on the disk did not change, are simply full control. 

I have reverted back to 8.2.1, no time to experiment here, but want it noted here...
Translate
Report
New Here ,
May 25, 2019 May 25, 2019
Just in case you need more data:
  • win 10 system, raw files come from a samba share mounted via a drive letter
  • export to a local drive fails with the given error; the workaround makes things work
  • however, a publish service to the local harddrive (jfriedl's folder publisher) works, without having to do anything special
So far have not rolled back to 8.2.1, since the impact for me is that high.
Translate
Report
New Here ,
May 26, 2019 May 26, 2019
I submitted a support ticket to Synology with reference to this feed to see if they have any insight into the fix.
Translate
Report
LEGEND ,
May 27, 2019 May 27, 2019
I an experiencing this issue and am also seeing it when I try and print via cannon print studo pro through the plung-in extra's menu.

First I get the "The specified folder is not writeable" then I get the following error twice:

"An internal error has occurred:  bad argument #1 to 'child' (string expected, got nil)"
Translate
Report
Adobe Employee ,
May 29, 2019 May 29, 2019
Lightroom Classic 8.3.1 was released today and contains a fix for this issue. Please update to 8.3.1 and verify that you are no longer seeing the issue. Thank you!

Smit | Lightroom Team
Translate
Report
New Here ,
May 29, 2019 May 29, 2019
Great!  I trust Adobe, but I am a Trust but Verify sort of guy.  Now I am looking for reports from those volunteers brave enough to try this out to see if it flies or crashes.  If it works, I am eager to upgrade!  
Translate
Report
New Here ,
May 29, 2019 May 29, 2019
29 May 2019 11:15 ET - 8.3.1 installed to my Windows 10 PC without issue. Exporting to specific folder located on a NAS device completed successfully, i.e. the 'folder not writable' error did not occur.
Translate
Report
Explorer ,
May 29, 2019 May 29, 2019
It work for me. Thank you!
Translate
Report
New Here ,
May 29, 2019 May 29, 2019
You can have both 8.2.1 and 8.3.1 installed, you don't need to be really brave to try 🙂 They work with the same catalog, so you are able to easily switch between them.
Translate
Report
New Here ,
May 29, 2019 May 29, 2019
I have problems with synchronization. It persists also with 8.3.1
Translate
Report
LEGEND ,
May 29, 2019 May 29, 2019
Sounds like a different problem, all this version fixed was the usability of some users to do a straight up export, typically involving NAS. You probably need to submit your own separate problem.
Translate
Report
LEGEND ,
May 29, 2019 May 29, 2019
Thank you Smit Keniya the update resolved my issues 🙂
Translate
Report
Community Beginner ,
May 29, 2019 May 29, 2019
Thank you, Smit.  I could also confirm 8.3.1 fixes the bug at my side.
Translate
Report
LEGEND ,
May 30, 2019 May 30, 2019
Sorted now - Thank you!!
Translate
Report
New Here ,
May 30, 2019 May 30, 2019
Tested it today with LR 8.3.1. and no issues publishing pictures anymore. Thank you!
Translate
Report
LEGEND ,
May 30, 2019 May 30, 2019
this bug is fixed for me too! Thanks
Translate
Report
New Here ,
May 30, 2019 May 30, 2019
8.3.1 fixes this problem for me! Thank you!

Translate
Report
Community Beginner ,
May 31, 2019 May 31, 2019
With 8.3.1 my problem was fixed. Thank you
Translate
Report
New Here ,
May 31, 2019 May 31, 2019
Hi, not fixed on my Mac...any thoughts?
Translate
Report
New Here ,
May 31, 2019 May 31, 2019
RackMultipart201906019758mreut-c412a689-409f-4769-924b-02308f176211-1014485407.jpgRackMultipart20190601536261ja5-561828cc-a29f-423b-8068-47f0bfedc84f-1473402704.jpg
Translate
Report
New Here ,
May 31, 2019 May 31, 2019
RackMultipart201906018314212sn-7d96e937-7b4d-4b8b-9aed-4672ffb89e6a-2059723220.jpg
Translate
Report
New Here ,
May 31, 2019 May 31, 2019
Only allows me to export documents folder, not hhd or external hdd
Translate
Report
New Here ,
May 31, 2019 May 31, 2019
LATEST
Apologies, found the problem, my WD External drive was only Windows formatted, not MAC
Translate
Report