Latest Webview2 Version 144.xxx causes problems with SAP GUI HTML control when using edge

[Bernd Welter]

Hi there,

recently I've been approached by multiple, independent partners / end customers who face issues in the map rendering of PTV map services: In the SAP TM frontend the map doesn't show properly. In the JavaScript console various resources seem to be "unavailable".

As different backends have been affected

• PTV xMap Server2 OnPremise
• PTV Developer Raster Maps API

I've been quite optimistic from scratch that the common factor is located outside our component but has a severe impact on users who rely on us.

After some investigation we spotted several mutual factors:

• All parties uses SaaS frontends of SAP TM
• Depending on the broswer the error occured:
  • Chrome: errors
  • Edge: errors
  • Firefox: ok

Magically these errors vanished in the last hours and maybe someone has patched the system in the background.

Nevertheless I'd like to share this article with you: Latest Webview2 Version 144.xxx causes problems with SAP GUI HTML control when using edge

Sounds like this is related to the story

Bernd

[Bernd Welter]

Further URLs that have been mentioned in this context:

• 2711181 - GIS Connector SCP Spatial Services:

  Symptom: It is not possible to connect from a SAP Transportation Management to SAP Cloud Platform Spatial Services to consume GIS services like geocoding, distance amd duration determination, and georouting.

• 3704912 - Latest Webview2 Versio 144.xxx causes problems with SAP GUI HTML control when using edge as browser control in SAP GUI for Windows

  Symptom: Since the automatic latest Webview2 Version 144.xxx from Microsoft the HTML control is not working properly anymore when usin "edge" as browser control in SAP GUI for Windows

[Bernd Welter]

Hi there,

meanwhile at least one client created a ticket at SAP and got the following response:

This issue has been identified in both our internal systems and among other customers.
Based on our analysis, the root cause is associated with recent browser updates.
To resolve this issue, we kindly request that you upgrade to the latest available versions of Chrome ore Edge.
Following the update, the map should render as expected.

Bernd