Below are a number of common errors that you may encounter when starting Retailer on the MAIN/SERVER computer.
The Transaction was Corrupt Due to an Earlier Failure / Cannot Locate or Connect to Network Server
When a computer shuts down unexpectedly or incorrectly, it can affect the service that runs Retailer. If this happens, you may see the following error message on your MAIN computer.
To fix this issue, follow the steps below:
- Access the Task Manager by pressing [Ctrl]+[Shift]+[Esc] on the keyboard.
- Click on the Processes tab on the top-left.
- Depending on your version of Windows, you may have to click More Details at the bottom of the window.
- Look for and click on RetailerV3.
Select End Process / End Task and confirm, if prompted.
Repeat this for all instances if there are multiple instances of RetailerV3. - Look for and click on NexusDB Server (Retailer 3) or nxServer (Older versions of Retailer).
Select End Process / End Task and confirm, if prompted. - Start Retailer again.
Retailer Stuck on 18% (Merging Menus) When Loading
If the printer settings on the terminal have changed, Retailer may get stuck at 18% while starting up. This can be caused if there is no Default printer selected in your computer, or if the Default printer cannot be connected for some reason.
https://support.microsoft.com/en-au/windows/set-a-default-printer-in-windows-e10cf8b8-e596-b102-bf84-c41022b5036f
You may also wish to consult an IT tech on how to do this.
Retailer Stuck on 59% When Loading
When Retailer is closed while it's in the middle of a task, it can sometimes get stuck at 59% when you try starting Retailer again.
To fix this issue, follow the same steps as the section above to close the background processes from the task manager.
Cannot Connect to Local License Manager Service
This error occurs when Retailer is unable to communicate with our serialisation server, which could be due to a number of reasons.
- Open Retailer Backup.
- Click Settings -> Database Settings in the menu on the left.
- Click Install LM service.
If you continue to get the error, please contact the Tower Systems Support team.
Error 404 or Error 409
This error occurs when the check with our serialisation server detects a change regarding serialised computers. A change in your hardware configuration can also cause this error.
Please contact the Tower Systems Support team if you get this error message.
Unable to Communicate with Service Controller
- Press the [Windows logo key] + [R] on your keyboard. This will open the Run dialog box.
- Type services.msc into the Run dialog box and press [Enter] or click OK.
- The Windows Services app will open, displaying a list of all services running on your system.
- Scroll down the list and click on Tower Security Service.
- Click Start the service or Restart the service on the left hand side to start the service again.