Skip to Content

-New Chrome version released is presenting rendering issues in loading SAP Portal as described in SAP note below:

#2421240 – Portal is not loaded on Chrome 56.

 

As described the Portal framework is not loading (blank TLN, blank DTN and blank content area)

 

The main suggestion for now is to follow SAP note bellow and patch EP-RUNTIME and its dependencies:

#2372722 – Portal is not loaded on Chrome 54 and above

 

-Issue is related to Chrome browser issue and it is already in discussion / analysis and will probably be fixed in new Chrome version update / release.

 

-Please follow KBA #2421240 and this commuinity blog in order to have updated information about the current status of the issue.

To report this post you need to login first.

12 Comments

You must be Logged on to comment or reply to a post.

  1. Matteo Stocco

    Hello,

    are there some information about new version of Chrome that should solve the problem?

    This issue is very severe for us and the SAP portal update is very demanding.

    Regards

    (0) 
    1. Edison BF Post author

      As described in SAP note #2372722, there was a fix provided in SAP Portal for Ajax frameworks to work as expected in newer versions of chrome (54, 55, 56…).
      -In order to check behavior for new Chrome version you can try Chrome beta.

      (0) 
      1. Axel Dubbert

        Problem persists as of today: Tested with Chrome Version 58.0.3006.0 canary (64-bit). (The Canary Build is supposedly even fresher than the beta.) … Starting Portal Update Preparation.

        (0) 
  2. Fabricio Pereira

    Hello Edison,

    The Google Chrome 56 bug with SAP Portal is a major issue for my company.

    SAP released 2 notes (2372722 and 2421240) describing the issue. They both claims the solution to the problem is in the latest EP-RUNTIME patch but the blog from Orit Harel is linking us to a Chrome forum  (687061) where Google is investigating and possibly working in a solution as well.

    It will take us some time to implement any patch in the Portal so should I expect to have any new version of Chrome with a fix for this issue in the next days?

    Is SAP working with Google to find a solution to this issue in the browser side?

    Best regards,

    Fabricio Pereira

     

    (0) 
  3. udit kandh

    Hi, Do we have any impact on LSO module once we do this:

    The below mentioned are the current & minimum patch levels required to update Patch level for EP-Runtime component to 740 SP09 Patch 041 from 740 SP09 Patch 27.

     

    Component Name Current Version / Patch Level Minimum required Version / Patch Level
    EP ADMINISTRATION 740 SP09 Patch 004 740 SP09 Patch 002
    KMC CONTENT MANAGEMENT 740 SP09 Patch 00 740 SP09 Patch 017
    PORTAL BASIS. 740 SP09 Patch 024 740 SP09 Patch 033
    PORTAL BASIS API 740 SP09 Patch 002 740 SP09 Patch 001
    (0) 
  4. Krishnagopal Mukundan

     

    Hello,
    For our NP1 system, we are facing the same issue as mentioned in note 2372722 with Chrome 56 & above.

    The solution section of this SAP Note mentions about applying patch on current EP-RUNTIME component.
    However, it has dependency to other components which in turn leads to entire SPS upgrade of entire Portal.
    We would like to know if this patch can be applied, just to EP-RUNTIME? Will it not lead to dependency failures in other components?
    For Java systems, SAP doesn’t recommend to upgrade the SP or patch level of a single component. Instead, we have to go for a full SP upgrade, correct?

    We verified and EP_RUNTIME  has far too many dependencies, which means upgrading all related components which are further dependent on others.

    Kindly advise on this.

    (0) 
  5. Ankit Nathani

    Hi Krishna

    You can analyse SCA dependency list of all direct and indirect dependent SCA using easy to use SC patch tool of SAP NW Java Support Tool. You can download the same from link https://wiki.scn.sap.com/wiki/display/ASJAVA/SAP+NW+Java+Support+Tool or from SAP marketplace. I have attached screenshot here for EP RUNTIME

    Full SP upgrade is not required if only single component patch is required. Only thing is to take care of all dependent patch (can be done through SC patch tool automatically instead of calculating manually and recursively) and using consistent manually prepared directory option of SUM tool as per note 1641062.

    Please comment if the info helped you resolving your query..

    regards

    Ankit Nathani

     

    (0) 
  6. Matteo Stocco

    Hello,

    since we don’t know when google will release the new version of Chrome (and  how Axel Dubbert wrote also with Chrome 58 the problem is still present) anybody has upgdraded the portal and verified that the problem is not present?

    Many thanks

    Matteo Stocco

    (0) 
  7. ANDREA KREGAR

    Already updated the portal to latest 7.31 19 patch level. The issue with Chrome is still present.

    At least, now I can access the admin page with IE (prepatched system had an issue rendering the left menu).

     

    K –

     

    (0) 

Leave a Reply