Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

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

Former Member replied

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

0 View this answer in context
Not what you were looking for? View more on this topic or Ask a question