Lightroom Classic: "An internal error has occurred: ?:0: attempt to index a nil value"

  • 47
  • Problem
  • Updated 1 week ago
  • (Edited)
When I delete photographs from catalogue + disc, I am now consistently having the following error dialogue box pop up in LR Classic CC:

"An internal error has occurred: ?:0: attempt to index a nil value"

It appears that LR is carrying out the delete function, however, in order to continue using the program, there is an "OK" checkbox that you must click on.
Photo of Brian Kipnis

Brian Kipnis

  • 8 Posts
  • 1 Reply Like
  • slightly annoyed

Posted 10 months ago

  • 47
Photo of Juraj Zimányi

Juraj Zimányi

  • 6 Posts
  • 0 Reply Likes
Thanks to anybody recommending to disable the plugins. After two weeks of trips I'm back home sitting at my desk and trying it out. After I disabled the plugins there seems to be no issue whatsoever. But re-enabling the LogiOptions plugin has brought the issue back again. In my case Lightroom used to freeze most of the time rather than displaying the error message, but after trying the -traceback option, in the log generated by the DbgView tool there were three occcurences of the error message "?:0: attempt to index a nil value" at the end, just before I had to kill Lightroom.
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1515 Posts
  • 489 Reply Likes
Hi Juraj, Could you post a downloadable link to the traceback logs? I can check if there is something that can be done from the Lr side to workaround the issue?
Photo of Brian Kipnis

Brian Kipnis

  • 8 Posts
  • 1 Reply Like
I disabled all plug-ins except the 2-3 that I actually use.  I no longer have this problem.  My assumption is that the two events correlate.  (P.S.  I am still running LR 7.2. I am still not convinced that Adobe has satisfactorily addressed all the bugs in LR 7.3)
Photo of mark

mark

  • 2 Posts
  • 0 Reply Likes
Lightroom Classic version: 7.3.1 [ 1167660 ]License: Creative Cloud
Language setting: en-US
Operating system: Mac OS 10
Version: 10.13.6 [17G39b]
Application architecture: x64
Logical processor count: 8
Processor speed: 4.0 GHz
Built-in memory: 32,768.0 MB
Real memory available to Lightroom: 32,768.0 MB
Photo of Bruce in Philly

Bruce in Philly

  • 9 Posts
  • 0 Reply Likes
I may have figured it out... disable "LogiOptions" plugin.  File -- Plug- in Manager - scroll down and select it... click disable.
I HATED this error.... finally it just got so darn bad... I would delete, get the error, and the pictures were still there.  Constantly getting this.   This plugin is a Logitech option for a mouse.  You don't need it at all.
I think it all runs a bit faster too... but maybe that is just me.
Peace,
Bruce in Philly
(Edited)
Photo of mark

mark

  • 2 Posts
  • 0 Reply Likes
Logitech options not one of the plugins for me. I'll keep hoping for a fix!
Photo of John R. Ellis

John R. Ellis, Champion

  • 3967 Posts
  • 1048 Reply Likes
Mark, did you try disabling all the plugins temporarily to see if another one causes the problem?  There are at least three plugins that trigger this problem.
(Edited)
Photo of Bruce in Philly

Bruce in Philly

  • 9 Posts
  • 0 Reply Likes
Update.... still not getting the error. ..but...when I select multiple pics, in Library, then delete, sometimes, only one pic is deleted.  There is a pretty serious bug in there.  

Regarding disabling plugins.... LogiOptions was only the last plugin I disabled.  I disabled one at a time, tested, still got the error.   LogiOptions was the last one so I assumed that was the evil bugger.  I did not try enabling the others.  The plugins I disabled prior were Photomatix, DXO 10 and 11 (there were two each... surprised to see the older version 10 in there), ColorChecker passport, HDR Efex Pro 2.  I also went ahead and disbled LR installed plugins like facebook, Canon and nikon tethering.  Again, the last I did LogiOptions so I assumed that was the bad boy but I am still getting odd behaviour with deletions albeit not that awful error.
oh,. ALL software operating system etc up to date.
FWIW:  I have anothe odd item that may be releated.... I get NOT RESPONDING... locks up... so I sit there... it eventually clears but if I hit alt-ctrl-delete, select Task Manager, then select Performance, then.. hit Open Resource MOnitor, the thing unfreezes.  Seriously.... this is highly repeatable.  As you can tell, I get this NOT RESPONDING quite a bit.

PeaceBruce in Philly
(Edited)
Photo of John R. Ellis

John R. Ellis, Champion

  • 3967 Posts
  • 1048 Reply Likes
Thanks for the extra details.
Photo of Mike Palomino

Mike Palomino

  • 1 Post
  • 0 Reply Likes
This reply was created from a merged topic originally titled Lightroom Classic: Error after deleting file from disk.

I get an error after deleting file from disk in compare mode.
Photo of John R. Ellis

John R. Ellis, Champion

  • 3959 Posts
  • 1046 Reply Likes
Try disabling the LogiOptions plugin.  If that doesn't help, as a test try disabling all installed plugins.  (Go to File > Plug-in Manager, select each plugin in turn, and click Disable in the Status panel on the right.)
Photo of Rick Butler

Rick Butler

  • 1 Post
  • 0 Reply Likes
This worked for me - thankfully!!
Photo of John R. Ellis

John R. Ellis, Champion

  • 3959 Posts
  • 1046 Reply Likes
Did you disable the LogiOptions plugin or some other plugin?
Photo of Francis Zera

Francis Zera

  • 8 Posts
  • 0 Reply Likes
I just started having this issue today; I have no plugins enabled, so there's nothing to disable.  Per a related post, here's the system info details for troubleshooting: 

Lightroom Classic version: 8.0 [ 1193777 ]
License: Creative Cloud
Language setting: en
Operating system: Mac OS 10
Version: 10.13.6 [17G65]
Application architecture: x64
Logical processor count: 4
Processor speed: 2.8 GHz
Built-in memory: 16,384.0 MB
Real memory available to Lightroom: 16,384.0 MB
Photo of dmeephd

dmeephd

  • 281 Posts
  • 61 Reply Likes
I've seen this error starting with 7.5 and it continues with 8.  I've seen it during writing XMP data, importing, and deleting files from the catalog and/or hard drive.

Odd thing is, the activity actually works with the sole exception that after deleting the image(s) from the hard drive, theerrormessage comes up and the images are NOIT deleted from the catalog.  I have to run the 'remove images' command again, this time specificing only from the catalog.  (A quick shows that the image files were indeed removed fromt he external drive, so it is unclear what LR is complaining about.)
Photo of Marcin

Marcin

  • 3 Posts
  • 0 Reply Likes
I have same situation. Lightroom always up to date. Current version: 8.0 Build 1193777, Windows 10. Every time when I run lightroom and want to delete something I got an error... This is for first file I'm deleting.. Any further "deleting" are going with no issues, unless I close LR and open again.
(Edited)
Photo of John R. Ellis

John R. Ellis, Champion

  • 3959 Posts
  • 1046 Reply Likes
Marcin, have you tried disabling all the plugins to see if one is the culprit? For some (but not all) occurrences of this error, a plugin has been found to be the proximate cause.  (I believe the plugins are not themselves buggy but triggering a bug in LR.)
Photo of Michele Bullock

Michele Bullock

  • 2 Posts
  • 0 Reply Likes
?:0: attempt to index field 'rootFile' (a nil value)

I just got this also while trying to delete 187 photos out of 289 from disk   Using latest LR Classic CC 8.0.  Has never been a problem before.  I don't use plug ins, but Adobe saw fit to install: Adobestock,Aperture iPhoto importer, Canon tether plugin, facebook,flickr,nikon tether. So I disabled all. Same result.  Restarted LR. Same error.  

 I am on a Mac and I did not upgrade so still using OS High Sierra 10.13.6.

Something happened recently to cause this error.  Has worked fine for deleting lots of photos before.
Photo of dmeephd

dmeephd

  • 281 Posts
  • 61 Reply Likes
Were the images actually deleted despite the error message?  I ask because this is what happened on my system (Mac OS Mojave, LR 8, MacPro, 128GB RAM).  The files are deleted but LR stops short of removing them from the catalog.  I have to run the command again, this time just specifying remove.
Photo of Michele Bullock

Michele Bullock

  • 2 Posts
  • 0 Reply Likes
Holy cow!  I think you are right.  WTHeck!  That never happened before!  It is still a bug, gives you a stupid error message, requires another step, but thanks for the work around.  Is there something I should do to make it work properly?  Did you get it to work right?  I have had good phone support from Adobe before. I have a MBP 2016 which has been nothing but trouble and 3 repair strikes for same port issue so Apple says they will replace it, but still waiting!
Photo of dmeephd

dmeephd

  • 281 Posts
  • 61 Reply Likes
I have no idea how to make this error message not appear.  I simply had to learn to work around it or ignore it.
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1510 Posts
  • 486 Reply Likes
If the issue is reproducible, please describes your steps and collect and share your Lightroom system info and the traceback logs and we will typically be able to pin point where it came from in the code. To collect the traceback logs, see https://forums.adobe.com/thread/925598. Thanks in advance.
Photo of dmeephd

dmeephd

  • 281 Posts
  • 61 Reply Likes
Reproducible?  It happens infrequently.  This error message appears in at least four documented (by others on the forum) functions: i.e., import, delete, writing xmp files, and keywording.  For all of these activities, nothing is being done which is out of the ordinary.

Next time it happens, I will send you a traceback log.
Photo of Donna Warshaw

Donna Warshaw

  • 1 Post
  • 0 Reply Likes
I am going to try uninstalling Logitech software which there are many complaints about
Photo of Marcin

Marcin

  • 3 Posts
  • 0 Reply Likes
Hello,

So I disabled all plugins and tried deleting photos.
Looks like Logitech plugin was causing this issue... I will keep trying and testing.
What is Logitech plugin for ?
I have Logitech MX Master mouse but I do not think the plugin is related to it ?

I have more plugins to test and we will see.

Marcin
Photo of John R. Ellis

John R. Ellis, Champion

  • 4002 Posts
  • 1055 Reply Likes
It appears that the Logitech Options software, which gets installed for many Logitech devices, added support for using the Craft keyboard with Lightroom Classic: 

https://support.logitech.com/en_us/article/Craft-keyboard-Crown-features-in-Adobe-Lightroom-Classic-... 

It seems the LogiOptions Lightroom plugin gets installed whether or not you have the keyboard.

With a recent release of LR, several plugins started triggering this error when users delete photos, including one of my own. I believe the underlying cause is a bug in LR's support for plugins, but I wasn't able to narrow it down sufficiently to file an actionable bug report. I was able to work around the problem in my plugin.
Photo of dmeephd

dmeephd

  • 282 Posts
  • 63 Reply Likes
As stated above, I see this error message for several functions, but not consistently.  In addition, I have no Logitech plugins at all.  Never had.

If the error message occurs consistently, then by removing a given plugin brings that behavior to a halt, one might be able to claim success.  However, intermittent behavior offers no such guarantee that the removal of the plugin worked.
Photo of John R. Ellis

John R. Ellis, Champion

  • 4002 Posts
  • 1055 Reply Likes
It's pretty clear from this thread that disabling particular plugins works around the problem for some but certainly not all.  Here are the people reporting that disabling LogiOptions helps:

https://feedback.photoshop.com/photoshop_family/topics/-an-internal-error-has-occurred-0-attempt-to-index-a-nil-value?topic-reply-list[settings][filter_by]=all&topic-reply-list[settings][reply_id]=19518613#reply_19518613

 https://feedback.photoshop.com/photoshop_family/topics/-an-internal-error-has-occurred-0-attempt-to-index-a-nil-value?topic-reply-list[settings][filter_by]=all&topic-reply-list[settings][reply_id]=19513648#reply_19513648

https://feedback.photoshop.com/photoshop_family/topics/-an-internal-error-has-occurred-0-attempt-to-index-a-nil-value?topic-reply-list[settings][filter_by]=all&topic-reply-list[settings][reply_id]=19518820#reply_19518820

https://feedback.photoshop.com/photoshop_family/topics/-an-internal-error-has-occurred-0-attempt-to-index-a-nil-value?topic-reply-list[settings][filter_by]=all&topic-reply-list[settings][reply_id]=19534027#reply_19534027

 https://feedback.photoshop.com/photoshop_family/topics/-an-internal-error-has-occurred-0-attempt-to-index-a-nil-value?topic-reply-list[settings][filter_by]=all&topic-reply-list[settings][reply_id]=19613674#reply_19613674

https://feedback.photoshop.com/photoshop_family/topics/-an-internal-error-has-occurred-0-attempt-to-index-a-nil-value?topic-reply-list[settings][filter_by]=all&topic-reply-list[settings][reply_id]=19836734#reply_19836734

https://forums.adobe.com/message/10712499#10712499


Photo of dmeephd

dmeephd

  • 282 Posts
  • 63 Reply Likes
Agreed.  If the error message occurs with regularity and then stops when the plugin has been removed.  That's basic troubleshooting 101.  However..., the appearance of this error message occurs infrequently and in coincidence with four different functions.
In decreasing frequency of appearance...
1.  Deleting & removing images — happens almost every time, disabling plugin has no effect
2.  Writing XMP files — happens when more than 1,000 images keyworded OR if error message aapears in the following case...
3.  Keywording (adding new to existing keywords to more than 1,000 images AND/OR deleting keywords incorrectly created by LR during keywording)
4.  Importing — less frequently in LR8; was more frequent in LR7.5
(Edited)
Photo of Andreas Balko

Andreas Balko

  • 1 Post
  • 0 Reply Likes
Disable "LogiOptions" plugin solves the problem for me.
Thank you very much.
With best regards
Andreas
Photo of Matt Coady

Matt Coady

  • 1 Post
  • 1 Reply Like
Count me into the group where LogiOptions is not the fix :(

Disabled and completely removed the LogiOptions plugin
Disabled all plugins
Removed all presets
Backed up library with integrity turned on
Restarted my computer
Optimize Catalog

I'm losing my mind. I need to batch delete photos.




EVERY TIME

Photo of Merk

Merk

  • 2 Posts
  • 1 Reply Like
I just started having this problem as well. In my case the exact error message is
"An internal error has occurred: ?:0: attempt to index a field '?' (a nil value)

For me this started occurring after i moved a folder containing multiple sub folders of images to a different drive. I did this outside of lightroom. When i went into lightroom and clicked on the folder and selected find missing folder, clicked on the new folder location, and that error pops up. 

If i however select 1 subfolder and point the subfolder to it's new location, that works. Each of the subfolders has subfolders of it's own so i don't think just the mere fact that there are subfolders involved is the problem, unless it's the total number involved. I also tried disabling all plugins. (i dont have the logitech plugin).

update: after updating each folder individually, one of the very last folders (of course it would be the last one) appears to have been the problem folder. It looks like i somehow had a duplicate copy of this folder already in LR at the new location. I would still say this is a bug though since LR should have a better way of handling trying to merge duplicates. If i select a bottom folder in this folder (no subfolders) it does pop up a useful message saying the folder already exists and asks if i want to combine them. 

Lightroom Classic version: 8.0 [ 1193777 ]
License: Creative Cloud
Language setting: en
Operating system: Windows 10 - Business Edition
Version: 10.0.17134
Application architecture: x64
System architecture: x64
Logical processor count: 28
Processor speed: 3.0 GHz
Built-in memory: 32470.0 MB
Real memory available to Lightroom: 32470.0 MB
Real memory used by Lightroom: 1360.2 MB (4.1%)
Virtual memory used by Lightroom: 1330.9 MB
GDI objects count: 705
USER objects count: 2089
Process handles count: 1954
Memory cache size: 370.8MB
Internal Camera Raw revision: 61
Maximum thread count used by Camera Raw: 5
Camera Raw SIMD optimization: SSE2,AVX,AVX2
Camera Raw virtual memory: 239MB / 16235MB (1%)
Camera Raw real memory: 239MB / 32470MB (0%)
System DPI setting: 96 DPI
Desktop composition enabled: Yes
Displays: 1) 2560x1080
Input types: Multitouch: No, Integrated touch: No, Integrated pen: No, External touch: No, External pen: No, Keyboard: No

Graphics Processor Info: 
DirectX: NVIDIA GeForce GTX 1080 (25.21.14.1701)
(Edited)
Photo of Ronald Byram

Ronald Byram

  • 104 Posts
  • 15 Reply Likes
This reply was created from a merged topic originally titled Error when deleting photo.

I get the same issue every time I delete a picture. Not sure what to do..

Note: This conversation was created from a reply on: Re: "An internal error has occurred: ?:0: attempt to index a nil value".
Photo of John R. Ellis

John R. Ellis, Champion

  • 3967 Posts
  • 1048 Reply Likes
Go to the menu command File > Plug-in Manager. If there is a LogiOptions plugin, disable it and restart LR.  If that doesn't help, try disabling all plugins and restarting LR. (To disable a plugin, in Plug-in Manager, select the plugin and click Disable in the Status panel on the right.)
Photo of Ronald Byram

Ronald Byram

  • 104 Posts
  • 15 Reply Likes
May I ask, anyone know what this LogiOptions plugin is for? I have disabled all plugins not used and testing. And yes with them turned off LR 8.1 seems faster!. Also the removal of the plugins has corrected issue. Thanks everyone for feed back! Happy New Year 2019
(Edited)
Photo of Michael Kaplan

Michael Kaplan

  • 4 Posts
  • 2 Reply Likes
It is installed by Logitech for mouse/keyboard. It is not needed. As soon as I disabled mine, everything worked perfectly.
Photo of John R. Ellis

John R. Ellis, Champion

  • 3965 Posts
  • 1047 Reply Likes
To build on Michael's reply, see this post for more details about LogiOptions: 
https://feedback.photoshop.com/photoshop_family/topics/-an-internal-error-has-occurred-0-attempt-to-...
Photo of Wouter van der Wal

Wouter van der Wal

  • 1 Post
  • 0 Reply Likes
Sadly I am stumbling upon the same error. Specifically when I try to relocate missing folders with pictures I moved from my internal HD to my NAS. I created a traceback log which can be found here: https://bit.ly/2M5FpYB 

This error is very easy to reproduce. It is consistent with several folders. When I try to relocate subfolders that is often no problem but sometimes it is. Even if that folder doesn't have any subfolders. I recently upgraded from Lightroom 5 to CC Classic  and imported around 50.000 new photos for a total collection of around 150.000. There has been quite a bit of reshuffling of files, locations and links but nothing Lightroom shouldn't be able to handle. 
Photo of Ronald Byram

Ronald Byram

  • 104 Posts
  • 14 Reply Likes
to the menu command File > Plug-in Manager. If there is a LogiOptions plugin, disable it and restart LR.  If that doesn't help, try disabling all plugins and restarting LR. (To disable a plugin, in Plug-in Manager, select the plugin and click Disable in the Status panel on the right.)