Hi,
Can you please right click on the jsatrt and then past the developer trace.
From the screen it looks like more data should be visible but its not.
Have you disable all the firewall on this machine and the firewall.
Thanks
Rishi Abrol
↧
Re: Netweaver 7.4 Install Stop Error - SCS01 will not start (err code: FCO-00011)
↧
Re: Netweaver 7.4 Install Stop Error - SCS01 will not start (err code: FCO-00011)
This is what I can see, but I thought this could be related to the install not fully completing yet?
↧
↧
Re: Netweaver 7.4 Install Stop Error - SCS01 will not start (err code: FCO-00011)
Here we go, yes the firewall disabled:
---------------------------------------------------
trc file: "dev_jstart.3144", trc level: 1, release: "740"
---------------------------------------------------
---------------------------------------------------
trc file: "dev_jstart.new", trc level: 1, release: "740"
---------------------------------------------------
sysno 00
sid J23
systemid 562 (PC with Windows NT)
relno 7400
patchlevel 0
patchno 0
intno 20020600
make multithreaded, Unicode, 64 bit, optimized
profile \\NWCE74PI\sapmnt\J23\SYS\profile\J23_J00_NWCE74PI
pid 3144
*
* ACTIVE TRACE LEVEL 1
* ACTIVE TRACE COMPONENTS All, egi
*
Tue Dec 24 10:26:22 2013
*
* trace logging activated, max size = 52428800 bytes, 2 versions
*
arguments :
arg[ 0] : C:\usr\sap\J23\J00\exe\jstart.EXE
arg[ 1] : pf=\\NWCE74PI\sapmnt\J23\SYS\profile\J23_J00_NWCE74PI
F
F [Thr 3152] Tue Dec 24 10:26:22 2013
F [Thr 3152] *** WARNING => SfCheckJeeVersion: Cannot find JEE application directory C:\usr\sap\J23\J00\j2ee\cluster\apps. [sfxxmain.cpp 861]
F ********************************************************************************
F Java environment properties (C:\usr\sap\J23\J00\work\jstart.jvm)
F root directory : C:\usr\sap\J23\J00\exe\sapjvm_6
F vendor : SAP AG
F version : 1.6.0_43
F cpu : amd64
F java vm type : server
F java vm version : 6.1.048 23.5-b01
F jvm library name : jvm.dll
F library path : C:\usr\sap\J23\J00\exe\sapjvm_6\jre\bin\server;C:\usr\sap\J23\J00\exe\sapjvm_6\jre\bin
F executable path : C:\usr\sap\J23\J00\exe\sapjvm_6\bin
F ********************************************************************************
F SAP extensions : available
F ********************************************************************************
I [Thr 3152] MtxInit: 30002 0 2
---------------------------------------------------
trc file: "dev_jstart", trc level: 1, release: "740"
---------------------------------------------------
*
* ACTIVE TRACE LEVEL 1
* ACTIVE TRACE COMPONENTS All, egi
*
F
F [Thr 3152] Tue Dec 24 10:26:23 2013
F [Thr 3152] *** LOG => connected to Enqueue Server.
F [Thr 3152] *** LOG => connected to Message Server.
F [Thr 3152] *** LOG => Starting run level 1.
F ********************************************************************************
F Java process [deployment] properties:
F section name : deployment
F config file : C:\usr\sap\J23\J00\exe\startup.properties
F node name : Deploy_offline
F home directory : C:\usr\sap\J23\J00\j2ee\cluster
F shutdown timeout : 136000 ms
F exit timeout : 7000 ms
F debuggable : false
F debugger active : false
F ********************************************************************************
F [Thr 3152] *** LOG => Instance state is "Deploying offline components" (STARTING @ 0, INACTIVE).
F [Thr 3152] *** LOG => Starting nodes: runlevel 1.
F ********************************************************************************
F Starting process: C:\usr\sap\J23\J00\exe\jstart.EXE
F arg[ 1] = -nodeId=0
F arg[ 2] = pf=\\NWCE74PI\sapmnt\J23\SYS\profile\J23_J00_NWCE74PI
F arg[ 3] = -hostvm
F arg[ 4] = -nodeName=deployment
F arg[ 5] = -file=C:\usr\sap\J23\J00\exe\startup.properties
F arg[ 6] = -jvmFile=C:\usr\sap\J23\J00\work\jstart.jvm
F arg[ 7] = -traceFile=C:\usr\sap\J23\J00\work\dev_deployment
F arg[ 8] = -javaOutFile=C:\usr\sap\J23\J00\work\jvm_deployment.out
F env : NODNSSAPTRANSHOST=1
F exePath : PATH=C:\usr\sap\J23\J00\exe\sapjvm_6\bin;C:\usr\sap\J23\J00\exe;C:\Program Files (x86)\Parallels\Parallels Tools\Applications;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\usr\sap\J23\SYS\exe\uc\NTAMD64;C:\sapdb\clients\J23\bin;C:\sapdb\clients\J23\pgm;C:\sapdb\programs\bin
F libPath : PATH=C:\usr\sap\J23\J00\exe\sapjvm_6\jre\bin\server;C:\usr\sap\J23\J00\exe\sapjvm_6\jre\bin;C:\usr\sap\J23\J00\j2ee\os_libs;C:\usr\sap\J23\J00\exe\sapjvm_6\bin;C:\usr\sap\J23\J00\exe;C:\Program Files (x86)\Parallels\Parallels Tools\Applications;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\usr\sap\J23\SYS\exe\uc\NTAMD64;C:\sapdb\clients\J23\bin;C:\sapdb\clients\J23\pgm;C:\sapdb\programs\bin
F stdout : C:\usr\sap\J23\J00\work\std_deployment.out
F stderr : C:\usr\sap\J23\J00\work\std_deployment.out
F console : no
F debugger: no
F nice : no
F ********************************************************************************
F Process Deploy_offline started with pid 3552
F ********************************************************************************
F [Thr 3152] *** LOG => Process deployment started (pid 3552).
F
F [Thr 3152] Tue Dec 24 10:26:24 2013
F [Thr 3152] *** LOG => Process deployment stopping (pid 3552).
F
F [Thr 4084] Tue Dec 24 10:26:25 2013
F [Thr 4084] *** LOG => Signal 13 SIGCHLD.
F
F [Thr 3152] Tue Dec 24 10:26:25 2013
F [Thr 3152] *** LOG => Process deployment stopped (pid 3552).
F [Thr 3152] *** LOG => Instance state is "Deploying offline components" (STOPPING @ 0, INACTIVE).
F [Thr 3152] *** LOG => Run level 1 completed.
F [Thr 3152] *** LOG => Starting run level 2.
F ********************************************************************************
F Java process [bootstrap] properties:
F section name : bootstrap
F config file : C:\usr\sap\J23\J00\exe\startup.properties
F node name : Instance_bootstrap
F home directory : C:\usr\sap\J23\J00\j2ee\cluster
F shutdown timeout : 136000 ms
F exit timeout : 7000 ms
F debuggable : false
F debugger active : false
F ********************************************************************************
F [Thr 3152] *** LOG => Instance state is "Synchronizing binaries" (STARTING @ 0, INACTIVE).
F [Thr 3152] *** LOG => Starting nodes: runlevel 2.
F ********************************************************************************
F Starting process: C:\usr\sap\J23\J00\exe\jstart.EXE
F arg[ 1] = -nodeId=0
F arg[ 2] = pf=\\NWCE74PI\sapmnt\J23\SYS\profile\J23_J00_NWCE74PI
F arg[ 3] = -hostvm
F arg[ 4] = -nodeName=bootstrap
F arg[ 5] = -file=C:\usr\sap\J23\J00\exe\startup.properties
F arg[ 6] = -jvmFile=C:\usr\sap\J23\J00\work\jstart.jvm
F arg[ 7] = -traceFile=C:\usr\sap\J23\J00\work\dev_bootstrap
F arg[ 8] = -javaOutFile=C:\usr\sap\J23\J00\work\jvm_bootstrap.out
F env : NODNSSAPTRANSHOST=1
F exePath : PATH=C:\usr\sap\J23\J00\exe\sapjvm_6\bin;C:\usr\sap\J23\J00\exe;C:\Program Files (x86)\Parallels\Parallels Tools\Applications;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\usr\sap\J23\SYS\exe\uc\NTAMD64;C:\sapdb\clients\J23\bin;C:\sapdb\clients\J23\pgm;C:\sapdb\programs\bin
F libPath : PATH=C:\usr\sap\J23\J00\exe\sapjvm_6\jre\bin\server;C:\usr\sap\J23\J00\exe\sapjvm_6\jre\bin;C:\usr\sap\J23\J00\j2ee\os_libs;C:\usr\sap\J23\J00\exe\sapjvm_6\bin;C:\usr\sap\J23\J00\exe;C:\Program Files (x86)\Parallels\Parallels Tools\Applications;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\usr\sap\J23\SYS\exe\uc\NTAMD64;C:\sapdb\clients\J23\bin;C:\sapdb\clients\J23\pgm;C:\sapdb\programs\bin
F stdout : C:\usr\sap\J23\J00\work\std_bootstrap.out
F stderr : C:\usr\sap\J23\J00\work\std_bootstrap.out
F console : no
F debugger: no
F nice : no
F ********************************************************************************
F Process Instance_bootstrap started with pid 2636
F ********************************************************************************
F [Thr 3152] *** LOG => Process bootstrap started (pid 2636).
F
F [Thr 3152] Tue Dec 24 10:26:27 2013
F [Thr 3152] *** LOG => Process bootstrap running (pid 2636).
F [Thr 3152] *** LOG => Instance state is "Synchronizing binaries" (RUNNING @ 0, INACTIVE).
F
F [Thr 3152] Tue Dec 24 10:26:28 2013
F [Thr 3152] *** LOG => Process bootstrap stopping (pid 2636).
F
F [Thr 3728] Tue Dec 24 10:26:29 2013
F [Thr 3728] *** LOG => Signal 13 SIGCHLD.
F
F [Thr 3152] Tue Dec 24 10:26:29 2013
F [Thr 3152] *** LOG => Process bootstrap stopped (pid 2636).
F [Thr 3152] *** LOG => Instance state is "Synchronizing binaries" (STOPPING @ 0, INACTIVE).
F [Thr 3152] *** LOG => Run level 2 completed.
F [Thr 3152] *** LOG => Starting run level 3.
F ********************************************************************************
F Java process [debugproxy] properties:
F section name : debugproxy
F config file : C:\usr\sap\J23\J00\exe\dproxy.properties
F node name : Debug_Proxy
F home directory : C:\usr\sap\J23\J00/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\J23\J00\exe\icm.properties
F node name : ICM
F home directory : C:\usr\sap\J23\J00\work
F shutdown timeout : 122000 ms
F exit timeout : 7000 ms
F ********************************************************************************
F ********************************************************************************
F Java process [server0] properties:
F section name : ID3963950
F config file : C:\usr\sap\J23\J00\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 3152] *** LOG => Instance state is "Starting the processes" (STARTING @ 0, INACTIVE).
F [Thr 3152] *** LOG => Starting nodes: runlevel 3, phase 0.
F ********************************************************************************
F Starting process: C:\usr\sap\J23\J00\exe\icman.EXE
F arg[ 1] = pf=\\NWCE74PI\sapmnt\J23\SYS\profile\J23_J00_NWCE74PI
F arg[ 2] = -nodeId=1
F arg[ 3] = -f
F arg[ 4] = C:\usr\sap\J23\J00\work\\dev_icm
F env : NODNSSAPTRANSHOST=1
F exePath : PATH=C:\usr\sap\J23\J00\exe;C:\Program Files (x86)\Parallels\Parallels Tools\Applications;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\usr\sap\J23\SYS\exe\uc\NTAMD64;C:\sapdb\clients\J23\bin;C:\sapdb\clients\J23\pgm;C:\sapdb\programs\bin
F libPath : PATH=C:\usr\sap\J23\J00\exe;C:\Program Files (x86)\Parallels\Parallels Tools\Applications;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\usr\sap\J23\SYS\exe\uc\NTAMD64;C:\sapdb\clients\J23\bin;C:\sapdb\clients\J23\pgm;C:\sapdb\programs\bin
F stdout : C:\usr\sap\J23\J00\work\std_icm.out
F stderr : C:\usr\sap\J23\J00\work\std_icm.out
F console : no
F debugger: no
F nice : no
F ********************************************************************************
F Process ICM started with pid 3636
F ********************************************************************************
F [Thr 3152] *** LOG => Process icm started (pid 3636).
F [Thr 3152] *** LOG => Process icm running (pid 3636).
F [Thr 3152] *** LOG => Starting nodes: runlevel 3, phase 1.
F ********************************************************************************
F Starting process: C:\usr\sap\J23\J00\exe\jstart.EXE
F arg[ 1] = -nodeId=2
F arg[ 2] = pf=\\NWCE74PI\sapmnt\J23\SYS\profile\J23_J00_NWCE74PI
F arg[ 3] = -DSAPINFO=J23_00_server0
F arg[ 4] = -hostvm
F arg[ 5] = -nodeName=ID3963950
F arg[ 6] = -file=C:\usr\sap\J23\J00\j2ee\cluster\instance.properties
F arg[ 7] = -jvmFile=C:\usr\sap\J23\J00\work\jstart.jvm
F arg[ 8] = -traceFile=C:\usr\sap\J23\J00\work\dev_server0
F arg[ 9] = -javaOutFile=C:\usr\sap\J23\J00\work\jvm_server0.out
F env : NODNSSAPTRANSHOST=1
F exePath : PATH=C:\usr\sap\J23\J00\exe\sapjvm_6\bin;C:\usr\sap\J23\J00\exe;C:\Program Files (x86)\Parallels\Parallels Tools\Applications;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\usr\sap\J23\SYS\exe\uc\NTAMD64;C:\sapdb\clients\J23\bin;C:\sapdb\clients\J23\pgm;C:\sapdb\programs\bin
F libPath : PATH=C:\usr\sap\J23\J00\exe\sapjvm_6\jre\bin\server;C:\usr\sap\J23\J00\exe\sapjvm_6\jre\bin;C:\usr\sap\J23\J00\j2ee\os_libs;C:\usr\sap\J23\J00\exe\sapjvm_6\bin;C:\usr\sap\J23\J00\exe;C:\Program Files (x86)\Parallels\Parallels Tools\Applications;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\usr\sap\J23\SYS\exe\uc\NTAMD64;C:\sapdb\clients\J23\bin;C:\sapdb\clients\J23\pgm;C:\sapdb\programs\bin
F stdout : C:\usr\sap\J23\J00\work\std_server0.out
F stderr : C:\usr\sap\J23\J00\work\std_server0.out
F console : no
F debugger: no
F nice : no
F ********************************************************************************
F Process server0 started with pid 1820
F ********************************************************************************
F [Thr 3152] *** LOG => Process server0 started (pid 1820).
F
F [Thr 3152] Tue Dec 24 10:26:34 2013
F [Thr 3152] *** LOG => Process server0 stopping (pid 1820).
F
F [Thr 2284] Tue Dec 24 10:26:34 2013
F [Thr 2284] *** LOG => Signal 13 SIGCHLD.
F [Thr 3152] *** LOG => Process server0 stopped (pid 1820).
F [Thr 3152] *** WARNING => Node server0 failed: result 2, exit code -1501. [sfxxnode.hpp 1024]
F ********************************************************************************
F Native process [snapshot] properties:
F section name : snapshot
F config file : C:\usr\sap\J23\J00\exe\startup.properties
F node name : snapshot
F home directory : C:\usr\sap\J23\J00\work
F shutdown timeout : 122000 ms
F sf support : false
F ********************************************************************************
F ********************************************************************************
F Starting process: C:\usr\sap\J23\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=ID3963950&exitcode=-1501
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\J23\J00\exe;C:\Program Files (x86)\Parallels\Parallels Tools\Applications;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\usr\sap\J23\SYS\exe\uc\NTAMD64;C:\sapdb\clients\J23\bin;C:\sapdb\clients\J23\pgm;C:\sapdb\programs\bin
F libPath : PATH=C:\usr\sap\J23\J00\exe;C:\Program Files (x86)\Parallels\Parallels Tools\Applications;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\usr\sap\J23\SYS\exe\uc\NTAMD64;C:\sapdb\clients\J23\bin;C:\sapdb\clients\J23\pgm;C:\sapdb\programs\bin
F stdout : C:\usr\sap\J23\J00\work\std_snapshot.out
F stderr : C:\usr\sap\J23\J00\work\std_snapshot.out
F console : no
F debugger: no
F nice : no
F ********************************************************************************
F Process snapshot started with pid 3584
F ********************************************************************************
F [Thr 3152] *** LOG => Process snapshot started (pid 3584).
F [Thr 3152] *** LOG => Process snapshot running (pid 3584).
F [Thr 3152] *** LOG => SAP Start Service (pid 1848) connected.
F [Thr 3152] *** LOG => Command THREAD_GET_CALLSTACK 2 (12) from SAP Start Service (pid 1848).
F [Thr 3152] *** WARNING => SfCJavaProcHandler(server0)::onProcCmd: state 1070 STOPPED cannot handle [mType=PROC_CMD, mReply=TRUE, pca=[cmd=GET_CALLSTACK, procId=2, arg=12], mpEvent=[mType=NODE_CMD, mReply=TRUE, nca=[cmd=GET_CALLSTACK, nodeId=2]]]! [sfxxproc.hpp 2031]
F [Thr 3152] *** WARNING => SfCEventDispatcher::processQueue: rc 3 (invalid function argument) from SfCJavaProcHandler(server0)([mType=PROC_CMD, mReply=TRUE, pca=[cmd=GET_CALLSTACK, procId=2, arg=12], mpEvent=[mType=NODE_CMD, mReply=TRUE, nca=[cmd=GET_CALLSTACK, nodeId=2]]]) [sfxxevt.hpp 3156]
F [Thr 3152] *** WARNING => SfCNodeManager(server0)::onReply: command 2010 GET_CALLSTACK returned 3 invalid function argument. [sfxxnode.hpp 1519]
F [Thr 3152] *** LOG => Result for THREAD_GET_CALLSTACK 12 {}: 3 invalid function argument, 00000000.
F [Thr 3152] *** LOG => SAP Start Service (pid 1848) disconnected.
F
F [Thr 3224] Tue Dec 24 10:26:39 2013
F [Thr 3224] *** LOG => Signal 13 SIGCHLD.
F
F [Thr 3152] Tue Dec 24 10:26:39 2013
F [Thr 3152] *** LOG => Process snapshot stopped (pid 3584).
F [Thr 3152] *** LOG => Removing enque locks for ID 3963950.
F [Thr 3152] *** LOG => Instance state is "Some processes running" (RUNNING @ 0, INACTIVE).
F
F [Thr 3152] Tue Dec 24 11:27:36 2013
F [Thr 3152] *** LOG => SAP Start Service (pid 1848) connected.
F [Thr 3152] *** LOG => Command NODE_DUMPSTACKS 2 from SAP Start Service (pid 1848).
F [Thr 3152] *** WARNING => SfCEventDispatcher::callEvent: rc 16 (wrong state for operation) from SfCNodeManager(server0)([mType=NODE_CMD, nca=[cmd=DUMP_THREADS, nodeId=2]]) [sfxxevt.hpp 2518]
F [Thr 3152] *** LOG => Result for NODE_DUMPSTACKS 2 {}: 16 wrong state for operation, 00000000.
F [Thr 3152] *** LOG => SAP Start Service (pid 1848) disconnected.
F
F [Thr 3152] Tue Dec 24 11:30:28 2013
F [Thr 3152] *** LOG => SAP Start Service (pid 1848) connected.
F [Thr 3152] *** LOG => Command NODE_START 2 {} from SAP Start Service (pid 1848).
F ********************************************************************************
F Starting process: C:\usr\sap\J23\J00\exe\jstart.EXE
F arg[ 1] = -nodeId=2
F arg[ 2] = pf=\\NWCE74PI\sapmnt\J23\SYS\profile\J23_J00_NWCE74PI
F arg[ 3] = -DSAPINFO=J23_00_server0
F arg[ 4] = -hostvm
F arg[ 5] = -nodeName=ID3963950
F arg[ 6] = -file=C:\usr\sap\J23\J00\j2ee\cluster\instance.properties
F arg[ 7] = -jvmFile=C:\usr\sap\J23\J00\work\jstart.jvm
F arg[ 8] = -traceFile=C:\usr\sap\J23\J00\work\dev_server0
F arg[ 9] = -javaOutFile=C:\usr\sap\J23\J00\work\jvm_server0.out
F env : NODNSSAPTRANSHOST=1
F exePath : PATH=C:\usr\sap\J23\J00\exe\sapjvm_6\bin;C:\usr\sap\J23\J00\exe;C:\Program Files (x86)\Parallels\Parallels Tools\Applications;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\usr\sap\J23\SYS\exe\uc\NTAMD64;C:\sapdb\clients\J23\bin;C:\sapdb\clients\J23\pgm;C:\sapdb\programs\bin
F libPath : PATH=C:\usr\sap\J23\J00\exe\sapjvm_6\jre\bin\server;C:\usr\sap\J23\J00\exe\sapjvm_6\jre\bin;C:\usr\sap\J23\J00\j2ee\os_libs;C:\usr\sap\J23\J00\exe\sapjvm_6\bin;C:\usr\sap\J23\J00\exe;C:\Program Files (x86)\Parallels\Parallels Tools\Applications;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\usr\sap\J23\SYS\exe\uc\NTAMD64;C:\sapdb\clients\J23\bin;C:\sapdb\clients\J23\pgm;C:\sapdb\programs\bin
F stdout : C:\usr\sap\J23\J00\work\std_server0.out
F stderr : C:\usr\sap\J23\J00\work\std_server0.out
F console : no
F debugger: no
F nice : no
F ********************************************************************************
F Process server0 started with pid 2632
F ********************************************************************************
F [Thr 3152] *** LOG => Process server0 started (pid 2632).
F [Thr 3152] *** LOG => Result for NODE_START 2 {}: 0 ok, 00000000.
F [Thr 3152] *** LOG => SAP Start Service (pid 1848) disconnected.
F
F [Thr 3152] Tue Dec 24 11:30:32 2013
F [Thr 3152] *** LOG => Process server0 stopping (pid 2632).
F
F [Thr 3660] Tue Dec 24 11:30:32 2013
F [Thr 3660] *** LOG => Signal 13 SIGCHLD.
F [Thr 3152] *** LOG => Process server0 stopped (pid 2632).
F [Thr 3152] *** WARNING => Node server0 failed: result 2, exit code -1501. [sfxxnode.hpp 1024]
F ********************************************************************************
F Starting process: C:\usr\sap\J23\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=ID3963950&exitcode=-1501
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\J23\J00\exe;C:\Program Files (x86)\Parallels\Parallels Tools\Applications;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\usr\sap\J23\SYS\exe\uc\NTAMD64;C:\sapdb\clients\J23\bin;C:\sapdb\clients\J23\pgm;C:\sapdb\programs\bin
F libPath : PATH=C:\usr\sap\J23\J00\exe;C:\Program Files (x86)\Parallels\Parallels Tools\Applications;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\usr\sap\J23\SYS\exe\uc\NTAMD64;C:\sapdb\clients\J23\bin;C:\sapdb\clients\J23\pgm;C:\sapdb\programs\bin
F stdout : C:\usr\sap\J23\J00\work\std_snapshot.out
F stderr : C:\usr\sap\J23\J00\work\std_snapshot.out
F console : no
F debugger: no
F nice : no
F ********************************************************************************
F Process snapshot started with pid 2512
F ********************************************************************************
F [Thr 3152] *** LOG => Process snapshot started (pid 2512).
F [Thr 3152] *** LOG => Process snapshot running (pid 2512).
F [Thr 3152] *** LOG => SAP Start Service (pid 1848) connected.
F [Thr 3152] *** LOG => Command THREAD_GET_CALLSTACK 2 (5) from SAP Start Service (pid 1848).
F [Thr 3152] *** WARNING => SfCJavaProcHandler(server0)::onProcCmd: state 1070 STOPPED cannot handle [mType=PROC_CMD, mReply=TRUE, pca=[cmd=GET_CALLSTACK, procId=2, arg=5], mpEvent=[mType=NODE_CMD, mReply=TRUE, nca=[cmd=GET_CALLSTACK, nodeId=2]]]! [sfxxproc.hpp 2031]
F [Thr 3152] *** WARNING => SfCEventDispatcher::processQueue: rc 3 (invalid function argument) from SfCJavaProcHandler(server0)([mType=PROC_CMD, mReply=TRUE, pca=[cmd=GET_CALLSTACK, procId=2, arg=5], mpEvent=[mType=NODE_CMD, mReply=TRUE, nca=[cmd=GET_CALLSTACK, nodeId=2]]]) [sfxxevt.hpp 3156]
F [Thr 3152] *** WARNING => SfCNodeManager(server0)::onReply: command 2010 GET_CALLSTACK returned 3 invalid function argument. [sfxxnode.hpp 1519]
F [Thr 3152] *** LOG => Result for THREAD_GET_CALLSTACK 5 {}: 3 invalid function argument, 00000000.
F [Thr 3152] *** LOG => SAP Start Service (pid 1848) disconnected.
F
F [Thr 4072] Tue Dec 24 11:30:37 2013
F [Thr 4072] *** LOG => Signal 13 SIGCHLD.
F
F [Thr 3152] Tue Dec 24 11:30:37 2013
F [Thr 3152] *** LOG => Process snapshot stopped (pid 2512).
F [Thr 3152] *** LOG => Removing enque locks for ID 3963950.
↧
Re: Netweaver 7.4 Install Stop Error - SCS01 will not start (err code: FCO-00011)
Hi,
Can you please post the below logs.
C:\usr\sap\J23\J00\work\std_server0.out
C:\usr\sap\J23\J00\work\jvm_server0.out
Can you also check the below note.
1922620 - Startup fails with exit code 131074
Thanks
Rishi Abrol
↧
Re: BW system connect to 3rd party database like MSSQL
Actually, SAP has put together a KBA article for the systems based on NW 7.10 and above.
Check the attachment for step by step instructions.
↧
↧
Re: App server for portal user
Is your issue is going to single SAP ECC application server or just portal itself.
If its portal, you can install a web dispatcher or use message server http port(usually 81XX) and ask the users to use the webdispatcher URL to login to the portal.
The belo example is for using message server http port as load balancer between portal CI and app servers.
http://<hostname of CI>:<message server http port>/irj
↧
Re: Upgrade NW Components Separate to ERP Components
Hello,
I am not sure what is your requirement to not to upgrade ERP components on equivalent stack level of Netweaver systems. But this should be possible.
You should define your system as SAP Netweaver system in SMSY and it should not give ERP components while you will create transaction in MOPZ. But even if it select ERP components then you can unselect ERP components. As a result ERP patches will not be present in stack file.
But in order to keep ERP patches on same level, you need to provide vendor key during upgrade. For Vendor keys, you can get in touch with SAP Support.
Thanks,
Sunny
↧
Re: App server for portal user
↧
Re: Upgrade NW Components Separate to ERP Components
↧
↧
Re: Netweaver 7.4 Install Stop Error - SCS01 will not start (err code: FCO-00011)
Dear Jon,
As i replied earlier did you try kernel upgrade to latest and try to start sap again,
Rableen
↧
Sap priveleges SPRO
Hello,
I'm trying to give read only access to SPRO but have no idea how to do it... I tried to use some topics here. For example:
Setting SPRO authorization only in disply mode | SCN
and various... But it does not work for me.
In my case i have user with role sap_all (i guess this permissions allow user alot to do).
And i created a role as it was discribed in topics above.
So... If user is a member of two roles. In first role SPRO is allowed to edit, in second role SPRO alowed only in readonly mode. Which permissions will work? i thought "deny" always has a priority.. but it seems like in SAP it work another way...
Thanks in advance for any advices
↧
Re: BW system connect to 3rd party database like MSSQL
Hello all,
Thanks a lot for your valuable replies, I have followed the guide to do the configurations in NWA and also setup a RFC connection in ABAP side, the test connection of RFC works well, however we met problem in data retrieval.
When I create a new source system in RSA1, I can not view the database/tables within the external MSSQL. could you kindly guide me how to setup in BW side? Is there something wrong?
Thanks!
↧
Re: Negative stock
To avoid any side effects in the BAPI call, kindly apply the calling pattern of SAP Note 369518 mentioned at the solution section to your custom call of the BAPI.
This will ensure that each BAPI call will get anew LUW and such the issue should be solved.
Regards.
M.Ozgur Unal
↧
↧
Re: SAP NetWeaver 7.0 SR3 Developer Workplace Installation on Windows 7 64-bit
Hi Julian,
I assume we are talking about NWDS 70X, because higher NWDS releases are fully supported on win7.
Please note that there is a difference between something is working and whether we can provide support for it.
See the official statement on this in the note:
which says:
7.00:
There are successfull installations of NWDS 7.0x running inside and outside of SAP.
Please make sure that the NWDS is running on a supported and correctly configured JDK.
Please acknowledge that while you may successfully install and run NWDS 7.0x on Windows 7 this still is not a supported OS! Running NWDS 7.0x on Windows 7 is at your own risk.
Best Regards,
Ervin
↧
Re: Netweaver 7.4: Still NWDS or Eclipse?
2018:
Not sure why people think 2018 is the year WDJ support will die. The actual PAM for NW 7.31 shows as: End of Mainstream Maintenance: 12/31/2020
As WDJ is shipped with NW 7.31, that's actually the EOL date for WDJ. Btw, that is also the same EOL for NW 7.4. This, for sure, won't avaid getting the usual answers from SAP: we advise you to use WDA or SAPUI5.
WDJ and EJB
WDJ needs the class/jar files in the classpath. There is no need to have your EJBs in the form of a DC. You just have to make them available to the WDJ project (but then again, I stopped using the NWDS compile/deploy wizards a few years ago and use Jenkins for this).
WDJ tooling
Yes, this would be nice. This was raised several times before, but as WDJ entered kiss-of-death-mode I guess there are simply no resources (aka humans) left to do this. If SAP did this years ago, we now could have WDJ applications running on HANA Cloud Platform. For sure this would have helped a lot in adopting HCP. Failures done in the past are still hunting us :-)
↧
Re: BW system connect to 3rd party database like MSSQL
Hello
Could you provide the details of the JDBC connection string ?
Are you able to see the database and the tables when you do a test JDBC ?
Regards
RB
↧
Re: Fordware Error Handling Monitor(FEH)
This may help !
Configuring Forward Error Handling - Supplier Relationship Management - SCN Wiki
Regards
Celeste
↧
↧
Re: Netweaver 7.4: Still NWDS or Eclipse?
Hi Tobias,
thanks for your reply.
2018:
The source of this number is SAP's flagship event from 2010 and that people listen to what SAP tells them, no woolgathering. SAP announced on Tech Ed 2010 that WE/J as part of major release 7.3 will be maintained "7 + 2 years". Indeed, in the CDN 201 session, it was 2019
CD201 Web Dynpro Java and SAP NetWeaver Visual Composer - What's New in SAP NetWeaver 7.3?
(ca. 33:30)
but all blogs about this event quoted 2018 (google "2018 web dynpro java") so I guess 2018 was the number mentioned in a keynote at TechEd 2010.
WDJ and EJB:
Of course your remarks are correct for the runtime, but not for the WDJ tools. They force you to use the DC concept from the EJB DC to the EAR DC, at least if you want to use EJB model.
No DC, no EJB model.
To use the EJB model for WDJ, you need an EJB DC with client Public Part and an EAR DC that references this PP in its own PP. The WDJ containing the EJB model references only the PP of the EAR (which is weird architecture since it only references the EJB at compile time) and the application-jee-engine.xml of the WDJ EAR application is generated with a classloading reference to the ear.
If you wanted to build a WDJ that consumes EJB services without the EJB and EAR being DC's, you would have to use plain Java model (which is much less usable than the EJB model), would have to write your own ctx.lookups() and would be stuck finally since you cannot insert the reference to the applicatoin EAR the application-jee-engine.xml of the WD/J: It gets overwritten during the WDJ DC build, only the EARs with PPs referenced by the WDJ DC are generated into the app-engine file. Finally you would have to hack into the WDJ build process.
Any hints for a non EJB model access to EJB services are welcome.
The usual answers from SAP: "We advise you to use WDA or SAPUI5"
For a Java based "heavy transactional" application on SAP NW Java, these "recommandations" are not helpful at all. Even more, this fact is so obvious that even SAP must have noticed it. To cast these "advices" to their customers is somewhat ignorant.
WDJ tooling
I do not think human resources are the only reason. Now that WDJ has reached "maturity" since 2010, SAP could have donated the WDJ framework to the Open Source community like Google did it with GWT. But from a business point of view, this is not interesting for SAP.
Finally to Java EE 6:My late wishlist
SAP, please skip Java EE 6 and go directly to Java EE 7. Do not get out with an outdated Java EE 6 after all these years on Java EE 5. Java EE 7 introduces an API for JSON processing that is useful for REST services and for your UI5.
Please, either implement Java EE 7 in your SAP NetWeaver 7.x or tell us how to run WDJ and BPM on JBoss and how to generate these weird wdrr.xml files inside WDJ EARs.
Thank you.
Regards
Rolf
↧
Re: BW system connect to 3rd party database like MSSQL
Hello Benjamin,
my JDBC settings in NWA are as below:
and in SAPJavaResourceAdapter15, I set programID:UDI_JAVA_P73 according to the guide, the test connection from ABAP side to Java side via RFC was successful, however, in BW system RSA1, it seems I could not add a UD connection, or in other words, nothing could be seen.
10.0.4.62 is the ip the the BW system resides.
Thanks a lot.
↧
Re: BW system connect to 3rd party database like MSSQL
Hello
You should always leave SDK_JDBC as it is and instead copy SDK_JDBC to another name and configure the new one.
Eg: Copy SDK_JDBC to SDK_JDBC_DBNAME
Secondly the URL is not complete.
You need to mention the JDBC port for the MSSQL server in it.
The default port is 1433 for MSSQL database but you may cross check with the SQL database specialist for this server.
The URL should be :
jdbc:sqlserver://10.10.12.31:1433;database=test
You can do a test using this string.
http://FQDN-OF-J2EE-SERVER:5NN00/TestJDBC_Web/TestJDBCPage.jsp
Regards
RB
↧