Back flush labor process task agent error

Epicor ERP 10
1

In Epicor 10.0.700.4, the back flush labor process has been running fine in task agent until yesterday, now getting the following error every time it tries to run.

Program Ice.Services.Lib.RunTask raised an unexpected exception with the following message: RunTask: Input string was not in a correct format.
at System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)
at System.Number.ParseDecimal(String value, NumberStyles options, NumberFormatInfo numfmt)
at Compatibility.Convert.ToDecimal(String strValue)
at Erp.Internal.Lib.AdjShopL.AddHours(Decimal ipHoursToApply, ProdCal& ProdCal, Resource& Resource, ResourceGroup& ResourceGroup, Plant& Plant, Company& Company, ResourceTimeUsed& ResourceTimeUsed, ResourceCal& ResourceCal)
at Erp.Internal.Lib.AdjShopL.ApplyLoad(Decimal HoursToApply, Boolean IP_WhatIf, JobOper JobOper)
at Erp.Internal.Lib.AdjShopL.Update_ResourceTimeUsed(JobOper JobOper, JobOper OldJobOper)
at Erp.Internal.Lib.JobOperWrite._JobOperWrite(JobOper JobOper, JobOper OldJobOper, Boolean RollUp)
at Erp.Internal.Lib.JobOperShWrite.DoJobOper(JobOper JobOper, JobOper OLDJobOper)
at Erp.Triggers.JobOper.WriteTrigger.write(JobOper JobOper, JobOper OldJobOper)
at Ice.Triggers.TriggerQueue.ExecuteWriteTrigger(IceDataContext context, LinqRow modifiedRecord, LinqRow originalRecord)
at Ice.Triggers.TriggerQueue.RunWriteTriggerInNewLevel(IceDataContext context, LinqRow modifiedRecord, LinqRow originalRecord, Boolean forAddedRow)
at Ice.Triggers.TriggerQueue.<>c__DisplayClass6.b__4()
at Ice.Triggers.TriggerQueue.RunAtNewLevel(Func1 buildTriggerRunState, Action action) at Ice.Triggers.TriggerQueue.RunTriggers(IceDataContext context) at Ice.IceDataContext.RunUntilAllTriggersHaveExecuted() at Ice.Triggers.TriggerQueue.RunAtNewLevel(Func1 buildTriggerRunState, Action action)
at Ice.IceDataContext.Validate[TLinqRow](TLinqRow row)
at Ice.IceDataContext.Release[TEntity](TEntity& entity)
at Erp.Triggers.LaborDtl.WriteTrigger.Write(LaborDtl LaborDtl, LaborDtl OLaborDtl)
at Ice.Triggers.TriggerQueue.ExecuteWriteTrigger(IceDataContext context, LinqRow modifiedRecord, LinqRow originalRecord)
at Ice.Triggers.TriggerQueue.RunWriteTriggerInNewLevel(IceDataContext context, LinqRow modifiedRecord, LinqRow originalRecord, Boolean forAddedRow)
at Ice.Triggers.TriggerQueue.<>c__DisplayClass6.b__4()
at Ice.Triggers.TriggerQueue.RunAtNewLevel(Func`1 buildTriggerRunState, Action action)
at Ice.Triggers.TriggerQueue.RunTriggers(IceDataContext context)
at Ice.IceDataContext.RunUntilAllTriggersHaveExecuted()
at Erp.Internal.Lib.BFLaborD.CreateProduction()
at Erp.Internal.Lib.BFLaborD._BFLaborD(Guid LaborDtlRowid, String& oMessage)
at Erp.Internal.JC.BackfluchLaborProcess.RunProcess(Int32 InstanceTaskNum, String OutputFileName)
at Ice.Hosting.TaskCaller.ExecuteTask()
at Ice.Services.Lib.RunTaskSvc.RunTask(Int32 ipTaskNum)

2

I’ve seen similar errors sometimes when operators enter labor. It has to do with the load being relieved in the ShopLoad table. Our workaround right now is to remove the problem job from the schedule and then reschedule it. Since you’re running the backflush labor process, I’m not sure if there’s a log that you can look at to see which job it’s failing on.