This article is a guide for troubleshooting common issues with QSR integration.
If you are having trouble with the POS sending products to QSR, there are a few errors you will receive when the QSR peripheral isn’t configured correctly. The errors are written to the POS log located in ‘C:\ProgramData\SkyWire\SkyWire POS\Logs.’ The errors below indicate that there is an issue with communication to the QSR server:
[ERROR] 1 SkyWire.Pos.Peripherals.Services.PeripheralService - System.InvalidOperationException: Sequence contains no matching element
[ERROR] 1 SkyWire.Pos.Peripherals.Services.PeripheralService - System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 10.250.15.57:80
To correct this issue, make sure that the URL has the correct IP and port number as shown below:
Note: The correct IP is location where QSR is installed and default communication port number for QSR is always 32768
The error below indicates that the URI specified in WebConfig for the QSR peripheral is invalid:
[ERROR] WorkPool-Session#1:Connection(d3385c57-9713-4563-bd3e-5844d371ee42,amqp://localhost:5672) SkyWire.Pos.Messaging.RabbitMq.RabbitMqSubscriber - System.UriFormatException: Invalid URI: The URI is empty.
To correct this issue, make sure that the URL header is in the Sever URL field in WebConfig as shown below:
QSR Specific Issues
There are instances where orders may fail to send to QSR due to the QSR Kitchen server at the interface. To check on the status of the Kitchen server service, log into the property interface, open windows services and make sure that the QSR services are running.
