Screen Personas 400 Session timed out error when clicking on Flavor after upgrade

[Veeramachaneni]

We recently upgrades Personas to 3.0 SP 19. After the upgrade, system health check is done and notes are up to date.

When I launch a Flavor I see the icons blank and anywhere I click on the flavor, I get 400 Session Timed out error with current timestamp. What am I missing.

Before upgrade screen is 

[Tamas_Hoznek · Accepted solution]

This sounds more like a webgui/ITS issue and not a Personas one. Something related to general session handling.

Do you have the same problem when you disable Personas using the URL parameter sap-personas-runmode=0 (with no blue line on top of the browser window and no Personas "P"), or is the problem only present when a flavor is active?

Also, I'd check the timeout settings for all related services (personas, personas3, webgui). Do you have anything set there or is it at 00:00:00 (off), which is the default? How about the profile parameter values related to session timeout? For these, involve your basis team for advice. Profile parameter rdisp/plugin_auto_logout controls the default value, but there may be others that are relevant here.

Lastly, was there any other upgrade than going from an older Personas SP to SP19? If yes, then that may also have an effect on your browser sessions and system behavior regarding timeout. A pure Personas SP upgrade should / will not cause such a difference.

These are only first guesses based on what you described, but if this doesn't help, then access to the system and more in-depth troubleshooting would be necessary.

[Veeramachaneni · Accepted solution]

Thank you so much for responding back to me. Our Basis really had to work through so many options to fix this issue and going back to a lower version of Kernel helped to fix the issue. Now The transactions are working in the New version of Personas.

[Veeramachaneni · Accepted solution]

What would be few things to check in the Personas itself after an upgrade like this, it was mainly a service pack upgrade? Thanks again.

[Tamas_Hoznek · Accepted solution]

After a Personas SP upgrade or a kernel / basis SP upgrade it is a good idea to do some basic smoke tests to ensure that previously working Personas objects still behave like they should. In your case, the other upgrade(s) caused the problem and not Personas itself (which was expected, based on the issue description). If a kernel downgrade solved the problem, then I would suggest creating a support incident, perhaps for component BC-FES-WGU and ask for clarification why the newer kernel is not working as expected. However, this may not be simple if the problem is not reproducible with the older kernel anymore.