Hello everyone, I've been registered for a while here, but this is my first post. I work in IT for a multi-specialty healthcare provider in Southeast Missouri. We currently run CPS 10.1.3.300 and experience tons of freezes and hangs on Windows 7. Windows XP was not immune to these issues, however 7 does experience the problems more. We have users every day who have issues simply getting into CPS and/or EMR. Here's a breakdown of some of the freezing issues we have:
1. When opening CPS, the browser opens but the login screen never appears.
2. After putting in your password for CPS, you just get the spinning wheel and the login screen never disappears and the menu never loads.
3. When printing receipts from the Billing module, the cursor just spins for long periods of time and you never can print.
4. When opening chart, you will sometimes get the 2 (duplicate) icons on the taskbar, but the Chart module never pops up. This typically results in having to reboot the computer.
I could go on with these types of issues and similar results from different modules and screens, but i'll spare you. I've gone as far as downgrading Internet explorer (9 to 8), downgrading .net framework (from 4.5 to 4) as well as many other tests trying to figure out the issue with no results. And oddly, sometimes a user will have no problems all day, and the next day they have nothing but problems. Our computers meet and exceed minimum requirements set forth by GE. One thing i have figured out is that if you kill explorer while the program is hung, the hanging module will either start working suddenly or crash. This works and is a much better solution than restarting the computer. And oddly, during this explorer does not crash or hang itself, just CPS/EMR. I can litterly let CPS sit there for 10 minutes with the cursor spinning and then kill explorer, the program will almost immediately pick up where it left off or crash (usually just continue). As a "remedy" i have created a batch file that the user can run when GE hangs. The batch file simply kills and restarts explorer. And while this is not a fix, it does help keep stress levels down when these situations occur.
Now that I've rambled on for a bit, i have a few questions. A) Do any of you experience these types of issues? and B) How do you address it or have you figured out any workarounds or fixes for this? Thanks in advance!
#1:
– Sounds like connectivity issues to JBoss. Are you rebooting the JBoss server nightly? Try it as an experiment, if you're not currently. I wouldn't expect it to be a magic cure but it should help.
– Check for networking issues between the client and JBoss machines.
– Do you have unnecessary websites in your JBoss installation? That could happen from test installations, previous install attempts, etc. You'll have to dig into the JBoss folders on the file system to find out.
#3:
– Likely related to your other issues, but it won't hurt to clear any old printers out of the dbo.PRINTERS table.
- Make sure all the daily cleanup jobs in SQL Server Agent are scheduled at reasonable times and running (coordinate with backup and reboot routines).
#4:
– Rebooting shouldn't be necessary. Killing explorer shouldn't be necessary either. Try using the "Restart CPS Processes" batch file.
I think IE 8 is the only version compatible with CPS 10, so it was probably a good idea to roll back to that.
.NET framework versions shouldn't interfere with each other. The DLLs for all install versions reside in the global assembly cache and are identified by unique version numbers, and any launching .net program should load with the correct assemblies. I think.
Look for more details in the exception log files. They're buried in hidden folders under the user's %APPDATA% folder.
Thanks Justin, any feedback is great.
1. We've actually had a test environment and during this troubleshooting we actually separated the test environment into its own server instead of running from the main app server. GE has gone as far as to send in a member of their tech staff (Andrew Hines) to check things out deeper and he found nothing wrong with our setup.
3. I'll look into that printers table and jobs schedule, though i'm pretty sure the jobs are scheduled off-hours already.
4-a. I agree, the Restart CPS processes file didn't seem to help much.
4-b. As for IE8, it's not a good idea to have IE8 running at this point anyway, but as of 10.1.3 IE9 is listed as supported.
4-c. The .net thing was just a test, it proved unhelpful so i don't bother with it anymore.
I'm still digging, and if the issue is on our side, i will find it. I think i've made it a step closer with the hanging explorer.exe discovery. Problem is, since explorer is used by everything it is hard to pinpoint where the issue lies, but i will keep working on it. My main objective with this post was to see if anyone else was having the issues that we have.
While I'm rambling, it's worth mentioning that our server environment runs on VMWare. From what i have gathered from other customers, and techs, that's not a common setup for CPS/EMR. However, that is how it was sold to us by GE and Clarity (now owned by DELL) installed everything.
You can also look for clues in the ErrorLog table.
VMWare is probably not your problem if it is set up correctly. We're running on it without issues. Although I would definitely keep an eye out for networking problems, especially for items #1 and #2. Best of luck to you.
Some the freezes may be related to stacked sessions. If users click the red 'x' rather than 'log out' CPS won't let that session go.
Rinse and repeat throughout the day and your login starts to get slower and then eventually chart will freeze.
It is related to the UI table, and below is a simple one liner to clear a users table. I don't have many providers so i just automated this script to run a few times during the day for each provider in SQL jobs
delete from UI_LAYOUT where pvid= (select PVID from USR where LOGINNAME = 'username')
edit: please note, if you see many rows being cleared by that script, that was your problem
Thanks! I have always wondered about that, but i have not checked the tables deep enough to research it. Very helpful information.