Notifications
Clear all
Topic starter
Our users are getting the error when the log in that they are logged in multiple times to CPS. Our SQL guy has left the company and was really good at clearing this up for us. I logged into the SQL server and looked at the jobs. It appears that cleanup logins job is running as expected with no errors. Anyone have any ideas what else could be causing this? This error happens to me first login in the morning, so I know that I haven't logged in elsewhere.
Many thanks,
Gary
Posted : August 28, 2020 8:45 am
I made a utility to clear these out. Email me at [email protected] and will be happy to provide you a copy.
Posted : August 28, 2020 8:54 am
This is totally normal after a client crash when the user logs right back in. We don't ever have any ill effects from it. The users ignore it.
-dp
Posted : August 28, 2020 9:43 am
Topic starter
Yes, I know it is normal, but it doesn’t seem to clear overnight like it has in the past for us. So, when I log in tomorrow morning, it will still say I’m logged in multiple times. For me it is no big deal, but for my providers and nurses, it is one extra click.
Posted : August 28, 2020 10:40 am
If you log out normally, do you still get the message that you're still logged in, or is it just after an app crash where the user doesn't log back in until the next day?
In either case, I would tend to agree that something isn't quite right. After a normal logout, you shouldn't be flagged in the database as logged in. For the latter case, I believe there's a periodic scheduled SP that clears stale login records. Unfortunately I don't know what it is offhand.
I'm sure Arnold has a good solution for you.
-dp
Posted : August 31, 2020 1:05 am
Topic starter
I had an app crash a couple of weeks ago. Since then, I've had this issue. I log out normally and still encounter the warning message on my next login. I've checked the jobs on the SQL server and it appears to run. I'm thinking that I might have to eventually reboot the SQL server, which is something that we hate to do.
Posted : August 31, 2020 1:11 am
I would not expect a SQL server reboot to resolve the issue. Even if it did, a SQL reboot doesn't scale well--you don't want to have to do it every day.
The medlists table is a table of tables for tracking random things all over CPS. That would probably be where I start if I were digging for the problem.
-dp
Posted : August 31, 2020 1:25 am
Topic starter
Understood about the reboot. I'm just thinking that the scheduled job was getting hung up and a reboot could fix the scheduled job to clear the stale logins. I'd rather not have to reboot at all, as it has been pretty reliable for us.
Posted : August 31, 2020 1:29 am
We've noticed that the cleanup job doesn't always catch everything. We have a SQL script that we can use to manually clear up hung sessions. Maybe that would be a solution for you? The first 2 lines are just a check to make sure our counts are matching up as we sometimes have NULL sessions that cause us trouble.
select dbo.cpodecrypt(current_user_count)from ilicinfo
select dbo.cpodecrypt(max_user_count)from ilicinfo
select*from iLicUserInfo
orderby LoginName
begintran
deletefrom iLicUserInfo
where SessionID=450
commit
Posted : August 31, 2020 8:48 am
I put my utility on the CHUG Marketplace
https://marketplace.centricityusers.com/#/my-account/preview/406
Posted : September 9, 2020 3:19 am
