- SAP Community
- Products and Technology
- Technology
- Technology Q&A
- jstart.exe process in sap mmc is not getting start...
- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
jstart.exe process in sap mmc is not getting started
- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
on 10-08-2012 6:12 AM
Hi,
The jstart.exe process of sap mmc (management console/server) is not getting started.
The status for this process is "starting the processes". Need help!
The developer trace is as follows :
---------------------------------------------------
trc file: "dev_jstart.7668", trc level: 1, release: "720"
---------------------------------------------------
---------------------------------------------------
trc file: "dev_jstart.new", trc level: 1, release: "720"
---------------------------------------------------
sysno 02
sid SV1
systemid 562 (PC with Windows NT)
relno 7200
patchlevel 0
patchno 63
intno 20020600
make multithreaded, Unicode, 64 bit, optimized
profile \\INLD50787371A\sapmnt\SV1\SYS\profile\SV1_J02_INLD50787371A
pid 7668
*
* ACTIVE TRACE LEVEL 1
* ACTIVE TRACE COMPONENTS All, egi
*
Mon Oct 08 10:03:13 2012
*
* trace logging activated, max size = 52428800 bytes, 2 versions
*
arguments :
arg[ 0] : C:\usr\sap\SV1\J02\exe\jstart.EXE
arg[ 1] : pf=\\INLD50787371A\sapmnt\SV1\SYS\profile\SV1_J02_INLD50787371A
F Mon Oct 08 10:03:13 2012
F ********************************************************************************
F Java environment properties (C:\usr\sap\SV1\J02\work\jstart.jvm)
F root directory : C:\usr\sap\SV1\J02\exe\sapjvm_6
F vendor : SAP AG
F version : 1.6.0_17
F cpu : amd64
F java vm type : server
F java vm version : 6.1.018
F jvm library name : jvm.dll
F library path : C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin\server;C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin
F executable path : C:\usr\sap\SV1\J02\exe\sapjvm_6\bin
F ********************************************************************************
F SAP extensions : available
F ********************************************************************************
I [Thr 7652] MtxInit: 30002 0 2
---------------------------------------------------
trc file: "dev_jstart", trc level: 1, release: "720"
---------------------------------------------------
*
* ACTIVE TRACE LEVEL 1
* ACTIVE TRACE COMPONENTS All, egi
*
F
F [Thr 7652] Mon Oct 08 10:03:14 2012
F [Thr 7652] *** LOG => connected to Enqueue Server.
F [Thr 7652] *** LOG => connected to Message Server.
F [Thr 7652] *** LOG => Starting run level 1.
F ********************************************************************************
F Java process [deployment] properties:
F section name : deployment
F config file : C:\usr\sap\SV1\J02\exe\startup.properties
F node name : Deploy_offline
F home directory : C:\usr\sap\SV1\J02\j2ee\cluster
F shutdown timeout : 136000 ms
F exit timeout : 7000 ms
F debuggable : false
F debugger active : false
F ********************************************************************************
F [Thr 7652] *** LOG => Instance state is "Deploying offline components" (STARTING @ 0, INACTIVE).
F [Thr 7652] *** LOG => Starting nodes: runlevel 1.
F
F Mon Oct 08 10:03:15 2012
F ********************************************************************************
F Starting process: C:\usr\sap\SV1\J02\exe\jstart.EXE
F arg[ 1] = -nodeId=0
F arg[ 2] = pf=\\INLD50787371A\sapmnt\SV1\SYS\profile\SV1_J02_INLD50787371A
F arg[ 3] = -hostvm
F arg[ 4] = -nodeName=deployment
F arg[ 5] = -file=C:\usr\sap\SV1\J02\exe\startup.properties
F arg[ 6] = -jvmFile=C:\usr\sap\SV1\J02\work\jstart.jvm
F arg[ 7] = -traceFile=C:\usr\sap\SV1\J02\work\dev_deployment
F arg[ 8] = -javaOutFile=C:\usr\sap\SV1\J02\work\jvm_deployment.out
F env : NODNSSAPTRANSHOST=1
F exePath : PATH=C:\usr\sap\SV1\J02\exe\sapjvm_6\bin;C:\usr\sap\SV1\J02\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files (x86)\Microsoft Application Virtualization Client;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files (x86)\Java\jdk1.6.0_23\bin;C:\usr\sap\SV1\SYS\exe\uc\NTAMD64;C:\sapdb\clients\SV1\bin;C:\sapdb\clients\SV1\pgm;C:\sapdb\programs\bin
F libPath : PATH=C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin\server;C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin;C:\usr\sap\SV1\J02\j2ee\os_libs;C:\usr\sap\SV1\J02\exe\sapjvm_6\bin;C:\usr\sap\SV1\J02\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files (x86)\Microsoft Application Virtualization Client;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files (x86)\Java\jdk1.6.0_23\bin;C:\usr\sap\SV1\SYS\exe\uc\NTAMD64;C:\sapdb\clients\SV1\bin;C:\sapdb\clients\SV1\pgm;C:\sapdb\programs\bin
F stdout : C:\usr\sap\SV1\J02\work\std_deployment.out
F stderr : C:\usr\sap\SV1\J02\work\std_deployment.out
F console : no
F debugger: no
F nice : no
F ********************************************************************************
F Process Deploy_offline started with pid 7968
F ********************************************************************************
F [Thr 7652] *** LOG => Process deployment started (pid 7968).
F
F [Thr 7652] Mon Oct 08 10:03:19 2012
F [Thr 7652] *** LOG => Process deployment stopping (pid 7968).
F
F [Thr 6972] Mon Oct 08 10:03:19 2012
F [Thr 6972] *** LOG => Signal 13 SIGCHLD.
F [Thr 7652] *** LOG => Process deployment stopped (pid 7968).
F [Thr 7652] *** LOG => Instance state is "Deploying offline components" (STOPPING @ 0, INACTIVE).
F [Thr 7652] *** LOG => Run level 1 completed.
F [Thr 7652] *** LOG => Starting run level 2.
F ********************************************************************************
F Java process [bootstrap] properties:
F section name : bootstrap
F config file : C:\usr\sap\SV1\J02\exe\startup.properties
F node name : Instance_bootstrap
F home directory : C:\usr\sap\SV1\J02\j2ee\cluster
F shutdown timeout : 136000 ms
F exit timeout : 7000 ms
F debuggable : false
F debugger active : false
F ********************************************************************************
F [Thr 7652] *** LOG => Instance state is "Synchronizing binaries" (STARTING @ 0, INACTIVE).
F [Thr 7652] *** LOG => Starting nodes: runlevel 2.
F
F Mon Oct 08 10:03:20 2012
F ********************************************************************************
F Starting process: C:\usr\sap\SV1\J02\exe\jstart.EXE
F arg[ 1] = -nodeId=0
F arg[ 2] = pf=\\INLD50787371A\sapmnt\SV1\SYS\profile\SV1_J02_INLD50787371A
F arg[ 3] = -hostvm
F arg[ 4] = -nodeName=bootstrap
F arg[ 5] = -file=C:\usr\sap\SV1\J02\exe\startup.properties
F arg[ 6] = -jvmFile=C:\usr\sap\SV1\J02\work\jstart.jvm
F arg[ 7] = -traceFile=C:\usr\sap\SV1\J02\work\dev_bootstrap
F arg[ 8] = -javaOutFile=C:\usr\sap\SV1\J02\work\jvm_bootstrap.out
F env : NODNSSAPTRANSHOST=1
F exePath : PATH=C:\usr\sap\SV1\J02\exe\sapjvm_6\bin;C:\usr\sap\SV1\J02\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files (x86)\Microsoft Application Virtualization Client;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files (x86)\Java\jdk1.6.0_23\bin;C:\usr\sap\SV1\SYS\exe\uc\NTAMD64;C:\sapdb\clients\SV1\bin;C:\sapdb\clients\SV1\pgm;C:\sapdb\programs\bin
F libPath : PATH=C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin\server;C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin;C:\usr\sap\SV1\J02\j2ee\os_libs;C:\usr\sap\SV1\J02\exe\sapjvm_6\bin;C:\usr\sap\SV1\J02\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files (x86)\Microsoft Application Virtualization Client;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files (x86)\Java\jdk1.6.0_23\bin;C:\usr\sap\SV1\SYS\exe\uc\NTAMD64;C:\sapdb\clients\SV1\bin;C:\sapdb\clients\SV1\pgm;C:\sapdb\programs\bin
F stdout : C:\usr\sap\SV1\J02\work\std_bootstrap.out
F stderr : C:\usr\sap\SV1\J02\work\std_bootstrap.out
F console : no
F debugger: no
F nice : no
F ********************************************************************************
F Process Instance_bootstrap started with pid 7952
F ********************************************************************************
F [Thr 7652] *** LOG => Process bootstrap started (pid 7952).
F
F [Thr 7652] Mon Oct 08 10:03:47 2012
F [Thr 7652] *** LOG => Process bootstrap running (pid 7952).
F [Thr 7652] *** LOG => Instance state is "Synchronizing binaries" (RUNNING @ 0, INACTIVE).
F
F [Thr 7652] Mon Oct 08 10:04:10 2012
F [Thr 7652] *** LOG => Process bootstrap stopping (pid 7952).
F
F [Thr 4436] Mon Oct 08 10:04:10 2012
F [Thr 4436] *** LOG => Signal 13 SIGCHLD.
F [Thr 7652] *** LOG => Process bootstrap stopped (pid 7952).
F [Thr 7652] *** LOG => Instance state is "Synchronizing binaries" (STOPPING @ 0, INACTIVE).
F [Thr 7652] *** LOG => Run level 2 completed.
F [Thr 7652] *** LOG => Starting run level 3.
F ********************************************************************************
F Java process [debugproxy] properties:
F section name : debugproxy
F config file : C:\usr\sap\SV1\J02\exe\dproxy.properties
F node name : Debug_Proxy
F home directory : C:\usr\sap\SV1\J02/j2ee/rdbg.proxy
F shutdown timeout : 136000 ms
F exit timeout : 7000 ms
F debuggable : false
F debugger active : false
F ********************************************************************************
F ********************************************************************************
F ICM process [icm] properties:
F section name : icm
F config file : C:\usr\sap\SV1\J02\exe\icm.properties
F node name : ICM
F home directory : C:\usr\sap\SV1\J02\work
F shutdown timeout : 122000 ms
F exit timeout : 7000 ms
F ********************************************************************************
F ********************************************************************************
F Java process [server0] properties:
F section name : ID24836450
F config file : C:\usr\sap\SV1\J02\j2ee\cluster\instance.properties
F node name : server0
F home directory : .
F shutdown timeout : 136000 ms
F exit timeout : 7000 ms
F debuggable : true
F debugger active : false
F ********************************************************************************
F [Thr 7652] *** LOG => Instance state is "Starting the processes" (STARTING @ 0, INACTIVE).
F [Thr 7652] *** LOG => Starting nodes: runlevel 3, phase 0.
F ********************************************************************************
F Starting process: C:\usr\sap\SV1\J02\exe\icman.EXE
F arg[ 1] = pf=\\INLD50787371A\sapmnt\SV1\SYS\profile\SV1_J02_INLD50787371A
F arg[ 2] = -nodeId=1
F arg[ 3] = -f
F arg[ 4] = C:\usr\sap\SV1\J02\work\\dev_icm
F env : NODNSSAPTRANSHOST=1
F exePath : PATH=C:\usr\sap\SV1\J02\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files (x86)\Microsoft Application Virtualization Client;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files (x86)\Java\jdk1.6.0_23\bin;C:\usr\sap\SV1\SYS\exe\uc\NTAMD64;C:\sapdb\clients\SV1\bin;C:\sapdb\clients\SV1\pgm;C:\sapdb\programs\bin
F libPath : PATH=C:\usr\sap\SV1\J02\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files (x86)\Microsoft Application Virtualization Client;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files (x86)\Java\jdk1.6.0_23\bin;C:\usr\sap\SV1\SYS\exe\uc\NTAMD64;C:\sapdb\clients\SV1\bin;C:\sapdb\clients\SV1\pgm;C:\sapdb\programs\bin
F stdout : C:\usr\sap\SV1\J02\work\std_icm.out
F stderr : C:\usr\sap\SV1\J02\work\std_icm.out
F console : no
F debugger: no
F nice : no
F ********************************************************************************
F Process ICM started with pid 7336
F ********************************************************************************
F [Thr 7652] *** LOG => Process icm started (pid 7336).
F
F [Thr 7652] Mon Oct 08 10:04:12 2012
F [Thr 7652] *** LOG => Process icm running (pid 7336).
F [Thr 7652] *** LOG => Starting nodes: runlevel 3, phase 1.
F
F Mon Oct 08 10:04:16 2012
F ********************************************************************************
F Starting process: C:\usr\sap\SV1\J02\exe\jstart.EXE
F arg[ 1] = -nodeId=2
F arg[ 2] = pf=\\INLD50787371A\sapmnt\SV1\SYS\profile\SV1_J02_INLD50787371A
F arg[ 3] = -DSAPINFO=SV1_02_server0
F arg[ 4] = -hostvm
F arg[ 5] = -nodeName=ID24836450
F arg[ 6] = -file=C:\usr\sap\SV1\J02\j2ee\cluster\instance.properties
F arg[ 7] = -jvmFile=C:\usr\sap\SV1\J02\work\jstart.jvm
F arg[ 8] = -traceFile=C:\usr\sap\SV1\J02\work\dev_server0
F arg[ 9] = -javaOutFile=C:\usr\sap\SV1\J02\work\jvm_server0.out
F env : NODNSSAPTRANSHOST=1
F exePath : PATH=C:\usr\sap\SV1\J02\exe\sapjvm_6\bin;C:\usr\sap\SV1\J02\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files (x86)\Microsoft Application Virtualization Client;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files (x86)\Java\jdk1.6.0_23\bin;C:\usr\sap\SV1\SYS\exe\uc\NTAMD64;C:\sapdb\clients\SV1\bin;C:\sapdb\clients\SV1\pgm;C:\sapdb\programs\bin
F libPath : PATH=C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin\server;C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin;C:\usr\sap\SV1\J02\j2ee\os_libs;C:\usr\sap\SV1\J02\exe\sapjvm_6\bin;C:\usr\sap\SV1\J02\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files (x86)\Microsoft Application Virtualization Client;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files (x86)\Java\jdk1.6.0_23\bin;C:\usr\sap\SV1\SYS\exe\uc\NTAMD64;C:\sapdb\clients\SV1\bin;C:\sapdb\clients\SV1\pgm;C:\sapdb\programs\bin
F stdout : C:\usr\sap\SV1\J02\work\std_server0.out
F stderr : C:\usr\sap\SV1\J02\work\std_server0.out
F console : no
F debugger: no
F nice : no
F ********************************************************************************
F Process server0 started with pid 7616
F ********************************************************************************
F [Thr 7652] *** LOG => Process server0 started (pid 7616).
- SAP Managed Tags:
- SAP NetWeaver
Accepted Solutions (1)
Accepted Solutions (1)
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi Shruthi,
Logs doesnot show any errors. Sometimes java takes long time to start.
What about other logs like server0 , default trace etc...
Thanks,
Ravi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi Ravi,
Thanks for your quick response.
Where do I find the default trace for this?
The server0 process status is "Waiting to start". The developer trace for server0 is as follows :
---------------------------------------------------
trc file: "dev_server0", trc level: 1, release: "720"
---------------------------------------------------
sysno 02
sid SV1
systemid 562 (PC with Windows NT)
relno 7200
patchlevel 0
patchno 63
intno 20020600
make multithreaded, Unicode, 64 bit, optimized
profile \\INLD50787371A\sapmnt\SV1\SYS\profile\SV1_J02_INLD50787371A
pid 7616
*
* ACTIVE TRACE LEVEL 1
* ACTIVE TRACE COMPONENTS All, egi
*
Mon Oct 08 10:04:17 2012
*
* trace logging activated, max size = 52428800 bytes, 2 versions
*
arguments :
arg[ 0] : C:\usr\sap\SV1\J02\exe\jstart.EXE
arg[ 1] : -appTrc
arg[ 2] : -nodeId=2
arg[ 3] : pf=\\INLD50787371A\sapmnt\SV1\SYS\profile\SV1_J02_INLD50787371A
arg[ 4] : -DSAPINFO=SV1_02_server0
arg[ 5] : -hostvm
arg[ 6] : -nodeName=ID24836450
arg[ 7] : -file=C:\usr\sap\SV1\J02\j2ee\cluster\instance.properties
arg[ 8] : -jvmFile=C:\usr\sap\SV1\J02\work\jstart.jvm
arg[ 9] : -traceFile=C:\usr\sap\SV1\J02\work\dev_server0
arg[10] : -javaOutFile=C:\usr\sap\SV1\J02\work\jvm_server0.out
F
F Mon Oct 08 10:04:17 2012
F ********************************************************************************
F Java environment properties
F root directory : C:\usr\sap\SV1\J02\exe\sapjvm_6
F vendor : SAP AG
F version : 1.6.0_17
F cpu : amd64
F java vm type : server
F java vm version : 6.1.018
F jvm library name : jvm.dll
F library path : C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin\server;C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin
F executable path : C:\usr\sap\SV1\J02\exe\sapjvm_6\bin
F SAP extensions : available
F ********************************************************************************
I [Thr 7280] MtxInit: 10002 0 2
I [Thr 7280] MPI: dynamic quotas disabled.
I [Thr 7280] MPI init: pipes=4000 buffers=1279 reserved=383 quota=10%
M [Thr 7280] NiInit3: NI already initialized; param 'maxHandles' ignored (init=2;par=32768;cur=2048)
M [Thr 7280] CCMS: SemInMgt: Semaphore Management initialized by AlAttachShm_Ext.
M [Thr 7280] CCMS: SemInit: Semaphore 38 initialized by AlAttachShm_Ext.
M [Thr 7280] CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
M [Thr 7280] CCMS: CCMS Monitoring Initialization finished, rc=0.
F
F Mon Oct 08 10:04:17 2012
F ********************************************************************************
F SAP Java VM arguments:
F arg[ 0] = vfprintf
F arg[ 1] = abort
F arg[ 2] = exit
F arg[ 3] = -XmonGcCallback
F arg[ 4] = -XdebugStateChangeCallback
F arg[ 5] = -DSAPJStartVersion=720, patch 68, changelist 1198183, NTAMD64, optU (Oct 20 2010, 01:55:49)
F arg[ 6] = -Xjvmx
F arg[ 7] = -XsapSystem:02
F arg[ 8] = -DSAPSTARTUP=1
F arg[ 9] = -DSAPSYSTEM=02
F arg[10] = -DSAPSYSTEMNAME=SV1
F arg[11] = -DSAPMYNAME=INLD50787371A_SV1_02
F arg[12] = -DSAPDBHOST=INLD50787371A
F arg[13] = -DSAPINFO=SV1_02_server0
F arg[14] = -Dj2ee.dbhost=INLD50787371A
F arg[15] = -Dsun.java.launcher=jstart
F arg[16] = -Dsun.java.command=com.sap.engine.boot.Start
F arg[17] = -Djstartup.mode=JSTART
F arg[18] = -Djstartup.whoami=server
F arg[19] = -Djstartup.ownProcessId=7616
F arg[20] = -Djstartup.ownHardwareId=Q0723431166
F arg[21] = -Djstartup.debuggable=yes
F arg[22] = -DLoadBalanceRestricted=no
F arg[23] = -XdebugPortRange:50221-50221
F arg[24] = -Denv.class.path=
F arg[25] = -Dsys.global.dir=C:\usr\sap\SV1\SYS\global
F arg[26] = -Dapplication.home=C:\usr\sap\SV1\J02\exe
F arg[27] = -Djava.class.path=C:\usr\sap\SV1\J02\exe\jstart71.jar;C:\usr\sap\SV1\J02\exe\sapjvm_6\lib\jvmx.jar;C:\usr\sap\SV1\J02\exe\sapjvm_6\lib\jvmx_tools.jar;C:\usr\sap\SV1\J02\exe\jre\lib\iqlib.jar;C:\usr\sap\SV1\J02\exe\sapjvm_6\lib\tools.jar;C:\usr\sap\SV1\J02\j2ee\cluster\bin\boot\sap.com~tc~bl~jkernel_boot~impl.jar;C:\usr\sap\SV1\J02\j2ee\cluster\bin\boot\jaas.jar;C:\usr\sap\SV1\J02\j2ee\cluster\bin\system\sap.com~tc~bl~bytecode~library.jar;C:\usr\sap\SV1\J02\j2ee\cluster\bin\boot\memoryanalyzer.jar
F arg[28] = -Djava.library.path=C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin\server;C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin;C:\usr\sap\SV1\J02\j2ee\os_libs;C:\usr\sap\SV1\J02\exe\sapjvm_6\bin;C:\usr\sap\SV1\J02\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files (x86)\Microsoft Application Virtualization Client;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files (x86)\Java\jdk1.6.0_23\bin;C:\usr\sap\SV1\SYS\exe\uc\NTAMD64;C:\sapdb\clients\SV1\bin;C:\sapdb\clients\SV1\pgm;C:\sapdb\programs\bin
F arg[29] = -XX:PermSize=1024m
F arg[30] = -Xmx2048m
F arg[31] = -XX:MaxNewSize=410m
F arg[32] = -XX:MaxPermSize=1024m
F arg[33] = -Xms2048m
F arg[34] = -XX:NewSize=410m
F arg[35] = -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
F arg[36] = -Djavax.management.builder.initial=com.sap.pj.jmx.server.interceptor.InterceptorChainBuilder
F arg[37] = -Djmx.invoke.getters=true
F arg[38] = -Djava.security.policy=./../bin/kernel/java.policy
F arg[39] = -Djava.security.egd=file:/dev/urandom
F arg[40] = -Djava.awt.headless=true
F arg[41] = -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
F arg[42] = -Drdbms.driverLocation=C:\sapdb\clients\SV1\runtime\jar\sapdbc.jar
F arg[43] = -Djava.io.tmpdir=./temp
F arg[44] = -Dsun.lang.ClassLoader.allowArraySyntax=true
F arg[45] = -Djava.protocol.handler.pkgs=com.sap.engine.httpdsrclient.protocols|iaik.protocol
F arg[46] = -Dnetworkaddress.cache.ttl=10
F arg[47] = -DSAPJVM_EXTENSION_COMMAND_HANDLER=com.sap.tools.memory.protocol.ProtocolHandler
F arg[48] = -Djco.jarm=1
F arg[49] = -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
F arg[50] = -agentpath:C:\PROGRA~1\JPROFI~1\bin\WINDOW~1\jprofilerti.dll==port=8849
F arg[51] = -XX:+UseConcMarkSweepGC
F arg[52] = -XX:TargetSurvivorRatio=90
F arg[53] = -verbose:gc
F arg[54] = -XX:+DumpDetailedClassStatisticOnOutOfMemory
F arg[55] = -XX:+PrintGCDetails
F arg[56] = -XX:MaxErrorQueueLength=200
F arg[57] = -XX:+PrintGCTimeStamps
F arg[58] = -XX:+DisableExplicitGC
F arg[59] = -XX:SoftRefLRUPolicyMSPerMB=1
F arg[60] = -XX:-StringInternTableInPermGen
F arg[61] = -XX:SurvivorRatio=9
F arg[62] = -XX:+HeapDumpOnOutOfMemoryError
F arg[63] = -XX:HeapDumpPath=OOM.hprof
F arg[64] = -XX:-TraceClassUnloading
F arg[65] = -Xss2097152
F ignore unrecognized options : no
F ********************************************************************************
J JVMX version - Sep 16 2010 15:40:24 - 61_REL - optU - windows amd64 - 6 - bas2:142976 (mixed mode)
J Error occurred during initialization of VM
J Could not find agent library in absolute path: C:\PROGRA?1\JPROFI?1\bin\WINDOW?1\jprofilerti.dll
F [Thr 7364] *** LOG => SfCJavaVm: abort hook is called.
F
F [Thr 7280] Mon Oct 08 12:28:13 2012
F [Thr 7280] *** LOG => Command STOP 0 {}.
F [Thr 7280] *** LOG => Result for STOP 0 {}: 0 ok, 00000000.
F
F [Thr 7280] Mon Oct 08 12:28:33 2012
F [Thr 7280] *** LOG => Command DUMP_THREADS 0 {}.
J
J ================================================================================
J Java thread dump : Mon Oct 08 12:28:33 2012
J
J ================================================================================
F [Thr 7280] *** LOG => Result for DUMP_THREADS 0 {}: 0 ok, 00000000.
M
M [Thr 684] Mon Oct 08 12:28:33 2012
M [Thr 684] CCMS: CCMS Monitoring Cleanup finished successfully.
---------------------------------------------------
trc file: "dev_server0", trc level: 1, release: "720"
---------------------------------------------------
sysno 02
sid SV1
systemid 562 (PC with Windows NT)
relno 7200
patchlevel 0
patchno 63
intno 20020600
make multithreaded, Unicode, 64 bit, optimized
profile \\INLD50787371A\sapmnt\SV1\SYS\profile\SV1_J02_INLD50787371A
pid 5508
*
* ACTIVE TRACE LEVEL 1
* ACTIVE TRACE COMPONENTS All, egi
*
Mon Oct 08 12:28:34 2012
*
* trace logging activated, max size = 52428800 bytes, 2 versions
*
arguments :
arg[ 0] : C:\usr\sap\SV1\J02\exe\jstart.EXE
arg[ 1] : -appTrc
arg[ 2] : -nodeId=2
arg[ 3] : pf=\\INLD50787371A\sapmnt\SV1\SYS\profile\SV1_J02_INLD50787371A
arg[ 4] : -DSAPINFO=SV1_02_server0
arg[ 5] : -hostvm
arg[ 6] : -nodeName=ID24836450
arg[ 7] : -file=C:\usr\sap\SV1\J02\j2ee\cluster\instance.properties
arg[ 8] : -jvmFile=C:\usr\sap\SV1\J02\work\jstart.jvm
arg[ 9] : -traceFile=C:\usr\sap\SV1\J02\work\dev_server0
arg[10] : -javaOutFile=C:\usr\sap\SV1\J02\work\jvm_server0.out
F
F Mon Oct 08 12:28:34 2012
F ********************************************************************************
F Java environment properties
F root directory : C:\usr\sap\SV1\J02\exe\sapjvm_6
F vendor : SAP AG
F version : 1.6.0_17
F cpu : amd64
F java vm type : server
F java vm version : 6.1.018
F jvm library name : jvm.dll
F library path : C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin\server;C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin
F executable path : C:\usr\sap\SV1\J02\exe\sapjvm_6\bin
F SAP extensions : available
F ********************************************************************************
I [Thr 500] MtxInit: 10002 0 2
I [Thr 500] MPI: dynamic quotas disabled.
I [Thr 500] MPI init: pipes=4000 buffers=1279 reserved=383 quota=10%
M [Thr 500] NiInit3: NI already initialized; param 'maxHandles' ignored (init=2;par=32768;cur=2048)
M [Thr 500] CCMS: SemInMgt: Semaphore Management initialized by AlAttachShm_Ext.
M [Thr 500] CCMS: SemInit: Semaphore 38 initialized by AlAttachShm_Ext.
M [Thr 500] CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
M [Thr 500] CCMS: CCMS Monitoring Initialization finished, rc=0.
F
F Mon Oct 08 12:28:34 2012
F ********************************************************************************
F SAP Java VM arguments:
F arg[ 0] = vfprintf
F arg[ 1] = abort
F arg[ 2] = exit
F arg[ 3] = -XmonGcCallback
F arg[ 4] = -XdebugStateChangeCallback
F arg[ 5] = -DSAPJStartVersion=720, patch 68, changelist 1198183, NTAMD64, optU (Oct 20 2010, 01:55:49)
F arg[ 6] = -Xjvmx
F arg[ 7] = -XsapSystem:02
F arg[ 8] = -DSAPSTARTUP=1
F arg[ 9] = -DSAPSYSTEM=02
F arg[10] = -DSAPSYSTEMNAME=SV1
F arg[11] = -DSAPMYNAME=INLD50787371A_SV1_02
F arg[12] = -DSAPDBHOST=INLD50787371A
F arg[13] = -DSAPINFO=SV1_02_server0
F arg[14] = -Dj2ee.dbhost=INLD50787371A
F arg[15] = -Dsun.java.launcher=jstart
F arg[16] = -Dsun.java.command=com.sap.engine.boot.Start
F arg[17] = -Djstartup.mode=JSTART
F arg[18] = -Djstartup.whoami=server
F arg[19] = -Djstartup.ownProcessId=5508
F arg[20] = -Djstartup.ownHardwareId=Q0723431166
F arg[21] = -Djstartup.debuggable=yes
F arg[22] = -DLoadBalanceRestricted=no
F arg[23] = -XdebugPortRange:50221-50221
F arg[24] = -Denv.class.path=
F arg[25] = -Dsys.global.dir=C:\usr\sap\SV1\SYS\global
F arg[26] = -Dapplication.home=C:\usr\sap\SV1\J02\exe
F arg[27] = -Djava.class.path=C:\usr\sap\SV1\J02\exe\jstart71.jar;C:\usr\sap\SV1\J02\exe\sapjvm_6\lib\jvmx.jar;C:\usr\sap\SV1\J02\exe\sapjvm_6\lib\jvmx_tools.jar;C:\usr\sap\SV1\J02\exe\jre\lib\iqlib.jar;C:\usr\sap\SV1\J02\exe\sapjvm_6\lib\tools.jar;C:\usr\sap\SV1\J02\j2ee\cluster\bin\boot\sap.com~tc~bl~jkernel_boot~impl.jar;C:\usr\sap\SV1\J02\j2ee\cluster\bin\boot\jaas.jar;C:\usr\sap\SV1\J02\j2ee\cluster\bin\system\sap.com~tc~bl~bytecode~library.jar;C:\usr\sap\SV1\J02\j2ee\cluster\bin\boot\memoryanalyzer.jar
F arg[28] = -Djava.library.path=C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin\server;C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin;C:\usr\sap\SV1\J02\j2ee\os_libs;C:\usr\sap\SV1\J02\exe\sapjvm_6\bin;C:\usr\sap\SV1\J02\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files (x86)\Microsoft Application Virtualization Client;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files (x86)\Java\jdk1.6.0_23\bin;C:\usr\sap\SV1\SYS\exe\uc\NTAMD64;C:\sapdb\clients\SV1\bin;C:\sapdb\clients\SV1\pgm;C:\sapdb\programs\bin
F arg[29] = -XX:PermSize=1024m
F arg[30] = -Xmx2048m
F arg[31] = -XX:MaxNewSize=410m
F arg[32] = -XX:MaxPermSize=1024m
F arg[33] = -Xms2048m
F arg[34] = -XX:NewSize=410m
F arg[35] = -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
F arg[36] = -Djavax.management.builder.initial=com.sap.pj.jmx.server.interceptor.InterceptorChainBuilder
F arg[37] = -Djmx.invoke.getters=true
F arg[38] = -Djava.security.policy=./../bin/kernel/java.policy
F arg[39] = -Djava.security.egd=file:/dev/urandom
F arg[40] = -Djava.awt.headless=true
F arg[41] = -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
F arg[42] = -Drdbms.driverLocation=C:\sapdb\clients\SV1\runtime\jar\sapdbc.jar
F arg[43] = -Djava.io.tmpdir=./temp
F arg[44] = -Dsun.lang.ClassLoader.allowArraySyntax=true
F arg[45] = -Djava.protocol.handler.pkgs=com.sap.engine.httpdsrclient.protocols|iaik.protocol
F arg[46] = -Dnetworkaddress.cache.ttl=10
F arg[47] = -DSAPJVM_EXTENSION_COMMAND_HANDLER=com.sap.tools.memory.protocol.ProtocolHandler
F arg[48] = -Djco.jarm=1
F arg[49] = -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
F arg[50] = -agentpath:C:\PROGRA~1\JPROFI~1\bin\WINDOW~1\jprofilerti.dll==port=8849
F arg[51] = -XX:+UseConcMarkSweepGC
F arg[52] = -XX:TargetSurvivorRatio=90
F arg[53] = -verbose:gc
F arg[54] = -XX:+DumpDetailedClassStatisticOnOutOfMemory
F arg[55] = -XX:+PrintGCDetails
F arg[56] = -XX:MaxErrorQueueLength=200
F arg[57] = -XX:+PrintGCTimeStamps
F arg[58] = -XX:+DisableExplicitGC
F arg[59] = -XX:SoftRefLRUPolicyMSPerMB=1
F arg[60] = -XX:-StringInternTableInPermGen
F arg[61] = -XX:SurvivorRatio=9
F arg[62] = -XX:+HeapDumpOnOutOfMemoryError
F arg[63] = -XX:HeapDumpPath=OOM.hprof
F arg[64] = -XX:-TraceClassUnloading
F arg[65] = -Xss2097152
F ignore unrecognized options : no
F ********************************************************************************
J JVMX version - Sep 16 2010 15:40:24 - 61_REL - optU - windows amd64 - 6 - bas2:142976 (mixed mode)
J Error occurred during initialization of VM
J Could not find agent library in absolute path: C:\PROGRA?1\JPROFI?1\bin\WINDOW?1\jprofilerti.dll
F [Thr 4136] *** LOG => SfCJavaVm: abort hook is called.
F
F [Thr 500] Mon Oct 08 12:29:02 2012
F [Thr 500] *** LOG => Command DUMP_THREADS 0 {}.
J
J ================================================================================
J Java thread dump : Mon Oct 08 12:29:02 2012
J
J ================================================================================
F [Thr 500] *** LOG => Result for DUMP_THREADS 0 {}: 0 ok, 00000000.
M
M [Thr 5068] Mon Oct 08 12:29:02 2012
M [Thr 5068] CCMS: CCMS Monitoring Cleanup finished successfully.
---------------------------------------------------
trc file: "dev_server0", trc level: 1, release: "720"
---------------------------------------------------
sysno 02
sid SV1
systemid 562 (PC with Windows NT)
relno 7200
patchlevel 0
patchno 63
intno 20020600
make multithreaded, Unicode, 64 bit, optimized
profile \\INLD50787371A\sapmnt\SV1\SYS\profile\SV1_J02_INLD50787371A
pid 7704
*
* ACTIVE TRACE LEVEL 1
* ACTIVE TRACE COMPONENTS All, egi
*
Mon Oct 08 12:29:17 2012
*
* trace logging activated, max size = 52428800 bytes, 2 versions
*
arguments :
arg[ 0] : C:\usr\sap\SV1\J02\exe\jstart.EXE
arg[ 1] : -appTrc
arg[ 2] : -nodeId=2
arg[ 3] : pf=\\INLD50787371A\sapmnt\SV1\SYS\profile\SV1_J02_INLD50787371A
arg[ 4] : -DSAPINFO=SV1_02_server0
arg[ 5] : -hostvm
arg[ 6] : -nodeName=ID24836450
arg[ 7] : -file=C:\usr\sap\SV1\J02\j2ee\cluster\instance.properties
arg[ 8] : -jvmFile=C:\usr\sap\SV1\J02\work\jstart.jvm
arg[ 9] : -traceFile=C:\usr\sap\SV1\J02\work\dev_server0
arg[10] : -javaOutFile=C:\usr\sap\SV1\J02\work\jvm_server0.out
F
F Mon Oct 08 12:29:17 2012
F ********************************************************************************
F Java environment properties
F root directory : C:\usr\sap\SV1\J02\exe\sapjvm_6
F vendor : SAP AG
F version : 1.6.0_17
F cpu : amd64
F java vm type : server
F java vm version : 6.1.018
F jvm library name : jvm.dll
F library path : C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin\server;C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin
F executable path : C:\usr\sap\SV1\J02\exe\sapjvm_6\bin
F SAP extensions : available
F ********************************************************************************
I [Thr 4980] MtxInit: 10002 0 2
I [Thr 4980] MPI: dynamic quotas disabled.
I [Thr 4980] MPI init: pipes=4000 buffers=1279 reserved=383 quota=10%
M [Thr 4980] NiInit3: NI already initialized; param 'maxHandles' ignored (init=2;par=32768;cur=2048)
M [Thr 4980] CCMS: SemInMgt: Semaphore Management initialized by AlAttachShm_Ext.
M [Thr 4980] CCMS: SemInit: Semaphore 38 initialized by AlAttachShm_Ext.
M [Thr 4980] CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
M [Thr 4980] CCMS: CCMS Monitoring Initialization finished, rc=0.
F
F Mon Oct 08 12:29:17 2012
F ********************************************************************************
F SAP Java VM arguments:
F arg[ 0] = vfprintf
F arg[ 1] = abort
F arg[ 2] = exit
F arg[ 3] = -XmonGcCallback
F arg[ 4] = -XdebugStateChangeCallback
F arg[ 5] = -DSAPJStartVersion=720, patch 68, changelist 1198183, NTAMD64, optU (Oct 20 2010, 01:55:49)
F arg[ 6] = -Xjvmx
F arg[ 7] = -XsapSystem:02
F arg[ 8] = -DSAPSTARTUP=1
F arg[ 9] = -DSAPSYSTEM=02
F arg[10] = -DSAPSYSTEMNAME=SV1
F arg[11] = -DSAPMYNAME=INLD50787371A_SV1_02
F arg[12] = -DSAPDBHOST=INLD50787371A
F arg[13] = -DSAPINFO=SV1_02_server0
F arg[14] = -Dj2ee.dbhost=INLD50787371A
F arg[15] = -Dsun.java.launcher=jstart
F arg[16] = -Dsun.java.command=com.sap.engine.boot.Start
F arg[17] = -Djstartup.mode=JSTART
F arg[18] = -Djstartup.whoami=server
F arg[19] = -Djstartup.ownProcessId=7704
F arg[20] = -Djstartup.ownHardwareId=Q0723431166
F arg[21] = -Djstartup.debuggable=yes
F arg[22] = -DLoadBalanceRestricted=no
F arg[23] = -XdebugPortRange:50221-50221
F arg[24] = -Denv.class.path=
F arg[25] = -Dsys.global.dir=C:\usr\sap\SV1\SYS\global
F arg[26] = -Dapplication.home=C:\usr\sap\SV1\J02\exe
F arg[27] = -Djava.class.path=C:\usr\sap\SV1\J02\exe\jstart71.jar;C:\usr\sap\SV1\J02\exe\sapjvm_6\lib\jvmx.jar;C:\usr\sap\SV1\J02\exe\sapjvm_6\lib\jvmx_tools.jar;C:\usr\sap\SV1\J02\exe\jre\lib\iqlib.jar;C:\usr\sap\SV1\J02\exe\sapjvm_6\lib\tools.jar;C:\usr\sap\SV1\J02\j2ee\cluster\bin\boot\sap.com~tc~bl~jkernel_boot~impl.jar;C:\usr\sap\SV1\J02\j2ee\cluster\bin\boot\jaas.jar;C:\usr\sap\SV1\J02\j2ee\cluster\bin\system\sap.com~tc~bl~bytecode~library.jar;C:\usr\sap\SV1\J02\j2ee\cluster\bin\boot\memoryanalyzer.jar
F arg[28] = -Djava.library.path=C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin\server;C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin;C:\usr\sap\SV1\J02\j2ee\os_libs;C:\usr\sap\SV1\J02\exe\sapjvm_6\bin;C:\usr\sap\SV1\J02\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files (x86)\Microsoft Application Virtualization Client;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files (x86)\Java\jdk1.6.0_23\bin;C:\usr\sap\SV1\SYS\exe\uc\NTAMD64;C:\sapdb\clients\SV1\bin;C:\sapdb\clients\SV1\pgm;C:\sapdb\programs\bin
F arg[29] = -XX:PermSize=1024m
F arg[30] = -Xmx2048m
F arg[31] = -XX:MaxNewSize=410m
F arg[32] = -XX:MaxPermSize=1024m
F arg[33] = -Xms2048m
F arg[34] = -XX:NewSize=410m
F arg[35] = -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
F arg[36] = -Djavax.management.builder.initial=com.sap.pj.jmx.server.interceptor.InterceptorChainBuilder
F arg[37] = -Djmx.invoke.getters=true
F arg[38] = -Djava.security.policy=./../bin/kernel/java.policy
F arg[39] = -Djava.security.egd=file:/dev/urandom
F arg[40] = -Djava.awt.headless=true
F arg[41] = -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
F arg[42] = -Drdbms.driverLocation=C:\sapdb\clients\SV1\runtime\jar\sapdbc.jar
F arg[43] = -Djava.io.tmpdir=./temp
F arg[44] = -Dsun.lang.ClassLoader.allowArraySyntax=true
F arg[45] = -Djava.protocol.handler.pkgs=com.sap.engine.httpdsrclient.protocols|iaik.protocol
F arg[46] = -Dnetworkaddress.cache.ttl=10
F arg[47] = -DSAPJVM_EXTENSION_COMMAND_HANDLER=com.sap.tools.memory.protocol.ProtocolHandler
F arg[48] = -Djco.jarm=1
F arg[49] = -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
F arg[50] = -agentpath:C:\PROGRA~1\JPROFI~1\bin\WINDOW~1\jprofilerti.dll==port=8849
F arg[51] = -XX:+UseConcMarkSweepGC
F arg[52] = -XX:TargetSurvivorRatio=90
F arg[53] = -verbose:gc
F arg[54] = -XX:+DumpDetailedClassStatisticOnOutOfMemory
F arg[55] = -XX:+PrintGCDetails
F arg[56] = -XX:MaxErrorQueueLength=200
F arg[57] = -XX:+PrintGCTimeStamps
F arg[58] = -XX:+DisableExplicitGC
F arg[59] = -XX:SoftRefLRUPolicyMSPerMB=1
F arg[60] = -XX:-StringInternTableInPermGen
F arg[61] = -XX:SurvivorRatio=9
F arg[62] = -XX:+HeapDumpOnOutOfMemoryError
F arg[63] = -XX:HeapDumpPath=OOM.hprof
F arg[64] = -XX:-TraceClassUnloading
F arg[65] = -Xss2097152
F ignore unrecognized options : no
F ********************************************************************************
J JVMX version - Sep 16 2010 15:40:24 - 61_REL - optU - windows amd64 - 6 - bas2:142976 (mixed mode)
J Error occurred during initialization of VM
J Could not find agent library in absolute path: C:\PROGRA?1\JPROFI?1\bin\WINDOW?1\jprofilerti.dll
F [Thr 4736] *** LOG => SfCJavaVm: abort hook is called.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
I found the solution to this problem. In the developer trace for server0 as shown above you can see
J Error occurred during initialization of VM
J Could not find agent library in absolute path: C:\PROGRA?1\JPROFI?1\bin\WINDOW?1\jprofilerti.dll
F [Thr 4736] *** LOG => SfCJavaVm: abort hook is called.
This was because the instance.properties file (found in C:\usr\sap\SV1\J02\j2ee\cluster
folder) had a reference to this dll file (jprofilerti.dll) which does not exist in the system.
On removing the reference, and restarting the server, all processes start up.
Answers (0)
- SAP Cloud Integration: Understanding the XML Digital Signature Standard in Technology Blogs by SAP
- Best practice how to deal with action parameters in RAP service in Technology Q&A
- Harnessing the Power of SAP HANA Cloud Vector Engine for Context-Aware LLM Architecture in Technology Blogs by SAP
- Long Awaited Transformation for Your Credentials in Technology Blogs by Members
- Part 4 - SAP MDG – A Stepping Stone for SAP S/4HANA Journey in Technology Blogs by Members
| User | Count |
|---|---|
| 94 | |
| 13 | |
| 13 | |
| 11 | |
| 11 | |
| 7 | |
| 5 | |
| 4 | |
| 4 | |
| 4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.