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

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.