topic Re: Problem: Eclipse debugging in Application Development and Automation Discussions

Problem: Eclipse debugging

Former Member — Thu, 28 Nov 2013 08:51:40 GMT

Hello

I have a problem with elipse debugging. When I try to catch my breakpoint, Eclipse send me error message "Debugger cannot be started since there are no mathcing projects for system AE0 client 100".

Error description:

Error while attaching debugger to: DSMIRNOV at ERP13.local () in CL_NWG_SR_DAO_SO_STATCM002: 100, debuggee: 000C29975CAE1ED396834AEA6B0CDA0E, IDE: , destination: com.sap.adt.debug_AE0_SAP-ERP13.local_00@AEO_100_dsmirnov_ru

Error while attaching debugger to: DSMIRNOV at SAP-ERP13.local () in CL_NWG_SR_DAO_SO_STATCM002: 100, debuggee: 000C29975CAE1ED396834AEA6B0CDA0E, IDE: , destination: com.sap.adt.debug_AE0_SAP-ERP13.local_00@AEO_100_dsmirnov_ru

Обнаружена особая ситуация

How can I solve this problem.

Thank you.

Re: Problem: Eclipse debugging

ThFiedler — Thu, 28 Nov 2013 11:41:01 GMT

Hi Dmitry,

can you give a bit background information about your system setup.

Which ADT Version? Which ABAP backend version?

Regards,

Thomas.

Re: Problem: Eclipse debugging

Former Member — Thu, 28 Nov 2013 12:17:18 GMT

Hi Thomas!

I'm using eclipse Juno.

Eclipse wrote some also errors:

Error while attaching debugger to: DS at SAP-ERP13.local () in CL_NWG_SR_DAO_SO_STATCM002: 100, debuggee: 000C29975CAE1ED39684479DB1CE5A0E, IDE: , destination: com.sap.adt.debug_AE0_SAP-ERP13.local_00@AEO_100_ds_en

See attach files with detail eclipse and abap backend info.

Thanks a lot.

Re: Problem: Eclipse debugging

chgeo — Thu, 28 Nov 2013 12:53:00 GMT

Hi Dmitry,

Sounds like the debug info sent from the server cannot be mapped back to the projects in your workspace. To further analyze the issue, I need to following information:

Which connection data does your project for system A00 have?
- Select the project in explorer -> Properties ->ABAP Development -> Take a screenshot of the dialog.
Repeat the scenario with enabled communication log
1. Enable communication log: Preferences -> ABAP Development -> Enable communication log
2. Repeat the debug scenario
3. Collect data: Help -> Collect Support Infomation -> Additional Data -> Select "Communication Log"
4. Disable communication log in preferences (otherwise it adds a performance penalty to every request).

Attach the zip from 2 and the screenshot from 1 to this thread, or open up a ticket with it.

Regards

Christian

Re: Problem: Eclipse debugging

Former Member — Thu, 28 Nov 2013 13:18:35 GMT

Hi Christian!

I attached all info for you.Here you are.

I cann't attach zip file, that is why I extracted content.

Thank you.

Re: Problem: Eclipse debugging

chgeo — Fri, 29 Nov 2013 08:08:19 GMT

Hi Dmitry,

The system ids don't match. The server sends "AE0" while the client logon configuration specifies "AEO". I guess the server is right, so you would need to change your client logon config. So:

1. Delete your project.

2. In SAP Logon change the system id to AE0.

3. Create a new project.

Regards,

Christian

Re: Problem: Eclipse debugging

Former Member — Fri, 29 Nov 2013 11:23:57 GMT

Hi Christian,

I had checked and fixed all, but my problem haven't solved.

Eclipse writes the error like my post №2.

SAP system received error "RFC Error: CPIC-CALL: 'ThSAPCMRCV' no data received".

Communication log was empty.

Thank you.

Re: Problem: Eclipse debugging

chgeo — Fri, 29 Nov 2013 16:28:44 GMT

Ok, this now seems to be a completely different issue. Is there any dump in ST22 called like that?

Please also attached the error log from Eclipse that is in the support zip (Help -> Create Support Information).

Re: Problem: Eclipse debugging

Former Member — Mon, 02 Dec 2013 06:38:05 GMT

Hi Christian,

I think it's problem with connection between two difference systems.

Debugger works without errors in first system.

Thank you.

Re: Problem: Eclipse debugging

former_member186363 — Fri, 04 Apr 2014 05:32:27 GMT

Hi Christian,

Thanks for sharing the solution.

I ran into the same issue and was able to resolve it based on information shared by you.

Issue:-

System name AA0 but on logon pad it has a description e.g. A01 Netweaver AA0. When creating a new project, I selected the system AA0 but it captured the system id as A01 instead of AA0.

Solution:-

Changed the description from "A01 Netweaver AA0" to "AA0 Netweaver AA0" and it picked the correct system id.

Question to SAP:

Why is SAP not permitting us to enter the system id? Why is SAP defaulting the system id to first 3 characters of description?

Looking forward to response from SAP.

Regards,

Anuj Kumar

Re: Problem: Eclipse debugging

chgeo — Fri, 04 Apr 2014 06:59:00 GMT

Hi Anuj,

the upcoming ADT shipping with NetWeaver SP7 (probably June 2014) contains improvements in this area:

Debugger does no longer wrongly match against the system id in the logon pad data, but use the correct id transmitted from the server.
You can define your own system connections from within Eclipse, and also add a custom system id.

So, stay tuned for this release!

Hope this helps & sorry for the inconveniences caused,

Christian