Skip to Content
0
Former Member
Feb 24, 2009 at 03:33 PM

Unable to login to IB - again com.sap.engine.services.rmi_p4.P4IOException

50 Views

We have installed a new PI 7.1 system and at he moment I have the problem that I can't login into the IB tools. I found a lot of threads with this problem but I can't find a solution for my specific problem. Have a look at the well known error log:

com.sap.aii.utilxi.misc.api.ReconnectRuntimeException: Cannot connect to server using message server: ms://MYHOST:8100/P4 
	at com.sap.aii.ib.clsif.login.EJBHomeFactory.getInitialContext(EJBHomeFactory.java:668)
	at com.sap.aii.ib.clsif.login.EJBHomeFactory.connect(EJBHomeFactory.java:461)
	at com.sap.aii.ib.clsif.login.EJBHomeFactory.initRemoteFactory(EJBHomeFactory.java:133)
	at com.sap.aii.ib.clsif.login.LoginServiceImpl.login(LoginServiceImpl.java:176)
	at com.sap.aii.ib.clsif.login.LoginServiceImpl.login(LoginServiceImpl.java:121)
	at com.sap.aii.ib.clsif.login.LoginServiceImpl.login(LoginServiceImpl.java:109)
	at com.sap.aii.ib.gui.login.SplashLoginFrame$LoginController.doTrial(SplashLoginFrame.java:960)
	at com.sap.aii.ib.gui.login.SplashLoginFrame$LoginAction$1.run(SplashLoginFrame.java:832)
	at java.awt.event.InvocationEvent.dispatch(Unknown Source)
	at java.awt.EventQueue.dispatchEvent(Unknown Source)
	at com.sap.aii.utilxi.swing.toolkit.Guitilities$EventProcessor.dispatchEvent(Guitilities.java:319)
	at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source)
	at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
	at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
	at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
	at java.awt.EventDispatchThread.run(Unknown Source)
Caused by: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext.
	at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:488)
	at javax.naming.spi.NamingManager.getInitialContext(Unknown Source)
	at javax.naming.InitialContext.getDefaultInitCtx(Unknown Source)
	at javax.naming.InitialContext.init(Unknown Source)
	at javax.naming.InitialContext.<init>(Unknown Source)
	at com.sap.aii.ib.clsif.login.EJBHomeFactory.getInitialContext(EJBHomeFactory.java:653)
	... 15 more
Caused by: com.sap.engine.interfaces.cross.EXTstinationException: cannot establish connection with any of the available instances:
MYHOST.DOMAIN.EXT:50104 Reason: com.sap.engine.services.rmi_p4.P4IOException: Cannot open connection to host: 172.24.205.193 and port: 50104
	at com.sap.engine.interfaces.cross.EXTstination.getNextAvailableBroker(Destination.java:59)
	at com.sap.engine.interfaces.cross.EXTstination.getRemoteBroker(Destination.java:35)
	at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:352)
	... 20 more

As you can see I call the IB via a pure hostname "MYHOST". But in the last step you can see the the FQDN "MYHOST.DOMAIN.EXT"was used. That brings me into trouble because these are different IP's. I can't reach the MYHOST.DOMAIN.EXT IP and that's why I can't login into the IB.

If I add an entry in my local host file for MYHOST.DOMAIN.EXT with the IP address I can reach all works fine but this solution is unacceptable.

The key question is why the IB uses this FQDN. I can't find any setting where this FQDN is used. I have checked the complete exchange profile, the sld and and and u2026. I always find only the pure hostname MYHOST.

Additionally I have to say that we have already a PI 7.1 system (DEV) whre I can use all tools. But this is a migrated system (from 3.0). I have only problems with that new installed empty system.