topic SAP GUI transaction does not open when launched from Eclipse in Application Development and Automation Discussions

SAP GUI transaction does not open when launched from Eclipse

satadas30 — Fri, 03 Jul 2020 22:18:38 GMT

I have Eclipse 2020-03 version and ADT version 3.10.0 installed. I have noticed that when try to launch any SAP GUI transaction, it opens up properly for the first time. However, it stops working when i try to launch it again on a different window.

Has anyone faced the same issue? How to resolve this issue?

Re: SAP GUI transaction does not open when launched from Eclipse

Sandra_Rossi — Sat, 04 Jul 2020 13:26:41 GMT

You say "launch it again on a different window".

What do you mean?

Re: SAP GUI transaction does not open when launched from Eclipse

balbinosoares — Sat, 04 Jul 2020 15:10:40 GMT

Some times ADT facing some kind of bug. Do you tried to uninstall ADT ... Or disconnect from your project? I say it because you inform me that the first time you were able to connect ... Otherwise could be an authorization issue.

Re: SAP GUI transaction does not open when launched from Eclipse

satadas30 — Sat, 04 Jul 2020 17:24:41 GMT

The GUI application opens up in a new tab when i execute a report for the first time after opening up Eclipse. But as soon as I try to execute any other report or the same report it displays a blank screen. I need to restart my eclipse to make it work again.

Re: SAP GUI transaction does not open when launched from Eclipse

satadas30 — Sat, 04 Jul 2020 17:27:52 GMT

i did try that. But that did not help. However, I noticed that as soon as I close Eclipse a log file is generated on my desktop with the error RFC_ERROR_REQUEST_CANCELLED.

Re: SAP GUI transaction does not open when launched from Eclipse

balbinosoares — Sat, 04 Jul 2020 17:51:36 GMT

Take a look in this configuration guide. https://help.sap.com/doc/2e65ad9a26c84878b1413009f8ac07c3/201909.000/en-US/config_guide_system_backend_abap_development_tools.pdf, maybe can help you. Other functionalities are ok? Only transactions are problem? Maybe the basis team can help you to identify the problem. I think it's related to authorization. Please check if your user have the authorizations according to guide.

Re: SAP GUI transaction does not open when launched from Eclipse

Sandra_Rossi — Sat, 04 Jul 2020 18:21:09 GMT

Do you have the same error with a very simple report like just one line "WRITE 'hello world'."?

You say you have a Eclipse log file with error RFC_ERROR_REQUEST_CANCELLED. Could you post the messages around?

Does the Eclipse error/problem/communication views say anything? (test all views you can find)

NB: I searched RFC_ERROR_REQUEST_CANCELLED in SAP notes and found nothing.

Re: SAP GUI transaction does not open when launched from Eclipse

satadas30 — Mon, 13 Jul 2020 01:52:53 GMT

Yes, the error persists for a simple report with one line of code as well.

No, I can't find any details in Eclipse in any of the Views.

Here is what the Eclipse Log File looks like:

**** Error file opened at 20200704 132705 Eastern Daylight Time Rel. 3.1.2 (2019-10-02) [753.512]
Error: >Sat Jul 04 13:27:05,625< >RfcGetException (rc=24) message: connection [4/16415583] closed after cancel

at com.sap.conn.rfc.engine.RfcIoOpenCntl.RfcCancel(RfcIoOpenCntl.java:1892)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcConnection.cancel(MiddlewareJavaRfc.java:587)
at com.sap.conn.jco.rt.ClientConnection.cancel(ClientConnection.java:209)
at com.sap.conn.jco.rt.ConnectionManager.releaseWithCancel(ConnectionManager.java:315)
at com.sap.conn.jco.rt.Context.closeConnections(Context.java:324)
at com.sap.conn.jco.rt.Context.reset(Context.java:386)
at com.sap.conn.jco.rt.DefaultSessionManager.finished(DefaultSessionManager.java:181)
at com.sap.adt.communication.internal.jco.session.JCoSessionManager.removeSession(JCoSessionManager.java:157)
at com.sap.adt.communication.internal.jco.session.JCoSession.closeInternal(JCoSession.java:150)
at com.sap.adt.communication.internal.jco.session.JCoSession.terminate(JCoSession.java:129)
at com.sap.adt.communication.internal.jco.dispatcher.JCoFunctionExecutor.doCancel(JCoFunctionExecutor.java:165)
at com.sap.adt.communication.util.CancelableBlockingJob.run(CancelableBlockingJob.java:162)
at com.sap.adt.communication.internal.jco.dispatcher.JCoRequestDispatcher.dispatchInternal(JCoRequestDispatcher.java:162)
at com.sap.adt.communication.internal.jco.dispatcher.JCoRequestDispatcher.dispatch(JCoRequestDispatcher.java:106)
at com.sap.adt.communication.internal.session.SystemSession.dispatchRequest(SystemSession.java:150)
at com.sap.adt.communication.internal.session.SystemSession.sendRequest(SystemSession.java:145)
at com.sap.adt.communication.internal.resources.RestResource.invoke(RestResource.java:168)
at com.sap.adt.communication.internal.resources.RestResource.post(RestResource.java:90)
at com.sap.adt.debugger.internal.AbapDebuggerServices.post(AbapDebuggerServices.java:874)
at com.sap.adt.debugger.internal.AbapDebuggerServices.waitForDebuggeeSessions(AbapDebuggerServices.java:743)
at com.sap.adt.debugger.ui.internal.launch.AutoAttachBackendListener.waitForDebuggeesAndAttach(AutoAttachBackendListener.java:683)
at com.sap.adt.debugger.ui.internal.launch.AutoAttachBackendListener.access$2(AutoAttachBackendListener.java:667)
at com.sap.adt.debugger.ui.internal.launch.AutoAttachBackendListener$AutoAttachJob.run(AutoAttachBackendListener.java:1045)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)

<RfcGetException

Error: [4] >Sat Jul 04 13:27:05,630< RfcException raised by system [S4S|ussltcsnl1379|00]:
message: connection [4/16415583] closed after cancel

at com.sap.conn.rfc.engine.RfcIoOpenCntl.RfcCancel(RfcIoOpenCntl.java:1892)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcConnection.cancel(MiddlewareJavaRfc.java:587)
at com.sap.conn.jco.rt.ClientConnection.cancel(ClientConnection.java:209)
at com.sap.conn.jco.rt.ConnectionManager.releaseWithCancel(ConnectionManager.java:315)
at com.sap.conn.jco.rt.Context.closeConnections(Context.java:324)
at com.sap.conn.jco.rt.Context.reset(Context.java:386)
at com.sap.conn.jco.rt.DefaultSessionManager.finished(DefaultSessionManager.java:181)
at com.sap.adt.communication.internal.jco.session.JCoSessionManager.removeSession(JCoSessionManager.java:157)
at com.sap.adt.communication.internal.jco.session.JCoSession.closeInternal(JCoSession.java:150)
at com.sap.adt.communication.internal.jco.session.JCoSession.terminate(JCoSession.java:129)
at com.sap.adt.communication.internal.jco.dispatcher.JCoFunctionExecutor.doCancel(JCoFunctionExecutor.java:165)
at com.sap.adt.communication.util.CancelableBlockingJob.run(CancelableBlockingJob.java:162)
at com.sap.adt.communication.internal.jco.dispatcher.JCoRequestDispatcher.dispatchInternal(JCoRequestDispatcher.java:162)
at com.sap.adt.communication.internal.jco.dispatcher.JCoRequestDispatcher.dispatch(JCoRequestDispatcher.java:106)
at com.sap.adt.communication.internal.session.SystemSession.dispatchRequest(SystemSession.java:150)
at com.sap.adt.communication.internal.session.SystemSession.sendRequest(SystemSession.java:145)
at com.sap.adt.communication.internal.resources.RestResource.invoke(RestResource.java:168)
at com.sap.adt.communication.internal.resources.RestResource.post(RestResource.java:90)
at com.sap.adt.debugger.internal.AbapDebuggerServices.post(AbapDebuggerServices.java:874)
at com.sap.adt.debugger.internal.AbapDebuggerServices.waitForDebuggeeSessions(AbapDebuggerServices.java:743)
at com.sap.adt.debugger.ui.internal.launch.AutoAttachBackendListener.waitForDebuggeesAndAttach(AutoAttachBackendListener.java:683)
at com.sap.adt.debugger.ui.internal.launch.AutoAttachBackendListener.access$2(AutoAttachBackendListener.java:667)
at com.sap.adt.debugger.ui.internal.launch.AutoAttachBackendListener$AutoAttachJob.run(AutoAttachBackendListener.java:1045)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)

return code: RFC_CANCELED (20)
error group: 112
key: RFC_ERROR_REQUEST_CANCELLED

Re: SAP GUI transaction does not open when launched from Eclipse

satadas30 — Mon, 13 Jul 2020 02:00:23 GMT

I think you are correct. I did check SU53 records and it seems that certain roles are missing.