cancel
Showing results for 
Search instead for 
Did you mean: 

EHP5 Upgrade - Getting error in MAIN_NEWBAS/STARTSAP_NBAS

Former Member
0 Kudos

Checks after phase MAIN_NEWBAS/STARTSAP_NBAS were negative!

Last error code set: RFC call to subst_get_uvers failed with key RFC_ERROR_SYSTEM_FAILURE (open): SAP_CMINIT3 : rc=20 > Connect to SAP gateway failed

Connect_PM GWHOST=accagtci, GWSERV=sapgw19, SYSNR=19

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

ERROR partner '10.69.18.210:3319' not reached

TIME Tue Oct 18 11:10:31 2011

RELEASE 720 COMPONENT NI (network interface)

VERSION 40 RC -10 MODULE nixxi.cpp

LINE 2897

DETAIL NiPConnect: 10.69.18.210:3319

SYSTEM CALL connect

ERRNO 239 ERRNO

TEXT Connection refused

COUNTER 7

System start failed

I tried system is Up, I also stopped & restarted it manually but same problem.

Can any one help in this regard,

Sriram

Edited by: skb2909 on Oct 19, 2011 7:21 AM

Accepted Solutions (0)

Answers (2)

Answers (2)

nicholas_chang
Active Contributor
0 Kudos

Hi,

is there any ASCS installed? if yes, do ensure ASCS is up and running.

Cheers,

Nicholas Chang

Former Member
0 Kudos

Hi Nicholas Chang ,

Thanks for your response, ASCS installed is not installed. May I get any other suggestions.

Sriram

Former Member
0 Kudos

Hi,

Is the port free/not used? Have you tried nstat -a | grep 3319

Regards,

Terry

Former Member
0 Kudos

Hi found the cause for the error

more stderr1

(11990) New Child Process created.

(11990) Starting local Command:

Command: ms.sap<SID>_DVEBMGS19

pf=/usr/sap/<SID>/SYS/profile/<SID>_DVEBMGS19_acc<sid>ci

***

      • MSG_SERVER died => MsSInit failed,

But not getting the solution what to do? can any one give some idea

Regards,

Sriram

Edited by: skb2909 on Oct 19, 2011 5:06 PM

Former Member
0 Kudos

Thanks for all your suggestions, problem solved its a confilict in rdisp/msserv_internal = 3919 ..

Thanks & Regards,

Sriram

Ramesh_Cirrus
Explorer
0 Kudos

I faced similar issue during this phase and found that during the preprocessing phase the upgrade tool should have added the following 2 lines to DEFAULT.PFL. But it didn't and raised a message to SAP to find out why.

Once you added these 2 parameter to the profile the upgrade continued to next step in Downtime phase.

  1. *** PERMANENT 702 CHANGE ***"

rdisp/msserv_internal = 13900

system/type = ABAP

Former Member
0 Kudos

Hi,

Try to check connection with niping utility according with sapnote https://service.sap.com/sap/support/notes/1341701

Also check your firewall and antivirus settings.

Best Regards,

Aleh