Update: I restarted the utility, and it completed, but no more records were deleted. When the error occurred on my first run attempt, it must have been done running through records, it just couldn't exit out of the program gracefully.
------------------------------
Jane Scanlan
Partner
Next Level Manufacturing Consulting Group
------------------------------
Original Message:
Sent: 08-09-2024 20:08
From: Jane Scanlan
Subject: Error 33 during Purge Completed Purchase Orders utility
Thanks @Robert Osborn! I got out of the error and have restarted the utility. Before I restarted it there were ~20k purchase orders already deleted, so I'm sure this will complete on this second attempt.
This can be moved out of urgent support.
------------------------------
Jane Scanlan
Partner
Next Level Manufacturing Consulting Group
------------------------------
Original Message:
Sent: 08-09-2024 19:24
From: Robert Osborn
Subject: Error 33 during Purge Completed Purchase Orders utility
Hi Jane, I have run into similar cases like this. Appears that the routine maxed out the memory on the system (bad comparison but like when you try to load Physical Count when there are a ton of items). Since this is a purge routine, I would just close out and restart it. You can check to see if the count of POs in history has changed (most likely has). Start up the routine again and there will be less records for it to go through. Might take more than one pass to get rid of all of them. Another thought - as they are on premium, you could remove the history from the SQL tables directly if you are game for doing that. One of the pluses of being on premium..
------------------------------
Bob Osborn
Consultant
ACI Consulting