Cannot Find j2ee engine--RSPLAN

I have installed EP in my system.
But when i login to the system with Tcode RSPLAN and click on Start Modeller
I am getting the message "CAnnot find J2ee Engine"
Pls help

Hi Balaji,
Check this thead,
/message/2812976#2812976 [original link is broken]
regards
Juan
please reward with points if helpful

Similar Messages

  • NW developer studio cannot find J2EE Engine

    Hi,
    In Netweaver developer studion I cannot find Windows --> Preferences --> J2EE Engine. It is not in the list.
    I have installed composite environment for portal development. Please advise. Thanks.
    Regards,
    FS

    Pls. check the file
    plugin.xml   in
    "C:\<NWDS Install Directory>\eclipse\plugins\com.sap.ide.eclipse.j2ee.engine_<Version>\"
    for entry like ,
       <extension
             point="org.eclipse.ui.preferencePages">
          <page
                name="SAP J2EE Engine"
                class="com.sap.ide.eclipse.j2ee.engine.ui.local.EnginePreferencePage"
                id="com.sap.engine.eclipse.PreferencePage">
          </page>
       </extension>
    & if this plugin ( "com.sap.ide.eclipse.j2ee.engine_<Version>" ) is there at all in your NWDS ( "C:\<NWDS Install Directory>\eclipse\plugins\" )  , if not you can copy this folder from another sys.
    Also , let me know if you see any folder like   "com.sap.ide.eclipse.j2ee.engine" in your workspace  "C:\<Workspace>\.metadata\.plugins" & you have sufficient read - write permission on the file system.
    Also, check the latest .log files in workspace "C:\<Workspace>\.metadata\"  for any error.
    Which version of JDK and NWDS are you in ? , try reinstalling it.
    Hope this helps.
    Thanks ,
    Uppal

  • Cannot find J2EE egine

    I have already j2ee engine running in the system
    But when i execute the transaction rzplan and click on start wizard it is giving the message   Cannot find J2EE engine
    Pls help me

    If somebody didn't realize, Balaji who faced this problem was in 2006 august. Not sure, if his issue is not yet resolved, its been more than 2 years!
    Anyways, I checked the above link for another thread for similar error.. that's also unanswered.
    For the integrated planning, the following JCo destinations must be created in the Web Dynpro Content administrator of the J2EE engine
    BI_MODELDATA
    BI_METADATA
    WD_ALV_MODELDATA_DEST
    WD_ALV_METADATA_DEST
    and Note 901022 deals with "J2EE engine not found".
    Hope this helps for someone who faces this problem in future.
    cheers,
    Debasis.

  • UME error - cannot start j2ee engine

    I have configured UME to work with Active Directory and it works fine. I have changed the Active Directory service user password, now the j2ee engine is not starting anymore. I cannot revert back to the default UME repository ( I am stuck with AD not working)
    how can I resolve this?
    Tiberiu
    this is the error I get:
    Caused by: com.sap.security.core.persistence.datasource.PersistenceException: Initialisation of connection pool failed for UACC
         poolname [AD server name here]     java.naming.provider.url= ldap://[AD server name here]
         java.naming.factory.initial= com.sun.jndi.ldap.LdapCtxFactory
         java.naming.ldap.version= 3
         com.sun.jndi.ldap.connect.timeout= 25000
         connection_pool_name= [AD server name here]     java.naming.security.principal= [AD user account name here]
         java.naming.security.authentication= simple
         java.naming.security.credentials= ******
         [EXCEPTION: No connection to the ldap server]
    Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.#

    Hi Sasu,
    Check the steps in the below link.check the authorization for JSF user
    http://help.sap.com/saphelp_nw04/helpdata/en/20/361941edd5ef23e10000000a155106/frameset.htm
    Koti Reddy

  • Cannot start j2ee engine after installation

    Hi All,
    After installation of WAS 6.30 (Netweaver 04) on IBM AIX 64 bit (with db2) my server is running but very slow.
    When the server is stopped and started the first time after the installation the dispatcher is running just fine but the server is not loading all applications. The server is timing out during load but with telnet it’s possible to load the applications manually.
    I tried to change the memory settings as described in some of the SAP notes but still no luck.
    The server is now failing with the following message in the dev_server0 log file (work directory) and the server is never writing to the output log file.
    ERROR => JHVM_LoadJavaVM: Cannot create Java VM (rc=-6) [jhvmxx_mt.c  466]
    ERROR => Cannot load Java VM (<default>) (rc=-1) [jlnchxxi_mt. 557]
    JLaunchCloseProgram: good bye (exitcode=-1)
    Changing the memory settings back again doesn’t change anything. The server is not starting!
    The server has 2Gb of memory, enough disk space and is running the correct JDK version.
    Any ideas?
    Thanks in advance!
    Regards
    Michael

    Hi,
    Thanks for the answers.... but the settings are already tried without success.
    Finally SAP came up with a solution that worked.... deleting the file instance.properties.vmprop solved my problems with starting the j2ee engine.
    Regards
    Michael

  • Cannot start j2ee engine

    Hi ALL.
    The server is now failing  sadanly with the following message in the dev_server0 log file (work directory)
    JStartupIReadSection: read node properties [ID18437450]
    -> node name          : server0
    -> node type          : server
    -> node execute       : yes
    -> jlaunch parameters :
    -> java path          : D:\j2sdk1.4.2_13
    -> 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 -Djco.jarm=1 -XX:MaxPermSize=256M -XX:PermSize=256M -XX:NewSize=171M -XX:MaxNewSize=171M -XX:DisableExplicitGC -verbose:gc -Xloggc:GC.log -XX:PrintGCDetails -XX:+PrintGCTimeStamps -Djava.awt.headless=true -Dsun.io.useCanonCaches=false -XX:SoftRefLRUPolicyMSPerMB=1 -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer -Djava.io.tmpdir=d:\EP_TEMP -Dcm.tmpdir=d:\EP_TEMP -Djco.trace_level=10 -Djco.trace_path=d:\trace -Djavax.security.auth.useSubjectCredsOnly=false -Djava.security.krb5.conf=D:\usr\sap\POT\SYS\global\kerberos\ID184374\krb5.conf -Dsun.security.krb5.debug=true -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine. services.ts.jts.ots.PortableInterceptor.JTSInitializer
    -> java vm version    : 1.4.2_13-b06
    -> java vm vendor     : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
    -> java vm type       : server
    -> java vm cpu        : x86
    -> heap size          : 1024M
    -> init heap size     : 1024M
    -> root path          : D:\usr\sap\POT\JC01\j2ee\cluster\server0
    -> class path         : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
    -> OS libs path       : D:\usr\sap\POT\JC01\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     : D:\usr\sap\POT\JC01\exe\jstartup.jar;D:\usr\sap\POT\JC01\exe\jvmx.jar
    -> shutdown class     : com.sap.engine.boot.Start
    -> parameters         :
    -> debuggable         : no
    -> debug mode         : no
    -> debug port         : 50121
    -> shutdown timeout   : 120000
    [Thr 2928] JLaunchISetDebugMode: set debug mode [no]
    [Thr 2968] JLaunchIStartFunc: Thread 2968 started as Java VM thread.
    [Thr 2968] *** WARNING => Using non-standard VM option 'services.ts.jts.ots.PortableInterceptor.JTSInitializer' [jhvmxx.c     1007]
    JHVM_LoadJavaVM: VM Arguments of node [server0]
    -> stack   : 262144 Bytes
    -> arg[  0]: exit
    -> arg[  1]: abort
    -> arg[  2]: vfprintf
    -> arg[  3]: -Djava.security.policy=./java.policy
    -> arg[  4]: -Djava.security.egd=file:/dev/urandom
    -> arg[  5]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
    -> arg[  6]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
    -> arg[  7]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
    -> arg[  8]: -Djco.jarm=1
    -> arg[  9]: -XX:MaxPermSize=256M
    -> arg[ 10]: -XX:PermSize=256M
    -> arg[ 11]: -XX:NewSize=171M
    -> arg[ 12]: -XX:MaxNewSize=171M
    -> arg[ 13]: -XX:+DisableExplicitGC
    -> arg[ 14]: -verbose:gc
    -> arg[ 15]: -Xloggc:GC.log
    -> arg[ 16]: -XX:+PrintGCDetails
    -> arg[ 17]: -XX:+PrintGCTimeStamps
    -> arg[ 18]: -Djava.awt.headless=true
    -> arg[ 19]: -Dsun.io.useCanonCaches=false
    -> arg[ 20]: -XX:SoftRefLRUPolicyMSPerMB=1
    -> arg[ 21]: -XX:SurvivorRatio=2
    -> arg[ 22]: -XX:TargetSurvivorRatio=90
    -> arg[ 23]: -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer
    -> arg[ 24]: -Djava.io.tmpdir=d:\EP_TEMP
    -> arg[ 25]: -Dcm.tmpdir=d:\EP_TEMP
    -> arg[ 26]: -Djco.trace_level=10
    -> arg[ 27]: -Djco.trace_path=d:\trace
    -> arg[ 28]: -Djavax.security.auth.useSubjectCredsOnly=false
    -> arg[ 29]: -Djava.security.krb5.conf=D:\usr\sap\POT\SYS\global\kerberos\ID184374\krb5.conf
    -> arg[ 30]: -Dsun.security.krb5.debug=true
    -> arg[ 31]: -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.
    -> arg[ 32]: services.ts.jts.ots.PortableInterceptor.JTSInitializer
    -> arg[ 33]: -Dsys.global.dir=D:\usr\sap\POT\SYS\global
    -> arg[ 34]: -Dapplication.home=D:\usr\sap\POT\JC01\exe
    -> arg[ 35]: -Djava.class.path=D:\usr\sap\POT\JC01\exe\jstartup.jar;D:\usr\sap\POT\JC01\exe\jvmx.jar;.\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
    -> arg[ 36]: -Djava.library.path=D:\j2sdk1.4.2_13\jre\bin\server;D:\j2sdk1.4.2_13\jre\bin;D:\j2sdk1.4.2_13\bin;D:\usr\sap\POT\JC01\j2ee\os_libs;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Windows Imaging\;D:\usr\sap\POT\SYS\exe\uc\NTI386
    -> arg[ 37]: -Dmemory.manager=1024M
    -> arg[ 38]: -Xmx1024M
    -> arg[ 39]: -Xms1024M
    -> arg[ 40]: -DLoadBalanceRestricted=no
    -> arg[ 41]: -Djstartup.mode=JCONTROL
    -> arg[ 42]: -Djstartup.ownProcessId=1532
    -> arg[ 43]: -Djstartup.ownHardwareId=O1715315850
    -> arg[ 44]: -Djstartup.whoami=server
    -> arg[ 45]: -Djstartup.debuggable=no
    -> arg[ 46]: -DSAPINFO=POT_01_server
    -> arg[ 47]: -DSAPSTARTUP=1
    -> arg[ 48]: -DSAPSYSTEM=01
    -> arg[ 49]: -DSAPSYSTEMNAME=POT
    -> arg[ 50]: -DSAPMYNAME=SESBPORTUDV_POT_01
    -> arg[ 51]: -DSAPDBHOST=SESBSQL01
    -> arg[ 52]: -Dj2ee.dbhost=SESBSQL01\SAP
    Unrecognized option: services.ts.jts.ots.PortableInterceptor.JTSInitializer
    [Thr 2968] *** ERROR => JHVM_LoadJavaVM: Cannot create Java VM (rc=-1) [jhvmxx.c     542]
    [Thr 2968] *** ERROR => Cannot load Java VM (server) (rc=-1) [jlnchxxi.c   752]
    [Thr 2968] **********************************************************************
    ERROR => Java VM initialization failed.
    Please see SAP Note 943602 , section 'Java VM initialization issues'
    for additional information and trouble shooting.
    [Thr 2968] JLaunchCloseProgram: good bye (exitcode = -1)
    The server has 4Gb of memory, enough disk space and is running the correct JDK version.
    Plz.
    Any ideas?

    I know I tyed all the thing. But at last her is
    dev_bootstrap.
    And Thanks for help.
    trc file: "D:\usr\sap\POT\JC01\work\dev_bootstrap", trc level: 1, release: "700"
    node name   : bootstrap
    pid         : 788
    system name : POT
    system nr.  : 01
    started at  : Thu Sep 18 10:04:34 2008
    arguments       :
           arg[00] : D:\usr\sap\POT\JC01\exe\jlaunch.exe
           arg[01] : pf=D:\usr\sap\POT\SYS\profile\POT_JC01_SESBPORTUDV
           arg[02] : -DSAPINFO=POT_01_bootstrap
           arg[03] : pf=D:\usr\sap\POT\SYS\profile\POT_JC01_SESBPORTUDV
    [Thr 1452] Thu Sep 18 10:04:34 2008
    [Thr 1452] *** WARNING => INFO: Unknown property [instance.box.number=POTJC01sesbportudv] [jstartxx.c   841]
    [Thr 1452] *** WARNING => INFO: Unknown property [instance.en.host=SESBPORTUDV] [jstartxx.c   841]
    [Thr 1452] *** WARNING => INFO: Unknown property [instance.en.port=3200] [jstartxx.c   841]
    [Thr 1452] *** WARNING => INFO: Unknown property [instance.system.id=1] [jstartxx.c   841]
    JStartupReadInstanceProperties: read instance properties [D:\usr\sap\POT\JC01\j2ee\cluster\instance.properties]
    -> ms host    : SESBPORTUDV
    -> ms port    : 3900
    -> OS libs    : D:\usr\sap\POT\JC01\j2ee\os_libs
    -> Admin URL  :
    -> run mode   : normal
    -> run action : NONE
    -> enabled    : yes
    Used property files
    -> files [00] : D:\usr\sap\POT\JC01\j2ee\cluster\instance.properties
    Instance properties
    -> ms host    : SESBPORTUDV
    -> ms port    : 3900
    -> os libs    : D:\usr\sap\POT\JC01\j2ee\os_libs
    -> admin URL  :
    -> run mode   : normal
    -> run action : NONE
    -> enabled    : yes
    Bootstrap nodes
    -> [00] bootstrap            : D:\usr\sap\POT\JC01\j2ee\cluster\instance.properties
    -> [01] bootstrap_ID18437400 : D:\usr\sap\POT\JC01\j2ee\cluster\instance.properties
    -> [02] bootstrap_ID18437450 : D:\usr\sap\POT\JC01\j2ee\cluster\instance.properties
    Worker nodes
    -> [00] ID18437400           : D:\usr\sap\POT\JC01\j2ee\cluster\instance.properties
    -> [01] ID18437450           : D:\usr\sap\POT\JC01\j2ee\cluster\instance.properties
    [Thr 1452] JLaunchRequestQueueInit: create named pipe for ipc
    [Thr 1452] JLaunchRequestQueueInit: create pipe listener thread
    [Thr 1504] WaitSyncSemThread: Thread 1504 started as semaphore monitor thread.
    [Thr 1444] JLaunchRequestFunc: Thread 1444 started as listener thread for np messages.
    [Thr 1452] NiInit3: NI already initialized; param 'maxHandles' ignored (1;202)
    [Thr 1452] CPIC (version=700.2006.09.13)
    [Thr 1452] [Node: bootstrap] java home is set by profile parameter
         Java Home: D:\j2sdk1.4.2_13
    [Thr 1452] JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\POT\JC01\exe\jvmx.jar
    JStartupIReadSection: read node properties [bootstrap]
    -> node name          : bootstrap
    -> node type          : bootstrap
    -> node execute       : yes
    -> java path          : D:\j2sdk1.4.2_13
    -> java parameters    : -Djco.jarm=1
    -> java vm version    : 1.4.2_13-b06
    -> java vm vendor     : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
    -> java vm type       : server
    -> java vm cpu        : x86
    -> heap size          : 256M
    -> root path          : D:\usr\sap\POT\JC01\j2ee\cluster
    -> class path         : .\bootstrap\launcher.jar
    -> OS libs path       : D:\usr\sap\POT\JC01\j2ee\os_libs
    -> main class         : com.sap.engine.offline.OfflineToolStart
    -> framework class    : com.sap.bc.proj.jstartup.JStartupFramework
    -> registr. class     : com.sap.bc.proj.jstartup.JStartupNatives
    -> framework path     : D:\usr\sap\POT\JC01\exe\jstartup.jar;D:\usr\sap\POT\JC01\exe\jvmx.jar
    -> parameters         : com.sap.engine.bootstrap.Bootstrap ./bootstrap ID0184374
    -> debuggable         : yes
    -> debug mode         : no
    -> debug port         : 60000
    -> shutdown timeout   : 120000
    [Thr 1592] JLaunchIStartFunc: Thread 1592 started as Java VM thread.
    JHVM_LoadJavaVM: VM Arguments of node [bootstrap]
    -> stack   : 262144 Bytes
    -> arg[  0]: exit
    -> arg[  1]: abort
    -> arg[  2]: vfprintf
    -> arg[  3]: -Djco.jarm=1
    -> arg[  4]: -Dsys.global.dir=D:\usr\sap\POT\SYS\global
    -> arg[  5]: -Dapplication.home=D:\usr\sap\POT\JC01\exe
    -> arg[  6]: -Djava.class.path=D:\usr\sap\POT\JC01\exe\jstartup.jar;D:\usr\sap\POT\JC01\exe\jvmx.jar;.\bootstrap\launcher.jar
    -> arg[  7]: -Djava.library.path=D:\j2sdk1.4.2_13\jre\bin\server;D:\j2sdk1.4.2_13\jre\bin;D:\j2sdk1.4.2_13\bin;D:\usr\sap\POT\JC01\j2ee\os_libs;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Windows Imaging\;D:\usr\sap\POT\SYS\exe\uc\NTI386
    -> arg[  8]: -Dmemory.manager=256M
    -> arg[  9]: -Xmx256M
    -> arg[ 10]: -DLoadBalanceRestricted=no
    -> arg[ 11]: -Djstartup.mode=BOOTSTRAP
    -> arg[ 12]: -Djstartup.ownProcessId=788
    -> arg[ 13]: -Djstartup.ownHardwareId=O1715315850
    -> arg[ 14]: -Djstartup.whoami=bootstrap
    -> arg[ 15]: -Djstartup.debuggable=yes
    -> arg[ 16]: -DSAPINFO=POT_01_bootstrap
    -> arg[ 17]: -DSAPSTARTUP=1
    -> arg[ 18]: -DSAPSYSTEM=01
    -> arg[ 19]: -DSAPSYSTEMNAME=POT
    -> arg[ 20]: -DSAPMYNAME=SESBPORTUDV_POT_01
    -> arg[ 21]: -DSAPDBHOST=SESBSQL01
    -> arg[ 22]: -Dj2ee.dbhost=SESBSQL01\SAP
    CompilerOracle: exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addIviewResources
    CompilerOracle: exclude com/sap/engine/services/keystore/impl/security/CodeBasedSecurityConnector getApplicationDomain
    CompilerOracle: exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator generateStub
    CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils escapeToJS
    CompilerOracle: exclude com/sapportals/portal/prt/core/broker/PortalServiceItem startServices
    CompilerOracle: exclude com/sap/engine/services/webservices/server/deploy/WSConfigurationHandler downloadFile
    CompilerOracle: exclude com/sapportals/portal/prt/jndisupport/util/AbstractHierarchicalContext lookup
    CompilerOracle: exclude com/sapportals/portal/navigation/cache/CacheNavigationNode getAttributeValue
    CompilerOracle: exclude com/sapportals/portal/navigation/TopLevelNavigationiView PrintNode
    CompilerOracle: exclude com/sapportals/wcm/service/ice/wcm/ICEPropertiesCoder encode
    CompilerOracle: exclude com/sap/lcr/pers/delta/importing/ObjectLoader loadObjects
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readElement
    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 1592] Thu Sep 18 10:04:35 2008
    [Thr 1592] JHVM_LoadJavaVM: Java VM created OK.
    JHVM_BuildArgumentList: main method arguments of node [bootstrap]
    -> arg[  0]: com.sap.engine.bootstrap.Bootstrap
    -> arg[  1]: ./bootstrap
    -> arg[  2]: ID0184374
    [Thr 1592] Thu Sep 18 10:04:36 2008
    [Thr 1592] JHVM_RegisterNatives: registering methods in com.sap.bc.krn.perf.PerfTimes
    [Thr 1604] Thu Sep 18 10:04:41 2008
    [Thr 1604] JLaunchIExitJava: exit hook is called (rc = 0)
    [Thr 1604] JLaunchCloseProgram: good bye (exitcode = 0)

  • BI Integrated Planning: Cannot find a J2EE Engine

    Hi gurus,
    I want to run "Start Modeler" in BI Integrated Planning transaction, but I got a error called "Cannot find a J2EE Engine". Does anyone have any idea to deal with it?
    I will assign reward points for useful comments or answers, thanks in advance.

    Hi,
    before going to work on IP make sure that your system has J2EE ingine if not ask ur basis guyes to integrate EP with ur system.
    i think this is helpfull to you.
    thanks,
    Raju. E

  • Com.sap.security.core.ume.service failed. J2EE Engine cannot be started

    Hi,
    I have configured SNC on NetWeaver 7.0 (ABAP+JAVA) System on Windows 2003 Server with MS-SQL 2005 Database.
    After the SNC configuration restarted the Server but the JAVA Server process is going down with EXIT Code -11113. The SNC Configuration is working fine but JAVA is not running. SDM and dispatcher are in green but server process is going gray.
    I have checked the log files under C:\usr\sap\SID\DVEBMGS00\j2ee\cluster\server0\log
    The following is the part of log file.
    #1.5#005056BA6C3F001D0000000F000008D8000489ACAFC86070#1277274683393#com.sap.engine.core.service630.container.ServiceRunner##com.sap.engine.core.service630.container.ServiceRunner#######SAPEngine_System_Thread[impl:5]_71##0#0#Error#1#/System/Server#Java###Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    [EXCEPTION]
    #1#com.sap.engine.frame.ServiceException: <Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='UME initialization failed.', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key UME initialization failed.
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:372)
         at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
         at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
         at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:105)
    Caused by: com.sap.security.core.persistence.datasource.PersistenceException: SNC required for this connection
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:178)
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:446)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:356)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:156)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:109)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:56)
         at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:266)
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:279)
         ... 6 more
    #1.5#005056BA6C3F001D00000011000008D8000489ACAFC8628E#1277274683393#com.sap.engine.core.Framework##com.sap.engine.core.Framework#######SAPEngine_System_Thread[impl:5]_71##0#0#Fatal#1#/System/Server#Plain###Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.#
    Please help me to solve the issue.
    Thanks,
    Ajay.

    Hi Tim,
    I have configured using Kerberos library for 32 bit on Net Weaver 7.0 with MS SQL 2005 Server on Windows 2003 Server. I didnt change any thing on JAVA side. I have configured as per the Kerberos configuration steps  as per below URL
    http://help.sap.com/saphelp_nw70ehp2/helpdata/en/44/0ebf6c9b2b0d1ae10000000a114a6b/frameset.htm
    The configuration was successful and I am able to login with out asking password, but After the configuration when I have restarted every thing on ABAP side works well but JAVA server process going down with EXIT code -11113. One of the log file contains follows error message.
    com.sap.engine.frame.ServiceException: <Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='UME initialization failed.', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key UME initialization failed.
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:372)
         at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
         at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
         at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:105)
    Caused by: com.sap.security.core.persistence.datasource.PersistenceException: SNC required for this connection
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:178)
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:446)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:356)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:156)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:109)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:56)
         at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:266)
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:279)
         ... 6 more
    [Framework -> criticalShutdown] Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    Jun 25, 2010 3:05:24 AM             com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_69] Fatal: Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    One of the line says "SNC required for this connection". What does this mean? What else need to be done for JAVA to communicate with ABAP?
    Thanks,
    Ajay.

  • J2EE Engine cannot be started. SAP CRM EHP1 Dialog Instance Installation

    Hi All,
    During Installation of a DI on a Linux host, I encounterd a problem. An error occured during " start dialog instance". The ABAP enginee is started successfully where as the JAVA Enginee cant be started. During investigation I found from the log directory
    ..j2ee/cluster/server0/log as stated below ..
    #1.#0050569F663E001E0000000C0000054F0004803004D18B3F#1266843634469#com.sap.engine.core.service630.container.ServiceRunner##com.sap.engine.core.service630.container.ServiceRunner#######SAPEngine_System_Thread[impl:5]_64##0#0#Error#1#/System/Server#Java###Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    [EXCEPTION]
    #1#com.sap.engine.frame.ServiceException: Start of UME service failed. Check help topic "Start of UME Service Failed". Technical details: null
            ume.db.connection_pool_type=SAP/BC_UME
            ume.db.connection_pool.j2ee.xatransactions_used=false
            ume.db.connection_pool.j2ee.is_unicode=false
            ume.db.connection_pool.j2ee.oracle_native_driver_used=false: (No text available)
            at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:398)
            at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
            at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
            at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
            at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
            at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:83)
            at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:109)
    Caused by: com.sap.security.core.persistence.datasource.PersistenceException: null
            ume.db.connection_pool_type=SAP/BC_UME
            ume.db.connection_pool.j2ee.xatransactions_used=false
            ume.db.connection_pool.j2ee.is_unicode=false
            ume.db.connection_pool.j2ee.oracle_native_driver_used=false: (No text available)
            at com.sap.security.core.persistence.datasource.imp.DataBasePersistence.init(DataBasePersistence.java:887)
            at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:440)
            at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:164)
            at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:117)
            at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:63)
            at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:221)
            at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:287)
            ... 6 more
    #1.#0050569F663E001E0000000E0000054F0004803004D18C49#1266843634469#com.sap.engine.core.Framework##com.sap.engine.core.Framework#######SAPEngine_System_Thread[impl:5]_64##0#0#Fatal#1#/System/Server/Critical#Plain###Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.#
    I checked with the env variable and parameter, it all looks good. If anybody finds the same issue please suggest ....
    Thanks in Advance.
    Regards,
    Shashi

    There is a troubleshooting topic for this on the Help Portal.
    See http://help.sap.com/saphelp_nw70ehp1/helpdata/en/20/361941edd5ef23e10000000a155106/frameset.htm.
    -Michael

  • J2EE Engine cannot be started

    Hi All,
    My j2ee engine is not starting. Kindly assist me regarding this. Kindly find below log.
    Where to check this user.
    stdout/stderr redirect
    node name   : server0
    pid         : 229540
    system name : GSQ
    system nr.  : 02
    started at  : Tue Feb 21 18:21:43 2012
    SAP J2EE Engine Version 7.00   PatchLevel 66803.450 is starting...
    Loading: LogManager ... 623 ms.
    Loading: PoolManager ... 2 ms.
    Loading: ApplicationThreadManager ... 3568 ms.
    Loading: ThreadManager ... 28 ms.
    Loading: IpVerificationManager ... 12 ms.
    Loading: ClassLoaderManager ... 20 ms.
    Loading: ClusterManager ... 307 ms.
    Loading: LockingManager ... 84 ms.
    Loading: ConfigurationManager ... 1674 ms.
    Loading: LicensingManager ... 19 ms.
    Loading: CacheManager ... 127 ms.
    Loading: ServiceManager ...
    Loading services.:
      Service DQE started. (37 ms).
      Service memory started. (62 ms).
      Service cafeuodi~mnuacc started. (2 ms).
      Service cross started. (138 ms).
      Service file started. (139 ms).
      Service timeout started. (147 ms).
      Service runtimeinfo started. (91 ms).
      Service trex.service started. (170 ms).
      Service cafeucc~api started. (196 ms).
      Service userstore started. (20 ms).
      Service jmx_notification started. (36 ms).
      Service p4 started. (215 ms).
      Service classpath_resolver started. (49 ms).
    <af type="nursery" id="1" timestamp="Feb 21 18:23:25 2012" intervalms="0.000">
      <minimum requested_bytes="96" />
      <time exclusiveaccessms="0.209" />
      <nursery freebytes="0" totalbytes="209715200" percent="0" />
      <tenured freebytes="1724301920" totalbytes="1728053248" percent="99" >
        <soa freebytes="1637899872" totalbytes="1641651200" percent="99" />
        <loa freebytes="86402048" totalbytes="86402048" percent="100" />
      </tenured>
      <gc type="scavenger" id="1" totalid="1" intervalms="0.000">
        <flipped objectcount="283441" bytes="21271320" />
        <tenured objectcount="0" bytes="0" />
        <refs_cleared soft="685" weak="1" phantom="0" />
        <finalization objectsqueued="1462" />
        <scavenger tiltratio="50" />
        <nursery freebytes="188305568" totalbytes="209715200" percent="89" tenureage="10" />
        <tenured freebytes="1724301920" totalbytes="1728053248" percent="99" >
          <soa freebytes="1637899872" totalbytes="1641651200" percent="99" />
          <loa freebytes="86402048" totalbytes="86402048" percent="100" />
        </tenured>
        <time totalms="101.150" />
      </gc>
      <nursery freebytes="188303520" totalbytes="209715200" percent="89" />
      <tenured freebytes="1724301920" totalbytes="1728053248" percent="99" >
        <soa freebytes="1637899872" totalbytes="1641651200" percent="99" />
        <loa freebytes="86402048" totalbytes="86402048" percent="100" />
      </tenured>
      <time totalms="102.710" />
    </af>
    <af type="nursery" id="2" timestamp="Feb 21 18:23:28 2012" intervalms="3381.768">
      <minimum requested_bytes="32552" />
      <time exclusiveaccessms="0.203" />
      <nursery freebytes="16072" totalbytes="209715200" percent="0" />
      <tenured freebytes="1724285064" totalbytes="1728053248" percent="99" >
        <soa freebytes="1637883016" totalbytes="1641651200" percent="99" />
        <loa freebytes="86402048" totalbytes="86402048" percent="100" />
      </tenured>
      <gc type="scavenger" id="2" totalid="2" intervalms="3383.004">
        <flipped objectcount="405653" bytes="30029056" />
        <tenured objectcount="0" bytes="0" />
        <refs_cleared soft="983" weak="0" phantom="0" />
        <finalization objectsqueued="901" />
        <scavenger tiltratio="50" />
        <nursery freebytes="179257688" totalbytes="209715200" percent="85" tenureage="10" />
        <tenured freebytes="1724285064" totalbytes="1728053248" percent="99" >
          <soa freebytes="1637883016" totalbytes="1641651200" percent="99" />
          <loa freebytes="86402048" totalbytes="86402048" percent="100" />
        </tenured>
        <time totalms="56.165" />
      </gc>
      <nursery freebytes="179225136" totalbytes="209715200" percent="85" />
      <tenured freebytes="1724285064" totalbytes="1728053248" percent="99" >
        <soa freebytes="1637883016" totalbytes="1641651200" percent="99" />
        <loa freebytes="86402048" totalbytes="86402048" percent="100" />
      </tenured>
      <time totalms="57.048" />
    </af>
      Service log_configurator started. (8042 ms).
      Service locking started. (9 ms).
      Service http started. (283 ms).
    <af type="nursery" id="3" timestamp="Feb 21 18:23:31 2012" intervalms="2407.476">
      <minimum requested_bytes="1208" />
      <time exclusiveaccessms="0.309" />
      <nursery freebytes="0" totalbytes="209715200" percent="0" />
      <tenured freebytes="1724206264" totalbytes="1728053248" percent="99" >
        <soa freebytes="1637804216" totalbytes="1641651200" percent="99" />
        <loa freebytes="86402048" totalbytes="86402048" percent="100" />
      </tenured>
      <gc type="scavenger" id="3" totalid="3" intervalms="2408.194">
        <flipped objectcount="554169" bytes="41224280" />
        <tenured objectcount="0" bytes="0" />
        <refs_cleared soft="952" weak="0" phantom="0" />
        <finalization objectsqueued="1316" />
        <scavenger tiltratio="50" />
        <nursery freebytes="167984600" totalbytes="209715200" percent="80" tenureage="10" />
        <tenured freebytes="1724206264" totalbytes="1728053248" percent="99" >
          <soa freebytes="1637804216" totalbytes="1641651200" percent="99" />
          <loa freebytes="86402048" totalbytes="86402048" percent="100" />
        </tenured>
        <time totalms="76.821" />
      </gc>
      <nursery freebytes="167983392" totalbytes="209715200" percent="80" />
      <tenured freebytes="1724206264" totalbytes="1728053248" percent="99" >
        <soa freebytes="1637804216" totalbytes="1641651200" percent="99" />
        <loa freebytes="86402048" totalbytes="86402048" percent="100" />
      </tenured>
      <time totalms="78.249" />
    </af>
      Service naming started. (801 ms).
      Service failover started. (69 ms).
      Service javamail started. (207 ms).
      Service ts started. (173 ms).
      Service appclient started. (192 ms).
      Service licensing started. (47 ms).
      Service jmsconnector started. (308 ms).
      Service connector started. (280 ms).
      Service iiop started. (325 ms).
      Service webservices started. (749 ms).
    <af type="nursery" id="4" timestamp="Feb 21 18:23:33 2012" intervalms="2262.903">
      <minimum requested_bytes="32" />
      <time exclusiveaccessms="0.192" />
      <nursery freebytes="0" totalbytes="209715200" percent="0" />
      <tenured freebytes="1724111408" totalbytes="1728053248" percent="99" >
        <soa freebytes="1637709360" totalbytes="1641651200" percent="99" />
        <loa freebytes="86402048" totalbytes="86402048" percent="100" />
      </tenured>
      <gc type="scavenger" id="4" totalid="4" intervalms="2264.002">
        <flipped objectcount="614335" bytes="45869976" />
        <tenured objectcount="0" bytes="0" />
        <refs_cleared soft="35" weak="0" phantom="0" />
        <finalization objectsqueued="7" />
        <scavenger tiltratio="50" />
        <nursery freebytes="163275192" totalbytes="209715200" percent="77" tenureage="10" />
        <tenured freebytes="1724111408" totalbytes="1728053248" percent="99" >
          <soa freebytes="1637709360" totalbytes="1641651200" percent="99" />
          <loa freebytes="86402048" totalbytes="86402048" percent="100" />
        </tenured>
        <time totalms="78.029" />
      </gc>
      <nursery freebytes="163273144" totalbytes="209715200" percent="77" />
      <tenured freebytes="1724111408" totalbytes="1728053248" percent="99" >
        <soa freebytes="1637709360" totalbytes="1641651200" percent="99" />
        <loa freebytes="86402048" totalbytes="86402048" percent="100" />
      </tenured>
      <time totalms="79.277" />
    </af>
      Service deploy started. (10986 ms).
      Service com.sap.portal.runtime.config.kmreadonly started. (11 ms).
      Service configuration started. (39 ms).
      Service MigrationService started. (69 ms).
      Service bimmrdeployer started. (17 ms).
      Service dbpool started. (1237 ms).
      Service UT started. (14 ms).
      Service cafeugpmailcf started. (53 ms).
    Feb 21, 2012 6:23:37 PM         com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_78] Fatal: Initialization of ABAP data source (com.sap.security.core.persistence.datasource.imp.R3Persistence) failed: "Password logon no longer possible - too many failed attempts". This message is critical if it appears during the startup of the AS Java.
    Feb 21, 2012 6:23:37 PM  ...re.server.ume.service.UMEServiceFrame [SAPEngine_System_Thread[impl:5]_78] Fatal:
      service com.sap.security.core.ume.service ================= ERROR =================
    Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    com.sap.engine.frame.ServiceException: Start of UME service failed. Check help topic "Start of UME Service Failed". Technical details: Password logon no longer possible - too many failed attempts
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:398)
         at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
         at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
         at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:83)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:109)
    Caused by: com.sap.security.core.persistence.datasource.PersistenceException: Password logon no longer possible - too many failed attempts
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:236)
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:491)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:446)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:164)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:117)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:63)
         at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:221)
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:287)
         ... 6 more
    com.sap.engine.frame.ServiceException: Start of UME service failed. Check help topic "Start of UME Service Failed". Technical details: Password logon no longer possible - too many failed attempts
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:398)
         at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
         at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
         at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:83)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:109)
    Caused by: com.sap.security.core.persistence.datasource.PersistenceException: Password logon no longer possible - too many failed attempts
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:236)
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:491)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:446)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:164)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:117)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:63)
         at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:221)
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:287)
         ... 6 more
    [Framework -> criticalShutdown] Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    Feb 21, 2012 6:23:37 PM             com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_78] Fatal: Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    </verbosegc>

    I would recommand to login as <SID>adm to your central instance and go to path usr\sap\<systemid>\<system instance>\J2EE\configtool
    then configtool.bat and start it.
    also access this tool only to make password reset
    Refer thread[http://forums.sdn.sap.com/thread.jspa?threadID=2107011&tstart=15] for setting env variable
    Regards,
    Edited by: Rupali B on Feb 22, 2012 2:09 PM

  • Cannot deploy app files to j2ee engine in NWDS

    Hi,
      I`ve got NWDS ver. 2.0.15 and I am trying to deploy some files to app server but I got message
    Cannot determine sdm host (is empty). Please configure your engine/sdm correctly !
    I am almost 100%  it`s because I need to use proxy to connect the server. I set up proxy settings in window->preferences->workbench->proxy but I think this option doesn't affect to j2ee engine connection. Cause for example I can access portal on port 50000 using my browser (with set up proxy), but I cannot deploy PAR file what`s more the settings window->preferences->SAP Enterprise portal are correct and the same which I used to connect portal using web browser.
      I was thinking about other way to check the connection and SDM Remote GUI came on my mind. Does anybody know how to set up proxy in this program?

    Rich,
      I did it and I am absolutley sure that host and message server are correct. I think that the problem is that to connect server the connection should be via proxy. And I think beacuse of it connection desnt work.
    Look at my example I can connect portal via web browser with configured proxy, but I cannot deploy PAR file using NWDS with the same port and host as I used in browser.
    I have configured proxy in NWDS (window->preferences->workbench->proxy) but I am affraid that this setting doesnt take affect to j2ee engine settings and Enterprise portal deployment settings.
    Now I am looking for tool which gives me possibility to connect SDM some other way with proxy. Or maybe there is some soft that allows me to set all outgoing network connections to go via proxy.

  • NWDS Webdynpro deploy: Cannot login to the SAP J2EE Engine using ......

    Friends,
    I am getting the following error while deploying a web dynpro application through NWDS.
    Aborted: development component 'WebDynpro_ErrorBehavior'/'local'/'LOKAL'/'0.2007.05.29.17.02.04'/'1':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)
    I get this error after I supply the SDM password which NWDS asks before deploying.
    Can someone guide?
    [email protected]
    Thanks

    In the additonal error log it says-
    Unable to compare host[px1db] and host[x900704] Throwable: java.net.UnknownHostException Throwable message: x900704: x900704
    where px1db is my portal server and x900704 is my localmachine name.
    I dont know why it says so ...In NWDS i have configured only px1db.
    any thoughts.
    Vinay

  • After upgrading from 8 to 9.0.1 I no longer have any search engines installed. I would like to install Google as my default search engine. When I click on "get more search engines" I cannot find Google or Bing or -

    Problem with search
    After upgrading from 8 to 9.0.1 I no longer have any search engines installed. I would like to install Google as my default search engine. When I click on “get more search engines” I cannot find Google or Bing or …

    I resolved my issue. Renamed search.sqlite and reinstalled Firefox 9.0.1
    All default search engines are now available.

  • J2EE Engine cannot start after applying SP11 on WAS 6.40

    Hi SAP
    I am upgrading my WAS 6.40 SR1 java instance from SP9 to SP11. At the last stages of the installation the Java instance is stopped & started,at the step where Java instance is started, the 'server' process of the Java instance is not coming up properly. jcmon shows the dispatcher & SDM with status 'running' while server0 is with status 'stopped'.
    Since I'm using ABAP as data source to the J2EE, appears to me that the problem is occuring due to password mismatch for user SAPJSF in R/3 client 168 & between user SAPJSF in J2EE though I'm not sure why the password might change in J2EE after applying SP11.
    Please advice if my reasoning is correct, if no please advice how to solve this problem.
    If yes pls advice how can I change the password for user SAPJSF in J2EE. FYI I already tried changing the password for user SAPJSF using the offline config tool, Under cluster-data-> Instance_ID87066 I select the
    services com.sap.security.core.ume.service, then I select the ume.r3.connection.master.passwd, then the problem is inside the value option I'm not able to input the new password, neither I'm able to delete the old password, so the best thing I can do is Click on Set which opens a small window without any description with 2 options OK & Cancel, here I put the password same as R/3 password & save, after this I re-start the J2EE, but the same problem persists. Please advice on solving the problem.
    Trace file std_server0.out shows that the foll error message......
    Apr 28, 2005 8:09:47 PM com.sap.security.core.persistence
    [SAPEngine_System_Thread[impl:5]_23] Fatal: User Management Engine
    (com.sap.security.core.persistence.datasource.imp.R3Persistence) failed to connect to the ABAP backend system. Check that connection data are correct and the backend system is available. Error message: "Name or password is incorrect. Please re-enter". Connection data (obtained
    from properties of UME service in section "ume.r3.connection.master.": "{
    snc_qop=
    client=168
    abap_debug=
    snc_myname=
    gwserv=
    snc_partnername=
    ashost=CDBNTD03
    group=
    r3name=
    snc_mode=0
    gwhost=
    sysnr=00
    msserv=
    poolmaxsize=10
    snc_lib=
    passwd=********
    poolmaxwait=
    trace=
    receiverid_guest=master
    mshost=
    user=SAPJSF
    lang=
    receiverid=master
    Apr 28, 2005 8:09:47 PM com.sap.security.core.persistence
    [SAPEngine_System_Thread[impl:5]_23] Fatal: Initialization of UME persistence adapter "R3_DATASOURCE" failed.
    service com.sap.security.core.ume.service ================= ERROR
    =================
    Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    com.sap.engine.frame.ServiceException: Name or password is incorrect.
    Please re-enter at com.sap.security.core.server.ume.service.UMEServiceFrame.start
    (UMEServiceFrame.java:555)
    at com.sap.engine.frame.ApplicationFrameAdaptor.start
    (ApplicationFrameAdaptor.java:31)
    at
    com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:
    201)
    at com.sap.engine.core.service630.container.ServiceRunner.run
    (ServiceRunner.java:142)
    at com.sap.engine.frame.core.thread.Task.run(Task.java:60)
    at com.sap.engine.core.thread.impl5.SingleThread.execute
    (SingleThread.java:73)
    at com.sap.engine.core.thread.impl5.SingleThread.run
    (SingleThread.java:145)
    Caused by:
    com.sap.security.core.persistence.datasource.PersistenceException: Name or password is incorrect. Please re-enter
    at
    com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3Persistenc
    eBase.java:1707) at
    com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init (R3PersistenceBase.java:1934)
    std_server0.out (16%)
    Thanks & Rgds,
    Abhishek

    Hi,
    have a look here.
    WebAS - invalid property value

  • Where i find trail version of j2ee engine for client machine.

    Hi,
    I am new bee in sap netweaver . Now i have ecc 5.0 at my office. I need to make WebDyn pro application at my client side. For testing purpose i need to create java environment for running my dynpro applications. So please can any one tell me where i find trail version of j2ee engine for client machine.
    Please explain it and provide me paths where i download environment.
    Regards,
    Gurprit Bhatia

    "(also, my profile says that I'm running OS X 10.4.6, but I'm not really sure, that's just what one of the disks has written on it that came with my used and very cheap machine "
    Click on the blue Apple icon at the top left of your screen and choose About this Mac. That will tell you what your OS version is and what amount of RAM you have. The "More Info" button in the pop-up screen will give you the Apple System Profiler application and that will give you whole bunches of information on the drive space used etc.
    David

Maybe you are looking for