BW 352 install Java Components
During the install of Java components I get the following error when attempting to start J2EE...SAPINST attempts to start but cannopt because server is not running...here is error log:
BW has been successfully installed and Oracle up and running.....
AP J2EE Engine Version 6.30 PatchLevel 66061.37 is starting...
Loading: LogManager ... 2177 ms.
Loading: PoolManager ... 64 ms.
Loading: ThreadManager ... 129 ms.
Loading: IpVerificationManager ... 19 ms.
Loading: ConnectionsManipulator ... 128 ms.
Loading: ClassLoaderManager ... 37 ms.
Loading: ClusterManager ... My Library Path is: /usr/j2se/jre/lib/sparcv9/server
:/usr/j2se/jre/lib/sparcv9:/usr/j2se/jre/../lib/sparcv9:/usr
/sap/BX1/DVEBMGS00/j2ee/os_libs:/tmp/sapinst_exe.8532.1098309844:/sapmnt/BX1/exe
:/usr/lib:/usr/sap/BX1/DVEBMGS00/j2ee/os_libs:/usr/sap/BX1/D
VEBMGS00/j2ee/os_libs:/usr/sap/BX1/SYS/exe/run:/usr/sap/BX1/SYS/exe/runU
1095 ms.
Loading: PortsManager ... 26 ms.
Loading: LockingManager ... My Library Path is: /usr/j2se/jre/lib/sparcv9/server
:/usr/j2se/jre/lib/sparcv9:/usr/j2se/jre/../lib/sparcv9:/usr
/sap/BX1/DVEBMGS00/j2ee/os_libs:/tmp/sapinst_exe.8532.1098309844:/sapmnt/BX1/exe
:/usr/lib:/usr/sap/BX1/DVEBMGS00/j2ee/os_libs:/usr/sap/BX1/D
VEBMGS00/j2ee/os_libs:/usr/sap/BX1/SYS/exe/run:/usr/sap/BX1/SYS/exe/runU
239 ms.
Loading: ConfigurationManager ... 5708 ms.
Loading: LicensingManager ... 158 ms.
Loading: ServiceManager ...
Loading services:
service security started. (52 ms)
service httptunneling started. (7 ms)
service licensing started. (22 ms)
service webservices started. (131 ms)
service keystore started. (241 ms)
service timeout started. (150 ms)
service memory started. (164 ms)
service sld started. (166 ms)
service jmx_notification started. (113 ms)
service r3startup started. (245 ms)
service shell started. (305 ms)
service telnet started. (76 ms)
service jmx started. (928 ms)
service basicadmin started. (461 ms)
service adminadapter started. (70 ms)
service monitor started. (281 ms)
service p4 started. (3069 ms)
service classload started. (5 ms)
service log_configurator started. (3536 ms)
service configuration started. (13 ms)
service jms_provider started. (397 ms)
service http started. (441 ms)
service tc.monitoring.logviewer started. (1141 ms)
ServiceManager started for 6169 ms.
Framework started for 15978 ms.
SAP J2EE Engine Version 6.30 PatchLevel 66061.37 is running!
PatchLevel 66061.37 January 11, 2004 21:06 GMT
>Decrease threads to 90
Decrease threads to 80
Decrease threads to 70
Decrease threads to 60
Stoping services
service tc.monitoring.logviewer stopped. (0 ms)
service classload stopped. (3 ms)
service p4 stopped. (103 ms)
service keystore stopped. (1 ms)
service adminadapter stopped. (1 ms)
service monitor stopped. (104 ms)
service security stopped. (0 ms)
service basicadmin stopped. (20 ms)
service jmx stopped. (0 ms)
service webservices stopped. (46 ms)
service sld stopped. (48 ms)
service telnet stopped. (1062 ms)
service http stopped. (1057 ms)
service timeout stopped. (1 ms)
service configuration stopped. (1 ms)
service jms_provider stopped. (1104 ms)
service log_configurator stopped. (1 ms)
service memory stopped. (1 ms)
service r3startup stopped. (50 ms)
service licensing stopped. (1 ms)
service httptunneling stopped. (1 ms)
service shell stopped. (55 ms)
service jmx_notification stopped. (49 ms)
Thank John
Hi John,
this log just shows the server going up and then going down again. Everything fine with it. There are no errors in here.
Can youn tell me where you have found that log?
Did you check other logs?
Regards,
Benny
Similar Messages
-
Hi
I have installed java components for ess mss from the master dvd on the PORTAL..thou this is wrong since it needs to be in the WAS. How can I uninstall them. I have tried to use sdm to undeploy them but i do not find the compnents there. I searched for sap.com/essaraddr for example to undeploy it..but it is not listed in the undeployment tab.
Am i going about this the wrong way?
Please assist.
Thank you
NamiraYou do not install on the Portal. Instead, you use SDM to install MSS & ESS. SDM is part of WebAS and it should be OK.
Portal, MSS & ESS are applications running on top of WebAS. SDM is the tool you use for Instllation of applications.
Let me know if my understanding of your question is wrong. -
Problems while installing BW UDI Java Components
To all,
A fellow co-worker of mine was trying to installing the "BW UDI Java Components" in 640 BW 3.5, and the installation crashed and now Java will not restart. I'm coming into this at this point as development wants java working again. We had upgraded the kernel to patch level 17 after the initial install but prior to the UDI installation. I've restarted the system, no luck - java will not restart.
Any suggestions?
Can I re-apply Java kernel patch 17?
Anybody install the UDI Java components? If so, could you give us some advice?
Thanks,
Ken Little
RJ Reynolds Tobacco CompanyPlease refer to SAP Note: 1565352 for its resolution. Its a reported bug
Regards, -
Stack file that is generated does not contain any java components
We are in process of upgrading our ecc6.0 system with ehp4. The enhancement is stuck up in configuration phase for JAVA. Though we have configured Java in solution manager the stack file that is generated does not contain any java components and so the installation is stuck up. Kindly request you to advice us on this issue .
Attached is the 'Trouble Ticket Report', PREPARE_JSPM_QUEUE_CSZ_01.LOG, and SMSDXML_EA4_20100623144541.375.txt
++++
Trouble Ticket Report
Installation of enhancement package 1 for SAP NetWeaver 7.0
SID................: EA4
Hostname...........: wipro
Install directory..: e:/usr/sap/EA4
Upgrade directory..: F:\EHPI\java
Database...........: Oracle
Operating System...: NT
JDK version........: 1.6.0_07 SAP AG
SAPJup version.....: 3.4.29
Source release.....: 700
Target release.....: 700
Start release SP...: $(/J2EE/StandardSystem/SPLevel)
Target release SP..: $(/J2EE/ShadowSystem/SPLevel)
Current usages.....:
ABAP stack present.: true
The execution of PREPARE/INIT/PREPARE_JSPM_QUEUE ended in error.
The stack E:\usr\sap\trans\EPS\SMSDXML_EA4_20100625054857.968.xml contains no components for this system.
More information can be found in the log file F:\EHPI\java\log\PREPARE_JSPM_QUEUE_CSZ_02.LOG.
Use the information provided to trouble-shoot the problem. There might be an OSS note providing a solution to this problem. Search for OSS notes with the following search terms:
com.sap.sdt.j2ee.phases.PhaseTypePrepareJSPMQueue
com.sap.sdt.ucp.phases.PhaseException
The stack E:\usr\sap\trans\EPS\SMSDXML_EA4_20100625054857.968.xml contains no components for this system.
PREPARE_JSPM_QUEUE
INIT
NetWeaver Enhancement Package Installation
SAPJup
Java Enhancement Package Installation
++++++
PREPARE_JSPM_QUEUE_CSZ_01.LOG>>
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[2.0.7.1006]/>
<!NAME[F:\EHPI\java\log\PREPARE_JSPM_QUEUE_CSZ_01.LOG]/>
<!PATTERN[PREPARE_JSPM_QUEUE_CSZ_01.LOG]/>
<!FORMATTER[com.sap.tc.logging.TraceFormatter(%d [%s]: %-100l [%t]: %m)]/>
<!ENCODING[UTF8]/>
<!LOGHEADER[END]/>
Jun 28, 2010 9:21:23 AM [Info]: com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:754) [Thread[main,5,main]]: Phase PREPARE/INIT/PREPARE_JSPM_QUEUE has been started.
Jun 28, 2010 9:21:23 AM [Info]: com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:755) [Thread[main,5,main]]: Phase type is com.sap.sdt.j2ee.phases.PhaseTypePrepareJSPMQueue.
Jun 28, 2010 9:21:23 AM [Info]: com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:409) [Thread[main,5,main]]: Parameter inputFile=EHPComponents.xml
Jun 28, 2010 9:21:23 AM [Info]: com.sap.sdt.j2ee.phases.jspm.JSPMQueuePreparatorFactory.createJSPMQueuePreparator(JSPMQueuePreparatorFactory.java:93) [Thread[main,5,main]]: Creating JSPM SP Stack queue preparator.
Jun 28, 2010 9:21:24 AM [Info]: com.sap.sdt.ucp.dialog.elim.DialogEliminatorContainer.canBeOmitted(DialogEliminatorContainer.java:96) [Thread[main,5,main]]: Dialog eliminator spStackDialogEliminator allows to omit dialog SPStackLocationDialog
Jun 28, 2010 9:21:24 AM [Info]: com.sap.sdt.util.validate.ValidationProcessor.validate(ValidationProcessor.java:97) [Thread[main,5,main]]: Validatable parameter SP/STACK/LOCATION has been validated by validator RequiredFields.
Jun 28, 2010 9:21:24 AM [Info]: com.sap.sdt.util.validate.ValidationProcessor.validate(ValidationProcessor.java:97) [Thread[main,5,main]]: Validatable parameter SP/STACK/LOCATION has been validated by validator SPStackLocationValidator.
Jun 28, 2010 9:21:24 AM [Info]: com.sap.sdt.j2ee.phases.jspm.JSPMSpStackQueuePreparator.createQueue(JSPMSpStackQueuePreparator.java:107) [Thread[main,5,main]]: Using SP Stack E:\usr\sap\trans\EPS\SMSDXML_EA4_20100625054857.968.xml.
Jun 28, 2010 9:21:24 AM [Info]: com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseStackTag(SPXmlParser.java:488) [Thread[main,5,main]]: STACK-SHORT-NAME tag is missing. The CAPTION of the stack will be used as stack name.
Jun 28, 2010 9:21:24 AM [Info]: com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseStackTag(SPXmlParser.java:582) [Thread[main,5,main]]: PRODUCT-PPMS-NAME tag is missing. The CAPTION of the product will be used as product PPMS name.
Jun 28, 2010 9:21:24 AM [Info]: com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseSPXml(SPXmlParser.java:424) [Thread[main,5,main]]: Parsing of stack definition file E:\usr\sap\trans\EPS\SMSDXML_EA4_20100625054857.968.xml has finished.
Jun 28, 2010 9:21:24 AM [Error]: com.sap.sdt.ucp.phases.AbstractPhaseType.doExecute(AbstractPhaseType.java:863) [Thread[main,5,main]]: Exception has occurred during the execution of the phase.
Jun 28, 2010 9:21:24 AM [Error]: com.sap.sdt.j2ee.phases.jspm.JSPMSpStackQueuePreparator.createQueue(JSPMSpStackQueuePreparator.java:136) [Thread[main,5,main]]: The stack E:\usr\sap\trans\EPS\SMSDXML_EA4_20100625054857.968.xml contains no components for this system.
Jun 28, 2010 9:21:24 AM [Info]: com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:906) [Thread[main,5,main]]: Phase PREPARE/INIT/PREPARE_JSPM_QUEUE has been completed.
Jun 28, 2010 9:21:24 AM [Info]: com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:907) [Thread[main,5,main]]: Start time: 2010/06/28 09:21:23.
Jun 28, 2010 9:21:24 AM [Info]: com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:909) [Thread[main,5,main]]: End time: 2010/06/28 09:21:24.
Jun 28, 2010 9:21:24 AM [Info]: com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:910) [Thread[main,5,main]]: Duration: 0:00:00.781.
Jun 28, 2010 9:21:24 AM [Info]: com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:911) [Thread[main,5,main]]: Phase status is error.
++++++++++++++++++++++
[stack xml data: version=1.0]
[SPAM_CVERS]
ST-PI 2005_1_7000006
LSOFE 600 0015
SAP_AP 700 0015
SAP_BASIS 701 0003
SAP_ABA 701 0003
SAP_BW 701 0003
PI_BASIS 701 0003
PLMWUI 700 0002
SAP_APPL 604 0002
EA-APPL 604 0002
SAP_BS_FND 701 0002
EA-IPPE 404 0002
WEBCUIF 700 0002
INSURANCE 604 0002
FI-CA 604 0002
ERECRUIT 604 0002
ECC-DIMP 604 0002
EA-DFPS 604 0002
IS-UT 604 0002
IS-H 604 0003
EA-RETAIL 604 0002
EA-FINSERV 604 0002
IS-OIL 604 0002
IS-PRA 604 0002
IS-M 604 0002
SEM-BW 604 0002
FINBASIS 604 0002
FI-CAX 604 0002
EA-GLTRADE 604 0002
IS-CWM 604 0002
EA-PS 604 0002
IS-PS-CA 604 0002
EA-HR 604 0005
SAP_HR 604 0005
ECC-SE 604 0002
[PRDVERS]
01200314690900000432SAP ERP ENHANCE PACKAGE EHP2 FOR SAP ERP 6.0 sap.com EHP2 FOR SAP ERP 6.0 -00000000000000
01200314690900000463SAP ERP ENHANCE PACKAGE EHP4 FOR SAP ERP 6.0 sap.com EHP4 FOR SAP ERP 6.0 -00000000000000
01200615320900001296 sap.com +00000000000000
01200615320900001469SAP ERP ENHANCE PACKAGE EHP3 FOR SAP ERP 6.0 sap.com EHP3 FOR SAP ERP 6.0 -00000000000000
01200615320900003195EHP4 FOR SAP ERP 6.0_NW701 EHP4 FOR ERP 6.0_NW701 sap.com EHP4 FOR SAP ERP 6.0 / NW7.01 +00000000000000
[SWFEATURE]
1 01200615320900001296SAP ERP 2005 sap.com SAP ERP 6.0: SAP ECC Server
19 01200615320900003195EHP4 FOR SAP ERP 6.0_NW701 EHP4 FOR ERP 6.0_NW701 sap.com EHP4 FOR SAP ERP 6.0 / NW7.01: Discrete Ind. & Mill Products
20 01200615320900003195EHP4 FOR SAP ERP 6.0_NW701 EHP4 FOR ERP 6.0_NW701 sap.com EHP4 FOR SAP ERP 6.0 / NW7.01: Media
21 01200615320900003195EHP4 FOR SAP ERP 6.0_NW701 EHP4 FOR ERP 6.0_NW701 sap.com EHP4 FOR SAP ERP 6.0 / NW7.01: Utilities/Waste&Recycl./Telco
23 01200615320900003195EHP4 FOR SAP ERP 6.0_NW701 EHP4 FOR ERP 6.0_NW701 sap.com EHP4 FOR SAP ERP 6.0 / NW7.01: Leasing/Contract A/R & A/P
24 01200615320900003195EHP4 FOR SAP ERP 6.0_NW701 EHP4 FOR ERP 6.0_NW701 sap.com EHP4 FOR SAP ERP 6.0 / NW7.01: Retail
25 01200615320900003195EHP4 FOR SAP ERP 6.0_NW701 EHP4 FOR ERP 6.0_NW701 sap.com EHP4 FOR SAP ERP 6.0 / NW7.01: Global Trade
26 01200615320900003195EHP4 FOR SAP ERP 6.0_NW701 EHP4 FOR ERP 6.0_NW701 sap.com EHP4 FOR SAP ERP 6.0 / NW7.01: Financial Supply Chain Mgmt
30 01200615320900003195EHP4 FOR SAP ERP 6.0_NW701 EHP4 FOR ERP 6.0_NW701 sap.com EHP4 FOR SAP ERP 6.0 / NW7.01: Central Applications
31 01200615320900003195EHP4 FOR SAP ERP 6.0_NW701 EHP4 FOR ERP 6.0_NW701 sap.com EHP4 FOR SAP ERP 6.0 / NW7.01: Strategic Enterprise Mgmt
33 01200615320900003195EHP4 FOR SAP ERP 6.0_NW701 EHP4 FOR ERP 6.0_NW701 sap.com EHP4 FOR SAP ERP 6.0 / NW7.01: Human Capital Management
37 01200615320900003195EHP4 FOR SAP ERP 6.0_NW701 EHP4 FOR ERP 6.0_NW701 sap.com EHP4 FOR SAP ERP 6.0 / NW7.01: Oil & Gas
38 01200615320900003195EHP4 FOR SAP ERP 6.0_NW701 EHP4 FOR ERP 6.0_NW701 sap.com EHP4 FOR SAP ERP 6.0 / NW7.01: Catch Weight Management
42 01200615320900003195EHP4 FOR SAP ERP 6.0_NW701 EHP4 FOR ERP 6.0_NW701 sap.com EHP4 FOR SAP ERP 6.0 / NW7.01: Public Sector Accounting
43 01200615320900003195EHP4 FOR SAP ERP 6.0_NW701 EHP4 FOR ERP 6.0_NW701 sap.com EHP4 FOR SAP ERP 6.0 / NW7.01: Insurance
44 01200615320900003195EHP4 FOR SAP ERP 6.0_NW701 EHP4 FOR ERP 6.0_NW701 sap.com EHP4 FOR SAP ERP 6.0 / NW7.01: Hospital
45 01200615320900003195EHP4 FOR SAP ERP 6.0_NW701 EHP4 FOR ERP 6.0_NW701 sap.com EHP4 FOR SAP ERP 6.0 / NW7.01: SAP ECC Server VPack successor
46 01200615320900003195EHP4 FOR SAP ERP 6.0_NW701 EHP4 FOR ERP 6.0_NW701 sap.com EHP4 FOR SAP ERP 6.0 / NW7.01: ERecruiting
47 01200615320900003195EHP4 FOR SAP ERP 6.0_NW701 EHP4 FOR ERP 6.0_NW701 sap.com EHP4 FOR SAP ERP 6.0 / NW7.01: Defense & Public Security
48 01200615320900003195EHP4 FOR SAP ERP 6.0_NW701 EHP4 FOR ERP 6.0_NW701 sap.com EHP4 FOR SAP ERP 6.0 / NW7.01: Financial Services
55 01200615320900003195EHP4 FOR SAP ERP 6.0_NW701 EHP4 FOR ERP 6.0_NW701 sap.com EHP4 FOR SAP ERP 6.0 / NW7.01: Oil & Gas with Utilities
56 01200615320900003195EHP4 FOR SAP ERP 6.0_NW701 EHP4 FOR ERP 6.0_NW701 sap.com EHP4 FOR SAP ERP 6.0 / NW7.01: Defense
59 01200615320900003195EHP4 FOR SAP ERP 6.0_NW701 EHP4 FOR ERP 6.0_NW701 sap.com EHP4 FOR SAP ERP 6.0 / NW7.01: PLM Core
69 01200615320900003195EHP4 FOR SAP ERP 6.0_NW701 EHP4 FOR ERP 6.0_NW701 sap.com EHP4 FOR SAP ERP 6.0 / NW7.01: EAM config control
9 01200615320900003195EHP4 FOR SAP ERP 6.0_NW701 EHP4 FOR ERP 6.0_NW701 sap.com EHP4 FOR SAP ERP 6.0 / NW7.01: SAP ESA ECC-SE
++++++++++++++++Though we have configured Java in solution manager the stack file that is generated does not contain any java components
You will probably need to update Solution Manager first with a number of corrections so you can get a correctly generated stack file. Depending on your ST400 version in Solution Manager apply collective corrections from "Note 1461849 - MOpz: Collective corrections 24" or "Note 1452118 - MOpz: Collective Corrections 23". They generally deal with these kind of stack file issues.
Nelis -
Deploy java components error in NW7.4 installation
Hi Experts,
I am installing NW 7.4, i have done all the pre-installation steps but i am getting error at deploy java components.
please find the log. please help me in this it is very urgent. I need your experience.
An error occurred while processing option SAP NetWeaver 7.4 Support Release 2 > MaxDB > SAP Systems > Optional Standalone Units > Process Orchestration > Standard System > Process Integration and Orchestration Package( Last error reported by the step: Execution of Deploy Controller Runner tool '"C:\Program Files\sapinst_instdir\NW740SR2\ADA\INSTALL\STANDALONE\STD\PICP\sapjvm\sapjvm_6\bin\java.exe" -classpath "C:/Program Files/sapinst_instdir/NW740SR2/ADA/INSTALL/STANDALONE/STD/PICP/install/lib;\\PO/sapmnt/POP/SYS/global/security/lib/tools/iaik_jce.jar;\\PO/sapmnt/POP/SYS/global/security/lib/tools/iaik_jsse.jar;\\PO/sapmnt/POP/SYS/global/security/lib/tools/iaik_smime.jar;\\PO/sapmnt/POP/SYS/global/security/lib/tools/iaik_ssl.jar;\\PO/sapmnt/POP/SYS/global/security/lib/tools/w3c_http.jar;D:/usr/sap/POP/J00/j2ee/j2eeclient/sap.com~tc~exception~impl.jar;D:/usr/sap/POP/J00/j2ee/j2eeclient/sap.com~tc~je~clientlib~impl.jar;D:/usr/sap/POP/J00/j2ee/j2eeclient/sap.com~tc~logging~java~impl.jar;C:/Program Files/sapinst_instdir/NW740SR2/ADA/INSTALL/STANDALONE/STD/PICP/install/lib/tc~je~cl_deploy.jar" -Xmx256m -Ddc.api.verbose=false com.sap.engine.services.dc.api.cmd.Runner deploy -l "C:\Program Files\sapinst_instdir\NW740SR2\ADA\INSTALL\STANDALONE\STD\PICP\deploy.lst" -e stop -u lower -w safety --lcm bulk -t 14400000 --host PO --port 50004' aborts with return code 104. Error message is 'Component:BI_UDI ( sap.com) Status:Aborted Description:. SOLUTION: Check 'C:\Program Files\sapinst_instdir\NW740SR2\ADA\INSTALL\STANDALONE\STD\PICP\log\dc_log\deploy_api.0.log' and 'deploycontroller.log' for more information.). You can now:
Choose Retry to repeat the current step.
Choose Log Files to get more information about the error.
Stop the option and continue later.
Log files are written to C:\Program Files/sapinst_instdir/NW740SR2/ADA/INSTALL/STANDALONE/STD/PICP.
Regards,
Patan Thavaheer.Hi manu,
Please find the error log.
[ Error ] Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
[ LOG EXCEPTION ] :: Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. 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:416)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:338)
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:1954)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.waitResultForOfflineDeploy(DeployProcessorImpl.java:1626)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:903)
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:315)
... 14 more
Caused by: com.sap.engine.services.rmi_p4.P4IOException: No alive connection. Check state of the server
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:828)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:813)
at com.sap.engine.services.rmi_p4.ClientConnection.sendRequest(ClientConnection.java:362)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.resolveInitialReference(P4ObjectBrokerClientImpl.java:123)
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
[ Error ] Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
[ Info ] +++ Wait for server response +++. Deploying offline [31] seconds. Will timeout in [14,368] seconds.
[ LOG EXCEPTION ] :: Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. 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:416)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:338)
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:1954)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.waitResultForOfflineDeploy(DeployProcessorImpl.java:1626)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:903)
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:315)
... 14 more
Caused by: com.sap.engine.services.rmi_p4.P4IOException: No alive connection. Check state of the server
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:828)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:813)
at com.sap.engine.services.rmi_p4.ClientConnection.sendRequest(ClientConnection.java:362)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.resolveInitialReference(P4ObjectBrokerClientImpl.java:123)
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
[ Error ] Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
[ LOG EXCEPTION ] :: Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. 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:416)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:338)
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:1954)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.waitResultForOfflineDeploy(DeployProcessorImpl.java:1626)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:903)
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:315)
... 14 more
Caused by: com.sap.engine.services.rmi_p4.P4IOException: No alive connection. Check state of the server
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:828)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:813)
at com.sap.engine.services.rmi_p4.ClientConnection.sendRequest(ClientConnection.java:362)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.resolveInitialReference(P4ObjectBrokerClientImpl.java:123)
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
[ Error ] Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
[ LOG EXCEPTION ] :: Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. 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:416)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:338)
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:1954)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.waitResultForOfflineDeploy(DeployProcessorImpl.java:1626)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:903)
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:315)
... 14 more
Caused by: com.sap.engine.services.rmi_p4.P4IOException: No alive connection. Check state of the server
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:828)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:813)
at com.sap.engine.services.rmi_p4.ClientConnection.sendRequest(ClientConnection.java:362)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.resolveInitialReference(P4ObjectBrokerClientImpl.java:123)
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
[ Error ] Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
[ LOG EXCEPTION ] :: Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. 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:416)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:338)
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:1954)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.waitResultForOfflineDeploy(DeployProcessorImpl.java:1626)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:903)
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:315)
... 14 more
Caused by: com.sap.engine.services.rmi_p4.P4IOException: No alive connection. Check state of the server
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:828)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:813)
at com.sap.engine.services.rmi_p4.ClientConnection.sendRequest(ClientConnection.java:362)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.resolveInitialReference(P4ObjectBrokerClientImpl.java:123)
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
[ Error ] Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
[ LOG EXCEPTION ] :: Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. 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:416)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:338)
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:1954)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.waitResultForOfflineDeploy(DeployProcessorImpl.java:1626)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:903)
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:315)
... 14 more
Caused by: com.sap.engine.services.rmi_p4.P4IOException: No alive connection. Check state of the server
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:828)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:813)
at com.sap.engine.services.rmi_p4.ClientConnection.sendRequest(ClientConnection.java:362)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.resolveInitialReference(P4ObjectBrokerClientImpl.java:123)
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
[ Error ] Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
[ LOG EXCEPTION ] :: Could not establish connection to AS Java on [PO:50004]. End of stream is reached unexpectedly during input from Socket[addr=/192.168.2.87,port=50004,localport=50597]. 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:416)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:338)
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:1954)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.waitResultForOfflineDeploy(DeployProcessorImpl.java:1626)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:903)
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:315)
... 14 more
Caused by: java.io.EOFException: End of stream is reached unexpectedly during input from Socket[addr=/192.168.2.87,port=50004,localport=50597]
at com.sap.engine.services.rmi_p4.ClientConnection.run(ClientConnection.java:501)
at java.lang.Thread.run(Thread.java:763)
[ Error ] Could not establish connection to AS Java on [PO:50004]. End of stream is reached unexpectedly during input from Socket[addr=/192.168.2.87,port=50004,localport=50597]. Check if the host and port specified are correct and AS Java is up and running.
[ LOG EXCEPTION ] :: Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. 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:416)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:338)
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:1954)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.waitResultForOfflineDeploy(DeployProcessorImpl.java:1626)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:903)
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:315)
... 14 more
Caused by: com.sap.engine.services.rmi_p4.P4IOException: No alive connection. Check state of the server
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:828)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:813)
at com.sap.engine.services.rmi_p4.ClientConnection.sendRequest(ClientConnection.java:362)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.resolveInitialReference(P4ObjectBrokerClientImpl.java:123)
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
[ Error ] Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
[ LOG EXCEPTION ] :: Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. 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:416)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:338)
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:1954)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.waitResultForOfflineDeploy(DeployProcessorImpl.java:1626)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:903)
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:315)
... 14 more
Caused by: com.sap.engine.services.rmi_p4.P4IOException: No alive connection. Check state of the server
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:828)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:813)
at com.sap.engine.services.rmi_p4.ClientConnection.sendRequest(ClientConnection.java:362)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.resolveInitialReference(P4ObjectBrokerClientImpl.java:123)
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
[ Error ] Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
[ Info ] +++ Wait for server response +++. Deploying offline [48] seconds. Will timeout in [14,351] seconds.
[ LOG EXCEPTION ] :: Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. 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:416)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:338)
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:1954)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.waitResultForOfflineDeploy(DeployProcessorImpl.java:1626)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:903)
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:315)
... 14 more
Caused by: com.sap.engine.services.rmi_p4.P4IOException: No alive connection. Check state of the server
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:828)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:813)
at com.sap.engine.services.rmi_p4.ClientConnection.sendRequest(ClientConnection.java:362)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.resolveInitialReference(P4ObjectBrokerClientImpl.java:123)
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
[ Error ] Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
[ LOG EXCEPTION ] :: Could not establish connection to AS Java on [PO:50004]. End of stream is reached unexpectedly during input from Socket[addr=/192.168.2.87,port=50004,localport=50615]. 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:416)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:338)
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:1954)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.waitResultForOfflineDeploy(DeployProcessorImpl.java:1626)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:903)
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:315)
... 14 more
Caused by: java.io.EOFException: End of stream is reached unexpectedly during input from Socket[addr=/192.168.2.87,port=50004,localport=50615]
at com.sap.engine.services.rmi_p4.ClientConnection.run(ClientConnection.java:501)
at java.lang.Thread.run(Thread.java:763)
[ Error ] Could not establish connection to AS Java on [PO:50004]. End of stream is reached unexpectedly during input from Socket[addr=/192.168.2.87,port=50004,localport=50615]. Check if the host and port specified are correct and AS Java is up and running.
[ LOG EXCEPTION ] :: Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. 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:416)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:338)
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:1954)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.waitResultForOfflineDeploy(DeployProcessorImpl.java:1626)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:903)
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:315)
... 14 more
Caused by: com.sap.engine.services.rmi_p4.P4IOException: No alive connection. Check state of the server
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:828)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:813)
at com.sap.engine.services.rmi_p4.ClientConnection.sendRequest(ClientConnection.java:362)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.resolveInitialReference(P4ObjectBrokerClientImpl.java:123)
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
[ Error ] Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
[ LOG EXCEPTION ] :: Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. 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:416)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:338)
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:1954)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.waitResultForOfflineDeploy(DeployProcessorImpl.java:1626)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:903)
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:315)
... 14 more
Caused by: com.sap.engine.services.rmi_p4.P4IOException: No alive connection. Check state of the server
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:828)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:813)
at com.sap.engine.services.rmi_p4.ClientConnection.sendRequest(ClientConnection.java:362)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.resolveInitialReference(P4ObjectBrokerClientImpl.java:123)
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
[ Error ] Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
[ Info ] +++ Deployment of session ID [21] finished with status [Error] +++. [[ deployerId=1 ]] [[#3: 340.111 sec]] [
===== Summary - Deploy Result - Start =====
Type | Status : Count
> SCA(s)
- [Aborted] : [80]
> SDA(s)
- [Success] : [80]
- [Admitted] : [1189]
Type | Status : Id
> SCA(s)
- [Aborted] : name: 'BI_UDI', vendor: 'sap.com', name: 'COMP_BUILDT', vendor: 'sap.com', name: 'CU-BASE-JAVA', vendor: 'sap.com', name: 'CU-BASE-WD', vendor: 'sap.com', name: 'DATA-MAPPING', vendor: 'sap.com', name: 'ECM-CORE', vendor: 'sap.com', name: 'ESCONF_BUILDT', vendor: 'sap.com', name: 'ESMP_BUILDT', vendor: 'sap.com', name: 'LM-TOOLS', vendor: 'sap.com', name: 'MMR_SERVER', vendor: 'sap.com', name: 'MOIN_BUILDT', vendor: 'sap.com', name: 'NWTEC', vendor: 'sap.com', name: 'EP-BASIS', vendor: 'sap.com', name: 'SERVICE-COMP', vendor: 'sap.com', name: 'SWLIFECYCL', vendor: 'sap.com', name: 'UKMS_JAVA', vendor: 'sap.com', name: 'KM-KW_JIKS', vendor: 'sap.com', name: 'INTG_VIS', vendor: 'sap.com', name: 'SAP_XIADMIN', vendor: 'sap.com', name: 'SAP_XITOOL', vendor: 'sap.com', name: 'PI-SCP-EXT', vendor: 'sap.com', name: 'PI-SCP-BUILDT', vendor: 'sap.com', name: 'BPEM-CORE', vendor: 'sap.com', name: 'BPEM-FACADE', vendor: 'sap.com', name: 'BPEM-COLLAB', vendor: 'sap.com', name: 'BPEM-BASE', vendor: 'sap.com', name: 'BPEM-BUILDT', vendor: 'sap.com', name: 'BPEM-CONTENT', vendor: 'sap.com', name: 'BPEM-HIM', vendor: 'sap.com', name: 'BPEM-MM', vendor: 'sap.com', name: 'BPEM-MON', vendor: 'sap.com', name: 'BPEM-PP', vendor: 'sap.com', name: 'BPEM-WDUI', vendor: 'sap.com', name: 'BPEM-CUUI', vendor: 'sap.com', name: 'BRMS-BASE', vendor: 'sap.com', name: 'BRMS-BUILDT', vendor: 'sap.com', name: 'BRMS-CORE', vendor: 'sap.com', name: 'BRMS-FACADE', vendor: 'sap.com', name: 'BRMS-WDUI', vendor: 'sap.com', name: 'BRMS-MON', vendor: 'sap.com', name: 'FP-INFRA', vendor: 'sap.com', name: 'CU-BASE-WD-EXT', vendor: 'sap.com', name: 'TM-WLUI', vendor: 'sap.com', name: 'BPEM-ACC', vendor: 'sap.com', name: 'CAF-MF', vendor: 'sap.com', name: 'CAF-UI', vendor: 'sap.com', name: 'COLLAB-ADP', vendor: 'sap.com', name: 'CAF', vendor: 'sap.com', name: 'BI-BASE-S', vendor: 'sap.com', name: 'BI-BASE-B', vendor: 'sap.com', name: 'BI-BASE-E', vendor: 'sap.com', name: 'SEA-CORE', vendor: 'sap.com', name: 'SEA-FACADE', vendor: 'sap.com', name: 'SEA-UI', vendor: 'sap.com', name: 'BI-WDEXT', vendor: 'sap.com', name: 'CU-WD4VC-ADPT', vendor: 'sap.com', name: 'ECM-APPS', vendor: 'sap.com', name: 'ECM-STORE', vendor: 'sap.com', name: 'EP-ADMIN', vendor: 'sap.com', name: 'EP_BUILDT', vendor: 'sap.com', name: 'EP-CONNECTIVITY', vendor: 'sap.com', name: 'EP-MODELING', vendor: 'sap.com', name: 'EP-RUNTIME', vendor: 'sap.com', name: 'UWLJWF', vendor: 'sap.com', name: 'VCFREESTYLEKIT', vendor: 'sap.com', name: 'VCCORERT', vendor: 'sap.com', name: 'VCBASE', vendor: 'sap.com', name: 'VCKITBI', vendor: 'sap.com', name: 'VCFRAMEWORK', vendor: 'sap.com', name: 'VTP_BUILDT', vendor: 'sap.com', name: 'WDEXTENSIONS', vendor: 'sap.com', name: 'WD-FLEX', vendor: 'sap.com', name: 'ECM-ADMIN', vendor: 'sap.com', name: 'ECM-JEE-COMP', vendor: 'sap.com', name: 'SAP_XIESR', vendor: 'sap.com', name: 'SAP_XIGUILIB', vendor: 'sap.com', name: 'XI_CNT_SAP_BASIS', vendor: 'sap.com', name: 'INTG_VIS_DCJ', vendor: 'sap.com', name: 'SAP_XIAF', vendor: 'sap.com', name: 'SOAMON', vendor: 'sap.com',
> SDA(s)
- [Success] : name: 'com.sap.ip.bi.sdk.dac.connector.odbodll', vendor: 'sap.com', name: 'com.sap.glx.mapping.lib', vendor: 'sap.com', name: 'com.sap.glx.common.rt.lib', vendor: 'sap.com', name: 'tc~lm~ctc~confs~service_sda', vendor: 'sap.com', name: 'bi~mmr~dictionary', vendor: 'sap.com', name: 'bi~mmr~deployer', vendor: 'sap.com', name: 'com.sap.portal.pcm.indexingservice', vendor: 'sap.com', name: 'com.sap.netweaver.rtmf.server', vendor: 'sap.com', name: 'tc~rtmf~service', vendor: 'sap.com', name: 'com.sap.aii.sca.xi.svc', vendor: 'sap.com', name: 'com.sap.aii.sca.maas.svc', vendor: 'sap.com', name: 'tc~bpem~eventlog~ddic', vendor: 'sap.com', name: 'com.sap.glx.base.lib', vendor: 'sap.com', name: 'com.sap.glx.container.dbschema', vendor: 'sap.com', name: 'com.sap.glx.rrhandlermanager.svc', vendor: 'sap.com', name: 'com.sap.glx.repository.handler.dbschema', vendor: 'sap.com', name: 'com.sap.glx.core.svc', vendor: 'sap.com', name: 'com.sap.glx.contextcontainer.dbschema', vendor: 'sap.com', name: 'com.sap.glx.core.dbschema', vendor: 'sap.com', name: 'com.sap.glx.core.svc.facade', vendor: 'sap.com', name: 'tc~bpem~index~ddic', vendor: 'sap.com', name: 'tc~bpem~base~svc', vendor: 'sap.com', name: 'com.sap.glx.repository.dbschema', vendor: 'sap.com', name: 'tc~bpem~bl~lib', vendor: 'sap.com', name: 'tc~bpem~base~type~plib', vendor: 'sap.com', name: 'com.sap.glx.repository.ifc', vendor: 'sap.com', name: 'com.sap.glx.repository.svc', vendor: 'sap.com', name: 'tc~bpem~base~lib', vendor: 'sap.com', name: 'tc~bpem~tm~ddic', vendor: 'sap.com', name: 'tc~bpem~shared~lib', vendor: 'sap.com', name: 'tc~brms~engine~lib', vendor: 'sap.com', name: 'tc~brms~ws~svc', vendor: 'sap.com', name: 'tc~brms~repository~svc', vendor: 'sap.com', name: 'tc~brms~io~plib', vendor: 'sap.com', name: 'tc~brms~acl~plib', vendor: 'sap.com', name: 'tc~brms~ddic', vendor: 'sap.com', name: 'tc~brms~wdui~plib', vendor: 'sap.com', name: 'caf~um~relgroups~ddic', vendor: 'sap.com', name: 'tc~esi~sea~schema~ddic', vendor: 'sap.com', name: 'tc~esi~sea~service', vendor: 'sap.com', name: 'tc~esi~sea~api~lib', vendor: 'sap.com', name: 'com.sap.portal.healthChecks', vendor: 'sap.com', name: 'com.sap.portal.fpn.migration.fpnmigrationlib', vendor: 'sap.com', name: 'com.sap.portal.landscape.config', vendor: 'sap.com', name: 'tc~pp~gpal~deploylistener', vendor: 'sap.com', name: 'com.sap.portal.fpn.service', vendor: 'sap.com', name: 'com.sap.portal.smart.smartsrv', vendor: 'sap.com', name: 'com.sap.obn.migration.obnmigrationlib', vendor: 'sap.com', name: 'tc~kmc~bc.uwl~api', vendor: 'sap.com', name: 'devserver_lib', vendor: 'sap.com', name: 'vc_ds_service', vendor: 'sap.com', name: 'vc_generation', vendor: 'sap.com', name: 'ds_repository', vendor: 'sap.com', name: 'ds_environment', vendor: 'sap.com', name: 'visualcomposer_server_api', vendor: 'sap.com', name: 'SAPMetamodelFW', vendor: 'sap.com', name: 'SAPBuildPluginHandler', vendor: 'sap.com', name: 'tc~ecm~svc~deploy', vendor: 'sap.com', name: 'com.sap.aii.adapter.rfc.svc', vendor: 'sap.com', name: 'com.sap.aii.adapter.ispeak.svc', vendor: 'sap.com', name: 'com.sap.aii.af.maas.lib', vendor: 'sap.com', name: 'com.sap.aii.af.ifc.facade', vendor: 'sap.com', name: 'com.sap.aii.adapter.marketplace.lib', vendor: 'sap.com', name: 'com.sap.aii.adapter.jdbc.svc', vendor: 'sap.com', name: 'com.sap.aii.adapter.bc.svc', vendor: 'sap.com', name: 'com.sap.aii.af.int.svc.facade', vendor: 'sap.com', name: 'com.sap.aii.af.svc.facade', vendor: 'sap.com', name: 'com.sap.aii.mapping.lib.facade', vendor: 'sap.com', name: 'com.sap.aii.adapter.file.svc', vendor: 'sap.com', name: 'com.sap.aii.af.lib.facade', vendor: 'sap.com', name: 'com.sap.aii.proxy.svc.facade', vendor: 'sap.com', name: 'com.sap.aii.adapter.marketplace.svc', vendor: 'sap.com', name: 'com.sap.aii.adapter.ispeak.dbs', vendor: 'sap.com', name: 'com.sap.aii.adapter.mail.svc', vendor: 'sap.com', name: 'com.sap.aii.adapter.ws.cxf.lib', vendor: 'sap.com', name: 'com.sap.aii.proxy.svc', vendor: 'sap.com', name: 'com.sap.aii.adapter.xi.svc', vendor: 'sap.com', name: 'com.sap.aii.adapter.http.svc', vendor: 'sap.com', name: 'com.sap.aii.adapter.jms.svc', vendor: 'sap.com', name: 'com.sap.aii.af.axis.lib', vendor: 'sap.com',
- [Admitted] : name: 'com.sap.ip.bi.sdk.monitoring', vendor: 'sap.com', name: 'bi~sdk~resultset', vendor: 'sap.com', name: 'com.sap.ip.bi.sdk.dac.connector.checks', vendor: 'sap.com', name: 'com.sap.ip.bi.sdk.dac.connector.checko', vendor: 'sap.com', name: 'com.sap.ip.bi.sdk.dac.connector.xmla.x', vendor: 'sap.com', name: 'com.sap.ip.bi.sdk.dac.connector.jdbc', vendor: 'sap.com', name: 'tc~bi~sdk', vendor: 'sap.com', name: 'com.sap.ip.bi.sdk', vendor: 'sap.com', name: 'com.sap.ip.bi.sdk.datasource.ds', vendor: 'sap.com', name: 'com.sap.ip.bi.sdk.datasource.fields', vendor: 'sap.com', name: 'com.sap.ip.bi.sdk.dac.connector.java', vendor: 'sap.com', name: 'bi~sdk~core', vendor: 'sap.com', name: 'com.sap.ip.bi.sdk.datasource.sys', vendor: 'sap.com', name: 'bi~sdk~query', vendor: 'sap.com', name: 'com.sap.ip.bi.sdk.datasource.sync', vendor: 'sap.com', name: 'com.sap.ip.bi.sdk.dac.connector.checkj', vendor: 'sap.com', name: 'com.sap.ip.bi.sdk.dac.connector.xmla', vendor: 'sap.com', name: 'com.sap.ip.bi.sdk.dac.connector.checkx', vendor: 'sap.com', name: 'com.sap.ip.bi.sdk.dac.connector.odbo', vendor: 'sap.com', name: 'sc~bi_udi', vendor: 'sap.com', name: 'com.sap.ip.bi.sdk.dac.connector.sapq', vendor: 'sap.com', name: 'sc~comp_buildt', vendor: 'sap.com', name: 'sc~cu-base-java', vendor: 'sap.com', name: 'tc~cu~base~java~ear', vendor: 'sap.com', name: 'tc~cu~base~wd~adapter~wd2wd~ps', vendor: 'sap.com', name: 'tc~cu~base~wd~core', vendor: 'sap.com', name: 'tc~cu~base~wd~adapter~wd2wd', vendor: 'sap.com', name: 'sc~cu-base-wd', vendor: 'sap.com', name: 'tc~cu~base~wd~intapi', vendor: 'sap.com', name: 'tc~cu~base~wd~utils', vendor: 'sap.com', name: 'tc~cu~base~wd~contract~ps', vendor: 'sap.com', name: 'sc~data-mapping', vendor: 'sap.com', name: 'tc~ecm~core', vendor: 'sap.com', name: 'sc~ecm-core', vendor: 'sap.com', name: 'tc~ecm', vendor: 'sap.com', name: 'sc~esconf_buildt', vendor: 'sap.com', name: 'sc~esmp_buildt', vendor: 'sap.com', name: 'tc~archtech~browser~viewer~model', vendor: 'sap.com', name: 'tc~lm~aci~apps~wd~ui~taskplnr', vendor: 'sap.com', name: 'tc~lm~aci~apps~wd~ui~processviewer', vendor: 'sap.com', name: 'tc~lm~itsam~lmr~app', vendor: 'sap.com', name: 'tc~bcf~prov~ddic', vendor: 'sap.com', name: 'tc~lm~ctc~nwa~initialsetuptables', vendor: 'sap.com', name: 'tc~lm~itsam~ui~ctc~wd', vendor: 'sap.com', name: 'tc~lm~aci~apps~wd~ui~master', vendor: 'sap.com', name: 'tc~lm~aci~engine~sapctrl~wsproxy', vendor: 'sap.com', name: 'tc~lm~aci~engine~ddic', vendor: 'sap.com', name: 'tc~slm~ui_maintain', vendor: 'sap.com', name: 'tc~archtech~browser_ume', vendor: 'sap.com', name: 'tc~slm~ui_jnet', vendor: 'sap.com', name: 'tc~lm~ctc~itsam~kpi', vendor: 'sap.com', name: 'tc~archtech~browser~viewer~defaultui', vendor: 'sap.com', name: 'tc~bcf~ws~ddic', vendor: 'sap.com', name: 'tc~lm~aci~vpm~wsproxy~sap', vendor: 'sap.com', name: 'tc~bcf~prov~wd', vendor: 'sap.com', name: 'tc~archtech~browser~viewer~compif', vendor: 'sap.com', name: 'tc~bcf~lib~ear', vendor: 'sap.com', name: 'tc~lm~itsam~ui~sys~overview~xi~wd', vendor: 'sap.com', name: 'tc~lm~aci~virtual~vmware~wsproxy', vendor: 'sap.com', name: 'tc~lm~aci~apps~wd~ui~resource', vendor: 'sap.com', name: 'tc~bcf_xi~ear', vendor: 'sap.com', name: 'tc~archtech~sbook_wd', vendor: 'sap.com', name: 'tc~lm~ctc~nwa~other_ear', vendor: 'sap.com', name: 'tc~lm~aci~apps~wd~ui~aclog', vendor: 'sap.com', name: 'tc~bcf~prov~ear', vendor: 'sap.com', name: 'tc~sec~sanity~jmx~sda', vendor: 'sap.com', name: 'tc~archtech~browser~viewer~locator', vendor: 'sap.com', name: 'tc~slm~ui_review', vendor: 'sap.com', name: 'tc~lm~aci~engine~csm~wsproxy', vendor: 'sap.com', name: 'tc~lm~aci~apps~wd~utils', vendor: 'sap.com', name: 'tc~archtech~browser~viewer~xmlui', vendor: 'sap.com', name: 'tc~lm~ctc~nwa~sldregisterapp', vendor: 'sap.com', name: 'sc~lm-tools', vendor: 'sap.com', name: 'tc~lm~aci~apps~wd~ui~services', vendor: 'sap.com', name: 'tc~lm~aci~apps~wd~ui~vpm', vendor: 'sap.com', name: 'tc~lm~ctc~confs~startup_app', vendor: 'sap.com', name: 'tc~lm~itsam~ui~overview~panel~interface', vendor: 'sap.com', name: 'tc~lm~itsam~ui~avail~panel', vendor: 'sap.com', name: 'tc~bcf~ws~ear', vendor: 'sap.com', name: 'tc~slm~ui_slm', vendor: 'sap.com', name: 'tc~lm~itsam~ui~thresholds~wd', vendor: 'sap.com', name: 'tc~lm~ctc~ccl~rep~hist~ddic', vendor: 'sap.com', name: 'tc~lm~aci~engine~archconfig', vendor: 'sap.com', name: 'tc~lm~itsam~ui~sysinfo', vendor: 'sap.com', name: 'tc~lm~aci~engine~hstctrl~wsproxy', vendor: 'sap.com', name: 'tc~lm~ctc~nwa~spc~config_ear', vendor: 'sap.com', name: 'tc~lm~aci~apps~wd~types', vendor: 'sap.com', name: 'tc~lm~aci~apps~wd~model', vendor: 'sap.com', name: 'tc~lm~aci~apps~wd~ui~overview', vendor: 'sap.com', name: 'tc~slm~ui_navigation', vendor: 'sap.com', name: 'tc~archtech~sbook_init_j2ee', vendor: 'sap.com', name: 'tc~bcf~prov~ddic~content', vendor: 'sap.com', name: 'tc~sld~destsvc_dic', vendor: 'sap.com', name: 'tc~bizc~ws~ear', vendor: 'sap.com', name: 'tc~archtech~browser', vendor: 'sap.com', name: 'tc~archtech~sbook_j2ee', vendor: 'sap.com', name: 'tc~sec~sanity~wd', vendor: 'sap.com', name: 'tc~lm~itsam~ui~nwso~cfg~db', vendor: 'sap.com', name: 'tc~lm~itsam~ui~perf~panel', vendor: 'sap.com', name: 'tc~archtech~browser~dbschema', vendor: 'sap.com', name: 'tc~bcf~transport~ddic', vendor: 'sap.com', name: 'tc~lm~aci~apps~wd~ui~acenable', vendor: 'sap.com', name: 'tc~lm~nzdm~crr~ui', vendor: 'sap.com', name: 'bi~mmr~mini_md_library', vendor: 'sap.com', name: 'bi~mmr~mini_mm_library', vendor: 'sap.com', name: 'bi~mmr~api', vendor: 'sap.com', name: 'bi~mmr~webToolsEAP', vendor: 'sap.com', name: 'bi~mmr~bi_library', vendor: 'sap.com', name: 'bi~mmr~bi_ear', vendor: 'sap.com', name: 'bi~mmr~mmrlib', vendor: 'sap.com', name: 'bi~mmr~reportmodel_library', vendor: 'sap.com', name: 'bi~mmr~cwm_1.0_library', vendor: 'sap.com', name: 'bi~mmr~reportmodel_ear', vendor: 'sap.com', name: 'bi~mmr~jnet', vendor: 'sap.com', name: 'bi~mmr~cwm_1.0_ear', vendor: 'sap.com', name: 'sc~mmr_server', vendor: 'sap.com', name: 'bi~mmr~mmrapplib', vendor: 'sap.com', name: 'bi~mmr~mof_1.4_library', vendor: 'sap.com', name: 'bi~mmr~amlib', vendor: 'sap.com', name: 'bi~mmr~mini_mm_ear', vendor: 'sap.com', name: 'bi~mmr~mini_md_ear', vendor: 'sap.com', name: 'bi~mmr~bi_repository', vendor: 'sap.com', name: 'bi~mmr~metamodel_library', vendor: 'sap.com', name: 'bi~mmr~mof_1.4_ear', vendor: 'sap.com', name: 'bi~mmr~ejb', vendor: 'sap.com', name: 'bi~mmr~metamodel_ear', vendor: 'sap.com', name: 'sc~moin_buildt', vendor: 'sap.com', name: 'sc~nwtec', vendor: 'sap.com', name: 'tc~di~sdic~support~wd', vendor: 'sap.com', name: 'com.sap.portal.supportability.isolde.api', vendor: 'sap.com', name: 'com.sap.portal.pcd.textrepository', vendor: 'sap.com', name: 'com.sap.portal.prt.cache', vendor: 'sap.com', name: 'com.sap.portal.htmlb', vendor: 'sap.com', name: 'tc~jpe~dbschema', vendor: 'sap.com', name: 'com.sap.portal.design.urdesigndataless', vendor: 'sap.com', name: 'com.sap.portal.pcm.admin.pcdimplservice', vendor: 'sap.com', name: 'com.sap.portal.runtime.system.notification', vendor: 'sap.com', name: 'sc~ep-basis', vendor: 'sap.com', name: 'com.sap.portal.runtime.system.clusterinformation', vendor: 'sap.com', name: 'com.sap.portal.runtime.application.contentconverter', vendor: 'sap.com', name: 'tc~epbc~pcd~pars~srvgl', vendor: 'sap.com', name: 'com.sap.portal.pcd.admintools.ucdadmin', vendor: 'sap.com', name: 'com.sap.portal.pcd.aclservice', vendor: 'sap.com', name: 'com.sap.portal.design.ui5designdataless', vendor: 'sap.com', name: 'com.sap.security.ume.consistencycheck', vendor: 'sap.com', name: 'com.sap.portal.pcd.admintools.configuration', vendor: 'sap.com', name: 'com.sap.portal.pcd.umwrapperservice', vendor: 'sap.com', name: 'tc~epbc~prt~apps~restricted', vendor: 'sap.com', name: 'rtmfcommunicator', vendor: 'sap.com', name: 'com.sap.portal.themes.lafservice', vendor: 'sap.com', name: 'tc~epbc~resourcerepository~api', vendor: 'sap.com', name: 'com.sap.portal.usermapping', vendor: 'sap.com', name: 'com.sap.portal.runtime.system.hooks', vendor: 'sap.com', name: 'com.sap.portal.runtime.system.authentication', vendor: 'sap.com', name: 'com.sap.portal.pcd.softcacheservice', vendor: 'sap.com', name: 'com.sap.portal.pcm.metadata.service', vendor: 'sap.com', name: 'tc~epbc~pcm~pcmadminimplsrv', vendor: 'sap.com', name: 'com.sap.portal.design.vc5designdataless', vendor: 'sap.com', name: 'com.sap.portal.pcd.basicrolefactory', vendor: 'sap.com', name: 'tc~supportplatform~wd', vendor: 'sap.com', name: 'com.sap.portal.design.portaldesigndata', vendor: 'sap.com', name: 'com.sap.portal.runtime.system.prtconnection', vendor: 'sap.com', name: 'com.sap.portal.runtime.prtws', vendor: 'sap.com', name: 'com.sap.portal.resourcerepository', vendor: 'sap.com', name: 'com.sap.portal.pcd.lockservice', vendor: 'sap.com', name: 'irj', vendor: 'sap.com', name: 'tc~epbc~prt~apps', vendor: 'sap.com', name: 'com.sap.portal.runtime.application.xsltransform', vendor: 'sap.com', name: 'com.sap.portal.pcd.traceservice', vendor: 'sap.com', name: 'tc~epbc~pcm~ext', vendor: 'sap.com', name: 'com.sap.portal.design.portaldesigndataless', vendor: 'sap.com', name: 'tc~rtmf~wdtestapp', vendor: 'sap.com', name: 'com.sap.portal.pcd.basictransport', vendor: 'sap.com', name: 'com.sap.portal.pcd.glservice', vendor: 'sap.com', name: 'com.sap.portal.runtime.system.idcounters', vendor: 'sap.com', name: 'com.sap.portal.design.urdesigndata', vendor: 'sap.com', name: 'com.sap.portal.usermanagement.admin', vendor: 'sap.com', name: 'tc~epbc~ume~ep5~deprecated', vendor: 'sap.com', name: 'tc~jpe~engine', vendor: 'sap.com', name: 'tc~epbc~pcd~pars~restricted', vendor: 'sap.com', name: 'tc~ep~useragent~api', vendor: 'sap.com', name: 'com.sap.portal.runtime.gwtintegration', vendor: 'sap.com', name: 'tc~bc~jpe~engine~api', vendor: 'sap.com', name: 'com.sap.portal.runtime.system.connection', vendor: 'sap.com', name: 'com.sap.portal.usermanagement', vendor: 'sap.com', name: 'com.sap.portal.pcd.configservice', vendor: 'sap.com', name: 'com.sap.portal.runtime.application.soap', vendor: 'sap.com', name: 'pcm_ext_libSDA', vendor: 'sap.com', name: 'com.sap.portal.runtime.application.document', vendor: 'sap.com', -
Error in Deploying java components - SAP NW CE 7.2 installation on Windows
Hi,
I am installing NW CE 7.2 on a windows machine. I opted for custom installation. I get the below error at "Deploy java components step. Any clue on why is this happening and how to resolve ?
<html> <head> </head> <body> <p> An error occurred while processing option SAP NetWeaver 7.2 Developer Edition > Install > Custom Server Installation( Last error reported by the step :Execution of Deploy Controller Runner tool '"C:\Program Files\sapinst_instdir\NW72\INSTALL\DEVSYSTEM\sapjvm\sapjvm_6\bin\java.exe" -classpath "C:/Program Files/sapinst_instdir/NW72/INSTALL/DEVSYSTEM/install/lib;E:/usr/sap/TR6/SYS/global/security/lib/tools/iaik_jce.jar;E:/usr/sap/TR6/SYS/global/security/lib/tools/iaik_jsse.jar;E:/usr/sap/TR6/SYS/global/security/lib/tools/iaik_smime.jar;E:/usr/sap/TR6/SYS/global/security/lib/tools/iaik_ssl.jar;E:/usr/sap/TR6/SYS/global/security/lib/tools/w3c_http.jar;E:/usr/sap/TR6/J00/j2ee/j2eeclient/sap.comtcexceptionimpl.jar;E:/usr/sap/TR6/J00/j2ee/j2eeclient/sap.comtcjeclientlibimpl.jar;E:/usr/sap/TR6/J00/j2ee/j2eeclient/sap.comtcloggingjavaimpl.jar;C:/Program Files/sapinst_instdir/NW72/INSTALL/DEVSYSTEM/install/lib/tcje~cl_deploy.jar" -Xmx256m -Ddc.api.verbose=false com.sap.engine.services.dc.api.cmd.Runner deploy -l "C:/Program Files/sapinst_instdir/NW72/INSTALL/DEVSYSTEM/deploy.lst" -e stop -u lower -w safety --lcm bulk -t 14400000 --host L-156007555 --port 50004' aborts with return code 104. Error message is <b>'undefinedStatus:AlreadyDeployedDescription: 1. Already deployed component has version:1000.7.20.1.0.20091117001100.</b> SOLUTION: Check 'undefined' and '' for more information.). You can now: </p> <ul> <li> Choose <i>Retry</i> to repeat the current step. </li> <li> Choose <i>View Log</i> to get more information about the error. </li> <li> Stop the option and continue with it later. </li> </ul> <p> Log files are written to C:\Program Files/sapinst_instdir/NW72/INSTALL/DEVSYSTEM. </p> </body></html>
Regards,
RukmaniThe below msg is from sapinst_dev.log
<html> <head> </head> <body> <p> An error occurred while processing option SAP NetWeaver 7.2 Developer Edition > Install > Custom Server Installation( Last error reported by the step :Execution of Deploy Controller Runner tool '"C:\Program Files\sapinst_instdir\NW72\INSTALL\DEVSYSTEM\sapjvm\sapjvm_6\bin\java.exe" -classpath "C:/Program Files/sapinst_instdir/NW72/INSTALL/DEVSYSTEM/install/lib;E:/usr/sap/TR6/SYS/global/security/lib/tools/iaik_jce.jar;E:/usr/sap/TR6/SYS/global/security/lib/tools/iaik_jsse.jar;E:/usr/sap/TR6/SYS/global/security/lib/tools/iaik_smime.jar;E:/usr/sap/TR6/SYS/global/security/lib/tools/iaik_ssl.jar;E:/usr/sap/TR6/SYS/global/security/lib/tools/w3c_http.jar;E:/usr/sap/TR6/J00/j2ee/j2eeclient/sap.comtcexceptionimpl.jar;E:/usr/sap/TR6/J00/j2ee/j2eeclient/sap.comtcjeclientlibimpl.jar;E:/usr/sap/TR6/J00/j2ee/j2eeclient/sap.comtcloggingjavaimpl.jar;C:/Program Files/sapinst_instdir/NW72/INSTALL/DEVSYSTEM/install/lib/tcje~cl_deploy.jar" -Xmx256m -Ddc.api.verbose=false com.sap.engine.services.dc.api.cmd.Runner deploy -l "C:/Program Files/sapinst_instdir/NW72/INSTALL/DEVSYSTEM/deploy.lst" -e stop -u lower -w safety --lcm bulk -t 14400000 --host L-156007555 --port 50004' aborts with return code 104. Error message is <b>'undefinedStatus:AlreadyDeployedDescription: 1. Already deployed component has version:1000.7.20.1.0.20091117001100.</b> SOLUTION: Check 'undefined' and '' for more information.). You can now: </p> <ul> <li> Choose <i>Retry</i> to repeat the current step. </li> <li> Choose <i>View Log</i> to get more information about the error. </li> <li> Stop the option and continue with it later. </li> </ul> <p> Log files are written to C:\Program Files/sapinst_instdir/NW72/INSTALL/DEVSYSTEM. </p> </body></html> -
What are the pros and cons of installing java+abap stack for portal?
Hi all,
1.What are the pros and cons of installing java+abap stack for portal?
2.what effect it does on the ume options to be choosen??
3.for the purpose of integration of r3,bw and crm on portal and crm 4.0 60.2.3 business package which option of stack(java or abap or both)will be good option and which ume option while installation should be choosen?
regards
RajendraHi Rajendra,
The NetWeaver Installation Master Guide offers some good scenarios on the pros and cons:
https://websmp201.sapag.de/~sapidb/011000358700005412792005E.pdf
In a nutshell:
ABAP+JAVA
Pros
- Decrease # of servers required to administer the portal
- Less costly
Cons
- Upgrades could be dependent on ABAP and Java release level
- Additional load on the server due to ABAP stack
- Limited scalability
JAVA and ABAP on separate server
Pros
- Improved performance
- Allows each system to be single-use purpose therefore downtime does not affect other components
- More scalable
Cons
- Adds complexity to landscape
- Additional costs
Regards,
Thomas Pham -
Hi, I have installed CRM 7.0 EHP3 AS ABAP over Windows 2012+SQL 2012 and I want to install AS JAVA CRM 7.0 EHP3
I recenlty upgraded my NW AS JAVA 7.3 to NW AS JAVA 7.4, can I use this NW AS JAVA to implement CRM 7.0 EHP3 AS JAVA Stack?
what package do I need to deploy?So from what I understand you have a NW 7.4 Java system you upgraded from NW 7.3. I am assuming this is standalone Java stack.
you can technically put CRM Java 703 as an add-on to this but it will be tricky. I think the best way to do that will be use Maint optimizer to select appropriate components. run an Maint optimizer transaction and see if it shows up SAP CRM as add-on to this. If it does, you should be able to put in all correct components along with appropriate add-ons.
doing it manually, you will have to pick all relevant CRM java components and still I think it will be tricky to get it working. Honestly I have not done it.
Easiest way to do it of-course will be to install a standalone Java stack system with CRM components to start with but then of-course you will end up with a separate java stack. We did the same and now we have 6 java stack business systems to serve various business add-ons. I would love to consolidate them to fewer but too lazy to put in the efforts.
Do update the message with your findings, it will be interesting to know how it worked. Maybe it encourages me to take the initiative.
hope this helped
regards
Yogesh -
Java components of XI, post installation check
Hey Guys,
I have installed Netweaver 2004s PI along with the Java and ABAP stack, with the ABAP user management pointing to the ABAP stack. I selected the PI option during the installation.
I wanted to know what java components get installed after a successful PI installation. I do not see any particular component related to XI/PI there. I feel the Java Components related to XI have not been installed during my installation. I found this problem during setup step of configuring RFC INTEGRATION_DIRECTORY_HMI. During the test of this HTTP destination the URL gave a 404 resource not found exception.
You can find out the components by using the link
http://<Server>:<Port>/sap/monitoring/ComponentInfo.
The components that are currently installed on my machine are SAP-JEE CAF JLOGVIEW SAP-JEECOR BASETABLES SAP_JTECHF SAP_JTECHS KM-KW_JIKS CORE-TOOLS UMEADMIN JSPM LM-TOOLS ADSSAP BI_MMR BI_UDI CAF-UM .
Is this a common problem during the PI/XI installation.
Please let me know.
Best Wishes
Sumit.Hello,
Please check the folowing SAP Note for the problem during post-instalaltion activity..u have to set time value for that HTTP RFC..
Note 782801 - SAP Exchange Infrastructure 3.0 SR1 Installation
Note 495857 - Tool: Testing HTTP connection for URL
The most important is that u must have same patch level for all the ABAP + JAVA compoenent to work properly.
plz. dont forget to reward the points -
How do you do the java Add-In installation either on NW04 or NW04s when the ABAP stack is on the latest support package level when compared to the support package level on the media you use to install the java Add-in.
Hi Bharath,
For a Java Add-In you would first need to create a new client on the ABAP side
which would be used during the Addin Installation. For more info please see the
guide @
http://service.sap.com/instguides -> Netweaver 04 -> Installation -> Web AS ->
Documentation -> Database -> Web AS.
As for the Patch levels, it will not be an issue as you
can patch the Java components later using SDM.
Regards
Srikishan -
How to Install JAVA on working systems
Hi gurus,
system : Windows 2003 64bit and SQL
on this server i have already installed :
DEV + Java (test/development)
BWD (development for BW NW2004s)
SSM + Java
i would like to install Java for BWD. Which packet should i install. How to start install.
Regards.Hi Markus,
i go through Planing->Technical Infrastructure Guide -> Installable Software Units -> SAP Systems Based on SAP NetWeaver Application Server with Usage Types (Software Units) -> SAP Application Server Java is it correct ?
Next i assume : Installation Guide - SAP NetWeaver 7.0 including EHP 1 correct ?
Media Label : SAP EHP1 FOR SAP NETWEAVER 7.0 Java based Software Components correct ?
I am little confused . Please help.
Regards -
Install Java and JAccelerator on RAC
Hello.
I need to install Java on two node Oracle RAC Database (AIX 10.2.0.5).
Should I install Jaccelerator? It is optional or required component for java?
And if I must install Jaccelerator should I set additional parameters for RAC database?
such as set cluster_Database = false when start catupgrd.sql
or there are another parameters for cluster installation?
Thanks.
Edited by: user13498124 on 21.07.2011 14:16I need to install Java on two node Oracle RAC Database (AIX 10.2.0.5).
Should I install Jaccelerator? It is optional or required component for java?
And if I must install Jaccelerator should I set additional parameters for RAC database?Jaccelerator comes with companion CD. Make sure all the components are valid always.
such as set cluster_Database = false when start catupgrd.sql
or there are another parameters for cluster installation?If you set cluster_database as FALSE then, it considered as non-RAC database only. -
Looking for label SAP:UT:NW04SSR3:*:*:* while installing java comp ECC6 SR3
Hi All,
Looking for label SAP:UT:NW04SSR3:::* while installing java component for ECC6.0 SR3.
I am using the path as 51033526\J2EE_OSINDEP but it is giving an error. Please help to provide the correct path for label.asc.
With Regards,
Lolla.
Edited by: Lolla Venkata Murali Krishna on Feb 17, 2009 2:24 PMHello,
Correct path is only number 51033526 for BS 2005 SR3 Java Components
But this installation I guess need number 51033513 NW 7.0 SR3 SP14 Java based SW Comp.
best regards,
Peter Nechala -
SNC Java Architecture - Where to install Java instance?
Hi...
We are workin on installing SCM - SNC.
What is the common architecture for installing the ABAP and Java components for SCM and SNC? Are the ABAP and Java components normally installed on the same server? From the installation, it seems they should be separatel but I have heard of no customer examples that have this architecture.
If installed seperately, can the Java instance be shared with other SAP customer facing solutions?
Are there any good architecture diagrams that clearly show this? The refridgerator style diagrams don't help.
What is recommended?Tug,
Thanks for your reply.
So I understand that I can install OC4J stand-alone 10.1.3.2 on a SUN computer running Solaris 9, in any directory and as any user.
Correct?
Currently we have it installed in "$ORACLE_BASE/product" and owned by user "oracle".
However, a different user is used to launch it.
My gut instinct is that it should be owned by the user who launches it and it should not be under "$ORACLE_BASE".
I'm just trying to confirm the correctness of my gut instinct.
Because I don't recall reading anything anywhere regarding where OC4J stand-alone 10.1.3.2 should be installed nor who should own it.
Thanks,
Avi. -
Installed Java 2 & jakarta-tomcat, Now VB6 & RDC (Crystal Rpts) App Fails
Help I recently installed java 2 and jakarta-tomcat and suddenly a Visual Basic 6 application that I've had forever won't call it's Crystal Reports (RDC) components correctly. I can't even open the RDC report designers from Visual Basic 6 at design time. I get an "Application Error" and I'm totally kicked out.
Does anyone know where I can find a list of known software conflicts for Java &/or Jakarta-tomcat?
Thanks in Advance,
gvanlaekenHave you tried to re-install Crystal Reports ?
Maybe you are looking for
-
Safari won't open after updating to 6.0.3
Hey, after I had updated my Safari to the latest version (6.0.3), Safari is unable to open itself and shows an instant crash window after clicking on it. I have deleted my extensions already, but that didn't help. I was hoping if someone would be abl
-
Art is mysteriously disappearing or moving to undesirable location when exporting to PDF
I'm on ID CS5 on an iMac, OS 10.6.4 I'm working on a book cover series. I started it last fall in ID CS3, front front covers and spines (for marketing files). Now, with the InDesign multiple page size feature, I thought this would be the perfect proj
-
Hi We are implementing PCA in ECC 6.0 1. Document splitting is not activated 2. A dummy Profit center is created When i post PCA related transactions they get updated in FAGLFLEXT and GLPCT both 1. Is it the standard SAP functioning that the data i
-
Spry Data Sets and IE7 and IE8
Whiile in IE 7 or IE 8, my spry data set is not displaying the data. However, using the Firefox browser, you can see the data within the spry data set. For some reason unbeknownst to me, IE 7 and IE 8 in not allowing the spry data set to display the
-
How to create custom adf tab in oim 11g for self service
Hi all, I want to create a new tab in self service console by using out box code. Any suggestions please Thanking you