Native access will not install, "ntkdaemon name too long", have uninstalled all NI directories

troby
troby Member Posts: 3 Member
edited November 2 in Native Access

I had a disk failure and trying to reinstall NI software. Native access will not install, gives an error about "… NTK Daemon name too long". I am doing a standard install in Windows 11 on C drive. Disk space is adequate. NA was working before the disk crash. No response from NI support.

Tagged:

Best Answer

Answers

  • antoniodominique
    antoniodominique Member Posts: 15 Member
    edited November 2

    did you check all you permissions I use a Mac but it could be that you don't have that folder or drive set up wit admin access juts a thought

  • PoorFellow
    PoorFellow Moderator Posts: 4,383 mod

    I had a disk failure

    I am doing a standard install in Windows 11 on C drive. Disk space is adequate.

    I had a disk failure and trying to reinstall NI software.

    NA was working before the disk crash.

    How did you 'recover' from said crash ? And what is a 'standard install' seen from your point of view ?

    I am asking because your experience is not "standard". If you put in a brand new drive , formatted the drive and installed Windows from scratch as a new user and then installed Native Access with all path settings left as default with 'adequate disk space' then a not standard experience would be kind of unexpected.

    No response from NI support.

    If a ticket has been correctly made and you got a ticket confirmation email then N.I. usually do respond given sufficient time , if you have not received a response within a week then update the ticket.

  • troby
    troby Member Posts: 3 Member

    Thanks all for your help. I did manage to install the NTK Daemon installer software, although it wasn't straightforward because for some reason it installed as a Google Drive file and it took me a while to figure out how to get the zip file to extract. It could not be downloaded and extracted normally. At that point I realized the problem was that I had symlinked the NTK driver to another disk (got tired of NI filling up my Windows drive with installs, even though I always try to direct the installs to other larger drives). Apparently the symlink was causing the error with filename too long (it wasn't long, it was the symlink that caused the problem). Now NI loads OK, and all I have to do is reinstall 30 years of NI products. That is, once I replace my failed 2 TB nvme drive so I have room for a new 400 GB NI install.

  • PoorFellow
    PoorFellow Moderator Posts: 4,383 mod

    Thank you for sharing what was the problem. It were sort of what I had expected that something else created the error that name were too long (error messages are never better than what they have been programmed to be). But great that you were able to diagnose what it was that you had done that gave the error 🙂

  • Mert_NI
    Mert_NI Customer Care Posts: 589 mod
    Answer ✓

    Hello troby, can you please create a support ticket or open a chat support using this link below:

    https://bit.ly/NI_support_NA

    So our team can help you further to solve that as soon as possible.

    I hope this helps☺️

Back To Top