Unable to login whil using correct Native ID password

olafmol · 2024-06-24T12:59:17+00:00

There was an error rendering this rich post.

Hello,

since last week my Native Access 2 (Version 3.11.1 (b2e0dd9 / 1.18.0.0)) does not let me log in again. I use a working Native ID account (i checked this by logging out on this website, and logging in again).

Interestingly enough, the old Native Access v1 let's me log in perfectly fine with the same account credentials.

What's causing this and how to fix this?

tnx, Olaf

Find more posts tagged with

Accepted answers

olafmol

after a full uninstall and reboot it worked (the second time, after "installing dependencies" became unresponsive and i had to restart Native Access again, duh)…. doesn't increase confidence…

All comments

olafmol

Also tried to reinstall Native Access 2, did not work.

PoorFellow

https://community.native-instruments.com/discussion/comment/161675#Comment_161675

There is technical differences between how the old and the new N.A. version works and it is possible that the problem is that N.A. 2 (3.x.x) has saved something wrong somewhere. So if you want to try to re-install N.A. 2 (3.x.x) then you would have to thoroughly remove any references to the old installation of N.A. and NTKDaemon prior to any attempted re-install from both drive and registry.

Else these are the links for N.I. Native Access and Installation Support and N.I. Account Support

olafmol

the thing is, it happened out of the blue, I was using native access 2 just fine with exactly that account.

PoorFellow

https://community.native-instruments.com/discussion/comment/161817#Comment_161817

You can try downgrading Native Access to 3.8.1 to see if that help

Courtesy Mert_NI : : NA 3.8.1 : WIN , MAC INTEL , Mac AMR (M1/M2/M3)

olafmol

after a full uninstall and reboot it worked (the second time, after "installing dependencies" became unresponsive and i had to restart Native Access again, duh)…. doesn't increase confidence…

Mert_NI

Hello olafmol, I'm happy that you could solve the issue even though it made you work a bit. We are aware of these kind of issues with the last update of the Native Access and we aim to solve these with the next update as soon as possible.

The workaround of PoorFellow looks like the correct workaround and if you have a similar issues you can follow this workaround until the next update of the Native Access. But as it seems solved for the moment, I'm happy about that☺️

Quick links

Unanswered questions