could not create new file or truncate existing file

leifwyn
leifwyn Member Posts: 1 Newcomer

Hey,

I've recently bought a large (100gb) library and I'm trying to download via Native Access. I am getting this error - "could not create new file or truncate existing file". I followed the support page about have different locations and it's all good but still the error remains. Any help would be much appreciated thaanks.

ca

Comments

  • DifferentMusicProd
    DifferentMusicProd Member Posts: 2 Newcomer

    also having the same issue, followed everything as mentioned on the help site, but no solution so far

  • arcade
    arcade Member Posts: 3 Newcomer
    I am having the same problem on my mac.
    Everything was working fine until now.
    NA shows 3 Updates and all of them have the error.
  • DarrenMcMS
    DarrenMcMS Member Posts: 17 Member

    I fixed my disc mount error issue by using sfc /scannow and enabling virtual drive enumerator but now have the above error.

    FFS


    Going mentally unstable here.

    NI footing my medical bill lol.

  • DarrenMcMS
    DarrenMcMS Member Posts: 17 Member

    I fixed this by uninstalling everything ,reinstalling BUT install to the default location!


    Then finally everything is working ,hooray.

  • manutter51
    manutter51 Member Posts: 1 Newcomer

    I had this error on my Mac when trying to update Kontakt 7 and some other libraries on an external drive that had been disconnected multiple times from my laptop without being properly ejected. (I'm forgetful that way.) I opened up a Terminal window and typed in "cd /Volumes" to get to the directory where all my external drives are mounted, and I found two copies of my "One Touch" volume, where my NI libraries all were. The first one contained an empty "Native Instruments Library" directory, while the duplicate (named "One Touch 1") had all my files and folders. I assume that, in the process of being improperly disconnected, an empty directory was created with the same name as my external drive, and then when I re-attached my external drive, it was renamed to "One Touch 1" to avoid the name conflict.

    To fix it, I ejected my external drive (properly, this time), and then used "sudo rm -rf One\ Touch\ 1" to delete the bad directory, typed in my password at the prompt, and boom, the bad directory was gone. When I re-attached my external drive, everything connected properly, and the update went without a hitch.

    One other minor thing: The duplicate external drives did NOT show in in the Finder. I had to use the Terminal window to fix the issue.

Back To Top