infor.com
concierge
infor u
developer portal
documentation central
Posts
Categories
Groups
Hubs
Developer
Healthcare
Hospitality
Public Sector
CloudSuites
Aerospace & Defense (LN)
Automotive (LN)
Chemicals (M3)
Corporate (FSM/HRT)
Distribution (Sx.e/CSD)
Distribution Enterprise (M3)
Engineering & Construction (LN)
Fashion (M3)
Food & Beverage (M3)
Healthcare (FSM/HRT)
Industrial (Syteline/CSI)
Industrial Enterprise (LN)
Manufacturing (M3)
Public Sector (FSM/HRT)
Solutions
Supply Chain Management (SCM)
Human Capital Management (HCM)
Events
Groups
Your Groups
User Groups
Migrated Forums
FSM/HCM/S3 - Infor Lawson 10.x
HCM/S3 - Learning and Development
HCM/S3 - Global HR
HCM/S3 - Talent Acquisition
HR Service Delivery
Human Capital Management (HCM) - EMEA
Infor Configuration Management for Service Industries
Lawson - Business Intelligence
Lawson - Financials
Lawson - Human Resources
Lawson - Supply Chain
Lawson - Supply Chain Management
Lawson - Technology
MSCM on Landmark
About
Community News
Email Community Support
Home
Groups
Pegasus - Partner Community
Open login screen prevents other users from logging on
Alex Aherne
Good morning,
We have one particular customers whose Opera users are unable to stay out of the system when told. They have a tendency to constantly try to log in (even through there's a shutdown/lockout in place) and leave the login screen sitting open even when they cannot log in.
We have found that when they leave this login screen open it seems to lock the SEQLOCK table and no other users can log into Opera (get a 'too many users message) until the login screen is closed down.
Has anybody else come across this? We've not been able to recreate the issue offsite as yet. All servers are 2008 R2, users access via remote desktop servers. They are running Opera 3 v2.14 but this has been ongoing for a fairly long time so occurred on earlier versions too.
Thanks,
Alex
Find more posts tagged with
Comments
alan-bourke
Just sitting at the login screen doesn't lock SEQLOCK or even have it open (you can verify this on your own PC by using Process Monitor).
It's more likely there is a terminal services session somewhere with somebody logged in.
Alex Aherne
Hi Alan,
There are no users logged in as they have all been cleared out to complete exclusive processes (e.g. upgrade, UDS or period ends).
As you've said it doesn't lock the SEQLOCK table which is why we've not been able to recreate this offsite. But it does lock on their system and users attempting to login after the user with the login screen open get a 'too many users, unable to login' message.
alan-bourke
We have had one site with a sort of similar issue - a large hospital with a lot of users.
The way the login works is that it will step down through SEQLOCK and look for the first record where lk_user is blank, assume that this slot is free and try to rlock() the record. However for whatever reason this site would end up with a record with lk_user empty but already locked. Thus someone would try to log in, it would hit this record and try to lock it and fail, and throw a 'Too Many Users' message, which is misleading.
The solution was to get all users out, zap SEQLOCK. After which it would be OK again for a month or two. I suspect it was because of users crashing and not telling anyone.
Important Links
Community Hubs
Discussion Forums
Groups
Community News
Popular Tags
CPQ: Ask a Colleague
FAQs, How-To, and Best Practices
Idea
Infor OS Portal
UI Design
CPQ: Tips and Tricks
Widget Development
Infor Homepages
Infor Ming.le
Infor EPM Migration
