TRAKTOR MK3 X1 ( An error occurred while processing your serial number )

Gusgudno
Gusgudno Member Posts: 1 Newcomer
edited October 22 in Native Access

I just bought my Traktor X1 (MK3) I've never had a native instruments product before besides an account I made 2 weeks ago. I open the box and plug in the device thru USB-C HUB and it lights up, Yet the 3 line on top the switch you from Mixer - Effects is the only light staying on after turning on. I then proceed to open Native Access and log in. I put in my Hardware Serial number yet the number seems to not work " An error occurred while processing your serial number; it stays like that everything I put it in and can move on in getting my Tracktor Pro 3 to connect to the X1 MK3. I also want to make sure my MK3 X1 is compatible with my MacBook Air M1 2020, Ventura 13.5.

Thank you I really need help and went ahead submitted 2 Tickets already.

Ticket Number - (4059333)

Tagged:

Comments

  • Mr. Nunez
    Mr. Nunez Member Posts: 1 Newcomer

    I am having the same issue. Its not accepting my serial number.

  • Mindproperty
    Mindproperty Member Posts: 1 Newcomer

    ~~~~~~I am having the same issue. Its not accepting my serial number.

  • ruslanchyk
    ruslanchyk Member Posts: 1 Newcomer
    edited September 2023

    Also having the same problem.

    Anyone hear from NI yet?

    EDIT: Just tried again and it worked!!!! Not sure what changed!

  • djSteele702
    djSteele702 Member Posts: 4 Newcomer
    edited October 2023

    Same here.... Bugs shipping with new firmware / software / hardware, sadly commonplace and widely accepted. But this.... this is nothing short of inexcusable.

    So what now, Native Instruments? 300$ paperweight until someone gets this sorted....


    Screenshot 2023-10-09 at 19.41.46.png


  • PoorFellow
    PoorFellow Moderator Posts: 4,814 mod
    edited October 2023
    https://community.native-instruments.com/discussion/comment/99303#Comment_99303

    Are you using latest version of N.A. ? If not , or if having problems installing the N.A: update then try downloading newest version of N.A. and install it on top of old version...

    Then , try running N.A. as an admin and then try again , if problem persists then contact registration support !

  • djSteele702
    djSteele702 Member Posts: 4 Newcomer

    I'm running v2 on my primary (Mac) machine, and I just tried installing it fresh on my Alienware running Win10. Now I'm not even able to reach support because I keep getting these "TypeForm Errors". This is just wild. Thanks for replying PoorFellow! I appreciate your effort.

  • PoorFellow
    PoorFellow Moderator Posts: 4,814 mod
    https://community.native-instruments.com/discussion/comment/99351#Comment_99351

    If you get errors in the internet browser then it is always a good idea to try another browser or two. I always recommends trying Vivaldi browser and Opera browser as alternatives , and remember to accept all cookies.

    With respect to the N.A. activation problem , then did you already try this trouble help ? : Native Access Error Message: "Activation failed...Internal error during activation" : https://support.native-instruments.com/hc/en-us/articles/360000848825-Native-Access-Error-Message-Activation-failed-Internal-error-during-activation-

  • djSteele702
    djSteele702 Member Posts: 4 Newcomer
    edited October 2023
    https://community.native-instruments.com/discussion/comment/99352#Comment_99352

    Hi PoorFellow - So the error message is in the actual Native Access 2 application, and I've tried it on both my Mac OSX 13.3 and Windows 10 machines. Here is the actual error:


    Serial Error.png

    EDIT Add info: I've also tried using my developer tools to try and get some insight on the actual error return code but I have been unsuccessful. I've tried attaching a debugger to the process and looking in memory, I've grabbed packets both to and from Native Instruments servers, and I ran a trace log through Apple's Console. I'm not seeing anything that indicates an error code (which isn't overly surprising as most internal application data is obfuscated by design for security).

    EDIT2: I followed your link (thanks for that by the way) and ran down their list. I verified the correct account was being used and all my other devices and software are associated with it. I then went in and deleted the "/Users/Shared/Native Instruments" folder, opened NA2, and input the serial to no avail. I also managed to access the NI support site finally (last night it was down) and submitted a ticket.

    I will continue to beatbox and pretend my X1 is functioning while I wait to hear from NI. Not impressed with the effects so far. They're getting saliva all over the booth ;)

  • PoorFellow
    PoorFellow Moderator Posts: 4,814 mod
    edited October 2023
    https://community.native-instruments.com/discussion/comment/99537#Comment_99537

    Sorry , if it were not "because of corrupted or missing activation tokens" as in help article then it could be a problem with the serial. Or if a more advanced problem maybe a problem for support. I did look up what people that previously have had that exact problem , but all I could find have had to contact support and also none of them returned with any feedback to the forum so really no statistics or explanations to support any conclusion other than most likely a case for support !

    So , sorry I can not do anything more other than say : please contact N.I. registration support so they can work it out: https://bit.ly/NIsupport_RA

    If you can not create a ticket then tell so here then we will call forum help staff that they may assist you in creating the ticket..

  • djSteele702
    djSteele702 Member Posts: 4 Newcomer
    https://community.native-instruments.com/discussion/comment/99543#Comment_99543

    It's funny because I had Day 01 issues with NI stuff going back to the release of the Maschine, then the Maschine Plus, and now the X1. If I remember correctly, the issue with the original Maschine was also related to registration. The M+'s went out with some strange issue with the firmware that bricked them right out the gate. I'll report back with what NI says the issue is this time just so anyone who reads through this post won't be left in a cliffhanger ending. Thanks again for all your help PoorFellow -- your time and efforts are greatly appreciated regardless of outcome. Cheers!

  • jori
    jori Member Posts: 6 Newcomer

    @djSteele702 Did you got the problem fixed? If so how did you fix it?

This discussion has been closed.
Back To Top

Categories