Skip to Content
0
Former Member
Nov 24, 2009 at 11:46 AM

Phase MAIN_SHDRUN/ACT_UPG hanging?

206 Views

<h5>

I am upgrading from NW 7.0 Enhancement Package 1 (7.01) using SAPEhpi. The SAPEhpi tools shows that the ABAP progress has status RUNNING 'Executing phase MAIN_SHDRUN/ACT_UPG', and J2EE progress has status WAITING 'Waiting for synchronization event PREPUPTIME=FINISHED'. The status has been the same for the last three days. I understand that long run times are not unusual for this phase, but I have my doubts due to the below circumstances.

<h5>

The shadow instance and standard instance is installed on the same server. I got lots of activation errors '8' in phase MAIN_SHDRUN/ACT_UPG as seen from Filepath:...\EHPI\abap\log\SAPehpiConsole.log

<h5>

Checks after phase MAIN_SHDRUN/ACT_UPG were negative!

<h5>

Last error code set: Process 'tp.exe' exited with 8, see

'C:\SAP_Download\EHPI\abap\tmp\MSGOUT.LOG' for details Check logfiles

'ACTUPG.ELG' and 'C:\SAP_Download\EHPI\abap\log\SAPehpi.ECO'

01) - Repeat phase ACT_UPG to continue at the point it stopped

02) * Initialize phase ACT_UPG to restart it from the beginning

03) - Accept non-severe errors and repeat phase ACT_UPG

04) - Exit this program

Choose action: Initialize phase ACT_UPG to restart it from the beginning

<h5>

>> 2009/11/21 05:20:35 START OF PHASE MAIN_SHDRUN/ACT_UPG

<h5>

running C:\SAP_Download\EHPI\abap\exe\tp.exe pf=C:\SAP_Download\EHPI\abap\bin\SHADOW.TPP checkimpdp AII

Collecting adjustments ...

<h5>

<h5>

But before i initialized the phase ACT_UPG I realised that the shadow instance was unable to connect to the message server. The disp+work was yellow with message 'could not connect to message server'. The DEFAULT.PFL profile for the shadow instance showed the following parameter for the message server: rdisp/msserv = 3607. So I changed the DEFAULT.PFL of the shadow instance to point to the message server of the standard instance. The standard instance nr. = 5, while the shadow instance nr. = 7.

<h5>

rdisp/mshost = turin-1

<h5>

rdisp/msserv = sapmsAII

<h5>

rdisp/msserv_internal = 3905

<h5>

I restarted the shadow instance using SAPMMC for Windows and the message server was then green. I chose to Initialize phase ACT_UPG as option 02) * Initialize phase ACT_UPG to restart it from the beginning.

<h5>

After this decision I can not see any entries in any logs in EHPI directories except the below log. No action for 3 days now, still waiting.....I can log on to the shadow instance using DDIC user but for other users I get message that 'Upgrade still running: Logon not possible'.

<h5>

Any ideas? How can I really determine if the upgrade is still running?

<h5>

Filepath:...\EHPI\sdt\trc\server.trc

<h5>

Nov 24, 2009 1:33:23 AM [Error]: com.sap.sdt.engine.core.communication.AbstractCmd.log(AbstractCmd.java:101) [Thread[ExecuteWorker,5,main]]: Execution of command com.sap.sdt.engine.core.communication.CmdActionEvent@71475e19 failed: null

Nov 24, 2009 1:33:23 AM [Error]: com.sap.sdt.engine.core.communication.AbstractCmd.log(AbstractCmd.java:102) [Thread[ExecuteWorker,5,main]]: java.lang.NullPointerException: null

Nov 24, 2009 1:33:23 AM [Error]: com.sap.sdt.engine.core.communication.AbstractCmd.log(AbstractCmd.java:102) [Thread[ExecuteWorker,5,main]]: java.lang.NullPointerException: null

Nov 24, 2009 1:33:23 AM [Error]: com.sap.sdt.engine.core.communication.CmdActionEvent [Thread[ExecuteWorker,5,main]]: java.lang.NullPointerException

at com.sap.sdt.engine.core.admin.AbstractServerAdmin.getClientConnection(AbstractServerAdmin.java:192)

at com.sap.sdt.server.core.controls.ServerControlFactory.getConsumer(ServerControlFactory.java:102)

at com.sap.sdt.server.core.controls.ServerControlFactory.register(ServerControlFactory.java:83)

at com.sap.sdt.server.core.controls.SDTControlFactory.createFrame(SDTControlFactory.java:114)

at com.sap.sdt.server.core.controls.SDTFrame.createDelegate(SDTFrame.java:119)

at com.sap.sdt.server.core.controls.SDTBase.getDelegate(SDTBase.java:127)

at com.sap.sdt.server.core.controls.SDTFrame.<init>(SDTFrame.java:41)

at com.sap.sdt.server.core.admin.SDTServerAdmin.getFrame(SDTServerAdmin.java:358)

at com.sap.sdt.dsu.ui.AbstractUpgradeViewManager.showBreakPointScreen(AbstractUpgradeViewManager.java:622)

at com.sap.sdt.dsu.ui.AbstractUpgradeViewManager.actionBreak(AbstractUpgradeViewManager.java:417)

at com.sap.sdt.dsu.ui.AbstractUpgradeViewManager.performMenuAction(AbstractUpgradeViewManager.java:160)

at com.sap.sdt.dsu.service.controls.DSUToolListener.actionPerformed(DSUToolListener.java:48)

at com.sap.sdt.server.core.controls.SDTActionListener$Listener.actionPerformed(SDTActionListener.java:49)

at com.sap.sdt.engine.core.communication.CmdActionEvent.actOnEvent(CmdActionEvent.java:38)

at com.sap.sdt.engine.core.communication.CmdEvent.execute(CmdEvent.java:54)

at com.sap.sdt.engine.core.communication.ExecWorker.handleCmd(ExecWorker.java:48)

at com.sap.sdt.engine.core.communication.AbstractWorker.run(AbstractWorker.java:85)