4GL STOP condition: The Server application has returned an error. (7243) (7241)

Epicor ERP 9
1

Urgent Please help. I am getting this error when editing job numbers whether I am in job entry or time & expense entry.

Error Detail

4GL STOP condition: The Server application has returned an error. (7243) (7241)

Stack Trace

at Progress.Open4GL.DynamicAPI.Session.runProcedure(String requestID, String procedureName, ParameterSet parms, Boolean persistent, Boolean internal_Renamed, Int64 procId, MetaSchema localSchema, Int32 stateModel)
at Progress.Open4GL.DynamicAPI.Session.runStatelessProcedure(String requestID, String fullProcedureName, ParameterSet inparams, Object procId, MetaSchema localSchema, Int32 stateModel)
at Progress.Open4GL.DynamicAPI.PersistentProc.runTheProcedure(String requestID, String procedureName, ParameterSet parms, MetaSchema schema)
at Progress.Open4GL.DynamicAPI.PersistentProc.runProcedure(String procedureName, ParameterSet parms, MetaSchema schema)
at Epicor.Mfg.Core.CallContext.CallContextPersistentProc.runProcedure(String procedureName, ParameterSet parameters, MetaSchema metaSchema)
at Epicor.Mfg.Core.CallContext.ProxyHelper.CallMethod(String methodName, ParameterSet parameters, MetaSchema metaSchema, BLConnectionPool connPool, Session connection, PersistentProc persistProc, CallContextDataSet callContextDataSet)
at Epicor.Mfg.Proxy.JobEntryImpl.Update(JobEntryDataSet ds)
at Epicor.Mfg.UI.Adapters.JobEntryAdapter.Update()
at Epicor.Mfg.UI.App.JobEntry.Transaction.Update()

2

Got Any BPMs (Data Directive or Method Directive) on JobHead?
Did you do anything special lately like recover from a backup?

3

I do not have any BPMS other than the default stuff that was setup from the start.

I have not done anything special lately like recover from backups. Except for we had someone edit our templates that we create the jobs with and setup and inactive the resource groups and resources? would that cause this issue?

4

I usually have seen that Error when I had a BPM and I removed it but somehow the files stuck around.

You can try running Directive Update via System Management / Business Process Management there should be a button / tab that has “Directive Recompile” and you can check both outdated / up-to-date. It will rebuild BPMs and clear left-overs.

The other time I have seen it is when I added a new Extended UD Column and I did not do Schema Update.

5

As to the Resource/s, it could be. I’ve seen something similar when someone didn’t have Calendar Configured properly.

6

Just in case… cleared client cache.?

Existing jobs or this happens when creating new jobs too?

7

just from what we are seeing it’s two existing jobs that we are seeing this on. Clients crash when accessing two jobs. but when not accessing them. epicor works perfect. the only thing i notice when in job entry before it crashes is the resource group is filled out but the resource itself is not? and when i dig a little further the resource the resource group is defaulting too has zero hours.

8

Not sure of the exact state of the job but I have seen removing them from the schedule and scheduling again resolve hanging job issues.

9

Thanks Hasokeric and the rest that replied. Shutting down the Epicor server and bringing it back up and going in fast allowed me to edit the job in job entry and add a resource under resource group under the operation. Now I am able to work with the job. I can’t believe the calendar and scheduling can cause a crazy issue like this.