We continue to have a problem in which EMR 9.8 SP3 occasionally crashes with the error "Exception ACCESS_VIOLATION (0xc0000005)." This happens to both fat clients and Citrix sessions. When it happens on Citrix, multiple sessions will crash at the same time, so my theory is that one session is doing something that takes down the others.
GE has been working on the problem without much enthusiasm for three weeks. Today they asked me to turn on local error logging for users who tend to have the problem. If that was needed, I don't know why they didn't ask for that three weeks ago.
I know that other clients have reported this problem. Has anyone found a solution?
Very interested in your solution, if any. My Clinic is currently experiencing very similar scenario...
Thank you.
GE ended up telling us that the Citrix problem was an issue with how the EMR interacted with Citrix and that they would need to create a fix. We're hoping that the fix exists in EMR 9.8.6, but the documentation is unclear on that point.
The problem occurs with fat clients when the PC goes to sleep. Adjust the power saver settings and it will not occur again on fat clients.
We have had the same problem in 9.8 which produces the Access Violation error. We were hoping that SP6 would resolve this, but continue to have this error.
For our practice it is not when the computer goes to sleep, but when a user is actively in the application.
Any additional solutions? Thank you,
We're in the same situation, I'll try that fix for fat clients but I would be interested to know if GE comes back with anything.
We have the same issue; all Citrix environment. No workaround, no fix. Users are getting irritated (understandably) and there doesn't seem to be anything we can do to resolve this. Only happens to a small group, thankfully. Sent log after log to GE and have only been greeted with silence. Potential fixes are promised in the next SP but they never are there. We are currently on 9.8.4
September 2016, EMR 9.8.11 and we are still having the same Access Violation errors. We've been back and forth with GE so many times since the 9.5 days with no explanation or resolution. Maybe next year?