These are the SC messages - It's really annoying- I think we would use this more if it worked on 100% of records
System.Web.Services.Protocols.SoapException: 4GL STOP condition: The Server application has returned an error. (7243) (7241) ;
Client proxy error
Original exception: System.Web.Services.Protocols.SoapException
Code:http://schemas.xmlsoap.org/soap/envelope/:Server
Actor:
Detail: <detail> 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.Proxy.ReceiptsFromMfgImpl.ReceiveMfgPartToInventory(ReceiptsFromMfgDataSet ds, Decimal pdSerialNoQty, Boolean plNegQtyAction, String& pcMessage)
at Epicor.Mfg.WS.Adapters.ReceiptsFromMfgBaseAdapter.ReceiveMfgPartToInventory(XmlNode& ds, Decimal pdSerialNoQty, Boolean plNegQtyAction, String& pcMessage)
at Epicor.Mfg.WS.Services.ReceiptsFromMfgService.ReceiveMfgPartToInventory(String CompanyID, XmlNode ds, Decimal pdSerialNoQty, Boolean plNegQtyAction, String& pcMessage)</detail>
System.Web.Services.Protocols.SoapException: 4GL STOP condition: The Server application has returned an error. (7243) (7241) ;
Client proxy error
Original exception: System.Web.Services.Protocols.SoapException
Code:http://schemas.xmlsoap.org/soap/envelope/:Server
Actor:
Detail: <detail> 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.Proxy.ReceiptsFromMfgImpl.ReceiveMfgPartToInventory(ReceiptsFromMfgDataSet ds, Decimal pdSerialNoQty, Boolean plNegQtyAction, String& pcMessage)
at Epicor.Mfg.WS.Adapters.ReceiptsFromMfgBaseAdapter.ReceiveMfgPartToInventory(XmlNode& ds, Decimal pdSerialNoQty, Boolean plNegQtyAction, String& pcMessage)
at Epicor.Mfg.WS.Services.ReceiptsFromMfgService.ReceiveMfgPartToInventory(String CompanyID, XmlNode ds, Decimal pdSerialNoQty, Boolean plNegQtyAction, String& pcMessage)</detail>
--- In vantage@yahoogroups.com, Karen Schoenung <kschoenung@...> wrote:
>
> The errors below seem to be in the logs for Epicor...Do you get any errors in the Service Connect workflows?
>
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Rupert
> Sent: Tuesday, September 13, 2011 9:06 AM
> To: vantage@yahoogroups.com
> Subject: [Vantage] Service Connect - some records not processed
>
>
>
> Hi All,
>
> We have occasions when we get service connect server connect errors. We may run a 1000 records then 3 or 4 may get random fails?
>
> Does anyone else get similar problems?
>
> this is the error message we get
>
> [11/09/13@09:08:56.772+0100] P-005804 T-005088 1 AS -- (Procedure: 'CommLinkTest as/deactivate.p' Line:90) Unable to communicate with the datatabase. (No message).
> [11/09/13@09:08:56.772+0100] P-005804 T-005088 1 AS -- (Procedure: 'CommLinkTest as/deactivate.p' Line:105) Trying to re-acquire database connection 0 seconds elapsed...
> [11/09/13@09:08:56.913+0100] P-005804 T-005088 1 AS -- (Procedure: 'CommLinkTest as/deactivate.p' Line:113) Database connection re-acquired successfully
> [11/09/13@09:08:57.007+0100] P-005804 T-005088 3 AS AS requestID= NULL
>
>
>
> [Non-text portions of this message have been removed]
>