Not usually a complainer! OMG sp 11 is a doozy. Initially not so bad (1 week) Now app crashes every 2-3 update signs. 5 or 6 different crash messages. All update opens are now taking a quick 7 seconds to an appalling 45 seconds. We are a small clinic with excellent hardware resources. We started on Oracle 5.6 and have upgraded over the last 15 years. (we've seen it all) . Archiving OBS likely not a solution. GE engineers very pleasant but not very helpful. They are scrambling with 30 to 40 other clinics in a similar situation.
Very difficult to work through a clinic day when you have to restart CPS every 2 patients.
Very unhappy with SP 11. Until issues are resolved I highly recommend not adopting sp11.
Disturbing
Thanks for the heads up. I miss the Oracle Days, and the simple medics on unix.
We are 3 and 1/2 weeks post SP11 and we did not really see much difference good or bad. Sorry to hear of your issues. I can't imagine having to try and support the system under those circumstances. Hopefully resolution comes quickly - please keep us posted.
Mike
we have not run into this issue at all, 1 month since upgrade. However, I have everyone on a FAT client setup and all are running on SSD drives, which made a huge difference on prior version of CPS.
More than 3/4 of my clients are FAT. All have SSD drives
The Term Server has ample resources for only 10 users signed on
32 GB ram on dual quad x5550
JBOSS only showing 7.6 GB RAM usage with almost no PROC load only intermittant spikes to 25-30% except at restart
SQL server 32 GB ram , SQL allocated 30 GB
no real problems with sp 10 at least none out of the ordinary
JJC
We have had multiple issues. This has been the most difficult upgrade for us, include version upgrades. I hate to bang on GE support, but they are in way over their collective IT heads. Sorry. To be promised a fix in the next SP is very scarey.
jcollins,
Any word form GE on your slowness? Seems like some users are getting the slowness and others aren't and from what I've heard it doesn't seem to relate to how powerful the hardware is.
Bovie,
No word from GE at all. These started 3 or 4 web ex sessions and poked around. No real help yet. App crasching with a multitude of different errors. Still with waxing and waning severe slowness for data entry.
Signed,
Seeking Solice in Sarasota
Another follow up. What is the error on the signing? Is it always the same?
Bovie,
The error on signing is THIS:
01/07/2016 10:28:59.005 FATAL Process Id #20476 ML Thread [ExceptionHandler] Error occurred in class , method CMLChartDoc::signUpdate
*****************************************************************************
I thought I would include a few of the more common crash errors from the crash dump just for completeness sake.
See Below.
01/07/2016 10:28:59.036 FATAL Process Id #20476 ML Thread [MiniDumpWriter] Writing crash dump C:\Users\jcollins.MPA\AppData\Local\Centricity\CrashLogs\ERRORLOG_92.dmp
01/07/2016 10:30:04.946 FATAL Process Id #20476 ML Thread [ExceptionHandler] Error occurred in class , method _observe
01/07/2016 10:30:04.962 FATAL Process Id #20476 ML Thread [MiniDumpWriter] Writing crash dump C:\Users\jcollins.MPA\AppData\Local\Centricity\CrashLogs\ERRORLOG_93.dmp
01/07/2016 13:29:13.292 ERROR Process Id #4568 ML Thread [CExceptionLogging]
-------
WSID: 6131 01/07/2016 1:29 PM
SPR 57494/58268: CMLLogicianApp::CheckActiveWindowOnIdle--Active window has been changed from:
0x00360c54(Update - Andres Torres -- Ofc Visit at MPA on 1/7/2016 11:26:22 AM by John J. Collins, M.D. [Doc ID: 30]) to
0x006508f8(Chart)
ChartIsNull=0, FormInVisible=0, FormMinimized=0, ChartActive=1, ChartAboveForm=0.
01/07/2016 13:29:13.317 ERROR Process Id #4568 ML Thread [CExceptionLogging]
-------
WSID: 6131 01/07/2016 1:29 PM
SPR 57494/58268: CMainFrame::OnCheckActivewWindowOnIdle(...ONACTIVATE_ENCOUNTER_FORM...).--Restore the active window to encounter form: 0x00360c54
01/07/2016 14:10:19.212 ERROR Process Id #4568 ML Thread [CExceptionLogging]
-------
WSID: 6131 01/07/2016 2:10 PM
Exception Caught In SQL Close for
01/07/2016 14:10:43.070 FATAL Process Id #4568 ML Thread [ExceptionHandler] Error occurred in class , method _lastLab
01/07/2016 14:10:43.113 FATAL Process Id #4568 ML Thread [MiniDumpWriter] Writing crash dump C:\Users\jcollins.MPA\AppData\Local\Centricity\CrashLogs\ERRORLOG_94.dmp
01/07/2016 14:10:44.148 FATAL Process Id #4568 ML Thread [ExceptionHandler] Error occurred in class , method Window::WindowProc
01/07/2016 14:10:44.166 FATAL Process Id #4568 ML Thread [MiniDumpWriter] Writing crash dump C:\Users\jcollins.MPA\AppData\Local\Centricity\CrashLogs\ERRORLOG_95.dmp
01/07/2016 14:10:45.104 FATAL Process Id #4568 ML Thread [MiniDumpWriter] Writing crash dump C:\Users\jcollins.MPA\AppData\Local\Centricity\CrashLogs\ERRORLOG_96.dmp
01/07/2016 14:17:20.598 FATAL Process Id #3948 ML Thread [ExceptionHandler] Error occurred in class , method CMLChartDoc::signUpdate
01/07/2016 14:17:20.779 FATAL Process Id #3948 ML Thread [MiniDumpWriter] Writing crash dump C:\Users\jcollins.MPA\AppData\Local\Centricity\CrashLogs\ERRORLOG_97.dmp
01/07/2016 14:28:54.272 FATAL Process Id #19932 ML Thread [ExceptionHandler] Error occurred in class , method CMLProbTabView::OnUpdate
01/07/2016 14:28:54.309 FATAL Process Id #19932 ML Thread [MiniDumpWriter] Writing crash dump C:\Users\jcollins.MPA\AppData\Local\Centricity\CrashLogs\ERRORLOG_98.dmp
01/07/2016 18:21:39.545 ERROR Process Id #4280 ML Thread [CExceptionLogging]
-------
WSID: 6120 01/07/2016 6:21 PM
Exception Caught In SQL Close for
01/07/2016 18:21:39.553 FATAL Process Id #4280 ML Thread [ExceptionHandler] Error occurred in class , method CMLLogicianApp::OnPatientChanged
01/07/2016 18:21:39.604 FATAL Process Id #4280 ML Thread [MiniDumpWriter] Writing crash dump C:\Users\jcollins.MPA\AppData\Local\Centricity\CrashLogs\ERRORLOG_99.dmp
01/07/2016 18:56:51.305 FATAL Process Id #4636 ML Thread [ExceptionHandler] Error occurred in class , method CMLChartDoc::signUpdate
01/07/2016 18:56:51.317 FATAL Process Id #4636 ML Thread [MiniDumpWriter] Writing crash dump C:\Users\jcollins.MPA\AppData\Local\Centricity\CrashLogs\ERRORLOG_0.dmp
01/08/2016 14:11:07.501 FATAL Process Id #7404 ML Thread [ExceptionHandler] Error occurred in class , method CMLChartDoc::signUpdate
01/08/2016 14:11:07.552 FATAL Process Id #7404 ML Thread [MiniDumpWriter] Writing crash dump C:\Users\jcollins.MPA\AppData\Local\Centricity\CrashLogs\ERRORLOG_1.dmp
01/08/2016 14:55:03.597 FATAL Process Id #8920 ML Thread [ExceptionHandler] Error occurred in class , method _observe
01/08/2016 14:55:03.610 FATAL Process Id #8920 ML Thread [MiniDumpWriter] Writing crash dump C:\Users\jcollins.MPA\AppData\Local\Centricity\CrashLogs\ERRORLOG_2.dmp
01/08/2016 16:27:06.603 FATAL Process Id #9592 ML Thread [ExceptionHandler] Error occurred in class , method _listProtocolType
01/08/2016 16:42:00.882 FATAL Process Id #8556 ML Thread [ExceptionHandler] Error occurred in class , method CMLChartDoc::signUpdate
01/08/2016 16:42:00.895 FATAL Process Id #8556 ML Thread [MiniDumpWriter] Writing crash dump C:\Users\jcollins.MPA\AppData\Local\Centricity\CrashLogs\ERRORLOG_4.dmp
I have also posted on this forum regarding SP11. Our practice is also experiencing many errors (unhandled exception errors, UI Refresh errors, etc.). It will crash several times a day on the same users, making for a very frustrating situation. I have been working with Quatris trying to resolve the errors but they can't figure it out as the errors are random. As a last resort, I recreated the user in Centricity and gave them a new user name too. This has stopped the errors for the employee that got the most but she's only been using her new user for two days. No errors yet! Maybe that will work for you too? Our practice uses a view environment ,VMware Horizon client so each one of our users have profiles. Hope this helps a bit.
Try going in sql and clearing the ui layout and other user settings. When we have a user having higher than normal crashing we did this and it usually fixes the problem. This would also align with your trial of a new user not having issues. Please let me know if you need the SQL script to do this.
Yes, we have tried the SQL scripts provided by GE but in our case it did not fix any of them. they even had us record the problem and they logged on our system and tried to run the scripts too without success. They are still trying to determine why it is happening.
Please give this a shot if you haven't already. This clears Window Placement, Encounter Form Layout, Shell Layout and Chard Module Layout.
delete
from UI_LAYOUT
where PVID = (select PVID from DoctorFacility where LoginUser = 'usernamehere')
Normally its giving with this at the end which limits it to just Chart Summary Layout but at least for my group we've found all four need to be cleared.
and NAME = 'ChartSummaryLayout'
The crashes could be caused by something else but its worth a shot. If you don't feel comfortable just deleting them you can select them into a new custom table before deleting them.
mcwilson, would you have any time to discuss your setup and see if I can do something to mimic this, we are seeing a slue of random issues.
Thanks!
George