Skip to Content
avatar image
Former Member

External debugging from .NET not working

We have a .Net system making a web service call into our ECC system. It is a 7.02 Netweaver system. I have External debugging turned on and placed an External Breakpoint in the RFC that gets called from the web service. However after trying everything suggested and based on OSS Notes, the WS call will never trigger the debugger window to open.

We have been able to trigger it using a Web Dynpro application, so we know the external debugger works but NOT thorough the .Net web service call.

The user being passed from .Net is the SAP dialog user. Please dont respond with the steps in how to turn on the external debugger....we have done that and know it works when we do it through a WD application.

Something is different when coming in through a wsdl web service call.

Anyone?

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • avatar image
    Former Member
    Aug 21, 2015 at 07:47 PM

    Hello Mike

    Is the external debugger set to the user who logs from the .Net application into the ECC system? Please check the debugger settings in SE37 is something similar to the picture below, with the corresponding user set. (Menu Utilities->Settings->ABAP Editor->Debugging).

    Also please chek ST22. Sometimes a dump can be occurring prior to the debugger hit the external breakpoint.

    Regards

    Luis Becker

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Dec 15, 2015 at 07:37 PM

    Hi Mike,

    I don't think that a deep technical problem like this can be solved without traces (RFC trace, kernel workprocess trace etc.)

    The only chance to get a solution to this is to open an OSS ticket and let SAP Dev Support
    analyze/debug it.

    Best Regards, Ulrich

    Add comment
    10|10000 characters needed characters exceeded