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
Showing results for 
Search instead for 
Did you mean: 

Error when connecting

stefan_schmcker
Explorer
0 Kudos

Good evening,

if you open Eclipse with an existing project w/o a network connection to the corresponding SAP-system you'll get an errormessage stating that it is not possible to logon.  This is just as it should be.

                                    

                      

If your networkconnection comes to life ( like establishing a VPN tunnel ) and you retry to logon via Eclipse you'll get the same errormessage even though the connection should be possible.  Crosschecking via a "real" SAPGUI shows that the corresponding system is alive and kicking.

Hitting Cancel and retrying to logon will not help.  Nor will opening a new window in Eclipse.

The only solution so far is by ending eclipse and restarting.

1 ACCEPTED SOLUTION

former_member186216
Active Participant
0 Kudos

Hello Stefan,

the root cause of this problem is not located in ABAP-in-Eclipse, but in a deeper basis component: the SAP network layer (NI). There, a caching mechanism for host and service names prevents the immediate refresh after the network connection comes to life.

But you have the opportunity to disable the NI cache, see SAP note 1425520. All you have to do in Windows is to set an environment variable: SAP_NI_CACHE_DISABLED=1

This will resolve the error, but it might have some theoretical drawback with regard to performance of the network layer.

Best regards,

Marco

3 REPLIES 3

former_member186216
Active Participant
0 Kudos

Hello Stefan,

the root cause of this problem is not located in ABAP-in-Eclipse, but in a deeper basis component: the SAP network layer (NI). There, a caching mechanism for host and service names prevents the immediate refresh after the network connection comes to life.

But you have the opportunity to disable the NI cache, see SAP note 1425520. All you have to do in Windows is to set an environment variable: SAP_NI_CACHE_DISABLED=1

This will resolve the error, but it might have some theoretical drawback with regard to performance of the network layer.

Best regards,

Marco

0 Kudos

Hello Marco,

this is totally out of my area of experience.  Thank you for proposing the workaround ( that I will not implement since it would mean to do this with every computer I install aie in ).

One question remains though. 

You state that this is no error of ABAP-in-Eclipse.  But since restarting Eclipse solved my problem - wouldn't it be possible to refresh the cache before trying to logon via the logonscreen I posted above?  Or is it that I just got lucky and the times it took Eclipse to restart was when the cache got refreshed somehow?

0 Kudos

Hi Stefan,

restarting Eclipse implies a reset of the communication layers below (JCo & NI), hence the hostname cache is refreshed.

Unfortunately, there is currently no suitable API available to trigger the refresh programmatically from a running ABAP-in-Eclipse.

For the time being the only solution is to set environment variable SAP_NI_CACHE_DISABLED=1.

Best regards,

Marco