When running Calculate Global Scheduling Order for the first time on Epicor 10.2.500.17 database converted from Vantage 6.1 task immediately cancels. What are we missing?
Thanks for any advice.
Jill
I’ve seen scheduling residue for job(s) on newly converted systems that will crash the process.
I have had to manually remove job(s) from the schedule (Job Entry - Actions) before the Calc Glob Sched Order would run to completion.
Can be tedious if you have a lot of jobs.
And the the trick (for me) was identifying only those jobs that I needed to remove from the schedule.
e.g. start Calc Glob Sched Order with logging
watch the System Monitor to see when it has crashed
then check log for jobs processed
---- the tricky part (if I remember correctly) is that the problem job will not listed in the log
---- only successfully processed jobs will be listed
---- so… I had to find next open job in the system… AFTER the last listed job in the log
---- and remove THAT job from the sched (job entry, actions)
Keep re-run Calc Glob Sched Order, watch SysMonitor for crash, etc… until no more errors.
Maybe someone else on this site will know of a faster way to remove all the jobs from the schedule in one go, possibly there is a conversion, etc… ?
I would put a support ticket in. We are on the cloud and it seems like I had this issue for MRP going from 10.2.500 to 10.2.600, it has been a few months ago now.
I think it had to do with refreshing the system agent credentials.
Thank your for the replies. Our issue was Task Manager settings.
Can you say more about what caused your issue and what you did to fix it? I am having the global scheduling cancel out immediately. Not the calculate global scheduling order, but the actual global scheduling process cancels out.
Global Scheduling - Cancelled? - Kinetic 202X - Epicor User Help Forum (epiusers.help)