cancel
Showing results for 
Search instead for 
Did you mean: 

Netweaver 7.4 Install Stop Error - SCS01 will not start (err code: FCO-00011)

Former Member
0 Kudos

Hi All,

I have been installing Netweaver 7.4, using MAX DB, the install runs happily up to the step where it tries to start the SCS01 instance, however it fails after trying to start for 5 minutes.

Looking through the error logs on the log analyser the error I have found is:

An error occurred at step:
ERROR 2013-12-17 14:23:33.545 [sixxcstepexecute.cpp:901]

FCO-00011 The step startSCSInstance with step key NW_CI_Instance -> startSCSInstance was executed with status ERROR

Logfile location: C:\Program Files\sapinst_instdir\NW740\ADA\INSTALL\ADA\STANDALONE\STD\PICP\sapinst.log

ERROR 2013-12-17 14:23:33.545 [sixxcstepexecute.cpp:901]
FCO-00011 The step startSCSInstance with step key NW_Java_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|onehost|0|NW_CI_Instance|ind|ind|ind|ind|ci|0|startSCSInstance was executed with status ERROR ( Last error reported by the step: Instance J21/SCS02 [PARTIAL] did not start after 5:10 minutes. Giving up.).

Logfile location: C:\Program Files\sapinst_instdir\NW740\ADA\INSTALL\ADA\STANDALONE\STD\PICP\sapinst_dev.log



I have tried all the usual things like restarting the install, trying a completely fresh install, starting the instance manually but it will always fail at this point.

Has anyone else encountered this error, or can suggest further logs to inspect?

Many thanks in advance!

Jon



Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

Jon, did you get this to work?  I"m experiencing the exact issue but with MSSQL.   I have tried installing/uninstalling several times but to no avail.  It it stops at the exact spot as reported by you where it tries to restart the instance but fails.     @

Former Member
0 Kudos

I got exactly same issue. Issue was resolved. In my case it was related to wrong path to Oracle Home and tnsnames.ora file.

Former Member
0 Kudos

Dear Jon,

As i replied earlier did you try kernel upgrade to latest and try to start sap again,

Rableen

Former Member
0 Kudos

Hi Rableen,

No I have not been able to upgrade kernel yet, please can you advise on the best approach to do this as it is something I have not done before.

Thank you,

Jon

Former Member
0 Kudos

Dear Jon,

For kernel upgrade please follow the below step,

Step 1: Download kernel file and db file (.SAR files) from service market a) Database Independent Files SAPEXE_<Patch level>-<release date>.SAR b) Database Dependent files SAPEXEDB_<Patch level>-<release date>.SAR

Step 2: Extract the .SAR files, To do this

 Login as <SID>adm user

 Open command prompt and move to the directory where the downloaded files are present.

 Execute the command,

SAPCAR -xvf <filename.SAR> (In Linux CAPITAL) Note: SAPCAR is a program executable located in the KERNEL folder itself. If SAPCAR is not working, then copy the executable from the kernel folder to the location where the .SAR files are located.

Step 3: Stop SAP using MMC.

Step 4: Stop SAP related services (SAPOSCOL), To do this Windows: Start-> run-> services.msc Unix: saposcol –k

Step 5: Take back up of current kernal directory (kernal_old). /usr/sap/SID/SYS/exe/uc/ Or /usr/sap/SID/SYS/exe/run

Step 6: Copy and overite the files inside kernal directory. Linux: cp -R <source file > <destination>

Step 7: Start SAP related services (SAPOSCOL), To do this Windows: Start-> run-> services.msc Unix: saposcol –l

Step 8: Start SAP using MMC.

~~~*~~~

Then after retry for the installation,,

Rableen

Former Member
0 Kudos

Hi,

If the issue still persist ,,,try to upgrade the kernel.

Rableen

Former Member
0 Kudos

Hi,

Because I am on windows I have run a saposcol -d and then the "leave" command instead of the cleanipc command.

And restarted the install but unfortunately still stops at the UME step,

What is the best method to upgrade the kernel?

Thank you,

Jon

Former Member
0 Kudos

Hi,

is the SAP MMC still showing yellow.

can you please share screen shot..

Thanks

RishiA brol

Former Member
0 Kudos

Here we go, previously I have left it in this state for 20 minutes and it will remain in this partial yellow state:

Reagan
Product and Topic Expert
Product and Topic Expert
0 Kudos

Select the AS Java process Table and check which process is not running.

Check the trace file of that process in the work directory.

Regards

RB

Former Member
0 Kudos

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

Former Member
0 Kudos

This is what I can see, but I thought this could be related to the install not fully completing yet?

Former Member
0 Kudos

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 [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 [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 [Thr 3152] Tue Dec 24 10:26:24 2013

F  [Thr 3152] *** LOG => Process deployment stopping (pid 3552).

F [Thr 4084] Tue Dec 24 10:26:25 2013

F  [Thr 4084] *** LOG => Signal 13 SIGCHLD.

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 [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 [Thr 3152] Tue Dec 24 10:26:28 2013

F  [Thr 3152] *** LOG => Process bootstrap stopping (pid 2636).

F [Thr 3728] Tue Dec 24 10:26:29 2013

F  [Thr 3728] *** LOG => Signal 13 SIGCHLD.

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 [Thr 3152] Tue Dec 24 10:26:34 2013

F  [Thr 3152] *** LOG => Process server0 stopping (pid 1820).

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 [Thr 3224] Tue Dec 24 10:26:39 2013

F  [Thr 3224] *** LOG => Signal 13 SIGCHLD.

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 [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 [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 [Thr 3152] Tue Dec 24 11:30:32 2013

F  [Thr 3152] *** LOG => Process server0 stopping (pid 2632).

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 [Thr 4072] Tue Dec 24 11:30:37 2013

F  [Thr 4072] *** LOG => Signal 13 SIGCHLD.

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.

Former Member
0 Kudos

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

Former Member
0 Kudos

Hi Rishi,

I have followed the steps in the note with increasing the jstart property however this has made now difference when starting the server back up again.

The std server log is below, the jvm log is empty for some reason? :

--------------------------------------------------------------------------------

stdout/stderr redirection

--------------------------------------------------------------------------------

node name   : server0

host name   : NWCE74PI

system name : J23

system nr.  : 00

started at  : Tue Dec 24 10:26:29 2013

JVMX version - Mar 14 2013 00:37:43 - 61_REL - optU - windows amd64 - 6 - bas2:191583 (mixed mode)

The active factory is : com.sap.engine.boot.loader.StandardClassLoaderFactory

Class loading cache information loaded from package index [C:\usr\sap\J23\J00\j2ee\cluster\bin\index.list]

Reading manager properties from [kernelProperties.bin] file

   Checked the data for [0] ms

   Objects read for [47] ms

   Substituted the values for [47] ms

Finished reading kernel objects for [94] ms

Startup mode [NORMAL] and action [NONE] read

AS Java version [7.40.3710.248546.20130404102423 SP 07] is starting server process [ID3963950] on host [NWCE74PI] ...

Loading [LogManager]... [47] ms

Loading [PoolManager]... [0] ms

Loading [ApplicationThreadManager]... 0.947: [GC 0.947: [ParNew: 1048320K->3689K(1223040K), 0.0141482 secs] 1048326K->3696K(4019584K), 0.0142079 secs] [Times: user=0.06 sys=0.00, real=0.01 secs]

[78] ms

Loading [ThreadManager]... [0] ms

Loading [ClassLoaderManager]... [15] ms

Loading [ClusterManager]...

FATAL: Server process failed to start; manager [ClusterManager] could not be started

Heap

par new generation   reserved 1397760K, committed 1397760K, used 451490K [0x0000000180010000, 0x00000001d5510000, 0x00000001d5510000)

  eden space 1048320K,  42% used [0x0000000180010000, 0x000000019b55e2b8, 0x00000001bffd0000)

  from space 174720K,   2% used [0x00000001caa70000, 0x00000001cae0a708, 0x00000001d5510000)

  to   space 174720K,   0% used [0x00000001bffd0000, 0x00000001bffd0000, 0x00000001caa70000)

concurrent mark-sweep generation reserved 2796544K, committed 2796544K, used 6K [0x00000001d5510000, 0x0000000280010000, 0x0000000280010000)

concurrent-mark-sweep perm gen reserved 1048576K, committed 1048576K, used 14473K [0x0000000280010000, 0x00000002c0010000, 0x00000002c0010000)

--------------------------------------------------------------------------------

stdout/stderr redirection

--------------------------------------------------------------------------------

node name   : server0

host name   : NWCE74PI

system name : J23

system nr.  : 00

started at  : Tue Dec 24 11:30:28 2013

JVMX version - Mar 14 2013 00:37:43 - 61_REL - optU - windows amd64 - 6 - bas2:191583 (mixed mode)

The active factory is : com.sap.engine.boot.loader.StandardClassLoaderFactory

Class loading cache information loaded from package index [C:\usr\sap\J23\J00\j2ee\cluster\bin\index.list]

Reading manager properties from [kernelProperties.bin] file

   Checked the data for [16] ms

   Objects read for [47] ms

   Substituted the values for [47] ms

Finished reading kernel objects for [94] ms

Startup mode [NORMAL] and action [NONE] read

AS Java version [7.40.3710.248546.20130404102423 SP 07] is starting server process [ID3963950] on host [NWCE74PI] ...

Loading [LogManager]... [31] ms

Loading [PoolManager]... [0] ms

Loading [ApplicationThreadManager]... 0.771: [GC 0.771: [ParNew: 1048320K->3480K(1223040K), 0.0130873 secs] 1048326K->3487K(4019584K), 0.0131432 secs] [Times: user=0.06 sys=0.00, real=0.01 secs]

[62] ms

Loading [ThreadManager]... [16] ms

Loading [ClassLoaderManager]... [15] ms

Loading [ClusterManager]...

FATAL: Server process failed to start; manager [ClusterManager] could not be started

Heap

par new generation   reserved 1397760K, committed 1397760K, used 495012K [0x0000000180010000, 0x00000001d5510000, 0x00000001d5510000)

  eden space 1048320K,  46% used [0x0000000180010000, 0x000000019e0131a0, 0x00000001bffd0000)

  from space 174720K,   1% used [0x00000001caa70000, 0x00000001cadd6190, 0x00000001d5510000)

  to   space 174720K,   0% used [0x00000001bffd0000, 0x00000001bffd0000, 0x00000001caa70000)

concurrent mark-sweep generation reserved 2796544K, committed 2796544K, used 6K [0x00000001d5510000, 0x0000000280010000, 0x0000000280010000)

concurrent-mark-sweep perm gen reserved 1048576K, committed 1048576K, used 14473K [0x0000000280010000, 0x00000002c0010000, 0x00000002c0010000)

--------------------------------------------------------------------------------

stdout/stderr redirection

--------------------------------------------------------------------------------

node name   : server0

host name   : NWCE74PI

system name : J23

system nr.  : 00

started at  : Tue Dec 24 11:46:53 2013

JVMX version - Mar 14 2013 00:37:43 - 61_REL - optU - windows amd64 - 6 - bas2:191583 (mixed mode)

The active factory is : com.sap.engine.boot.loader.StandardClassLoaderFactory

Class loading cache information loaded from package index [C:\usr\sap\J23\J00\j2ee\cluster\bin\index.list]

Reading manager properties from [kernelProperties.bin] file

   Checked the data for [0] ms

   Objects read for [47] ms

   Substituted the values for [31] ms

Finished reading kernel objects for [78] ms

Startup mode [NORMAL] and action [NONE] read

AS Java version [7.40.3710.248546.20130404102423 SP 07] is starting server process [ID3963950] on host [NWCE74PI] ...

Loading [LogManager]... [47] ms

Loading [PoolManager]... [0] ms

Loading [ApplicationThreadManager]... 0.744: [GC 0.744: [ParNew: 1048320K->3728K(1223040K), 0.0129811 secs] 1048326K->3734K(4019584K), 0.0130714 secs] [Times: user=0.06 sys=0.00, real=0.02 secs]

[47] ms

Loading [ThreadManager]... [16] ms

Loading [ClassLoaderManager]... [15] ms

Loading [ClusterManager]...

FATAL: Server process failed to start; manager [ClusterManager] could not be started

Heap

par new generation   reserved 1397760K, committed 1397760K, used 460430K [0x0000000180010000, 0x00000001d5510000, 0x00000001d5510000)

  eden space 1048320K,  43% used [0x0000000180010000, 0x000000019be0f848, 0x00000001bffd0000)

  from space 174720K,   2% used [0x00000001caa70000, 0x00000001cae14168, 0x00000001d5510000)

  to   space 174720K,   0% used [0x00000001bffd0000, 0x00000001bffd0000, 0x00000001caa70000)

concurrent mark-sweep generation reserved 2796544K, committed 2796544K, used 6K [0x00000001d5510000, 0x0000000280010000, 0x0000000280010000)

concurrent-mark-sweep perm gen reserved 1048576K, committed 1048576K, used 14473K [0x0000000280010000, 0x00000002c0010000, 0x00000002c0010000)

Former Member
0 Kudos

Hi,

Can you please try to check the defaultTrace and see if you get more info.

Can be that the port 5XX20 was occupied, so manage server is not able to connect this port.

Thanks

Rishi Abrol

Former Member
0 Kudos

Please check defaultTrace or post it here.

Former Member
0 Kudos

Hi,

Please post the logs in the work directory. can you also past the sapinst_dev.log log as this might suggest which file to check in work directory.

What happens when you run the below command.

sapcontrol -nr <shadow SCS instance number> -function Start

Thanks

Rishi abrol

Former Member
0 Kudos

Thank you for the replies,

Checking the Database service it  reports MaxDb: J21 (starting) and never actually seems to start, if I manually start the service it will eventually timeout.

I've attached a link to the log file because it is quite large to paste here. https://db.tt/1CdObYqv

I am new to executing commands that you have suggested, which directory should I be running the commands from?

Thank you!

Former Member
0 Kudos

Hi,

You can run this command with SIDADM.

But it looks like that gateway service is not running.

Execution of the command "C:\usr\sap\J21\SCS02\exe\sapcontrol.exe -prot PIPE -nr 02 -function GetProcessList" finished with return code 0. Output:

17.12.2013 14:23:13

GetProcessList

OK

name, description, dispstatus, textstatus, starttime, elapsedtime, pid

msg_server.EXE, MessageServer, GREEN, Running, 2013 12 17 14:18:22, 0:04:51, 3600

enserver.EXE, EnqueueServer, GREEN, Running, 2013 12 17 14:18:22, 0:04:51, 3352

gwrd.EXE, Gateway, GRAY, Stopped, 2013 12 17 14:18:23, 0:00:00, -1

Thanks

Rishi Abrol

Reagan
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hello

Have you run r3trans -d ?

Is the database up and running.

Install MacDB database manager on the system and connect the database to it.

You can do MaxDB database administration using that.

Make sure all the MaxDB services are running as well.

If the database is not started then you may start it.

Check these errors as well.


Account user="NWCE74PI\SAP_LocalAdmin" does not exist.

Failed action:  with parameters

Error number 207 error type SPECIFIC_CODE

TRACE      2013-12-17 14:11:47.242

State of service 'XServer' on host '' is SERVICE_STOPPED

TRACE      2013-12-17 14:11:47.242

State of service 'XServer' on host '' is SERVICE_STOPPED

17.12.2013 14:23:23


GetProcessList

OK

name, description, dispstatus, textstatus, starttime, elapsedtime, pid

msg_server.EXE, MessageServer, GREEN, Running, 2013 12 17 14:18:22, 0:05:01, 3600

enserver.EXE, EnqueueServer, GREEN, Running, 2013 12 17 14:18:22, 0:05:01, 3352

gwrd.EXE, Gateway, GRAY, Stopped, 2013 12 17 14:18:23, 0:00:00, -1

It looks like all the processes are running except the Gateway.

Check the dev_rd trace file.

Regards

RB

Former Member
0 Kudos

Hi,

Thank you, I've been working through the recommendations:

1) When I run sapcontrol, the following is displayed.

c:\usr\sap\J21\SCS02\exe>sapcontrol -nr 01 -function Start

20.12.2013 10:51:14

Start

FAIL: HTTP error, HTTP/1.1 401 Unauthorized

Which does not look correct! Is there a user account being used here that I need to check?

2) When I run the r3Tranc -d I get the following:

This is r3trans version 6.24 (release 740 - 19.03.13 - 20:13:03 ).

unicode enabled version

sizeof(Selection_t) = 272

2EETW169 no connect possible: "DBMS = ADABAS D                         --- DBNAM

E = ''"

r3trans finished (0012).

3) Looking at the dev_rd trace file, I can see there is an error finding reginfo.dat:

---------------------------------------------------

trc file: "dev_rd", trc level: 1, release: "740"

---------------------------------------------------

Fri Dec 20 10:35:20 2013

***LOG S00=> GwInitReader, gateway started ( 3364) [gwxxrd.c     1763]

systemid   562 (PC with Windows NT)

relno      7400

patchlevel 0

patchno    7

intno      20020600

make       multithreaded, Unicode, 64 bit, optimized

pid        3364

Fri Dec 20 10:35:20 2013

gateway (version=740.2013.02.14)

gw/reg_no_conn_info = 1

gw/local_addr : 0.0.0.0

* SWITCH TRC-RESOLUTION from 1 TO 1

gw/logging : ACTION=Ss LOGFILE=gw_log-%y-%m-%d SWITCHTF=day MAXSIZEKB=100

gw/sim_mode : set to 0

***LOG S1I=> GwSetSimMode, simulation mode deactivated () [gwxxprf.c    4354]

switch off alert monitoring

Bind service 3302 (socket) to port 3302

GwIRegInitRegInfo: reg_info file C:\usr\sap\J21\SCS02\data\reginfo.DAT not found

*** ERROR => GwInitHostAdrs: GwHostToAddr failed [gwxxaddr.c   205]

***LOG S10=> GwInitReader, GwInitHostAdrs () [gwxxrd.c     2027]

I'm not to sure if the gateway service is connected to my hostfile? however checking this I only have three entries:

127.0.0.1       localhost

0.0.0.0         .psf

0.0.0.0         psf

Is there anything else I can try to resolve the gateway service?

Thank you again!

Jon

Former Member
0 Kudos

Hi,

Can you please let me know that do you have DNS setup or are using local host.

Can you ping the hostname from the server and see if that reaches correctly? Also, is it resolving the correct IP when you ping?


Can you add entry of the host name and the ip in the hostfile.


Thanks

Rishi Abrol

Reagan
Product and Topic Expert
Product and Topic Expert
0 Kudos

After executing the R3trans -d there will be an output file called trans.log created in the directory where you have run the command. You need to check that file to know why the return code is not 0000.

The gateway service with the port number should be mentioned in the services file.

Regards

RB

Former Member
0 Kudos

Hi All,

I have now been able to progress further the host file recommendation moved the install on further,

however the install now stops at the "Configuring UME" step, the error is:

ERROR 2013-12-23 15:44:35.117 [sixxcstepexecute.cpp:901]
FCO-00011 The step installTempLicense with step key |NW_Java_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|onehost|0|NW_CI_Instance|ind|ind|ind|ind|ci|0|NW_CI_Instance_Configure_Java|ind|ind|ind|ind|javaconfig|0|installTempLicense was executed with status ERROR ( Last error reported by the step: Error when installing temporary license. DIAGNOSIS: External systems are temporarily unavailable. SOLUTION: Ensure that the SCS instance (SAP Messaging Service) and the Java database are up and running.).

Looking in SAPMMC the system has partially started up, the message server is up, the enserver is up, and the gateway is up. Jstart is in a yellow state saying some processes running.

Any ideas what could be causing this?

Thank you,

Jon

Former Member
0 Kudos

Hi,

Can you try to stop the system and clean all the ipc and restart it back and then run then retry the installation.

Please don't forget to restart the sapstartsrv if still doesn't works please check if kernel upgrade helps.

Thanks

Rishi Abrol