Skip to Content
avatar image
Former Member

Error Encountered while applying SP7 on WAS 6.40

We have a WAS 6.4 running on ORACLE 9i.

We are applying SP7 (ABAP+JAVA stack) of SAP Web AS Java 6.40

We are encountering the following error during the deployment phase.

04/08/19 19:50:40 - Start updating EAR file...

04/08/19 19:50:40 - start-up mode is lazy

04/08/19 19:50:41 - EAR file updated successfully for 591ms.

04/08/19 19:50:41 - Start updating...

04/08/19 19:50:41 - EAR file uploaded to server for 271ms.

04/08/19 19:51:10 - ERROR: NOT updated. The Deploy Service returned the following error:

For detailed information see the log file of the Deploy Service.

Exception is:

com.sap.engine.services.rmi_p4.P4ConnectionException: Possible problem: no available running server node. Check your running servers.

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

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

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

at com.sap.engine.services.rmi_p4.Connection.run(Connection.java:306)

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

04/08/19 19:51:10 - ***********************************************************

Aug 19, 2004 7:51:10 PM Info: End of log messages of the target system.

Aug 19, 2004 7:51:10 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****

Aug 19, 2004 7:51:10 PM Error: Aborted: development component 'tc/TechSrv/XML_DAS'/'sap.com'/'SAP AG'/'6.3007.00.0000.20040609162547.0000':

Caught exception during application deployment from SAP J2EE Engine's deploy API:

com.sap.engine.deploy.manager.DeployManagerException: ERROR: NOT updated. The Deploy Service returned the following error: com.sap.engine.services.rmi_p4.P4ConnectionException: Possible problem: no available running server node. Check your running servers.

Exception is:

com.sap.engine.services.rmi_p4.P4ConnectionException: Possible problem: no available running server node. Check your running servers.

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

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

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

at com.sap.engine.services.rmi_p4.Connection.run(Connection.java:306)

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

(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).DMEXC)

Aug 19, 2004 7:51:10 PM Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.

Aug 19, 2004 7:51:10 PM Info: -


Deployment was successful -


Aug 19, 2004 7:51:11 PM Info: Summarizing the deployment results:

Aug 19, 2004 7:51:11 PM Error: Admitted: D:\SAP XI Study Material\XI 3.0\Installation\SAP XI Installation Docs\Patches\Stack04\J2EE-RUNT-CD\J2EE-ENG\ONLINE\SAPJTECHS07_0.SCA

Aug 19, 2004 7:51:11 PM Error: Processing error. Return code: 4

Plz reply ASAP.

Thanks in advance.

Regards,

Sai Krishna

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

1 Answer

  • avatar image
    Former Member
    Aug 19, 2004 at 02:53 PM

    Hi,

    Obviously the J2EE server node is not running. If you are on windows, you can check the status via SAPMMC, or windows services, or if unix use telnet.

    If the server node is running, retry the deployment.

    If not running, exit from sapinst, restart your j2ee server, and then restart sapinst to continue the deployment.

    This should resolve the problem.

    Regards,

    Hart

    Add comment
    10|10000 characters needed characters exceeded