Portal Login Error: "Your Session has time out. Please login and try again"

[former_member676613]

Hello All,

The user is having the issues that she is not able to View/Change Expense in portal in PROD, and the same user is able to do the activities in QA what is not able to do in PROD.

I have also checked that the users is having same set of roles, profiles, assigned to what it is assigned in PE1 and in QE2 230.

The user id comparison is also GREEN between the sytems.

The below error comes immediately when the user login to the Portal, but it does not come when user login to QA portal.

The Error :- Your Session has time out. Please login and try again

Thanks,

CB

Edited by: Julius Bussche on Aug 25, 2011 9:01 PM

Subject title made more meaningful

[Former Member]

Are you using logon tickets between the portal and the PE1? (we need to assume yes, as you have not stated anything else).

What is the lifetime of the ticket and when did the user logon to the portal?

Note that logon related errors do not always give too much information to the unsuccessful caller and this could also be misused. Your portal should ideally redirect to a generic error page asking them to contact the administrator. It is the task of the administrator to trace the logon procedure for a valid caller.

Cheers,

Julius

[former_member676613]

Hi Julius,

Yes portal logon tickets is in use, if the user is idle for 30 mins then the user will be automatically logged off.

But here the user is getting this Message when she login to Portal, After putting her User Id and password.

A screen appears of Creating Expense reports for 2 seconds then after this screen system throws this error.

"Your Session has time out. Please login and try again*

Thanks,

CB

[Former Member]

Hi Chandresh,

This some times happens with the load balancer. If the load on the system is more it might terminate the threads. Ensure that you have proper resources.

Also, ensure that the timeout token was done at cluster-wide. You can check the same from the Global properties.

You may refer SAP Note 1144722 for more information on this.

Regards,

Raghu

[mvoros]

Another guess. Is the system time in sync between portal and backend system? Or is the problem isolated to one user only?

Cheers

[Former Member]

Very good observation! I read somewhere in an old thread that the tolerance is 2 seconds between the clocks as they are intended to be in the same (server) domain.

Cheers,

Julius