Registry error: Unable to find key HKEY_LOCAL_MACHINE\SOFTWARE\Neolane\NL_5\nlclient\ | Community
Skip to main content
November 26, 2019
Solved

Registry error: Unable to find key HKEY_LOCAL_MACHINE\SOFTWARE\Neolane\NL_5\nlclient\

  • November 26, 2019
  • 4 replies
  • 16012 views

I am getting the above error when attempting to open Adobe Campaign Classic - Client Console. I have checked the Roaming folder and I do have Neolane\NL_5\nlclient\ directory. I have nothing in the nlclient folder. I have tried to re-install the client on my machine and am still receiving the same error and unable to log in.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by anshuld20839734

This issue came after a system update. Opening the client console as Administrator fixed the issue. 

Go to start and on Adobe client icon "Run as administrator"

4 replies

Jyoti_Yadav
Level 8
November 27, 2019

Hi,

Type 'regEdit' in your start 'Search Command' and Navigate to:

HKEY_LOCAL_MACHINE/Software/Neolane/NL_5/nlclient.

If Neolane folder is present, delete it and then try to reinstall the Neolane folder.

Also check whether you have :

HKEY_CURRENT_USER/Software/Neolane/NL_5/nlclient folder present or not.

and define value for

confAdvisedUpgrade

It should be your build version.

Thanks.

Manoj_Kumar
Community Advisor
Community Advisor
November 27, 2019

Just restart your machine and it will be fixed.

Manoj     Find me on LinkedIn
Prem_Kumar_Gane
Level 3
November 27, 2019

Trying Clearing the Hard Cache from the below path  and follow these steps


  • Windows 7: C:\Users\<Username>\AppData\Roaming\Neolane\NL_5\
  • Windows XP: C:\Documents and Settings\<Username>\Application Data\Neolane\NL_5
Here you will see many xml files named nlclient-config-<alphanumerical value>.xml.

  • Delete these xml files and associated folders.
    Caution:Do not delete nlclient_cnx.xml file.
  • Sign in to client console.
anshuld20839734
Adobe Employee
anshuld20839734Adobe EmployeeAccepted solution
Adobe Employee
July 15, 2020

This issue came after a system update. Opening the client console as Administrator fixed the issue. 

Go to start and on Adobe client icon "Run as administrator"

Level 2
November 18, 2020
This fixed it for me. Thanks!