Lawson Login screen mid transactions

It sounds like the Websphere timeout feature is kicking in. There is a config file where you can set this - I think the default might be 10 minutes.

You should also check your Lawson sso timeout. Are your users leaving the session idle for ANY period of time, or are they truly getting timed out mid-transaction? If they do an inquire, take a phone call, and then click change, then SSO timeout is probably working correctly, but is just too short.

Ok, I think that's what I was referring to. There isn't more than one timeout value in LSF9 is there? We also had to tweak the "secs to load" value since users with low bandwidth who were getting a portal initialzion failed error but that was before even logging in for the first time.

Hi John, Joe
I will recheck the ssoconfig value but i dont think thats set to a low value.
This issue has been noticed not while the user has left the session to do other things, but actually midway through entering a transaction
i.e they start the transaction, and half way through the screen get the login screen , enter user id and password and carry on completing the transaction
Regards
Saurabh

Just checked the ssoconfig it seems to be set to 60 mins

Saurabh, Can you elaborate on being "in the middle of a transaction" and what screen are they in when this happens? Did you check LATM and LADB log files? I've not had much luck resolving errors in them but the GSC normally has you to check them. I'm not sure what you mean by migrated to a new IP. Did you just change the IP or move LSF to a new machine? I'm not sure if it's possible that you have some users pointing at an old DNS or DHCP server, but it still sounds like the session is timing out and SSO is requesting reauthentication. The next time this happens, ask them if the name field is grayed out and if they just need to enter password. I seem to remember that when SSO times you out the login fields presented look different than the initial login screen is displayed.

Hi Joe,

One of the session in question was AP90.1 (i can send you a screenshot if you let me have your email id- cant see an option here to attach a file). I did do a search in the latm and ladb logs but could not see any timeout errors in them (nor in ios logs). Can try and find a few more examples tommorow

We recently moved our servers from one data centre to another , but the only change that happenned was that the lawson Apps and DB server got moved to a new IP address range. The Server name and Domain did not change (this was done around 4 weeks back)

The DNS is all correctly updated (and resolves to the new ip address)

Regards
Saurabh

Another session where this issue is happenning is AP10
have checked logs and cant find anything written to it

regards
saurabh

Does it happen in LID too? I am assuming you are still capable of using LID.

If it doesn't happen in LID, then it's pointing to the portal server.

I would troubleshoot from the IIS/Websphere end since you already check all the lawson log files and no errors. Probably the IIS dropping users, thus, users need to re-login.

All our users login via the portal.

Checking the IIS website for lawson it has a timeout of 120 seconds, that does seem a bit low.
Would changing that have any effect?

Also this only seems to be happenning randomly across the user community I.e not everyone at the same time or same location. This makes it even harder to diagnose
regards
saurabh

I have mine set to 240. You could try bumping it up, but I think that is just the timeout value for the initial connect. Your users are conencted to the lawson server via Portal and are not getting an http 400 or 500 error, just a reauthentication request. If someone bounced your WAS or LDAP services everyone would get booted so you'll need to dig a bit further.

Do you have enough licenses for the applications?

licsta to see the peak usage for each module...

Apologies for the delay. we seem to have around 150 or so licenses. had done it a few times and it never reached that limit.
will try it again at random times next few days
thanks
saurabh