The Web Dynpro Application 'XssMenu' has expired

[Former Member]

Hi,

we implement an ESS Scenario, with One Enterprise Portal 6.0 SP17, a mySAP ECC 5.0 System with ERP2004 and a seperate server with a java stack, because our customer don´t want to install and use a java stack on their HR/ERP systems. They want to minimize the performance.

After some configurations, we get the startpage for ESS. If I click on a service like travel management it has no effect. If I click the second time, I got an error "500 Internal Server Error" with the message

The Web Dynpro Application 'XssMenu' has expired. Please restart the application either with the refresh button or click the following link XssMenu.

Same error comes, if I choose travel management in the second navigation level and click the service. And same message on every service.

Now I tried anotehr way. I call the ess startpage directly on the external java stack. And here´s no problem. All WebDynpro-Services works fine.

Can anyone help me, why the WebDynpro Service doesn´t work in the Portal?

Best regards

Christian

[ChrisSolomon · Accepted solution]

We had the same issue....and actually it was due to services on the backend (???). We ran the report....W3_PUBLISH_SERVICES (I think that is the correct name) and all was fine once more. Very odd, I know.

[Former Member · Accepted solution]

Hi Christopher,

if we call the ess direct on the java stack by browser without portal, the webdynpro services works fine.

Then the services are already published, or?

[darren_hague · Accepted solution]

I have come across this problem when the portal is running HTTP and the ESS is called using HTTPS - everything is fine when both are called with ESS.

Does that help?

Cheers,

Darren

[Former Member · Accepted solution]

we had a similar problem... and realized that it was becuase we where not using the fully qualified domain name to reach the portal, thus the "token" didn't get passed correctly to the backend system.

Maybe that will help???

[Former Member · Accepted solution]

Hi,

thanks... that was the problem.

We runs our portal qith https and the javastack was called with http.

now I changed the portal to http and it works finely 🐵

thanks a lot

[former_member110461]

We had exactly the same problem. We had multiple java servers and our switch was not retaining stickiness. So it would send the user to a different java server which hadn't got any session data for that user.

If this could be it, get something like httplook to do a trace of what is happening. We saw it switching java servers.

If you do not have multiple servers it could be switches chopping out cookies, causing the same issue.

Paul

[Former Member]

Hi Paul,

our Portal connect to the external Java stack via UIDPW.

The Jco´s of the Java Stack conenct to the ECC5.0 ABAP Stack via Ticket.