I currently have only one active machine I am attempting to install/run on. This is a new machine to replace me earlier one which bricked due to a motherboard issue.
Yes, it’s Windows 10.
The reason my account history shows me revoking the same machine over and over is because that is what I was prompted to do by the plugin while attempting to sort out the license issue on my own. The first revoke you see is that bricked computer which I’m assuming is apparent due to that serial number being different from the newer revokes, where I see those are the same.
While attempting the online activation mode currently, it is still telling me to revoke my license and directing me to my account page which informs me I cannot revoke again for 30 days.
This leaves me with only the keyfile option. When I supply the keyfile obtained from my account page, the plugin tells me the activation failed and I should contact support, which I have done both via Zendesk and also attempted here.
It also occurred to me a few hours ago that the Ableton projects which exhibit the issue may have been running an older version of Kick 2 which seems to have received an update last winter (I missed that update at the time where now I am installing the updated version on the fresh machine which is leading to the issue being exhibited in those older projects which were created on that older machine and ported over to this one. I can test this later today when I get out of work by attempting to recreate the issue in a fresh project using a reset Ableton.
Note that I did somehow end up with two keyfiles - one keyfile indeed tells me the activation failed while the other tells me it succeeds but later reverts to evaluation mode. I can’t remember where that other keyfile came from; I assume I got it during one of the many reinstall attempts I’ve been doing since I first noticed the issue.
OK, understood the different step you took, so that’s clear for the online procedure, and the number of installation, thank you. I can’t see anything about your attempts and licensing BTW ( again just moderating here ) but that’s an update for support anyway.
Also when you’re writing about license key, do you mean the key file in your account ? Because that won’t work with the latest v1.1. version of Kick 2, that key file is only for previous version using the old authorization method.
IMO it seems like just a loop because of the revoking limitation, support should fix this for you, I’ve seen that someone replied to your 2nd post so the request is handled by them now IMO.
I’ll re-check this when I get home in a short while, but I’m assuming the “License Key” download button I see underneath the “Download v.1.1.1” button is the one I’m supposed to be using.
Somehow, I ended up with two keyfiles, which could not have come from the old computer running the old Kick 2, because I did not copy anything from that old computer before it failed (I had been backing up my Ableton projects via cloud storage which is why I have those on my new computer from the old one). One of those keyfiles gives me a success, which reverts to evaluation mode after a few moments, and I am able to use that to repeat that whole process; the other keyfile flat out tells me it fails to authorize and I should contact support.
As mentioned I will re-test a few things when I get home this evening and post a more detailed step-by-step for walkthrough purposes.
Thank you for the clear step by step description, definitely looks like the revoke devices attempts reached. Needs to be cleared by support. Allow them some time to work on your account and try to avoid new attempt for now on your end, it’s night time here anyway. Will ask them about this tomorrow again and keep you updated here, thank you.
Edit : forgot to mention, you should be able to see you devices management historical using this link once logged in on S.A website Sign Up
Haha yes I’ve visited that page a bazillion times already but it looks like there was a new revoke about half an hour ago which I’m assuming is from your support?
So should I continue to wait to hear back from support or can I go ahead with another reattempt?
I will do, though there might be a reason why the older license file is still available on the download page + there’s a red disclaimer warning users about that. Here is an actual screenshot from Firefox just made now :
Yeah I discovered that page after we started talking in this thread. The page in my screenshot is from the “My Account” main page which is the first page you come to when you log into your account and click “My Account”
How many device(s) are showing up active in there right now ?
If only one appears in the list, you could try a new activation but if it’s matching again your older PC ( defect Motherboard ) like it seemed to have done in first place, you may fall in the same problem again. I can’t tell what kind of ID they use to identify your device, I really don’t know about that, but it could be your Hard Drive or Ethernet card that was also used with your first configuration, therefore making a problem to distinct your new PC from the old one. So if you decide to try and if that doesn’t work, you’ll need to ask that they revoke all your devices.
This screenshot is what I see now. Note it’s different from when we first started talking here as Sonic Academy wouldn’t let me revoke the top one due to the limitation imposed.
This computer is completely different from that computer and that computer was the first one I revoked when this whole thing started. So I’m not sure how my hardware could be matching since that old computer is currently in the recycle bin. (Note it is possible to revoke one computer by logging into the account using a different computer)
So I’m assuming based on this screenshot that all my licenses are currently revoked which seems like a good sign as progress seems like it’s being made but I’m just not going to touch anything at this point and go have a beer to reduce my stress levels from all this with the hopes it gets resolved tomorrow
Have a good night and thanks again for the help!
Moderator edit : Removed the screen shot displaying ID, the forums are on public access for reading only, we don’t need this info here
First I want to thank you for your patience and help in this issue. I am currently working with support but in case anyone reading the forum is curious later down the road, the issue is partially resolved.
The new registration seems to take, and persist between saves, but whenever an older project that used Kick 2 is loaded initially, the Kick 2 starts in evaluation mode. I can delete the plugin, add it back, and it starts as registered, and I need to re-select the preset I used. It then seems to operate normally until the next time I re-load the project.
A brand new project seems to work fine. I can start a new one, add Kick 2, select my preset, save, close, and re-open that new project, which all works normally, so the current state of the issue seems to only be affecting my projects which were made before the issue started.
As mentioned, support has been great so far once we got in contact and progress is being made, so I will post updates as things move along.
Thanks for the kind words and no worries, I’m glad if that could help and yes, it’s nice for others members to keep the forum’s topics up to date when you get something sorted out thanks to the support team, good community behavior ! Thanks
My take on this is that it might also come from the way Live handles projects saving and the data being written in Ableton’s project files. Many times if you open a Live Project done with an older version of the DAW, it will ask you to convert it or warn you about compatibility issue. Another example is opening a previous project using older Live’s native plugins ( i.e : the older version of “Utility” ), you will see an “Upgrade” button displayed on the plugin if you are using the new version.
Removing the older instance of the plugin and replacing it with the new one and saving again your Live Project will solve this most of the time, so IMO, it’s a good habit to have with Ableton Projects across versioning anyway