Hello,
Since a couple of months, I have had a problem with my licence.
3-4 times a week waitresses are calling me because they cannot use sambaPOS.
SambaPOS freezes and licence is deactivated.
So what can I do to fix that?
Thanks,
Marc
Hello,
Since a couple of months, I have had a problem with my licence.
3-4 times a week waitresses are calling me because they cannot use sambaPOS.
SambaPOS freezes and licence is deactivated.
So what can I do to fix that?
Thanks,
Marc
Hello,
You can migrate the latest version, SambaPOS 5.5.2. Licensing has been changed in this version.
https://kb.sambapos.com/en/2-5-how-to-handle-licensing-on-sambapos-5-5-and-higher-versions/
Have a nice day.
Hi,
Thanks for your answer.
I am on SambaPOS 5.3.0, DB 153
In real life, I cannot upgrade now nor in a near future, we open 20hours a day, 7/7, 1 server with lots of tayloring + 3 terminals.
Is there another way to get rid of the licence deactivation, like the cleaning of the key, etc … ?
Maybe disconnecting the terminals from internet (the server has always been offline after initial install)?
Thanks,
Marc
it takes literally seconds to download and install the new version and it will probably fix your issue and other bugs you arent aware of. If the licence is causing such a big issue to you then just update to newest version which should solve your issue
Literally takes 30 seconds to doenload and install
So, somebody knows if it’s possible?
Hello,
This situation might be caused by various reasons that we can’t be aware of.
Some of them are below;
These are some of the possible reasons for the general cases, other than that we can’t tell you any specific reason for it.
In order to find out the reason of the problem, turn auto backup feature off for a while on the main computer that SambaPOS is installed;
Main Menu > Manage > Settings > Database Backups > Settings > Uncheck Auto Create Backups after Work Period Ends
Have a nice day.
Thanks a lot for the information.
Yes we are subject to a lot power outages.
I’ll also monitor the backup and the logoff process.
![]()
This morning, again, unregistered.
I checked the backup process and no backup was made because they closed the working period on a terminal and not on the server.
Could that be the reason why it deactivates the licence?
Note: This time the “unregistered” happened when opening working period, but sometimes, “unregistered” happens during working time.
Thanks
It will be really hard to know for sure. We fixed these issues with an entire new license engine in 5.5
Do the terminals have both wifi and ethernet connected?
We ran into a similar issue a while back and traced it down to wifi going down intermittently and would fall back on ethernet and the licenses would mismatch.
Some digressions
We are in though environment. Power outage and internet failure are almost daily events.
Isolated in the amazon rain forest, so no electrical grid and no stable internet connection in a city of half a million persons.
And I think it’s important SambaPOS can still be easily used in such environment because power outages and internet failures might now happen in more and more places in the world.
To answer to Memo, here is our setup.
In the rack:
In the Restaurant:
3 android tablets wireless-remote-connected to the above computers. (not with RDP though, android client too slow, but with nomachine, surprisingly fast)
At the end of the day, 1 waiter left, “must” close working period on the Server (remotely).
Is there a way to see on which terminal (server/term1/term2) was closed the work period?
When “licence unregisters”, I activate it back on one of the mini PCs (terminal) as they are connected to internet.
I then close SambaPOS on the server and run it again, and licence is activated on the server and everything is fine. Until the next “unregistered”, which now happens more and more often.
Yes I agree and it is partly why we redesigned the license engine with the new version and company redesign.
Ok.
I’ll update.
App 5.3.0
DB 153-153
Some questions, I have:
I guess
Thanks
You can install it to another system and compare. We can’t support these types of modifications unfortunately. But if you look at it and compare it should help get your answers.
On upgrade, SambaPOS will only modify what it knows to exist. It does not recreate a db on upgrade. Your additional tables/triggers, etc. will not be affected (unless referencing something in the primary schema that may have changed).
There appears to be no changes to the orders table that would cause queries written against the 5.3 db to fail.