Error occurred in class ServicesInit, method CurrentDomainOnUnhandledException
DllNotFoundException: Unable to load DLL 'GEHC.Centricity.EMR.Interop.dll': The specified procedure could not be found. (Exception from HRESULT: 0x8007007F)
at GEHC.Centricity.EMR.Common.Framework.Interop.InteropAdapter.NativeMethods.InitializeInteropAdapter()
at GEHC.Centricity.EMR.Common.Framework.Interop.InteropAdapter.RegisterInteropAdapterAsService()
at GEHC.Centricity.CPS.EMR.EmrApplication.RegisterAppServicesAndEvents()
at GEHC.Centricity.CPS.EMR.EmrApplication.c__DisplayClass2.b__1()
at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()
For what it's worth, I have seen an uptick in CPS-related crashes on the forum since Windows pushed out a fairly major update in late April. Something to consider is rolling back windows updates on one of your problem computers to a date when things were working properly to see if that resolves the issue. Not something you will want to maintain, but at least it will confirm that the issue is related to software incompatibilities.
Does anyone here use Windows 10 LTSB? I ask as this would help in such a situation but it may come with it's own caveats depending on the future direction of CPS. I would love to get some dialogue going so we could petition GE/Veritas to loop us in.
I would love to not worry about a clinic-wide outage due to a forced Windows 10 update. It could happen, especially with the slow adoption of MS standards at GE a lot of the time. We were not allowed to use IE11 for a long while after MS pulled the plug.
Anyway, chime in here if anyone has any thoughts.
Mike Zavolas
Tallahassee Neurological Clinic
I solved this sort of...I found a working install on another machine and copied the Client folder under Program Files (x86)/Centricity Practice Solutions.
Then I had to give it Write access for DomUsers so non-admin accounts would work.
It just seams that every machine except that 1 good one, had a bad install occur.
I agree Mike. This is a legitimate concern. The only way to truly control the end user's environment is to move to a thin client platform like Citrix or transition to virtual desktops. I have long wanted to do this but it is an expensive proposition for most organizations.