SM>CRM>Setup>Sales Territory maint>Post - generates 4GL STOP con

I also receive this error in test.

 

I’ll be retesting again today in verbose and check the logs.

 

What I’d like to do is have a method that shows me more information/step through/see details as to which table/record it was last processing to diagnose.

 

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Tanya Denison
Sent: Wednesday, February 05, 2014 7:17 PM
To: vantage@yahoogroups.com
Subject: Re: [Vantage] SM>CRM>Setup>Sales Territory maint>Post - generates 4GL STOP condition (7243) (7241)

 

 

My understanding is that record locking and deadlocks can generate these issues.  Are you running this maintenance during normal business hours?  If so, then I can see that customer records in use or sales orders being created and invoiced could be causing record locks and preventing your program from completing.

 

Can you run this with no errors in a test environment?


 

Tanya Denison | IT Manager 

NRS - 100% Employee Owned

 

2009 S. Main Street, Moscow, ID  83843

p: 208.883.7834 Ext 277 | c: 208.301.0599 | f: 208.882.1744

 

On Wed, Feb 5, 2014 at 10:58 AM, <jim_chance@...> wrote:

 

Does anyone know how to message/display/trace the details behind a 4GL STOP condition?

 

Its occurring during the post from: SM>CRM>Setup>Sales Territory maint>Post 

 

No BPM is tied to this app. 

No customization.

No personalization.

The trace shows nothing. 

 

The gut feeling is this is a data issue. But until i can have it show me what it was doing just prior to this message - table/record; its difficult to know where its gotten confused. 

 

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.Core.CallContext.ProxyHelper.CallMethod(String methodName, ParameterSet parameters, BLConnectionPool connPool, Session connection, PersistentProc persistProc, CallContextDataSet callContextDataSet)

   at Epicor.Mfg.Proxy.SalesTerImpl.PostTerritories()

   at Epicor.Mfg.UI.Adapters.SalesTerAdapter.PostTerritories()

   at Epicor.Mfg.UI.App.SalesTerEntry.SalesTerTransaction.PostTerritories()

 

Does anyone know how to message/display/trace the details behind a 4GL STOP condition?

Its occurring during the post from: SM>CRM>Setup>Sales Territory maint>Post 

No BPM is tied to this app. 
No customization.
No personalization.
The trace shows nothing. 

The gut feeling is this is a data issue. But until i can have it show me what it was doing just prior to this message - table/record; its difficult to know where its gotten confused. 

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.Core.CallContext.ProxyHelper.CallMethod(String methodName, ParameterSet parameters, BLConnectionPool connPool, Session connection, PersistentProc persistProc, CallContextDataSet callContextDataSet)
   at Epicor.Mfg.Proxy.SalesTerImpl.PostTerritories()
   at Epicor.Mfg.UI.Adapters.SalesTerAdapter.PostTerritories()
   at Epicor.Mfg.UI.App.SalesTerEntry.SalesTerTransaction.PostTerritories()

Aren’t 72XX errors related to connectivity?  Have you looked at the server logs?

 

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of jim_chance@...
Sent: Wednesday, February 05, 2014 1:59 PM
To: vantage@yahoogroups.com
Subject: [Vantage] SM>CRM>Setup>Sales Territory maint>Post - generates 4GL STOP condition (7243) (7241)

 

 

Does anyone know how to message/display/trace the details behind a 4GL STOP condition?

 

Its occurring during the post from: SM>CRM>Setup>Sales Territory maint>Post 

 

No BPM is tied to this app. 

No customization.

No personalization.

The trace shows nothing. 

 

The gut feeling is this is a data issue. But until i can have it show me what it was doing just prior to this message - table/record; its difficult to know where its gotten confused. 

 

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.Core.CallContext.ProxyHelper.CallMethod(String methodName, ParameterSet parameters, BLConnectionPool connPool, Session connection, PersistentProc persistProc, CallContextDataSet callContextDataSet)

   at Epicor.Mfg.Proxy.SalesTerImpl.PostTerritories()

   at Epicor.Mfg.UI.Adapters.SalesTerAdapter.PostTerritories()

   at Epicor.Mfg.UI.App.SalesTerEntry.SalesTerTransaction.PostTerritories()

I don’t see where 72XX is connectivity.





From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Joe Englert
Sent: Wednesday, February 05, 2014 2:18 PM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] SM>CRM>Setup>Sales Territory maint>Post - generates 4GL STOP condition (7243) (7241)





Aren’t 72XX errors related to connectivity? Have you looked at the server logs?



From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of jim_chance@...
Sent: Wednesday, February 05, 2014 1:59 PM
To: vantage@yahoogroups.com
Subject: [Vantage] SM>CRM>Setup>Sales Territory maint>Post - generates 4GL STOP condition (7243) (7241)





Does anyone know how to message/display/trace the details behind a 4GL STOP condition?



Its occurring during the post from: SM>CRM>Setup>Sales Territory maint>Post



No BPM is tied to this app.

No customization.

No personalization.

The trace shows nothing.



The gut feeling is this is a data issue. But until i can have it show me what it was doing just prior to this message - table/record; its difficult to know where its gotten confused.



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.Core.CallContext.ProxyHelper.CallMethod(String methodName, ParameterSet parameters, BLConnectionPool connPool, Session connection, PersistentProc persistProc, CallContextDataSet callContextDataSet)

at Epicor.Mfg.Proxy.SalesTerImpl.PostTerritories()

at Epicor.Mfg.UI.Adapters.SalesTerAdapter.PostTerritories()

at Epicor.Mfg.UI.App.SalesTerEntry.SalesTerTransaction.PostTerritories()





[Non-text portions of this message have been removed]

You’re right, I think I’m wrong.

 

Have you looked at the server logs?

 

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Jim Chance
Sent: Wednesday, February 05, 2014 3:29 PM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] SM>CRM>Setup>Sales Territory maint>Post - generates 4GL STOP condition (7243) (7241)

 

 

I don’t see where 72XX is connectivity.

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Joe Englert
Sent: Wednesday, February 05, 2014 2:18 PM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] SM>CRM>Setup>Sales Territory maint>Post - generates 4GL STOP condition (7243) (7241)

Aren’t 72XX errors related to connectivity? Have you looked at the server logs?

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of jim_chance@...
Sent: Wednesday, February 05, 2014 1:59 PM
To: vantage@yahoogroups.com
Subject: [Vantage] SM>CRM>Setup>Sales Territory maint>Post - generates 4GL STOP condition (7243) (7241)

Does anyone know how to message/display/trace the details behind a 4GL STOP condition?

Its occurring during the post from: SM>CRM>Setup>Sales Territory maint>Post

No BPM is tied to this app.

No customization.

No personalization.

The trace shows nothing.

The gut feeling is this is a data issue. But until i can have it show me what it was doing just prior to this message - table/record; its difficult to know where its gotten confused.

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.Core.CallContext.ProxyHelper.CallMethod(String methodName, ParameterSet parameters, BLConnectionPool connPool, Session connection, PersistentProc persistProc, CallContextDataSet callContextDataSet)

at Epicor.Mfg.Proxy.SalesTerImpl.PostTerritories()

at Epicor.Mfg.UI.Adapters.SalesTerAdapter.PostTerritories()

at Epicor.Mfg.UI.App.SalesTerEntry.SalesTerTransaction.PostTerritories()

[Non-text portions of this message have been removed]

My understanding is that record locking and deadlocks can generate these issues.  Are you running this maintenance during normal business hours?  If so, then I can see that customer records in use or sales orders being created and invoiced could be causing record locks and preventing your program from completing.

Can you run this with no errors in a test environment?


Tanya Denison | IT Manager 
NRS - 100% Employee Owned

2009 S. Main Street, Moscow, ID  83843
p: 208.883.7834 Ext 277 | c: 208.301.0599 | f: 208.882.1744


On Wed, Feb 5, 2014 at 10:58 AM, <jim_chance@...> wrote:

 
<div>
  
  
  <p>Does anyone know how to message/display/trace the details behind a 4GL STOP condition?</p><div><br></div><div>Its occurring during the post from:&nbsp;SM&gt;CRM&gt;Setup&gt;Sales Territory maint&gt;Post&nbsp;</div><div><br>
No BPM is tied to this app. 
No customization.
No personalization.
The trace shows nothing. 

The gut feeling is this is a data issue. But until i can have it show me what it was doing just prior to this message - table/record; its difficult to know where its gotten confused. 

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.Core.CallContext.ProxyHelper.CallMethod(String methodName, ParameterSet parameters, BLConnectionPool connPool, Session connection, PersistentProc persistProc, CallContextDataSet callContextDataSet)
   at Epicor.Mfg.Proxy.SalesTerImpl.PostTerritories()
   at Epicor.Mfg.UI.Adapters.SalesTerAdapter.PostTerritories()
   at Epicor.Mfg.UI.App.SalesTerEntry.SalesTerTransaction.PostTerritories()

</div>
 


<div style="color:#fff;min-height:0;"></div>