Skip to Content
avatar image
Former Member

Portal is not working after support package(webdynpro~runtime) up-gradation.

Hi Experts,

       I have applied webdynpro~runtime support package for portal 7.3 . After up-gradation portal is not working. But server is running.

/irj/portal and /nwa - both urls are not working. Most of the components are not started in portal.

Thanks

untitled2.PNG (15.0 kB)
untitled1.PNG (16.6 kB)
Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

4 Answers

  • avatar image
    Former Member
    Jan 06, 2015 at 06:22 AM

    Hi Muthuraja,

    I hope you would have restarted your Portal server after the upgrade.

    Please go through the below SAP KBAs that might prrove helpful for your case:

    1630240 - Portal runtime error after installing or upgrading to SAP NW 7.3x and 7.4x


    1709737 - Portal Runtime errors when accessing Support, creating a system object or opening a folder after successful upgrade to SAP Netweaver Enterprise Portal 7.3


    BR,

    Anurag

    Add comment
    10|10000 characters needed characters exceeded

  • Jan 06, 2015 at 12:19 PM

    Hi Muthuraja,

    tc~wd~dispwda is not started. You can manually start it and check corresponding defaultTrace to see what happened.

    But before everything make sure

    - all SCs are on same release/SP

    - system is NOT in safe mode

    BR, Tom

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jan 06, 2015 at 03:12 PM

    Hello Muthuraja,

    when you upgraded the 'webdynpro~runtime' component to a new support package, have you upgraded the dependentSCAs that are listed in the service marketplace ?

    A yellow box with exclamation mark appears in the list of webdynpro support package patch level version in the marketplace and you need to click on it to see all SCAs dependencies. This is required for every component upgrade in general.

    Best regards,

    Johann

    Add comment
    10|10000 characters needed characters exceeded

  • Jan 06, 2015 at 08:52 PM

    Hi muthu,


    Hope you are doing good.
    Nice to hear from you again. Such an issue can be caused due to inconsistencies and it will be worthwhile to run the force bootstrap once:

    1)

    Stop the j2ee server. Under cluster directory (/usr/sap/<SID>/J<nr>/cluster) rename server0 and subsequent nodes to ".old" respectively. The intention here is to create a backup of the existing files. Do not rename the bootstrap folder as this is needed for the sync process.
    2)

    Change bootstrap.properties file to ensure it has element.resynch=force as per SAP note 710663.

    3)

    Restart the J2EE Engine. The new server folders should be created during the bootstrapping and this is a time consuming process as all the contents of the server nodes will be syched with the DB content.

    4)

    Remove the element.resynch=force property or change it to element.resynch=detect which is the default setting.

    Please try this; if the issue persists, we will need to check the detailed logs..


    ____________
    Kind Regards,
    Hemanth
    SAP AGS
     

    Add comment
    10|10000 characters needed characters exceeded