Agile-Developer
POS Issues Encounte...
 
Notifications
Clear all

[Solved] POS Issues Encountered After Recent Update

3 Posts
2 Users
0 Likes
26 Views
Posts: 220
Topic starter
(@banupriya)
Honorable Member
Joined: 5 months ago

Sharing the POS issues encountered after the recent update:

  • Out of System Error.
  • The Parameter is Incorrect.
  • Error Reading spbtncancel.
  • Error Reading spbtnok.

These issues are occurring on Axpert Version 9x, POS (03052024) Fix 7. Please find the issue screenshots that have been included below for reference.

2 Replies
Posts: 224
Admin
(@axpertsupport)
Estimable Member
Joined: 9 months ago

Two potential causes have been identified. The first is related to the SQL utilized in the POS screen, which is currently under analysis. If any changes are required, we will inform you promptly. The second issue involves random system errors and resource leaks, for which we have implemented detection tools to pinpoint the root cause and are conducting an internal investigation

Reply
Posts: 224
Admin
(@axpertsupport)
Estimable Member
Joined: 9 months ago

Have investigated the reported issues with Axpert POS 9.5. While they were unable to replicate these issues in our environment, we identified resource leaks in the product using exception handling tools. These leaks have the potential to cause Out of Memory errors and other system issues. We conducted a thorough investigation to identify possible causes and have applied appropriate fixes.

In addition to addressing these issues, we have incorporated an option in Axpert POS to manage unused memory, which is now configurable.

Following the implementation of these fixes, we conducted extensive testing involving over 120+ transactions across two different machines, during which no issues were encountered.

We are providing you with the Axpert POS Fix-8 binary. You can download it using the following link:AxpertPOS_95_Fix8_Binaries_ResourceleakFix_14062024_V1.zip

We recommend installing this binary on one machine initially and monitoring its performance for a few days before deploying it across all locations.

Installation instructions for the new binary:

  1. Stop Axpert POS if it is currently running.
  2. Back up your existing Axpert POS executable.
  3. Replace it with the newly shared Axpert POS exe (Fix 8), which includes fixes for resource leaks.
  4. Clear the existing axperterrorlog.txt file from the Axpert POS root directory (Errorslog folder).
  5. Run Axpert POS with highest privileges.

Regarding the configurable memory cleanup feature:
The necessary fixes have been integrated into the product. If you encounter errors such as 'Out of System', 'Parameter is Incorrect', or 'System Error' after installing Axpert POS Fix 8, you can enable automatic memory cleanup by adding a variable named 'Axp_TrimMemoryAfterNSaves' and setting its value. This variable accepts numeric values only. For example, setting it to 20 will trigger memory cleanup after every 20 POS transactions.

To disable automatic memory cleanup, simply remove the 'Axp_TrimMemoryAfterNSaves' variable from Axpert.

Please remember to log out and log back in whenever you modify variables to ensure changes take effect in the Axpert POS application.

Reply
Share: