We cancelled a hung MRP task and then restarted the task agent. Are there any concerns with cancelling any tasks that are still in the status of ‘cancelling’ when the task agent is restarted afterwards without the task being fully “cancelled”? We’ve noticed that sometimes tasks stay in a status of ‘cancelling’ until you restart the task agent.
My regular maintenance schedule includes a restart the database and appservers.
Part of the reason for this is to clear out any hung processes and zombies.
As far as I know there is not anything to be concerned about but just in case, the first thing I always do is make full backups.
Epicweb used have an answerbook that recommended restarting on a regular basis.
I’m not sure if it still applies to E9 / E10.
A best practice for Epicor and any other application is to program to be prepared to clean up after an unexpected shutdown or crash. Even though Epicor seems to ignore most programming best practices, even they could not ignore this one, and it seems the Epicor does reasonably well in recovering from crashes and such.
Given that, what it says “Cancelling”, the process is in fact still running. The biggest pitfall with shutting down MRP while it’s running is that there will be suggestions and/or un-firm jobs still in the process deleted or created. It may seem that the list looks good, but how do you know? And is one only partially written? Is a flag still set that MRP uses in the middle of its processing? The best way to guarantee that you end up with good data is to perform a regenerative MRP after any such unplanned interruption of MRP.
we get this issue often, if I can’t cancel it i usually have to restart my APPSERVERS on the Report server.
A couple occasions where MRP wasn’t completing so someone had canceled the task, remained in sysmon with “canceling”.
Reminded me of a couple steps I did not mention
– ran MRP full regen on the live system after the restart… as you suggested.
— also restored that backup to a test system, probably overkill but just in case.
Luckily have not had any issues after restarts