Server Terminated Unexpectedly

Can someone help me on what is causing this or pinpoint it? I have never had this problem within the last two years and the last two weeks I have had this problem in Sales Order Tracker(retrieving shipping/invoicing) and Customer Tracker (retrieving orders) but if I wait a second and try again to retrieve invoices/shipping in SOT it loads just fine.

Exception caught in: Epicor.Mfg.BO.CustShip

Error Detail

Message: Server terminated unexpectedly
Type: Error

Stack Trace

at Epicor.Mfg.Proxy.CustShipImpl.GetCustShipOrdTrk(Int32 orderNum)
at Epicor.Mfg.UI.Adapters.CustShipAdapter.GetCustShipOrdTrk(Int32 orderNum)

Inner Exception

ERROR condition: Server terminated unexpectedly (7211)

Inner 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.CustShipImpl.GetCustShipOrdTrk(Int32 orderNum)

We sometimes get Open4GL errors - i’m not entirely sure what causes it but essentially reading forum after forum, restarting the app servers within the open edge management console generally solves the problem.

We used to have this kind of mystery a few years ago. ours was a problem with one appservers instance would lose the connection to the sql server and just be lost.
The rest were fine, so if your transaction happened to get assigned to the disconnected appservers if would throw an error and if not then would work fine.

We were using physical servers then and support wanted a cross over cable to directly connect the two servers to eliminate any networking issues.

In our case we noticed the Last Change column would not be current anymore and would click on the link and kill that appserver.

You may also find the 72xx error in the server log and kill that appserver. The P-010500 is the appserver 10500 above.


How often do your appservers get restarted? I do ours every weekend, so we start off Monday clean. Epicor wanted me to do it by script nightly, but we have three shifts so it was not feasible.


Just to note, I restart our app servers 3 times a week.

I contacted our IT department and they rebooted the servers last night and haven’t had any problems today.

Thank you!