Who's On?

	Membership:
	Latest: HireIQ
	Past 24 Hours: 0
	Prev. 24 Hours: 0
	Overall: 5264

	People Online:
	Visitors: 281
	Members: 0
	Total: 281

Name	Points
Greg Moeller	4184
David Williams	3349
JonA	3291
Kat V	2984
Woozy	1973
Jimmy Chiu	1883
Kwane McNeal	1437
Ragu Raghavan	1375
Roger French	1315
mark.cook	1244

LSO timeout

4 Replies

0 Subscribed to this topic

11 Subscribed to this forum

Sort:

Author

Messages

mwilliamson

Basic Member Send Private Message

Posts: 7

1/11/2012 3:54 PM

Does anyone know how to make the session timeout different for LSO than it is in Portal? I just took an LSO Admin class and asked the question if the timeout feature was different for LSO than in Portal, the response I received response that the timeout is the same as in Portal, it is set in SSO config. My understanding is that LSO is for core users not casual users, so why not have a different timeout feature....

TrangP

Posts: 3

1/9/2013 2:58 PM

Tried to sign in LSO, then Inquiry Customer. It's spins then get error msg Does anyone know how to fix Server timed out?

Karin

Veteran Member Send Private Message

Posts: 57

1/11/2013 5:40 PM

Are you having an issue with a session timeout or can't you inquire because the server does not answer? A server timeout is an indication that there is an issue with the server.

In Smart Office there are different timeouts depending on the application you run. So M3 can have one and S3 another. As you use the application you might get prompt for your password, but it should not fail.

Do you have anything interesting in the log (launch with internal://log in the start and search field on the canvas)?

TrangP

Posts: 3

1/18/2013 9:08 PM

LSO cannot connect to any S3 application. How, where to fix, or change I tried but can't inquiry to any applications.
The log viewer msg "Error encountered in LawsonSsoHttpService: Server Timed Out"

Karin

Veteran Member Send Private Message

Posts: 57

1/19/2013 8:02 AM

Hi,
I'm assuming that you have configured the DSSO session provider in the grid?
And you only get an error when you tun inquire and not a message that Lawson /S3 usercontext can't be loaded?

I would report it to support.
Check the logs in the Grid for the session provider.
This appears to be more DSSO related than LSO so I'm sorry but I'm not sure how to troubleshoot.