Skip to Content
author's profile photo Former Member
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 a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • author's profile photo Former Member
    Former Member
    Posted on 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


    external_debug.JPG (49.0 kB)
    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on 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 a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.