Vantage 8.0 I am getting application error message

Dan,

Our experience is that the 4GL Stop errors can be almost anything. I
would definately check the main App Server log. Although often there
is not any detail. Also, the next time it happens, you might want to
ask around and see if anyone thinks they did anything that may have
caused the problem (may be difficult in a large installation).

Hope this helps.

--- In vantage@yahoogroups.com, "Dan Ernst" <dernst@...> wrote:
>
> I have mailed my database to Epicor and they are unable to recreate
> the error. They can create jobs using my database. I was wondering
> if it could possibly have something to do with OpenEdge 10.0B,
maybe
> there are settings that are pointing to Progress 9.1D or something
> on that line.
>
> Thanks
> Dan Ernst
> Computer Services
> Correct Craft, Inc.
> (407) 855-4141
> http://www.correctcraft.com
>
>
>
> --- In vantage@yahoogroups.com, "Chris Robisch" <blue.wine@>
> wrote:
> >
> > Check for duplicate JobAsmbl.BOMSequence numbers... they must be
> unique within a job. Electroimpact has 7 large jobs corrupted
during
> the v8 conversion with bad sequence numbers and bad child/next
> pointers. I suspect the duplicate sequence numbers cause the bad
> pointers which might cause your problem if the last assembly of a
> job has bad enough pointers to affect the next job.
> >
> > Or it may not have anything to do with it but the duplicate
> numbers are easy to check.
> >
> > ----- Original Message -----
> > From: "Dan Ernst" <dernst@>
> > To: <vantage@yahoogroups.com>
> > Sent: Wednesday, February 01, 2006 10:16 AM
> > Subject: [Vantage] Vantage 8.0 I am getting application error
> message
> >
> >
> > I have converted our database from Vantage 6.1 to Vantage 8.0 and
> > when I try and create a job in Vantage 8.0 I am getting an error
> > message. The job I am trying to create is on a configured part
and
> > below is the message I receive:
> > 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)
> > at Progress.Open4GL.DynamicAPI.Session.runProcedure(String
> > requestID, String procedureName, ParameterSet parms, Object
> procId,
> > MetaSchema localSchema)
> > at Progress.Open4GL.DynamicAPI.PersistentProc.runProcedure
> (String
> > procedureName, ParameterSet parms, MetaSchema schema)
> > at Epicor.Mfg.Proxy.OrderJobWizImpl.CreateJobs
> (OrderJobWizDataSet
> > ds, String& pErrorMessages)
> > at
> Epicor.Mfg.BO.OrderJobWiz.Epicor.Mfg.IF.IOrderJobWiz.CreateJobs
> > (OrderJobWizDataSet , String& )
> > at Epicor.Mfg.UI.Adapters.OrderJobWizAdapter.CreateJobs
(String&
> > pErrorMessages)
> >
> >
> > Epicor Support has not been able to figure out what is causing
it.
> Anyone out there have any ideas?
> > Thanks
> >
> >
> > [Non-text portions of this message have been removed]
> >
>
I have converted our database from Vantage 6.1 to Vantage 8.0 and
when I try and create a job in Vantage 8.0 I am getting an error
message. The job I am trying to create is on a configured part and
below is the message I receive:
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)
at Progress.Open4GL.DynamicAPI.Session.runProcedure(String
requestID, String procedureName, ParameterSet parms, Object procId,
MetaSchema localSchema)
at Progress.Open4GL.DynamicAPI.PersistentProc.runProcedure(String
procedureName, ParameterSet parms, MetaSchema schema)
at Epicor.Mfg.Proxy.OrderJobWizImpl.CreateJobs(OrderJobWizDataSet
ds, String& pErrorMessages)
at Epicor.Mfg.BO.OrderJobWiz.Epicor.Mfg.IF.IOrderJobWiz.CreateJobs
(OrderJobWizDataSet , String& )
at Epicor.Mfg.UI.Adapters.OrderJobWizAdapter.CreateJobs(String&
pErrorMessages)


Epicor Support has not been able to figure out what is causing it.
Anyone out there have any ideas?
Thanks
Check for duplicate JobAsmbl.BOMSequence numbers... they must be unique within a job. Electroimpact has 7 large jobs corrupted during the v8 conversion with bad sequence numbers and bad child/next pointers. I suspect the duplicate sequence numbers cause the bad pointers which might cause your problem if the last assembly of a job has bad enough pointers to affect the next job.

Or it may not have anything to do with it but the duplicate numbers are easy to check.

----- Original Message -----
From: "Dan Ernst" <dernst@...>
To: <vantage@yahoogroups.com>
Sent: Wednesday, February 01, 2006 10:16 AM
Subject: [Vantage] Vantage 8.0 I am getting application error message


I have converted our database from Vantage 6.1 to Vantage 8.0 and
when I try and create a job in Vantage 8.0 I am getting an error
message. The job I am trying to create is on a configured part and
below is the message I receive:
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)
at Progress.Open4GL.DynamicAPI.Session.runProcedure(String
requestID, String procedureName, ParameterSet parms, Object procId,
MetaSchema localSchema)
at Progress.Open4GL.DynamicAPI.PersistentProc.runProcedure(String
procedureName, ParameterSet parms, MetaSchema schema)
at Epicor.Mfg.Proxy.OrderJobWizImpl.CreateJobs(OrderJobWizDataSet
ds, String& pErrorMessages)
at Epicor.Mfg.BO.OrderJobWiz.Epicor.Mfg.IF.IOrderJobWiz.CreateJobs
(OrderJobWizDataSet , String& )
at Epicor.Mfg.UI.Adapters.OrderJobWizAdapter.CreateJobs(String&
pErrorMessages)


Epicor Support has not been able to figure out what is causing it. Anyone out there have any ideas?
Thanks


[Non-text portions of this message have been removed]
I have mailed my database to Epicor and they are unable to recreate
the error. They can create jobs using my database. I was wondering
if it could possibly have something to do with OpenEdge 10.0B, maybe
there are settings that are pointing to Progress 9.1D or something
on that line.

Thanks
Dan Ernst
Computer Services
Correct Craft, Inc.
(407) 855-4141
http://www.correctcraft.com



--- In vantage@yahoogroups.com, "Chris Robisch" <blue.wine@...>
wrote:
>
> Check for duplicate JobAsmbl.BOMSequence numbers... they must be
unique within a job. Electroimpact has 7 large jobs corrupted during
the v8 conversion with bad sequence numbers and bad child/next
pointers. I suspect the duplicate sequence numbers cause the bad
pointers which might cause your problem if the last assembly of a
job has bad enough pointers to affect the next job.
>
> Or it may not have anything to do with it but the duplicate
numbers are easy to check.
>
> ----- Original Message -----
> From: "Dan Ernst" <dernst@...>
> To: <vantage@yahoogroups.com>
> Sent: Wednesday, February 01, 2006 10:16 AM
> Subject: [Vantage] Vantage 8.0 I am getting application error
message
>
>
> I have converted our database from Vantage 6.1 to Vantage 8.0 and
> when I try and create a job in Vantage 8.0 I am getting an error
> message. The job I am trying to create is on a configured part and
> below is the message I receive:
> 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)
> at Progress.Open4GL.DynamicAPI.Session.runProcedure(String
> requestID, String procedureName, ParameterSet parms, Object
procId,
> MetaSchema localSchema)
> at Progress.Open4GL.DynamicAPI.PersistentProc.runProcedure
(String
> procedureName, ParameterSet parms, MetaSchema schema)
> at Epicor.Mfg.Proxy.OrderJobWizImpl.CreateJobs
(OrderJobWizDataSet
> ds, String& pErrorMessages)
> at
Epicor.Mfg.BO.OrderJobWiz.Epicor.Mfg.IF.IOrderJobWiz.CreateJobs
> (OrderJobWizDataSet , String& )
> at Epicor.Mfg.UI.Adapters.OrderJobWizAdapter.CreateJobs(String&
> pErrorMessages)
>
>
> Epicor Support has not been able to figure out what is causing it.
Anyone out there have any ideas?
> Thanks
>
>
> [Non-text portions of this message have been removed]
>