MAIN_SWITCH/STARTSAP_TRANS Error

[former_member229542]

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?

[yakcinar · Accepted solution]

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

[former_member229542 · Accepted solution]

Hi Yuksel

tried to to that trick but still saying Message Server Unreachable

During that phase, SUM copies profiles to a TEMP folder but only starts Instance 00, does not start instance 01 so not sure why is trying to find message server in port 3900.

Besides, all those changes are done by SUM tool during this phase.

dev_disp

Thu May 21 19:54:00 2015

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

*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 17/sock 836

    (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]

***LOG Q0L=> DpLoopInit, nomscon () [dpxxdisp.c   1808]

CCMS: SemInMgt: Semaphore Management initialized by AlAttachShm_Doublestack.

CCMS: SemInit: Semaphore 38 initialized by AlAttachShm_Doublestack.

CCMS: start to initalize 3.X shared alert area (first segment).

DpAppcBlksLow: max appc blocks in queue is 500 (50 %)

DpWpBlksLow: max wp blocks in queue is 800 (80 %)

Thu May 21 19:57:01 2015

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

*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 26/sock 484

    (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 19:57:21 2015

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

*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 29/sock 484

    (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 19:57:41 2015

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

*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 24/sock 1100

    (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]

dev_w0

M Thu May 21 19:54:11 2015

M  calling db_connect ...

B  Loading DB library 'S:\usr\sap\STA\DVEBMGS00\exe\dbmssslib.dll' ...

B  Library 'S:\usr\sap\STA\DVEBMGS00\exe\dbmssslib.dll' loaded

B  Version of 'S:\usr\sap\STA\DVEBMGS00\exe\dbmssslib.dll' is "721.02", patchlevel (0.326)

C  Callback functions for dynamic profile parameter registered

C  Thread ID:3708

C  Thank You for using the SLODBC-interface

C  Using dynamic link library 'S:\usr\sap\STA\DVEBMGS00\exe\dbmssslib.dll'

C  7210 dbmssslib.dll patch info

C    SAP patchlevel  0

C    SAP patchno  401

C    Last MSSQL DBSL patchlevel 0

C    Last MSSQL DBSL patchno         326

C    Last MSSQL DBSL patchcomment A simplified DBCON connection approach (1852521)

C  ODBC Driver chosen: SQL Server Native Client 11.0 native

C  lpc:(local) connection used on STKABAERPSTA

C  lpc:(local) connection used on STKABAERPSTA

C  Driver: sqlncli11.dll Driver release: 11.00.3393

C  GetDbRelease: 11.00.2100.60

C  GetDbRelease: Got DB release numbers (11,0,2100,60)

C  comm. rd. spid 83

C  unc. rd. spid 85

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

I 

I Thu May 21 19:54:13 2015

I  MtxInit: 0 0 0

M  SHM_PRES_BUF (addr: 00000000154D0050, size: 4400000)

M  SHM_ROLL_AREA (addr: 00007FFFBF3C0050, size: 267059200)

M  SHM_PAGING_AREA (addr: 0000000015910050, size: 115015680)

M  SHM_ROLL_ADM (addr: 0000000000750050, size: 2740736)

M  SHM_PAGING_ADM (addr: 00000000009F0050, size: 787488)

M  ThCreateNoBuffer allocated 328144 bytes for 1000 entries at 0000000000AC0050

M  ThCreateNoBuffer index size: 3000 elems

M  ThCreateVBAdm allocated 17104 bytes (50 server) at 0000000000B20050

X  EmInit: MmSetImplementation( 2 ).

X  MM global diagnostic options set: 0

X  <ES> client 0 initializing ....

X  Using implementation view

X  ES initialized.

X  mm.dump: set maximum dump mem to 192 MB

X  mm.dump: set global maximum dump mem to 192 MB

X  EsRegisterEmCheck: Register EmGetEsHandles at 00007FF7F958A580

B  db_con_shm_ini:  WP_ID = 0, WP_CNT = 19, CON_ID = -1

B  dbtbxbuf: Buffer TABL  (addr: 0000000035780160, size: 30000000, end: 000000003741C4E0)

B  dbtbxbuf: Buffer TABLP (addr: 0000000037420160, size: 10240000, end: 0000000037DE4160)

B  dbsync[db_syinit]: successfully attached to shared memory, sync_adm_p = 00000000111F0050

B  dbsync[db_syinit]: Buffer synchronisation started with

There is no dev_ms since it was never started.

Best

Martin

[former_member229542 · Accepted solution]

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!

[Former Member]

Dear Martin,

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

Regards,

Sanjeev Kumar

[former_member229542]

Hi Sanjeev.

In order to overcome the issue, you may need to create a duplicate shadow instance profile file with the proper naming (SID_XX_servername)