cancel
Showing results for 
Search instead for 
Did you mean: 

Portal Runtime Error after Upgrade 7.01 to 7.3

steven_bier
Active Participant
0 Kudos

Hi,

i have a Problem after Upgrade a BW 7.01 to 7.3 SP5 the,

abap works fine but the Java Portal bring up Error on many time by choosing any funktion

for example:

try to use Portalcontent -> Systemlandscape -> SAP_BW

this error is shown.

Portal Runtime Error

Tracefile:

2011 11 24 13:05:51:546#+0100#Error#com.sap.portal.prt.connection#

#EP-PIN-PRT#tcepbcprtc~api#C0000A11295500740000000000E900F2#9281050000000004#sap.com/irj#com.sap.portal.prt.connection#FREYAD#3##8D780B5716941 1E1C8790000008D9E1A#a6e61adf169411e1cab50000008d9e1a#a6e61adf169411e1cab50000008d9e1a#0#Thread[HTTP Worker [@904797166],5,Dedicated_Application_ Thread]#Plain##

Exception ID:01:05_24/11/11_0004_9281050

[EXCEPTION]

com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Portal Component

Application name : com.sap.portal.appdesigner.framework

Component : pcd:portal_content/com.sap.pct/admin.templates/iviews/editors/com.sap.portal.pcmEditor

Component class : com.sap.portal.admin.propertyeditor.core_functionality.PCMEditor

-all Funktions in NWA are working

-Diagnose an Supporttool is Green !

Thanks Steven

Accepted Solutions (0)

Answers (4)

Answers (4)

steven_bier
Active Participant
0 Kudos

Hi Raj,

You need to redeploy the patches in the message from Alexandra.

How to redeploy same component with JSPM?

JSPM does not allow to deploy an SCA with the same version (release, SP-level, patch-level) as an already deployed component. However, in some special cases you may need to redeploy an SCA with the same version. Use command line:

go "-config=/jspm/forceMode=true" "-config=/jspm/deployVersionRule=updateAll" to redeploy all SDAs. See note #1123333 for more options.

regards

Steven

Former Member
0 Kudos

Thank you very much Alexandra and Steve. I did redeploy the list of components (mentioned above). Issue is resolved.

Former Member
0 Kudos

Hi,

You can try one of the following:

I. Deploy the latest patches of the following components:

     ENGINEAPI 7.3

     J2EE ENGINE FRAMEWORK 7.30

     J2EE ENGINE SERVERCORE 7.30

  •      EP ADMINISTRATION 7.30
  •      EP CONNECTIVITY 7.30
  •      EP RUNTIME 7.30
  •      PORTAL BASIS 7.30
  •      PORTAL BASIS API 7.30
  • II. Deploy the com.sap.portal.pcd.initialcontent.sda manually - extract rge EP-RUNTIME.SCA and locate com.sap.portal.pcd.initialcontent.sda under DEPLOYARCHIVES.
  • You can also take a look at note 1687499 and see whteher the OOM error occured in the default traces during the upgrade process.
  • Regards,
  • Alex
  • Former Member
    0 Kudos

    Hi Steven,

    Were you able to fix the problem? I am into the same problem now. After BW 7.30 upgrade , I am unable to edit the exiting system defined under system landscape. Can you please share the solution?

    thanks

    Raj

    Former Member
    0 Kudos

    Hi Steven,

    Not sure of the exact solution, but just a try-

    Login into the portal as admin and navigate to System admin > System Config > Service Config > Applications > com.sap.portal.appdesigner.contentcatalog and compare the settings in the old and new system.

    Regards,

    Atul