SAPup broke during phase SHDINST_CHK2 in module MAIN_SHADOW

[Former Member]

Hello All,

During CRM upgrade in preprocessing in SHDINST_CHK2 in module MAIN_SHADOW,

Upgrade stop wih:

Severe error(s) occurred in phase MAIN_SHADOW/SHDINST_CHK2!
Last error code set: Messageserver "sapmsSHDDC2" is not an entry in services

-------------------------------------------------------------
SAPup broke during phase SHDINST_CHK2 in module MAIN_SHADOW / Shadow System Operations: Start shadow system
Error Message: Messageserver "sapmsSHDDC2" is not an entry in services,

I had tried to add "sapmsSHDDC2" entry in services file, But did not help,

Any body havd the same problem?

Thanks

Reza

[Former Member · Accepted solution]

Hello.

I have this from file "SHDINST_CHK2.LOG

#!--------------------------------------------------------------
#!---- MASKING file "SHDINST_CHK2.LOG" from "E:\usr\sap\DC2\SUM\abap\log"
#!---- TIME: 20141112160252  PHASE: MAIN_SHADOW/SHDINST_CHK2
#!--------------------------------------------------------------

1 ETQ201 Entering upgrade-phase "MAIN_SHADOW/SHDINST_CHK2" ("20141112155344")
2 ETQ367 Connect variables are set for standard instance access
4 ETQ399 System-nr = '00', GwService = 'sapgw00' Client = '000'
4 ETQ399 Environment variables:
4 ETQ399   dbs_mss_schema=<null>
4 ETQ399   auth_shadow_upgrade=<null>
1 ETQ206 Executing pre-phase DB specific actions.
1 ETQ200 Executing actual phase 'MAIN_SHADOW/SHDINST_CHK2'.
1EETQ399 Last error code set is: Messageserver "sapmsSHDDC2" is not an entry in services
1EETQ204 Upgrade phase "SHDINST_CHK2" aborted with severe errors ("20141112155344")

[Reagan · Accepted solution]

What is the entry you have put in the /etc/services file ?

It should be like this:

sapmsSHD<SAPSID>  36<instance number of SHD instance>/tcp

Eg: sapmsSHDDC1     3603/tcp

Cheers

Reagan

[Former Member · Accepted solution]

Hello Reagan.

The entry is

sapmsSHDDC2 3601/TCP

Thanks

Reza

[Reagan · Accepted solution]

I believe the shadow system number is 01 and there is no system using it.

Stop SUM and maintain this entry

sapmsSHDDC1     3601/tcp

Hit enter and restart SUM

[Former Member · Accepted solution]

Yes the shadow system number is 01 and there is no system using  3601 on  /etc/services file.

The SID for this system is DC2 and not DC1?

Why should use:

sapmsSHDDC1     3601/tcp  and not

sapmsSHDDC2     3601/TCP

Thanks

Reza

[Reagan · Accepted solution]

Sorry mate, bad eyes nowadays. Just put the right SID entry and save the file. Restart SUM and see if that helps.

[Former Member · Accepted solution]

Thanks it is working now,

I did tried defferent thing, the way is Work for me was,

Stop SUM, add entry in service file, stop sap instance, restart server, start sap and shodow instance and restart SUM.

Thankes for help

[hemanth2 · Accepted solution]

Hi Reza,

It would be a good idea to set the severity HIGH so that you get more detailed logs; this should have had the exact errors.

Set com.sap.sdt.severity to DEBUG in:

    -SUM\sdt\param\logging.properties

    -SUM\sdt\prop\logging.properties

    -SUM\java\param\logging.properties

Kind regards,
Hemanth

[divyanshu_srivastava3]

Add this entry in service file and restart shadow instance including sapstartsrv.

[Former Member]

Hello Divyanshu,

I had add :

sapmsSHDDC2 3601/tc on service file and restart SUM and server to be sure about service file get update. But no help

I had start shadow instance  manual? But still the same error.

What do mean by  including sapstartsrv?

Thanks