Error while attaching debugger - route permission denied

[ChristophLordieck]

Hi all,

i can't start the debugger in my adt. I get the following error:

I searched some older threads and already checked:

- Number of workprocesses defined for debugging in RZ11 is ok (8 of 15 total)

- There are free workprocesses to debug. I can use the normal debugger without problems

- I assigned all necessary roles to my user

- I checked the consistency between sap gui connection configuration and eclipse

I still can't access the debugger. Everything else kinda works fine so far. Any ideas? Which information do you need additionally?

I appreciate your help.

Regards,

Christoph

[ChristophLordieck]

Hi all,

i can't start the debugger in my adt. I get the following error:

I searched some older threads and already checked:

- Number of workprocesses defined for debugging in RZ11 is ok (8 of 15 total)

- There are free workprocesses to debug. I can use the normal debugger without problems

- I assigned all necessary roles to my user

- I checked the consistency between sap gui connection configuration and eclipse

I still can't access the debugger. Everything else kinda works fine so far. Any ideas? Which information do you need additionally?

I appreciate your help.

Regards,

Christoph

[Armin_Beil]

Hello Christoph,

we are currently still checking this. We will give you an update as soon as possible.

Best regards,

Armin

[Armin_Beil]

Hi Christoph,

the error route permission denied is raised by a SAProuter and it means that your client is not allowed to access the target application server sap01-205. This interrupts the ADT Debugger startup.

We tested the ADT Debugger startup in combination with a SAProuter in our systems but we found no general issues on debugger side.

Currently we see 2 scenarios that could potentially cause this error:

1) Maybe a SAProuter configuration on your network or your target network causes the problem. Granting access to server sap01-205 via the SAProuter permissions table might be the fix.

Why the other ADT tools are working in this case:

As you probably know an SAP system can have multiple ABAP application servers. When you use ADT (or SAP GUI) to logon to a system there is some load balancing that decides which one of those servers you reach. Afterwards all requests are sent to that same server until you log off.

But there is one special case: For debugging it is necessary that the backend debugger instance is created on the same server where the debuggee (the process to be debugged) runs.

External requests (requests that are not started from your IDE; for example a HTTP request from a browser / UI5 or a RFC call from a foreign system) do not belong to your ADT logon session and therefore are processed on any server. In case you try to debug such an external request the debugger has to potentially access a different server than the rest of ADT.

For example ADT is connected to server XY while you are trying to debug an external request that is processed on server sap01-205. If access to sap01-205 is not allowed everything but debugging that external request works.

2) If your network configuration would require a server name different from "sap01-205" to access that server from outside the network. This might also explain the symptoms even for non-external requests.

How to go on:

You can verify the first scenario by simply trying to debug a non-external request in ADT (e.g. try to debug a simple report without any RFC logic that is directly started from ADT).

• If that works you should check if there is some SAProuter on the path from your network to server sap01-205 that needs configuration adjustments.
• If this simple test gives the same exception as before then scenario 1 is not relevant for you. In that case and/or if you need further support we would ask you to create a customer incident for further processing.

For an incident please also provide the following information:

• ADT support.zip file (ADT Menu "Help" -> "Collect Support Information")
• The file dev_jco_rfc.log from your ADT installation directory
• The server list shown by transaction SM51 in your ABAP system I68 (screenshot or text)
• Within ADT you can see the currently used application server on the bottom bar once you set the cursor into some code. We would ask you to note down this name, reproduce the mentioned exception, note down the server name that is mentioned in the exception and let us know both (or at least whether they are identical).

Additionally we plan for ADT 2.68 (planned to be available in October) a change regarding the debugger backend connection. This might also fix your issue in some cases, but probably not for all cases.

Best regards,

Armin

[ChristophLordieck]

Hi Armin,

thank you very much for your effort and the background information! I'm gonna check your suggestions as soon as possible. I'll keep you updated if i find any solutions for this.

Best regards,

Christoph

[ChristophLordieck]

Hi Armin,

i wasn't able to resolve the issue so far. I addressed it to our hoster and hopefully they will take care of this now. Thank you anyways for your great support, hopefully other people get their issues resolved with these information.

Regards,

Christoph