Negative.lua:223: attempt to index local 'i' (a nil value)

Suggestion to move the plugin folder outside of the protected Program Files/Adobe/Adobe Lightroom Classic/ location worked. I compared the permissions on the plugin folder when under Program Files and outside and the difference appears to be in the Authenticated Users entry with rwx permissions which is missing when the plugin is placed under Program Files. Adding this permission to the plugin folder makes it work even when placed under Program Files/Adobe/Adobe Lightroom Classic/.

Another approach that worked for me is placing the plugin under C:\Users\<UserName>\AppData\Roaming\Adobe\Lightroom\Modules (as suggested also at Adobe Forums). Note that in my case the Modules folder was missing and had to be created manually. After that though Lightroom has automatically found the plugin and it worked without errors.

There is still one other concern. Since my plugin was not registered yet on Windows, I tried to do that but the registration was not saved and the plugin was still in trial mode on the next Lightroom start. It only succeeded when starting Lightroom with Administrator priviledges and registering. It worked well with regular starts afterwards. This might be a part of the same permissions issue which this topic is about.

The only reason I don’t broadly recommend this is that I don’t believe this will work if you are saving your presets with your lightroom catalog (rather than the default location). So for about 10% of users, it won’t work as expected.

Good to know. I’m not really sure why this is only needed in some situations. I haven’t been able to replicate the permissions issue on my own Windows machine, no matter where I put it. Oh well, the ways of Windows are sometimes mysterious. :slight_smile:

Hello, I tried your suggestions above, i.e the AppData\Roaming etc. path. No luck so far.

I noticed that once it’s placed in that path you can no longer remove it through Lightroom, the Plugin Manager “Remove” button being greyed out. As for why it doesn’t work, I’m guessing it’s most certainly folder permission related as I get the lua:223 error on any photo, RAW, jpeg etc.

I’ve tried moving it to other folders, restarted Windows. I haven’t reinstalled Lightroom 6 yet though that will probably be the next step. I’ll keep the forum posted.

Try this:

1) In Windows file explorer, navigate to where you have placed the NegativeLabPro.lrplugin folder that you are using in Lightroom. Right click on that folder.

2. Select "Properties"

3. In the properties dialog, move to the “Security” tab. Select “Authenticated Users”, then click "Edit"

4. To the right of “Full Control” hit “Allow”. Then click "OK"

5. Restart Lightroom (if it is open) and try again.

Hi Nate, I tried your solutions, no luck. I’ll continue tinkering. But thanks for the quick reply!

Hmm… :thinking:

And you’re sure that the file names do not contain any symbols?

You’re sure that the files you are trying to convert are available and not just previews? (For instance, if the original files are on an external hard drive that is not currently connected, that would cause an issue)

The only other thing I could think of is perhaps you have an anti-virus program that is not allowing it to run…

Yes, I thought of that too. My Anti-Virus is disabled, no luck on that front.

As for the file name, I DSLR scanned a picture yesterday, named it “Test”. As its Olympus raw format the file extension is .ORF
Unless its the file format that’s throwing NLP off, though I’ve tried a bunch of JPEG’s and same story.
I’m sure there’s a real simple answer to this :thinking:

As for the the file location, the “Test.ORF” file is on my desktop. I tried putting it on D: drive, same story.


Could you go to “help > system info” in Lightroom and copy/paste that info and PM to me?

Another thing you might try is going into the folder " NegativeLabPro.lrplugin/win" and double clicking “convert.exe” to see if anything on your system prevents that from running…

Convert.exe functions, as in a DOS script style window pops up, runs through and closes.

Well, I’ve tried the various suggestions, I even downloaded the sample RAW files on the Download page. Nothing doing. I’m almost positive its something that’s blocking the NLP plugin from correctly launching. Trouble is, what? :face_with_monocle:

Just want to say that im gettign this issue too. Trying the trial version and was really hoping to buy this but its not working for me. I’ve tried all the suggestions in this thread and I get the same error message.


So… It now works. I have no, seriously, zero idea why. :crazy_face:

The only thing I have changed recently is I downloaded the latest Nvidia driver, though I do this regularly so it’s not as if the card was using a prehistoric driver.

I’m going to not touch anything settings-wise, try the demo for a week or so then buy it, if it still works. As far as I’m concerned it’s voodoo.

Thanks to Nate and the other posters for their solutions!

1 Like

after reading your update, i tried updating the driver for my GTX 1070 to the September 10th 2019 latest driver. it didn’t work for me :frowning:

Hi, Just downloaded NLP for mac for lightroom 6 and I’m getting the same issue, every attempt to convert gives negative:lua:223. Was there ever a cause/workaround identified?
DSLR scans held on NAS. Permissions appear to be OK.

@stagecoach - Not that I’m aware of. As I mentioned it just started working once I updated my Nvidia driver. I’m guessing it’s probably something else, and yes I did fiddle around with umpteen settings, changing the plugin folder etc. Not that I noticed this doing anything. Then it just worked. I suggest following the advice at the top of this post. Best of luck.

@nate You mention that the filename should consist of only numbers and letters. The first image I successfully converted was a canon CR2 file whose capture name was _IMGnnn.CR2 so I assumed _ was considered a valid letter. in my case all DSLR scans are of this form and containing folders contain spaces. The image that had the error was imported from a folder whose name contained a number of spaces.
If 2.1 fixes the naming issue, when do you expect 2.1 to be released?

  • stagecoach

Yeah, no problems with under-spaces… the problem was just certain characters that are reserved in the system to do other things, so I have to sanitize the name to remove those characters internally…

Hmm, that’s weird. I’m not aware of any issues with folder’s containing spaces in name… I have folders spaces and have not had this issue…

This is more likely what is causing the issue… I need to learn more about how Lightroom works with NAS… basically, Negative Lab Pro needs access to the full file (not just preview) - for it to work its magic… if it isn’t available it can cause the analysis to fail…

hi @nate, you are right, in my case it is the NAS that is causing this issue.
I made sure that the NAS was available and converted an image. I then unconverted the image and then forced the NAS offline. An attempt to convert again gave the error. I then remounted the NAS and tried again with the same image and it successfully converted.
Thanks, purchase imminent…

1 Like

Awesome @stagecoach, glad to hear that!

1 Like