Can not add qty when opreator clock out the job

Epicor ERP 10
,
1

One of Operator has completed 40 pcs yesterday ( I enter 1 qty to check, we have to update to add 39 pcs more as completed to the job) , he could not enter his qty. I tired to enter and check we can only qty 1, any thing over one we have the error message as below

untitled
untitled1341×954 44.3 KB

Any ideas?

2

Try removing the job from the Schedule and re-scheduling in Job Entry.

3

I’ve tried it. but same error came up

4

So you went into Job Entry, unreleased/unengineered the job, clicked schedule>unscheduled job, then clicked the checkboxes to engineer it and release it which should prompt you to schedule it?

5

Which epicor version are you using? Can you paste the entire exception text?

6

here is the error detail
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

7

There is a Detail button on the exception box, it should provide a more detailed exception message.

8

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()

9

Doesn’t seem to provide enough detail, seems to be missing the server stack trace.

You can try enabling server side logging through AppServer.config, this will generate file ServerLog.txt on the server deployment folder with more technical details.

You can also check windows event viewer to see if there is a more detailed error.

10

There are two KBs both with the same basic steps. We had this just after go live a few months ago and removing and rescheduling fixed it.

https://epicorcs.service-now.com/epiccare?id=epiccare_kb_article&sys_id=d1069e46dbc8c0509520e7970596198e

https://epicorcs.service-now.com/epiccare?id=epiccare_kb_article&sys_id=ff5602a6dbc19748949df438bf961973

1 Like