We have a licenced setup with one server and two terminals which has been running fine for several years. As the restuarant is getting busier the customer requested a third terminal. We were at version 5.3.6 so I started by upgrading to the latest V5.5.4. All went well with the server and the two original terminals are showing the correct licence info. When I tried to add the third terminal (with new install of SambaPOS) it is showing Demo in the licence display and unregistered trial.
If I go to Samba Market > activate and enter the licence details it says incorrect email/password, which it isn’t as it is the same as I entered on the other terminals. I have tried several times so also not a typo. If I go to Samba Market I have the following
I am reluctant to click “clear licences” as the system is live, but I am guessing that is what needs to be done. Can anybody confirm this, or advise what is required?
Apart from the licencing issue the terminal works fine with database and message server connected correctly.
You only license the server. Please shutoff all terminals then license the server and start Sambapos on it. Then once it’s started you can startup the others and it should be fine.
Yes the same issues, I have tried to repair sambapos dependency from net framework and etc, and the end I choose reinstall windows, solves the problem.
From my own personal experience with v5.5.4 now with a few setups, this is what I found and the only way I can get licensing to work now:
The account you run SambaPOS on has to have full admin rights on Windows
You need to run licensing.exe on the same Windows account as you run SambaPOS
You need to run licensing.exe on EVERY terminal - this goes against what @Jesse says however to date I have never once been able to only run it on the server.
This is a real pain and far more effort than needed in the past, and also a security concern since SambaPOS must now be on a windows account with full admin rights so staff can mess with any windows setting now if they wanted to. However so far this is the only way I can get the license to “stick” on multi terminal setups. :
My understanding is that SambaPOS licensing.exe and the SambaPOS software is wanting write access to the registry, and if it doesn’t have this access, it goes back to trial and you have to complete the steps again. Even once it is activated, if you then set the windows account back to a standard user (no admin rights) then you run SambaPOS again on that account, it goes back to trial.
The licencing is a bit strange now. Having spent some time on this on Wednesday, I sent this post to the forum and went home. Yesterday, I came back, switched on the terminal and it picked up the licence info and all was good. None of the other terminals and in particular the server had not been switched off in the interim. So essentially I did nothing and it worked!
The terminal in question is booting from a local account and does not have admin rights: The two existing ones are the same. Server currently has admin rights and is using a microsoft account. I was planning to change it but I think now I will leave it for a while and see how it goes. So far (one day only) all terminals have retained the licence info.
I’m sorry to bump this up but I’m trying to figure this out but can’t. I recently moved samba database to new computer with windows 11, i cleared licenses on old computer and also in my samba.com account. I have set everything up (database, message server, opened ports) and when i run licensing.exe it says login was successful but when I go to samba market on POS it shows email on top right in red letters but not where it says that this “licensed to” on left side under samba version number. Also when try to connect other windows terminals it says they don’t have valid licenses even though they are connected to database and message server. I have followed other instructions here to try and reset license but nothing has worked. I went as far as resetting windows on terminals and fresh samba install and it still doesn’t work.
Some help would be greatly appreciated
