We are getting an error on all of our accounts when trying to access live data from our S4HANA systems from SAC (all S4HANA systems, dev/test/prod). Both in Edge and Chrome but works in Firefox. Happens both when trying to create a new model as well as running stories that are fetching the data from S4. Has been working fine until today.

If anyone has run into this then ideas or solutions very welcome.

The error is like this:

IOLayer Error: Error [IOLayer]: (#2001) Unexpected token A in JSON at position 0
Error [Protocol]: (#400) An exception was raisedCorrelation ID: 70707512-9134-4022-9847-295993377429 Unexpected token in JSON at position 331 Correlation ID: 24837134-8215-4089-b444-815367091721

Hello bjornvdelis ,

the issue is probably with the cookies settings in Chrome and Edge. Check out this article, everything should be explained there: Direct Live Connections in SAP Analytics Cloud and SameSite Cookies | SAP HANA Journey . You just basically need to set SamSite=None .

Hope this helps,
Adam

Hi bjornvdelis ,

As you mentioned that you are facing this issue from 07-Sep-2021 onwards. I 100% agree with you.

We are also facing the same issue from 07-Sep-2021 onwards connecting to DEV, TST, QAS and PRD systems via SAC using either via Chrome Version 93.0.4577.82 and Edge Version 93.0.961.52 browsers.

I raised an Incident with SAP, they asked us to maintain the parameters in S/4 Systems. Currently, we are not in a position to perform these changes in all DEV, TST, QAS and PRD systems. This will requires proper testing and we are going live for other applications in S4 system.

My question to SAP is why it is stopped working from 07-Sep-2021 onwards as we have not performed any changes into the connections and software changes in S/4 Hana systems.

If anyone has the proper solution then please let me know.

Thanks,

Abdul

Thanks Adam for that suggestion. As it relates to an old chrome version (80) and this is happening on both Edge and Chrome and was working yesterday on 4 different machines but none today, this must be something else. We are running Chrome version 93 (latest) but actually it was working for me on version 92 but after restart of chrome today (updated to 93) it stopped working. I have looked through the release notes of 93 and cannot see any changes that could be causing this. As this happens on all systems (dev/test/prod) I cannot imagine that clearing any cache on the backend would solve this either. Currently I am thinking it is some change on the corporate network security settings that is causing this as we appear to be the only ones effected by this. If it was something generic with Chrome 93 then I would expect a lot of people complaining about this problem.