<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Not getting stopped on debugger point in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/not-getting-stopped-on-debugger-point/m-p/10848396#M1885342</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Mathew,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for your answer. Yes you are right there are some 9 application servers in the system. So what I did was, I went to tcode srdebug and tried to active it for all application servers. But still i am not able to reach the debugging point. Any other suggestion to activate it in all application servers.?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BR.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 31 Dec 2014 12:15:20 GMT</pubDate>
    <dc:creator>former_member207873</dc:creator>
    <dc:date>2014-12-31T12:15:20Z</dc:date>
    <item>
      <title>Not getting stopped on debugger point</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/not-getting-stopped-on-debugger-point/m-p/10848391#M1885337</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Experts,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; I am having an adobe form which is getting called from&amp;nbsp; SAP PLM application (webdynpro based). I am able to reach the debugger point in dev and quality with the help of generating the function module for the adobe form and putting the external debugger point. But the same way i tried in production, the debugging is not getting triggered. What will be the possible reason for this ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BR.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 31 Dec 2014 11:00:38 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/not-getting-stopped-on-debugger-point/m-p/10848391#M1885337</guid>
      <dc:creator>former_member207873</dc:creator>
      <dc:date>2014-12-31T11:00:38Z</dc:date>
    </item>
    <item>
      <title>Re: Not getting stopped on debugger point</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/not-getting-stopped-on-debugger-point/m-p/10848392#M1885338</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Sam,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check your System Setting.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Go to&lt;/P&gt;&lt;P&gt;SE38-&amp;gt;Menu-&amp;gt;Utilities-&amp;gt;setting-&amp;gt;in ABAP Editor tab-&amp;gt;Debugging tab-&amp;gt;Put user Production User id.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;and then check with External Break-point.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;And also check, Your user id is having Debug authorization of not. (once you will enter you user id in setting, and if your user id is not having authorization for debug, a pop-up message will appear. )&lt;/P&gt;&lt;P&gt;regards.&lt;/P&gt;&lt;P&gt;Praveer.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 31 Dec 2014 11:11:46 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/not-getting-stopped-on-debugger-point/m-p/10848392#M1885338</guid>
      <dc:creator>ipravir</dc:creator>
      <dc:date>2014-12-31T11:11:46Z</dc:date>
    </item>
    <item>
      <title>Re: Not getting stopped on debugger point</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/not-getting-stopped-on-debugger-point/m-p/10848393#M1885339</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Not the same sap user ID?&lt;BR /&gt;The ID not have SAP_ALL authority in SU01?&lt;/P&gt;&lt;P&gt;Interesting.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 31 Dec 2014 11:13:41 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/not-getting-stopped-on-debugger-point/m-p/10848393#M1885339</guid>
      <dc:creator>former_member192023</dc:creator>
      <dc:date>2014-12-31T11:13:41Z</dc:date>
    </item>
    <item>
      <title>Re: Not getting stopped on debugger point</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/not-getting-stopped-on-debugger-point/m-p/10848394#M1885340</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Praveen,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for your answer. I am using a fire fighter id. So that id is being shown in the debugging user space.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BR.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 31 Dec 2014 11:27:56 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/not-getting-stopped-on-debugger-point/m-p/10848394#M1885340</guid>
      <dc:creator>former_member207873</dc:creator>
      <dc:date>2014-12-31T11:27:56Z</dc:date>
    </item>
    <item>
      <title>Re: Not getting stopped on debugger point</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/not-getting-stopped-on-debugger-point/m-p/10848395#M1885341</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Go to SM51. If there is more than one application server shown, then that's the answer. You have to set an external breakpoint in the code on &lt;SPAN style="text-decoration: underline;"&gt;each&lt;/SPAN&gt; application server. Which can be annoying when you've got thirty of them... &lt;SPAN __jive_emoticon_name="shocked" __jive_macro_name="emoticon" class="jive_macro_emoticon jive_macro jive_emote" src="https://community.sap.com/1103/images/emoticons/shocked.gif"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 31 Dec 2014 11:39:29 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/not-getting-stopped-on-debugger-point/m-p/10848395#M1885341</guid>
      <dc:creator>matt</dc:creator>
      <dc:date>2014-12-31T11:39:29Z</dc:date>
    </item>
    <item>
      <title>Re: Not getting stopped on debugger point</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/not-getting-stopped-on-debugger-point/m-p/10848396#M1885342</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Mathew,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for your answer. Yes you are right there are some 9 application servers in the system. So what I did was, I went to tcode srdebug and tried to active it for all application servers. But still i am not able to reach the debugging point. Any other suggestion to activate it in all application servers.?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BR.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 31 Dec 2014 12:15:20 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/not-getting-stopped-on-debugger-point/m-p/10848396#M1885342</guid>
      <dc:creator>former_member207873</dc:creator>
      <dc:date>2014-12-31T12:15:20Z</dc:date>
    </item>
    <item>
      <title>Re: Not getting stopped on debugger point</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/not-getting-stopped-on-debugger-point/m-p/10848397#M1885343</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I don't know what you mean by "srdebug".&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Go to SM51. You can switch into each application server in turn and set the breakpoint at the appropriate place.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 31 Dec 2014 12:31:46 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/not-getting-stopped-on-debugger-point/m-p/10848397#M1885343</guid>
      <dc:creator>matt</dc:creator>
      <dc:date>2014-12-31T12:31:46Z</dc:date>
    </item>
    <item>
      <title>Re: Not getting stopped on debugger point</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/not-getting-stopped-on-debugger-point/m-p/10848398#M1885344</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Mathew,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SRDEBUG is a tcode. We can make external debugger active for all application server for a particular user. This is an alternative for putting break point in each server.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BR.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 31 Dec 2014 12:40:37 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/not-getting-stopped-on-debugger-point/m-p/10848398#M1885344</guid>
      <dc:creator>former_member207873</dc:creator>
      <dc:date>2014-12-31T12:40:37Z</dc:date>
    </item>
  </channel>
</rss>

