Skip to Content

Prepare: Shadow instance not starting and RFC error

Hi all

I am running PREPARE because we want to upgrade from R/3 4.7 Ext.set 2.00 to ERP 2005 SR2 on Windows 2003 and MSSQL 2005.

I have a problem when trying to start the Shadow Instance that is created during prepare (I try using the SAPMMC, "./startsap DVEBMGS<NR> R3" command). The Message Server starts, but the Dispatcher is not starting.

In the dev_disp log file for the shadow instance I find this:

Wed Jan 03 18:05:25 2007

  • Error 11 while initializing OS dependent part.

  • ERROR => DpEmInit: EmInit (1) [dpxxdisp.c 9544]

  • ERROR => DpMemInit: DpEmInit (-1) [dpxxdisp.c 9473]

  • DP_FATAL_ERROR => DpSapEnvInit: DpMemInit

  • DISPATCHER EMERGENCY SHUTDOWN ***

increase tracelevel of WPs

NiWait: sleep (10000ms) ...

NiISelect: timeout 10000ms

NiISelect: maximum fd=1

NiISelect: read-mask is NULL

NiISelect: write-mask is NULL

Wed Jan 03 18:05:35 2007

NiISelect: TIMEOUT occured (10000ms)

dump system status

Any ideas on how to proceed??

However, when I try to continue prepare I get this error message in the PSUPGRFC.LOG file:

1 ETQ201XEntering upgrade-phase "RUN_RSUPGRFC" ("20070103171730")

2 ETQ367 Connect variables are set for standard instance access

4 ETQ399 System-nr = '01', GwService = 'sapgw01'

4 ETQ399 Environment variables:

4 ETQ399 dbs_mss_schema=t01

4 ETQ399 auth_shadow_upgrade=0

4 ETQ010 Date & Time: 20070103171730

4 ETQ265 Starting report "RSUPGRFC" with variant "SAP_SHDREM" in batch

4 ETQ359 RFC Login to: System="T01", Nr="01", GwHost="vmkomplett", GwService="sapgw01"

2 ETQ231 RFC Login failed

2EETQ360 RFC of "subst_start_report_in_batch" failed:

2EETQ361 code/exception : open

2EETQ362 key : RFC_ERROR_COMMUNICATION

2EETQ364 message :

2EETQ399 Connect to SAP gateway failed

2EETQ399 Connect_PM DEST=T01, GWHOST=vmkomplett, GWSERV=sapgw01, SYSNR=01

2EETQ399

2EETQ399 LOCATION CPIC (TCP/IP) on local host

2EETQ399 ERROR partner 'vmkomplett:3301' not reached

2EETQ399

2EETQ399 TIME Wed Jan 03 17:17:31 2007

2EETQ399 RELEASE 700

2EETQ399 COMPONENT NI (network interface)

2EETQ399 VERSION 38

2EETQ399 RC -10

2EETQ399 MODULE nixxi.cpp

2EETQ399 LINE 2764

2EETQ399 DETAIL NiPConnect2

2EETQ399 SYSTEM CALL connect

2EETQ399 ERRNO 10061

2EETQ399 ERRNO TEXT WSAECONNREFUSED: Connection refused

2EETQ399 COUNTER 1

2EETQ399

4 ETQ359 RFC Login to: System="T01", Nr="01", GwHost="vmkomplett", GwService="sapgw01"

2 ETQ231 RFC Login failed

2EETQ236 RFC Login failed with return code -1

1EETQ204 Upgrade phase "RUN_RSUPGRFC" aborted with severe errors ("20070103173337")

Return code -1 indicates an error with client, username or password for the RFC connection. When I look at the RFC in SM59 in my system, the hosts that the R/3 connection "SAP_UPGRADE_SHADOW_SYSTEM" points to in sapp01r3, which is totally unknown to me. Our host is called something else.

I have no idea on where to start looking from here.

Help is greatly appreciated and needed.

Regards,

Thomas

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

9 Answers

  • Best Answer
    avatar image
    Former Member
    Jan 08, 2007 at 03:42 PM

    Hi Thomas,

    To reset the upgrade to initial state I proceed as followed:

    1. Stop the upgrade server. If you can't do this from Upgrade Assistant, kill the java process.

    2. Delete put directory

    3. Start prepare.bat again (don't forget to create put directory)

    4. After prepare.bat has finished, start upgrade server as normal (java -cp ua.jar UaServer)

    5. Try to loggon on with upgrade assistant

    6. If this works stop upgrade server (i normally kill the java process) and replace SAPup, R3trans, tp in ../usr/sap/put/bin

    7. Restart upgrade server and connect with upgrade assistant

    If you change any files while upgrade server is running you have to restart them!

    ATTENTION!!!

    You have to use tp and R3trans from Kernel for WebAS 7.00 because you are upgrading to ERP2005 -> this is your TARGET RELEASE. Don't change any other tp, R3trans in other directories, only if upgrade assistant told you to do so. Upgrade assistant comes with an right version of the source release kernel!!

    Regards,

    Daniel

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Thomas Kjelsrud

      hi thomas,

      as you have re-started the prepare from the first.. i hope you have cleared tht etc/service file, removed the previous settings.

      as per my understanding, i guess you didn't start the actual upgrade. if tht is so, then it is too early to worry abt tht shadow instance. R3up will bring the shadow instance only at the system downtime ( for more on this refer upgrade manual).

      that time, the central instance will be down and shadow instance will be up, once we complete our SPDD activity, then shadow instance will down complete forever.

      i had forwarded my documentation on upgrade to your mail id.

      with best rgds,

      Rajesh.

      <i>award suitable points</i>

  • avatar image
    Former Member
    Jan 04, 2007 at 08:53 AM

    Hi Thomas,

    please look into ‘STARTSFI.LOG’ & ‘DEVTRACE.LOG’ for the error details. and try remote log on, using the RFC connection,

    "SAP_UPGRADE_SHADOW_SYSTEM". check whtr instance number is correctly mentioned &

    check whtr the following actions are done already.

    • You have to login as root and enter: the shadow dispatcher instance sapdp<shadow instance number> in /etc/services with number 32<insance number>

    • Please create the user for the shadow instance by executing

    SQL script crshdusr.sql. [which is available in “/DEPOT” directory].

    try to create a copy of START_DVEBMGS<instance no>_<hostname> with name START_DVEBMGS<instance_no>.

    and try starting it manually.

    <u><b>Stopping Shadow instance</b></u>

    cd /usr/sap/put

    cd bin

    R3up stopshd

    Enter the path of your upgrade directory [/usr/sap/put]:

    Upgrade directory = /usr/sap/put

    <u><b>Starting Shadow instance</b></u>

    R3up startshd

    Enter the path of your upgrade directory [/usr/sap/put]:

    Upgrade directory = /usr/sap/put

    with br,

    Raj.

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Thomas Kjelsrud

      Hi Thomas,

      i was under the impression tht, their might be some problem while specifying inputs, so i asked you to cross check this Shadow.TP0 file. sometime it happens, tht SAP will take wrong inputs, even you give the correct [it will pick from previous installations].

      even i am unable to trace out anything from this file.

      Raj.

  • avatar image
    Former Member
    Jan 03, 2007 at 08:30 PM

    Hi thomas,

    I think manual stopstart of shadow instance should be done with : R3up startshd

    also , I see that the gateway service is not present.

    Check your services file and see if sapgw01 exists and points to 3301

    Regards,

    Siddhesh

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Thomas Kjelsrud

      Hi Thomas,

      What is the instance number of your original source system ?

      Is it 00 , cause if its 01 then the Shadow instance should have instance number 02.

      Also your services file doesn't seem to be correct,

      instead of this...

      sapmsSHDT01 3601/tcp #Upgrade shadow instance

      sapdp01 3601/tcp #Upgrade shadow instance

      sapgw01 3601/tcp #Upgrade shadow instance

      it should be this...

      sapmsSHDT01 3601/tcp #Upgrade shadow instance

      sapdp01 3201/tcp #Upgrade shadow instance

      sapgw01 3301/tcp #Upgrade shadow instance

      All this assuming that your source system has instance number 00 and shadow instance is having instance number 01.

      Regards,

      Siddhesh

  • avatar image
    Former Member
    Jan 08, 2007 at 01:23 PM

    Hi Thomas,

    It is always a good Idea to use the latest SAPup Version. Download the latest version

    from marketplace and put it /usr/sap/put/bin (don't delete the old one, rename it).

    I also recommend to start prepare from beginning with this new SAPup version (Don't forget to restart upgrade Server first!!!).

    Is the shadow instance installed one the same host as the R/3 System?

    Also check if there is anything running that blocks or uses port 3201, 3301, 3601.

    regards,

    daniel

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jan 08, 2007 at 02:28 PM

    Hi,

    You've have to use tp and R3trans of your target release! Kernel 83 is the latest one. Use this one. I've used this version this week for an upgrade.

    Regards

    Daniel

    Add comment
    10|10000 characters needed characters exceeded

    • Hi Prince,

      When I restart the Upgrade Server and Upgrade Gui, a message at the bottom is telling me that "SAPup started in PREPARE mode". This should indicate that I am in fact in PREPARE? I also look at the CHECKS.LOG, and it is telling me that I am in the Installation phase. So why is it telling me that the upgrade has started, and how can I reset PREPARE in order to start over?

      Ok, so I only need those two files (R3trans and tp), and not the entire kernel?

      Thanks!

      Regards,

      Thomas

  • avatar image
    Former Member
    Jan 03, 2007 at 08:31 PM

    Hi,

    Also check the following SAP Notes:

    Note 525677 - Problems when starting the shadow instance

    Note 398100 - Shadow instance during upgrade

    Regards,

    Siddhesh

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jan 05, 2007 at 07:51 PM

    Hi Thomas,

    Intressting probem. I had a similar problem some time ago.

    Some questions: In what phase of PREPARE are you?

    Have you applied the latest tp, R3trans, SAPup, Corrections for Upgrade, after you first start the Upgrade Server (this is a very importent information, because if the versions are not correct you will always run in trouble, believe me, at the moment I make an upgrage from 4.6C to ERP2005 / MSSQL2005).

    And don't think about R3up. You make an upgrade to to WebAS 7.00 so you only have to use SAPup 7.00 (R3up is used until WebAS 6.40).

    Regards

    Daniel

    Add comment
    10|10000 characters needed characters exceeded

    • Hi Daniel,

      My biggest concern is that the shadow instance is not starting. In the process list for the shadow instance, the message server is running, but the dispatcher starts ok and then stops after about a minute. Do you have any idea of what might cause this, and possibly how to fix it?

      I am in the Installation phase of Prepare, in a phase called "RUN_RSUPGRFC".

      I have checked the CHECKS.LOG file, and it tells me that no upgrade of R3trans, tp, disp+work is needed. There is no information regarding SAPup. I have applied the latest corrections for the upgrade "ERP2005SR2_8-20000914.SAR" and unpacked. The files FIX_ERP2005SR2.UPG and FIX_ERP2005SR2_8.info are in the usr\sap\put directory.

      Please let me know if you think you have any information that might help us get through this.

      Regards,

      Thomas

      Message was edited by:

      Thomas Kjelsrud

  • avatar image
    Former Member
    Jan 08, 2007 at 01:50 PM

    Hi Thomas,

    Yes, I recommend to start PREPARE from begining (including delete put directory) and also delete the service of the shadow instance (in the regestry or with sapstartsrv.exe).

    Use netstat -a to see what ports are used on your host.

    Regards

    Daniel

    Add comment
    10|10000 characters needed characters exceeded

  • Jan 10, 2007 at 01:02 PM

    Hi all!

    I would like to give all of you 10 points for helping me solve this issue, but unfortunately I can't. Thanks to everyone helping me, and I hope that I can be of help to you in the future.

    Best Regards,

    Thomas Kjelsrud

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Hamendra Patel

      Hi Hamendra

      <i> i suggest you to create a new msg in this forum. since it will be viewed the rest of the users and they will come up with there suggestions too</i>.

      comming to your problem,

      i guess its the problem of ports..it should be, something like this.

      1. SHD INSTANCE NUMBER = 03

      2. SHD send d talk port = 1303

      3. SHD send d listen port = 1203

      4. SHD collect d listen port = 3903

      5. SHD collect d talk port = 4003

      6. SHD GW SERVICE = sapgw03

      based upon the shadow instance number, provide the appropriate values. pls, check that ports are not used by any other services. check the values in R3up.log file.

      i hope this info helps you!

      with regards,

      raj.

      <i>pls award suitable points.</i>