- SAP Community
- Products and Technology
- Technology
- Technology Q&A
- AS JAVA Install Problem
- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
AS JAVA Install Problem
- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
on 09-27-2009 5:29 PM
Hello
I am trying to install Netweaver 7.0 EHP1 with SP1. I installed ABAP side without any problems but when I try to install Java side as Distributed install on the same server, I am getting error on phase Install Software Units in Central Instance install phase. I also tried Central System installation but it failed too. This server is newly formatted Windows Server 2003 with SP2 (64 bit edition). I have installed java 1.4.2-18 x64 and SQL Server 2005 with SP3. I am logging to server with domain administrator account and I also added domain administrator into server's local admin group.
I am providing you callSdmViaSapinst log where the error begins at below.
Sep 27, 2009 7:20:32 PM Info: Software type of SDA: J2EE
Sep 27, 2009 7:20:32 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Sep 27, 2009 7:20:32 PM Info: Begin of log messages of the target system:
09/09/27 19:20:32 - ***********************************************************
09/09/27 19:20:32 - Start updating EAR file...
09/09/27 19:20:32 - start-up mode is always
09/09/27 19:20:32 - EAR file updated successfully for 78ms.
09/09/27 19:20:32 - Start deploying ...
09/09/27 19:20:32 - EAR file uploaded to server for 141ms.
09/09/27 19:20:32 - Successfully deployed. Deployment took 172ms.
09/09/27 19:20:32 - Application : sap.com/com.sap.portal.ajax.navigation.servlet
09/09/27 19:20:32 -
09/09/27 19:20:32 - NavigationServlet - WEB
09/09/27 19:20:32 - ***********************************************************
Sep 27, 2009 7:20:32 PM Info: End of log messages of the target system.
Sep 27, 2009 7:20:32 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Sep 27, 2009 7:20:32 PM Warning: Finished with warnings: development component 'com.sap.portal.ajax.navigation.servlet'/'sap.com'/'SAP AG'/'7.0103.20090106140608.0000'/'1', grouped by software component 'EP-PSERV'/'sap.com'/'SAP AG'/'1000.7.01.3.0.20090108071100''/'1':
Caught exception during application startup from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Error occurred while starting application sap.com/com.sap.portal.ajax.navigation.servlet and wait.
Reason: Clusterwide exception: server ID 13582450:com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Application sap.com/com.sap.portal.ajax.navigation.servlet cannot be started. Reason: it has hard reference to resource com.sap.portal.nav.ws.NavigationWSEar with type application, which is not active on the server.
at com.sap.engine.services.deploy.server.ReferenceResolver.processReferenceToApplication(ReferenceResolver.java:597)
at com.sap.engine.services.deploy.server.ReferenceResolver.processMakeReference(ReferenceResolver.java:399)
at com.sap.engine.services.deploy.server.ReferenceResolver.beforeStartingApplication(ReferenceResolver.java:328)
at com.sap.engine.services.deploy.server.application.StartTransaction.beginCommon(StartTransaction.java:162)
at com.sap.engine.services.deploy.server.application.StartTransaction.begin(StartTransaction.java:136)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:342)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:126)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:245)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4712)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4617)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4590)
at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1163)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Caused by: com.sap.engine.services.deploy.container.DeploymentException: <Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='Exception while starting: sap.com/com.sap.portal.nav.ws.NavigationWSEar', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key Exception while starting: sap.com/com.sap.portal.nav.ws.NavigationWSEar
at com.sap.portal.prt.sapj2ee.PortalRuntimeContainer.prepareStart(PortalRuntimeContainer.java:527)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:4366)
at com.sap.engine.services.deploy.server.ReferenceResolver.processReferenceToApplication(ReferenceResolver.java:589)
... 21 more
Caused by: com.sap.engine.services.deploy.container.DeploymentException: <Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='Exception while starting: SAPJ2EE::sap.com/com.sap.portal.ajax.navigation.servlet', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key Exception while starting: SAPJ2EE::sap.com/com.sap.portal.ajax.navigation.servlet
at com.sap.portal.prt.sapj2ee.SAPJ2EEPortalRuntime.getAndStartSAPJ2EEApplicationItem(SAPJ2EEPortalRuntime.java:888)
at com.sap.portal.prt.sapj2ee.PortalRuntimeContainer.prepareStart(PortalRuntimeContainer.java:511)
... 23 more
Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: [ExternalApplicationItem.prepare]: SAPJ2EE::sap.com/com.sap.portal.ajax.navigation.servlet
at com.sapportals.portal.prt.core.broker.ExternalApplicationItem.prepare(ExternalApplicationItem.java:188)
at com.sapportals.portal.prt.core.broker.SAPJ2EEApplicationItem.prepare(SAPJ2EEApplicationItem.java:232)
at com.sapportals.portal.prt.core.broker.SAPJ2EEApplicationItem.start(SAPJ2EEApplicationItem.java:192)
at com.sapportals.portal.prt.service.sapj2ee.Mediator.getAndStartExternalApplication(Mediator.java:132)
at com.sap.portal.prt.sapj2ee.StartPortalApplication.coreRun(StartPortalApplication.java:59)
at com.sap.portal.prt.sapj2ee.SAPJ2EEPortalRuntime.getAndStartSAPJ2EEApplicationItem(SAPJ2EEPortalRuntime.java:884)
... 24 more
Caused by: com.sapportals.portal.prt.core.broker.PortalApplicationNotFoundException: Could not find portal application com.sap.portal.nav.ws.NavigationWSEar
at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:415)
at com.sapportals.portal.prt.core.broker.ExternalApplicationItem.prepare(ExternalApplicationItem.java:180)
... 29 more
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Sep 27, 2009 7:20:33 PM Info: Starting to save the repository
Sep 27, 2009 7:20:33 PM Info: Finished saving the repository
Sep 27, 2009 7:20:33 PM Info: Starting: Initial deployment: Selected development component 'com.sap.portal.cnf.ws.ConfigurationWSEar'/'sap.com'/'SAP AG'/'7.0103.20081208074141.0000'/'1' will be deployed.
Sep 27, 2009 7:20:33 PM Info: SDA to be deployed: D:\usr\sap\MBJ\JC01\SDM\root\origin\sap.com\com.sap.portal.cnf.ws.ConfigurationWSEar\SAP AG\1\7.0103.20081208074141.0000\com.sap.portal.cnf.ws.ConfigurationWSEar.ear
Sep 27, 2009 7:20:33 PM Info: Software type of SDA: J2EE
Sep 27, 2009 7:20:33 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Sep 27, 2009 7:20:38 PM Info: Begin of log messages of the target system:
09/09/27 19:20:33 - ***********************************************************
09/09/27 19:20:33 - Start updating EAR file...
09/09/27 19:20:33 - start-up mode is lazy
09/09/27 19:20:33 - EAR file updated successfully for 47ms.
09/09/27 19:20:33 - Start deploying ...
09/09/27 19:20:33 - EAR file uploaded to server for 47ms.
09/09/27 19:20:37 - Successfully deployed. Deployment took 3985ms.
09/09/27 19:20:37 - Application : sap.com/com.sap.portal.cnf.ws.ConfigurationWSEar
09/09/27 19:20:37 -
09/09/27 19:20:37 - ConfigurationWSBean - EJB
09/09/27 19:20:37 - WEB SERVICE PORTS:
/ConfigurationWS/ConfigurationWSConfig
- WEBSERVICES
09/09/27 19:20:37 - ConfigurationWS/ConfigurationWSConfig - WEB
09/09/27 19:20:37 - ***********************************************************
Sep 27, 2009 7:20:38 PM Info: End of log messages of the target system.
Sep 27, 2009 7:20:38 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Sep 27, 2009 7:20:38 PM Info: Finished successfully: development component 'com.sap.portal.cnf.ws.ConfigurationWSEar'/'sap.com'/'SAP AG'/'7.0103.20081208074141.0000'/'1', grouped by software component 'EP-PSERV'/'sap.com'/'SAP AG'/'1000.7.01.3.0.20090108071100''/'1'
Sep 27, 2009 7:20:38 PM Info: Starting to save the repository
Sep 27, 2009 7:20:38 PM Info: Finished saving the repository
Sep 27, 2009 7:20:38 PM Info: Starting: Initial deployment: Selected development component 'com.sap.portal.coll.app.dispatcher'/'sap.com'/'SAP AG'/'7.0103.20090108065259.0000'/'1' will be deployed.
Sep 27, 2009 7:20:38 PM Info: SDA to be deployed: D:\usr\sap\MBJ\JC01\SDM\root\origin\sap.com\com.sap.portal.coll.app.dispatcher\SAP AG\1\7.0103.20090108065259.0000\com.sap.portal.coll.app.dispatcher.ear
Sep 27, 2009 7:20:38 PM Info: Software type of SDA: J2EE
Sep 27, 2009 7:20:38 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Sep 27, 2009 7:20:38 PM Info: Begin of log messages of the target system:
09/09/27 19:20:38 - ***********************************************************
09/09/27 19:20:38 - Start updating EAR file...
09/09/27 19:20:38 - start-up mode is lazy
09/09/27 19:20:38 - EAR file updated successfully for 47ms.
09/09/27 19:20:38 - Start deploying ...
09/09/27 19:20:38 - EAR file uploaded to server for 110ms.
09/09/27 19:20:38 - ERROR: NOT deployed. 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.P4RuntimeException: Unexpected exception.
Nested exception is:
java.net.SocketException: Connection reset
java.net.SocketException: Connection reset
at java.net.SocketInputStream.read(SocketInputStream.java:168)
at com.sap.engine.services.rmi_p4.Connection.run(Connection.java:395)
at java.lang.Thread.run(Thread.java:534)
;
09/09/27 19:20:38 - ***********************************************************
Sep 27, 2009 7:20:38 PM Info: End of log messages of the target system.
Sep 27, 2009 7:20:38 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Sep 27, 2009 7:20:38 PM Error: Aborted: development component 'com.sap.portal.coll.app.dispatcher'/'sap.com'/'SAP AG'/'7.0103.20090108065259.0000'/'1', grouped by software component 'EP-PSERV'/'sap.com'/'SAP AG'/'1000.7.01.3.0.20090108071100''/'1':
Caught exception during application deployment from SAP J2EE Engine's deploy API:
com.sap.engine.deploy.manager.DeployManagerException: ERROR: NOT deployed. The Deploy Service returned the following error: com.sap.engine.services.rmi_p4.P4RuntimeException: Unexpected exception.
Nested exception is:
java.net.SocketException: Connection reset
Exception is:
com.sap.engine.services.rmi_p4.P4RuntimeException: Unexpected exception.
Nested exception is:
java.net.SocketException: Connection reset
java.net.SocketException: Connection reset
at java.net.SocketInputStream.read(SocketInputStream.java:168)
at com.sap.engine.services.rmi_p4.Connection.run(Connection.java:395)
at java.lang.Thread.run(Thread.java:534)
;
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).DMEXC)
Sep 27, 2009 7:20:38 PM Info: Starting to save the repository
Sep 27, 2009 7:20:39 PM Info: Finished saving the repository
Sep 27, 2009 7:20:39 PM Info: Starting: Initial deployment: Selected software component 'EP-PSERV'/'sap.com'/'SAP AG'/'1000.7.01.3.0.20090108071100''/'1' will be deployed.
Sep 27, 2009 7:20:39 PM Error: Aborted: software component 'EP-PSERV'/'sap.com'/'SAP AG'/'1000.7.01.3.0.20090108071100''/'1':
Failed deployment of SDAs:
development component 'com.sap.portal.coll.app.dispatcher'/'sap.com'/'SAP AG'/'7.0103.20090108065259.0000'/'1' : aborted
Please, look at error logs above for more information!
Sep 27, 2009 7:20:39 PM Info: Starting to save the repository
Sep 27, 2009 7:20:39 PM Info: Finished saving the repository
Sep 27, 2009 7:20:39 PM Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
Sep 27, 2009 7:20:39 PM Error: -
At least one of the Deployments failed -
Sep 27, 2009 7:20:40 PM Info: Summarizing the deployment results:
Sep 27, 2009 7:20:40 PM Info: OK: D:\JAVA\DATA_UNITS\JAVA_J2EE_OSINDEP_UT\EPBC03_0.SCA
Sep 27, 2009 7:20:40 PM Error: Admitted: D:\JAVA\DATA_UNITS\JAVA_J2EE_OSINDEP_UT\EPBC203_0.SCA
Sep 27, 2009 7:20:40 PM Error: Aborted: D:\JAVA\DATA_UNITS\JAVA_J2EE_OSINDEP_UT\EPPSERV03_0.SCA
Sep 27, 2009 7:20:40 PM Error: Admitted: D:\JAVA\DATA_UNITS\JAVA_J2EE_OSINDEP_UT\EPWDC03_0.SCA
Sep 27, 2009 7:20:40 PM Error: Admitted: D:\JAVA\DATA_UNITS\JAVA_J2EE_OSINDEP_UT\UWLJWF03_0.SCA
Sep 27, 2009 7:20:40 PM Error: Admitted: D:\JAVA\DATA_UNITS\JAVA_J2EE_OSINDEP_UT\SAPEU03_0.SCA
Sep 27, 2009 7:20:40 PM Error: Processing error. Return code: 4
Thanks for your time
Edited by: KAAN TURKES on Sep 27, 2009 6:38 PM
- SAP Managed Tags:
- SAP Customer Relationship Management,
- SAP NetWeaver Application Server
Accepted Solutions (0)
Answers (2)
Answers (2)
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
I solved my problem. I reinstalled whole system, used Java SDK 1.4.2_23 x64 instead of 1.4.2_18, added domain administrator to local administrators group and everything went fine. It is weird that I logged in first time with "Administrator" account of domain and I get login errors in sap install logs. After I put "Administrator" into local admin group it went normal.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hello Kaan,
The exception that caused the stop of the deployment is:
Sep 27, 2009 7:20:38 PM Error: Aborted: development component 'com.sap.portal.coll.app.dispatcher'/'sap.com'/'SAP AG'/'7.0103.20090108065259.0000'/'1',
grouped by software component 'EP-PSERV'/'sap.com'/'SAP AG'/'1000.7.01.3.0.20090108071100''/'1':
Caught exception during application deployment from SAP J2EE Engine's deploy API: com.sap.engine.deploy.manager.DeployManagerException:
ERROR: NOT deployed. The Deploy Service returned the following error: com.sap.engine.services.rmi_p4.P4RuntimeException: Unexpected exception.
Nested exception is:
java.net.SocketException: Connection reset
The cause of the problem is the following exception:
java.net.SocketException: Connection reset
It indicates that the connection between the SDM Server and the Deploy Service on the Server node was broken. The most likely reason for that is crash of the server node.
Please check the dev_server0 and the std_server0.out in the work directory for restart/crash at the time of the above error (Sep 27, 2009 7:20:38 PM).
Furthermore check the defaultTrace of the server node and dispatcher node for clues about the error.
The Warning before the exception that I mentioned is not a problem and you could ignore it.
Regards,
Ventsi Tsachev
Technology Development Support (J2EE Engine)
SAP Labs, Palo Alto, Ca (USA)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- IoT - Ultimate Data Cyber Security - with Enterprise Blockchain and SAP BTP 🚀 in Technology Blogs by Members
- Enabling Support for Existing CAP Projects in SAP Build Code in Technology Blogs by Members
- CF Deployment Error: Error getting tenant t0 in Technology Q&A
- SAP SABRIX UPGRADE in Technology Blogs by Members
- how to create destinations on mufti tenancy subscriber account with java cloud sdk in Technology Q&A
| User | Count |
|---|---|
| 85 | |
| 10 | |
| 9 | |
| 9 | |
| 6 | |
| 6 | |
| 6 | |
| 5 | |
| 3 | |
| 3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.