Web Service Logs

SUGGESTED

I am using several X3 objects exposed as web services.  When I am using the Web Services tester, I often get error messages, such as:

"BLOK,Bad input [XML] parameters (See web service process report)

but there aren't any details.  Another one I have received is

**Exception** - Class[CCommException]

X3 server did not return a response (NDRESULT).

unknown key [message.error.open.win] in resource [com.adonix.x3.comm.client.adonix.pool.CAdonixPool]

  --Stack--

 Where do I go to review the web service process report or log, so I can determine exactly what these errors mean?

Parents
  • 0
    SUGGESTED

    Hi Denise:

    For any web service tester action that you try, there are four outputs sections that will display for the web service result data (they are all available within the XML output stream)

    • Reply Description which is a description of the final processing status.
    • XML reply which shows the response part where actual Sage ERP X3 data is contained.
    • Data Process Log is a detailed account of how the input XML data was processed.
    • Request Trace which is the detailed of the entire process

     As an exmaple, below is a screen shot of an error in a webservice tester Modify action.

    In the result displayed there are 3 other sections that you can expand and the data process log should help, giving you a better explanation of the error, for instance in this example below is what is shown.

     

    Finally, for "X3 server did not return a response (NDRESULT)"  .Below information might help you

    Cause
    • This issue may be caused by an interruption in the normal flow of the object executed.
    • For example in Sales order object if you create a work flow that requires a prompt for user intervention then the web service cannot make a direct call and get a direct response.
    • A user is required to answer some piece of information or click on Some things on the screen.
    Resolution
    • Remove the interruption.
    • Note: Only SOH BPC and ITM objects are validated to work.
    • Other objects may require code customization.
Reply
  • 0
    SUGGESTED

    Hi Denise:

    For any web service tester action that you try, there are four outputs sections that will display for the web service result data (they are all available within the XML output stream)

    • Reply Description which is a description of the final processing status.
    • XML reply which shows the response part where actual Sage ERP X3 data is contained.
    • Data Process Log is a detailed account of how the input XML data was processed.
    • Request Trace which is the detailed of the entire process

     As an exmaple, below is a screen shot of an error in a webservice tester Modify action.

    In the result displayed there are 3 other sections that you can expand and the data process log should help, giving you a better explanation of the error, for instance in this example below is what is shown.

     

    Finally, for "X3 server did not return a response (NDRESULT)"  .Below information might help you

    Cause
    • This issue may be caused by an interruption in the normal flow of the object executed.
    • For example in Sales order object if you create a work flow that requires a prompt for user intervention then the web service cannot make a direct call and get a direct response.
    • A user is required to answer some piece of information or click on Some things on the screen.
    Resolution
    • Remove the interruption.
    • Note: Only SOH BPC and ITM objects are validated to work.
    • Other objects may require code customization.
Children
  • 0 in reply to Esfahani

    Even though this is an old topic:   we've had trouble with the "message.error.open.win" even when we were certain we were passing valid data -- and could only diagnose by reproducing via the GUI.  Once we identified the warning pop-up that was causing the problem, we ended up commenting out that message code in the standard processing. We're working with unsupported Objects (Work Orders and Production Tracking).