We are experiencing issue with opening chart in the schedule module where it tries to open the chart, then you get a blank screen then cps crashes. It happens to everyone but for some users a lot more than others. The only way back in is to relaunch cps. Anyone experiencing this?
I just tried it. It worked fine for me. Is this a term server environment? What are the error details?
-dp
it works fine most of the time but for some users it crashes like 5-10 times a day. the error is centricity practice solution Dll is not responding. Apphangb1.
You didn't mention if this was a term server environment or not.
Apphangb1 does not seem familiar to me.
Have you checked the C:\Users\<username>\AppData\Local\Centricity\Logs\ folder to see if the log files have any more detail?
If this is a term server environment, there are a couple of registry tweaks that may help. The problem description doesn't sound like your issue, but maybe your trouble is related. We set these values on all of our new term servers.
Term server users can't open very many schedules. Too many resources have been selected
- http://support.microsoft.com/kb/981013
- [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management]
- SessionPoolSize"=dword:00000030
- SessionViewSize"=dword:00000040
CPS frequently crashes. Error log reports display-type issues.
- The default number of GDI objects available for a process is 10,000. The default can be increased to 20,000 by setting the following registry entry to 20,000 (DWORD): HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows\GDIProcessHandleQuota
We are using rds 2012 r2.
Does this also happen if you try to access that patient as soon as you log into Centricity?
I think this is a related issue to another thread I recently brought back from the dead:
https://centricityusers.com/forum/cps-12-2-appcrash-error-for-multiple-users
Did you ever find a solution? We have been working to track this down for a week now, and have some leads, but nothing has paid off yet. In that other thread, there was a recommendation to rollback to an older version of .NET, but that breaks our Document Manager, so that's a no go.
We also tried running regbin, but that only worked on one term server and not another (we also need to do more research with this one).
I want to mine from as many places as I can to see if a solution has been found and/or help find a solution for everyone. We have made GE aware that we are also experiencing this issue, but hasn't offered any assistance yet.
Our workaround right now is telling providers to log in and access a test patient that we know works, then to move to the patient they originally wanted to access. It appears that once you get into a chart, all charts work until you log out. It's kind of gross, but it's what allows our providers to get their work done.
Heard there are issues with .NET 4.6 and above and increased crashing w 12.2
GE said cps 12.2.2.4212 fixed this issue. We are currently on it and it seems work better and less crashing when opening chart from the schedule module.