P: Issues exporting photos to a Network Drive

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.

> 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.

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....

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.

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.

Smit,

This property dialog is irrelevant when the folder is located on a NAS accessed using UNC names, which seems to be the case for many affected users. In that case, the listed permissions are related to NAS users, not to Windows users. When accessing NAS resources from Windows, a user must logon with the NAS credentials, at least the first time. Then the permissions specified on the NAS apply. It seems that there's a problem with this when LR tries to access these resources.

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

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

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

> 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.