upgrading to sp13

[Former Member]

Hi I tried to upgrade the AS JAVA server to sp13, but some problems occured, and the J2EE engien is running in safe mode ever since.

I got an error message like this(I left some blanks, there were many stuff there i didn't feel typing in):

Deployment of archive ....\EPBC13_0-10003473.SCA has been terminated.Aborted software component EPBC.....FaIled deployment of SDAs: development component: 'com.sap.prt.....'

I looked up the logs and found this:

C:\usr\sap\J2E\JC02\SDM\root\origin\sap.com\com.sap.prt.application.rfcframework\SAP AG\2\7.0013.20070808101344.0000\com.sap.prt.application.rfcframework.sda.ear

Nov 25, 2007 11:38:16... Info: Software type of SDA: J2EE

Nov 25, 2007 11:38:17... Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****

Nov 25, 2007 11:38:33... Info: Begin of log messages of the target system:

07/11/25 23:38:32 - ***********************************************************

07/11/25 23:38:33 - Start updating EAR file...

07/11/25 23:38:33 - start-up mode is lazy

07/11/25 23:38:33 - EAR file updated successfully for 125ms.

07/11/25 23:38:33 - Start updating...

07/11/25 23:38:33 - EAR file uploaded to server for 78ms.

07/11/25 23:38:33 - ERROR: Not updated. Deploy Service returned ERROR:

java.rmi.RemoteException: Cannot deploy application sap.com/com.sap.prt.application.rfcframework..

Reason: Container PortalRuntimeContainer is not active at the moment and it is not possible to update sap.com/com.sap.prt.application.rfcframework.; nested exception is:

com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Container PortalRuntimeContainer is not active at the moment and it is not possible to update sap.com/com.sap.prt.application.rfcframework.

at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:681)

at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1278)

at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:313)

at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:199)

at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136)

at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)

at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)

at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)

at java.security.AccessController.doPrivileged(Native Method)

at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)

Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Container PortalRuntimeContainer is not active at the moment and it is not possible to update sap.com/com.sap.prt.application.rfcframework.

at com.sap.engine.services.deploy.server.application.UpdateTransaction.getConcernedContainers(UpdateTransaction.java:483)

at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:263)

at com.sap.engine.services.deploy.server.application.UpdateTransaction.begin(UpdateTransaction.java:164)

at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292)

at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:326)

at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3184)

at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:669)

... 10 more

For detailed information see the log file of the Deploy Service.

07/11/25 23:38:33 - ***********************************************************

Nov 25, 2007 11:38:33... Info: End of log messages of the target system.

Nov 25, 2007 11:38:33... Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****

Nov 25, 2007 11:38:33... Error: Aborted: development component 'com.sap.prt.application.rfcframework'/'sap.com'/'SAP AG'/'7.0013.20070808101344.0000'/'2', grouped by software component 'EPBC'/'sap.com'/'SAP AG'/'1000.7.00.13.0.20070812123744''/'2':

Caught exception during application deployment from SAP J2EE Engine's deploy service:

java.rmi.RemoteException: Cannot deploy application sap.com/com.sap.prt.application.rfcframework..

Reason: Container PortalRuntimeContainer is not active at the moment and it is not possible to update sap.com/com.sap.prt.application.rfcframework.; nested exception is:

com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Container PortalRuntimeContainer is not active at the moment and it is not possible to update sap.com/com.sap.prt.application.rfcframework.

(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineJ2EE620OnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)

Nov 25, 2007 11:38:33... Info: Starting to save the repository

Nov 25, 2007 11:38:34... Info: Finished saving the repository

Nov 25, 2007 11:38:34... Info: Starting: Update: Selected software component 'EPBC'/'sap.com'/'SAP AG'/'1000.7.00.13.0.20070812123744''/'2' updates currently deployed software component 'EPBC'/'sap.com'/'SAP AG'/'1000.7.00.11.0.20070201073900''/'0'.

Nov 25, 2007 11:38:34... Error: Aborted: software component 'EPBC'/'sap.com'/'SAP AG'/'1000.7.00.13.0.20070812123744''/'2':

Failed deployment of SDAs:

development component 'com.sap.prt.application.rfcframework'/'sap.com'/'SAP AG'/'7.0013.20070808101344.0000'/'2' : aborted

Please, look at error logs above for more information!

Nov 25, 2007 11:38:34... Info: Starting to save the repository

Nov 25, 2007 11:38:35... Info: Finished saving the repository

Nov 25, 2007 11:38:35... Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.

Nov 25, 2007 11:38:35... Error: -

---

At least one of the Deployments failed -

---

After this the engine seemed to run in safe mode.

Do you have any ideas as why this happened and how to fix it?

Bye,

Peter

[former_member185954 · Accepted solution]

Hi,

Also have a look at this SAP Note:

Note 870234 - Portal doesn't come up during/after SP13 upgrade

It may resolve your issue, please note before applying any note/patch, please take a complete offline backup of your system.

Regards,

Siddhesh

[Former Member · Accepted solution]

AS Java was running fine earlier.

The note is interesting, but refers to 6.4 not 7.0 sp13, that we tried to patch.

[former_member185954 · Accepted solution]

Hi,

It would be worthwhile raising an OSS Message for the same if possible.

Regards,

Siddhesh

[Former Member]

ASJaVA and AS ABAP server both needed to be upgraded to sp13.

[Former Member]

Hi!

Maybe you can manually start the prt if you find out, which service on Visual Admin-Level it belongs to. I've seen a similar situation where the webdynpro container was missing. PRT is more central though, so it may not be possible.

If you want to get your J2EE out of safe mode that can be easily accomplished in configtool, where you will find a 'Safe Mode' configuration in the Menu.

Good luck,

Jörg

[former_member185954]

Hi,

This seems to be your actual error:

Container PortalRuntimeContainer is not active at the moment

Was the AS Java running fine earlier.

Regards,

Siddhesh