Personas 3.0 Slipstream engine not working after 1809 upgrade

[ashok_mohan]

Hi,

The slipstream engine was working fine in 1709. But after we upgraded to 1809, slipstream engine is not working. After the credentials are entered in logon screen, the page is blank. In the HTTP trace, some access denied errors are showing. The screenshots are attached.

[tamas_hoznek · Accepted solution]

Hi Ashok,

We are processing your corresponding support incident and will provide a solution to this problem shortly.

[ashok_mohan · Accepted solution]

Dear Tamas Hoznek

Issue resolved.

[tamas_hoznek]

By now there is a note fixing this problem: 3071554

[lauraquinterosa]

Thanks Tamas for guiding me to this note. I applied it though now I have a different issue:

I tried executing the SE service in SICF directly (/default_host/sap/bc/se/m) and I get the below error re "rg" (/default_host/sap/bc/se/rg) and keeps "loading" SE screen.

Any idea how to overcome this issue please? can't find any notes related to this.

Thanks and regards,

Laura

[tamas_hoznek]

In this case, you should see an error in the browser console. Press Ctrl+Shift+I to start it before using the Slipstream Engine URL. What is this error?

[lauraquinterosa]

Hi,

We are having the same issue in both our servers S/4H 1909 & 2020.

Is there a fix to this or do we have to log an incident with SAP to get SE working?

Thanks and regards,

Laura

[skotti]

Thank you for getting back.

Will do.

[skotti]

Hi,

has this been fixed yet?

I am seeing this as well with our System.

[tamas_hoznek]

This is not something we (the Personas team) can fix, because it is due to a kernel regression which we don't have control over. However, we can provide you a workaround which enables SE. For this, you need to create a support incident with access to your environment (preferably the development system, so the fix can be transported to other systems on the transport path), and provide development-level access.

[timo_salo1]

We have the same error visible. How should I then proceed to get this fixed?

[tamas_hoznek]

Create a support incident with access to your dev.system, with development-level authorization granted and we'll help you with this.

[timo_salo1]

It would be nice to know what was the fix?

[tamas_hoznek]

In such cases, we log on to the customer system and use a workaround to enable SE.

The problem stems from a regression in the kernel and backend core ABAP code. There is no note to include the fix yet, due to technical reasons.