Excessive 4GL Errors

Some versions of Progress have trouble with trimming or re-using app server processes. You can try going into Progress Explorer, bring up the properties of the main app server (not the process server or task agent), find the Pool Range properties, and set the Minimum, Maximum, and Initial number of servers to the same number. It should be a number great enough to handle your server needs during heavy load. You can monitor the Status window to see how many are in use at different times of the day. Take the maximum you see in use and add some extra to that for padding. That way no server processes are ever disconnected because they are not in use.

--- In vantage@yahoogroups.com, "asrayon" <asrayon@...> wrote:
>
> We are experiencing similar errors. It typically happens after running the calculate and global scheduling. Can anyone help?
>
> --- In vantage@yahoogroups.com, Gene Mcdonald <gmcdonald333@> wrote:
> >
> > My users are receiving 4GL errors when running their inventory receipt process
> > (it is occuring in other processes also, but the majority occur during
> > Receipts). Once this begins, the performance of the entire system comes to a
> > crawl, then a halt. has anyone experienced this? Does anyone have any ideas on
> > this? Epicor Tech Support is having problems identifying the culprit here.
> > Â
> > In trouble here.
> > Â
> > Gene McDonald
> > M Holland Co.
> > Â 01/12/2011 09:05:02
> > Error Detail
> > 4G1, STOP condition: The Server application has returned an error. ( 7243 ) (
> > 7241 )
> > Stack Trace
> > at Progress.Open4GL.DynamicAPI.SessionsunProcedure( String requestID, String
> > procedureName,
> > ParameterSet parms, Boolean persistent, Boolean internal Renamed, Int64 procld,
> > MetaSchema localSchema, Int32 stateModel )
> > at Progress.Open4GEDynamicAPI.Session.runStatelessProcedure( String requestID,
> > String
> > fullProcedureName, ParameterSet inparams, Object procld, MetaSchema localSchema,
> > Int32
> > stateModel )
> > at Progress.Open4GL.DynamicAPI.PersistentProc.runTheProcedure( String request1D,
> > 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 inethodName,
> > ParameterSet
> > parameters, MetaSchema metaSchema, BLConnectionPool connPool, Session
> > connection,
> > PersistentProe persistProc, CallContextDataSet callContextDataSet )
> > at Epicor.Mfg.Proxy.InvTransferhnpl.CommitTransfer( InvTransferDataSet ds,
> > String&
> > legalNumberMessage, String& partTranPKs )
> > at Epicor.Mfg.UI.AdaptersinvTransferAdapter.CommitTransfer( InvTransferDataSet
> > ds, String&
> > legalNumberMessage, String& partTranPKs )
> >
> >
> >
> >
> > [Non-text portions of this message have been removed]
> >
>
My users are receiving 4GL errors when running their inventory receipt process
(it is occuring in other processes also, but the majority occur during
Receipts). Once this begins, the performance of the entire system comes to a
crawl, then a halt. has anyone experienced this? Does anyone have any ideas on
this? Epicor Tech Support is having problems identifying the culprit here.
Â
In trouble here.
Â
Gene McDonald
M Holland Co.
 01/12/2011 09:05:02
Error Detail
4G1, STOP condition: The Server application has returned an error. ( 7243 ) (
7241 )
Stack Trace
at Progress.Open4GL.DynamicAPI.SessionsunProcedure( String requestID, String
procedureName,
ParameterSet parms, Boolean persistent, Boolean internal Renamed, Int64 procld,
MetaSchema localSchema, Int32 stateModel )
at Progress.Open4GEDynamicAPI.Session.runStatelessProcedure( String requestID,
String
fullProcedureName, ParameterSet inparams, Object procld, MetaSchema localSchema,
Int32
stateModel )
at Progress.Open4GL.DynamicAPI.PersistentProc.runTheProcedure( String request1D,
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 inethodName,
ParameterSet
parameters, MetaSchema metaSchema, BLConnectionPool connPool, Session
connection,
PersistentProe persistProc, CallContextDataSet callContextDataSet )
at Epicor.Mfg.Proxy.InvTransferhnpl.CommitTransfer( InvTransferDataSet ds,
String&
legalNumberMessage, String& partTranPKs )
at Epicor.Mfg.UI.AdaptersinvTransferAdapter.CommitTransfer( InvTransferDataSet
ds, String&
legalNumberMessage, String& partTranPKs )




[Non-text portions of this message have been removed]
We are experiencing similar errors. It typically happens after running the calculate and global scheduling. Can anyone help?

--- In vantage@yahoogroups.com, Gene Mcdonald <gmcdonald333@...> wrote:
>
> My users are receiving 4GL errors when running their inventory receipt process
> (it is occuring in other processes also, but the majority occur during
> Receipts). Once this begins, the performance of the entire system comes to a
> crawl, then a halt. has anyone experienced this? Does anyone have any ideas on
> this? Epicor Tech Support is having problems identifying the culprit here.
> Â
> In trouble here.
> Â
> Gene McDonald
> M Holland Co.
> Â 01/12/2011 09:05:02
> Error Detail
> 4G1, STOP condition: The Server application has returned an error. ( 7243 ) (
> 7241 )
> Stack Trace
> at Progress.Open4GL.DynamicAPI.SessionsunProcedure( String requestID, String
> procedureName,
> ParameterSet parms, Boolean persistent, Boolean internal Renamed, Int64 procld,
> MetaSchema localSchema, Int32 stateModel )
> at Progress.Open4GEDynamicAPI.Session.runStatelessProcedure( String requestID,
> String
> fullProcedureName, ParameterSet inparams, Object procld, MetaSchema localSchema,
> Int32
> stateModel )
> at Progress.Open4GL.DynamicAPI.PersistentProc.runTheProcedure( String request1D,
> 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 inethodName,
> ParameterSet
> parameters, MetaSchema metaSchema, BLConnectionPool connPool, Session
> connection,
> PersistentProe persistProc, CallContextDataSet callContextDataSet )
> at Epicor.Mfg.Proxy.InvTransferhnpl.CommitTransfer( InvTransferDataSet ds,
> String&
> legalNumberMessage, String& partTranPKs )
> at Epicor.Mfg.UI.AdaptersinvTransferAdapter.CommitTransfer( InvTransferDataSet
> ds, String&
> legalNumberMessage, String& partTranPKs )
>
>
>
>
> [Non-text portions of this message have been removed]
>