SAP NW PI 7.3 EHP1 Installation Error in step Deploy Java components

[former_member276340]

Hello, colleagues, a little help is needed and will be appreciated.

We're installing the SAP NetWeaver PI 7.3 EHP1 on Windows Server 2008 Enterprise / MSSQL2008.

Installation fails at step Deploy Java components.

We've checked the MMC - all system processes of all instances are at the green state.

We've also re-started them and started the SWPM state again.

At sapinst_dev.log file we have the following errors:

.......

EVENT[ BEGIN ]

Action: deployment triggered

Item:

    File: \\PI\saploc\PIA\DVEBMGS00\j2ee\cluster\server0\.\temp\tc~bl~deploy_controller\archives\41\SAPXIAF01_0_SCA1370322737419\DEPLOYARCHIVES\com.sap.aii.proxy.svc.facade.sda

    Status: Admitted

    Version: NEW

    Component info:

        Name: com.sap.aii.proxy.svc.facade

        Vendor: sap.com

        Version: 7.3101.20111107124316.0000

        Location: SAP AG

        Sca:

            Name: SAP_XIAF

            Vendor: sap.com

        Dependencies:

            Name:com.sap.aii.proxy.svc, Vendor:sap.com

EVENT[ END ]

[ Info ] +++ Server is being restarted for offline deploy +++. The currently set engine start timeout is [14,400] seconds.

[ Info ] +++ Wait for server response +++. Deploying offline [0] seconds. Will timeout in [14,400] seconds.

[ LOG EXCEPTION ]  :: Could not establish connection to AS Java on [PI:50004]. Error. Server process is down or disconnected from ICM. Check server process traces and ICM logs for details. Error message: the requested server is not available. Check if the host and port specified are correct and AS Java is up and running.

javax.naming.NamingException: Exception during getInitialContext operation. Cannot establish connection to the remote server. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]

    at com.sap.engine.services.jndi.InitialContextFactoryImpl.handleConnectionPropblem(InitialContextFactoryImpl.java:411)

    at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:333)

    at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)

    at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)

    at javax.naming.InitialContext.init(InitialContext.java:223)

    at javax.naming.InitialContext.<init>(InitialContext.java:197)

    at com.sap.engine.services.dc.api.session.impl.SessionImpl.getContext(SessionImpl.java:215)

    at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.reconnectDeployer(DeployProcessorImpl.java:1983)

    at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.waitResultForOfflineDeploy(DeployProcessorImpl.java:1655)

    at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:932)

    at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:259)

    at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.performOperation(DeployCommand.java:208)

    at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.executeCommand(DeployCommand.java:540)

    at com.sap.engine.services.dc.api.cmd.AbstractCommand.execute(AbstractCommand.java:197)

    at com.sap.engine.services.dc.api.cmd.Runner.execute(Runner.java:37)

    at com.sap.engine.services.dc.api.cmd.Runner.main(Runner.java:61)

Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.

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

    at com.sap.engine.services.jndi.implclient.LoginHelper.clientSideLogin(LoginHelper.java:79)

    at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:314)

    ... 14 more

Caused by: java.io.IOException: Reading reply for initial call failed. Check remote side state

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

    at com.sap.engine.services.rmi_p4.RemoteBroker.resolveInitialReference(RemoteBroker.java:41)

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

    ... 16 more

Caused by: com.sap.engine.services.rmi_p4.P4ConnectionException: Error. Server process is down or disconnected from ICM. Check server process traces and ICM logs for details. Error message: the requested server is not available

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

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

    at com.sap.engine.services.rmi_p4.Parser.newRequest(Parser.java:153)

    at com.sap.engine.services.rmi_p4.ClientConnection.run(ClientConnection.java:425)

    at java.lang.Thread.run(Thread.java:722)

..... (many times)

And after all we have:

[ Error ] Component:AJAX-RUNTIME ( sap.com)

Status:AlreadyDeployed

Description:1. Already deployed component has version:1000.7.31.1.0.20110917183000

ERROR[ BEGIN ]

Component:AJAX-RUNTIME ( sap.com)

Status:AlreadyDeployed

Description:1. Already deployed component has version:1000.7.31.1.0.20110917183000

ERROR[ END ]

[ Error ] Component:BI-WDALV ( sap.com)

Status:AlreadyDeployed

Description:1. Already deployed component has version:1000.7.31.1.0.20110917191400

ERROR[ BEGIN ]

Component:BI-WDALV ( sap.com)

Status:AlreadyDeployed

Description:1. Already deployed component has version:1000.7.31.1.0.20110917191400

ERROR[ END ]

[ Error ] Component:CFG_ZA_CE ( sap.com)

Status:AlreadyDeployed

Description:1. Already deployed component has version:1000.7.31.1.0.20110917182900

ERROR[ BEGIN ]

Component:CFG_ZA_CE ( sap.com)

Status:AlreadyDeployed

Description:1. Already deployed component has version:1000.7.31.1.0.20110917182900

ERROR[ END ]

[ Error ] Component:DI_CLIENTS ( sap.com)

Status:AlreadyDeployed

Description:1. Already deployed component has version:1000.7.31.1.0.20110917183000

......... (many times)

Server is not responding on http at port 50004. At port 50000 we have the following:

Error: Application error occurred during the request processing.

Server is accessible for ping by short name and FQDN.

We lost one day in searching and trying, your help will bust us, thank you.

[Former Member]

Hello,

we have the same problem,

Alexey   can you said us how to solve the problem, please'

many thanks

Antonietta

[Former Member]

Check server process traces and ICM logs for details. Also check port 50004 status with netstat command and status of owner process for this port.

[former_member276340]

Hello, Roman, thank you for your question,

the most suspicious records in ICM file are:

[Thr 5852] Tue Jun 04 08:03:28 2013

[Thr 5852] *** WARNING => P4RecvHandShake: received illegal P4 version: 4745 [p4_plg.c     3218]

[Thr 5852] *** WARNING => P4PlugInReadHandler(id=1/1012): P4RecvHandShake failed: Version error(-4) [p4_plg.c     1262]

and

[Thr 5852] Tue Jun 04 08:11:34 2013

[Thr 5852] JNCMIHttpCallLBListener: node 4021050, service Http is stopped

[Thr 5852] HttpJ2EELbDel: server 4021050 lost protocol HTTP

[Thr 5852] JNCMIHttpMsPutLogon: delete http logon information

[Thr 5852] JNCMIP4CallLBListener: node 4021050, service P4 is stopped

[Thr 5852] JNCMIP4MsPutLogon: reset p4 logon information

[Thr 5852] IcmJSessCommServiceLost: server 4021050 lost protocol P4(active services: 0, lb restricted services 0)

[Thr 5852] *** ERROR => IcmJSessSendMsg: no server with protocol P4 connected [icxxjcom.c   5313]

[Thr 5852] *** WARNING => P4PlugInReadHandler(id=1/1032): P4ProcessRequest failed: Dispatching error(-26) [p4_plg.c     1378]

[Thr 5852] *** WARNING => IcmJSessSendConnClosedMsg: server 0 with protocol P4 not connected [icxxjcom.c   6142]

[Thr 5852] *** WARNING => IcmJSessSendConnClosedMsg: server 4021050 with protocol P4 not connected [icxxjcom.c   6142]

[Thr 5852] Tue Jun 04 08:11:36 2013

[Thr 5852] *** ERROR => IcmJSessSendMsg: no server with protocol P4 connected [icxxjcom.c   5313]

[Thr 5852] *** WARNING => P4PlugInReadHandler(id=1/1575): P4ProcessRequest failed: Dispatching error(-26) [p4_plg.c     1378]

[Thr 5852] *** WARNING => IcmJSessSendConnClosedMsg: server 0 with protocol P4 not connected [icxxjcom.c   6142]

[Thr 5852] Tue Jun 04 08:11:38 2013

[Thr 5852] *** ERROR => IcmJSessSendMsg: no server with protocol P4 connected [icxxjcom.c   5313]

[Thr 5852] *** WARNING => P4PlugInReadHandler(id=1/1576): P4ProcessRequest failed: Dispatching error(-26) [p4_plg.c     1378]

[Thr 5852] *** WARNING => IcmJSessSendConnClosedMsg: server 0 with protocol P4 not connected [icxxjcom.c   6142]

[Thr 5852] JNCMIHttpMsPutLogon: delete http logon information

[Thr 5852] JNCMIP4MsPutLogon: reset p4 logon information

[Thr 5852] JNCMIIIOPMsPutLogon: reset iiop logon information

[Thr 5852] JNCMITelnetMsPutLogon: reset telnet logon information

[Thr 6116] *** ERROR => IcmMsgProcess: IcmRecMsg (rc=-8,nirc=-6) failed for partner: JCONTROL(6), wp_no: 0 [icxxextbnd.c 739]

[Thr 6116] *** ERROR => IcmLoop: Connection to Java Startup Framework broken: rc = -8 [icxxman.c    3978]

[Thr 6116] IcmJsfDetach: detach from Java Startup Framework

[Thr 5852] Tue Jun 04 08:11:40 2013

[Thr 5852] *** ERROR => IcmJSessSendMsg: no server with protocol P4 connected [icxxjcom.c   5313]

[Thr 5852] *** WARNING => P4PlugInReadHandler(id=1/1577): P4ProcessRequest failed: Dispatching error(-26) [p4_plg.c     1378]

[Thr 5852] *** WARNING => IcmJSessSendConnClosedMsg: server 0 with protocol P4 not connected [icxxjcom.c   6142]

[Thr 5852] Tue Jun 04 08:11:42 2013

[Thr 5852] *** ERROR => IcmJSessSendMsg: no server with protocol P4 connected [icxxjcom.c   5313]

[Thr 5852] *** WARNING => P4PlugInReadHandler(id=1/1579): P4ProcessRequest failed: Dispatching error(-26) [p4_plg.c     1378]

[Thr 5852] *** WARNING => IcmJSessSendConnClosedMsg: server 0 with protocol P4 not connected [icxxjcom.c   6142]

Port 50004 is not listed in netstat output.

[Former Member]

Check server process traces.

[Sriram2009]

Hi

Have you disable the Firewall & UAC(User account control setting) in Windows 2008 server? because it may block the port.

[ LOG EXCEPTION ]  :: Could not establish connection to AS Java on [PI:50004]. Error. Server process is down or disconnected from ICM. Check server process traces and ICM logs for details. Error message: the requested server is not available. Check if the host and port specified are correct and AS Java is up and running.

Regards

Ram

[former_member276340]

S Sriram, thank you for your answer.

Firewall and UAC are disabled.

[Sriram2009]

Could you go thru the link and sap notes

Error Msg-

Already deployed component has version:1000.7.31.1.0.20110917182900

ERROR[ END ]

http://wiki.sdn.sap.com/wiki/display/TechTSG/%28JSTTSG%29%28Deploy%29Problems-P43

http://scn.sap.com/thread/3300049

http://scn.sap.com/thread/2080626

Error Msg - com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException

http://wiki.sdn.sap.com/wiki/display/TechTSG/%28JSTTSG%29%28Deploy%29Problems-P20

Please check the  Note 1248926 - AS Java VM Parameters for NetWeaver 7.1+ based products  as wrong setting can be a cause of this issue

Thanks & Regards

Sriram