The customer is unable to log in to one of their companies due to a max number of users being reached.
In Everest, the table responsible for user sessions is EVEREST_SPM, located in the EVEREST_SYSTEM database. The user, in this case, was unable to access their WACA_CA database. Deleting active sessions for WACA_CA solves this problem.
Please note when deleting active sessions that if any users are actually logged in to Everest, they will lose that session and likely the contents of their work.
The command that worked for this situation was this:
delete from everest_spm where uid in ( select uid from everest_spm where attribute = 5 and value = 'WACA_CA')
A few more details worth knowing: This EVEREST_SPM table stores various information, by the 'attribute' field. There are 20+ attributes, and their functionality is explained in the stored procedure called insert_spm, also part of the EVEREST_SYSTEM database.
Here is an excerpt from that stored procedure, where attributes are a bit more clearly defined. 2,@ServerName
So in the above query that fixes the issue where too many users are logged in at once, we are looking for all active sessions for company name "WACA_CA".