cancel
Showing results for 
Search instead for 
Did you mean: 

Debug point is not getting triggered in WD ABAP application

Former Member
0 Kudos

Hi Experts,

I'm not able to trigger the debugger from WD after upgrading the system to EHP1.

But I'm able to trigger debugger from normal GUI applications.

Can anybody tell me what the problem exactly is or any OSS note which can help?

thanks in advance,

Subhasis

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

Hi subhasis,

Check out the SAP notes 1004248, 1386082, 668252, 668256, 751872 & note 868830 - Cannot debug an RFC in a HTTP session

Also check the [SAP Help|http://help.sap.com/saphelp_nw70ehp1/helpdata/en/48/74d50bd1431b5ae10000000a42189c/frameset.htm] for Debugging Web Dynpro ABAP Applications & check the Wiki [Why debugger don't stop at my break-point?|http://wiki.sdn.sap.com/wiki/display/ABAP/ABAP+Debugger#ABAPDebugger-Whydebuggerdon%27tstopatmybreakpoint%3F].

Hope it helps you.

KiranJ
Active Participant
0 Kudos

Hai ,

goto the SICF tcode on that find the ur component name and delete the user login details like,

that should be empty, at time of runing the application its asking for user name and password.

follow steps and external Break point is Trigger.

i hope its helpful.

Former Member
0 Kudos

Try this:

Go to the method WDDOINIT and set an EXTERNAL BREAK-POINT, once you have the external breakpoint go to TCODE SRDEBUG and ACTIVE your external break-points.

Now run your app, SRDEBUG will activate all your external BP and it should work.

hope this help

Jason PV

Former Member
0 Kudos

Hi subhasis ,

Read this OSS note .

Note 1386082 - ICF: External debugging does not work

Regards,

chinnaiya P