Notifications
Clear all
Topic starter
When I do the monthly KB updates I also take the opportunity to restart my CPS-related servers. I use the "CPS essentials" Application from Triad Technologies to just take a look to see if anyone is currently logged in. In the course of a month there are usually about a dozen or so users who are no longer logged in but taking up a spot in SQL as if they are. They show that they have been logged in for weeks. I remote to the users workstation and if I execute that "reset CPS process" there is almost always at least one process to be killed there. Eventually I can get most of them cleaned up but I still have some which stay active even after a SQL restart.
My questions are, is this normal and do you all generally care about them? I am not as concerned about the ones which I can get rid of but those left over ones which remain might be zombie processes so I worry about DB corruption. Should I just ignore them or should I open a case with support to deal with them? I am guessing since Triad Technologies doesn't have an option to deal with these users, like a logout button, that there might be more to this. Is there a certain percentage of them which are "normal" to see? I have about 100 users but over a month I have 10-12 of the users which are listed there due to an application crash (I suppose) and sometimes I see the suspected zombie transaction ones.
I am doing pretty good with resources and probably OK with licensing that they would not be an issue so I could ignore them if they don't warrant a deeper dive.
Mike Zavolas
Tallahassee Neurological Clinic
Posted : August 10, 2020 1:01 am
We use this batch file to kill and then start CPS processes per user. This results in users killing their own hung processes every time they start CPS. It may or may not help in your specific case, but it has substantially reduced terminal server issues where hung processes consume irrational amounts of CPU.
@echo on
start Wbusy "Centricity" "Starting Centricity" /marquee
RunDll32.exe InetCpl.cpl,ClearMyTracksByProcess 8
taskkill /f /fi "USERNAME eq %USERNAME%" /im mbcexec.exe
taskkill /f /fi "USERNAME eq %USERNAME%" /im CPOPM06.exe
taskkill /f /fi "USERNAME eq %USERNAME%" /im ml.exe
taskkill /f /fi "USERNAME eq %USERNAME%" /im CPSBrowser.exe
start /min iexplore http://app28:9080/centricitypm/cps/
Wbusy "Centricity" /Stop
The wbusy process ( https://www.horstmuc.de/w32dial.htm#wbusy) is optional. It just launches a pop-up window so the user knows something is happening.
-dp
Posted : August 11, 2020 2:25 am
Topic starter
Wow, that's a great idea. Thanks
It won't necessarily deal with the possible zombie processes on the server but this helps.
Posted : August 13, 2020 12:55 am
