Shadow instance couldn't be started in phase MAIN_SHDRUN/START_SHDI_FIRST

[Former Member]

Hi,

When I patch solution manager 7.1 SP04 to SP12. I meet this kind of issue as below.

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

      Severe error(s) occurred in phase MAIN_SHDRUN/START_SHDI_FIRST!

Last error code set: Shadow instance couldn't be started, check 'STARTSFI.LOG' and 'DEVTRACE.LOG': RFC login to system KS1 ashost IDES-SM nr 03 gwhost IDES-SM gwservice sapgw03 failed with code 1 key RFC_COMMUNICATION_FAILURE: <br/> LOCATION CPIC (TCP/IP) on local host with Unicode<br/> ERROR partner '192.168.11.192:3303' not reached<br/> TIME Wed Jan 07 14:21:54 2015<br/> RELEASE 721<br/> COMPONENT NI (network interface)<br/> VERSION 40<br/> RC -10<br/> MODULE nixxi.cpp<br/> LINE 3283<br/> DETAIL NiPConnect2: 192.168.11.192:3303<br/> SYSTEM CALL connect<br/> ERRNO 10061<br/> ERRNO TEXT WSAECONNREFUSED: Connection refused<br/> COUNTER 47<br/>

      To analyze errors during the start of the shadow instance, check the 'STARTSFI.LOG' and 'DEVTRACE.LOG' files in directory 'C:\usr\sap\KS1\SUM\abap\log'.

Repeat the phase until the shadow instance is started and you can log on to instance number '03'.

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

After search from sap scn, I try to restart shadow instance but it can't get started successfully.

And also, I confuse why error info shows solution manager system instance 03 and sapgw03 ? I can't find system instance 03 in sapmmc. Any idea?

1. FROM STARTSFI.LOG#

3 ETQ123 20150107141428: PID 9284 exited with status 0 (time 0.000 real)

1 ETQ206 Executing pre-phase DB specific actions.

1 ETQ200 Executing actual phase 'MAIN_SHDRUN/START_SHDI_FIRST'.

1 ETQ399 Phase arguments:

2 ETQ399 Arg[0] = 'START_SERVICE'

2 ETQ399 Arg[1] = 'DEVTRACE.LOG'

4 ETQ380 computing toolpath for request "TP_ALWAYS_NEW"

4 ETQ381 request "TP_ALWAYS_NEW" means "always tp from DIR_PUT/exe, for phase KX_SWITCH"

4 ETQ382 translates to group "R3UP_TOOL_GROUP_NEW"

4 ETQ399 Requirement for tp maps to 'exe'

4 ETQ383 translates to path "C:\usr\sap\KS1\SUM\abap\exe"

2 ETQ399 Distribute 3 parallel processes to 2 tp and 2 R3trans.

2 ETQ399 Starting shadow instance

4 ETQ399 Set database connect to shadow.

4 ETQ399 Set environment for shadow connect:

4 ETQ399 Set RFC variables for shadow connect:

4 ETQ399 System-nr = '03', GwService = 'sapgw03' Client = '000'

4 ETQ380 computing toolpath for request "TP_SHADOW_CONNECT"

4 ETQ381 request "TP_SHADOW_CONNECT" means "tp needs to connect to shadow system"

4 ETQ382 translates to group "R3UP_TOOL_GROUP_NEW"

4 ETQ399 Requirement for tp maps to 'exe'

4 ETQ383 translates to path "C:\usr\sap\KS1\SUM\abap\exe"

4 ETQ399 Set tool parameters for shadow connect with TPPARAM 'SHADOW.TPP'.

4 ETQ399 Set RFC variables for shadow connect:

4 ETQ399 System-nr = '03', GwService = 'sapgw03' Client = '000'

1 ETQ359 RFC Login to: System="KS1", AsHost="IDES-SM" Nr="03", GwHost="IDES-SM", GwService="sapgw03"

2EETQ231 RFC Login failed

4 ETQ399 Set RFC variables for shadow connect:

4 ETQ399 System-nr = '03', GwService = 'sapgw03' Client = '000'

1 ETQ359 RFC Login to: System="KS1", AsHost="IDES-SM" Nr="03", GwHost="IDES-SM", GwService="sapgw03"

2EETQ231 RFC Login failed

1 ETQ399 SYSTEM MANAGER: SAPControl action START failed for instance 03 ('Error: System is still down!').

1 ETQ399 SYSTEM MANAGER: CheckSystemStatus.

1 ETQ399 SAPCONTROL MANAGER: getProcessList with host: IDES-SM and instance: 03

3 ETQ120 20150107142214: PID 9376 execute 'C:\usr\sap\KS1\SUM\abap\exe\sapcontrol.exe -format script -prot PIPE -host IDES-SM -nr 03 -function GetProcessList', output written to 'C:\usr\sap\KS1\SUM\abap\log\SAPup.ECO'.

3 ETQ123 20150107142215: PID 9376 exited with status 0 (time 0.000 real)

1EETQ399 SYSTEM MANAGER: START of mandatory instance 03 on server IDES-SM has failed

2EETQ399 Starting shadow instance failed

1EETQ399 Last error code set is: Shadow instance couldn't be started, check 'STARTSFI.LOG' and 'DEVTRACE.LOG': RFC login to system KS1 ashost IDES-SM nr 03 gwhost IDES-SM gwservice sapgw03 failed with code 1 key RFC_COMMUNICATION_FAILURE:

LOCATION    CPIC (TCP/IP) on local host with Unicode

ERROR       partner '192.168.11.192:3303' not reached

TIME        Wed Jan 07 14:21:54 2015

RELEASE     721

COMPONENT   NI (network interface)

VERSION     40

RC          -10

MODULE      nixxi.cpp

LINE        3283

DETAIL      NiPConnect2: 192.168.11.192:3303

SYSTEM CALL connect

ERRNO       10061

ERRNO TEXT  WSAECONNREFUSED: Connection refused

COUNTER     47

1EETQ204 Upgrade phase "START_SHDI_FIRST" aborted with severe errors ("20150107142215")

2. FROM　SAPup.ECO#

EXECUTING C:\usr\sap\KS1\SUM\abap\exe\sapcontrol.exe -format script -prot PIPE -host IDES-SM -nr 03 -function GetProcessList

07.01.2015 15:10:15

GetProcessList

OK

0 name: msg_server.EXE

0 description: MessageServer

0 dispstatus: GREEN

0 textstatus: Running

0 starttime: 2015 01 07 15:04:59

0 elapsedtime: 0:05:16

0 pid: 8900

1 name: enserver.EXE

1 description: EnqueueServer

1 dispstatus: GREEN

1 textstatus: Running

1 starttime: 2015 01 07 15:04:59

1 elapsedtime: 0:05:16

1 pid: 8656

2 name: disp+work.EXE

2 description: Dispatcher

2 dispstatus: GRAY

2 textstatus: Stopped

2 starttime: 2015 01 07 15:04:59

2 elapsedtime: 0:01:04

2 pid: -1

3. FROM DEVTRACE.LOG#

Wed Jan 07 14:17:21 2015

*** ERROR => DpHdlDeadWp: W0 (pid 8180) died (severity=0, status=0) [dpxxwp.c     1740]

*** ERROR => DpHdlDeadWp: W1 (pid 9384) died (severity=0, status=0) [dpxxwp.c     1740]

*** ERROR => DpHdlDeadWp: W2 (pid 5540) died (severity=0, status=0) [dpxxwp.c     1740]

*** ERROR => DpHdlDeadWp: W3 (pid 10016) died (severity=0, status=0) [dpxxwp.c     1740]

*** ERROR => DpHdlDeadWp: W4 (pid 1380) died (severity=0, status=0) [dpxxwp.c     1740]

*** ERROR => DpHdlDeadWp: W5 (pid 9064) died (severity=0, status=0) [dpxxwp.c     1740]

*** ERROR => DpHdlDeadWp: W6 (pid 1844) died (severity=0, status=0) [dpxxwp.c     1740]

*** ERROR => DpHdlDeadWp: W7 (pid 9944) died (severity=0, status=0) [dpxxwp.c     1740]

*** ERROR => DpHdlDeadWp: W8 (pid 9348) died (severity=0, status=0) [dpxxwp.c     1740]

*** ERROR => DpHdlDeadWp: W9 (pid 5504) died (severity=0, status=0) [dpxxwp.c     1740]

*** ERROR => DpHdlDeadWp: W10 (pid 5208) died (severity=0, status=0) [dpxxwp.c     1740]

*** DP_FATAL_ERROR => DpWPCheck: no more work processes

*** DISPATCHER EMERGENCY SHUTDOWN ***

C Wed Jan 07 14:16:46 2015

C  Driver: sqlncli10.dll Driver release: 10.50.2769

C  GetDbRelease: 10.50.2769.00

C  GetDbRelease: Got DB release numbers (10,50,2769,0)

C  comm. rd. spid 130

C  unc. rd. spid 136

B  Connection 0 opened (DBSL handle 0)

M  ThInit: db_connect o.k.

M  ICT: exclude compression: *.zip,*.rar,*.arj,*.z,*.gz,*.tar,*.lzh,*.cab,*.hqx,*.ace,*.jar,*.ear,*.war,*.jpg,*.pdf,*.gzip,*.uue,*.bz2,*.iso,*.sda,*.sar,*.gif,*.png,*.swc,*.swf

M  rdisp/thsend_order : -1 -> 1

M  rdisp/system_user_handshake : -1 -> 0

I  MtxInit: 0 0 0

M  SHM_PRES_BUF (addr: 0000000014D40050, size: 4400000)

I  *** ERROR => [CreateOsShm] CreateFileMapping(9,262144 KB) failed with Err=1455

              ERROR_COMMITMENT_LIMIT: The paging file is too small for this operation to complete. [shmnt.c      2263]

I  *** ERROR => ShmCreate: Create (9,268435456,3) failed [shmnt.c      535]

M  *** ERROR => ThShMCreate: ShmCreate SHM_ROLL_AREA_KEY failed [thxxhead.c   2821]

M  *** ERROR => ThIPCInit: ThShMCreate [thxxhead.c   2212]

M  ***LOG R19=> ThInit, ThIPCInit ( TSKH-IPC-000001) [thxxhead.c   1607]

M  in_ThErrHandle: 1

M  *** ERROR => ThInit: ThIPCInit (step 1, th_errno 17, action 3, level 1) [thxxhead.c   11535]

M 

M  Info for wp 0

[shriramcse · Accepted solution]

Hi Eric,

Increase the Swap space in the server try to make double of the current value. If didn't worked go for a reboot of the server.

One more thing gw03 you asked its for shadow instance ,since it didn't has enough memory to start its not getting listed in MMC.

Regards,

Sriram

[former_member57686]

1.Find the default profile of shadow system from following path:

C:\usr\sap\(SYSID)\SUM\abap\system\SLM\SYS\profile

2. Set initial memory size as below:

em/initial_size_MB=2048

3.Restart shadow system

[Former Member]

ERROR_COMMITMENT_LIMIT: The paging file is too small for this operation to complete.

Increase the page file size and restart the upgrade.

Follow the below links on how to set and how much to set the page file.

1518419 - Page file and virtual memory required by the SAP system

Changing the size of virtual memory - Windows Help

regards,

pavan

[Former Member]

Hi Pavan,

I appreciate your useful answer. Yes, I increase virtual memory and restart the upgrade.

It pass this phrase and go ahead. Both of instance 03 and sapgw03 are working well right now.

Thanks,

Eric

[Reagan]

I  *** ERROR => [CreateOsShm] CreateFileMapping(9,262144 KB) failed with Err=1455
              ERROR_COMMITMENT_LIMIT: The paging file is too small for this operation to complete. [shmnt.c      2263]
I  *** ERROR => ShmCreate: Create (9,268435456,3) failed [shmnt.c      535]

There is an SAP KBA released for this issue.

1997262 - The shadow instance won't start up. System dev_w* trace files highlight error message 1455...

First restart the server and start the primary and shadow instance and see if that helps.

If not follow the above SAP KBA.

You should also review the work process trace files of the shadow instance

Cheers

RB

[Former Member]

Hi Sriram,

Thanks, I increase swap space and restart. It pass this phrase and go ahead.

Eric