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
Hi everyone -
As John and Grant have noted, this is a particular idiosyncrasy of Windows and how we serve the Tessitura application in Citrix. When you open Tessitura in the hosting environment, you are essentially logging in to a terminal server which then opens the Tessitura client. The terminal services connection caches the Windows machine name that you are logging in from, and passes that to Tessitura, which then determines which EMV device (from TR_MACHINE_SETTINGS) is activated. This is true with Windcave and Worldpay EMV devices.
If you jump from one computer to another without logging out of Tessitura and Citrix, your existing terminal services connection is re-established on the new computer (this is why Tessitura just "pops up") and the Windows machine name is not re-cached in the session. Doing a full logoff (or even ending your session in the Self Service tool) is a good way around this for users who move around frequently.
This is noted on the Defect List under "Reported Defects that Won't be Fixed" using key DEVOLD-4285 - as it is related to something in Windows that is beyond our control.
Thanks!
Patrick