Error Ending Activity or adjusting Time

bordway · January 23, 2017, 5:01pm

Wonder if anyone has seen errors like these?
Only on one job/asm/operation so far but I’ve not been able to spot anything different with the job/labor records.

1.) Error when MES user tries to end activity.
Exception caught in: Epicor.ServiceModel

Error Detail

Message: Specified argument was out of the range of valid values.
Parameter name: Specified argument was out of the range of valid values.
Parameter name: Position is greater than number of delimited values
Program: Epicor.ServiceModel.dll
Method: ShouldRethrowNonRetryableException

Client Stack Trace

at Epicor.ServiceModel.Channels.ImplBase`1.ShouldRethrowNonRetryableException(Exception ex, DataSet[] dataSets)
at Erp.Proxy.BO.LaborImpl.Update(LaborDataSet ds)
at Erp.Adapters.LaborAdapter.OnUpdate()
at Ice.Lib.Framework.EpiBaseAdapter.Update()
at Erp.UI.App.EndActivityEntry.EndActTransaction.Update()

2.) Error adjust the same labor record in Time entry (after using conversion to force labor record end)
Application Error

Exception caught in: Epicor.ServiceModel

Error Detail

Message: Specified argument was out of the range of valid values.
Parameter name: Specified argument was out of the range of valid values.
Parameter name: Position is greater than number of delimited values
Program: Epicor.ServiceModel.dll
Method: ShouldRethrowNonRetryableException

Client Stack Trace

at Epicor.ServiceModel.Channels.ImplBase`1.ShouldRethrowNonRetryableException(Exception ex, DataSet[] dataSets)
at Erp.Proxy.BO.LaborImpl.Update(LaborDataSet ds)
at Erp.Adapters.LaborAdapter.OnUpdate()
at Ice.Lib.Framework.EpiBaseAdapter.Update()
at Erp.UI.App.TimeAndExpenseEntry.Transaction.Update()

And finally… related section of the log file
#Exception

msg=Specified argument was out of the range of valid values.Parameter name:

Position is greater than number of delimited values (ArgumentOutOfRangeException)

at Epicor.Utilities.StringExtensions.Entry(String sourceString, Int32 index, Char delimiter)

in c:_Releases\ICE\3.1.400.22\Source\Shared\Framework\Epicor.ServiceModel\Utilities\StringExtensions.cs:
line 134

at Erp.Internal.Lib.AdjShopL.RemoveLoad(Decimal HoursToRemove, Boolean IP_WhatIf, JobOper JobOper)

in c:_Releases\ERP\UD10.1.400.22\Source\Server\Internal\Lib\JobOperShared\AdjShopL\adjshopl.cs:line 1549

at Erp.Internal.Lib.AdjShopL.Update_ResourceTimeUsed(JobOper JobOper, JobOper OldJobOper)

in c:_Releases\ERP\UD10.1.400.22\Source\Server\Internal\Lib\JobOperShared\AdjShopL\adjshopl.cs:line 320

at Erp.Internal.Lib.JobOperWrite._JobOperWrite(JobOper JobOper, JobOper OldJobOper, Boolean RollUp)

in c:_Releases\ERP\UD10.1.400.22\Source\Server\Internal\Lib\JobOperShared\JobOperWrite\JobOperWrite.i.cs:line 1386

at Erp.Internal.Lib.JobOperShWrite.DoJobOper(JobOper JobOper, JobOper OLDJobOper)

in c:_Releases\ERP\UD10.1.400.22\Source\Server\Internal\Lib\JobOperShared\JobOperShWrite\JobOperShWrite.cs:line 1232

at Erp.Triggers.JobOper.WriteTrigger.write(JobOper JobOper, JobOper OldJobOper)

in c:_Releases\ERP\UD10.1.400.22\Source\Server\Db\Triggers\JobOper\write.cs:line 232

at Ice.Triggers.TriggerQueue.ExecuteWriteTrigger(IceDataContext context, LinqRow modifiedRecord, LinqRow originalRecord)

in c:_Releases\ICE\3.1.400.22\Source\Framework\Epicor.System\Triggers\TriggerQueue.cs:line 296

at Ice.Triggers.TriggerQueue.RunWriteTriggerInNewLevel(IceDataContext context, LinqRow modifiedRecord, LinqRow originalRecord, Boolean forAddedRow)

in c:_Releases\ICE\3.1.400.22\Source\Framework\Epicor.System\Triggers\TriggerQueue.cs:line 157

at Ice.Triggers.TriggerQueue.<>c__DisplayClass6.b__4()

in c:_Releases\ICE\3.1.400.22\Source\Framework\Epicor.System\Triggers\TriggerQueue.cs:line 148

at Ice.Triggers.TriggerQueue.RunAtNewLevel(Func`1 buildTriggerRunState, Action action)

in c:_Releases\ICE\3.1.400.22\Source\Framework\Epicor.System\Triggers\TriggerQueue.cs:line 501

at Ice.Triggers.TriggerQueue.RunTriggers(IceDataContext context)

in c:_Releases\ICE\3.1.400.22\Source\Framework\Epicor.System\Triggers\TriggerQueue.cs:line 83

at Ice.IceDataContext.RunUntilAllTriggersHaveExecuted()

in c:_Releases\ICE\3.1.400.22\Source\Framework\Epicor.System\Data\IceDataContext.cs:line 542

at Ice.Triggers.TriggerQueue.RunAtNewLevel(Func`1 buildTriggerRunState, Action action)

in c:_Releases\ICE\3.1.400.22\Source\Framework\Epicor.System\Triggers\TriggerQueue.cs:line 501

at Ice.IceDataContext.Validate[TLinqRow](TLinqRow row)

in c:_Releases\ICE\3.1.400.22\Source\Framework\Epicor.System\Data\IceDataContext.cs:line 299

at Ice.IceDataContext.Release[TEntity](TEntity& entity)

in c:_Releases\ICE\3.1.400.22\Source\Framework\Epicor.System\Data\IceDataContext.cs:line 249

at Erp.Triggers.Labor

bw2868bond · January 23, 2017, 5:14pm

Which version / patch are you running?

Problem is listed as fixed – don’t recall the exact version where the fix happened

DavisStd1 · January 23, 2017, 5:54pm

Try to remove the job the employee is clocked on from the schedule. Once it has been removed, you should be able to end activity.

Beth · January 23, 2017, 8:38pm

Yes, I have seen this error. What I had to do was remove the job from the schedule, then reschedule it. The employee can then end activity. I have an open call with support on this issue.

bordway · January 24, 2017, 4:19pm

Thanks, now that you mention it… I remember having to play with the schedule in V8/E9 sometimes too. With those I believed it was certain entry sequences resulting in “what-if” records being out of whack?

Current issue is with version E10 10.1.400.22
Once the labor was ended we still couldn’t adjust time.
In order to process payroll we just adjusted labor for the day on the labor header.
And finally just used a job adjust to add the labor time.

bordway · January 24, 2017, 5:01pm

…WhatIf…?
And maybe it’s just a coincidence but I just got some new feedback from another user…

“Quote entry - using the What If Schedule feature - get the blue circle and nothing happens - quit the process ends the Epicor session and need to restart and log back in again”

Chris_Conn · January 24, 2017, 10:02pm

We’ve seen this issue - When we use schedule forward, the issue occurred. When we used schedule backwards, the problem went away.

Beth · January 25, 2017, 2:03pm

Chris,

That is good to know. I was also using schedule forward when this occurred. I’ll mention it to support when I talk with them today. Thanks!

Beth

Beth · January 25, 2017, 2:00pm

Bruce,

I have been waiting on Epicor support to get back with me. I am supposed to have a WebEx with support this morning on this issue. Wish me luck!

Beth

Chris_Conn · January 25, 2017, 2:14pm

Beth,

Would you mind sharing the fruits of your labor if the call is helpful?

ERPSysAdmin · January 25, 2017, 2:14pm

Good luck Beth! Yes, if you could please share your results! Thanks!

Beth · January 25, 2017, 3:03pm

I would be happy to share anything new that I learn! So far the only solution is to remove the job from the schedule and reschedule it which is not the best solution for anyone.

Beth · January 26, 2017, 4:44pm

I was able to finally connect with support on this issue, unfortunately since it is a “random” issue and cannot be reproduced on demand, they have closed the case and asked me to call again when I have the issue. I wish Epicor had a better way of tracking the “random” things. I know it is hard to figure out the random issues, but I have all the data and could give them a copy of the database. But because I couldn’t reproduce it at the moment in time when I was speaking with the support person, nothing is captured.

bordway · January 28, 2017, 3:51pm

I couldn’t reproduce at the moment
with the support person
nothing is captured.
Thanks for the feedback
random
I know the feeling
If nothing else I’ll remember that playing with the schedule can clear some labor entry issues.
Reminded me that I’ve seen similar random behavior in Sales Orders and Quotes. I’ve come to believe that certain entry sequences throw those records off. The only way I’ve found to clear records is changing values back and forth or deleting/adding back in.

Beth · January 30, 2017, 3:56pm

Does your company forward schedule or backward schedule? When I saw the errors, I was using forward scheduling.

bordway · January 31, 2017, 7:24pm

forward/backward
For the most part they schedule all jobs manually from job entry and default to backward.

Now that you mention it, I do remember playing with directions on some jobs before.
I can’t remember why now, only that it wasn’t related to the “clocking out” issue.

Eric_Howell · December 8, 2020, 5:31pm

thank you for this thread. I just came across this error. I unengineered the job. removed it from schedule. re-engineered and scheduled and released and it was resolved.
version 10.2.300.13

cchang · May 14, 2021, 8:23pm

We are running into this issue and tried it but did not resolve it. How did you remove it from the schedule. We rescheduled it with a different due date if this is sufficient.

bordway · May 14, 2021, 8:35pm

Job Entry →

Un-Engineer the job
then Actions → Schedule → “Remove from Schedule”
then Re-Engineer and Schedule.
Usually clears the issue

In some cases I have needed to use the conversion to force the active labor to end.

cchang · May 14, 2021, 8:38pm

I removed it from schedule and still did not clear the issue. What “conversion” did you use to force it to end active labor?