cancel
Showing results for 
Search instead for 
Did you mean: 

NW 2004s X64 Install issue

Former Member
0 Kudos

Hi I have tried several times to get past this last step of the install which continues to fail. Any help would be appreciated. My J2EE server not runing.

I am trying to install NW 2004s SR2 7.00 X64.

And I used "j2sdk1.4.2_16-x64".

And I did Increased memory size.

Here are some of the log entries:

FROM --- callSdmViaSapinst.log

3:44:32 PM Info: Begin of log messages of the target system:

08/04/25 15:44:15 - ***********************************************************

08/04/25 15:44:16 - Start updating EAR file...

08/04/25 15:44:16 - start-up mode is lazy

08/04/25 15:44:17 - EAR file updated successfully for 735ms.

08/04/25 15:44:17 - Start deploying ...

08/04/25 15:44:19 - EAR file uploaded to server for 1078ms.

08/04/25 15:44:25 - Successfully deployed. Deployment took 5812ms.

08/04/25 15:44:25 - Application : sap.com/irj

08/04/25 15:44:25 -

08/04/25 15:44:25 - irj - WEB

08/04/25 15:44:25 - sap.com/irj monitoring configuration - MONITORING CONFIGURATION

08/04/25 15:44:25 - ***********************************************************

Apr 25, 2008 3:44:32 PM Info: End of log messages of the target system.

Apr 25, 2008 3:44:32 PM Error: ***** Abnormal end of SAP J2EE Engine Deployment (J2EE Application) *****

Apr 25, 2008 3:44:32 PM Error: Aborted: development component 'irj'/'sap.com'/'SAP AG'/'7.0009.20061026160346.0000'/'0', grouped by software component 'EPBC'/'sap.com'/'SAP AG'/'1000.7.00.9.2.20061026162900''/'0':

Error: Caught the following error or exception: "com.sap.engine.services.rmi_p4.P4ConnectionException"

Additional error message is:

Possible problem: no available running server node. Check your running servers.

Apr 25, 2008 3:44:32 PM Info: Starting to save the repository

Apr 25, 2008 3:44:33 PM Info: Finished saving the repository

Apr 25, 2008 3:44:33 PM Info: Starting: Initial deployment: Selected software component 'EPBC'/'sap.com'/'SAP AG'/'1000.7.00.9.2.20061026162900''/'0' will be deployed.

Apr 25, 2008 3:44:33 PM Error: Aborted: software component 'EPBC'/'sap.com'/'SAP AG'/'1000.7.00.9.2.20061026162900''/'0':

Failed deployment of SDAs:

development component 'irj'/'sap.com'/'SAP AG'/'7.0009.20061026160346.0000'/'0' : aborted

Please, look at error logs above for more information!

Apr 25, 2008 3:44:33 PM Info: Starting to save the repository

Apr 25, 2008 3:44:34 PM Info: Finished saving the repository

Apr 25, 2008 3:44:34 PM Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.

Apr 25, 2008 3:44:34 PM Error: -


At least one of the Deployments failed -


Apr 25, 2008 3:44:34 PM Info: Summarizing the deployment results:

Apr 25, 2008 3:44:35 PM Error: Aborted: F:\X64\Javabased copm\J2EE_OSINDEP\UT\EPBC09_2.SCA

Apr 25, 2008 3:44:35 PM Error: Processing error. Return code: 4

Regards,

Reza

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Reza,

Increasing the memory is not always the case. Depending on the amount of physical RAM, JDK release, usage types, # instances of SAP on the same server, # server nodes, you might consider decreasing the max heap size memory settings for the j2ee server. Again, the max heap size (plus max perm size) of all Java server nodes must fit completely into the physical memory along with other processes.

Please refer to the following note.

723909 - Java VM settings for J2EE 6.40/7.0

Regards,

Thomas Pham

Former Member
0 Kudos

Thanks for help. That is working now.

Reza

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi ,

The reason the deployment failed is because the j2ee server process has seem to crash , due to memory issue or somethign else.

Please see the std_server0.out file more details , dev_server0.out

Thanks

Prasanna