What can I do if my hardware TSE takes a lot of time to respond after some idle time, or if the Middleware cannot access it infrequently?
lang-en, market-de, middleware, PosCreator, PosDealer, PosOperator
If the TSE (and therefore the Middleware) infrequently takes higher amounts time for processing requests, or some requests are infrequently processed by the TSE at all, it might be connected to the USB power saving mode. This should not be confused with the regular Windows power saving mode (which should also be disabled in case of errors), and can be set in the Windows Device Manager.
- Open the Device Manager
- Identify the USB device that represents the TSE, and also the USB controllers, card readers, and all other devices that might be involved
- Open the Properties of these devices, check if there's a Power Management tab (German: Energieverwaltung)
- Disable the checkbox left to 'Allow the computer to turn off this device to save power' (German: 'Computer kann das Gerät ausschalten, um Energie zu sparen')
- Either plug the device out and in again, or restart the machine
We have observed the following TSE-specific behaviors that could be connected to this issue:
- Swissbit Hardware TSE: After a few minutes of idle time, the first request to the Middleware takes very long (up to 30 seconds)
- CryptoVision/Bundesdruckerei Hardware TSE: The Middleware fails on processing requests and e.g. prints one of the following error messages to the log:
Response headers didn´t match.Expected <QWRWYW5jRUQgU2VDdVJlIFNEL01NQyBDQXJkAQ==>, but instead got <AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA==>
It's also possible to deactivate this power saving mode via Powershell, as described e.g. in this Technet thread.