Starting deployment prerequisites: error in BI-Java installation sapinst

Hi all,
We are in process updating Bw 3.5 to BI 7.0 we hace sucessfully completed the Upgrade but while installing Bi java thru Sapinst in third step like java instance installtion  i was stck with the below error.
           We have downloaded the Cryptographic file and placed in jdk folder still the same problem is  coming.
Please suggest...
Thanks,
Subhash.G
Starting deployment prerequisites:
Oct 13, 2007 2:42:18 AM  Error: Creation of DataSource for database "BWQ" failed.
Original error message is:
com.sap.sql.log.OpenSQLException: Error while accessing secure store: Encryption or decryption is not possible because the full version of the SAP Java Crypto Toolkit was not found (iaik_jce.jar is required, iaik_jce_export.jar is not sufficient) or the JCE Jurisdiction Policy Files don't allow the use of the "PbeWithSHAAnd3_KeyTripleDES_CBC" algorithm..
Stack trace of original Exception or Error is:
com.sap.sql.log.OpenSQLException: Error while accessing secure store: Encryption or decryption is not possible because the full version of the SAP Java Crypto Toolkit was not found (iaik_jce.jar is required, iaik_jce_export.jar is not sufficient) or the JCE Jurisdiction Policy Files don't allow the use of the "PbeWithSHAAnd3_KeyTripleDES_CBC" algorithm..

Problem solved  followed the notes 1063396.

Similar Messages

  • Setup (deployment) prerequisite error

    Warning     1     The 'SAP Crystal Reports Runtime Engine for .NET Framework 4.0' item selected requires 'Microsoft.Net.Framework.2.0'. Select the missing prerequisite in the Prerequisites Dialog Box or create a bootstrapper package for the missing prerequisite.     
    What the...  CR for .net 4.0 requires .net 2.0 ?!
    Is the Runtime Engine not the correct option to install on end user's machines? This is the only prerequisite listed for CR.
    Ron

    CR still has some components that have dependencies on framework 2.0.
    Other prerequisites are the MS C++ runtime library. See Kb [1544708  - What are the runtime dependencies for CRVS2010?|http://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes_boj/sdn_oss_boj_bi/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/scn_bosap/notes%7B6163636573733d36393736354636443646363436353344333933393338323636393736354637333631373036453646373436353733354636453735364436323635373233443330333033303331333533343334333733303338%7D.do].
    Ludek
    Follow us on Twitter http://twitter.com/SAPCRNetSup
    Got Enhancement ideas? Try the [SAP Idea Place|https://ideas.sap.com/community/products_and_solutions/crystalreports]

  • Error while  java installation during ecc enp1 installition on win + oracle

    hi,
    i'm started installing SAP ecc6 ehp1, during  java installation i tryied to install  j2sdk se 1.4.2_28
    after that when i tried to check it on the command prompt it is showing
    *C:\Documents and Settings\Administrator>java -version*
    *'java' is not recognized as an internal or external command,*
    *operable program or batch file.*
    after that i installed jdk 1.6 now its showing
    C:\Documents and Settings\Administrator>java -version
    java version "1.6.0_22"
    Java(TM) SE Runtime Environment (build 1.6.0_22-b04)
    Java HotSpot(TM) 64-Bit Server VM (build 17.1-b03, mixed mode)
    but i am supposed to use j2sdk se 1.4.2_28
    please help

    >>'java' is not recognized as an internal or external command,*
    have you set the JAVA_HOME environment variable correctly to point to 1.4.2_28 installation folder?

  • Java Install error 1603 on Java 8u45

    I am having issues getting Java to Install on a Windows 7 Pro PC in a stand alone environment. 
    Error Code 1603.  Java is needed on this PC to be able to print shipping labels from FEDEX.com. I am trying to install using the administrator account. I have removed previous versions of Java. I have  removed the MS updated KB2918614.
    The java uninstall tool doesn't run because Java is required to run the java uninstall tool.  I have run multiple Microsoft Fixit Tools.  This is the second PC I have had this error with in this office. Does anyone have any thing more to offer that
    might assist me. I have "Google'd" this error for 2 weeks now.  Help would be greatly appreciated, Thank You!

    Hi,
    According to official site of Oracle, This is a known issue with Microsoft KB2918614The root causes of these errors are under investigation. If this error still persists after uninstalled this update.
    You could try following zooeyhall’s suggestion to download and install a previous version of Java or try creating a new administrative user account and install Java with the new account.
    https://social.technet.microsoft.com/Forums/windows/en-US/78ac199b-316b-4fbc-8b2b-2c90e5425ff0/java-install-errors
    Regarding to JAVA installation error, I’d suggest that we post at JAVA forum for further support. There you can get more effective suggestion by other experts who familiar with it. Your understanding is highly appreciated.
    Regards,
    D. Wu
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • EP installation SAPINST HANGS

    System details: windows 2003, jdk 1.4.2_10, sql 2000, ecc 5.0 unicode
    sequence of installation: abap (central and database instance) java add-in,upgrade java instance to sp16
    Current: installation of EP
    Problem 1: On screen of Portal platform for sap java system it shows J2EE Engine: DEV DBTYPE UNDEFINED
    Problem: Sapinst hangs on deploy jdbc libraries
    For problem i read that from netweaver sr01 portal can be installed on abap+java system, as java add-in is seperately installed on another schema.
    For problem 2 java.exe.log is shown below:
    java.lang.NoClassDefFoundError: iaik/utils/Base64Exception
         at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.<init>(DBConnectionPool.java:108)
         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:49)
         at com.sap.engine.configtool.batch.BatchConfig.go(BatchConfig.java:47)
         at com.sap.engine.configtool.batch.BatchConfig.main(BatchConfig.java:83)
    I downloaded sap crypto.. lib, sda file and try to deploy it via sdm but when i execute remotegui.bat, after entering the default password 'sdm' it give the error
    ERROR: Could not establish connection to server SAPDevSrv at port 50018: Connection refused: connect
    Further to add,i find scs(java instance running)in sapmmc, but there is no entry for java.exe in task manager, i use jcontro.exe pf=<..> file
    can anyone help me.
    thanks
    Imran

    the problem is solved a little bit, the sapinst moved few phases ahead.
    what i did was that i started deploying sda file via sdm command mode and i started the sdm server from command mode.
    But now there is another error of compilation. the callSdmviaSAPinst.log
    Apr 18, 2006 5:22:51 PM  Info: Start logging to console
    Apr 18, 2006 5:22:51 PM  Info:
    Apr 18, 2006 5:22:51 PM  Info: ============================================
    Apr 18, 2006 5:22:51 PM  Info: =   Starting to execute command 'deploy'   =
    Apr 18, 2006 5:22:51 PM  Info: ============================================
    Apr 18, 2006 5:22:51 PM  Info: Starting SDM - Software Deployment Manager...
    Apr 18, 2006 5:22:51 PM  Info: tc/SL/SDM/SDM/sap.com/SAP AG/6.4016.00.0000.20060119123612.0000
    Apr 18, 2006 5:22:52 PM  Info: SDM operation mode successfully set to: Standalone
    Apr 18, 2006 5:22:52 PM  Info: Initializing Network Manager (50017)
    Apr 18, 2006 5:22:52 PM  Info: Checking if another SDM is running on port 50018
    Apr 18, 2006 5:22:52 PM  Info: -
    Starting deployment -
    Apr 18, 2006 5:22:52 PM  Info: Error handling strategy: OnErrorStop
    Apr 18, 2006 5:22:52 PM  Info: Prerequisite error handling strategy: OnPrerequisiteErrorStop
    Apr 18, 2006 5:22:52 PM  Info: Update strategy: UpdateAllVersions
    Apr 18, 2006 5:22:52 PM  Info: Starting deployment prerequisites:
    Apr 18, 2006 5:22:52 PM  Info: Loading selected archives...
    Apr 18, 2006 5:22:52 PM  Info: Loading archive 'Z:\SAPCDs\G3\51030723\EP-KMC\DQE\SDA\J2EE\com.sapportals.dqe.beans.ear'
    Apr 18, 2006 5:22:55 PM  Info: Selected archives successfully loaded.
    Apr 18, 2006 5:22:55 PM  Info: Actions per selected component:
    Apr 18, 2006 5:22:55 PM  Info: Initial deployment: Selected development component 'com.sapportals.dqe.beans'/'sap.com'/'SAP AG'/'609.20041012204607.0000' will be deployed.
    Apr 18, 2006 5:22:55 PM  Info: Ending deployment prerequisites. All items are correct.
    Apr 18, 2006 5:22:55 PM  Info: Saved current Engine state.
    Apr 18, 2006 5:22:55 PM  Info: Starting: Initial deployment: Selected development component 'com.sapportals.dqe.beans'/'sap.com'/'SAP AG'/'609.20041012204607.0000' will be deployed.
    Apr 18, 2006 5:22:55 PM  Info: SDA to be deployed: E:\usr\sap\DEV\DVEBMGS00\SDM\root\origin\sap.com\com.sapportals.dqe.beans\SAP AG\609.20041012204607.0000\com.sapportals.dqe.beans.ear
    Apr 18, 2006 5:22:55 PM  Info: Software type of SDA: J2EE
    Apr 18, 2006 5:22:55 PM  Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
    Apr 18, 2006 5:22:58 PM  Info: Begin of log messages of the target system:
    06/04/18 17:22:56 -  ***********************************************************
    06/04/18 17:22:57 -  Start updating EAR file...
    06/04/18 17:22:57 -  start-up mode is lazy
    06/04/18 17:22:57 -  EAR file updated successfully for 156ms.
    06/04/18 17:22:57 -  Start deploying ...
    06/04/18 17:22:57 -  EAR file uploaded to server for 63ms.
    06/04/18 17:22:58 -  ERROR: Not deployed. Deploy Service returned ERROR:
                         java.rmi.RemoteException: Cannot deploy application sap.com/com.sapportals.dqe.beans..
                         Reason: Errors while compiling:
                         Compilation process error : CreateProcess: null\bin\javac -J-Xmx256m @E:/usr/sap/DEV/DVEBMGS00/j2ee/cluster/server0/compilerTempDir/compiler_Apr_18_at_17.22/O1145373778846.txt @E:/usr/sap/DEV/DVEBMGS00/j2ee/cluster/server0/compilerTempDir/compiler_Apr_18_at_17.22/S1145373778846.txt error=2; nested exception is:
                              com.sap.engine.services.ejb.exceptions.deployment.EJBFileGenerationException: Errors while compiling:
                         Compilation process error : CreateProcess: null\bin\javac -J-Xmx256m @E:/usr/sap/DEV/DVEBMGS00/j2ee/cluster/server0/compilerTempDir/compiler_Apr_18_at_17.22/O1145373778846.txt @E:/usr/sap/DEV/DVEBMGS00/j2ee/cluster/server0/compilerTempDir/compiler_Apr_18_at_17.22/S1145373778846.txt error=2
                              at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:554)
                              at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1555)
                              at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:304)
                              at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:193)
                              at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:122)
                              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)
                         Caused by: com.sap.engine.services.ejb.exceptions.deployment.EJBFileGenerationException: Errors while compiling:
                         Compilation process error : CreateProcess: null\bin\javac -J-Xmx256m @E:/usr/sap/DEV/DVEBMGS00/j2ee/cluster/server0/compilerTempDir/compiler_Apr_18_at_17.22/O1145373778846.txt @E:/usr/sap/DEV/DVEBMGS00/j2ee/cluster/server0/compilerTempDir/compiler_Apr_18_at_17.22/S1145373778846.txt error=2
                              at com.sap.engine.services.ejb.util.AdminUtils.compile(AdminUtils.java:473)
                              at com.sap.engine.services.ejb.deploy.DeployAdmin.deploySingleJar(DeployAdmin.java:628)
                              at com.sap.engine.services.ejb.deploy.DeployAdmin.generate(DeployAdmin.java:264)
                              at com.sap.engine.services.ejb.EJBAdmin.deploy(EJBAdmin.java:2144)
                              at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:606)
                              at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:319)
                              at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:307)
                              at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292)
                              at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:326)
                              at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3139)
                              at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:539)
                              ... 10 more
                         Caused by: com.sap.engine.compilation.CompilerProcessFailureException: Compilation process error : CreateProcess: null\bin\javac -J-Xmx256m @E:/usr/sap/DEV/DVEBMGS00/j2ee/cluster/server0/compilerTempDir/compiler_Apr_18_at_17.22/O1145373778846.txt @E:/usr/sap/DEV/DVEBMGS00/j2ee/cluster/server0/compilerTempDir/compiler_Apr_18_at_17.22/S1145373778846.txt error=2
                              at com.sap.engine.compilation.ExternalCompiler.compile(ExternalCompiler.java:77)
                              at com.sap.engine.services.ejb.util.AdminUtils.compile(AdminUtils.java:471)
                              ... 20 more
                         For detailed information see the log file of the Deploy Service.
    06/04/18 17:22:58 -  ***********************************************************
    Apr 18, 2006 5:22:59 PM  Info: End of log messages of the target system.
    Apr 18, 2006 5:22:59 PM  Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
    Apr 18, 2006 5:22:59 PM  Error: Aborted: development component 'com.sapportals.dqe.beans'/'sap.com'/'SAP AG'/'609.20041012204607.0000':
    Caught exception during application deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: Cannot deploy application sap.com/com.sapportals.dqe.beans..
    Reason: Errors while compiling:
    Compilation process error : CreateProcess: null\bin\javac -J-Xmx256m @E:/usr/sap/DEV/DVEBMGS00/j2ee/cluster/server0/compilerTempDir/compiler_Apr_18_at_17.22/O1145373778846.txt @E:/usr/sap/DEV/DVEBMGS00/j2ee/cluster/server0/compilerTempDir/compiler_Apr_18_at_17.22/S1145373778846.txt error=2; nested exception is:
         com.sap.engine.services.ejb.exceptions.deployment.EJBFileGenerationException: Errors while compiling:
    Compilation process error : CreateProcess: null\bin\javac -J-Xmx256m @E:/usr/sap/DEV/DVEBMGS00/j2ee/cluster/server0/compilerTempDir/compiler_Apr_18_at_17.22/O1145373778846.txt @E:/usr/sap/DEV/DVEBMGS00/j2ee/cluster/server0/compilerTempDir/compiler_Apr_18_at_17.22/S1145373778846.txt error=2
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Apr 18, 2006 5:22:59 PM  Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
    Apr 18, 2006 5:22:59 PM  Error: -
    At least one of the Deployments failed -
    Apr 18, 2006 5:22:59 PM  Info: Summarizing the deployment results:
    Apr 18, 2006 5:22:59 PM  Error: Aborted: Z:\SAPCDs\G3\51030723\EP-KMC\DQE\SDA\J2EE\com.sapportals.dqe.beans.ear
    Apr 18, 2006 5:22:59 PM  Error: Processing error. Return code: 4
    But as you suggested if i change my java version would it not be a problem for sap other instances? if not then i can change. and also if i change the java version should i have to repeat ep installation or the aborted installation will work?
    thanks
    Imran

  • 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',

  • BI Java Installation Error

    Hi,all:
    I did the installation of BI Java Installation yesterday,but it terminated during process"SAP J2EE Engine Online Deployment". It informs "MUT-02041 SDM call of deploySdaList ends with returncode 4". I check the callSdmViaSapinst.log, below is the error information:
    05/11/20 22:49:59 -  ***********************************************************
    05/11/20 22:50:01 -  Start updating EAR file...
    05/11/20 22:50:01 -  start-up mode is lazy
    05/11/20 22:50:01 -  EAR file updated successfully for 137ms.
    05/11/20 22:50:01 -  Start deploying ...
    05/11/20 22:50:02 -  EAR file uploaded to server for 385ms.
    05/11/20 22:50:02 -  ERROR: Not deployed. Deploy Service returned ERROR:
                         java.rmi.RemoteException: Error occurred while deploying ear file ./temp/deploy/work/deplo
    ying/bi_mmr_bi_4.0.ear.
                         Reason: None of the available containers recognized the components of application sap.com/
    bimmrbi_4.0; it is not possible to make deploy.
                            at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.jav
    a:480)
                            at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServic
    eImplp4_Skel.java:1555)
                            at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:291)
                            at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:183)
                            at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.
    java:119)
                            at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageList
    ener.process(ApplicationSessionMessageListener.java:37)
                            at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(Unorder
    edChannel.java:71)
                            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:94)
                            at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
                         For detailed information see the log file of the Deploy Service.
    05/11/20 22:50:02 -  ***********************************************************
    Nov 20, 2005 10:50:02... Info: End of log messages of the target system.
    Nov 20, 2005 10:50:02... Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
    Nov 20, 2005 10:50:02... Error: Aborted: development component 'bi/mmr/bi_4.0'/'sap.com'/'SAP AG'/'350.6918.000
    Caught exception during application deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: Error occurred while deploying ear file ./temp/deploy/work/deploying/bi_mmr_bi_4.0.ea
    r.
    Reason: None of the available containers recognized the components of application sap.com/bimmrbi_4.0; it is
    not possible to make deploy.
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(Deployme
    ntActionTypes).REMEXC)
    Nov 20, 2005 10:50:02... Info: SDM configuration: Do not automatically start/stop J2EE Engine. Do not restore s
    tate of J2EE Engine now.
    Nov 20, 2005 10:50:02... Info: -
    Deployment was successful -
    Nov 20, 2005 10:50:03... Info: Summarizing the deployment results:
    Nov 20, 2005 10:50:03... Error: Admitted: /Inst_CDs/BW/BW-UDI/ONLINE/BIUDI09_0.sca
    Nov 20, 2005 10:50:03... Error: Processing error. Return code: 4
    My platform is SUSE Linux Enterprise Server 9. I do the installation on a NetWeaver ABAP+Java 640 system. Also I have installed BI content 3.53.
    Please help me.
    Thanks,
    Daniel

    I am having the same problem.
    Can anyone help on this topic please?

  • 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: ???)).

  • JRA / xMii dependency error when deploying XMII 12.1 on Java AS 7.0.3

    Hi there,<p>I'm trying to deploy XMII 12.1 on a freshly installed JAVA AS System (NW 7.01 SP3), but the deployment logs appear to be reporting an unsupported version of the JRA connector when I attempt to deploy via JSPM.
    <p>
    <hr>
    Aug 27, 2010 11:04:54... Info: Begin of log messages of the target system:<p>
    10/08/27 23:04:52 -  ***********************************************************<p>
    10/08/27 23:04:53 -  Start updating EAR file...<p>
    10/08/27 23:04:53 -  start-up mode is lazy<p>
    10/08/27 23:04:53 -  EAR file updated successfully for 172ms.<p>
    10/08/27 23:04:53 -  Start deploying ...<p>
    10/08/27 23:04:54 -  EAR file uploaded to server for 78ms.<p>
    10/08/27 23:04:54 -  ERROR: Not deployed. Deploy Service returned ERROR: <p>
                         java.rmi.RemoteException: Cannot deploy application sap.com/sapjra~xMIIIDOC01.. <p>
                         Reason: Not supported version of connector.; nested exception is: <p>
                              com.sap.engine.services.deploy.container.DeploymentException: <--Localization failed:<p>
    ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle',<p>
    ID='com.sap.engine.services.connector.exceptions.BaseDeploymentException: Not supported version of connector.<p>
                              at com.sap.engine.services.connector.jca15.deploy.Container15Impl.deploy(Container15Impl.java:180)<p>
    .....<p>
    ......<p>
    10/08/27 23:04:54 -  ***********************************************************<p>
    Aug 27, 2010 11:04:54... Info: End of log messages of the target system.<p>
    Aug 27, 2010 11:04:54... Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****<p>
    Aug 27, 2010 11:04:54... Error: Aborted: development component 'sapjra/xMIIIDOC01'/'sap.com'/'MAIN_MII'/'20091209120000'/'1', grouped by software component 'XMII'/'sap.com'/'MAIN_xM121PAT_C'/'1000.12.1.5.12.20100713044315''/'1':<p>
    Caught exception during application deployment from SAP J2EE Engine's deploy service:<p>
    java.rmi.RemoteException: Cannot deploy application sap.com/sapjra~xMIIIDOC01.. <p>
    Reason: Not supported version of connector.; nested exception is: <p>
         com.sap.engine.services.deploy.container.DeploymentException: <--Localization failed:<p>
    ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', <p>
    ID='com.sap.engine.services.connector.exceptions.BaseDeploymentException: Not supported version of connector.<p>
    ...........<p>
    <hr>
    <p><p><p>
    The above theory appears to be confirmed when I I attempt to deploy via the SDM:
    <P>
    <hr>Unresolved dependencies found for the following SDAs:
    <P>
    1.: development component 'xapps/xmii/jraapp'/'sap.com'/'MAIN_xM121VAL_C'/'3702066'/'0' dependency: <P>
           name:     'tc/bl/jra/api'<P>
         vendor:     'sap.com'
    <p</P>
    There is no component either in SDM repository or in Deployment batch that resolves the dependency.
    <p</P>
    Deployment will be aborted.
    <hr>
    <p</P>
    NOW, I have deployed the sapjra.ra file as per the Note 861752 - basic JRA setup.  I used the sapjra.rar that came with the JAVA AS install - I thought there may have been a different one that came with the XMII install, but I haven't been able to find it if it exists.  Also, I couldn't find a description of what specific values (if any) are required for XMII or other Composites - things like the deployment name and so on.  Are there any such specific values ?
    <p</P>
    Any help, hints or ideas would be greatly appreciated
    Edited by: Martin English on Aug 27, 2010 6:23 PM (fixing markup)

    Martin,
    go to this link:
    https://websmp207.sap-ag.de/~form/handler?_APP=00200682500000001303&_EVENT=DISP_NEW&00200682500000002804=01200314690900000455
    It is documented in the Installation Guide Page 5.
    BR
    Pedro Iglesias
    Edited by: Pedro Iglesias on Aug 29, 2010 10:49 PM

  • Error in WAS ABAP+JAVA installation

    Hi all,
    I have a notebook with WAS 6.40 ABAP stack running fine. Now I'm trying to install WAS Java stack (NW04 Sneak Preview SP11) in the same machine, but I always get this error in the 6th step of the installation process:
    6th step: MaxDB Database Installation:
    <i>ERROR 2005-10-25 15:41:59
    CJS-00030  Assertion failed: in function sapdb_param_init(db_name, db_host, sapdb_version, inst_type) {    var init_s;    if (inst_type == undefined) {        init_s = "OLTP";    } else {        switch (inst_type) {          case "LVC":            init_s = "LVC";            break;          default:            init_s = "OLTP";            break;        }    }    var r_arr = sdb_instance_type(db_name, db_host, init_s, sapdb_version);    ASSERT(arguments.callee, r_arr != undefined, "SDB: ERROR EXECUTING PARAM_INIT!");    ASSERT(arguments.callee, r_arr[0] == "true", "SDB: ERROR EXECUTING PARAM_INIT! CHECK THE XCMDOUT.LOG FILE!");    return (r_arr[0] == "true");}SDB: ERROR EXECUTING PARAM_INIT! CHECK THE XCMDOUT.LOG FILE!</i>
    I've tried several times. I've tried to start and stop the WAS ABAP and all SAP windows services and I always get an error. Before any installation I uninstall previous incomplete installation and I remove all registry entries.
    During the SAPinst previous parameters pages, sapinst ask for "reinstall or reuse the SAP MaxDB Web Manager" (or similar). I've tried both options without success. Which is the correct option?
    I need to install EP NW04 in the same machine that WASP WAS ABAP to configure the SLD and run a webdynpro application at the portal.
    Can anybody help me?
    Best regards.

    Agustin I think you probably have the same problem as I had which can be resolved by dropping the J2E database read my install log:
    A major problem was that I kept on getting installation error where the message gave no indication on what is actually wrong. This was probably caused by the uninstall failure of another Netweaver installation.
    To completely remove the installation manually I had to find and stop all the related services in order to delete the files, then I had to clean up the registry.
    A another major problem was that the system still believed that there was a J2E database on the system although all its files were deleted. In order to remove (drop) the database I first had to install MaxDB in order to remove the database with the following statement “dbmcli -d J2E -u control,control db_drop”. Use statement “dbmcli db_enum” to view the databases on your system (go to the folder, probably c:\sapdb, were the SAPDB is installed before executing the command in a dos box).
    Let me know if this helped.
    Kind Regards,
    Dennis.
    Message was edited by: Dennis

  • PCUI GP Deployment ERROR on Standalone Java Stack

    We are in the midst of deploying the PCUI archive via SDM (also tried JSPM)
    Got the following error
    Aborted: development component 'pcui_gp/isr/cfg'/'sap.com'/'MAIN_ERP05VAL_C'/'2515722'/'0', grouped by software component 'SAPPCUI_GP'/'sap.com'/'MAIN_ERP05VAL_C'/'1000.600.0.13.0.20080516101947''/'0':Caught exception during application deployment from SAP J2EE Engine's deploy service:java.rmi.RemoteException: Error occurred while deploying ear file ./temp/deploy/work/deploying/pcui_gp_isr_cfg.ear. Reason: None of the available containers recognized the components of application sap.com/pcui_gpisrcfg; it is not possible to make deploy. (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Deployment of pcui_gp/isr/cfg finished with Error (Duration 12495 ms)
    Starting Deployment of SAPPCUI_GP
    Aborted: software component 'SAPPCUI_GP'/'sap.com'/'MAIN_ERP05VAL_C'/'1000.600.0.13.0.20080516101947''/'0':Failed deployment of SDAs:development component 'pcui_gp/isr/cfg'/'sap.com'/'MAIN_ERP05VAL_C'/'2515722'/'0' : abortedPlease, look at error logs above for more information!
    Deployment of SAPPCUI_GP finished with Error (Duration 6525 ms)
    PCUI Patch level is SP13 (highest). and Java stack is 15
    Even tried starting from PCUI SP1
    This is a Standalone Java Stack. Not Add-In
    HAs anyone had experience deploying PCUI on Standalone Java Stack.
    Any help/pointers appreciated.

    Hi ,
    Please check :
    https://wiki.sdn.sap.com/wiki/display/WDJava/Clusterwideexception-FailedtodeployWebDynprocontentforapplication
    Regards,
    Nibu Antony
    Edited by: Nibu Antony on Dec 13, 2010 2:52 PM

  • Ruleset webservice: error during deployment EAR file on the java server

    Hi,
    I want to create a webservices for a ruleset which i have created with the rules composer (NWDS).
    During this proces, the following problem occurs: after creating a ruleset and the EAR file with the Web Service Generation Tool, i wanted to deploy this file on the java server for creating a webservices. During deployment, I get the following warning with no results:
    <h5>
                S U M M A R Y
    ~~~~~~~~~~~~~~~~~~~
    Successfully deployed:           0
    Deployed with warnings:           1
    Failed deployments:                0
    ~~~~~~~~~~~~~~~~~~~
    1. File:C:\Documents and Settings\Martin Gerritsen\Desktop\Webservices\DeclaratieCheckRulesetEAR.ear
         Name:DeclaratieCheckRulesetEAR
         Vendor:sap.com
         Location:localhost
         Version:2008.03.12.12.02.09
         Deploy status:Warning
         Version:NEW
         Description:
              1. Warning occurred on server 1573750 during deploy sap.com/DeclaratieCheckRulesetEAR : Web Class Existence Test: The servlet "GenericWS" must implement "javax.servlet.Servlet"., file: DeclaratieCheckRulesetWEB.war#WEB-INF/web.xml, column 0, line 0, severity: warning
              2. Exception has been returned while the [sap.com/DeclaratieCheckRulesetEAR] was starting. Warning/Exception :[
    ][[ERROR CODE DPL.DS.6193] Error while ; nested exception is:
         com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5030] Clusterwide exception: [server ID 1573750:[ERROR CODE DPL.DS.5035] Application [sap.com/DeclaratieCheckRulesetEAR] cannot be started. Reason: it has hard reference to resource [tcbrmsfacade] with type [application], which is not active on the server.
    Hint: 1) Is referred resource deployed? 2) Is referred resource able to start?
               -> [ERROR CODE DPL.DS.5082] Exception while [validating application sap.com/tcbrmsfacade.
         The sap.com/tcbrmsfacade application was processed from [EJBContainer] containers, but none of them returned information about deployed components.
         The registered containers in this moment were [CTCContainer, MDRContainer, com.sap.security.ume, developmentserver, SCA Composites Container, com.sap.security.login-modules, app_libraries_container, Cache Configuration Upload, servlet_jsp, dbcontentcontainer, connector, Cluster File System, BRMS_Content_Archive, JMSConnector, MigrationContainer, Galaxy_Content_Archive, Monitoring Configurator, dbschemacontainer, appclient, orpersistence, PortalRuntimeContainer, JDBCConnector, EJBContainer, metamodelrepository, webservices_container, scheduler~container, ConfigurationsContainer, Content Container].
         Possible reasons :
         1.Empty or incorrect application, which is not recognized by registered containers.
         2.An AS Java service, which is providing a container, is stopped or not deployed.
         3.The containers, which processed it, are not implemented correctly, because the application was deployed or started initially, but containers didn't return information about deployed components in the application deployment info].
    server ID 1573750:com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5035] Application [sap.com/DeclaratieCheckRulesetEAR] cannot be started. Reason: it has hard reference to resource [tcbrmsfacade] with type [application], which is not active on the server.
    Hint: 1) Is referred resource deployed? 2) Is referred resource able to start?
         at com.sap.engine.services.deploy.server.ReferenceResolver.checkApplicationStatus(ReferenceResolver.java:871)
         at com.sap.engine.services.deploy.server.ReferenceResolver.processReferenceToApplication(ReferenceResolver.java:848)
         at com.sap.engine.services.deploy.server.ReferenceResolver.processMakeReference(ReferenceResolver.java:575)
         at com.sap.engine.services.deploy.server.ReferenceResolver.beforeStartingApplication(ReferenceResolver.java:489)
         at com.sap.engine.services.deploy.server.application.StartTransaction.beginCommon(StartTransaction.java:169)
         at com.sap.engine.services.deploy.server.application.StartTransaction.begin(StartTransaction.java:134)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:493)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:544)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.super_MakeAllPhases(ParallelAdapter.java:286)
         at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:555)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:197)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:358)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3421)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3407)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3297)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3269)
         at com.sap.engine.services.dc.lcm.impl.J2EELCMProcessor.doStart(J2EELCMProcessor.java:105)
         at com.sap.engine.services.dc.lcm.impl.LifeCycleManagerImpl.start(LifeCycleManagerImpl.java:78)
         at com.sap.engine.services.dc.cm.deploy.impl.LifeCycleManagerStartVisitor.visit(LifeCycleManagerStartVisitor.java:34)
         at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
         at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcessLCMDeplItem(DefaultDeployPostProcessor.java:91)
         at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcess(DefaultDeployPostProcessor.java:61)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doPostProcessing(DeployerImpl.java:862)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.performDeploy(DeployerImpl.java:810)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doDeploy(DeployerImpl.java:640)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:359)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:248)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImplp4_Skel.dispatch(DeployerImplp4_Skel.java:897)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:355)
         at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:69)
         at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:67)
         at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:41)
         at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:971)
         at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:57)
         at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:55)
         at com.sap.engine.core.thread.execution.Executable.run(Executable.java:109)
         at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)
    Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5082] Exception while [validating application sap.com/tcbrmsfacade.
         The sap.com/tcbrmsfacade application was processed from [EJBContainer] containers, but none of them returned information about deployed components.
         The registered containers in this moment were [CTCContainer, MDRContainer, com.sap.security.ume, developmentserver, SCA Composites Container, com.sap.security.login-modules, app_libraries_container, Cache Configuration Upload, servlet_jsp, dbcontentcontainer, connector, Cluster File System, BRMS_Content_Archive, JMSConnector, MigrationContainer, Galaxy_Content_Archive, Monitoring Configurator, dbschemacontainer, appclient, orpersistence, PortalRuntimeContainer, JDBCConnector, EJBContainer, metamodelrepository, webservices_container, scheduler~container, ConfigurationsContainer, Content Container].
         Possible reasons :
         1.Empty or incorrect application, which is not recognized by registered containers.
         2.An AS Java service, which is providing a container, is stopped or not deployed.
         3.The containers, which processed it, are not implemented correctly, because the application was deployed or started initially, but containers didn't return information about deployed components in the application deployment info].
         at com.sap.engine.services.deploy.server.utils.ValidateUtils.missingDCinDIValidator(ValidateUtils.java:80)
         at com.sap.engine.services.deploy.server.application.StartInitiallyTransaction.prepare(StartInitiallyTransaction.java:158)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:502)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:544)
         at com.sap.engine.services.deploy.server.application.StartTransaction.doStartInitiallyLocal(StartTransaction.java:477)
         at com.sap.engine.services.deploy.server.application.StartTransaction.doStartInitially(StartTransaction.java:433)
         at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:193)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:591)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:202)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:367)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.regularStartApplicationLocalAndWait(DeployServiceImpl.java:3218)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:3210)
         at com.sap.engine.services.deploy.server.ReferenceResolver.checkApplicationStatus(ReferenceResolver.java:863)
         ... 36 more
    Result
    Status:Warning
    </h5>
    Development Infrastructure:
    - development configuration: local development
    - development configuration: saptest (SAP NetWeaver CE 7.1 EHP1)
    Before I created the EAR file with the Web Service Generation Tool, I have carried out the following steps:
    - Created a ruleset (including two rules and one decision table) (development configuration: saptest)
    - Build and deploy the ruleset on the java server...
    - Created a dummy web module (development configuration: local development)
    - Added 3 dependencies (references) to the dummy web module:
    - References 1: enginee.jee5.facade (no selection on design time, deploy time or runtime)
    - References 2: tc/bl/logging/api (selection on design time, deploy time and runtime)
    - References 3: tc/brms/ facade (selection on design time, deploy time and runtime)
    - Dummy web module -> sync used DC's
    - Build dummy web module
    After that I started the Web Service Generation Tool and created the EAR file....
    1) NWDS -> window -> show view -> others -> deploy view -> deploy view
    2) Added the EAR file to External Deployable Archives
    3) deployed the file to the java server... then the warning occurs...
    How can I resolve this error?
    <h5>Application [sap.com/DeclaratieCheckRulesetEAR] cannot be started. Reason: it has hard reference to resource [tcbrmsfacade] with type [application], which is not active on the server.
    Hint: 1) Is referred resource deployed? 2) Is referred resource able to start...</h5>
    And...
    <h5>[ERROR CODE DPL.DS.5082] Exception while [validating application sap.com/tcbrmsfacade.
         The sap.com/tcbrmsfacade application was processed from [EJBContainer] containers, but none of them returned information about deployed components.</h5>
    Can somebody help me with this problem?
    Kind regards,
    Martin Gerritsen

    Hello Martin Gerritsen,
    This is Arti from the PM team.
    It seems to me that the brms facade has not yet started in your application server. You can check whether it has started or not by doing the following -
    You need to access the JavaEE Applications running on your AS. To do this -
    1. Open the nwa portal
    2. Navigate to Operations Management > Systems > Start & Stop > Java EE Applications
    3. Search for the brms related applications available on the server.
    In case the applications have not yet been started, please try to manually start them. If you still have problem in starting the BRMS facade please contact me.
    I will send across to you a fresh set of SCAs which you can deploy into your server to resolve this issue.
    Regards,
    Arti

  • Cannot install itunes 10.6 to my windows 7 computer. Have tried several times, completely unistalled several times, all with same result. Error message that starts "An error occurred during the installation of assembly 'Microsoft VC80 CRT. type="win 32"

    Keep getting the following error message when I try to instal itunes 10.6.  An error occurred during the installation of assembly 'Microsoft VC80 CRT.type="win 32". version = "8.0 50727.61 95". public Key token = ""1fc8b3b9a1e18e3b." processor architeture = "x86". Please refer to help and support for more information.
    HRESULT:0x80073712
    The program then acts like it is still trying to load, but then I get another message later which reads:
    Service 'Aple Mobile Device' failed to start. verify that you have sufficient privileges to start system services.
    any suggestions?

    HRESULT: 0x80073712
    These ones are typically caused by underlying problems on the PC that also often cause Windows Updates to fail to install. If we can fix the Windows Update trouble, we can usually get the iTunes trouble cleaned up en passant.
    Go into your Windows update and try to check for new updates. If updates install, stock up on the ones you're behind on, restarting the PC if requested to do so. After the restart, try installing iTunes again. Does it go through this time for you?
    If windows updates fail to install, go into your Update History and doubleclick the failures. What alphanumeric codes appear for you? Are they also 80073712, or some other number? (If they're another number, what number are you getting?)

  • I can't upgrade my iPhone 4 to iOS 5.1.1 from the iPhone using wifi!! the installation start but before finishing an error occurred and the installation stop! help

    I can't upgrade my iPhone 4 to iOS 5.1.1 from the iPhone using wifi!! the installation start but before finishing an error occurred and the installation stop! help

    I will try, and what happen is that after it is intall and start "Preparing upgrade" the installation stop and a message occure: An error occure download the iOS 5.1.1" thas all.
    But now it is too late because the iOS 6 is now availabel, is it recommendet to donwload iOS 6 on iPhone 4 or not?

  • SAP AS JAVA installation in Solaris Zone envirn throws OUT of Memory error.

    Hi,
    We are installing SAP NW2004s 7.0 SR3 AS JAVA on Solaris 10 in zone environment. Thsi was prod server getting build where on top of this we will install GRC 5.3.
    We have faced no issues in development build.
    But during the Prod build at databse create step, we are getting the below error
    ORA-27102: out of memory
    SVR4 Error: 22: Invalid argument
    Disconnected
    SAPinst log entries where error messages started:
    04:43:58.128
    Execute step createDatabase of component |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|2|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_OraDBCheck|ind|ind|ind|ind|0|0|NW_OraDBMain|ind|ind|ind|ind|0|0|NW_OraDBStd|ind|ind|ind|ind|3|0|NW_OraDbBuild|ind|ind|ind|ind|5|0
    INFO 2011-04-01 04:45:14.590
    Working directory changed to /tmp/sapinst_exe.16718.1301647358.
    INFO 2011-04-01 04:45:14.595
    Working directory changed to /tmp/sapinst_instdir/NW04S/SYSTEM/ORA/CENTRAL/AS.
    INFO 2011-04-01 04:45:14.609
    Working directory changed to /tmp/sapinst_exe.16718.1301647358.
    INFO 2011-04-01 04:45:14.621
    Working directory changed to /tmp/sapinst_instdir/NW04S/SYSTEM/ORA/CENTRAL/AS.
    INFO 2011-04-01 04:45:14.850
    Account oraac5 already exists.
    INFO 2011-04-01 04:45:14.852
    Account dba already exists.
    INFO 2011-04-01 04:45:14.852
    Account oraac5 already exists.
    INFO 2011-04-01 04:45:14.853
    Account dba already exists.
    INFO 2011-04-01 04:45:14.867
    Working directory changed to /tmp/sapinst_exe.16718.1301647358.
    INFO 2011-04-01 04:45:14.899
    Working directory changed to /tmp/sapinst_instdir/NW04S/SYSTEM/ORA/CENTRAL/AS.
    ERROR 2011-04-01 04:45:32.280
    CJS-00084  SQL statement or script failed. DIAGNOSIS: Error message: ORA-27102: out of memory
    SVR4 Error: 22: Invalid argument
    Disconnected
    . SOLUTION: See ora_sql_results.log and the Oracle documentation for details.
    ERROR 2011-04-01 04:45:32.286
    MUT-03025  Caught ESAPinstException in Modulecall: ORA-27102: out of memory
    SVR4 Error: 22: Invalid argument
    Disconnected
    ERROR 2011-04-01 04:45:32.453
    FCO-00011  The step createDatabase with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|2|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_OraDBCheck|ind|ind|ind|ind|0|0|NW_OraDBMain|ind|ind|ind|ind|0|0|NW_OraDBStd|ind|ind|ind|ind|3|0|NW_OraDbBuild|ind|ind|ind|ind|5|0|createDatabase was executed with status ERROR ( Last error reported by the step :Caught ESAPinstException in Modulecall: ORA-27102: out of memory
    SVR4 Error: 22: Invalid argument
    Disconnected
    ora_sql_results.log
    04:45:15 SAPINST ORACLE start logging for
    SHUTDOWN IMMEDIATE;
    exit;
    Output of SQL executing program:
    SQL*Plus: Release 10.2.0.4.0 - Production on Fri Apr 1 04:45:15 2011
    Copyright (c) 1982, 2007, Oracle.  All Rights Reserved.
    Connected to an idle instance.
    ORA-01034: ORACLE not available
    ORA-27101: shared memory realm does not exist
    SVR4 Error: 2: No such file or directory
    Disconnected
    SAPINST: End of output of SQL executing program /oracle/AC5/102_64/bin/sqlplus.
    SAPINST found errors.
    SAPINST The current process environment may be found in sapinst_ora_environment.log.
    2011-04-01, 04:45:15 SAPINST ORACLE stop logging
    ================================================================================
    2011-04-01, 04:45:15 SAPINST ORACLE start logging for
    STARTUP NOMOUNT;
    exit;
    Output of SQL executing program:
    SQL*Plus: Release 10.2.0.4.0 - Production on Fri Apr 1 04:45:15 2011
    Copyright (c) 1982, 2007, Oracle.  All Rights Reserved.
    Connected to an idle instance.
    ORA-27102: out of memory
    SVR4 Error: 22: Invalid argument
    Disconnected
    SAPINST: End of output of SQL executing program /oracle/AC5/102_64/bin/sqlplus.
    SAPINST found errors.
    SAPINST The current process environment may be found in sapinst_ora_environment.log.
    2011-04-01, 04:45:32 SAPINST ORACLE stop logging
    Already viewed S-note
    724713 - parameter settings for Solaris 10 - (Parameters are set as per this note)
    743328 - Composite SAP note: ORA-27102 - (no much information in memory problem on zones)
    Please provide your suggestions/resolution.
    Thankyou.

    Hi,
    @ Sunny: Thanks for response, the referred note was already checked and parameters are in sync as per note.
    @Mohit: SAP wouldn't proceed till create database if Oracle software was not installed. thanks for the response.
    @Markus: Thanks I agree with you, but I have doubt in this area. Isn't it like project.max-shm-memory was new parameter we need to set in local zone rather using shmsys:shminfo_shmmax in /etc/system. Do we need to still maintain this parameter in /etc/system in global zone.
    As per SUN doc below parameter was obsolete from Solaris 10.
    The following parameters are obsolete.
    ■ shmsys:shminfo_shmmni
    ■ shmsys:shminfo_shmmax
    As per your suggestion, do we need to set below parameters in that case, please clarify.
    Parameter                           Replaced by Resource Control      Recommended Value
    semsys:seminfo_semmni   project.max-sem-ids                      100
    semsys:seminfo_semmsl   process.max-sem-nsems               256
    shmsys:shminfo_shmmax  project.max-shm-memory             4294967295
    shmsys:shminfo_shmmni   project.max-shm-ids                       100
    Also   findings of /etc/release
    more /etc/release
    Solaris 10 10/08 s10s_u6wos_07b SPARC
    Regards,
    Sitarama.

Maybe you are looking for

  • 1080i at 30hz instead of 60hz?

    I have a mini-DVI to HDMI adapter for my MacBook. I am trying to connect it to a video projector. Problem is, this video projector is 1080i not p... it only accepts up to 30hz. In the display options, the only refresh rate available is 60hz. Is there

  • My Satellite C wont load Windows - error code 0xcoooooe9

    Hi, get a status error come up when the laptop is turned on. The error code is 0xcoooooe9, windows does not load up and the diagnostics tool does not work. Tried to recover to factory settings but this crashed out saying partition could not be create

  • Not able to call REST service

    Hi, I'm trying to consume a REST service. It seems that its a problem to set the http:query-parameters or http:query-string. I saw this https://blogs.oracle.com/jeffdavies/entry/enhanced_rest_support_in_oracl article and and the one in the OSB 11G De

  • "emails to all names in a group"

    When I try to email all the names in a group I've created in my contacts, it will only take the first 3 names in the group.  Is there something else I need to do.  I have 50 names in this group I would like to email all at once.

  • Need documentation on Multiprovider

    Hi, I am developing Multiprovider on 3 ODS and 1 Cube. i don't have proper document on multiprovider. can anybody have the documentation on multiprovider. Thanks Madhu