KMC Installation
I'm encountering a following errors while installing KM on my portal:
1.
QUERY DID NOT RETURN A RESULT.
QUERY DID NOT RETURN A RESULT. SELECT attribute SDM_HOME;
statement: WHERE DISPLAYNAME = "
2.
Processing error. Return Code: 4
then it asks to look into callSdmViaSapinst log file for details
is there any solution for this problem?
Hi Srikant,
I forgot to say something about the first error you encountered during installation of KM:
QUERY DID NOT RETURN A RESULT.
QUERY DID NOT RETURN A RESULT. SELECT attribute SDM_HOME;
statement: WHERE DISPLAYNAME = "
<b>Solution:</b>
Do not call SAPInst via a preceeding (relative or absolute) path.Navigate to the loacation of SAPInst <SAPINST/<OS-TYPE>/ folder on the DVD or the DVD image> and call SAPInst from there.
Hope I could help.
Martin
Similar Messages
-
EP6.0 and KMC Installation and cf_installation.report errors
Hi,
I am installing EP6.0 on SUSE9 box.
The OS level is as follows:
Linux nadess01 2.6.5-7.191-smp #1 SMP Tue Jun 28 14:58:56 UTC 2005 x86_64 x86_64 x86_64 GNU/Linux
The java version is:
java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 2.2)
IBM J9SE VM (build 2.2, J2RE 1.4.2 IBM J9 2.2 Linux amd64-64 j9xa64142ifx-20051125 (JIT enabled)
J9VM - 20050524_1742_LHdSMr
JIT - r7_level20050518_1803)
After installing the Portal I get the following messages in the cf_installation.report file
A Configuration upload sequence has started at: Sat Jan 21 22:13:17 PST 2006
Number of upgrades to be processed: 3
com.sap.portal.supportability.isolde: non-fatal error(s).
com.sapportals.portal.prt.service.soap: non-fatal error(s).
com.sap.portal.runtime.config.component: non-fatal error(s).
Please check the log file for more details.
The upgrade sequence completed with some non fatal errors.
I can connect to the Portal using the URL and there are no *err files in the following directories
../../WEB-INF/deployment/
../../WEB-INF/deployment/pcd
../../WEB-INF/deployment/pcdContent.
So the question is why am I getting these messages?
After the Portal installation I am trying to install the KMC module. The installation errors
ERROR 2006-01-21 23:32:46
CJS-00320 Portal Deployment Monitor Error: The Portal Configuration Upgrade report file (/usr/sap/NED/JC00/j2ee/cluster/server0/cf_installation.report) does not exist. Contact your local support center.
There is a cf_installation.report.bak file that exists. I removed the .bak extension according to a forum reply. The installation moves on and I get the following messages
WARNING 2006-01-22 00:24:49
Portal Deployment Monitor Warning: Nothing to monitor. No remaining EPT files found.
WARNING 2006-01-22 00:24:49
Portal Deployment Monitor Warning: Nothing to monitor. No remaining PAR files found.
completes succsessfully. BUT there are NO files with
com.sap.ib.bi.*
com.sap.km.*
com.sap.netweaver.*
com.sap.workflow.*
installed in the pcd and pcdContent directories.
I have tried the installation many times but don't know where the problem is.
I connect to the portal but get error messages when try to access the System Configuration -> Content Management.
I would appreciate a resolution to this problem.Hi Javed,
Seems there is some problem with Linux x86_64 systes. Please check SAP Note 874092. It may provide some idea.
Regards,
Siva
P.S: Award points if you find this useful. -
Hi all,
I have installed EP6 SP9 on SAP WebAs640 SR1 Java and Abap engines.When i tried to install KMC i get an error stating that an installation report does not exist.
can any one help ne in this regard.
ERROR 2005-06-17 11:03:39
CJS-00320 Portal Deployment Monitor Error: The Portal Configuration Upgrade report file (D:\usr\sap/EP6/DVEBMGS00/j2ee/cluster/server0/cf_installation.report) does not exist. Contact your local support center.
GopiHi Gopi,
had the same problem. Same error message during installation of KMC. Before I started installation of KMC I had installed SAP Web AS 6.40 SR1 and EP6.
Solution:
To continue installation go to directory D:\usr\sap/EP6/DVEBMGS00/j2ee/cluster/server0/. There should be a file called cf_installation.report.bak. Duplicate that file and rename the copy to cf_installation.report. Afterwards click on retry in the installation dialog. This worked for me.
Hope I could help
Martin -
KMC installation after applying EP patch??
Hi experts
We have a WebAS Java on NW 04 SP 21 with EP on it. Now we have a requirement of installing KMC on it, is it possible to install KMC SP 21 directly?
Has anyone tried this before? I tried looking for an installation document to carry this out but didnt find any. Hence i got the doubt whether this kind of installation is possible or not.
Please let me know your comments.
Regards
SwarnaHello Swarna,
You can do the following. I will strongly recommand that please try this first on your Dev server for the safety point of view.
1) Upgrade your J2EE Engine to Latest SPS (If I am not wrong, now a days latest is 23 or 24).
2) Install EP and KMC SPS also over the J2EE Engine SPS (Please take same SPS for this also as of J2EE (23 or 24)) and this should be simply working fine.
With Regards,
Saurabh -
Error in KMC installation. waiting 1800 seconds at 2nd phase and errors out
Hi,
I am installing KMC and on 2nd phase "Deploy Content Mangement and Collaboration Components " it hangs stating
Portal Configuration upgrade (66 of 69 done.0 with warning Time elapsed
<Number> seconds. waiting....... ".
Note 779699 referred. In the file cf_installation.report there are no
two lines. it has only one line. Please help..
ThanksHi Tony,
you should adjust the timeout parameters and do a redeployment again, in order to fix this problem.
Have you checked the two SAPNotes mentioned in your note (779699): Note: 769859 (About the parameter: PingReplyTimeout)
and Note: 752049 (About the parameter: AdditionalLoadTimeOut)???
You might experience problems seeing the second Note so I paste the important paragraph here:
a) ATTENTION : Duration of configmerge
By starting the engine after deployment a CM configmerge is initiated as part of the upgrade
process.
Depending on the hardware the configmerge may take 15min up to 2h.
Do NOT restart the servlet engine before you're absolutely sure that the config merge has
finished.
Wait till the portal is back on its own.
View the status of the configmerge in the latest config.*.trc file, located in
..usrsap<j2ee instance>clusterserver.
The status of the merge process is also written to the error.log available under:
..usrsap<j2ee instance>clusterservermanagerconsole_logs
Wait for this entry in processing the upgrade 41 out of 41 : "The upload sequence is now
complete, all the upgrades have been performed."
b) ATTENTION : Beware of Timeout definition for SAP J2EE
Be sure that the J2EE engine is not stopped due to a timeout definition during the merge.
This would cause an undefined status of the system. Toavoid this, set parameter
AdditionalLoadTimeout=10800 (in seconds) to an appropiate value for that upgrade
(..usrsapxxj2eej2ee_00 clusterservermanagerssettingsServiceManager.properties).
Additional timeout parameter since J2EE PL 22
This AdditionalLoadTimeout parameter needs also to be set in ServiceManager.properties
for state (..usrsapxxj2eej2ee_00 clusterstatemanagerssettingsServiceManager.properties).
The configtool can also be used for checking and setting these parameters.
If server node is started by the r3startup service of the dispatcher
Set the r3startup to manual and call any "go" directly.
Troubleshooting a timeout
If run already into timeout and stucked on certain stage of config- merge it's usually
sufficient to adjust timeout parameters and choose SDM option 'Redeploy' and do another
deploymenent and subsequent configmerge, normaly this keeps the system in a valid state.
Hope this helps,
Robert -
Hi all
We have installed the portal ep 6 sp 17 without kmc on linux everything is working fine except one iview that is import iview
under system administrator - transport- import
it is giving following error
An exception occurred while processing a request for :
iView : pcd:portal_content/administrator/super_admin/super_admin_role/com.sap.portal.system_administration/com.sap.portal.system_admin_ws/com.sap.portal.transport/com.sap.portal.transport_packages/com.sap.portal.import
Component Name : com.sap.portal.pcd.admintools.import.default
Error occurs during the rendering of jsp component.
Exception id: 11:13_08/06/06_0011_3859550
See the details for the exception ID in the log file
i am giving the details of log file
log file contents
#1.5#0017A43A079A006A0000001500002061000415B1977A0034#1149752401592#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#J2EE_ADMIN#52##sapepdev_DEP_3859550#Guest#608ce500f6b911da99540017a43a079a#Thread[PRT-Async 0,5,PRT-Async]##0#0#Error#1#/System/Server#Java###Exception ID:11:40_08/06/06_0014_3859550
[EXCEPTION]
#1#com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Resource^M
Component : pcd:portal_content/administrator/super_admin/super_admin_role/com.sap.portal.system_administration/com.sap.portal.system_admin_ws/com.sap.portal.transport/com.sap.portal.transport_packages/com.sap.portal.import^M
Component class : com.sapportals.portal.transport.ui.ImportComponent^M
User : J2EE_ADMIN
at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:969)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:444)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:527)
at com.sapportals.portal.prt.core.async.AsyncPortalComponentResponse.include(AsyncPortalComponentResponse.java:682)
at com.sapportals.portal.transport.ui.ImportComponent.doContent(ImportComponent.java:266)
at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.core.async.AsyncPortalComponentResponse.include(AsyncPortalComponentResponse.java:355)
at com.sapportals.portal.prt.core.async.AsyncPortalComponentResponse.include(AsyncPortalComponentResponse.java:310)
at com.sapportals.portal.navigation.workAreaiView.doContent(workAreaiView.java:169)
at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable$1$DoDispatchRequest.run(AsyncIncludeRunnable.java:377)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable.run(AsyncIncludeRunnable.java:390)
at com.sapportals.portal.prt.core.async.ThreadContextRunnable.run(ThreadContextRunnable.java:164)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor..java:729)
at java.lang.Thread.run(Thread.java:595)
Is this error has something to do with KMC installation?
Awaiting your suggestion
RajendraHi all
we haven't installed kMC on ep 6.0 sp17 .
will this be reason for getting error while running import iview ?
export iview and all other iviews are running fine but only this import iview is giving the error when we try to click the link System administratorTransport packagesimport
it is giving following error
An exception occurred while processing a request for :
iView : pcd:portal_content/administrator/super_admin/super_admin_role/com.sap.portal.system_administration/com.sap.portal.system_admin_ws/com.sap.portal.transport/com.sap.portal.transport_packages/com.sap.portal.import
Component Name : com.sap.portal.pcd.admintools.import.default
Error occurs during the rendering of jsp component.
Exception id: 11:13_08/06/06_0011_3859550
See the details for the exception ID in the log file
can any body help?
regards
Rajendra -
Getting the following error when installing KM SP9.
I did not get this error when I installed in DEV and QAS, but getting only in Prod environment.
Any suggestions?
FJS-00003 TypeError: node has no properties (in script InstallationScript_33, line 12683: ???)hi,
Similar kind of error has already been faced by Patrick. See this thread
KMC installation fails
Hope it helps....
Regards,
Ganesh -
Shortest possible upgrade path to EP6.0 SP9
Hello,
I want to install EP6.0 SP9 and KMC6.0 SP9 on WebAS6.40 SP9 (Windows/MS-SQL Server) in the shortest possible way.
I understand that I can go like this:
1. Install WebAS6.40 SP9
2. Install EP6.0 SP3
3. Install KMC6.0 SP3
4. Upgrade to EP6.0 SP9
5. Upgrade to KMC6.0 SP9
Can you guys please confirm whether these are the right installation steps? I remember reading somewhere that we need to follow a different path because of some problems with the KMC installation. Please advise me regarding this.
Thanks and Regards,
SagarSagar,
Also the installation of the SR1 release will put right at SP9
John -
Hello again,
during the installation process i have to provide the SAP System Administrator, his password and the SAP System Domain (Windows Domain). The problem is, when i do so (any yes the data is correct!) i get an error with the message the account doesnt exists! Im pretty much confused right now...
Could it be that i need a user for the installation process with admin rights on the windows domain? The user im currently using has only local admin rights.
regards,
MarkusYes this was indeed the problem. This time i logged on as the SAP System Administrator which is a NT Admin and now it does work....
-
Installation problem with KM collaboration
Dear All,
I am trying to install KM on WEBAS 6.4 patch 9.
I am using master CD to start SAP INSt.. then i specify location for NW Component CD and give user logon details.. it starts installation, but in second step itself. it gives error:
ERROR 2006-02-06 12:41:51
FJS-00003 TypeError: node has no properties (in script InstallationScript_32, line 12683: ???)
Can you please suggets is i am missing something here..
I am attaching detail of log:
INFO 2006-02-06 12:38:56
Copying file C:/Program Files/sapinst_instdir/NW04SR1/CMC/KMC/keydb.xml to: q0w9e9r8t7.1.xml.
INFO 2006-02-06 12:38:56
Copying file C:/Program Files/sapinst_instdir/NW04SR1/CMC/KMC/keydb.xml to: q0w9e9r8t7.1.xml.
INFO 2006-02-06 12:38:56
Creating file C:\Program Files\sapinst_instdir\NW04SR1\CMC\KMC\q0w9e9r8t7.1.xml.
INFO 2006-02-06 12:38:57
Copying file C:/Program Files/sapinst_instdir/NW04SR1/CMC/KMC/keydb.xml to: C:/Program Files/sapinst_instdir/NW04SR1/CMC/KMC/keydb.1.xml.
INFO 2006-02-06 12:38:57
Copying file C:/Program Files/sapinst_instdir/NW04SR1/CMC/KMC/keydb.xml to: C:/Program Files/sapinst_instdir/NW04SR1/CMC/KMC/keydb.1.xml.
INFO 2006-02-06 12:38:57
Creating file C:\Program Files\sapinst_instdir\NW04SR1\CMC\KMC\keydb.1.xml.
INFO 2006-02-06 12:38:58
Installation start: Monday, 06 February 2006, 12:38:56; installation directory: C:\Program Files\sapinst_instdir\NW04SR1\CMC\KMC; product to be installed: SAP NetWeaver '04 Support Release 1> NetWeaver Components Running on Java> Content Management and Collaboration> Content Management and Collaboration Installation
INFO 2006-02-06 12:39:07
Creating file C:\Program Files\sapinst_instdir\NW04SR1\CMC\KMC\java.log.
INFO 2006-02-06 12:39:08
Output of C:\j2sdk1.4.2_08\jre/bin/java '-version' is written to the logfile java.log.
INFO 2006-02-06 12:39:08
Execution of the command "C:\j2sdk1.4.2_08\jre/bin/java '-version'" finished with return code 0. Output: java version "1.4.2_08"Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_08-b03)Java HotSpot(TM) Client VM (build 1.4.2_08-b03, mixed mode)
INFO 2006-02-06 12:39:08
Looking for SAP system instances installed on this host...
INFO 2006-02-06 12:39:10
Found these instances: sid: NWD, number: 01, name: SCS01, host: chn-mumsap02sid: NWD, number: 00, name: DVEBMGS00, host: chn-mumsap02
INFO 2006-02-06 12:39:22
Looking for SAP system instances installed on this host...
INFO 2006-02-06 12:39:24
Found these instances: sid: NWD, number: 01, name: SCS01, host: chn-mumsap02sid: NWD, number: 00, name: DVEBMGS00, host: chn-mumsap02
INFO 2006-02-06 12:39:24
Copying file C:/Program Files/sapinst_instdir/NW04SR1/CMC/KMC/java.log to: C:/Program Files/sapinst_instdir/NW04SR1/CMC/KMC/java.1.log.
INFO 2006-02-06 12:39:24
Copying file C:/Program Files/sapinst_instdir/NW04SR1/CMC/KMC/java.log to: C:/Program Files/sapinst_instdir/NW04SR1/CMC/KMC/java.1.log.
INFO 2006-02-06 12:39:24
Creating file C:\Program Files\sapinst_instdir\NW04SR1\CMC\KMC\java.1.log.
INFO 2006-02-06 12:39:24
Removing file C:\Program Files\sapinst_instdir\NW04SR1\CMC\KMC\java.log.
INFO 2006-02-06 12:39:24
Creating file C:\Program Files\sapinst_instdir\NW04SR1\CMC\KMC\java.log.
INFO 2006-02-06 12:39:24
Working directory changed to G:/Comp/EP-KMC/ANALYZER.
INFO 2006-02-06 12:39:24
Working directory changed to C:\Program Files\sapinst_instdir\NW04SR1\CMC\KMC.
INFO 2006-02-06 12:39:24
Output of C:\j2sdk1.4.2_08\jre/bin/java '-classpath' 'G:/Comp/EP-KMC/ANALYZER/analyzer.jar;E:/usr/sap/NWD/DVEBMG1/j2ee/cluster/server0/bin/ext/SAPXML1/SAPXML~1.JAR' '-Dj2ee.path=E:\usr\sap\NWD\DVEBMGS00\j2ee' '-Dj2ee.userName=j2ee_admin' 'XXXXXX' '-DMainClass=com.sapportals.utilities.analyzer.ui.console.MainConsole' '-DappendRelativePath=E:\usr\sap\NWD\DVEBMGS00\j2ee' 'com.sapportals.utilities.analyzer.ui.Launcher' 'C:\Program Files\sapinst_instdir\NW04SR1\CMC\KMC/analyzerResults.htm' '-e' '/' '-i' 'KMC/Portal Existence' is written to the logfile java.log.
INFO 2006-02-06 12:39:26
Execution of the command "C:\j2sdk1.4.2_08\jre/bin/java '-classpath' 'G:/Comp/EP-KMC/ANALYZER/analyzer.jar;E:/usr/sap/NWD/DVEBMG1/j2ee/cluster/server0/bin/ext/SAPXML1/SAPXML~1.JAR' '-Dj2ee.path=E:\usr\sap\NWD\DVEBMGS00\j2ee' '-Dj2ee.userName=j2ee_admin' 'XXXXXX' '-DMainClass=com.sapportals.utilities.analyzer.ui.console.MainConsole' '-DappendRelativePath=E:\usr\sap\NWD\DVEBMGS00\j2ee' 'com.sapportals.utilities.analyzer.ui.Launcher' 'C:\Program Files\sapinst_instdir\NW04SR1\CMC\KMC/analyzerResults.htm' '-e' '/' '-i' 'KMC/Portal Existence'" finished with return code 0. Output: file:/E:/usr/sap/NWD/DVEBMGS00/j2ee/cluster/server0/bin/services/appclient/appclient.jarfile:/E:/usr/sap/NWD/DVEBMGS00/j2ee/cluster/server0/bin/boot/boot.jarfile:/E:/usr/sap/NWD/DVEBMGS00/j2ee/cluster/server0/bin/system/bytecode.jarfile:/E:/usr/sap/NWD/DVEBMGS00/j2ee/cluster/server0/bin/services/configuration/configuration.jarfile:/E:/usr/sap/NWD/DVEBMGS00/j2ee/cluster/server0/bin/interfaces/cross/cross_api.jarfile:/E:/usr/sap/NWD/DVEBMGS00/j2ee/cluster/server0/bin/services/dbpool/dbpool.jarfile:/E:/usr/sap/NWD/DVEBMGS00/j2ee/cluster/dispatcher/bin/system/exception.jarfile:/E:/usr/sap/NWD/DVEBMGS00/j2ee/cluster/server0/bin/system/frame.jarfile:/E:/usr/sap/NWD/DVEBMGS00/j2ee/cluster/server0/bin/system/iq-lib.jarfile:/E:/usr/sap/NWD/DVEBMGS00/j2ee/cluster/server0/bin/boot/jaas.jarfile:/E:/usr/sap/NWD/DVEBMGS00/j2ee/cluster/server0/bin/interfaces/log/log_api.jarfile:/E:/usr/sap/NWD/DVEBMGS00/j2ee/cluster/server0/bin/system/logging.jarfile:/E:/usr/sap/NWD/DVEBMGS00/j2ee/cluster/server0/bin/services/naming/naming.jarfile:/E:/usr/sap/NWD/DVEBMGS00/j2ee/cluster/server0/bin/services/p4/p4.jarfile:/E:/usr/sap/NWD/DVEBMGS00/j2ee/cluster/server0/bin/ext/sapxmltoolkit/sapxmltoolkit.jarfile:/E:/usr/sap/NWD/DVEBMGS00/j2ee/cluster/server0/bin/services/security/security.jarfile:/E:/usr/sap/NWD/DVEBMGS00/j2ee/cluster/server0/bin/interfaces/security/security_api.jarfile:/E:/usr/sap/NWD/DVEBMGS00/j2ee/cluster/server0/bin/system/util.jarfile:/E:/usr/sap/NWD/DVEBMGS00/j2ee/cluster/server0/bin/services/deploy/deploy.jarfile:/E:/usr/sap/NWD/DVEBMGS00/j2ee/cluster/server0/bin/interfaces/container/container_api.jarfile:/E:/usr/sap/NWD/DVEBMGS00/j2ee/admin/lib/admin.jar
INFO 2006-02-06 12:39:26
Looking for SAP system instances installed on this host...
INFO 2006-02-06 12:39:28
Found these instances: sid: NWD, number: 01, name: SCS01, host: chn-mumsap02sid: NWD, number: 00, name: DVEBMGS00, host: chn-mumsap02
INFO 2006-02-06 12:39:53
RFC parameter CLIENT set to value 000.
INFO 2006-02-06 12:39:53
RFC parameter USER set to value DDIC.
INFO 2006-02-06 12:39:53
RFC parameter LCHECK set to value 1.
INFO 2006-02-06 12:39:53
RFC parameter PCS set to value 1.
INFO 2006-02-06 12:39:53
RFC parameter LANG set to value EN.
INFO 2006-02-06 12:39:53
RFC parameter ASHOST set to value chn-mumsap02.
INFO 2006-02-06 12:39:53
RFC parameter SYSNR set to value 00.
INFO 2006-02-06 12:39:53
RFC connection is logged in file 'rfc#####_#####.trc'.
INFO 2006-02-06 12:39:53
RFC parameter TRACE set to value 1.
INFO 2006-02-06 12:39:53
RFC connection information checked successfully.
INFO 2006-02-06 12:39:53
RFC connection opened successfully.
INFO 2006-02-06 12:39:53
Setting new application function RFC_SYSTEM_INFO.
INFO 2006-02-06 12:39:53
Generating interface for remote function.
INFO 2006-02-06 12:39:53
Function call was successful.
INFO 2006-02-06 12:39:53
Function interface generated successfully.
INFO 2006-02-06 12:39:53
Technical properties of function set successfully.
INFO 2006-02-06 12:39:53
Information for application function RFC_SYSTEM_INFO copied to local Repository.
INFO 2006-02-06 12:39:53
Function module RFC_SYSTEM_INFO set successfully.
INFO 2006-02-06 12:39:53
Executing function call RFC_SYSTEM_INFO.
INFO 2006-02-06 12:39:54
Function call was successful.
INFO 2006-02-06 12:39:54
Version 640 of remote SAP System NWD accepted.
INFO 2006-02-06 12:41:37
Creating file C:\Program Files\sapinst_instdir\NW04SR1\CMC\KMC\summary.html.
PHASE 2006-02-06 12:41:37
Deployment of Basis functionality for Integration Server
INFO 2006-02-06 12:41:38
Creating file C:\Program Files\sapinst_instdir\NW04SR1\CMC\KMC\msclients.exe.log.
INFO 2006-02-06 12:41:38
Working directory changed to C:\Program Files\sapinst_instdir\NW04SR1\CMC\KMC.
INFO 2006-02-06 12:41:38
Output of E:\usr\sap\NWD\SYS\exe\run/msclients.exe '-mshost' 'chn-mumsap02' '-msserv' '3601' is written to the logfile msclients.exe.log.
INFO 2006-02-06 12:41:42
Execution of the command "E:\usr\sap\NWD\SYS\exe\run/msclients.exe '-mshost' 'chn-mumsap02' '-msserv' '3601'" finished with return code 0. Output:
INFO 2006-02-06 12:41:42
Creating file C:\Program Files\sapinst_instdir\NW04SR1\CMC\KMC\jcmon.exe.log.
INFO 2006-02-06 12:41:42
Working directory changed to C:\Program Files\sapinst_instdir\NW04SR1\CMC\KMC.
INFO 2006-02-06 12:41:42
Output of E:\usr\sap/NWD/DVEBMGS00/j2ee/os_libs/jcmon.exe 'pf=E:\usr\sap\NWD\SYS\profile/NWD_DVEBMGS00_chn-mumsap02' is written to the logfile jcmon.exe.log.
INFO 2006-02-06 12:41:45
Execution of the command "E:\usr\sap/NWD/DVEBMGS00/j2ee/os_libs/jcmon.exe 'pf=E:\usr\sap\NWD\SYS\profile/NWD_DVEBMGS00_chn-mumsap02'" finished with return code 0. Output: snipped
ERROR 2006-02-06 12:41:47
FJS-00003 TypeError: node has no properties (in script InstallationScript_31, line 12683: ???)
<b>ERROR 2006-02-06 12:41:51
FJS-00003 TypeError: node has no properties (in script InstallationScript_32, line 12683: ???)</b>Hi Robert,
Thanks for your reply.. but i was unable to find out
< step name="increaseAddServTimeout">
in my control.xml file..
any clue.. why this is missing.?
FJS-00003 TypeError: node has no properties (in script InstallationScript 304, line 3372: ???)
SOLUTION/WORKAROUND
1. In the sapinst error window, press "OK" to terminate sapinst.
2. Open the file <installation_dir>/control.xml with a text editor.
3. Search for the first occurance of the string
< step name="increaseAddServTimeout">
You should see the following piece of code:
<step name="increaseAddServTimeout">
<script include="UM,epHelpers"><![CDATA[
var targetdir = context.get("inqmy_installationDirectoryToBeU...
1. Add the following line (in one line !)
context. set("inqmy_instanceNameToBeUsed",new Table("t_context_for_InQMy").select("SAPSID", "WHERE ROWNUM = 0"));
o that the result looks as follows: -
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', -
Hi
I am Installing SAP NW 2004 on AIX 5.3 + Oracle Database. At the Software Unit Installation Phase I am getting the following Error
ERROR 2009-10-15 14:22:31
CJS-30156 SDM deployment failed for at least one of the components to deploy.<br> SOLUTION: Check '/tmp/sapinst_instdir/NW04S/SYSTEM/ORA/CENTRAL/AS/callSdmViaSapinst.log' for more information.
There is no clutser control instance running on host SAPPEP which is described in SecureStorage .
ERROR 2009-10-15 14:53:59
FCO-00011 The step enableUsageTypes with step key |NW_Onehost|ind|ind|ind|ind|0|0|SAP_Software_Features_Enablement|ind|ind|ind|ind|4|0|enableUsageTypes was executed with status ERROR .
I am getting the following error in callSdmViaSapinst.log
15, 2009 2:46:47 PM Info: Starting: Initial deployment: Selected development component 'com.sap.netweaver.bc.logging'/'sap.com'/'SAP AG'/'7.0009.20060825141640.0000'/'1' will be deployed.
Oct 15, 2009 2:46:47 PM Info: SDA to be deployed: /usr/sap/PEP/JC00/SDM/root/origin/sap.com/com.sap.netweaver.bc.logging/SAP AG/1/7.0009.20060825141640.0000/com.sap.netweaver.bc.logging.ear
Oct 15, 2009 2:46:47 PM Info: Software type of SDA: J2EE
*Oct 15, 2009 2:46:47 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) ******
Oct 15, 2009 2:46:47 PM Info: Starting cluster instance processes.
Oct 15, 2009 2:46:47 PM Error: An error occured while starting a cluster instance.
Oct 15, 2009 2:46:47 PM Error: There is no clutser control instance running on host SAPPEP which is described in SecureStorage .
The instances, returned by MessageServer [MS host: SAPPEP; MS port: 3901], are :
|Name:JM_T1255592807640_1_SAPPEP |Host:SAPPEP |State:5|HostAddress:172.31.199.240|
Please check if there is an appropriate running cluster instances.
*Oct 15, 2009 2:46:47 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) ******
Oct 15, 2009 2:46:47 PM Error: Aborted: development component 'com.sap.netweaver.bc.logging'/'sap.com'/'SAP AG'/'7.0009.20060825141640.0000'/'1', grouped by software component 'KMC-BC'/'sap.com'/'SAP AG'/'1000.7.00.9.0.20060827081000''/'1':
SDM could not start the J2EE cluster on the host SAPPEP! The online deployment is terminated.
There is no clutser control instance running on host SAPPEP which is described in SecureStorage .
The instances, returned by MessageServer [MS host: SAPPEP; MS port: 3901], are :
|Name:JM_T1255592807640_1_SAPPEP |Host:SAPPEP |State:5|HostAddress:172.31.199.240|
Please check if there is an appropriate running cluster instances.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineJ2EE620OnlineDeployerImpl.performAction(DeploymentActionTypes).STARTUP_CLUSTER)
Oct 15, 2009 2:46:47 PM Info: Starting to save the repository
Oct 15, 2009 2:46:48 PM Info: Finished saving the repository
Please Suggest
Regards
Soumya DasguptaThanks
The Issue is Solved as per you Suggestion
Regards
Soumya Dasgupta -
hi experts,
Jan 21, 2021 1:14:55 PM Info: Initial deployment: Selected development component 'PRTDatabaseMigrationController'/'sap.com'/'SAP AG'/'7.0100.20081117062041.0000'/'0' will be deployed.
Jan 21, 2021 1:14:55 PM Info: Initial deployment: Selected development component 'tc/eu/jwf/wd/tport'/'sap.com'/'MAIN_NW701P03_C'/'2857529'/'0' will be deployed.
Jan 21, 2021 1:14:55 PM Info: Initial deployment: Selected development component 'com.sap.netweaver.bc.uwl.uwladmin'/'sap.com'/'SAP AG'/'7.0100.20081208074141.0000'/'0' will be deployed.
Jan 21, 2021 1:14:55 PM Info: Initial deployment: Selected development component 'tc/kmc/bc.uwl.ui/wd_pp'/'sap.com'/'SAP AG'/'7.0103.20081208074141.0000'/'0' will be deployed.
Jan 21, 2021 1:14:55 PM Info: Initial deployment: Selected development component 'com.sap.portal.nav.ws.NavigationWSEar'/'sap.com'/'SAP AG'/'7.0103.20081208074141.0000'/'3' will be deployed.
Jan 21, 2021 1:14:55 PM Info: Initial deployment: Selected development component 'caf/eu/gp/ui/gpconf'/'sap.com'/'MAIN_NW701P03_C'/'2857562'/'0' will be deployed.
Jan 21, 2021 1:14:55 PM Info: Initial deployment: Selected development component 'caf/eu/gp/croom/content'/'sap.com'/'MAIN_NW701P03_C'/'2857536'/'0' will be deployed.
Jan 21, 2021 1:14:55 PM Info: Initial deployment: Selected development component 'com.sap.prt.ws.container'/'sap.com'/'SAP AG'/'7.0100.20081117062041.0000'/'0' will be deployed.
Jan 21, 2021 1:14:56 PM Info: Ending deployment prerequisites. All items are correct.
Jan 21, 2021 1:14:57 PM Info: Saved current Engine state.
Jan 21, 2021 1:14:57 PM Info: Starting: Initial deployment: Selected development component 'com.sapportals.urdesigndata'/'sap.com'/'SAP AG'/'7.0103.20081117062041.0000'/'3' will be deployed.
Jan 21, 2021 1:14:57 PM Info: ***** Begin of File-System Deployment com.sapportals.urdesigndata *****
Jan 21, 2021 1:14:57 PM Info: Deploy Action is DEPLOY
Jan 21, 2021 1:14:57 PM Error: Fileset "com.sapportals.designservices_FS" does not contain any files!
Jan 21, 2021 1:14:57 PM Error: ==> SDA cannot be deployed!
Jan 21, 2021 1:14:57 PM Error: Aborted: development component 'com.sapportals.urdesigndata'/'sap.com'/'SAP AG'/'7.0103.20081117062041.0000'/'3', grouped by software component 'EP-PSERV'/'sap.com'/'SAP AG'/'1000.7.01.3.0.20090108071100''/'3':
No Filesets for Deployment found
Jan 21, 2021 1:14:57 PM Info: Starting to save the repository
Jan 21, 2021 1:14:57 PM Info: Finished saving the repository
Jan 21, 2021 1:14:57 PM Info: Starting: Initial deployment: Selected software component 'EP-PSERV'/'sap.com'/'SAP AG'/'1000.7.01.3.0.20090108071100''/'3' will be deployed.
Jan 21, 2021 1:14:57 PM Error: Aborted: software component 'EP-PSERV'/'sap.com'/'SAP AG'/'1000.7.01.3.0.20090108071100''/'3':
Failed deployment of SDAs:
development component 'com.sapportals.urdesigndata'/'sap.com'/'SAP AG'/'7.0103.20081117062041.0000'/'3' : aborted
Please, look at error logs above for more information!
Jan 21, 2021 1:14:57 PM Info: Starting to save the repository
Jan 21, 2021 1:14:58 PM Info: Finished saving the repository
Jan 21, 2021 1:14:58 PM Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
Jan 21, 2021 1:14:58 PM Error: -
At least one of the Deployments failed -
Jan 21, 2021 1:15:00 PM Info: Summarizing the deployment results:
Jan 21, 2021 1:15:00 PM Error: Admitted: E:\NW_Java Components\51037093\DATA_UNITS\JAVA_J2EE_OSINDEP_UT\EPBC03_0.SCA
Jan 21, 2021 1:15:00 PM Error: Admitted: E:\NW_Java Components\51037093\DATA_UNITS\JAVA_J2EE_OSINDEP_UT\EPBC203_0.SCA
Jan 21, 2021 1:15:00 PM Error: Aborted: E:\NW_Java Components\51037093\DATA_UNITS\JAVA_J2EE_OSINDEP_UT\EPPSERV03_0.SCA
Jan 21, 2021 1:15:00 PM Error: Admitted: E:\NW_Java Components\51037093\DATA_UNITS\JAVA_J2EE_OSINDEP_UT\EPWDC03_0.SCA
Jan 21, 2021 1:15:00 PM Error: Admitted: E:\NW_Java Components\51037093\DATA_UNITS\JAVA_J2EE_OSINDEP_UT\UWLJWF03_0.SCA
Jan 21, 2021 1:15:00 PM Error: Admitted: E:\NW_Java Components\51037093\DATA_UNITS\JAVA_J2EE_OSINDEP_UT\SAPEU03_0.SCA
Jan 21, 2021 1:15:00 PM Error: Processing error. Return code: 4
java log
Info:
Info: ============================================
Info: = Starting to execute command 'deploy' =
Info: ============================================
Info: Starting SDM - Software Deployment Manager...
Starting SDM - Software Deployment Manager...
Info: tc/SL/SDM/SDM/sap.com/SAP AG/7.0103.20081105085605.0000
tc/SL/SDM/SDM/sap.com/SAP AG/7.0103.20081105085605.0000
Info: SDM operation mode successfully set to: Standalone
Initializing Network Manager (50317)
Info: Initializing Network Manager (50317)
Checking if another SDM is running on port 50318
Info: Checking if another SDM is running on port 50318
Info: -
Starting deployment -
Info: Error handling strategy: OnErrorStop
Info: Prerequisite error handling strategy: OnPrerequisiteErrorStop
Info: Update strategy: UpdateLowerVersions
Info: Starting deployment prerequisites:
Info: Loading selected archives...
Info: Loading archive 'E:\NW_Java Components\51037093\DATA_UNITS\JAVA_J2EE_OSINDEP_UT\EPBC03_0.SCA'
Info: Loading archive 'E:\NW_Java Components\51037093\DATA_UNITS\JAVA_J2EE_OSINDEP_UT\EPBC203_0.SCA'
Info: Loading archive 'E:\NW_Java Components\51037093\DATA_UNITS\JAVA_J2EE_OSINDEP_UT\EPPSERV03_0.SCA'
Info: Loading archive 'E:\NW_Java Components\51037093\DATA_UNITS\JAVA_J2EE_OSINDEP_UT\EPWDC03_0.SCA'
Info: Loading archive 'E:\NW_Java Components\51037093\DATA_UNITS\JAVA_J2EE_OSINDEP_UT\UWLJWF03_0.SCA'
Info: Loading archive 'E:\NW_Java Components\51037093\DATA_UNITS\JAVA_J2EE_OSINDEP_UT\SAPEU03_0.SCA'
Error: Exception occured during extractSingleFile: invalid entry CRC (expected 0x6e0e516b but got 0xd0b33b44)
Caught Exception: java.lang.NullPointerException
java.lang.NullPointerException
at com.sap.sdm.app.sequential.deployment.impl.DeployItemList.findByComponentBase(DeployItemList.java:31)
at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.loadSelectedArchives(DeployerImpl.java:291)
at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.deploymentPrerequisite(DeployerImpl.java:490)
at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.deploy(DeployerImpl.java:91)
at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.deploy(DeployerImpl.java:68)
at com.sap.sdm.control.command.cmds.Deploy.execute(Deploy.java:179)
at com.sap.sdm.control.command.decorator.AssureStandaloneMode.execute(AssureStandaloneMode.java:53)
at com.sap.sdm.control.command.decorator.AssureOneRunningSDMOnly.execute(AssureOneRunningSDMOnly.java:61)
at com.sap.sdm.control.command.decorator.SDMInitializer.execute(SDMInitializer.java:52)
at com.sap.sdm.control.command.decorator.GlobalParamEvaluator.execute(GlobalParamEvaluator.java:60)
at com.sap.sdm.control.command.decorator.AbstractLibDirSetter.execute(AbstractLibDirSetter.java:46)
at com.sap.sdm.control.command.decorator.ExitPostProcessor.execute(ExitPostProcessor.java:48)
at com.sap.sdm.control.command.decorator.CommandNameLogger.execute(CommandNameLogger.java:49)
at com.sap.sdm.control.command.decorator.AdditionalLogFileSetter.execute(AdditionalLogFileSetter.java:65)
at com.sap.sdm.control.command.decorator.AbstractLogDirSetter.execute(AbstractLogDirSetter.java:54)
at com.sap.sdm.control.command.decorator.SyntaxChecker.execute(SyntaxChecker.java:37)
at com.sap.sdm.control.command.Command.exec(Command.java:42)
at SDM.main(SDM.java:21)
Severe (internal) error. Return code: 16Hi Hassan,
Info: Loading archive 'E:\NW_Java Components\51037093\DATA_UNITS\JAVA_J2EE_OSINDEP_UT\EPBC03_0.SCA' Info: Loading archive 'E:\NW_Java Components\51037093\DATA_UNITS\JAVA_J2EE_OSINDEP_UT\EPBC203_0.SCA' Info: Loading archive 'E:\NW_Java Components\51037093\DATA_UNITS\JAVA_J2EE_OSINDEP_UT\EPPSERV03_0.SCA' Info: Loading archive 'E:\NW_Java Components\51037093\DATA_UNITS\JAVA_J2EE_OSINDEP_UT\EPWDC03_0.SCA' Info: Loading archive 'E:\NW_Java Components\51037093\DATA_UNITS\JAVA_J2EE_OSINDEP_UT\UWLJWF03_0.SCA' Info: Loading archive 'E:\NW_Java Components\51037093\DATA_UNITS\JAVA_J2EE_OSINDEP_UT\SAPEU03_0.SCA' Error: Exception occured during extractSingleFile: invalid entry CRC (expected 0x6e0e516b but got 0xd0b33b44) Caught Exception: java.lang.NullPointerException java.lang.NullPointerException at com.sap.sdm.app.sequential.deployment.impl.DeployItemList.findByComponentBase(DeployItemList.java:31) at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.loadSelectedArchives(DeployerImpl.java:291) at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.deploymentPrerequisite(DeployerImpl.java:490) at
You DVD number 51037093 seems to be corrupt. Could you stop the installation. Re-copy the DVD correctly.
Restart your installation with "new installation" option.
Hope this is useful.
Regards,
Deepak Kori -
Error while installing KMC SP09
Hey,
I am getting the following error while installing KMC on Web AS 6.40 EP 6.0 SP09.
Other colleagues of mine have been able to install the same successfully from the same installatin DVD.
Can someone help me with a work around? Thanks.
Regards,
winston
***********************Error Descrition****************
INFO 2005-08-02 14:11:24
Execution of the command "C:\Program Files\Java\j2re1.4.2_05/bin/java '-version'" finished with return code 0. Output: java version "1.4.2_05"Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_05-b04)Java HotSpot(TM) Client VM (build 1.4.2_05-b04, mixed mode)
INFO 2005-08-02 14:11:25
Looking for SAP system instances installed on this host...
INFO 2005-08-02 14:11:28
Found these instances: sid: J2E, number: 01, name: SCS01, host: blrkec41167dsid: J2E, number: 00, name: JC00, host: blrkec41167dsid: JEE, number: 03, name: SCS03, host: blrkec41167dsid: JEE, number: 02, name: JC02, host: blrkec41167d
ERROR 2005-08-02 14:11:30
CJS-00291 SAPInst could not find any SAP J2EE instances that match the Portal Platform requirements. The installation stops. Install the SAP J2EE 6.40 according to the Portal PAM requirements, and run the portal installation again.
WARNING 2005-08-02 14:11:30
The step lookForAlreadInstalledJ2EEEngine with step key EP_KMC_MAIN|ind|ind|ind|EP60|ind|0|EP60|ind|ind|ind|EP60|ind|0|lookForAlreadInstalledJ2EEEngine was executed with status ERROR.
***********************Error Descrition****************Hi
In your desktop probably this is second J2E instance so my suggestion is that you unistall using the uninstaller and then go to sapinst_dir in program files delete it compeletely and then go for fresh installation .Also mention the java path and home correctly.
With regards
subrato kundu
IBM
SAP Enterprise Portal Technology Consultant -
Getting error iview while accessing room in EP6.0 SP9 KMC
Hi
I am trying to configure KMC first time. I have done all the basic configuration needed after installation to get collaboration service active.
I can create a room. but while clicking on the link to get into the room I am getting error in iview com.sap.portal.pcm.Title
with error
<error>
<i>Portal Runtime Error
An exception occurred while processing a request for :
iView : pcd:portal_content/com.sap.ip.collaboration/Rooms/f0eecc1b-52af-2710-cebd-e94073869c63/workset/com.sap.netweaver.coll.TeamRoomOverview/RoomQuickLaunch
Component Name : null
Page could not create the iView.
See the details for the exception ID in the log file</i>
</error>
from the logviewer I found these errors
<error>
<i>No status mapped to the given list type <http://sap.com/xmlns/collaboration/rooms/room> using hard coded default</i>
</error>
<error>
<i>Permission check failed - Object portal_content/com.sap.ip.collaboration/Rooms/f0eecc1b-52af-2710-cebd-e94073869c63/workset/com.sap.netweaver.coll.TeamRoomOverview/RoomQuickLaunch Permissions: Pcd.Use Principal: Information not available with current trace level</i>
</error>
please help me. I think some mapping needs to be done. but not sure exactly where and what mapping. I may be wrong
regards
AshutoshHi Ashutosh,
See SAP Note 792370 and this thread: EP Colloboration Room Error
Probably this is the solution to your problem.
If it doesn't work, before smashing your head against the wall, I would seriously advise to patch up to SP12 for there have been some problems within KMC/Rooms within the lower versions (they might not all have gone, but many of them).
Hope it helps
Detlev
Maybe you are looking for
-
HT4527 how to move my itunes library from my Ipod to a NEW PC
My Laptop had to be reformatted and as a result I lost access to Itunes. I was not able to save any of my backups nor my iTunes library. I am trying to sync my iPod and iPhone to my NEWLY formatted hard drive and iTunes wants to WIPE my devices. Is
-
Upgrading Solaris from 2.6 to 2.8 -- how to relink IAS 1.0.2.2.2
Hi, We will be upgrading our Application Server from Solaris 2.6 to 2.8 (32-bit) very soon. We have the following Oracle products installed on this server: Oracle Internet Application Server (IAS) 1.0.2.2.2 components: Apache HTTP 1.3.19.0.0f Oracle
-
I'm trying to upgrade my G3 power mac (DV) from OS 9 to OS X. I bought Tiger for my new G5 mac and want to load it on my old machine. I've updated the firmware to the latest for this model, 1.1. When I follow the instructions on the Tiger cd to click
-
EDI 850 - Config to avoid Sending Item with Delv. Completed=ON
Hi Guys We are sending our PO and Schedulling Agreement (SA) through EDI (as 850) to our suppliers. However, our SA are opened for a long time so they can grow a lot, meaning that we have multiple items with multiple Schedule Lines. Sometimes, that
-
OS Deployment - Unable to read task sequence, WpeInit.exe does not start automatically
Ok so this is a very very weird one. this is my first time actually coming to the community for help. I need assistance asap. I have 4517 systems in SCCM 2007, we have a mixture of PXE enabled offices and offices with just DPs that use boot media fo