Login
Register
Search
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Forums
Financial Management
Lawson S3 Financials
Portal Cannot Load because of SSO Compenent
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Who's On?
Membership:
Latest:
Jeffin Joy
Past 24 Hours:
0
Prev. 24 Hours:
0
Overall:
4988
People Online:
Visitors:
53
Members:
0
Total:
53
Online Now:
New Topics
Top Forum Posters
Name
Points
Greg Moeller
4184
David Williams
3349
Kat V
2984
Woozy
1973
Jimmy Chiu
1883
Kwane McNeal
1437
Ragu Raghavan
1377
Roger French
1315
mark.cook
1244
Chris Martin
825
Forums
Filtered Topics
Unanswered
Unresolved
Active Topics
Most Liked
Most Replies
Search Forums
Advanced Search
Prev
Next
Forums
Financial Management
Lawson S3 Financials
Portal Cannot Load because of SSO Compenent
Please
login
to post a reply.
1 Replies
2
Subscribed to this topic
45 Subscribed to this forum
Sort:
Oldest First
Most Recent First
Author
Messages
alarson90187
New Member
Posts: 1
2
New Poster
Congrats on posting!
12/14/2017 7:39 PM
Hello,
We recently went through a system conversion to a different ERP and we were still using Lawson 9.0.4.
Today the system is tossing the servlet call /ssoconfig/SSOCfgInfoServlet error and we can't connect through portal. I can RDP into the machine, connect to LID, and LDAP bind to our active directory. But I cannot figure out why this error is popping up now.
I cannot access the Lawson RM or Lawson Security tools, i receive an SSO connection failure response.
I know this is way past support but that was not a decision made by me to not upgrade and spend money with a new ERP in sights years ago.
If anybody could point me in the right direction, that would be great.
Thanks,
Anthony
Jason Beard
Veteran Member
Posts: 125
New Poster
Congrats on posting!
Engaged Reader
You are an engaged reader!
Avid Reader
Avid Reader art thou!
3/9/2018 8:18 PM
Split
I'm assuming you've resolved this by now, but it looks like Websphere is not running. If it is running then check the logs under WebSphere/Appserver/profiles/AppSrv01/logs/nameofwasserver/*
Please
login
to post a reply.