Remote debugging of 4.6C from ecc 6.0

Hello,
we are developing Web applications in WD Abap on an ecc 6.0 system. The necessary data are provided from a 4.6c System.
Question.
I need to DEBUGG the functionality on the 4.6C system with input from the website (ecc6.0 application). Can anyone give me a hint or tell me which settings are necessary - in 4.6C or in ecc 6.0.
note: in 4.6C there is no tab (at least i don't have one) with 'Debugging' like there is in ecc when you do 'tc_SE80 -> go to -> abap editor -> debugging'.
thank you in advance.

I can only suggest to refer you :
http://help.sap.com/saphelp_nw04s/helpdata/en/8c/8f2422e701604cb9f8f4f4b15bd7b9/frameset.htm
Re: Remote Debugging SAP J2EE 6.30 - WEB AS 6.40

Similar Messages

Debugging RFC function module from ECC to CRM

Hi All,
My requirement is to debug an RFC function module present in CRM(7.0) system from ECC(6.0) system. A report program in ECC will call CRM custom FM. I found many posts in SDN with the same issue and tried to implement suggestions provided there. But I couldn't succeed. The approach I followed is:
I logged in to ECC report program and kept an external breakpoint just before the function module call.
I logged in to CRM system, opened the function module and kept an external breakpoint there.
In both the systems I provided the dialogue userid( id through which I log in to SAPGUI) in the system->settings->debugging option.
In CRM I activated the external break point in transaction SRDEBUG.
Now when I execute the report program in ECC, control stops at the breakpoint. If I press F5 at the function call, control is not going to the external break point set in the CRM FM. I am getting output of FM directly.
I tried with different settings like turning on the check box for IP matching and session breakpoint active immediate, switching to classic debugger etc. I also tried to provide the RFC user id instead of dialogue user but system throws exception saying only dialogue userids are allowed. I found that by inserting an infinite loop statement, control goes inside the RFC CRM FM but I prefer not to change the code.
Please let me know if I missed anything.
Thanks and Regards,
Naren

Hi,
Debug RFC calls
When an RFC function module is called it is usually not possible to debug the call, using the below techniques we can achieve the same. For this example we are calling an RFC enabled FM in ECC system from CRM system.
Scenario 1: Calling a custom RFC FM
STEP 1: Add an infinite loop in the remote custom Function Module (adding a u201CDO. ENDDO.u201D statement at the start of the FM would be enough).
STEP 2: Execute your program in the CRM system. The execution stops at the RFC call, because of the infinite loop.
STEP 3: Now login to the ECC system and go to transaction SM51 select the process which is executing the RFC and navigate to the menu: u201CProgram/Session->Program->Debuggingu201D this triggers the debugger session in a separate window.
Scenario 2: Calling a Standard RFC FM
When we are debugging a standard program we cannot add the infinite loop, hence we cannot go to SM51 and debug the work process. The RFC destination for the ECC system has a User specified, the RFC function module gets executed using this users credentials. Usually the basis team set up the RFC user as non Dialog user, this does not allow debugging. Contact your Basis team and get this changed to a dialog user enabling you to debug RFC function calls via the normal debugger.
Note: User name configured in the RFC destination (transaction SM59)
Note: User type for the RFC User (transaction SU01D)
Hope this will be helpful..

WD Java Remote Debug problem: Release Process from debugging

Hi Community,
when I used to debug Web Dynpro Java from the SAP Developer Studio (eclipse) to a remote host (Portal AS NW Java), it works fine for the first run. After disconnecting the remote debug session (server0), I changed the coding and try to debug again with the effect that the old coding is still used from the server process (server0) even though the parameter "Create and Deploy archive" is set (enabled) in the debug configuration. Furthermore the funktionality of "Relase process from debugging" option in the J2EE Engine dosn't react / work.
I think that the debug session is still running and the Developer Studio is not able to send any "Kill" statement to the server process for ending this session.
I tried following:
A. Rebuild Project and Deploy the archive on the "normal" way
B. Reopen the Developer Studio itself
C. Start the Project in debugmode again and chose the option "Terminate All"
...all without any success.
The only way is to restart the whole server process server0 again with the same trouble after the first debug.
Did any of you have a clue or experience to clear or kill the debugsession from the process so that next debugsessions can be started, please reply.
Thanks
Used Basic Manuell
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/849170e3-0601-0010-d59e-ddfce735fac5

So, I'm having the same issue, but it's like I'm chasing down a port. The first time I got these error messages
Connecting to the database DEV.
Executing PL/SQL: ALTER SESSION SET PLSQL_DEBUG=TRUE
Executing PL/SQL: CALL DBMS_DEBUG_JDWP.CONNECT_TCP( '555.12.18.288', '5950' )
ORA-30683: failure establishing connection to debugger
ORA-12535: TNS:operation timed out
ORA-06512: at "SYS.DBMS_DEBUG_JDWP", line 68
ORA-06512: at line 1
Process exited.
Disconnecting from the database DEV.Our network staff found a bunch of other denials in the firewall logs
/5185
/5200
/5236
/5815
/5950 Now that they've those allowed, I tried to start debug again, and this time I got
Connecting to the database DEV.
Executing PL/SQL: ALTER SESSION SET PLSQL_DEBUG=TRUE
Executing PL/SQL: CALL DBMS_DEBUG_JDWP.CONNECT_TCP('555.12.18.288', '6266' )
ORA-30683: failure establishing connection to debugger
ORA-12535: TNS:operation timed out
ORA-06512: at "SYS.DBMS_DEBUG_JDWP", line 68
ORA-06512: at line 1
Process exited.
Disconnecting from the database DEV.What gives? Do I just keep trying until I get all of the ports allowed?
Thanks,
---=Chuck

Remote debugging through NAT - VS2013, C#

I need help figuring out how to initiate a remote debugging session when the target computer is across the internet and behind NAT. VS2013 and a C# application, .net 4.5
Remote debugging works great here on my LAN, but now I need to connect to a remote stand alone (not on a domain) PC that is behind NAT; it's WAN IP is different from its LAN IP. My development PC is also behind NAT. I do not have access to the
remote firewall/router to configure port forwarding. Is there any other way I can connect? Are there any tools that will allow me to connect directly to the remote PC with the remote debugger, similar to how TeamViewer can connect to PC's even
though they're behind NAT?

Hi Matt_FL,
Like this document here:
http://www.codeproject.com/Tips/618804/Remote-debugging-for-Visual-Studio-from-different
It shared us the detailed steps about how we setup the remote debugging if the Environments are not in the same domain.
So I'm afraid that we would check whether the Environments meet the requirements of remote debugging.
Reference:
https://msdn.microsoft.com/en-us/library/vstudio/bt727f1t%28v=vs.100%29.aspx?f=255&MSPPError=-2147217396#bkmk_setuptheremotecomputer
If the remote computer is protected by a firewall, you must configure the firewall to allow the Remote Debugging Monitor to communicate with the Visual Studio host computer.
If your network requires that communication be performed using IPSec, you must open additional ports in the firewall.
If you are debugging a process on a web server, you must open an additional port.
Other threads I met before:
https://social.msdn.microsoft.com/Forums/vstudio/en-US/0058a97a-8595-4235-88b1-7575aed2e2de/remote-debug-issuevisual-studio-remote-computer-can-not-back-connect-to-remote-computera-firewall?forum=vsdebug
https://social.msdn.microsoft.com/Forums/vstudio/en-US/897782e5-dada-4df1-8ef2-f119cdce7e5e/remote-debugging-over-internetMaybe
you could refer to them, hope it could provide useful information.
But as far as I know, we could remote debugging with WAN even if it has some specific requirements.
Reference:
http://stackoverflow.com/questions/5091207/net-remote-debugging-domain-networking-issues
If I have misunderstood this issue, please feel free to let me know.
Best Regards,
Jack
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Remote debugging issue

I've used the following remote debug properties and able to remote debug the Weblogic server from Oracle workshop.
-Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n
But this restricts to only one user/ client at any given time. Is there anyway inwhich one can enable mulitple user while remote debugging?
Amarnath

Not sure if it matters but I am using JDEV 9.0.3.4 with a 9.2.0.4 database and successfully stepped into and over a call to a java stored procedure from a PL/SQL trigger. I have a PL/SQL procedure which causes a trigger to be fired which in turn calls a Java Stored procedure.
Here is what I did:
1) create PL/SQL (including trigger and procedure) and deploy Java Stored Procedure
2) In SQLPlus send the command:
ALTER SESSION SET PLSQL_DEBUG=TRUE;
3) Execute the PL/SQL Procedure (which causes trigger to be fired)
4) In JDeveloper select Project properties->Debugger->remote and select JPDA Listen
5) Set a breakpoint in the trigger
6) Select debug and enter a port number for the listener
7) In SQLPLUS send the command:
CALL DBMS_DEBUG_JDWP.CONNECT_TCP( '<Your IP>', '<listener port>' );
8) Verify call succeeded is received in SQLPlus and debuggee connects to the debugger in JDeveloper.
9) Execute the PL/SQL procedure
10) When breakpoint hit stepped into the Java Stored procedure (which was not in the project so added to source path via the popup dialog)
11) stepped out of the Java Stored Procedure back into trigger
Hope this helps,
Bud

Remotely debugging JWS

I have deployed WAR file in Tomcat. Now I am accessing this application through the Java Web Start. I want the debug my code (In Eclipse) while accessing the application through the JWS.
I did the following:
1) I started Tomcat in debug mode in port 8000.
2) I configured this port in Eclipse under Debug option --> Remote Java Application.
3) I set the env variable JAVAWS_VM_ARGS=-Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket, address=8200,server=y,suspend=n
4) I accessed the JNLP application. URL used for accessing the application is http://localhost:8080/SAC/webstart/launch.jnlp
But the application is not launching in the debug mode. I am not getting any hits at my breakpoing in the Eclipse.
Please help me whether I am doing any mistakes. Also give me some reference how remote debugging works.

Start webstart from the command line like this:
JAVAWS_VM_ARGS="-Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=8070" javaws <url-to-jnlp-file>

Cannot remote debug from JDev 10.1.3 on AS 10.1.2 running hotspot

Hi,
I've set up an embedded OC4J instance in an application server as described in the help topic, "Remote Debugging in OC4J" (with a few changes, such as the fact that I added startup options using the OC4J instance Admin page of EM, rather than at the command line (since the instance is embedded in a full AS). I followed the directions specifically for HotSpot, because that's the JVM the instance was set up to use, and I can't change it (I know OJVM enables lots more features, but that's the situation I'm in).
I've also configured my project for remote debugging, ensuring the host name and port matches, and trying both "Attach to JDPA" and "Attach to OJVM" (these being the only two options, except for starting a listener, which I don't think will help with a web application).
When I try to debug, though, I get:
Debugger unable to connect to remote process.
Should I be doing something differently?
Thanks much,
Avrom

I had the delete key quit working after accidentally pressing a key sequent that included the delete key. I don't know what keys were involved, but the delete key from that point on did nothing.
I am running JDeveloper 10.1.3.0.4 on Window XP.
To resolve the problem, I set the keyboard Accelerators back to 'Default' in JDeveloper.
I selected... Tools->Preferences->Accelerators
then click on 'Load preset' then I chose 'Default'
You may need to select something other than default for your platform, but that did the trick for me.

Changes are not updated from ECC to CRM How to debug

Hi,
QCs 1140049726 and 1140047459 were updated in P20 system to remove the WBS. This was done per normal P20 process and instructions. P20 system correctly reflects that QCs have no WBS value and the contracts are BOX - all is correct in P20.
CSP still shows these QCs as having a WBS assigned to them. This is incorrect. It has been over 24 hours since the P20 QCs were changed to reflect no WBS, but CSP still has not been replicated with the correct data.
How to proceed with it. How to debug from ECC to CRM.
Prem.

Hello Prem,
Could you please have a look at SAP note 656823?
This note contains debug tips for btx data transfer. Please check point 6 which talks about the delta download.
Hope this could be helpful.
Best regards,
Maggie

Remote Function Module call from ECC to CRM (how to pass parameters?)

Hi there,
I have a remote FM that I would like to call from ECC to CRM. The FM is remote-enabled, so I assume that I can call this from CRM. However, in CRM some of the table structures that is required are not available. Hence, my export/import parameters won't be match, unless I create those types in CRM, but this is going to major work!!
How do we pass/import the parameters since the data type in ECC is vastly different/not available in CRM?
Cheers

The structure will need to be defined in CRM.

JSP Remote debugging from Jdev to WL 7.0

          I am trying to remote debug my JSP deployed on WL from Jdeveloper 903.
          I have included the parameters to make WL start in a debug mode.
          I have also included ojsp.jar, servlet.jar and ojc.jar in WL classpath.
          So I can start WL in debug mode, I can launch the url to get access to my JSP,
          a break point is included in the code but it doesn't stop at the break point.
          I am using JPDA.
          Do I have to modify something else to be able to remote debug my JSP?
          PS: remote debugging my EJB works fine.
          Thanks for your help


          Is there any possibility to change the JSP engine in Weblogic server and customize
          the new JSP
          with additional parameters, so that IDE's can debug JSP code itself?
          "Mike Herrick" <[email protected]> wrote:
          >
          >As far as I know this is behaving correctly.
          >
          >To debug a JSP via JDPA you have to compile your JSPs and put the Servlet
          >classes
          >the JSP compiler spits out in your IDE Classpath. Then you can debug
          >those Servlets
          >-- but you can't set break points in the JSP itself. Not the best.
          >
          >Some IDE Vendors add this on top of JDPA etc.
          >
          >I'm not 100% on this, but think I'm correct.
          >
          >Mike
          >
          >"Magali Richard" <[email protected]> wrote:
          >>
          >>I am trying to remote debug my JSP deployed on WL from Jdeveloper 903.
          >>I have included
          >>the parameters to make WL start in a debug mode. I have also included
          >>ojsp.jar,
          >>servlet.jar and ojc.jar in WL classpath. So I can start WL in debug
          >mode,
          >>I can
          >>launch the url to get access to my JSP, a break point is included in
          >>the code
          >>but it doesn't stop at the break point. I am using JPDA. Do I have to
          >>modify something
          >>else to be able to remote debug my JSP?
          >>
          >>PS: remote debugging my EJB works fine. Thanks for your help
          >>
          >

Remote debugging from Windows to Linux

Is there a full description of every step needed to do remote cross-platform C++ debugging? I'm using the Indigo version of Eclipse CDT on Windows and would like to debug an application on a remote Linux machine.
On Windows, I do not have the ability to install a compiler or cygwin, but I do have plink and ssh on Windows. I am able to access the remote machine via RSE SFTP (a la stackoverflow.com/questions/4216822/work-on-a-remote-project-with-eclipse-via-ssh). I do have VNC but I find that the Eclipse IDE is very unresponsive under that setup, hence the desire to develop and debug from a native Windows app.
This FAQ is the most complete (wiki.eclipse.org/CDT/User/FAQ#How_do_I_debug_a_remote_application.3F), but doesn't discuss how to deal with Windows using backslash paths and having a different filesystem root compared to Linux and its forward slashes.
I am able to get a remote connection by playing around with the suggestions here (www.eclipse.org/forums/index.php?S=5e54b35462bb80f79ebb9fbbaf93a288&t=msg&th=173880), resulting in console output that looks like:
Last login: Fri Apr 6 20:19:09 2012 from foo.bar.com
echo $PWD'>'
/usr/bin/gdbserver :12345 /linux/path/to/my/binary args_to_my_binary;exit
but it fails with "Error while launching command: gdb --version"
The old FAQ is very incomplete and seems out of date: wiki.eclipse.org/TM_and_RSE_FAQ#How_can_I_do_Remote_Debugging_with_CDT.3F
This suggests it's possible but does not have sufficient details on how to set the myriad configuration options in Eclipse: stackoverflow.com/questions/6044138/remote-debugging-in-eclipse-cdt
I suspect many people would benefit if there was a clear set of instructions in one place on how to make this happen.
--Gerald Dalley

OK. I just spent the last two days figuring this out, so here are step-by-step instructions that hopefully will help others (This list is unusually anal by the standards of this group, but really simple concrete instructions would have helped me).
on the target linux box, make sure you have gdbserver. If you don't, get the gdb sources. Note: Making gdb does not build gdbserver. Instead, you have to go into the gdbserver directory and configure/make there.
Run gdb on the linux box. In the startup banner, it will say what its target is. This will be something like x86_64-unknown-linux-gnu or i686-pc-linux-gnu. Remember this for later.
Install MinGW on your Windows box (I had trouble building gdb on cygwin, so I recommend MinGW).
Download expat from http://sourceforge.net/projects/expat/files/expat/2.1.0/.Note: Do not download the Windows expat installer. Download the sources instead.
In the expat directory. "./configure --enable-shared", make, make install.
Download the gdb sources
../gdb-7.4/configure --with-expat --target=x86_64-unknown-linux-gnu --host=i686-pc-mingw32
make, make install
Time to test. On your linux box, create and compile hello.cpp to hello.
On your linux box, gdbserver :4444 hello
Note:If you are on a corporate network, non-standard ports may be blocked. Set up an ssh tunnel if necessary.
Copy hello.cpp and hello to your Windows machine
From the MinGW prompt, run "x86_64-unknown-linux-gnu-gdb ./Hello" Note: Substitute the name of the gdb you built as appropriate based on the target platform you got in step 2.
In gdb, load the executable with "file hello"
target remote localhost:4444 Note: This assumes that you have an ssh tunnel on localhost. Modify appropriately.
Verify that gdb commands like break, cont, and run work here.
Now we want to run it from outside of MinGW. In Control Panel/System/Advanced/Environment Variables add something like E:\MinGW\bin to the path. This is necessary for the loader to find libiconv_2.dll, etc. Now verify that you can do the preceding step from an ordinary Windows command prompt.
Launch Eclipse (finally!). New debug configuration C/C++ attach to process.
In Main, give path to the copy of the Linux executable on the Windows system.
In Debugger tab, set Debugger dropdown to gdbserver. Set "GDB debugger" to something like "E:\MinGW\msys\1.0\local\bin\x86_64-unknown-linux-gnu-gdb.exe" based on where your gdb is. For Connection, choose TCP and fill in the hostname and port number you've been using from gdb in the previous steps.
Make sure gdbserver is running (it often quits when the program ends) and launch the debug configuration
In the gdb console, enter "file hello," "break main," and cont or run (sometimes it wants one. Sometimes the other) and voila, you should be there.
Let me know if this works, and I'll post it somewhere better.
Good luck,
Mike

Remote debugging the Oracle weblogic 10.3.3 from eclipse

As I see the startWeblogic.cml, I am finding it totally different frim the earlier scripts. I need to do remote debugging of the weblogic 10.3.3 from eclipse. Can someone guide me. Here below is the script of startweblogic.cmd I am finding on the oracle weblogic server. Need help as I need to do the remote debugging.
1. @rem *************************************************************************
2. @rem This script is used to set up your environment for development with
3. @rem WebLogic Server. It sets the following variables:
4. @rem
5. @rem WL_HOME - The root directory of your WebLogic installation
6. @rem JAVA_HOME - Location of the version of Java used to start WebLogic
7. @rem Server. This variable must point to the root directory of a
8. @rem JDK installation and will be set for you by the installer.
9. @rem See the WebLogic platform support page
10. @rem (@DOCSHOST/platforms/index.html) for an up-to-date list of
11. @rem supported JVMs on Windows NT.
12. @rem PATH - Adds the JDK and WebLogic directories to the system path.
13. @rem CLASSPATH - Adds the JDK and WebLogic jars to the classpath.
14. @rem
15. @rem Other variables that setWLSEnv takes are:
16. @rem
17. @rem PRE_CLASSPATH - Path style variable to be added to the beginning of the
18. @rem CLASSPATH
19. @rem POST_CLASSPATH - Path style variable to be added to the end of the
20. @rem CLASSPATH
21. @rem PRE_PATH - Path style variable to be added to the beginning of the
22. @rem PATH
23. @rem POST_PATH - Path style variable to be added to the end of the PATH
24. @rem
25. @rem When setting these variables below, please use short file names(8.3).
26. @rem To display short (MS-DOS) filenames, use "dir /x". File names with
27. @rem spaces will break this script.
28. @rem
29. @rem jDriver for Oracle users: This script assumes that native libraries
30. @rem required for jDriver for Oracle have been installed in the proper
31. @rem location and that your system PATH variable has been set appropriately.
32. @rem
33. @rem For additional information, refer to the WebLogic Server Administration
34. @rem Guide (@DOCSWEBROOT/adminguide/startstop.html).
35. @rem *************************************************************************
36. @echo off
37.
38. @rem Set user-defined variables.
39. set WL_HOME=C:\bea\wlserver_10.3
40. call "%WL_HOME%\common\bin\commEnv.cmd"
41.
42. @rem Check that the WebLogic classes are where we expect them to be
43. @if exist "%WL_HOME%\server\lib\weblogic.jar" goto checkJava
44. @echo.
45. @echo The WebLogic Server wasn't found in directory %WL_HOME%\server.
46. @echo Please edit the setWLSEnv.cmd script so that the WL_HOME
47. @echo variable points to the WebLogic installation directory.
48. @echo Your environment has not been set.
49. @goto finish
50.
51. @rem Check that java is where we expect it to be
52. :checkJava
53. @if exist "%JAVA_HOME%\bin\java.exe" goto setWLSEnv
54. @echo.
55. @echo The JDK wasn't found in directory %JAVA_HOME%.
56. @echo Please edit the setWLSEnv.cmd script so that the JAVA_HOME
57. @echo variable points to the location of your JDK.
58. @echo Your environment has not been set.
59. @goto finish
60.
61. :setWLSEnv
62. set CLASSPATH=%WEBLOGIC_CLASSPATH%;%CLASSPATH%
63.
64. @rem Import extended environment
65.
66. if exist extEnv.cmd call extEnv.cmd
67. if not "%EXT_PRE_CLASSPATH%" == "" set CLASSPATH=%EXT_PRE_CLASSPATH%;%CLASSPATH%
68. if not "%EXT_POST_CLASSPATH%" == "" set CLASSPATH=%CLASSPATH%;%EXT_POST_CLASSPATH%
69. if not "%EXT_PRE_PATH%" == "" set PATH=%EXT_PRE_PATH%;%PATH%
70. if not "%EXT_POST_PATH%" == "" set PATH=%PATH%;%EXT_POST_PATH%
71.
72. @rem Get PRE and POST environment
73. if not "%PRE_CLASSPATH%" == "" set CLASSPATH=%PRE_CLASSPATH%;%CLASSPATH%
74. if not "%POST_CLASSPATH%" == "" set CLASSPATH=%CLASSPATH%;%POST_CLASSPATH%
75. if not "%PRE_PATH%" == "" set PATH=%PRE_PATH%;%PATH%
76. if not "%POST_PATH%" == "" set PATH=%PATH%;%POST_PATH%
77.
78. @echo.
79. @echo CLASSPATH=%CLASSPATH%
80. @echo.
81. @echo PATH=%PATH%
82. @echo.
83. @echo Your environment has been set.
84.
85. :finish

this Running Weblogic Server 10.3.3 in Debug mode gentleman seems to have found the solution.
if you create a server inside Eclipse, you have the menu option "start in debug mode" who should do the job for you

How to remote debug JSPs on Tomcat 5.0 from JDev 10.1.2

I can remote debug Java applications and servlets. But I can not make it stop within any JSP pages while doing remote debug. I have no problem if I debug locally within the built-in OC4J server.
I set my project properties with remote debugging -> Attaching to JPDA. I start my tomcat using catalina jpda start after setting environment variables JPDA_ADDRESS=8000 and JPDA_TRANSPORT=dt_socket.
Please help,
TIA

Ashraf, thanks for sharing your experience. I would like to comment on your precedure.
Jdeveloper 10.1.2
Tomcat 4.1.31 ( version 5.x.x won't work as it needs jdk 1.5 at least, and jdev is configured to run with 1.4 )I was able to use Jdeveloper 9.0.5 to debug a servlet running in Tomcat 5.5.9 with jdk 1.5.0. I would belive there is no fundamental obstacle for Jdeveloper 10.1.2 to debug Tomcat 5.x.x, thanks to the nature of JPDA.
a- backup $TOMCAT$\bin\catalina.bat.
b- edit $TOMCAT$\bin\catalina.bat to include the following:
set JAVA_OPTS=%JAVA_OPTS% -Xdebug -Xnoagent -Djava.compiler=NONE
-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=8000Another way is to set your environment variable JAVA_OPTS. There is then no need to modify catalina.bat.

(PC and Surface 8.1)bad pool header error: remote debugging using ARM device

Tools used:
Microsoft Visual Studio Professional 2013
Remote Debugger Monitor (Surface RT 8.1)
I have successfully activated the developer license as administrator.
I have attempted to run the test app on remote device but my pc crashes before or when reaching certification.
So far, I have attempted to run an app software for the ARM device; however, ever since I have upgraded the surface to 8.1, I constantly get the bad pool header crash, even after successfully connecting the pc to rt device.
is there any way I can resolve the issue so I can successfully to remote debugging?
any help is appreciated.

Hi,
Considering that the issue should be related to Windows RT 8.1, and Since we have limited testing environment, I suggest you submit a new case on Windows RT forum as they will be more professional on your issue:
This is the Windows RT 8.1 forum link.
http://answers.microsoft.com/en-us/windows/forum/windowsrt8_1?sort=lastreplydate&dir=desc&tab=Threads&status=&mod=&modAge=&advFil=&postedAfter=&postedBefore=&threadType=All&tm=1392101458999
The reason why we recommend posting appropriately is you will get the most qualified pool of respondents, and other partners who read the forums regularly can either share their knowledge or learn from your interaction with us. Thank you for your understanding.
Regards,
Kelvin hsu
TechNet Community Support

No master data upload from ECC to GTS

Hello together
today I have opened an OSS Note regarding a problem at our client side.
We implement SAP GTS 7.2 SP08 but I`m not able to upload any master data (customer and/or material) from ECC to GTS. This is my third implementation project. On both projects in the past, I didn`t had such a trouble with this topic in the past.
I searched the whole forum and tried every hint - everything without any success. ;-(
Unfortunately, the OSS Note is in German. But I hope that anyone could help me to find an solution. Thanks to all very much.
Here is the OSS Note:
Keine Initialüberleitung von Kunden- und Materialstämmen OSS-NOTE: 0000637481
Alle notwendigen Supportpackage-Stände für R/3, PlugIn und GTS sind eingespielt gemäss MasterGuide.
R/3 client:-
- RFC Destinationen korrekt eingestellt. Laufen sauber
- Methodenaufrufe korrekt eingestellt
- ALE Verteilmodell korrekt eingestellt
- Änderungszeiger global aktiviert
- Änderungszeiger korrekt eingestellt (siehe unten)
Customer master /SAPSLL/DEBMAS_SLL
Vendor master /SAPSLL/CREMAS_SLL
Material master /SAPSLL/MATMAS_SLL
- Ànderungszeiger den jeweiligen Funktionsbausteinen zugeordnet (siehe unten)
/SAPSLL/DEBMAS_DISTRIBUTE_R3
/SAPSLL/CREMAS_DISTRIBUTE_R3
/SAPSLL/MATMAS_DISTRIBUTE_R3
- Nummernkreise für Änderungszeiger angelegt
GTS client:-
- Logische Systeme angelegt und Gruppen zugeordnet
- RFC Destinationen korrekt eingestellt. Laufen sauber
- Methodenaufrufe korrekt eingestellt
- Partnermapping eingestellt
- Organisationsstrukturen angelegt und Buchungskreis bzw. Werken aus
Vorsystem zugeordnet
- Nummernkreise angelegt
Beispiel:
1. Kundenstamm im Vorsystem hat keine PLZ in den Stammdaten. Bei Übertragung nach GTS wird im GTS-System ein Überleitungsprotokoll erzeugt, mit dem Hinweis, dass Kunde nicht übertragen werden konnte aufgrund fehlender PLZ. Korrektes Systemverhalten.
2. Kundenstamm wurde entsprechend im Vorsystem gepflegt. Bei erneuter Übertragung wird angezeigt 0 von 1 Partner übertragen. Ein Überleitungsprotokoll in GTS wird nun nicht mehr erzeugt.
Auch unter Transaktion SLG1 wird im Vorsystem kein Anwendungs-Log
geschrieben. Ebenfalls gibt Transaktion SM58 keine Fehlerhinweise.
Edited by: Andreas Drees on Jun 29, 2009 3:35 PM

Hi Sameer,
thanks very much for your instructions. We created the variants and debugged it. Now fe found out, where the error occurs.
The call function for calling GTS "/SAPSLL/API_1006__SYNCH_MASS" gives us following message:
"Not just yet all adress numbers are collected."
Then on the other hand the SAP Basis suppors gaves us a possible solution. They told us:
The problem occurs, because the tables TBD24 and TBD62 are not filled correct.
Please use the following steps to correct this:
- Transaction BD53
- Select Message type (/SAPSLL/CREMAS_SLL, etc.), change mode
- Choose segment (mark an unmarked segemnt)
- save
- Delete the activated segment
- Activate change pointer
- in TA BD60 set up the function module correct (/SAPSLL/DEBMAS_DISTRIBUTE_R3)
The tables should filled correct after these steps. You can check it with report /SAPSLL/PLUGIN_CHECK_R3.
So I we went through these steps - but without any success. I`m getting crazy. ;-(
Regards,
Andreas

Remote debugging of 4.6C from ecc 6.0

Similar Messages

Maybe you are looking for