Skip to Content

MAIN_SWITCH/STARTSAP_TRANS Error

Hi Guys


While Upgrading an ERP6 from EHP2 to EHP7, I'm experiencing an error during MAIN_SWITCH/STARTSAP_TRANS step

System was working fine, until Downtime.

Dispatcher trace is showing it cant connect to port 3900, but message server is running in 3901 (Instance 01) so not sure why its trying to do this

Services file is ok

sapmsSTA 3601/tcp # SAP System Message Server Port

R3trans connects to database (0000)

H:\SUM>R3trans -d

This is R3trans version 6.24 (release 721 - 14.10.14 - 20:14:08).

non-unicode version

R3trans=>sapparam(1c): No Profile used.

R3trans=>sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline

R3trans finished (0000).

At this moment Kernel is still 721, so Switch havent completed yet

H:\SUM>disp+work -v |more

disp+work=>sapparam(1c): No Profile used.

disp+work=>sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline

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

disp+work information

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

kernel release 721

kernel make variant 721_EXT_REL

DBMS client library SQL_Server_9.00

DBSL shared library version 721.02

compiled on NT 6.1 7601 S x86 MS VC++ 16.00 for NTAMD64

compiled for 64 BIT

compilation mode Non-Unicode

compile time Jan 21 2015 23:58:11

update level 0

patch number 401

H:\SUM>

Thu May 21 12:29:48 2015

***LOG Q0I=> NiPConnect2: 172.16.80.177:3900: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]

*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 25/sock 1284

(SI_ECONN_REFUSE/10061; I4; ST; 172.16.80.177:3900) [nixxi.cpp 3283]

*** ERROR => MsIAttachEx: NiBufConnect to STKABAERPSTA/3900 failed (rc=NIECONN_REFUSED) [msxxi.c 718]

Thu May 21 12:30:08 2015

In Default profile which was updated in this step, its stated rdisp/msserv_internal = 3901 and rdisp/msserv = sapmsSTA

SAPDBHOST = STKABAERPSTA

dbms/type = mss

dbs/mss/server = STKABAERPSTA

dbs/mss/dbname = STA

dbs/mss/schema = sta

SAPSYSTEMNAME = STA

SAPGLOBALHOST = STKABAERPSTA

system/type = ABAP

SAPFQDN = softtek.com

SAPLOCALHOSTFULL = $(SAPLOCALHOST).$(SAPFQDN)

rslg/new_layout = 9

rsdb/ssfs_connect = 0

rdisp/mshost = STKABAERPSTA

rdisp/msserv = sapmsSTA

rdisp/msserv_internal = 3901

enque/process_location = REMOTESA

enque/serverhost = STKABAERPSTA

enque/serverinst = 01

is/HTTP/show_detailed_errors = FALSE

icf/user_recheck = 1

icm/HTTP/ASJava/disable_url_session_tracking = TRUE

service/protectedwebmethods = SDEFAULT

rsec/ssfs_datapath = $(DIR_GLOBAL)$(DIR_SEP)security$(DIR_SEP)rsecssfs$(DIR_SEP)data

rsec/ssfs_keypath = $(DIR_GLOBAL)$(DIR_SEP)security$(DIR_SEP)rsecssfs$(DIR_SEP)key

# *** TEMPORARY 740 CHANGE ***

#ssf/name = SAPSECULIB

gw/acl_mode = 1

login/password_downwards_compatibility = 0

login/system_client = 001

PHYS_MEMSIZE = 8192

# Added lines

DIR_PUT=H:\SUM\abap

# *** TEMPORARY 740 CHANGE ***

rdisp/btcname = STKABAERPSTA_STA_00

# Entries for support of High-Availibitity release 740

rdisp/sna_gw_service = sapgw00

But in Instance Profile it says

# Entries for support of High-Availibitity release 740

rdisp/mshost = STKABAERPSTA

rdisp/msserv_internal = 3900

rdisp/msserv = 3600




# *** TEMPORARY 740 CHANGE ***

rdisp/btctime = 60

rdisp/btcname = STKABAERPSTA_STA_00

rdisp/max_wprun_time = 0

rsdb/pmandt = 000

login/system_client = 000

rdisp/bufrefmode = sendoff,exeauto

rdisp/TRACE = 1

transport/during_upgrade = ON

DIR_TRANS = H:\SUM\abap

DIR_PUT = H:\SUM\abap

rdisp/system_needs_spool = false

rspo/spool_id/use_tskh = 0

rec/client = OFF

abap/buffersize = 800000

rdisp/autoabaptime = 0

rdisp/j2ee_start = 0

rdisp/start_icman = false

vmcj/enable = off

rdisp/rfc_max_own_used_wp = 100

# Entries for support of High-Availibitity release 740

rdisp/mshost = STKABAERPSTA

rdisp/msserv_internal = 3900

rdisp/msserv = 3600

# Entries for stand-alone enqueue server

enque/serverhost = STKABAERPSTA

enque/serverinst = 00

enque/encni/port = 50019

enque/process_location = REMOTESA

Any Idea why Message Server is being unreachable?

temp.png (25.7 kB)
Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

2 Answers

  • Best Answer
    May 21, 2015 at 10:15 PM

    Hello Martin,

    It seems as if your MS is on instance 01. So Default profile settings are right. Port must be 3901.

    Since instance profile overwrites default one, system looks 3900 port for MS. (STKABAERPSTA/3900 failed).

    Comment msserv lines on Instance profile and restart the system.

    If the system does not start, send dev_ms, dev_disp, dev_w0, dev_w1 trace files, please?

    Regards,

    Yuksel AKCINAR

    Add comment
    10|10000 characters needed characters exceeded

    • Hi Yuksel,

      Ports definition in the profiles were correct, since during this step, the upgrade starts que message server and Enqueue in same instance as Dispatcher

      It was due a profile has a unproper naming I was carring over from before the Upgrade, and it caused SAP to not start since it could not find it during this step

      Thanks!

  • avatar image
    Former Member
    Aug 17, 2015 at 01:08 AM

    Dear Martin,

    I am also facing same issue, Can you guide me how to fix the issue.

    Regards,

    Sanjeev Kumar

    Add comment
    10|10000 characters needed characters exceeded