J2EE Engine Deployment Error

I have written the betting pool applicaton for Soccer world Cup (/people/raphael.vogel/blog/2006/05/18/writing-a-betting-pool-application-for-the-soccer-world-cup-2006-part-i)
now i would like to deploy to j2ee Engine((/people/raphael.vogel/blog/2006/05/18/writing-a-betting-pool-application-for-the-soccer-world-cup-2006-part-ii), Deploy and test the Services)
but i receive follow error:
01.06.2006 14:57:28 /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
[029]Deployment aborted
Settings
SDM host : uxept01
SDM port : 50118
URL to deploy : file:/C:/DOKUME1/FICHTE1/LOKALE1/Temp/temp46974sap.comwc~metadata.ear
Result
=> deployment aborted : file:/C:/DOKUME1/FICHTE1/LOKALE1/Temp/temp46974sap.comwc~metadata.ear
Aborted: development component 'wc/metadata'/'sap.com'/'local'/'20060601143708':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/wc_metadata.ear. Reason: None of the available containers recognized the components of application sap.com/wc~metadata; it is not possible to make deploy. (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment exception : The deployment of at least one item aborted
Can anybody help me please
Thanks
Julia
Message was edited by: Julia Fichtel
Message was edited by: Julia Fichtel

I also had this error and was solved with just uninstalling everything and reinstalling it again.
I followed the following steps proposed in other forum:
Regards,
María Margarita Monteverde
Hello Andre,
It seems that you'd already an NWDS installation on your machine that wasn't de-installed completely. Before you install an new NWDS you must be sure that the following steps have been checked:
1) Having completely run the de-installation routine of the NWDS
2) It’s recommended to delete the directories “c:program filessapide” and “c:program filessapjdt” to be sure that there won’t stay any ‘old’ files.
3) Furthermore you should delete the folder ‘workspace’ (including all files and subfolders) in the path ‘c:documents and settingsDocumentsSAP’ (where d012345 is your username). Or move this folder somewhere in the file system, afterwards you may re-import the 'old' projects.
4) It's recommended to delete all .dtr/.dtc/.metadata directories in your personal folder (e.g. C:Documents and Settingsd0abcde).
Please stop the IDE before you do all these steps.
Regards,
Jan
Message was edited by:
        Maria Margarita Monteverde

Similar Messages

  • J2ee application deployment error

    Hi All,
             I have created a J2ee application. I have created a EJB module project in which i have created a session bean. Also I have created a Web module project, i am referring the above created EJB in this web module. Both these projects are added to one enterprise application.While deploying this ear file to j2ee engine I am getting following error.
    Aborted: development component 'TestEAR'/'sap.com'/'localhost'/'2007.06.28.10.34.29'/'0':
    Caught exception during application deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: Cannot deploy application sap.com/TestEAR.. Reason: Exception during generation of components of application sap.com/TestEAR in container EJBContainer.; nested exception is:      com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application sap.com/TestEAR in container EJBContainer.
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Deployment exception : The deployment of at least one item aborted
    Please can anybody tell me what is going wrong?
    I am using NW 2004s.
    Cheers
    jayant

    I have the same problem. I retart the SDM.and del the app in VA,It is OK now.

  • J2EE Engine start error: Database initialization failed!

    My J2EE engine now fails to start - jcontrol stays yellow.  I've followed Troubleshooting pages from help.sap.com Admin manual topic "starting J2EE Engine".
    Background:
    I was running through JDI Scenario 2+ on a fresh installed WebAS 6.40 at SP9.  Using NWDevStudio2.09, I attempted to load a DC, but servers stopped responding.  So I downed everything (in MMC) including offlining the DB, then put DB back online and restart the J2E engine, and now jcontrol stays yellow. 
    I find this in the file log_bootstrap_ID0014430.0.log:
    Apr 7, 2005 3:10:23 PM  ] Bootstrap MODE:
    [Apr 7, 2005 3:10:23 PM  ] <INSTANCE GLOBALS>
    [Apr 7, 2005 3:10:23 PM  ]  determined by parameter [ID0014430].
    [Apr 7, 2005 3:10:23 PM  ] -
    [Apr 7, 2005 3:10:26 PM  ] Exception occured:
    com.sap.engine.bootstrap.SynchronizationException: Database initialization failed! Check database properties!
         at com.sap.engine.bootstrap.Bootstrap.initDatabaseConnection(Bootstrap.java:422)
         at com.sap.engine.bootstrap.Bootstrap.<init>(Bootstrap.java:144)
         at com.sap.engine.bootstrap.Bootstrap.main(Bootstrap.java:813)
    .........a few lines cut out here..........
         at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
    ==[ Caused by: ]==----
    com.sap.engine.frame.core.configuration.ConfigurationException: Error while connecting to DB.
         at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.createConnection(DBConnectionPool.java:344)
    ............ a few lines cut out here..........
         at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
    Caused by: com.sap.dbtech.jdbc.exceptions.JDBCDriverException: SAP DBTech JDBC: Cannot connect to jdbc:sapdb://PHI21811/J2E [Cannot connect to host PHI21811 [Connection refused: connect], -813.].
         at com.sap.dbtech.jdbc.DriverSapDB.connect(DriverSapDB.java:183)
         at com.sap.sql.jdbc.NativeConnectionFactory.createNativeConnection(NativeConnectionFactory.java:219)
         at com.sap.sql.connect.OpenSQLDataSourceImpl.createPooledConnection(OpenSQLDataSourceImpl.java:570)
         at com.sap.sql.connect.OpenSQLDataSourceImpl.getPooledConnection(OpenSQLDataSourceImpl.java:263)
         at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.createConnection(DBConnectionPool.java:294)
         ... 14 more
    [Apr 7, 2005 3:10:26 PM  ] [Bootstrap module]> Problem occured while performing synchronization.
    [Apr 7, 2005 3:22:24 PM  ] -
    ANYONE HAVE ANY SUGGESTIONS?????

    Using the Database Administration section of the help.sap.com library, I found the location of SAPDB/MySQL log files.  They are in C:\sapdb\data\wrk\J2E.  In 'knldiag' I found entries complaining of Log files being full and tasks put in suspension.
    So I figured out to do a full back up of the DB and/or backup the log files.  The log file bar (in MMC) still showed 100% full, but I figured out to refresh the view and voila it was empty (so one of the backups emptied it, not sure which one).
    After that the DB comes up fine and now my J2E WebAS goes all green.
    Message was edited by: Michael W Rains

  • J2ee engine startup error- cant attach shared memory

    Hello Experts,
    We have upgraded ERP abap+java to EHP4 but J2ee engine is not coming up. It is giving the following errors. There are no issues on the abap side.
    Bootstrap logs are fine and are able to syncronize.
    Following is the dev_jcontrol log.
    JStartupIReadSection: read node properties [ID44702600]
    -> node name          : dispatcher
    -> node type          : dispatcher
    -> node execute       : yes
    -> java path          : /usr/j2se
    -> java parameters    : -Djava.security.policy=.\java.policy -Djava.security.egd
    =file:/dev/urandom -XX:NewSize=181M -XX:MaxNewSize=181M -XX:+DisableExplicitGC -
    verbose:gc -Xloggc:GC.log
    -> java vm version    : 1.4.2_13-b06
    -> java vm vendor     : Java HotSpot(TM) 64-Bit Server VM (Sun Microsystems Inc.
    -> java vm type       : server
    -> java vm cpu        : sparcv9
    -> heap size          : 544M
    -> init heap size     : 544M
    -> root path          : /usr/sap/DV2/DVEBMGS04/j2ee/cluster/dispatcher
    -> class path         : ./bin/boot/boot.jar:./bin/system/bytecode.jar:.
    -> OS libs path       : /usr/sap/DV2/DVEBMGS04/j2ee/os_libs
    -> main class         : com.sap.engine.boot.Start
    -> framework class    : com.sap.bc.proj.jstartup.JStartupFramework
    -> registr. class     : com.sap.bc.proj.jstartup.JStartupNatives
    -> framework path     : /usr/sap/DV2/SYS/exe/run/jstartup.jar:/usr/sap/DV2/SYS/e
    xe/run/jvmx.jar
    -> parameters         :
    -> debuggable         : no
    -> debug mode         : no
    -> debug port         : 60000
    -> shutdown timeout   : 120000
    [Thr  1] [Node: server0] java home is set by profile parameter
            Java Home: /usr/j2se
    [Thr  1] JStartupICheckFrameworkPackage: can't find framework package /usr/sap/D
    V2/SYS/exe/run/jvmx.jar
    JStartupIReadSection: read node properties [ID44702650]
    -> node name          : server0
    -> node type          : server
    -> node execute       : yes
    -> jlaunch parameters :
    -> java path          : /usr/j2se
    -> java parameters    : -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.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jt
    s.ots.PortableInterceptor.JTSInitializer -Djco.jarm=1 -Dsun.io.useCanonCaches=fa
    lse -XX:NewSize=341m -XX:MaxNewSize=341m -XX:MaxPermSize=192m -Djava.awt.headles
    s=true -XX:PermSize=192m -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -XX:Soft
    RefLRUPolicyMSPerMB=1 -verbose:gc -XX:DisableExplicitGC -XX:PrintGCDetails -XX
    :PrintGCTimeStamps -XX:UseParNewGC -Drdbms.driverLocation=/oracle/DV2/920_64/j
    dbc/lib/classes12.jar -Dsys.global.dir=/sapmnt/DV2/global -Xms2048m
    -> java vm version    : 1.4.2_13-b06
    -> java vm vendor     : Java HotSpot(TM) 64-Bit Server VM (Sun Microsystems Inc.
    -> java vm type       : server
    -> java vm cpu        : sparcv9
    -> heap size          : 2048M
    -> init heap size     : 1024M
    -> root path          : /usr/sap/DV2/DVEBMGS04/j2ee/cluster/server0
    -> class path         : ./bin/boot/boot.jar:./bin/boot/jaas.jar:./bin/system/byt
    ecode.jar:.
    -> OS libs path       : /usr/sap/DV2/DVEBMGS04/j2ee/os_libs
    -> main class         : com.sap.engine.boot.Start
    -> framework class    : com.sap.bc.proj.jstartup.JStartupFramework
    -> registr. class     : com.sap.bc.proj.jstartup.JStartupNatives
    -> framework path     : /usr/sap/DV2/SYS/exe/run/jstartup.jar:/usr/sap/DV2/SYS/e
    xe/run/jvmx.jar
    -> parameters         :
    -> debuggable         : no
    -> debug mode         : no
    -> debug port         : 50421
    -> shutdown timeout   : 120000
    [Thr  1] [Node: server1] java home is set by profile parameter
            Java Home: /usr/j2se
    [Thr  1] JStartupICheckFrameworkPackage: can't find framework package /usr/sap/D
    V2/SYS/exe/run/jvmx.jar
    JStartupIReadSection: read node properties [ID44702651]
    -> node name          : server1
    -> node type          : server
    -> node execute       : yes
    -> java path          : /usr/j2se
    -> java parameters    : -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.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jt
    s.ots.PortableInterceptor.JTSInitializer -Djco.jarm=1 -XX:MaxPermSize=192M -XX:P
    ermSize=192M -XX:NewSize=170M -XX:MaxNewSize=170M -XX:+DisableExplicitGC -verbos
    e:gc -Xloggc:GC.log -XX:PrintGCDetails -XX:PrintGCTimeStamps -Djava.awt.headle
    ss=true -Dsun.io.useCanonCaches=false -XX:SoftRefLRUPolicyMSPerMB=1 -XX:Survivor
    Ratio=2 -XX:TargetSurvivorRatio=90 -Dorg.omg.PortableInterceptor.ORBInitializerC
    lass=com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer
    -> java vm version    : 1.4.2_13-b06
    -> java vm vendor     : Java HotSpot(TM) 64-Bit Server VM (Sun Microsystems Inc.
    -> java vm type       : server
    -> java vm cpu        : sparcv9
    -> heap size          : 2048M
    -> init heap size     : 1024M
    -> root path          : /usr/sap/DV2/DVEBMGS04/j2ee/cluster/server1
    -> class path         : ./bin/boot/boot.jar:./bin/boot/jaas.jar:./bin/system/byt
    ecode.jar:.
    -> OS libs path       : /usr/sap/DV2/DVEBMGS04/j2ee/os_libs
    -> main class         : com.sap.engine.boot.Start
    -> framework class    : com.sap.bc.proj.jstartup.JStartupFramework
    -> registr. class     : com.sap.bc.proj.jstartup.JStartupNatives
    -> framework path     : /usr/sap/DV2/SYS/exe/run/jstartup.jar:/usr/sap/DV2/SYS/e
    xe/run/jvmx.jar
    -> parameters         :
    -> debuggable         : yes
    -> debug mode         : no
    -> debug port         : 50426
    -> shutdown timeout   : 120000
    [Thr  1] INFO: Invalid property value [Debbugable=yes]
    [Thr  1] [Node: SDM] java home is set by profile parameter
            Java Home: /usr/j2se
    [Thr  1] JStartupICheckFrameworkPackage: can't find framework package /usr/sap/D
    V2/SYS/exe/run/jvmx.jar
    JStartupIReadSection: read node properties [sdm]
    -> node name          : SDM
    -> node type          : sdm
    -> node execute       : yes
    -> java path          : /usr/j2se
    -> java parameters    :
    -> java vm version    : 1.4.2_08-b03
    -> java vm vendor     : Java HotSpot(TM) 64-Bit Server VM (Sun Microsystems Inc.
    -> java vm type       : server
    -> java vm cpu        : sparcv9
    -> heap size          : 512M
    -> root path          : /usr/sap/DV2/DVEBMGS04/SDM/program
    -> class path         : /usr/sap/DV2/DVEBMGS04/SDM/program/bin/SDM.jar
    -> OS libs path       : /usr/sap/DV2/DVEBMGS04/j2ee/os_libs
    -> main class         : SDMInternal
    -> framework class    : com.sap.bc.proj.jstartup.JStartupFramework
    -> registr. class     : com.sap.bc.proj.jstartup.JStartupNatives
    -> framework path     : /usr/sap/DV2/SYS/exe/run/jstartup.jar:/usr/sap/DV2/SYS/e
    xe/run/jvmx.jar
    -> shutdown class     : com.sap.sdm.jstartup.shutdown.InternalShutDown
    -> parameters         : server sdmhome=/usr/sap/DV2/DVEBMGS04/SDM/program
    -> debuggable         : yes
    -> debug mode         : no
    -> debug port         : 60000
    -> shutdown timeout   : 120000
    [Thr  1] ***LOG Q0I=> NiIWrite: writev (32: Broken pipe) [nixxi.cpp 3803]
    [Thr  1] *** ERROR => NiIWrite: SiSendV failed for hdl 2 / sock 13
        (SI_ECONN_BROKEN/32; UD; ST; 172.20.40.15:3601) [nixxi.cpp    3803]
    [Thr  1] *** ERROR => MsINiWrite: NiBufSend (rc=NIECONN_BROKEN) [msxxi_mt.c   24
    80]
    [Thr  1] *** ERROR => MsIDetach: MsINiWrite (rc=NIECONN_BROKEN) [msxxi_mt.c   11
    46]
    [Thr  1]
    [Thr  1] *  ERROR       mserrno received (MSEACCESSDENIED)
    [Thr  1] *
    TIME        Wed Oct  6 14:34:06 2010
    [Thr  1] *  RELEASE     700
    [Thr  1] *  COMPONENT   MS (message handling interface, multithreaded)
    [Thr  1] *  VERSION     4
    [Thr  1] *  RC          -24
    [Thr  1] *  MODULE      msxxi_mt.c
    [Thr  1] *  LINE        810
    [Thr  1] *  COUNTER     2
    [Thr  1] *
    [Thr  1] *****************************************************************************
    [Thr  1] *** WARNING => Can't attach to message server (aeerpdv1/3601) [rc = -20]-> reconnect [jcntrms_mt.c 368]
    [Thr  1] Wed Oct  6 14:34:11 2010
    [Thr  1] ***LOG Q0I=> NiIWrite: writev (32: Broken pipe) [nixxi.cpp 3803]
    [Thr  1] *** ERROR => NiIWrite: SiSendV failed for hdl 2 / sock 13
        (SI_ECONN_BROKEN/32; UD; ST; 172.20.40.15:3601) [nixxi.cpp    3803]
    [Thr  1] *** ERROR => MsINiWrite: NiBufSend (rc=NIECONN_BROKEN) [msxxi_mt.c   2480]
    [Thr  1] *** ERROR => MsIDetach: MsINiWrite (rc=NIECONN_BROKEN) [msxxi_mt.c   1146]
    [Thr  1]
    [Thr  1] *  ERROR       mserrno received (MSEACCESSDENIED)
    [Thr  1] *
    TIME        Wed Oct  6 14:34:11 2010
    [Thr  1] *  RELEASE     700
    [Thr  1] *  COMPONENT   MS (message handling interface, multithreaded)
    [Thr  1] *  VERSION     4
    [Thr  1] *  RC          -24
    [Thr  1] *  MODULE      msxxi_mt.c
    [Thr  1] *  LINE        810
    [Thr  1] *  COUNTER     4
    [Thr  1] *
    [Thr  1] *****************************************************************************
    [Thr  1] *** WARNING => Can't attach to message server (aeerpdv1/3601) [rc = -20]-> reconnect [jcntrms_mt.c 368]
    [Thr  1] Wed Oct  6 14:34:16 2010
    [Thr  1]
    Please advise and help.
    Thanks,
    Antarpreet

    Hello Sunny,
    Thanks for your help.
    All the other relavant logs look fine to me. The default traces of server0, server1 are not being populated. Niether is there any change in dispatcher and bootstrap logs.
    Here are the other logs:
    aeerpdv1:dv2adm 127% tail -20 dev_bootstrap_ID44702650
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readSequence
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/TypeMappingImpl initializeRelations
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/GeneratedComplexType _loadInto
    [Thr  4] JHVM_LoadJavaVM: Java VM created OK.
    JHVM_BuildArgumentList: main method arguments of node [server0 bootstrap]
    -> arg[  0]: com.sap.engine.bootstrap.Bootstrap
    -> arg[  1]: ./bootstrap
    -> arg[  2]: ID044702650
    [Thr  4] Thu Oct  7 01:44:54 2010
    [Thr  4] JHVM_RegisterNatives: registering methods in com.sap.bc.krn.perf.PerfTimes
    [Thr  5] Thu Oct  7 01:44:57 2010
    [Thr  5] JLaunchIExitJava: exit hook is called (rc = 0)
    [Thr  5] SigISetIgnoreAction : SIG_IGN for signal 18
    [Thr  5] JLaunchCloseProgram: good bye (exitcode = 0)
    aeerpdv1:dv2adm 128%
    aeerpdv1:dv2adm 128% tail jvm_bootstrap_ID44702651.out
    ...Synched ok!
    Synchronizing file [/usr/sap/DV2/DVEBMGS04/j2ee/cluster/server1/dtd/application-j2ee-engine.dtd].
    ...Synched ok!
    Synchronizing file [/usr/sap/DV2/DVEBMGS04/j2ee/cluster/server1/dtd/application-client-additional.dtd].
    ...Synched ok!
    Synchronizing file [/usr/sap/DV2/DVEBMGS04/j2ee/cluster/server1/dtd/db-init.dtd].
    ...Synched ok!
    Ok! (46 ms)
    Done!
    Synch time: 3537 ms
    aeerpdv1:dv2adm 131% tail dev_bootstrap_ID44702651
    [Thr  4] Thu Oct  7 01:45:00 2010
    [Thr  4] JHVM_RegisterNatives: registering methods in com.sap.bc.krn.perf.PerfTimes
    [Thr  5] Thu Oct  7 01:45:03 2010
    [Thr  5] JLaunchIExitJava: exit hook is called (rc = 0)
    [Thr  5] SigISetIgnoreAction : SIG_IGN for signal 18
    [Thr  5] JLaunchCloseProgram: good bye (exitcode = 0)
    tail dev_disp
    Thu Oct  7 01:42:40 2010
    J2EE server info
      start = TRUE
      state = STARTED
      pid = 3355
      argv[0] = /usr/sap/DV2/DVEBMGS04/j2ee/os_libs/jcontrol
      argv[1] = jcontrol
      argv[2] = pf=/usr/sap/DV2/SYS/profile/DV2_DVEBMGS04_aeerpdv1
      argv[3] = -DSAPSTART=1
      argv[4] = -DCONNECT_PORT=64996
      argv[5] = -DSAPSYSTEM=04
      argv[6] = -DSAPSYSTEMNAME=DV2
      argv[7] = -DSAPMYNAME=aeerpdv1_DV2_04
      argv[8] = -DSAPPROFILE=/usr/sap/DV2/SYS/profile/DV2_DVEBMGS04_aeerpdv1
      argv[9] = -DFRFC_FALLBACK=ON
      argv[10] = -DFRFC_FALLBACK_HOST=localhost
      start_lazy = 0
      start_control = SAP J2EE startup framework
    DpJ2eeStart: j2ee state = STARTED
    DpJ2eeLogin: j2ee state = CONNECTED
    Thu Oct  7 01:44:09 2010
    *** ERROR => DpJ2eeMsgProcess: NiRead failed (NIECONN_BROKEN) [dpxxj2ee.c   1212]
    DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)
    Thu Oct  7 01:44:20 2010
    DpJ2eeEmergencyShutdown: j2ee state = SHUTDOWN
    Thu Oct  7 01:44:40 2010
    J2EE server info
      start = TRUE
      state = STARTED
      pid = 3417
      argv[0] = /usr/sap/DV2/DVEBMGS04/j2ee/os_libs/jcontrol
      argv[1] = jcontrol
      argv[2] = pf=/usr/sap/DV2/SYS/profile/DV2_DVEBMGS04_aeerpdv1
      argv[3] = -DSAPSTART=1
      argv[4] = -DCONNECT_PORT=64995
      argv[5] = -DSAPSYSTEM=04
      argv[6] = -DSAPSYSTEMNAME=DV2
      argv[7] = -DSAPMYNAME=aeerpdv1_DV2_04
      argv[8] = -DSAPPROFILE=/usr/sap/DV2/SYS/profile/DV2_DVEBMGS04_aeerpdv1
      argv[9] = -DFRFC_FALLBACK=ON
      argv[10] = -DFRFC_FALLBACK_HOST=localhost
      start_lazy = 0
      start_control = SAP J2EE startup framework
    DpJ2eeStart: j2ee state = STARTED
    DpJ2eeLogin: j2ee state = CONNECTED
    Thu Oct  7 01:46:09 2010
    *** ERROR => DpJ2eeMsgProcess: NiRead failed (NIECONN_BROKEN) [dpxxj2ee.c   1212]
    DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)
    Thu Oct  7 01:46:20 2010
    DpJ2eeEmergencyShutdown: j2ee state = SHUTDOWN
    Thu Oct  7 01:46:40 2010
    DpHdlDeadWp: restart wp (pid=3015) automatically
    DpEnvCheckJ2ee: switch off j2ee start flag
    Please help, struck in a very bad situation.
    Regards,
    Antarpreet

  • J2EE Engine Jcontrol Error :Oracle upgrade 10 to11  :ODBC driver Solution

    Hello Every one,
    To  make a valuable information for Oracle upgrade from Oracle 10 to oracle 11.2.0.2 on Java environment.
    Please do the following changes to avoid JDBC driver version error.
    Memo : When The upgrade happens the JDBC drivers are overwritten under drive:/oracle/.../JDBC/lib
    you will not see classes12.jar and nls_charset12.jar which is a part of Oracle 10 and JDBC driver version. Thereis no such files for Oracle 11. The application is not supported under Oracle 11.
    Following steps will make the J2ee Engine work.
    1. Upgrade SDK to 1.6. and verify using Java -version. Set Path and Class path.
    2. Since the Jdk is changed now do update in this 3 files
      a. SID_JC01_hostname 
    In this file update the parameter "jstartup/vm/home = C:\Program Files\Java\jdk1.6.0_26"
    b. Also for SID_SCS00_Hostname
    3. Check for j2ee/dbdriver = $(DIR_EXECUTABLE)\ojdbc14.jar    which can work with this version at this time or need to change to ojdbc6.jar
    in profile parameter, bootstrap properties (:\usr\sap\sid\jc01\j2ee\cluster\bootstrap), and template configuaration file in usr\sap\sid\jc01\j2ee
    4. Copy classes12.jar and nls_charset12.jar in \oracle\jdbc\lib from any Oracle 10 installation. and set in classpath.
    5. Hope last the password in secure  store is correct.
    Restart the cluster.
    This is exclusively of your oracle is upgraded and J2ee does not come up.
    Regards,
    Chetan Poojary.

    I think you'd need to contact Oracle support to get access to older versions of the driver.
    Since 8.0.5 isn't supported any longer, however, is it possible for you to update your Oracle client to one of the supported releases-- 8.1.7 or 9i?
    Justin

  • J2ee Application Deployed,error connecting to 9i db

    Hi,
    I am working on a Oracle 10g 9.0.4 AS and a Oracle 9i db, both of which I have just installed on red Hat Linux 2.1 Advanced Server.
    I have deployed a j2ee ear file in an OC4J container. The deployment works fine as I get the login page correctly. But it fails to go further than that and gives an error "contact system administrator".The Http Server logs show the following error messages :
    [Fri Mar 25 13:07:22 2005] [error] [client 127.0.0.1] [ecid: 172.16.117.169:61745:1111736242948,2] MOD_OC4J_0015: recv() returns 0. There
    has no message available to be received and oc4j has gracefully (orderly) closed the connection.
    [Fri Mar 25 13:07:22 2005] [error] [client 127.0.0.1] [ecid: 172.16.117.169:61745:1111736242948,2] MOD_OC4J_0054: Failed to call network
    routine to receive an ajp13 message from oc4j.
    [Fri Mar 25 13:07:22 2005] [error] [client 127.0.0.1] [ecid: 172.16.117.169:61745:1111736242948,2] MOD_OC4J_0033: Failed to receive an
    ajp13 message from oc4j.
    [Fri Mar 25 13:07:22 2005] [warn] [client 127.0.0.1] [ecid: 172.16.117.169:61745:1111736242948,2] MOD_OC4J_0078: Network connection errors
    happened to host: midtier.mastek.com and port: 3303 while receiving the first response from oc4j. This request is recoverable.
    I have configured a user in the database with the reqd schema and also a datasource pointing to it and whose jndi name I have specified in the application.
    Also, I get an error saying in the OC4J container :
    05/03/25 13:02:28 log4j:WARN No appenders could be found for logger (org.apache.struts.util.PropertyMessageResources).
    05/03/25 13:02:28 log4j:WARN Please initialize the log4j system properly.
    indicating that mebbe the logging hasnt been successfully installed and that's mebbe why I am not getting proper error messages.
    I am thinking that there maybe some error in the connection to the 9i database, but cant figure out what.
    PLEASE,PLEASE HELLLLPPPPP!!!!

    Also got these in logs
    emias.log
    com.evermind.server.http.HttpIOException: Broken pipe ---> Enterprise Manager
    em-application.log
    Broken pipe sometimes followed with : java.io.FileNotFoundException: Could not find ias/.uix
    and                    : java.io.FileNotFoundException: Could not find ias/clusters/.uix
    OHS errors :
    [warn] [client 127.0.0.1] MOD_OC4J_0078: Network connection errors happened to host: midtier.mastek.com and port: 3303 while receiving
    the first response from oc4j. This request is recoverable.
    March 25, 2005 12:47:15 PM IST HTTP_Server Error ohs [error] [client 172.16.117.254] (32)Broken pipe: MOD_OC4J_0087: Got an unexpected error while calling send() to send a message to oc4j
    and the error code is 32.
    March 25, 2005 12:47:15 PM IST HTTP_Server Error ohs [error] [client 172.16.117.254] MOD_OC4J_0053: Failed to call network routine to send out an ajp13 buffer message to oc4j.
    March 25, 2005 12:47:15 PM IST HTTP_Server Error ohs [error] [client 172.16.117.254] MOD_OC4J_0032: Failed to send out an ajp13 message to oc4j.
    March 25, 2005 12:47:21 PM IST HTTP_Server Error ohs [error] [client 127.0.0.1] MOD_OC4J_0015: recv() returns 0. There has no message available to be received and oc4j has gracefully (orderly)
    closed the connection.
    March 25, 2005 12:47:21 PM IST HTTP_Server Error ohs [error] [client 127.0.0.1] MOD_OC4J_0054: Failed to call network routine to receive an ajp13 message from oc4j.
    March 25, 2005 12:47:21 PM IST HTTP_Server Error ohs [error] [client 127.0.0.1] MOD_OC4J_0033: Failed to receive an ajp13 message from oc4j.

  • J2EE application deploy error

    Hi!
    thank you for see my question.
    when I deploy EJB Model to Oracle 10 AS, the server notice exception like this
    "java.rmi.RemoteException
    deploy failed!: ; nested exception is:
    oracle.oc4j.admin.internal.DeployerException: Unknown assembly root-tag attribute: xmlns. deploy failed!: ; nested exception is:
    oracle.oc4j.admin.internal.DeployerException: Unknown assembly root-tag attribute: xmlns".
    and I deploied a JSF Application to Oracle 10g AS, but the Faces Servlets cann't be used.
    please help me, thank you so much.

    What specific versions are you using? It sounds like you are deploying a J2EE 1.4 based application (from JDev 10.1.3) to OC4J/OracleAS 10.1.2. That version of the server implements J2EE 1.3 which used DTDs and not XML schema. Thus when you are throwing some schema at it, it's not able to handle it.
    Using OC4J/OracleAS 10.1.3 should solver this problem.
    -steve-

  • Error in Online Deployment patching J2EE Engine

    Hi,
    We are installing the J2EE engine in a BW server with Windows S.O. In step "Deploy Online" we obtain the following error:
    Sep 13, 2006 8:23:22 AM  Info: Start logging to console
    Sep 13, 2006 8:23:22 AM  Info:
    Sep 13, 2006 8:23:22 AM  Info: ============================================
    Sep 13, 2006 8:23:22 AM  Info: =   Starting to execute command 'deploy'   =
    Sep 13, 2006 8:23:22 AM  Info: ============================================
    Sep 13, 2006 8:23:22 AM  Info: Starting SDM - Software Deployment Manager...
    Sep 13, 2006 8:23:23 AM  Info: tc/SL/SDM/SDM/sap.com/SAP AG/6.4018.00.0000.20060706111659.0000
    Sep 13, 2006 8:23:24 AM  Info: SDM operation mode successfully set to: Standalone
    Sep 13, 2006 8:23:25 AM  Info: Initializing Network Manager (50017)
    Sep 13, 2006 8:23:25 AM  Info: Checking if another SDM is running on port 50018
    Sep 13, 2006 8:23:25 AM  Info: -
    Starting deployment -
    Sep 13, 2006 8:23:25 AM  Info: Error handling strategy: OnErrorStop
    Sep 13, 2006 8:23:25 AM  Info: Prerequisite error handling strategy: OnPrerequisiteErrorStop
    Sep 13, 2006 8:23:25 AM  Info: Update strategy: UpdateLowerVersions
    Sep 13, 2006 8:23:25 AM  Info: Starting deployment prerequisites:
    Sep 13, 2006 8:23:31 AM  Info: Loading selected archives...
    Sep 13, 2006 8:23:31 AM  Info: Loading archive 'E:\18_0-20000118_directory\J2EE-RUNT-CD\J2EE-ENG\ONLINE\SAPJTECHS18_0.SCA'
    Sep 13, 2006 8:23:38 AM  Info: Selected archives successfully loaded.
    Sep 13, 2006 8:23:39 AM  Info: Actions per selected component:
    Sep 13, 2006 8:23:39 AM  Info: No action: Selected development component 'com.sap.aii.ibtranslationclient'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'1' will not update currently deployed development component 'com.sap.aii.ibtranslationclient'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'com.sap.security.core.admin'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111713.0000'/'1' updates currently deployed development component 'com.sap.security.core.admin'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060426183247.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: No action: Selected development component 'com.sap.rprof.jddschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413101559.0000'/'1' will not update currently deployed development component 'com.sap.rprof.jddschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413101559.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/wd/wslib'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060726153907.0000'/'1' updates currently deployed development component 'tc/wd/wslib'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060503180106.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/workflowmodeler'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050606172955.0000'/'1' updates currently deployed development component 'tc/workflowmodeler'/'sap.com'/'SAP AG'/'6.4017.00.0000.20050606172955.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'com.sap.lcr.saprfc'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'1' updates currently deployed development component 'com.sap.lcr.saprfc'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413101546.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/wd/pdfsvrchal'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112627.0000'/'1' updates currently deployed development component 'tc/wd/pdfsvrchal'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413102720.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: No action: Selected development component 'com.sap.aii.util.rb'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'1' will not update currently deployed development component 'com.sap.aii.util.rb'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'com.sap.util.monitor.grmg'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050818153022.0000'/'1' updates currently deployed development component 'com.sap.util.monitor.grmg'/'sap.com'/'SAP AG'/'6.4017.00.0000.20050818153022.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: No action: Selected development component 'com.sapportals.supportplatform.dbschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111519.0000'/'1' will not update currently deployed development component 'com.sapportals.supportplatform.dbschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111519.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: No action: Selected development component 'com.sap.engine.customizing.ccms'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060814115206.0000'/'1' will not update currently deployed development component 'com.sap.engine.customizing.ccms'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060814115206.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/supportplatform/engine'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111519.0000'/'1' updates currently deployed development component 'tc/supportplatform/engine'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413101310.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/SL/utility/wsear'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060119145451.0000'/'1' updates currently deployed development component 'tc/SL/utility/wsear'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060119145451.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: No action: Selected development component 'com.sap.lcr.namealloc'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'1' will not update currently deployed development component 'com.sap.lcr.namealloc'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/bcb/api'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050606172625.0000'/'1' updates currently deployed development component 'tc/bcb/api'/'sap.com'/'SAP AG'/'6.4017.00.0000.20050606172625.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: No action: Selected development component 'SQLTrace'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112013.0000'/'1' will not update currently deployed development component 'SQLTrace'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112013.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'com.sap.lcr'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'1' updates currently deployed development component 'com.sap.lcr'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413101546.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'com.sap.rprof.remoteProfile'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413101559.0000'/'1' updates currently deployed development component 'com.sap.rprof.remoteProfile'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413101559.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'com.sapmarkets.mesyncjco'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413101332.0000'/'1' updates currently deployed development component 'com.sapmarkets.mesyncjco'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413101332.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: No action: Selected development component 'tc/TechSrv/xml_das_connector_init'/'sap.com'/'SAP AG'/'6.4018.00.0000.20051027101045.0000'/'1' will not update currently deployed development component 'tc/TechSrv/xml_das_connector_init'/'sap.com'/'SAP AG'/'6.4018.00.0000.20051027101045.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: No action: Selected development component 'tc/uddi/dbschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050606164207.0000'/'1' will not update currently deployed development component 'tc/uddi/dbschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050606164207.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/sec/wssec/app'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111002.0000'/'1' updates currently deployed development component 'tc/sec/wssec/app'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413100412.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: No action: Selected development component 'tc/TechSrv/XML_DAS_Connector_Schema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20051027101045.0000'/'1' will not update currently deployed development component 'tc/TechSrv/XML_DAS_Connector_Schema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20051027101045.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/wd/tools'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112627.0000'/'1' updates currently deployed development component 'tc/wd/tools'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413102720.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'com.sap.util.monitor.jarm.j2ee'/'sap.com'/'SAP AG'/'6.4018.00.0000.20051027104030.0000'/'1' updates currently deployed development component 'com.sap.util.monitor.jarm.j2ee'/'sap.com'/'SAP AG'/'6.4017.00.0000.20051027104030.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/wd/dispwda'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060726153907.0000'/'1' updates currently deployed development component 'tc/wd/dispwda'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060503180106.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'com.sapportals.htmlb'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050121164722.0000'/'1' updates currently deployed development component 'com.sapportals.htmlb'/'sap.com'/'SAP AG'/'6.4017.00.0000.20050121164722.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/bcb/ici'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050606172625.0000'/'1' updates currently deployed development component 'tc/bcb/ici'/'sap.com'/'SAP AG'/'6.4017.00.0000.20050606172625.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: No action: Selected development component 'synclog'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112013.0000'/'2' will not update currently deployed development component 'synclog'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112013.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/monitoring/systeminfo'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060814115206.0000'/'1' updates currently deployed development component 'tc/monitoring/systeminfo'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060427163646.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: No action: Selected development component 'com.sap.aii.util.misc'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'1' will not update currently deployed development component 'com.sap.aii.util.misc'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: No action: Selected development component 'tc/sld/data'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'1' will not update currently deployed development component 'tc/sld/data'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/TechSrv/XML_DAS_Connector'/'sap.com'/'SAP AG'/'6.4018.00.0000.20051027101045.0000'/'1' updates currently deployed development component 'tc/TechSrv/XML_DAS_Connector'/'sap.com'/'SAP AG'/'6.4017.00.0000.20051027101045.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: No action: Selected development component 'com.sap.aii.proxy.framework'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'1' will not update currently deployed development component 'com.sap.aii.proxy.framework'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'com.sapportals.supportplatform'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111519.0000'/'1' updates currently deployed development component 'com.sapportals.supportplatform'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413101310.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Initial deployment: Selected software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.6.40.18.0.20060816080857''/'1' will be deployed.
    Sep 13, 2006 8:23:39 AM  Info: No action: Selected development component 'com.sap.engine.docs.examples'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060814115206.0000'/'1' will not update currently deployed development component 'com.sap.engine.docs.examples'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060814115206.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: No action: Selected development component 'com.sap.engine.class.download'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060814115206.0000'/'1' will not update currently deployed development component 'com.sap.engine.class.download'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060814115206.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: No action: Selected development component 'com.sap.lcr.jddschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'1' will not update currently deployed development component 'com.sap.lcr.jddschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'com.sap.util.monitor.jarm.ccms'/'sap.com'/'SAP AG'/'6.4018.00.0000.20051027104030.0000'/'1' updates currently deployed development component 'com.sap.util.monitor.jarm.ccms'/'sap.com'/'SAP AG'/'6.4017.00.0000.20051027104030.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/sec/vsi/app'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111002.0000'/'1' updates currently deployed development component 'tc/sec/vsi/app'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413100412.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/uddi'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050606164207.0000'/'1' updates currently deployed development component 'tc/uddi'/'sap.com'/'SAP AG'/'6.4017.00.0000.20050606164207.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'com.sap.pmi.adm'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050818152118.0000'/'1' updates currently deployed development component 'com.sap.pmi.adm'/'sap.com'/'SAP AG'/'6.4017.00.0000.20050818152118.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: No action: Selected development component 'com.sap.jdo'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112029.0000'/'1' will not update currently deployed development component 'com.sap.jdo'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112029.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/SL/CMS/Util'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413101532.0000'/'1' updates currently deployed development component 'tc/SL/CMS/Util'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413101532.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'com.sap.mobile.clientinfo'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050331133205.0000'/'1' updates currently deployed development component 'com.sap.mobile.clientinfo'/'sap.com'/'SAP AG'/'6.4017.00.0000.20050331133205.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/conn/connectorframework'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413100235.0000'/'1' updates currently deployed development component 'tc/conn/connectorframework'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413100235.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/SL/CMS/IDEClient'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413101532.0000'/'1' updates currently deployed development component 'tc/SL/CMS/IDEClient'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413101532.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'com.sap.ip.me.insttool'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050818150135.0000'/'1' updates currently deployed development component 'com.sap.ip.me.insttool'/'sap.com'/'SAP AG'/'6.4017.00.0000.20050818150135.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: No action: Selected development component 'com.sap.aii.ibtransportclient'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'1' will not update currently deployed development component 'com.sap.aii.ibtransportclient'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'com.sap.ip.me.webconsole'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111540.0000'/'1' updates currently deployed development component 'com.sap.ip.me.webconsole'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413101350.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/wd/pdfobject'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060726153907.0000'/'1' updates currently deployed development component 'tc/wd/pdfobject'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060503180106.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'com.sap.lcrabapapi'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050606164103.0000'/'1' updates currently deployed development component 'com.sap.lcrabapapi'/'sap.com'/'SAP AG'/'6.4017.00.0000.20050606164103.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/sec/app'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111002.0000'/'1' updates currently deployed development component 'tc/sec/app'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413100412.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'com.sapportals.htmlb.ear'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050121164722.0000'/'1' updates currently deployed development component 'com.sapportals.htmlb.ear'/'sap.com'/'SAP AG'/'6.4017.00.0000.20050121164722.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/TechSrv/XML_DAS'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060119123705.0000'/'1' updates currently deployed development component 'tc/TechSrv/XML_DAS'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060119123705.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/wd/corecomp'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112627.0000'/'1' updates currently deployed development component 'tc/wd/corecomp'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413102720.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: No action: Selected development component 'com.sap.aii.util.xml'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'1' will not update currently deployed development component 'com.sap.aii.util.xml'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/eCATTPing'/'sap.com'/'SAP AG'/'6.4018.00.0000.20041104140331.0000'/'1' updates currently deployed development component 'tc/eCATTPing'/'sap.com'/'SAP AG'/'6.4017.00.0000.20041104140331.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'com.sap.rprof.dbprofiles'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413101559.0000'/'1' updates currently deployed development component 'com.sap.rprof.dbprofiles'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413101559.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'com.sap.engine.services.webservices.tool'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060814115206.0000'/'1' updates currently deployed development component 'com.sap.engine.services.webservices.tool'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060427163646.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'com.sap.engine.heartbeat'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060814115206.0000'/'1' updates currently deployed development component 'com.sap.engine.heartbeat'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060427163646.0000'/'0'.
    Sep 13, 2006 8:23:40 AM  Info: Ending deployment prerequisites. All items are correct.
    Sep 13, 2006 8:23:41 AM  Info: Saved current Engine state.
    Sep 13, 2006 8:23:41 AM  Info: Starting: Update: Selected development component 'com.sap.lcr.saprfc'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'1' updates currently deployed development component 'com.sap.lcr.saprfc'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413101546.0000'/'0'.
    Sep 13, 2006 8:23:41 AM  Info: SDA to be deployed: E:\usr\sap\SBD\DVEBMGS00\SDM\root\origin\sap.com\com.sap.lcr.saprfc\SAP AG\1\6.4018.00.0000.20060706111625.0000\lcrsaprfc.ear
    Sep 13, 2006 8:23:41 AM  Info: Software type of SDA: J2EE
    Sep 13, 2006 8:23:41 AM  Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
    Sep 13, 2006 8:24:03 AM  Info: Begin of log messages of the target system:
    06/09/13 08:23:57 -  ***********************************************************
    06/09/13 08:23:59 -  References from application sap.com/com.sap.lcr.saprfc to its loaders done.
    06/09/13 08:23:59 -  Start updating EAR file...
    06/09/13 08:23:59 -  start-up mode is lazy
    06/09/13 08:23:59 -  EAR file updated successfully for 94ms.
    06/09/13 08:23:59 -  Start updating...
    06/09/13 08:24:00 -  EAR file uploaded to server for 719ms.
    06/09/13 08:24:03 -  ERROR: Not updated. Deploy Service returned ERROR:
                         java.rmi.RemoteException: Exception in operation update with application sap.com/com.sap.lcr.saprfc..
                         Reason: com/sap/mw/jco/JCO$Function; nested exception is:
                              java.lang.NoClassDefFoundError: com/sap/mw/jco/JCO$Function
                              at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:682)
                              at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1278)
                              at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
                              at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
                              at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
                              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: java.lang.NoClassDefFoundError: com/sap/mw/jco/JCO$Function
                              at java.lang.Class.getDeclaredMethods0(Native Method)
                              at java.lang.Class.privateGetDeclaredMethods(Class.java:1655)
                              at java.lang.Class.privateGetPublicMethods(Class.java:1778)
                              at java.lang.Class.getMethods(Class.java:832)
                              at com.sap.engine.services.ejb.deploy.xml.MethodsExtractor.getWithNotSpecifiedMethodInterface(MethodsExtractor.java:121)
                              at com.sap.engine.services.ejb.deploy.xml.MethodsExtractor.getAllMethodsInBean(MethodsExtractor.java:103)
                              at com.sap.engine.services.ejb.deploy.xml.EJBJarParser.getMethodXml(EJBJarParser.java:1168)
                              at com.sap.engine.services.ejb.deploy.xml.EJBJarParser.processContainerTransaction(EJBJarParser.java:1023)
                              at com.sap.engine.services.ejb.deploy.xml.EJBJarParser.processAssemblyDescriptor(EJBJarParser.java:924)
                              at com.sap.engine.services.ejb.deploy.xml.EJBJarParser.parseXml(EJBJarParser.java:156)
                              at com.sap.engine.services.ejb.deploy.xml.EJBJarParser.parseXml(EJBJarParser.java:97)
                              at com.sap.engine.services.ejb.deploy.DeployAdmin.parseSingleJar(DeployAdmin.java:297)
                              at com.sap.engine.services.ejb.EJBAdmin.buildAppDescriptorBeforeUpdate(EJBAdmin.java:408)
                              at com.sap.engine.services.ejb.EJBAdmin.needUpdate(EJBAdmin.java:341)
                              at com.sap.engine.services.deploy.server.application.UpdateTransaction.getContainersWhichNeedUpdate(UpdateTransaction.java:537)
                              at com.sap.engine.services.deploy.server.application.UpdateTransaction.getConcernedContainers(UpdateTransaction.java:493)
                              at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:263)
                              at com.sap.engine.services.deploy.server.application.UpdateTransaction.begin(UpdateTransaction.java:164)
                              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:3184)
                              at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:670)
                              ... 10 more
                         For detailed information see the log file of the Deploy Service.
    06/09/13 08:24:03 -  ***********************************************************
    Sep 13, 2006 8:24:03 AM  Info: End of log messages of the target system.
    Sep 13, 2006 8:24:03 AM  Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
    Sep 13, 2006 8:24:03 AM  Error: Aborted: development component 'com.sap.lcr.saprfc'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'1', grouped by :
    Caught exception during application deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: Exception in operation update with application sap.com/com.sap.lcr.saprfc..
    Reason: com/sap/mw/jco/JCO$Function; nested exception is:
         java.lang.NoClassDefFoundError: com/sap/mw/jco/JCO$Function
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineJ2EE620OnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Sep 13, 2006 8:24:03 AM  Info: Starting to save the repository
    Sep 13, 2006 8:24:04 AM  Info: Finished saving the repository
    Sep 13, 2006 8:24:04 AM  Info: Starting: Initial deployment: Selected software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.6.40.18.0.20060816080857''/'1' will be deployed.
    Sep 13, 2006 8:24:04 AM  Error: Aborted: software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.6.40.18.0.20060816080857''/'1':
    Failed deployment of SDAs:
    development component 'com.sap.lcr.saprfc'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'1' : aborted
    Please, look at error logs above for more information!
    Sep 13, 2006 8:24:04 AM  Info: Starting to save the repository
    Sep 13, 2006 8:24:04 AM  Info: Finished saving the repository
    Sep 13, 2006 8:24:04 AM  Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
    Sep 13, 2006 8:24:04 AM  Error: -
    At least one of the Deployments failed -
    Sep 13, 2006 8:24:05 AM  Info: Summarizing the deployment results:
    Sep 13, 2006 8:24:05 AM  Error: Aborted: E:\18_0-20000118_directory\J2EE-RUNT-CD\J2EE-ENG\ONLINE\SAPJTECHS18_0.SCA
    Sep 13, 2006 8:24:05 AM  Error: Processing error. Return code: 4
    Regards,

    Hi everybody,
    Well, after of the last post where it commented that the possible solution would be to update Java to version 12, the issue continues.
    Now, we have the following error after SAP recommended to deploy the file manually with SDM Tool, the file is lcrsaprfc.ear and show the following error:
    Manifest attributes are missing or have badly formatted value:
    attribute keylocation is missing
    attribute keyname is missing
    attribute keyvendor is missing
    attribute keycounter is missing
    Maybe can be a problem with the file?, format?, build?.
    Thanks for your help and patience.
    Regards,
    Rafa R.R.

  • Error occurs in patching J2EE engine to SP11

    Hi there,
    I try to update my J2ee engine to sp11. But in the phase 16 of 21,"start J2EE engine", a error was thrown out as below:
    <i>ERROR 2005-08-24 14:37:55
    CJS-20058  J2EE Engine JC00 of SAP system J2E did not reach state "Starting Applications" after 1112 seconds: giving up.</i>
    From then my j2ee engine can't run any more. My configuration is,
    RAM: 2G
    OS : windowsXP SP2
    EP 6.0 SP9
    Any suggestions or help would be appreciated.
    Thanks
    Julian

    Hello Julian,
    Have a look at the log files in <J2EE instance>\work directory. Check dev_* and std_* files. There must be some  error messages in them, which will give you a clue what might have got wrong.
    Kind Regards
    Vyara

  • NWDS: Component deploying error

    Hi,
    i'm trying to deply a component with NWDS. But it raise the error:
    <i>None of the available containers recognized the components of application sap.com/pcui_gp~xsscfg; it is not possible to make deploy.</i>
    Visual Adm, SMD works fine; access to DTR granted.
    configuration:
    NWDS 7.0.11
    sap.com  UMEADMIN  7.00 SP11 (1000.7.00.11.0.20061128062751)  SAP AG  MAIN_APL70SP_C  20061128144405 
    sap.com  BI_MMR  7.00 SP10 (1000.7.00.10.0.20061021201000)  SAP AG  SAP AG  20061128135902 
    sap.com  BI_UDI  7.00 SP10 (1000.7.00.10.0.20061021205400)  SAP AG  SAP AG  20061128140800 
    sap.com  SAP-JEE  7.00 SP10 (1000.7.00.10.0.20061026144500)  SAP AG  SAP AG  20061128135127 
    sap.com  SAP-JEECOR  7.00 SP10 (1000.7.00.10.0.20061026144500)  SAP AG  SAP AG  20061128135123 
    sap.com  BASETABLES  7.00 SP10 (1000.7.00.10.0.20061022040500)  SAP AG  SAP AG  20061128135125 
    sap.com  SAP_JTECHF  7.00 SP10 (1000.7.00.10.0.20061022040800)  SAP AG  SAP AG  20061128135124 
    sap.com  SAP_JTECHS  7.00 SP10 (1000.7.00.10.0.20061022040900)  SAP AG  SAP AG  20061128140701 
    Name:  Java HotSpot(TM) Server VM 
    Vendor:  Sun Microsystems Inc. 
    Version:  1.4.2_12-b03
    full log here:
    16.07.2007 15:29:04 /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] INFO:
    [008]Additional log information about the deployment
    <!LOGHEADER[START]/>
    <!HELP[Manual modification of the header may cause parsing problem!]/>
    <!LOGGINGVERSION[1.5.3.7185 - 630]/>
    <!NAME[C:\usr\sap\F48\JC30\SDM\program\log\sdmcl20070716112902.log]/>
    <!PATTERN[sdmcl20070716112902.log]/>
    <!FORMATTER[com.sap.tc.logging.TraceFormatter(%24d %s: %m)]/>
    <!ENCODING[Cp1251]/>
    <!LOGHEADER[END]/>
    Jul 16, 2007 3:29:02 PM  Info: -
    Starting deployment -
    Jul 16, 2007 3:29:02 PM  Info: Error handling strategy: OnErrorStop
    Jul 16, 2007 3:29:02 PM  Info: Prerequisite error handling strategy: OnPrerequisiteErrorStop
    Jul 16, 2007 3:29:02 PM  Info: Update strategy: UpdateAllVersions
    Jul 16, 2007 3:29:02 PM  Info: Starting deployment prerequisites:
    Jul 16, 2007 3:29:02 PM  Info: Loading selected archives...
    Jul 16, 2007 3:29:02 PM  Info: Loading archive 'C:\usr\sap\F48\JC30\SDM\program\temp\temp65389sap.compcui_gpxsscfg.sda'
    Jul 16, 2007 3:29:02 PM  Info: Selected archives successfully loaded.
    Jul 16, 2007 3:29:02 PM  Info: Actions per selected component:
    Jul 16, 2007 3:29:02 PM  Info: Initial deployment: Selected development component 'pcui_gp/xsscfg'/'sap.com'/'MAIN_ERP53SP_D'/'1166839'/'0' will be deployed.
    Jul 16, 2007 3:29:02 PM  Info: Ending deployment prerequisites. All items are correct.
    Jul 16, 2007 3:29:02 PM  Info: Saved current Engine state.
    Jul 16, 2007 3:29:02 PM  Info: Starting: Initial deployment: Selected development component 'pcui_gp/xsscfg'/'sap.com'/'MAIN_ERP53SP_D'/'1166839'/'0' will be deployed.
    Jul 16, 2007 3:29:02 PM  Info: SDA to be deployed: C:\usr\sap\F48\JC30\SDM\root\origin\sap.com\pcui_gp\xsscfg\MAIN_ERP53SP_D\0\1166839\temp65389sap.compcui_gpxsscfg.sda
    Jul 16, 2007 3:29:02 PM  Info: Software type of SDA: J2EE
    Jul 16, 2007 3:29:02 PM  Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
    Jul 16, 2007 3:29:04 PM  Info: Begin of log messages of the target system:
    07/07/16 15:29:02 -  ***********************************************************
    07/07/16 15:29:02 -  Start updating EAR file...
    07/07/16 15:29:02 -  start-up mode is lazy
    07/07/16 15:29:03 -  EAR file updated successfully for 120ms.
    07/07/16 15:29:03 -  Start deploying ...
    07/07/16 15:29:03 -  EAR file uploaded to server for 541ms.
    07/07/16 15:29:04 -  ERROR: Not deployed. Deploy Service returned ERROR:
                         java.rmi.RemoteException: Error occurred while deploying ear file ./temp/deploy/work/deploying/pcui_gp_xsscfg.ear.
                         Reason: None of the available containers recognized the components of application sap.com/pcui_gp~xsscfg; it is not possible to make deploy.
                              at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:570)
                              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:320)
                              at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
                              at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
                              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)
                         For detailed information see the log file of the Deploy Service.
    07/07/16 15:29:04 -  ***********************************************************
    Jul 16, 2007 3:29:04 PM  Info: End of log messages of the target system.
    Jul 16, 2007 3:29:04 PM  Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
    Jul 16, 2007 3:29:04 PM  Error: Aborted: development component 'pcui_gp/xsscfg'/'sap.com'/'MAIN_ERP53SP_D'/'1166839'/'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_xsscfg.ear.
    Reason: None of the available containers recognized the components of application sap.com/pcui_gp~xsscfg; it is not possible to make deploy.
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Jul 16, 2007 3:29:04 PM  Info: Starting to save the repository
    Jul 16, 2007 3:29:04 PM  Info: Finished saving the repository
    Jul 16, 2007 3:29:04 PM  Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
    Jul 16, 2007 3:29:04 PM  Error: -
    At least one of the Deployments failed -
    any advices?
    Best regards,
    Dima

    Hello Ken,
    I’m tried to deploy this application as a prerequisite of ESS development, but with other DC the same problem. Anyway I'm a newbie in all these tools using, so I just don't know where and how I should check - is "GP installed" or not... and what means "None of the available containers", what they are?
    Cheers,
    Dima

  • Java.lang.NullPointerException when connect to the J2EE engine

    I want to connect to the J2EE engine ,but the error message "java.lang.NullPointerException" is displayed in the console.  Please help me ! Thank you !!  The full error exception like this:
    java.lang.NullPointerException
            at com.sap.engine.services.adminadapter.gui.tasks.LoginTask.connectActio
    n(LoginTask.java:191)
            at com.sap.engine.services.adminadapter.gui.tasks.LoginTask.run(LoginTas
    k.java:79)
            at java.lang.Thread.run(Thread.java:534)

    Hi:
    The whole errror message like this:(deploy aborted error message)
    2009/4/27 上午 08:53:52 /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
    [001]Deployment aborted
    Settings
    SDM host : 10.138.6.10
    SDM port : 50118
    URL to deploy : file:/C:/DOCUME1/F3221789/LOCALS1/Temp/temp53268foxconn.com~bbs_demo.ear
    Result
    => deployment aborted : file:/C:/DOCUME1/F3221789/LOCALS1/Temp/temp53268foxconn.com~bbs_demo.ear
    Aborted: development component 'bbs_demo'/'foxconn.com'/'LOKAL'/'0.2009.04.27.08.53.22':
    Cannot login to the SAP J2EE Engine using user and password as provided in the Filesystem Secure Store. Enter valid login information in the Filesystem Secure Store using the SAP J2EE Engine Config Tool. For more information, see SAP note 701654.
    com.sap.sdm.serverext.servertype.inqmy.extern.DeployManagerAuthExceptionWrapper: Wrong security credentials detected while trying to obtain connection to the J2EE Engine.
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.checkLoginCredentials.DMAUTHEXC)
    Deployment exception : The deployment of at least one item aborted
    The Log infomation is like this:
    2009/4/27 上午 08:53:52 /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] INFO:
    [001]Additional log information about the deployment
    <!LOGHEADER[START]/>
    <!HELP[Manual modification of the header may cause parsing problem!]/>
    <!LOGGINGVERSION[1.5.3.7185 - 630]/>
    <!NAME[D:\usr\sap\SCM\DVEBMGS01\SDM\program\log\sdmcl20090427005331.log]/>
    <!PATTERN[sdmcl20090427005331.log]/>
    <!FORMATTER[com.sap.tc.logging.TraceFormatter(%24d %s: %m)]/>
    <!ENCODING[MS950]/>
    <!LOGHEADER[END]/>
    Apr 27, 2009 8:53:32 AM  Info: -
    Starting deployment -
    Apr 27, 2009 8:53:32 AM  Info: Error handling strategy: OnErrorStop
    Apr 27, 2009 8:53:32 AM  Info: Prerequisite error handling strategy: OnPrerequisiteErrorStop
    Apr 27, 2009 8:53:32 AM  Info: Update strategy: UpdateAllVersions
    Apr 27, 2009 8:53:32 AM  Info: Starting deployment prerequisites:
    Apr 27, 2009 8:53:36 AM  Info: Loading selected archives...
    Apr 27, 2009 8:53:36 AM  Info: Loading archive 'D:\usr\sap\SCM\DVEBMGS01\SDM\program\temp\temp53268foxconn.com~bbs_demo.ear'
    Apr 27, 2009 8:53:37 AM  Info: Selected archives successfully loaded.
    Apr 27, 2009 8:53:37 AM  Info: Actions per selected component:
    Apr 27, 2009 8:53:37 AM  Info: Update: Selected development component 'bbs_demo'/'foxconn.com'/'LOKAL'/'0.2009.04.27.08.53.22' updates currently deployed development component 'bbs_demo'/'foxconn.com'/'LOKAL'/'0.2009.04.23.14.34.21'.
    Apr 27, 2009 8:53:37 AM  Info: Ending deployment prerequisites. All items are correct.
    Apr 27, 2009 8:53:39 AM  Error: Unable to compare host[sidcsms.foxconn.com] and host[GDS-SF-F21789] Throwable: java.net.UnknownHostException Throwable message: GDS-SF-F21789: GDS-SF-F21789
    Apr 27, 2009 8:53:39 AM  Info: Saved current Engine state.
    Apr 27, 2009 8:53:39 AM  Info: Starting: Update: Selected development component 'bbs_demo'/'foxconn.com'/'LOKAL'/'0.2009.04.27.08.53.22' updates currently deployed development component 'bbs_demo'/'foxconn.com'/'LOKAL'/'0.2009.04.23.14.34.21'.
    Apr 27, 2009 8:53:39 AM  Info: SDA to be deployed: D:\usr\sap\SCM\DVEBMGS01\SDM\root\origin\foxconn.com\bbs_demo\LOKAL\0.2009.04.27.08.53.22\temp53268foxconn.com~bbs_demo.ear
    Apr 27, 2009 8:53:39 AM  Info: Software type of SDA: J2EE
    Apr 27, 2009 8:53:40 AM  Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
    Apr 27, 2009 8:53:43 AM  Error: Unable to compare host[sidcsms.foxconn.com] and host[GDS-SF-F21789] Throwable: java.net.UnknownHostException Throwable message: GDS-SF-F21789: GDS-SF-F21789
    Apr 27, 2009 8:53:44 AM  Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
    Apr 27, 2009 8:53:44 AM  Error: Aborted: development component 'bbs_demo'/'foxconn.com'/'LOKAL'/'0.2009.04.27.08.53.22':
    Cannot login to the SAP J2EE Engine using user and password as provided in the Filesystem Secure Store. Enter valid login information in the Filesystem Secure Store using the SAP J2EE Engine Config Tool. For more information, see SAP note 701654.
    com.sap.sdm.serverext.servertype.inqmy.extern.DeployManagerAuthExceptionWrapper: Wrong security credentials detected while trying to obtain connection to the J2EE Engine.
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.checkLoginCredentials.DMAUTHEXC)
    Apr 27, 2009 8:53:44 AM  Info: Starting to save the repository
    Apr 27, 2009 8:53:44 AM  Info: Finished saving the repository
    Apr 27, 2009 8:53:44 AM  Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
    Apr 27, 2009 8:53:44 AM  Error: -
    At least one of the Deployments failed -
    Edited by: sap-abap-tw on Apr 27, 2009 3:01 AM

  • Deploy Error for Web Dynpro

    I have got the error message on Deploying the project of web dynpro, they are:
    Deployment aborted
    2006&#24180;7&#26376;6&#26085; &#19978;&#21320;10:21:13 /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
    [002]Deployment aborted
    Settings
    SDM host : fly-2012
    SDM port : 50018
    URL to deploy : file:/C:/DOCUME1/Family/LOCALS1/Temp/temp25891TutWD_FlightList_Init.ear
    Result
    => deployment aborted : file:/C:/DOCUME1/Family/LOCALS1/Temp/temp25891TutWD_FlightList_Init.ear
    Aborted: development component 'TutWD_FlightList_Init'/'local'/'LOKAL'/'0.2006.07.06.10.17.59':
    Caught exception during application deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: Only Administrators have the right to perform this operation.
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Deployment exception : The deployment of at least one item aborted
    Additional log information about the deployment
    2006&#24180;7&#26376;6&#26085; &#19978;&#21320;10:21:13 /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] INFO:
    [002]Additional log information about the deployment
    <!LOGHEADER[START]/>
    <!HELP[Manual modification of the header may cause parsing problem!]/>
    <!LOGGINGVERSION[1.5.3.7186 - 630]/>
    <!NAME[C:\usr\sap\J2E\JC00\SDM\program\log\sdmcl20060706022108.log]/>
    <!PATTERN[sdmcl20060706022108.log]/>
    <!FORMATTER[com.sap.tc.logging.TraceFormatter(%24d %s: %m)]/>
    <!ENCODING[MS950]/>
    <!LOGHEADER[END]/>
    Jul 6, 2006 10:21:08 AM  Info: -
    Starting deployment -
    Jul 6, 2006 10:21:08 AM  Info: Error handling strategy: OnErrorStop
    Jul 6, 2006 10:21:08 AM  Info: Prerequisite error handling strategy: OnPrerequisiteErrorStop
    Jul 6, 2006 10:21:08 AM  Info: Update strategy: UpdateAllVersions
    Jul 6, 2006 10:21:08 AM  Info: Starting deployment prerequisites:
    Jul 6, 2006 10:21:08 AM  Info: Loading selected archives...
    Jul 6, 2006 10:21:08 AM  Info: Loading archive 'C:\usr\sap\J2E\JC00\SDM\program\temp\temp25891TutWD_FlightList_Init.ear'
    Jul 6, 2006 10:21:09 AM  Info: Selected archives successfully loaded.
    Jul 6, 2006 10:21:09 AM  Info: Actions per selected component:
    Jul 6, 2006 10:21:09 AM  Info: Initial deployment: Selected development component 'TutWD_FlightList_Init'/'local'/'LOKAL'/'0.2006.07.06.10.17.59' will be deployed.
    Jul 6, 2006 10:21:10 AM  Info: Ending deployment prerequisites. All items are correct.
    Jul 6, 2006 10:21:10 AM  Info: Saved current Engine state.
    Jul 6, 2006 10:21:10 AM  Info: Starting: Initial deployment: Selected development component 'TutWD_FlightList_Init'/'local'/'LOKAL'/'0.2006.07.06.10.17.59' will be deployed.
    Jul 6, 2006 10:21:10 AM  Info: SDA to be deployed: C:\usr\sap\J2E\JC00\SDM\root\origin\local\TutWD_FlightList_Init\LOKAL\0.2006.07.06.10.17.59\temp25891TutWD_FlightList_Init.ear
    Jul 6, 2006 10:21:10 AM  Info: Software type of SDA: J2EE
    Jul 6, 2006 10:21:10 AM  Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
    Jul 6, 2006 10:21:12 AM  Info: Begin of log messages of the target system:
    06/07/06 10:21:10 -  ***********************************************************
    06/07/06 10:21:11 -  Start updating EAR file...
    06/07/06 10:21:11 -  start-up mode is lazy
    06/07/06 10:21:11 -  EAR file updated successfully for 811ms.
    06/07/06 10:21:11 -  Start deploying ...
    06/07/06 10:21:12 -  EAR file uploaded to server for 120ms.
    06/07/06 10:21:12 -  ERROR: Not deployed. Deploy Service returned ERROR:
                         java.rmi.RemoteException: Only Administrators have the right to perform this operation.
                              at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:526)
                              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)
                         For detailed information see the log file of the Deploy Service.
    06/07/06 10:21:12 -  ***********************************************************
    Jul 6, 2006 10:21:12 AM  Info: End of log messages of the target system.
    Jul 6, 2006 10:21:12 AM  Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
    Jul 6, 2006 10:21:12 AM  Error: Aborted: development component 'TutWD_FlightList_Init'/'local'/'LOKAL'/'0.2006.07.06.10.17.59':
    Caught exception during application deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: Only Administrators have the right to perform this operation.
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Jul 6, 2006 10:21:13 AM  Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
    Jul 6, 2006 10:21:13 AM  Error: -
    At least one of the Deployments failed -

    The tools I using to Deploy is
    SAP NetWeaver Developer Studio. and I'm follow the tutorial from it, I have enter the sdm password and operate the delopyment, but when it create the ear file, then the error have occur and catch the error about:
    Caught exception during application deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: Only Administrators have the right to perform this operation.
    I have try to login as j2eadm to operate the deployment, but the error message is same.
    as you say, the user "SDM" or "J2EE_ADMIN" user account I haven't find in my windows XP.
    and one more question, does the project need to deploy success then the web page "Web Dynpro Content Administrator" could find the project?
    lastly, I have try to login to SDM by using the SAP given program C:\usr\sap\J2E\JC00\SDM\program\RemoteGui for testing, It was success. and does the default SDM account could change the permission by different password?

  • SDM deployment error during XI 3.0 installation

    (nobody in the PI forum replied, so I'm reposting here)
    I need to install a sandbox using this old version. Installation base is 6.40 WebAS plus Java addon SR1. System installs fine, however during final SDM deployment I get a problem during the J2EE engine restart:
    errors:
    service sld ================= ERROR =================
    Cannot start service com.sap.aii.af.cpa.svc; it has hard reference to service sld which is not started.
    and around 20 more services which have a dependency on sld
    sld does not start because:
    /Applications/SLD#sap.com/com.sap.lcr#com.sap.lcr.sagent.BuilderDirector#J2EE_
    GUEST#328####e4cd3451819411dec19c001d72bd0666#SAPEngine_Application_Threadimpl:3_0##0#0#Error#1#com.sap.lcr.sagent.BuilderDirector#Plain###Can't access http store#
    OR:
    SAPEngine_System_Threadimpl:5_32##0#0#Error#1#com.sap.engine.core.service630.container.ServiceRunner#Plain###Service sld error. Nested exception is: com.sap.engine.frame.ServiceException: <--Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='sld_3012', A
    rguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key sld_3012
    at com.sap.sldserv.SldServerFrame.start(SldServerFrame.java:109)
    at com.sap.sldserv.SldServerFrame.start(SldServerFrame.java:78) ...........
    further suspicious warnings:
    Aug 5, 2009 12:51:17 AM Info: No action: Selected development component 'com.sap.aii.af.ms.svc'/'sap.com'/'SAP AG'/'3.0.0920041027171222.0000' will not be deployed because containing software component 'SAP-XIAFC'/'sap.com'/'SAP AG'/'1000.3.0.9.1.20041028052722' will not be deployed.
    and this for around 20 more components from comp.sap.aii*
    What went wrong, and, what can I do to fix this? Redeploy sld ? I could not find how.
    Java version is latest 1.4.2 x86_64 from IBM (1.4.2_13) for my architecture (x86_64 Linux RHEL5), DB is maxdb 7.6
    Any help is appreciated, Thanks.
    Sanjay

    Can you please check thet if you have given a central SLD then that SLD is up and running as you are getting the message.
    Cannot start service com.sap.aii.af.cpa.svc; it has hard reference to service sld which is not started.
    Please check this note it will solve your issue.
    Note 994433 - XI AF on J2EE Engine terminates with OutOfMemoryError
    you can manually start th services.
    Thanks Rishi Abrol

  • Deployment Error when transporting to TEST server

    Hi experts,
    I'm having a deployment error when transporting my dc from development server to test server using the Change Management Service - Transport Studio.
    In the error message, there is the mention of the following sentence:
    =============================================
    Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine ?
    =============================================
    But the dc is using only the standard default dcs like:
    com.sap.aii.proxy.framework (default)
    com.sap.aii.util.misc (default)
    com.sap.exception (default)
    com.sap.mw.jco (default)
    tc/cmi (default)
    tc/ddic/ddicruntime (default)
    td/ddic/metamodel/content (default)
    tc/logging (default)
    tc/wd/webdynpro (default)
    tc/wdp/metamodel/content (default)
    So could these dcs not have been deployed on the test server ?
    How do we confirm this ?
    Thanks in advance.
    Rgds,
    Daniel

    A dump of the exception i m getting.
    Anyone has a clue or advice of how to overcome this problem ?
    20081107165952 Info   :Nov 7, 2008 4:46:03 PM   Info: Starting: Update: Selected development component 'appl/main'/'com.diagonal'/'dev_devcias_C'/'823'/'0' updates currently deployed development component 'appl/main'/'com.diagonal'/'LOKAL'/'0.2006.01.12.14.18.23'/'0'.
    20081107165952 Info   :Nov 7, 2008 4:46:03 PM   Info: SDA to be deployed: /usr/sap/WS5/JC00/SDM/root/origin/com.diagonal/appl/main/dev_devcias_C/0/823/appl~main.sda
    20081107165952 Info   :Nov 7, 2008 4:46:03 PM   Info: Software type of SDA: J2EE
    20081107165952 Info   :Nov 7, 2008 4:46:03 PM   Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
    20081107165952 Info   :Nov 7, 2008 4:46:07 PM   Info: Begin of log messages of the target system:
    20081107165952 Info   :08/11/07 16:46:03 -  ***********************************************************
    20081107165952 Info   :08/11/07 16:46:04 -  Start updating EAR file...
    20081107165952 Info   :08/11/07 16:46:04 -  start-up mode is lazy
    20081107165952 Info   :08/11/07 16:46:04 -  EAR file updated successfully for 70ms.
    20081107165952 Info   :08/11/07 16:46:04 -  Start updating...
    20081107165952 Info   :08/11/07 16:46:06 -  EAR file uploaded to server for 861ms.
    20081107165952 Info   :08/11/07 16:46:07 -  ERROR: Not updated. Deploy Service returned ERROR:
    20081107165952 Info   :                     java.rmi.RemoteException: Cannot deploy application com.diagonal/appl~main..
    20081107165952 Info   :                     Reason: Clusterwide exception: Failed to deploy application com.diagonal/appl~main. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?; nested exception is:
    20081107165952 Info   :                          com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to deploy application com.diagonal/appl~main. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?
    20081107165952 Info   :                          at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:681)
    20081107165952 Info   :                          at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1278)
    20081107165952 Info   :                          at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:313)
    20081107165952 Info   :                          at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:199)
    20081107165952 Info   :                          at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136)
    20081107165952 Info   :                          at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
    20081107165952 Info   :                          at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
    20081107165952 Info   :                          at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    20081107165952 Info   :                          at java.security.AccessController.doPrivileged(AccessController.java:215)
    20081107165952 Info   :                          at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
    20081107165952 Info   :                          at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    20081107165952 Info   :                     Caused by: com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to deploy application com.diagonal/appl~main. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?
    20081107165952 Info   :                          at com.sap.engine.services.webdynpro.WebDynproContainer.deploy(WebDynproContainer.java:1050)
    20081107165952 Info   :                          at com.sap.engine.services.webdynpro.WebDynproContainer.makeUpdate(WebDynproContainer.java:1281)
    20081107165952 Info   :                          at com.sap.engine.services.deploy.server.application.UpdateTransaction.makeComponents(UpdateTransaction.java:400)
    20081107165952 Info   :                          at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:321)
    20081107165952 Info   :                          at com.sap.engine.services.deploy.server.application.UpdateTransaction.begin(UpdateTransaction.java:164)
    20081107165952 Info   :                          at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292)
    20081107165952 Info   :                          at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:326)
    20081107165952 Info   :                          at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3184)
    20081107165952 Info   :                          at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:669)
    20081107165952 Info   :                          ... 10 more
    20081107165952 Info   :                     For detailed information see the log file of the Deploy Service.
    20081107165952 Info   :08/11/07 16:46:07 -  ***********************************************************
    20081107165952 Info   :Nov 7, 2008 4:46:07 PM   Info: End of log messages of the target system.
    20081107165952 Info   :Nov 7, 2008 4:46:07 PM   Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
    20081107165952 Info   :Nov 7, 2008 4:46:07 PM   Error: Aborted: development component 'appl/main'/'com.diagonal'/'dev_devcias_C'/'823'/'0', grouped by :
    20081107165952 Info   :Caught exception during application deployment from SAP J2EE Engine's deploy service:
    20081107165952 Info   :java.rmi.RemoteException: Cannot deploy application com.diagonal/appl~main..
    20081107165952 Info   :Reason: Clusterwide exception: Failed to deploy application com.diagonal/appl~main. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?; nested exception is:
    20081107165952 Info   :     com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to deploy application com.diagonal/appl~main. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?
    20081107165952 Info   : (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    20081107165952 Info   :Nov 7, 2008 4:46:07 PM   Info: Starting to save the repository
    20081107165952 Info   :Nov 7, 2008 4:46:07 PM   Info: Finished saving the repository
    20081107165952 Info   :Nov 7, 2008 4:46:07 PM   Info: Starting: Update: Selected software component 'CIAS_WD_APPLICATIONS'/'diagonal.com'/'dev_devcias_C'/'1000.1.0.6.0.20081107075633''/'0' updates currently deployed software component 'CIAS_WD_APPLICATIONS'/'diagonal.com'/'dev_devcias_C'/'1000.1.0.0.0.20061122075934''/'1'.
    20081107165952 Info   :Nov 7, 2008 4:46:07 PM   Error: Aborted: software component 'CIAS_WD_APPLICATIONS'/'diagonal.com'/'dev_devcias_C'/'1000.1.0.6.0.20081107075633''/'0':
    20081107165952 Info   :Failed deployment of SDAs:
    20081107165952 Info   :development component 'appl/main'/'com.diagonal'/'dev_devcias_C'/'823'/'0' : aborted
    20081107165952 Info   :Please, look at error logs above for more information!
    20081107165952 Info   :Nov 7, 2008 4:46:07 PM   Info: Starting to save the repository
    20081107165952 Info   :Nov 7, 2008 4:46:08 PM   Info: Finished saving the repository
    20081107165952 Info   :Nov 7, 2008 4:46:08 PM   Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
    20081107165952 Info   :Nov 7, 2008 4:46:08 PM   Error: -
    At least one of the Deployments failed -
    20081107165952 Info   :end of log
    20081107165952 Info   :RC of deployment: 12
    20081107165952 Info   :Step SDM-deploy ended with result 'fatal error' ,stopping execution at 2008-11-07 16:59:52.0155 +9:00

  • Deployment Error / WAS 6.40 on Linux / Netweaver Dev. Studio

    Hi,
    I use WAS 6.40 on linux and I want to deploy a littel Web-Application, developed on Netweaver Developer Studio (Windows XP)
    The SAP-Instances are up and I can reach the Java-Application Server through The Web-Browser (The demo Applications and the Mangamenet console)
    While the deploying process (ear file, Context Menu Developer STudio), i get an Error Message. Maybe someone can help me........
    thx vm for Help, George
    <u>The log-output:</u>
    May 21, 2005 7:34:47 PM  Info: -
    Starting deployment -
    May 21, 2005 7:34:47 PM  Info: Loading selected archives...
    May 21, 2005 7:34:47 PM  Info: Loading archive '/usr/sap/SI4/DVEBMGS00/SDM/program/temp/temp51019eeeee.ear'
    May 21, 2005 7:34:54 PM  Info: Selected archives successfully loaded.
    May 21, 2005 7:34:55 PM  Info: Actions per selected component:
    May 21, 2005 7:34:55 PM  Info: Initial deployment: Selected development component 'eeeee'/'sap.com'/'localhost'/'2005.05.17.21.55.34' will be deployed.
    May 21, 2005 7:34:56 PM  Info: Saved current Engine state.
    May 21, 2005 7:34:56 PM  Info: Error handling strategy: OnErrorStop
    May 21, 2005 7:34:56 PM  Info: Update strategy: UpdateAllVersions
    May 21, 2005 7:34:56 PM  Info: Starting: Initial deployment: Selected development component 'eeeee'/'sap.com'/'localhost'/'2005.05.17.21.55.34' will be deployed.
    May 21, 2005 7:34:56 PM  Info: SDA to be deployed: /usr/sap/SI4/DVEBMGS00/SDM/root/origin/sap.com/eeeee/localhost/2005.05.17.21.55.34/temp51019eeeee.ear
    May 21, 2005 7:34:56 PM  Info: Software type of SDA: J2EE
    May 21, 2005 7:34:57 PM  Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
    May 21, 2005 7:35:00 PM  Info: Starting cluster instance processes.
    May 21, 2005 7:35:00 PM  <b>Error: An error occured while starting a cluster instance!
    May 21, 2005 7:35:00 PM  Error: JStartup Framework is not able to deliver an information about the cluster control instances!
    Please check the status of the J2EE Engine
    May 21, 2005 7:35:00 PM  Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
    May 21, 2005 7:35:00 PM  Error: Aborted: development component 'eeeee'/'sap.com'/'localhost'/'2005.05.17.21.55.34':
    SDM could not start the J2EE cluster on the host si4host! The online deployment is terminated.
    JStartup Framework is not able to deliver an information about the cluster control instances!
    Please check the status of the J2EE Engine
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineAp</b>plOnlineDeployerImpl.performAction(DeploymentActionTypes).STARTUP_CLUSTER)
    May 21, 2005 7:35:00 PM  Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
    May 21, 2005 7:35:00 PM  Error: -
    At least one of the Deployments failed -

    Hi,
    I had exactely the same problem and found the solution here:
    http://listserv.sap.com/pipermail/linux.general/2005-May/004673.html
    After I changed the entry in /etc/hosts, everything went smooth.
    Regards,
    Andreas

Maybe you are looking for