We had a very strange emv reader situation yesterday and I’m wondering if anyone has seen something similar. For background, we’re RAMP, Worldpay and often use remote desktop/roaming profiles.
During the day, we had users at windows 1, 2, and 3 (these are essentially their assigned windows and they sit in the same places every day). Everything was working fine. For show time, user 3 went home, and user 1 turned off his PC and moved over to window 3, logging into the PC and Tessitura with his own credentials. He mentioned something about his emv reader not working, so I suggested restarting the tripos service. When he did that, the emv reader back at window 1 was affected. He did a pc reboot and same thing- even though he was now at window 3, the emv on window 1 was being affected.
We then tried having someone else log into the pc at window 3 and having the user log into Tess. That didn’t make the emv at window 3 work. Only when someone else logged into the PC AND Tessitura at window 3 did the emv at window 3 work.
I’m just very confused as to how the emv reader worked fine for nearly everyone, but when this one user logged into the pc and or tess at window 3, it was affecting the emv at window 1!
Thanks,Kathleen
We had this happen once when we were using Worldpay. We finally figured out that the user was not logging out of Tessitura on window 1 then came back from back and logged back into window 2. Even if Tessitura timed out, it still hung onto the session. Our best solution was to have them do a full logout of Tessitura AND the PC on window 1 before leaving if they planned on switching workstations.
Apparently those Worldpay readers somehow hold onto a session if you dont logout properly. It might take some trial and error to replicate it, that's what we ended up having to do.