Recent content by George Potemkin

  1. George Potemkin

    Error Request for Progress Review – ipurch DB Abnormal Shutdown with WebSpeed Memory Violation and APW/AIW Lock Stack Errors

    Does each client connect to all these databases? Is ipurchprod the first database the clients connect to?
  2. George Potemkin

    Error Request for Progress Review – ipurch DB Abnormal Shutdown with WebSpeed Memory Violation and APW/AIW Lock Stack Errors

    src/web/objects/web-disp.p is a standard program but your application calls it from $DLC/src. It can be a customized version. tptstart-new.p is a part of application.
  3. George Potemkin

    Error Request for Progress Review – ipurch DB Abnormal Shutdown with WebSpeed Memory Violation and APW/AIW Lock Stack Errors

    The probability that the cause is rcode corruption is, IMHO, very low. Upgrade your Progress version first.
  4. George Potemkin

    Error Request for Progress Review – ipurch DB Abnormal Shutdown with WebSpeed Memory Violation and APW/AIW Lock Stack Errors

    There are many articles about error # 1179.
  5. George Potemkin

    Error Request for Progress Review – ipurch DB Abnormal Shutdown with WebSpeed Memory Violation and APW/AIW Lock Stack Errors

    You know the rcode's names
  6. George Potemkin

    Error Request for Progress Review – ipurch DB Abnormal Shutdown with WebSpeed Memory Violation and APW/AIW Lock Stack Errors

    Or rcode corruption, for example. Protraces point out that the same rcode and the same statement in rcode was running while the errors were issued. But the best choice is to upgrade your Progress version first.
  7. George Potemkin

    Error Request for Progress Review – ipurch DB Abnormal Shutdown with WebSpeed Memory Violation and APW/AIW Lock Stack Errors

    So BFP locks are zeroes - as expected. So it's not expected for latchId 18 to be mentioned in the errors.
  8. George Potemkin

    Error Request for Progress Review – ipurch DB Abnormal Shutdown with WebSpeed Memory Violation and APW/AIW Lock Stack Errors

    You only get stats for the first 15 latches. You need to press ENTER one more time.
  9. George Potemkin

    Error Request for Progress Review – ipurch DB Abnormal Shutdown with WebSpeed Memory Violation and APW/AIW Lock Stack Errors

    It's statistics since db startup. Type S to get statistics for a sampling interval.
  10. George Potemkin

    Error Request for Progress Review – ipurch DB Abnormal Shutdown with WebSpeed Memory Violation and APW/AIW Lock Stack Errors

    Enter <return> for more.
  11. George Potemkin

    Error Request for Progress Review – ipurch DB Abnormal Shutdown with WebSpeed Memory Violation and APW/AIW Lock Stack Errors

    Type: debghb Press ENTER Screen will stay unchanged Type: 6 Press ENTER and you will get This menu is not here Menu
  12. George Potemkin

    Error Request for Progress Review – ipurch DB Abnormal Shutdown with WebSpeed Memory Violation and APW/AIW Lock Stack Errors

    promon R&D debghb - in V11.7 you need to enter a secret password; 6 - a hidden menu ("This menu is not here Menu"); 11. Latch Counts
  13. George Potemkin

    Error Request for Progress Review – ipurch DB Abnormal Shutdown with WebSpeed Memory Violation and APW/AIW Lock Stack Errors

    Example: 07/01/26 Activity: Latch Counts 15:51:15 07/01/26 15:41 to 07/01/26 15:51 (10 min 1 sec) ----- Locks ----- ------ Busy ------ Naps ---------- Spins ----------- ----- Nap Max ----- Owner Total /Sec /Sec...
  14. George Potemkin

    Error Request for Progress Review – ipurch DB Abnormal Shutdown with WebSpeed Memory Violation and APW/AIW Lock Stack Errors

    When db will be up and running again check promon / Activity: Latch Counts Does BFP latch (latchId 18) activity is zero for intervals when backup is not running? It's HIGHLY recommended [2026/07/18@12:46:29.000+0000] P-6251 T-139917056815360 I WSAGENT 0: (49) SYSTEM ERROR: Memory violation...
  15. George Potemkin

    Error Request for Progress Review – ipurch DB Abnormal Shutdown with WebSpeed Memory Violation and APW/AIW Lock Stack Errors

    It's very difficult to answer these questions for memory violation errors. Strictly speaking, it's not an error, but a consequence of an error. The bug caused an access to an invalid address. As a result, the code received or modified invalid data. This will continue until the invalid address...
See more
Back
Top