So, one of our RB493s running 3.30 was all set to be upgraded to v4. Licence in new format? Check. Bootloader uploaded? Check.

After upgrade we get a message saying "Licence valid for 72 hours, please upgrade" and when we click on the 'upgrade licence' button, we get:

Licence updating: failed: this key is upgraded and have changed software ID!

Apart from the nonsensical language which doesn't help in diagnosing the problem, does anybody have any ideas?

I'll e-mail support@ when I'm at my desk tomorrow.

have you checked your 8-digit SoftwareID before and after upgrade? haven't it changed?

have you checked your 8-digit SoftwareID before and after upgrade?

It had a 7 character software ID, I did the upgrade and it now has an 8 character software ID. I upgraded it to v4.0 and it still has the same software ID. When I telnet in I get the following message:

ROUTER NEEDS A NEW LICENSE
----------------------------
This RouterOS version is designed to work only with new format RouterOS
keys. These keys can be recognized by the longer SoftID, which is 8
characters long, instead of previous 7.

But it definitely has an 8 chacter software ID.

Strange.

Interesting... As soon as I try to create a supout.rif file, CPU usage jumps to 100% and the box stops responds in jitters to command line/winbox commands in periods of about 6 seconds. The supout.rif file is never created and the only way of bringing CPU usage and responsivness back is to reboot the router.

Traffic passing through the router doesn't seem to be affected at all.

What a PITA.

Woohoo. After a few reboots and attempts to create the supout.rif file, it's finally done it.

CPU pegged at 100% and with very sluggish response still though.

Tried a backup/reset/restore and it's still just as sluggish as before - CPU at 100% and a "/export file=exp.rsc" took 31 minutes to run.

I think I've found a different bug.

If I create the supout.rif file as soon as the box is booted, the whole box becomes unresponsive and pegs the CPU at 100%. It stays like this even after the supout.rif file has been created.

If I do nothing after a reboot, wait for 5 minutes or so, the CPU climbs to 100% and then we have the same problem.

I'm now about to try this with a clean configuration to find out if it's the config's fault or the RB/ROS fault.

no, you definitely have a different 8 char SoftID now. What did you do to make it change? I see in our DB that you first clicked "update key", got a key, then did "something" and now you have a different SoftID. this is why it's asking you for a new key.

Hi Normis,

Replied via e-mail to support as well as here.

you definitely have a different 8 char SoftID now.

It's exactly the same SoftID I had prior to upgrading to v4.

What did you do to make it change?

Nothing. It hasn't changed.

I see in our DB that you first clicked "update key", got a key, then did "something" and now you have a different SoftID. this is why it's asking you for a new key.

That was today, after the problem arose and was just me trying to see if I could sort the problem out a different way. I added the old key, but it wouldn't let me generate a new one.

Things stand exactly as they were at 0917 this morning when I first raised the ticket.

umm, let's move this discussion to the support ticket. I hate to double post

One day gone and one working day left before the Routerboard stops working (48 hours before the temporary licence expires).

Luckily I trialled the upgrade on my home box before rolling out to customers.

If this isn't resolved by tomorrow, which lucky MT employee would like to speak to my wife and explain to her that they broke her Internet connection?

Seriously, you don't want to go there.

I now have a fully working RB493 running ROSv4.0.

Woohoo.

So, I'd like to say a public "Thank you" to the guys at MT for supplying a new key whilst they investigate the problem.

After updating the key, the CPU usage dropped back to normal and the DHCP servers started working again.

hmmm... somebody have already complained about high CPU usage with wrong license key %)

Hello Normis,

I have a similar issue. I upgraded my router from ver 3.3 to 5.o and its now saying my licence cant be found... ...why would this be sir?
my network is being threathened because of an upgrade to a newer version. P{ls fix this bug in your key server and keep my network for me

I have less than 24 hrs left to get a key licence after having used the router for 4 years

have you upgraded your key on v3.30?

when i did the upgrade to ver 3.3 in october last year i got a new softID and an Old ID thats whats being using until i did an upgrade to ver 5.0 and now its 18 hrs to go?

What help can i get from the forum pls? Mikrotik support is sleeping on this issue and am getting angry

Do i downgrade back to ver 3.3 somebody help!!!!

Efosa

reinstall (not sure about Downgrade, probably with NetInstall, tick 'Keep current config') v3.30, update your key to new format (via System -> License menu), then you can install any new version