Resolving “Transaction Failed due to DB error Try again…” in POS: Step-by-Step Solution

The “DB error Try again…” message during counter bookings in Point of Sale (POS) systems often points to database or synchronization issues.

Follow these steps to troubleshoot :

1. Check Synchronization
Start by verifying the synchronization process between the POS and Backoffice software on the server. Run a high synchronization and ensure it completes without any interruptions.

Download and Apply the Database Patch
Address any database inconsistencies by applying a patch:
Open a browser on the server system and go to:  http://172.19.64.105:8080/pos/Database_Build/Db_Patch_Renewal.zip
Download the Db_Patch_Renewal.zip file.

Run the Patch File

• Extract the contents of Db_Patch_Renewal.zip.
• Locate and run the DbActivity.bat file in the extracted folder.
• After running, look for the success message:  “Utility Executed Successfully”

Alternative Solution: Copy POS Folder from a Working System
If issues persist, this alternative may resolve them:
Copy the entire POS folder from a functional system.
Replace the po-connection.properties file with your system’s specific file.
Restart the system to verify the fix.

Perform Daily Synchronizations
Running daily synchronization will help maintain database accuracy and reduce error recurrence.

FAQs

Are these steps essential?
Yes, these actions target database synchronization and patching to prevent the “DB error Try again…” error from disrupting bookings.

Can this fix database issues?
In most cases, yes. The patch and synchronization process should resolve these database errors, and the POS folder replacement method serves as a backup solution if needed.

Another Issue: POS & Back Office Not Working on Client Systems While Server is Functioning Properly

Sometimes, client systems in a Post Office may face issues accessing POS and Back Office, even though the server is working correctly, all services are active, networking and sharing settings appear normal, and all systems are within the domain.

Solution for Client-Specific POS & Back Office Access Issues

This problem often arises due to one or more of the following factors:

1. POS Folder on Server Not Shared
   Ensure the POS folder on the server PC is shared correctly. If it isn’t shared, client systems won’t be able to access the required files.
2. Network Discovery Disabled
   Network discovery must be enabled on both the server and the client systems (nodes) to ensure they recognize each other on the network.
3. Corrupted or Mismatched po_connection File
   Check the po_connection file on client systems. If this file is corrupted or doesn’t match the server configuration, replace it with the correct version from the server.
4. Firewall Issue
   Sometimes, firewall settings can block access, particularly if there are custom rules. A recommended approach is to install Symantec Antivirus (AV) on all systems and ensure it’s updated with the latest patch. Symantec AV is known to handle network permissions and firewall settings effectively, which often resolves connectivity issues between client systems and the server.

The last point—firewall settings managed via Symantec AV—tends to be the most commonly overlooked. Implementing this step has proven successful in many cases and is worth a try if the other steps don’t solve the problem.

Summary

Checking synchronization, applying the patch, and, if required, using a working POS folder can restore proper POS system functionality.