Our company upgraded to 10.1.3.300 due to GE's advice of fixing the error messages we were receiving. After upgrading, we immediately received multiple error messages on the PM side.
Error Messages:
- "Error occurred in class , method CTransactionMgmtWndCtrl::OnBtnDelete Encountered an improper argument."
- "Error occurred in class, method CTransDistWndCtrl::OnQuickPay
Encountered an improper argument." - "Error occurred in class An exception was generated in SEH Exception and caught in CMainFrame:Unknown error 0xC015000F"
- When users are in scheduling, billing, or chart the system freezes and automatically kicks users out.
- Intermittent- Providers accessing patient charts and submitting orders will receive a frozen screen "Caused by: com.gehcit.cp.security.exceptions.LoginContextExpiredException: Invalid or expired Client ID: 6220"
- Intermittent- MA’s receive the below error message within scheduling
"An error has occurred in the script on this page.
Line: 288
Char: 30
Error: An outgoing call cannot be made since the application is dispatching and input-synchronous call.
Code: 0
URL: http://centddaapp:9080/centric.....hedule.jsp ?
Hub=19256&view=2&NotUsingViews=0
Do you want to continue running scripts on this page?
Yes or No" - "Error occurred in class SEH Exception, method CMBCChargeEntryPage::OnChargeEntryPageSetFor: 0xC0000005-Access Violation"
After contacting GE support and speaking with team leads on both the revenue and PM side, their response to all of these error messages was:
"This is a known issue and you will need to reboot your servers nightly to resolve"
I understand that rebooting our servers nightly can repatch and refresh all of our applications..but for us to get all of these error messages by different users within the first couple hours of working in CPS, I don't believe that rebooting will resolve all of these problems. The worst is that we only have a fraction of our staff using production at this time..so more than likely there are many other error messages within the EMR side that we have yet to encounter"
Is anyone else getting thrown around by GE stating that the error mesages are just "known issues"? I read a couple forums stating nightly reboots but what about receiving multiple error messages with no solution?
Have any of these issues been resolved??
would also like to know if these issues have been resolved.
Did you receive SPRs (product defect numbers) on any of these error messages? We have been escalating this with GE Support & Development but had not gotten to "known issues" or the recommendations that they sent to you.
I have been receiving the error below for over a year and have never been able to get anyone from GE to assist. Has anyone out there had any luck tracking down the issue? We receive the 0xC0000005 in many different areas not just charge entry.
Thanks,
Davy
- "Error occurred in class SEH Exception, method CMBCChargeEntryPage::OnChargeEntryPageSetFor: 0xC0000005-Access Violation"
We're on CPS 11.1 and are having quite a bit of exceptions and errors as well. We are getting the same feedback as everyone else; that these are known issues but none are being corrected. If any one has any suggestions or resolutions for any of these errors that would be so awesome!
Here are a list of errors we are receiving:
- Open: RECURSIVE ROW CHANGE ON TABLE FIRING TRIGGERS TOO COMPLEX
- Error occurred in class MedToolDialog, method
SelectMedicationRow Medication could not be found While updating the medication
list
- Error: 32785 Possibly too much data for field.retry? --> This happens when trying to print a complete chart to a pdf
- Error occurred in class, method CNoteView::onUIRefresh
- Unhandled Exception caught in App_DispatcherUnhandledException
- Error occurred in class MedToolDialog, method SelectMedicationRow Medication could not be found
- Error occurred in class WebServiceClientbase, method CallWebService
- Error occurred in class, method Window::WindowProc
Sorry to say I never had any luck getting GE to resolve any of these issues. Promises were made and broken many times.
Thanks dmontgomery. If I have any solutions I will surely post them here, but so far we're in the same boat. Hopefully we can get these resolved soon! Our customers aren't too happy about it.