Error ERP 6.0 Installation step 32 of 96 JAVA

Hello everybody,
i have the folowing error in my installation:
FCO-00011 The step redeployForJSPM with step key |NW_Onehost|ind|ind|ind|ind|0|0|SAP_Software_Features_Enablement|ind|ind|ind|ind|4|0|redeployForJSPM was executed with status ERROR
So all Java Server and the SDM Server are running!
Here are my log files sapinstlog:
INFO 2010-01-22 01:57:11.105
Execute step redeployForJSPM of component |NW_Onehost|ind|ind|ind|ind|0|0|SAP_Software_Features_Enablement|ind|ind|ind|ind|5|0
ERROR 2010-01-22 01:57:13.198
FJS-00003 uncaught exception: undefined (in script unknown, line 0: ???)
ERROR 2010-01-22 01:57:14.823
FCO-00011 The step redeployForJSPM with step key |NW_Onehost|ind|ind|ind|ind|0|0|SAP_Software_Features_Enablement|ind|ind|ind|ind|5|0|redeployForJSPM was executed with status ERROR ( Last error reported by the step :uncaught exception: undefined (in script unknown, line 0: ???)).
INFO 2010-01-22 01:58:29.776
An error occured and the user decided to retry the current step: "|NW_Onehost|ind|ind|ind|ind|0|0|SAP_Software_Features_Enablement|ind|ind|ind|ind|5|0|redeployForJSPM".
ERROR 2010-01-22 01:58:31.245
FJS-00003 uncaught exception: undefined (in script unknown, line 0: ???)
ERROR 2010-01-22 01:58:32.401
FCO-00011 The step redeployForJSPM with step key |NW_Onehost|ind|ind|ind|ind|0|0|SAP_Software_Features_Enablement|ind|ind|ind|ind|5|0|redeployForJSPM was executed with status ERROR ( Last error reported by the step :uncaught exception: undefined (in script unknown, line 0: ???)).
INFO 2010-01-22 01:58:55.261
An error occured and the user decide to stop.\n Current step "|NW_Onehost|ind|ind|ind|ind|0|0|SAP_Software_Features_Enablement|ind|ind|ind|ind|5|0|redeployForJSPM".
INFO 2010-01-22 01:59:02.214
Creating file C:\Program Files\sapinst_instdir\.lastInstallationLocation.
INFO 2010-01-22 01:59:03.089
Creating file C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\__instana_tmp.xml.
And the callSdmViaSapinst.log
Jan 21, 2010 8:10:22 AM Info:
Jan 21, 2010 8:10:22 AM Info: ==============================================
Jan 21, 2010 8:10:22 AM Info: = Starting to execute command 'jstartup' =
Jan 21, 2010 8:10:22 AM Info: ==============================================
Jan 21, 2010 8:10:22 AM Info: Starting SDM - Software Deployment Manager...
Jan 21, 2010 8:10:22 AM Info: tc/SL/SDM/SDM/sap.com/SAP AG/7.0014.20071029094708.0000
Jan 21, 2010 8:10:23 AM Info: SDM operation mode successfully set to: Standalone
Jan 21, 2010 8:10:24 AM Info: Initializing Network Manager (50017)
Jan 21, 2010 8:10:24 AM Info: Checking if another SDM is running on port 50018
Jan 21, 2010 8:10:24 AM Info:
Jan 21, 2010 8:10:24 AM Info: SDM operation mode successfully set to: Integrated
Jan 21, 2010 8:10:24 AM Info: Operationmode for JStartupFramework set to "integrated".
Jan 21, 2010 8:10:24 AM Info: Successfully executed. Return code: 0
And my configurationtoool.bat java infos:
Djava.security.policy=./java.policy
-Djava.security.egd=file:/dev/urandom
-Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
-Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
-Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
-Dorg.xml.sax.driver=com.sap.engine.lib.xml.parser.SAXParser
-verbose:gc
-Xmx1024m
-Xms1024m
-Djco.jarm=1
-XX:PermSize=512m
-XX:MaxPermSize=1024m
-XX:NewSize=320m
-XX:MaxNewSize=320m
-XX:SurvivorRatio=2
-XX:TargetSurvivorRatio=90
-XX:+PrintGCTimeStamps
-XX:+UseTLAB
-XX:SoftRefLRUPolicyMSPerMB=1
-Dsun.io.useCanonCaches=false
-Djava.awt.headless=true
-Xss2m
-XX:+UseParNewGC
-Drdbms.driverLocation=C:/usr/sap/DRC/DVEBMGS00/exe/ojdbc14.jar
Have anyone a Solutiion for my problem?
Thank you for your answers
Greets
Naucho
Edited by: Naucho on Jan 22, 2010 11:12 AM

I shutdown all my instances and restart it but the error comes again.
Here my actually sapinst.log file:
INFO 2010-01-22 02:25:00.808
Creating file C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\x.
INFO 2010-01-22 02:25:00.808
Removing file C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\x.
INFO 2010-01-22 02:25:03.589
Creating file C:\Program Files\sapinst_instdir\x.
INFO 2010-01-22 02:25:03.589
Removing file C:\Program Files\sapinst_instdir\x.
INFO 2010-01-22 02:25:07.542
Copied file 'C:/Program Files/sapinst_instdir/ERP/SYSTEM/ORA/CENTRAL/AS/statistic.xml' to 'C:/Program Files/sapinst_instdir/ERP/SYSTEM/ORA/CENTRAL/AS/statistic.18.xml'.
INFO 2010-01-22 02:25:14.605
Copied file 'C:/Program Files/sapinst_instdir/ERP/SYSTEM/ORA/CENTRAL/AS/statistic.xml' to 'C:/Program Files/sapinst_instdir/ERP/SYSTEM/ORA/CENTRAL/AS/statistic.19.xml'.
WARNING 2010-01-22 02:26:02.776
Unable to get information about path
LABEL.ASC\ using GetVolumeInformation. Operating system error message: The filename, directory name, or volume label syntax is incorrect.
INFO 2010-01-22 02:26:07.714
Copied file 'C:/Program Files/sapinst_instdir/ERP/SYSTEM/ORA/CENTRAL/AS/inifile.xml' to 'C:/Program Files/sapinst_instdir/ERP/SYSTEM/ORA/CENTRAL/AS/inifile.7.xml'.
INFO 2010-01-22 02:26:08.480
Execute step
Component W2K_ServicePack_Check|ind|ind|ind|ind
Preprocess of component |NW_Onehost|ind|ind|ind|ind|0|0|NW_First_Steps|ind|ind|ind|ind|1|0|W2K_ServicePack_Check|ind|ind|ind|ind|2|0
INFO 2010-01-22 02:26:40.870
Copied file 'C:/Program Files/sapinst_instdir/ERP/SYSTEM/ORA/CENTRAL/AS/keydb.xml' to 'C:/Program Files/sapinst_instdir/ERP/SYSTEM/ORA/CENTRAL/AS/keydb.7.xml'.
INFO 2010-01-22 02:26:42.011
Copied file 'C:/Program Files/sapinst_instdir/ERP/SYSTEM/ORA/CENTRAL/AS/statistic.xml' to 'C:/Program Files/sapinst_instdir/ERP/SYSTEM/ORA/CENTRAL/AS/statistic.20.xml'.
INFO 2010-01-22 02:26:42.495
Execute step redeployForJSPM of component |NW_Onehost|ind|ind|ind|ind|0|0|SAP_Software_Features_Enablement|ind|ind|ind|ind|5|0
ERROR 2010-01-22 02:26:44.511
FJS-00003 uncaught exception: undefined (in script unknown, line 0: ???)
ERROR 2010-01-22 02:26:46.214
FCO-00011 The step redeployForJSPM with step key |NW_Onehost|ind|ind|ind|ind|0|0|SAP_Software_Features_Enablement|ind|ind|ind|ind|5|0|redeployForJSPM was executed with status ERROR ( Last error reported by the step :uncaught exception: undefined (in script unknown, line 0: ???)).
INFO 2010-01-22 02:28:51.823
An error occured and the user decided to retry the current step: "|NW_Onehost|ind|ind|ind|ind|0|0|SAP_Software_Features_Enablement|ind|ind|ind|ind|5|0|redeployForJSPM".
ERROR 2010-01-22 02:28:53.589
FJS-00003 uncaught exception: undefined (in script unknown, line 0: ???)
ERROR 2010-01-22 02:28:54.745
FCO-00011 The step redeployForJSPM with step key |NW_Onehost|ind|ind|ind|ind|0|0|SAP_Software_Features_Enablement|ind|ind|ind|ind|5|0|redeployForJSPM was executed with status ERROR ( Last error reported by the step :uncaught exception: undefined (in script unknown, line 0: ???)).
INFO 2010-01-22 02:28:56.683
An error occured and the user decided to retry the current step: "|NW_Onehost|ind|ind|ind|ind|0|0|SAP_Software_Features_Enablement|ind|ind|ind|ind|5|0|redeployForJSPM".
ERROR 2010-01-22 02:28:58.636
FJS-00003 uncaught exception: undefined (in script unknown, line 0: ???)
ERROR 2010-01-22 02:29:03.542
FCO-00011 The step redeployForJSPM with step key |NW_Onehost|ind|ind|ind|ind|0|0|SAP_Software_Features_Enablement|ind|ind|ind|ind|5|0|redeployForJSPM was executed with status ERROR ( Last error reported by the step :uncaught exception: undefined (in script unknown, line 0: ???)).

Similar Messages

Error in the post installation steps of SLD .

Hi
We are working on EP7.0 2004s.We are using local sld.Right now I am doing the post installation steps for SLD.I added the J2EE and UME roles.In the next step I went into the administration tab of SLD for configuring.It is throwing this error.
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Exit-Plug must no be triggered with an URL when running in portal. Use portal navigation instead to navigate to another application!
This is detailed exception I got.
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Exit-Plug must no be triggered with an URL when running in portal. Use portal navigation instead to navigate to another application!
at com.sap.tc.webdynpro.progmodel.view.View.navigate(View.java:516)
at com.sap.tc.webdynpro.progmodel.view.View.navigate(View.java:462)
at com.sap.sld.wd.main.wdp.InternalMainInterfaceView.wdFirePlugToOldUI(InternalMainInterfaceView.java:154)
at com.sap.sld.wd.main.Head.onActionAdministration(Head.java:277)
at com.sap.sld.wd.main.wdp.InternalHead.wdInvokeEventHandler(InternalHead.java:227)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:420)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:299)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:711)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:665)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:232)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Please help me.
Thanx & Regards,
Naresh

Hi Naresh,
Can you let me know the service pack for the portal.
Also try login in using administrator using the http://<localhost><port>/sld
thanks
Pankaj

Error while executing template installer: Step 14 Maintain JCO Destinations

Dear all:
We are applying Template Installer to perform post installation for BI-JAVA in NW2004s SP09.
Onto step 14: Maintain WebDynpro JCO Destinations, we faced the following Error message :
Element 'SAPConfigLib.BW8.Unclassified.maintainJcoDestination':!BrokerImport.import_of_element_failed!!BrokerImport.Fehler!com.sap.tc.lm.ctc.cul.cpi.exceptions.CPIBaseException: <Localization failed: ResourceBundle='com.sap.tc.lm.ctc.cul.cpi.CPIResourceBundle', ID='com.sap.tc.lm.ctc.cul.cpi.BaseException_BASE_EXCEPTION', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key com.sap.tc.lm.ctc.cul.cpi.BaseException_BASE_EXCEPTION:com.sap.tc.lm.ctc.provider.javaServiceProvider.JavaServiceWriter.writeElement!BrokerImport.LINE!157-:com.sap.tc.lm.ctc.cul.broker.BrokerImport.importElement.86
-:com.sap.tc.lm.ctc.cul.broker.BrokerImport.importElement.128
-:com.sap.tc.lm.ctc.cul.broker.BrokerImport.importElement.128
-:com.sap.tc.lm.ctc.cul.serviceimpl.importservice.CULConfigurationImport.importConfiguration.96
-:com.sap.tc.lm.ctc.ccl.templateinstaller.StepExecuter.run.41
Element 'SAPConfigLib.BW8.Unclassified.maintainJcoDestination':Error during executing Java Reflection:Failed to delete JCO client connection 'WD_ALV_MODELDATA_DEST' on 'BW8.SystemHome.sap15\kin'
Does anyone have any idea about it ?
Thank you very much
SF

We are encountering the same issue in NW2004s SP 10. Szu-Fen, did you find a solution? If so, could you please post it here?
Does anybody else have a hint how to resolve this?
kind regards,
Hartmut

NW PI Post Installation steps

Hello All,
I have installed a dual stack PI system and performing post installation steps for PI AS Java. In configuration tasks After completing NetWeaver initial setup with skipped steps I was progressing to next step to configure NW PI - AS ABAP in All Configuration Tasks-->NW PI - AS ABAP (Basic Configuration for Idoc, Proxy Maintain) but I couldn't find this option.
I have updated system, patches, cim etc still I couldnt find the above option, Please advise where I went wrong.
Thanks
Sam

Hi,
What is the pi version?
The steps differs from version to version . Like 7.1 and 7.3 are not exactly same. Can you check in the installation guide for the pi specific post steps for your version .
Regards,
Amit.

ERP 2005 IDES Installation UME Configuration Error

Hello All,
I am installing ERP 2005 SR2 .
At the step of UME Configuration it is stopped.
I restarted sapinst but no luck , again stoped sap with mmc and restarted the machine and started the sap and then started the sapinst but there was also no luck.
I really appreciate if some one can suggest me.Thanks a lot in advance
ERROR 2010-10-14 16:20:54
CJS-30059 Java EE Engine configuration error. DIAGNOSIS: Error when configuring J2EE Engine. See output of logfile umconfigurator.log: 'Warning :
ERPTRAINING/sapmnt/ER5/SYS/global/security/lib/tools/w3c_http.jar file stated but does not exist !Exception occurred in openJar(
ERPTRAINING\sapmnt\ER5\SYS\global\security\lib\tools\iaik_ssl.jar ) : java.util.zip.ZipException: The specified network name is no longer available at java.util.zip.ZipFile.open(Native Method) at java.util.zip.ZipFile.<init>(ZipFile.java:111) at java.util.jar.JarFile.<init>( JarFile.java:127) at java.util.jar.JarFile.<init>(JarFile.java:65) at com.sap.engine.offline.JarFilter.<init>(JarFilter.java:30) at com.sap.engine.offline.FileClassLoader.openJar(FileClassLoader.java:1131) at com.sap.engine.offline.FileClassLoader.findClass(FileClassLoader.java:623) at com.sap.engine.offline.FileClassLoader.loadClass(FileClassLoader.java:600) at com.sap.engine.offline.FileClassLoader.loadClass(FileClassLoader.java :578) at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:79)Oct 14, 2010 4:20:52 PM Info: UME configurator (com.sap.security.tools.UMConfiguratorLoad) called for action "setup"PerfTimes : loadNativeLayer: loading jperflib failed. no jperflib in java.library.pathOct 14, 2010 4:20:53 PM Error: main() [EXCEPTION] com.sap.engine.frame.core.configuration.ConfigurationException: Error while connecting to DB. at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool .<init>(DBConnectionPool.java:115) at com.sap.engine.core.configuration.impl.persistence.rdbms.PersistenceHandler.<init>(PersistenceHandler.java:38) at com.sap.engine.core.configuration.impl.cache.ConfigurationCache .<init>(ConfigurationCache.java:149) at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.init(ConfigurationManagerBootstrapImpl.java:236) at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl .<init>(ConfigurationManagerBootstrapImpl.java:60) at com.sap.security.tools.UMConfigModel.<init>(UMConfigModel.java:79) at com.sap.security.tools.UMConfiguratorLoad.main(UMConfiguratorLoad.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke( Method.java:324) at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)Caused by: com.sap.sql.log.OpenSQLException: Error while accessing secure store: File "
ERPTRAINING/sapmnt/ER5/SYS/global/security/data/SecStore.properties" is invalid: record with key "$internal/mode" is missing.. at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:106) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:145) at com.sap.sql.connect.OpenSQLDataSourceImpl.setDataSourceName(OpenSQLDataSourceImpl.java:226) at com.sap.sql.connect.OpenSQLDataSourceImpl.setDataSourceName (OpenSQLDataSourceImpl.java:197) at com.sa
p.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.<init>(DBConnectionPool.java:112) ... 11 moreCaused by: com.sap.security.core.server.secstorefs.FileInvalidException : File "
ERPTRAINING/sapmnt/ER5/SYS/global/security/data/SecStore.properties" is invalid: record with key "$internal/mode" is missing. at com.sap.security.core.server.secstorefs.StorageHandler.openExistingStore(StorageHandler.java:391) at com.sap.security.core.server.secstorefs.SecStoreFS.openExistingStore(SecStoreFS.java:1946) at com.sap.sql.connect.OpenSQLConnectInfo.getStore (OpenSQLConnectInfo.java:802) at com.sap.sql.connect.OpenSQLConnectInfo.lookup(OpenSQLConnectInfo.java:783) at com.sap.sql.connect.OpenSQLDataSourceImpl.setDataSourceName(OpenSQLDataSourceImpl.java:209) ... 13 more
ERROR 2010-10-14 16:20:54
FCO-00011 The step runUMConfigurator with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CI_Instance|ind|ind|ind|ind|11|0|NW_CI_Instance_Configure_Java|ind|ind|ind|ind|4|0|NW_UME_Configuration|ind|ind|ind|ind|1|0|NW_UME_Configuration_Doublestack|ind|ind|ind|ind|1|0|runUMConfigurator was executed with status ERROR .

Hi Basis,
Note 848950/851251 may solve your problems.
If problem persists, then try copying the CD again to dump location and restart the installation , it appears that sapinst is not able to open jar file.
Hope this is useful
Regards
Umesh

Error in the SAP ERP 6.0 Installation

Hello everybody,
i have a error in the phase 43 of 46 in the ERP 6.0 Installation.
Here are my UTL_configure_usages.log , i hope everone can help me by the solution. It´s my first time at the Installation of a SAP System.
+Path   : Exception : The Usage Type SM-APP/sap.com from product SOLMAN is not activated!+
+java.lang.Exception+
++     at com.sap.exception.BaseExceptionInfo.traceAutomatically(BaseExceptionInfo.java:1141)++
++     at com.sap.exception.BaseExceptionInfo.(UTInfoException.java:94)++
++     at com.sap.sl.ut.manager.persistence.db.InfoManager.setConfigured(InfoManager.java:450)++
++     at com.sap.sl.ut.manager.persistence.db.DataBaseInfoFactory.setConfigured(DataBaseInfoFactory.java:1504)++
++     at com.sap.sl.ut.manager.command.Configure.execute(Configure.java:30)++
++     at com.sap.sl.ut.manager.command.Command.exec(Command.java:88)++
++     at com.sap.sl.ut.manager.UtlMain.exec(UtlMain.java:74)++
++     at com.sap.sl.ut.manager.UtlMain.main(UtlMain.java:70)++
++     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)++
++     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)++
++     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)++
++     at java.lang.reflect.Method.invoke(Method.java:324)++
++     at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)++
+Jan 18, 2010 2:52:21 AM Info   : Precondition not fulfilled. The Usage Type needs to be active. Return code: 56+

An error occurred while processing service SAP ERP 6.0 Support Release 3 > SAP Systems > Oracle > Central System > Central System( Last error reported by the step :uncaught exception: nw.sdm.deploymentErrorWithLog: SDM deployment failed for at least one of the components to be deployed. SOLUTION: Check C:\Program Files/sapinst_instdir/ERP/SYSTEM/ORA/CENTRAL/AS/callSdmViaSapinst.log for more information. (in script unknown, line 0: And here are my logfile , i hope you can help me for a solution. I have restart the SAP System and start it again and click retry but nothing happen, the same error comes again. Jan 19, 2010 7:34:14 AM Info: Initial deployment: Selected development component 'tc/kmc/bc.uwl.ui/wd_pp'/'sap.com'/'SAP AG'/'7.0010.20061109164817.0000'/'1' will be deployed. Jan 19, 2010 7:34:14 AM Info: No action: Selected development component 'com.sap.portal.nav.ws.NavigationWSEar'/'sap.com'/'SAP AG'/'7.0014.20071210113331.0000'/'2' will not be deployed because containing software component 'EP-PSERV'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20071210193159''/'2' will not be deployed. Jan 19, 2010 7:34:14 AM Info: No action: Selected development component 'caf/eu/gp/ui/gpconf'/'sap.com'/'MAIN_APL70VAL_C'/'1534144'/'3' will not update currently deployed development component 'caf/eu/gp/ui/gpconf'/'sap.com'/'MAIN_APL70VAL_C'/'1534144'/'2'. Jan 19, 2010 7:34:14 AM Info: No action: Selected development component 'caf/eu/gp/croom/content'/'sap.com'/'MAIN_APL70VAL_C'/'1498043'/'3' will not update currently deployed development component 'caf/eu/gp/croom/content'/'sap.com'/'MAIN_APL70VAL_C'/'1498043'/'1'. Jan 19, 2010 7:34:14 AM Info: No action: Selected development component 'com.sap.prt.ws.container'/'sap.com'/'SAP AG'/'7.0010.20061109164817.0000'/'2' will not be deployed because containing software component 'EPBC2'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20071210152356''/'2' will not be deployed. Jan 19, 2010 7:34:14 AM Info: Ending deployment prerequisites. All items are correct. Jan 19, 2010 7:35:49 AM Info: Saved current Engine state. Jan 19, 2010 7:35:49 AM Info: Starting: Initial deployment: Selected development component 'caf/eu/gp/ws/msosrv'/'sap.com'/'MAIN_APL70VAL_C'/'963790'/'3' will be deployed. Jan 19, 2010 7:35:49 AM Info: SDA to be deployed: C:\usr\sap\DRC\DVEBMGS00\SDM\root\origin\sap.com\caf\eu\gp\ws\msosrv\MAIN_APL70VAL_C\3\963790\sap.com_cafeugpwsmsosrv.sda Jan 19, 2010 7:35:49 AM Info: Software type of SDA: J2EE Jan 19, 2010 7:35:49 AM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) ***** Jan 19, 2010 7:35:56 AM Info: Begin of log messages of the target system: 10/01/19 07:35:50 - *********************************************************** 10/01/19 07:35:51 - Start updating EAR file... 10/01/19 07:35:51 - start-up mode is lazy 10/01/19 07:35:51 - EAR file updated successfully for 47ms. 10/01/19 07:35:51 - Start deploying ... 10/01/19 07:35:51 - EAR file uploaded to server for 32ms. 10/01/19 07:35:56 - ERROR: NOT deployed. The Deploy Service returned the following error: For detailed information see the log file of the Deploy Service. Exception is: com.sap.engine.services.rmi_p4.P4ConnectionException: Possible problem: no available running server node. Check your running servers. at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:700) at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:688) at com.sap.engine.services.rmi_p4.Parser.newRequest(Parser.java:180) at com.sap.engine.services.rmi_p4.Connection.run(Connection.java:427) at java.lang.Thread.run(Thread.java:534) ; 10/01/19 07:35:56 - *********************************************************** Jan 19, 2010 7:35:56 AM Info: End of log messages of the target system. Jan 19, 2010 7:35:56 AM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) ***** Jan 19, 2010 7:35:56 AM Error: Aborted: development component 'caf/eu/gp/ws/msosrv'/'sap.com'/'MAIN_APL70VAL_C'/'963790'/'3', grouped by software component 'SAP-EU'/'sap.com'/'MAIN_APL70VAL_C'/'1000.7.00.14.0.20071210153525''/'3': Caught exception during application deployment from SAP J2EE Engine's deploy API: com.sap.engine.deploy.manager.DeployManagerException: ERROR: NOT deployed. The Deploy Service returned the following error: com.sap.engine.services.rmi_p4.P4ConnectionException: Possible problem: no available running server node. Check your running servers. Exception is: com.sap.engine.services.rmi_p4.P4ConnectionException: Possible problem: no available running server node. Check your running servers. at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:700) at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:688) at com.sap.engine.services.rmi_p4.Parser.newRequest(Parser.java:180) at com.sap.engine.services.rmi_p4.Connection.run(Connection.java:427) at java.lang.Thread.run(Thread.java:534) ; (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).DMEXC) Jan 19, 2010 7:35:56 AM Info: Starting to save the repository Jan 19, 2010 7:35:57 AM Info: Finished saving the repository

Post installation steps for SAP PI, scenarios for SAP ERP 6.0 EhP 3.0 BAIO

Hi!
I installed SAP NetWeaver 2004S with PI component.
I also have a demo SAP ERP 6.0 EhP 3.0 BAIO system with several clients:
(100: demo client, 200: BW, 300: demo client (copy of 100)).
Questions:
what are the post installation steps to configure SAP PI?
Which scenarios can be used in such landscape?
(eg. exchange (IDOC, RFC, etc.) from client ERP:100 to ERP:200)
Thank you very much indeed!
regards
Holger

Hi Holger:
what are the post installation steps to configure SAP PI?
http://help.sap.com/saphelp_nw70/helpdata/en/a0/40084136b5f423e10000000a155106/content.htm
Which scenarios can be used in such landscape?
(eg. exchange (IDOC, RFC, etc.) from client ERP:100 to ERP:200)
I recommend you to use proxys in your landscape as you want to interchange messages between
different clients in the same system.
Hope this helps you.
Carlos

Webdynpro error in Post installation steps of SLD

Hi
We are working on EP7.0 2004s.We are using local sld.Right now I am doing the post installation steps for SLD.I added the J2EE and UME roles.In the next step I went into the administration tab of SLD for configuring.It is throwing this error.
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Exit-Plug must no be triggered with an URL when running in portal. Use portal navigation instead to navigate to another application!
This is detailed exception I got.
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Exit-Plug must no be triggered with an URL when running in portal. Use portal navigation instead to navigate to another application!
at com.sap.tc.webdynpro.progmodel.view.View.navigate(View.java:516)
at com.sap.tc.webdynpro.progmodel.view.View.navigate(View.java:462)
at com.sap.sld.wd.main.wdp.InternalMainInterfaceView.wdFirePlugToOldUI(InternalMainInterfaceView.java:154)
at com.sap.sld.wd.main.Head.onActionAdministration(Head.java:277)
at com.sap.sld.wd.main.wdp.InternalHead.wdInvokeEventHandler(InternalHead.java:227)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:420)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:299)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:711)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:665)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:232)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Please help me.
Thanx & Regards,
Naresh

Hey Aviad,
Yes I did, in my case I've installed PDK SP 9 over SP2 which is prohibited. If this is your case as well do the following:
1) From the Undeployment tab of the SDM select the com.sap.pct.pdk..
components.
2) Using the Archive remover tool which can be accessed from
System Administration > Support > Portal Runtime > Administration
Console > Archive Remover --> Remove the portal applications with prefixcom.sap.pct.pdk...
3) Navigate to Content Administration > Portal content > Content
Provided by SAP > Platform Add-Ons > Developer Content
and remove all the contents below this folder.
4) Restart the server
After this you can deploy the SP9 business package using the SDM.
Hope it helps,
Roy

Post Installation Steps for ERP add-on Inventory Manager 4.0

Hi,
I need to confirm what are the post-installation activities we must to perfom for ERP Add-on (Inventory Manager 4.0), besides de BC Activation. I did not find any information regarding the post installation steps for the ERP Add-on of Inventory Manager 4.0 (the installation guide for IM 4.0 on service marketplace does not remark the steps only explain the theorical part of the installation)... And we need to confirm if the steps are the same of Inventory Manager 3.2 Add-on or we must do an additional step?
Best Regards,
MC
Stephen Streeter Manju Venkatesha

Yeah...of course...
I forgot to specify it.
I install the first ERP 2005 SR2 on Oracle 10.2.0.2 and the other have to be installed on the same version of DB.
All installation are not MCOD.
This mean every installation has its own DB with different SID for every installation.
And of course I have at least doubled the space required by installer. Taken from sap notes the required space for ERP 2005 SR2 is about 90 GB.
The total space of mount point is about 500 GB....
Thanks
Dan

Some package installation error during zone installation steps.....

hi,
i am totally new to this technology.
i had created 3 Zone's on X86 Sun Fire X4270 M2 Hardware (OS - Solaris 10 update 9)
& during OS Installation i had selected Software installations using the Entire Distribution.
every thing worked fine but during zone installation steps, got some package installation error (refer the below output)
bash-3.00# zoneadm -z OFSMU-PWM-zone1 install
Preparing to install zone <OFSMU-PWM-zone1>.
Creating list of files to copy from the global zone.
Copying <158400> files to the zone.
Initializing zone product registry.
Determining zone package initialization order.
Preparing to initialize <1240> packages on the zone.
Initialized <1240> packages on zone.
Zone <OFSMU-PWM-zone1> is initialized.
Installation of these packages generated errors: <SUNWpostgr-82-libs SUNWpostgr-82-devel SUNWpostgr-83-server-data-root SUNWpostgr-82-server SUNWpostgr-82-contrib SUNWpostgr-82-client SUNWpostgr-82-server-data-root>
The file </zone/OFSMU-PWM-zone1/root/var/sadm/system/logs/install_log> contains a log of the zone installation.
i checked the log file "/zone/OFSMU-PWM-zone1/root/var/sadm/system/logs/install_log"
its show below error's
*** package <SUNWpostgr-82-libs> failed to install with fatal errors:
*** package <SUNWpostgr-82-devel> failed to install with fatal errors:
need your help my friends..
thanks in advance....
Edited by: Raja Kondar on Dec 9, 2010 11:59 AM

hi DR,
thnks for reply..
but i can see that "postgres" already exist in the system as user &l group.
postgres:x:90:90:PostgreSQL Reserved UID:/:/usr/bin/pfksh
also the failed packages duirng zone creation steps are already installed in the global zone..
is thr any other way to resolve this issue....
Edited by: Raja Kondar on Dec 16, 2010 11:00 AM

KW 7.0 Installation Step Error

Hi All,
I am currently installing IKS 1.0 on a NW04 system. Post installation steps need you to configure default connection settings to the backend system. However, you receive a logon screen that does not accept any named users. I did check that UME is configured correctly in the J2EE. Is there a trick or default userid/pw to get into the configuration screen? Thanks!

Hi Karsten,
I have opened an OSS message for this and found that there is a default user that should be used for this configuration piece. This user doesn't work either, but that's a separate issue
Thanks for your response.
Tim

Error in ECC6 During installation

Dear all
Error in ECC6 During installation , the following contents is get from sapnst_dev.log
148556: if ( componentToBeCalled == 'NW_Usage_Types_Configuration_BI_ind_ind_ind_ind')
148557:
148560: if ( componentToBeCalled == 'NW_Call_Offline_CTC_ind_ind_ind_ind')
148561:
148564: }
ERROR 2008-06-27 07:43:37 [iaxxejsbas.cpp:178]
 EJS_ErrorReporter
FJS-00003 TypeError: spStringRE.exec(labelString) has no properties (in script NW_Onehost|ind|ind|ind|ind, line 63483: ???)
ERROR 2008-06-27 07:43:37
FCO-00011 The step validateContent with step key |NW_Onehost|ind|ind|ind|ind|0|0|SAP_Software_Features_Enablement|ind|ind|ind|ind|4|0|SAP_Software_Features_GetContent|ind|ind|ind|ind|0|0|validateContent was executed with status ERROR .
TRACE
<html><head></head><body>An error occurred while processing service SAP ERP 2005 Support Release 2 > SAP Systems > Oracle > Central System > Central System Installation. You may now<ul> <li>press Retry to repeat the current step.</li> <li>press the View Log button to get more information about the error.</li> <li>stop the task and continue with it later.</li></ul>Log files are written to C:\Program Files/sapinst_instdir/ERP/SYSTEM/ORA/CENTRAL/AS.</body></html>
TRACE [iaxxgenimp.cpp:1155]
 showDialog()
waiting for an answer from gui
INFO 2008-06-27 07:45:05 [iaxxgenimp.cpp:782]
 showDialog()
An error occured and the user decide to stop.\n Current step "|NW_Onehost|ind|ind|ind|ind|0|0|SAP_Software_Features_Enablement|ind|ind|ind|ind|4|0|SAP_Software_Features_GetContent|ind|ind|ind|ind|0|0|validateContent".

Up !?

Post installation steps for PI 7.0

Hi,
Can anybody send me the Post installation steps for PI 7.0?
Thanks in advance..
~Kumar

Hello,
 
We did PI Installation recently and version is 7.1
 
Steps are as under...
 
 1. Basic PI installation
 2. System checks after basic installation
 a. SM50
 b. SM21
 c. ST22
 d. SM12
 e. SM13
 f. SM37
 3. Unlock the 001 client for cross-client changes temporarily and set system timezone (STZAC)
 4. Change 001 client settings back to no changes allowed.
 5. Create BASIS team member accounts in ABAP Stack and assign SAP_ALL.
 6. Set directory permission for \usr\sap\trans directory on Transport Domain Controller system.
 7. Import profiles (RZ10)
 8. Add the 4 following entries in to the instance profile and restart instance(RZ10)
 a. DIR_TRANS =
hostname.domain.ext\sapmnt\trans
 b. icm/host_name_full = hostname.domain.ext
 c. login/system_client = 100
 d. icm/server_port_0 = PROT=HTTP,PORT=5<sysno>00,TIMEOUT=1800,PROCTTIMEOUT=1800 {SAP Note 1107808}
 9. Configure TMS in transport domain controller{PI DEV} (STMS)
 a. Add virtual system
 b. STMS in newly installed system and configure proper transport domain
 c. In domain controller approve the new system (STMS -> SAP system -> Approve)
 10. Get maintenance certificate and SAP license from service marketplace and apply in to the new system {ABAP and JAVA} (slicense and NWA)
 11. Kernel Update JSPM
 a. JSPM update
 b. Kernel update
 c. BC-FES-IGS update
 12. Support pack installation ABAP
 a. SPAM update
 b. Support packs update
 13. Support pack installation JAVA
 a. Apply support pack stack
 b. Apply support pack patches
 i. After JVM installation Error occurs apply MS windows KB973544 {SAP Note 1367498}
 c. Restart JSPM and continue patch installation
 14. Client copy from client 001 to X00 using profile SAP_ALL
 15. Create logical system and assign it to new client (SALE)
 16. Change UME target in JAVA to client X00.
 a. Enter URL as http://hostname.domain.ext:port/nwa
 b. Management -> Infrastructure -> Destination
 c. Logon data TAB change client to X00
 d. Restart JAVA Instance
 17. Create following users
 a. PIAFUSER, PIRWBUSER, PIISUSER, PIDIRUSER, PIREPUSER and PIAPPLUSER on the target SLD and new system manually and assign role/group SAP_SLD_CONFIGURATOR to them. {SAP Note 1309239}
 b. PISUPER in new system and assign appropriate roles in ABAP and JAVA
 c. SLD_DS_<SID> and SLD_CL_<SID> on target SLD {Use source system master password}
 d. JCoRFC_<SID> in new system
 e. Sapadm user in new system
 18. Assign roles and groups to BASIS team on JAVA Stack
 19. Create PUBLIC logon group (SMLG)
 20. Configure SLD collector job as sapadm (RZ70)
 21. Run Configuration Wizard
 a. Enter URL as http://hostname.domain.ext:port/nwa
 b. Configuration management -> Scenarios -> Configuration Wizard
 c. Select Initial Configuration and click Start.
 22. Create the JCoRFC connection.
 a. Enter URL as http://hostname.domain.ext:port
 b. Web Dynpro -> Content administrator -> Maintain JCo destination
 c. Fill in information for the following 4 entries using client X00 and JCoRFC_<SID> as the user {Make sure you note the distinction between Metadata and Model destinations when you are creating the destination}
 i. WD_ALV_METADATA_DEST
 ii. WD_ALV_MODELDATA_DEST
 iii. WD_MODELDATA_DEST
 iv. WD_RFC_METADATA_DEST
(Use dictionary Meta Data for the Metadata connections, use Application Data for the Model Data connections.)
(Use the master password for EXQ)
 23. Repeat for the remaining 3 JCo RFC destinations.
 24. Run PI Full Qualified Host Name Wizard {SAP Note: 1320707}{Make sure you check the host names for integration server and SLD}
 25. Create RFC destination in to ERP target system (SM59)
 a. Give Name PI_INTEGRATIONSERVER
 b. Connection type H
 c. In Technical settings TAB provide
 i. Target host = hostname.domain.ext
 ii. Path Prefix = /sap/xi/engine/?type=entry
 iii. User information is blank
 26. Setting SXMB_ADM ERP target system
 a. Open Integration engine configuration
 b. Goto -> Change Global Configuration Data
 c. Role of Business system = Application System {This is optional}
 d. Provide RFC destination name in Corresponding Integ. Server = dest://PI_INTEGRATIONSERVER
 27. Schedule Standard Jobs as SAPADM in client X00.
 28. SICF service to activate
 a. /default_host/sap/public/bc/pictograms
 b. /default_host/sap/public/bc/webicons
 c. /default_host/sap/public/bc/its/designs
 d. /default_host/sap/public/bc/workflow
 e. /default_host/sap/bc/ccms
 f. /default_host/sap/bc/webdynpro/sap/CTS_BROWSER
 g. /default_host/sap/bc/webflow
 h. /default_host/sap/bc/workflow
 i. /default_host/sap/bc/workflow_xml
 j. /default_host/sap/bc/xmb
 k. /default_host/sap/bc/ping
 l. /default_host/sap/xi/wsdl_sr
 m. /default_host/sap/xi/wsdl_url
 n. /sap/bc/webdynpro/sap/appl_soap_management
 29. Adjusting JNLP Heap size
 a. Open the Exchange profile through the link u201Cadministrationu201D from the web page of the Process Integration tools.
 b. Under the folder u201CIntegration Builderu201D click on the variable u201Ccom.sap.aii.ib.clientjnlp.j2se.maxheapsizeu201D
 c. Value = 1024
 d. Save the change and restart the J2EE instance of PI so that the new value can take effect.
 30. Create RFC destination for Advanced Adaptor Engine in sender ERP system(SM59)
 a. RFC Destination = AAE_<SID>
 b. Connection type = G
 c. Target Host = Host Name of AAE Server {PI Server}
 d. Service No. u2013 HTTP port number of AAE Server
 e. Path Prefix = /XISOAPAdepter/MessageServlet?ximessage=true
 f. Under Logon & Security use PIAPPLUSER with PI target systemsu2019 master password.
 31. Create RFC destination <SID>_ALE in ERP Source system with user ERQALEUSER {Make sure you have this user created in new installed system}
 32. Install External Driver Configuration in Process Integration 7.1 Using JSPM {SAP NOTE: 1138877}
 
Please let me know if I am missing anything there...
 
Cheers,
 
Yogesh

Deploy java components error in NW7.4 installation

Hi Experts,
I am installing NW 7.4, i have done all the pre-installation steps but i am getting error at deploy java components.
please find the log. please help me in this it is very urgent. I need your experience.
An error occurred while processing option SAP NetWeaver 7.4 Support Release 2 > MaxDB > SAP Systems > Optional Standalone Units > Process Orchestration > Standard System > Process Integration and Orchestration Package( Last error reported by the step: Execution of Deploy Controller Runner tool '"C:\Program Files\sapinst_instdir\NW740SR2\ADA\INSTALL\STANDALONE\STD\PICP\sapjvm\sapjvm_6\bin\java.exe" -classpath "C:/Program Files/sapinst_instdir/NW740SR2/ADA/INSTALL/STANDALONE/STD/PICP/install/lib;\\PO/sapmnt/POP/SYS/global/security/lib/tools/iaik_jce.jar;\\PO/sapmnt/POP/SYS/global/security/lib/tools/iaik_jsse.jar;\\PO/sapmnt/POP/SYS/global/security/lib/tools/iaik_smime.jar;\\PO/sapmnt/POP/SYS/global/security/lib/tools/iaik_ssl.jar;\\PO/sapmnt/POP/SYS/global/security/lib/tools/w3c_http.jar;D:/usr/sap/POP/J00/j2ee/j2eeclient/sap.com~tc~exception~impl.jar;D:/usr/sap/POP/J00/j2ee/j2eeclient/sap.com~tc~je~clientlib~impl.jar;D:/usr/sap/POP/J00/j2ee/j2eeclient/sap.com~tc~logging~java~impl.jar;C:/Program Files/sapinst_instdir/NW740SR2/ADA/INSTALL/STANDALONE/STD/PICP/install/lib/tc~je~cl_deploy.jar" -Xmx256m -Ddc.api.verbose=false com.sap.engine.services.dc.api.cmd.Runner deploy -l "C:\Program Files\sapinst_instdir\NW740SR2\ADA\INSTALL\STANDALONE\STD\PICP\deploy.lst" -e stop -u lower -w safety --lcm bulk -t 14400000 --host PO --port 50004' aborts with return code 104. Error message is 'Component:BI_UDI ( sap.com) Status:Aborted Description:. SOLUTION: Check 'C:\Program Files\sapinst_instdir\NW740SR2\ADA\INSTALL\STANDALONE\STD\PICP\log\dc_log\deploy_api.0.log' and 'deploycontroller.log' for more information.). You can now:
Choose Retry to repeat the current step.
Choose Log Files to get more information about the error.
Stop the option and continue later.
Log files are written to C:\Program Files/sapinst_instdir/NW740SR2/ADA/INSTALL/STANDALONE/STD/PICP.
Regards,
Patan Thavaheer.

Hi manu,
Please find the error log.
[ Error ] Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
[ LOG EXCEPTION ] :: Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
javax.naming.NamingException: Exception during getInitialContext operation. Cannot establish connection to the remote server. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]
at com.sap.engine.services.jndi.InitialContextFactoryImpl.handleConnectionPropblem(InitialContextFactoryImpl.java:416)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:338)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at com.sap.engine.services.dc.api.session.impl.SessionImpl.getContext(SessionImpl.java:215)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.reconnectDeployer(DeployProcessorImpl.java:1954)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.waitResultForOfflineDeploy(DeployProcessorImpl.java:1626)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:903)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:259)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.performOperation(DeployCommand.java:208)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.executeCommand(DeployCommand.java:540)
at com.sap.engine.services.dc.api.cmd.AbstractCommand.execute(AbstractCommand.java:197)
at com.sap.engine.services.dc.api.cmd.Runner.execute(Runner.java:37)
at com.sap.engine.services.dc.api.cmd.Runner.main(Runner.java:61)
Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.
at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:164)
at com.sap.engine.services.jndi.implclient.LoginHelper.clientSideLogin(LoginHelper.java:79)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:315)
... 14 more
Caused by: com.sap.engine.services.rmi_p4.P4IOException: No alive connection. Check state of the server
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:828)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:813)
at com.sap.engine.services.rmi_p4.ClientConnection.sendRequest(ClientConnection.java:362)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.resolveInitialReference(P4ObjectBrokerClientImpl.java:123)
at com.sap.engine.services.rmi_p4.RemoteBroker.resolveInitialReference(RemoteBroker.java:41)
at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:153)
... 16 more
[ Error ] Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
[ Info ] +++ Wait for server response +++. Deploying offline [31] seconds. Will timeout in [14,368] seconds.
[ LOG EXCEPTION ] :: Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
javax.naming.NamingException: Exception during getInitialContext operation. Cannot establish connection to the remote server. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]
at com.sap.engine.services.jndi.InitialContextFactoryImpl.handleConnectionPropblem(InitialContextFactoryImpl.java:416)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:338)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at com.sap.engine.services.dc.api.session.impl.SessionImpl.getContext(SessionImpl.java:215)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.reconnectDeployer(DeployProcessorImpl.java:1954)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.waitResultForOfflineDeploy(DeployProcessorImpl.java:1626)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:903)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:259)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.performOperation(DeployCommand.java:208)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.executeCommand(DeployCommand.java:540)
at com.sap.engine.services.dc.api.cmd.AbstractCommand.execute(AbstractCommand.java:197)
at com.sap.engine.services.dc.api.cmd.Runner.execute(Runner.java:37)
at com.sap.engine.services.dc.api.cmd.Runner.main(Runner.java:61)
Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.
at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:164)
at com.sap.engine.services.jndi.implclient.LoginHelper.clientSideLogin(LoginHelper.java:79)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:315)
... 14 more
Caused by: com.sap.engine.services.rmi_p4.P4IOException: No alive connection. Check state of the server
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:828)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:813)
at com.sap.engine.services.rmi_p4.ClientConnection.sendRequest(ClientConnection.java:362)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.resolveInitialReference(P4ObjectBrokerClientImpl.java:123)
at com.sap.engine.services.rmi_p4.RemoteBroker.resolveInitialReference(RemoteBroker.java:41)
at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:153)
... 16 more
[ Error ] Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
[ LOG EXCEPTION ] :: Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
javax.naming.NamingException: Exception during getInitialContext operation. Cannot establish connection to the remote server. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]
at com.sap.engine.services.jndi.InitialContextFactoryImpl.handleConnectionPropblem(InitialContextFactoryImpl.java:416)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:338)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at com.sap.engine.services.dc.api.session.impl.SessionImpl.getContext(SessionImpl.java:215)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.reconnectDeployer(DeployProcessorImpl.java:1954)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.waitResultForOfflineDeploy(DeployProcessorImpl.java:1626)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:903)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:259)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.performOperation(DeployCommand.java:208)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.executeCommand(DeployCommand.java:540)
at com.sap.engine.services.dc.api.cmd.AbstractCommand.execute(AbstractCommand.java:197)
at com.sap.engine.services.dc.api.cmd.Runner.execute(Runner.java:37)
at com.sap.engine.services.dc.api.cmd.Runner.main(Runner.java:61)
Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.
at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:164)
at com.sap.engine.services.jndi.implclient.LoginHelper.clientSideLogin(LoginHelper.java:79)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:315)
... 14 more
Caused by: com.sap.engine.services.rmi_p4.P4IOException: No alive connection. Check state of the server
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:828)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:813)
at com.sap.engine.services.rmi_p4.ClientConnection.sendRequest(ClientConnection.java:362)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.resolveInitialReference(P4ObjectBrokerClientImpl.java:123)
at com.sap.engine.services.rmi_p4.RemoteBroker.resolveInitialReference(RemoteBroker.java:41)
at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:153)
... 16 more
[ Error ] Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
[ LOG EXCEPTION ] :: Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
javax.naming.NamingException: Exception during getInitialContext operation. Cannot establish connection to the remote server. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]
at com.sap.engine.services.jndi.InitialContextFactoryImpl.handleConnectionPropblem(InitialContextFactoryImpl.java:416)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:338)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at com.sap.engine.services.dc.api.session.impl.SessionImpl.getContext(SessionImpl.java:215)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.reconnectDeployer(DeployProcessorImpl.java:1954)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.waitResultForOfflineDeploy(DeployProcessorImpl.java:1626)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:903)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:259)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.performOperation(DeployCommand.java:208)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.executeCommand(DeployCommand.java:540)
at com.sap.engine.services.dc.api.cmd.AbstractCommand.execute(AbstractCommand.java:197)
at com.sap.engine.services.dc.api.cmd.Runner.execute(Runner.java:37)
at com.sap.engine.services.dc.api.cmd.Runner.main(Runner.java:61)
Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.
at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:164)
at com.sap.engine.services.jndi.implclient.LoginHelper.clientSideLogin(LoginHelper.java:79)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:315)
... 14 more
Caused by: com.sap.engine.services.rmi_p4.P4IOException: No alive connection. Check state of the server
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:828)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:813)
at com.sap.engine.services.rmi_p4.ClientConnection.sendRequest(ClientConnection.java:362)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.resolveInitialReference(P4ObjectBrokerClientImpl.java:123)
at com.sap.engine.services.rmi_p4.RemoteBroker.resolveInitialReference(RemoteBroker.java:41)
at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:153)
... 16 more
[ Error ] Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
[ LOG EXCEPTION ] :: Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
javax.naming.NamingException: Exception during getInitialContext operation. Cannot establish connection to the remote server. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]
at com.sap.engine.services.jndi.InitialContextFactoryImpl.handleConnectionPropblem(InitialContextFactoryImpl.java:416)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:338)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at com.sap.engine.services.dc.api.session.impl.SessionImpl.getContext(SessionImpl.java:215)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.reconnectDeployer(DeployProcessorImpl.java:1954)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.waitResultForOfflineDeploy(DeployProcessorImpl.java:1626)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:903)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:259)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.performOperation(DeployCommand.java:208)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.executeCommand(DeployCommand.java:540)
at com.sap.engine.services.dc.api.cmd.AbstractCommand.execute(AbstractCommand.java:197)
at com.sap.engine.services.dc.api.cmd.Runner.execute(Runner.java:37)
at com.sap.engine.services.dc.api.cmd.Runner.main(Runner.java:61)
Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.
at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:164)
at com.sap.engine.services.jndi.implclient.LoginHelper.clientSideLogin(LoginHelper.java:79)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:315)
... 14 more
Caused by: com.sap.engine.services.rmi_p4.P4IOException: No alive connection. Check state of the server
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:828)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:813)
at com.sap.engine.services.rmi_p4.ClientConnection.sendRequest(ClientConnection.java:362)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.resolveInitialReference(P4ObjectBrokerClientImpl.java:123)
at com.sap.engine.services.rmi_p4.RemoteBroker.resolveInitialReference(RemoteBroker.java:41)
at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:153)
... 16 more
[ Error ] Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
[ LOG EXCEPTION ] :: Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
javax.naming.NamingException: Exception during getInitialContext operation. Cannot establish connection to the remote server. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]
at com.sap.engine.services.jndi.InitialContextFactoryImpl.handleConnectionPropblem(InitialContextFactoryImpl.java:416)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:338)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at com.sap.engine.services.dc.api.session.impl.SessionImpl.getContext(SessionImpl.java:215)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.reconnectDeployer(DeployProcessorImpl.java:1954)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.waitResultForOfflineDeploy(DeployProcessorImpl.java:1626)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:903)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:259)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.performOperation(DeployCommand.java:208)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.executeCommand(DeployCommand.java:540)
at com.sap.engine.services.dc.api.cmd.AbstractCommand.execute(AbstractCommand.java:197)
at com.sap.engine.services.dc.api.cmd.Runner.execute(Runner.java:37)
at com.sap.engine.services.dc.api.cmd.Runner.main(Runner.java:61)
Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.
at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:164)
at com.sap.engine.services.jndi.implclient.LoginHelper.clientSideLogin(LoginHelper.java:79)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:315)
... 14 more
Caused by: com.sap.engine.services.rmi_p4.P4IOException: No alive connection. Check state of the server
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:828)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:813)
at com.sap.engine.services.rmi_p4.ClientConnection.sendRequest(ClientConnection.java:362)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.resolveInitialReference(P4ObjectBrokerClientImpl.java:123)
at com.sap.engine.services.rmi_p4.RemoteBroker.resolveInitialReference(RemoteBroker.java:41)
at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:153)
... 16 more
[ Error ] Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
[ LOG EXCEPTION ] :: Could not establish connection to AS Java on [PO:50004]. End of stream is reached unexpectedly during input from Socket[addr=/192.168.2.87,port=50004,localport=50597]. Check if the host and port specified are correct and AS Java is up and running.
javax.naming.NamingException: Exception during getInitialContext operation. Cannot establish connection to the remote server. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]
at com.sap.engine.services.jndi.InitialContextFactoryImpl.handleConnectionPropblem(InitialContextFactoryImpl.java:416)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:338)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at com.sap.engine.services.dc.api.session.impl.SessionImpl.getContext(SessionImpl.java:215)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.reconnectDeployer(DeployProcessorImpl.java:1954)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.waitResultForOfflineDeploy(DeployProcessorImpl.java:1626)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:903)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:259)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.performOperation(DeployCommand.java:208)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.executeCommand(DeployCommand.java:540)
at com.sap.engine.services.dc.api.cmd.AbstractCommand.execute(AbstractCommand.java:197)
at com.sap.engine.services.dc.api.cmd.Runner.execute(Runner.java:37)
at com.sap.engine.services.dc.api.cmd.Runner.main(Runner.java:61)
Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.
at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:164)
at com.sap.engine.services.jndi.implclient.LoginHelper.clientSideLogin(LoginHelper.java:79)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:315)
... 14 more
Caused by: java.io.EOFException: End of stream is reached unexpectedly during input from Socket[addr=/192.168.2.87,port=50004,localport=50597]
at com.sap.engine.services.rmi_p4.ClientConnection.run(ClientConnection.java:501)
at java.lang.Thread.run(Thread.java:763)
[ Error ] Could not establish connection to AS Java on [PO:50004]. End of stream is reached unexpectedly during input from Socket[addr=/192.168.2.87,port=50004,localport=50597]. Check if the host and port specified are correct and AS Java is up and running.
[ LOG EXCEPTION ] :: Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
javax.naming.NamingException: Exception during getInitialContext operation. Cannot establish connection to the remote server. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]
at com.sap.engine.services.jndi.InitialContextFactoryImpl.handleConnectionPropblem(InitialContextFactoryImpl.java:416)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:338)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at com.sap.engine.services.dc.api.session.impl.SessionImpl.getContext(SessionImpl.java:215)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.reconnectDeployer(DeployProcessorImpl.java:1954)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.waitResultForOfflineDeploy(DeployProcessorImpl.java:1626)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:903)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:259)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.performOperation(DeployCommand.java:208)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.executeCommand(DeployCommand.java:540)
at com.sap.engine.services.dc.api.cmd.AbstractCommand.execute(AbstractCommand.java:197)
at com.sap.engine.services.dc.api.cmd.Runner.execute(Runner.java:37)
at com.sap.engine.services.dc.api.cmd.Runner.main(Runner.java:61)
Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.
at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:164)
at com.sap.engine.services.jndi.implclient.LoginHelper.clientSideLogin(LoginHelper.java:79)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:315)
... 14 more
Caused by: com.sap.engine.services.rmi_p4.P4IOException: No alive connection. Check state of the server
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:828)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:813)
at com.sap.engine.services.rmi_p4.ClientConnection.sendRequest(ClientConnection.java:362)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.resolveInitialReference(P4ObjectBrokerClientImpl.java:123)
at com.sap.engine.services.rmi_p4.RemoteBroker.resolveInitialReference(RemoteBroker.java:41)
at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:153)
... 16 more
[ Error ] Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
[ LOG EXCEPTION ] :: Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
javax.naming.NamingException: Exception during getInitialContext operation. Cannot establish connection to the remote server. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]
at com.sap.engine.services.jndi.InitialContextFactoryImpl.handleConnectionPropblem(InitialContextFactoryImpl.java:416)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:338)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at com.sap.engine.services.dc.api.session.impl.SessionImpl.getContext(SessionImpl.java:215)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.reconnectDeployer(DeployProcessorImpl.java:1954)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.waitResultForOfflineDeploy(DeployProcessorImpl.java:1626)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:903)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:259)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.performOperation(DeployCommand.java:208)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.executeCommand(DeployCommand.java:540)
at com.sap.engine.services.dc.api.cmd.AbstractCommand.execute(AbstractCommand.java:197)
at com.sap.engine.services.dc.api.cmd.Runner.execute(Runner.java:37)
at com.sap.engine.services.dc.api.cmd.Runner.main(Runner.java:61)
Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.
at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:164)
at com.sap.engine.services.jndi.implclient.LoginHelper.clientSideLogin(LoginHelper.java:79)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:315)
... 14 more
Caused by: com.sap.engine.services.rmi_p4.P4IOException: No alive connection. Check state of the server
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:828)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:813)
at com.sap.engine.services.rmi_p4.ClientConnection.sendRequest(ClientConnection.java:362)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.resolveInitialReference(P4ObjectBrokerClientImpl.java:123)
at com.sap.engine.services.rmi_p4.RemoteBroker.resolveInitialReference(RemoteBroker.java:41)
at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:153)
... 16 more
[ Error ] Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
[ Info ] +++ Wait for server response +++. Deploying offline [48] seconds. Will timeout in [14,351] seconds.
[ LOG EXCEPTION ] :: Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
javax.naming.NamingException: Exception during getInitialContext operation. Cannot establish connection to the remote server. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]
at com.sap.engine.services.jndi.InitialContextFactoryImpl.handleConnectionPropblem(InitialContextFactoryImpl.java:416)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:338)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at com.sap.engine.services.dc.api.session.impl.SessionImpl.getContext(SessionImpl.java:215)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.reconnectDeployer(DeployProcessorImpl.java:1954)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.waitResultForOfflineDeploy(DeployProcessorImpl.java:1626)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:903)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:259)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.performOperation(DeployCommand.java:208)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.executeCommand(DeployCommand.java:540)
at com.sap.engine.services.dc.api.cmd.AbstractCommand.execute(AbstractCommand.java:197)
at com.sap.engine.services.dc.api.cmd.Runner.execute(Runner.java:37)
at com.sap.engine.services.dc.api.cmd.Runner.main(Runner.java:61)
Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.
at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:164)
at com.sap.engine.services.jndi.implclient.LoginHelper.clientSideLogin(LoginHelper.java:79)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:315)
... 14 more
Caused by: com.sap.engine.services.rmi_p4.P4IOException: No alive connection. Check state of the server
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:828)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:813)
at com.sap.engine.services.rmi_p4.ClientConnection.sendRequest(ClientConnection.java:362)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.resolveInitialReference(P4ObjectBrokerClientImpl.java:123)
at com.sap.engine.services.rmi_p4.RemoteBroker.resolveInitialReference(RemoteBroker.java:41)
at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:153)
... 16 more
[ Error ] Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
[ LOG EXCEPTION ] :: Could not establish connection to AS Java on [PO:50004]. End of stream is reached unexpectedly during input from Socket[addr=/192.168.2.87,port=50004,localport=50615]. Check if the host and port specified are correct and AS Java is up and running.
javax.naming.NamingException: Exception during getInitialContext operation. Cannot establish connection to the remote server. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]
at com.sap.engine.services.jndi.InitialContextFactoryImpl.handleConnectionPropblem(InitialContextFactoryImpl.java:416)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:338)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at com.sap.engine.services.dc.api.session.impl.SessionImpl.getContext(SessionImpl.java:215)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.reconnectDeployer(DeployProcessorImpl.java:1954)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.waitResultForOfflineDeploy(DeployProcessorImpl.java:1626)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:903)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:259)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.performOperation(DeployCommand.java:208)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.executeCommand(DeployCommand.java:540)
at com.sap.engine.services.dc.api.cmd.AbstractCommand.execute(AbstractCommand.java:197)
at com.sap.engine.services.dc.api.cmd.Runner.execute(Runner.java:37)
at com.sap.engine.services.dc.api.cmd.Runner.main(Runner.java:61)
Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.
at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:164)
at com.sap.engine.services.jndi.implclient.LoginHelper.clientSideLogin(LoginHelper.java:79)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:315)
... 14 more
Caused by: java.io.EOFException: End of stream is reached unexpectedly during input from Socket[addr=/192.168.2.87,port=50004,localport=50615]
at com.sap.engine.services.rmi_p4.ClientConnection.run(ClientConnection.java:501)
at java.lang.Thread.run(Thread.java:763)
[ Error ] Could not establish connection to AS Java on [PO:50004]. End of stream is reached unexpectedly during input from Socket[addr=/192.168.2.87,port=50004,localport=50615]. Check if the host and port specified are correct and AS Java is up and running.
[ LOG EXCEPTION ] :: Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
javax.naming.NamingException: Exception during getInitialContext operation. Cannot establish connection to the remote server. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]
at com.sap.engine.services.jndi.InitialContextFactoryImpl.handleConnectionPropblem(InitialContextFactoryImpl.java:416)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:338)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at com.sap.engine.services.dc.api.session.impl.SessionImpl.getContext(SessionImpl.java:215)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.reconnectDeployer(DeployProcessorImpl.java:1954)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.waitResultForOfflineDeploy(DeployProcessorImpl.java:1626)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:903)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:259)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.performOperation(DeployCommand.java:208)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.executeCommand(DeployCommand.java:540)
at com.sap.engine.services.dc.api.cmd.AbstractCommand.execute(AbstractCommand.java:197)
at com.sap.engine.services.dc.api.cmd.Runner.execute(Runner.java:37)
at com.sap.engine.services.dc.api.cmd.Runner.main(Runner.java:61)
Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.
at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:164)
at com.sap.engine.services.jndi.implclient.LoginHelper.clientSideLogin(LoginHelper.java:79)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:315)
... 14 more
Caused by: com.sap.engine.services.rmi_p4.P4IOException: No alive connection. Check state of the server
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:828)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:813)
at com.sap.engine.services.rmi_p4.ClientConnection.sendRequest(ClientConnection.java:362)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.resolveInitialReference(P4ObjectBrokerClientImpl.java:123)
at com.sap.engine.services.rmi_p4.RemoteBroker.resolveInitialReference(RemoteBroker.java:41)
at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:153)
... 16 more
[ Error ] Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
[ LOG EXCEPTION ] :: Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
javax.naming.NamingException: Exception during getInitialContext operation. Cannot establish connection to the remote server. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]
at com.sap.engine.services.jndi.InitialContextFactoryImpl.handleConnectionPropblem(InitialContextFactoryImpl.java:416)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:338)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at com.sap.engine.services.dc.api.session.impl.SessionImpl.getContext(SessionImpl.java:215)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.reconnectDeployer(DeployProcessorImpl.java:1954)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.waitResultForOfflineDeploy(DeployProcessorImpl.java:1626)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:903)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:259)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.performOperation(DeployCommand.java:208)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.executeCommand(DeployCommand.java:540)
at com.sap.engine.services.dc.api.cmd.AbstractCommand.execute(AbstractCommand.java:197)
at com.sap.engine.services.dc.api.cmd.Runner.execute(Runner.java:37)
at com.sap.engine.services.dc.api.cmd.Runner.main(Runner.java:61)
Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.
at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:164)
at com.sap.engine.services.jndi.implclient.LoginHelper.clientSideLogin(LoginHelper.java:79)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:315)
... 14 more
Caused by: com.sap.engine.services.rmi_p4.P4IOException: No alive connection. Check state of the server
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:828)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:813)
at com.sap.engine.services.rmi_p4.ClientConnection.sendRequest(ClientConnection.java:362)
at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.resolveInitialReference(P4ObjectBrokerClientImpl.java:123)
at com.sap.engine.services.rmi_p4.RemoteBroker.resolveInitialReference(RemoteBroker.java:41)
at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:153)
... 16 more
[ Error ] Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
[ Info ] +++ Deployment of session ID [21] finished with status [Error] +++. [[ deployerId=1 ]] [[#3: 340.111 sec]] [
===== Summary - Deploy Result - Start =====
Type | Status : Count
> SCA(s)
 - [Aborted] : [80]
> SDA(s)
 - [Success] : [80]
 - [Admitted] : [1189]
Type | Status : Id
> SCA(s)
 - [Aborted] : name: 'BI_UDI', vendor: 'sap.com', name: 'COMP_BUILDT', vendor: 'sap.com', name: 'CU-BASE-JAVA', vendor: 'sap.com', name: 'CU-BASE-WD', vendor: 'sap.com', name: 'DATA-MAPPING', vendor: 'sap.com', name: 'ECM-CORE', vendor: 'sap.com', name: 'ESCONF_BUILDT', vendor: 'sap.com', name: 'ESMP_BUILDT', vendor: 'sap.com', name: 'LM-TOOLS', vendor: 'sap.com', name: 'MMR_SERVER', vendor: 'sap.com', name: 'MOIN_BUILDT', vendor: 'sap.com', name: 'NWTEC', vendor: 'sap.com', name: 'EP-BASIS', vendor: 'sap.com', name: 'SERVICE-COMP', vendor: 'sap.com', name: 'SWLIFECYCL', vendor: 'sap.com', name: 'UKMS_JAVA', vendor: 'sap.com', name: 'KM-KW_JIKS', vendor: 'sap.com', name: 'INTG_VIS', vendor: 'sap.com', name: 'SAP_XIADMIN', vendor: 'sap.com', name: 'SAP_XITOOL', vendor: 'sap.com', name: 'PI-SCP-EXT', vendor: 'sap.com', name: 'PI-SCP-BUILDT', vendor: 'sap.com', name: 'BPEM-CORE', vendor: 'sap.com', name: 'BPEM-FACADE', vendor: 'sap.com', name: 'BPEM-COLLAB', vendor: 'sap.com', name: 'BPEM-BASE', vendor: 'sap.com', name: 'BPEM-BUILDT', vendor: 'sap.com', name: 'BPEM-CONTENT', vendor: 'sap.com', name: 'BPEM-HIM', vendor: 'sap.com', name: 'BPEM-MM', vendor: 'sap.com', name: 'BPEM-MON', vendor: 'sap.com', name: 'BPEM-PP', vendor: 'sap.com', name: 'BPEM-WDUI', vendor: 'sap.com', name: 'BPEM-CUUI', vendor: 'sap.com', name: 'BRMS-BASE', vendor: 'sap.com', name: 'BRMS-BUILDT', vendor: 'sap.com', name: 'BRMS-CORE', vendor: 'sap.com', name: 'BRMS-FACADE', vendor: 'sap.com', name: 'BRMS-WDUI', vendor: 'sap.com', name: 'BRMS-MON', vendor: 'sap.com', name: 'FP-INFRA', vendor: 'sap.com', name: 'CU-BASE-WD-EXT', vendor: 'sap.com', name: 'TM-WLUI', vendor: 'sap.com', name: 'BPEM-ACC', vendor: 'sap.com', name: 'CAF-MF', vendor: 'sap.com', name: 'CAF-UI', vendor: 'sap.com', name: 'COLLAB-ADP', vendor: 'sap.com', name: 'CAF', vendor: 'sap.com', name: 'BI-BASE-S', vendor: 'sap.com', name: 'BI-BASE-B', vendor: 'sap.com', name: 'BI-BASE-E', vendor: 'sap.com', name: 'SEA-CORE', vendor: 'sap.com', name: 'SEA-FACADE', vendor: 'sap.com', name: 'SEA-UI', vendor: 'sap.com', name: 'BI-WDEXT', vendor: 'sap.com', name: 'CU-WD4VC-ADPT', vendor: 'sap.com', name: 'ECM-APPS', vendor: 'sap.com', name: 'ECM-STORE', vendor: 'sap.com', name: 'EP-ADMIN', vendor: 'sap.com', name: 'EP_BUILDT', vendor: 'sap.com', name: 'EP-CONNECTIVITY', vendor: 'sap.com', name: 'EP-MODELING', vendor: 'sap.com', name: 'EP-RUNTIME', vendor: 'sap.com', name: 'UWLJWF', vendor: 'sap.com', name: 'VCFREESTYLEKIT', vendor: 'sap.com', name: 'VCCORERT', vendor: 'sap.com', name: 'VCBASE', vendor: 'sap.com', name: 'VCKITBI', vendor: 'sap.com', name: 'VCFRAMEWORK', vendor: 'sap.com', name: 'VTP_BUILDT', vendor: 'sap.com', name: 'WDEXTENSIONS', vendor: 'sap.com', name: 'WD-FLEX', vendor: 'sap.com', name: 'ECM-ADMIN', vendor: 'sap.com', name: 'ECM-JEE-COMP', vendor: 'sap.com', name: 'SAP_XIESR', vendor: 'sap.com', name: 'SAP_XIGUILIB', vendor: 'sap.com', name: 'XI_CNT_SAP_BASIS', vendor: 'sap.com', name: 'INTG_VIS_DCJ', vendor: 'sap.com', name: 'SAP_XIAF', vendor: 'sap.com', name: 'SOAMON', vendor: 'sap.com',
> SDA(s)
 - [Success] : name: 'com.sap.ip.bi.sdk.dac.connector.odbodll', vendor: 'sap.com', name: 'com.sap.glx.mapping.lib', vendor: 'sap.com', name: 'com.sap.glx.common.rt.lib', vendor: 'sap.com', name: 'tc~lm~ctc~confs~service_sda', vendor: 'sap.com', name: 'bi~mmr~dictionary', vendor: 'sap.com', name: 'bi~mmr~deployer', vendor: 'sap.com', name: 'com.sap.portal.pcm.indexingservice', vendor: 'sap.com', name: 'com.sap.netweaver.rtmf.server', vendor: 'sap.com', name: 'tc~rtmf~service', vendor: 'sap.com', name: 'com.sap.aii.sca.xi.svc', vendor: 'sap.com', name: 'com.sap.aii.sca.maas.svc', vendor: 'sap.com', name: 'tc~bpem~eventlog~ddic', vendor: 'sap.com', name: 'com.sap.glx.base.lib', vendor: 'sap.com', name: 'com.sap.glx.container.dbschema', vendor: 'sap.com', name: 'com.sap.glx.rrhandlermanager.svc', vendor: 'sap.com', name: 'com.sap.glx.repository.handler.dbschema', vendor: 'sap.com', name: 'com.sap.glx.core.svc', vendor: 'sap.com', name: 'com.sap.glx.contextcontainer.dbschema', vendor: 'sap.com', name: 'com.sap.glx.core.dbschema', vendor: 'sap.com', name: 'com.sap.glx.core.svc.facade', vendor: 'sap.com', name: 'tc~bpem~index~ddic', vendor: 'sap.com', name: 'tc~bpem~base~svc', vendor: 'sap.com', name: 'com.sap.glx.repository.dbschema', vendor: 'sap.com', name: 'tc~bpem~bl~lib', vendor: 'sap.com', name: 'tc~bpem~base~type~plib', vendor: 'sap.com', name: 'com.sap.glx.repository.ifc', vendor: 'sap.com', name: 'com.sap.glx.repository.svc', vendor: 'sap.com', name: 'tc~bpem~base~lib', vendor: 'sap.com', name: 'tc~bpem~tm~ddic', vendor: 'sap.com', name: 'tc~bpem~shared~lib', vendor: 'sap.com', name: 'tc~brms~engine~lib', vendor: 'sap.com', name: 'tc~brms~ws~svc', vendor: 'sap.com', name: 'tc~brms~repository~svc', vendor: 'sap.com', name: 'tc~brms~io~plib', vendor: 'sap.com', name: 'tc~brms~acl~plib', vendor: 'sap.com', name: 'tc~brms~ddic', vendor: 'sap.com', name: 'tc~brms~wdui~plib', vendor: 'sap.com', name: 'caf~um~relgroups~ddic', vendor: 'sap.com', name: 'tc~esi~sea~schema~ddic', vendor: 'sap.com', name: 'tc~esi~sea~service', vendor: 'sap.com', name: 'tc~esi~sea~api~lib', vendor: 'sap.com', name: 'com.sap.portal.healthChecks', vendor: 'sap.com', name: 'com.sap.portal.fpn.migration.fpnmigrationlib', vendor: 'sap.com', name: 'com.sap.portal.landscape.config', vendor: 'sap.com', name: 'tc~pp~gpal~deploylistener', vendor: 'sap.com', name: 'com.sap.portal.fpn.service', vendor: 'sap.com', name: 'com.sap.portal.smart.smartsrv', vendor: 'sap.com', name: 'com.sap.obn.migration.obnmigrationlib', vendor: 'sap.com', name: 'tc~kmc~bc.uwl~api', vendor: 'sap.com', name: 'devserver_lib', vendor: 'sap.com', name: 'vc_ds_service', vendor: 'sap.com', name: 'vc_generation', vendor: 'sap.com', name: 'ds_repository', vendor: 'sap.com', name: 'ds_environment', vendor: 'sap.com', name: 'visualcomposer_server_api', vendor: 'sap.com', name: 'SAPMetamodelFW', vendor: 'sap.com', name: 'SAPBuildPluginHandler', vendor: 'sap.com', name: 'tc~ecm~svc~deploy', vendor: 'sap.com', name: 'com.sap.aii.adapter.rfc.svc', vendor: 'sap.com', name: 'com.sap.aii.adapter.ispeak.svc', vendor: 'sap.com', name: 'com.sap.aii.af.maas.lib', vendor: 'sap.com', name: 'com.sap.aii.af.ifc.facade', vendor: 'sap.com', name: 'com.sap.aii.adapter.marketplace.lib', vendor: 'sap.com', name: 'com.sap.aii.adapter.jdbc.svc', vendor: 'sap.com', name: 'com.sap.aii.adapter.bc.svc', vendor: 'sap.com', name: 'com.sap.aii.af.int.svc.facade', vendor: 'sap.com', name: 'com.sap.aii.af.svc.facade', vendor: 'sap.com', name: 'com.sap.aii.mapping.lib.facade', vendor: 'sap.com', name: 'com.sap.aii.adapter.file.svc', vendor: 'sap.com', name: 'com.sap.aii.af.lib.facade', vendor: 'sap.com', name: 'com.sap.aii.proxy.svc.facade', vendor: 'sap.com', name: 'com.sap.aii.adapter.marketplace.svc', vendor: 'sap.com', name: 'com.sap.aii.adapter.ispeak.dbs', vendor: 'sap.com', name: 'com.sap.aii.adapter.mail.svc', vendor: 'sap.com', name: 'com.sap.aii.adapter.ws.cxf.lib', vendor: 'sap.com', name: 'com.sap.aii.proxy.svc', vendor: 'sap.com', name: 'com.sap.aii.adapter.xi.svc', vendor: 'sap.com', name: 'com.sap.aii.adapter.http.svc', vendor: 'sap.com', name: 'com.sap.aii.adapter.jms.svc', vendor: 'sap.com', name: 'com.sap.aii.af.axis.lib', vendor: 'sap.com',
 - [Admitted] : name: 'com.sap.ip.bi.sdk.monitoring', vendor: 'sap.com', name: 'bi~sdk~resultset', vendor: 'sap.com', name: 'com.sap.ip.bi.sdk.dac.connector.checks', vendor: 'sap.com', name: 'com.sap.ip.bi.sdk.dac.connector.checko', vendor: 'sap.com', name: 'com.sap.ip.bi.sdk.dac.connector.xmla.x', vendor: 'sap.com', name: 'com.sap.ip.bi.sdk.dac.connector.jdbc', vendor: 'sap.com', name: 'tc~bi~sdk', vendor: 'sap.com', name: 'com.sap.ip.bi.sdk', vendor: 'sap.com', name: 'com.sap.ip.bi.sdk.datasource.ds', vendor: 'sap.com', name: 'com.sap.ip.bi.sdk.datasource.fields', vendor: 'sap.com', name: 'com.sap.ip.bi.sdk.dac.connector.java', vendor: 'sap.com', name: 'bi~sdk~core', vendor: 'sap.com', name: 'com.sap.ip.bi.sdk.datasource.sys', vendor: 'sap.com', name: 'bi~sdk~query', vendor: 'sap.com', name: 'com.sap.ip.bi.sdk.datasource.sync', vendor: 'sap.com', name: 'com.sap.ip.bi.sdk.dac.connector.checkj', vendor: 'sap.com', name: 'com.sap.ip.bi.sdk.dac.connector.xmla', vendor: 'sap.com', name: 'com.sap.ip.bi.sdk.dac.connector.checkx', vendor: 'sap.com', name: 'com.sap.ip.bi.sdk.dac.connector.odbo', vendor: 'sap.com', name: 'sc~bi_udi', vendor: 'sap.com', name: 'com.sap.ip.bi.sdk.dac.connector.sapq', vendor: 'sap.com', name: 'sc~comp_buildt', vendor: 'sap.com', name: 'sc~cu-base-java', vendor: 'sap.com', name: 'tc~cu~base~java~ear', vendor: 'sap.com', name: 'tc~cu~base~wd~adapter~wd2wd~ps', vendor: 'sap.com', name: 'tc~cu~base~wd~core', vendor: 'sap.com', name: 'tc~cu~base~wd~adapter~wd2wd', vendor: 'sap.com', name: 'sc~cu-base-wd', vendor: 'sap.com', name: 'tc~cu~base~wd~intapi', vendor: 'sap.com', name: 'tc~cu~base~wd~utils', vendor: 'sap.com', name: 'tc~cu~base~wd~contract~ps', vendor: 'sap.com', name: 'sc~data-mapping', vendor: 'sap.com', name: 'tc~ecm~core', vendor: 'sap.com', name: 'sc~ecm-core', vendor: 'sap.com', name: 'tc~ecm', vendor: 'sap.com', name: 'sc~esconf_buildt', vendor: 'sap.com', name: 'sc~esmp_buildt', vendor: 'sap.com', name: 'tc~archtech~browser~viewer~model', vendor: 'sap.com', name: 'tc~lm~aci~apps~wd~ui~taskplnr', vendor: 'sap.com', name: 'tc~lm~aci~apps~wd~ui~processviewer', vendor: 'sap.com', name: 'tc~lm~itsam~lmr~app', vendor: 'sap.com', name: 'tc~bcf~prov~ddic', vendor: 'sap.com', name: 'tc~lm~ctc~nwa~initialsetuptables', vendor: 'sap.com', name: 'tc~lm~itsam~ui~ctc~wd', vendor: 'sap.com', name: 'tc~lm~aci~apps~wd~ui~master', vendor: 'sap.com', name: 'tc~lm~aci~engine~sapctrl~wsproxy', vendor: 'sap.com', name: 'tc~lm~aci~engine~ddic', vendor: 'sap.com', name: 'tc~slm~ui_maintain', vendor: 'sap.com', name: 'tc~archtech~browser_ume', vendor: 'sap.com', name: 'tc~slm~ui_jnet', vendor: 'sap.com', name: 'tc~lm~ctc~itsam~kpi', vendor: 'sap.com', name: 'tc~archtech~browser~viewer~defaultui', vendor: 'sap.com', name: 'tc~bcf~ws~ddic', vendor: 'sap.com', name: 'tc~lm~aci~vpm~wsproxy~sap', vendor: 'sap.com', name: 'tc~bcf~prov~wd', vendor: 'sap.com', name: 'tc~archtech~browser~viewer~compif', vendor: 'sap.com', name: 'tc~bcf~lib~ear', vendor: 'sap.com', name: 'tc~lm~itsam~ui~sys~overview~xi~wd', vendor: 'sap.com', name: 'tc~lm~aci~virtual~vmware~wsproxy', vendor: 'sap.com', name: 'tc~lm~aci~apps~wd~ui~resource', vendor: 'sap.com', name: 'tc~bcf_xi~ear', vendor: 'sap.com', name: 'tc~archtech~sbook_wd', vendor: 'sap.com', name: 'tc~lm~ctc~nwa~other_ear', vendor: 'sap.com', name: 'tc~lm~aci~apps~wd~ui~aclog', vendor: 'sap.com', name: 'tc~bcf~prov~ear', vendor: 'sap.com', name: 'tc~sec~sanity~jmx~sda', vendor: 'sap.com', name: 'tc~archtech~browser~viewer~locator', vendor: 'sap.com', name: 'tc~slm~ui_review', vendor: 'sap.com', name: 'tc~lm~aci~engine~csm~wsproxy', vendor: 'sap.com', name: 'tc~lm~aci~apps~wd~utils', vendor: 'sap.com', name: 'tc~archtech~browser~viewer~xmlui', vendor: 'sap.com', name: 'tc~lm~ctc~nwa~sldregisterapp', vendor: 'sap.com', name: 'sc~lm-tools', vendor: 'sap.com', name: 'tc~lm~aci~apps~wd~ui~services', vendor: 'sap.com', name: 'tc~lm~aci~apps~wd~ui~vpm', vendor: 'sap.com', name: 'tc~lm~ctc~confs~startup_app', vendor: 'sap.com', name: 'tc~lm~itsam~ui~overview~panel~interface', vendor: 'sap.com', name: 'tc~lm~itsam~ui~avail~panel', vendor: 'sap.com', name: 'tc~bcf~ws~ear', vendor: 'sap.com', name: 'tc~slm~ui_slm', vendor: 'sap.com', name: 'tc~lm~itsam~ui~thresholds~wd', vendor: 'sap.com', name: 'tc~lm~ctc~ccl~rep~hist~ddic', vendor: 'sap.com', name: 'tc~lm~aci~engine~archconfig', vendor: 'sap.com', name: 'tc~lm~itsam~ui~sysinfo', vendor: 'sap.com', name: 'tc~lm~aci~engine~hstctrl~wsproxy', vendor: 'sap.com', name: 'tc~lm~ctc~nwa~spc~config_ear', vendor: 'sap.com', name: 'tc~lm~aci~apps~wd~types', vendor: 'sap.com', name: 'tc~lm~aci~apps~wd~model', vendor: 'sap.com', name: 'tc~lm~aci~apps~wd~ui~overview', vendor: 'sap.com', name: 'tc~slm~ui_navigation', vendor: 'sap.com', name: 'tc~archtech~sbook_init_j2ee', vendor: 'sap.com', name: 'tc~bcf~prov~ddic~content', vendor: 'sap.com', name: 'tc~sld~destsvc_dic', vendor: 'sap.com', name: 'tc~bizc~ws~ear', vendor: 'sap.com', name: 'tc~archtech~browser', vendor: 'sap.com', name: 'tc~archtech~sbook_j2ee', vendor: 'sap.com', name: 'tc~sec~sanity~wd', vendor: 'sap.com', name: 'tc~lm~itsam~ui~nwso~cfg~db', vendor: 'sap.com', name: 'tc~lm~itsam~ui~perf~panel', vendor: 'sap.com', name: 'tc~archtech~browser~dbschema', vendor: 'sap.com', name: 'tc~bcf~transport~ddic', vendor: 'sap.com', name: 'tc~lm~aci~apps~wd~ui~acenable', vendor: 'sap.com', name: 'tc~lm~nzdm~crr~ui', vendor: 'sap.com', name: 'bi~mmr~mini_md_library', vendor: 'sap.com', name: 'bi~mmr~mini_mm_library', vendor: 'sap.com', name: 'bi~mmr~api', vendor: 'sap.com', name: 'bi~mmr~webToolsEAP', vendor: 'sap.com', name: 'bi~mmr~bi_library', vendor: 'sap.com', name: 'bi~mmr~bi_ear', vendor: 'sap.com', name: 'bi~mmr~mmrlib', vendor: 'sap.com', name: 'bi~mmr~reportmodel_library', vendor: 'sap.com', name: 'bi~mmr~cwm_1.0_library', vendor: 'sap.com', name: 'bi~mmr~reportmodel_ear', vendor: 'sap.com', name: 'bi~mmr~jnet', vendor: 'sap.com', name: 'bi~mmr~cwm_1.0_ear', vendor: 'sap.com', name: 'sc~mmr_server', vendor: 'sap.com', name: 'bi~mmr~mmrapplib', vendor: 'sap.com', name: 'bi~mmr~mof_1.4_library', vendor: 'sap.com', name: 'bi~mmr~amlib', vendor: 'sap.com', name: 'bi~mmr~mini_mm_ear', vendor: 'sap.com', name: 'bi~mmr~mini_md_ear', vendor: 'sap.com', name: 'bi~mmr~bi_repository', vendor: 'sap.com', name: 'bi~mmr~metamodel_library', vendor: 'sap.com', name: 'bi~mmr~mof_1.4_ear', vendor: 'sap.com', name: 'bi~mmr~ejb', vendor: 'sap.com', name: 'bi~mmr~metamodel_ear', vendor: 'sap.com', name: 'sc~moin_buildt', vendor: 'sap.com', name: 'sc~nwtec', vendor: 'sap.com', name: 'tc~di~sdic~support~wd', vendor: 'sap.com', name: 'com.sap.portal.supportability.isolde.api', vendor: 'sap.com', name: 'com.sap.portal.pcd.textrepository', vendor: 'sap.com', name: 'com.sap.portal.prt.cache', vendor: 'sap.com', name: 'com.sap.portal.htmlb', vendor: 'sap.com', name: 'tc~jpe~dbschema', vendor: 'sap.com', name: 'com.sap.portal.design.urdesigndataless', vendor: 'sap.com', name: 'com.sap.portal.pcm.admin.pcdimplservice', vendor: 'sap.com', name: 'com.sap.portal.runtime.system.notification', vendor: 'sap.com', name: 'sc~ep-basis', vendor: 'sap.com', name: 'com.sap.portal.runtime.system.clusterinformation', vendor: 'sap.com', name: 'com.sap.portal.runtime.application.contentconverter', vendor: 'sap.com', name: 'tc~epbc~pcd~pars~srvgl', vendor: 'sap.com', name: 'com.sap.portal.pcd.admintools.ucdadmin', vendor: 'sap.com', name: 'com.sap.portal.pcd.aclservice', vendor: 'sap.com', name: 'com.sap.portal.design.ui5designdataless', vendor: 'sap.com', name: 'com.sap.security.ume.consistencycheck', vendor: 'sap.com', name: 'com.sap.portal.pcd.admintools.configuration', vendor: 'sap.com', name: 'com.sap.portal.pcd.umwrapperservice', vendor: 'sap.com', name: 'tc~epbc~prt~apps~restricted', vendor: 'sap.com', name: 'rtmfcommunicator', vendor: 'sap.com', name: 'com.sap.portal.themes.lafservice', vendor: 'sap.com', name: 'tc~epbc~resourcerepository~api', vendor: 'sap.com', name: 'com.sap.portal.usermapping', vendor: 'sap.com', name: 'com.sap.portal.runtime.system.hooks', vendor: 'sap.com', name: 'com.sap.portal.runtime.system.authentication', vendor: 'sap.com', name: 'com.sap.portal.pcd.softcacheservice', vendor: 'sap.com', name: 'com.sap.portal.pcm.metadata.service', vendor: 'sap.com', name: 'tc~epbc~pcm~pcmadminimplsrv', vendor: 'sap.com', name: 'com.sap.portal.design.vc5designdataless', vendor: 'sap.com', name: 'com.sap.portal.pcd.basicrolefactory', vendor: 'sap.com', name: 'tc~supportplatform~wd', vendor: 'sap.com', name: 'com.sap.portal.design.portaldesigndata', vendor: 'sap.com', name: 'com.sap.portal.runtime.system.prtconnection', vendor: 'sap.com', name: 'com.sap.portal.runtime.prtws', vendor: 'sap.com', name: 'com.sap.portal.resourcerepository', vendor: 'sap.com', name: 'com.sap.portal.pcd.lockservice', vendor: 'sap.com', name: 'irj', vendor: 'sap.com', name: 'tc~epbc~prt~apps', vendor: 'sap.com', name: 'com.sap.portal.runtime.application.xsltransform', vendor: 'sap.com', name: 'com.sap.portal.pcd.traceservice', vendor: 'sap.com', name: 'tc~epbc~pcm~ext', vendor: 'sap.com', name: 'com.sap.portal.design.portaldesigndataless', vendor: 'sap.com', name: 'tc~rtmf~wdtestapp', vendor: 'sap.com', name: 'com.sap.portal.pcd.basictransport', vendor: 'sap.com', name: 'com.sap.portal.pcd.glservice', vendor: 'sap.com', name: 'com.sap.portal.runtime.system.idcounters', vendor: 'sap.com', name: 'com.sap.portal.design.urdesigndata', vendor: 'sap.com', name: 'com.sap.portal.usermanagement.admin', vendor: 'sap.com', name: 'tc~epbc~ume~ep5~deprecated', vendor: 'sap.com', name: 'tc~jpe~engine', vendor: 'sap.com', name: 'tc~epbc~pcd~pars~restricted', vendor: 'sap.com', name: 'tc~ep~useragent~api', vendor: 'sap.com', name: 'com.sap.portal.runtime.gwtintegration', vendor: 'sap.com', name: 'tc~bc~jpe~engine~api', vendor: 'sap.com', name: 'com.sap.portal.runtime.system.connection', vendor: 'sap.com', name: 'com.sap.portal.usermanagement', vendor: 'sap.com', name: 'com.sap.portal.pcd.configservice', vendor: 'sap.com', name: 'com.sap.portal.runtime.application.soap', vendor: 'sap.com', name: 'pcm_ext_libSDA', vendor: 'sap.com', name: 'com.sap.portal.runtime.application.document', vendor: 'sap.com',

Error while performing SAP Installation in HA Env on Windows Server 2008

Hello,
I am performing a SAP Installation in HA Environment on Windows Server 2008. I am at the ASCS installation step.
As per the guide before installing ASCS there are some activities to be carried out on Failover Cluster Management.
I have done all the steps except one as per the guide. I am stuck in the Add FileServer Step. In this step the guide says to go to the Dependencies tab and add the cluster disk resource to the dependencies list. It also says to add the Name:Virtual NetworkName to the dependencies list.
Now in my scenario I have 3 shared drives for SAP and I have added each of them in the dependencies list of the new FileServer. The only problem is how do I add the Name:Virtual NetworkName to this list
When I continue without giving the Network name the system issues a warning "This resource requires dependencies on instances of the following resource types or classes:Network Name. Not adding these dependencies will prevent the resource from working properly. Do you want to save the current settings anyway"
If I click on Yes and bring this resource online it fails with this error message
"The action Bring this resource online did not complete.An error occured while attempting to bring the resource 'SAPECC FileServer online'. The cluster resource could not be brought online by resource monitor."
My question is how to add the Name:VirtualNetworkName to the dependencies list of the FileServer.
Regards
Mitesh Nair

Hi,
I have resolved the issue with the help of cluster admin
Regards
Mitesh

Error ERP 6.0 Installation step 32 of 96 JAVA

Similar Messages

Maybe you are looking for