I just try on MY computer, I open another user session, after the “no valid Licence install”, I could start the POS with the current WP started
2nd waitress has clocked in…
Right now I have:
On the SERVER, I have right now 3 windows sessions opened, with 3 SambaPOS programs running:
Abistro (the main)
On my COMPU:
Amazon Bitrso (just me)
Sorry, I cannot seem to get mult-session to work. Don’t know why.
Windows Users are different
Both instances have License Activated.
SambaPOS configured for different Terminal Name in each User Session.
Message Server is running, both sessions indicate connected.
Started WP on my main Windows Account.
Switched to 2nd Windows Account, run SambaPOS (or maybe it is already running), but WP is closed.
Switch back to main Account, WP is Open.
Switch back to 2nd Account, WP is Closed.
I doubt it was meant to run like that. Perhaps Emre needs to add some features to use it across sessions like that. Typically most places use single session and make staff use different sambapos logins.
Basically I did not change any settings at SambaPOS.
Then I added “terminals” - without knowing what is exactly is, maybe it is supposed to work as you say : 1 terminal = 1 supermarket cashier with own working period … don’t know.
No terminals is for connecting other physical computers to same database.
Until you use tablet - which makes your services 2 more efficient …
So RDP (which is really nothing more than emulation of Screen and Keyboard/mouse/touch)
So 2 concurrent windows sessions
however the problem is not “rdp/2 concurrent windows users” related
If using Windows tablets you don’t need RDP
Thanks ! I am asking that for a while now
I really want to know why - must be some loacl/terminal settings somewhere
Never touch “message server” settings, not configured by default
Splitting this Windows User Sessions to another Topic … please stand by…
Probably not. But there must be something “local” to the Session that gets set/unset when a WP is started (or not). Don’t know if it stored in a file somewhere or in the registry?
I always just assumed the way it determined whether the WP was open or not was to look at the
[Workperiods] table in the DB. If that was the case, then in the 2nd session, at least when SambaPOS is started, it would know the WP was open (or closed). This is obviously not the case for the Session scenario, but it is the method I have used in many coding scenarios (JS and PHP) to determine if the WP is open or closed.
And what is happening with the Messaging Service across Sessions? Are they still receiving messages from other Sessions? Who knows?
I found the problem.
The SambaPOS instances in the different User Sessions were configured to connect to different Databases.
The DBs are so similar that I could not tell just looking at the NAV screen.
On to testing…