Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Problems with connecting to customer system

Go to solution
former_member204167
Participant

‎08-07-2015 4:37 PM

0 Kudos

Hello Guys,

I am using ABAP in Eclipse for a while now and it works fine for all systems except one of our customers. When I try to create a new ABAP Project I always receive the following (technical) message:

eclipse.buildId=4.5.0.I20150603-2000

java.version=1.8.0_31

java.vendor=Oracle Corporation

BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=de_DE

Framework arguments:  -product org.eclipse.epp.package.jee.product

Command-line arguments:  -os win32 -ws win32 -arch x86 -product org.eclipse.epp.package.jee.product

com.sap.adt.compatibility

Info

Fri Aug 07 17:21:30 CEST 2015

Failed to load discovery "/sap/bc/adt/core/discovery" for destination CE1_100_ascent2_en; using default settings

com.sap.adt.communication.exceptions.CommunicationException: timeout occured; Destination data=CE1_100_ascent2_en [client=100, language=EN, systemConfiguration=Name={null} | Host=10.160.3.111 | Origin=null | SystemId=CE1 | Description=null | Group=null | MessageServerService=null | Server=10.160.3.111 | SystemNumber=01 | SNCType=SNC_UNAVAILABLE | Router=/H/ascorpi_013.ascorpi.local/H/109.234.184.194/H/ | PartnerName=null | MessageServer=null | PreferredUser=null | PreferredClient=null | PreferredLanguage=null, user=ASCENT2]

------------ Request -----------------------

GET /sap/bc/adt/core/discovery HTTP/1.1

User-Agent: Eclipse/4.5.0.v20150603-2000 ADT/2.44.3

X-sap-adt-profiling: server-time

    at com.sap.adt.communication.internal.jco.dispatcher.JCoRequestDispatcher.handleJcoException(JCoRequestDispatcher.java:233)

    at com.sap.adt.communication.internal.jco.dispatcher.JCoRequestDispatcher.dispatch(JCoRequestDispatcher.java:166)

    at com.sap.adt.communication.internal.session.SystemSession.sendRequest(SystemSession.java:168)

    at com.sap.adt.communication.internal.resources.RestResource.invoke(RestResource.java:162)

    at com.sap.adt.communication.internal.resources.RestResource.get(RestResource.java:67)

    at com.sap.adt.compatibility.internal.discovery.Discovery.createInstance(Discovery.java:84)

    at com.sap.adt.compatibility.internal.discovery.Discovery.access$0(Discovery.java:72)

    at com.sap.adt.compatibility.internal.discovery.Discovery$DiscoveryProxy.verifyDelegate(Discovery.java:166)

    at com.sap.adt.compatibility.internal.discovery.Discovery$DiscoveryProxy.getCollectionMember(Discovery.java:201)

    at com.sap.adt.compatibility.internal.graph.provider.GraphProviderFactory.getGraphProvider(GraphProviderFactory.java:39)

    at com.sap.adt.compatibility.base.internal.graph.provider.GraphAnalyzer.processExtensionPointGraphProviders(GraphAnalyzer.java:275)

    at com.sap.adt.compatibility.base.internal.graph.provider.GraphAnalyzer.isNodeAvailable(GraphAnalyzer.java:172)

    at com.sap.adt.compatibility.base.internal.graph.provider.GraphAnalyzerProxy.isNodeAvailable(GraphAnalyzerProxy.java:124)

    at com.sap.adt.compatibility.base.internal.graph.provider.GraphAnalyzerProxy.verifyIsLoaded(GraphAnalyzerProxy.java:89)

    at com.sap.adt.compatibility.base.internal.graph.provider.GraphAnalyzerProxy.getGraphAnalyzer(GraphAnalyzerProxy.java:58)

    at com.sap.adt.compatibility.base.internal.Activator.getCompatibilityGraphAnalyzer(Activator.java:92)

    at com.sap.adt.compatibility.internal.graph.analyzer.CompatibilityGraphAnalyzer.<init>(CompatibilityGraphAnalyzer.java:21)

    at com.sap.adt.compatibility.internal.graph.analyzer.CompatibilityGraphAnalyzer.<init>(CompatibilityGraphAnalyzer.java:17)

    at com.sap.adt.compatibility.internal.Activator.getCompatibilityGraphAnalyzer(Activator.java:152)

    at com.sap.adt.destinations.internal.logon.AdtLogonService$1.runInternal(AdtLogonService.java:185)

    at com.sap.adt.communication.util.CancelableBlockingJob$BlockingJob.run(CancelableBlockingJob.java:227)

    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

Caused by: com.sap.conn.jco.JCoException: (102) JCO_ERROR_COMMUNICATION: Initialization of repository destination CE1_100_ascent2_en failed: Connect to SAP gateway failed

Connection parameters: TYPE=A DEST=CE1_100_ascent2_en ASHOST=10.160.3.111 SYSNR=01 SAPROUTER=/H/ascorpi_013.ascorpi.local/H/109.234.184.194/H/ PCS=1

LOCATION    CPIC (TCP/IP) on local host with Unicode

ERROR       timeout occured

TIME        Fri Aug 07 17:21:30 2015

RELEASE     721

COMPONENT   NI (network interface)

VERSION     40

RC          -5

MODULE      nibuf.cpp

LINE        4795

DETAIL      NiBufIConnect: route connect

            '/H/ascorpi_013.ascorpi.local/H/109.234.184.194/H/10.160.3.111

            ' timeout

COUNTER     2

    at com.sap.conn.jco.rt.RfcDestination.getSystemID(RfcDestination.java:1031)

    at com.sap.conn.jco.rt.RepositoryManager.getRepository(RepositoryManager.java:29)

    at com.sap.conn.jco.rt.RfcDestination.initRepository(RfcDestination.java:982)

    at com.sap.conn.jco.rt.RfcDestination.getRepository(RfcDestination.java:1094)

    at com.sap.conn.jco.rt.RfcDestination.getRepository(RfcDestination.java:34)

    at com.sap.adt.communication.internal.jco.util.JCoFunctionBuilder.createFunctionBuilder(JCoFunctionBuilder.java:58)

    at com.sap.adt.communication.internal.jco.dispatcher.JCoRequestDispatcherRestProtocolStrategy.createFunctionBuilder(JCoRequestDispatcherRestProtocolStrategy.java:138)

    at com.sap.adt.communication.internal.jco.dispatcher.JCoRequestDispatcherRestProtocolStrategy.createRequestFunction(JCoRequestDispatcherRestProtocolStrategy.java:93)

    at com.sap.adt.communication.internal.jco.dispatcher.JCoFunctionExecutor$1.createServiceRequest(JCoFunctionExecutor.java:217)

    at com.sap.adt.communication.internal.jco.dispatcher.JCoFunctionExecutor.runInternal(JCoFunctionExecutor.java:112)

    ... 2 more

Caused by: com.sap.conn.jco.JCoException: (102) JCO_ERROR_COMMUNICATION: Connect to SAP gateway failed

Connection parameters: TYPE=A DEST=CE1_100_ascent2_en ASHOST=10.160.3.111 SYSNR=01 SAPROUTER=/H/ascorpi_013.ascorpi.local/H/109.234.184.194/H/ PCS=1

LOCATION    CPIC (TCP/IP) on local host with Unicode

ERROR       timeout occured

TIME        Fri Aug 07 17:21:30 2015

RELEASE     721

COMPONENT   NI (network interface)

VERSION     40

RC          -5

MODULE      nibuf.cpp

LINE        4795

DETAIL      NiBufIConnect: route connect

            '/H/ascorpi_013.ascorpi.local/H/109.234.184.194/H/10.160.3.111

            ' timeout

COUNTER     2

    at com.sap.conn.jco.rt.MiddlewareJavaRfc.generateJCoException(MiddlewareJavaRfc.java:593)

    at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcClient.connect(MiddlewareJavaRfc.java:1323)

    at com.sap.conn.jco.rt.ClientConnection.connect(ClientConnection.java:720)

    at com.sap.conn.jco.rt.RepositoryConnection.connect(RepositoryConnection.java:53)

    at com.sap.conn.jco.rt.PoolingFactory.init(PoolingFactory.java:117)

    at com.sap.conn.jco.rt.ConnectionManager.createFactory(ConnectionManager.java:352)

    at com.sap.conn.jco.rt.DefaultConnectionManager.createFactory(DefaultConnectionManager.java:46)

    at com.sap.conn.jco.rt.ConnectionManager.getFactory(ConnectionManager.java:326)

    at com.sap.conn.jco.rt.RfcDestination.getSystemID(RfcDestination.java:1026)

    ... 11 more

Caused by: RfcException:

    message: Connect to SAP gateway failed

Connection parameters: TYPE=A DEST=CE1_100_ascent2_en ASHOST=10.160.3.111 SYSNR=01 SAPROUTER=/H/ascorpi_013.ascorpi.local/H/109.234.184.194/H/ PCS=1

LOCATION    CPIC (TCP/IP) on local host with Unicode

ERROR       timeout occured

TIME        Fri Aug 07 17:21:30 2015

RELEASE     721

COMPONENT   NI (network interface)

VERSION     40

RC          -5

MODULE      nibuf.cpp

LINE        4795

DETAIL      NiBufIConnect: route connect

            '/H/ascorpi_013.ascorpi.local/H/109.234.184.194/H/10.160.3.111

            ' timeout

COUNTER     2

    return code: RFC_FAILURE (1)

    error group: 102

    key: RFC_ERROR_COMMUNICATION

    at com.sap.conn.rfc.engine.RfcIoControl.error_end(RfcIoControl.java:248)

    at com.sap.conn.rfc.engine.RfcIoControl.ab_rfcopen(RfcIoControl.java:98)

    at com.sap.conn.rfc.api.RfcApi.RfcOpen(RfcApi.java:87)

    at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcClient.connect(MiddlewareJavaRfc.java:1287)

    ... 18 more

When I try to log in via SAP GUI it works fine. Someone experienced similar issues?

Best regards

Tobias

1 ACCEPTED SOLUTION

Go to solution
former_member204167
Participant

‎08-11-2015 2:19 PM

0 Kudos

Hi Guys,

the issue is solved. For any reason eclipse seems to work with an older version of the saplogon.ini. The file used had a wrong sap router string for the server I wanted to use. When I added the server manually in eclipse using the correct router string everything worked fine. Does anyone know how eclipse determines the server list when adding a new ABAP project? Which saplogon.ini file is used? Where is it located?

Best regards

Tobias

6 REPLIES 6

Go to solution
schneidermic0
Advisor
Advisor

‎08-07-2015 4:46 PM

0 Kudos

Hi Tobias,

I guess you already checked the version of software component SAP_BASIS in the system, right? I get a similar info message when I connect to a system that does not support ADT.

Kind regards,
Michael

Go to solution
schneidermic0
Advisor
Advisor
In response to schneidermic0

‎08-07-2015 4:49 PM

0 Kudos

Sorry, my reply was just to fast: This seems to be something different:



...


Caused by: com.sap.conn.jco.JCoException: (102) JCO_ERROR_COMMUNICATION: Initialization of repository destination CE1_100_ascent2_en failed: Connect to SAP gateway failed


...

Go to solution
former_member204167
Participant
In response to schneidermic0

‎08-07-2015 4:50 PM

0 Kudos

Hi Michael,

these are the versions:

As far as I know this should not be the problem. My colleague could connect to this system via eclipse two days ago. He is not in the office today so I cannot check if that still works.

Regards

Tobias

Preview file
32 KB

Go to solution
schneidermic0
Advisor
Advisor
In response to schneidermic0

‎08-07-2015 5:01 PM

0 Kudos

You are right, the perquisites wrt server version is fulfilled. As I said, I was a little bit to fast with my reply. Sorry! 😕

Unfortunately, I don't know how this issue could be solved. Maybe one of my colleagues or any other community member has an idea ...

Go to solution
former_member204167
Participant

‎08-11-2015 2:19 PM

0 Kudos

Hi Guys,

the issue is solved. For any reason eclipse seems to work with an older version of the saplogon.ini. The file used had a wrong sap router string for the server I wanted to use. When I added the server manually in eclipse using the correct router string everything worked fine. Does anyone know how eclipse determines the server list when adding a new ABAP project? Which saplogon.ini file is used? Where is it located?

Best regards

Tobias

Go to solution
former_member186216
Active Participant
In response to former_member204167

‎08-12-2015 3:38 PM

0 Kudos

Hi Tobias,

ABAP-in-Eclipse should use the same configuration file as SAPLogon does - that is, saplogon.ini or SAPUILandscape.xml for SAP GUI releases 7.30 or 7.40, respectively.

You can verify which file at which location is actually used by invoking the New Project Wizard with activated trace:

Preferences -> ABAP Development -> Trace Configuration,

check 'Destination Management - com.sap.adt.destinations'

Best regards,

Marco