Adding New Data into Epicor 9.05.700B2

Yahoo Archive
1
Make sure you are using the new DMT version for 9.05.700. There are two versions out there that seem to be different:
'1.0.4.5 for 9.05.607'
and
'1.0.4.5 for 9.05.700'

I no longer have the detail, but I thought I was getting an error like this after we upgraded to 700B2 and I forgot to upgrade my DMT because the DMT version number matched.
Not sure this is your problem, but something to check.

-Rick Bird
IT Software Administrator
Rowmark, LLC.


--- In vantage@yahoogroups.com, "carlitaxbonita" <ctat121490@...> wrote:
>
> We are having problems adding new Data into our Epicor905 and EpicorTest905 datasets.
> It does not matter if I add a new part or supplier from the Part or Supplier screens in setup or if I try to upload data through the DMT.
> We always get a "4GL STOP condition: The server application has returned an error. (7243)(7241). "
> The detailed error is listed below for adding a new Part:
>
> Error Detail
> ============
> 4GL STOP condition: The Server application has returned an error. (7243) (7241)
>
> Stack Trace
> ===========
> at Progress.Open4GL.DynamicAPI.Session.runProcedure(S tring requestID, String procedureName, ParameterSet parms, Boolean persistent, Boolean internal_Renamed, Int64 procId, MetaSchema localSchema, Int32 stateModel)
> at Progress.Open4GL.DynamicAPI.Session.runStatelessPr ocedure(String requestID, String fullProcedureName, ParameterSet inparams, Object procId, MetaSchema localSchema, Int32 stateModel)
> at Progress.Open4GL.DynamicAPI.PersistentProc.runTheP rocedure(String requestID, String procedureName, ParameterSet parms, MetaSchema schema)
> at Progress.Open4GL.DynamicAPI.PersistentProc.runProc edure(String procedureName, ParameterSet parms, MetaSchema schema)
> at Epicor.Mfg.Core.CallContext.CallContextPersistentP roc.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.PartImpl.Update(PartDataSet ds)
> at Epicor.Mfg.UI.Adapters.PartAdapter.Update()
> at Epicor.Mfg.UI.App.PartEntry.PartTransaction.Adapte rUpdate()
> at Epicor.Mfg.UI.App.PartEntry.PartTransaction.Update X()
>
>
> When I look at the Appserver logs, I see that during the add new transaction, I get the following error:
>
> P-009332 T-012400 1 AS -- (Procedure: 'PartCreateRow bo/Part/Part.p' Line:9818) 24000: [Microsoft][SQL Server Native Client 10.0]Invalid cursor state
>
>
> We have contacted Epicor support. They told us we need to take all the data out of the tables and then try importing the data again. We tried one table and when we try to put the data back into it, we get the same above error. It is taking a very long time to get any response from Epicor so I'm wondering if anyone has seen this before and knows a fix for it.
>
> Thank you.
>
2
We are having problems adding new Data into our Epicor905 and EpicorTest905 datasets.
It does not matter if I add a new part or supplier from the Part or Supplier screens in setup or if I try to upload data through the DMT.
We always get a "4GL STOP condition: The server application has returned an error. (7243)(7241). "
The detailed error is listed below for adding a new Part:

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

Stack Trace
===========
at Progress.Open4GL.DynamicAPI.Session.runProcedure(S tring requestID, String procedureName, ParameterSet parms, Boolean persistent, Boolean internal_Renamed, Int64 procId, MetaSchema localSchema, Int32 stateModel)
at Progress.Open4GL.DynamicAPI.Session.runStatelessPr ocedure(String requestID, String fullProcedureName, ParameterSet inparams, Object procId, MetaSchema localSchema, Int32 stateModel)
at Progress.Open4GL.DynamicAPI.PersistentProc.runTheP rocedure(String requestID, String procedureName, ParameterSet parms, MetaSchema schema)
at Progress.Open4GL.DynamicAPI.PersistentProc.runProc edure(String procedureName, ParameterSet parms, MetaSchema schema)
at Epicor.Mfg.Core.CallContext.CallContextPersistentP roc.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.PartImpl.Update(PartDataSet ds)
at Epicor.Mfg.UI.Adapters.PartAdapter.Update()
at Epicor.Mfg.UI.App.PartEntry.PartTransaction.Adapte rUpdate()
at Epicor.Mfg.UI.App.PartEntry.PartTransaction.Update X()


When I look at the Appserver logs, I see that during the add new transaction, I get the following error:

P-009332 T-012400 1 AS -- (Procedure: 'PartCreateRow bo/Part/Part.p' Line:9818) 24000: [Microsoft][SQL Server Native Client 10.0]Invalid cursor state


We have contacted Epicor support. They told us we need to take all the data out of the tables and then try importing the data again. We tried one table and when we try to put the data back into it, we get the same above error. It is taking a very long time to get any response from Epicor so I'm wondering if anyone has seen this before and knows a fix for it.

Thank you.
3
Interesting information, I am testing the new DMT on an upgraded version of our database that is preloaded only with Static data for our CRP. I'm seeing issues with using the project combined import. The same spreadsheets worked perfectly with 606a version of DMT.

I'll put in some parts tomorrow and see if I can replicate. At least then you will be able to confirm if it is site specific or not.

Cheers
SH

--- In vantage@yahoogroups.com, "carlitaxbonita" <ctat121490@...> wrote:
>
> We are having problems adding new Data into our Epicor905 and EpicorTest905 datasets.
> It does not matter if I add a new part or supplier from the Part or Supplier screens in setup or if I try to upload data through the DMT.
> We always get a "4GL STOP condition: The server application has returned an error. (7243)(7241). "
> The detailed error is listed below for adding a new Part:
>
> Error Detail
> ============
> 4GL STOP condition: The Server application has returned an error. (7243) (7241)
>
> Stack Trace
> ===========
> at Progress.Open4GL.DynamicAPI.Session.runProcedure(S tring requestID, String procedureName, ParameterSet parms, Boolean persistent, Boolean internal_Renamed, Int64 procId, MetaSchema localSchema, Int32 stateModel)
> at Progress.Open4GL.DynamicAPI.Session.runStatelessPr ocedure(String requestID, String fullProcedureName, ParameterSet inparams, Object procId, MetaSchema localSchema, Int32 stateModel)
> at Progress.Open4GL.DynamicAPI.PersistentProc.runTheP rocedure(String requestID, String procedureName, ParameterSet parms, MetaSchema schema)
> at Progress.Open4GL.DynamicAPI.PersistentProc.runProc edure(String procedureName, ParameterSet parms, MetaSchema schema)
> at Epicor.Mfg.Core.CallContext.CallContextPersistentP roc.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.PartImpl.Update(PartDataSet ds)
> at Epicor.Mfg.UI.Adapters.PartAdapter.Update()
> at Epicor.Mfg.UI.App.PartEntry.PartTransaction.Adapte rUpdate()
> at Epicor.Mfg.UI.App.PartEntry.PartTransaction.Update X()
>
>
> When I look at the Appserver logs, I see that during the add new transaction, I get the following error:
>
> P-009332 T-012400 1 AS -- (Procedure: 'PartCreateRow bo/Part/Part.p' Line:9818) 24000: [Microsoft][SQL Server Native Client 10.0]Invalid cursor state
>
>
> We have contacted Epicor support. They told us we need to take all the data out of the tables and then try importing the data again. We tried one table and when we try to put the data back into it, we get the same above error. It is taking a very long time to get any response from Epicor so I'm wondering if anyone has seen this before and knows a fix for it.
>
> Thank you.
>
4
Ok,
I've given that a test using an upgraded database from 606a. I had no error when I imported the part. I have to I only used minimal information such as company, part number, description, UOM and what ever other mandatory values were required.

Have you tried just putting in minimal information and then doing an update one field at a time?

Cheers

--- In vantage@yahoogroups.com, "s1mhall" <s1mhall@...> wrote:
>
> Interesting information, I am testing the new DMT on an upgraded version of our database that is preloaded only with Static data for our CRP. I'm seeing issues with using the project combined import. The same spreadsheets worked perfectly with 606a version of DMT.
>
> I'll put in some parts tomorrow and see if I can replicate. At least then you will be able to confirm if it is site specific or not.
>
> Cheers
> SH
>
> --- In vantage@yahoogroups.com, "carlitaxbonita" <ctat121490@> wrote:
> >
> > We are having problems adding new Data into our Epicor905 and EpicorTest905 datasets.
> > It does not matter if I add a new part or supplier from the Part or Supplier screens in setup or if I try to upload data through the DMT.
> > We always get a "4GL STOP condition: The server application has returned an error. (7243)(7241). "
> > The detailed error is listed below for adding a new Part:
> >
> > Error Detail
> > ============
> > 4GL STOP condition: The Server application has returned an error. (7243) (7241)
> >
> > Stack Trace
> > ===========
> > at Progress.Open4GL.DynamicAPI.Session.runProcedure(S tring requestID, String procedureName, ParameterSet parms, Boolean persistent, Boolean internal_Renamed, Int64 procId, MetaSchema localSchema, Int32 stateModel)
> > at Progress.Open4GL.DynamicAPI.Session.runStatelessPr ocedure(String requestID, String fullProcedureName, ParameterSet inparams, Object procId, MetaSchema localSchema, Int32 stateModel)
> > at Progress.Open4GL.DynamicAPI.PersistentProc.runTheP rocedure(String requestID, String procedureName, ParameterSet parms, MetaSchema schema)
> > at Progress.Open4GL.DynamicAPI.PersistentProc.runProc edure(String procedureName, ParameterSet parms, MetaSchema schema)
> > at Epicor.Mfg.Core.CallContext.CallContextPersistentP roc.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.PartImpl.Update(PartDataSet ds)
> > at Epicor.Mfg.UI.Adapters.PartAdapter.Update()
> > at Epicor.Mfg.UI.App.PartEntry.PartTransaction.Adapte rUpdate()
> > at Epicor.Mfg.UI.App.PartEntry.PartTransaction.Update X()
> >
> >
> > When I look at the Appserver logs, I see that during the add new transaction, I get the following error:
> >
> > P-009332 T-012400 1 AS -- (Procedure: 'PartCreateRow bo/Part/Part.p' Line:9818) 24000: [Microsoft][SQL Server Native Client 10.0]Invalid cursor state
> >
> >
> > We have contacted Epicor support. They told us we need to take all the data out of the tables and then try importing the data again. We tried one table and when we try to put the data back into it, we get the same above error. It is taking a very long time to get any response from Epicor so I'm wondering if anyone has seen this before and knows a fix for it.
> >
> > Thank you.
> >
>