I have one RB433 running 3.30 and i try to upgrade to v4.
Update the Bootloader if using a RouterBOARD
Done
If already running RouterOS v3.25 or newer, Update your RouterOS license
I have tried, but without success before and after actual ROS upgrade.
“Update license keys” fail with following message:
“failed: key for specified software ID not found”
If you will use Netinstall for installation, make sure you have the latest version of Netinstall
I use combined package to upgrade.
After upgrade i get a message saying “Licence valid for 72 hours, please upgrade” and when i click on the ‘upgrade licence’ button, i get:
Licence updating: failed: key for specified software ID not found
I’have e-mail support@mikrotik.com with attached supout.rif file from upgraded ROS v4. I have open ticket [Ticket#2009101366000602] but no answer from support yet.
I had exactly this problem. In my case, the guys at MT were kind enough to furnish a new (correct) key.
They seemed to think that the router had a different SoftID to the one it was displaying in the licence mananager so somewhere, something is changing the SoftID and causing problems.
NAB, your problem was that you actually had pushed the button “Update License” way back in June, when we only added this button to RouterOS. At that time, there were still some issues with the new SoftID generation, so - after you upgraded from v3.24 to a newer version, the SoftID changed and stayed this way until you upgraded to v4. Only now you noticed this.
Here is my experience with RB133C SW ID issue: Every nand format process over terminal always cause changing “new” 9 digit Software ID (XXXX-XXXX). When you install old versions of RouterOS, like 2.9.51 or 3.13, problem doesnt appear, because these versions work with former 8 digit SW IDs (XXXX-XXX). So you need to Update SW ID only when you install new ones like 3.30 or 4.1. Then you have to access (after click update license via Winbox) your new licence hash for new 9 digit SW ID in you account at mikrotik.com. From now NEVER USE “format nand” over serial terminal, because this procedure change your 9 digit SW ID and there is only one chance to “upgrade” licence from the old one to new type of SW ID! Every further “format nand” procedure always causes changing 9 digit SW ID!
What was there to notice? As far as I was concerned, the licence upgrade had worked - certainly the RB was working properly with all the features enabled. How on earth was I to know that something was wrong. What, exactly, should I have noticed?
Am I right in understanding that it was your code which caused the problem? If so, I can only wonder why you think that I should have noticed something.
You don’t understand I don’t blame you. I said - back then, there was a bug in SoftID generator. It was then fixed, so your SoftID changed AFTER you already had upgraded the license.
I must admit that I was rather upset that MT’s support policy on the matter seemed to be to prove that I was at fault rather than to try and diagnose the problem. The fact that you only recently mention the SoftID has, I am afraid to say, reinforced that opinion.
However, I am glad you have managed to find and fix the bug.
I don’t blame you. I said - back then, there was a bug in SoftID generator. It was then fixed, so your SoftID changed AFTER you already had upgraded the license.