Lightroom Classic 8.3: Issues exporting photos to a Network Drive

  • 51
  • Problem
  • Updated 3 weeks ago
  • Solved
  • (Edited)
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.
Photo of Chris

Chris

  • 8 Posts
  • 5 Reply Likes

Posted 1 month ago

  • 51
Photo of Mary Hughes

Mary Hughes

  • 6 Posts
  • 1 Reply Like
Ditto. I can't export to my either my internal hard drive or an external hard drive on a Windows 10 system after updating to the new version yesterday. I've checked through diskpart that the externals are all read write. I can export if I choose select folder later.
Photo of Mary Hughes

Mary Hughes

  • 6 Posts
  • 1 Reply Like
Some screen shots:


Photo of Victoria Bampton - Lightroom Queen

Victoria Bampton - Lightroom Queen, Champion

  • 4899 Posts
  • 1907 Reply Likes
A really long shot, but how are you selecting that folder path? For example, is that a preset? Or are you selecting it from the pop-up? Or are you clicking the Choose button?
Photo of Mary Hughes

Mary Hughes

  • 6 Posts
  • 1 Reply Like
It isn’t a preset. It was the previous folder that I had exported to via the Choose button This method of exporting worked on all other versions of Lightroom until this version. I now follow the work around method to export after spending a lot of time thinking that my hard drives had suddenly become read only. I tried to export to multiple drives and my desktop using my normal method and got the failure notice.
Photo of Victoria Bampton - Lightroom Queen

Victoria Bampton - Lightroom Queen, Champion

  • 4899 Posts
  • 1907 Reply Likes
If you were to manual select that folder (rather than it being the previous folder), does that work? That could be just the clue we need.
Photo of Mary Hughes

Mary Hughes

  • 6 Posts
  • 1 Reply Like
Nope, tried that. I have tried selecting a different file from the little down arrow.I tried reselecting the folder completely. I shut down Lightroom and my laptop completely. The Specific Folder option is what appears to be failing me.
Photo of Benton Lam

Benton Lam

  • 5 Posts
  • 5 Reply Likes
My computer has a SSD as C:, an old fasioned HD as D:, and a network drive on Z:

I tried creating a new folder under Z:, and LR 8.3 still refuses to export.

It was able to export to a folder under D:
Photo of Mary Hughes

Mary Hughes

  • 6 Posts
  • 1 Reply Like
The only export option that does not work is the export to a specific folder option. All other options in the drop down menu work for me.

I completed a preference reset as suggested and that did not correct the issue.
Photo of Chris

Chris

  • 8 Posts
  • 5 Reply Likes
I have received a message from Adobe confirming that this is a bug and that they are working on a solution.


(Edited)
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 5534 Posts
  • 1164 Reply Likes
While the engineering team works on a solution, I wanted to point out this help doc which contains a potential workaround for the issue: https://helpx.adobe.com/lightroom-classic/kb/error_export_folder.html

As soon as we have updated information we will be posting it to this thread. 

Make sure you hit the [Me-Too] button at the top so we can have an accurate impact of this bug. 

Thanks!
Photo of Benton Lam

Benton Lam

  • 5 Posts
  • 5 Reply Likes
Please make sure the engineering team have an automated test to prevent this issue from creeping back in the future.

Exporting to a network drive is such a common use case, I'm a little surprised that this isn't part of the standard release testing before the product ships.

I simply went for the downgrade.
Photo of Victoria Bampton - Lightroom Queen

Victoria Bampton - Lightroom Queen, Champion

  • 4914 Posts
  • 1913 Reply Likes
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.
Photo of Steve Valentine

Steve Valentine

  • 7 Posts
  • 2 Reply Likes
@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.
Photo of Victoria Bampton - Lightroom Queen

Victoria Bampton - Lightroom Queen, Champion

  • 4914 Posts
  • 1913 Reply Likes
Steve, you're welcome to email it to me at mail AT lightroomqueen DOT com and I'll pass it on to Rikk.
Photo of Steve Valentine

Steve Valentine

  • 7 Posts
  • 2 Reply Likes
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.
Photo of Yvon Daigle

Yvon Daigle

  • 7 Posts
  • 3 Reply Likes
For me it does not work on both, PC and NAS. Work only on original directory files.
Photo of Benton Lam

Benton Lam

  • 5 Posts
  • 5 Reply Likes
@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.
Photo of Victoria Bampton - Lightroom Queen

Victoria Bampton - Lightroom Queen, Champion

  • 4914 Posts
  • 1913 Reply Likes
Thanks Benton, I've forwarded it on.
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 5516 Posts
  • 1161 Reply Likes
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
Photo of James Wall

James Wall

  • 3 Posts
  • 1 Reply Like
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.
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 5516 Posts
  • 1161 Reply Likes
@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. 
Photo of Victoria Bampton - Lightroom Queen

Victoria Bampton - Lightroom Queen, Champion

  • 4914 Posts
  • 1913 Reply Likes
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.
Photo of James Wall

James Wall

  • 3 Posts
  • 1 Reply Like
...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.
Photo of Patrick Philippot

Patrick Philippot

  • 479 Posts
  • 134 Reply Likes
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.
Photo of David Golding

David Golding

  • 9 Posts
  • 0 Reply Likes
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"
Photo of Yvon Daigle

Yvon Daigle

  • 7 Posts
  • 3 Reply Likes
All my files are on my NAS. I can export on the original directory but not on an others directory.
Photo of Poyen Huang

Poyen Huang

  • 3 Posts
  • 1 Reply Like
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.
Photo of Victoria Bampton - Lightroom Queen

Victoria Bampton - Lightroom Queen, Champion

  • 4914 Posts
  • 1913 Reply Likes
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.
Photo of Patrick Philippot

Patrick Philippot

  • 479 Posts
  • 134 Reply Likes
> 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.
Photo of Victoria Bampton - Lightroom Queen

Victoria Bampton - Lightroom Queen, Champion

  • 4914 Posts
  • 1913 Reply Likes
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. :-(
Photo of Askold Karidi

Askold Karidi

  • 3 Posts
  • 2 Reply Likes
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




Photo of Hans Broeksteeg

Hans Broeksteeg

  • 1 Post
  • 0 Reply Likes
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!
Photo of Smit Keniya

Smit Keniya, Employee

  • 227 Posts
  • 106 Reply Likes
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
(Edited)
Photo of Geoff Baylis

Geoff Baylis

  • 1 Post
  • 0 Reply Likes
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.
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 5534 Posts
  • 1164 Reply Likes
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?
Photo of Benton Lam

Benton Lam

  • 5 Posts
  • 5 Reply Likes
I didn't do a full reset. I tried restoring the export settings to default, somewhere in the settings menu to no avail.
Photo of Askold Karidi

Askold Karidi

  • 3 Posts
  • 2 Reply Likes
I did the reset - the problem the same
Photo of David Golding

David Golding

  • 9 Posts
  • 0 Reply Likes
Did you follow the directions for a reset? Or did you just enter Preferences, and changed options to defaults? Not the same.
Photo of David Golding

David Golding

  • 9 Posts
  • 0 Reply Likes
Asked members yesterday about resetting preference file over at: https://forums.adobe.com/thread/26219..., re-asked today, bring this Adobe REP posting up. Have not gotten feedback att the a Forum discussion as to reset yay or nay.
Photo of Francois Hendrickx

Francois Hendrickx

  • 10 Posts
  • 1 Reply Like
My result is nay.
Photo of Patrick Philippot

Patrick Philippot

  • 479 Posts
  • 134 Reply Likes
Rikk,

> If it works - great

No, it's not great. This would not help fixing the bug. I encourage everyone to read this thread :

https://feedback.photoshop.com/photoshop_family/topics/reset-your-preferences-moving-from-the-magic-...

Photo of Patrick Philippot

Patrick Philippot

  • 479 Posts
  • 134 Reply Likes
> We are still struggling to reproduce this issue on our test machines and Victoria has graciously attempted to repro as well.

I'm wondering why similar situations occur that often. Many users have an obvious problem that they can reproduce at will and that problem can't be reproduced at Adobe. Maybe it would be interesting to obtain information about Adobe's test systems configuration ? Hardware, software, preference file, etc. This way, we could try to find a difference between our systems and yours. Adobe tend to explain this by suggesting that the affected users have special configurations, unhealthy systems or corrupted files. I can't believe this, especially when the problems are only related to Adobe products.

There's something very strange, indeed. Each time a new bug appears, most of the time a part of the users are hit and another part is unaffected. And most often, Adobe testers belong to the first category. Having information about how and on which systems tests are made at Adobe could help determine what's different.

Giving access to the bug tracking system could also help, I guess. We should have access to a list of currently acknowledged bugs and have the possibility to me-too them, to add information about our configuration, etc. This would also give a more accurate idea about what Adobe are actually doing regarding reported bugs (especially when bugs have been reporting since years and are still not fixed). Transparency about this is in order, I think. Especially because the code quality is obviously decreasing since a while.
Photo of Victoria Bampton - Lightroom Queen

Victoria Bampton - Lightroom Queen, Champion

  • 4914 Posts
  • 1913 Reply Likes
It's not just Adobe's test system specs that you'd need, but the machines of a whole load of beta testers too. 

When Adobe says they're struggling to reproduce it, they're not blaming user's systems, but trying to figure out what is different. 

27 reports (so far) is a tiny percentage of the installed users, even if only 1 in 100 actually reported their problem, which means Adobe's looking for a needle in a haystack. It's faster to look for similarities across 27 systems than to compare all the things it might not be.
Photo of Patrick Philippot

Patrick Philippot

  • 479 Posts
  • 134 Reply Likes
Agreed. But having information about Adobe's test machines would allow this tiny percentage of users to compare their systems with systems where Adobe claim to not have any problem. Each affected user could do that.

As of beta testing, I don't see Lightroom on this page. Did I miss something ?
Photo of Chris

Chris

  • 8 Posts
  • 5 Reply Likes
Victoria Bampton - Lightroom Queen, this bug has been reported on another forum as well:

https://forums.adobe.com/thread/2622582

Adobe must have acknowledged this as a bug as they have posted a work around under their help section?

https://helpx.adobe.com/lightroom-classic/kb/error_export_folder.html


(Edited)
Photo of Mac MacDermaid

Mac MacDermaid

  • 1 Post
  • 0 Reply Likes
Same issue here. The suggestion of "choose folder later" worked for me
Photo of Bob Weder

Bob Weder

  • 3 Posts
  • 0 Reply Likes
Not experiencing this issue with my Synology NAS on a Mac.
Photo of David Golding

David Golding

  • 9 Posts
  • 0 Reply Likes
Inquiry. catalog location, for those with the problem, is your catalog located in the default path:

C:\Users\[user name]\Pictures\Lightroom\Lightroom Catalog.lrcat. ?

mine is not, I do not have the problem.

not Adobe staff.
Photo of Mary Hughes

Mary Hughes

  • 6 Posts
  • 1 Reply Like
Mine is not and I have the problem.
Photo of Jeff Stovall

Jeff Stovall

  • 16 Posts
  • 7 Reply Likes
I have a similar issue, but not just limited to export. Instead, I am using the Negative Lab Pro plugin and get this same error message whenever I try to use the plugin. The behavior is the same whether the image file is on my local C: drive or on an external hard drive. I also see this message when attempting to use an export preset that has the folder specified. No issues before the recent update.

I'm using Windows 10. I tried adding "Everyone" with Full Control to all folders within C:\Users\...\Pictures, but nothing changed.
(Edited)
Photo of Patrick Philippot

Patrick Philippot

  • 479 Posts
  • 134 Reply Likes
Same problem here with nuances...

I tried to export an image to a folder of my Synology NAS and I got the "not writable" error. However, I tried again with the "Export with previous" command and this time the export succeeded (as well as subsequent exports to the same NAS folder be they triggered with or without the "Export with previous" command).

Then I tried to export to another NAS folder and this time, I got the "not writable" error when selecting the folder, not when actually exporting. I repeated the test under control of Process Monitor and I observed that when trying to open the NAS folder specified in the "Choose folder" dialog, LR immediately tried to open C:\Windows\CSC\v2.0.6\namespace\MYNAS (MYNAS being... my NAS). The CSC folder contains all the files that have been made available offline. However, this feature is disabled on my system. By default, the CSC folder can't be opened in File Explorer. You must take ownership to do that. I did this just to verify whether the MYNAS subfolder existed there. It didn't.

I could see that LR stubbornly tried and tried again to access this non existing offline NAS folder until it decided to issue the error message.

Well, obviously, something has been broken in 8.3 (not only that since I can no longer run LR unless as an administrator). No doubt that the development team has a source archiving tool allowing to easily compare the source code for 2 different versions. Finding what has been changed in this area shouldn't take that much time.

Yet another well tested release...

Photo of Patrick Philippot

Patrick Philippot

  • 479 Posts
  • 134 Reply Likes
Additional information : I'm accessing my NAS using UNC names. It is not mapped to a drive letter.

Should I add that my synchronization utility (SyncBack) writes data on a daily basis, using UNC names, to the NAS folders to which I'm trying to export from LR ? No problem. So the problem is with LR, not with our systems.

Photo of Smit Keniya

Smit Keniya, Employee

  • 227 Posts
  • 106 Reply Likes
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


Also, meanwhile, could you try a potential workaround for the issue mentioned in this help doc: https://helpx.adobe.com/lightroom-classic/kb/error_export_folder.html

Thanks,
Smit
(Edited)
Photo of Thomas Hendel

Thomas Hendel

  • 6 Posts
  • 2 Reply Likes
Why? It used to work in the previous version. And almost nobody, who reports that problem here, has changed anything on the side of the NAS or anything else regarding image folders. Me included. Sorry for the german directness :-), but it should not be that hard to figure out the code changes in the context of accessing the export folder. You can safely assume that the other end (the target folder) was not changed at all.
Photo of Patrick Philippot

Patrick Philippot

  • 479 Posts
  • 134 Reply Likes
Following this with Process Monitor demonstrates that for the very same operation (selecting a destination folder) there are 2 different paths in the code. When specifying the folder before exporting, LR tries to directly access the folder (\\MYNAS\Images in my case). When using the "Choose folder later" option, LR opens \\MYNAS\PIPE\srvsvc ??

2 different routines for executing the very same simple operation : not good. Beside uselessly duplicating code, if you have to fix something in one routine you'll usually forget to do the same in the other.
Photo of Patrick Philippot

Patrick Philippot

  • 479 Posts
  • 134 Reply Likes
Well, the problem is new with version 8.3. It doesn't occur with version 8.2.1. Just compare the source files, spot the changes related to network management and that's it. There are not that much changes in 8.3. This shouldn't take too much time to find the differences.
Photo of Michael Gibbs

Michael Gibbs

  • 2 Posts
  • 2 Reply Likes
Adobe have identified this as a "bug" so I dont understand why we are being asked for so much more information. It does not work. Once again a new release has broken the software for many people. Perhaps its related to W10 Pro and W10 Home as well as there are differences. Has anyone thought it may be related to UAC which people can have set differently. Either way this cant be too hard to figure out as Patrick has said, just look at the source differences. I am assuming that Adobe has a source repository and staging system to ensure you can go back and see the changes. I hope so. One would wonder with the number of bugs that get released. Amazing how much quicker other software runs without bugs aye....

Photo of Patrick Philippot

Patrick Philippot

  • 471 Posts
  • 133 Reply Likes
> I am assuming that Adobe has a source repository and staging system to ensure you can go back and see the changes.

Sometimes, I'm really wondering.
Photo of Benton Lam

Benton Lam

  • 5 Posts
  • 5 Reply Likes
The reason why we're being asked a bunch of information is clearly that they're missing that key piece to identify why it works in their test environments and not ours.

I've seen bugs that we know exists, but we could not root-cause for months. In that example, it was code that was working on Linux with case-sensitive filesystems that did not play well with OSX's case-aware filesystem. Without that information, we can observe the misbehaviour but never quite know why it was misbehaving.

I have been just tracking down deadlocks at work for a few weeks, and initially I had a snowball's chance in hell in finding it. Without some critical information, again, we would only know that something is wrong but not where it might be.

Depending on how they structure their release, a minor version bump could have hundreds or thousands of commits between 8.2 and 8.3. You might say, oh why not just git bisect and it should be found with 10 tests with a binary search of the first defective commit. But that hinges on being able to actually reproduce the problem. *That* is what they really need to locate it. If they can't reproduce that issue themselves, just purely staring at the code won't help much. I had been staring at code for the deadlock I had been chasing for a week and all that gave me was eye strain.

It's easy to vent because it's frustrating and appears to be a simple issue. Heck, I had given a smart-aleck comment already. And frankly I myself do have lots of choice words about testing, it's my bread and butter afterall. But doing that alone won't help jack. We think it's easy, because it's a "network drive", but there are at least two major protocols (SMB, NFS), a handful of versions each, and different server providing the protocols. The number of combinations goes up fast, even if someone is quite dedicated in setting up all the test beds to cover as much as one can. There is no such thing as 100% coverage.

Believe you me, I'm not particularly happy about this bug, but the quickest way to solve it is to provide information. One of these would be the key to help RCA the bug and get it fixed.

@Rikk incidentally a casual glance suggests a lot of consumer grade NAS ran into issues. They're probably running some version of Samba. Mine is a hand-rolled server running Samba 4.1.22 (I know it's ancient...)
Photo of David Golding

David Golding

  • 5 Posts
  • 0 Reply Likes
Is it limited to NAS? in the various discussions at the customer forum, non NAS users are reporting the issue . Ok, supposedly not NAS users. incidentally, Not a NAS user, not having the issue.
One of the six or so threads: https://forums.adobe.com/thread/2621939
Photo of fsaronson

fsaronson

  • 1 Post
  • 0 Reply Likes
I'm having the same issue.  However, importing to my Synology NAS is not a problem.  I will try the workaround when I get back home.  My suspicion is that it has to do with the upgrade, combined with Synology and Windows 10.  It's a very particular issue, it would seem to me, which may explain why Adobe can't replicate it.
(Edited)
Photo of Andrey Dzizenko

Andrey Dzizenko

  • 1 Post
  • 0 Reply Likes
The same for me. Publish services which had a OneDrive folder as a destination have stopped working with the error "Folder is not writable". 
I'm able to use the "workaround" for Export, but not for Publish services. And actually Publish services are the comfortable way of burning jpegs, without them exporting photos becomes a pain for me.
Photo of Andrew Merritt

Andrew Merritt

  • 9 Posts
  • 5 Reply Likes
I upgraded yesterday, to try the new Texture feature, and I'm hitting the same problem when I try to export.  Shame there wasn't any warning, and that the upgrade was still being offered when there's such a significant bug.

Yes, the work around works for me, but I've wasted an hour trying to find the cause.
Photo of Jay Wilcox

Jay Wilcox

  • 2 Posts
  • 0 Reply Likes
For what it's worth, I too discovered the problem immediately after updating to 8.3 when trying to update a long-ago-established-and-much-used published collection on a network folder.  Tried a straight export to the same network folder and had the same problem (i.e. "not writable").  Then I set up a published collection on a LOCAL drive and had no problem publishing,  I am using a fully updated Windows 10 PC. The "choose folder later" workaround is great (thanks), but helpful only on export since this option is not available for published collections.  Need a fix soon.
Photo of Dan Traun

Dan Traun

  • 1 Post
  • 0 Reply Likes
Is there any update on this issue?
Photo of Yvon Daigle

Yvon Daigle

  • 6 Posts
  • 2 Reply Likes
I received this from Adobe, this morning:
Hello Yvon,
Greetings from Adobe!
Thank you for your response, You can continue start working in the older version which
is 8.2, we will let you know on our next update if the issue get fixed in the 8.3 update.


Thanks&Regards
Adobe Support
(Edited)
Photo of Jim Irwin

Jim Irwin

  • 1 Post
  • 1 Reply Like
For me, I can export locally, but I cannot export to a Synology DiskStation (which has worked fine until LR 8.3).  On my wife's computer, which was still running 8.2, I exported to the DiskStation.  I upgraded LR to 8.3, and got the "folder is not writeable" message.  I wrote software for 25 years before retiring.  Something changed in 8.3 that broke exporting for many of us.
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 5534 Posts
  • 1164 Reply Likes
Official Response
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. 

Thank you for all the information you've provided thus far and we hope to have this resolved quickly so everyone can get back to their normal workflow. 

Thanks for your patience.
Photo of Laura Shoe

Laura Shoe, Champion

  • 84 Posts
  • 52 Reply Likes
Thank you for jumping on this, Rikk and team, and for the update.
Photo of Scott Prokop

Scott Prokop

  • 4 Posts
  • 0 Reply Likes
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!!!
Photo of w.vuyk

w.vuyk

  • 7 Posts
  • 2 Reply Likes
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...
(Edited)
Photo of Iustin Pop

Iustin Pop

  • 9 Posts
  • 0 Reply Likes
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.
Photo of Scott Prokop

Scott Prokop

  • 4 Posts
  • 0 Reply Likes
I submitted a support ticket to Synology with reference to this feed to see if they have any insight into the fix.