There have been a few instances where MPOS crashes while processing a transaction or the RTS times out saving a customer order. In normal circumstances, this transaction persists in the cart when you log into MPOS again so that you can complete the transaction. But it is possible that you may run into an instance where a split tender was performed with a credit card showing processed while the transaction failed to save processing the cash tender as the RTS call timed out. AX is showing this order successfully invoiced, but POS still thinks it needs a payment. Thus the transaction will not allow you to accept a payment nor void the payment/transaction and it is stuck!
If you are simply looking to remove this recalled transaction from the MPOS cart, follow the steps below:
1. Close MPOS
2. Go to the file location (C:\Users\Administrator\AppData\Local\Packages\Microsoft.Dynamics.Retail.Pos_8wekyb3d8bbwe\AC\Microsoft\Internet Explorer\DOMStore\X2XSTARI\microsoft.dynamics.retail[1]
3. In the Explorer window click View >> Options >> Change folder and search option.
a. Enable the Show hidden files, folders and drives
b. Disable the Hide protected operation system files
4. Edit the microsoft.dynamics.retail[1] file in NotePad or another editor
5. Search the text file for CART to locate the start of the string <item name=”CART” value =
6. To resolve this issue, you can simply update the text file to remove the transaction details of the CART. What I did was copy the value of an empty cart such as the one below over the value of a cart with an item.
<item name=”CART” value=”{"CartLines":[],"Id":"","ShippingAddress":null}” ltime=”2136110528″ htime=”30567907″ />
Spaces were only added in the text of the screenshot below to help pinpoint the CART string value.
(Click picture to enlarge)
7. Once you have this updated, save the file.
8. Log into MPOS and the cart should be empty again.
Important Note:
You will also want to review the transaction in the RETAILTRANSACTIONTABLE and other related tables in the event that this transaction was partially written. You would want to verify the values in the tables to avoid any Retail statement posting issues or orphaned posted records.