J2EE VISUAL ADMINISTRATOR

[Former Member]

Hi experts,

The J2EE Server of our XI 3.0 (WAS 6.40 SP09) is broken down...

We canu00B4t log on visual administrator (5% on the loggin screen), we can see in the trace the following text:

<!LOGHEADER[START]/>

<!HELP[Manual modification of the header may cause parsing problem!]/>

<!LOGGINGVERSION[1.5.3.7162 - 630_SP]/>

<!NAME[C:\usr\sap\SXI\DVEBMGS00\j2ee\admin\log\.\traces\visual_administration.trc]/>

<!PATTERN[visual_administration.trc]/>

<!FORMATTER[com.sap.tc.logging.ListFormatter]/>

<!ENCODING[Cp1252]/>

<!FILESET[0, 5, 10000000]/>

<!PREVIOUSFILE[visual_administration.4.trc]/>

<!NEXTFILE[visual_administration.1.trc]/>

<!LOGHEADER[END]/>

#1.5#C000C0A80A1D00000000000000009F0D00041232902A1F38#1145908283171#com.sap.engine.services.adminadapter.gui.tasks.LoginTask##com.sap.engine.services.adminadapter.gui.tasks.LoginTask#######Thread[Thread-3,5,main]##0#0#Error##Java###Error while trying to login to sap-xi: Cannot open connection on host: 192.168.10.29 and port: 50004

[EXCEPTION]

#1#com.sap.engine.services.security.exceptions.BaseLoginException: Cannot create new RemoteLoginContext. at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:65) at com.sap.engine.services.adminadapter.gui.tasks.LoginTask.connectAction(LoginTask.java:97) at com.sap.engine.services.adminadapter.gui.tasks.LoginTask.run(LoginTask.java:79) at java.lang.Thread.run(Unknown Source) Caused by: com.sap.engine.services.rmi_p4.P4IOException: Cannot open connection on host: 192.168.10.29 and port: 50004 at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:562) at com.sap.engine.services.rmi_p4.ConnectionManager.getConnection(ConnectionManager.java:195) at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.resolveInitialReference(P4ObjectBrokerClientImpl.java:115) at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.resolveInitialReference(P4ObjectBrokerClientImpl.java:84) at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:54) ... 3 more # #1.5#C000C0A80A1D00000000000200009F0D00041232902A1F38#1145908283187#com.sap.engine.services.adminadapter.gui.tasks.LoginTask##com.sap.engine.services.adminadapter.gui.tasks.LoginTask#######Thread[Thread-3,5,main]##0#0#Error#1#/System/Server/VisualAdministrationTool#Plain###Error while trying to login to sap-xi: Cannot open connection on host: 192.168.10.29 and port: 50004# #1.5#C000C0A80A1D00000000000000E33E1800041232912BDBB0#1145908300078#com.sap.engine.services.adminadapter.gui.tasks.LoginTask##com.sap.engine.services.adminadapter.gui.tasks.LoginTask#######Thread[Thread-3,5,main]##0#0#Error##Java###Error while trying to login to sap-xi: Cannot open connection on host: 192.168.10.29 and port: 50004 [EXCEPTION] #1#com.sap.engine.services.security.exceptions.BaseLoginException: Cannot create new RemoteLoginContext.

at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:65)

at com.sap.engine.services.adminadapter.gui.tasks.LoginTask.connectAction(LoginTask.java:97)

at com.sap.engine.services.adminadapter.gui.tasks.LoginTask.run(LoginTask.java:79)

at java.lang.Thread.run(Unknown Source)

Caused by: com.sap.engine.services.rmi_p4.P4IOException: Cannot open connection on host: 192.168.10.29 and port: 50004

at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:562)

at com.sap.engine.services.rmi_p4.ConnectionManager.getConnection(ConnectionManager.java:195)

at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.resolveInitialReference(P4ObjectBrokerClientImpl.java:115)

at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.resolveInitialReference(P4ObjectBrokerClientImpl.java:84)

at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:54)

... 3 more

#

#1.5#C000C0A80A1D00000000000200E33E1800041232912C1648#1145908300093#com.sap.engine.services.adminadapter.gui.tasks.LoginTask##com.sap.engine.services.adminadapter.gui.tasks.LoginTask#######Thread[Thread-3,5,main]##0#0#Error#1#/System/Server/VisualAdministrationTool#Plain###Error while trying to login to sap-xi: Cannot open connection on host: 192.168.10.29 and port: 50004#

Please we are working out of hours, can someone help us??

Another question: How can we enter into the configtool.bat when we execute the file we get another error of type "cannot connect to database"

Thanks in advance.

[Former Member · Accepted solution]

Hi,

what do you mean by broken down? are there any other signs the J2EE is not working (like no access to the Integration Builder) or is it just the connection to the Visual Admin not working?

If it seems to be a general J2EE problem, did you try to restart the J2EE? (Transaction smicm, Menu "Administration --> J2EE Server --> Send Hard Shutdown with Restart")

Regards

Christine

[Former Member · Accepted solution]

Hi all,

Thanks at all for your replies.

We have tried to restart the J2EE (Transaction smicm, Menu "Administration-> J2EE Server-> Send Hard Shutdown with Restart") as Christine has indicated us. It hasn’t worked. We continue with the same problem.

It is not possible to access to Java service (Visual Administrator, SLD,…). There will be a process that does not start inside j2ee engine. However, in MMC it appears started (green colour).

When we try to execute the file “jcmon.xe”, in option menu it is indicated that there isn’t any instance available.

Executing the fie “Jlaunch” appears an error “rc=3”.

Do you have any idea about where is the source of the problem?

Thanks in advance,

Xavier

[Former Member · Accepted solution]

Hi Xavier

Where to execute jcmon.exe

where u have find Jlaunch appear an error rc=3

please tell even i am also facing the same problem our J2EE Engine is also not going up

While opening the Visual Administrator through Default user it shows "Unable to lookup connection Default"

regards

Punit

[Former Member]

Xavier,

Try restarting the J2EE Engine. Maybe there is some authentication problem with your server & there is some corrupt data sitting in the cache. Re-starting sometimes does the trick.

[Former Member]

Hi Xavier,

Your problem seems like authentication issue.

May be the user you are using to connect to visual admin do not have the required roles, or is locked.

You can logon to the abap stack and check this in transaction su01.

If the user is locked unlock it and check that it has J2EE_ADMINISTRATOR roles.

Also check whether the java stack is working properly through this url.

http://<host>:<j2ee http port>/rep/start/index.jsp

http://<host>:<j2ee http port>/index.html.

Regards,

Yomesh