on 03-05-2013 1:18 PM
Hello,
we have installed SAP NETWEAVER PORTAL 7.3. The system is windows Server2008 r2 64bit and with 8GB RAM.
The jstart.exe process of sap MMC (management console/server) is not getting started.
The status for this process is "Some process running".
Initially it started fine and then i changed UME settings DATABASE ONLY to ABAPSYTEM in portal SYSTEM ADMINISTARTION -->UMECONFIGURATION
I have attached the screenshot for reference.
please help me.
I am running into similar issues but I am not able to resolve with the above mentioned solutions:
--------------------------------------------------- trc file: "dev_jstart.2412", trc level: 1, release: "720" --------------------------------------------------- --------------------------------------------------- trc file: "dev_jstart.new", trc level: 1, release: "720" --------------------------------------------------- sysno 00 sid C73 systemid 562 (PC with Windows NT) relno 7200 patchlevel 0 patchno 63 intno 20020600 make multithreaded, Unicode, 64 bit, optimized profile \\ip-0A4F07E3\sapmnt\C73\SYS\profile\C73_J00_ip-0A4F07E3 pid 2412 * * ACTIVE TRACE LEVEL 1 * ACTIVE TRACE COMPONENTS All, egi * Tue Aug 19 13:46:32 2014 * * trace logging activated, max size = 52428800 bytes, 2 versions * arguments : arg[ 0] : C:\usr\sap\C73\J00\exe\jstart.EXE arg[ 1] : pf=\\ip-0A4F07E3\sapmnt\C73\SYS\profile\C73_J00_ip-0A4F07E3 F F Tue Aug 19 13:46:32 2014 F ******************************************************************************** F Java environment properties (C:\usr\sap\C73\J00\work\jstart.jvm) F root directory : C:\usr\sap\C73\J00\exe\sapjvm_6 F vendor : SAP AG F version : 1.6.0_29 F cpu : amd64 F java vm type : server F java vm version : 6.1.037 1.6-b11 F jvm library name : jvm.dll F library path : C:\usr\sap\C73\J00\exe\sapjvm_6\jre\bin\server;C:\usr\sap\C73\J00\exe\sapjvm_6\jre\bin F executable path : C:\usr\sap\C73\J00\exe\sapjvm_6\bin F ******************************************************************************** F SAP extensions : available F ******************************************************************************** I [Thr 3568] MtxInit: 30002 0 2 --------------------------------------------------- trc file: "dev_jstart", trc level: 1, release: "720" --------------------------------------------------- * * ACTIVE TRACE LEVEL 1 * ACTIVE TRACE COMPONENTS All, egi * F [Thr 3568] *** LOG => connected to Enqueue Server. F [Thr 3568] *** LOG => connected to Message Server. F [Thr 3568] *** LOG => Starting run level 1. F ******************************************************************************** F Java process [deployment] properties: F section name : deployment F config file : C:\usr\sap\C73\J00\exe\startup.properties F node name : Deploy_offline F home directory : C:\usr\sap\C73\J00\j2ee\cluster F shutdown timeout : 136000 ms F exit timeout : 7000 ms F debuggable : false F debugger active : false F ******************************************************************************** F [Thr 3568] *** LOG => Instance state is "Deploying offline components" (STARTING @ 0, INACTIVE). F [Thr 3568] *** LOG => Starting nodes: runlevel 1. F ******************************************************************************** F Starting process: C:\usr\sap\C73\J00\exe\jstart.EXE F arg[ 1] = -nodeId=0 F arg[ 2] = pf=\\ip-0A4F07E3\sapmnt\C73\SYS\profile\C73_J00_ip-0A4F07E3 F arg[ 3] = -hostvm F arg[ 4] = -nodeName=deployment F arg[ 5] = -file=C:\usr\sap\C73\J00\exe\startup.properties F arg[ 6] = -jvmFile=C:\usr\sap\C73\J00\work\jstart.jvm F arg[ 7] = -traceFile=C:\usr\sap\C73\J00\work\dev_deployment F arg[ 8] = -javaOutFile=C:\usr\sap\C73\J00\work\jvm_deployment.out F env : NODNSSAPTRANSHOST=1 F exePath : PATH=C:\usr\sap\C73\J00\exe\sapjvm_6\bin;C:\usr\sap\C73\J00\exe;C:\Program Files\Java\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\usr\sap\C73\SYS\exe\uc\NTAMD64;C:\sapdb\clients\C73\bin;C:\sapdb\clients\C73\pgm;C:\sapdb\programs\bin F libPath : PATH=C:\usr\sap\C73\J00\exe\sapjvm_6\jre\bin\server;C:\usr\sap\C73\J00\exe\sapjvm_6\jre\bin;C:\usr\sap\C73\J00\j2ee\os_libs;C:\usr\sap\C73\J00\exe\sapjvm_6\bin;C:\usr\sap\C73\J00\exe;C:\Program Files\Java\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\usr\sap\C73\SYS\exe\uc\NTAMD64;C:\sapdb\clients\C73\bin;C:\sapdb\clients\C73\pgm;C:\sapdb\programs\bin F stdout : C:\usr\sap\C73\J00\work\std_deployment.out F stderr : C:\usr\sap\C73\J00\work\std_deployment.out F console : no F debugger: no F nice : no F ******************************************************************************** F Process Deploy_offline started with pid 2820 F ******************************************************************************** F [Thr 3568] *** LOG => Process deployment started (pid 2820). F F [Thr 3568] Tue Aug 19 13:46:35 2014 F [Thr 3568] *** LOG => Process deployment stopping (pid 2820). F F [Thr 3432] Tue Aug 19 13:46:35 2014 F [Thr 3432] *** LOG => Signal 13 SIGCHLD. F [Thr 3568] *** LOG => Process deployment stopped (pid 2820). F [Thr 3568] *** LOG => Instance state is "Deploying offline components" (STOPPING @ 0, INACTIVE). F [Thr 3568] *** LOG => Run level 1 completed. F [Thr 3568] *** LOG => Starting run level 2. F ******************************************************************************** F Java process [bootstrap] properties: F section name : bootstrap F config file : C:\usr\sap\C73\J00\exe\startup.properties F node name : Instance_bootstrap F home directory : C:\usr\sap\C73\J00\j2ee\cluster F shutdown timeout : 136000 ms F exit timeout : 7000 ms F debuggable : false F debugger active : false F ******************************************************************************** F [Thr 3568] *** LOG => Instance state is "Synchronizing binaries" (STARTING @ 0, INACTIVE). F [Thr 3568] *** LOG => Starting nodes: runlevel 2. F ******************************************************************************** F Starting process: C:\usr\sap\C73\J00\exe\jstart.EXE F arg[ 1] = -nodeId=0 F arg[ 2] = pf=\\ip-0A4F07E3\sapmnt\C73\SYS\profile\C73_J00_ip-0A4F07E3 F arg[ 3] = -hostvm F arg[ 4] = -nodeName=bootstrap F arg[ 5] = -file=C:\usr\sap\C73\J00\exe\startup.properties F arg[ 6] = -jvmFile=C:\usr\sap\C73\J00\work\jstart.jvm F arg[ 7] = -traceFile=C:\usr\sap\C73\J00\work\dev_bootstrap F arg[ 8] = -javaOutFile=C:\usr\sap\C73\J00\work\jvm_bootstrap.out F env : NODNSSAPTRANSHOST=1 F exePath : PATH=C:\usr\sap\C73\J00\exe\sapjvm_6\bin;C:\usr\sap\C73\J00\exe;C:\Program Files\Java\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\usr\sap\C73\SYS\exe\uc\NTAMD64;C:\sapdb\clients\C73\bin;C:\sapdb\clients\C73\pgm;C:\sapdb\programs\bin F libPath : PATH=C:\usr\sap\C73\J00\exe\sapjvm_6\jre\bin\server;C:\usr\sap\C73\J00\exe\sapjvm_6\jre\bin;C:\usr\sap\C73\J00\j2ee\os_libs;C:\usr\sap\C73\J00\exe\sapjvm_6\bin;C:\usr\sap\C73\J00\exe;C:\Program Files\Java\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\usr\sap\C73\SYS\exe\uc\NTAMD64;C:\sapdb\clients\C73\bin;C:\sapdb\clients\C73\pgm;C:\sapdb\programs\bin F stdout : C:\usr\sap\C73\J00\work\std_bootstrap.out F stderr : C:\usr\sap\C73\J00\work\std_bootstrap.out F console : no F debugger: no F nice : no F ******************************************************************************** F Process Instance_bootstrap started with pid 3496 F ******************************************************************************** F [Thr 3568] *** LOG => Process bootstrap started (pid 3496). F F [Thr 3568] Tue Aug 19 13:48:22 2014 F [Thr 3568] *** LOG => Process bootstrap stopping (pid 3496). F F [Thr 3844] Tue Aug 19 13:48:23 2014 F [Thr 3844] *** LOG => Signal 13 SIGCHLD. F F [Thr 3568] Tue Aug 19 13:48:23 2014 F [Thr 3568] *** LOG => Process bootstrap stopped (pid 3496). F [Thr 3568] *** WARNING => Node bootstrap failed: result 1, exit code 556. [sfxxnode.hpp 1024] F ******************************************************************************** F Native process [snapshot] properties: F section name : snapshot F config file : C:\usr\sap\C73\J00\exe\startup.properties F node name : snapshot F home directory : C:\usr\sap\C73\J00\work F shutdown timeout : 122000 ms F sf support : false F ******************************************************************************** F ******************************************************************************** F Starting process: C:\usr\sap\C73\J00\exe\sapcontrol.EXE F arg[ 1] = -prot F arg[ 2] = PIPE F arg[ 3] = -nr F arg[ 4] = 00 F arg[ 5] = -function F arg[ 6] = CreateSnapshot F arg[ 7] = Servercrash F arg[ 8] = postmortem?node=bootstrap&exitcode=556 F arg[ 9] = 1 F arg[10] = 10000 F arg[11] = "" F arg[12] = "" F arg[13] = DEFAULT F env : NODNSSAPTRANSHOST=1 F exePath : PATH=C:\usr\sap\C73\J00\exe;C:\Program Files\Java\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\usr\sap\C73\SYS\exe\uc\NTAMD64;C:\sapdb\clients\C73\bin;C:\sapdb\clients\C73\pgm;C:\sapdb\programs\bin F libPath : PATH=C:\usr\sap\C73\J00\exe;C:\Program Files\Java\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\usr\sap\C73\SYS\exe\uc\NTAMD64;C:\sapdb\clients\C73\bin;C:\sapdb\clients\C73\pgm;C:\sapdb\programs\bin F stdout : C:\usr\sap\C73\J00\work\std_snapshot.out F stderr : C:\usr\sap\C73\J00\work\std_snapshot.out F console : no F debugger: no F nice : no F ******************************************************************************** F Process snapshot started with pid 1152 F ******************************************************************************** F [Thr 3568] *** LOG => Process snapshot started (pid 1152). F [Thr 3568] *** LOG => Process snapshot running (pid 1152). F [Thr 3568] *** LOG => SAP Start Service (pid 3744) connected. F [Thr 3568] *** LOG => SAP Start Service (pid 3744) disconnected. F F [Thr 2892] Tue Aug 19 13:48:35 2014 F [Thr 2892] *** LOG => Signal 13 SIGCHLD. F F [Thr 3568] Tue Aug 19 13:48:35 2014 F [Thr 3568] *** LOG => Process snapshot stopped (pid 1152). F [Thr 3568] *** LOG => Instance state is "Synchronizing binaries" (STOPPING @ 0, INACTIVE). F [Thr 3568] *** LOG => Run level 2 completed. F [Thr 3568] *** LOG => Instance state is "Some processes failed" (STOPPED @ 0, INACTIVE). I [Thr 3568] MPI: dynamic quotas disabled. I [Thr 3568] MPI init: pipes=4000 buffers=1279 reserved=383 quota=10% F F ******************************************************************************** F *** ERROR => Node 'bootstrap' failed with exit code 556. F *** F *** Please see section 'Failures in the 'synchronizing binaries' phase' F *** in SAP Note 1316652 for additional information and trouble shooting advice. F ******************************************************************************** F F [Thr 3568] *** LOG => exiting (exitcode 22002, retcode 1).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear all,
Thanks for your support.
Now jstart.exe is starting . I have reverted back UME settings( ABAPSYSTEM to DATABASE) in Configtool.Problem is UME configuration.
Thanks & Regards,
Satya.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Satya,
I hope you followed the SAP note#718383 for UME datasource related settings.
Please check dev_jstart and dev_server0 and std_server0 logs from work directory for possible error messages.
Regards,
Asha
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi satya,
Can you please paste the content of default.trc file located at usr/sap/<sid>/<instance>/j2ee/cluster/server0/log.
With Regards
Ashutosh Chaturvedi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Satya,
Regarding your issue, can you please try to update the kernel to the latest version available in the SMP.
Thank You.
Regards,
Deepika
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Can you please click on AS JAVA process table screen too?
Thanks and Regards,
Vimal
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Sathya,
Please go through the below two links and see whether it works.
1707693 - J2EE engine startup fails due to backend user account not in validity date error
Thanks and Regards,
Vimal
User | Count |
---|---|
88 | |
10 | |
10 | |
9 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.