Severe error(s) occurred in phase MAIN_SHDRUN/START_SHDI_FIRST! Last error code set: Shadow instance couldn't be started, during stack apply via SUM???

[farkathulla_cikkanther]

Hello Friends,

  We are facing below error during applying sps stack 31 in Solution manager 7.01.

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': Process F:\usr\sap\trans\SUM\abap\exe/sapcontrol.exe exited with 2, see 'F:\usr\sap\trans\SUM\abap\log\SAPup.ECO'

In DEVTRACE.LOG i can see some error like below.

Wed Jul 23 14:16:35 2014

*** WARNING => DpNetCheck: NiAddrToHost(1.0.0.0) took 5 seconds

***LOG GZZ=> 1 possible network problems detected - check tracefile and adjust the DNS settings [dpxxtool2.c  6484]

MtxInit: 30000 0 0

DpSysAdmExtInit: ABAP is active

DpSysAdmExtInit: VMC (JAVA VM in WP) is not active

display_tcp_ip:    0

DpIPCInit2: write dp-profile-values into sys_adm_ext

DpIPCInit2: start server >sap2apsrv1_SLM_02                      <

DpShMCreate: sizeof(wp_adm)        29328    (2256)

DpShMCreate: sizeof(tm_adm)        5517056    (27448)

DpShMCreate: sizeof(wp_ca_adm)        64000    (64)

DpShMCreate: sizeof(appc_ca_adm)    64000    (64)

DpCommTableSize: max/headSize/ftSize/tableSize=500/16/1384064/1384080

DpShMCreate: sizeof(comm_adm)        1384080    (2744)

DpSlockTableSize: max/headSize/ftSize/fiSize/tableSize=0/0/0/0/0

DpShMCreate: sizeof(slock_adm)        0    (296)

DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0

DpShMCreate: sizeof(file_adm)        0    (80)

DpShMCreate: sizeof(vmc_adm)        0    (2160)

DpShMCreate: sizeof(wall_adm)        (41664/42896/64/192)

DpShMCreate: sizeof(gw_adm)    48

DpShMCreate: sizeof(j2ee_adm)    3952

DpShMCreate: SHM_DP_ADM_KEY        (addr: 0000000003330050, size: 7161328)

DpShMCreate: allocated sys_adm at 0000000003330060

DpShMCreate: allocated wp_adm_list at 00000000033330D0

DpShMCreate: allocated wp_adm at 00000000033332C0

DpShMCreate: allocated tm_adm_list at 000000000333A560

DpShMCreate: allocated tm_adm at 000000000333A5B0

DpShMCreate: allocated wp_ca_adm at 000000000387D4C0

DpShMCreate: allocated appc_ca_adm at 000000000388CED0

DpShMCreate: allocated comm_adm at 000000000389C8E0

DpShMCreate: system runs without slock table

DpShMCreate: system runs without file table

DpShMCreate: allocated vmc_adm_list at 00000000039EE780

DpShMCreate: system runs without vmc_adm

DpShMCreate: allocated gw_adm at 00000000039EE830

DpShMCreate: allocated j2ee_adm at 00000000039EE870

DpShMCreate: allocated ca_info at 00000000039EF7F0

DpShMCreate: allocated wall_adm at 00000000039EF880

DpCommAttachTable: attached comm table (header=000000000389C8E0/ft=000000000389C8F0)

DpSysAdmIntInit: initialize sys_adm

rdisp/test_roll : roll strategy is DP_NORMAL_ROLL

dia token check not active (5 token)

MBUF state OFF

DpCommInitTable: init table for 500 entries

DpRqQInit: keep protect_queue / slots_per_queue 0 / 2001 in sys_adm

rdisp/queue_size_check_value :  -> on,50,30,40,500,50,500,80

EmInit: MmSetImplementation( 2 ).

MM global diagnostic options set: 0

<ES> client 0 initializing ....

<ES> EsILock: use spinlock for locking

<ES> InitFreeList

<ES> block size is 4096 kByte.

<ES> Info: em/initial_size_MB( 4093MB) not multiple of em/blocksize_KB( 4096KB)

<ES> Info: em/initial_size_MB rounded up to 4096MB

Using implementation view

<EsNT> Using memory model view.

<EsNT> Memory Reset disabled as NT default

*** ERROR => <EsNT> CreateFileMapping name=Global\ES_SEG_02_001 ,size=2044 MB, error=1455 [esnti.c      1276]

.

.

.

*** Error 11 while initializing OS dependent part.

*** ERROR => DpEmInit: EmInit (1) [dpxxdisp.c  10781]

*** ERROR => DpMemInit: DpEmInit (-1) [dpxxdisp.c  10695]

*** DP_FATAL_ERROR => DpSapEnvInit: DpMemInit

*** DISPATCHER EMERGENCY SHUTDOWN ***.

I found the fourm regarding same error url:

    Where i have to change this parameter for shadow instance ?

I found instance PFL in F:\usr\sap\trans\SUM\abap\bin.

If here means i tried but still error occurred.

whether here or any where else.

Please help me to resolve this error.

Regards,

Farkath C

STARTSFI.txt.zip

devtrace.txt.zip

[farkathulla_cikkanther · Accepted solution]

RB,

What you said in below forum is right.

Shadow instance couldn't be started, check 'STARTSFI.LOG' and 'DEVTRACE.LOG': Process G:\usr\sap\EPD...

I found the shadow instance profile in Sum directory and just created parameter em/initial_size_MB=2048. it worked. Thanks.

Regards,

Farkath.C

[Reagan · Accepted solution]

In that case you should consider increasing the memory on the system.

setting the parameter em/initial_size_MB to 2048 is quite small

Good to know that the issue has been resolved.

RB

[farkathulla_cikkanther · Accepted solution]

RB,

   Later i faced more issues during the SUM process. i decrease the value to em/initial_size_MB = 256, then it went fine and completed.

Regards,

Farkath C

[divyanshu_srivastava3]

Hi,

Inshort

*** ERROR => <EsNT> CreateFileMapping name=Global\ES_SEG_02_001 ,size=2044 MB, error=1455 [esnti.c      1276]

Your system is having memory problems.

Make adjustments.

Take a reboot of your system, remove unwanted bottlenecks and adjust memory parameters.

1518419 - Page file and virtual memory required by the SAP

Divyanshu

[Reagan]

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

Regards

RB

[farkathulla_cikkanther]

Hello RB,

   During the upgrade, Can i restart the windows?

Will SUM continue from same phase?

Regards,

Farkath

[Reagan]

During the upgrade, Can i restart the windows?
 Will SUM continue from same phase?

Yes