Skip to main content
Adobe Photoshop Family
chris_fourie's profile

8 Messages

 • 

690 Points

Wed, May 15, 2019 6:05 AM

Solved

Lightroom Classic 8.3: Issues exporting photos to a Network Drive

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.

Responses

Champion

 • 

6.3K Messages

 • 

107.8K Points

2 years ago

I'm trying to reproduce this on both Windows 10 and macOS 10.14 with no joy. There has to be a specific detail that we're not getting. Can we get screenshots of your export dialog settings when this occurs please? That might offer some clues.

Victoria Bampton a.k.a. The Lightroom Queen

www.lightroomqueen.com

Author of Adobe Lightroom Classic - The Missing FAQ and Adobe Lightroom - Edit Like a Pro books.

7 Messages

 • 

164 Points

@Victoria Bampton
I have a PDF of info from my Windows PC regarding the issue. What is the best way to get the document to Lightroom support?
Using Lr Classic cc 8.3, I cannot export to a NAS drive but can export to my Google Drive. Also, I confirmed on my PC Lr 8.2.1 does not have the same issue, i.e. export to the NAS creates the exported image files.
Note: Windows applied updates yesterday (15 May) and today (16 May) to my PC.

Champion

 • 

6.3K Messages

 • 

107.8K Points

Steve, you're welcome to email it to me at mail AT lightroomqueen DOT com and I'll pass it on to Rikk.

Victoria Bampton a.k.a. The Lightroom Queen

www.lightroomqueen.com

Author of Adobe Lightroom Classic - The Missing FAQ and Adobe Lightroom - Edit Like a Pro books.

7 Messages

 • 

164 Points

Victoria, From further testing, the issue appears to be with folder permissions. The windows user account I use has full control over the target folder but 'Everyone' is limited to List, Read & Execute and Read. Changing 'Everyone' to 'Full control', then Lr 8.3.1 does not display the write protected error and successfully creates the image files. I do not recommend changing the folder access permissions for 'Everyone' as a solution to the writable issue. The way Lr is acting would lead me to look at the Lr code related to accessing folders to make sure the code is using the logged in user account and not a general account for the access. Running Lr as the administrator also encounters the writable error which should not happen. BTW, the writable error does not occur when I export to the pictures folder on the PC hard drive. The writable error occurs when using the NAS mapped drive.

7 Messages

 • 

180 Points

For me it does not work on both, PC and NAS. Work only on original directory files.

6 Messages

 • 

200 Points

@victoria Sent you an email. I triggered a coredump, basically a snapshot of the program state. It should be useful for the engineering team on trying to figure out the problem.

Champion

 • 

6.3K Messages

 • 

107.8K Points

Thanks Benton, I've forwarded it on.

Victoria Bampton a.k.a. The Lightroom Queen

www.lightroomqueen.com

Author of Adobe Lightroom Classic - The Missing FAQ and Adobe Lightroom - Edit Like a Pro books.

Adobe Administrator

 • 

9.5K Messages

 • 

130.6K Points

I've received and added the link to our internal tracking issue. Please leave it in place for a week to ensure that our engineers have downloaded.

Thanks
Adobe Photography Products

Quality Engineering - Customer Advocacy

3 Messages

 • 

106 Points

Rikk,
I am running W10 and use a Synology NAS and became aware of the issue only accidentally while reading Victoria's newsletter.  I was about to update from 8.1 to the latest version, but am now holding off for resolution of this issue.

Why has Adobe not notified we users of the issue directly?  It concerns me that I have to search around various newsletters and websites to find out that there is a problem with the software.  As software is created by humans we know there will be errors.  It is what we humans do.  That there are errors is unfortunate, that we are not told of them -- well, see how Boeing is doing with it's 737 MAX issues or review Richard Nixon's experiences of coverups being worse than the crime.  Sure we will complain about what you could have/should have done, but Adobe not telling us will enrage us.

Adobe Administrator

 • 

9.5K Messages

 • 

130.6K Points

@James Wall

At this point, we are tracking this as an internal issue but not as a bug as it has not be reproduced by development, quality engineering or our Lightroom Champions on this forum.

This forum is the official place to get information and will be updated if and when we can reproduce and identify the source of the issue. 

Note that it is not affecting all users. 
Adobe Photography Products

Quality Engineering - Customer Advocacy

Champion

 • 

6.3K Messages

 • 

107.8K Points

Hey James. As Rikk says, it's not affecting everyone. I still can't reproduce it. I only flagged it up as a possible issue so anyone affected would know where to come for information - and a workaround has since been found and posted in this thread. You may not be affected, and if you are, both the workaround and/or rolling back to a previous version are both very easy.

Victoria Bampton a.k.a. The Lightroom Queen

www.lightroomqueen.com

Author of Adobe Lightroom Classic - The Missing FAQ and Adobe Lightroom - Edit Like a Pro books.

3 Messages

 • 

106 Points

...and the Boeing 737 MAX issue only affected two flights.  It's not the frequency, it's the impact on those affected.

The reported issue does have a material adverse impact on anyone upgrading to 8.3 using W10 and a NAS who would like to export a file.  At a minimum (you do better than the minimum at Adobe, right?) during the upgrade process you should be flagging it as a potential issue for those who use a NAS.  No NAS, no problem. 

We are waiting for you to decide what the reported issue really is and a fix before we make a terrible muddle of our work.  Meanwhile, we are missing out on the new 8.3 features.  This is very powerful software, and with that power comes complexity.  While we love the software, some of us are just hanging on by our teeth.

Thanks for letting me know this is the official source on such issues.  I did not know about it before, but not sure I could find it again for a new issue that I don't know exists (an unknown unknown).  I think you need greater proactivity.

604 Messages

 • 

11.3K Points

Victoria,

Rollback, reinstall, reset (your preferences) : indeed, these are the 3 words that anyone wanting to update a version of Lightroom should learn.

The fact that not everyone is affected doesn't mean anything and it's not a indication that it's not a bug. It is one, obviously. When a developer changes something in the code and a program feature no longer works afterwards while nothing changed in the user's environment, how to call this other than a bug ? We can't reproduce so we don't file this as a bug. Interesting. Is this how code quality is measured at Adobe ?

I'm rather irritated by this kind of Pavlovian reflex at Adobe tending to systematically insinuate that we are the problem. The main problem at Adobe is the ever declining  quality of the code. They are now unable to release a new version without breaking something. And this didn't start with version 8.3 of LR.  Each time, it's a loss of time (and sometimes of data) for many users. This indicates problems

- with the development methodology and tools  (LUA, OMG, why LUA ?)
- with the quality insurance dpt.

Anyone having experience in software development and observing what's happening can draw the same conclusion.

 

--
Patrick
www.ppphoto.fr
Hamburg ist der wahre Grund warum
Kompassnadeln nach Norden zeigen.

162 Messages

 • 

2K Points

Somewhere above it was stated no NAS no problem, not true. I do not have the issue, but both in this feedback site and over at https://forums.adobe.com/community/li... customers without NSS are having the problem. look at
No Export after update
"The specified folder is not writeable" during Export after update to LR Classic 8.3
All folders on Synology NAS are write protected
Exportproblem nach update auf LR 8.3
Lightroom 8.3 unable to write to hard drive after update
export message "the specified folder is not writable"?
Lightroom Classic 8.3 error "the destination folder is not writable"

7 Messages

 • 

180 Points

All my files are on my NAS. I can export on the original directory but not on an others directory.

5 Messages

 • 

168 Points

Wow, I cannot believe what Victoria has said above.

The workaround does NOT work for existing publish services, which cannot change the destination once they were set up. And a lot of people, like me, have many publish services, which renders creating new ones is not an option, either.

Telling a paid user not to use the latest version and rolling back to an old version is not a solution at all. We might be forced to roll back WHILE ADOBE IS FIXING THE CODES, but it is definitely not a solution without filling it as a bug.

This is absolutely not the reason we are paying for the subscription. Contrarily, we are paying for continuously bug fixing, new features, quality improvement, and good customer support. Again, telling a paid user to roll back as a solution is totally unacceptable.

Champion

 • 

6.3K Messages

 • 

107.8K Points

Oh man, I can't say anything these days. 
  • I'm not saying it's not a bug.
  • I'm not saying Adobe shouldn't fix it ASAP.
  • I'm not saying that rolling back or using a workaround is a permanent solution. 

I alerted my readers to it because some may be affected, and I wanted them to know where to come for information if they were.

I haven't told people not to upgrade, because most people clearly aren't affected and will want to benefit from the new features. Of course that doesn't make it any less of a problem for the people who are affected.

If you are affected, this is the right place to find out the latest information and help Adobe figure out why they can't reproduce this bug yet. That'll get the solution we all want much quicker. And in the meantime, rolling back is a reliable workaround.

Victoria Bampton a.k.a. The Lightroom Queen

www.lightroomqueen.com

Author of Adobe Lightroom Classic - The Missing FAQ and Adobe Lightroom - Edit Like a Pro books.

604 Messages

 • 

11.3K Points

> Oh man, I can't say anything these days.

Victoria,

I hope there's no misunderstanding here. I do appreciate your work. I'm a premium member of your site. I've never considered you as an Adobe evangelist. Just, you should take into account the enormous frustration that is generated among many customers by the way Adobe manage their business and their software. Every post that is apparently "defending" Adobe (be that true or not) can generate irritated reactions.

Like you, I always want to be positive but very frankly, their behavior is questionable. I'm a former developer and system engineer. I have taught software engineering for years. Lightroom is an open book about their internal difficulties and I don't observe any attempt to do something about that. Regression testing obviously bypassed, bugs lasting since years, trend to consider that problems are on the user's side, ready-made answers (the famous "rollback-reinstall-reset" trio mentioned above),... This kind of behavior always appears in monopolistic situations. They should be cautious, though.

 

--
Patrick
www.ppphoto.fr
Hamburg ist der wahre Grund warum
Kompassnadeln nach Norden zeigen.

Champion

 • 

6.3K Messages

 • 

107.8K Points

Hey Patrick. I really do understand the frustration, probably more than most, because I get to spend my days listening to people (understandably) complain about things I can't fix. :-(

Victoria Bampton a.k.a. The Lightroom Queen

www.lightroomqueen.com

Author of Adobe Lightroom Classic - The Missing FAQ and Adobe Lightroom - Edit Like a Pro books.

3 Messages

 • 

122 Points

2 years ago

I have the same problem with the plug-in for online galleries - TTG Publisher. OS Windows 10. The settings for the plug-in are below





During export, I have the error messages:

Two times this one



And then this one




2 Messages

 • 

112 Points

Same problem here. after update to Lightroom Classic 8.3. on Windows 10 Pro with Synology NAS. I have two main shared folders on my NAS. Export two one of them work as before, where the other folder gives the 'not writable' issue. Definitely a Lightroom problem!

Employee

 • 

295 Messages

 • 

7.8K Points

Hi All,

Please share the Screenshot of the Securities tab from the Folder Properties using the File Explorer for the folder where you are facing this issue. Please select your user for the same.

See below for a sample


Thanks,
Smit

1 Message

 • 

60 Points

2 years ago

I installed LR 8.3 yesterday on my Windows 10 system (including yesterday's WIndows update 1803/17134.765) and everything works perfectly when I export to Desktop or Pictures (both reassigned to a non-system local HDD) and also to my QNAP NAS. I've tried many different export options but none will make it fail.

Adobe Administrator

 • 

9.5K Messages

 • 

130.6K Points

2 years ago

Greetings all,

We are still struggling to reproduce this issue on our test machines and Victoria has graciously attempted to repro as well. We have an issue logged with engineering and are tracking this trying to find a repro case so we can get a fix in your hands quickly. 

One thing I've noticed here is that no one has mentioned resetting preferences. Normally preference issues are a one-off type of thing but in the absence of reproducible steps I am going to ask that you try a reset of your preference file and see if something shakes loose.  If it works - great, if not, we've checked a box on the troubleshooting chart and look elsewhere for the source of the issue. 

A Preference File will survive a Lightroom uninstall/reinstall. Sometimes weird behavior is corrected/cured by resetting the preferences. 

Reset Procedure:

1. Close Lightroom.
2. Hold down [Alt/Opt]+[Shift] while restarting Lightroom. 
3. Overwrite the Preferences when prompted by the dialog.
4. Close Lightroom.
5. Restart Lightroom.

Are you able to export normally after resetting the preferences?
Adobe Photography Products

Quality Engineering - Customer Advocacy

6 Messages

 • 

200 Points

I didn't do a full reset. I tried restoring the export settings to default, somewhere in the settings menu to no avail.