Transaction Server Configuration Issue: An error has occurred in retrieving the selected transaction

Transaction Server Configuration Issue: An error has occurred in retrieving the selected transaction

************** ************** INTERNAL KB ************** **************

Version:

iVend 6.6

Issue:

Store POS not able to fetch transaction details from the enterprise server, below is the error Pops-
up when clicks on Transaction search screen at POS:
"An error has occurred in retrieving the selected transaction from the server. Do you want to continue 
with local transaction?" 
Below is the screenshot of the error:
When Clicking on "Yes", then if transaction is from same store then result will be displayed, if transaction 
is from other stores then nothing will be displayed. 
If clicked on No, then nothing will be displayed and POS will move to home screen. 
Notes:
Transaction Server:: This section is enabled only if the user has purchased a license for the 
Transaction Server. This helps to fetch the transactions done at other stores also. 
Below are 2 ways to perform Transaction Search at POS: 
•Local: Shows the transaction search result by doing the transaction search only on the local store server. 
•Local and Enterprise: Shows the transaction search result by doing the transaction search at local and at 
the Enterprise Server. 
To open the screen at Enterprise MC >> Administration > System Initialization > Enterprise >>  Section 
"Transaction Server" 
Below is the screenshot for the same:

Solution:

After enabling the transaction server (with the option "Local and Enterprise")when searching 
any transaction at POS then the system was throwing the above error and was not able to fetch data 
from the enterprise server even there was no error logged to the POS log file. It was identified that there 
was some backup copy of trxtransaction table created at the enterprise server database which was 
causing the issue and not allowing the system to fetch details from the enterprise server.
Once deleted the backup tables related to the trxtransaction table,the issue got resolved.